Hi,
I've been trying to use nvflash for awhile on Windows. I'd got it kind of working awhile ago, but I haven't actually flashed TO my Gtab using nvflash, because when I first got it working, one of the first things that I tried was doing:
nvflash.exe -r --getpartitiontable foo.txt
BUT, the foo.txt file that was output was always a binary file, which just didn't seem right, so I didn't want to take the chance of trying a flash with possibly bad files.
Up until tonight, I'd been trying to use the files from Bekit's dropbox, as linked in this thread here:
http://forum.xda-developers.com/showthread.php?t=861950
However, tonight, I wanted to setup a new Windows laptop, so first thing was to get the APX USB driver working.
In that thread above, it's mentioned that the USB drivers may be in the ZIP files from the dropbox, but that doesn't seem to be the case. The .inf is in the ZIP, but not the actual driver files.
I eventually found the drivers by downloading the .msi file for Android 2.2 Froyo from Nvidia's developer website:
http://tegradeveloper.nvidia.com/tegra/downloads
After I downloaded the .msi, I ran it.
That creates an "NVIDIA\tegra_froyo_20101105\usbpcdriver" directory, and in there, there's a file named "NvidiaUsb.inf", with the subdirs containing the DLLs.
Now, after you power on the Gtab, while holding the Vol- button and get to the black screen, in Windows Device Manager, there'll be a device under USB devices, "APX", with a yellow exclamation mark.
Right click on "APX" and select "Update", then browse to the "NVIDIA\tegra_froyo_20101105\usbpcdriver" directory, then let the driver install.
Then, a device named "NVIDIA USB Boot-recovery driver for Mobile devices" should appear under Universal Serial Bus controllers.
At this point, the APX USB driver is installed.
Now, going back to my original problem, i.e., that the --getpartitiontable was outputing a binary file...
I found that in the "NVIDIA\tegra_froyo_20101105" directory, there's an nvflash.exe, but it was larger than the one from the dropbox ZIP, so, I decided to try that, but, using the "bootloader.bin" from the dropbox ZIP.
So, I did:
- Change directory to "NVIDIA\tegra_froyo_20101105"
- Run nvflash to push the dropbox bootloader.bin to the Gtab:
nvflash.exe --bl <PATH_TO_DROPBOX_ZIP_DIR>\bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714404641e0f5d7
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: 0x108000
sending file: ..\..\Windows\bootloader.bin
| 928945/928945 bytes sent
..\..\Windows\bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
At this point, the following small text appears on the Gtab display:
Code:
Entering NvFlash recovery mode / Nv3p Server
[The above message is being displayed by the code in the bootloader.bin when it got loaded into the Gtab, and then "executed" (the --go part of the command line). After the "--bl", the bootloader.bin is in the Gtab memory, then the --go tells the Gtab to execute the bootloader code.]
- Then, I did the --getpartitiontable:
nvflash.exe -r --getpartitiontable foo.txt
Nvflash started
[resume mode]
Succesfully updated partition table information to foo.txt
[The -r in the command line above is because the bootloader has already been started on the Gtab, so this command is a continuation/resume.]
- After that, I checked the foo.txt file, and it was now a text-formated file:
Code:
LASH-USB-DRIVER\tegra_froyo_20101105>type foo.txt
PartitionId=2
Name=BCT
DeviceId=19
StartSector=0
NumSectors=1536
BytesPerSector=2048
PartitionId=3
Name=PT
DeviceId=19
StartSector=1536
NumSectors=64
BytesPerSector=2048
PartitionId=4
Name=EBT
DeviceId=19
StartSector=1600
NumSectors=1024
BytesPerSector=2048
PartitionId=5
Name=MBT
DeviceId=19
StartSector=2624
NumSectors=64
BytesPerSector=2048
PartitionId=6
Name=MSC
DeviceId=19
StartSector=2688
NumSectors=8192
BytesPerSector=2048
PartitionId=7
Name=BLO
DeviceId=19
StartSector=10880
NumSectors=2048
BytesPerSector=2048
PartitionId=8
Name=OGO
DeviceId=19
StartSector=12928
NumSectors=16384
BytesPerSector=2048
PartitionId=9
Name=SOS
DeviceId=19
StartSector=29312
NumSectors=8192
BytesPerSector=2048
PartitionId=10
Name=LNX
DeviceId=19
StartSector=37504
NumSectors=8192
BytesPerSector=2048
PartitionId=11
Name=APP
DeviceId=19
StartSector=45696
NumSectors=102400
BytesPerSector=2048
PartitionId=12
Name=CAC
DeviceId=19
StartSector=148096
NumSectors=111104
BytesPerSector=2048
So, in summary, for Windows, I think that:
- Use the APX USB driver files from the Tegra download to install the APX USB driver
- Use the nvflash.exe in the Tegra download folder, but the bootloader.bin from the dropbox ZIP file.
Anyway, that's what works for me, and I hope that this helps someone here in the future...
Jim
jimcpl said:
Hi,
I've been trying to use nvflash for awhile on Windows. I'd got it kind of working awhile ago, but I haven't actually flashed TO my Gtab using nvflash, because when I first got it working, one of the first things that I tried was doing:
nvflash.exe -r --getpartitiontable foo.txt
BUT, the foo.txt file that was output was always a binary file, which just didn't seem right, so I didn't want to take the chance of trying a flash with possibly bad files.
Up until tonight, I'd been trying to use the files from Bekit's dropbox, as linked in this thread here:
http://forum.xda-developers.com/showthread.php?t=861950
However, tonight, I wanted to setup a new Windows laptop, so first thing was to get the APX USB driver working.
In that thread above, it's mentioned that the USB drivers may be in the ZIP files from the dropbox, but that doesn't seem to be the case. The .inf is in the ZIP, but not the actual driver files.
I eventually found the drivers by downloading the .msi file for Android 2.2 Froyo from Nvidia's developer website:
http://tegradeveloper.nvidia.com/tegra/downloads
After I downloaded the .msi, I ran it.
That creates an "NVIDIA\tegra_froyo_20101105\usbpcdriver" directory, and in there, there's a file named "NvidiaUsb.inf", with the subdirs containing the DLLs.
Now, after you power on the Gtab, while holding the Vol- button and get to the black screen, in Windows Device Manager, there'll be a device under USB devices, "APX", with a yellow exclamation mark.
Right click on "APX" and select "Update", then browse to the "NVIDIA\tegra_froyo_20101105\usbpcdriver" directory, then let the driver install.
Then, a device named "NVIDIA USB Boot-recovery driver for Mobile devices" should appear under Universal Serial Bus controllers.
At this point, the APX USB driver is installed.
Now, going back to my original problem, i.e., that the --getpartitiontable was outputing a binary file...
I found that in the "NVIDIA\tegra_froyo_20101105" directory, there's an nvflash.exe, but it was larger than the one from the dropbox ZIP, so, I decided to try that, but, using the "bootloader.bin" from the dropbox ZIP.
So, I did:
- Change directory to "NVIDIA\tegra_froyo_20101105"
- Run nvflash to push the dropbox bootloader.bin to the Gtab:
nvflash.exe --bl <PATH_TO_DROPBOX_ZIP_DIR>\bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714404641e0f5d7
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: 0x108000
sending file: ..\..\Windows\bootloader.bin
| 928945/928945 bytes sent
..\..\Windows\bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
At this point, the following small text appears on the Gtab display:
Code:
Entering NvFlash recovery mode / Nv3p Server
[The above message is being displayed by the code in the bootloader.bin when it got loaded into the Gtab, and then "executed" (the --go part of the command line). After the "--bl", the bootloader.bin is in the Gtab memory, then the --go tells the Gtab to execute the bootloader code.]
- Then, I did the --getpartitiontable:
nvflash.exe -r --getpartitiontable foo.txt
Nvflash started
[resume mode]
Succesfully updated partition table information to foo.txt
[The -r in the command line above is because the bootloader has already been started on the Gtab, so this command is a continuation/resume.]
- After that, I checked the foo.txt file, and it was now a text-formated file:
Code:
LASH-USB-DRIVER\tegra_froyo_20101105>type foo.txt
PartitionId=2
Name=BCT
DeviceId=19
StartSector=0
NumSectors=1536
BytesPerSector=2048
PartitionId=3
Name=PT
DeviceId=19
StartSector=1536
NumSectors=64
BytesPerSector=2048
PartitionId=4
Name=EBT
DeviceId=19
StartSector=1600
NumSectors=1024
BytesPerSector=2048
PartitionId=5
Name=MBT
DeviceId=19
StartSector=2624
NumSectors=64
BytesPerSector=2048
PartitionId=6
Name=MSC
DeviceId=19
StartSector=2688
NumSectors=8192
BytesPerSector=2048
PartitionId=7
Name=BLO
DeviceId=19
StartSector=10880
NumSectors=2048
BytesPerSector=2048
PartitionId=8
Name=OGO
DeviceId=19
StartSector=12928
NumSectors=16384
BytesPerSector=2048
PartitionId=9
Name=SOS
DeviceId=19
StartSector=29312
NumSectors=8192
BytesPerSector=2048
PartitionId=10
Name=LNX
DeviceId=19
StartSector=37504
NumSectors=8192
BytesPerSector=2048
PartitionId=11
Name=APP
DeviceId=19
StartSector=45696
NumSectors=102400
BytesPerSector=2048
PartitionId=12
Name=CAC
DeviceId=19
StartSector=148096
NumSectors=111104
BytesPerSector=2048
So, in summary, for Windows, I think that:
- Use the APX USB driver files from the Tegra download to install the APX USB driver
- Use the nvflash.exe in the Tegra download folder, but the bootloader.bin from the dropbox ZIP file.
Anyway, that's what works for me, and I hope that this helps someone here in the future...
Jim
Click to expand...
Click to collapse
Thanks, I had to figure most of this out the hard way a few days ago. I did use the nvflash.exe from Bekit's ZIP, actually, but I likewise had to download the MSI from NVidia's website to get the APX drivers.
Hi,
Do you get text file out when you do --getpartitiontable with the nvflash.executive in his ZIP?
Jim
Finally able to get nvflash setup. Had first magic value mismatch today and this saved me. Thanks
I have tried to download the .msi file but did not have the inf file for the usb driver. I have not been able to update the file on my windows 7 machine.
kchuskerrph,
I couldn't get the USB to install either.
So I found the "SystemUSB.zip" I had downloaded from the Advent Vega download site.
When I attached my G-Tab to the PC and the driver install failed (didn't know where to look, of course) -- I then went to Control Panel/Device Manager and found the APX entry. Clicked that and told it to Update Driver and then I did manual and Browse to
tell it to look in the folder for the above files. It installed and worked fine for me although I only did it one time so I can't "guarantee" it.
Hope this helps.
Rev
were did you get the "SystemUSB.zip file"? I have not downloaded that before I don't think. I'm about ready to just junk that damn thing and get an ipad!!!!
Go to:
http://www.myadventvega.co.uk
and look under the Downloads tab in the middle of the page.
Rev
P. S. -- BTW, this thing is about three layers of directories deep. When I pointed my updater to it I tried to get to the subdirectory where the .inf file is -- "USB".
P. S. S. -- Also, there is a long narrative of my nvflash experience at the end of the TNT 5.0.0 sticky -- page 380 post 3798 in Developer forum. Tells it all.
Partition tables
hello folks,
to get partitions-structure of each FW-Build? isn't it easy to take the *.cfg files from the build and print it???
Even there are more info's about each partition and mostly an image that you can reflash if you bricked your tablet
butchconner said:
Go to:
and look under the Downloads tab in the middle of the page.
Rev
P. S. -- BTW, this thing is about three layers of directories deep. When I pointed my updater to it I tried to get to the subdirectory where the .inf file is -- "USB".
P. S. S. -- Also, there is a long narrative of my nvflash experience at the end of the TNT 5.0.0 sticky -- page 380 post 3798 in Developer forum. Tells it all.
Click to expand...
Click to collapse
OMG Thank you SO much. I've spent at least 6 hours trolling around trying to find the correct drivers needed to unbrick my tablet during my upgrade attempt. Installed from the AdventVega site and it all worked perfectly the first time around.
What is the exact name of the file you downloaded from nvidia? The target or the host? I only saw the windows openGL ES in .msi format. Could be real specific. Thanks, been trying to unbrick my tab. If I can't get nvflash on it I will be returning it as defective.
butchconner said:
Go to:
http://www.myadventvega.co.uk
and look under the Downloads tab in the middle of the page.
Rev
P. S. -- BTW, this thing is about three layers of directories deep. When I pointed my updater to it I tried to get to the subdirectory where the .inf file is -- "USB".
P. S. S. -- Also, there is a long narrative of my nvflash experience at the end of the TNT 5.0.0 sticky -- page 380 post 3798 in Developer forum. Tells it all.
Click to expand...
Click to collapse
Thanks, I tell you. The UK sure knows how to simplify things. I got my cell phone unlocked from europe for that reason. They cut to the chase.
PING: jimcpl -- info for you
jimcpl,
PMs were down, so I am just posting this as a reply so you and anyone else who needs this will have it:
In this thread about nvflashing, you have a reference to the nvidia developer download area. I think they may have taken the .msi file you recommend out of there. I was looking for it yesterday and found a substitute for the USB driver (or at least a re-packaged version.
Then I found a post in the Developer nvflash thread which lists a direct download link for what I think you were saying get. (The SDK) Thought you might want to check your thread and update it if needed since Roebeet refers to it.
"Since this post I have found a post by CyHawk which has a direct link to the nVidia Android SDK:
http://developer.download.nvidia.com...o_20101105.msi
If you download and install this it looks like it includes the nvflash stuff in the "windows" files listed above --
and more importantly it has a folder in it called "usbpcdriver" which contains the same files as the Advent
Vega download above. I have not used the nVidia SDK stuff, though, so I can't vouch for it."
Thanks for your help.
Rev
NVFlash the easy way
Get this zip from mediafire.Instructions inside zip file. It does work I created this zip after struggling for almost 1 hr trying to flash back stock rom.
http://www.mediafire.com/?5op96ostv5w2qiy
all,
otreblada's .zip file as referenced above pulls together the two .zip files and the USB driver directory I used to create an NVFlash directory on my PC and then flash my G-Tablet after a bad lockup.
As he said, with these files loaded in a subdirectory, all you have to do is hook up the cable, go into APX mode (power/Volume- at the same time), load the USB driver, and run the .bat file.
All of that is described in my post 3798 in Roebeet's 5.0.0 thread.
Rev
rcgabriel said:
Thanks, I had to figure most of this out the hard way a few days ago. I did use the nvflash.exe from Bekit's ZIP, actually, but I likewise had to download the MSI from NVidia's website to get the APX drivers.
Click to expand...
Click to collapse
Hi,
Still trying to get the apx to show up. I am able to get the nvflash window stating it is starting, but in 32 bit. Enter to continue: However after that nothing happens. I tried loading the nvidia usb driver .exe to approach it from a different angle along with the android version at one point in time. All my inputs are non-functioning on the actual VS device. Problem with Windows 7, 64 bit with a nvidia 3D optimus graphics card and nvidia drivers already on my system. The usb program goes through the installation then nothing. Not sure if there is some kind of conflict going on with the driver installation or why I never see apx. Or if the drivers are actually being loaded on to the system. How can I verify if that part of the process is successful and move forward from that standpoint?
Any suggestions on how to get one of the set of the usb driver approaches to fully work?
edirector,
You don't have to "install" the USB, per se. I didn't even use an .exe to install it.
You have to get the USB directory into your "NVFlash" directory. The directory named
"USB" has the NvidiaUsb.inf file in it as well as an "i386" directory and an "amd64" directory in it. The two directories actually have all the drivers your system might need in them.
So you have your nvflash files, your .img files and the USB driver directory in your NVFlash directory. You are ready.
Turn on the G-Tablet (power button) while holding down the (Volume-) button to get into APX mode. You actually don't have to be hooked up to the PC to do this.
Then hook the tablet to the PC using the mini-USB to USB cable.
When you hook up the USB cable, your PC should flash a message telling you it is installing the USB driver -- but it can't because it doesn't know where your USB driver directory is and so will fail.
Once it has failed, click "Start" then "Control Panel" then "Device Manager." On Device Manager you find a device called "APX" listed with a yellow "!" (exclamation point) on it because the load failed. Double-click the "APX" and you will get a driver
info screen which has a "Update Drive" button. Click the update button and when it comes up it will give you the choice of searching the internet or searching the local drives for the drive. Choose the local option and select the "Browse" button out beside it. When you do, do to the NVFlash directory and then the USB directory and point the updater at the "USB" directory with the .inf in it.
When you click next, it should bring up a message saying the driver author is unknown or something like that. You need to tell it to proceed and it will successfully finish loading the drivers.
Now you are ready to flash and need to run "nvflash_gtablet.bat". A black command box will appear and list the flashing process as it occurs. Somewhere in there it gives you a message to press enter to continue -- do so.
When it finishes while still connected to your PC it will boot -- hopefully successfully -- to the normal main screen of Update/software version 2638.
That being done you are back in business. If you get wireless working, you will get a message to update to OTA 3588 almost immediately and that will get you back almost to current. If it doesn't appear quick enough for you, go to the "Update" icon and
manually request it.
I hope this helps you. If you have trouble or questions, Roebeet has put a couple of links to threads myself and others have put together to help others with this process.
I have been somewhat more detailed here because I know your problem and know you were working hard one it. Please don't be offended -- I'm not trying to do anything except make sure the process is right and that it helps you.
Good luck. Let us know how it goes.
Rev
EDIT: For more (maybe similar but with more reference links) on USB driver sources:
http://forum.xda-developers.com/showthread.php?t=989320
I need help...
Your zip and instructions were great - thanks!
However, I still have the same problem that existed before this process. My GTab is boot looping. It gets to the G Tablet screen (after the Viewsonic screen), sits for about three seconds, then reboots.
I've tried a few different recovery options, but none have worked (including following your nvflash instructions precisely). It flashed and rebooted, but same problem.
Any advice? FWIW - this problem just started happening out of the blue, not during an update. Last night it was working fine - today, boot looping.
I can' t say that I have an obvious answer, but can you tell us a little more about what Rom you are running? When it is looping, if you hold down the power button will it turn off correctly? If you press power/volume+ do you in fact get a recover still? The opposite, if you press power/volume- do you get the black APX screen?
My first notion is to suggest installing clockworkmod. You would have to use an external SDcard with a recovery/command file edited to point to /SDcard2. Or you would have to nvflash CWM (which I have never done but I have seen fairly new
instructions for in the Developer Forum.)
If you can get CWM to install, then I would go in and do a factory data wipe. I would find the menu item for partitions and I would repartition to 2048 and 0. And I would wipe the caches.
When I hear about a G-Tablet acting like yours, I worry about the file system.
If none of the above work, do you have a return option? And I don't know much about the RMA option though there is a thread in General about that.
I have not heard of a G-Tab which was totally bricked yet, so I hope my suggestions and those of others will help you get it back to normal.
Good luck. And let us know how it goes?!
Rev
Finally got it running again
Through much trial and error - using NVFlash and CW in various combinations with TnTLite ROMS and stock TnT ROMs - finally got a combination where I was able to get to original stock, boot cleanly, and load TnTlite 5.0. Phew. Three hours of work.
Related
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
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
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?
hi all
i think this tablet is japanes version of G-table
when turn on the tablet ,i dont can see any things ,only white screen (only backlight lcd) . i pressed vol+ and power but nothings
is it possible help me?
sirone said:
when turn on the tablet ,i dont can see any things ,only white screen (only backlight lcd) .
Click to expand...
Click to collapse
The data cable going into the LCD display might have come loose, or, it might be damaged. See this thread. The symptoms are similar.
i checked this cable . is ok.
i read this link ,i bumped the bottom, right corner of the tab but dont change
in addition, how i can test tablet maybe my tablet is dead?
i press and hold vol- and power button but i dont can see any bird .
in addition when i connect tablet to pc , i can see Tegra label in Device manager
even i test backlight sensor ,it work perfect then i think my issue is software.
Also led wifi is on
sirone said:
i press and hold vol- and power button but i dont can see any bird .
Click to expand...
Click to collapse
The birds are a ViewSonic-specific splash screen. It might be something else entirely on your LuvPad. Anyway, since your screen isn't displaying anything except white, looking for the boot splash screen is not useful.
in addition when i connect tablet to pc , i can see Tegra label in Device manager
even i test backlight sensor ,it work perfect then i think my issue is software.
Also led wifi is on
Click to expand...
Click to collapse
All of those point to a HW problem (cables, connector, LCD panel) rather than a SW one. The screen will go white when there is no video signal coming into the LCD panel. Then, only the backlight (white) will be displayed. (This is the reverse of what happens on a CRT monitor which displays black when it isn't receiving any signals.)
I would check those cable(s) and connectors again. Pull out all the cables going into the LCD panel at both ends, and inspect them carefully for breaks as this thread recommends, then plug the cable(s) back in firmly.
Software checks are these.
1. Check bootloader.
Get the nvflash program (the ones used on this board might work too) and the bootloader.bin for the LuvPad AD100 from one of the official firmware update files. Install the nvflash program (and, on Windows, its USB drivers) and then run this command (both the nvflash executable and bootloader.bin should be sitting in the same directory) in a CMD.exe window after you've put the LuvPad into APX mode (on the gTablet, you have to power off, then press both the Vol [-] and the Power buttons--it might be some other button combination on the LuvPad):
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable part.txt[/B]
If the command completes and the part.txt file looks OK, then your LuvPad is running the bootloader just fine.
2. Check Recovery.
Power off the LuvPad, then try putting it into Recovery mode by pressing the Vol [+] and Power buttons at the same time. (Again, those keys work on the gTablet; it might be something else on the LuvPad). After a few seconds, see if you can get into an ADB shell (install ADB first if you need to, or just use Linux). If you have CWM, or some other kind of custom recovery installed, then you will get a shell. The stock recovery may or may not give you a shell.
Code:
C:\SOME\PATH> [B]adb shell[/B]
3. Check ROM.
Power off the LuvPad, then run this adb command and power on the LuvPad. If you've enabled ADB debugging in the ROM (or, it comes enabled by default) and the ROM doesn't have problems booting, then you should see the system logs scrolling by.
Code:
C:\SOME\PATH> [B]adb logcat -v time[/B]
Also, in both the ROM and in recovery mode, if when you connect and disconnect the USB cable, Windows detects the device connection/disconnection, then the HW and ROM/recover are most probably OK, and you may be able to look at the logs to troubleshoot this further. (When you connect the cable in the ROM, a new removable drive may even appear, even though it may show no data in it--I don't use Windows, so I don't know precisely what should happen there.)
if when you connect and disconnect the USB cable, Windows detects the device connection/disconnection, then the HW and ROM/recover are most probably OK
Click to expand...
Click to collapse
yes , i can see windows detect a device .
Luvpad is very similar "Malata SMB-A1011" .i found this link for bootloader and rom :
4pda.ru/forum/index.php?showtopic=237500&st=100
downloaded "usbpcdriver.zip" and setup manually then now i can see "NVidia Android Composite Device" in device manager and a unknown device in NVFlash
But still i need help
sirone said:
now i can see "NVidia Android Composite Device" in device manager and a unknown device in NVFlash
Click to expand...
Click to collapse
1. Please don't use any other commands other than what I've posted above. All of the commands I gave are "safe"--meaning that none of them make permanent changes to your tablet. The command that you're trying to run in the screenshot:
Code:
[B]"nvflash.exe" --bct gtablet.bct ... --create --go[/B]
doesn't look right (why is it using gTablet files?) and it could make your problem worse by bricking the device.
2. I think it is a HW problem (LCD panel, cable, connector). Use a magnifying glass on the cable and the connectors, and a fine-probed continuity tester on the cable, and see if they're OK.
3. If you want to rule out SW problems, then do the tests in reverse order: ROM first, then Recovery, bootloader last.
4. The nvflash command probably didn't work because the device was not in APX mode. Put the LuvPad into APX mode first (Power off, then press Vol [-] and Power), then run my nvflash command. To run the recovery mode test, put tablet into recovery mode first (Power off, then press Vol [+] and Power).
2. I think it is a HW problem (LCD panel, cable, connector). Use a magnifying glass on the cable and the connectors, and a fine-probed continuity tester on the cable, and see if they're OK.
Click to expand...
Click to collapse
i checked, i dont have any lose connection
4. The nvflash command probably didn't work because the device was not in APX mode. Put the LuvPad into APX mode first (Power off, then press Vol [-] and Power), then run my nvflash command. To run the recovery mode test, put tablet into recovery mode first (Power off, then press Vol [+] and Power)
Click to expand...
Click to collapse
I've posted above about i dont can see any change when i use " vol- & power "
too "vol+ & power"
i receive a different version Nvflash but almost all without result.
finally i see this message " UNKnown Device Found " in Cmd page
in addition, i remove battery ,about for 30 second ,when i plug it , i can see the tablet turn on automatically and i dont can turn off with power switch .
o my god
i success for APX mode and now i can see t20 chip and more .
pls help me in continue ...
Hi sirone,
Rajeevvp asked me to assit you since he is busy @ work. Can we start from the beginning? How exactly did your tablet get in this situation (dropped, flashed someothing, just turned on & it started doing it, etc)?
I know you said the connecections are good but have you tried disconnecting BOTH ends of the video cable & reseating it? Were you able do a continutity check on the cable as raj suggested to eliminate the possiblity of a cable problem?
Since none of us have seen or heard of the Luvpad it may help to have some hires photos of the internals (boards, connections, lcd)...anything thing you feel comfortable with removing & taking a photo of may help you (or others that may have the same hardware). I know you said the Luvpad is similar to the Malata A1011. Do you see any designation of the system board...I know the gTablet has SMB-A1002 embossed into the RF cover. While there are a lot similarites in this generation of tablets, the actual system boards layouts (and actual componets) vary significantly.
To me is sounds like you may have multiple problems. You MAY be stuck in an APX loop & you may also (as rajeevvp noted) have a hardware video problem (bad connection, bad cable or even bad lcd panel).
You say that you don't see anything different when you power on with Vol (+) or Vol (-) but if you do it with the USB cable connected to your PC does it detect different hardware when you power on in each mode (APX...Vol- and Recovery..Vol+)...it should detect the tablet differerntly. The issue you are having with nvflash (unknown device found) could be a driver or bootloader isue. Where exactly did you get the nvflash & bootloader for your device?
Also, when starting in Recovery mode (Power 7 Vol+...with USB connected) were you access the tablet via the adb commands raj suggested? If your Windows PC isn't configured/detecting the adb driver you may want to download a live Linux distro (I use Linux Mint 11) & boot your PC off the live DVD so you won't have the driver issues of Windows.
Al
first i should say thx for help
Can we start from the beginning? How exactly did your tablet get in this situation (dropped, flashed someothing, just turned on & it started doing it, etc)?
Click to expand...
Click to collapse
i can say dont know because i get this tablet with this problem
some hires photos of the internals (boards, connections, lcd)...anything thing
Click to expand...
Click to collapse
i attached
You say that you don't see anything different when you power on with Vol (+) or Vol (-)
Click to expand...
Click to collapse
in post no.9 i mention about success about APX mode
in addition i use Win vista32
Need bootloader.bin
sirone said:
o my god
i success for APX mode and now i can see t20 chip and more .
pls help me in continue ...
Click to expand...
Click to collapse
Where did you get the nvflash package you are using? Check the folder for a file called bootloader.bin...that is what nvflash is looking for. It can't find it, thus you get the error. Check your nvflash folder & see if you have a file by a different name (wih a .bin extention). You can try the gTablet bootloader if you don't have a Luvtab specific one (it may or may not work though since we've never tried it) & you can get it from here http://dl.dropbox.com/u/36150173/backup_gtablet_rev2.zip.
Al
i checked. in NVFlash folder i have bootloader.bin but i dont understand why nvflash couldnt found it
CD, cable & Hannspad
sirone said:
i checked. in NVFlash folder i have bootloader.bin but i dont understand why nvflash couldnt found it
Click to expand...
Click to collapse
Did you type in the nvflash command from a command prompt (& if so had you change the current directory to the one where nvflash & bootloader.bin are located) or did you created a batch file?
On the video cable...to check the end that connects to the actual lcd display you must remove the metal bracket to get to the display. Did you do that & remove & reseat the cable?
Also, from the markings on the board it, your board appears to be the EXACT same board as used in the Hanspree Hannspad. There is a forum on SlateDroid http://www.slatedroid.com/forum/234-hannspree-hannspad/ dedicated to the Hannspad...you may wnat to check it out when you have a chance.
Al
Did you type in the nvflash command from a command prompt (& if so had you change the current directory to the one where nvflash & bootloader.bin are located) or did you created a batch file?
Click to expand...
Click to collapse
i dont can understand your means . is it possible tell again
describe my process :
in start , type CMD and ,cmd appear in dos .
c:\user\sirone\nvflash\nvflash --bl bootloader.bin --getpartitiontable part.txt
similar this command and nvflash file there is in sirone path
a new test :
in your link i found page .slatedroid.com/topic/25805-hannspad-backup-brick-recovery-ics-installation-destruction-guide/#entry276544
and DL a nvflash file .there is a file with name "RunME.bat" ,i run and choose the backup menu item .i see nvflash download partition 2 - 14 and atlast a error in Part 11 .
i think this process can help
Save as a .bat
sirone said:
i dont can understand your means . is it possible tell again
describe my process :
in start , type CMD and ,cmd appear in dos .
c:\user\sirone\nvflash\nvflash --bl bootloader.bin --getpartitiontable part.txt
similar this command and nvflash file there is in sirone path
Click to expand...
Click to collapse
Download the file & rename it to getpartitiontable.bat. Paste it into your nvflash folder & double click on it (when your tablet is in APX mode & connected). If it runs sucessfully post the partition table.
Al
i receive this :
PartitionId=2
Name=BCT
DeviceId=19
StartSector=0
NumSectors=1536
BytesPerSector=2048
PartitionId=3
Name=PT
DeviceId=19
StartSector=1536
NumSectors=64
BytesPerSector=2048
PartitionId=4
Name=EBT
DeviceId=19
StartSector=1600
NumSectors=1024
BytesPerSector=2048
PartitionId=5
Name=MBT
DeviceId=19
StartSector=2624
NumSectors=64
BytesPerSector=2048
PartitionId=6
Name=MSC
DeviceId=19
StartSector=2688
NumSectors=8192
BytesPerSector=2048
PartitionId=7
Name=BLO
DeviceId=19
StartSector=10880
NumSectors=2048
BytesPerSector=2048
PartitionId=8
Name=OGO
DeviceId=19
StartSector=12928
NumSectors=16384
BytesPerSector=2048
PartitionId=9
Name=SOS
DeviceId=19
StartSector=29312
NumSectors=8192
BytesPerSector=2048
PartitionId=10
Name=LNX
DeviceId=19
StartSector=37504
NumSectors=8192
BytesPerSector=2048
PartitionId=11
Name=APP
DeviceId=19
StartSector=45696
NumSectors=102400
BytesPerSector=2048
PartitionId=12
Name=CAC
DeviceId=19
StartSector=148096
NumSectors=111104
BytesPerSector=2048
another search :
i find this link sumapho.wordpress.com/2010/12/18/luvpadnvflash%E3%81%A7rom%E7%84%BC%E3%81%8D/
and translated .this is luvpad and end of page i see similar above text .compare two together and found different in part 6 and 7 .
pls see this different :
mine
PartitionId=6
Name=MSC
DeviceId=19
StartSector=2688
NumSectors=8192
BytesPerSector=2048
PartitionId=7
Name=BLO
DeviceId=19
StartSector=10880
NumSectors=2048
BytesPerSector=2048
link
PartitionId = 6
Name = BLO
DeviceId = 19
StartSector = 2688
NumSectors = 2048
BytesPerSector = 2048
PartitionId = 7
Name = MSC
DeviceId = 19
StartSector = 4736
NumSectors = 8192
BytesPerSector = 2048
is it possible We conclude?
Which
sirone said:
i receive this :
PartitionId=2
Name=BCT
DeviceId=19
StartSector=0
NumSectors=1536
BytesPerSector=2048
PartitionId=3
Name=PT
DeviceId=19
StartSector=1536
NumSectors=64
BytesPerSector=2048
PartitionId=4
Name=EBT
DeviceId=19
StartSector=1600
NumSectors=1024
BytesPerSector=2048
PartitionId=5
Name=MBT
DeviceId=19
StartSector=2624
NumSectors=64
BytesPerSector=2048
PartitionId=6
Name=MSC
DeviceId=19
StartSector=2688
NumSectors=8192
BytesPerSector=2048
PartitionId=7
Name=BLO
DeviceId=19
StartSector=10880
NumSectors=2048
BytesPerSector=2048
PartitionId=8
Name=OGO
DeviceId=19
StartSector=12928
NumSectors=16384
BytesPerSector=2048
PartitionId=9
Name=SOS
DeviceId=19
StartSector=29312
NumSectors=8192
BytesPerSector=2048
PartitionId=10
Name=LNX
DeviceId=19
StartSector=37504
NumSectors=8192
BytesPerSector=2048
PartitionId=11
Name=APP
DeviceId=19
StartSector=45696
NumSectors=102400
BytesPerSector=2048
PartitionId=12
Name=CAC
DeviceId=19
StartSector=148096
NumSectors=111104
BytesPerSector=2048
Click to expand...
Click to collapse
Is this from the Hannspad backup or my getpartitiontable?
adb shell adb shell "exec '/system/bin/sh' failed: No such file or directory (2)"
hello people but once I need your help
someone deleted all folders from my TF101
'm trying flashing mode with adb but is giving this error
adb shell "exec '/ system / bin / sh' failed: No such file or directory (2)"
what can I do? regarding this error.
try fastboot mode but this does not recognize the device
help me please
even more
Fastboot isn't available on the TF, have you tried APX mode?
Hold volume-up while the TF is off, then press power and wait a second, the screen will stay blank but you'll enter apx mode. If you then plug in the TF it should be recognized by your computer.
Then you can use the NvFlash tool to completely restore your tf to stock, and if you want root you can then manually or use one of the many tools (Mine/1-click/easyflasher) to do this...
Links --
NvFlash files to get back to stock ASUS version .27 -- Also includes driver folder called 'usbpcdriver' which you install to get your computer to see the TF in APX mode. Pick WW for a tablet outside of the United States and US for a US tablet.
You should then download wheelie.zip from here - Wheelie - NvFlash for TF101.
Extract all files from the wheelie.zip and place them in the .zip of the NvFlash version you downloaded, overwrite any files that already exist.
Make sure the driver properly installs, you can run in command prompt:
Code:
pnputil -a C:\Users\[username]\Downloads\TheNvFlashzip\Usbpcdriver\Nvidiausb.inf
Be sure to do this with the TF unplugged, the drivers will install on next plugin.
-Or use the manually search for a driver option when windows fails to find the proper drivers and manually navigate to the usbpcdriver folder.
Only do this if apx mode isn't detected.
--
From here you have everything you need, and you will need to find out your TF's Serial Number to find the SBK (Secure Boot Key) version. It can be found on a sticker on the bottom of your tablet by the charge port, or on the box that the device came in.
The serial will be rather long, you're only interested in the first 3 entries:
-If it reads B60 or a lower number than 60, run the 'reflash sbkv1.bat' in the folder, which will reflash your tf completely to stock assuming it's plugged in during APX mode and the drivers were properly installed.
-If it reads B70 or a higher number than 70, run the reflashsbkv2.bat to NvFlash the device.
--
This process should take a little while, then the device should boot up like new, assuming everything was done properly..
If you wish to root afterwards, use either my PERI tool (link below) or another tool, one can be found in General and a few can be found in the Development threads.. Or manually root with Wolf's method 3. Currently all methods require a pc with usb connection and proper adb drivers installed, my tool and others assist you through this process.. it's very similar to above Nvflashing driver process.
Thing O Doom said:
Fastboot isn't available on the TF, have you tried APX mode?
Hold volume-up while the TF is off, then press power and wait a second, the screen will stay blank but you'll enter apx mode. If you then plug in the TF it should be recognized by your computer.
Then you can use the NvFlash tool to completely restore your tf to stock, and if you want root you can then manually or use one of the many tools (Mine/1-click/easyflasher) to do this...
Links --
NvFlash files to get back to stock ASUS version .27 -- Also includes driver folder called 'usbpcdriver' which you install to get your computer to see the TF in APX mode. Pick WW for a tablet outside of the United States and US for a US tablet.
You should then download wheelie.zip from here - Wheelie - NvFlash for TF101.
Extract all files from the wheelie.zip and place them in the .zip of the NvFlash version you downloaded, overwrite any files that already exist.
Make sure the driver properly installs, you can run in command prompt:
Code:
pnputil -a C:\Users\[username]\Downloads\TheNvFlashzip\Usbpcdriver\Nvidiausb.inf
Be sure to do this with the TF unplugged, the drivers will install on next plugin.
-Or use the manually search for a driver option when windows fails to find the proper drivers and manually navigate to the usbpcdriver folder.
Only do this if apx mode isn't detected.
--
From here you have everything you need, and you will need to find out your TF's Serial Number to find the SBK (Secure Boot Key) version. It can be found on a sticker on the bottom of your tablet by the charge port, or on the box that the device came in.
The serial will be rather long, you're only interested in the first 3 entries:
-If it reads B60 or a lower number than 60, run the 'reflash sbkv1.bat' in the folder, which will reflash your tf completely to stock assuming it's plugged in during APX mode and the drivers were properly installed.
-If it reads B70 or a higher number than 70, run the reflashsbkv2.bat to NvFlash the device.
--
This process should take a little while, then the device should boot up like new, assuming everything was done properly..
If you wish to root afterwards, use either my PERI tool (link below) or another tool, one can be found in General and a few can be found in the Development threads.. Or manually root with Wolf's method 3. Currently all methods require a pc with usb connection and proper adb drivers installed, my tool and others assist you through this process.. it's very similar to above Nvflashing driver process.
Click to expand...
Click to collapse
I tried this several times but giving error
Using SBK type 2.
Using bootloader: ´bootloader.bin´.
Using BCT: ´transformer.bct´.
_________________________________
= Chip UID: 0x299648565018420119
- Incorrect SBK or SBK type selected. nverror: 0x4
connetion failed Nverror 0x30011
acacioxda said:
I tried this several times but giving error
Using SBK type 2.
Using bootloader: ´bootloader.bin´.
Using BCT: ´transformer.bct´.
_________________________________
= Chip UID: 0x299648565018420119
- Incorrect SBK or SBK type selected. nverror: 0x4
connetion failed Nverror 0x30011
Click to expand...
Click to collapse
You used the wrong sbkvX.bat file, as stated in the error message.
use sbkv1. If that doesn't work then you have the 3g version or the slider, and are probably SOL.