Related
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.
I flashed a Paranoid Android ROM and now the 7 won't boot past the logo. When going to the boot loader I can't select other options and the power will not initiate the 'Start' sequence to continue with boot.
It will, however, respond to the 3-finger salute and shut down. I can then press the power button and start a normal boot (meaning that the button does work).
I will say I probably forgot to wipe or something, but it is an unusual situation that I can't even enter recovery.
I am also having plenty of issues with Win8 and drivers (granted I am still using the Evaluation one), so getting to fastboot for manual intervention is not working right now.
Has anyone encountered a situation where you are in Bootloader and NOT be able to execute fastboot commands?
I had the same problem.
Dawezilla said:
I flashed a Paranoid Android ROM and now the 7 won't boot past the logo. When going to the boot loader I can't select other options and the power will not initiate the 'Start' sequence to continue with boot.
It will, however, respond to the 3-finger salute and shut down. I can then press the power button and start a normal boot (meaning that the button does work).
I will say I probably forgot to wipe or something, but it is an unusual situation that I can't even enter recovery.
I am also having plenty of issues with Win8 and drivers (granted I am still using the Evaluation one), so getting to fastboot for manual intervention is not working right now.
Has anyone encountered a situation where you are in Bootloader and NOT be able to execute fastboot commands?
Click to expand...
Click to collapse
I had the same problem with PA and being unable to execute fastboot commands. An easy fix for me was to use the Nexus root toolkit to boot into temporary CWM. I was able to wipe and re-flash PA and it was fixed. Unfortunately, you said you can't do this because of Windows 8 problems... This actually happened to me a couple times though, and once I was able to get into recovery. Try this. Make sure your 7 is absolutely unplugged from anything, so it can't even be charging. Get to the bootloader with the 3-finger salute and see if you can use the volume buttons to get to recovery. If you can, and it actually take you to recovery, thats great, but most of the time for me it got stuck at the Google screen. So if this doesn't work you may have to figure out whats wrong with Windows 8 first. Hope I could help!
Did you make a back up? Did you Flash clockwork mod or a custom recovery image? If not do what he said.
Sent from my Nexus 7 using xda app-developers app
pbone771 said:
I had the same problem with PA and being unable to execute fastboot commands. An easy fix for me was to use the Nexus root toolkit to boot into temporary CWM. I was able to wipe and re-flash PA and it was fixed. Unfortunately, you said you can't do this because of Windows 8 problems... This actually happened to me a couple times though, and once I was able to get into recovery. Try this. Make sure your 7 is absolutely unplugged from anything, so it can't even be charging. Get to the bootloader with the 3-finger salute and see if you can use the volume buttons to get to recovery. If you can, and it actually take you to recovery, thats great, but most of the time for me it got stuck at the Google screen. So if this doesn't work you may have to figure out whats wrong with Windows 8 first. Hope I could help!
Click to expand...
Click to collapse
UPDATE:
With WUGS Nexus Root Toolkit 154 I was able to do a complete system restore from the boot loader screen. Even though I could not use the three buttons individually to change options OR initiate the displayed option.
I did have to reload Win7 on my machine *just as well I only has the trial one anyway) and the drivers picked up fine. This issue is independent of the Nexus7.
The bottom line is that the Bootloader, even though it seemed frozen, was still accessible via Fastboot commands.
Ryan_Shea said:
Did you make a back up? Did you Flash clockwork mod or a custom recovery image? If not do what he said.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
HAd backup. Was with TWRP. BUT could not get to Recovery mode. All good now though.
With WUGS Nexus Root Toolkit 154 I was able to do a complete system restore from the boot loader screen. Even though I could not use the three buttons individually to change options OR initiate the displayed option.
I did have to reload Win7 on my machine *just as well I only has the trial one anyway) and the drivers picked up fine. This issue is independent of the Nexus7.
The bottom line is that the Bootloader, even though it seemed frozen, was still accessible via Fastboot commands.
Glad to hear it. There is an updated boot loader in the forum somewhere that fixes the "unable to boot in to recovery via fast boot" which can save a lot of hassle if you happen to boot loop again. Makes it a hell of a lot easier to recover. I had the same issue when I first rooted too. Had to just full wipe and recover to stock because I rooted first and then unlocked the boot loader which made the root not stick so when I tried to flash the first ROM got a boot loop and couldn't get to recovery, such a pain in the ass the nexus is.
Sent from my Nexus 7 using xda app-developers app
Hello, friends at XDA!
My dad has a MyTouch 4G Slide. I didn't want to root it because, ironically, I wanted him to have better support and not end up with a bunch of questions from T-Mobile, should he ever need support. I'm now regretting that decision; his future devices will be rooted out of the box...
The phone, in its current state, will get as far as the splash screen. It will sit there for about 20 seconds, and then turn the screen off. After another ten seconds or so, the phone goes back to the splash screen again.
I can get myself into the bootloader, which is still S-ON. That works reliably, but it's still a bit of a dead end. It checks for a baseband update on the phone, and upon not finding an applicable file on the SD card, spits me back into the fastboot menu. Naturally, I went for the recovery environment. I was able to get to it last night, but even that was a bit shallow in that I got to the red triangle screen, but no menu options were presented. Still, I figured that the recovery environment would allow me to run Unrevoked or similar, but when I came home the phone was camping out on the "waiting for device..." screen, to no avail.
My goal was to root in order to install a recovery environment; I know that ClockWorkMod and TWRP both allow for data to be backed up from within the recovery environment. There are call logs and contacts (no, they're not synced with Exchange or Google) that would be greatly appreciated if I could recover before I perform a factory reset as T-Mobile has instructed me to do.
Is there a way I can flash a recovery environment onto this phone using only the access provided by the phone's search for a baseband update from the bootloader?
Thank you for your time and assistance in this matter.
Joey
Unfortunately no, if you can't boot to os and have stock recovery then you have no adb access which means chances of recovering any data is nil
The red triangle is stock recovery, some combo of buttons (like volume up and down) will bring you options but I forget which ones
Hopefully a factory reset will bring your phone a live as you need to get to the os just to unlock your bootloader so you can flash a custom recovery and root the phone
Sent from my Nexus 4 using xda premium
I always root my phone so I'm not sure but,
You can try to start the device by pressing the power and volume - key at the same time.
Then connect to the pc and try the toolkit.
Maybe others can comment if this wil work.
Sent from my HTC One X using xda app-developers app
No Solution
Hey guys,
by some miracle I managed to get the phone working JUST long enough to run a MyBackup Pro task on it; T-Mobile performed a warranty swap on the phone. There was no consistent solution to it though, but thanks for the input everyone.
Joey
Nevermind fixed it. I am a dumbass lol I booted into stock recovery and factory reset, and now I am good to go.
Silicon Knight said:
Nevermind fixed it. I am a dumbass lol I booted into stock recovery and factory reset, and now I am good to go.
Click to expand...
Click to collapse
this happens buddy you just have to boot into recovery and do a factory reset and wipe cache and there will be no problem
HAPPY NEW YEAR
So I had the same issue it sounds like, tried to flash PhilZ recovery over Odin seemed fine I put the PhilZ file and superSU files on the device to continue through and now I am unable to get into recovery mode only download and my tab does not turn off, it sits on the Samsung Galaxy Tab 2 10.1 logo unless I hold the power then it turns off and then right back on again.
Any ideas? I cant seem to find anything
Does your device boot up completely or just sit at the Samsung bootscreen?
swrght13 said:
Does your device boot up completely or just sit at the Samsung bootscreen?
Click to expand...
Click to collapse
Just the boot screen, not even past the first logo
You must have missed a step. Try the process again using this video tutorial: http://www.youtube.com/watch?v=sO3y7JCqfc8
Follow the directions step by step.
This is actually the video I was using, but, I have tried again and I cant get it to boot into PhilZ. I am able to get to download screen so I have tried a different version as well, but after it gets the pass it disconnects to reboot and then never boots or reconnects until I put it into download and reconnect the device.
Weird. This is the way I installed Phil's touch. I had no issue with it. Make sure your usb is disconnected from your device before rebooting. On the p5113, to get into recovery, hold down power + volume-down, when you see first Samsung big-screen, release power button and continue to hold the volume-down button.
Sent from my GT-P5113 using XDA Premium 4 mobile app
That's what I've been doing and it does nothing. Device sits at that Samsung Galaxy Tab 2 10.1 screen. The only way I can turn it off is to plug it into my computer and restart it until the battery symbol comes up and disconnect. That's it.
Not sure what route to take now, but, it still connects to odin and after flashing the PDA to it, it disconnects.
Ok. Tell me. Are you rooted? Can you boot up to your home screen at all? You must be rooted in order to flash a custom recovery.
Sent from my P5113 using XDA Premium 4 app
Rooted, running CM 10.2 [4.3.1]
I didn't even get to that step, I was flashing philz recovery in order to backup before rooting. I was unable to boot anything except the download mode, no recovery mode to factory reset and not able to boot the actual system at all.
I ended up trying CWM and flashing that to the device through Odin and was able to open recovery mode after that and have since flashed Cyanogen to the device and have everything good to go.
I dont know what was wrong with philz, but, I tried multiple downloads of the version we need and none did anything.
Problem is solved, but, there's got to be something wrong with philz recovery for this device or my tablet just doesn't like philz.
Thanks for your suggestions though I appreciate your efforts!
No problem. I'm glad you found a way to fix it!