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] ICS update failed

Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan

I had the exact same problem. Got it fixed. Use the method from this thread: tabletroms.com/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html

Thanks for your reply. I noticed on that page that it says that if the serial number is BD70 or above (which mine is) do not use the tool. Has there been an update that allows this to be used on the newer units?
Thanks,
Ryan

Hi there!
I got a similar problem yesterday and the error was that a file inside the DATA partition could not be deleted. I noticed when doing a factory reset from CWM.
If you have CWM and you can flash the "super wipe tool" you can fix the problem. Then you re-flash the ROM. I got it working and now I'm on a clean clean clean clean.... clean shiny install
check my threat if you want:
http://forum.xda-developers.com/showthread.php?t=1516204
Hope it helps!

I'm guessing I do not have CWM as I do not know what it is?
Thanks,
Ryan

sh.assassin said:
Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan
Click to expand...
Click to collapse
Ok, I'm going to help you unbrick your device. But you need to forget everything other people in here have told you. Ok? And just do. Don't question. Just follow the steps.
(1) Go to the following asus webpage, choose android as OS and download your version of the 21 firmware. WW, US, TW, etc.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
(2) Rename the downloaded zip file to "EP101_SDUPDATE.zip"
(3) Move zip file to a micro sdcard.
(4) Insert microsdcard into the TF.
(5) Turn off TF.
(6) Power on by pressing power button and volume down buttons at the same time. When white texts appear on upper left hand corner, release power button and volume down buttons and press volume up button.
(7) Watch your TF unbricking itself.
(8) Leave it alone to do its thing.
(9) Write me a check for 2,000 yen.

Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan

british.assassin said:
Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan
Click to expand...
Click to collapse
Download is corrupted. Have you tried again?

Yes I have, about 10 times and it always comes up with that error.

I had the same failure and had to install .13 and update 3times to get to ICS. Got it from the Unlockr link. Worked great and then rooted with ViperMod.
A clean install is seemingly not having as many issues. Plus I already have an AOKP ICS rom on my phone, so I already know most of the ICS features.

I did try downloading .13 and installing it the same way as I did .21 (putting in on the micro sd and powering on with power & vol - to get into recovery mode), however when I try this I get the yellow triangle and black exclamation mark again, only this time it does not stop my tablet from booting back in to .21.

british.assassin said:
Yes I have, about 10 times and it always comes up with that error.
Click to expand...
Click to collapse
This error comes up when you have a corruption in your stock recovery.
You won't be able to "downgrade" to .13 the way you did with this. Unfortunately, there's no easy way for you to go about this. Here is what you need to do. Yeah, it will be a little long.
(1) Root via nachoroot.
(2) Install CWM via recovery installer. Can be found in the app portion of this forum.
(3) Download the repacked .13 version from the following link.
http://dl.project-voodoo.org/transformer-roms/3.0.x/
(4) Download stock recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=606402&d=1306284085
(5) Flash the repacked .13 version via CWM.
(6) Restart the TF.
(7) Flash the stock recovery.
(8) Restart TF.
(9) Upgrade via OTA. One of the updates will give you the appropriate stock recovery.
Failure to follow my instructions precisely will result in brick.

[HELP] MY TF101 won't wake up (no matter which ROM)

Hi, I've been experiencing this problem for a while now. Once the screen comes off, the tablet will never wake up. I've clean flashed, with/without gapps, and even right after flashing (EOS, CM, RaymanFX's & Gierdo's, ARHD...) once I turn the screen off (with either the lockpad button in the keyboard, the button on the screen, or after a display timeout) it will never light up again.
I also have trouble switching off the tablet, i.e. I hit shut down and it will never do (I had to go into recovery by power vol-) and hit shut down from there.
Buttons work, so I am thinking it might be firmware problem? Since all roms and different recoveries dont make a difference... I am currently downloading the latest ASUS official firmware from their website, but it'll take some hours since my internet connection here is rubbish.
thanks for any advice and help!

When you flash the different ROMs, are you wiping all the following:
Cache
Davlik Cache
System
Factory Reset (from recovery)
If you are skipping any of these, it can cause issues. The most important one is the Factory Reset to erase the system settings and can cause huge issues when jumping from one ROM to another ROM.

Yes thanks, of course I am. Full wipes between flashes, cache and dalvik, when changing kernel, etc.
TWRP recovery doesn't install (nor with EasyFlash or GooManager) I currently have CM recovery flashable with EasyFlash. Twrp stalls on a splashscreen and nothing else...

TheKaser said:
Yes thanks, of course I am. Full wipes between flashes, cache and dalvik, when changing kernel, etc.
TWRP recovery doesn't install (nor with EasyFlash or GooManager) I currently have CM recovery flashable with EasyFlash. Twrp stalls on a splashscreen and nothing else...
Click to expand...
Click to collapse
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes

thanks for your help, it still didn't work. It stays stuck in the recovery splash screen and it won't even boot into the rom. I have to fix it using EasyFlasher.
I am thinking that all my problems are due to a corrupt firmware or something like that. The tablet never reboots by software or shuts down, with no matter which ROM.
I will perform an internal storage backup and use EasyFlasher to install the official Asus firmware. Hopefully that will make the trick.

TheKaser said:
thanks for your help, it still didn't work. It stays stuck in the recovery splash screen and it won't even boot into the rom. I have to fix it using EasyFlasher.
I am thinking that all my problems are due to a corrupt firmware or something like that. The tablet never reboots by software or shuts down, with no matter which ROM.
I will perform an internal storage backup and use EasyFlasher to install the official Asus firmware. Hopefully that will make the trick.
Click to expand...
Click to collapse
I found a little mixup with my code, it should be just a REBOOT command at the end and not a REBOOT RECOVERY.
If you do the reboot recovery, it does not complete the flash of the firmware on boot.
Give that a shot and see if it works if you want.

frederuco said:
I found a little mixup with my code, it should be just a REBOOT command at the end and not a REBOOT RECOVERY.
If you do the reboot recovery, it does not complete the flash of the firmware on boot.
Give that a shot and see if it works if you want.
Click to expand...
Click to collapse
Nothing worked. I indeed followed the insturctions you gave me but reading them in the TWRP site so I did it correctly. Still didn't work. I flashed using EasyFlasher the official ASUS firmware, and the tablet still behaves in the same way: Will never shutdown or reboot by software command, will not wake up when screen is switched off... this is frustrating, but it needs to be software, right? It can't be hardware, since the power button does work...
I dont know what else to do... I wiped my tablet clean and flashed the official firmware and the issue is still present...

the thing is that the tablet is working (PC reacts to usb) and it makes noises when I plug the keyboard dock... but the power button will just not turn the screen on...

Hi, a little bump just to see if someone could help me out. I flashed the latest Team EOS nightly 4.2.2, and it runs like a charm, but as soon as I turn off the screen, it wont come back. I need to do a reboot by holding the power button to be able to use it again. Could it be hardware?
It happens likewise with all roms...
Sent from my Transformer TF101 using Tapatalk 4 Beta

TheKaser said:
Hi, a little bump just to see if someone could help me out. I flashed the latest Team EOS nightly 4.2.2, and it runs like a charm, but as soon as I turn off the screen, it wont come back. I need to do a reboot by holding the power button to be able to use it again. Could it be hardware?
It happens likewise with all roms...
Sent from my Transformer TF101 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Go to the android development tab of this forum and use the katkernel. Works with EOS roms. I still had a screen freeze but better than the stock kernel. This may help you. Follow the flashing instructions.
Sent from my SGH-T999 using Tapatalk 2

Thanks Tom, I have already tried katkernel in the past, with the same result.
the tablet cant power off either, it stays with the powering down box for ever. I need to hard reboot it into the recovery and power it down from there...
It's all very strange, it happens like that with every rom i've tried, from 4.0 to 4.2.2, and every kernel.
Sent from my Transformer TF101 using Tapatalk 4 Beta

I have followed all the threads I have seen, flashed from roaches Prime 3.0 rom, to EOS 4.2.2, stock Asus/unbrick with easyflash, and using tubuntu installer.
I always find the same issue, cant reboot (it stays stuck), cant tunr screen on after turning it off, and TWRP recovery doesn't work (only the two others provided by easy flasher).
Might it be there is something partially bricked?
I once bricked my USB in my old nexus. I am desperate, the tablet works fine when turned on but can't reboot, power down, or turn the screen back on... it has to be some kind of bricking...
ps: from here: http://forum.xda-developers.com/showthread.php?p=42046184#post42046184
TomTcom said:
It's probable my commands aren't correct. Hopefully you can see from the idea of how I started the commands and try to figure it out with some google searches. I don't know for sure if that config file is in the correct format for nvflash either. I used it from the Tubuntu application but the Tubuntu application doesn't have a "format all" and recreate everything option.
I believe your partitions are either not set correctly or the partition table is corrupt or non-existent.
I don't think you have faulty hardware at this point because you can execute wheelie and nvflash without problems so as long as you can do that you still have a fighting chance to recover the tablet.
I searched a lot on these commands but you'll need to do some more. I don't know yet what else I can provide. Good luck!
Click to expand...
Click to collapse
I can corroborate that your commands work.
TomTcom said:
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
Let me know what happens.
Click to expand...
Click to collapse
Is there a way that some part of the hardware is bricked?

That's always possible it's bricked but I wouldn't give up. Dig deep into wheelie and nvflash and how they work. I'm sure you can get it running right again.
Wish I knew more, sorry!
Sent from my SGH-T999 using Tapatalk 2

TomTcom said:
That's always possible it's bricked but I wouldn't give up. Dig deep into wheelie and nvflash and how they work. I'm sure you can get it running right again.
Wish I knew more, sorry!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
no worries, thanks for your effort. Is there a way to completely start from scratch? like format and wipe everything, install fresh bootloader, firmware, etc? like wipe everything wipeable and installable in the hardware?

TheKaser said:
no worries, thanks for your effort. Is there a way to completely start from scratch? like format and wipe everything, install fresh bootloader, firmware, etc? like wipe everything wipeable and installable in the hardware?
Click to expand...
Click to collapse
My commands from the previous postings were to do just that. Format_all and use the configuration file to load from but I could've edited it wrong.
You can try manually pulling all the files from fresh stock software. I don't use any of the tools out there so it's back to research on it.
Sent from my SGH-T999 using Tapatalk 2

once I do a format all, do you know what will I end up with? no OS, no SDCard files, no internal memory, but also no recovery? If so, I guess I have to do flash recovery via Easy Flasher on APX mode.
edit 1:
i couldnt make the --format_partition --format_all work, it gave an error on partition 0.
So, I run --format_partition 1 and its taking too long it seems, cant tell if it's hung up or what...
edit2.
from the config file you provided in the other thread, I can see the partitions are named 3-16. I manually formatted them with your androidpartition.cfg file. I will proceed to installing the stuff and report back. Thanks!

I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December

TheKaser said:
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
Click to expand...
Click to collapse
Good for you! Glad you got it!
Sent from my SGH-T999 using Tapatalk 2

TheKaser said:
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
Click to expand...
Click to collapse
Hi!
I have similar problem to you.
My tablet is not booting corectly. Stuck on the logo (look at the picture).
I have tried: Easy flash (a few soft), and when i click on the "unbric" my tablet is disconecting from PC.
I can't go into TWRP. I only boot into APX mode.
I can turn on my tablet by recovery mode, and chose there "android" option, but this is annoying.
I dont konw what to do ;(

[Q] Stuck on boot Asus spinning wheel

First I'd like to thank the mods and everyone who contributes to this forum. It's an invaluable resource. Now to my problem.
Asus Tf700 is unlocked and rooted on latest TWRP recovery, which does work. However, after making a backup with the new TWRP version, the tablet is stuck on the boot screen (spinning wheel). Last week I flashed a JB ROM, didn't like it, so went back to ICS with the .30 firmware. Flashed it using old version of TWRP from micro-SD card. Device has been working fine since then. I tried reflashing the .30 kernel again using the same method. It installs kernel, but no luck, still stuck on boot screen. Then I tried TWRP restore, using the new restore file. It restores, but goes to the boot screen and just spins. Any ideas? nvFlash is unavailable to me. What else can I do? Should I try a factory restore in TWRP? I'll keep messing with it later today, but any suggestions are appreciated.

When you install a stock rom, doesnt it install back the stock recovery? I would try reflashing twrp and installing cleanrom, keep it as stock as possible and see if it boots.
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4

A spinning Asus wheel is always recoverable.
You have some incompatible rom / kernel / bootloader / data combination I suspect. It's easily done.
I'd make sure you are on a more recent version of TWRP - something like 2.3.1.0 or 2.3.3.0 that supports ICS and JB. It's very dangerous leaving such an old version of TWRP if you go to JB.....
Personally I'd update TWRP to 2.3.1.0 and then install the latest JB file from the Asus website to start with.

missiveusa said:
First I'd like to thank the mods and everyone who contributes to this forum. It's an invaluable resource. Now to my problem.
Asus Tf700 is unlocked and rooted on latest TWRP recovery, which does work. However, after making a backup with the new TWRP version, the tablet is stuck on the boot screen (spinning wheel). Last week I flashed a JB ROM, didn't like it, so went back to ICS with the .30 firmware. Flashed it using old version of TWRP from micro-SD card. Device has been working fine since then. I tried reflashing the .30 kernel again using the same method. It installs kernel, but no luck, still stuck on boot screen. Then I tried TWRP restore, using the new restore file. It restores, but goes to the boot screen and just spins. Any ideas? nvFlash is unavailable to me. What else can I do? Should I try a factory restore in TWRP? I'll keep messing with it later today, but any suggestions are appreciated.
Click to expand...
Click to collapse
1. What bootloader are you on currently? (See 4)
2. By flashing the ".30 kernel" I assume you mean flashing the .30 stock ROM, am I right?
Your device went into a hung boot after making the backup, so I'm not really surprised it does exactly the same when you restore that backup. Have you tried flashing .30 stock ROM again?
3. Which recovery do you currently have? As Tylorw1 said, if you flash a full stock ROM, you'll reflash everything, up to and including the bootloader and recovery.
4. If you still have fastboot available (pick the USB symbol instead of RCK after POWER+VOL_DOWNing), you might want to try to reflash either TWRP or CWM (http://forum.xda-developers.com/showthread.php?t=1926286 for the latter; I have VERY limited experience with the former and you may well have more than me ).
Updating your bootloader just to be sure is recommended, as most current ROMs will not boot properly without it.
Has the fiddling brought any new points of view, or new discoveries?

Update
Just got in from work. Of course can't do anything else but try to get this unworking device to boot. Not in panic mode yet, as I assume if I get to the spinning wheel, there is hope for recovery.
Just flashed back to the stock ROM, which indeed restored stock recovery. Still would not boot past Asus wheel. Now I will attempt to install the latest TWRP version using fastboot, then try to flash new ROM. Panic is slowly creeping in, but I think I just need to keep at it. How should I proceed once latest version of TWRP is installed? Backup? Flash? Android is new territory for me, a bit rockier than Windows. If this were a laptop on Windows 7 I'd be up and running already . Thanx for the replies and any help.
OK. I used stock recovery to to a system restore. That worked, but of course all user data and apps are gone. Assume root access is also history, so it's just a matter of getting root access and restoring apps. I made a backup to SD card using Titanium Backup. Can I restore from here using the backup file, or should I just stop complaining and be happy I got the damn thing to boot?!!! No big deal really: I'm back to STOCK .26, virgin device (except for being unlocked). Guess I'll get root and move on. Thanks. Great work here. I've learned a lot browsing these forums. Maybe one day I'll graduate from N00B status!

missiveusa said:
Just got in from work. Of course can't do anything else but try to get this unworking device to boot. Not in panic mode yet, as I assume if I get to the spinning wheel, there is hope for recovery.
Click to expand...
Click to collapse
Agreed.
Just flashed back to the stock ROM, which indeed restored stock recovery. Still would not boot past Asus wheel. Now I will attempt to install the latest TWRP version using fastboot, then try to flash new ROM. Panic is slowly creeping in, but I think I just need to keep at it. How should I proceed once latest version of TWRP is installed? Backup?
Click to expand...
Click to collapse
No use -- it won't boot.
Flash?
Click to expand...
Click to collapse
CROMI, redownload, hash check.
Android is new territory for me, a bit rockier than Windows. If this were a laptop on Windows 7 I'd be up and running already .
Click to expand...
Click to collapse
I know exactly what you're talking about. Was there once as well, and still it is changing so fast it's hard to keep up.
Thanx for the replies and any help.
OK. I used stock recovery to to a system restore. That worked, but of course all user data and apps are gone. Assume root access is also history, so it's just a matter of getting root access and restoring apps. I made a backup to SD card using Titanium Backup. Can I restore from here using the backup file, or should I just stop complaining and be happy I got the damn thing to boot?!!!
Click to expand...
Click to collapse
I would not take the chance, and just leave it as it is.
No big deal really: I'm back to STOCK .26, virgin
Click to expand...
Click to collapse
<< and still complaining?
device (except for being unlocked). Guess I'll get root and move on. Thanks. Great work here. I've learned a lot browsing these forums. Maybe one day I'll graduate from N00B status!
Click to expand...
Click to collapse
Maybe...
J/K!
You've done great, and I am happy to hear you got it up and running. I started out answering before reading your post in full, assuming it wasn;t fixed yet. Left the comments for reference (and fun, or mockery... -- good job, see you around!

same issue
Hi,
I have a same issue. I still was using the original ROM of ASUS. Now JB.
The device was once rooted in ICS, but that was lost when going to JB. And I did not yet try to reroot it. I was running JB already several months.
The device is unlocked, but I did not install a custom boatloader yet.
This week I was working in the car. Using the 3G connection of my phone and shared it via bluetooth to my pad to access my mails.
Suddenly the pad rebooted, and it never got further than the ASUS screen with the spinning wheel.
I can boot in recovery mode (power and V-), but then I cannot use my V+ buttom. I can only select the RCK, but unfortunately, It's not succesful. I first get the android with open lid and the spinning ball, but after a few seconds it changes to the android with the open lid laying on his bag with the red triangle on it. And it stays like this forever.
I cannot seem to enter fastboot mode (power and V+)
any suggenstion? All data can be erased. No problem as long as the tablet is working again.

TeTTiweTTi said:
Hi,
I have a same issue. I still was using the original ROM of ASUS. Now JB.
The device was once rooted in ICS, but that was lost when going to JB. And I did not yet try to reroot it. I was running JB already several months.
The device is unlocked, but I did not install a custom boatloader yet.
This week I was working in the car. Using the 3G connection of my phone and shared it via bluetooth to my pad to access my mails.
Suddenly the pad rebooted, and it never got further than the ASUS screen with the spinning wheel.
I can boot in recovery mode (power and V-), but then I cannot use my V+ buttom. I can only select the RCK, but unfortunately, It's not succesful. I first get the android with open lid and the spinning ball, but after a few seconds it changes to the android with the open lid laying on his bag with the red triangle on it. And it stays like this forever.
I cannot seem to enter fastboot mode (power and V+)
any suggenstion? All data can be erased. No problem as long as the tablet is working again.
Click to expand...
Click to collapse
When you hold down vol- and power button to boot into stock recovery, then when you see white text on the screen, let go both buttons, then hitting the Vol down button to move the highlighted to USB icon, can you try that?
Edit: if that's working move the highlighted to the "WIPE" icon, then hit Volume up twice, this will perform factory reset and wipe all your data and reset your device back to factory setup. You will see the Android spinning for awhile then your tablet will reboot and you will have to do the setup again, just like when you just brought the device.

buhohitr said:
When you hold down vol- and power button to boot into stock recovery, then when you see white text on the screen, let go both buttons, then hitting the Vol down button to move the highlighted to USB icon, can you try that?
Edit: if that's working move the highlighted to the "WIPE" icon, then hit Volume up twice, this will perform factory reset and wipe all your data and reset your device back to factory setup. You will see the Android spinning for awhile then your tablet will reboot and you will have to do the setup again, just like when you just brought the device.
Click to expand...
Click to collapse
Thanks for your help. I can boot into stock recovery. But I could move to the USB icon or the the Wipe Icon previously. Now I was able to select the Wipe Data Icon and currently I'm at the virgin "Welcome" screen again.
I don't understand why now it's working and previously not. Did I switch the v- and v+ button? If that's the case, I'm even a bigger idiot then I thought :silly:
Anyhow, All well that ends well.

Stuck on spinning wheel as well
sbdags said:
A spinning Asus wheel is always recoverable.
You have some incompatible rom / kernel / bootloader / data combination I suspect. It's easily done.
I'd make sure you are on a more recent version of TWRP - something like 2.3.1.0 or 2.3.3.0 that supports ICS and JB. It's very dangerous leaving such an old version of TWRP if you go to JB.....
Personally I'd update TWRP to 2.3.1.0 and then install the latest JB file from the Asus website to start with.
Click to expand...
Click to collapse
Hi sdbags! Thanks for all the work that you have put in to make this rom!
I am stuck on the spinning wheel as well. I installed cromi x last week. The tab was working okay. Very laggy, was very disappointed. I guess I did something wrong? Last night I used lagfix and rebooted. Since then the tablet has been stuck on the spinning wheel stage. I am pretty sure I installed the latest version of TWRP and checked I had the latest bootloader. Can I check these things now? Also if they are outdated how I do I update them if my tablet wont boot up?
Thanks!

TransformingPad said:
Hi sdbags! Thanks for all the work that you have put in to make this rom!
I am stuck on the spinning wheel as well. I installed cromi x last week. The tab was working okay. Very laggy, was very disappointed. I guess I did something wrong? Last night I used lagfix and rebooted. Since then the tablet has been stuck on the spinning wheel stage. I am pretty sure I installed the latest version of TWRP and checked I had the latest bootloader. Can I check these things now? Also if they are outdated how I do I update them if my tablet wont boot up?
Thanks!
Click to expand...
Click to collapse
Lagfix takes a good 20 mins to complete, even though it says it has finished after 5. I wonder if you rebooted too early. If you have sync off it can cause corruption on the data partition which might be your issue.
The fix is to format data from the twrp wipe menu and reflash. You will lose Everything on internal so back up in twrp first please.

Sigh - all for naught

stuck on spinning cyan screen
i rooted the tf700t and installed twrp, flash cm 10.2 rc 1, then rebooted and now it is stuck on boot screen. now i find i cant get back to stock recovery or twrp to correct the issue or bootloader. anyway that my tablet isnt totalled?

tcemle said:
i rooted the tf700t and installed twrp, flash cm 10.2 rc 1, then rebooted and now it is stuck on boot screen. now i find i cant get back to stock recovery or twrp to correct the issue or bootloader. anyway that my tablet isnt totalled?
Click to expand...
Click to collapse
Why can't you go back? Vol down and power doesn't work?
CM requires you to be on the 10.6.1.14.4+ bootloader first. Also a wipe before installing is mandatory.

sbdags said:
Why can't you go back? Vol down and power doesn't work?
CM requires you to be on the 10.6.1.14.4+ bootloader first. Also a wipe before installing is mandatory.
Click to expand...
Click to collapse
i have tried several times to use the vol- and power buttons but it doesnt seem to work. i press them and then i feel like its trying but doesnt go anywhere just stays on the black screen. adb recognizes the tablet but says it is offline because the boot screen is stuck. it usually only took a few seconds for it to go to the fastboot screen but nothing now. any ideas, if i get to the fastboot i can correct the problem.

tcemle said:
i have tried several times to use the vol- and power buttons but it doesnt seem to work. i press them and then i feel like its trying but doesnt go anywhere just stays on the black screen. adb recognizes the tablet but says it is offline because the boot screen is stuck. it usually only took a few seconds for it to go to the fastboot screen but nothing now. any ideas, if i get to the fastboot i can correct the problem.
Click to expand...
Click to collapse
Hmm that sounds like apx mode to me. If you didn't save nvflash backups I suspect it has bricked

I just updated to KitKat via this threat: http://forum.xda-developers.com/showthread.php?p=52214068
I noticed that the tablet was running excessively slow and so I decided to do a Factory Reset from within the tablets Setting. Now it's rebooted and it's sitting at the Android and the spinning thing in it's chest for more than 5 mins. Does it normally take this long?

stuck itwrp 2.7.0.0
Hey guys
Long time reader 1st time asking for help. Had tf700t unlocked, rooted and running cm 10.2.1 with twrp 2.6.3.1. Tried several times to load cm 11 and met only with failure. Read a post to try twrp 2.7.0.0. Loaded twrp 2.7.0.0, via goo, backed up everything and tried to flash cm 11. Tablet stuck in wipe mode for 90 minutes. (didn't even get a chance to load it!) I stopped it and re-started into twrp 2.7.0.0. Tried to recover and got pictured error, basically stating that at the wiping data point - E:Unable to mount '/data'. Tried to flash new rom and get the same thing. I can get into recovery but that is about it..............spock help me

gothamhill said:
Hey guys
Long time reader 1st time asking for help. Had tf700t unlocked, rooted and running cm 10.2.1 with twrp 2.6.3.1. Tried several times to load cm 11 and met only with failure. Read a post to try twrp 2.7.0.0. Loaded twrp 2.7.0.0, via goo, backed up everything and tried to flash cm 11. Tablet stuck in wipe mode for 90 minutes. (didn't even get a chance to load it!) I stopped it and re-started into twrp 2.7.0.0. Tried to recover and got pictured error, basically stating that at the wiping data point - E:Unable to mount '/data'. Tried to flash new rom and get the same thing. I can get into recovery but that is about it..............spock help me
Click to expand...
Click to collapse
TWRP 2.7 does take a long time to wipe. You shouldn't have interrupted it. Now you probably have a corrupted data partition and you will have to format it. That will erase all your data, but if the nandroid you made was successful, that should not be a problem.

stolen
berndblb said:
TWRP 2.7 does take a long time to wipe. You shouldn't have interrupted it. Now you probably have a corrupted data partition and you will have to format it. That will erase all your data, but if the nandroid you made was successful, that should not be a problem.
Click to expand...
Click to collapse
1st of all thank you, unfortunately the nandroid bu was on a laptop that was stolen. Anything else I can do?

[Q] TF101 Running CM10 Won't Factory Reset

I've been scouring the Googlenets for days now trying to figure out how to fix this, and nobody has either had the exact same problem I have (doubtful), or no one has posted it.
I'm currently running CM10 and Android 4.1.2. I was planning on upgrading to lollipop via http://forum.xda-developers.com/eee-pad-transformer/development/rom-t2942560, but somehow my recovery stopped working. I had TWRP 2.3 and was going to upgrade to 2.8 (as recommended), and that's where something went wrong. I'm not exactly sure what I did, or what step I was on when it happened, but I rebooted the tablet and ended up with a never ending Asus splash screen. POWER + VOLUME DOWN to access recovery didn't get me anywhere but the same splash screen with some white text promising a recovery that would never come.
I tried APX flashing with Easy Flasher to no avail. I tried POWER + VOLUME DOWN, wait, then select wipe. Nothing. When I POWER + VOLUME DOWN, and wait, I can boot into CM10 just fine and everything appears dandy. That's when I tried Factory Reset in the settings. Still nothing!
Am I being dumb? Any help or even just some empathy would be great about now. What should I do?
Thanks in advance.

bump for luck...

I'm guessing this is a new problem and the device is too old to tinker.

I would suggest returning to stock and starting over again.

barkeater said:
I would suggest returning to stock and starting over again.
Click to expand...
Click to collapse
By returning to stock do you mean factory reset? My problem is I am unable to factory reset. Do you know another way to factory reset that I didn't try? Thanks.

I had a little time to mess around with this again, but unfortunately I didn't succeed. I tried using EasyFlasher from this post: http://forum.xda-developers.com/showthread.php?t=1688012. It taught me that the difficulties continue. It would appear tat I am not able to turn on APX mode, as I get no connection after holding power and volume up for what seems like an eternity.
I also started to wonder if something is wrong with my partitions. When I look at storage in settings, it says I have 13 GB total space, but when I add up the apps, pictures, audio, downloads, and available, it only ends up at 4 GB. That's weird.
Anyone out there have any ideas? Thanks.

ZachTMartin said:
I had a little time to mess around with this again, but unfortunately I didn't succeed. I tried using EasyFlasher from this post: http://forum.xda-developers.com/showthread.php?t=1688012. It taught me that the difficulties continue. It would appear tat I am not able to turn on APX mode, as I get no connection after holding power and volume up for what seems like an eternity.
I also started to wonder if something is wrong with my partitions. When I look at storage in settings, it says I have 13 GB total space, but when I add up the apps, pictures, audio, downloads, and available, it only ends up at 4 GB. That's weird.
Anyone out there have any ideas? Thanks.
Click to expand...
Click to collapse
Sounds like your OS is still loading? If so you might try this apk. "Reboot2Recovery" if that gets you into recovery you can flash the new twrp from there.

No luck. It boots to the never ending Eee Pad splash screen, which is the same screen it hangs on if I reboot normally.

ZachTMartin said:
No luck. It boots to the never ending Eee Pad splash screen, which is the same screen it hangs on if I reboot normally.
Click to expand...
Click to collapse
Anything here help you?
http://www.transformerforums.com/fo...-recovery-kernel-need-help-desperately-2.html
or here
http://www.transformerforums.com/fo...ogo-screen-keeps-restarting-eternal-loop.html
Stock firmware is still avaialble
http://www.asus.com/ca-en/support/Download/28/1/0/1/32/

None of them had an answer to my problem. When I do the volume down + power I get the two icons, wipe and cold boot. Wipe doesn't do anything and the other option puts me back in my OS.
I really think it's something to do with my partitions, but I haven't been able to find anything to fix it. Is there a way to reset my partitions without APX? I can't seem to APX either.

ZachTMartin said:
None of them had an answer to my problem. When I do the volume down + power I get the two icons, wipe and cold boot. Wipe doesn't do anything and the other option puts me back in my OS.
I really think it's something to do with my partitions, but I haven't been able to find anything to fix it. Is there a way to reset my partitions without APX? I can't seem to APX either.
Click to expand...
Click to collapse
When I read your problem again t seems that you have CM10 installed with stock recovery? Must be due to failed install in your first post.
Did you try the firmware download from the asus link above? Wonder what happens if you copy to system and if cm10 would recognize it as a system update ans install.
http://www.asus.com/support/FAQ/1011948/
Watch out for asus's zip in a zip.

I dusted this off with the long break. Tried to install the Asus firmware and ended up hanging on the load screen again. I'm starting to think it must be something with my bootloader, but I can't seem to figure out how to get in there.
This is probably a lost cause at this point. Thanks for the help.
Happy new year!
Edit:
I decided not to give up and ended up getting recovery back! Woohoo! I'm not really sure exactly what the problem was, but I was looking here (http://blog.chazomatic.us/2013/10/27/updating-and-rooting-an-asus-transformer-tablet/) and it looks like the following fixed it:
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
I'm still not sure why, but now it boots normally and goes into recovery just fine. :good: