Related
Hello guys,
in this thread i will explain, how a RUU (Rom Update Utility) works.
What does a RUU contain?
Yeah, really important for some guys. A normal RUU contains following files:
- AdbWinApi.dll (for use of adb.exe)
- adb.exe (for adb commands)
- ARUGlobal.dll (for the executable file)
- ARUWizard.exe (the RUU executable)
- ARUWizard.ini (basic configuration for the RUU)
- some language files for the RUU
- some bmp-files for the recovery fail (solutions)
- one PHONE.bmp shown in the RUU
- fastboot.exe (for fastboot commands)
- rom.zip (a signed HTC Rom)
- ReadMe-files in different languages
- some other unimportant files
Normaly the RUU is provided in a executable. This exe-file is a compressed, self-extracting InstallShield archive. If you start the file, the InstallShieldWizard extract the contents in the temp-folder of your current User and starts the ARUWizard.exe which is the "real" RUU.
Click to expand...
Click to collapse
What does the RUU while updateing the phone?
Well, its much easier as you think. First the RUU check which version is installed in phone. This is basicly done with following adb-command:
Code:
adb -s {phones adb name} shell getprop ro.build.description
The return is the version number of the phone.
If the phone is started in fastboot mode the RUU run following command and become the same return like with the adb-command:
Code:
fastboot -s {phones fastboot name} getvar version-main
If the version of the RUU rom.zip is higher as the version of the Rom installed on the phone, the RUU give you the option to update your phone.
Click to expand...
Click to collapse
The Update process
Some of you maybe think now, the RUU begins to do magic things. But the next thing is very easy. The RUU restarts the phone into fastboot RUU mode:
Code:
adb reboot-bootloader
fastboot oem rebootRUU
The next command is easily to send the rom.zip to the phones fastboot:
Code:
fastboot update {full path to the update package (rom.zip)}
The rest will do by phones fastboot, not by the RUU self. The RUU return and give out the actual state of the installation only, and gives you the error message if anything go false, or the message, that the phone is updated successfully. After this the RUU will restart the phone.
Click to expand...
Click to collapse
That is basicly what the RUU did, not more
Thx especially for the adb/fastboot commands.
Now everyone can see why modifying the ruu will not give us full access
Yeah, thats the BIG reason why i created this thread
ONeill123 said:
Code:
adb -s {phones adb name} shell getprop ro.build.description
Click to expand...
Click to collapse
does that mean i can change my version in build.prop ro.build.description and we can reinstall a rom from other country ????
ONeill123 said:
CODE]adb reboot-bootloader
fastboot oem rebootRUU[/CODE]
The next command is easily to send the rom.zip to the phones fastboot:
Code:
Code:
fastboot update {full path to the update package (rom.zip)}
The rest will do by phones fastboot, not by the RUU self. The RUU return and give out the actual state of the installation only, and gives you the error message if anything go false, or the message, that the phone is updated successfully. After this the RUU will restart the phone.
Click to expand...
Click to collapse
in ths way giving the comands manually can we falsh ny rom.zip ?? is it possible.? my wfs is with my bro he is gone out of town.. so cant try it.. will surely do it when he gets back.. but still very exited to know. is it possible?
You misunderstood all i think
To the ro.build.description:
The RUU check this only to get the current version and prevent a unuseful restart of phone and to give you the information. Not more.
And you can change the build.prop only with unlocked BL or s-off, and then you can install the system.img of another country self without a RUU.
To the rom.zip:
The RUU sent the rom.zip to fastboot only. The signature check do the fastboot/bootloader of the phone. So you can change the rom.zip, but the bootloader will say "signature error" or something else.
ONeill123 said:
You misunderstood all i think
To the ro.build.description:
The RUU check this only to get the current version and prevent a unuseful restart of phone and to give you the information. Not more.
And you can change the build.prop only with unlocked BL or s-off, and then you can install the system.img of another country self without a RUU.
To the rom.zip:
The RUU sent the rom.zip to fastboot only. The signature check do the fastboot/bootloader of the phone. So you can change the rom.zip, but the bootloader will say "signature error" or something else.
Click to expand...
Click to collapse
hehehe actually i have radio probs.. with my wifi n data pack.. so thought that i might be able to update the radio like this hehehe nvm ty oneil
Hi guys
I want to update my hboot in order to install Jb roms. My current rom is a costum one.
My hboot is: 0.43
my build number ( I got this in menu>settings>about) : 2.17.401.2
And in fast boot when I run ''fastboot getvar version-main" I get this: 1.26.206.2
I have downloaded this RUU: RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed
I do this things:
Install a stock recovery
relock phone
Run RUU and extract rom.zip from temp but I can't extract it completely and I get the corrupted error ( In order to get recovery, boot.img and system files)
I continue the installing RUU process and i get [132] error, "update signature failed"
I don't know what eles should I do
Can anyone help please?
majidadib said:
Hi guys
I want to update my hboot in order to install Jb roms. My current rom is a costum one.
My hboot is: 0.43
my build number ( I got this in menu>settings>about) : 2.17.401.2
And in fast boot when I run ''fastboot getvar version-main" I get this: 1.26.206.2
I have downloaded this RUU: RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed
I do this things:
Install a stock recovery
relock phone
Run RUU and extract rom.zip from temp but I can't extract it completely and I get the corrupted error ( In order to get recovery, boot.img and system files)
I continue the installing RUU process and i get [132] error, "update signature failed"
I don't know what eles should I do
Can anyone help please?
Click to expand...
Click to collapse
that is because thats the wrong RUU for your phone you need the O2 2.17.206.xx RUU first then you should be able to install jelly bean from there. i hope this helps
Download this RUU
http://www.htcruu.com/securekey.php..._Radio_1.1204.90.13_release_251230_signed.exe
Now put the phone in the bootloader / fastboot usb mode and lock your bootloader ( if it is not locked)
Fastboot oem lock
After this you keep the phone in the bootloader / fastboot usb mode and right click the RUU.EXE file on the pc and select
RUN WITH ADMINISTRATOR RIGHTS (or the similar command )
Reboot the phone and start updating by checking for updates in settings - software
Hi,
So after fighting for hours, I managed to successfully use fastboot flash zip command to RUU the google play edition rom to my phone. However, the tutorial I followed didn't say I needed to match my CID and MID, so now I am stuck at the GPE fastboot bootloader. I can flash a custom recovery (I put TWRP on after the RUU was finished). However, since my phone is stuck at fastboot, I can't transfer any files to it using adb.
What I have: Fastboot, and TWRP recovery. Booting normally brings up Fastboot. Booting to recovery brings up TWRP.
My goal: Change my CID and MID so I can properly RUU the GPE rom to my phone. I think I can change the CID from fastboot but I don't think I can change MID from there.
What do you think? Am I going in the right direction? Did I make a wrong assumption?
In fastboot, you should be able to change you CID running this command:
Code:
fastboot oem writecid GOOGL001
If your MID doesn't start with 0P6B, you need to open the RUU file with a zip explorer program and modify the android-info.txt file inside and add your MID to the list. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2708589
hellhawk741 said:
In fastboot, you should be able to change you CID running this command:
Code:
fastboot oem writecid GOOGL001
If your MID doesn't start with 0P6B, you need to open the RUU file with a zip explorer program and modify the android-info.txt file inside and add your MID to the list. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
Well I changed my CID and MID according to the thread (I edited the android-info.txt). However when I ran fastboot flash zip it failed with
FAILED (remote: not allowed)
Any ideas? It worked before, which confuses me as to why it's not working now.
EDIT: Nevermind I am an idiot. FAILED (remote: not allowed) means you need to reboot into RUU mode by using fastboot oem rebootRUU. However now I am back to where I started.
I successfully RUUed the Google Play rom, but now my phone only boots to the bootloader and fastboot.
I'm confused by flashing the RUU, if you have an ext SD card you can copy the image there rename it, boot and it will install itself. There is a rooted image available in the Android Development forum by GrafxNYC. I followed his instructions there and it worked perfectly.
Assuming the RUU file is not an exe file, move it to your SD card and rename it to match your MID exactly and reboot into bootloader. It should flash without a problem.
Ive been wrestling with this since last Saturday but I've finally got the GPE rom working. I couldn't tell you what I did, because I've gotten sidetracked and backtracked a bazillion times. I need to make a new thread though, the GPE rom is *extremely* unstable and crashes very frequently
Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
gmdiesel05 said:
Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
Click to expand...
Click to collapse
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
clsA said:
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
Click to expand...
Click to collapse
yes the second time it said device not found! In cmd window, i type adb devices and none there
This is what happens, and hangs there
C:\Users\Desktop\platform-tools>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.072s]
finished. total time: 0.073s
C:\Users\Cedrik\Desktop\platform-tools>fastboot flash zip RUU-HTC_One_M8_GPE_5.0
.1-3.11.1700.5.zip
gmdiesel05 said:
yes the second time it said device not found! In cmd window, i type adb devices and none there
Click to expand...
Click to collapse
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
clsA said:
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
Click to expand...
Click to collapse
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. now i cant flash a 2nd time
Click to expand...
Click to collapse
are you s-off ? is your phone a GSM M8 ?
Did you try the other method, just renaming the RUU to 0p6bimg.zip (<a 0 (Zero) not a capital o (O), naturally...)
What error do you get when the flashing of the RUU fails?
Like mentioned by clsA said, adb devices won't work in fastboot mode, it should be "fastboot devices" to check if it's connected
---------- Post added at 06:20 AM ---------- Previous post was at 06:18 AM ----------
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
Click to expand...
Click to collapse
You changed CID and MID I take it?
CID - GOOGL001
MID - 0P6B17000
Would have helped a bit if we had an idea what the error was.
clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
Yeah he said his phone is S-OFF in OP
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Click to expand...
Click to collapse
gmdiesel05 said:
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
Click to expand...
Click to collapse
just use the fastboot flash zip ruu.zip command again
clsA said:
just use the fastboot flash zip ruu.zip command again
Click to expand...
Click to collapse
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
gmdiesel05 said:
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
Click to expand...
Click to collapse
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
clsA said:
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
Click to expand...
Click to collapse
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
ok heres the latest
FAILED <command write failed <No such device or address>>
gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything. Sorry you lost me here
maybe im not waiting long enough?
Click to expand...
Click to collapse
you have the file renamed just copy it to your Ext - sdcard and let the bootloader flash it
don't forget to delete or rename it on the sdcard before you reboot again or it will flash it again
ok heres the latest
FAILED <command write failed <No such device or address>>
gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
Click to expand...
Click to collapse
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Method 1
No computer required. Everything else still required. s-off, super CID/gpe CID etc..
1. Rename the RUU zip file 0p6bimg.zip (if your hboot is looking for a different name then rename it to whatever it's looking for)
2. Place the zip on your external SD card
3. Power off your phone
4. Boot into Hboot (hold down vol down as you power on the device)
5. it will load the zip and ask you if you want to proceed
6. Say yes
7. Wait
8. Profit
Click to expand...
Click to collapse
Didn't say anything about flashing it in RUU mode.
BerndM14 said:
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Didn't say anything about flashing it in RUU mode.
Click to expand...
Click to collapse
i used
Method 2
ADB/FastBoot Method
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
you will the following message:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
Code:
fastboot reboot
Hey guys,
Recently I have bought used m8 with custom rom. Seller said he sells it because after trying to do factory reset (thinking it could restore to stock) he lost any gsm signal, only wifi worked. I had some experience with flashing sony mobiles and lg few years ago, so thought it would be easy to install stock rom and use device again. Googled a bit about flashing HTC devices, then downloaded rom, after that had some dificulties with win 8 and htc drivers, so tried to put rom into sd, it was too small. Somehow managed to put rom into device, tried to flash, had some errors, tried another roms, got another fails, changed my cid and mid, played with locked/relocked things, that didn't help either. Tried to restore a nandroid backup, even if it says restore was successful, after i choose reboot, it only boots me in bootloader. Now i cant access twrp, my pc recognises phone, but none of adb commands work.
I apologise if anyone got similar problem, but tried to look for explainations on my own, and found nothing, so this is my last hope to get it working.
Any help or info will be appreciated, I also am very interested in what you guys are doing, so i could even donate for people who can help alot.
***RELOCKED***
M8_WLV PVT SHIP S-OFF
CID-HTC__032
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OS-6.12.401.4 (6.12.401.4)
eMMC-boot 2048mb
If any info more needed, just write, ill add anything you ask.
iTrolis said:
***RELOCKED***
M8_WLV PVT SHIP S-OFF
CID-HTC__032
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OS-6.12.401.4 (6.12.401.4)
Click to expand...
Click to collapse
A big mistake has been made, either by you, or the previous owner. As you indicated the previous owner lost GSM signal, I would guess that person may be the culprit.
Here's what I mean: Your M8 version is Verizon, indicated by the product name M8_WLV. I can see from the OS number (6.12.401.4) that installation of Euro firmware was attempted.
The Verizon version is somewhat unique, in that its designed for use on US Verizon carrier's CDMA network (in addition to GSM, HSPA, LTE) and therefore has its own partition layout, radio firmware, etc. Trying to flash any other version's firmware to this device will not work, and may result in a permanent radio brick. Essentially, only Verizon firmware or RUUs should only be installed to this device. Unlike most other M8 versions, you cannot convert the Verizon M8 to another version by changing the CID/MID (after s-off) and flashing another version RUU.
Indeed, the OS number in parenthesis indicates a problem with the firmware. And I'll venture to guess that this line is also in red font (which also indicated a firmware problem).
Your best (and really, only) option is to try the proper Verizon RUU. A lot of times, this will fix the firmware, and get the radio to work. Although there is a possibility that its a permanent radio brick (as we've seen a number of times). Try the 6.21.605.3 RUU from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another couple mistakes that I can see:
There was never a need to relock the bootloader for what you are doing, since the device is s-off. Its not needed to do this in order to flash firmware or RUU (the main reason to relock bootloader) as this requirement is bypassed by s-off. A relocked bootloader won't interfere with the RUU I recommended. But it would hamper trying to install TWRP custom recovery.
adb won't work unless you are booted to Android OS, or in TWRP. Since neither of those are working, it is normal and expected that adb command won't work. Fastboot command should work, while booting into bootloader-fastboot mode (and only that mode). While fastboot is related to adb, there are important conditions and differences.
redpoint73 said:
Your best (and really, only) option is to try the proper Verizon RUU. A lot of times, this will fix the firmware, and get the radio to work. Although there is a possibility that its a permanent radio brick (as we've seen a number of times). Try the 6.21.605.3 RUU from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
If the latest RUU doesn't fix the radio signal, I suggest to install the lowest version 1.5x. as the lower version usually will fix the NV partition which related to radio and unbrick it. (This is what I read in VZW thread before)
ckpv5 said:
If the latest RUU doesn't fix the radio signal, I suggest to install the lowest version 1.5x. as the lowest version usually will fix the NV partition which related to radio and unbrick it. (This is what I read in VZW thread before)
Click to expand...
Click to collapse
Good to know, I wasn't aware.
I think the 1.5x files would be here: https://forum.xda-developers.com/verizon-htc-one-m8/development/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
Edited my earlier post.
Your earlier link is good ... click 4.4.4 RUU zip link, it's 3.28.605.4 RUU
The only way to reset the partition to out of the box stock is to flash your carrier's 4.4.4 firmware and the stock recovery for you device. Reboot to recovery and select factory data reset and let it do it's thing. If you watch the reset log you will see it mention resetting the NV partition.
Source : https://forum.xda-developers.com/showpost.php?p=57453624&postcount=2
guys, thank you for help, downloaded latest .zip file, renamed it to 0P6GIMG.zip, did fastboot flash zip 0P6GIMG.zip and it shows this: target reported max download size of 1826
Invalid sparse file format at header magi
any ideas?
iTrolis said:
guys, thank you for help, downloaded latest .zip file
Click to expand...
Click to collapse
Try the 4.4.4 RUU as ckpv5 advised in his most recent post.
what if i have changed cid and mid thinking to make my device to international?
now my cid is HTC__032
and MID 0P6B12000
i have to change these to original for verizon?
iTrolis said:
what if i have changed cid and mid thinking to make my device to international?
now my cid is HTC__032
and MID 0P6B12000
i have to change these to original for verizon?
Click to expand...
Click to collapse
That's correct, you will need to change back to the Verizon CID and MID to run the RUUs, firmware. Sorry, I missed that in the details you provided.
Alternately, if you change to SuperCID (11111111) in most cases this will bypass the MID check (and save you some steps).
now got RUU mode with exclamation marks on the edges of screen..
changed cid to vzw__001, but now need to get to fastboot again, to change it to supercid and will try 6,0 ruu.exe 4,4,4ruu.exe and 6,0 .zip files i have downloaded
Edit: cid changed to supercid, still stuck on silver htc logo with 4triangles on the edges. cant find a solution...
Read this on how-to : https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your ruu.zip not the one in the guide.
At the end of the guide, you'll see there are 3 methods to install ruu.zip
tried your method and got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip rom.zip
sending 'zip'... (46028 KB) OKAY
writing 'zip'... FAILproject does not have sa key to decrypt rom
FAILED (remote: project does not have sa key to decrypt rom)
Execution time is 2(s)
already tried to do it with ARUwizard.exe and stuck on silver HTC letters with 4 triangles nad exclamation marks on the edges of the screen, cant boot to bootloader, and i dont have enough storage in SD card to put rom in it
edit: trying again with another .zip file, now got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip 1.zip
sending 'zip'... (1760932 KB) OKAY
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL24 parsing android-info fail
FAILED (remote: 24 parsing android-info fail)
Execution time is 56(s)
ckpv5 said:
Read this on how-to : https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your ruu.zip not the one in the guide.
At the end of the guide, you'll see there are 3 methods to install ruu.zip
Click to expand...
Click to collapse
another question, what should be there in that ruu.zip? downloaded few and there is one with rom.zip, adb.exe, ARUwizard.exe, alot of .dat files and bitmap images inside, others are only with boot-signed.img and android-info.txt
iTrolis said:
another question, what should be there in that ruu.zip? downloaded few and there is one with rom.zip, adb.exe, ARUwizard.exe, alot of .dat files and bitmap images inside, others are only with boot-signed.img and android-info.txt
Click to expand...
Click to collapse
What are those you downloaded ? Which link ?
In my earlier post, I specifically suggested this one : https://www.androidfilehost.com/?fid=95784891001604006
If in ruu.zip you downloaded has all those files, it means you need to extract the ruu.zip then run the ARUwizard.exe to install.
ckpv5 said:
What are those you downloaded ? Which link ?
In my earlier post, I specifically suggested this one : https://www.androidfilehost.com/?fid=95784891001604006
If in ruu.zip you downloaded has all those files, it means you need to extract the ruu.zip then run the ARUwizard.exe to install.
Click to expand...
Click to collapse
yes i have downloaded exactly this and two more, now extracted this, ran wizard and got error 171 usb connection error, tried another usb cable, another usb slot but same error, what could solve this?
Do you have latest HTC USB drivers installed ? As explained in this guide - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
where it says - first you need this ?
Also try with USB2.0, if running it with ARUwizard.exe (that also explained in the same guide in the link at the lower part).
Or take only the rom.zip then
htc_fastboot flash zip rom.zip
ckpv5 said:
Do you have latest HTC USB drivers installed ? As explained in this guide - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
where it says - first you need this ?
Also try with USB2.0, if running it with ARUwizard.exe (that also explained in the same guide in the link at the lower part).
Or take only the rom.zip then
htc_fastboot flash zip rom.zip
Click to expand...
Click to collapse
downloaded htc sync manager, uninstalled it, tried both usb cables on all three different usb ports, same 171 error, tried to flash zip, got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip rom.zip
sending 'zip'... (46028 KB) OKAY
writing 'zip'... FAILproject does not have sa key to decrypt rom
FAILED (remote: project does not have sa key to decrypt rom)
Execution time is 3(s)
I downloaded the 3.28.605.4 ruu.zip to see what's going on here .. it's a signed RUU, you're not supposed to extract it. No normal zip archiver can extract it properly.
Rename the whole as ruu.zip or rom.zip then htc_fastboot it after you put the device in RUU mode
fastboot oem reboot RUU
fastboot flash zip ruu.zip (or rom.zip if you renamed it rom.zip)
fastboot reboot-bootloader
also make sure your windows extension is not hidden so it won't actually become ruu.zip.zip where you will have unable to load ruu.zip error
The whole
0P6BIMG_M8_WL_K444_SENSE60_VZW_MR_VERIZON_WWE_3.28.605.4_HSM_Radio_1.09.20.0926_NV_VZW_2.11_002_release_393779_signed_1.zip
is the rom.zip
ckpv5 said:
I downloaded the 3.28.605.4 ruu.zip to see what's going on here .. it's a signed RUU, you're not supposed to extract it. No normal zip archiver can extract it properly.
Rename the whole as ruu.zip or rom.zip then htc_fastboot it after you put the device in RUU mode
fastboot oem reboot RUU
fastboot flash zip ruu.zip (or rom.zip if you renamed it rom.zip)
also make sure your windows extension is not hidden so it won't actually become ruu.zip.zip where you will have unable to load ruu.zip error
The whole
0P6BIMG_M8_WL_K444_SENSE60_VZW_MR_VERIZON_WWE_3.28.605.4_HSM_Radio_1.09.20.0926_NV_VZW_2.11_002_release_393779_signed_1.zip
is the rom.zip
Click to expand...
Click to collapse
downloading that .zip again, but i think that RUU fail doesnt let me to work now, how can i access fastboot when im locked to that ruu fail screen? power+vol up then vol- just restarts me to that black screen with htc letters and four triangles on the corners of screen
type command
fastboot reboot-bootloader