Related
I have no idea how this happened, but basically my XOOM has spontaneously broken itself. I was using it like normal, just watching some videos over TVersity and I noticed it started running a little slow. So I restarted it and it never got past the boot animation and hasn't since.
I figured I would try a factory reset under Recovery, but it won't work because it can't even find the internal sdcard. I can't mount the sdcard, I can't wipe it, I can't do anything with it.
I'm hoping someone here might know what to do? Or if not, how can I remove all traces of ClockworkMod Recovery so I can exchange it without them claiming I somehow broke it?
Could reflashing the boot and recovery with the stock images possibly fix this problem, or are they also kept on the internal sdcard and therefore untouchable while the XOOM is in this state?
If your pc can recognise your xoom and connect, you can flash the official images from Moto and recover your xoom with adb, unlike me.
http://forum.xda-developers.com/showthread.php?t=1108505
This thread has all the info you need to reflash to your stock Xoom.
But then again, you may not need to go this far. Perhaps just hang around until someone with much more knowledge can help you.
flombs said:
If your pc can recognise your xoom and connect, you can flash the official images from Moto and recover your xoom with adb, unlike me.
http://forum.xda-developers.com/showthread.php?t=1108505
This thread has all the info you need to reflash to your stock Xoom.
But then again, you may not need to go this far. Perhaps just hang around until someone with much more knowledge can help you.
Click to expand...
Click to collapse
Thanks for that, I'll hold out for an easier solution but I appreciate your advice as a fall-back plan
I wish I could have that as a fallback plan. Can't even connect my Xoom to my PC. oh...wait...
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.
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
I'm throwing in the towel and posting after looking for help on the threads, IRC, etc.
How can I reset my phone to stock? I no longer want root access, I just want a phone that works.
I have an AT&T HTC One X+ that I was trying to root using Hasson2000's all-in-one for the X+. If I don't push anything, it stays on the HTC simply brilliant screen. I can get to the white boot loader screen, fastboot, etc. Recover does nothing besides reboot, show the HTC screen, then go to a black screen. Factory Reset used to go to a black screen with a green arrow logo, but that doesn't happen any more. I used to be able to get to TWRP but it doesn't seem to like me any more. I've read threads about how you can use ADB PUSH to put a boot file on your phone, but I can't seem to find out where to put it. I got a stock ROM from Scott's ROMs, but I am unable to get my phone to be recognized by windows. Windows thinks it's an empty removable drive that asks me to put a disk in when I click it. I can get SOME adb commands to work, like adb reboot, but if I try to do anything else, it says it can't find the device.
Yes, I'm a noob, yes I screwed things up, but this is my only phone and it's a work phone and it might cost me my job. Lesson learned. I just need to get my phone back to working order. Please, please help.
Alternatively, it does have insurance, so I could let one my kids drop it into the toilet.
I know I'm not giving you much help, but you may want to find the correct forum for the phone you need help with.
It's surprising how the people that can't find the right forum for the phone they tinker with have so many problems!
It's never too early to get your kids involved in fraud because you can't do things right.
Sent from my HTC One XL
I appreciate the suggestion. However, I did not see one specifically for the AT&T HTC One X+. Since this was for the AT&T HOX, I figured this would be the best bet.
edit: Sorry I'm a dumbass. I found the forum for the One X+. Thanks again.
Plaguen0g said:
I'm throwing in the towel and posting after looking for help on the threads, IRC, etc.
How can I reset my phone to stock? I no longer want root access, I just want a phone that works.
I have an AT&T HTC One X+ that I was trying to root using Hasson2000's all-in-one for the X+. If I don't push anything, it stays on the HTC simply brilliant screen. I can get to the white boot loader screen, fastboot, etc. Recover does nothing besides reboot, show the HTC screen, then go to a black screen. Factory Reset used to go to a black screen with a green arrow logo, but that doesn't happen any more. I used to be able to get to TWRP but it doesn't seem to like me any more. I've read threads about how you can use ADB PUSH to put a boot file on your phone, but I can't seem to find out where to put it. I got a stock ROM from Scott's ROMs, but I am unable to get my phone to be recognized by windows. Windows thinks it's an empty removable drive that asks me to put a disk in when I click it. I can get SOME adb commands to work, like adb reboot, but if I try to do anything else, it says it can't find the device.
Yes, I'm a noob, yes I screwed things up, but this is my only phone and it's a work phone and it might cost me my job. Lesson learned. I just need to get my phone back to working order. Please, please help.
Alternatively, it does have insurance, so I could let one my kids drop it into the toilet.
Click to expand...
Click to collapse
i cant help you much .. but .. i can tell you one thing.. if u seeing htc brilliant screen... your phones safe... so just go to right forum and ask the right questions .. and get things right
maybe this is your forum : http://forum.xda-developers.com/forumdisplay.php?f=1814
but make it sure yourself
I know it's close that's the problem with things that are similar but different, sometimes they can get you in big trouble if you aren't careful.
Sent from my HTC One XL
Plaguen0g said:
I'm throwing in the towel and posting after looking for help on the threads, IRC, etc.
How can I reset my phone to stock? I no longer want root access, I just want a phone that works.
I have an AT&T HTC One X+ that I was trying to root using Hasson2000's all-in-one for the X+. If I don't push anything, it stays on the HTC simply brilliant screen. I can get to the white boot loader screen, fastboot, etc. Recover does nothing besides reboot, show the HTC screen, then go to a black screen. Factory Reset used to go to a black screen with a green arrow logo, but that doesn't happen any more. I used to be able to get to TWRP but it doesn't seem to like me any more. I've read threads about how you can use ADB PUSH to put a boot file on your phone, but I can't seem to find out where to put it. I got a stock ROM from Scott's ROMs, but I am unable to get my phone to be recognized by windows. Windows thinks it's an empty removable drive that asks me to put a disk in when I click it. I can get SOME adb commands to work, like adb reboot, but if I try to do anything else, it says it can't find the device.
Yes, I'm a noob, yes I screwed things up, but this is my only phone and it's a work phone and it might cost me my job. Lesson learned. I just need to get my phone back to working order. Please, please help.
Alternatively, it does have insurance, so I could let one my kids drop it into the toilet.
Click to expand...
Click to collapse
Firstly, you need to find the way to unlock your bootloader. After that, you can flash the TWRP and get in to recovery ( The original recovery cant access, dont worry, just flash TWRP after unlock bootloader) Next you will be able to flash the custom roms.
Your phone can boot to briliant screen, so it wasnt brick, dont worry.
SOLVED
Followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=2051032
I'm rock solid with a relatively stock app. Thanks for all posters and for Clonz for writng a badass [HOWTO].
Congratulations, next time please post in the correct forum as noted above.
Thank you,
mf2112
XDA Moderator
I would gladly appreciate and donate to anyone who can step-by-step guide Me to reviving My Shield Tablet 32GB LTE US! I had TWRP but somehow cannot make it back into it, all i get is the bootloop or the Fastboot screen. My laptop runs on Win8 and most of the time can't or won't recognize the tablet and when it does, it can never seem to find the files I'm trying to push to it. Someone told Me it can never be truly or permanently bricked and for about 6 months I gave up but I miss having a bigger screen, games, all the storage, etc. I need My tablet back and NOBODY is giving Me a clear way to do it as I AM pretty much a noob at all this. This is the absolute most stressful/tedious root I had ever had to do and shortly after getting TWRP and achieving root access through KingRoot, I accidentally wiped My partition and then locked Myself out of recovery... If ANYONE can help, I would ULTIMATELY appreciate it. Thank You.
Mmmmmmmh your tablet have unlocked bootloader?
If yes probably you can do something with ADB....
if not...i think you can trash your tablet ;_; at least if you don't solder an eprom flasher, but it's out of my possibility and need sort of reverse engeneering
If you can actually get to the fastboot menu, you should be good to go. You'll have to unlock your bootloader, but once you do that you can flash the recovery partition or flash an entire recovery image. Do respond if you're looking to do so.
I unlocking the bootloader was the very first thing I did. Yes, i need to know exactly where to get the image, where to save it, and how to push it thru adb please.
I do have accidental insurance... But i don't want to do that.
If you go to the link in my signature, you will find guides for flashing the recovery partition (among other things) as well as download links for the recovery images.
If you lack installations for adb/fastboot, there's a tool on XDA called Minimal ADB and Fastboot. I'd recommend using it.
can you help me? I have same issue.
My tablet only shows up as APX in device manager.
Cant boot up to NVIDIA logo, Cant boot up to fastboot nothing.
It was unlocked before now.
No bootloader, no luck. Only NVIDIA can help you now.
http://forum.xda-developers.com/shield-tablet/help/help-help-bricked-shield-tablet-original-t3313428
I believe I can get it working again somehow by puting the recovery on the SD card seeing how mine came with a usb adapter
Reflash twrp via fastboot