When the ota hit my droid 2, I couldn't update because I deleted all those stupid apps like vznav, blockbuster, amazon mp3, etc and couldn't upgrade without reverting my cell to stock. I hear that if you have a rooted droid 2 with just some rooted apps and haven't deleted anything, you can use the ota or skip reinstalling 2.2.20.
I understand this is a common issue right now so here is how I did it successfully.
First Download these files as they are ABSOLUTELY necessary.
Motorola drivers for omap 3630
RSD lite 4.7 & patch (4.8 and 4.9 didnt detect the device on my pc)
2.2.20 firmware (stock at launch)
2.3.20 firmware (latest)
2. Install RSDLite by double clicking the RSD Lite.msi file you just downloaded.
3. Once RSD Lite is installed, copy the pst_flash.ini file you downloaded with the RSD Lite install file and paste it into C:\Program Files (x86)\Motorola\RSD Lite OR C:\Program Files\Motorola\RSD Lite depending on where your computer put it when installing. Allow it to overwrite the existing pst_flash.ini file.
3. Unzip the drivers folder you downloaded (32 bit OR 64 bit), then double click the Motorola Consumer Driver Installer application and install the drivers.
4. Plug in your phone to the computer via USB cable and pull down the notification bar and choose USB connection as PC Mode.
5. Open the RSDLite program by right clicking it and selecting Run As Administrator.
6. Click on the “…” button next to the filename box and select the DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file you downloaded earlier.
7. Once it is selected, hit Start and wait for it to finish flashing the phone.
8. Once it is done, click on the “…” button next to the filename box again and this time select the BL_D235_cdma_droid2_Consumer_replacer_HSPart.sbf file you downloaded earlier.
9. Once it is selected, hit Start and wait for it to finish flashing the phone.
10. Once both have been flashed, your are back to the stock Android 2.2 firmware.
11. Load in recovery mode and reset to factory default.
You can either upgrade now over the air or you can load the sbf for 2.3.20.
1. Plug in your phone to the computer via USB cable and pull down the notification bar and choose USB connection as PC Mode.
2. Open the RSDLite program by right clicking it and selecting Run As Administrator.
3. Click on the “…” button next to the filename box and select the VRZ_A955_2.3.20_1FF_01.sbf file you downloaded earlier.
4. Once it is selected, hit Start and wait for it to finish flashing the phone.
5. Bam you have 2.3.20, now you can do a recovery factory reset and do your thing.
From what I have seen on the web, you can't use this sbf if you installed the OTA cause it will brick your phone but you can reflash this sbf if you upgraded using this sbf.
I do not know if you can just take your rooted phone with deleted apps and flash the 2.3.20 over your current 2.2.20. I do know the process I used worked without a hitch.
Edit: Hey guys, after the patch I noticed bad battery life and my battery monitor wouldn't open. Apparently you will need to boot into recovery and wipe the cache partition. All the links work.
Thanks for taking the time to write this up ! Much appreciated =)
Sent from my DROID2 using Tapatalk
so does this mean if i'm on 2.3.20 and want to go back to stock( and reflash to 2.3.20 is impossible??.... I'm doing this because i went directly from fission 1.2.1(stock band) to 2.3.20 and just want to make sure whether i have the latest kernels
This isn't entirely correct. If you use the 2.3.20 FULL FLASH SBF, you do not need to restore back to 2.2.20, or reinstall any missing applications. The full flash is the entire stock sytem, as well as the bootloader and the kernel. So you can start from any D2 on any previous firmware with any modifications (removing apps, installing custom ROMs, etc) and if you hook it up to RSD and use the most recent full flash it will restore you back to stock on the newest kernel/baseband and restore all missing applications, everything. The full stock flash will take you back to stock regardless of the state of your D2, including if it is bricked and stuck at bootloader. The extra steps are not needed
Also, RSD 4.8 and 4.9 do work, provided you have the latest motorola moto connect drivers installed. If you are having connection issues with RSD put the phone in bootloader mode (not recovery) before you connect it to the PC.
You were correct in stating that you can not receive or apply the OTA by itself without having the original system with all pre-installed apps intact.
is there a way to go from 2.3 to 2.2, like the original kernel and radio, baseband that most people were running like a month ago. im trying to sbf form 2.3 to the older one and i keep getting errors is there any way i can go back?
Not currently. The bootloader has been updated and will no longer accept the old kernel.
Sent from my DROID2 using XDA App
zibrah3ed said:
Not currently. The bootloader has been updated and will no longer accept the old kernel.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Thanks for the reply. now i can stop trying lol, it was driving me crazy.
bladearronwey said:
This isn't entirely correct. If you use the 2.3.20 FULL FLASH SBF, you do not need to restore back to 2.2.20, or reinstall any missing applications. The full flash is the entire stock sytem, as well as the bootloader and the kernel. So you can start from any D2 on any previous firmware with any modifications (removing apps, installing custom ROMs, etc) and if you hook it up to RSD and use the most recent full flash it will restore you back to stock on the newest kernel/baseband and restore all missing applications, everything. The full stock flash will take you back to stock regardless of the state of your D2, including if it is bricked and stuck at bootloader. The extra steps are not needed
Also, RSD 4.8 and 4.9 do work, provided you have the latest motorola moto connect drivers installed. If you are having connection issues with RSD put the phone in bootloader mode (not recovery) before you connect it to the PC.
You were correct in stating that you can not receive or apply the OTA by itself without having the original system with all pre-installed apps intact.
Click to expand...
Click to collapse
I gotcha, well it works exactly as stated so it was safe and is safe to do it the way I flashed. I will edit the sticky though to remove irrelevant info. Also reflashing the 2.3.20 sbf after flashing once yielded no errors. I'll edit the op.
Well I ran into big problems. I had 2.2.20 and wanted to sbf to 2.3.2 and it worked all the way up to downloading ram to bootloader and froze and got stuck and I sbfd back to 2.2.20 with no errors. Now my phone says the system is 2.3.2 but the baseband is still .05 and I tired to flash sbf to 2.2.0 today and I got the same downloading ram to bootloader and now I can't get even 2.2.20 to run on the phone. With this being said I got stuck on the bootloader screen(told me there were some errors and battery okay and plug in usb) so I figured id try to sbf to 2.3.2 and it came up with the same error of "downloading ram to bootloader and froze" and the phone restarted but now the M showed back up and is running normal now with the system 2.3.2 but still old baseband so idk what went wrong and why it wont let me get past downloading ram to bootloader. What's wrong because I've tried several times now and I just want the new baseband and bootloader. Please help me
Sent from my DROID2 using XDA App
you cant downgrade from 2.3.20 to 2.2.20 because of the updated bootloader. What OS are you using? What rds are you using? did you copy over the fix into the rds directory? You may have bricked your phone by tryin to downgrade =(. Have you tried loading your phone into recovery?
JonandRoid said:
Well I ran into big problems. I had 2.2.20 and wanted to sbf to 2.3.2 and it worked all the way up to downloading ram to bootloader and froze and got stuck and I sbfd back to 2.2.20 with no errors. Now my phone says the system is 2.3.2 but the baseband is still .05 and I tired to flash sbf to 2.2.0 today and I got the same downloading ram to bootloader and now I can't get even 2.2.20 to run on the phone. With this being said I got stuck on the bootloader screen(told me there were some errors and battery okay and plug in usb) so I figured id try to sbf to 2.3.2 and it came up with the same error of "downloading ram to bootloader and froze" and the phone restarted but now the M showed back up and is running normal now with the system 2.3.2 but still old baseband so idk what went wrong and why it wont let me get past downloading ram to bootloader. What's wrong because I've tried several times now and I just want the new baseband and bootloader. Please help me
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Make sure you use the FULL FLASH and not the system only file
Renegade8100 said:
you cant downgrade from 2.3.20 to 2.2.20 because of the updated bootloader. What OS are you using? What rds are you using? did you copy over the fix into the rds directory? You may have bricked your phone by tryin to downgrade =(. Have you tried loading your phone into recovery?
Click to expand...
Click to collapse
Im using RDS 4.9 there was no inf files that came with .9 so idk what you're talking about. I know 4.7 required a patch but idk if the new ones require it. I have fission 2.0.1 and my phone didn't brick because I have it up and running right now but I still don't have the new baseband mine is still .05...
Sent from my DROID2 using XDA App
JonandRoid said:
I still don't have the new baseband mine is still .05.
Click to expand...
Click to collapse
There's a tutorial on my "[TOOL] Ubuntu livecd" thread on how to update the baseband only, after flashing 2.3.2. Just go to the bottom of the OP and it will all be there. (I'd quote it but I'm on my D2 not my computer)
Sent from Newk's DROID2 using XDA App
No files
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
ameggs said:
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
Click to expand...
Click to collapse
This should help you out.
http://www.mydroidworld.com/forums/...rld-present-droid-2-2-3-20-triple-threat.html
ameggs said:
Hey thanks for the Tutorail. Looks like the 2.3 Update is no longer being hosted. Can you point me in another safe location.
Click to expand...
Click to collapse
The update file in my tut still works for me. Update.zip
All the links should work. I just uploaded the 2.2.20 to include the drivers and rsdlite
bladearronwey said:
Make sure you use the FULL FLASH and not the system only file
Click to expand...
Click to collapse
FYI, I did the full flash for 2.3.20 because the automatic update kept failing. Not sure why it didn't work - I had rooted the Droid2, "removed" a few annoying apps by renaming the adk and odec files to .bak. I unrooted it and tried the auto update again but it failed. Not sure what was making it fail, but rather than put all the apps back and try letting the phone do its thing, I used the method above - just using RDS Lite to flash to 2.3.20 without doing the previous steps.
It worked fine, but I had to dial *22899 to re-activate the phone afterward.
So far so good, but I'm not sure that rooting the phone and messing around with it, to the tune of a few good hours of my life, was worth a little bit of battery life, especially considering the 2.3.20 is supposed to fix the two problems I had with the Droid, namely poor battery life and email sync problems after inactivity.
thanks for the how-to! i flashed straight over from a rooted 2.2 phone to the new version as well.
i did experience force closes on the battery monitor as well, and clearing the cache did not fix that. i cleared, rebooted, and when it still didnt work, i flashed the phone once more and all is well. did not need to clear cache a second time. im a rookie still at all this, so bear with me if my reply seems obvious- or doesnt make sense.
i also had to reactivate the phone with the *# referenced above.
thanks again!
Had no problems updating from 2.2 to 2.3 using only the 2.3 SBF. Worked great and kept all other settings intact.
To fix the battery monitor force closing issue; just plug your phone into the charger while it's on! Fixed the issue right up for me!
Allright, I've got S-OFF, it's rooted, and I've switched between Sense and CM7.1ALPHA's for a few times, but I'm mainly using Sense (CM just isn't stable enough, yet ), and since the latest OTA update, I'm looking for ways to install that, though simply following http://forum.xda-developers.com/showthread.php?t=1228648 does not work because there doesn't seem to be any TMO_NL ruu for the sensation.
I've tried using the EU version from the previously mentioned thread, but that failed at
"7. When the application finishes flashing, press <No> which will reboot into recovery."
I pressed no, but it did not go to recovery, instead it siimply rebooted, and it looked like it had reset itself to factory settings.
I tried to download and install the OTA update anyway but to no avail.
I've heard about unbranding by changing the CID, will this make me able to use other recovery images to then install the OTA?
Current Software number: 1.45.114.1 / TMO_NL_1.45.114.1
Carrier: T-Mobile NL
Desperate bump.
Got the official update today, was so excited. did not relise i would have so much trouble with it. first off i didnt relise having a rooted phone even with stock rom meant i could not install it. so i followed a few tutorials on here and installed my original RUU was fine but now after it all working, i downloaded the update and its reboots and comes up with an android phone with a red triangle then reboots. so i googled it and thought it my be recovery problem. so i re unlocked my phone. flashed the original ville_recovery_signed.img. re ran the ruu exe and all went well. downloaded the updated officialy again and still the same error? i have no idea what to do next, any help?
Thanks
Hello. I decided to start a new thread. I have a Moonshine s-off phone. Recently I reset the phone put stock recovery on it and ran the newest RUU. It worked I got the new software[emoji3] . Then I unlocked the phone using the HTCDev method and my old unlock key, everything worked, when I went into BOOTLOADER phone said TAMPERED UNLOCKED S-OFF.
The only thing missing is my camera. Sometimes it turns on, but very rarely ( maybe 1/200 tries ). It tells me Unable To Start The Camera.
I think it's a software glitch, as with previous version of Android I had no issues. Also with the new OS the flash is BUSY sometimes. When I want to use a flashlight phone tells me PHONE SCREEN WILL BE USED FOR ILLUMINATION SINCE THE FLASH IS IN USE BY OTHER APP. There is no other app running...
I tried flashing TWRP but fastboot just hangs, I left it on for 3 hours and it never finished. I tried using the SD IMG method. It goes thru, tells me to reboot. When I do I'm on the same stock recovery...
I have backups of my phone. But they are all done with TWRP and I can't install it. I tried CWM as well, same result, timeout.
I might try running a lower version RUU and see if that fixes all...
It's been a long night and I'm at a complete loss as to what to look for next...
Around 9PM last night, my phone randomly rebooted... it's done this a few times before, and i thought nothing of it. When it finally booted back up, I was at the "choose your language" setup screen. WTF.
I lost literally EVERYTHING.
FYI, this was on stock rom, and I didn't even have the OTA(s) because I was rooted and was content with 4.4.2
Well, since all my data was gone, I figured it was about time to see what I could get with a custom ROM. The phone's been sluggish lately, so I figured a bloat-less upgrade would help.
Long story short, I loaded the 5.1 firmwares for VZW, and the HBOOT as well, and flashed GPE_5.1 on it. It took it like a champ, but refused to boot. I tried changing the kernels during the GPE install, but none of them worked. Some would loop, some would kick me into recovery, and one would just stall and the animation would run forever. No worries, I'm sure I can go to a stock 5.x rom! But that's a big NOPE. I just get "installation aborted" with no reasoning or errors in CWM (I had TWRP at one point as well, and it didn't get me anywhere either) Or I get "symlink: some symlinks failed" ... it depends what rom i'm flashing.
I've tried stock and custom, rooted and not... literally nothing will take.
ALSO, in my attempts to remedy the problem, I tried to reflash the firmware, but fastboot starts that there's not enough space. A quick google search pointed to "not enough ram in the PC" which is BS because it's done it on 2 different systems, both with 16GB ram, one running Win8.1 and the other Win7.
To top it all off, somehow I relocked the phone (but i still have S-OFF) and without being able to boot into the OS, I can't unlock it with SunShine/Firewater.
Hopefully, someone can point me in the right direction...
Welp... It's working now...
Not 100% sure what I ended up doing that worked, but I was able to run the unlocker via creating a new unlock_code.bin from htcdev and ran that with the all in one toolkit.
From there, I was able to use the toolkit to flash a stock ruu rom (I flashed the 5.0.1 RUU, but when it booted, I was still in 4.4.2)
It apparently didn't like somwething in the boot order other than the ROM itself.
I'm now running S-OFF, relocked but rooted 5.0.1 after it took several OTAs. Not sure how many more OTA's are pending, but it just keeps prompting me lol...
At this point, I'm just happy it's booting, stock or not. I don't even know what recovery I'm running at this point...
Did you update your recovery??? To the latest one
Sent from my HTC6525LVW using XDA Premium 4 mobile app