Database Info

TF101 in boot loop

Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move

This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.

TomTcom said:
This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.
Click to expand...
Click to collapse
The ICS to JB isn't the issue as the issue started happening randomly with a ICS Rom that has been working for 4+ months when it has never had anything put ICS (well HC when I got it last year). Trying the JB rom was a near last ditch effort
I tried Revolutions superwipe several times, didn't help.
I probably completely screwed it up now in frustration. Tried to load the stock rom and now Recovery is screwed and it is boot loop so I don't think I can connect it to the computer now.
Hosed you think?

So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.

Firehawkns said:
So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.
Click to expand...
Click to collapse
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop

Firehawkns said:
Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move
Click to expand...
Click to collapse
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium

morphuex said:
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop
Click to expand...
Click to collapse
Yea, I can do the power + vol down and then up and get the recovery android guy, then he goes on his back and a red exclamation comes up (which I believe means no recovery mode installed
I can also do the pwr + vol down and then wait 5 seconds and get the wipe device or android options, but it won't let me choose anything, 10 seconds later it reboots.
clouse2013 said:
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
Will try tonight, but I believe all of those involve the computer having time to recognize the device, which it doesn't stay on long enough for the computer to recognize is and it won't seem to connect USB when the android guy is up.

nice rom! going to check this out tonight, thanks!

So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?

Firehawkns said:
So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?
Click to expand...
Click to collapse
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go

pops106 said:
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go
Click to expand...
Click to collapse
Thanks for the info, truly! I had searched for Drivers, but not naked.
That worked and it allowed me to use Easyflasher to get CWM back on.
Now I am back where I started, I have tried loading several Roms. Everyone hangs up about 15 seconds into first boot while the setup splash screen is on (for example the dotted circle on stock Asus rom or the simon says color circle like the JB rom or what ever it was in the ICS rom I was using. Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.

Firehawkns said:
Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.
Click to expand...
Click to collapse
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.

grgmre said:
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.
Click to expand...
Click to collapse
Yea, I tried that first. Sorry forgot to mention.

Are you able to flash the stock firmware using Easyflasher?

cabraswell said:
Are you able to flash the stock firmware using Easyflasher?
Click to expand...
Click to collapse
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWOP and delete everything you see on the system and then reflash?

Firehawkns said:
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWRP and delete everything you see on the system and then reflash?
Click to expand...
Click to collapse
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?

Firehawkns said:
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?
Click to expand...
Click to collapse
Have you tried using nvflash that blasts everything, takes you back to as clean as clean can be.
I am starting to think hardware though but if you can sit in recovery of adb / apx mode without issue then maybe it is a software thing.
No probs wiith the drivers by the way, its not really the right website for searching for the word naked.... dam don't can't won't imagine what you could of found with the members in here...

SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.

Firehawkns said:
SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.
Click to expand...
Click to collapse
I'm glad you finally got it fixed. I had some issues a while back (two weeks after I bought it) and I panicked and caused more trouble. Finally after stepping away from it for a day or two and a wife encouraging me I was able to get it going again...but my gut was in knots for that day or two.

Tablet after redoing the original root does not go over the system.
Not have access to ADB DEVICE or by Windows or the Linux Ubuntu, no longer accepts update totally blocked.
Ask help for those who have been through this problem.

[A700] bricked infinite boot loop

So starting from beginning, while playing some music, my A700 reboot and hang up in infinite loop of Acer and Iconia Tab logos. As Vol+Power was not responding, I sent it back to Acer for repair and received it back yesterday after they replaced motherboard (and microphone!?).
Cool.
But no, because after a couple of hours of re-installing, it reboot and finished in the same Logos loop, just after selecting Airplane mode.
So my question, can I re-flash this A700 with a complete clean stock ROM, as I have only access to Fastboot mod?

To reflash with fastboot, you'd need an unlocked bootloader. I wouldn't risk that if I were you.
It looks likes a hardware issue. A ROM contains drivers. Drivers control the hardware. When going into airplane mode, the drivers shut down some of the hardware components, like WIFI and Bluetooth. If you'd have a modded ROM, I'd say there's some driver issue which causes the tablet to crash (weird that it's stuck on bootloop, though). Since that's not the case, I'd say there's something wrong with your hardware.
To apply factory settings, did you do the right moves?:
http://forum.xda-developers.com/showthread.php?t=1861092
How did you enter fastboot mode?
Note that there's only a slight difference in going into fastboot or the factory reset mode. It's only a Vol + and -.

I was asking because I already flashed (in November) my 'previous' A700 with a stock ROM (because JB OTA update failed) without unlocking anything (but using Recovery).
You are probably right, it may be an hardware fault as it does exactly the same as first time and that Acer Support replaced complete motherboard. However it was looking at me very strange that I could get two hardware fault in the row.
I will give a try to the factory reset (I did not knew the move), thanks for the tips.

As far as I know it's not possible to flash a stock ROM with fastboot without unlocking the bootloader. Instead, you have to rename the stock ROM to update.zip and put it on your internal storage and then flash it by using recovery (also a button trick).
It could be that it's still the same hardware problem. Maybe Acer didn't know what was wrong and just replaced the motherboard. It's a massive repairing service center, so they're not going to search for everything.
Oh, an important question:
Did Acer, or did they not reinstall your tablet after they "repaired" it?
If not, then it might just be that. It's like your home pc. When you change your motherboard, you might need to reinstall the thing (or re-activate Windows, but that's not relevant ) to prevent errors.
Good luck and I hope you succeed
Ps. For what it's worth, you can also try to reflash your device with a beta ROM (it's beta because there isn't a stock ROM available which you can flash without having the bootloader unlocked). You can download it here. Now I'm not quite sure if you can update your tablet then, so it's coming out of beta. To flash it, do whatever I said with the renaming to update.zip (to transfer the ROM, you can use an sd card. It might just look for update.zip on the sdcard too). Please keep in mind that I'm not sure if you can update your tablet so it'll come out of beta. If you are going to try this, please post your results here

troun2000 said:
So starting from beginning, while playing some music, my A700 reboot and hang up in infinite loop of Acer and Iconia Tab logos. As Vol+Power was not responding, I sent it back to Acer for repair and received it back yesterday after they replaced motherboard (and microphone!?).
Cool.
But no, because after a couple of hours of re-installing, it reboot and finished in the same Logos loop, just after selecting Airplane mode.
So my question, can I re-flash this A700 with a complete clean stock ROM, as I have only access to Fastboot mod?
Click to expand...
Click to collapse
Considering the same issue happened under the same circumstances, we can pretty much rule out hardware failure. (they claim to have changed the mainboard.
If you look at the Acer 700 troubleshooting tree, they followed procedures. Or perhaps they "claimed" to have changed the system board, when in reality they just re-flashed the rom over the top so they can make more money by the hour. A common practice.
So the issue to me, seems to be either a faulty rom, or, faulty player. Were you using a player from the Play Store?
Also, would help to know which OS you were on. ICS or JB?
As with re-installing a rom, you should be able to get to the stock recovery. In which case, you could try
a. Re-installing the stock version rom again (renamed as update.zip)
b. Install an update.zip compatible with your region.
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
More than likely you have animation loop. Which means the OS is corrupted somehow.If I understand you correctly.
As with fastboot OEM unlock, you can do the following;
Flash a custom recovery
Flash a kernel (boot.img)
Flash a complete system image. This is not like flashing a Rom. It's an image file generated from another user who has a working 700.
As with unlocking your bootloader, well, it depends on if you wish to get things fixed. Or to return it yet again to Acer Repair. Can't tell you what to do Mate. But if it were me, I would take matters into my own hands after previous attempts.
MD

So I tried the following (yes, it is inverted relative to theory);
- Press [vol +] + [power]
- As soon as the tablet vibrates, let go of power and play several times [lock]
=> Fastboot mod, displaying "Bootloader vJB-653b3d3: Starting Fasboot USB download protocol"
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] and play [lock]
=> no effect
And as reminder, Recovery is not reachable.
TomONeill said:
As far as I know it's not possible to flash a stock ROM with fastboot without unlocking the bootloader. Instead, you have to rename the stock ROM to update.zip and put it on your internal storage and then flash it by using recovery (also a button trick).
It could be that it's still the same hardware problem. Maybe Acer didn't know what was wrong and just replaced the motherboard. It's a massive repairing service center, so they're not going to search for everything.
(...)
Ps. For what it's worth, you can also try to reflash your device with a beta ROM (it's beta because there isn't a stock ROM available which you can flash without having the bootloader unlocked). You can download it here. Now I'm not quite sure if you can update your tablet then, so it's coming out of beta. To flash it, do whatever I said with the renaming to update.zip (to transfer the ROM, you can use an sd card. It might just look for update.zip on the sdcard too). Please keep in mind that I'm not sure if you can update your tablet so it'll come out of beta. If you are going to try this, please post your results here
Click to expand...
Click to collapse
So I guess I can not flash, because I do not have access to recovery, only to fastboot.
TomONeill said:
Oh, an important question:
Did Acer, or did they not reinstall your tablet after they "repaired" it?
If not, then it might just be that. It's like your home pc. When you change your motherboard, you might need to reinstall the thing (or re-activate Windows, but that's not relevant ) to prevent errors.
Good luck and I hope you succeed
Click to expand...
Click to collapse
Yes they re-install OS as the A700 came back with a German Rom where I sent it with a French Rom.
Thanks a lot for your help :good:

Moscow Desire said:
Also, would help to know which OS you were on. ICS or JB?
[...]
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
Click to expand...
Click to collapse
Can you answer both questions MD asked you?
If you're running Jelly Bean, the bootloader has changed. This requires a different way of going in the recovery mode:
DЯΦ[email protected]П said:
With JB there is a change on the A700 (can't test on A701):
Boot into recovery:
- Press [vol-] + [power]
- Once the tablet vibrated, let go [power] and keep [vol-].
- Now the tablet vibrates a second time, let go [vol-] and press [vol+] quick
- Once the text that appears on the screen ("loading recovery kernel image"), let go [vol+].
Click to expand...
Click to collapse

Moscow Desire said:
Considering the same issue happened under the same circumstances, we can pretty much rule out hardware failure.
Click to expand...
Click to collapse
Not really, first time it happened while playing music with google music player (reboot then loop).
Second time it was after setting the Airplane mode for night (reboot then loop).
Moscow Desire said:
(they claim to have changed the mainboard).
If you look at the Acer 700 troubleshooting tree, they followed procedures. Or perhaps they "claimed" to have changed the system board, when in reality they just re-flashed the rom over the top so they can make more money by the hour. A common practice.
Click to expand...
Click to collapse
I though the same but I found a 'technical paper' saying that board and microphone were changed, and both Wifi and Bluetooth Mac adresses have changed. So it seems they really changed motherboard.
Moscow Desire said:
So the issue to me, seems to be either a faulty rom, or, faulty player. Were you using a player from the Play Store?
Also, would help to know which OS you were on. ICS or JB?
Click to expand...
Click to collapse
Rom were 'different' when it happened; first was an FR and second was a DE. It was google stock player (only first time).
JB both times.
Moscow Desire said:
As with re-installing a rom, you should be able to get to the stock recovery. In which case, you could try
a. Re-installing the stock version rom again (renamed as update.zip)
b. Install an update.zip compatible with your region.
Click to expand...
Click to collapse
I do not have access to stock recovery, only fastboot mode
Moscow Desire said:
There are 2 types of boot loop.
1. Iconia.... this is a boot animation loop (stuck at boot animation)
2. Tab continually re-boots over and over. This is a boot-loop
3. Although not considered a boot-loop, stuck at the Acer logo.
So which do you have?
More than likely you have animation loop. Which means the OS is corrupted somehow.If I understand you correctly.
Click to expand...
Click to collapse
I have;
Acer Logo/animation -> Inconia Tab Logo/animation -> reboot -> Acer Logo/animation -> and so on...
Moscow Desire said:
As with fastboot OEM unlock, you can do the following;
Flash a custom recovery
Flash a kernel (boot.img)
Flash a complete system image. This is not like flashing a Rom. It's an image file generated from another user who has a working 700.
As with unlocking your bootloader, well, it depends on if you wish to get things fixed. Or to return it yet again to Acer Repair. Can't tell you what to do Mate. But if it were me, I would take matters into my own hands after previous attempts.
MD
Click to expand...
Click to collapse
OK, that helps a lot, thanks. I guess what I would like to do is to flash a system Image. Where can I get one?
So far, I have Android SDK installed and Acer drivers installed (which bring me a "ADB interface"-"Acer fastboot interface" device in Windows Device manager)

[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] Cyanogenmod stuck, hours in vain

For Tab 2 P3100:
I'm a stranger to flashing Android ROMs, and it's hardly a surprise that after 2 hours of struggling with my rooting and then flashing, Cyanogenmod gets stuck on the blue-circles load screen.
Cause of the problem would likely be that I unknowingly flashed in the newest nightly release, which was unstable. All stock roms I've encountered either don't allow me to load it from Odin because it's not a .md5, or it takes hours to download (and the server likely cuts me off before I'm done).
I've been roaming these boards (and others) for a long while, but there's been no easy way to unscrew the Cyanogenmod up without those stock roms that have to be downloaded from failing servers with terrible download rates and cut me off. Any help on how to easily recover it with any working ROM in any way (even if it unroots the device) would be appreciated. (Got to lower my standards by now!)
Alternatively, are there any custom ROMs out there that flash straight from Odin instead of from ROM Manager (I don't know how to make Cyanogenmod flash from Odin)? With the OS stuck in boot I obviously can't open ROM Manager app to flash a new one...
Side note: Clockwork Recovery is definitely on my Tab, but using Vol.Up and Power buttons won't conjure it (although Vol.Down and Power does conjure my Odin). Therefore my plight.

icehawk_1995 said:
For Tab 2 P3100:
Side note: Clockwork Recovery is definitely on my Tab, but using Vol.Up and Power buttons won't conjure it (although Vol.Down and Power does conjure my Odin). Therefore my plight.[/I]
Click to expand...
Click to collapse
Make sure you hold the Power and vol + until you see the Samsung Tab2 and then keep holding the vol+ a little longer till Recovery starts to load.
Here is a good video on installing CM 10.2 with download links in the description area.
https://www.youtube.com/watch?v=uooLuG0Ydr8

Try wiping data from recovery.
You know, it's a sad day when your cellular service is faster than your home broadband.

Hi, thanks for your replies.
I've made some progress, because I could load my default ROM again via Odin, so I can sustainably retry different Cyanogenmod builds.
Sadly, I've tried the latest nightly build, release candidate and stable release, and ALL of them have gotten stuck during booting (at the cyanogenmod spinning circle).
I have since tried to reformat the device and clear the cache, but that apparently hasn't been working as well.
Regarding the YouTube tutorial video shared above, I tried following the steps exactly, but it appears that my Clockworkmod Recovery mode screen looks quite different from the one in the video, and mine doesn't have some of the options it has. (I did use ROM Manager to automatically download CWM Recovery, not sure what is wrong with that). In any case, I still can't conjure Recovery mode from Vol.Up + Power button--I can only access it by using the ROM Manager app and clicking restart into Recovery.
Is there a similar error to what I'm experiencing? Because so far I still haven't found a thread that has a resolved issue with my device's symptoms.
Thanks for any help again!

Thanks for your help, particularly the YouTube tutorial video link that concisely showed me how the successful install looks like.
Turns out the CWM Recovery that ROM Manager automatically downloaded and flashed for me the first couple of times was an outdated/screwed up one that didn't work properly (ie. couldn't follow every step in the video because some features required in the video's steps were unavailable).
For future reference, if anyone encounters the same problem I did, it's something wrong with the Clockworkmod Recovery version, no doubt. For some reason, one fine instance like any other, ROM Manager finally got it right and installed the right version of CWM Recovery and I can now access all the features, and pressing Vol.Up + Power does conjure the Recovery Mode now.
Thanks for helping me fix my tablet, guys. I kinda absolutely hate TouchWiz UI and Cyanogenmod is indeed miles ahead. Happily running the latest nightly build of 10.2, loving it.

Cyanegonmod stuck
I cant reboot system , I have tried everything but wipe data/system restore. everytime it goes back to same screen. Now I am getting error messages while back and restoring image of data. I my be just not familiar but it shows my recovery files dated back to 2000 and 2010. How could the date change.

Recovery Help

So I've gotten back an old TF300t that I had originally rooted and rommed and all that good stuff long ago before handing it over to someone else and I'm not sure what exactly was done in the meantime but I can't seem to get the recovery to work now. It boots into recovery but the screen is split into two halves one on top of each other and it does not recognize any touch input, the screen also flashes off every few seconds. It is on the 4.2 boot loader and It appears to be some version of TWRP installed currently but any attempts to install another recovery do not seem to do anything(I've tried clockwork, newer TWRP and a "Kang" TWRP that was recommended in the most popular rom). I haven't seen anything like this before but I don't have much experience with ASUS stuff and my current phone is a super locked down Verizon S5 so I'm quite a bit out of practice.
Does anyone have any thoughts on how I might fix this odd issue? Or even what the cause is for that matter. The tablet works fine otherwise though being stuck on the kit kat rom is kind of annoying. A solution that can be done from the tablet alone would be ideal as the USB cable seems to have gone bad and I only have a wall charger on hand but I can get a replacement cable if this is fixable.
EDIT: NEVERMIND...after manually loading another TWRP recovery I was able to fix the issue and now have a 6.0.1 rom running from that, when I tried to install the Kang recovery I got the same thing with the split screens though not sure what I must be doing wrong. A mod can delete this thread if they wish.