m1kew1lson
Lurker
after doing a upgrade like this and wiping data do you need to run an activation for the handset again?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yes. But all that entails is dialing *22899 and waiting 15 seconds.after doing a upgrade like this and wiping data do you need to run an activation for the handset again?
Possibly. But if you're sbfing back to stock anyway, just install .588 and then .595 right over the clean setup. Its the easiest way to make sure nothing goes wrong.
If you're on stock .340, with no bloatware deleted, no deodexing, no themes or ROM's, you don't need to do an SBF.
Most of us did customize .340, so we had to SBF.
Sorry to hijack the thread but I have a question. If I am on stock .340 do I just install the zips for .588 then to .595 without rooting or anything else?
Step by step if you want to get to the newest Gingerbread:
Note: If you are already on stock .340 and you have not deleted any bloatware, not themed, not deodexed, not installed a ROM, and have unfrozen anything you might have frozen before, you can skip step 3. If you've rooted and done anything you think might not be close to stock, I'd SBF just to be safe. Its good to know how to do it anyway.
1. Download z4root (here), Droid 2 Bootstrap (here), the 3 parts of the .588 install (here), and .595 deodexed (here) and put them all onto your SD card (.588 files and .595 should be in a folder, not the root of your SD card)
2. Backup your files and whatnot from your current build however you usually do. I did a TiBU of all of my user apps+data as well as my user dictionary. Also did a backup of my call log using "call log backup and restore"
3. Get to .340 stock via SBF (instructions here) Make sure it is the .340 full SBF. NOT system only. If you get into a bootloop after SBFing, 100% of the time it can be fixed by getting into stock recovery (hold home and power) and doing a factory reset/data wipe.
(3.5) Once you get to stock and boot for the first time, you can skip reauthenticating your phone by just touching all four corners of the screen with the android on it when you boot up in clockwise order, starting with the upper left. This is optional, just saves a few minutes fiddling with settings.
4. Install z4root and root with it. If it doesn't work, reboot your phone and try again.
5. install droid 2 bootstrap. Bootstrap recovery, reboot into recovery, wipe data/cache, and install all 3 parts of .588, sequentially. To install them, you will go through "install zip from sd card" and "choose zip from SD card." You must install all 3 parts before you leave recovery. Wipe data/cache again here. (Yes, you're wiping it a lot when there shouldn't be anything on there, but its the easiest way to avoid bootloops)
6. Install .595 same as you did .588. You don't even need to leave recovery from the previous step.
7. At this point I'd reboot (first boot may take up to 10 minutes), reinstall droid 2 bootstrap, and do a quick backup of the clean GB install. Then I'd start restoring everything I backed up during step 2. (Note: The first time you open Ti backup after installing .595, hit the "problems?" button and reinstall busybox. Otherwise TiBU will not function)
Finally, if you are getting the blue triangle icon and are no longer connected to Verizon, simply open your dialer and dial *22899 to reauthenticate.
Note: You will need to SBF back to .340 before you can take the OTA. OTA won't be rootable for a while though, so I'd stick with .595 for now.
PS. if you follow these instructions, you can't really screw it up. Even if you somehow flash files in the wrong order or something, you will only be an SBF away from fixing it. (Make sure it is the .340 full SBF. If your file says "system only" it is the wrong one and will not work) The only circumstances in which you could break your phone is if your battery dies mid-flash. So have a full (or almost full) battery before you start.
I hope I didn't sound ungrateful earlier. It is my fault I didn't think to thaw the bloatware, nobody else's. It is unpleasant to be on the road all week with no phone.
Since I can get into the boodloader, can I do the procedure outlined at the page linked below to restore my phone instead of an sbf?
maderstcok - OTA 2.3.340 update.zip - Droid Forum - Verizon Droid & the Motorola Droid Forum
It seems like a simpler procedure, and the file seems to be in a place I can download it. What's the worst that can happen if it doesn't work and I follow all the instructions? I'll have to then sbf, right? Seems like a minor risk, considering how impossible it has been for me to get the sbf file.
Thank you 1x10E90
Matt
did anybody go to gingerbread and now regret it? or have gone back already?
did anybody go to gingerbread and now regret it? or have gone back already?