Related
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.
Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
willjohnson said:
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
Click to expand...
Click to collapse
try here http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html#comment220 scroll down towards the end (idk if you use windows or linux but the linux method of sbf'ing is alot easier ive used both) except in their directions it says an older sbf file just insert the one you have, then go here http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html to download these zip files for kernel updater, 340 system update your baseband and bootloader should already be the correct ones, (i recently bought my X too) then once you finally root your newly sbf'd X and installed droid x bootstrap etc and get into clockwork mod recovery you can flash those 2 zips (recommend flashing only one at a time, reboot, and do the next) and then you should be updated to full .340
gl
http://forum.xda-developers.com/showthread.php?t=869007
heres a thread with discussion about those update zips
Thanks for the quick replies. Gonna try your suggestion tonight or tomorrow. Now i get random lock ups followed by a boot after about five minutes. The only upside right now is that its 4 days old so if i can get some resemblance of factory back on it then i can just exchange it Thanks again will report back with results.
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
willjohnson said:
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
Click to expand...
Click to collapse
correct tho the one i used had was labeled VRZ_MB810_2.3.32_1FF_01.sbf
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Ok, so now i am starting to worry. Tried 3 different .320 full sbf's. All the same result. Failed process close to the begging. Then on the phone it says
Critical Error
FEBE
0047
Please Helppppp. I don't need a really expensive paperweight, all i need to do is get it so that GummyJar doesn't show on boot and i can take it back, its brand new.
Try removing the battery. Then boot into recovery (volume down + power) then do a factory reset/restore.
Sent from my ADR6300 using XDA App
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
willjohnson said:
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
Click to expand...
Click to collapse
ive heard there are several problems with rsd lol thats why ive stuck with my ubuntu/Linux its 10x easier
willjohnson said:
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Click to expand...
Click to collapse
i also believe you DO have to have it all in specific locations but idk i use linux to do it, if you continue to play with the X after u get new one i would read up on how to dual boot ubuntu its a whole lot easier once you find ur way around i have it booting off of a 1TB external hard drive no need to install the correct moto drives etc..just plain easy lol
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
willjohnson said:
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
Click to expand...
Click to collapse
it only takes once correctly doing it to feel comfortable lol also make sure using droid x bootstrap recovery make sure to tap the first choice and let it do its thing, otherwise it will constantly reboot to recovery EVERY time you turn it back on
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
willjohnson said:
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
Click to expand...
Click to collapse
try something blurless like darkslide, which im currently running, no random reboots
Funnyface19 said:
try something blurless like darkslide, which im currently running, no random reboots
Click to expand...
Click to collapse
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
willjohnson said:
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
Click to expand...
Click to collapse
Well I haven't overclocked yet anyway the phone gets hot enuf lol plus coming from an Eris 1k is fast lol
Um yeah it should be wright depends on what the blur clock looks like lol
Sent from my DROIDX using XDA App
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
willjohnson said:
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
Click to expand...
Click to collapse
yeah but the obsidian rom is completely blurless just not everything working
Running DarkSlide4.1 can't tell u last I had a reboot
Sent from my DROIDX using XDA App
My phone isn't working. My DROID 2 is running the stock ROM, and it's not doing anything. I can't get it into recovery, I've tried the PC recovery, it didn't work, because the "Droid 2 2.3.2 SBF.zip" file is corrupted. I boot it up, it goes through the boot animation, but when it boots up, nothing happens. The screen is black. I'm pretty sure everything is running under it, and the haptic feedback from both the lockscreen buttons and and soft buttons work. I'm at wits end, nothing it working at all. Help. Please, help. I use my phone all the time, I just got it 2 weeks ago, however it was a Certified Pre Owned device from Verizon. One little thing, I changed my SD card from the one I had in it before, and it booted up like normal, then after about 20 seconds, it goes to the black screen. I'm about ready to call Verizon and get them to send me a new one.
If it says the zip is corrupted, you might try re downloading the SBF file and trying it over again.
Sent from my DROID2 using XDA App
I tried downloading it several times. None of them worked. I can't open the zip to get the .sbf.
your back light prob died
You probably removed Backup Assistant. Do as the earlier poster said and re download the SBF its a lot easier than trying to get Backup assistant back on your phone.
And to the earlier poster he wouldn't see the phone boot up if the back light was dead.
Where are you downloading the SBF from? Try downloading it form here:
hxxp://bit.ly/dir7fq (replace xx with tt)
what I did was somehow get Clockwork Recovery loaded. I promptly wiped it clean, and requested a new one from Verizon. I got it, and rooted it and such. Now I'm running Fission 2.5.7 with an FM Radio. It's epic!
You must have had a bad sbf file. If i were sending it back i would have used the sbf method rather than having them boot recovery to see clockwork there. Hope they don't bill you for that one...ouch...
Sent from my LogicPD Zoom2 using XDA App
V.A.T.Juice said:
You must have had a bad sbf file. If i were sending it back i would have used the sbf method rather than having them boot recovery to see clockwork there. Hope they don't bill you for that one...ouch...
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Actually, the recovery is the default Android recovery. Clockwork was temporarily put in there, so it's not anymore. The reason I couldn't fix it was because I couldn't boot back into Clockwork. When they look, they'll find nothing
Can you put [SOLVED] in your thread title? Thanks!
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!