Ok, so here is the situation:
I rooted my Droid 2, no problem. You guys give very easy to follow directions, so kudos.
Things worked fine once rooted for a week or so, then I installed LCD Density changer. I put in the new density I wanted, it told me to reboot. Fine, I do so. Once I do it, it goes into an endless boot cycle.
My first thought was boot into recovery and do 'restore to factory defaults', so I figured out how to do that, and it 'worked'. But once I restarted, now it reboots with an LCD density of 90 (like I set in LCD Density changer); it takes me to the initial setup screen, works for 10-15 seconds, then reboots. I repeated the 'restore to factory defaults' and same thing.
I'm at a loss as to what to do! I've read about 'flashing' a recovery...can I do that while my phone is in its current state?
Thanks so much for your help, people!
I think you can flash your phone. I don't think you need to have your phone working to flash. Maybe just having it on?
phud1066 said:
Ok, so here is the situation:
I rooted my Droid 2, no problem. You guys give very easy to follow directions, so kudos.
Things worked fine once rooted for a week or so, then I installed LCD Density changer. I put in the new density I wanted, it told me to reboot. Fine, I do so. Once I do it, it goes into an endless boot cycle.
My first thought was boot into recovery and do 'restore to factory defaults', so I figured out how to do that, and it 'worked'. But once I restarted, now it reboots with an LCD density of 90 (like I set in LCD Density changer); it takes me to the initial setup screen, works for 10-15 seconds, then reboots. I repeated the 'restore to factory defaults' and same thing.
I'm at a loss as to what to do! I've read about 'flashing' a recovery...can I do that while my phone is in its current state?
Thanks so much for your help, people!
Click to expand...
Click to collapse
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.
jcsugrue said:
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.
Click to expand...
Click to collapse
You're right! This let me get access to the bootloader, and flash the recovery .sbf I found in another thread. I'm keeping my fingers crossed, but this seems to be working. Thanks for your help!
Update: Fixed!
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!
phud1066 said:
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!
Click to expand...
Click to collapse
No problem. Glad that my tutorial can help!
jcsugrue said:
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.
Click to expand...
Click to collapse
I had given up all hope of restoring my phone until I read this. Thanks you very much
phud1066 said:
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!
Click to expand...
Click to collapse
RSD lite would not work while I was in the bootloader program. It would get to 100% then would go into a second flashing of image file then it would fail. I am pretty sure I have bricked my phone, but still hanging on to it hoping against hope that I can fix it. I have tried almost everything, with the exception of using Linux. I don’t know where to get it or how much it costs.
I wound up having to buy another Droid 2 from the Verizon store here in town. :/
Sent from my DROID2 using XDA App
Terri M said:
I have tried almost everything, with the exception of using Linux. I don’t know where to get it or how much it costs.
Click to expand...
Click to collapse
Linux unlike Mac and Windows is basically free. Ubuntu is free to download. I dual boot windows 7 and Ubuntu 10.04.
Sent from my DROID2 using XDA App
Related
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
Hey guys, after a stupid mistake I screwed myself, and after a lot of research and aggravation I decided to throw in the towel and ask for help. I installed the Fission rom and it worked great till I did a reset after I had uninstalled the stock launcher. When I hold down X and start the phone, it boots into a recovery screen with an exclamation mark and says "E: Cant open /cache/recovery/command." When I "wipe data/factory reset" I can get the phone to load but with no home launcher, but I can receive texts and phone calls. I have tried to reinstall Launcher Pro by sending a link to download by text but when I go to install it says something about a parse error and wont install. Im completely lost at this point and need help please. Im so angry that a stupid mistake cost me so much time and effort. How can I go about fixing this?
In your case, I would SBF that ***** back to stock. You can find a guide to doing so in the development section.
bluek24a4 said:
Hey guys, after a stupid mistake I screwed myself, and after a lot of research and aggravation I decided to throw in the towel and ask for help. I installed the Fission rom and it worked great till I did a reset after I had uninstalled the stock launcher. When I hold down X and start the phone, it boots into a recovery screen with an exclamation mark and says "E: Cant open /cache/recovery/command." When I "wipe data/factory reset" I can get the phone to load but with no home launcher, but I can receive texts and phone calls. I have tried to reinstall Launcher Pro by sending a link to download by text but when I go to install it says something about a parse error and wont install. Im completely lost at this point and need help please. Im so angry that a stupid mistake cost me so much time and effort. How can I go about fixing this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=804088
Thanks guys. I woke up this morning with fresh eyes and figured the whole thing out. It was quite a pain in the ass.
Now that you know how to do it, it shows a) you dont have a brick b) itll be easier next time.
a first time for everything
theecho said:
Now that you know how to do it, it shows a) you dont have a brick b) itll be easier next time.
Click to expand...
Click to collapse
haha yeah, I know brick implies an unfixable phone but I couldnt think of a better word. It is a straight foward process and should be very easy if theres a next time now that ive already done it.
If you could change your thread title to include [SOLVED]. Thanks!
I had the same EXACT problem. Deleted the stock launcher and sat for HOURS on and on trying to figure it out. SBF didnt want to work either...so i called vzw and they ordered me a replacement...the next day at school i tried sbf again with 4.8 instead of 4.7 it worked!
Coderedpl said:
the next day at school i tried sbf again with 4.8 instead of 4.7 it worked!
Click to expand...
Click to collapse
Could have tried the linux method with the Ubuntu Livecd. But glad it's all working again. Nobody likes a nonfunctional $200 Droid 2.
newk8600 said:
If you could change your thread title to include [SOLVED]. Thanks!
Click to expand...
Click to collapse
Yes sir. Taken care of.
Coderedpl said:
I had the same EXACT problem. Deleted the stock launcher and sat for HOURS on and on trying to figure it out. SBF didnt want to work either...so i called vzw and they ordered me a replacement...the next day at school i tried sbf again with 4.8 instead of 4.7 it worked!
Click to expand...
Click to collapse
Yes I believe it was your thread that I had read through when I ran into the problem. I went straight to RSD 4.9 and it worked perfect.
newk8600 said:
Could have tried the linux method with the Ubuntu Livecd. But glad it's all working again. Nobody likes a nonfunctional $200 Droid 2.
Click to expand...
Click to collapse
That would definitely be a shame.
I had an older gingerbread leak, and decided to upgrade to a newer gingerbread leak. Well that is not where the problem came from. I stupidly decided to install the crt animation zip file. Turns out after reading comments it leaves you stuck at the M logo.
Any suggestions on SBFing back to froyo so I can get my gingerbread back on. I have RSDlite, but in the gingerbread bootloader it won't recognize my Droid X.
I was running the .595 Gingerbread leak and I was able to SBF back to Froyo with no issues whatsoever. Are you certain all of the drivers are properly installed on the PC?
Yeah they installed. I have SBF'd using RSDlite before, but what exactly do I need to do to do it from gingerbread. I can get to clockwork, and from there to the gingerbread bootloader, but once there my Droid X is not recognized.
Forget about Clockwork, just turn your phone completely off. Then press the volume down and camera keys while you press the power button. Release all keys after about 2-3 seconds. This should get you right into the bootloader and RSD should see your phone.
wwwilly1986 said:
Forget about Clockwork, just turn your phone completely off. Then press the volume down and camera keys while you press the power button. Release all keys after about 2-3 seconds. This should get you right into the bootloader and RSD should see your phone.
Click to expand...
Click to collapse
Ah yes, its comming back to me now. It has been recognized and is currently SBFing I believe. If I run into any more trouble I'll let you know.
Thanks
aquaurchin99 said:
Ah yes, its comming back to me now. It has been recognized and is currently SBFing I believe. If I run into any more trouble I'll let you know.
Thanks
Click to expand...
Click to collapse
No problem glad I could help
Just finished. Phone simply boots to bootloader screen like I went to to initiate the SBF.
OK if SBF has completely finished pull the battery to power off. Then press "Home" and power until you see the Motorola logo. Release power and continue to hold "Home" until an exclamation appears. Then release "Home" and press "Search" From the recovery menu you will need to clear cache a couple of times and then reboot and all should be well. Anytime you SBF from GBread to Froyo you will need to do this or you will get boot loops. Let me know if this works for you.
Thats odd. The logo is still red. I am now downloading froyo from http://www.mydroidworld.com/forums/...id-x-gingerbread-2-3-3-release-prerooted.html
Thats how I did it when I SBF'd a while back. For some reason I downloaded a different version from another thread. I will SBF that and see what happens.
aquaurchin99 said:
Thats odd. The logo is still red. I am now downloading froyo from http://www.mydroidworld.com/forums/...id-x-gingerbread-2-3-3-release-prerooted.html
Thats how I did it when I SBF'd a while back. For some reason I downloaded a different version from another thread. I will SBF that and see what happens.
Click to expand...
Click to collapse
Yeah try that Official 2.3.340 SBF and then boot into recovery after SBF'ing and clear the cache out. The SBF you previously used may have been corrupt somehow.
Okay it is currently SBFing. Once it finishes I'll boot into recovery wipe data/cached. Then I'll boot up and see how it goes.
I never thought I'd be so happy to see the Froyo "M" xD. Just booted up. Gotta root, then do the gingerbread stuff again. How can I get to .595 again? I do have the TBH app by the way. I just want to make sure I do everything right. Rooting with Z4root right now.
Well its activating right now.
Hmm said it didnt activate. Trying again.
Activated. Now going to root.
aquaurchin99 said:
I never thought I'd be so happy to see the Froyo "M" xD. Just booted up. Gotta root, then do the gingerbread stuff again. How can I get to .595 again? I do have the TBH app by the way. I just want to make sure I do everything right. Rooting with Z4root right now.
Well its activating right now.
Click to expand...
Click to collapse
Ok once it's rooted hop into the Market and grab Droid 2 Bootstrap (Not X)
Then go to http://www.mydroidworld.com/forums/droid-x-discussion/7047-droidx-gingerbread-2-3-3-4-5-588-install-patch-root.html and pick up the 3 files for the .588 leak and flash those in order. Once booted into .588 then go to http://www.droidforums.net/forum/droid-x-roms/136891-official-thread-gingerbread-leak-root-get-now.html and grab the .595 version that you want and flash that through the Droid 2 Bootstrap as well. You cannot flash .595 directly from Froyo or it will fail when flashing.
I thought by enabling USB debugging Droid X bootstrapper would work I believe. If I am not mistaken I used the Droid X bootstrapper to get from froyo to gingerbread in the first place, and from there I went to .595 back previously.
aquaurchin99 said:
I thought by enabling USB debugging Droid X bootstrapper would work I believe. If I am not mistaken I used the Droid X bootstrapper to get from froyo to gingerbread in the first place, and from there I went to .595 back previously.
Click to expand...
Click to collapse
I can't be certain. I haven't tried the Droid X bootstrapper but if it gets you into Clockwork then you should be ok.
I thought I had z4root on my sd card still. Gotta go download it agian.
Stupid computer keeps telling me its a virus and deleting it.
My dad amped up all the security things on here lmao. Just got it downloaded. Root time.
This is taking a while, though I do remember it taking a while when I first did it.
Sweet sounds like you got it.
wwwilly1986 said:
Sweet sounds like you got it.
Click to expand...
Click to collapse
Yup I think so. You've been a wonderful help, especially since its late here. I'm pretty tired, so remembering all these things you told me was not about to happen haha.
You are a life saver.
And to think all of this could have been avoided if I read the stinking comments below the crt animation thing. THis is such a waste of time haha, but then again, I gotta do it. We all make stupid mistakes sometimes.
Wow taking forever to root.
Edit: Rebooting my phone since it was taking too long. I heard that was a problem with z4root anyway. Time to try it agian.
Okay root is working. Time to move on to the next steps.
aquaurchin99 said:
Yup I think so. You've been a wonderful help, especially since its late here. I'm pretty tired, so remembering all these things you told me was not about to happen haha.
You are a life saver.
And to think all of this could have been avoided if I read the stinking comments below the crt animation thing. THis is such a waste of time haha, but then again, I gotta do it. We all make stupid mistakes sometimes.
Wow taking forever to root.
Click to expand...
Click to collapse
I remember having issues with Z4root as well. The first time I think it force closed on me (or stopped responding and gave me the option to force close) and kept doing that until I rebooted and tried it again.
Wow phone reboots soooo fast. I guess this SBF business wasnt so bad. Really cleans things up I guess.
Used ROM Manager and downloaded Leedriod 3.0, ran Terminal Emulator and did everything by the book. Went into ClockWork Recovery mode and everything looked okay. Then went to HTC boot animation screen and that's where it has been ever since. Every five minutes or so I get the delightful sound of HTC and a permanently on HTC, Quietly Brilliant Boot screen. It's been going like that for about 25 minutes now.
Any help would be appreciated.
No its not bricked, its in bootloop.
This is what i do when it happens to me:
Pull out the battery. If the phone is off, turn it back on with volume down + power on button. Wait till you get the bootloader screen. Now select recovery. In ClockWork Recovery you can set your backup back. (if you had made one before).
I hope its helps you. Goodluck.
Or just copy another rom file to the sd card and flash again.
Unfortunately I made the classic error of not backing up first, was trying to do this while in work (not good) so I presume at this point I'm screwed
joooe said:
Or just copy another rom file to the sd card and flash again.
Click to expand...
Click to collapse
Thanks, will try that tonight.
It doesn't hurt to try to flash the rom you already have once again.
Just what joooe said. Use super wipe to clear data. just for sure.
Good luck.
Sent from my Desire HD using XDA Premium App
Just a quick thanks to you guys, did Super Wipe and installed Android Revolution 6.20 last night and all went well. It was worth the screw up to have the small learning curve in the end
I did this one of the first times i flashed roms
i did have abackup first but its a scary experience lol
I found the solution.
Really pisses me off that it was this simple.
Turn on your phone into bootloader
Leave it on bootloader until the battery drains 100%
You can tell it is drained when the phone looks like it is bricked and when you plug it in a red light shows on the notification light
Let it charge for ten minutes
Boot the phone
It should boot. Yeah. Seriously.
It looks like a battery fault of some sort. Welcome
YFBanana said:
So two days ago my Nexus 4 died, and i charged it back up. When I tried to turn it on, it would go to my boot screen, but it would bootloop for 5 minutes, and then restart. This never happened before even the other two times my phone died. I have tried doing a lot of things including switching PA for CM11, and getting stock everything from google. Everything goes succesfully, but again, for every different boot logo, it does the same thing. It really pisses me off beacuse i cant find anyone else with a similar problem, so i dont know what to do.. Also, since the thing cant boot, i cant even turn it back in to tmobile, because it is unlocked and they don't help with anything unlocked... any help would be appreciated Also, if i need to proivide more info on the software i can
Click to expand...
Click to collapse
Did you try to wipe Dalvik Cache & Cache in recovery after flashing back to stock?
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Click to expand...
Click to collapse
+1. And if that doesn't work and you have a hardware issue, boot into fastboot and use
fastboot oem lock
That'll lock the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google
It's the best way.
Click to expand...
Click to collapse
Well yeah, but flashing the stock rom just left me with a bootloop, just with those 4 rings..
boot into recovery, see if your computer detect your phone as android device, try use minimal adb and fastboot, it happen to me once, and success to fix it. if it cant fix it, try use nexus root toolkit, the tools here on xda nexus 4 forum. choose back to stock, and dont forget to choose current status as soft-bricked/bootloop. let me know how it goes.. we'll figure it out
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Update. I somehow managed to get it up and running on factory version 4.3 but I flashed/ used an older radio.img "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48.img" got it from here
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
and by using this method "[URL="http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312]http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312[/URL]
Many thanks to all the good ppl on here
Kdom81 said:
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Click to expand...
Click to collapse
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
YFBanana said:
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
Click to expand...
Click to collapse
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
I fixed it, and had it fixed for maybe 4 months, but now it is back in a bootloop. What i did to fix it the first time beats me, i just randomly flashed 4.4 roms, and it booted once. I used adb sideload for some stuff, but i am gonna keep trying.
Kdom81 said:
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
Click to expand...
Click to collapse
I cant even boot in 4.2.2...
I hate this so much.
Also, i just rebooted my phone and i got this loop again.
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
YFBanana said:
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
Click to expand...
Click to collapse
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
I am gonna try this now, i just hope it doesnt ruin my phone even more lol
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
There is a problem, seems like the lg drivers are not compatible with windows 8.1...
Found a fix, check the forum page