Related
Hello Everyone
I tried something stupid and now my Desire doesn't boot anymore. I have made a Nandroid backup, but I am unable to restore with my device, because I don't seem to have the ClockworkMod Recovery
I can go to the screen with the 3 skateboarding androids, but when I choose recovery, It goes to "Android system recovery <2e>". There doesnt seem to be an option to restore Nandroid backups there.
What's the easiest way to restore my backup? I can access my SD-card on my PC.
Or maybe it is easier just to install a random fresh ROM and from there restore my nandroid backup? (but I don't know how to do that from the recovery screens I have access to)
PS: I already tried some things on I found on google, I tried restoring using fastboot method, but get this message:
c:\Android>fastboot flash system system.img
sending 'system' (232637 KB)... FAILED (remote: data length is too large)
Please help, Thanks!
Edit: Tried to manually 'install' ClockWorkMod Image 2.5.0.7 with fastboot... I get the following error:
c:\Android>fastboot flash recovery recovery-clockwork-2.5.0.7-bravo.img
sending 'recovery' (4216 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
You need to be s-off to be able to use those fastboot commands. Have you tried reflashing a custom recovery with unrevoked? Otherwise you probably need to use a Ruu and root again.
Sent from my HTC Desire using XDA Premium App
Hi, Thanks
you're right, I do have S-On
I also have H-boot 0.75
(Radio-5.11.05.27 just to be complete)
What do I need to do first? Remember that I am stuck on the HBoot screen (3 skateboarding androids).
Can I get S-off from here and flash ClockworkMod Recovery? Or do I need to flash a RUU Rom first?
Also do I need to update HBoot to 0.80?
And are 'HBoot drivers' the same as the 'Fastboot/ADB drivers' ?
Need more help please. Most tutorials start with a working phone
Thanks!
Need some help guys please, Everything I try doesn't seem to work.
I figured out my phone is stuck in HBOOT with USB debugging disabled. Because Unrevoked doens't recognize my phone. Next step was to try and install a RUU. But the version I needed is corrupt. (I think) I downloaded twice and it just doens't work, I get an error even before the program loads.
I downloaded from RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed here: http : / / shipped-roms . com/shipped/Bravo/
Should I maybe try another RUU? Maybe 2.29.405.5 ? Or is that not safe?
Grtz!
Solved,
xda forum member EddyOS pointed me to this RUU http://www.multiupload.com/LEJCW182AH
(filename: RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed)
Thanks!
Hello,
I am reading for hours and lost the overview...
My Desire had CM7 installed and had many reboots lately (maby caused by juice defender or the dalvic cache on the ext) but now it just wont boot at all. Not even into recovery.
Bootloader and Fastboot work but I cant flash anything or boot a recovery
S-ON
HBOOt-0.93.0001
RADIO-5.11.05.27
Code:
fastboot flash recovery recovery-clockwork-2.5.1.3-z71.img
sending 'recovery' (3742 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Code:
fastboot boot recovery-clockwork-2.5.1.3-z71.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
I am using a Mac but could also use a Win7 or Ubuntu maschine if this is necessary...
Please help
Ruu?
Sent from CM7
Is the custom recovery flash failing because the phone is s-on?
If so would it help to run alpharev on it?
Not sure, just a thought!
From what I understood you need to be able to boot to use alpharev or RUU?
I started the RUU .exe and stole the ROM.zip from TEMP but either the CID is not correct (I have VODAP102) or the version is older since CM7 is 2.3.3 I guess.
00droid said:
Is the custom recovery flash failing because the phone is s-on?
Click to expand...
Click to collapse
I guess so. Isn't S-OFF the thing you need to flash custom roms? I had it rooted and installed the recovery with clockwork or so from within OS without changing S-ON.
I got a UK VODA RUU to start at least (SD inside, sim not) but fails with ERROR[170] USB-Connoction Error
Afterwards it booted magically, I could backup data, flash LeeDroid to (what I thought) would solve the instability problem but it crashed again (connected cable is not good). And now its the same all over again but this time I cannot reproduce the luck from the first time.
Should I keep trying and then S-OFF, dwongrade bootloader and upgrade radio? What else could I do.
But I dont think the attepted flashing will work again...
magreet said:
From what I understood you need to be able to boot to use alpharev or RUU?
I started the RUU .exe and stole the ROM.zip from TEMP but either the CID is not correct (I have VODAP102) or the version is older since CM7 is 2.3.3 I guess.
Click to expand...
Click to collapse
Hmm, I think you're right actually, it's been a while since s-off for me!
S-OFF is indeed needed to flash the custom recovery via fastboot.
RUU - so probably you need a branded RUU for your phone (VODA-Germany VODAP102).
Or do the above mentioned method - take the ROM.zip and put it on your SD Card, but RENAME it to PB99IMG.zip.
Since you are branded, you need to create a goldcard, to avoid CID error:
Here's how
The phone needs to boot to create a GoldCard Luckily this happens from time to time.
But since 2.3.3 is newer than the newest 2.2 RUU the GoldCard CID fix wont work in my oppinion...
Even I am struck with the same issue. Only fastboot access with an Orange desire. I do not have a gold card to try out anything.
My phone's CID: ORANG001
Bootloader throws up the following error:
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No image!
Loading...[PB99IMG.nbh]
No image or wrong image!
Any suggestions?
Could you flash a RUU from within Windows? I tried many, at least one of them tried to start and failed but the phone started at least. If a boot loop occurs remove the battery and retry as long as it takes. Worked for me.
Maybe without sim.
Some people reported being able to boot WITHOUT sd in the phone. Try it.
I stupidly ran ace hack kit a second time after installing Android Revolution.
It stopped working after trying to turn radio off. Now the phone wont load past the HTC screen. I can access the HBOOT menu. but recovery and factory reset both dont work.
Ive looked everywhere and cant find someone with the same issue (I dont think anyone else was stupid enough to run the kit twice)
Any ideas?
No help at all??
Get the recovery.img for 4EXT or Clockworkmod. The one for the latest 4EXT I have attached. You'll have to unzip it. When you have unzipped it check the MD5 of the recovery.img in there matches:
84b31bc1b1c254b2c46054c957e63701
Put it in your Android SDK Tools (Or Platform-Tools) folder.
Plug your phone into the computer while it is in the bootloader.
Open a CMD to that folder.
Type:
fastboot flash recovery recovery1.img
That will install a recovery environment. After that you will be able to install a ROM.
I keep getting getting an error saying that fastboot isnt recognized as a internal or external command, operable program or batch file
Im getting this error
sending 'recovery' (3624 KB)... OKAY [ 0.766s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.766s
You don't have an engineering hboot (eng s-off) Therefore you can't use fastboot commands.
Download a stock 1.32 pd98img.zip and put it on your sdcard and boot into hboot. Your phone will be completely sock after the installation.
I do what i want, because I can.
Flussen said:
You don't have an engineering hboot (eng s-off) Therefore you can't use fastboot commands.
Download a stock 1.32 pd98img.zip and put it on your sdcard and boot into hboot. Your phone will be completely sock after the installation.
I do what i want, because I can.
Click to expand...
Click to collapse
Will it be S-on again?
Also thank you! It worked, phone is up and running again.
Radio s-off should stick, eng hboot (which you don't had anyway) will be gone.
I do what i want, because I can.
Help. Ace hack been running for 30 minutes and stuck on flashing radio
Ran ace hack kit. Everything fine until flashing radio. Been stuck on infocruujwp, radio, 95 for a while.
What do i do now?
I was trying to get S-ON so I started my DHD and flashed stock fryo ROM. Aahk went trough the process and finished but my phone were on HTC update screen so I had to pull the battery, anyone else with this problem?
Hi guys,
A good friend of mine recently requested me to help with rooting her Wildfire S A510e (purchased from SingTel, CID HTC__044). I managed to change her Wildfire S from S-ON to S-OFF via HTCdev. As far as I know, HTCdev isn't supposed to give you S-OFF but only to remove the NAND write locks on certain partitions.
Users: This is NOT for you. This is NOT a tutorial.I will not be responsible for any bricked WFS.
Here's what happened, pretty long so I'm gonna break it down into multiple sections. Important points in red.
Replacing SingTel ROM with HTC EU ROM
The phone was originally running Android 2.3.3, ROM version 1.35.707.1, HBOOT 0.90.0000. This ROM version is not supported by HTCdev unlock yet.
Reboot to HBOOT on WFS. Choose FASTBOOT.
Connect WFS to computer via USB.
Downloaded the HBOOT RUU for "hTC Asia India" from HTCdev. Attempted to install the RUU but got a CID error.
Disconnected WFS from computer.
Rebooted normally on WFS.
Connect WFS to computer via USB (Disk Drive).
Created a goldcard by using SimpleGoldCard while WFS is mounted as Disk Drive. (this wipes your SD card)
Disconnect WFS from computer and reboot.
Connect WFS to computer via USB (Disk Drive).
Downloaded RUU_Marvel_S_HTC_Europe_2.13.401.2
Ran the RUU. Went into %temp%, found the relevant directory and copied rom.zip to the goldcard as PG76IMG.zip.
Disconnect WFS from computer.
Turn off WFS and rebooted into HBOOT.
Went into HBOOT -> Fastboot. RUU_Marvel_S_HTC_Europe_2.13.401.2 was installed successfully (Android 2.3.5, ROM version 2.13.401.2, HBOOT 0.90.0000).
Installing HTCdev Unlock
Rebooted WFS into HBOOT.
Connect WFS to computer via USB.
Downloaded the HBOOT RUU from HTCdev for "HTC EU".
Ran the HBOOT RUU. RUU installation gets stuck at 50% ("Flushing radio...") for about 20 minutes.
Decided that the RUU has hung so disconnected WFS from USB and did a battery pull
RUU offered to do a recovery but I clicked "Exit".
Turn on WFS in HBOOT mode.
S-OFF obtained!
I was pretty much at "dafuq?" at this stage. I didn't even need to upload the device identifier to HTCdev to get an unlock key. The device was already S-OFF (HBOOT shows it)!
HBOOT remained at 0.90.0000.
I verified the S-OFF by flashing ClockWorkMod which went without issues.
Possible theory of operation: (just my thoughts)
The HTCdev HBOOT RUU provides a temporary S-OFF in order to unlock the NAND
When the RUU is done, it is supposed to restore S-ON to the device.
However, since the process was hung, the RUU had no chance of restoring the device to S-ON.
Hence the WFS was left at S-OFF.
If there are any adventurous devs around who are willing to try to dissect the RUU, please do so, but standard disclaimer applies. Attempting to interrupt the HBOOT RUU flashing is pretty dangerous and WILL possibly brick your device! I will not be held responsible if you brick your WFS!
This seems to be a case of pure luck.
Addendum:
The HBOOT RUU contains 2 ZIP files: rom_01.zip, rom_02.zip
They are presumably flashed in-order.
rom_01.zip contains Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img
rom_02.zip contains hboot_1.08.0099_6e20b6fac09.nb0 and radio_47.23a.35.3035H_7.53.39.03M_MR.img
My friend has radio version 47.23b.35.3035_7.54.39.08M. From here, we can tell that rom_01.zip was successfully flashed but rom_02.zip wasn't. Also notice the "special" file name of the first radio image.
Addendum 2:
It appears that both radio ROMs have the same size but different md5sum. Can someone with S-ON try to flash Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img? (Again, standard disclaimer applies)
i like the very last sentence that you used ...
good job anyway mate !
how do you go about flashing a radio??
---------- Post added at 04:12 AM ---------- Previous post was at 04:09 AM ----------
rom1.zip is 10.370.252
rom2.zip is 10.586.425
ie not the same size
stevie67 said:
rom1.zip is 10.370.252
rom2.zip is 10.586.425
ie not the same size
Click to expand...
Click to collapse
If you look into the ZIP files, Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img and radio_47.23a.35.3035H_7.53.39.03M_MR.img are both the same size.
Reboot to HBOOT, choose FASTBOOT, connect WFS to computer. Use "fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img".
ok i tried to flash this radio i put the .img file on my sdcard went to fastboot then recovery,install from sdcard and there was nothing there so i put the rom1.zip folder on my sdcard went to fastboot,install from sdcard,rom1.zip and got this
CWM-based Recovery v5.0.2.6
-- Installing: /sdcard/rom_01.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom_01.zip
(bad)
Installation aborted
did i do something wrong??
You must flash the radio with fastboot command. But this wont work, bc the hboot will check if the file is signed. And that isn't.
But try, maybe i'm not right.
Sent from my HTC Wildfire S A510e using XDA App
and the fastboot command is??
and the file says its signed
Reboot to HBOOT, choose FASTBOOT, connect WFS to computer. Use "fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img".
Click to expand...
Click to collapse
He said it
Sent from my HTC Wildfire S A510e using XDA App
My phone wouldn't update using the HTC method so I extracted the two ROMs from the RUU and flashed them seperately. After the first one (radio) I noticed that the phone was S-OFF but when I'd flashed the second it was S-ON again and I couldn't go back.
WOW, you have S-OFF after flashing radio via
fastboot flash radio radio.img
???
And now you can't go back?
I extracted the htcdev ruu and tried to flash the radio image. but it is not possible, signature check fails. so if the bootloader is already unlocked, it is not possible to obtain s-off this way
Have u test it with
fastboot oem lock
first and then to flash the radio.img?
Or to try to downfrade hnoot with the tutorial here in forum and then flash the new radio.
not yet. Will try that and report again
did relock phone using oem lock.
*** RELOCKED ***
Tried flashing 1st radio from htcdev ruu
flashing successful, but still S-ON
Hmm, and can u try to downgrade to Hboot 0.9 or Hboot 1.08?
I'm a noob so it's possible I made a mistake but I'm pretty sure I was S-OFF after the first flash. I was on Hboot 0.09.0000. Unfortunately I didn't realise the significance at the time so proceeded anyway.
I will try
I will try too, but earliest tomorrow, then i have my windows pc
this is what i get with or without bootloader locked
C:\Android>fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.0
8M_Signed_20111208.img
sending 'radio' (23936 KB)...
OKAY [ 5.375s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.063s
stevie67 said:
this is what i get with or without bootloader locked
C:\Android>fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.0
8M_Signed_20111208.img
sending 'radio' (23936 KB)...
OKAY [ 5.375s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.063s
Click to expand...
Click to collapse
I extracted the rom1.zip and renamed it PG76IMG.zip and flashed via hboot. this worked when the phone was re-locked
theq86 said:
I extracted the rom1.zip and renamed it PG76IMG.zip and flashed via hboot. this worked when the phone was re-locked
Click to expand...
Click to collapse
so are you now s-off??
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