Related
Trying to root via unrEVOked..."reflash.exe is not a valid Win32 application."
I seem to be the only one to ever have this problem. I followed the unrEVOked instructions - I installed HBOOT drivers and installed modified USB drivers. When I get to the point where I turn the phone back on, plug it in, and open "reflash.exe", the "reflash.exe" file won't open. I get the error message "reflash.exe is not a valid Win32 application." I've tried downloading the unrEVOked package again and again. I've tried extracting the files again and again. I've tried opening the file as an administrator. I also get an error message whenever I extract the files, but they seem to be successfully extracted anyway.
JTravisRolko said:
I seem to be the only one to ever have this problem. I followed the unrEVOked instructions - I installed HBOOT drivers and installed modified USB drivers. When I get to the point where I turn the phone back on, plug it in, and open "reflash.exe", the "reflash.exe" file won't open. I get the error message "reflash.exe is not a valid Win32 application." I've tried downloading the unrEVOked package again and again. I've tried extracting the files again and again. I've tried opening the file as an administrator. I also get an error message whenever I extract the files, but they seem to be successfully extracted anyway.
Click to expand...
Click to collapse
Corrupt download. Clear your cache (on the PC) and download again. The reason why you keep getting the same error even after downloads is because IE/FF is using the locally stored copy of the file instead of redownloading again.
I'm not exactly sure what you mean by "clear the PC cache", but I had CCleaner clean up a lot of stuff and then redownloaded the unrEVOked package. I extracted the files from the package, and again, it said that reflash.exe (and only reflash.exe) was corrupt, and again, I get the same error message when trying to open reflash.exe.
Enrevoked is an EXE, there is nothing to extract or remove?
Just start the program, it pushes the file to the phone, reboots it, phone finds image, roots itself basically and bobs your uncle, you have root.
It is fully automated, there is nothing to open or extract.
Problem solved. I downloaded the file to a different hard drive. I don't why, but files that I download via my browser frequently get corrupted.
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
Hi, guys. First of all, thanks for all of your hard work and time you put into all of these custom ROMs.
So, I rooted my HTC Tattoo, then flashed it with CyanogenMod 7 and I am very happy how ROM works. I was wondering how can I get back to stock (for warranty reasons) since I was stupid enough to not make a backup of Stock rom with ROM Manager.
First, I tried installing RUU exe file(RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver) from Winows 7 computer, but when I connect my phone to PC, i got error message 170 saying "USB Connection Error".
When that didn't work, I downloaded and put CLICIMG.zip (I belive thats rom.zip from RUU) on root of my SD card, then rebooted to HBoot, but i got error saying something like "No images found in CLICIMG". I also tried to rename this file to CLICKIMG.zip, CLICDIAG.zip, but that didn't work either.
Hope you can help me somehow.
Thanks.
PavleSRB said:
First, I tried installing RUU exe file(RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver) from Winows 7 computer, but when I connect my phone to PC, i got error message 170 saying "USB Connection Error".
When that didn't work, I downloaded and put CLICIMG.zip (I belive thats rom.zip from RUU) on root of my SD card, then rebooted to HBoot, but i got error saying something like "No images found in CLICIMG". I also tried to rename this file to CLICKIMG.zip, CLICDIAG.zip, but that didn't work either.
Click to expand...
Click to collapse
Hope the CLICIMG.zip you have downloaded is not corrupt.
Best thing would be to copy the rom.zip form the temp folder,
Here is what you can do:
After you started RUU wait until you get the prompt to proceed or you get the usb error and don't close the application
Then you can get rom.zip file from following folder
"C:\Users\<your user name>\appdata\Local\Temp"
replace "your user name" with your account name in windows
copy the rom.zip and rename it to CLICIMG.zip
place it in root of SDCARD and proceed
Thanks for replay. I managed to resolve this, I will post little guide soon on this topic.
I have flashed official CyanogenMod 10.1. I have installed the driver and using USB debugging. When I try to copy a file from pc to my nexus 4, this window pop up. How can I solve it?
That particular directory has problems with the USB Debugging sequence AFAIK.
For me my Titanium Backup folder wont work.
What I did was, I copy it to elsewhere that can be copied, then when I'm back to the ROM, use certain file manager to copy again.
I know its time exhausting, but hey, at least it works!
Just copy to somewhere that works.
Hello,
After unlocking, and rooting nexus 4, I cannot copy any zip file in device, I tried another files like Videos, pictures, songs etc, this files copied successfully but there is problem to copy zip files have tried on 2 different computers, but it still not copying Please Help :crying:
razor17 said:
Hello,
After unlocking, and rooting nexus 4, I cannot copy any zip file in device, I tried another files like Videos, pictures, songs etc, this files copied successfully but there is problem to copy zip files have tried on 2 different computers, but it still not copying Please Help :crying:
Click to expand...
Click to collapse
what do you mean cant copy what error does it give ?
fahadsul3man said:
what do you mean cant copy what error does it give ?
Click to expand...
Click to collapse
No any error, whenever I start copying, progress bar of copying is stopped on 50% to 70% and after clicking on that zip file windows start zip file copying again and again
Today I have rooted 2 nexus 4 devices, 1st was successfully installed caynogenmod 10.1.3 and working normal and 2nd device cannot copy any .zip files,
I can't understand exact problem, Windows 7 stop copying after some 50% or 70%, and if I open that copied zip windows 7 start copying again and again, I tried another method, I sent cm-10.1.3-mako.zip from my another Android device to nexus 4, then I installed cm-10.1.3-mako.zip successfully, after installation CM-10 device is just booting, and cannot complete boot. just booting and booting, and I copied cm 10 zip from my desktop, but progress bar shows "copying from C:\Users\INDRAJ~1\AppData\Local\Temp\WPDNSE\SID-{10001,,13874577408}"
I did not understand why windows copy zip file form WPDNSE folder, this folder in temp, the original copy source is from desktop,
I have installed my stock 4.3 rom from CWM backup but now I can't download any app from play store the error is "Error while retrieving information from the server [RPC:s-7:AEC-0]"
Can anyone PLEASE, PLEASE, PLEASE Help to fix this problems :crying: :crying:
(Sorry for bad English)