Related
powered up with PWR and (-) key and wont come out of it
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
still stuck
tried your solution, nothing.
let it charge overnight to make sure I wasnt being a total scrub and the battery was dead....nothing
Any other suggestions would be greatly appreciated.
skip this, finally woke it up...on to next problem thanks all
When I first tried to flash to 1.1a, something like this happened. I don't think it was the ROM -- I think something malfunctioned inside the file system.
It was in the continuous Off/VS Birds/G-TabletLogo loop and even the power switch would not turn it off!
I wound up flashing CWM, and when I got into CWM I re-partitioned and re-formatted everything and then was able to successfully re-flash to TnT 2.2.0. (With the file system fixed, I am guessing I probably could have gone back to 1.01a if I have wanted to.)
Glad you are back working.
Rev
ARGHH!!
So has anyone found a definitive way to get these devices out of APX mode? I did a full restore on new device to clean up all the partitions and such, now nothing seems to get this thing to come out of APX. I suppose I could power it up with nvflash and leave it on the nvflashing screen until the battery dies, but there had to be a better way than burning the battery down overnight...
I have tried all sorts of combinations of powering on and off, is there a magic sequence lol...
my gtab wont boot up
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
georgetirone said:
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
Click to expand...
Click to collapse
Please don't hijack threads. There are LOTS of threads about boot loops. Check out some of the boot loop threads.
I was able to finally get the device unlocked and running much better. I used the nvflash recovery to get back to stock, then used Z4Root to get the device rooted stock. The rooting seems to have un-apx'd the device, and it works fine from there. So I would recommend keeping z4root on your drive so you can install it and root the device if it gets stuck in apx mode lol. It's a dirty hack but it worked for me when nothing else did.
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
butchconner said:
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
Click to expand...
Click to collapse
Hi,
Would a logcat (adb logcat) show anything?
Just a thought...
Jim
blue tooth stuck in apx
my bluetooth was stuck in apx. i unstuck it by installing a bluetooth switcher from the market.
Hop this helps someone.
roebeet said:
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
Click to expand...
Click to collapse
what worked for me is holding down the same buttons to getting into apx mode.
both +/- volume buttons and then power until the screen turns off.
nickmaccombs said:
skip this, finally woke it up...on to next problem thanks all
Click to expand...
Click to collapse
May I ask how you got it started up? The only way I can get it to start is to NVFLASH. If I turn it off again, it'll be stuck in APX mode...
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
I got my TF yesterday, I rooted today, and everything has been working marvelously.
That is, until I got ambitious. This is the fifth android device I've installed a custom ROM to, so I figured it would be smooth sailing. I did a nandroid backup in CWM, and then installed the newest version of Prime, which then refused to boot. Ever the optimist, I restore my backup. Which also won't boot. Then I get frustrated. Moving on, I try out Revolver, which then boots just fine. I download Revolver Parts, and it tells me there is an update (I installed 3.5.2), which I confirm for install. The tablet reboots, and never makes it into CWM..
Every time it boots, I get to the initial screen, that says Eee PC, Asus, and NVidia. after two or three seconds, it goes black, and starts again. If I tell it to enter recovery, it reboots and never gets to CWM. The only way I found to get it to boot is to hold volume down, and then NOT hit volume up to enter recovery, and cold boot android from there.
The tablet is still functioning, but without being able to get into recovery, I'm feeling paranoid about something happening that would need recovery to... recover from.
I wasn't able to find any answers after looking for most of the day; I thought perhaps NVflash would help (I can get into USB mode by holding volume up), but the download link isn't working. Does anyone have any suggestions, or have heard of anything like this before? Any answers at all would be appreciated, thanks in advance.
nvflash and only nvflash...if the link is dead,try here..
btw nvflash links here in xda works well
linux
http://www.mediafire.com/?vyci8t4i5ayg2t1
windows
http://www.mediafire.com/?004a8n53arbc5o6
sert00 said:
nvflash and only nvflash...if the link is dead,try here..
btw nvflash links here in xda works well
linux
http://www.mediafire.com/?vyci8t4i5ayg2t1
windows
http://www.mediafire.com/?004a8n53arbc5o6
Click to expand...
Click to collapse
yea, this happen somtime, not sure why, especially with prime for me. use nvflash and push revolver 3.5.2 with cwm, busybox, and su. then make a nand and try and restore it.
you could always try holding low vol + pwr for 6 secs then let go of owr but still hold low vol untill promt tells you to hit high vol to load cwm. that should work as well....
Thanks for the replies, both of you. Nvflash fixed it, works like a charm now. I love this device
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.
Hi everybody, I am experiencing trouble with my tf101 S/N B70 after I tried to install a custom ROM.
I am not able to boot properly as it seems I have deleted the ROM before trying to install a new recovery. The result is the tablet is stuck on ASUS logo and it is not possible to boot, recover, wipe, basically anything.
I tried PERI, Easy flasher, but none of them seem to work.
If I plug the tablet on a PC running win7 but I cannot install the drivers.
Any idea or suggestion on what to do?
Up for help...
Any news here? Would somebody please answer this call for help?
Even if someone would tell me to just throw it in the garbage can...it would be appreciated!
I had the same problem. I was stuck on the logo too.
I discovered I was only able to cold boot by vol down and power like recovery but when the text appear, you wait 10 sec.
Do you have access to APX mode ?
Hope that will help
espad0n said:
I had the same problem. I was stuck on the logo too.
I discovered I was only able to cold boot by vol down and power like recovery but when the text appear, you wait 10 sec.
Do you have access to APX mode ?
Hope that will help
Click to expand...
Click to collapse
I have the same problem and your solution doesn't work. I see the text but restarting runs to same screen as before.
Research and learn look up ADB mode on this site.
These fine gentlemen do not have the time to repeat themselves day after day.
If you look for information as to how to use ADB and find the software you will succeed.
It really is easier if you find and fix. I am not trying to be a a hole.