When setting up to nvflash my G-Tablet to recover from an install problem, I couldn't flash because my computer couldn't find the driver to install that would let my Windows 7 64-bit PC talk to my G-Tablet. Turns out that the file set I was using for nvflash did not have the drivers in it.
Per Roebeet's sticky thread I went to:
http://db.tt/Wm25t7U
and downloaded the Windows files:
nvflash_gtablet_2010110500.zip
nvflash_windows_20100500.zip
The second file with "windows" in the middle has the nvflash program in it and also has an Android USB .inf file listed in it. After working with it, however, I found that it does not have the drivers to go with the .inf file. So I searched all over Nvidia's site and everywhere else looking for USB drivers.
Then I remembered that I had downloaded a copy of Advent Vega's USB files while researching one day. I extracted it and put it in my NVFlash folder and tried flashing again.
When I connected my tablet to the PC, the PC immediately tried to load a driver -- but since it didn't know where my files were it failed. I then went to Start/Control Panel/Device Manager and found APX listed in the devices with a yellow "!" (exclamation point) on the icon. I then selected the APX item and found the "Update Driver" button and clicked it. When it ask where to search, I took the local computer manual selection choice and told it to Browse.
I then pointed Browse (and the USB install) at the "USB" directory under "SystemUSB" in my NVFLash folder. (The SystemUSB folder actually has a "Flash USB driver" folder under it with the "USB" folder under it.) I suppose when you extract from the original you could just put the "USB" folder in the NVFlash directory.
When pointed at the "USB" directory, the driver installed and I was ready to nvflash.
I did this myself successfully. I have read posts from two other folks who also have used this successfully. So I believe it works fine.
But, of course, I urge you use caution and can't promise something could go wrong. (Disclaimer complete.)
The USB driver download is at:
http://www.myadventvega.co.uk/
Find the "Downloads" tab in the middle of the page and click on "USB System Driver" to get the files.
I hope this helps.
Rev
I also posted the files in one of the nvflash related threads here.. if you have the msi you can do this:
msiexec /a %1 /qb TARGETDIR=%~d1NVtemp
move "%~d1\NVtemp\PFiles\NVIDIA Corporation\%~n1\usbpcdriver" %~d1usbpcdriver
thats a batch file.. and it extracts the msi without installing.. into <drive>\NVtemp\
%1 = file name
%~n1 = file name without extension
%~d1 = drive of file name
windows will fill in the blanks if you drag and drop the msi file onto the batch file you create.
fyi latest is tegra_ventana_froyo_20110207.msi .. well technically it is tegra_ventana_gb_20110222.msi - but they both have 01/31/2011 driver inf and 06/24/2010 dll files - so... not that new
this is the apx drivers rar'd up. from tegra_ventana_froyo_20110207.msi
http://forum.xda-developers.com/attachment.php?attachmentid=535715&d=1299488454
Listed below is a link from Blades which provides the USB drivers we need without
having to load the whole SDK to get to them:
http://forum.xda-developers.com/attachment.php?attachmentid=535715&d=1299488454
I hope he doesn't mind my moving the link over here since I have been trying to get
this info together where people having trouble can find it. Thanks to him for the info.
rev
I posted it here first.. but no prob.. those drivers worked right away.. make sure to point to the inf file and not the subdirs AMD64/i386.. as they only contain dll files
Blades,
hmmm. I would have swore your edit was not there when I wrote my post. Certainly you can see that there would be no reason to re-post otherwise!!! Your edit was way before my post
unless there's something weird with the time stamp. Or maybe my tired old head is just working weirder than usual today.
Either way, your work is appreciated and you should get the credit for it. Thanks,
Main thing for me is that I am trying to solve the problem that people didn't have the needed USB drivers. Now we have multiple sources.
Rev
All,
Otreblada posted the following message in a thread over in General. Since it provides a download source for the NVFlash stuff we are talking about, I have copied it over here.
His work, not mine. It contains the nvflash file, image files and USB subdirectory needed to nvflash your tablet back to stock. I have not used it. He says it works fine.
"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
butchconner said:
When setting up to nvflash my G-Tablet to recover from an install problem, I couldn't flash because my computer couldn't find the driver to install that would let my Windows 7 64-bit PC talk to my G-Tablet. Turns out that the file set I was using for nvflash did not have the drivers in it.
Per Roebeet's sticky thread I went to:
http://db.tt/Wm25t7U
and downloaded the Windows files:
nvflash_gtablet_2010110500.zip
nvflash_windows_20100500.zip
The second file with "windows" in the middle has the nvflash program in it and also has an Android USB .inf file listed in it. After working with it, however, I found that it does not have the drivers to go with the .inf file. So I searched all over Nvidia's site and everywhere else looking for USB drivers.
Then I remembered that I had downloaded a copy of Advent Vega's USB files while researching one day. I extracted it and put it in my NVFlash folder and tried flashing again.
When I connected my tablet to the PC, the PC immediately tried to load a driver -- but since it didn't know where my files were it failed. I then went to Start/Control Panel/Device Manager and found APX listed in the devices with a yellow "!" (exclamation point) on the icon. I then selected the APX item and found the "Update Driver" button and clicked it. When it ask where to search, I took the local computer manual selection choice and told it to Browse.
I then pointed Browse (and the USB install) at the "USB" directory under "SystemUSB" in my NVFLash folder. (The SystemUSB folder actually has a "Flash USB driver" folder under it with the "USB" folder under it.) I suppose when you extract from the original you could just put the "USB" folder in the NVFlash directory.
When pointed at the "USB" directory, the driver installed and I was ready to nvflash.
I did this myself successfully. I have read posts from two other folks who also have used this successfully. So I believe it works fine.
But, of course, I urge you use caution and can't promise something could go wrong. (Disclaimer complete.)
The USB driver download is at:
http://www.myadventvega.co.uk/
Find the "Downloads" tab in the middle of the page and click on "USB System Driver" to get the files.
I hope this helps.
Rev
EDIT: 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/tegra/files/android_tegra_froyo_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.
Click to expand...
Click to collapse
When you unzip those 2 nvflash zip files do they containany zip files within them? When icicles I see abunch of files and a zip file.
isu205,
I don't remember any .zip files. The "nvflash" file does start off with an .inf file, but that is the USB .inf file that does not have the drivers with it (which is one of our problems.
If you:
1. Download the Advent Vega USB files
2. Down load and extract the two .zip files roebeet suggested.
Then put those files in a NVFlash subdirectory -- your are ready to nvflash.
That's all you will need to restore to the older bekit stock version.
(I think if you download the otreblada file it has the above already in it.)
Rev
P. S. -- You can find, download and install the nvidia SDK, and it will give you
the same files plus more -- but it also adds some complexity.
You pays your money and takes your choice!!!
EDIT: I double-checked and the answer is NO. No zip files I could find.
I'm a linux guy but do have a Win 7 Starter netbook. A while back I installed everything (sdk and USB driver)? necessary to grab screenshots using adb and ddms or QtADB and everything works well.
Anyway, does this mean all I need on the netbook is:
nvflash_gtablet_2010110500.zip
nvflash_windows_20100500.zip
to get nvflash up and running?
joe2262,
Yes, I think you should be good to go as you have described. Once you install the
USB drivers, or once ADB is installed in the SDK with its drivers -- the drivers stay in
the system and are activated when you connect the tab and PC.
And actually, I've never done it this way, but if you have the SDK you should have
the nvflash_windows-20100500 installed. All you would need is the .img files from
nvflash_gtablet_2010110500.zip (and the ngflash_gtablet.bat file which runs the flash
which is in the other .zip file).
Rev
I hope some of you guys can help me, didn't find any similar to my problem.
I am not able to restore a TWRP nandroid via TWRP and a CWM nandroid via CWM anymore.
The backup finishes correctly in both of the recovery systems, but when I want to restore it they don't show up.
I can't access the folders sdcard/clockworkmod/ or sdcard/twrp/backup to copy these nandroids to my pc.
I tried it via MTP: sdcard shows up but the directories aren't listed in my structure. A reboot doesn't solve it(either PC nor cellphone).
In Root Explorer the folders also don't show up.
I tried clicking through every folder I found when I was browsing my file structure on my cellphone.
Then I found a folder /mnt/shell/emulated/TWRP/ and /mnt/shell/emulated/clockworkmod/ where I finally found my missing files.
I can't see these folders via MTP, only via Root Explorer. So I tried to copy them to the root of my sdcard.
That took some time, no errors when copying etc.
The folders are not there. They just appear in the /mnt/shell/ folders mentioned above.
What do I need to do to restore my nandroids? What did I do wrong?
Hi! i did a root with motochopper..and after it when i wanted to transfer a file from pc to a folder of the s 4 i saw a message like this the device stop responding or is disconnected...but when i transfer a file outside the folders i can and its all ok.So i did a reset and i installed the original german firmware that there is on net but after the reset and after i installed this firmware....i cant still transfer files inside the galaxy s 4 folders..but outside them i can.So i guess, is not the root? is a characteristic of the s 4? if not how can i solve this..i have windows 7.
Edit i rooted the phone with another method found on net..now i can put a file in many folder but not in the obb folder..why?
not entirely sure why it is like that. but the easiest fix is to move the file you want to put into obb somewhere else on your phone and then use a root explorer on your device to move it into obb.
hello,
i have a problem when i copy files via usb cable from my pc to my device.
it only occurs if the files are a little larger. i use a custom rom on my g2 and if i want to copy the new version of the rom to my device (181 mb) copying stops just before the end and i have to cancel. Then i have to reconnect my g2. After that i copy the rom zip again and its successfully.
but if i copy gapps (83 mb) its directly copied successfully.
i have the problem on now two custom roms and the problem was not always there only for some time.
and i have tried it with usb debugging enabled and disabled... same problem.
any suggestions to solve the problem?
I recently flashed the stock android lollipop tgz file on my nexus 7. I rooted it, and then wanted to restore my nandroid backup. But, the backup does not appear in the recovery menu. I couldn't also copy the backup files to the tarp folder (no such folder existed, and when I tried making one using es file explorer or root explorer, it gave an error message.) How do I fix this problem. Please help guys I am sort of new to the forum[emoji16]
Same problem here. It does show up but it's a 0 bytes file last modified in 1970 (start of unixtime)
This is on my Nexus 4 though. Flashed manually with official images from Google and rooted with SuperSU.
- make sure you're using the latest twrp recovery for your device. get the latest img file for grouper (nexus 7) and mako (nexus 4) here: http://techerrata.com/browse/twrp2
- if you look around the forums, you'll find that people have had similar issues since lollipop. forget about trying to access twrp folder in android/es explorer for now (BTW droiderrr18 is probably getting the error when trying to create the folder because it's already there, just doesn't look like a folder and can't be opened, it looks like the 0 byte file looking thing LooieENG mentioned).
What you want to do instead is boot into twrp recovery and connect to your computer. you should be able to access your folders and files in MTP connection from Windows and move to your old backup that way. if not you can always use adb push command. the backup folder for twrp is storage/sdcard0/TWRP/BACKUPS
you can also do a new backup and find it, then move your old backup there to restore.
(side note: twrp also has its own file manager where you can see and if necessary manipulate your files, but be sure you know what your doing in there)
dtg7 said:
- make sure you're using the latest twrp recovery for your device. get the latest img file for grouper (nexus 7) and mako (nexus 4) here: http://techerrata.com/browse/twrp2
- if you look around the forums, you'll find that people have had similar issues since lollipop. forget about trying to access twrp folder in android/es explorer for now (BTW droiderrr18 is probably getting the error when trying to create the folder because it's already there, just doesn't look like a folder and can't be opened, it looks like the 0 byte file looking thing LooieENG mentioned).
What you want to do instead is boot into twrp recovery and connect to your computer. you should be able to access your folders and files in MTP connection from Windows and move to your old backup that way. if not you can always use adb push command. the backup folder for twrp is storage/sdcard0/TWRP/BACKUPS
you can also do a new backup and find it, then move your old backup there to restore.
(side note: twrp also has its own file manager where you can see and if necessary manipulate your files, but be sure you know what your doing in there)
Click to expand...
Click to collapse
I have the same problem. I need to access its data.f2fs.winxxx files for restoring my backed up apps using Nandroid Manager, which cannot access the folder, even though the original folder (/data/media/0/TWRP) can be accessed from ROOT EXPLORER and TWRP recovery file system
Nandroid Manager looks for only /sdcard/TWRP directory i guess, thus is unable to get backup storage location. Changing the Storage location in Nandroid Manager also has no effect.
I need to restore my backup apps. Please help if u can!