Database Users

[Q] Stubborn Droid 2

To preface, I've been off the phone hacking/ROM flashing scene for a couple years now; previously working with Windows Mobile, so I know a lot has changed but I'm not largely unfamiliar with the general process of what we are doing here.
Droid 2 In Question:
System Version - Version.2.3.20.A955.Verizon.en.US (After OTA Update 03 NOV 10)
Baseband - BP_C_01.09.07P
I've got a stubborn Droid 2 that just WON'T boot to recovery. I bought a fresh Droid 2 last week, rooted via the 1-2-3 'One-Click' successfully. Then I attempted to follow AngDroid's Fission install step by step for my first ROM flash. http://forum.xda-developers.com/showthread.php?t=823473
Issues:
ROM Manager wouldn't do ANYTHING when I would select 'Reboot into Recovery' or attempting to select ROM using 'Install ROM from SD Card'.
Found and installed Koush's Bootstrapper, got 'SUCCESS!' pop-up when selected 'Bootstrap Recovery' yet when I tapped 'Reboot Recovery' nothing happened.
I then attempted to re-install the SBF (which I'm still not 100% clear on what the role of the SBF is, perhaps just the Baseband?) using both AngDroid's instructions in his Fission thread as well as using RSD Lite 4.7+patch AND 4.8 AND 4.9 instructions from this thread. http://forum.xda-developers.com/showthread.php?t=827624 All those attempts where unsuccessful. RSD wouldn't allow me to 'Start' the SBF flash which I can only assume is because I had the latest version on my Droid 2.
I then decided to restore my phone to factory and start over, so I booted the device pressing x, then search and selecting wipe data/factory reset. Once done, it rebooted and to my surprise it still had the Superuser Permissions app that was installed during the 1-2-3 One-Click process.
I went as far as to install the full Android SDK/Eclipse setup for ADB use and continued to run into 'operation not authorized', 'root not allowed on production ROMs' and 'failure' with any command attempting to remove SU Permissions app and install a diff. SU app/reboot into recovery.
I checked to see if I still, in fact, had SU permissions by re-installing Barnacle, it stated that it needed su but the Superuser Permissions app never prompt me to authorize su. There is also no way (that I see) to manually authorize su for barnacle, or any app, in the SU Permissions app.
Way Forward?
I believe that I either need to re-root and try to reboot to recovery again but I am not confident that will work.
I am starting to think that ROM Manager and Droid 2 Bootstrapper apps didn't have SU and might be why they didn't respond when I selected 'Reboot Recovery' options? As I stated I do not know how to manually authorize.
With this information, what am I to do from here?

That's strange. After root, you should be able to install SU from the market if the one click root doesn't already do it for you. When you run Koush's bootstrapper, the first time you should get a pop up from the SU program asking you if you want to allow or deny the bootstrapper. After that, everytime you load up the bootstrapper you should see a little pop up stating that it has been granted superuser privileges.
Try rooting again, this time use the 1 click root for 2.3.20 found here http://www.mydroidworld.com/forums/droid-2-discussion/5321-2-3-20-1-click-root.html, and then go through the steps again and report back

Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?

wjones said:
Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?
Click to expand...
Click to collapse
Id wipe cache and wipe data/factory reset and start fresh. I've never had any of your problems and I think they can be fixxed with a factory reset.

Sounds like you didn't get rooted properly.
If it were me, I'd sbf and start over.
- Charge battery fully
- Get drivers from Motorola and install them (wait for it to finish)
- Get RSD 4.8+, and 2.3.20 sbf (make sure you get the full file)
- Wipe data and cache in stock recovery (access by power + X key, then search key)
- Boot into bootloader (power + Up key)
- Load RSD and make sure your device shows
- Choose the sbf and click Start
If you follow those steps exactly and sbf doesn't work, then you probably have a hardware problem either on your phone, your PC, or the USB cable.

karnovaran said:
Sounds like you didn't get rooted properly.
- Boot into bootloader (power + Up key)
Click to expand...
Click to collapse
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!

wjones said:
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!
Click to expand...
Click to collapse
Yeah I don't know why some methods recommend PC Mode. Sbfs are meant to be flashed in bootloader.

Honestly, it sounds like everything is working like it should be, it's just some steps are being skipped or overlooked. Like the SBF in bootloader, and the sbf doesn't erase your data, you need to do a factory reset after sbfing so thats why your superuser app was still there.
There really is no such thing as a phone being stubborn, and majority of errors like that are from the user. Not to be insulting but thats just the case. The only time I have ever seen a stubborn piece of hardware is from overclocking, where some can go higher than others due to having a better piece of wafer. But if you rooted correctly, bootstrapped, etc, there is no reason that you wouldn't be able to install a ROM.

Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App

wjones said:
Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Is this solved now? May I close it?

Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App

wjones said:
Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
No problem! I'm in no rush to close it, was just curious Hope it all goes well

DONE!
It worked like a charm! Thanks for all the support!

wjones said:
It worked like a charm! Thanks for all the support!
Click to expand...
Click to collapse
Awesome. Could you add [SOLVED] to your thread title before the mods close it?

Stuck in bootloader after 3.40

Used Boot Straper from Market flashed .320 from .315 everything went correctly verified update in settings. Booted with bootstraper again cleared all the partitions like cache installed
2.3.340 Kernel Updater (2.6.32.9-g55626e1) .zip
BP_C_1.09.07P Baseband Updater .zip
2.3.340 System Updater .zip
ApeX 1.3.1 .zip
note none where sbf files rebooted the system and im stuck in bootleader and reads
Bootloader
30.04
err:A5,69,35,00,27
Battery OK
OK to Program
USB connected
Data Cable
Nothing I do can avoid botloader. After Finaly getting RSD Loader 4.9 to reconize my device I tried to cure it by flashing Droid Life 2.3.340 .sbf file and RSD give err 0x700

Try the .320 SBF, then .340 SBF. If that fails you will have to wait until you can get a hold of the next full SBF.

I went to a new computer and I flashed .15 SBF I belive full bc it was like 400mb with success on flash but my cute little android man pissing on craple is gone and boots immedieately into BL saying no system. So Now flashing .340 SBF and see what happens. If this don't work I am fresh out of ideas

That won't work. Flash the full .320 SBF then the system only .340 SBF and you'll be fine.

mlclm said:
That won't work. Flash the full .320 SBF then the system only .340 SBF and you'll be fine.
Click to expand...
Click to collapse
This worked for me. You should do it this way.
Sent from my DROIDX using XDA App

iceblue11 said:
I went to a new computer and I flashed .15 SBF I belive full bc it was like 400mb with success on flash but my cute little android man pissing on craple is gone and boots immedieately into BL saying no system. So Now flashing .340 SBF and see what happens. If this don't work I am fresh out of ideas
Click to expand...
Click to collapse
If you are on stock 2.3.15 now, then just go to Settings>About Phone>System Updates. This should do the OTA update and bring you to 2.3.340. No Need to flash the 2.3.320 full sbf and then the 2.3.340 sbf.

Your right that won't work. Its stuck in loader so no system will boot. So I need to go find the 320 sbf in order to get out of this. I'm asuming its the 30.04 bootloader preventing the 315 sbf from bringing me out and why the 340 system sbf won't rescue me. Ok ill try it thanks

iceblue11 said:
Your right that won't work. Its stuck in loader so no system will boot. So I need to go find the 320 sbf in order to get out of this. I'm asuming its the 3040 bootloader preventing the 315 sbf from bringing me out and why the 340 system sbf won't rescue me. Ok ill try it thanks
Click to expand...
Click to collapse
Yeah, I think I remember reading if you have 30.04 bootloader, the 2.3.15 sbf will not work, but I can't remember for sure.
To check what bootloader you have, power off your phone. Now press and hold both volume keys; keep pressing the volume keys as you power the phone back up. The phone will proceed to enter bootloader mode and show you what bootloader you have.

Sorry for the pore responses and spelling. I was sneaking posts at the Verizon store while fighting with the manager to please charge my battery so I could flash my phone. Battery died on me apparently it will not accept any type of charge from the phone when stuck in boot loader.
bouchigo - Thanks you been a big help bud, Finally! Someone says how to put the X into that bootloader I couldn't figure it out so went with the clockworks .zip 340 system flash instead of the sbf. Had to google for the 320.sbf couldn't find much on here for this so it is downloading now and see what happens after that. I did find during my search that if the bootload was 30.04 the phone would not accept a 315 system so that is indeed accurate.
mlclm - Thank you

w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon, coincidence of bad timing was an outage in service on my area life is peachy now

iceblue11 said:
w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon
Click to expand...
Click to collapse
Strange. I have had the ota programming fail and I had the option to skip. Then open dialer and do *22899 to program.
Sent from my DROIDX using XDA App

iceblue11 said:
w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon
Click to expand...
Click to collapse
Try doing a "data/factory reset" and "wipe cache", after that reboot and see if fixes your problem.
1. Power off your phone
2. Press and hold the home key (the button with the little house on it).
3. While holding the home button down, power up the phone. Once phone starts to power up, you can let go of the power button, but keep holding the home button until you see a triangle with an exclamation mark in the middle with a little android underneath the triangle.
4. Now, press the search button (the magnifying glass button).
5. Scroll to "wipe data/factory reset" (with the volume up and down buttons) and select it with the camera button.
6. Now scroll to "wipe cache partition" and do the same as you did previously.
7. Reboot and hope it solved your problem.

Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far

iceblue11 said:
Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far
Click to expand...
Click to collapse
I had that service problem too when I SBF'd. When I was on .15 I tried to use the
system updater on droid world (stupidly) to .340 and the patches. So after I got
stuck on the bootloader like you did, I just SBF'd to .320 and then went back
to droid world and then installed the system updater (.340) with bootstrap and
then the following patches. I had to go outside to get at least one bar of service
in order to activate the phone. After about 20 minutes or so I started getting
signal back the way it was before. I *228 again a few times to get rid of the
roaming icon. Sometimes it takes a few programs to get you to the correct towers.
Here's the droid world thread.
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
Note: I of course activated the phone before using the system updater and patches.
Gain your signal back first before you get onto .340

iceblue11 said:
Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far
Click to expand...
Click to collapse
Open droid x bootstrapper and hit the bootstrap recovery button. This should stop you booting to ce everytime you restart.
Sent from my DROIDX using XDA App

Dont wanna brick my atrix

Im sure all the info is here already but im pretty nervous about bricking my phone. I'm on 1.2.6 but it kept asking me to update over and over and i would hit no but it popped up at the wrong time and i hit yes and it rebooted the phone and tried to do it. I pulled the battery out to stop it and booted it back up but now in my notifications it says next time i connect to wifi it will install 4.1.57. So my question is do i have to flash back to a stock rom (im on the gingurblur rom) before i can run the update. Also i used aroot to root the phone so since i already rooted if i flash back to stock rom and update to 4.1.57 ill retain root?

fallchild said:
Im sure all the info is here already but im pretty nervous about bricking my phone. I'm on 1.2.6 but it kept asking me to update over and over and i would hit no but it popped up at the wrong time and i hit yes and it rebooted the phone and tried to do it. I pulled the battery out to stop it and booted it back up but now in my notifications it says next time i connect to wifi it will install 4.1.57. So my question is do i have to flash back to a stock rom (im on the gingurblur rom) before i can run the update. Also i used aroot to root the phone so since i already rooted if i flash back to stock rom and update to 4.1.57 ill retain root?
Click to expand...
Click to collapse
In order to update you will need to flash 4.1.26 if you don't then while trying to install the update it will fail. Once you update you will lose root and you will lose gingerblur as there isn't one for 1.57 right not. But you can keep root if you follow these instructions. Hope this helps.
http://forum.xda-developers.com/showthread.php?t=1016060
PS. None of this will brick your phone just read all instructions and you'll be alright.
Sent from my MB860 using XDA Premium App

[Q] 1.8.3 update, now 'failed to boot 2' help!

ok can't get this to work. first i was on 1.5.7 with gingerblur, tried updating to the latest through rsd lite and after it finished my phone shows
Failed to boot 2
Starting RSD mode
i've tried everything and always end up with this outcome. whats going on?

CustomA313 said:
ok can't get this to work. first i was on 1.5.7 with gingerblur, tried updating to the latest through rsd lite and after it finished my phone shows
Failed to boot 2
Starting RSD mode
i've tried everything and always end up with this outcome. whats going on?
Click to expand...
Click to collapse
If rsd mode is working then try and go back to 1.26. At least I would try that to get a fresh start and then reupdate and root and everything again.

Gutterball said:
If rsd mode is working then try and go back to 1.26. At least I would try that to get a fresh start and then reupdate and root and everything again.
Click to expand...
Click to collapse
i also did that. i went back to 1.26, updated OTA to 1.57 and tried again to get to 1.83 but same thing happenedd

Where are you getting 4.1.83 from?

a post from the development forums

I had the same problem, it failed as it went to update the radio as I had already done the hsupa update.
The found I could not restore any sbf over the top. Update your Rsd to a version 5 or higher and then apply either 1.2.6 or 1.5.7 sbf and all is well.
Sent from my MB860 using XDA App

jysue said:
I had the same problem, it failed as it went to update the radio as I had already done the hsupa update.
The found I could not restore any sbf over the top. Update your Rsd to a version 5 or higher and then apply either 1.2.6 or 1.5.7 sbf and all is well.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
i'm using version 5.0 and did a full restore back to 1.2.6, then updated to 1.5.7 so shouldn't that fix any radio issues that your talking about? everytime i try i get the same 'failed to boot 2' error

CustomA313 said:
i'm using version 5.0 and did a full restore back to 1.2.6, then updated to 1.5.7 so shouldn't that fix any radio issues that your talking about? everytime i try i get the same 'failed to boot 2' error
Click to expand...
Click to collapse
everytime you update 1.8.3 after restoring all the way back to the start and upgrading?
I was using Tenfars to apply the Zip file update and noticed it failed to apply the radio everytime, I ended up applying it 10 times in a row (at wits end) and when I rebooted everything worked but I had the old radio. Then I applied the HSUPA updated radio (again).
Previously everytime I applied it would fail and then reboot would show failed to boot 2.
My RSD Lite version is 5.3.1, before when I could not apply 1.2.6 or 1.5.7 it was version 4.9

jysue said:
everytime you update 1.8.3 after restoring all the way back to the start and upgrading?
I was using Tenfars to apply the Zip file update and noticed it failed to apply the radio everytime, I ended up applying it 10 times in a row (at wits end) and when I rebooted everything worked but I had the old radio. Then I applied the HSUPA updated radio (again).
Previously everytime I applied it would fail and then reboot would show failed to boot 2.
My RSD Lite version is 5.3.1, before when I could not apply 1.2.6 or 1.5.7 it was version 4.9
Click to expand...
Click to collapse
yea pretty much and now i think my phone is toast. it's dead and so it's not recognized when i plug it in my computer and when i plug it in the wall it just goes to the error screen with the moto logo on it and just gets really hot -_-

CustomA313 said:
yea pretty much and now i think my phone is toast. it's dead and so it's not recognized when i plug it in my computer and when i plug it in the wall it just goes to the error screen with the moto logo on it and just gets really hot -_-
Click to expand...
Click to collapse
pull the battery and let it sit a while, have a go in a few minutes. if it's not booting straight to fail 2 then try forcing RSD mode with vol up and see how you go getting it back to flashable mode.
I thought I was toast a dozen times when mine went off the rails...not quite sure still how having the HSUPA update on rooted 1.5.7 made me incompatible with 1.8.3 update since it contains a new radio image not a patch - maybe someone smarter can figure it out!

[Q] How To Needed - update from 2.2.1

I've been running Liberty on my Droid X for some time now and love it compared to the stock Blur interface. But it's gotten to the point where I'd like to update from Froyo to one of the more modern versions and see if that can liven up the phone again. So my question is this - from what I've read before I can update Liberty (or any other ROM for that matter) from a Froyo based version I need to restore the phone to a semi-stock state, update via an official OTA release, re-root and go from there. Is that true? If so, any convenient guide on how to do so? I did a bit of searching and couldn't find much and while I'm pretty technically inclined my skills do not extend into the phone region and back when I originally modified the phone there were many handy guides and videos to walk me through it.
Any help would be greatly appreciated.
Nate

If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk

Let the stupid questions begin...
Ok, I confirmed that I'm running 30.04 and I found a site that maintains the correct 4.5.602 file so I downloaded that. Is there anything that I need to back up before installing? Also, I read that a special program is required to install the SBF files so any assistance there would be appreciated as well.
Thanks!

Ok, so I managed to track down RSD-Lite and got it to recognize the device and start loading the sbf file however the phone couldn't get past the "manually power up the phone" phase (or something like that). It just kept showing the boot animation over and over again regardless of what I did - it would cycle between the red eye and the DROID text. I tried pushing and holding the power button, no good and none of the other buttons did anything either. Nothing worked. So I'm rerunning it again and we'll see if the second time is a charm...

Well crap, I got through the SBF install process and got the pass message from RSD but now my phone is stuck at the animation and won't go any further. I've left it running for the better part of 10 minutes and it just hangs. I'm now performing a manual factory data wipe to see if that will help.
EDIT: It appears that the factory data wipe got me through the locked animation. Still having minor issues getting through the programing and setup phase but I think it'll work eventually.
Thanks again for the help.

infazzdar said:
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.

Well, it's sort of worked out.
Everything is up and running but ROM Toolbox isn't able to load any ROMs. It gets granted Superuser permission so I'm pretty sure that I've got the X rooted correctly but when it tries to boot into Clockwork it appears to get an error (icon with an exclamation point) and reboots into the regular Blur interface. I'm going to have a go at loading something like Liberty Gingerbread or 3.0 via zip file but it makes me nervous that the Toolbox Pro App can't get this done.

After determining that the Toolbox App was not booting into Clockwork I downloaded and installed the Droid X Bootstrapper App and got that running. It was able to correctly boot into recovery from which allowed me to install the Liberty 3 ROM. I'm now going back through the process of setting the phone up with the new ROM so we'll see how that goes. It appears to be working, but only time will tell if it's stable. One thing is for sure, a few hours on Blur'd Gingerbread and I was ready for something else again.

Jubakuba said:
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Click to expand...
Click to collapse
I was actually wondering whether it would or not, but I can't think of another way to update the bootloader.
Sent from my DROIDX using Tapatalk

Ok, so here's an issue that I'd appreciate some guidance on. After installing Liberty 3.0 it appears as if the phone can't fully charge. It was plugged in for 10hrs last night and yet this morning the battery only reads 61%. I don't know if it would be best to boot into recovery and wipe the battery stats not knowing if it's fully charged or not.
Thoughts?