So i have used nvflash before and have ran into this issue before and eventually luck my way out of the problem but this time it aint happening. I am nv flashing the original nvflash_gtablet_2010110500 and it is successful but then it restarts and shows the gtable screen then when tapNtap shows up the screen starts to flash between the tapNtap logo and a black screen then eventually goes black. i flashed and reflashed 5-6 times and then tried the gtab 3588 apx and that didnt work and tried the first one and still no dice.
WHAT THE HELL!!!!
please someone help me .. i beg you!
After it goes black, have you tried holding down the "power" button to make sure it is off. Then restarting. Does anything happen.
Am I right that you are trying to get back to 2967 stock so you can do something else?
Rev
I figured it out and its really stupid. It was one line i didnt read. apperently NVflash DOES NOT format /data and well that was the issue. So i had to use NVflash and replace the recovery.img with the CWM.img and then boot into CWM, and wipe /data and then reflash 3588 via apx and it worked. stupid nv flash
You used nvlfash to fix a device. You didn't read the directions correctly and something went wrong. And you blame the program? Take a closer look at the user.
Agree with you, here people just jump to do advanced stuff to their tablets without reading and without knowing what the hell is a Rom and when things go wrong they blame any one besides themselves.
I nvflash my tablet, jumped from stock to vegan, tnt, and tnt 5 , flashing cwm, I don't remember how many times, and the only times I was in trouble was because I didn't read properly the warnings, but always I was able to fix it.
If you don't fully understand what you are doing, don't do it until you understand it.
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...
ok i know this has been mentioned already just not sure if those topics/posts apply to me.
before i did the below, i tried the tnt lite enhancement pack and had upgraded to 3588 from viewsonic, don't know if that mattered, but i reinstalled clockwork .8 afterword and started to flash zpad
was flashing zpad and zpad enhancement pack (though i don't think i needed to) and i flashed the mdpi tegra gapps now i have a borked tablet.
at first when i was trying to flash zpad and the enhancement pack it would restart with viewsonic logo and then it would just be blank black screen that was lit up so the screen was on. and it took atleast 5 seconds of holding power button to get it off, but it was still able to go into recovery.
so i figured something i was flashing was causing something to go wrong, so i just flashed zpad and the gapps no enhancement pack and it booted, read that pershoots kernel was best so i downloaded it from his site, maybe it was the wrong one, idk but after flashing that all that would happen is the screen would turn on to the viewsonic logo, did not recognize the command to enter recovery by holding volume button.
so i was like wth turned it off and literally touch the button for like 2 seconds and it would turn off. tried going into recovery no dice. wth do i do, i just passed the 30 day mark from sears. (i was gonna return it but after seeing honeycomb, hells no)
any advice???
Instructions if you have a brick.
http://forum.xda-developers.com/showpost.php?p=11230514&postcount=1
http://forum.xda-developers.com/showthread.php?t=861950
Try that before you take apart your machine.....It sounds like you flashed the zpad kernel for the zpad. That kernel is for the malata zpad not the zpad rom on the gtab. If you can get to apx mode then you can nvflash stock and start over.
Don't even have nvflash or how to use it.
Kinda lost....I downloaded pershoots kernel for zpab/gtab of his site.....
Sent from my PC36100 using Tapatalk
your gonna have to read that thread...it tells you how to get and flash nvflash
K thanks ill update later once I get a chance to try the fix
Sent from my PC36100 using Tapatalk
get on the irc channel at freenode.....#tegratab....someone there is usually around to walk you through it
Hehs never used irc
Sent from my PC36100 using Tapatalk
well crap i did the nvflash stuff and some last part or something failed and now it really is a brick
got back to stock now how do i get clockwork working? i have the right update.zip, but i get the android txt then a triangular sign with a ! any suggestions
thorpe24 said:
got back to stock now how do i get clockwork working? i have the right update.zip, but i get the android txt then a triangular sign with a ! any suggestions
Click to expand...
Click to collapse
Have you followed the instructions in the following thread? Sounds like you're missing the recovery folder, or did not extract the the clockwork.zip which would have an update.zip file and the recovery folder with command file. You need both on the sdcard for clockworkmod to install from stock recovery.
http://forum.xda-developers.com/showthread.php?t=865245
yeah realized that myself. well i finally got it working right except that now when i try to restore with titanium or download something from the market etc. the damn thing restarts.
would that be a kernel or rom probem, trying to run zpad. was on vegan 5.1 for forever but i need to play around with stuff to find what is the most stable and quick, i use it for work and now i can't it's really irritating.
what did you do to get back from the brick state? Nvflash ran for me, something at the end failed and now it looks like I have no APX mode because the tablet wont turn on at all. I have done apx and nvidia flash before so I think I know when the tablets turns on and goes into apx mode. My pc also tells me by attaching the device when I enter APX mode. So no APX mode, no turning on. Whats does the internal pushbutton really do? There is another post about touching/bridging two contact points together but no pictures. I think its talking about the place next to the interal pushbutton but I am not sure nor do I know which two contacts to bridge/short together. Is the second pushbutton location something like a flash recovery. I used my nvflash bat file and folder that I used before to do recovery so I am not sure why nvflash failed and screwed my tablet but this not looking good.
Any help recovering from this would be appreciated because this is not looking good. I am hoping its a dead battery so I am charging now and when I get back from work I will check again and then maybe take it apart.
nvflash crash, gtab is dead
charged the battery and still no apx mode, the gtab appears to be dead. nvflash errored out, and either rebooted this gtab or crashed it immediately but I have no signs of life and not sure what the disassembly can help with at this point.
I just joined the site, so it is NOT allowing me to post in any area that is directly related to what I need answered. I flashed to various versions of TnT, managed to brick my tab, and ran the NvFlash to get it back to stock, at which point it boots up, but I get a Force Close on pretty much everything, including "system" so I cannot even do a wipe or anything else. The problem is, once I reboot, it will not come back up, and just gives me a black screen, but if I hold down volume and power it will allow me to get back to the screen where I can run nvflash again, but for some reason, I cannot manage to get it to reboot in order to install any other rom. any assistance is greatly appreciated.
chanse said:
I just joined the site, so it is NOT allowing me to post in any area that is directly related to what I need answered. I flashed to various versions of TnT, managed to brick my tab, and ran the NvFlash to get it back to stock, at which point it boots up, but I get a Force Close on pretty much everything, including "system" so I cannot even do a wipe or anything else. The problem is, once I reboot, it will not come back up, and just gives me a black screen, but if I hold down volume and power it will allow me to get back to the screen where I can run nvflash again, but for some reason, I cannot manage to get it to reboot in order to install any other rom. any assistance is greatly appreciated.
Click to expand...
Click to collapse
You already have nvflash experience, so I would suggest this:
http://forum.xda-developers.com/showthread.php?t=974422
You erase, then do the regular nvflash again. If you need clockworkmod, here's a neat trick -- in the 1105 bekit image, take the bekit .8 recovery.img (which is clockworkmod) and then copy it over to your 1105 foider. Then, rename part9.img to something else and then recovery.img to part9.img. Then re-flash.
What that does is add cwm from the start. So after the nvflash, you can reboot right into recovery and wipe your user data.
Thanks for this, man (and the nine billion other things you and the collective devs do). I borked the tablet by attempting to do something that VeganGinger experimental didn't like. Not sure what, but even after an NVflash, it wasn't happy booting. Doing this enabled me to get clockwork on and wipe data, which in turn let me get it booting. Now to go back to TNTLite and stop playing with things labeled experimental.
Hey guys, so I rooted my gtab after I got it today (from woot), and went to flash CM7 (after rooting per http://forum.xda-developers.com/showthread.php?t=865245). On boot, it went to the ANDROID text screen, then went blank, and stayed there.
I then tried flashing g-harmony, as well as doing a full wipe. The same thing happened.
So I was getting a little weirded out. I then tried to do a full nvflash, using the G-tablet format then nvflash.
After the G-tablet format, there was some red text on the g-tab that said about some error with a magic file... not sure what that is.
I then booted up, and it got to the stock ROM, then it blue screened(?).
I did another nvflash, and this time after the g-tablet format, I got some red text about a critical error, but it booted up to the stock rom.
Now in the ROM, it shows no SD card, just 1.63GB internal memory...
I tried to root again, and it showed a triangle with a exclamation point in the middle. Now I cant mount the tablet to my PC at all..
What the heck is going on? How can I get it totally back to stock?
cardriverx said:
Hey guys, so I rooted my gtab after I got it today (from woot), and went to flash CM7 (after rooting per http://forum.xda-developers.com/showthread.php?t=865245). On boot, it went to the ANDROID text screen, then went blank, and stayed there.
I then tried flashing g-harmony, as well as doing a full wipe. The same thing happened.
So I was getting a little weirded out. I then tried to do a full nvflash, using the G-tablet format then nvflash.
After the G-tablet format, there was some red text on the g-tab that said about some error with a magic file... not sure what that is.
I then booted up, and it got to the stock ROM, then it blue screened(?).
I did another nvflash, and this time after the g-tablet format, I got some red text about a critical error, but it booted up to the stock rom.
Now in the ROM, it shows no SD card, just 1.63GB internal memory...
I tried to root again, and it showed a triangle with a exclamation point in the middle. Now I cant mount the tablet to my PC at all..
What the heck is going on? How can I get it totally back to stock?
Click to expand...
Click to collapse
Put it in the box and send it back stating defect. I read your statement and there's were so many foreign things going on I couldn't keep up. Wow sounds like it's beyond something you did or could do. The question is do you want to continue on? The longer you keep something that could of or well may have been defective before your rooting experiment the better chance of you eating the cost. Your decision. I wish you the best for remedy.
did you try the repartitioning fix.
absolutely no idea if it will make any difference but at this point can't help.
http://forum.xda-developers.com/showthread.php?t=896395
Nvflash doesn't wipe the bct so user junk might still affect. Check the partition tool above or the gtablet format tool in development before that. But honestly I got a bad tablet too. It was so prone to bootlooping. Just exchange it.
So I tried the G-Tablet format again, and got the error for the "magic values" again. I have no clue what that means.
I tried to install CM7 again, and it boots to the ANDROID text, then the little android flys by the screen, then it goes blank... nothing.
Ugh.. calling viewsonic now.
So I searched for "magic number"
Found this
http://forum.xda-developers.com/showthread.php?t=925504&highlight=magic+number
Hope that helps.
sleebus.jones said:
So I searched for "magic number"
Found this
http://forum.xda-developers.com/showthread.php?t=925504&highlight=magic+number
Hope that helps.
Click to expand...
Click to collapse
Magic Value Mismatch is likely caused by a corrupted zip download.
So when you flash that corrupted file it may complete succesfully but the end result isn't as good.
Sometimes even though the download may have comepleted it may still be corrupt.
What might help is downloading the zip file again from the source location and using that one instead of the original download.
Also, what may help (if you have access to recovery mode) is to flash
Calkulins Format all.zip file before you flash another rom.
This format all zip will wipe everything the standard Data & Cache wipe will not.
Thanks sleebus and tek, using the fix from that thread might help. But.. I ended up contacting Woot and they are going to do an exchange, no hassle. So Ill just get a fresh one.
When I get the new Gtab, ill re download everything and try rooting/ROM flashing again. Hopefully I won't have any problems with it!
Thanks guys, very helpful as always.
Um... what the heck happened, now whenever i try and turn on my gtab, it goes straight into clockworkmod saying that it is Booting recovery kernel image, when i am not holding down the power button and volume +!!!!!!!!!!! i am freaking out and really am in need of some guidance, please, i hope i didnt brick it... I wanted to see if i could get my battery stat to show 100% when it charged so i went into CWM and wiped battery stats... along with wiping the cache partition.... please... i hope i didnt brick it....
Sorry guys... just a little scared... what should i do, with a little more reading i realized its only partially bricked and that i should just NVFlash back to the stock rom, is this correct?
yes.........
I'm starting to get annoyed at people using "nvflash" as the answer to everything. I've soft bricked my device more than a few times and have managed to save the day without nvflash. And when I say soft brick, I mean everything from boot loop to not being able to boot beyond the birds screen to not being to go into cwm. In fact, I've dealt with all of these things without having to nvflash at all.
Wiping out the cache was your mistake. Have you tried reflashing a rom?
nvflash is a solid and relatively easy to use solution. I prefer to spend 20 minutes setting it up rather than 2 hours trying to figure out to un-brick without nvflash. I don't understand the nvflash haters at all. If you do regular backups in cwm then it's always easy to nvflash back to stock, load cwm, and restore a working backup.
Sounds like something that could be solved outside of nvflash, but if you've got backups and want to be done with the troubleshooting then just go for it.
Once properly set up, NVFlash is a simple as flashing a ROM. And it can be done regardless of bootloaders. This is the beauty of the G-Tablet.
I had recently used NVFlash to flash back to one of the stock images so i could flash BoS onto my tablet, so how should i attempt to recover from this? NVFlash? or another method, without NVFlash?
I guess go for nvflash. It is the easiest solution.