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 might have missed something.
I am trying to install the USB driver, but it looks like I am not having much luck.
I first tried to connect the Gtab while it was running the stock software. It showed that it connected with no problems. When I try to run it in APX mode, it does not show that the Gtab is connected.
Is there a way to go back and start over?
EDIT: I just tried it and it said that it installed the drivers - now it is showing something like NVIDIA USB Boot, but it is not showing APX as a drive.
I recover my gtab and it is working fine as long as I keep turned on... when I turned off and turned on again, goes straight to APX mode and I have to nvflash to get on.
Does anyboby knows how to disable the aPX mode?
I am using windows xp.
none of the drivers seem to work for windows xp x64... suggestions?
thanks for this!
Does anyone know where I can get the following files?
"nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip
Need to a restore on my veiwsonic gtablet and need these files to do so.
Thanks in advance,
Steve
The DropBox on the first post will work
find the url
Is there anyway to download JOdin3 to use offline, as the goo download link is finished I understand, so can not find alternative link (linux install)
Thanks
Sorry if in wrong place
I am trying to download OTA G930FXXU1APF3 (Ireland Vodafone) - since that is the only way to upgrade rooted S7.
The archive here is broken (... says zip, tried twice):
https://samsung-firmware.org/download/Galaxy S7/093e/VDI/G930FXXU1APF3/G930FVFG1APF3/
The archives here are greater than 2G, so I cannot download them freely from mirrors (limit 2G):
http://samsung-updates.com/details/69862/Galaxy_S7/SM-G930F/VDI/G930FXXU1APF3.html
Could anyone please share? Thank you.
http://www.sammobile.com/firmwares/database/SM-G930F/
Interesting enough, that archive did not work either. And then... I found that it is broken only for Mac's version of zip. 7zip can unzip it. Thank you!
Here you go guys. Please help each other out using this thread on the how to.
It is pretty straight forward. Just read the READ-ME folder.
I highly recommend using the Factory Flasher version A.05 !
Download Link here: https://mega.nz/#F!70hwFCTa!Kiy6R0TeL70QrLGuvOHFAA
ColorOS A.05 will allow for use of the OppoTools.
Which can be used to gain root access.
Such as seen on my guide here:
https://forum.xda-developers.com/r7...very-official-twrp-oppo-r7sf-3-0-2-0-t3358552
Look at the buttom for the PDF Guide.
Please do NOT PM me for help.
I won't reply. I already have hundreds of unread PM's. I simply don't have time for replying.
So please help each other out.
a short screenshot guide (NOT BY ME!):
just ignore the device model number shown in one of the screenshots and select the proper one.
Hey,
sorry to bug you, I know you're incredibly busy. I've gone to your provided link and downloaded the R7sfEX_11_A.05_151119 Factory Flasher file.
Only thing is - there is no readme. Not in the archive, not at your link. I need the readme to know what to do.
Am I being stupid, or is it nowhere to be found?
Cheers
zaako said:
Hey,
sorry to bug you, I know you're incredibly busy. I've gone to your provided link and downloaded the R7sfEX_11_A.05_151119 Factory Flasher file.
Only thing is - there is no readme. Not in the archive, not at your link. I need the readme to know what to do.
Am I being stupid, or is it nowhere to be found?
Cheers
Click to expand...
Click to collapse
i just noticed the DownloadTool is missing from the A.05 package.
Do this to unbrick:
download the R7sfEX_11_A.06_151210.7z package.
unpack it and install the Qualcomm Driver in the READ-ME folder.
run the "Msm8x39DownloadTool.exe" select the device model which is listed in the "Instructions.txt"
with this package your R7S is unbrickable.
if you want the A.05 version.
do the same just copy the md5sum.exe and Msm8x39DownloadTool.exe from the A.06 package to the A.05 package and follow the same procedure.
at everyone using those packages.
feel free to write a step by step instruction (maybe with screenshots) and include it in this thread!
i've uploaded one older version and the latest i could find to my archive.
older version R7sfEX_11_A.03_151105.7z (rooting works with OppoTools)
newer version R7sfEX_11_A.11_160721.7z (rooting does not work with OppoTools, downgrade to A.05!)
i also came across a possible list of factory flasher versions.
R7sfEX_11_A.03_151105.tar.bz2 (in archive)
R7sfEX_11_A.05_151119.tar.bz2 (in archive)
R7sfEX_11_A.10_160421.tar(1).bz2 (missing)
R7sfEX_11_A.11_160721.tar.bz2 (in archive)
R7sfEX_11_A.12_160809.tar.bz2 (missing)
R7sfEX_11_A.13_170311.tar.bz2 (missing)
if anyone comes across one of the missing packages. please mirror a direct download link and i will push it into my mirror.
Can this thread be updated. Had an old phone lying around and need to reflasg. Cant get into download mode.
Thanks guys x
ROM Explorer
From time to time I need to extract some files from various Android ROMs. So far I downloaded the ROM file and then started to search for further tools to extract files from the downloaded ROM. If all went well I ended up with an image I could open with ext4_unpacker to finally extract the files I needed. This whole procedure took a lot of time, involved tools from unknown sources and often simply didn't work. So I decided to create my own tool.
ROM Explorer can directly open the following files:
zip archives with img or new.dat entries
Samsung md5 archives
Sony ftf archives
Huawei update.app archives
img/ext4 image files
lz4 image files (used by Samsung)
sin fies (used by Sony)
In case you have a file which is not supported let me know. Maybe I find the time to add support. Or simply add it yourself - ROM Explorer is Open Source.
Usage
Download the installer and run it or build your own version with Visual Studio 2017.
Start the executable. You will see a window similar to ext4_unpacker. In the first line you select a file, in the second line you can choose an archive entry if the file is an archive file.
Loading a file or archive entry can take a significant amount of time and disk storage. ROM Explorer may need to create temporary files with several gigabytes. A fast flash disk helps a lot!
You can extract files or folders by dragging and dropping them to Windows Explorer.
Downloads
ROM Explorer 0.9
ROM Explorer 0.9.1
Thanks To
ROM Explorer would not exist without the distributed knowledge of this forum. Especially I want to thank worstenbrood, Androxyde, IgorEisberg for their work.
So I'm waiting for your comments - but be patient it may take some time for me to react
Reserved for whatever purpose...
Wew
Let me try and report you back
Thank you I will try this out. Thanks too for making it open source
Not Running on Windows 7 x64
samidos said:
Not Running on Windows 7 x64
Click to expand...
Click to collapse
0.9.1 should fix this. Be sure to first uninstall before installing 0.9.1.
After hours of google search and downloading countless apps that dont work I found this. This app is legit and works on windows 10 64bit. Thank you for your work.
Your app is GREAT! Thanks for sharing it.
Edit: Answered my own question. Windows 10 tip "Run As Administrator" and dont drag files "to the desktop" but instead to an Explorer window.
Can this program find the differences between compiled ROMs?
I ask this question because Xiaomi on the Mi 9 released an initial kernel with sourcecode that was changed over time without updating the GitHub https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/cepheus-p-oss and because of this change, the ROMs have something different between how they connect to the cameras. The old ROM versions (4/1/2019 and before) connect fine to the cameras, but post that date, a custom kernel built from the GitHub source will fail to connect to the cameras. Since the change has not been made open source on GitHub, there has to be another way to find and patch new kernel builds in order for them to work. Would your software be able to extract these changes? If not, do you have any other ideas which may? Much appreciated.