Database Info

Stucked on rebooting loop using Prime v 1.9.1

Hello everyone,
First i know this is the general Q&A but since i do not post often [ever] i can't post directly to the development forum for the Prime [ROM]
My Transformer is a B6 model
So here is my issue, I installed Prime about 4 days ago was working fine no problems, and just today (silly of me) i realized that the time zone for the table was at default (don't remember what it was) i think UTC - 0, in any case i went ahead and changed that to Eastern didn't install anything new other the amazon market app.
In any case the table was working fine but as soon as it went to sleep it got locked into a rebooting mode it will perform the mem check and POST, it completes initialization but when it reaches "Activating root access..." it reboots and the cycle repeats.
I can obviously re-flash it and get back to working order but is a rather a unusual error, by the way i do have APX access.
Any ideas?
Thank you very much

Cheers for posting in the correct section dude. You have a problem, you are asking a question.
Thanks for not cluttering up the DEV threads with this.
Have you tried a cold boot?
Also, boot into CWM and clear the caches
Still havin probs? then reinstall the rom and see what happens
Cheers
CaNsA

XRACER said:
Hello everyone,
First i know this is the general Q&A but since i do not post often [ever] i can't post directly to the development forum for the Prime [ROM]
My Transformer is a B6 model
So here is my issue, I installed Prime about 4 days ago was working fine no problems, and just today (silly of me) i realized that the time zone for the table was at default (don't remember what it was) i think UTC - 0, in any case i went ahead and changed that to Eastern didn't install anything new other the amazon market app.
In any case the table was working fine but as soon as it went to sleep it got locked into a rebooting mode it will perform the mem check and POST, it completes initialization but when it reaches "Activating root access..." it reboots and the cycle repeats.
I can obviously re-flash it and get back to working order but is a rather a unusual error, by the way i do have APX access.
Any ideas?
Thank you very much
Click to expand...
Click to collapse
Hi, I doubt that changing the timezone would have a negative effect on your transformer so I'm wondering if maybe something else causes this. Maybe some app that doesn't like the TZ to be changed or maybe even something completely unrelated. Can you get a logcat of the problem and it might help to shed some light on this problem you are experiencing?

you probably have a bad download. Redownload the Tom and try again.
Redownloading the Rom would be better though...oopps

Hello everyone,
thanks for the quick reply, although i am familiar with computers in general i am not very familiar with the android platform.
How do i get it if the system keeps rebooting every 5-7 seconds? or is by default created when the system reboots?
I have been reading through the android dev tools and it needs to be access via adb, i am not very familiar with this environment. Any guidance will be appreciated.

power on with power / vol - and when it says to hit vol up. Yhis will boot you into CWM. Clear dalvik and cache and reboot. If that doesnt work then just flash the rom again. If that doesnt work then wipe data.

thebadfrog said:
power on with power / vol - and when it says to hit vol up. Yhis will boot you into CWM. Clear dalvik and cache and reboot. If that doesnt work then just flash the rom again. If that doesnt work then wipe data.
Click to expand...
Click to collapse
Hello,
Thanks for the reply, i have already try, all of the above mentioned steps, except for the last one i am not really sure what you mean (If that doesnt work then wipe data)
Also i attempted to install another rom (revolver) in this case since it hides the POST procedures it just shows the eee Pad and Asus logo for about 7-10 secs and then reboots

There is an option in CWM that wipes data/factory reset. It wont wipe your personal folders or your external sdcards but it will reset the system back to the beginning and remove all your apps which you have to reinstall

thanks i also did that as a last ditch effort, yet nothing.
hmmm... i refuse to believe my tablet is bricked.
What i will try to do is restore to stock 3.1 and see if that works.
it just seems weird that it was working with no issues until i modified the TZ.
But thanks, and i will give the reset one more try.
----Update----
On a side note.
when in recovery mode i have tried the restore option, but it keeps giving me
E:Can't mount /sdcard
i do presume that is the internal memory where the recovery image is located am i right?
--------------------------Update 2--------------
So i went ahead and nvflash with stock 3.1 that got me back in to working mode, however when attempting to go into the recovery meny it seems something got messed up.
First the prime animation shows up (although i have flashed, revolver and stock on top of that)
then the android logo shows up with a warning triangle on his chest, i guess that is the typical something is wrong here logo.
and then nothing no access to recovery.
So i am trying to flash this one more time, let see if that fixes the issues.
---------------Update 3----------------
well that got me no where :S
i flashed the system with revolver 3.2 via nvflash and i am back to the rebooting loop.
I will wait to see if any of you guys have some ideas, in order to further proceed

Sorry to keep asking.
Does any one have any idea how to resolve this?
Also Roach you mention a log dump, could you please let me know how i can get this log.
thank you.

I know this doesn't help all of your problems, but people have reported having trouble with the nvflash version of Revolver. (myself included) I would recommend, because this is always what works for me when I soft-brick my tablet, nvflashing the latest version of Prime again. Assuming it boots successfully, you can always put the normal version of Revolver on your sdcard, reboot into Recovery, wipe data, and then install Revolver from there.
I hope something works for you soon
Sent from my DROIDX using Tapatalk

Well it seems that did the job.
Although weird why the issue happened in the first place, well i would like to thank everyone who replied. Next time i will keep a rom on my sdcard all the time :-D.
Also thanks XDA And all the community in here.
Sent from my transformer using XDA Premium. (Revolver ROM)

[Q] Stuck in recovery loop and cant install custom rom

Hi Everyone.
Im a real noob so please take it easy on me.
So today i decided I wanted to root my Asus Transformer TF101 - B70
I used "viperMOD PrimeTime v4.5" according to a post on this forum and had no hassles what so ever. The link - http://forum.xda-developers.com/showthread.php?t=1427125
I proceeded to download root apps and everything worked fine.
After reading - http://forum.xda-developers.com/showthread.php?t=1518768
I decided it was time to root my device.
I downloaded Revolver IC400 Beta 1.3 and "RecoveryInstaller" also found on this forum. I placed both of these files on my micro sd card.
I then installed recoveryInstaller and the device booted in recovery. When i selected "install zip from sdcard" and then "choose a zip from sdcard" the device does not seem to find the sd card and only shows data on the device.
So i clicked "go back" and then "reboot system now".
But now everytime my device boots it goes to the recovery screen.
If i hold the power button and volume down when the device is booting, then when the text appears press nothing, then it boots. But the next time it just boots to recovery again..
I have searched the forum and see others have this issue but cannot find useful information.
Please help me out of this loop and i would really like to install revolver rom. Can anyone tell me what to do to install it or what i have done wrong?
Thank you in advance!

Are you sure you installed CWM recovery by RecoveryInstaller or did you install it via Rom Manager?
This thread show how to solve the recovery loop problems when installing CWM via ROM Manager
http://forum.xda-developers.com/showthread.php?t=1530337

Thank you so much! I followed that post and solved the repeat recovery problem. Now to figure out getting the recovery to read the sd card..

chemm said:
Thank you so much! I followed that post and solved the repeat recovery problem. Now to figure out getting the recovery to read the sd card..
Click to expand...
Click to collapse
Use either Roach's 3.2.0.1 or Team Rouge recovery for external sd card
both can be found here in a RecoveryInstaller form
http://forum.xda-developers.com/showpost.php?p=22359727&postcount=218

Thank you for the reply and all assistance.
I installed Team Rogue's recovery and started the installation from sd. It went perfectly and even said "Done". i proceeded to reboot my device but it still has stock rom. As if the installation was not successful at all.. Why could this be?

All I can suggest is try again. When it boot up, do you see a blue progress bar?

Yes there was a progress bar briefly but that was it. Then it did some short update and booted. Exactly the same and stock and revolver parts confirms that it is not revolver rom. Im so bummed

Try a different custom ROM to see if it work

I tried again and still nothing. The links on Gnufabio's older posts dont work. Where can i find an older version of revolver to try that?
Thanks

Im now trying "Download version 3.11 full" from this link, http://forum.xda-developers.com/showthread.php?t=1173230&highlight=wallpaper
As this seems to be the only download still working. I can find any working downloads of any other versions.
Thank you for your time in replying, as you may see I'm new and cant post in the developer area where all this discussion is going on.

Did you do a full wipe? Factory reset, wipe cache and then wipe Dalvik? A must do procedure before a ROM change. And dont forget to backup before all , just in case.

ok so that didnt work... It gets stuck at the blue android loading screen.....
and i cant recover either as it now does not find any of my recovery files.........
HELP!! please...

bboyle said:
Did you do a full wipe? Factory reset, wipe cache and then wipe Dalvik? A must do procedure before a ROM change. And dont forget to backup before all , just in case.
Click to expand...
Click to collapse
Hi, yes i did do all of the above... Im out of ideas. DOnt know what else to do..
Think i should just try load stock os and stick with that

I have the same problem now, im on AOKP 1.5
Then i updated my CWM with Rom manager (thinking it might be a new version or something)
And now constant CWM loops.
I will try to reflash CWM.
Btw. is the touch CWM working on the asus transformer?

cmalo.nl said:
I have the same problem now, im on AOKP 1.5
Then i updated my CWM with Rom manager (thinking it might be a new version or something)
And now constant CWM loops.
I will try to reflash CWM.
Btw. is the touch CWM working on the asus transformer?
Click to expand...
Click to collapse
There is a problem with the recovery, have a look at this thread/:http://forum.xda-developers.com/showthread.php?t=1530337
I had the same problem but it is fine now after following the solution.
Sent from my Transformer TF101 using Tapatalk

so i managed to boot to recovery and installed Prime rom. That didnt work but them atleast i could recover from my back up which i couldnt do prior. I proceeded to install 3.1.1 of revolver which is now working fine.
Happy that i finally have something installed and working. I still dont know what was wrong or what i was doing wrong and very curious as to why revolver 4 wont work..
Hope his new update comes out soon and will work fine.
Thanks for all the help and support guys!

chemm said:
so i managed to boot to recovery and installed Prime rom. That didnt work but them atleast i could recover from my back up which i couldnt do prior. I proceeded to install 3.1.1 of revolver which is now working fine.
Happy that i finally have something installed and working. I still dont know what was wrong or what i was doing wrong and very curious as to why revolver 4 wont work..
Hope his new update comes out soon and will work fine.
Thanks for all the help and support guys!
Click to expand...
Click to collapse
Very odd....... Revolver should work once you have a previous version. You probably did wipe data/and factory reset. ??
EDIT: What is you tablet version BXX?

chappatti said:
Very odd....... Revolver should work once you have a previous version. You probably did wipe data/and factory reset. ??
EDIT: What is you tablet version BXX?
Click to expand...
Click to collapse
Revolver 4 still refuses to work. Have tried many times.
My tablet is B70.
So now that my tablet is rooted and has custom roms on it. Does any1 know of any kernels, apps or anything that can help me set the "Login" details to a wifi connection.
Basically to connect to my university wifi you have to use your username and password. If you go through the browser there is a pop up, and then you can browse fine. But none of the apps work. Ipad 2 , playbook and many other tablets allow you to add the login details to the wifi settings on that connection so there after all connections from the tab use the login in, thus working fine.

chemm said:
Revolver 4 still refuses to work. Have tried many times.
My tablet is B70.
So now that my tablet is rooted and has custom roms on it. Does any1 know of any kernels, apps or anything that can help me set the "Login" details to a wifi connection.
Basically to connect to my university wifi you have to use your username and password. If you go through the browser there is a pop up, and then you can browse fine. But none of the apps work. Ipad 2 , playbook and many other tablets allow you to add the login details to the wifi settings on that connection so there after all connections from the tab use the login in, thus working fine.
Click to expand...
Click to collapse
Re the WiFi, if you go to >settings>>wireless networks>>wifi, and long press (press and hold for few seconds) on the network a menu should pop up that says "modify network" or "modify config" or so. Choosing that gives you a menu to enter username, pass, seurity settings etc.
At my University, I can do that on any network that is broadcast even if I have not connected to it before.
Good luck !!

chappatti said:
Re the WiFi, if you go to >settings>>wireless networks>>wifi, and long press (press and hold for few seconds) on the network a menu should pop up that says "modify network" or "modify config" or so. Choosing that gives you a menu to enter username, pass, seurity settings etc.
At my University, I can do that on any network that is broadcast even if I have not connected to it before.
Good luck !!
Click to expand...
Click to collapse
hi there.
Thank you for the reply. I unfortunately only get the options "proxy settings" and "ip settings".

[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] Bricked?

Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark

mmanis said:
Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark
Click to expand...
Click to collapse
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad Infinity TF700T&p=28&s=1
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.

berndblb said:
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here:
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.
Click to expand...
Click to collapse
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark

mmanis said:
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark
Click to expand...
Click to collapse
Hmm, still bootlooping.
Next thing I would try is to boot into the bootloader, select 'Wipe Data' with the Volume Down button, hit Volume Up execute.
And actually, before even booting back to system (that would be choosing the Android), I would reflash the firmware - just for good measure after the data wipe.
Can't wait to hear if that solves it!

So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark

mmanis said:
So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark
Click to expand...
Click to collapse
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.

berndblb said:
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.
Click to expand...
Click to collapse
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark

mmanis said:
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark
Click to expand...
Click to collapse
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491

berndblb said:
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491
Click to expand...
Click to collapse
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark

mmanis said:
Hi, how do you capture a logcat
Click to expand...
Click to collapse
This was at the top of the xda portal http://forum.xda-developers.com/showthread.php?t=2274119
best bookmark it for future reference its a really good tutorial

mmanis said:
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark
Click to expand...
Click to collapse
At this point only a bootloop logcat can shed light on this. Check the tutorial JTR recommended. It's truly good - thanks for the link!

Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark

mmanis said:
Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Right try booting without the microsd card in. Something is wrong with it. Also turn off the Bluetooth, what ever it is trying to connect to is adding lots of entries to the log.

TF300T Bootloop?

Hello, I'm trying to fix an ASUS tf300t here. It's not mine, actually it's a co-workers' tablet. He asked me to flash a custom ROM and recovery, so I did. I installed TWRP 3X and KatKiss ROM. Once I gave it to him, 2 weeks later he called me and said it was on a boot loop (the thing was working fine before).
Now I'm stuck with what I think is a soft brick and a bootloop, I see the ASUS logo, and I can access fastboot, plus I can see the 3 icons (RCK, Android logo and the forbidden "WIPE DATA").
If I try to start Android, it says "Cold Booting linux", then resets.
If I try to start Recovery, I see the TWRP logo, then it resets after 15 seconds.
I see the tablet in fastboot devices, but not on adb devices.
Help!

Ebony Dubois said:
I installed TWRP 3X and KatKiss ROM.
Now I'm stuck with what I think is a soft brick and a bootloop, I see the ASUS logo, and I can access fastboot, plus I can see the 3 icons (RCK, Android logo and the forbidden "WIPE DATA").
Help!
Click to expand...
Click to collapse
I'm sorry, but KatKiss ROM needs KangTWRP strictly recommended in the install instruction in post #1 https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702.
However it's good to hear that you are able to start in fastboot protocol.
What to do now you will find here: https://forum.xda-developers.com/showthread.php?p=44244313#post44244313. Doing a Buster99 is the only way to get out of the trouble you have without bricking your device. Be sure you have the latest Asus firmware "WW_epad-user-10.6.1.27.5"

Lifesaver
ebonit said:
I'm sorry, but KatKiss ROM needs KangTWRP strictly recommended in the install instruction in post #1 https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702.
However it's good to hear that you are able to start in fastboot protocol.
What to do now you will find here: https://forum.xda-developers.com/showthread.php?p=44244313#post44244313. Doing a Buster99 is the only way to get out of the trouble you have without bricking your device. Be sure you have the latest Asus firmware "WW_epad-user-10.6.1.27.5"
Click to expand...
Click to collapse
My man, you're a lifesaver. I saw this post but I didn't think it was necessary. Turns out, it was. Now I'm back up and running! Imma install that kang TWRP Thank you so much!!!!

Ebony Dubois said:
My man, you're a lifesaver. I saw this post but I didn't think it was necessary. Turns out, it was. Now I'm back up and running! Imma install that kang TWRP Thank you so much!!!!
Click to expand...
Click to collapse
You are welcome!
Thank you very much for your very kindly response. Wish you always good luck. :fingers-crossed: