Database Info

Black Screen After bad TNT 5.0 Lite Install

I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.

jesusgi said:
I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.
Click to expand...
Click to collapse
nvflash to the version included in the tntlite post there is an apk file link there

Do you mean 3588 stock?

jesusgi said:
Do you mean 3588 stock?
Click to expand...
Click to collapse
yes check the first post in the lite thread. It is linked as APK 3588

I downloaded it, but I am not sure how to use it with nvflash as compared to the restore which was relatively simple using the included bat file. Am I missing something or am I just a hopeless Noob?

jesusgi said:
I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.
Click to expand...
Click to collapse
Hmm?.. Seems there are a lot of users trying to prove the GTAB is in fact Brickable..*lol*
It is NOT!
Go here:
http://forum.xda-developers.com/showthread.php?t=861950

Yes I feel dumb about it. I did read that thread before posting. I did the restore. I can get the gtab to boot up and it is usable.......until I power down, then the only way to use it again is to reflash the restore again. I mean its usable. Not really bricked, really, but I am frustrated because it seems like I am missing the solution.

I used the nvflash from http://forum.xda-developers.com/showthread.php?t=861950 to prep my gtab for 5.0. Once it flashed and booted to the OS, I had it join wireless, then it prompted to start the update to 3588 immediately. Have you tried this?

Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours

jesusgi said:
Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours
Click to expand...
Click to collapse
Been there.......months later the tablet is still there. I can not power it off or reboot it. I bought another tablet and use "the unbootable" one at home where it sits in a dock until needed.
I have tried every nvflash recommendation out there...
There are about 4 or 5 tablets like this. Most have either been returned/swapped out or set aside and no longer used (from my reading of others with the same problem).
I can get it to boot by formatting partition 2 so if it ever goes off or I need to "update" it I turn it off.....connect it and nvflash it...holding volume + if I need to get to recovery. If not...once nvflash sends the bootloader over and formats partition 2, the device boots.
Something on mine is preventing the bootloader from booting.....the nvflash sending it over executes it and the tablet runs......

redundant - double posted

jesusgi said:
Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours
Click to expand...
Click to collapse
I got the same problem. I can only power my gtab by doing nvflash, and if i reboot, it only goes into apx mode.

Ouch. That has stopped me in my tracks. It's really bad news.
"Something on mine is preventing the bootloader from booting.....the nvflash sending it over executes it and the tablet runs......"
That's my problem exactly. My wife is going to be very upset. I thought I could keep her gtab updated without bricking it. Oh jeez that's exactly what I've done..........

Suggestion? don't do the update after you nvflash.. let the device boot up normally and put a different ROM zip file on the SD via USB.
Calkulins new ROM is based in TnT is super smooth.
http://forum.xda-developers.com/showthread.php?t=985705
From there try to reboot into recovery mode with an app like quick boot AniReboot and flash the different rom.
It may be the ROM you're trying to flash is corrupt.

I did the same too. . An didn't read the fine print. After getting the info
on how to fix my bricked gtab. Also, I had to do some Googling on apx
USB drivers for windows 7.
Long story short.. had a few pints. .. got it back to stock and installed tntl 5
The next day.. I'm using it now and I'm happy. Time for another pint.

I thought I bricked my GTab, after several hours of tweaking I was
able to flash it and run TnT Lite 5.0 now. Here is the procedure I did:
a. nvflash to stock rom. download the usb driver for windows 7 here and install (link from post by syntrix) : http://developer.download.nvidia.com/tegra/files/os/tegra_ventana_froyo_20110207.msi
b. grab the stock rom from the post by roebeet, choose "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip": http://db.tt/Wm25t7U
c. following roebeet's instruction, put Gtab to APX mode (volume down + power on), run nvflash_gtablet.bat, should flash the rom fine.
d. boot the Gtab after flashing, should be able to run the original stock rom.
e. download the 3588 stock rom from this thread:http://forum.xda-developers.com/showthread.php?t=842000
f. run recovery (volume up + power on) to upgrade to 3588 rom, remember to make a "recovery" folder with "command" (check the prefix and see if is name "sdcard") and rename the downloaded 3588 rom to "update.zip". Put both to the root of the sdcard.
g. now you should have 3588 rom after the recovery
h. download tnt lite 5.0 rom and run a recovery. you will get stuck at a black screen. Just reboot and enter recovery mode again (volume up + power on). do a "wipe data" and reboot. Then you will be able to run TnT lite 5.0. In the recovery mode, the "power" button is "enter", not the "home" button in CWM 0.8. Anyway, just follow the instruction on screen for button layout.

Thanks. I have actually done those and would do them all but G-Tab will only boot once after flash (step d) after that if I power down, I gotta black screened brick until reflashing original ROM again. It is impossible for me to do step "F" from Gaspra post

and with that I give up. I ordered another G-Tab, and I'm using the old one as a plant stand. Who said this can't be bricked? I managed to do it.

Send it to me. I'll pay shipping.

jesusgi said:
Thanks. I have actually done those and would do them all but G-Tab will only boot once after flash (step d) after that if I power down, I gotta black screened brick until reflashing original ROM again. It is impossible for me to do step "F" from Gaspra post
Click to expand...
Click to collapse
did you try to erase the rom? try this before flashing to the stock rom:
http://forum.xda-developers.com/showthread.php?t=974422

[Q] Unable to factory reset

Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section

Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).

I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.

Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App

Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?

I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.

I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back

Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.

rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything

DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty

I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric

Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App

rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.

Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.

[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.

[Q] rebooting TF700T..... first ever problem

Constant reboot suddenly appeared today
Can you stop it rebooting?
Message come up when using on and vol button
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol

PaulCopel61 said:
Constant reboot suddenly appeared today
Can you stop it rebooting?
Message come up when using on and vol button
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Click to expand...
Click to collapse
So it boots to the bootloader, you see the three icons - and then what?
It bootloops again?
Give us more info: Are you on stock? Rooted? Locked/unlocked? What did you do/install prior to this happening? Did you drain the battery so that it suddenly shut down?

TF700T first ever problem
berndblb said:
So it boots to the bootloader, you see the three icons - and then what?
It bootloops again?
Give us more info: Are you on stock? Rooted? Locked/unlocked? What did you do/install prior to this happening? Did you drain the battery so that it suddenly shut down?
Click to expand...
Click to collapse
Hi
Thanks for reply
The pad has never touched,altered,rooted,etc.... ,after reading a book on pad ..shut down in evening ...next morning problem occurs
Loads up main screen for about 6 seconds freezes the starts rebooting
By pressing on/vol button I get messages
With flashing RCK it says
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Moving along to Android symbol
it adds booting recovery kernel
signature match
Starts to install update ..
then gives me "error" android symbol
Trust that helps ...I am newbie at this worked perfectly up to now

PaulCopel61 said:
Hi
Thanks for reply
The pad has never touched,altered,rooted,etc.... ,after reading a book on pad ..shut down in evening ...next morning problem occurs
Loads up main screen for about 6 seconds freezes the starts rebooting
By pressing on/vol button I get messages
With flashing RCK it says
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Click to expand...
Click to collapse
That's ok and healthy. You are in the bootloader menu and seeing exactly what you're supposed to see here.
Moving along to Android symbol
it adds booting recovery kernel
signature match
Starts to install update ..
then gives me "error" android symbol
Click to expand...
Click to collapse
Mhh, this doesn't quite make sense...
If you say: Moving along to Android symbol - you are pushing Volume Up?
You toggle between the icons with Volume Down and execute them with Volume Up.
"Booting recovery kernel" would indicate that you pushed Volume Up on the flashing RCK icon which would fire up your recovery, and since it doesn't find a valid update file you get the Android on his back and the error message.
Since you are on stock your options are very limited. My guess is somehow your system partition got corrupted and your tablet can't boot into Android anymore.
You can give it a shot by using Volume Down to get the Android icon to flash and then pushing Volume Up, but I doubt that it would help since the tablet refuses to boot your system in the first place.
So if the above fails, go the Asus support website, the download section, enter "Transformer" in the search box, select the TF700t, choose "Android" as OS and from the resulting page choose the firmware for your SKU. If you are in Europe it would be WW, US for North America, JP for Japan - you get my drift...
Download the file and then unzip it ONCE, the result being another zip file. Rename that zip to EP201_768_SDUPDATE.zip and copy it to a microSD.
Turn the tablet off and insert the microSD.
Boot into the bootloader with Volume Down and Power.
Push Volume Up on the flashing RCK icon to boot into recovery and it should recognize the firmware zip and start to flash it.
You will probably loose everything you have on the tablet if it is not backed up. But I don't see any option for you to save your data if you want to get the tablet working again. I just hope you knew and lived by my mantra: Data not backed up is data not yet lost....
Good luck.

Tried advice
Thanks for advice
Took a week to get micro card reader !!, however downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)
Booted up as per instructions, it recognized the firmware zip and started to flash it.
Loaded as normal .. however same problem still exists ... noticed it the few seconds before it rebooted that not much had changed on desktop ?
Definitely says Android US Epad 10.6.14.10-20130801
Should desktop have changed ?
I am missing anything ?
Getting desperate
Any help appreciated
thanks
paul

PaulCopel61 said:
Thanks for advice
Took a week to get micro card reader !!, however downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)
Booted up as per instructions, it recognized the firmware zip and started to flash it.
Loaded as normal .. however same problem still exists ... noticed it the few seconds before it rebooted that not much had changed on desktop ?
Definitely says Android US Epad 10.6.14.10-20130801
Should desktop have changed ?
I am missing anything ?
Getting desperate
Any help appreciated
thanks
paul
Click to expand...
Click to collapse
I think you are going to have to wipe the device mate.

wipe
Thanks
Will do anything to get it working
As I am new at this could you guide me to best thread which gives clear instructions how to wipe and re install?
Pad is out of warranty never been altered ...
paul

PaulCopel61 said:
Thanks
Will do anything to get it working
As I am new at this could you guide me to best thread which gives clear instructions how to wipe and re install?
Pad is out of warranty never been altered ...
paul
Click to expand...
Click to collapse
When you are in the bootloader menu, choose the third icon 'Wipe Data'. You navigate there by pressing Volume Down twice, then it should be flashing. Press Volume Up to wipe your device.
You will have to re-install the firmware (same procedure I described already)

Thanks...
Everything working !!
Finally...
So I don't have similar problem again should I unlock?
What program should I use ?
Could you point to thread to show me how too ?
Paul

Glad you got it going!
Check this out: http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html