Database Info

Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo

Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.

So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike

Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.

DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!

It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.

well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.

DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.

okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse

farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.

Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!

farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.

DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?

Thanks for that important tidbit, solarnz. I'm going to file it away for future use.

OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!

Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk

[Q] Can't boot into recovery/Boot loop issue

I got my TF yesterday, I rooted today, and everything has been working marvelously.
That is, until I got ambitious. This is the fifth android device I've installed a custom ROM to, so I figured it would be smooth sailing. I did a nandroid backup in CWM, and then installed the newest version of Prime, which then refused to boot. Ever the optimist, I restore my backup. Which also won't boot. Then I get frustrated. Moving on, I try out Revolver, which then boots just fine. I download Revolver Parts, and it tells me there is an update (I installed 3.5.2), which I confirm for install. The tablet reboots, and never makes it into CWM..
Every time it boots, I get to the initial screen, that says Eee PC, Asus, and NVidia. after two or three seconds, it goes black, and starts again. If I tell it to enter recovery, it reboots and never gets to CWM. The only way I found to get it to boot is to hold volume down, and then NOT hit volume up to enter recovery, and cold boot android from there.
The tablet is still functioning, but without being able to get into recovery, I'm feeling paranoid about something happening that would need recovery to... recover from.
I wasn't able to find any answers after looking for most of the day; I thought perhaps NVflash would help (I can get into USB mode by holding volume up), but the download link isn't working. Does anyone have any suggestions, or have heard of anything like this before? Any answers at all would be appreciated, thanks in advance.

nvflash and only nvflash...if the link is dead,try here..
btw nvflash links here in xda works well
linux
http://www.mediafire.com/?vyci8t4i5ayg2t1
windows
http://www.mediafire.com/?004a8n53arbc5o6

sert00 said:
nvflash and only nvflash...if the link is dead,try here..
btw nvflash links here in xda works well
linux
http://www.mediafire.com/?vyci8t4i5ayg2t1
windows
http://www.mediafire.com/?004a8n53arbc5o6
Click to expand...
Click to collapse
yea, this happen somtime, not sure why, especially with prime for me. use nvflash and push revolver 3.5.2 with cwm, busybox, and su. then make a nand and try and restore it.
you could always try holding low vol + pwr for 6 secs then let go of owr but still hold low vol untill promt tells you to hit high vol to load cwm. that should work as well....

Thanks for the replies, both of you. Nvflash fixed it, works like a charm now. I love this device

[Q] UK 3G Xoom - Possible brick? Bootloop after Moray update.

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.

Stuck no recovery. No nothing.

I have a sl101. I only get eeepad screen. My son did something to the machine. I can get it to say booting recovery but nothing happens. I also can get a text that says cold booting Linux. Again nothing happens. Nvflash says USB write fail. But when I check adb the device is recognized. Is there a way for me to adb push a recovery in there for me to boot too, so I can reflash a rom. I have a little dilema here. I also was wondering if I can flash rom thru adb. I read once that's how they used to do it on g1. I don't know if I am speaking accurately though. Any kind of light shed on me will be greatly appriciated
Sent from my SAMSUNG-SGH-I997 using xda premium

not sure about the slider but i had a customer return yesterday with this exact issue on the tf101 and i couldnt get out of it. the tf just kept switching itself back on and getting stuck on the splash screen.
found this set of instructions but im not sure if its what you need or if it will work:
http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
good luck

That is exactly what is going on with mine. The slider is basicly the same thing. I plug it in and I tries to boot. I thought you had to be booted into recovery or the rom for adb to work? That's why I believe this method you just revealed to me. Or some variation of it will work. I will be trying shortly.
Sent from my SAMSUNG-SGH-I997 using xda premium

not working transformer
i have asus tranfrormer 9.x.x.x, recovery 5.8.x.x, after i did superwipe , every thing is gone and i cant flash any rom through adb/nvflash saying cant write to sdcard (read only). any suggestions?

HELP : Same problem, no apx, recovery strange, no boot
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!

densleonis said:
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
Click to expand...
Click to collapse
nvflash if your TF101 is compatible model.. (must B60 and below).
Or read Wolf's thread HERE. It might helped everyone here..

Thanks but everything needs adb connexion and as apx is not working, i can't connect ADB..
I have a B50 model

Nobody have a clue ?
well, I have to send it back to my reseller that will change it but before that I need to delete clockwork mode or brick it, how can i do ?
I tried every thread here, update rom does nothing, looks like it does not write anything on the tablet
Thanks in advance

try to follow this procedure...
http://forum.xda-developers.com/showpost.php?p=25636698&postcount=5
let me know

Hello, thanks, but as I can't get to apx mode, I can't use nvflash, so still stuck with my recovery, I tried to modify super Wipe package to do things but can't get through...
If someone can make a package to delete recovery, then I can try it on my tablet, I really yneed it to be bricked cause now it load with Rogue's recovery on and on, so the reseller will new it has been modified and I will have to pay to get it back ...
Thanks in advance

with the procedure posted in the previous link you don't need APX mode and don't need NVflash...
Just boot your TF in recovery mode and plug it to your pc...
remove all previous drivers and install the new one that you can find in the post
ciao
ps... at the end of the procedure you will have your TF101 with stock rom and stock recovery

I will try but even when I am on recovery, nothing appears in Hardware management, no recognition from My computer, still strange... And when I power + vol down key, It never says to presse vol up in the text in the upper left corner, just says booting linux kernel...
When I try to boot pressing vol up + power, nothing happens, not even the clics that can be heard when it powers up...

I had a similar issue when I used SuperWipe and discovered my ROM on the external SD Card could not be accessed by CWM
I tried pushing the file with adb but kept receiving errors - protocol, etc. I suspected it was a driver issue along with the fact that 64 bit systems don't always play nicely with drivers. I actually dug up an old hard drive and did a very basic install of 32bit Win7. I booted the Transformer into CWM and when I connected it to my PC - I pointed it to the universal naked driver. I was then able to successfully push the rom to internal storage and used CWM to flash it

Hello,
I tried to connect my tablet to an old Windows 2000, but still nothing happens

Hello every one, I finally sendt back my transformer to my reseller, now I can buy a new one...
Thanks again

Tf101 boots directly to cwm.

I have a tf101. Today I was poking around at it, trying to fix some odd issues I have with it. Its rooted, and on cyanogen 10 nightly.
Its sbk2 or maybe even newer.. sbk3? Not sure if that exists. Anyway, when I rooted it I was unable to get insecure boot, and I had it in my head that this was the cause of some of my issues. So I grabbed tool from the tf101 development forum here (I'll get the link and add it once I'm at a computer) which claimed to work on sbk2 and newer. Ran through its procedure. And at the end I was back to my cm10 but supposedly with insecure boot. One of the things that. Ever worked for me was the reboot to recovery option in the shut down menu. So I tried that. And it worked! But its cwm 3.x. figured I'd take care of that through ROM manager later. I rebooted, and I stead of booting to android, it went to recovery again!
If I power it on holding vol down it'll let me 'cold boot' android, but I can't get it to boot normally any other way. I can't get to... apx? Power and vol up, if just never powers on...
Did my recovery get flashed to the wrong partition or something? Is there some bit I can flip back to tell the tablet to boot normally?
Oh, also, I flashed cwm 6 a d it never took. It still boots this 3.x version.
Sent from my Galaxy Nexus using xda app-developers app

Here's a link to the tool i used.
http://forum.xda-developers.com/showthread.php?t=1688447

I seem to have fixed my issued by using the following threads advice:
http://forum.xda-developers.com/showpost.php?p=23339963&postcount=249