So I've been reading all the threads about recovery, and I'm just at a loss as to what to do. Here's what happened - and not sure how it happened which is even more disturbing. (Unit is 5 days old from Amazon)
I had VEGAN-Tab installed on the unit, and it was working just fine. I was playing with some MicroSD cards, and left the unit with a 2 Gig one in, that I formatted through VEGAN-Tab (no real issues from what I can tell). I left it charging and went out.
When I came home, I grabbed the tab and it was powered down, which was odd. I went to boot it and got the GTab animation which repeated over and over. I figured something went haywire (what's disturbing is I have no idea why) but I figured - OK was 5 days old.. not much on there.. I"ll just blow it away.
The problem is I can't get anything to work properly. Recovery DOES get me into ClockworkMod Recovery 2.5.1.8 but while in there, I can't do anything with the internal SDCard. I keep getting "Can't mount /dev/block/mmcblk2p1" or when I try to wipe the system I get "Can't mount /dev/block/mmcblk3p2 (no such file or directory)" as well as "No app2sd partition found, skipping format)... etc.
So I can't even wipe the SDCard. I've tried doing the NVFlash to connect and re-write, but with CWM I can't seem to get to the point where the PC sees the device in recovery mode - only as a removable drive (running windows).
Not sure what my next step is - so any help would be greatly appreciated. Thanks!
Ok - first DUH is my own - was trying to recover by hitting Volume + not Volume - .. my mistake.. NVFlashing now.. Still don't know what happened and why the SDCard went Haywire.
Anyone have any ideas on that one? Don't want it to happen again!
UPDATE - and now even after NVFlashing I can't get it to boot into recovery or normally.. Keep getting birds, then GTABlet, and then nothing. When using the Vol + option, I get that it's booting to recovery, and then I get a BANG symbol and then a reboot.. Not sure what to do..
UPDATE 2- And now insult to injury - the unit won't even turn on. It recognizes power plugged in, but the power button does nothing. I'm going to leave it plugged in for a while and hopefully leaving it will eventually make it work. /sigh/ Any help would be great.....
UPDATE 3 - And TapNTap is back... after another flash... Whew- Ok all.. Now the question is WHY did it happen? Any ideas?
Related
Could I have bricked my tablet? Or could there be a way to recover?
As for what it's current state is; (I am sure is is stuck in the reboot loop) When powering on the tablet, it displays "Android", goes dark, and repeats. Though this is a change from when I was trying to fix it on my own. Before it looping, it would show the "Android" screen and just sit there.
No comes what I think the REAL issue is... Running 'ClockworkMod v2.5.1.1-bekit-0.8', I am unable to mount an external SDcard or mount the USB Storage(text in menu implies to me it is the USB cable to computer).
So other than the images already on the tablet, I seem to be unable to get a new image into it. And of course the images on it don't do any good.
Tech1381 said:
Could I have bricked my tablet? Or could there be a way to recover?
As for what it's current state is; (I am sure is is stuck in the reboot loop) When powering on the tablet, it displays "Android", goes dark, and repeats. Though this is a change from when I was trying to fix it on my own. Before it looping, it would show the "Android" screen and just sit there.
No comes what I think the REAL issue is... Running 'ClockworkMod v2.5.1.1-bekit-0.8', I am unable to mount an external SDcard or mount the USB Storage(text in menu implies to me it is the USB cable to computer).
So other than the images already on the tablet, I seem to be unable to get a new image into it. And of course the images on it don't do any good.
Click to expand...
Click to collapse
Most definitely not bricked. I've recovered from a much worse situation (bootloader wouldn't even budge - couldn't boot into recovery or regular at all).
Since you are able to boot into recovery, there's probably a way to get things working without resorting to nvflash (we'll get to that in a second - nvflash is the failsafe mechanism, and you should be able to re-nvflash your tablet back to its original state if all else fails).
Here's roughly what I'd try in order:
Option 1) Figure out why you are unable to mount as USB in recovery. I've actually never heard of this problem. Are you using the right cable - i.e. a working USB-to-mini-USB cable (I don't think this works at all with the full sized USB port under the latch cover). Have you tried it with another computer - perhaps there's a driver issue on your PC?
Option 2) If for some reason you really aren't able to get USB mounting working in recovery (I'm skeptical - again, I've never heard of that problem - unless you really did flash a bum recovery image or something - but seems unlikely), then I'd see if you can get ADB working properly when you are in recovery mode. Search around and read about setting up ADB if you haven't already - just a matter of getting the right driver installed on your PC and installing the binary stuff (either from the full Android SDK or one of the packages that just has the ADB stuff floating around). Search the forums, you'll find some references to help you get this working and download the right stuff.
If ADB works, you can always use "adb push filetoflash.zip /sdcard/filetoflash.zip" to put a new file on your internal SD card area and flash it.
Option 3) You can always use nvflash. I'm not going to write up a tutorial on it here - search the forums for nvflash, there are several HOWTOs. Look for the stuff Roebeet posted. You'll need to install the APX driver on your PC first before this will work, and Roebeet's posts don't explain how to install it on Windows, so you'll need to search separately for that. I have gotten this to work before, but it's a pain and I only recommend it if your recovery image is truly trashed or your bootloader is malfunctioning as mine was. In other words, don't bother until you've exhausted the first two options.
So in short - you are in a pain-in-the-ass situation, but you have by no means bricked your tablet - it is very, very far from bricked. Give us more info on *exactly* what happens when you try to "mount as USB" while you have your mini USB cable plugged into the G Tablet - do you see a drive appear on your PC? Are you running a Windows box? Mac? Linux? Have you verified that a USB keychain drive works fine with your PC but the G Tablet won't mount? Basically we need some more info to guide you in your search.
Ok finally had some free time from cleaning/packing and house hunting to try fixing the tablet.
Good news is that I was able to mount the USB. I didn't notice the cat nibble on my cable... So once I dug a spare out, I was able to copy a TnT-Lite image (still had on computer) onto it right quick. Restarted and it installed the image.
So now it has TnT-Lite, though it is weirdly stuck on the setup wizard. It tells me to touch the android to continue and shows an animation of a hand touching the android. But when I touch the android, it turns white and thats it. Also I can change the language to UK or American English. Plus when I press the menu button, I can go to wireless settings, as in cell phone wireless settings. Lastly, I can make an emergency call. So new worthless image. YEY!
I next tried to reboot back into ClockworkMod to see what I could possibly do to get by the lack of continuation in the TnT. But the image install did something interesting. When trying to enter Clockwork Mod, here is what it does from powerup: Displays "Detect a recovery key pressed" then on the next line "Booting recovery kernel image", blanks the screen and then displays "Android" for a few seconds, lastly switching to an exclamation mark in a triangle and rebooting.
So how do I go about screwing it up more?
Tech1381 said:
I next tried to reboot back into ClockworkMod to see what I could possibly do to get by the lack of continuation in the TnT. But the image install did something interesting. When trying to enter Clockwork Mod, here is what it does from powerup: Displays "Detect a recovery key pressed" then on the next line "Booting recovery kernel image", blanks the screen and then displays "Android" for a few seconds, lastly switching to an exclamation mark in a triangle and rebooting.
)
Click to expand...
Click to collapse
CWM is not installed
flash the latest firmware using stock recovery
read read read
http://forum.xda-developers.com/showthread.php?t=892090
It almost sounds like you now have stock recovery in your Gtab.
If that's the case, then maybe copy a stock TNT update.zip onto the external Sdcard, and create recovery/command file on there with the string for SDCARD2, then reboot w power and volume+. If you do have stock recovery, that should flash it back to stick TNT. Try Stock TNT 3452, since that'll also flash a stock recovery for sure.
Jim
Looks like Brian and I crossposted each other .
For the recovery/command file on the external SDCARD, put the following text in it:
--update_package=SDCARD2:/update.zip
NOTE THE 2 DASHES AT BEGINNING OF THE LINE...
Jim
No really, I've Bricked It
So, G Tablet arrived about 5 hours ago. I got it rooted and tried to install CMod 8.1. Things went wrong but I'm not sure what. Anyway, the last thing that I did was to boot in Recovery and then I selected, Format System. Now, when the tablet is turned on, in the top right corner, I have a tiny red message, Magic Value Mismatch. I get this message whether the SD card is installed or not.
I know this information is a little vague but as a Nod, it's all that I have.
f3justusc said:
So, G Tablet arrived about 5 hours ago. I got it rooted and tried to install CMod 8.1. Things went wrong but I'm not sure what. Anyway, the last thing that I did was to boot in Recovery and then I selected, Format System. Now, when the tablet is turned on, in the top right corner, I have a tiny red message, Magic Value Mismatch. I get this message whether the SD card is installed or not.
I know this information is a little vague but as a Nod, it's all that I have.
Click to expand...
Click to collapse
I'm freaking out, I think I bricked it...
I'm only getting the black android screen, I can't seem to mount USB, suggestions?
Ive been stuck right where you are a few times, not to big of a deal, just NVFlash back and start over. I am assuming you are getting the black screen you mention is the APX mode one you get by starting your tab by pressing vol down and power at the same time.
Hi,
My device started boot looping while trying to restore to stock ROM to update to a new ROM.
I wen't through the nvflash process successfully (meaning nvflash wrote the images to the device) but it continue with the loop.
Eventually, it powered down and now it will not power up at all. Battery is fully charged.
Any ideas?
Thanks.
OK, so I figured out that the device was stuck in APX mode.
nvflash doesn't seem to be fixing the problem, so I'm trying adb. It doesn't seem to see the device at all. I'm sure I'm missing step on how to work with adb.
Can anyone point me in the right direction for getting adb connected properly?
Thanks.
I'm trying to get adb working following this guide:
http://forum.xda-developers.com/showthread.php?t=902860
but it cannot see the device. The drive is installed fine but the device does not show up.
I know that if I can get into the device I can put it in debug mode, but I'm not sure how to do this now. I'm thinking this could be my problem, that the device is not in the correct "mode"
Any ideas?
Thanks.
did you get this resolved? i'm having the same problem.
williec30 said:
did you get this resolved? i'm having the same problem.
Click to expand...
Click to collapse
Nope, still playing with nvflash.
Trying this now:
http://forum.xda-developers.com/showthread.php?t=974422
pgonza02 said:
Nope, still playing with nvflash.
Trying this now:
http://forum.xda-developers.com/showthread.php?t=974422
Click to expand...
Click to collapse
i was able to get the device back into apx mode and run the nvflash utility again.
williec30 said:
i was able to get the device back into apx mode and run the nvflash utility again.
Click to expand...
Click to collapse
I've been able to do that a couple of times, but after nvflash completes, just get into a TapNTap logo loop and eventually just powers down. When I am able to turn it back on, it goes straight into APX mode.
http://forum.xda-developers.com/showpost.php?p=12089833&postcount=92
kostyamat said:
http://forum.xda-developers.com/showpost.php?p=12089833&postcount=92
Click to expand...
Click to collapse
Do you mean to install CW from external micro SD?
Thanks.
This is Where I Stand
1. nvflash from TNT lite post
2. Completes and reboots, goes into GTab screen, no Viewsonic screen
3. TapNTap screen and then to n animation
4. Reboot and go to #3. Haven't counted but at some point it just powers off.
I have tried installing CW from the external SD card but cannot get to it.
Have tried adb but cannot get it to connect.
I'm totally out of ideas...I'm thinking that if I just let it sit there, it'll just work
This is Where I Stand
1. nvflash from TNT lite post
2. Completes and reboots, goes into GTab screen, no Viewsonic screen
3. TapNTap screen and then to n animation
4. Reboot and go to #3. Haven't counted but at some point it just powers off.
I have tried installing CW from the external SD card but cannot get to it.
Have tried adb but cannot get it to connect.
I'm totally out of ideas...I'm thinking that if I just let it sit there, it'll just work
Finally Worked
I have no idea what made it work.
I decided to just take a break and left the tablet connected to the computer through USB but powered down. Came back a couple of hours later and when I turned it back on, I got the Viewsonic screen.
After that, I was able to reboot and go into CW and do a factory reset, which put it in a really old version. It was all easy from there.
pgonza02:
As I understand, you can now power off and reboot you GTab.
Can you recall what were your steps to get to this point?
I'm stuck in APX mode for almost a month! I don't know what else to try...
Thanks in advance.
I tried many things, including:
Install CW by replacing the image for partition 9 with the update.zip for CW (basically rename update.zip to whatever the img file is called)
Add CW to external SD card and attempt to reboot.
Eventually I just left the tablet alone and when I came back I turned it on I saw the Viewsonic birds (this seemed to be the key, when it was not working I never saw it)
I read a thread somewhere that mentioned that nvflash has the ability to redirect output through the HDMI out so you would not see it in the main screen. My guess is that what's happening is that the output of something, that is taking time to complete, is going out that way and I just could not see it. By leaving it alone, whatever it was, completed. This is just a guess, maybe someone with more knowledge can confirm.
Sorry I couldn't give you more details.
Boot loop and black screen
I'm having the same problem. In fact, I'm unable to boot into APX mode.
I have the cover off and read about a hardware reset button. I tried pushing the
reset button (k2) but nothing happened. I also read that I can disconnect
the batter. But, I don't see where the battery wire can be just disconnected
without soldering.
Any ideas?
Hi guys, first post!
I really need help as I think I've tried everything.
I installed CM7 but it was low on battery while installing. Midway through the install process the screen said I need to plug into the charger that came with my device. Then it instantly went to the screen with an exclamation point and says
www dot palm dot com/ROM
Power+Center just gets it back to the same screen.
WebOS always fails at 1% and says it could not be reset.
I've tried ClockworkMod but it is unable to reinstall the .zip files.
I ran WebOS through command prompt and it said the required files were locked by an unknown file.
PLEASE HELP, my touchpad is useless now and I don't fully know what to do in ClockworkMod, which seems to be the only thing that works right now.
Here is what I Did
This is what worked for me....good luck
I would recommend you hard power it off by power and center buttton for 15 seconds.
Make sure you have charged it
Then Run the webOSdoctor program.
For me I rebooted the tablet and held the volume up button until the USB symbol popped on the screen...then the WEBOS Doctor found the tablet and we where on the road to recovery.
Give it a shot and let us know if this helps. You won't be the first or the last to get this issue.
Wait... it died while installing?
Part 1: breathe
Part 2:
IF you can get into cwm right?
In CWM, you can mount the tablet as a USB drive, then copy the update cm7.zip file to it... and install it.
DO you have the blue text boot menu?
If not you need to install moboot again...
you can do that AFTER you've fixed cm7...
IF all else fails, and you can't install cm7 via CWM, then doctor it.
If you don't know how to use CWM, google it... it's pretty straight forward.
Lesson: Don't update when battery is low?
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
WidePants said:
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
Click to expand...
Click to collapse
I'm having the same problem. I downgraded from 1.4.3 to 1.4.0. I was able to boot it once and then shut it back down so I could root it. Now it won't start up at all and I have tried everything that I can find to boot it to no avail.
The NT can sometimes get stuck in limbo while booting up, especially with SD-based boot. To get out of it, hold down the power button for 20-30 sec to turn it off then power it on again. Also remove any "bootable" SD card from the card slot; if it boots then the card was not bootable and its non-bootability was the problem.
It's also possible that the NT battery is completely drained (battery readings on some CM builds can be quite off, sometimes as much as 20 points) in which case you'd need to use the BN wall-charger and charge it for 8-12 hours.
Hi all,
Ok, so I have a weird problem with my Asus TF101 that for the life of me I can't seem to solve myself. Which is why I finally decided to ask for help.
To make a long story short: About two years ago I bought a used TF101 that I have been very happy with so far. And I definitely don't want to give it up, as it's been working fine until a few weeks ago. Then those boot loops (that everybody seems to be talking about) started and I was able to revive the device once by leaving it plugged off for a few days until the battery was empty (thus, I think, forcing a clearing of some kind of cache) and then re-booting it. Unfortunately, this does not seem to work anymore.
My TF101 has been rooted by the guy that owned it before. It features TWRP in version 2.2.1.4 and an older KatKiss ROM. Now, my situation is as follows:
Boot loops are preventing me from getting past the boot screen. I can thus not install or use any apps.
I can enter TWRP recovery mode and I could wipe the device, but I cannot find any ROM on the internal memory.
When connecting the TF101 to the computer (I'm using Linux Mint 17.3) it doesn't show up as disk. Only when unplugging it again, an error shows up on the Linux screen saying that the TF101 could not be connected. This is preventing me from loading a new ROM onto the device via a cable.
The device doesn't seem to recognize an SD card (32GB), no matter if formatted as FAT32 or as EXT3, with or without SWAP. So, in the TWRP file manager I cannot access an external SD card to load and flash a ROM.
When I enter "Mount" in the TWRP menu, I can't seem to switch to "Using external SD": When doing that I get an error "E:failed to mount /sdc (No such file or directory)" in the terminal window.
I have been reading forums up and down, but can't seem to find any helpful advice that applies in my case. I'm guessing the boot loop would disappear, if I could flash a new ROM, but I don't know how to put that on the device. Also, in case some of the problems are caused by version of TWRP that is installed, I would like to update that... but, again, I don't know how to get the new version on the device. I thought about entering APX mode, but holding Power and Vol+ simply turns my display black after a few seconds... no sounds, no beeps, nothing showing up on my desktop.
Any ideas? Pretty please?
Any help would be much appreciated.
Thanks in advance.