Database Info

Some info about nvflash and Windows (LONG)

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.

[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

Frankenkaisers for different radio versions

In this threat i gonna upload some patched frankenkaisers for different versions.
With "FrankenKaiser" you can unbrick "task 2a" bricks:
There is no SPL, Splash and OS present as "task 2a" formats the entire application area.
Before FrankenKaiser there was no method available to unbrick and therefore they were called "hard bricks"
With frankenkaiser you can also revive kaisers where you don't see anything on it but is detectable (after turning on your device) in windows as an other device:
you got stuck in the OEMSBL and you can only talk to your device with mtty.
Credits goes to Jocky Wilson who created the original frankenkaisers. (Paypal to [email protected])
I've only changed them to work with different versions.
These versions are created at forum user requests.
Method to dump your rom:
1. connect your bricked phone and power it on
2. connect with MTTY to diag port COM#: (look up # in device manager)
3. type "radata" followed by enter (you'll see a parameter error message)
4. type "GO2AMSS" followed by enter
5. your phone should now change to "QC download mode"
6. use "QPST Memory Debug" tool to dump smi.bin and ebi.bin
7. zip smi.bin and upload it to Rapidshare (or any fileshare service) and send me the link
oemsbl: V1.9309
Radio: V1.71.09.XX
Verified.

oemsbl: V1.9519
Radio: V1.70.19.XX
20110823: new version uploaded

oemsbl: V1.9529
Radio: V1.65.29.21

oemsbl: V1.9518
Radio: V1.70.18.xx

Frankenkaiser for other versions can be created in this thread

Excellent work massivekid, just what I needed to fix the 600+ bad blocks on my spare Kaiser! Thank you!
You da MAN!!!

Turns out I cannot use any of this because my laptop has NO COMM ports.
Unless I can find a USB to serial adapter and force a COMM port, I'm stuck.

You don't need a com port. If your phone is in OEMSBL then it will ask for a different driver. This driver will create a virtual com port on your computer thru USB.

First of all, thanks for creating frankenkaisers for different radio versions,
but I need some help, my radio is version V1.71.09.XX, I did all the steps to rescue the phone up to step 11, and when I connect the usb to computer, windows shows an error and wont recognize the usb connector, not allowing me to flash the hard spl through usb. would be absolutelly happy if you would help me solving this.

Do you see the tricolor screen?
Did you disconnect and reconnect the usb cable again and do you see USB on the tricolor screen?
if no usb is seen, redo steps 7-10 again (after pulling your battery) but this time in step 9 run FrankenKaiser with the other SPL "sspl-0.92-jumpspl-force-usb.nb".
this will force usb detection.

i redid steps 7-10 at least 10 times already, tri-color screen shows up with the first spl and gives problem when connecting the usb, when I try the 0.92 spl the screen stays black (I tried connecting the usb even with it staying black and the same error message showed up)
*During the whole step by step the only difference I saw between my results and the screenshots was the oesmbl version on screenshot 7, where instead of a "2" there was a "1"

And did you tried the "sspl-0.92-jumpspl-force-usb.nb" at step 9?

If you enter mtty and type ? or h what is the output of the command?
if you see a lot of commands, then your device is security unlocked.
the "sspl-0.92-jumpspl-force-usb.nb" file is to force USB connection so you can connect with usb.
If that doesn't work, try with the original spl and after cego, pull the usb cord quickly and if the tricolor appears, try to connect the usb again.

after typing "h"
Available monitor commands are:
? [command]
h [command]
mb [StartAddr [Count [Filler]]]
mh [StartAddr [Count [Filler]]]
mw [StartAddr [Count [Filler]]]
setboot [0/1/2/3]
setatcmd [0:SIO/1:UART/2:USB/3PRAM]
setsmdloop [0:disable/1:enable]
setmpatch [0x1: CPU Freq/0x2: acoustic/0x4: simdoor/0x8: RTC]
setiot [0isable/1:Enable]
eraseall [erase all setting flags]
setdiag [0:USB/1:UART/2PRAM/3:SIO]
partition
checksum
format
setinfo
readadc
cego
setgpio
getgpio
gpio
version
powerdown
platformid
radata
showexplog [n]
usbdppulldown [n]
usbdmpulldown [n]
usbdppullup [n]
usbdmpullup [n]
Headsetpullhigh [n]
rfid
wpmic [PM_VREG] [0/1]
the "sspl-0.92-jumpspl-force-usb.nb" gives only blackscreen on the phone, no tri-color.
I`ll try the first spl and take out the usb quickly.
Same result after pulling usb quickly after doing the command "cego"
Tried the same with sspl-0.92 and the blackscreen apears the same way, and the error message on windows is the same:
(translation might no be exact because my windows is in portuguese)
"One of the usb devices connected to this computer had a problem and windows can not recognize it. to get help click on this message.
After clicking it shows a windows with a root usb hub, 4 usb doors being one of them the one where the phone is connected with a red X before it.
Ps.: I`m not exactly sure, and I don`t know if this might influence on anything, but if I remember right, when first unlocking my phone, the JumpSPL1.56-KAIS.exe wasn`t effective, I needed using one of the other 2 jumpspl available on that thread.

With "sspl-0.92-jumpspl-force-usb.nb", you can also try after cego to press and hold camera to enter tricolor bootloader mode
Also you can try this spl: SPL3.56-patch-nostuckinSPL-FORCEUSB.nb at step 9?
Just unzip it in your folder and use it.

when using the sspl0.92 it wont go out of the blackscreen (even holding camera button), and the same error message is shown on usb
when using the new spl3.56 the usually blinking green led stay orange after the cego command and the screen stay black, tried holding the camera button, to no effect in either "spls".
Same usb error on three spls...

The error states that the device is halted and is not handling usb functions anymore. The one that has the tricolor screen, should work, but some devices are not detecting the usb correctly. Therefore the usb force spl are created.
I'll try to find out how we can overcome this...

thank for your attention and taking your time to help me, hope you can find a solution, surelly you will help many kaiser owners that got many "bad blocks" in memory...
(shouldn`t ever have tried to put android on nand...)
keep me informed on any kind of progress and let me help you on testing.

Ok, try this one:
Remove and reinsert battery, then hold the send button and power on. Connect with MTTY (COMn) and this time enter "dload" to put phone in dload mode Continue with step 9.
Try SPL1.56-KAIS-unbricker.nb then or sspl-0.92-jumpspl-force-usb.nb

tried it, no letters under the: "Just be patient while I'm working ..."
believe the phone hunged up, will try again.
(also tried using the send button whenever turning the phone on in the steps 7 through 10, nothing different happened, I believe the jumpspl can only be loaded while in setboot 1 I`m thinking about trying to use "cego" without typing setboot 0 before...)
Phone will absolutelly lock if I dont enter setboot 1 in the step before typing dload,
frankenkaiser isn`t able to access it (no letters under te message to wait) and it locks after the frankenkaiser attempt (wont accept mtty commands), removing battery returns to "normal" (as in dead kaiser).

A self inflicted wound

Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.

hushpup131 said:
Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
Click to expand...
Click to collapse
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053

jamcar said:
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
Click to expand...
Click to collapse
I am not able to get into the APX mode. The basis of my belief is there is no audible signal (USB to PC) and there is no new window opening inviting me to explore a new drive.

I have disconnected the battery both short term as well as over night, no response from the power only and power plus volume – buttons.
The charge light has turned green; no response from the buttons.
Measuring the voltage at the charger tip read 12+ volts. I am using a new USB to PC cable. Out of curiosity I unplugged the battery connector and re-connected to see the charge light switch off and on while the charger was connected. As a novice here, I suspect that test eliminated the charging circuit as a fault.
I'm in UBUNTU
loaded and extracted gtab.nvflash.1.1.branch.20110422 with cwmv8.zip
the response says:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
@set /p batuserinput=Press enter to continue:
- what does this mean?

1. Is there any sort of display brightening (even briefly?) after you power on? In APX mode, for example, the screen will brighten slightly, then go dead again.
2. Try this test on Ubuntu to see if the tablet has gone into APX mode:
Code:
[I]Power off gTab.
Power on gTab using Power & Vol [-].[/I]
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[18045.279886] usb 1-1.2: new full speed USB device number 6 using ohci_hcd
[18045.384823] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7820[/B]
[18045.384830] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18045.384835] usb 1-1.2: Product: APX
[18045.384839] usb 1-1.2: Manufacturer: NVIDIA Corp.
$
A USB product id of 7820 indicates APX mode on the gTab.
Post the exact output (if any) of your run here.
For reference this is the output when the gTab is running either CWM or the ROM:
Code:
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to the gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[17516.799429] usb 1-1.2: new full speed USB device number 5 using ohci_hcd
[17516.911353] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7100[/B]
[17516.911361] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17516.911366] usb 1-1.2: Product: NVIDIA Harmony
[17516.911370] usb 1-1.2: Manufacturer: NVIDIA
[17516.911374] usb 1-1.2: SerialNumber: 0270308341006257
$
The product id will be 7100.

[email protected]:~$ coonected USB to Gtab, power button plus vol minus 2 minutes
coonected: command not found
[email protected]:~$ sudo dmesg -c >/dev/nul
bash: /dev/nul: Permission denied
[email protected]:~$ pwd
/home/ubuntu
[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ pwd
/
[email protected]:/$ sudo dmesg -c >/dev/null
[email protected]:/$ dmesg
[email protected]:/$
[email protected]:/$

It's not surprising that you got no output--I screwed up. The sequence of steps was incorrect: the cable has to be connected between the 2 dmesg commands. Please repeat.
(If you want to insert inline comments on the command line do it like this:
Code:
$ [B]# This is just a comment.[/B]
The shell will ignore everything from the `#' character to the end of the line.)
And, this video is what I recommend to people whose bootloader seems to be trashed--which is what I think your problem is: How to unbrick your Viewsonic G-Tablet

[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$

The first 2 commands are not needed:
hushpup131 said:
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
Click to expand...
Click to collapse
Yeah, as I suspected, its a bad bootloader and/or other critical partition problem.
If you are certain that the USB cable and ports are OK (check using another device--try a "sudo adb devices" command with a phone, for instance) and you ran the second dmesg command after connecting the USB cable (otherwise, power off and do the sequence again), then your only option now is to follow the K1 pad-shorting procedure shown in the video.
BTW, you didn't answer question #1 in post #5, above. Is there any change in the display brighness after powering on?

[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
[13557.908045] usb 4-1: new low-speed USB device number 4 using uhci_hcd
[13558.145227] input: Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00 as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input17
[13558.145525] generic-usb 0003:045E:00E1.0003: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00] on usb-0000:00:1a.1-1/input0
[13558.256080] usb 1-4: new high-speed USB device number 6 using ehci_hcd
[13558.397196] scsi9 : usb-storage 1-4:1.0
[13559.397403] scsi 9:0:0:0: Direct-Access Motorola A855 0001 PQ: 0 ANSI: 2
[13559.398816] sd 9:0:0:0: Attached scsi generic sg3 type 0
[13559.403602] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[email protected]:~$
question one, post five... there was no change in the display
There was no change in the display after shorting K1

hushpup131 said:
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
Click to expand...
Click to collapse
Your USB cable seems OK, but, I don't like that line above. Can you describe exactly what you did when you captured that output?
And, run through that dmesg sequence once again exactly as described and post the output. Also, connect the gTab directly to a USB port, and not through a hub.

[Q] broke asus tf101 eee pad transformer

Hi.
It's been some time since i tried fixing my Asus Transformer...
The problem is : If it has battery life. It boot's and gets stuck on the first screen.
With the logo "eee pad" .
If i turn it off, it automaticly reboots and gets stuck in the same screen.
If i try to get into recovery mode.
Vol down, Powerup... and the vol up , i can see the few line's of code , saying it will boot into recovery mode.
but while trying to start recovery mode the icon changes to a fallen android and an "! triangle above it
I've been looking around forums evrywhere but i cant find a solution for my exact problem.
can anyone help?

Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.

Lethe6 said:
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Click to expand...
Click to collapse
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?

DarkCloud98 said:
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
Click to expand...
Click to collapse
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
http://www.xdafileserver.nl/Files/A...OMS/ICS .27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z

*Detection* said:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
Click to expand...
Click to collapse
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926

DarkCloud98 said:
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
Click to expand...
Click to collapse
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin

*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Click to expand...
Click to collapse
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash

DarkCloud98 said:
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
Click to expand...
Click to collapse
I edited my post with quick instructions
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin

*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
Click to expand...
Click to collapse
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server

DarkCloud98 said:
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
Click to expand...
Click to collapse
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF

*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help

DarkCloud98 said:
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
Click to expand...
Click to collapse
You could flash the pre-rooted versions too although I think it's easy enough to root yourself these days
This is the XDA Fileserver for different ROMs if you need them
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)
I was just reading someone else who had the same display stuck on their TF while trying to use NVFlash and they said re-downloading the ROM and trying it again fixed it
So if this fails for some reason, try another NVFlash ROM from the XDA Server

*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?

DarkCloud98 said:
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
Click to expand...
Click to collapse
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
http://forum.xda-developers.com/showthread.php?t=1123429

*Detection* said:
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
Click to expand...
Click to collapse
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?

DarkCloud98 said:
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
Click to expand...
Click to collapse
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
http://www.portableandroid.co.uk/androidDL/new Windows.zip

*Detection* said:
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
Click to expand...
Click to collapse
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
EDIT: And the other NvFlash version you linked me, does the same...after it being sent, the CMD closes and thats it

DarkCloud98 said:
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
Click to expand...
Click to collapse
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way

*Detection* said:
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
Click to expand...
Click to collapse
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!

DarkCloud98 said:
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
Click to expand...
Click to collapse
Great news! Linux vs Linux did the trick
How long have you been without your TF until now? It'll be like having a new toy again I would imagine