154 replies to this topic

[wjchisholm86]

almaster87 said:

So, no noob my any stretch but I have a question about the steps. At step 3 I am a little lost. When I am rebooting and holding up on the D pad nothing happens -- it makes it all the way back to the main screen. Should it be entering recovery mode? Or do I just follow word for word and as it is boot up and as I am holding up on the D pad I click start with RSD? A little confused with that step... any help is appreciated. Thanks.

almaster87, You need to make sure you are holding up on the D-Pad before you even push the power button to turn your phone on. This should then automatically bring you to the screen.

[Sponsored Links]

• Back to top

[wjchisholm86]

The update for the 2.1 OTA was sent out in my area on 4/5/10, which is Monday, and I used this method to put my phone back to 2.0.1 in order to download and install the official release. The only problem is after rooting my phone and using custom ROMs then using this to go back to 2.0.1 I am not able to update my phone. For some reason my phone thinks it is up to date with 2.0.1 and doesn't recognize the update. I am not sure if I am the only person this is happening to but I think this has a lot to do with my phone actually not be stock even with this method of reverting back. This is not a big deal for me since I enjoy using Chevy’s amazing ROM (Simply Stunning 3.0). I just wanted to let everyone know the problem I am having and see if this is an issue that is regular.

[almaster87]

Thanks thats what it was. Much appreciated.

[NepperZ]

wjchisholm86 said:

The update for the 2.1 OTA was sent out in my area on 4/5/10, which is Monday, and I used this method to put my phone back to 2.0.1 in order to download and install the official release. The only problem is after rooting my phone and using custom ROMs then using this to go back to 2.0.1 I am not able to update my phone. For some reason my phone thinks it is up to date with 2.0.1 and doesn't recognize the update. I am not sure if I am the only person this is happening to but I think this has a lot to do with my phone actually not be stock even with this method of reverting back. This is not a big deal for me since I enjoy using Chevy’s amazing ROM (Simply Stunning 3.0). I just wanted to let everyone know the problem I am having and see if this is an issue that is regular.

I think you have to 'un-root' as well to get your phone to recognize the update

[watkins]

wjchisholm86 said:

The update for the 2.1 OTA was sent out in my area on 4/5/10, which is Monday, and I used this method to put my phone back to 2.0.1 in order to download and install the official release. The only problem is after rooting my phone and using custom ROMs then using this to go back to 2.0.1 I am not able to update my phone. For some reason my phone thinks it is up to date with 2.0.1 and doesn't recognize the update. I am not sure if I am the only person this is happening to but I think this has a lot to do with my phone actually not be stock even with this method of reverting back. This is not a big deal for me since I enjoy using Chevy’s amazing ROM (Simply Stunning 3.0). I just wanted to let everyone know the problem I am having and see if this is an issue that is regular.

I have had so many different roms on my phone over the months and when i used this process it took me all the way back to stock. But the difference for me was when i was updating to the new OTA 2.1 i was doing it manually and i know that works.

[wjchisholm86]

I just wanted to see of I was going to be able to apply the new update through the automatic update on the phone and not manual. I un-rooted my phone also. Oh well I like the high powered ROMs better anyways.

[nomad1125]

Hey can i do this on my mac because wont the command stuff be different

[bpickens]

I tried reverting my Droid from the latest OTA 2.1, back to your suggested 2.0.1, using your instructions. It looked like it was going to work, but I got the message, "Failed Flashing Process".
Before I started the RSD Lite v4.6-Flash, I selected "Show Device", and this is what it indicated:

IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x002C6C
DRM Version: N / A
AP Die ID: 1610010f28680304000000000400
BP Die ID: 0000000000000000000000000000
AP Public ID: ffffffffffffffffffffffffffffffffffffffff
BP Public ID: 0000000000000000000000000000000000000000

Is this normal for it to look like the above?
My Motorola Droid is showing:
Bootloader
2C.6C
Battery OK
Ok to Program
Transfer Mode:
USB

Please tell me what might be wrong. Is it due to my phone was recently accepted and installed with the OTA 2.1 version from Verizon?

Thanks,
Barry

[bpickens]

olta777 said:

Motorola Droid 2.0.1 sbf file released!!!

These directions come from ikithme @ alldroid. The .sbf file is used to flash a bricked droid. It will return you to a pre-rooted state.

THIS COMPLETELY WIPES YOUR PHONE AND REFLASHES IT! YOU WILL NEED TO REACTIVATE YOUR PHONE WHEN THIS FINISHES!

Requirements
A.

Please Login HERE or Register HERE to see this link!

(.sbf file)

Alt download link

Please Login HERE or Register HERE to see this link!

B.

Please Login HERE or Register HERE to see this link!

(RSDLite 4.6)
C.

Please Login HERE or Register HERE to see this link!

... _4.2.0.zip (32-bit Motorola USB Drivers)
or

Please Login HERE or Register HERE to see this link!

... _4.2.0.zip (64-bit Motorola USB Drivers)

Instructions:
1. Download all of the files above including the 32-bit OR 64-bit Motorola USB Drivers.
2. Install RSDLite 4.6 AND the 32-bit or 64-bit Motorola USB Drivers (Depends on your system most will need 32-bit some will need 64-bit)
3. Connect your phone to USB and turn it off then while your phone is booting hold up on the DPAD.
4. Run RSD Lite 4.6 as Administrator (For all you Vista and 7 folks out there. If you are using XP you may not need to run as Administrator)
5. Click the ... next to the filename box and browse to where you saved the .sbf file and double click the .sbf file.
6. Hit start and below it should give you completion progress and all of that.
7. Once your phone is done being flashed (It may take a while so don't unplug it) it will reboot and you will be back at stock 2.0.1 no root.
8. Done

I get to your step 7 but my phone does not reboot automatically, even after I select "Show Device" on RSD Lite v4.6-Flash. I waited for 5 minutes, but still no reboot took place.

Thank you for any help from anyone.

[bpickens]

bpickens said:

I get to your step 7 but my phone does not reboot automatically, even after I select "Show Device" on RSD Lite v4.6-Flash. I waited for 5 minutes, but still no reboot took place.

Thank you for any help from anyone.

I figured out what was going wrong with my Droid not rebooting by itself. The problem was with the first .sbf file download,
A. VZW_A855_ESD56_QSC6085BP_C_01.3E.01P_SW_UPDATE_03. sbf (.sbf file) . Maybe it was corrupted or something. I tried it again with the alternate download site,

Please Login HERE or Register HERE to see this link!

, and this .sbf file worked successfully. It sure helps by reading further through the postings, which is what I did to figure it out.

[pb_develop]

I am currently on 2.1-update1. As I understand, it is required to flash down to 2.0.1. I am preparing to do this, however this is the first message I have seen regarding "REACTIVATE". What does this entail? Does it require having your carrier reactivate the phone?

If it is possible, could someone outline the steps for reactivating the droid once flashing to 2.0.1 is complete.

Thanks much!

[BBCrackman]

Once you successfully flash your device reactivating entails the same steps as when you purchased your phone. It will turn on and you will have a button that says activate, once pressed a dialpad will popup and all you have to do is listen to the prompts. Select 1 and the phone will gather information then activate and you will now be able to proceed with setup. Hope that helps

[giuseppe]

I accepted the OTA update thinking that the hype would be true and I'd have Flash 10 support along with swype. After I realized that 2.1 didn't bring much to the table I wanted to go back to BB 0.9 with Smoked glass but I couldn't root! Thanks for the post and helping me get back to the custom rom that delivered more than this much anticipated OTA update did!

:no

[tdiebold]

Am I supposed to be booting up into safe mode?

[tdiebold]

I am trying to follow the directions given on returning back to 2.01. When I hold the D pad while booting up my phone, am I supposed to be entering into safe mode?

That is what is happening to me. Also, if I am supposed to be in safe mode, when I run rsd lite on my comp and browse to the sbf for 2.01 and click start, nothing happens. Thoughts?

Do I have to mount my phone?

[olta777]

tdiebold said:

I am trying to follow the directions given on returning back to 2.01. When I hold the D pad while booting up my phone, am I supposed to be entering into safe mode?

That is what is happening to me. Also, if I am supposed to be in safe mode, when I run rsd lite on my comp and browse to the sbf for 2.01 and click start, nothing happens. Thoughts?

Do I have to mount my phone?

You have to hold the "up" on the dpad. Welcome to MyDroidWorld!!! :)

[vertigoelectric]

I am so frustrated. I knew I would have to wipe the user data in order to root my phone, but I figured it would be worth it... but nothing I'm trying is working to root the device.

I am also getting FAIL errors while attempt to flash the phone with RSD Lite. I have even tried running via the command prompt as suggested in this thread. However, even when the flashing fails, when I reboot the phone into RECOVERY it does allow me to apply the update.zip file that I have copied to the SD card using instructions I got at the following web site:

Please Login HERE or Register HERE to see this link!

So I guess one of my questions is... Which part of the process is incorrect? The flashing, the manual updating, or both?

Here is a copy of the FAIL log generated by RSD Lite the last time I attempted to flash the phone via the command prompt method posting in this thread:

-------------------
13:07:08, May 09, 2010
Line: 517
ERROR: AP Die ID: 06e0010d1b680304000000000400

13:07:08, May 09, 2010
Line: 524
ERROR: BP Die ID: 0000000000000000000000000000

13:07:08, May 09, 2010
Line: 531
ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff

13:07:08, May 09, 2010
Line: 538
ERROR: BP Public ID: 0000000000000000000000000000000000000000

13:14:31, May 09, 2010
Line: 919
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x150000 Command: ADDR
File: X:\test_dev_usb\flash\code\flashdll\RDLOp.cpp
Device ID: 0

13:14:31, May 09, 2010
Line: 1182
ERROR: Phone[0000]: Flash failed.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

13:14:31, May 09, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x150000 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

13:15:34, May 09, 2010
Line: 1492
ERROR: Error getting subscriber unit information.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

13:15:34, May 09, 2010
Line: 1492
ERROR: Error getting subscriber unit information.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
-------------------

Any help would be very, very appreciated. I know this thread is kinda old...

[BBCrackman]

Welcome to MyDroidWorld vertigoelectric! Sorry you are having difficulties. Lets see if we can get you going.

1st lets make sure you have everything
SBF file from OP
Drivers from OP
RSDlite from OP

If you have those boot your device into bootloader (power off, press D pad and while holding power on device)
Connect Droid to PC via usb
Launch RSDlit
Select the SBF file from the dropdown menu
Start
Let it finish, it may fail it may not, either way the device will reboot on its own.

Once we get back to 2.0.1 we will continue to root

[rony07]

After reverting down to 2.0.1, I have no mobile network. Any ideas?