Boot Loop (Stock Rom) NV Flash no Option - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi there,
Tried the search a bit, but nothing really fits my problem.
To make it short:
TF 101 -> Stock 3.0.1 ROM
Downloaded Update @ Asus Website (to get 3.1 / 3.2)
Put on SD Card
Installation aborts (Android with yellow/black "!" Picture)
Since that only Boot Loops
Serial is B70, so NV Flash would not help, right?
Is there something I can do to get this wonderful device to work again?
Some background info:
Bought it off "used" from a marketplace. Told me he was on Revolver Rom before. But he unrooted and went back to stock (3.0.1 and Asus Recovery) to sell it. After I checked for software updates since the version was 3.0.1 (and i know that 3.2 is out)but the System told me "No Update Available", I wanted to manually update (Asus Site /SD Card). I made sure the version was the correct one (DE). After aborting installation I also tried the WW Version.
Thanks for any help!
adios

mio15 said:
Serial is B70, so NV Flash would not help, right?
Is there something I can do to get this wonderful device to work again?
Click to expand...
Click to collapse
Some B70 are NVFlash compatible. Just try it, might work might not.

Thanks for the answer!
After installing the USB Driver and setting APX Mode I got this:
(sidenote: when I run the download.bat via explorer it closes instantly)
is there maybe another method that I´m missing?
Thanks a lot

mio15 said:
Thanks for the answer!
After installing the USB Driver and setting APX Mode I got this:
(sidenote: when I run the download.bat via explorer it closes instantly)
is there maybe another method that I´m missing?
Thanks a lot
Click to expand...
Click to collapse
When using:
nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 xECFE1D98 --sync
You should get something like this:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c624940007497
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
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: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Otherwise do the SBK test.

mio15 said:
Thanks for the answer!
After installing the USB Driver and setting APX Mode I got this:
(sidenote: when I run the download.bat via explorer it closes instantly)
is there maybe another method that I´m missing?
Thanks a lot
Click to expand...
Click to collapse
If I am not mistaken, the rcm version 0x4 means you have SBK2, which can't be recovered with nvflash, this is what I got when I tried my new TF101.
this brings the question: What is the Stock Asus recovery useful for? can't it recover a stock rom from the sdcard?

Can you get back into recovery mode? i would suggest downloading another coy of the stock ROM, place it on your SD card name it WW_epad-user-8.6.5.19.zip (or whatever the name of the firmware version is, but I would recommend this version) and try to get bck into recovery again..worth a shot

Thanks for all posts!
Tried different Firmwares from Asus so far. 8.6.5.(21 & 13 ) DE and WW (just in case even US)
8.6.5.19 is missing on Asus Site
None of them worked. -> Short unpacking animation -> Android with "!" Sign
I put the device into Stock Recovery (Power + Vol Down)
Option 1:
Hit no Button -> Wipe User Data (when I chose this the TF101 stucks after "This could take a few minutes...")
or - Cold Start Device (changes nothing)
Option 2:
Hit Volume Up (within 5 Secs)
Booting Recovery Kernel Image
-> Android with Exclamation Mark Sign (even if no SD is inside)
The curious thing is. The Eee Pad will not stay off anymore. After holding the Power Button it just fires up again and stucks at Boot Logo.
I wonder why this all happens to a "non" root device with Stock ROM(´s)
Thanks to all you guys!

You are extracting the files after downloading correct?

What I get after downloading is a .zip (e.g. UpdateLauncher_US_epaduserV8_6_5_13)
After extracting with winrar 4.0 (x64) there is "Asus\Update\WW_epad-user-8.6.5.13 (.zip)"
put WW_epad-user-8.6.5.13 on root on MicroSD
(like on every tutorial found woth google)
(tested it also with Folder Structure (Asus\Update\ or Update\)
Nothing worked for me.
But I will try something using another extraction tool. good idea.
Thanks! -> downloading with another browser and using 7zip changed nothing
Edit: Someone got a link to 8.6.5.19 Firmware?
When I rename the Update into "EP101_SDUPDATE" the installation bar shows up and runs a while. but after a few seconds again Android with exclamation mark

Any news here? I have the exact same problem..
I bought my new TF101 (B70) a couple of months ago. Never rooted it nor istalled anything strange (just 100k+ downloaded apps from stock market). Last week it started crashing.. Got it boot looped but wiping data did the trick. Now it is boot looped again and wipe data doesn't work anymore ... any ideas?

Related

Recovery is gone

I have searched the threads and have not been able to find a problem like mine
I modded my Gtablet with CyanogenMod 6.14b and have also installed the Gapps and all is working great!. But I wanted to do a image backup so I powered off and then using the Pwr VOL+ keys to try and enter recovery. I get the "android" text on the screen for about 15 seconds and then it just boots into cyanogen. I have done the following but to no avail
1) copy new clockworkMod Update.zip and recovery folder to root of MicoSD
no luck
2) same as above, but to mtn/emmc (What Cyanogen now calls Internal SDCARD)
3) Changed the value in command file from --update_package=SDCARD2:\update.zip
to
--update_package=SDCARD:\update.zip
I also noted that there are folders EMMC and SDCARD listed under "/" as well as under "/MNT" they appear to be the same. Is this normal???
No mater what I do, I cannot get into recovery Mode.
Any help will most likely get you into heaven
Success!!!! Was able to restore using the recovery.img in clockworkMod Many thanks to ngorgi and ReoBeet for the help.
Did you use the clockworkmod specifically for our device and the one I use, which is .08? It sounds likely, but I wanted to confirm that.
Assuming that you did and that recovery is borked, you won't be to fix it the normal way since there's no recovery to flash recovery (if that makes sense). You might have to try either flash_image which a few people have suggested might work, or nvflash. I personally have used the latter.
If you can get APX mode working and get bekit's nvflash setup working, you can just flash partition 9 with bekit's recovery.img and that might work. I have a post on nvflash here: http://forum.xda-developers.com/showthread.php?t=861950
i Used the .08 as your surmised, My question is how did the recovery get lost?
When the PWR + VOL+ get used to enter recovery, what file is executed?
It took me several days to configure my tablet, it would be a shame to lose all that work.
But If that is my only option, then NVFlashing I will go
Try to change the value in the command file to...
--update_package=EMMC:\update.zip
Might do it... you can't point it to SDCARD unless you place the update.zip on an inserted Micro SD Card.
- AdamZ
I'm not sure how your recovery is borked, but I'm assuming that it is. You can use nvflash to just flash recovery and nothing else - technically you shouldn't lose anything that way (but, backing up first is always a good idea).
Just Tried that (Good Idea), but no luck. I believe that the COMMAND file is only used when you execute the ZIP from recovery so It appears I am out of luck. The good news is that my Tablet is running great, just have no way to backup or restore an Image.
I may be suborn, but I believe there must be a way to get recovery working again. I do see that there is a recovery.img file on both my SDCARD and EMMS.
When I try and start recovery, I do get the Recovery Key Detected, just never goes into the recovery program.
This is an interesting problem ...
roebeet, Did not see your post until just now, I will reseach the NVFlash as I see there are a few threads on using it. I assume you can select what to flash.
Thank your
Tried the NVFLash and here is what I got
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflas
loader.bin --download 9 recovery.img
Nvflash started
USB device not found
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflas
loader.bin --download 9 recovery.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17141188448001d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x10800
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery.img
- 589824/3463168 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>
Help!!!!
BUt it still boots fine
Now on trying recovery Mode it says Booting Recovery Image after recovery key detected (So a little progress is made)
I am wondering if I need to get the specific recovery image for the recovery partition. I was just using the one that came with NVFlash. I downloaded the NVFlash_Gtablet and there are 11 image files so I do not know what Image file is for the Recovery Partition.
Am i on the right track yet???
JUST fixed this problem for myself, I'm gonna post another thread with a how-to of how I fixed this.
brookfield said:
I am wondering if I need to get the specific recovery image for the recovery partition. I was just using the one that came with NVFlash. I downloaded the NVFlash_Gtablet and there are 11 image files so I do not know what Image file is for the Recovery Partition.
Am i on the right track yet???
Click to expand...
Click to collapse
Recovery is image 9. There is a recovery image floating around here that can be used in place of image 9 and it will put clockwork back.

[GUIDE]NVFlash Procedure to Load ClockWorkMod (CWM)

Following is the NVFlash procedure for installing ClockWorkMod (CWM) for those
people who are having boot loop problems (or other problems) and need
to install CWM by flashing rather than by using /sdcard or a microSD card
via /SDCARD2. No apologies -- this is written so even the new folks can use it.!
1. You need to get a copy of ClockWorkMod v.8, which can best be done
by downloading through the following thread. Also, you might check the
thread for related info -- it's a good one:
http://forum.xda-developers.com/showthread.php?t=1010943
2. Once you have the CWM files, go to your NVFlash directory (or whatever
you call it) and make sure you have the right files in it.
-- Nvflash.exe and related files (nvflash_gtablet_2010110500.zip) from
the original NVFlash Recovery thread.
-- USB drivers (also from NVFlash Recovery thread. If you already are
flashing via APX you should have them installed.)
-- The file "nvflash_gtablet.bat" from the NVFlash Recovery thread.
-- The CWM .img file (next item will tell you how to get it.)
3. Next you will need to extract the CWM .img file from the .zip file you
downloaded. First, extract the files from the download -- you should get
a recovery folder and an update.zip. Now unzip the update.zip file and
you will get a file named recovery.img.
4. Rename the file "recovery.img" to "part9.img".
5. Now edit the file "nvflash_gtablet.bat to make the command line read:
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
The command line above for the .bat file does require the quotes around
nvflash.exe!!!
Or you can simply leave the other .bat file alone and create a new
nvflash_cwm.bat file and put the cwm command line in it if you want to.
6. Boot your tablet into APX mode using power/volume - (you will have a black
screen). Connect the USB cable from your G-Tablet to your PC. If you check
the little USB/green check icon on the PC toolbar (bottom right corner of screen)
you see an APX connection listed.
7. Go to the NVFlash subdirectory on your PC and run the .bat file to load CWM.
8. When the flash is done, use the USB/Green Check icon to disconnect from
the PC and then disconnect from the G-Tablet.
9. Shut down and the boot the G-Tablet into Recovery Mode by pressing
Power/Volume + and hopefully you will see the word "Android" and then the
green CWM menu will appear."
Now you're ready to do whatever you need to do with CWM.
Hope this helps.
Rev
This suggest that NVflash tool is more versatile. Not only can you flash the stock ROM but also the recovery and perhaps other ROM's as well.
Thank you for the post. It worked wonderfully. It saved me from having to buy a sdMicro card that I would not need otherwise.
holzy99,
NVFlashing is most useful -- but it also is useful to have a microSD card handy.
In the Q&A forum you will find a similar post I did on how to install CWM using a
microSD card in a pinch. When you need it, you need it!!!
butchconner said:
Following is the NVFlash procedure for installing ClockWorkMod (CWM) for those
people who are having boot loop problems (or other problems) and need
to install CWM by flashing rather than by using /sdcard or a microSD card
via /SDCARD2. No apologies -- this is written so even the new folks can use it.!
1. You need to get a copy of ClockWorkMod v.8, which can best be done
by downloading through the following thread. Also, you might check the
thread for related info -- it's a good one:
http://forum.xda-developers.com/showthread.php?t=1010943
2. Once you have the CWM files, go to your NVFlash directory (or whatever
you call it) and make sure you have the right files in it.
-- Nvflash.exe and related files (nvflash_gtablet_2010110500.zip) from
the original NVFlash Recovery thread.
-- USB drivers (also from NVFlash Recovery thread. If you already are
flashing via APX you should have them installed.)
-- The file "nvflash_gtablet.bat" from the NVFlash Recovery thread.
-- The CWM .img file (next item will tell you how to get it.)
3. Next you will need to extract the CWM .img file from the .zip file you
downloaded. First, extract the files from the download -- you should get
a recovery folder and an update.zip. Now unzip the update.zip file and
you will get a file named recovery.img.
4. Rename the file "recovery.img" to "part9.img".
5. Now edit the file "nvflash_gtablet.bat to make the command line read:
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
The command line above for the .bat file does require the quotes around
nvflash.exe!!!
Or you can simply leave the other .bat file alone and create a new
nvflash_cwm.bat file and put the cwm command line in it if you want to.
6. Boot your tablet into APX mode using power/volume - (you will have a black
screen). Connect the USB cable from your G-Tablet to your PC. If you check
the little USB/green check icon on the PC toolbar (bottom right corner of screen)
you see an APX connection listed.
7. Go to the NVFlash subdirectory on your PC and run the .bat file to load CWM.
8. When the flash is done, use the USB/Green Check icon to disconnect from
the PC and then disconnect from the G-Tablet.
9. Shut down and the boot the G-Tablet into Recovery Mode by pressing
Power/Volume + and hopefully you will see the word "Android" and then the
green CWM menu will appear."
Now you're ready to do whatever you need to do with CWM.
Hope this helps.
Rev
Click to expand...
Click to collapse
very nice!
just need some clarification..
where are we installing the NVFlash directory and APX drivers?
on the PC or on the Gtablet?
On your pc.
Help needed in NV Flash
Sticky thanks for putting such a detailed guide and appreciate that very much. I followed your guide and i am stuck at the NV Flash started. I believe that I had a confusion while editing the nvflash.bat. I edited the NV Flash.bat as following:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --download 9 part9.img --create --go
@set /p batuserinput=Press enter to continue:
Please let me know if I an making a mistake here.
punjabigator,
You were very, very close. The command line needs to be \
exactly what was in the Procedure:
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
Change it to that and try again.
Rev
Didnt work for me stops on
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
Nvflash started
and thats it
Same here
NVFlash starts, but doesn't go anywhere. I am trying to get back to CWM after an NVFlash that has left me with arecovery kernel boot image message switching me away from CWM. Any advise?
Thank you for all you have done for everyone using these! It has been a lifesaver!
Power off
Press Power And Volume-
Start NvFlash
I am going to receive my gtablet this weekend and the first thing I was planning to do was install cyanogenmod. According to the guide on the cyanogenmod website (http://wiki.cyanogenmod.com/index.php?title=Viewsonic_G_Tablet:_Full_Update_Guide), they do not mention anything about nvflash. Is that really required. This is the first time I am modding. Thanks
still stuck in boot loop
Tried this .bat change, it did complete successfully but there were no changes.
Now I can turn it on and have SV birds/gtablet screen changing and shutting off at the end. I can use Nvflash but like I said, regular .bat or this modified didnt work.
anyone in the south Florida area , i cant get this to work right too many downloads g- tablet is driving krazy
Problems with NVFlash
Ok so I have CWM and BL 1.1 on my GTab. I would like to move to BL 1.2 so that I can install a 1.2 Honeycomb.
I also only have access to linux.
So I got the Linux NVFlash tool. I try to get into APX mode and that just boots me into the CWM recovery. NVFlash does not find my GTab.
lsusb shows:
Bus 004 Device 031: ID 0955:7100 NVidia Corp.
Then when I try ./nvflash_gtablet.sh I get:
Nvflash started
UnKnown device found
Done!
Nothing happens.
What am I missing? Has anybody found a good Linux how to?
Thanks
edit
Figured it out.
It is power and volume -
Djnasty18 said:
Didnt work for me stops on
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
Nvflash started
and thats it
Click to expand...
Click to collapse
Yep same problem for me.
New gtab 2.1
Followed cyangen install instructions in the update guide and there was no mention of differences between 1.x and 2.x platforms. SO of course I put a 1.x CMW on my 2.1 platform. Cant boot into recovery. Can boot into the god aweful stock rom.
Followed the NVflash instructions. Installed drivers.
One interesting note is that after finding the apx device, pointing to the drivers, and completing the install (windows of course), there is no apx anything in my drivers lists.
Im in desperate need of getting CMW on this thing.
THanks for you help.
gtablet down
my gtablet will not boot up from any media pleeeease help
rvsuper8 said:
Yep same problem for me.
New gtab 2.1
Followed cyangen install instructions in the update guide and there was no mention of differences between 1.x and 2.x platforms. SO of course I put a 1.x CMW on my 2.1 platform. Cant boot into recovery. Can boot into the god aweful stock rom.
Followed the NVflash instructions. Installed drivers.
One interesting note is that after finding the apx device, pointing to the drivers, and completing the install (windows of course), there is no apx anything in my drivers lists.
Im in desperate need of getting CMW on this thing.
THanks for you help.
Click to expand...
Click to collapse
Go here http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm . Do the 1.2 branch (4349) Stock Rom 1.2 brach with CWM preinstalled. Follow the instructions. One you get back to stock 1.2 branch, go the Start Here page http://viewsonic-gtablet-for-dummies.webs.com/ and do code green.
hugdbear said:
my gtablet will not boot up from any media pleeeease help
Click to expand...
Click to collapse
Can you expound alot!!! What rom are you on, what were you doing, what do you mean by can't boot from any media, etc. Be as detailed as you can so we can assist you.
I think I might be missing something and I apologize if you feel like you are repeating yourselves but when you edit the .bat file what exactly do you put in the file? If someone could just paste into here what it looks like that would be really helpful.
Thanks for the help
EDIT: this post by Im_Gumby from this thread: http://forum.xda-developers.com/showthread.php?t=1058649
worked perfectly for me.
Thanks

[GUIDE] [4/26/12] [CWM 5.8.1.3 *TOUCH*] NVFlashing CWM Recovery for Dummies

This has been tested and confirmed to be working. Follow instructions to the key and you should be good to go!
If you are having ANY issues, watch the video below before posting! It seems to solve a lot of the errors
*WARNING* *WARNING* *WARNING*
NVFlash is a powerful utility that works at a very low level on your phone. There are few safety mechanisms built into a tool like this because it is intended for use by people with suitable training. This CAN brick your device. It is unlikely to create an irrecoverable situation, but it does have the power to create a situation that you can not recover from yourself, thus requiring factory maintenance. Warranty coverage for your phone is not guaranteed after using NVFlash. Please proceed with the use of the tool carefully and at your own risk.​
All credit goes to RussUnderhill, Fitsnugly, krylon360, player911, djmcnz and mapin0518 who made this guide possible
Useful hint: Copy and paste the commands into the command prompt to reduce error
><><><><><><><><><><><><><><><><><><><><
The files you need:
NVFlash.zip (Windows NVFlash app + CWM Recovery 5.0.2.0 Image)
APX Driver.zip (APX Driver)
><><><><><><><><><><><><><><><><><><><><
Optional files:
part5.img (Stock Recovery Image)
p999-4.0.0.2-external-recovery.img (CWM 4.0.0.2 Recovery Image)
p999-ext4-08222011-external-recovery.img (CWM 4.0.1.5 Recovery Image)
recovery-clockwork-5.0.1.6-p999.img (CWM 5.0.1.6 Recovery Image)
recovery-clockwork-5.0.2.0-p999.img (CWM 5.0.2.0 Recovery Image)
recovery-clockwork-5.0.2.6-p999.img (CWM 5.0.2.6 Recovery Image)
recovery-clockwork-5.0.2.7-p999.img (CWM 5.0.2.7 Recovery Image)
><><><><><><><><><><><><><><><><><><><><
Now let's extract the files:
We will be extracting to these two folders:
Code:
C:\G2x\APX Driver
C:\G2x\NVFlash
Extract APX Driver.zip to C:\G2x\APX Driver
Extract NVFlash.zip to C:\G2x\NVFlash
><><><><><><><><><><><><><><><><><><><><
Here's how to do it:
Remove the battery
Hold Vol Up/Down (and keep them held)
Insert the USB cable
Install APX driver from the your APX folder
For windows 7(and vista? please confirm):
Open Device Manager in Windows and you should see "APX Device" listed with an error
Right click on the APX device
Select 'Update driver software'
Select 'Browse my computer...'
Select 'Let me pick...'
Select 'Have disk'
Browse to directory you extracted the *driver* software to: C:\G2x\APX Driver
Select the *entire* 'APX Driver' folder; Do not go inside of it!
Accept any warnings, including the big red alert (you may need to disable UAC)
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat​
Unplug everything
Hold Vol Up/Down (and keep them held)
Insert USB cable
open command prompt
navigate to your NVFlash folder:
Code:
cd \
cd g2x\nvflash
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-5.0.2.0-p999.img
You should see it send a bunch of files to the device and the phone screen should say "S/W Upgrade - Please wait while upgrading...". You can let go of the volume buttons at this point. Once the files are sent and the program is finished running in the command window, you CAN just pull the USB cord or be safe and just wait a few extra minutes, however it will still say "upgrading."
><><><><><><><><><><><><><><><><><><><><
To get into Recovery:
Plug the battery back in (or power off the device if it was on)
Hold Vol Down + Power until you see the LG splash screen with blue highlights (that means keep holding for ~10 seconds after you see the LG boot screen).
><><><><><><><><><><><><><><><><><><><><
This is if you already have all the files and drivers set up:
How to flash ClockworkMod Recovery 5.8.1.3:
CWM Touch is still experimental. Flash at your own risk. Do not expect much help if something goes wrong or does not work right, be prepared for some crisis management. Not everything works properly, but when it does work, it works pretty well. This has bugs. Do NOT flash this unless you know how to flash an alternate recovery if things go wrong.​
download the 5.8.1.3 clockworkmod *TOUCH* recovery image
place p999-5.8.1.3.img in C:\G2x\NVFlash
Unplug everything
remove the battery
Hold Vol Up/Down (and keep them held)
Insert USB cable
open command prompt
execute the following commands:
Code:
cd \
cd g2x\nvflash
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 p999-5.8.1.3.img
><><><><><><><><><><><><><><><><><><><><
This is if you already have all the files and drivers set up:
How to flash ClockworkMod Recovery 5.0.2.7:
download the 5.0.2.7 clockworkmod recovery image
place recovery-clockwork-5.0.2.7-p999.img in C:\G2x\NVFlash
Unplug everything
remove the battery
Hold Vol Up/Down (and keep them held)
Insert USB cable
open command prompt
execute the following commands:
Code:
cd \
cd g2x\nvflash
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-5.0.2.7-p999.img
><><><><><><><><><><><><><><><><><><><><
How to revert back to stock recovery:
download the optional stock recovery image
extract or place part5.img in C:\G2x\NVFlash
Unplug everything
remove the battery
Hold Vol Up/Down (and keep them held)
Insert USB cable
open command prompt
execute the following commands:
Code:
cd \
cd g2x\nvflash
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 part5.img
><><><><><><><><><><><><><><><><><><><><
NVFlash for dummies - Guide to set up and flash a recovery
***Poor quality and outdated but it gets the job done***
><><><><><><><><><><><><><><><><><><><><
Frequently asked questions:
Where do I place the .img files?
You place the .img files in the NVFlash folder you created PRIOR to flashing.
I'm getting an error.
You MUST keep both volume buttons held down the whole time until you get the success message in command prompt!
Try using a different USB port on the computer
This is great to have an official guide thread. For the sake of completeness, here is the link to stock recovery as well so there aren't dozens of posts asking how to return to stock recovery.
http://mirror.dal.tdrevolution.net/ctso/g2x/part5.img
Flash it with nvflash just like you did CWM:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc _x8.bct --bl fastboot.bin --download 5 part5.img
Great stuff. The Mod should definitely add this to the sticky thread.
can u or someone please make a video im a visual person... thanks in advance
EDIT: Nevermind.
los0325 said:
can u or someone please make a video im a visual person... thanks in advance
Click to expand...
Click to collapse
same here. anyone? thanks in advance.
jdaclutch said:
same here. anyone? thanks in advance.
Click to expand...
Click to collapse
I'll try to make a video later, but I've been busy lately so don't get your hopes up for it to be soon
omarsalmin said:
I'll try to make a video later, but I've been busy lately so don't get your hopes up for it to be soon
Click to expand...
Click to collapse
Thanks, i was cluelessly staring at the instructions, lol.
GOOD job! thanks!
Doesnt seem to be working for me, performed as instructed, 2x, still with same results.
Any Ideas?
C:\nvflash>nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emm_x8.bc
t --bl fastboot.bin --download 5 part5.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841c3433f8457
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
Yes Please !!!!!!!!!!!! Thanks
N1user said:
Doesnt seem to be working for me, performed as instructed, 2x, still with same results.
Any Ideas?
C:\nvflash>nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emm_x8.bc
t --bl fastboot.bin --download 5 part5.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841c3433f8457
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
Click to expand...
Click to collapse
I figured out the problem... There nvflash command was wrong. I have correctly updated it in the OP
omarsalmin said:
I'll try to make a video later, but I've been busy lately so don't get your hopes up for it to be soon
Click to expand...
Click to collapse
Patience I got of a lot of it, I got two kids
Sent from my LG-P999 using XDA Premium App
thanks for this guide
i dont feel comfortable flashing new ROMS with the fakeflash. gonna dust off my PC in a few minutes and give this a shot!
unless a mac guide comes out in the next 20 minutes.
suhailtheboss said:
thanks for this guide
i dont feel comfortable flashing new ROMS with the fakeflash. gonna dust off my PC in a few minutes and give this a shot!
unless a mac guide comes out in the next 20 minutes.
Click to expand...
Click to collapse
Don't think so... Haven't been able to find anything pertaining to macs... and Linux just scares me
suhailtheboss said:
thanks for this guide
i dont feel comfortable flashing new ROMS with the fakeflash. gonna dust off my PC in a few minutes and give this a shot!
unless a mac guide comes out in the next 20 minutes.
Click to expand...
Click to collapse
I did this in Fusion with no issues. Keep that PC where it belongs
At least for me, the battery had to be reinserted to flash the recovery...not to install the drivers, however. YMMV.
jlevy73 said:
I did this in Fusion with no issues. Keep that PC where it belongs
Click to expand...
Click to collapse
awesome idea, just flashed it through fusion with no issues!
i used to avoid it because i tried to flash something to my HD2 via fusion and had some odd errors. makes it much more convenient since everything worked first try this time.
overground said:
At least for me, the battery had to be reinserted to flash the recovery...not to install the drivers, however. YMMV.
Click to expand...
Click to collapse
mine flashed w/o the battery just to put that information out there as well.
not sure if different OS' may cause the issue or not.
can anyone please make a video on how to use nvflash?
and the apx cant be installed since they are just files and not a exe. so how would it work
I can't even get my computer to install the APX drivers... when I pull the battery and hold both volume buttons and insert the usb it just comes up as unknown device not apx device and when I try and update the driver I says no files related to your device when I select the nvidia drivers. Hating my pc right now, this is why I love my old mac lol.
Sent from my G2x

Restoring the G2x to stock GB through nvflash

Since I've not seen this done here, and lately I had to do some research on how to pull this off I'll post it here for everyone's benefit.
I had an issue, where the phone would only boot to the recovery. Any recovery that I flashed with nvflash... and even when I flashed a perfectly good ROM image from ClockWorkRecovery, it would still boot into the recovery.
First of all, this will reformat the phone's internal storage, so get your precious data off the phone or make backups.
This method is utilizing nvflash program, which is available on both windows and Linux, to get your phone into the special mode where nvflash can talk to your phone you need to:
- have APX USB drivers installed if you are on windows
- disconnect your G2x from everything, and remove the battery (don't put it back)
- holding both Vol+ anf Vol- buttons, plug in the USB cable connected to your computer (where you have nvflash and the required files)
You can search the web for "APX" "nvflash" to get some more perspective on these things.
I'm not going to explain how to make backups of the partitions with nvflash. Suffice to say that there is --help option in nvflash and look for "--read N filename"
What saved my chops (and allowed me to wipe the partitions and bring everything to stock) was:
1) The files from the first post in http://forum.xda-developers.com/showthread.php?t=1248644
2) you can use this to restore your phone to stock:
Code:
sudo ./nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --setbct --bl fastboot.bin --configfile android_fastboot_emmc_full.cfg --create --go
Thanks anyway, but unfortunately this way doesn't update the baseband/RADIO..only returns the stock ROM with same existing baseband/RADIO..
I have searched a lot, but is there any way to update baseband/RADIO?
(have tried KDZ flashing and LG updater it doesn't work)
Thanks

Bricked TF101 SBKv2 can only enter APX

Like I mentioned, I can only enter APX with my tablet. I cannot boot into recovery, and I cannot boot into Android. Easy Flash does not work. Any attempt to use EasyFlash hangs on "Sending Bootloader..... Sending file: 100%" I am uncertain how to proceed. I would prefer a non-volatile solution(Keeping at least my internal sdcard intact) but through all the things I've tried I may very well have already wiped everything, So I will accept either. I'll soon be trying to use OLiFE-wheelie but I don't have high hopes
Before the brick I was using KatKiss-KitKat #29 Stable
Any help would be appreciated
Easyflasher should work if you have installed the Universal Naked Drivers from the same thread, and are using Win 7 or lower OS (And your cable works for Data, not just charging)
Win 8 needs driving signing disabled to install those drivers
Without the drivers installed, Easyflasher wont be able to talk to the TF
If you get Easyflasher working, you could install TWRP Recovery, then create a backup of your Data > Wipe everything > install a new ROM > Use something like Titanium Backup to restore your saved data
*Detection* said:
Easyflasher should work if you have installed the Universal Naked Drivers from the same thread, and are using Win 7 or lower OS (And your cable works for Data, not just charging)
Win 8 needs driving signing disabled to install those drivers
Without the drivers installed, Easyflasher wont be able to talk to the TF
If you get Easyflasher working, you could install TWRP Recovery, then create a backup of your Data > Wipe everything > install a new ROM > Use something like Titanium Backup to restore your saved data
Click to expand...
Click to collapse
I already had TWRP Installed but nonetheless I did try EasyFlasher after installing the drivers, but wheelie always gets stuck like so: www\.dropbox.\com/s/4zpe8t595ymi7sv/Screenshot%202014-07-16%2020.09.26.png (Remove backslashes, since I am not allowed to post links)
I've also tried using a Linux machine with wheelie to the same effect, thus it can't be a drivers issue.
As for the cable, I don't think there's anyway I can be certain it is functioning Unfortunately, so it may very well be that. You see, my tablet bricked itself after my previous cable broke, thus I have never been able to test this cable with a working transformer. However, it does recognize the APX device attached so it seems to be working.
I seem to remember once putting some empty file in my external sd with a specific name and that magically waking it up... I don't remember, it was quite a while ago
Oh, yes, I've had this same problem before and all I had to do was run nvflash with ""nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go" and that magically woke it up without destroying any data even though it was supposed to. It was odd, but I didn't ask questions.

Categories

Resources