Database Users

[Q] Emergency. HELP!

I was adding a new custom ROM to my Droid 2 because I wasn't happy with the Epic ROM so I went with the VZW 2.4.5 Clean ROM, I wanted to add the kangerade blue theme to it but accidently installed the wrong version of it over my ROM and now my phone is in a constant boot loop. sometimes it stays at the droid eye for a while and then load into the lock screen but will go right back into the boot sequence.
When it does boot into the lock screen there is not enough time for me to get into the bootstrapper app to boot into recovery mode.
are there any other ways to get into recovery mode? I've searched high and low on this forum and others as well.
I want my droid back =[

Have you tried to pull the battery and then put it back in. Everytime I do that, I end up at recovery thing.

yup, i've pull the battery many times. i've got it into the android recovery screen but when I to the data/cache format it just brings me to the green android starting screen and goes back into the boot loop, what's weird is that the theme is still applied to the phone

yaooitsbrett said:
yup, i've pull the battery many times. i've got it into the android recovery screen but when I to the data/cache format it just brings me to the green android starting screen and goes back into the boot loop, what's weird is that the theme is still applied to the phone
Click to expand...
Click to collapse
Hmmm. Kind of a roundabout process, but did you make a backup. I'd just restore it to a backup and then go from there.

i can't get into the clockwork recovery, just the stock android recovery. are there any backdoors that i could use with adb?

Try taking the battery out during the boot animation a few times, if that doesn't get you to clockwork recovery you've probably lost your recovery. I've noticed that I sometimes (or always?) Lose clockwork when installing a Rom. If that is the case you may have to sbf unless you can get adb to work from the lockscreen.
Sent from my DROID2 using XDA App

pulptastic said:
Try taking the battery out during the boot animation a few times, if that doesn't get you to clockwork recovery you've probably lost your recovery. I've noticed that I sometimes (or always?) Lose clockwork when installing a Rom. If that is the case you may have to sbf unless you can get adb to work from the lockscreen.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
how would I go about doing an sbf? could you point me in the right direction?

On this forum three posts down is a guide. Follow the guide exactly, except you will have to put your phone in bootloader mode since it will not turn on and stay on. Do do this, hold the up button on the dpad when you turn it on.
It works, i just did it yesterday. First time ive ever had to flash SBF, and i did ALOT of roms and modding on my D1. The bootstrap is nice but not as nice as a full bootloader.
Sent from my DROID2 using XDA App

cool. i think i found the guide. it says backup my sd card to my computer..this doesn't delete everything on the sd card does it?
(not a huge concern since having a working phone is better than losing all my stuff on my memory card)

okay. I tried doing what the tutorial said and I got an error on my bootloader that says
"Critical Error: DEA1"
EDIT:
Well it looks like it was just a simple "I need to update my rsd lite program"
I was using the 4.5 and I read that 4.9 was out so I gave updating RSDLITE a shot and boom, the phone is reflashing as we speak

My sd card is intact... untouched from what I can tell. I had no apps2sd though (with 8 gigs on board why would I?)
Sent from my DROID2 using XDA App

Where is the RSD Lite 4.9? All I come across is 4.7.
Sent from my DROID2 using XDA App

Terri M said:
Where is the RSD Lite 4.9? All I come across is 4.7.
Click to expand...
Click to collapse
Google "RSDLite 4.9" it should be in one of the first results..I found mine in a forum

http://droid2files.com/tools/RSD Lite 4.9.zip
This is RSD Lite 4.9.

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

[Q] Ensuring my Droid 2 is Un-Rooted?

I need to send my D2 back to Verizon for a replacement (Keyboard isn't registering presses, double letters, etc.)
I had rooted my D2 originally.
I have pushed the stock SFB to the Phone (Which did not wipe out my apps/settings?)
I then ran Root Checker which returned False, and indicated the folders + files did not exist.
I then did a System Reset, and went back to square one. I re-activated the phone (Did not add any accounts though).
Is there anything else I should do before sending it back to Verizon?
Thanks!
Edit:
On a similar note, What's the difference between an Oxidized and Deoxidzed SBF? Same with System-Only and Full.
(I pushed the Full SBF to the phone, but I'm curious what the other ones are)

Lord Ned said:
I need to send my D2 back to Verizon for a replacement (Keyboard isn't registering presses, double letters, etc.)
I had rooted my D2 originally.
I have pushed the stock SFB to the Phone (Which did not wipe out my apps/settings?)
I then ran Root Checker which returned False, and indicated the folders + files did not exist.
I then did a System Reset, and went back to square one. I re-activated the phone (Did not add any accounts though).
Is there anything else I should do before sending it back to Verizon?
Thanks!
Edit:
On a similar note, What's the difference between an Oxidized and Deoxidzed SBF? Same with System-Only and Full.
(I pushed the Full SBF to the phone, but I'm curious what the other ones are)
Click to expand...
Click to collapse
It didn't delete your apps or data? Interesting. You should have gone into a bootloop after the SBF, requiring you to go into the stock recovery to format system/cache....
As far as odex and deodex'd. Stock ROM's have odex files for every system app installed on the phone. Supposedly they are supposed to help speed up the startup time of the phone.
Deodex'd is obviously when the odex files have been removed, usually to save room in /system and also to allow themeing.
Full SBF includes EVERYTHING the phone came with (ROM, Kernel, Bootloader, Radio, etc.)
System only SBF is only the operating system. You would use this if your not worried about going back to complete stock, and just need to reload the OS.
Hope this has helped!

That's what I thought @ Still had data.
(Unless this process requires an SD card to work, I don't have one in my phone because it's dead )
I flashed it twice, once with the phone on and connected via RSD Lite 4.8, I just selected the phone there, picked the SBF and hit start... It restarted the phone into some boot-loader like menu, said it was recieved a SW Update, restarted itself and... nothing change.
So then I did it again but started it in the boot-loader like menu to no difference, so I just did a factory reset.
Thanks @ Explanation though!

You should be good. Just make sure your system version is 2.3.20 (I think that's the latest version, haven't had a d2 for a while). Make sure your boot logo and boot animation are stock, and that you don't have superuser install.
Sent from my HTC GingerBolt powered by the lastest Synergy ROM

They are indeed stock.
I took my D2 into the store today to see what they had to say, I have no idea if this is truthful or if the guy was just making it up to sound smart (Never can be sure after listening to other people talk about your own field )
Said that the missed keypresses + double repeats I was getting was from the phone having overheated at some point, and the keyboard is coming away from the keys a bit (The rubber mat is 'bubbled' a bit in some spots) were indicators of overheating too.
No idea if this is true or not, but he said warrenty should cover it and I just have to call into Verizon so I'll do that.

I'd have to say the phone would have had to get pretty damned hot to do that, but who knows. As long as warrenty will cover it its all good.
Sent from my HTC GingerBolt powered by the lastest Synergy ROM

I agree... The previous owner might have left it in the sun or something... Did that with my DS, turned itself off but it was fine in the end.
Gonna call Verizon tomorrow, too late now. Thanks for the help!
I'm still curious as to why the full-sbf didn't factory reset it though.

is Root Checker an app?

The Albatross said:
is Root Checker an app?
Click to expand...
Click to collapse
Yes. It attempts to do something that requires Root to do. If it fails, it tells you. It then checks if the superuser app exists and if the folders for root exist.

I have the same problem with double entries on the physical keyboard. I've had my phone for a year and I'm pretty sure I have never had an overheat (and definitely have never left my phone out in the sun). I attributed this to CM7 nightlies, but now I doubt that.
Anyone else have this problem?
Sent from my DROID2 using XDA Premium App

[Q] Stuck at android logo

Hello. I looked over all the forums and other site's forums. (Android forums, droid x forums etc...) and finally had to post. Sorry for the trouble.
I have a droid x I got 9/2010, one of the first ones out. Recently on a friend's advice i rooted and uninstalled some of the "bloatware". (NFS demo, Blockbuster, etc...). Then I made the mistake of OTA-ing to GB. You guys probably know what happened. So then I decided to factory reset, which just dug the hole deeper. Now I can't get past the "m" logo unless I go into safe mode. I'm thinking about calling VZ as a last resort
I have purchased a full version of clockwork as well as the dx bootstrap, but i understand that without getting into a normal boot I cannot run those programs to try and change the rom/run recovery.
I tried SBF-ing, as well as reinstalling the bloat, both with no luck. Any other ideas?
Thanks a million,
Danny

Did you do a full sbf? If worst comes to worst, and you have insurance, call verizon and tell them you lost it
Sent from my DROID X running MIUI

Yeah, i'm trying the SBF again, using the Linux instructions in the sticky. (My laptop runs Ubuntu) I still can only boot into safe mode. I'm probably gonna leave it in safe mode for now so I can call Verizon. I may not say i've lost it, maybe that it's broken and I don't want to ship a bag of metal parts through the mail/take to store. I figured I was up a creek, but I thought to check. Thanks!

Whenever you SBF and the phone misbehaves, you should do a factory reset. Did you try that?
Edit: Just reread your post and saw you did try that. Try the SBF again followed immediately by factory reset. Also, try the Droid2 bootstrap instead.

Try the bootstrap? If it's a program I need to run then your advice is moot. I can only get into safe mode, which doesn't allow me to run anything. And now my phone displays no icons, just the top status bar. The screen is blank, i can't switch panels and i can't access any menus. I think it's a paperweight.

Can you get to the bootloader screen? If so you can sbf with 1kds linux cd
Sent from my DROIDX using XDA App

I followed a thread explaining how to "sbf" using Ubuntu. (it's a sticky on this forum) I have Ubuntu Linux on my laptop so i did it. It still got stuck at the "m" logo. I "sbf"-ed again with a different sbf file supposed to be Gingerbread. Still stuck at the logo. I understand since my phone will boot it not considered a brick. (I work in the IT field and have dealt with bricked routers,etc...) But the last two sbf's failed.
I'm still open to suggestions. I may go to a VZ store tomorrow afternoon, but until then i'll try anything since it can't get much worse.

I'd try 1kds. One way or another you should be able to get back to froyo and start over. Just to be sure you are using d2 bootstrap?
Sent from my DROIDX using XDA App

I'm under the impression that this "bootstrap" thing is a program you have to run while in the phone's OS. If so i'm out of luck since I can't. My phone won't boot into safe mode anymore. Now it looks like a normal boot, but there's no icons, just a black background and the upper status bar. (signal, clock etc). i can't get any menus except the sliding unlock screen. The buttons on the bottom do nothing. (Holding HOME displays a screen saying I have no recent programs, ironic since I can't run anything/go anywhere)
So if Bootstrap is something I can load/run without being in the OS, i'm good. But everything I read says otherwise. Thanks either way.

D2 bootstrap is an app. You could run your phone forever without it. It's primary function is allow you to get into cwm to flash things or make a nandroid backup.
Sent from my DROIDX using XDA App

I just discovered that. So it's something I could have installed before it all went south. I'm trying this 1kds sbf thing, but i think it's gonna fail like the last time. I'll post the results later.

Well it lets me into the OS, and it's not safe mode, but I can't really do anything. The screens are still empty. I can get to the apps menu, but touching any of the icons does nothing. If it did i'd just run the z4root and then bootstrap from my SD card. But the icons won't do anything. I'll keep trying things until I can run stuff from my card. I'm determined to get this to work.

You successfully burned the 1kds discount, got your phone into bootloader mode, and ran the disc? What did your pc screen say the moment you ran the sbf?
Sent from my DROIDX using XDA App

You should be able to SBF your phone and then immediately boot it into the recovery menu (hold the Home key while turning on the phone, then press the Search key to get the recovery menu). From there, do a reset, wipe, or whatever it's called. That should get rid of whatever remaining software turds is causing your phone problems. If that still doesn't work, then I'd chalk it up to a hardware problem.

I did burn and run the CD. It didn't say anything special after it ran but i wasn't looking for something special. Now I can't get to the recovery menu. It's still frozen at the logo. I can get into safe mode, sometimes. I'm gonna take it into VZ tonight just to see. But I recently found out I haven't been paying for insurance this whole 11 months i've had it. So my idea of a replacement got more expensive.

Was trying to find out if you got to the "boot baby boot" screen before it did it's thing. Bummer it didn't work.
Sent from my DROIDX using XDA App

Yeah, i think it's a hardware issue so i'll see what Verizon says. Regardless thank you all for helping. I'll give you "thanks" after work today. Rock on!

Stuck at Android welcome screen

My nook was rooted then problems started like the markets not searching. It used to work. So I decided to reroot my nook.
I used minimal touch the first time. So I used cwr and did a factory reset. This is when the welcome screen of death appeared. It tells me to click the Android to begin but nothing happens.
So I just loaded my sd card with cwr again and loaded the minimal touch beta 5 and attempted to install the first step again then restarted. I am met with the welcome screen of death again and it doesn't do anything else. Except now I have my savior buttons but they still don't do anything.
What do I need to do?
Sent from my Samsung Precedent using XDA.

Ok, I did some searching & there is not a whole lot of information about this issue. The problem started after I did a factory reset w/ clockworkmod recovery & I confirmed that I was using the latest version.
Anyways since there aren't a lot of people jumping to answer this question I might as well share what I found thus far.
Tap in the four corners of the Android welcome screen from top left clockwise ending at bottom left to bypass this screen.
I'm going to reroot using this bypass & see if I get anywhere..

SeeingBlue said:
Ok, I did some searching & there is not a whole lot of information about this issue. The problem started after I did a factory reset w/ clockworkmod recovery & I confirmed that I was using the latest version.
Anyways since there aren't a lot of people jumping to answer this question I might as well share what I found thus far.
Tap in the four corners of the Android welcome screen from top left clockwise ending at bottom left to bypass this screen.
I'm going to reroot using this bypass & see if I get anywhere..
Click to expand...
Click to collapse
I have the same predicament. the touch four corners method hasnt worked for me at all. Going to try and restore it or something similiar, and try again.
Have you made any progress?

Restore method works for me .
http://forum.xda-developers.com/showthread.php?t=1475613
jje