Related
I want to flash userdata.img, system.img, recovery.img, boot.img files via ADB to my Desire in order to unroot my 2.1, then make it able to upgrade to 2.2 via OTA.
I am using rooted HK 2.1 ROM, have downloaded Asia WWE 2.1 RUU and extracted those .img files.
How can I disable the signature checking? I've got below errors when I tried to flash the img file to my Desire.
C:\r5>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... INFOsignature che
FAILED (remote: signature verify fail)
If you are using a custom recovery like clockwork mod or Amon ra. There is an option called "Toggle Signature".
txitxi2004 said:
If you are using a custom recovery like clockwork mod or Amon ra. There is an option called "Toggle Signature".
Click to expand...
Click to collapse
thanks, but ADB is unable to connect to the device if it is in recovery mode, can only be in fastboot mode. So that I need to disable signature checking in fastboot mode.
scott4 said:
thanks, but ADB is unable to connect to the device if it is in recovery mode, can only be in fastboot mode. So that I need to disable signature checking in fastboot mode.
Click to expand...
Click to collapse
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
kekojan said:
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
Click to expand...
Click to collapse
i've tried flashing the original recovery.img to Desire, still can't solve the signature check problem. I also have tried doing below:
push flash_image and mtd0.img (what should be the CID of HK 2.1 official rom?) to Desire through ADB, the execute like: flash_image misc mtd0.img
however the upgrade still couldn't pass the signature check... sigh..
kekojan said:
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
Click to expand...
Click to collapse
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
st0kes said:
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
Click to expand...
Click to collapse
So, is there any way I can flash the images I build for Desire? (I have rebuild the froyo platform for desire)
Can I flash them via sdcard using for e.g clockwork or similar recovery method?
kekojan said:
So, is there any way I can flash the images I build for Desire? (I have rebuild the froyo platform for desire)
Can I flash them via sdcard using for e.g clockwork or similar recovery method?
Click to expand...
Click to collapse
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
I zipped system.img and boot.img and toggled off the signed files in clockwork and flashed the zipped (50Mb) package. All were installed really way too fast and without errors. After reboot nothing was updated. Next steps? Any ideas?
eh.. delete me
Update to previous post. I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing (clockwork) was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
kekojan said:
I zipped system.img and boot.img and toggled off the signed files in clockwork and flashed the zipped (50Mb) package. All were installed really way too fast and without errors. After reboot nothing was updated. Next steps? Any ideas?
Click to expand...
Click to collapse
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
Now I did as per the instructions except the update-script part.
I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
kekojan said:
Now I did as per the instructions except the update-script part.
I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
Click to expand...
Click to collapse
The corresponding part of the recovery log below.
- Installing: SDCARD:images_new.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:images_new.zip
Opening update package...
I:Update file path: /sdcard/images_new.zip
Installing update...
I:Trying update-binary.
I:Trying update-script.
Starting recovery on Fri Sep 3 13:03:42 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Set boot command "boot-recovery"
Command: "recovery"
What do you think what is wrong?
st0kes said:
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
Click to expand...
Click to collapse
technically, that is incorrect.
S-ON or S-OFF is a flag that's being interpreted by fastboot/hboot.
The engineering bootloader you talk about, ignores this flag and exposes developer options like flashing through the fastboot protocol directly, without a signature.
scott4 said:
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
Click to expand...
Click to collapse
I like the theory, but you would probably have to fool the RRU so that it thinks your img files have the same checksums as the original img files. I've never heard of anyone being able to repack and flash an RRU file.
kekojan said:
Starting recovery on Fri Sep 3 13:03:42 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Set boot command "boot-recovery"
Command: "recovery"
What do you think what is wrong?
Click to expand...
Click to collapse
I think something is wrong with your update-script.
Btw, forget about your system.img, you can't use it .. you have to work with the contents of the system directory instead
ieftm said:
technically, that is incorrect.
S-ON or S-OFF is a flag that's being interpreted by fastboot/hboot.
The engineering bootloader you talk about, ignores this flag and exposes developer options like flashing through the fastboot protocol directly, without a signature.
Click to expand...
Click to collapse
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
st0kes said:
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
Click to expand...
Click to collapse
unrevoked 3.2 seems to be able to set to S-OFF!! but waiting it release
st0kes said:
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
Click to expand...
Click to collapse
Bootloaders are either ship or eng.
The latter ignores secuflag and allows extended fastboot commands.
So bootloader or s-off are two separate things.
S-off is mainly for unsigned flashing and nand writelocks.
scott4 said:
unrevoked 3.2 seems to be able to set to S-OFF!! but waiting it release
Click to expand...
Click to collapse
only on cdma desire.
For gsm desire you will need to wait for our s-off/eng hboot 0.93 release.
This is a patched hboot to ignore security, and allow extended fastboot commands.
So essentially S-OFF and eng.
scott4 said:
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
Click to expand...
Click to collapse
Flashing the misc partition allows you to bypass (fake, really) version checks with an RUU flash, nothing more. It doesn't affect root nor does it have anything to do with signature checking (which is currently impossible to disable on the GSM Desire).
Hi, I'm trying to install cm10.1-RC5 from Arch Linux. I've wiped and factory reset and flashed the boot.img. I don't have s-off.
When I try to install the .zip in ClockworkMod 5.8.4.0 I get errors indicating that my bootloader isn't a compatible version. For example:
assert failed: getprop("ro.bootloader") == "1.31.0000"
E:Error in /sdcard/cm-10.1.0-RC5-endeavoru.zip
(Status 7)
Installation aborted.
I gather that this means my hboot or firmware needs an update. I've found this thread which seems relevant:
http://forum.xda-developers.com/showthread.php?t=2241419
I ran "fastboot oem readcid" and got this:
...
(bootloader) DEBUG: cid: VODAP021
OKAY [ 4.075s]
finished. total time: 4.075s
So I guess this means I need Vodaphone specific firmware? Where can I access this?
Or am I on the wrong track?
Post the result of fastboot getvar version-main..
This is a cmd fastboot command (windows)... No idea what's the command for Linux.. Might be something similar..
This way we can make sure which firmware you have...
-Sent from my IceCold One X!
vin4yak said:
Post the result of fastboot getvar version-main..
This is a cmd fastboot command (windows)... No idea what's the command for Linux.. Might be something similar..
This way we can make sure which firmware you have...
-Sent from my IceCold One X!
Click to expand...
Click to collapse
Thanks for the quick reply, here's the output:
version-main: 1.29.862.11
finished. total time: 4.069s
I've located this thread:
http://forum.xda-developers.com/showthread.php?t=1957376&highlight=upgrade+firmware+linux
This pointed me to .zip containing hboot 1.36.
I tried following these instructions:
http://sadevil.org/blog/2012/12/23/manually-flashing-an-ota-update/
Unfortunately the directories the tutorial references are different to the one in my .zip.
Now there are 2 ways you can upgrade your device's hboot
1: Returning to stock with a ruu and then updating to jellybean hboot with ota update.
2. Flashing the firmware zip and then installing a custom rom.
For running a ruu you will need access to a windows pc since it's an exe file : http://bugsylawson.com/files/file/1...11-radio-1120410514-release-260561-signedexe/
If you want to upgrade your firmware by flashing... Here's the firmware upgrade for your cid : http://goo.gl/yAa0G
Download the firmware and rename it to firmware.zip and then put it in the fastboot folder..
Steps:
1. Relock bootloader : fastboot oem lock
2. Reboot to ruu : fastboot oem rebootRUU
It will take you to a black htc screen... Wait for a few seconds for the screen to settle down and then flash the firmware :
Fastboot flash zip firmware.zip
You might need to flash the firmware twice if you get an error the first time! Its quite normal! After successfully flashing the firmware, you need to unlock the Bootloader, flash a custom recovery and then flash the custom rom!
PS: Again, the commands are for fastboot cmd (windows).. Linux might be a little different..
-Sent from my IceCold One X!
vin4yak said:
Now there are 2 ways you can upgrade your device's hboot
1: Returning to stock with a ruu and then updating to jellybean hboot with ota update.
2. Flashing the firmware zip and then installing a custom rom.
For running a ruu you will need access to a windows pc since it's an exe file : http://bugsylawson.com/files/file/1...11-radio-1120410514-release-260561-signedexe/
If you want to upgrade your firmware by flashing... Here's the firmware upgrade for your cid : http://goo.gl/yAa0G
Download the firmware and rename it to firmware.zip and then put it in the fastboot folder..
Steps:
1. Relock bootloader : fastboot oem lock
2. Reboot to ruu : fastboot oem rebootRUU
It will take you to a black htc screen... Wait for a few seconds for the screen to settle down and then flash the firmware :
Fastboot flash zip firmware.zip
You might need to flash the firmware twice if you get an error the first time! Its quite normal! After successfully flashing the firmware, you need to unlock the Bootloader, flash a custom recovery and then flash the custom rom!
PS: Again, the commands are for fastboot cmd (windows).. Linux might be a little different..
-Sent from my IceCold One X!
Click to expand...
Click to collapse
Golden gold you are sir/madam! Got CM10.1 running like a beast!
Thankyou kindly.
That's Great! Enjoy cm10! :good:
-Sent from my IceCold One X!
firmware for htc_38 for hboot update
I have HTC One X, currently i m at hboot 1.72 and CWR 6.0.4.7. I want to update my hboot for that i need firmware for my device whose CID is htc_38. I have already gone through xda page of "collection of firmware" to search for my device's firmware but i didnt get it there. plzzzzzzz help me out here.
abhinav625 said:
I have HTC One X, currently i m at hboot 1.72 and CWR 6.0.4.7. I want to update my hboot for that i need firmware for my device whose CID is htc_38. I have already gone through xda page of "collection of firmware" to search for my device's firmware but i didnt get it there. plzzzzzzz help me out here.
Click to expand...
Click to collapse
You are with the latest firmware!!!!
Hey there.
I am S-ON and trying to find a way of updating the firmware to 2.22xxx on my M8 with CID HTC_032.
Anyone?
EDIT:
I found this guide http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 and the firmware zip has my phone's modelid and cidnum.
However, after renaming the file 0P6BIMG.zip, placing it on the ext_sd and rebooting to bootloader, the hboot checks the zip and after that I get an error in red font: Press <POWER> to reboot.
Anyone?
EDIT2:
nevermind. I found this guide http://forum.xda-developers.com/showthread.php?t=2735235 and following step 6 with the zip file provided there I managed to upgrade my firmware.
Hello there...I have an issue with my htc m8...When I try to flash a firmware or a custom rom like Maximus HD rom..I always get that error : Failed : no md5 file found
I have a rooted device with s-off and twrp recovery
Any help ? Thanks
1. You cannot flash a firmware in TWRP recovery .. you need fastboot flash the firmware.zip in RUU mode
2. Disable md5 checking in TWRP so you won't have that md5 error when a zip has no md5
ckpv5 said:
1. You cannot flash a firmware in TWRP recovery .. you need fastboot flash the firmware.zip in RUU mode
2. Disable md5 checking in TWRP so you won't have that md5 error when a zip has no md5
Click to expand...
Click to collapse
So all I have to do is ticking the "Skip MD5 verification of backup files " option ?
Is there any guide to how to flash unsigned firmware using fast boot in RUU mode ?
Thanks ?
1. Yes
2. Lazy to rewrite thing all over again ... you can find it on many threads ...
Here is what I wrote for different firmware but the basic is the same ...
http://forum.xda-developers.com/showpost.php?p=64471713&postcount=10519
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