my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
eggyfish said:
my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
Click to expand...
Click to collapse
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
eggyfish said:
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
Click to expand...
Click to collapse
There is a newer version (2.8.7.1-CPTB-B1) which can be found in the beta version section here. Furthermore there is a stock backup provided in this thread that corresponds to your firmware version. Try to update TWRP and then to restore the backup.
Edit (Just to answer my own question from my previous post): The second Link provides a 1.40.401.8 RUU, too.
Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
and i still cant flash twrp
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
eggyfish said:
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
Click to expand...
Click to collapse
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
eggyfish said:
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
Click to expand...
Click to collapse
I actually don't see any error in that output. Everthing is the way it should be.
Flippy498 said:
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
I actually don't see any error in that output. Everthing is the way it should be.
Click to expand...
Click to collapse
hmm, thats strange as it didnt update, i get the same readout when i flash stock, but it stsys on twrp. sureley it cant be full as a ruu flash wipes your data, i think i'll try get a repair from htc, thanks for your help
Related
Hi, I've tried to root my htc one x with Insecure boot & root method without locking bootloader fist and it went into a bootloop, then I've tried to do the recovery from this guide http://forum.xda-developers.com/showthread.php?t=1609190 but i dont know where to find the correct ruu, also I cannot open rom.zip file form the ruu I've found RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed, my phone is from three uk. I'm not sure if it's rooted or not and don't really know how to check it from bootloader or revovery. Could anyone please help me, thanks.
kalasster said:
Hi, I've tried to root my htc one x with Insecure boot & root method without locking bootloader fist and it went into a bootloop, then I've tried to do the recovery from this guide http://forum.xda-developers.com/showthread.php?t=1609190 but i dont know where to find the correct ruu, also I cannot open rom.zip file form the ruu I've found RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed, my phone is from three uk. I'm not sure if it's rooted or not and don't really know how to check it from bootloader or revovery. Could anyone please help me, thanks.
Click to expand...
Click to collapse
please post the result from command fastboot getvar all and delete your IMEI and S/N.
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 5.1204.167.31H
version-cpld: None
version-microp: None
version-main: 4.18.771.4
serialno:
imei:
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: H3G__001
battery-status: good
battery-voltage: 3612mV
devpower: 0
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Click to expand...
Click to collapse
is that it?
Look here: http://forum.xda-developers.com/showthread.php?t=1975140
I think there is a nandroid for your phone.
This should be the one: https://dl.dropboxusercontent.com/u/64946445/JB-4.2.2-stock-factory_H3G_001.7z
Read instructions carefully!!
[email protected]|-|oR said:
Look here: http://forum.xda-developers.com/showthread.php?t=1975140
I think there is a nandroid for your phone.
This should be the one: https://dl.dropboxusercontent.com/u/64946445/JB-4.2.2-stock-factory_H3G_001.7z
Read instructions carefully!!
Click to expand...
Click to collapse
I cannot mount a device into PC in recovery mode, its comming on adb devices and I cant see it on devices manager. How to I copy rom on my sd card? I would actually would prefer to use Android Revolution HD mod is it possible?
kalasster said:
I cannot mount a device into PC in recovery mode, its comming on adb devices and I cant see it on devices manager. How to I copy rom on my sd card? I would actually would prefer to use Android Revolution HD mod is it possible?
Click to expand...
Click to collapse
How did you get the fastboot getvar all, then?
Did you try adb reboot recovery? It should work. Or, adb reboot bootloader, and once there, select recovery.
Do you have stock or custom recovery?
If on stock, download CWM from here: https://www.dropbox.com/s/2ph8jrr6lrmjqfc/fastboot.zip (there are other files, too, don't worry)
Flash CWM from fastboot and bootloader: fastboot flash recovery recovery-cwm.img
Go to your recovery and mount sd card.
Copy the nandroid backup and follow the instructions from the link in my previous post.
Once you're back to stock, you can flash any ROM at your will. These instructions are to get your phone out of bootloop.
icitiesc article
C:\android>fastboot flash revovery recovery-cwm.img
sending 'revovery' (5742 KB)...
OKAY [ 0.711s]
writing 'revovery'...
FAILED (remote: not allowed)
finished. total time: 0.917s
Click to expand...
Click to collapse
also i had cwm recovery before, but when I tried to use Mounts and storage menu/mount usb storage I'm getting back E:unable to opem ums lunfile(no such file or disc) am I doing something wrong?\
I also mount sd but still my PC doesnt see anything.
kalasster said:
also i had cwm recovery before, but when I tried to use Mounts and storage menu/mount usb storage I'm getting back E:unable to opem ums lunfile(no such file or disc) am I doing something wrong?\
I also mount sd but still my PC doesnt see anything.
Click to expand...
Click to collapse
Hm!
This is strange.
I recommend you uninstall HTC drivers, and try installing them again. That could be the reason of your trouble.
Do other fastboot commands work properly? Did you do fastboot erase cache? Sometimes that helps too.
There is also a way with "adb push..." but I don't remember it from the top of my head...
If Mr. Hofs woud be so kind to help you...
And, watch your battery, mate, don't let it drain out!
C:\android>fastboot flash revovery recovery-cwm.img
sending 'revovery' (5742 KB)...
OKAY [ 0.711s]
writing 'revovery'...
FAILED (remote: not allowed)
finished. total time: 0.917s
Click to expand...
Click to collapse
kalasster said:
also i had cwm recovery before, but when I tried to use Mounts and storage menu/mount usb storage I'm getting back E:unable to opem ums lunfile(no such file or disc) am I doing something wrong?\
I also mount sd but still my PC doesnt see anything.
Click to expand...
Click to collapse
First you must to flash recovery not REVOVERY. Second flash Philz recovery because it is the only one that work without any problem every time, mount SD storage and wait 1-3 minutes to mount the stodage and you can start restore nandroid.
Yeah flash philz indeed, the ems lunfile error is because you are using an old recovery that not support usb mass storage !
I already did it, now i cannot restore nandroid backup, because I cannot use JB version, since my hboot is to old and there is not firmware for my CID (H3G_001) so i cannot update hboot. I cannot find any older nandroid backup version for cwm recovery for my CID. Also when i tried to restore TWRP nandroid and I couldn't because I can't use touch in TWRP recovery. Anyone has any idea on how can I resolve this please?
Or is it something else my hboot ver is 1.72 and I cannot flash 16mb boot.img, but all of the nandroid recoveries I'm finding have one of that size.
kalasster said:
I already did it, now i cannot restore nandroid backup, because I cannot use JB version, since my hboot is to old and there is not firmware for my CID (H3G_001) so i cannot update hboot. I cannot find any older nandroid backup version for cwm recovery for my CID. Also when i tried to restore TWRP nandroid and I couldn't because I can't use touch in TWRP recovery. Anyone has any idea on how can I resolve this please?
Or is it something else my hboot ver is 1.72 and I cannot flash 16mb boot.img, but all of the nandroid recoveries I'm finding have one of that size.
Click to expand...
Click to collapse
Man install Philz recovery and this is your nandroid download and unzip in folder on the sd card flash the nandroid flash the boot.img flash the recovery.img from nandroid.
And the boot.img in this nandroid is only 8 MB from where you take this 16 MB
Thant said:
Man install Philz recovery and this is your nandroid download and unzip in folder on the sd card flash the nandroid flash the boot.img flash the recovery.img from nandroid.
And the boot.img in this nandroid is only 8 MB from where you take this 16 MB
Click to expand...
Click to collapse
Yeah, this is TWRP nandroid and TWRP is not working (no touch), i managed to just flash cyonogenmod though, so everything is fine, also i think i found firmware for my model, so I'll uprage hboot version and flash Revolution HD, thanks for your help everyone.
kalasster said:
Yeah, this is TWRP nandroid and TWRP is not working (no touch), i managed to just flash cyonogenmod though, so everything is fine, also i think i found firmware for my model, so I'll uprage hboot version and flash Revolution HD, thanks for your help everyone.
Click to expand...
Click to collapse
Philz recovery work with TWRP and CWM nandroid I can't understand what is your problem with Phi9lz recovery and why you can't restore nandroid!!!!
Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
HTCNerdYoda said:
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
OTA failure
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
ecmelg said:
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
Click to expand...
Click to collapse
Try flashing RUU for ur model id.
Alxens said:
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
Click to expand...
Click to collapse
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
HTCNerdYoda said:
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I have twrp backup system
would this work??
Alxens said:
Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
Click to expand...
Click to collapse
Esta solución me sirvió a mi. www . htc.com/us/support/rom- downloads . html (saca los espacios) en tú caso descarga la versión desbloqueada
Yes would work
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
sonoman87 said:
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
Click to expand...
Click to collapse
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
redpoint73 said:
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
Click to expand...
Click to collapse
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Thanks again!
sonoman87 said:
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Click to expand...
Click to collapse
If there is a MM RUU for your version, download and run it.
redpoint73 said:
If there is a MM RUU for your version, download and run it.
Click to expand...
Click to collapse
I've fixed it! Thanks so much again!
sonoman87 said:
I've fixed it! Thanks so much again!
Click to expand...
Click to collapse
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
oscar1355 said:
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
Click to expand...
Click to collapse
First of all, you need to understand that ROM and RUU are two very different things.
Also, nobody can advise you the proper RUU is, without knowing some basic information. Namely, do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
Hey everyone,
I am trying to get my M8 to stock (been stuck at this for about 10 days now, tried everything). I am from India. There was some problem and I accidentally have a phone now with no OS and TWRP. I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device:
Software status: Modified
Unlocked S-ON
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <serial number>
(bootloader) imei: <imei number>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would really appreciate it if you could guide me how to get my phone to stock OS. The ROM that I should prefer etc. I have been going through a lot of forums and ended up being utterly confused.
Thanks in advance for the help!
skull_143 said:
been stuck at this for about 10 days now, tried everything
There was some problem and I accidentally have a phone now with no OS and TWRP.
Click to expand...
Click to collapse
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
skull_143 said:
I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device
Click to expand...
Click to collapse
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
redpoint73 said:
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
Click to expand...
Click to collapse
Sorry about the shortened version, just though it might be too big and unnecessary. Okay here goes what happened. I moved the whatsapp media to my laptop (at this time the device was unrooted and running stock android M updated over OTA). After the move, the device was stuck at the splash screen with HTC logo. After this I gave the phone to a service centre (not official HTC) and asked them to NOT root and put stock OS and get the phone working. What they did was, rooted it and installed a custom ROM with TWRM recovery (which was very screwed up, as in the camera kept crashing and I couldn't even use that). So, I decided to get it back to stock ROM and sense UI.
So what I did was looked up some thread (not sure which one) and went ahead to do a wipe through recovery. Here I did the mistake of wiping everything and so the device doesn't have any OS at the moment. The phone is still getting stuck in HTC logo now (obviously as it doesn't have an OS). I have tried to do the following:
1. To flash the boot only using fastboot flash boot and fastboot flash zip commands. The version I tried was stock 3.35.720.1_recovery.img. This didnt seem to work.
2. Next tried to go to usb fastboot mode and tried to run the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe official one from the laptop. But it showed some mismatch of versions and aborted.
3. Then I read that stock could only be flashed on S-ON devices if we relock the bootloader. So used the fastboot oem relock command to relock bootloader and then tried both the above but didn't work.
4. Next saw somewhere that it is pretty impossible to flash on a locked S-ON device. So went to htcdev and got the bootloader unlocked again.
5. Downloaded a stock image 3.35.720.1 Stock Unrooted. Read that we need lower or same stock recovery to flash the same and so flashed the stock recovery of the same version. Next extracted the .win001 and .win002 files using the tar command and finally put them along with META_INF folder and boot.img files into a zip file. The image had the contents of the system folder and tried to flash this using fastboot and also through the stock option "Update from SD card". Got error "E: footer is wrong. E: update signature verification failed".
This is the status so far. I am not sure what I should be doing anymore. Hope this helps in understanding the situation. Sorry it's so long.
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
skull_143 said:
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
Click to expand...
Click to collapse
1. Download the 6.15.720.2 RUU.zip : http://forum.xda-developers.com/showpost.php?p=66309774&postcount=20
2. relock the bootloader with command - fastboot oem lock
option 1 - if you have a microsd
1. rename the downloaded RUU.zip as to 0P6BIMG.zip
2. put it on root of your microsd not in any folder
3. on bootloader select hboot - it will scan the zip and ask you to update.
4. select volume up to update
5. once completed, delete the zip from microsd
option 2
1. Download htc_fastboot.exe : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
2. put both htc_fastboot.exe and the 0P6BIMG.zip in your fastboot folder
3. run below commands :
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip 0P6BIMG.zip (to install RUU - read it is htc_fastboot not fastboot)
Once complete - fastboot reboot
run setup .. done
Tried rooting my phone to recover lost important photos for university studies and now i'm stuck with a relocked, S-ON phone.
Having S-on is not letting me do anything, I've tried recovery which fails and flashing zip also I've tried unlocking with token code.
C:\Users\Josh\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.771.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_93.00.51117G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: H3G__001
Thank you for your time
It would appear that you've properly goosed it.
You need to unlock the bootloader first. Without this you can't proceed.
Then try flashing twrp that is version 3.0.0.0 or LESS and see if you can then get to recovery.
If you can get into twrp you need to mount system as read only and take a backup of system and data.
If you can't get to twrp recovery you'll need to flash back to stock firmware and start over.
Once you've taken a backup of system and data you can mount system as read/write (r/w or rw) and flash supersu 2.65.
You should then have a bootable rooted phone with a backup incase something goes a rye.
S-off is only obtained through an app called "sunshine" which cannot be found on googleplay. It will cost 25$/£18 to complete the s-off procedure. Provided that you use the proper apk from the sunshine website you should not encounter any issues as the app will guide you through the entire process and do everything for you except pay, for which you'll need a credit/debit card or paypal. Upon completion sunshine will issue a license that it will use in future should you ever need to unlock it again.
The only other way to s-off is via expensive hardware which costs more than the sunshine app charges.
Beamed in by telepathy.
shivadow said:
It would appear that you've properly goosed it.
You need to unlock the bootloader first. Without this you can't proceed.
Then try flashing twrp that is version 3.0.0.0 or LESS and see if you can then get to recovery.
If you can get into twrp you need to mount system as read only and take a backup of system and data.
If you can't get to twrp recovery you'll need to flash back to stock firmware and start over.
Once you've taken a backup of system and data you can mount system as read/write (r/w or rw) and flash supersu 2.65.
You should then have a bootable rooted phone with a backup incase something goes a rye.
S-off is only obtained through an app called "sunshine" which cannot be found on googleplay. It will cost 25$/£18 to complete the s-off procedure. Provided that you use the proper apk from the sunshine website you should not encounter any issues as the app will guide you through the entire process and do everything for you except pay, for which you'll need a credit/debit card or paypal. Upon completion sunshine will issue a license that it will use in future should you ever need to unlock it again.
The only other way to s-off is via expensive hardware which costs more than the sunshine app charges.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you very much for your help and time
I've managed to unlock phone and get back on to recovery mode and done all of the above, but now i'm stuck in a bootloop. Anymore suggestions?
jpall91 said:
Thank you very much for your help and time
I've managed to unlock phone and get back on to recovery mode and done all of the above, but now i'm stuck in a bootloop. Anymore suggestions?
Click to expand...
Click to collapse
flashed the twrp 3.0.0.0 and flashed supersu 2.65
jpall91 said:
flashed the twrp 3.0.0.0 and flashed supersu 2.65
Click to expand...
Click to collapse
Did you get it to boot or not?.
If not then flash an older twrp. My phone, running Marshmallow 6.0 runs this twrp: https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk
Beamed in by telepathy.
shivadow said:
Did you get it to boot or not?.
If not then flash an older twrp. My phone, running Marshmallow 6.0 runs this twrp: https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk
Beamed in by telepathy.
Click to expand...
Click to collapse
hi shivadow
No i didnt get it to boot it just restarts with htc logo and red writing.
However i tried your twrp 2.9.0.1 and it failed to boot in recovery mode.
On the security warning on download mode it says: FILE /mnt/media_rw/ext_sd/0PJAIMG.zip File NOT FOUND
Do i need to re flash stock boot image??
jpall91 said:
hi shivadow
No i didnt get it to boot it just restarts with htc logo and red writing.
However i tried your twrp 2.9.0.1 and it failed to boot in recovery mode.
On the security warning on download mode it says: FILE /mnt/media_rw/ext_sd/0PJAIMG.zip File NOT FOUND
Do i need to re flash stock boot image??
Click to expand...
Click to collapse
Yep, I'd attempt to return it back to stock at this point.
I highly doubt this phone is recoverable at this stage. It would seem like the recovery partition is corrupt
Beamed in by telepathy.
Help me , I was trying to get s-off on my m8 with firewater, and it wasn't working because superSU wouldn't grant shell access(it wasn't the pro version), so i looked on the internet and found a supersu v2.02 zip file. I flashed it in twrp/recovery then after rebooting, it got stuck in a bootloop. the phone is rooted/unlocked, access to recovery, no access to adb/fastboot because my phone wont connect to the pc.
does anyone know a fix to this? Pretty desperate because this is the only phone I got.
also I was stupid enough not to have a backup saved :/ I tried everything... formatting from bootloader, wiping phone in recovery.. nothings working.
You are using methods from 3 years ago. You need to look at the current (or at least, the most updated as possible) root and s-off methods for your device.
braydenp said:
so i looked on the internet and found a supersu v2.02 zip file. I flashed it in twrp/recovery then after rebooting, it got stuck in a bootloop.
Click to expand...
Click to collapse
In particular, that SuperSU is ancient (3 years?) and probably wouldn't work with any Android version on the phone, except KitKat.
Assuming you were on Marshmallow before trying to root (most folks are, at this point) the proper SuperSU version would be the current stable SuperSU, which is 2.79: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Literally, you were using a SuperSU versions that is 77 iterations obsolete. Flashing the proper version SuperSU should solve the bootloop issue. Although your user data is now gone, since you wiped/factory reset (which as you now known, is not a valid fix for the problem).
braydenp said:
I was trying to get s-off on my m8 with firewater, and it wasn't working because superSU wouldn't grant shell access
Click to expand...
Click to collapse
Getting shell SU access won't help you. Firewater stopped being supported 2-1/2 years ago. Since it had an online server component required to work, nothing you do will get firewater to work. So you can stop trying.
The only valid s-off method is sunshine app ($25 US): http://theroot.ninja/
redpoint73 said:
You are using methods from 3 years ago. You need to look at the current (or at least, the most updated as possible) root and s-off methods for your device.
In particular, that SuperSU is ancient (3 years?) and probably wouldn't work with any Android version on the phone, except KitKat.
Assuming you were on Marshmallow before trying to root (most folks are, at this point) the proper SuperSU version would be the current stable SuperSU, which is 2.79: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Literally, you were using a SuperSU versions that is 77 iterations obsolete. Flashing the proper version SuperSU should solve the bootloop issue. Although your user data is now gone, since you wiped/factory reset (which as you now known, is not a valid fix for the problem).
Getting shell SU access won't help you. Firewater stopped being supported 2-1/2 years ago. Since it had an online server component required to work, nothing you do will get firewater to work. So you can stop trying.
The only valid s-off method is sunshine app ($25 US): http://theroot.ninja/
Click to expand...
Click to collapse
I slight had a feeling that's why firewater wasn't working xD. I guess sunshine is the only way... well,.. i did get the latest version of supersu, but i noticed that i still can't get past bootloop eitherway because I have no OS installed from wiping my device in my attempt of "fixing" things. I gotta somehow find a 4.20.666.2 backup zip to flash(if there's even any on the internet) :/
braydenp said:
I guess sunshine is the only way
Click to expand...
Click to collapse
No guesswork here. Sunshine is the only way.
Unless you count spending $150+ on a javacard. Which of course makes no sense, when sunshine costs $25.
braydenp said:
i did get the latest version of supersu, but i noticed that i still can't get past bootloop eitherway because I have no OS installed from wiping my device in my attempt of "fixing" things.
Click to expand...
Click to collapse
If you wiped "system" in the TWRP "Advanced" wipe section, then you wiped the OS, and therefore (somewhat obviously) have no OS to boot.
If you were wiping things, without knowing what they are, or what the result would be; then that behavior needs to stop immediately!
Also, another good basic rule of thumb (good common sense on any Android device) is not to do any mods (root, custom ROM, etc.) without first knowing how to return to stock.
You can return to stock by using the guide and files in the following thread. Important to note, that these are not flashable zips. You need to follow the instructions carefully, extract the files and save them to the proper location on the phone, then boot TWRP and Restore (not Install like a ROM or other flashable zip): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I did give that a try earlier.. my only problem is, I Haven't been able to connect to adb/fastboot ever since I got into the bootloop(probably because I can't get past reboot), not even mount usb storage, nor does adb sideload works, how can I get adb to work so i can return to stock?
braydenp said:
i tried that kind of... my only problem is, I cant connect to adb/fastboot(adb devices wont work in cmd) ever since I got into the bootloop. mount usb storage doesn't work, nor does adb sideload, how can I get adb to work so i can return to stock?
Click to expand...
Click to collapse
Make sure you are in the correct mode:
Fastboot only works in bootloader-fastboot mode.
adb only works in OS (not an option, in the current condition) or in TWRP.
You should also be able to access the phone's internal storage (and SD card, if you have one) on your PC, when phone is booted to TWRP. In which case, you can copy the needed TWRP stock backup files to internal storage or SD.
i got an sd card and can access internal storage so no worries in that area, just curious, is there another way to get the device serial/imei number?
oh wait nvm found it, it was in barcode
braydenp said:
i got an sd card and can access internal storage so no worries in that area, just curious, is there another way to get the device serial/imei number?
Click to expand...
Click to collapse
You mean, for the purpose of putting the TWRP backup folder in the right place?
If so, you can simply boot into TWRP, select Backup, then make a "dummy" backup by selecting to backup boot.img (just because it's the smallest thing to backup) and picking the desired the backup location (SD card or internal storage). TWRP will then create the necessary folder structure (including serial number), and you can simply copy the downloaded/extracted stock TWRP backup folders to that location.
It's actually preferable to do it this way, as any error in folder structure/names will result in TWRP not "seeing" the backup and unable to restore it.
redpoint73 said:
You mean, for the purpose of putting the TWRP backup folder in the right place?
If so, you can simply boot into TWRP, select Backup, then make a "dummy" backup by selecting to backup boot.img (just because it's the smallest thing to backup) and picking the desired the backup location (SD card or internal storage). TWRP will then create the necessary folder structure (including serial number), and you can simply copy the downloaded/extracted stock TWRP backup folders to that location.
It's actually preferable to do it this way, as any error in folder structure/names will result in TWRP not "seeing" the backup and unable to restore it.
Click to expand...
Click to collapse
Yes. it created the folder all for me with the code on it. what do i do with the 4.20.666.2_ckpv5.zip folder? it looks like its got some important OS stuff in it, & ty for pointing out that the boot stuff goes into the recovery.img folder
nvm about the extra folder i just added the system 'n data stuff in the recovery folder and its working now. thank you for helping me
:victory: on step 11 now pretty much done, ty )
huh... :/ the fastboot flash recovery x.xxx.xx.x_recovery.img command ain't working in fastboot
i got the fastboot flash recovery to work, ran it, rebooted to get ota's but nothing came, still no OS i guess because its still stuck in bootloop and after doing all of that, twrp is gone.
yeah, no OTA's, installed twrp again and it gets rid of twrp when i run the flash recovery file in fastboot then no ota's afterwards... i wonder if its because im running the recovery.img file from the sdk/adb file location instead of twrp/backup/serialno./... on the device, is that where I'm going wrong or is it something else? the boot, system and data files installed nicely though
braydenp said:
Yes. it created the folder all for me with the code on it. what do i do with the 4.20.666.2_ckpv5.zip folder? it looks like its got some important OS stuff in it
Click to expand...
Click to collapse
Looks like you figured it out, but in interest of not confusing anyone else which may read this post: the zip folder contains all the folders which makeup the stock TWRP backup. So yes, it's not just important, it's the whole point of what you are trying to restore. The instructions are very explicit about what to do with the zip. You need to extract it on a computer, then save the extracted folders to the exact location on the phone (although it can be SD card or internal storage) indicated in the instructions.
braydenp said:
ty for pointing out that the boot stuff goes into the recovery.img folder
Click to expand...
Click to collapse
The boot folder (extracted from the zip) goes in the TWRP folder on the phone, which has nothing to do with the recovery.img
Be careful there not to mix up the terms. They are 2 very different things (TWRP folders vs. recovery.img).
recovery.img is either TWRP itself, or the stock recovery (the "official" HTC recovery for installing OTAs, etc.).
---------- Post added at 09:45 AM ---------- Previous post was at 09:39 AM ----------
braydenp said:
i got the fastboot flash recovery to work . . . and after doing all of that, twrp is gone.
Click to expand...
Click to collapse
The fastboot flash recovery command over-writes TWRP with the "stock" (official HTC) recovery (which is needed to install OTAs). So literally, the reason TWRP is gone, is due to the fact that you literally performed the action to erase it, and replace it with the stock recovery.
Am I understanding you correctly, that the phone is not booting to OS properly, but when you do to Settings and check for updates, there are none?
redpoint73 said:
Looks like you figured it out, but in interest of not confusing anyone else which may read this post: the zip folder contains all the folders which makeup the stock TWRP backup. So yes, it's not just important, it's the whole point of what you are trying to restore. The instructions are very explicit about what to do with the zip. You need to extract it on a computer, then save the extracted folders to the exact location on the phone (although it can be SD card or internal storage) indicated in the instructions.
The boot folder (extracted from the zip) goes in the TWRP folder on the phone, which has nothing to do with the recovery.img
Be careful there not to mix up the terms. They are 2 very different things (TWRP folders vs. recovery.img).
recovery.img is either TWRP itself, or the stock recovery (the "official" HTC recovery for installing OTAs, etc.).
---------- Post added at 09:45 AM ---------- Previous post was at 09:39 AM ----------
The fastboot flash recovery command over-writes TWRP with the "stock" (official HTC) recovery (which is needed to install OTAs). So literally, the reason TWRP is gone, is due to the fact that you literally performed the action to erase it, and replace it with the stock recovery.
Am I understanding you correctly, that the phone is not booting to OS properly, but when you do to Settings and check for updates, there are none?
Click to expand...
Click to collapse
When i try to flash the 4.20.666.2_recovery.img while its in the sdktools folder on my pc it wont install OTA's.
fastboot wont reach my phones internal storage twrp/backups/SerialNO./Recovery.img when i try flashing with the recovery.img in my phones storage. i got all the paths set up properly for fastoot/abd.. why wont it reach unless i have the recovery.img in sdktools folder on my pc? after i flash the recovery.img from sdkfile no OTA's are popping up after the phone reboots
error: cannot load '4.20.666.2_Recovery.img' when i try flashing it from twrp/backups/SerialNO./Recovery.img
braydenp said:
When i try to flash the 4.20.666.2_recovery.img while its in the sdktools folder on my pc it wont install OTA's, fastboot wont reach the twrp/backups/SerialNO./Recovery.img on my phones internal storage when i try flashing it. i got all the paths set up properly for fastoot/abd.. why wont it work unless i have the recovery.img in sdktools folder on my pc?
Click to expand...
Click to collapse
Fastboot is for flashing a file from your computer, to your phone. I've never seen anyone try to fastboot flash a file that resides on the phone's SD or internal storage; I don't think you can do that, nor is there a reason to do so.
Not receiving OTAs is not a problem with how you have stock recovery installed. If you have the right recovery (matches the TWRP, and it's installed, and matches the firmware) then the problem is somewhere else. Might just be a bug in the OTA system.
I'd like to verify you are restoring the right version number TWRP backup, and the right number recovery. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------
braydenp said:
error: cannot load '4.20.666.2_Recovery.img' when i try flashing it from twrp/backups/SerialNO./Recovery.img
Click to expand...
Click to collapse
Not a valid way to run the fastboot command, as already mentioned. The file should be on the computer, not on the phone.
Let me try to explain it in simple terms:
TWRP: Makes backup files of the ROM and kernel (boot.img), and can restores those. These backup files are saved to the phone's internal storage or SD. By moving/copying the files from the stock backup collection, you are "tricking" TWRP into thinking it is a backup that you made with TWRP. Everything is done by the phone, the computer is just used to move the files to the phone.
Fastboot: Use fastboot to replace TWRP with the "stock" recovery, which is required for OTA. The file and tool (fastboot) reside on the computer.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.666.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:******
(bootloader) imei: *******
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c7c8c7ac
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
alright, well my only problem now it getting the OTA's, everything is setup like in the tutorial proper versions for my OS...
hello
Since the new OTA came e cant upgrade because give a error "Can't update software. There was an unexpected error and the file f system may be corrupted. Please contact HTC support"
I´m S-OFF/LOCKED and stock rom 2.41.401.3 that i flash from a RUU.EXE because i want to take OFFICIAL STATUS
Before that i had a S-ON/UNLOCK and a 2.41.401.4 stock but ROOTED and MODIFIED STATUS
i downgrade because i had a lot of reboots.
I have try to flash 2.41.401.41 via fastboot flash zip
dry to rename the file to "2PS6IMG.ZIP and flash in download mode
but e receive always 22 RU_HEADER_ ERROR
please help
enduromen said:
hello
Since the new OTA came e cant upgrade because give a error "Can't update software. There was an unexpected error and the file f system may be corrupted. Please contact HTC support"
I´m S-OFF/LOCKED and stock rom 2.41.401.3 that i flash from a RUU.EXE because i want to take OFFICIAL STATUS
Before that i had a S-ON/UNLOCK and a 2.41.401.4 stock but ROOTED and MODIFIED STATUS
i downgrade because i had a lot of reboots.
I have try to flash 2.41.401.41 via fastboot flash zip
dry to rename the file to "2PS6IMG.ZIP and flash in download mode
but e receive always 22 HEADER RUU ERROR
please help
Click to expand...
Click to collapse
Reflash RUU will get you to stock. But will wipe everything. Then you can take the OTA. Also this should be in the Q&A section
i did it right now and upgrade too 2.41.401.4 with RUU.exe but still the same problema can´t upgrade
enduromen said:
i did it right now and upgrade too 2.41.401.4 with RUU.exe but still the same problema can´t upgrade
Click to expand...
Click to collapse
Whats your CID
HTC__001
I'm complet stock exception the S-OFF so I don't see a reason that I can't upgrade
Do you think S-OFF state could be the reason?
enduromen said:
I'm complet stock exception the S-OFF so I don't see a reason that I can't upgrade
Do you think S-OFF state could be the reason?
Click to expand...
Click to collapse
No you should be able to take OTA if you flashed RUU. Are you still getting the same error message?
yldlj said:
No you should be able to take OTA if you flashed RUU. Are you still getting the same error message?
Click to expand...
Click to collapse
yes, as i saided i flashed RUU.EXE 2.41.401.4 (bootloader is LOCKED and OFFICIAL STATUS) and the same error
Flash in download mode get this
C:\adb>fastboot flash zip OTA_PERFUME_UHL_N70_SENSE80GP_MR_HTC_Europe_2.41.401.41-2.41.401.4_release_508220k03ww80trnr46pl3.zip
target reported max download size of 1579200000 bytes
sending 'zip' (266199 KB)...
OKAY [ 14.049s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 15.179s
enduromen said:
yes, as i saided i flashed RUU.EXE 2.41.401.4 (bootloader is LOCKED and OFFICIAL STATUS) and the same error
Flash in download mode get this
C:\adb>fastboot flash zip OTA_PERFUME_UHL_N70_SENSE80GP_MR_HTC_Europe_2.41.401.41-2.41.401.4_release_508220k03ww80trnr46pl3.zip
target reported max download size of 1579200000 bytes
sending 'zip' (266199 KB)...
OKAY [ 14.049s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 15.179s
Click to expand...
Click to collapse
Lol xD you can't flash this that easy in fastboot not download mode xD you have to either name it to MID number .zip or download it from directly on the phone and let it install . Stock recovery mandatory if you flash this way. There is a way with TWRP, but a lot more to do
Sent from my HTC 10 using XDA Labs
thanks for your answer
"download it from directly on the phone and let it install " i cant because the phone give a error "Can't update software. There was an unexpected error and the file f system may be corrupted. Please contact HTC support"
i rename the OTA file to 2PS6IMG.ZIP put on SDcard go to download mode and the same 22 RU_HEADER_ERROR
to you have some other sugestion?? I have stock recovery because i flash a RUU.EXE
Ps- also try flash in recovery doing UPDATE FROM SD but give a signed error
thanks for your answer
"download it from directly on the phone and let it install " i cant because the phone give a error "Can't update software. There was an unexpected error and the file f system may be corrupted. Please contact HTC support"
i rename the OTA file to 2PS6IMG.ZIP put on SDcard go to download mode and the same 22 RU_HEADER_ERROR
to you have some other sugestion?? I have stock recovery because i flash a RUU.EXE
Ps- also try flash in recovery doing UPDATE FROM SD but give a signed error
flash TRWP and to a restore from a Untouched System Image + Boot +stock recovery is not the same thing that flash a RUU.EXE?
enduromen said:
thanks for your answer
"download it from directly on the phone and let it install " i cant because the phone give a error "Can't update software. There was an unexpected error and the file f system may be corrupted. Please contact HTC support"
i rename the OTA file to 2PS6IMG.ZIP put on SDcard go to download mode and the same 22 RU_HEADER_ERROR
to you have some other sugestion?? I have stock recovery because i flash a RUU.EXE
Ps- also try flash in recovery doing UPDATE FROM SD but give a signed error
flash TRWP and to a restore from a Untouched System Image + Boot +stock recovery is not the same thing that flash a RUU.EXE?
Click to expand...
Click to collapse
try the sytem image. worked for me too. sometimes something is broken and with an untouched system image you can install the update again. or just get latest system image and no need of installing the update anymore xD
but let me ask again. your phone is s-off, with locked bootloader right? normally after a RUU you should be able to either install it via downloading directly on the phone and install it there. or you should be also able to flash it like anyone else through either download mode when renamed or even in stock recovery. you can try to boot into stock recovery, apply that zip for installation. maybe that works for you. if you try a full factry reset throught fastboot or stock recovery. I forgot what I exactly did. but one of those steps helped me
answer your question YES i´m S-OFF and LOCKED and STOCK RECOVERY.
"normally after a RUU you should be able to either install it via downloading directly on the phone and install it there. or you should be also able to flash it like anyone else through either download mode when renamed or even in stock recovery"
fully agree with you but i cant i just do it all and nothing work
After Flash RUU.EXE i do a factory reset in stock recovery but didnt help still can download in the phone
"you can try to boot into stock recovery, apply that zip for installation" i did it and the result is "signature verification failed"
just dont do a restore system image in TWRP because i think the result was the same that flash the RUU but maybe it isnt
any one more sugestion that can help?
enduromen said:
answer your question YES i´m S-OFF and LOCKED and STOCK RECOVERY.
"normally after a RUU you should be able to either install it via downloading directly on the phone and install it there. or you should be also able to flash it like anyone else through either download mode when renamed or even in stock recovery"
fully agree with you but i cant i just do it all and nothing work
After Flash RUU.EXE i do a factory reset in stock recovery but didnt help still can download in the phone
"you can try to boot into stock recovery, apply that zip for installation" i did it and the result is "signature verification failed"
just dont do a restore system image in TWRP because i think the result was the same that flash the RUU but maybe it isnt
any one more sugestion that can help?
Click to expand...
Click to collapse
Find and Download the RUU zip file instead of the .exe. rename the RUU zip to 2PS6IMG.zip, place on ex sdcard, boot to download mode and press uo to flash. The RUU zip has never failed for me as i can take OTA's straight after.
yldlj said:
Find and Download the RUU zip file instead of the .exe. rename the RUU zip to 2PS6IMG.zip, place on ex sdcard, boot to download mode and press uo to flash. The RUU zip has never failed for me.
Click to expand...
Click to collapse
The ruu.exe works for him, afterwords he just can't install the it's because something is triggered.
@ OP did you download the zip, go into data/data/updater.htc-something folder and take the zip. You need either root or custom recovery for that. And try to flash that. If you've done that already. Don't know just get either latest ruu if finally available or take the system image of the latest and restore it. For some it works for some not
Sent from my HTC 10 using XDA Labs
DeeZZ_NuuZZ said:
The ruu.exe works for him, afterwords he just can't install the it's because something is triggered.
@op did you download the zip, go into data/data/updater.htc-something folder and take the zip. You need either root or custom recovery for that. And try to flash that. If you've done that already. Don't know just get either latest ruu if finally available or take the system image of the latest and restore it. For some it works for some not
Click to expand...
Click to collapse
Yeah i know but something isnt right as after flashing RUU he still cant update which to me is very strange. What i ment in my post was after flashing an RUU you should be able to take the ota and using the RUU zip has always worked for me to do that
Try go into stock recovery, there shall be an option to sideload OTA file, then use adb sideload OTAfile.zip, this is how I manually apply OTA.
also check the md5 to see if the OTA file is correct.
https://forum.xda-developers.com/showpost.php?p=73528777&postcount=2188
also try 401.3 ruu to see if that help
DeeZZ_NuuZZ said:
The ruu.exe works for him, afterwords he just can't install the it's because something is triggered.
@ OP did you download the zip, go into data/data/updater.htc-something folder and take the zip. You need either root or custom recovery for that. And try to flash that. If you've done that already. Don't know just get either latest ruu if finally available or take the system image of the latest and restore it. For some it works for some not
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
no is not I can't even download in phone so there it's is not in that folder. I downloaded here in update thread
Will try flash ruu.zip but before I install a run.exe this gave me a error to
TRY THIS>>> https://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187