DroidForums.net is the original Verizon Android Forum! Registered Users do not see these ads. Please Register - It's Free!
Results 1 to 8 of 8

Thread: why do i always get this error when using rsdlite to flash a sbf?

  1. Droid Ninja
    tktouch12's Avatar
    Member #
    5909
    Join Date
    Nov 2009
    Posts
    1,247
    Phone
    HTC Droid Incredible 2
    #1

    Exclamation why do i always get this error when using rsdlite to flash a sbf?

    i've used it twice now (to go to ese53 and now back to 2.0.1 (so i can get the ota, then i'll root it)). both times it said failed, but really worked. it scares the heck out of me. its not a big problem if its actaully working, but why does it think its failing? and could this lead to a problem later?

    i looked in program files>motorola>rsd lite and found a couple flasherrorlogs i will attach, maybe they will explain it.
    is anyone else having this problem?
    thanks

    (p.s.- i know using rsd lite is bad, thats why i'm concerned, but i'm fairly fluent in using droid)

    its .log so i can't attach it, so here it is (i wish i knew how to quote something):

    23:32:22, March 17, 2010
    Line: 517
    ERROR: AP Die ID: 0a80011843680304000000000400
    23:32:22, March 17, 2010
    Line: 524
    ERROR: BP Die ID: 0000000000000000000000000000
    23:32:22, March 17, 2010
    Line: 531
    ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff
    23:32:22, March 17, 2010
    Line: 538
    ERROR: BP Public ID: 0000000000000000000000000000000000000000
    23:36:16, March 17, 2010
    Line: 919
    ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR
    File: X:\test_dev_usb\flash\code\flashdll\RDLOp.cpp
    Device ID: 0
    23:36:16, March 17, 2010
    Line: 1182
    ERROR: Phone[0000]: Flash failed.
    File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashTh read.cpp
    Device ID: 0
    23:36:16, March 17, 2010
    Line: 587
    ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR (Error Code: e0030009),
    Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
    File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
    Device ID: 0
    got eris: 12/24/09
    returned eris: 12/28/09
    got droid: 12/31/09
    rooted droid: sometime in january (right after it was released (manually))
    bb->2.1 sbf->desire rom> 2.1bb> 2.2
    got incredible as warranty replacement 8/31/10
    shattered inc screen 9/25/10-> got insurace replacement 10/4/10
    broke inc screen 10/19/10-> got warranty replacement 10/22/10
    got moto droid 1 off ebay 1/7/11
    broke inc screen 5/26/11-> got insurance replacement inc2 5/27/11
    sold inc2 & bought vzw 16gb iphone 4 6/9/11
  2.  
     
     
     
  3. RS Admin
    jstafford1's Avatar
    Member #
    4777
    Join Date
    Nov 2009
    Location
    Hebron, Oh.
    Posts
    9,060
    Liked
    412 times
    Twitter
    jstaff79
    Phone
    D-R-O-I-D 3
    Premium Member
    #2
    Well....what's on your phone right now? Firmware, build number??
    I don't really know anything about rsd lite or the sbf, but if your phone works can get you back to stock for the OTA.
    Last edited by jstafford1; 03-17-2010 at 10:55 PM.
  4. Developer
    adrynalyne's Avatar
    Member #
    18036
    Join Date
    Dec 2009
    Posts
    2,896
    Liked
    4 times
    Phone
    Droidzilla
    DroidForums.net Developer
    Premium Member
    #3
    I believe that error means the radio flash did not go through.
  5. Droid Ninja
    JCo352's Avatar
    Member #
    36721
    Join Date
    Feb 2010
    Location
    Texas
    Posts
    1,830
    Liked
    1 times
    Phone
    Droid A855
    #4
    When I flashed to 2.1 with RSD Lite it said failed(I got scared too). But tonight when flashed back to 2.0.1 it never said failed, It never said successful either,it just said processing. Did your phone reboot by itself? Because when I flashed 2.1 I had to click "show phone", but with 2.0.1 it did it by itself.
  6. Beta Team
    JonKyu's Avatar
    Member #
    4977
    Join Date
    Nov 2009
    Location
    Provo, UT
    Posts
    2,398
    Phone
    DROID X
    #5
    This was happening to me also, the Radio flash didn't go through and it was the damn reason why I flashing the .sbf in the first place.

    I Finally got it to go through by just leaving it alone. While it was flashing the radio it would "disconnect" from the computer but it's actually trying to get into some mode to flash the radio firmware.

    Also are you using a virtual machine? I tried this first with virtualbox and got the same errors you did with the phone rebooting by itself. I finally tried VMWare and it finally worked.
  7. Droid Ninja
    tktouch12's Avatar
    Member #
    5909
    Join Date
    Nov 2009
    Posts
    1,247
    Phone
    HTC Droid Incredible 2
    #6
    it did the exact same thing when i flashed to ese53 and when i flashed back down to 2.0.1. i'm using vista, so no. both times it rebooted by itself after it said failed.

    well thanks for telling me its (probably) the radio flash didnt go through. I'll just wait for the ota like i was planning then root from there
    got eris: 12/24/09
    returned eris: 12/28/09
    got droid: 12/31/09
    rooted droid: sometime in january (right after it was released (manually))
    bb->2.1 sbf->desire rom> 2.1bb> 2.2
    got incredible as warranty replacement 8/31/10
    shattered inc screen 9/25/10-> got insurace replacement 10/4/10
    broke inc screen 10/19/10-> got warranty replacement 10/22/10
    got moto droid 1 off ebay 1/7/11
    broke inc screen 5/26/11-> got insurance replacement inc2 5/27/11
    sold inc2 & bought vzw 16gb iphone 4 6/9/11
  8. Droid Newbie
    WackoZacho's Avatar
    Member #
    116007
    Join Date
    Sep 2010
    Posts
    1
    Phone
    Motorola Droid A855
    #7

    I keep getting this too!

    I'm trying to load the Smoked Glass rom.

    I keep getting stuck in a loop as follows:

    I use RSD Lite to try to flash the 2.0.1 firmware and original stock ROM to the phone. After the first couple stages, it will say FAIL, and say "Failed downloading RAM for bootloader". If I click on the fail part, the phone will reboot, and startup normally, I'll get to the Droid activation screen, etc.

    I figure from what I've read in the posts above I can fix the radio flashing later when I update to 2.1.

    Next, I go ahead and bypass the activation screen, mount the USB drive on the computer, and pass the Smoked Glass rom and the Update.zip "give me root" zip file to the root directory of the flash drive. Then I do safely remove mass storage device etc. and unplug the usb cable from the phone.

    Next I turn off phone, reboot into the normal built in recovery mode, (not sprecovery yet) and complete the command on the menu that says install update.zip.

    After I do this, it says complete, I reboot the phone, again bypass activation, and when I look in the apps, I can see the ninja superuser app, indicating update.zip was successful and I do indeed have root.

    Now I close RSD on my computer, and reopen it. I turn off the phone and connect the USB. I turn it on into bootloader mode again, and on RSD I flash SPRecovery 3b. It finishes successfully, I get a PASS this time from RSD. (when holding up at the reboot phase, otherwise I get the whole please manually reboot the phone thing).

    The next time I boot up with x pressed to get into recovery, it does indeed load SPRecovery 3b patched by psycho, etc.

    I've followed the directions in Adams post releasing the ROM for Smoked Glass, where it says make a backup - I try to do this and it says E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory).

    I tried going to mount options from the main menu and manually clicking Mount/sdcard and I get the same error, followed by the line Mounted /sdcard.

    But it's not really mounted, because when I got back to browse the sdcard for the rom file, I get that error again.

    Also when I go to backup/restore, to do a backup, and go to advanced Nandoird backup, * all items then click perform backup, I get the following error:

    Attempting Nandroid backup... ERROR: NAndroid exited with status 31.

    I take it this is again related to the SDCard problem? What can I do here? I know the card is good, and it's inserted correctly, because my computer can read and write to/from it. I also know that the computer isn't taking control of the files preventing access to SPRecovery becaus it's ejected and the cable is unplugged.

    If I try to boot the phone in a normal mode (not sprecovery and not bootloader) then it stalls on the Moto M at startup and doesn't continue to boot. I've been able to determine that this stall occurs each time I use RSD to install SPRecovery. Prior to that, I can start normal after flashing the stock rom, and I can still start normal after rooting it, to see the ninja, it's simply after I install SPRecovery my normal boot stalls at the M.

    Might it have something to do with the flashing of the radio not finishing?

    Should I try 2b instead of 3b for sprecovery?
    Or does anyone have any other ideas or solutions?

    Thanks in advance.
  9. Droid Newbie
    scottmotron's Avatar
    Member #
    143569
    Join Date
    Dec 2010
    Posts
    2
    Phone
    DROID
    #8
    I was scrambling to reflash for warranty, and was getting this problem as well, but I did eventually get it to work by doing the following:
    * switched from win7 64 to winxp 32. Not sure if this is necessary, but i hear rsdlite is "buggy" on win7 64
    * downloaded the latest rsdlite (5.0 as of now) and drivers (4.9) from peter alfonso here
    * followed the directions carefully for properly flashing from here

    Other things
    * ticking ODM_Serial from Config->Flash/Flex Options helped some people, but this didn't work for me
    * some people needed multiple tries before it flashed correctly. I think I probably did it about 6 to 8 times before it worked. First with 4.6, then 4.9, finally 5.0. Flash worked the first time with rsdlite 5.0 and 4.9 drivers. Not sure if that's coincidence or not.
    * I can confirm that this error seems to indicate a bad radio flash. Booting into the O.S. after this error, I don't get a 3g connection

Links

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Similar Threads

  1. RSDLite Flashing
    By freemenot in forum Android Hacks and Help
    Replies: 4
    Last Post: 03-20-2010, 05:43 PM
  2. adobe flash or flash apps to view internet pages?
    By rabyfox in forum Android Tech Support
    Replies: 4
    Last Post: 02-24-2010, 11:34 AM
  3. SD Card Error
    By CDWITT1 in forum New Member Introductions & Site Assistance
    Replies: 1
    Last Post: 02-06-2010, 07:40 AM
  4. Error 21
    By bracemg in forum Android Hacks and Help
    Replies: 5
    Last Post: 02-04-2010, 11:01 AM
  5. 2.1 Error HELP
    By mglasson in forum Android Hacks and Help
    Replies: 0
    Last Post: 01-28-2010, 03:57 PM

Search tags for this page

device api error: 0xe0030009
,

error sending ram download for bootloader

,
error: flash failure: interface bp: error sending ram downlo
,
failed flashing process interface bp error sending ram downl
,
failed flashing process. interface bp error sending ram
,
interface bp error sending ram download for bootloader
,
loading ram downloader for bootloader
,
rsd lite device api error
,
rsd lite error sending ram
,
rsd lite error sending ram download for bootloader
Click on a term to search our site for related topics.

Tags for this Thread

Find us on Google+