Hi,
Ok so I have a g-tablet that I got stock/retail box. I flashed it with VeganTab 7 RC1 Stable (The latest one) and it was working fine for a few weeks. I wanted to give it away as a present so I decided to go into the settings and "Restore Factory/ Completely wipe data" in Gingerbread and delete all data because I didnt want the new owner to have my google login and stuff.
After this, the tablet rebooted and was since STUCK on the VeganTab booting animation. I tried everything... I reflashed it with CWM ... nothing
I tried using nvFlash to just put the damn thing into Factory defaults (the viewsonic interface) and after nvFlash I just get a Viesonic/Gtablet splash screen boot loop. I cant seem to get this device to work.
Is this a expensive paperwight now???
SOLUTION IS HERE: http://forum.xda-developers.com/showthread.php?t=932157
Found it myself,
Sorry for the thread lol but it may help people who have identical problem.
I NEED looping help
lambergino said:
Hi,
Ok so I have a g-tablet that I got stock/retail box. I flashed it with VeganTab 7 RC1 Stable (The latest one) and it was working fine for a few weeks. I wanted to give it away as a present so I decided to go into the settings and "Restore Factory/ Completely wipe data" in Gingerbread and delete all data because I didnt want the new owner to have my google login and stuff.
After this, the tablet rebooted and was since STUCK on the VeganTab booting animation. I tried everything... I reflashed it with CWM ... nothing
I tried using nvFlash to just put the damn thing into Factory defaults (the viewsonic interface) and after nvFlash I just get a Viesonic/Gtablet splash screen boot loop. I cant seem to get this device to work.
Is this a expensive paperwight now???
Click to expand...
Click to collapse
I cannot get out of this same loop. I am so confused as to what to do. I have nvflashed and it just keeps looping.
Can someone please help me? I am begging.
My site start here code red. Look at signature.
Are you doing a factory rest after nvflash? I think it is impossible to hard brick....or near it anyway
Sent from my HERO200 using Tapatalk
Can't get CWM to even install
goodintentions said:
My site start here code red. Look at signature.
Click to expand...
Click to collapse
I've followed all the instructions for installing CWM to a T but the the boot recover kernal image won't do anything. It just sits there and won't load CWM from the microSD card. Does the card need to have some sort of special formatting (FAT, FAT32, NTFS) to be recognized?
My Vewsonic G-Tablet is just stuck in the boot loop with the birds screen and then the G-tablet initialization screen and then it reboots.
Gary
Update: Hallelujah, we have seen the birds!
Just for future reference to those of you who may be stuck in an "APX loop", where NVFlashing and even repartioning do not work for you. I tried many things, and only one thing worked.
Didn't work:
1) NVFlashing to anything
2) Repartioning or wiping
3) Wiping out all storage on the SD card
After doing many, many rinse and repeats on the above, the only thing that did work were these instructions:
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Click to expand...
Click to collapse
Now, I don't know of too many cases like mine where APX was the only thing that was working and that no amount of CWM or NVFlashing could bring back whatever was wrong with the bootloader, but this method forced a recovery image restore and got me back to the point where I can now power down and reboot. And for that, I thank this fine community!
I think we need a better guide somewhere on... Stages of recovery. If this doesn't work, here's the next deeper level. (Example: Level 1, wipe data/cache and reflash the rom. Level 2: Repartition and fix permissions. Level 3: NVFlash for 1.1 or 1.2 back to stock. Level 4: run the steps I have listed above. Level 5: fixing the bootloader. Level 6: Remove the case cover and short the back.)
Anyways, thanks again guys. Hopefully someone else will search with the same issue I had and get fixed as I have.
try this (not a developer here) when it boots up use your computer to delete all the files on the sd card so it looks blank- not sure if it will fix your issue but if there is a file on there messing your reboot into cwm that should will get rid of it. let me know how it goes. (standard at your own risk disclaimer) i have done this before just to see what would happen and nvflash brought it back up.
Hey, thanks for the reply. The sdcard was already blanked out through my various steps, so that doesn't appear to be the problem. Same things happen.
Now, that's just the app data and such on the sdcard, so I am guessing if I was able to see/delete all the system files instead via USB and delete it that way, I'd see something else.
just to bee clear i would delete everything on there not just the system files- so when you go to the drive from your computer it shows nothing at all.
here are the steps i would take start to finish.
1 nvflash rom
2 connect to computer, mount usb, then highlight and delete all files on gtab.
3 nv flash again (preferably with a stock rom with cmw pre loaded
4 reboot and pray that this fixed it.
OP - What size is the nvflash file you are using? I have run into a similar issue before with the larger nvflash.exe (like 152kb). It should be 140KB.
Just something else to check.
So to clarify, when you nvflash the 3588 stock image, it will automatically reboot at the end of the nvflash_gtablet.bat batch file?
pugsby said:
Hey all. Little frustrated since I've tried most of the tricks and still have a soft-bricked device. Not sure how it happened originally, but one way or another, I have a bad bootloader and no access to CWM.
APX works. I can NVFlash 1.1 or 1.2-based Stock or otherwise roms, and they boot (once, and only once...) . I can get USB mount. I've tried them with and without CWM pre-installed and see no differences.
But as soon as I reboot or power off, it just returns to APX mode. It is only a black screen, however. No birds, no logo, no nothing. The only way to make it boot again is to NVFlash it again.
All the instructions say to enter CWM to re-partition or to wipe data. That's great, but I have no access to CWM. Pressing the buttons during bootup does nothing because the device never makes it that far through bootup. And the format utility doesn't wipe enough data to return this back to a truly blank device, because when I nvflash, my apps still show to be there and I want it back to a blank slate.
I've tried pressing the buttons directly after a NVFlash to enter CWM that way, but it just goes straight into the rom.
Others have suggested popping off the back of the case and grounding out things to reset that way, but I thought that was just if APX didn't work, but APX is the only thing that DOES work, so not sure if it applies. (Let me know if I'm wrong there)
More things to try?
Click to expand...
Click to collapse
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
After you repartition, wipe data, clear cache, etc. it might still loop into APX. If it does you'll need to force it to install a new bootloader. I'll dig up a link to the procedure if you need it.
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
K J Rad said:
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
Click to expand...
Click to collapse
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Acidburn find out a solution for this problem
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
K J Rad said:
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
Click to expand...
Click to collapse
This got me into CWM (Yay!). This, however, did not fix the APX looping (boo).
I repartitioned, wiped, nvflashed, wiped, repeat. Even though I have more options now with CWM, the end outcome is still the same that after the initial boot, it won't boot again.
BUT, I did find a working method. See the original post.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I was hoping you'd respond, goodintentions, as I used your NVFlash files and instructions this last time around from your very handy site.
I'm not sure exactly what happened. I do know that Rom manager was involved somehow, trying to use that integration with recovery. (I know, not recommended, but at first it acted like it would work).
Also, I think a 1.2 Rom was mistakenly flashed on top of a 1.1 bootloader somehow.
The details are fuzzy. It's been so many things since then that who knows..
goodintentions said:
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Click to expand...
Click to collapse
I am a tech. Been working with/on/in electronics and computers for roughly 35 years. I had a hard time believing the problem was real until I had one in my hands that was doing it. I've tried doing it to my own tablet but a simple nvflash always got me going again.
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
Click to expand...
Click to collapse
This is successful in some cases but not all. In some cases the bootloader has to be updated using factory stock recovery. ClockworkMod and nvflash don't update the bootloader (and I suspect some other system related partitions/information) properly. For those cases the fix is a little more complex. This process...
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
has worked on all but one of the tablets I've recovered. The odd one out required an extra reboot (though I was doing the steps from memory and on an unfamiliar computer so I could be mistaken). However... as noted above... a subsequent nvflash of even the same image resulted in another APX loop. The end result was I had to craft a custom nvflash for each of those machines to avoid the problem in the future. That may or may not be necessary for all cases but since it's relatively easy I just do it out of habit now.
Keep in mind that serious APX looping issues are very rare in the grand scheme of things. Many times folks get confused and fail to follow directions properly and think they have a bigger problem than they really do. The overwhelming majority of times a simple nvflash and repartitioning will fix these things right up.
Added: BTW, the best way I've found to avoid the APX loop issue entirely... do a data wipe before you flash a new ROM and then again immediately after and before you boot it for the first time. I know... one should be enough... but if you make it a habit to do two... then you'll probably remember to do at least one of them ;-)
Great info. I shall try not to enter another painful APX loop. I was shocked how many things I had to try and places I had to go before I found a working method. I guess I really did a number on this thing somehow. But I'm happy that it's back.
I didn't have to do the more painful one you mentioned, but honestly I was ready to try about anything short of slaying a dragon.
Hi i am writing this after i dont know how many threads i read, how many videos i saw especially after the noob video.
But all fail i need to ask the masterminds,
i was trying to back up the ROM and one of the guides stated to use nvflash for full recovery i tried to follow that but after shutting the tab down in recovery mode.
its not turning on at all, its not even getting detected to windows 7 or linux ubuntu.
i just bought this tab today and i badly need help
so please help.
i am sure i rooted the tablet.
but havent installed any roms on it.
thank you for any help
you're getting a bump because I am in a similar situation.
I had VeganGinger on my tab. Was tired of the market crashes and was going to NVFlash back to the original and *possibly* go to the Flshback Honeycomb.
However after following all the instructions for NVFlash my tab was stuck in the boot loading screen. I tried to power off and boot into Clockwork Recovery Mode based on the Gtab for dummies site. however it would not do that. So I also followed suggestions to flash again. This time it seemed that the bat that ran on my computer ran more stuff (great terminology I know - sorry). I figured, hey - maybe it was a bad install. but alas, it did the same thing.
Again, following Gtab for dummies, I tried their NVFlash file. Same deal. However here is where I hard bricked. stuck in the loop again. Can't leave it like that forever. So I powered down. Now it won't do anything. Nada - zilch - zero.
So now you know my whole sad saga.
So I now have a piece of worthless plastic?
I would GREATLY appreciate any help!
Oh - and darn if I wasn't worried about running out of battery while putting a new ROM on there, so the battery was finishing charging shortly before the brick.
I've tried to look for this problem and haven't found anything similar. If it's already been addressed please direct me to the previous thread, if this is in the wrong place please move it.
I rooted my Galaxy S II a while ago and it's been working great. I wanted to try Cyanogen mod 7 and so I followed the instructions on their website. Trying to use ROM manager gave me a weird error message telling me that there was an invalid signature or something, despite toggling everything and wiping the cache to turn it off. So I followed the "method via recovery" instructions. I did everything exactly as it is there, including the Google apps stuff, and it all seemed to work perfectly. Then I rebooted it hoping for it to boot into CM7, and instead, when it turns on it goes to the screen saying Samsung Galaxy S II with the yellow triangle underneath, and stays there. Every time it turn it on it goes to that screen and doesn't change. It's now been like that for half an hour. I can start it up into download mode, and I've tried flashing zImage to it again, but no change.
I have a NANDroid backup (it's backed up with CWM anyway), and I've copied the backup to my computer, but I have no idea how to apply it when the bloody thing won't turn on.
I'm using Linux with Heimdall (the cross-platform Odin clone).
Please help me. Unfortunately I have no internet in my flat so I won't be able to see any advice until tomorrow unless it;s given in the next ten minutes. God I really hope the thing's ok.
Hi
Do you have jigg? ( if you don't have it buy it from ebay or ask some friend of you )
With jigg you can enter download mode and then flash the stock rom.
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Sent from my Transformer TF101 using xda premium
TheGhost1233 said:
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Click to expand...
Click to collapse
I can't believe it was this simple, I knew power+vol-down+home got tme to downloading but I didn't know that got me into recovery. Everything's recovered now.
Thank you Dutch people!
I just got the Gtab (UPC300-2.2) but it fails to load anything.
It does not boot and gets stuck. I do not know the boot version of it or any versions of anything because I can't access it.
When I try to put it in recovery I only get the following 2 messages:
Recovery Key Detected
Booting recovery kernel image
Thats it. i took the SD out of it and same bit when I tried to access it I seen Update and recovery files and roms folder so looks like someone tried to mod it but failed.
Is there a way I can recover it to working state to ether restore it to factory or any recommended rom...
I kind of need instructions because I never messes with this type of issue yet, as in I haven't bricked a device to this state before.
I also need to find a charger for it. looks like connecting the USB does not charge the Gtab
Id prefer recovering it to FACTORY SOFTWARE.
Im just not sure where to get the Factory software and how to go about recovering it...
So far I found out that this unit possibly has Bootloader v1.2 but recovery that was loaded onto the device was for bootloader v1.1
I do know know what the previous owner tried to do to it but failed and screwed up the device. Im just trying to fix it back to working condition.
It does not matter if its factory rom or a modded rom, as long as its stable.
Also I read up I need NVflash or something like that to recover the units bootloader ignorer to get it to work.
Any help is welcome, and I thank you all in advance.
Well I did the stuff from one of the posts here using nvflash.
Nvflash —bl bootloader.bin —getpartitiontable p.txt
Returned the SOS partition to be 11
Then tried the:
Nvflash —bl bootloader.bin —download 11 recovery.img
Finished successfully but I still have the message while trying to enter recovery:
Recovery key detected
Booting recovery kernel image
Then just sits there with the birds background.
When I try to normally boot it it does boot but I can’t open settings or anything and I constantly get this error message:
The process Android.process.acore has stopped unexpectedly. Please try again with force close button.
It constantly pops up, like once every 3-5 sec.
when i got mine it was messed up too, sounds very similar. When I got to the Viewsonic birds logo I let it sit forever and i thought it was done for, but after sitting for literally hours it actually booted up and i've been using ever since. that was about 6 months ago. just find a charger for it, i cut the end off one with the wrong voltage and attached it to an adapter with the correct voltage and amperage. It says on the back of my device "dc 12V 2A" then get it to the birds logo and set it down. Go have a day at the park or let it sit overnight, go to work for a day, out for dinner. do something so you're not sitting there looking at it every five minutes. Good luck!
Would it be possible for anyone to provide me with either the files or operational links to the files needed to recover this device?
I've scoured this forum and found nothing but dead links to NVFlash and the like. Thanks in advance!
Seems like there are a few of us still rocking this piece of hardware, me included. I"m stuck in the same dilema and the links to all the restore files haven't been preserved. Is it best to just concede that the tablet is ancient history and go purchase a new one or are the nvflash files available somewhere on the web?