from the wiki page, attempting to nvflash the stock image. Problem is after downloading 3 different times, there is NO nvflash_gtablet.bat file in there. Am I missing something? am I doing something wrong here?
http://forum.xda-developers.com/showthread.php?t=861950
I'm not a Windows user, so I don't really know if the batch works myself. I am assuming that it does.
thank you roebeet, this will be the 2nd time today youve saved my newb a$$ if it works.
Awesome
I had to use CW and repartition, scrub cache and such but I am back to factory again, now to mod this turd..Thanks a ton Roebeet!
Glad to hear that you got it working!
I've run into an issue where my Gpad flashes properly, but after being flashed, it continually goes back into APX mode on power cycle. If I issue the command "nvflash --bl bootloader.bin --go", I can confirm this as it will reload the flash bootloader. I can re-run the script to reload the tablet and it will reload the partitions over and over again, but each time the Gpad is powered off, it returns to APX mode. Thoughts?
Problem solved... I had downloaded the _46 flash image. That apparently causes the tablet to into APX mode instead of working properly if you use it. Is that for the Gpad, or for some other product??
so i have been using vegan roms for about 3 months now and for some really unexplained cosmic reasoning i went and loaded the vanilla rom for the g tablet. Now all i get is gtablet splash screen it will cycle the spash screen for about 2 minutes then completely shut down. i tried to boot into cmod recovery but everytime i do it will see that i am trying to boot into it and then reboots without going into the cmod recovery at all. HELP i have no idea what to do as i am so lonely without my viewsonic g tablet.
Try using nvflash, worked for me over the weekend.
http://forum.xda-developers.com/showthread.php?t=861950
i have tried that but no avail it keeps saying when in the command prompt.
*:\Users\*&*&*&*\gtab>"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin
--configfile gtablet.cfg --create --go
Nvflash started
USB device not foundPress enter to continue:
when i depress enter it just closes the screen.
i am not able to get into the adx as well i have installed the USBdeview and installed the Android ADB Interface as the device in hopes for it to be reconigize.
Did you try this thread I think its the one that saved me after I borked the partitions:
http://forum.xda-developers.com/showthread.php?t=842000
I put the update on a SDCard.
lsl73 said:
i have tried that but no avail it keeps saying when in the command prompt.
*:\Users\*&*&*&*\gtab>"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin
--configfile gtablet.cfg --create --go
Nvflash started
USB device not foundPress enter to continue:
when i depress enter it just closes the screen.
i am not able to get into the adx as well i have installed the USBdeview and installed the Android ADB Interface as the device in hopes for it to be reconigize.
Click to expand...
Click to collapse
Did you boot the tablet while holding down both the + and - sides of the volume button? Did windows (I'm assuming a PC) come up and ask you to install the driver for ADX mode?
thanks for all the suggestions and help guys i AM finally able to do it. i just finish installing cwmod and vegan. man i promise i will never try to go back to stock ever again. thanks a lot fellas
lsl
First time rooting the tablet. Thoroughly read and understood all instructions and have had multiple android phone devices that I have rooted/soft bricked/unbricked/restored to original so ive been through the process.
adb working and got tablet into apx. performed every step in the pure root for tablets thread and everything went well.
ran root.bat, tablet says it updated successfully
ran cwm.bat for clockwork and it shows to update successfully
instructions say to restart tablet, done. Now it stays in apx mode and will not go into booting screen.
tried to use nvflash to restore since i have apx access. run it and it appears to complete on the computer but on the tablet it only shows that i got into nvflash recovery and the chip uid. It never shows if it is successful.
Is there anything else I can do from while in APX? restarting the tab immediately dumps me back into apx even if i dont hold the up button.
Thanks for the help
puma
Did you try holding the power button down for 10-20 seconds?
If you are using the pure root method, you can use nvflash --resume --go to kick start the bootloader. You might have to add ./ or \ and .exe.
I managed to fix it after looking over everything.
the recovery nvflash would exit faster than i could read if there were any errors so i changed the batch file to incorporate /k
(edit your batch file and before the 'nvflash.exe' command put in 'cmd /k' include the space and add a space after the /k. Save it and let it run and it wont close after it does whatever its doing so you can now see what the prompt is doing)
after that I saw that nvflash failed bc it didnt have the boot/system/recovery images in the folder.
i cant post external links and cant link to the img's i got but just do a quick search for nvflash and prime you'll find em.
I knew it was prime and wanted to keep stock but with root but whatever, I'll look to get back into stock later.
just posting this up so if someone has the same problem they can fix it.
You MUST use apx to restore your device it seems the boot partition is wrong you should restore that with nvflash.
Update: SOLVED! See post #9
Hi... I ended up with a brick, unable to boot into anything at all, not even APX mode.
I followed the guide on the AndroidRoot.mobi website and made backup of all the files before that, though.
After finish with the guide, my device was working, but stuck in APX mode after every reboot and the only way to boot further (into fastboot or system) was to go through the command sequence
Code:
wheelie -r --blob blob.bin
nvflash -r --go
So then I started experimenting on my own... Firstly I tried
Code:
nvflash -r --download 6 boot.blob.LNX
Where boot.blob.LNX I extracted from boot.blob in the latest CM10 nightly.
After a restart, nothing changed, so I did this
Code:
wheelie -r --blob blob.bin
nvflash -r --download 4 bootloader.ebt # [B]bootloader.ebt[/B] is the file from the backup
nvflash -r --go # Did this while swiftly pressing PowerDown and went into Fastboot mode only to break everything with the next command
fastboot reboot
Since then I don't get any reaction whatsoever when I plug in my tab through USB. Tried both Linux (I completed the guide under Linux, btw) and Windows - they don't even recognise there is a usb device connected. Pressing/holding down on Power, Power+VolumeUp or etc. seems to have no effect. wheelie is stuck on
Waiting for device in APX mode...
Click to expand...
Click to collapse
Is there hope for me? Is there some other way to get to APX?
Is there hope for me? Is there some way to get to APX?[/QUOTE]
Have you asked in the NVFlash thread? " http://forum.xda-developers.com/showthread.php?t=1894867 " They don't provide a thread in general for support so I assume that is proper.
The site with the guide " http://androidroot.mobi/t3_nvflash/ "does not appear to offer support either. However there is this quote " ** Failure to make this back-up file will lead to support being withheld if you brick your device. You have been warned. ** ". So it seems they expect to provide support!
Good Luck!
I have JB bootloader so no NVFlash for me.
tobdaryl said:
Is there hope for me? Is there some way to get to APX?
Click to expand...
Click to collapse
Have you asked in the NVFlash thread? " http://forum.xda-developers.com/showthread.php?t=1894867 " They don't provide a thread in general for support so I assume that is proper.
The site with the guide " http://androidroot.mobi/t3_nvflash/ "does not appear to offer support either. However there is this quote " ** Failure to make this back-up file will lead to support being withheld if you brick your device. You have been warned. ** ". So it seems they expect to provide support!
Good Luck!
I have JB bootloader so no NVFlash for me.
Click to expand...
Click to collapse
Thank you for your answer. I did ask in the NVFlash thread a few weeks ago, got no answer. I've now commented on the website with the guide, hope I get some support there. In the meantime, if anyone has ideas, I'm willing to experiment!
I am sorry, I had hoped someone involved with the project would give proper advice.
I was already on JB when nvflash arrived.
I will invest more time on searching and reply when I find answers or give up the chase!
I have seen a thread with some info about how the OP unbricked but it was not the same issue as you have. The OP stated that he received no help and just started trying commands and got lucky.
xilunas said:
Thank you for your answer. I did ask in the NVFlash thread a few weeks ago, got no answer. I've now commented on the website with the guide, hope I get some support there. In the meantime, if anyone has ideas, I'm willing to experiment!
Click to expand...
Click to collapse
Time for some background info. I know I will be covering ground you have already covered but try to humor me!
It seems the only way into apx is when unit reboots!
Does your unit charge, when you power on is there at least indication unit tries to come on ( slight glow, etc. )?
In linux terminal without unit plugged into computer type ( lsusb ), now plug unit into computer power on and type ( lsusb ). Are the results returned identical? If they are not identical in linux terminal type ( adb devices ) then type ( fastboot devices ).
Reply with results.
Be careful with the info in the link posted below. It is hard on your battery plus as voltage drops current flow rises to compensate and the chances of electronic components being damaged rises as well.
If you have gotten beyond my above suggestions then next power on, hold volume up, and use small paper clip to press reset ( this is done while plugged into computer to catch apx on reboot. Reset is located on left side about one inch below the external sdcard.
There is one more but I'll reserve it as I had this one so we didn't get ahead of ourselves.
Last of all if you are at the end of your road and still no love, disconnect battery (here you could also run your battery down) while usb plugged onto computer. When you replug battery ( while holding volume + ) unit should reboot and get apx mode.
The following may be what you wish if you are trying to exit NVFlash - http://androidroot.mobi/t3_nvflash/.
WARNING: If you run the following command it will boot your device into regular android. This is listed as an *EXAMPLE*. Run the commands in “What Next?” section first.
From this point you will be able to use nvflash as normal by running commands such as the following to continue booting your device:-
$ nvflash --resume --go
i read this thread http://forum.xda-developers.com/showthread.php?t=1478361
maybe it good for u.....just try and tell me what u get
I think that this fix won't work for your TF cause you must use "ODIN" which it's particular to Samsung.
Read this sentence:
From here on out everything is easy sailing. Get the right firmware and Odin and flash the firmware you require. It doesn't matter what region you are from, the tablet is made to accept any regional firmware BUT the model number should be the same. Which mean's 7500 for 7500 ONLY.
Click to expand...
Click to collapse
xilunas said:
Thank you for your answer. I did ask in the NVFlash thread a few weeks ago, got no answer. I've now commented on the website with the guide, hope I get some support there. In the meantime, if anyone has ideas, I'm willing to experiment!
Click to expand...
Click to collapse
I got bored and decided to read the NVFlash thread. I copied everything in that thread I thought I would like to know if I had NVFlash.
Here is a link that includes that info.
http://forum.xda-developers.com/showthread.php?p=33428304#post33428304
Good Luck!
I know it is not laid out very well but at least the info is there.:good:
tobdaryl said:
If you have gotten beyond my above suggestions then next power on, hold volume up, and use small paper clip to press reset ( this is done while plugged into computer to catch apx on reboot. Reset is located on left side about one inch below the external sdcard.
Click to expand...
Click to collapse
This worked! After pressing the reset button my TF300 was recognized in APX mode and from then I was able to restore it to a working state!
Thank you, tobdaryl!
BTW, to recover the tablet from APX I used ideas using an automated linux script TF201-nvFlashFactoryRecovery-Linux which can be found in another forum. It is intended for tf200 but some small modifications it worked great for my TF300:
replace the nvflash and wheelie given there (for TF200) with the ones you have (for TF300)
replace flash.cfg with the attached to this post flash.cfg (I modified it to reflect some different partition sizes on TF300)
use AndroidRoot-BlobTools to unblob a system image (I used a 4.0 image from the asus website)
in my case, I have to use the -r flag with wheelie each time for it to work:
Code:
sudo ./wheelie -r --blob blob.bin
follow the README
I'll be happy to assist anyone in my situation, just write here or PM.
Finally, I am still unable to power on the tablet without wheelie and nvflash --resume --go because it is stuck in APX by default. I think I will flash the new bootloader and see if this fixes it.
Hi all,
I have a bricked TF101 (SBK v2) that I am trying to recover. There are numerous threads for this which I have tried following but keep hitting brick walls and as these threads tend to be in the development section, I am currently unable to post in them for advice.
I have tried a few differing programs to try and recover the device including "Oneclickrecovery", "BRK_Rootkit" and "Easyflasher"
Easy flasher (0.8.3b) seems to give the best results so far so I'm going to try and continue with this.
When running through the steps I get the following on the tablet screen:
Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!
and the following from Easyflasher:
EasyFlasher for TF101 - By [email protected]
Using SBK2
---------------------------------------------------------------------------------------------------------------------------
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
>Blob extracted!
>Blob size 533946.73828125kb
Running Wheelie..
>Tablet is now ready for Nvflash
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 4184kb
>APP size 524288kb
>EBT size 1420.6171875kb
>LNX size 4054kb
Done!
However each time I reboot the device goes straight back in to APX mode. I have seen from the thread that different folks had different outcomes with different versions of easyflasher, but I cannot locate where to download different versions.
I am currently in the UK but the device was purchased in the US but I get the same results when trying to use any of the WW or US stock ROM update versions.
Any help locating different versions of easyflasher or any other advice you guys might have would be very well received as I now have a sore forehead from banging it on my desk.
Thanks for your time,
dhehir
reinstall recovery with easy flasher and after it finish power nadh olf button down.
vietchinh said:
reinstall recovery with easy flasher and after it finish power nadh olf button down.
Click to expand...
Click to collapse
Thanks vietchinh,
I have tried this, just keeps going back to APX mode each time.
Have you tried just a straight forward NVFLASH ROM ?
http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
*Detection* said:
Have you tried just a straight forward NVFLASH ROM ?
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
Click to expand...
Click to collapse
That link above did the trick for me! 3 months later and your post saved my device!
After installing TEAMEOS 4.2.1 (Jelly Bean) and not liking the performance and lockups, I tried to go back to the stock using first Rogue XM recovery (and didn't like it ever) and then TWRP 2.3.2.3. I tried a variety of things from different forums, but my tf101 eventually would only go into APX mode. No matter what, the screen would always remain black and I would see the device show APX in devices on my windows 7.
I tried EasyRecovery (this one didn't seem to do anything), OneRecover, direct nvflash, and nothing worked. I kept trying even more suggestions and doing the same things over and over as some people suggested worked for them (duh), and still nothing worked.
After countless hours of searching, trying different things, your easy suggestion was all I needed!
I have a C10 serial tf101 (US stock firmware).
Thanks a million!
--Eli
morroyoki said:
That link above did the trick for me! 3 months later and your post saved my device!
After installing TEAMEOS 4.2.1 (Jelly Bean) and not liking the performance and lockups, I tried to go back to the stock using first Rogue XM recovery (and didn't like it ever) and then TWRP 2.3.2.3. I tried a variety of things from different forums, but my tf101 eventually would only go into APX mode. No matter what, the screen would always remain black and I would see the device show APX in devices on my windows 7.
I tried EasyRecovery (this one didn't seem to do anything), OneRecover, direct nvflash, and nothing worked. I kept trying even more suggestions and doing the same things over and over as some people suggested worked for them (duh), and still nothing worked.
After countless hours of searching, trying different things, your easy suggestion was all I needed!
I have a C10 serial tf101 (US stock firmware).
Thanks a million!
--Eli
Click to expand...
Click to collapse
haha Great! Well, at least you picked up some knowledge on your journey
Now you know you can play around with anything you want and always be able to get back to stock when you're done
btw, give Team EOS3 #81 combined with K.A.T Kernel #69 a shot
That is JellyBean 4.1.2 and the fastest and most stable ROM for the TF101 imo
*Detection* said:
haha Great! Well, at least you picked up some knowledge on your journey
Now you know you can play around with anything you want and always be able to get back to stock when you're done
btw, give Team EOS3 #81 combined with K.A.T Kernel #69 a shot
That is JellyBean 4.1.2 and the fastest and most stable ROM for the TF101 imo
Click to expand...
Click to collapse
Hello,
I have a very similar problem with my TF101 since few months. Like "dhehir", it is always in APX mode, EasyFlasher seems to works (it displays the three lines
"Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!", EasyFlasher stops at the partition 7.
The link puposed by *Detection* doesn't work, do you know where I can find it ?
Thanks,
Erev
erevlis said:
Hello,
I have a very similar problem with my TF101 since few months. Like "dhehir", it is always in APX mode, EasyFlasher seems to works (it displays the three lines
"Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!", EasyFlasher stops at the partition 7.
The link puposed by *Detection* doesn't work, do you know where I can find it ?
Thanks,
Erev
Click to expand...
Click to collapse
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
*Detection* said:
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Click to expand...
Click to collapse
Thanks a lot !
I'll run it tonight.
*Detection* said:
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Click to expand...
Click to collapse
Snif.... it doesn't work .
During the process, I have the same issue I had with EasyFlasher :
The proces stop at the line :
"
........
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
"
Nothing else, only a blinking cursor on the next line.
The tablet displays "Entering NvFlash recorery mode / Nv3p server
Chip Uid 037...
"
And then nothing appends. (I have waitted about 30 minutes)
Perharps it's a hardware issue :/
Are you running the flashing program as Admin? (Right click > Run as Administrator)
And which version of Windows are you running?
Ive found 32bit Windows 7 to have best compatibility for this sorta thing
I have tried this (as admin, W7 32-bit) and it runs through creating all 15 partitions, then formatting all 15 partitions, the tablet screen shows the Chip UID and then nothing else happens.
I have left it for over an hour and still nothing. The cmd window just shows Formatting Partition 15 Done! and the tablet screen remains the same.
Turn off tablet, and then still won't turn on in anything other than APX mode.
Ideas?
toweliechaos said:
I have tried this (as admin, W7 32-bit) and it runs through creating all 15 partitions, then formatting all 15 partitions, the tablet screen shows the Chip UID and then nothing else happens.
I have left it for over an hour and still nothing. The cmd window just shows Formatting Partition 15 Done! and the tablet screen remains the same.
Turn off tablet, and then still won't turn on in anything other than APX mode.
Ideas?
Click to expand...
Click to collapse
Hmm, I know it does take a long time using NVFLASH, but you should see the progress bar after the partition sections have finished it starts sending the files across, there is one partition that takes a super long time to complete though
Have you tried a different machine ?
Maybe set it going and leave it overnight in case it manages to complete whatever it's getting stuck on
*Detection* said:
Hmm, I know it does take a long time using NVFLASH, but you should see the progress bar after the partition sections have finished it starts sending the files across, there is one partition that takes a super long time to complete though
Have you tried a different machine ?
Maybe set it going and leave it overnight in case it manages to complete whatever it's getting stuck on
Click to expand...
Click to collapse
I tried EasyFlasher and left it running for hours and hours (when I previously thought it was stuck at partition 10) and it coompleted - but with no change in behaviour.
I then tried NVFlash again and left it over night - again the same result. Everything seems to 'work' in that it completes without errors but still the tablet won't turn on in anything other than APX mode.
I have tried to get the device registered as an ADB device and after spending a long time yesterday upgrading the SDK tools, I managed to get it showing in Device Manager as an ADB device and working correctly. However, running adb.exe I still cannot get it to 'show' as a device, even after running adb kill-server and adb start-server. I always get "error: device not found".
This is so frustrating as the device is clearly turning on and off but I can't seem to get it to be anything other than an APX mode.
A shot in the dark, but have you checked to see if the Volume Up button is stuck in ?
That would make it boot in APX mode each time
Quite simple to take the plastic bezel surround off and get to the micro switch under the volume rocker, just 2 screws near the port, then use a plastic flat thing to unclip the bezel
*Detection* said:
A shot in the dark, but have you checked to see if the Volume Up button is stuck in ?
That would make it boot in APX mode each time
Quite simple to take the plastic bezel surround off and get to the micro switch under the volume rocker, just 2 screws near the port, then use a plastic flat thing to unclip the bezel
Click to expand...
Click to collapse
Tried that, as expected the buttons are fine. Nothing stuck, all operating as it should.
Currently sitting in a semi-morgue state (the tablet, not me) with me having run out of ideas...
:crying:
No further suggestions?
It seems a waste to let this one die when it surely must be salvageable?
*Detection* said:
Have you tried just a straight forward NVFLASH ROM ?
(...) (I can't post the link .. it doesn't matter anyway) (...)
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
Click to expand...
Click to collapse
Hi. I'm quite new here (in fact, this is my first post).
I've had an ASUS TF101 for a while now. I haven't used it in a while, and i believe that caused the batery to fully drain - as a result, i couldn't get it even to re-charge with the wall charger, much less to boot. I am now trying to revive it, so have been doing some research on the net, and reached as far here. I am able to connect it in APX mode, and tried running nvflash as above indicated (following the later posted correct link). However the bootloader doesn't seem to want to initialize. Below is what I've gotten:
C:\Users\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT>cd C:\Users
\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT\
C:\Users\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT>"nvflash.ex
e" --bct transformer.bct --setbct --configfile flash.cfg --create --bl blob.EBT
--odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0388924041ff3457
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
waiting for bootloader to initialize
And that's it, it has been like this for about one hour now - is it normal to take this long.
By the way, the tablet screen is all black, nothing on it.
Can someone help me beyond this? Thanks!