I'm using the R2D2 Droid 2 running 2.2. The first thing I'd like to know is if you have to hard root your phone to get ROM's to work or if using one touch roots will work as well? The main thing I'd like to ask is why I can't boot into recovery mode. I've followed several different guides verbatim. Whenever I go to boot into recover mode, the phone just restarts instead and I get no recovery mode. Ultimately, I'd like to get CM7 working. I've been hearing that the R2D2 phone acts a little strange when trying to use the same method for the normal Droid 2, although I could be completely wrong. Thanks in advance.
Related
hello all, I am having a bit of an issue. So as you know, there is a new 2.2 version of froyo, so i and my noob self wanted to download it, so i searched on Google on how to do it using Odin, and i did, then next thing i knew i was stuck at the recovery menu because there wasn't a "select" key on the vibrant, so my phone was semi-bricked kinda. but i fixed it by going to the download mode and downgrading my firmware back using Odin, but there was a problem, every time i booted my phone, the "Samsung GT-i9000" logo would show up, then 3 seconds later the "Vibrant" logo would show up, so 2 logos at once, that seems weird and i don't want that. but i really want my phone to be normal again! (and also my phone got unrooted for some reason after i "downgraded") and whenever i wanted my phone to go to recovery mode, you would have to use the i9000 method to get that to work, but obviously i cant use that method because i don't have a middle button on my Vibrant, and i don't want that, so my question is:
How do i make my phone normal again? do i have to use Odin to do that and what files do i have to use to bring it "back"?
plz Help!
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
issact said:
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
Click to expand...
Click to collapse
zironia said:
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
Click to expand...
Click to collapse
Hey, it's good to hear I'm not alone in this. lopestom has been friendly enough to correspond with me about it and he suspects it's a new model of the same phone. I sent him a screen cap of the factory settings screen (VOL-/POW)
In the end we might be out of luck until more people get their hands on the new version of the phone.
My phone stopped working after I installed Chain Fire 3D and rebooted. I realized it was boot looping but didn't panic. First I tried the traditional method that always used to work and that is rebooting into recovery mode and wiping everything (ClockWork Recovery). Then I tried repeating it multiple times to no avail. After, I tried loading my latest backup. I then tried wiping everything multiple times and now ClockWork Recovery disappeared (I have no idea why). When all of that failed I tried using RSD Lite, but although my computer recognized my phone RDS Lite wouldn't recognize my phone even after installing the drivers and .sbf files. Now the battery is dead and I can only use the phone when it is plugged into the wall. I can load the boot loader, but no use anymore because the battery is dead. I can still use the system recovery which seems to be my only option of fixing it.
Key things:
•Chain Fire 3D was most definitely the cause
•Only works when plugged into the wall
•Not willing to cough up money for a new battery when fix isnt guaranteed
•I tried multiple different .sbf files and RSD Lite Versions (Which is why my phone's battery is so low)
Thank You for taking the time to read this. After trying everything that I feel should have worked I am open to any and all suggestions that may help.
XDA Visitor said:
My phone stopped working after I installed Chain Fire 3D and rebooted. I realized it was boot looping but didn't panic. First I tried the traditional method that always used to work and that is rebooting into recovery mode and wiping everything (ClockWork Recovery). Then I tried repeating it multiple times to no avail. After, I tried loading my latest backup. I then tried wiping everything multiple times and now ClockWork Recovery disappeared (I have no idea why). When all of that failed I tried using RSD Lite, but although my computer recognized my phone RDS Lite wouldn't recognize my phone even after installing the drivers and .sbf files. Now the battery is dead and I can only use the phone when it is plugged into the wall. I can load the boot loader, but no use anymore because the battery is dead. I can still use the system recovery which seems to be my only option of fixing it.
Key things:
•Chain Fire 3D was most definitely the cause
•Only works when plugged into the wall
•Not willing to cough up money for a new battery when fix isnt guaranteed
•I tried multiple different .sbf files and RSD Lite Versions (Which is why my phone's battery is so low)
Thank You for taking the time to read this. After trying everything that I feel should have worked I am open to any and all suggestions that may help.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Please create an XDA account so you can post within your device's forums found here:
Motorola Droid 2
Your questions will go here:
Droid 2 Global General
Good luck and welcome to XDA!