Hi,
I just spent 4 hours trying to unbrick my Prime, no success.
Here's how I got there....
I had an unlocked (using the official tool) Prime, under ICS. I wanted to upgrade to JB, Cyanogen mod 10, latest nightly. I read i had to upgrade to the 10/13/2012 build to upgrade the bootloader then use the latest nightly build.
So i did. CWM 5.8.2.0 was installed, i rebooted in recovery (power + vol down), did a backup. Another reboot the copy the backup on my external sd card and every zip file i needed (10/13/2012 build, latest nightly build and google tools zip files) to the root of internal "sd card".
Another reboot in recovery mode, erase everything. The install from zip, select the 10/13/2012 zip file.
Ok it's working. Reboot, everything seems fine. I wait like 20 minutes (i read that i should wait the first time boot...).
Then i reboot into CWM to install the latest nightly. I was surprised that CWM had been replaced by... well i don't really know what but it seemed to be able to do the same things.
So i installed the latest nightly... Everything seems fine, reboot.... And it's bricked !
My prime is now stuck on the Asus logo. I can't even turn it off. When i try, it just reboot itself (skynet ? xD)
I tried going into CWM (power + vol down). No luck.
Then i tried power + vol up, oops what's that ? APX ? After a few search, i found out there was a tool (nvflash), that might be able to help me.
I installed the APX drivers, all good. But..... I need the blob.bin from my device.... Silly me, i didn't make one when it was working.... In my defense, i didn't know about that blob.bin before.
So there i am, my Prime totally locked at the Asus logo, can't go in the CWM menu, can't fastboot... Only APX without the blob.bin....
Is there anything i can do to save it ? Or should i just take my best shot at the tablet throwing contest ?
Thank you in advance
EnderEOC said:
Hi,
I just spent 4 hours trying to unbrick my Prime, no success.
Here's how I got there....
I had an unlocked (using the official tool) Prime, under ICS. I wanted to upgrade to JB, Cyanogen mod 10, latest nightly. I read i had to upgrade to the 10/13/2012 build to upgrade the bootloader then use the latest nightly build.
So i did. CWM 5.8.2.0 was installed, i rebooted in recovery (power + vol down), did a backup. Another reboot the copy the backup on my external sd card and every zip file i needed (10/13/2012 build, latest nightly build and google tools zip files) to the root of internal "sd card".
Another reboot in recovery mode, erase everything. The install from zip, select the 10/13/2012 zip file.
Ok it's working. Reboot, everything seems fine. I wait like 20 minutes (i read that i should wait the first time boot...).
Then i reboot into CWM to install the latest nightly. I was surprised that CWM had been replaced by... well i don't really know what but it seemed to be able to do the same things.
So i installed the latest nightly... Everything seems fine, reboot.... And it's bricked !
My prime is now stuck on the Asus logo. I can't even turn it off. When i try, it just reboot itself (skynet ? xD)
I tried going into CWM (power + vol down). No luck.
Then i tried power + vol up, oops what's that ? APX ? After a few search, i found out there was a tool (nvflash), that might be able to help me.
I installed the APX drivers, all good. But..... I need the blob.bin from my device.... Silly me, i didn't make one when it was working.... In my defense, i didn't know about that blob.bin before.
So there i am, my Prime totally locked at the Asus logo, can't go in the CWM menu, can't fastboot... Only APX without the blob.bin....
Is there anything i can do to save it ? Or should i just take my best shot at the tablet throwing contest ?
Thank you in advance
Click to expand...
Click to collapse
What are you doing to make you think you can't get into fasboot?
Sent from my LG-SU760 using xda premium
I had this exact same thing happen to me and I don't have good news.
I spent several days pulling my hair out and the final conclusion I came to was that if I couldn't connect using APX I couldn't reload the boot loader and I had painted myself into a corner. I also didn't have my blob file.
I ended up sending it to ASUS, had no warranty because I had unlocked it.
They charged my $240 to replace the motherboard and camera, which had gone green screen last summer.
Now that I have it back everything works great except now when I connect the dock the tablet doesn't recognize the keyboard at all. It charges through the dock and sees the SD card slot.
I also have a bluetooth keyboard I like.
I really don't want to send it back.
Sent from my Transformer Prime TF201 using Tapatalk HD
Since i can't access the recovery menu, i can't select fastboot or anything else :/
Too bad we can't use a generic blob.bin just to install a new bootloader in APX mode.
Related
First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
Can you still boot into your main ROM or not? IF so, just reinstall recovery - Clockwork Mod 0.8 works, I don't know about later versions or ROM Manager, I don't trust them, based on what I see on the forums.
If you can't boot into recovery OR boot normally, then you have to use APX mode and nvflash to reflash your G Tablet. That completely wipes and rewrites everything on the tablet.
EDIT: If indeed it sounds like clockwork isn't installed and stock recovery is still working, see the instructions in the next post to install clockwork mod 0.8. No need to resort to nvflash.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
You could become a professional gadget breaker with all the broken stuff you have
Clockwork never got installed if you are seeing the ! and then it reboots. I would not fool with rom manager, or any of the other stuff. Your tablet is NOT a Vega. The vega rom is used as a base to build stuff for the G tablet but it is not the same.
Get clockwork installed. You need to find Clockwork.8 ... You will have an update.zip file, and a recovery folder with a command file inside it. You can install it from the internal sdcard, or an external. You just need to look at the command file with a text editor like notepad and see if it lists sdcard, or sdcard2. If you want to install from internal, sdcard.. From external, sdcard2. The command file does not have an extension. If you do not have one in your clockwork package then download one of the other roms. Most of them will have it. Or even the stock rom package. They are all the same.
Go to SDX and we'll help you with the Intercept. Follow the info hear and the G will be rockin.
webosb said:
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
Click to expand...
Click to collapse
I'm pretty sure I wrote that... I don't care that your reposting it...just link where you got it from next time.
Anywho, keep in mind that it's nearly impossible to completely brick these things. Follow this guide, step by step, from start to finish. You will need a microSD card with a way to get files onto it (microSD slot on computer/SD slot with microSD -> SD adapter)
http://forum.xda-developers.com/showthread.php?t=865245
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
If you really have managed to mess up recovery.. You can use Nvflash to get all the way back to stock. Just use caution.. The only 2 tablets I know of that may have actually been completely bricked have been from folks that ran the incorrect batch file in Nvflash... It is really simple to use though... Guide is here...
http://forum.xda-developers.com/showthread.php?t=861950&highlight=nvflash
scsione889 said:
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
Click to expand...
Click to collapse
Yeah, I got it to recognize it, I didn't take recovery and update.zip out of the cwrecovery folder so it didn't work before. I just got it to "unpackage" for a second. but the same boot cycle happened.
I have to run out now for a bit, I'll try the flash later. Thanks for the help so far.
As mentioned before you need a microSD to put the CM recovery on. It also needs to be the .8version of clockwork. AndroidPolice is alright but you really should stick to the xda forums for this kinda thing. It only took me 5 mins to flash clockwork and get the VEGAn build up and running. I wish you the best of luck with your tab. It really is a nifty device....once you're running a custom ROM lol.
Edit: you can hard reset...unfortunately viewsonic failed to make a hole in the case to be able to reach it
Sent from my VEGAn G-Tab
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
Happy New Year! I hope!
Hello,
I flashed my GTab with TNT Lite a while back, but I was going to switch to Vegan. When I try to go into recovery mode, I get the message in the corner "Recovery Key Detected" but it won't go into CWM. I've got the update.zip and Recovery folder (with command file) in the root of my sdcard. I opened the command file to check the file path, and it's to the internal sdcard, not sdcard2. I even put those files on sdcard2 just in case, but still no go.
Any ideas? CWM 0.8 worked like a charm the first time around when I flashed to TNT Lite 4.2.1, but I just can't get into recovery anymore. I redownloaded it, and erased and put new versions of the update.zip and recovery folder on the sdcard (when the existing ones didn't work), just in case, but still no go.
I can still boot into my ROM, so I also tried "Reboot into recovery mode" from CWM inside the app, but it reboots to the Viewsonic splash screen and hangs there.
Any help would really be appreciated.
Hey, so I ran into the same problem as the first post (with the recycling boot screens). I flashed TNT-Lite onto it, and it worked for a few hours before the problem happened. I NVFlashed it, and at the very least I know the recovery screen is different than after I flashed it, but the yield sign only lasts a few seconds and then the problem persists.
Does NVFlash actually unroot? If so, can I return this to viewsonic and get a replacement? If not, am I screwed?
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
To NVFlash using windows 7 shouldn't be a problem I actually used it today and I'm running windows 7 home edition maybe you need to update your PC and try a linux live CD to run linux on a PC it has more drivers available for equipment and saves someone who doesn't understand linux alot of headache as it uses the CD as your hard disk and it sets it self up just make your system boot from the CD first.
Sent from my Bottle of Smoke using XDA Premium App
TimmSpinn said:
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
Click to expand...
Click to collapse
Really it depends on your boot loader branch and its good practice to ensure that everything installs as the Rom develoer intends.
Sent from my Bottle of Smoke using XDA Premium App
While I was checking my emails i rediscovered this thread... lol
I'm a linux user, I got ubuntu 10.10 on my laptop running, again, months ago.
But now I don't touch it and use my tablet or phone 98% of the time. (this is 2% other on an XP desktop)
I also share the same recovery mode issues, but after reading the rest of this topic, I think I might feel adventurous enough to try that honeycomb... >.>
stuck cant get into cwm and is stuck on the tapntap logo
after i nvflash the tablet it wont boot. it gets stuck on the tapntap logo after a few seconds it turns the screen black. and even cant get into cwn it just get stuck on the view sonic logo. i need help
I followed this guide http://forum.xda-developers.com/showthread.php?t=861950 (Roebeet's post) which brought me back to stock.
However, when I apply the 1.1-3588 the tablet shuts off and is unable to be turned back on. The only way to turn it back on is to run the nvflash_gtablet batch file. At which point a receive a notice saying 'The update to version 1.1-3588' was not successful. Please try again or contact customer support.'
Why is the tablet unresponsive after the failed update? Why must I NVFlash to reactivate the screen?
I searched through the forums for the past hour and although I found similar problems I have yet to run into my exact one. I am hoping to find some help.
Edit*
I have the same problem as another user which can be found here http://forum.xda-developers.com/showthread.php?t=903684
I can NVFlash the stock image (or even the NVFlash of TnT-lite 1.02) and the tablet will boot after the flash and function. Power it off (or do something that requires a reboot) and the tablet will no longer function. No power on (that I can tell), can't boot to recovery......and if I plug the tablet in to the PC I can NVFlash it and it boots. It's like it's stuck in APX mode now. I just have to plug it in to the PC, no Power + Volume- combo.....just plug the USB in and run NVFlash. It boots (to whatever I flashed) and will run until I power it off or try to reboot.
Getting APX mode to function is not a problem......so I can NVFlash it but what I've tried so far has not worked (it doesn't delete the data partition, etc..as I reflash and it's right where it was before I turned it off).
Click to expand...
Click to collapse
The fix posted by acidburn89 was unsuccessful for me
Citi,
I'm not sure exactly what you are doing, but if you are getting the message
you described, that sounds more like you are booting in recovery or a regular
boot and not APX (Power/Volume - to be the white, the black APX NVFlash screen).
My suggestion is to do the stock recovery NVFlash Procedure again. Check
everything step by step to make sure the right files are there and the right
things done.
See if you can complete that and get back to a working bekit 1105 (Stock
Version 2638).
If you can do that, go into Settings/Display and set it so the display does not
turn off).
THEN, if it offers you the OTA Update, let it run.
If it is unsuccessful again, post back here and I will see if I can find the file
and instructions to load 3588 manually.
Hope this helps,
Rev
Ok so I reread Roebeets NVFlash post and double checked my files. All of them are there and in the correct location. I set up my USB drivers, booted into APX mode and ran the nvflash_gtablet.bat
Then the tablet loads properly into the stock TNT 2638. After setting up my WiFi I get a notification that the 3588 update is available. I download the update and after it ask me if I would like to apply now or later. I have tried both options however both seem to fail.
At this point if I hit apply now it shuts down the tablet however it does not turn on. The only way to turn it on is using nvflash_gtablet.bat file. Which it then boots up properly (and it is not wiped, it's as if it is jut turning on normally)and I either get one of two errors.
'The update to version 1.1-3588' was not successful. Please try again or contact customer support.'
or
'The update process cannot proceed due to an unrecoverable error. More information about the error is below, 'Verify checksum: file was not found. Downloaded file does not exist.null'
Hope this helps, I am not new to rooting/flashing roms but this is a completely new error to me.
Citi,
Did you do what I said about setting the display not to go off?
I tell people to do that because I have heard that it can
interrupt the download.
Whatever is happening, it seems like the download is not happening
or not finishing.
You can go to the Developer Forum (or there may be one in General)
and find the thread that tells where to download the .zip version of
the OTA 3588 download.
Then go down to end of the top 4349 thread in General and I wrote a post there for a
guy on how to install an update from the .zip file.
Rev
Yup I set the display to never turn off. However, it seems as if I have this problem http://forum.xda-developers.com/showthread.php?t=999832
I am currently working on this method
Edit* Well I figured out the exact problem however the link I posted was unable to solve it
Another thread on my problem, and the fix found to work for others has not worked for me,
http://forum.xda-developers.com/showthread.php?t=903684
Just bumping this as it is still relevant and it seems to be a unique issue, as all past solutions have yet to fix this problem. I spent the whole day on IRC and have seemed to stump a few people. Looks like I may have the first fully bricked tablet
Have you tried re-partitioning?
Can't get into CWM to do so, stuck in an infinite APX mode and I can only turn the power on via an NVFlash
Citi said:
Can't get into CWM to do so, stuck in an infinite APX mode and I can only turn the power on via an NVFlash
Click to expand...
Click to collapse
get the recovery.img from from cwm .8 zip file and then use nvFlash to load that.
nvflash --bl bootloader.bin --download 9 recovery.img
(make sure you put the recovery.img in you nvFlash folder and then issue the command above. That will install cwm .8)
from what you wrote above it seems like you are getting stuck in apx mode when you reboot. So my question is what files did you download to setup your nvFlash????
I will attempt to load CWM using NVFlash, and I followed this guide EXACTLY http://forum.xda-developers.com/showthread.php?t=861950 for NVFlash for windows
Citi said:
I will attempt to load CWM using NVFlash, and I followed this guide EXACTLY http://forum.xda-developers.com/showthread.php?t=861950 for NVFlash for windows
Click to expand...
Click to collapse
which files did you download from his dropbox????? I am more interested in knowing if you used nvflash_gtablet_2010110500.zip or nvflash_gtablet_46_2010112600.zip????
I initially used that nvflash_gtablet_2010110500.zip and had the same problem as you few weeks ago. So I tried using nvflash_gtablet_46_2010112600.zip and that worked a lot better for me .
hope that helps...let me know if you stuck anywhere.
enjoy
Unfortunately I tried out both with the same result
So the problem has changed from not being able to load an update to being in an APX loop? If I understand your original post correctly you were indeed able to nvflash back to original stock and boot normally. Then it failed when you tried to do the update to 3588. If you can still do that...
1) nvflash to bekit's 1105 stock
2) do not install the update
3) clear cache and data with Method I from: http://forum.xda-developers.com/showthread.php?t=1030915 - If this fails due to not being able to enter recovery then your nvflash was no good. You'll need to verify that you have the correct drivers installed, you're using the correct version of nvflash and that your image is sound. Easiest way to do that is to download them again.
4) install ClockworkMod .8 using MicroSD card method.
5) Re-partition 2048 and 0
Were there any error messages in the output of your latest nvflash attempts?
I posted on how you can get cwm .8 installed on your tablet if you are stuck in apx mode. There are also other threads that are pinned under the development section that explain how you can get cwm .8 using nvFlash. You will need that to get out of the apx loop that you are stuck in.
The problem is found here http://forum.xda-developers.com/showthread.php?t=903684
I can NVFlash the stock image (or even the NVFlash of TnT-lite 1.02) and the tablet will boot after the flash and function. Power it off (or do something that requires a reboot) and the tablet will no longer function. No power on (that I can tell), can't boot to recovery......and if I plug the tablet in to the PC I can NVFlash it and it boots. It's like it's stuck in APX mode now. I just have to plug it in to the PC, no Power + Volume- combo.....just plug the USB in and run NVFlash. It boots (to whatever I flashed) and will run until I power it off or try to reboot.
Getting APX mode to function is not a problem......so I can NVFlash it but what I've tried so far has not worked (it doesn't delete the data partition, etc..as I reflash and it's right where it was before I turned it off).
Click to expand...
Click to collapse
And I attempted to install CWM using the NVFlash method with no success. It seemed to install however when I booted the system back up (using the batch file) I saw the "Android" screen and then the tablet went black, no green CWM menu appeared or anything
rbansal2 said:
I posted on how you can get cwm .8 installed on your tablet if you are stuck in apx mode. There are also other threads that are pinned under the development section that explain how you can get cwm .8 using nvFlash. You will need that to get out of the apx loop that you are stuck in.
Click to expand...
Click to collapse
Citi said:
The problem is found here http://forum.xda-developers.com/showthread.php?t=903684
And I attempted to install CWM using the NVFlash method with no success. It seemed to install however when I booted the system back up (using the batch file) I saw the "Android" screen and then the tablet went black, no green CWM menu appeared or anything
Click to expand...
Click to collapse
If the screen is blank then connect it to your computer and see if your tablet is in APX mode. You will probably hear the usb connect sound and you can go in device manager to see if it is connected. Let me know and then we can go from there
Yes it has been in a permanent APX mode since my original NVFlash, with the only way to turn the tablet on is to use the nvflash_gtablet.bat file. This will bring the tablet to TnT however my data has not wiped since my original NVFlash and the Wifi and other information is still present. It prompts me to download the new update however there is no need since once the tablet shuts down it will go to APX mode, with a rinse repeat of the cycle and I use .bat file to turn the tablet on.
ok try this...not sure if it will work but its worth a try
1. replace part9.img with the recovery.img ( i m sure u have done this already. this is so cwm .8 gets installed when you do a full nvFlash)
2. when you boot on for the first time.. press the power & + so you go in cwm .8.
let me know if you access cwm .8 if you do this ....we'll move forward from there
Failed first time I did it, but I just tried again and what do you know...success, unsure why.
Currently sitting in CWM looking at that beautiful green screen. I am in the IRC room if we could continue there that would probably work better and faster.
ya i m still at work and cant get on irc here :/...but if you are in cwm .8 then first thing i would do is wipe data then clear cache and then clear dalvik...then go under mounts menu and mount all the partiontions and then format all the partitions...once you are done with that i would mount your tablet so you can see is as a mass storage device on your computer and upload stock frimware 3588 on there...
use this link http://forum.xda-developers.com/showthread.php?t=861950 and go down to post nvflash and get the 3588.zip
from the 3588.zip get the update.zip and copy that to your tablet...once u have that go to the main menu of cwm .8 and choose the option to install update.zip form sdcard...i thikn thats the second one down
try that and see if it works...if not then i'll on irc in the evening today and i'll help you out ...dont stress we'll get your tablet up and running again
i have a gtab and it is giving me a headache already trying to figure out how to fix it. I have search high andd low for a solution but havent quite found one, yet.
This is my brother-in-laws gtab. For some reason he tried to flash to a different rom and update the tablet. Right now, the tablet won't boot. It gets stuck on the 3 bird screen. If i try to go into recovery, i still get the 3 birds with the "detected a recovery key pressed."
What i have done...well since i can get into apx mode, the first thing i did was flash nvflash 1.1, that should clear things up, then i pushed recovery. But that didn't work, i am still at the same place i started. So i flashed nvflash 1.2, still didn't work. I re-downloaded the files again from different sources and tried it again, and again, and again. I have tried it atleast 6 times but all with the same outcome. I am still stuck at the 3 birds. I tried holding the + while in nvflash to boot into recovery but that didn't work either. I am fresh out of ideas. Everything i read tells me to wipe cache/data, but i can't even get into CW. And nvflash isn't working for me either.
I am still on the same screen, this darn gtab is giving me the bird three times over. so right now i am going to allow the battery to drain then try again. unless anyone can suggest anything that will give me some hope....or even to tell me that i have bricked the "unbrickable."
oh and everytime i do the nvflash the device does not reboot itself...it stays stuck on the "entering nvflash recovery mode / nv3p server"
I had a similar issue with my gtab except I keptrebooting into apx mode. I then downloaded some nvflash from roebert that said deprecated not use (in a dropbox) and flashed that, my gtab came back to life there... funny thing is that I'm pretty sure I ended up on 1.0, luckily I was able to flash came from that and it's all been good from there.
I would say give that a try, then again I'm relatively proud to say I'm a n00b at Modding these things so tread carefully.
PS : as unbrickable as the gtab might or might not be it can (and to me it is) quite frustrating ; so I feel your pain
rantsh said:
I had a similar issue with my gtab except I keptrebooting into apx mode. I then downloaded some nvflash from roebert that said deprecated not use (in a dropbox) and flashed that, my gtab came back to life there... funny thing is that I'm pretty sure I ended up on 1.0, luckily I was able to flash came from that and it's all been good from there.
I would say give that a try, then again I'm relatively proud to say I'm a n00b at Modding these things so tread carefully.
PS : as unbrickable as the gtab might or might not be it can (and to me it is) quite frustrating ; so I feel your pain
Click to expand...
Click to collapse
yeah i tried it...i wish it was that easy..but it didn't work..it still didn't do a reboot after nvflash, and when i powered it off i didn't get anything...
butwhydoitalk2u said:
i have a gtab and it is giving me a headache already trying to figure out how to fix it. I have search high andd low for a solution but havent quite found one, yet.
This is my brother-in-laws gtab. For some reason he tried to flash to a different rom and update the tablet. Right now, the tablet won't boot. It gets stuck on the 3 bird screen. If i try to go into recovery, i still get the 3 birds with the "detected a recovery key pressed."
What i have done...well since i can get into apx mode, the first thing i did was flash nvflash 1.1, that should clear things up, then i pushed recovery. But that didn't work, i am still at the same place i started. So i flashed nvflash 1.2, still didn't work. I re-downloaded the files again from different sources and tried it again, and again, and again. I have tried it atleast 6 times but all with the same outcome. I am still stuck at the 3 birds. I tried holding the + while in nvflash to boot into recovery but that didn't work either. I am fresh out of ideas. Everything i read tells me to wipe cache/data, but i can't even get into CW. And nvflash isn't working for me either.
I am still on the same screen, this darn gtab is giving me the bird three times over. so right now i am going to allow the battery to drain then try again. unless anyone can suggest anything that will give me some hope....or even to tell me that i have bricked the "unbrickable."
oh and everytime i do the nvflash the device does not reboot itself...it stays stuck on the "entering nvflash recovery mode / nv3p server"
Click to expand...
Click to collapse
www.viewsonic-gtablet-for-dummies.webs.com/
You're a code red. You've been missing a very important step. Please follow instructions precisely.
goodintentions said:
www.viewsonic-gtablet-for-dummies.webs.com/
You're a code red. You've been missing a very important step. Please follow instructions precisely.
Click to expand...
Click to collapse
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. either way, after i flash nvflash the tablet does not reboot it stays at the nv3p server screen. If i turn it off and back on again the birds come out again. i have even held to the volume + during nvflash and it shows the nv3p server, detect a recovery key pressed, and booting recovery kernel, but no go...it's just stuck...i can turn it on and off, i can get it in and out of apx but it will not reboot after nvflash or boot up a rom or clockwork recovery.
btw, i do have my own tablet as well and i ran nvflash on it just for giggles, and it works as it is suppose to. After it flashes it boots up to tap n
butwhydoitalk2u said:
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. either way, after i flash nvflash the tablet does not reboot it stays at the nv3p server screen. If i turn it off and back on again the birds come out again. i have even held to the volume + during nvflash and it shows the nv3p server, detect a recovery key pressed, and booting recovery kernel, but no go...it's just stuck...i can turn it on and off, i can get it in and out of apx but it will not reboot after nvflash or boot up a rom or clockwork recovery.
btw, i do have my own tablet as well and i ran nvflash on it just for giggles, and it works as it is suppose to. After it flashes it boots up to tap n
Click to expand...
Click to collapse
Try code detox, you need a pc/laptop and load the proper driver, run the bat file from the directory. This mode completely reload all the petitions and usually fixes the issue. I think your boot petition is toasted.
Good luck.
tsukaza said:
Try code detox, you need a pc/laptop and load the proper driver, run the bat file from the directory. This mode completely reload all the petitions and usually fixes the issue. I think your boot petition is toasted.
Good luck.
Click to expand...
Click to collapse
This is not normal...
I did the detox and i DID get the "magic value mismatch" in the apx mode. But then i loaded the nvflash it is still in the same state as it was before...not loading recovery, booting, i can only get into apx mode...this is really weird..
I did the detox with both nvflash, 1.1 & 1.2, with and without Clockwork, but none worked. I can do the nvflash "format" and i still get the mismatch message but redoing the nvflash to get the tap n tap stock image or heck even not seeing the darn birds it won't do...
I have even taken it apart, let the battery run out, pulled the battery, pressed the reset button...but nothing!
I can't push anything in adb since i can't boot or get into clockwork...i think the tablet is offically bricked...i have ran out of ideas and have read many...i
butwhydoitalk2u said:
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. . .
Click to expand...
Click to collapse
Give this one a try and let us know if it helps.
Dave,
mydave1 said:
Give this one a try and let us know if it helps.
Dave,
Click to expand...
Click to collapse
I just tried ... and no cigar... i can go all the way to step 2.1 but it won't boot to recovery...it stays at the apx "entering nvflash...recovery key detected...booting recovery..."
to me it seems like it is not retaining any of the info that i am pushing onto it...like a "bios" is being reset and not remembering what to do...
A new error message.
Sent from my PC36100 using Tapatalk
Edit: i reflashed nvflash 1.2 and got rid of the error message...but i am back at square one...but taking a look at the error and from what i am seeing the tab is not finding the kernel image to start recovery. but why?
Cannot get NVFlash to "take"
butwhydoitalk2u said:
A new error message.
Sent from my PC36100 using Tapatalk
Edit: i reflashed nvflash 1.2 and got rid of the error message...but i am back at square one...but taking a look at the error and from what i am seeing the tab is not finding the kernel image to start recovery. but why?
Click to expand...
Click to collapse
Did you (or anyone else) discover the "secret" here? What did you do?
Unfortunately, I am now experiencing EXACTLY the same issues. My processes have fixed tons of GTabs that people thought were bricked. I *THOUGHT* that there was no way to HARD-brick the device but I may have been wrong!
I really need some help here. Anyone have an answer?
You could install a copy of Ubuntu and try nvflash with that. That would eliminate any possible driver issues since Ubuntu does not require drivers for apx mode. From the error you posted earlier "entering nvflash recovery mode / nv3p server" it would appear nvflash is not actually flashing anything.
Sent from my Nexus S using XDA App
NVFlash does not "take"
the3dman said:
You could install a copy of Ubuntu and try nvflash with that. That would eliminate any possible driver issues since Ubuntu does not require drivers for apx mode. From the error you posted earlier "entering nvflash recovery mode / nv3p server" it would appear nvflash is not actually flashing anything.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thanks for the comment. I agree about Ubuntu. I use it exclusively - have for a couple years. I did all my testing and attempts with it. I finally decided to build a WinXP machine and I am now trying to use it.
You are correct about NVFlash not saving anything to the device. There is no bootloader and although all of the NVFlash commands are "successful" it just does not save.
When I try to use the external SDCard to run recovery, the GTab does not seem to recognize it. It acts just as if there was not a recovery file on the card.
One thing that seems to give me some hope. I am seeing the USB connection (while not in APX mode) with the Windows Machine. So, I will install ADB and see if I can grab control that way. But ADB is such a bugger with Windows.
Since FuHu has removed the updates for the nabi2 ant otheres probably,i decided to give it a whir myself. I installed twrp 2.2.,went through some setting and in doping so somehow i have deleted the OD on the tablet. I searched and found the stock rom for the nabi2-nv7, put it on a sd card, put the sd card in, and wouldnt ya know it the version of twrp i had wouldnt read the card. I downloaded vers 2.8 and installed it, everything seeemed to be ok untill i went to slid the button to install, it wouldnt move. I rebooted, then went back into twrp once more with hopes, no deal, slider stil wouldnt work. After doing more reading I downloaded twrp 2.6 and that one was supposed to work, installed it, nowi have next to nothing. Without being plugged in to power, i can get to this screen,but anything i select will no work. Now if i plug the tablet into power, it automaticall goes into screen #2 still with no being ablee to get into anything.
Screen#1
boot normally
fastboot protocol
recovery kernal
forced recovery
Screen #2
bootloader
continue
reboot-bootloader
reboot
power off
It just keep fliping back and forth betwen thos 2 screens,it shows connected on my laptop,but try to do anything ( adb devices ) and it says no device connected..
Im thinking that the twrp's are working against one another and has meloced out in some way or another, is there any way i can wipe it all clean and start from scratch?
Any and all help is appreciated. also read wher xda has a toolkit for the nabi2, searched but not really sure what im looking for.
Thank you
Rascle