TWRP Says Invalid Zip format. Phone seems bricked. - HTC 10 Questions & Answers

I have an HTC 10 Sprint version. After the last big update, I decided I didnt really like it so I wanted to root my phone and install a custom rom, or even just the stock rom but get some cool root apps that could help me deal with some of the changes to the OS. I had previously rooted my HTC One M8 and it went through flawlessly.
So I was following a guide and everything went well until I started getting an error while trying to wipe the data on the phone.
The full process went something like this: Download all the stuff i need, booted the phone into download mode, used the command prompt to get the token, unlocked the bootloader, flashed twrp(all with the cmd prompt) and then attempt to wipe data using twrp on the phone. It kept saying something like "failed to mount data." I found a guide on how to fix this, and it worked. However, I didnt do it right. The guide said to change the file system types and then wipe them, but I did it to the system data, which seems to have wiped my OS. Apparently I was only supposed to wipe data and cache... woops.
I didnt think that was a big deal, because I could just flash a new rom, like I did on my old phone. However, I have tried 2 separate zip roms and both are giving me an error that says "invalid zip format." The forum posts I have found about this error simply resolved it by redownloading. So i redownloaded the zip twice and it failed both times. I found out that the page I got the zips from,
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
said to rename them first, so I renamed them and tried all 3 again. I tried putting them on the micro sd card and on internal storage. I get the same error every time.
So it seems that I am stuck and I cant find an easy-to-understand forum post with a solution to this particular issue. I assume that because I have twrp installed that I can find a way to get a rom on it, I just dont know how...
Can anyone help me out here?

ciano25 said:
I have an HTC 10 Sprint version. After the last big update, I decided I didnt really like it so I wanted to root my phone and install a custom rom, or even just the stock rom but get some cool root apps that could help me deal with some of the changes to the OS. I had previously rooted my HTC One M8 and it went through flawlessly.
So I was following a guide and everything went well until I started getting an error while trying to wipe the data on the phone.
The full process went something like this: Download all the stuff i need, booted the phone into download mode, used the command prompt to get the token, unlocked the bootloader, flashed twrp(all with the cmd prompt) and then attempt to wipe data using twrp on the phone. It kept saying something like "failed to mount data." I found a guide on how to fix this, and it worked. However, I didnt do it right. The guide said to change the file system types and then wipe them, but I did it to the system data, which seems to have wiped my OS. Apparently I was only supposed to wipe data and cache... woops.
I didnt think that was a big deal, because I could just flash a new rom, like I did on my old phone. However, I have tried 2 separate zip roms and both are giving me an error that says "invalid zip format." The forum posts I have found about this error simply resolved it by redownloading. So i redownloaded the zip twice and it failed both times. I found out that the page I got the zips from,
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
said to rename them first, so I renamed them and tried all 3 again. I tried putting them on the micro sd card and on internal storage. I get the same error every time.
So it seems that I am stuck and I cant find an easy-to-understand forum post with a solution to this particular issue. I assume that because I have twrp installed that I can find a way to get a rom on it, I just dont know how...
Can anyone help me out here?
Click to expand...
Click to collapse
What version of Twrp?
Make sure you have the latest version...
Best bet at this point, would be to RUU, especially if your Twrp is already current.
Sent from my HTC6545LVW using Tapatalk

ciano25 said:
I have an HTC 10 Sprint version. After the last big update, I decided I didnt really like it so I wanted to root my phone and install a custom rom, or even just the stock rom but get some cool root apps that could help me deal with some of the changes to the OS. I had previously rooted my HTC One M8 and it went through flawlessly.
So I was following a guide and everything went well until I started getting an error while trying to wipe the data on the phone.
The full process went something like this: Download all the stuff i need, booted the phone into download mode, used the command prompt to get the token, unlocked the bootloader, flashed twrp(all with the cmd prompt) and then attempt to wipe data using twrp on the phone. It kept saying something like "failed to mount data." I found a guide on how to fix this, and it worked. However, I didnt do it right. The guide said to change the file system types and then wipe them, but I did it to the system data, which seems to have wiped my OS. Apparently I was only supposed to wipe data and cache... woops.
I didnt think that was a big deal, because I could just flash a new rom, like I did on my old phone. However, I have tried 2 separate zip roms and both are giving me an error that says "invalid zip format." The forum posts I have found about this error simply resolved it by redownloading. So i redownloaded the zip twice and it failed both times. I found out that the page I got the zips from,
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
said to rename them first, so I renamed them and tried all 3 again. I tried putting them on the micro sd card and on internal storage. I get the same error every time.
So it seems that I am stuck and I cant find an easy-to-understand forum post with a solution to this particular issue. I assume that because I have twrp installed that I can find a way to get a rom on it, I just dont know how...
Can anyone help me out here?
Click to expand...
Click to collapse
Which of the files from that thread are you trying to flash? If they're RUU files you won't be able to flash them from TWRP, they need to be flashed in download mode which you can't do easily (downgrading from Oreo to Nougat) unless you're s-off.
If you're talking about the ROM zip linked in the last post of that thread, it should work. What are the steps you're doing in twrp?

santod040 said:
What version of Twrp?
Make sure you have the latest version...
Best bet at this point, would be to RUU, especially if your Twrp is already current.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
3.2.1-2 is on the phone
I believe it is current, because i tried first with the one in the guide and it wouldnt flash, so i went to the twrp site and got the latest version and it flashed.
i tried running one of the .exe versions from that page i linked and from the htc website. both gave me an error that it could not be installed.

Tarima said:
Which of the files from that thread are you trying to flash? If they're RUU files you won't be able to flash them from TWRP, they need to be flashed in download mode which you can't do easily (downgrading from Oreo to Nougat) unless you're s-off.
If you're talking about the ROM zip linked in the last post of that thread, it should work. What are the steps you're doing in twrp?
Click to expand...
Click to collapse
I tried all three. neither zip is a "valid" format and the .exe one gave me an error that it could not install onto my device.
Here's what I am doing: Put phone in recover mode, drag files to the sd card or storage, and then hit install on twrp, find the file, and attempt to install.
I am currently trying a recovery zip that i got from here: https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
TWRP does not see that zip when I hit the recovery button, but it does see it when I hit the install button. Unfortunately, I get the same error.
EDIT FOR MORE INFO: I just ran the exe again to get the error code: ERROR [132]: SIGNARURE ERROR .... Please get the correct ROM Update Utility and try again. And yes, it says signarure, not signature... lol
Even more info: I am apparently trying to go from version 3.18.651.3 to version 2.51.651.31 Could it be an issue going backwards like that?

So I decided to just scroll further down on that page and download a rom that i really didnt want. I got the Bad Boyz Rooted rom or whatever. It seems to be working. Twrp installed it with no issue. I really just wanted as close to bone stock as possible, or totally crazy out-there roms, but if my phone works, then I am ok with it, for now at least. It says android is starting and its optimizing all the apps. If this rom can actually get ota updates to get back to oreo, then I will stick with it.
Thanks for the help!

Unfortunately, the 10 seems to be a bit weird when trying to flash and root. For instance, Nexus 5 is much easier to root and flash custom rom.
I have tried to flash Lineage OS on the 10, which messed up radio signal. Luckily, I have made a stock image backup previously.
Rooting can mess up radio as well, at least rooting with SuperSu. Magisk worked without any problem.
Now I'm waiting for LOS 15.1, hopefully they will release it soon.
Sent from my HTC 10 using Tapatalk

petar01 said:
Unfortunately, the 10 seems to be a bit weird when trying to flash and root. For instance, Nexus 5 is much easier to root and flash custom rom.
I have tried to flash Lineage OS on the 10, which messed up radio signal. Luckily, I have made a stock image backup previously.
Rooting can mess up radio as well, at least rooting with SuperSu. Magisk worked without any problem.
Now I'm waiting for LOS 15.1, hopefully they will release it soon.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
"Correlation does not imply causation."
LOS has nothing to do with firmware (the radio). Likewise with SuperSU/root apps.
re: "seems" bricked; "seems" to be a bit weird: if you use the word, "seems", that means you have to further diagnose cause/effect to definitively conclude, "A causes B".
The TWRP instructions and downgrade instructions talk about radios, not to mention the loss of radio thread.
The issues reported in this thread clearly show a lack of reading relevant threads and instructions and asking questions that have been answered dozens of times. "Flash first, ask questions later." is an unwise way to go.

Rolo42 said:
"Correlation does not imply causation."
LOS has nothing to do with firmware (the radio). Likewise with SuperSU/root apps.
re: "seems" bricked; "seems" to be a bit weird: if you use the word, "seems", that means you have to further diagnose cause/effect to definitively conclude, "A causes B".
The TWRP instructions and downgrade instructions talk about radios, not to mention the loss of radio thread.
The issues reported in this thread clearly show a lack of reading relevant threads and instructions and asking questions that have been answered dozens of times. "Flash first, ask questions later." is an unwise way to go.
Click to expand...
Click to collapse
Do you maybe know what's the actual problem about losing radio after flashing custom rom on the 10?
Sent from my HTC 10 using Tapatalk

petar01 said:
Do you maybe know what's the actual problem about losing radio after flashing custom rom on the 10?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I know one problem: failure to read, both my first post and the htc 10 threads.
I don't know what you did, so, no, I don't know what the actual problem is or its cause.
As long as you keep asking this loaded question that asserts rooting or LOS is the cause of your radio problem, you'll have a difficult time finding the solution, if at all.
You need to present specifics: what you did, exactly, the details of your phone, etc. We don't have a scry that tells us your problem. Well, I don't; I suppose I can't speak for everyone...
Did you read any other thread, particularly the one right on your topic?

Rolo42 said:
I know one problem: failure to read, both my first post and the htc 10 threads.
I don't know what you did, so, no, I don't know what the actual problem is or its cause.
As long as you keep asking this loaded question that asserts rooting or LOS is the cause of your radio problem, you'll have a difficult time finding the solution, if at all.
You need to present specifics: what you did, exactly, the details of your phone, etc. We don't have a scry that tells us your problem. Well, I don't; I suppose I can't speak for everyone...
Did you read any other thread, particularly the one right on your topic?
Click to expand...
Click to collapse
Phone information at the time of flashing: Unlocked variant bought in the US, unlocked bootloader, S-ON, stock Oreo, not rooted, with TWRP custom recovery, CID htc_j15, software number 3.16.401.2.
Now it's rooted using Magisk, but since then I have not tried to flash.
I have read many htc 10 related threads and posts, but no luck finding particular solution. I'm not saying that solution isn't somewhere out there, but searching for it failed, at least for me. I've seen that you have participated in some threads that might contain solution, I'll check them again soon.
I've found that some of them didn't have this problem at all, some of them lost the signal and didn't manage to get it back without flashing stock image, some of them lost signal and didn't get it back even after flashing stock image.
Since this is my primary phone and I use it on daily basis, I cannot make experiments anymore without the solution how to actually flash LOS, which is not Sense based rom, and keep radio signal working.
In some threads there is a solution by using an app called Sunshine, but it's paid.
Sent from my HTC 10 using Tapatalk

delete

yldlj said:
Post your getvar all output.
Click to expand...
Click to collapse
This is the output:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
I see that information is, for some reason, incomplete.
Sent from my HTC 10 using Tapatalk

Delete

yldlj said:
You need to be in download mode. Make sure you delete imei
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
Sent from my HTC 10 using Tapatalk

Delete.

yldlj said:
There's no RUU for Oreo wwe which your on and being S ON its risky to downgrade. i'm not sure what you could do. Have you tried flashing the latest twrp released yesterday then try formatting data follwed by flashing leedroid ROM
Edit: I just read through you OP again and the reason why it's saying invalid zips is because your trying to flash a RUU with twrp which isn't the correct way to do it. I would try flashing leedroid latest ROM R137 as it supports sprint now.
Edit 2: if when you try to wipe data in twrp and it fails to mount data just reboot to Bootloader then from there reboot back to twrp.
Click to expand...
Click to collapse
Current TWRP version on my phone is 3.2.1-2.
The goal is to flash some custom rom which is near to Stock Android, which is Lineage.
I'd wait for 15.1 version, which will hopefully be released soon.
Sent from my HTC 10 using Tapatalk

petar01 said:
Current TWRP version on my phone is 3.2.1-2.
The goal is to flash some custom rom which is near to Stock Android, which is Lineage.
I'd wait for 15.1 version, which will hopefully be released soon.
Click to expand...
Click to collapse
Oh **** I thaught you were the OP of this thread. Sorry. Please delete my quote as it doesn't make sense lol

petar01 said:
Phone information at the time of flashing: Unlocked variant bought in the US, unlocked bootloader, S-ON, stock Oreo, not rooted, with TWRP custom recovery, CID htc_j15, software number 3.16.401.2.
Now it's rooted using Magisk, but since then I have not tried to flash.
I have read many htc 10 related threads and posts, but no luck finding particular solution. I'm not saying that solution isn't somewhere out there, but searching for it failed, at least for me. I've seen that you have participated in some threads that might contain solution, I'll check them again soon.
I've found that some of them didn't have this problem at all, some of them lost the signal and didn't manage to get it back without flashing stock image, some of them lost signal and didn't get it back even after flashing stock image.
Since this is my primary phone and I use it on daily basis, I cannot make experiments anymore without the solution how to actually flash LOS, which is not Sense based rom, and keep radio signal working.
In some threads there is a solution by using an app called Sunshine, but it's paid.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Flashing LOS has nothing to do with your radio not working. I've run LOS just fine, no radio issues.
LOS is not compatible with Oreo firmware, which is what you're on (3.16). To run LOS or PF, you have to downgrade to Nougat firmware (is it really worth it?) and that is where you run into radio issues that require fixing. Each step is its own isolated issue that must be completed fully before continuing.
If you really want LOS, then downgrade and get a fully-functioning stock Nougat working first, then flash LOS.

Rolo42 said:
Flashing LOS has nothing to do with your radio not working. I've run LOS just fine, no radio issues.
LOS is not compatible with Oreo firmware, which is what you're on (3.16). To run LOS or PF, you have to downgrade to Nougat firmware (is it really worth it?) and that is where you run into radio issues that require fixing. Each step is its own isolated issue that must be completed fully before continuing.
If you really want LOS, then downgrade and get a fully-functioning stock Nougat working first, then flash LOS.
Click to expand...
Click to collapse
Thank you for answering.
Yesterday, while reading instructions for LeeDroid rom, I came across warning about losing signal because of the improper firmware. That's the thing I did wrong, flashing LOS 14.1 over Sense Oreo.
By the way, did you like LOS on the 10? How was battery, audio and camera quality?
Since yesterday I'm running LeeDroid rom, trying to get better battery life and to remove bloatware. LeeDroid is running with no issues but I must admit that I'm a fan of stock Android, so I hope that LOS 15.1 is coming soon for the 10.
Sent from my HTC 10 using Tapatalk

Related

WiFi will not turn on after custom ROM installs

So, just for a bit of background info:
I found out about the release of Lollipop for the HTC One M8 is in February. Me, being the kinda impatient type, wanted it sooner! So, having never messed around with android devices before, thought "Why not now?" And dived in to some tutorials. After unlocking my bootloader, installing TWRP as the recovery, and installing a new ROM to do the S-Off with firewater, I learned a few things: Firewater doesn't work anymore, the next best (and seemingly only) alternative costs $25, my phone wasn't booting up anymore, and I hadn't made a backup.
So yeah, that sucked. After attempting to side load the ROM and a few different ROMS, I finally managed to find a stock ROM that worked on the first load and actually booted successfully at an acceptable rate.
<b>SO WHERE I'M AT NOW</B>
Everything is fine and dandy now, with the exception of one thing: the WiFi will not turn on. I will press the WiFi "switch," and it will only become greyed out. All of my other wireless connections will work, and I am not on airplane mode (I have even switched that on and off plenty of times as well). The only solution I could find through searching was to flash the boot.img that came in the ROM, and that didn't work.
As for specs, I'm a little inexperienced, so I don't know what to provide other than this:
HTC One M8
Carrier: AT&T
Not rooted, and don't plan on it
Boot loader is unlocked
I believe it is on a stock ROM
Does anybody know how to fix this? Any help would be appreciated!
Sent from my HTC One_M8 using XDA Free mobile app
Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
redpoint73 said:
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already! And the fact that'll AT&T doesn't release the M8 RUUs doesn't help either.
Sent from my HTC One_M8 using XDA Free mobile app
hardcore_spaghetti said:
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already! And the fact that'll AT&T doesn't release the M8 RUUs doesn't help either.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Who told you there were no RUUs for AT&T?
Here ya go:
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
---------- Post added at 07:38 PM ---------- Previous post was at 07:14 PM ----------
redpoint73 said:
Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
People don't like to follow instructions. I ALWAYS have a recent backup. If stuff goes bad, you can go back to the way it was before you screwed stuff up. It is the most basic step when flashing/modding; and it is always step #1 on any ROM/mod thread, but people like to skip it for some reason. I guess people like to learn the hard way.
xunholyx said:
Who told you there were no RUUs for AT&T?
Click to expand...
Click to collapse
Me and the people who were looking for AT&T-branded RUUs, not Cingular! I'll give it a try, thanks a lot!
Sent from my HTC One_M8 using XDA Free mobile app
EDIT:
It worked! Thank you so much for that RUU. My phone is running great now.
hardcore_spaghetti said:
Me and the people who were looking for AT&T-branded RUUs, not Cingular! I'll give it a try, thanks a lot!
Click to expand...
Click to collapse
I don't know why they still use the "Cingular" name in the RUU title. But regardless, you will find the AT&T RUUs listed in a variety of places, including the HTC website:
http://www.htc.com/us/support/htc-one-m8-att/news/
---------- Post added at 09:19 AM ---------- Previous post was at 09:10 AM ----------
hardcore_spaghetti said:
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Click to expand...
Click to collapse
Well, at least you thought to make a backup of some sort, which is better than a lot of folks. My rant was aimed at folks who (all too often) know well that they should make a backup, and don't bother to do so. Than are all "Uh oh, I can't boot now and didn't make a backup. What should I do?"
Modding the phone with no backup plan and no plan to recover = a bad idea.
hardcore_spaghetti said:
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already!
Click to expand...
Click to collapse
The information is all here if you read and search enough; but I'll admit the concept of "firmware" is a bit confusing.
The short answer: Boot into bootloader, and unless you've tampered with hboot in some way (not possible with s-on) the hboot number will correspond with your current firmware version, which will also tell you what software based ROMs you can run properly:
hboot 3.16 = 1.x software
hboot 3.18 = 2.x software
hboot 3.19 = 3.x software
If you look at the title or top post of each custom ROM, they will usually call out what software version the ROM is based. So you just need to find one that corresponds to your hboot number, flash it, and everything should work find. If you are looking at a specific ROM, and still can't determine what software version its based, just post a link here and we will answer that.
If you are currently on hboot 3.16 (1.x firmware) you can also relock the bootloader and run the 2.23 RUU to update to the 2.x firmware; and then be able to run 2.x software based ROMs. But with s-on, you can't update to 3.x firmware yet, until AT&T releases the corresponding OTA and/or RUU. There are methods to update to 3.x firmware with s-off.
You can read more technical info about firmware here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
redpoint73 said:
Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
Hey about that your firmware doesn't match the rom HOW COULD I KNOW?
Void tracer said:
Hey about that your firmware doesn't match the rom HOW COULD I KNOW?
Click to expand...
Click to collapse
You would only know by reading or searching. But its discussed on many threads, including the various custom ROM threads (sometimes in one of the top posts of the ROM thread).
For the most part, if you are changing to a higher software number (first number in the string: 1.x to 2.x, 3.x , etc.) you will need to update your firmware accordingly. This goes mostly for Sense ROMs; although some GPE or AOSP ROMs also require certain firmwares or at least an updated hboot. Again, check the specific ROM thread for details.
redpoint73 said:
You would only know by reading or searching. But its discussed on many threads, including the various custom ROM threads (sometimes in one of the top posts of the ROM thread).
For the most part, if you are changing to a higher software number (first number in the string: 1.x to 2.x, 3.x , etc.) you will need to update your firmware accordingly. This goes mostly for Sense ROMs; although some GPE or AOSP ROMs also require certain firmwares or at least an updated hboot. Again, check the specific ROM thread for details.
Click to expand...
Click to collapse
i still don't understand .... i went for a rom called revolutionhd and got stuck in boot loop,, spent around 8 hours trying different things , after that i got lucky that a rom called maxiumushd worked , i am s-on the dev says S-on will probably face a certain problems one of them is camera issue and files disappeared , that i fixed by the way he mentioned it should be fixed , but the wifi fix You must update firmware to latest 4.xx.xxx.x i don't understand , by installing his rom didn't i update to that version? the 4.xx.xxx.x ? or i must be at the same version before i flash a rom with that version? if yes, now roms are modding the current software? not also upgrading? and in my case i was 4.4.4 i think what should i do? i can't upgrade to lolipop? i didn't study for my finals thinking the device got bricked please help me out this is the second day ...
Void tracer said:
i still don't understand .... i went for a rom called revolutionhd and got stuck in boot loop,, spent around 8 hours trying different things , after that i got lucky that a rom called maxiumushd worked , i am s-on the dev says S-on will probably face a certain problems one of them is camera issue and files disappeared , that i fixed by the way he mentioned it should be fixed , but the wifi fix You must update firmware to latest 4.xx.xxx.x i don't understand , by installing his rom didn't i update to that version? the 4.xx.xxx.x ? or i must be at the same version before i flash a rom with that version? if yes, now roms are modding the current software? not also upgrading? and in my case i was 4.4.4 i think what should i do? i can't upgrade to lolipop?.
Click to expand...
Click to collapse
Your confusion is a bit understandable. The term "firmware" is confusing. Its true that in the past, the term "firmware" has sometimes been used interchangeably with "ROM". However in this case (and most frequently when talking about this phone), we are not talking about the ROM; but rather we are talking about a number of other modules including hboot, radio, recovery, WiFi, Bluetooth and others that actually do not get flashed with the ROM. And in fact, most of these modules can't be modified by "unofficial" means unless you have s-off.
HTC has also developed a somewhat contrived situation on their recent devices, in that while they claim to be "friendly to the mod community" by letting users unlock the bootloader and flash ROMs; they also have been in the habit of making significant updates to the firmware for every major software update (update from from Android 4.4.2 to 4.4.3, etc). And if you don't update the firmware when flashing a ROM of a higher software base, you are going to run into some major issues as you have seen (most commonly broken WiFi and extreme long boot times).
For a little more explanation on firmware vs. ROM, the following link has some good info: http://forum.xda-developers.com/showthread.php?p=52484527
You can still update the firmware with s-on by installing your version's OTA of (if available) RUU. You can also flash a firmware.zip if one has been posted for your CID that is still HTC signed/encrypted. But many firmware zips are not signed, and in that case you can't flash it unless you have s-off.
Void tracer said:
i didn't study for my finals thinking the device got bricked please help me out this is the second day ...
Click to expand...
Click to collapse
You can erase the notion in your mind that this phone is ever bricked, if the screen comes on. As long as the screen comes on, this phone is virtually always recoverable. And usually not that hard, just involves knowing the correct steps.
Also one of the cardinal rules of flashing ROMs, is always have a known good nandroid backup before flashing. Having a known-good nandroid to revert to resolves a lot of "OMG I bricked the phone" moments.
redpoint73 said:
Your confusion is a bit understandable. The term "firmware" is confusing. Its true that in the past, the term "firmware" has sometimes been used interchangeably with "ROM". However in this case (and most frequently when talking about this phone), we are not talking about the ROM; but rather we are talking about a number of other modules including hboot, radio, recovery, WiFi, Bluetooth and others that actually do not get flashed with the ROM. And in fact, most of these modules can't be modified by "unofficial" means unless you have s-off.
HTC has also developed a somewhat contrived situation on their recent devices, in that while they claim to be "friendly to the mod community" by letting users unlock the bootloader and flash ROMs; they also have been in the habit of making significant updates to the firmware for every major software update (update from from Android 4.4.2 to 4.4.3, etc). And if you don't update the firmware when flashing a ROM of a higher software base, you are going to run into some major issues as you have seen (most commonly broken WiFi and extreme long boot times).
For a little more explanation on firmware vs. ROM, the following link has some good info: http://forum.xda-developers.com/showthread.php?p=52484527
You can still update the firmware with s-on by installing your version's OTA of (if available) RUU. You can also flash a firmware.zip if one has been posted for your CID that is still HTC signed/encrypted. But many firmware zips are not signed, and in that case you can't flash it unless you have s-off.
You can erase the notion in your mind that this phone is ever bricked, if the screen comes on. As long as the screen comes on, this phone is virtually always recoverable. And usually not that hard, just involves knowing the correct steps.
Also one of the cardinal rules of flashing ROMs, is always have a known good nandroid backup before flashing. Having a known-good nandroid to revert to resolves a lot of "OMG I bricked the phone" moments.
Click to expand...
Click to collapse
Thanks you big time for explaining this to me i did go to a nandroid backup of my same cid/mid and everything was good , restored using twrp i still have the wifi issue ... i tried to flash the latest OTA and it failed (after going to stock) i really don't know what to do googled everything .. do u think i should make a thread for it?
Void tracer said:
Thanks you big time for explaining this to me i did go to a nandroid backup of my same cid/mid and everything was good , restored using twrp i still have the wifi issue ... i tried to flash the latest OTA and it failed (after going to stock) i really don't know what to do googled everything .
Click to expand...
Click to collapse
You probably installed the nandroid that didn't match with your firmware, so you are going to have the same issue as with a custom ROM: Your current firmware version doesn't match the software (OS) version.
What CID, what hboot number? What nandroid did you restore?
Void tracer said:
do u think i should make a thread for it?
Click to expand...
Click to collapse
We've already been back and forth on your issue on this thread, and its relevant to this thread's topic. So NO I don't think you should make a new thread.
redpoint73 said:
You probably installed the nandroid that didn't match with your firmware, so you are going to have the same issue as with a custom ROM: Your current firmware version doesn't match the software (OS) version.
What CID, what hboot number? What nandroid did you restore?
We've already been back and forth on your issue on this thread, and its relevant to this thread's topic. So NO I don't think you should make a new thread.
Click to expand...
Click to collapse
I believe its correct here is the link to the thread : http://forum.xda-developers.com/showthread.php?t=2701376
go to nandroid backups then all other CIDS i grabbed the htc__59 here is my phone info :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Void tracer said:
I believe its correct here is the link to the thread : http://forum.xda-developers.com/showthread.php?t=2701376
go to nandroid backups then all other CIDS i grabbed the htc__59
Click to expand...
Click to collapse
Yes, but which one did you use exactly? There are 3 different software numbers available for your CID on the stock nandroid thread: 1.54, 2.22 and 3.32.
redpoint73 said:
Yes, but which one did you use exactly? There are 3 different software numbers available for your CID on the stock nandroid thread: 1.54, 2.22 and 3.32.
Click to expand...
Click to collapse
newest which is 3.32
Void tracer said:
newest which is 3.32
Click to expand...
Click to collapse
Your hboot (3.18) corresponds with 2.22, you want to restore that nandroid.
The 3.32 nandroid doesn't match with your 2.22 firmware. That is why WiFi is still broken.
redpoint73 said:
Your hboot (3.18) corresponds with 2.22, you want to restore that nandroid.
The 3.32 nandroid doesn't match with your 2.22 firmware. That is why WiFi is still broken.
Click to expand...
Click to collapse
so i download 2.2 and i am good to go?
Void tracer said:
so i download 2.2 and i am good to go?
Click to expand...
Click to collapse
Yes, you should be.
redpoint73 said:
Yes, you should be.
Click to expand...
Click to collapse
Hey man just installed it everything works TY big time , but umm now i want to update to the maximushd rom and i have to update as i understood to match the android version of the rom itself , i am s-on and unlocked, now i have to re-lock to flash it ? and then unlock again to flash the rom??
Void tracer said:
Hey man just installed it everything works TY big time , but umm now i want to update to the maximushd rom and i have to update as i understood to match the android version of the rom itself , i am s-on and unlocked, now i have to re-lock to flash it ? and then unlock again to flash the rom??
Click to expand...
Click to collapse
What you want to do now, is apply any available OTA updates available for your CID. You will need to update to 3.x software (Android 4.4.4) than to 4.x (Android 5.0, Lollipop). Do you know if Lollipop has been rolled out for your version?
The OTA will also update your firmware (not just the ROM). Then once you are on Lollipop firmware, you will be able to run any custom Lollipop ROMs.
You do not need to relock the bootloader to install the OTA. And I do not recommend you do so (its better unlocked).
Reason for that, once you are OTA updated to Lollipop, you can then re-install custom recovery (you need an unlocked bootloader for that) then you can install a custom ROM (such as MaximumHD as you asked).

OTA Update 5.1 Help

So right now my phone says it's getting the 5.1 update OTA. I am using TWRP. When I try to install the update it goes to the TWRP everytime. I dont use custom roms, just what came with the phone. How do I update the phone?
Found out I need to return it to stock recovery before I can install an OTA update. So I tried using instructions found on the web made for the noob I am. But when I use the CDM console it tells me that it can't open the recovery file.
\
What do?
Edit: I just need step by step help on what to do. I just rooted it so I could have BB10-like gestures and stock android navigation buttons. I didnt know it would screw me over for OTA updates
Edit 2: I got it work, now the update fails and goes to bootloader and tell me this, i am using the carrier supplied OTA update.
"this package of fir"htc_himaulatt" devices; this is a "htc_himauhl""
BriniaSona said:
Found out I need to return it to stock recovery before I can install an OTA update. So I tried using instructions found on the web made for the noob I am. But when I use the CDM console it tells me that it can't open the recovery file.
\
What do?
Edit: I just need step by step help on what to do. I just rooted it so I could have BB10-like gestures and stock android navigation buttons. I didnt know it would screw me over for OTA updates
Edit 2: I got it work, now the update fails and goes to bootloader and tell me this, i am using the carrier supplied OTA update.
"this package of fir"htc_himaulatt" devices; this is a "htc_himauhl""
Click to expand...
Click to collapse
This phone is a real hassle to update.
You won't be able to do OTAs until you return it to stock, and to do that, you'll have to run an RUU so that it removes TWRP and root. Make sure to re-lock the bootloader. So run the RUU of the latest version if it exists if you can then you won't have to OTA, or run the RUU that matches your phone's OS version and then take the OTA.
TWRP is removed using a stuck recovery image
the bootloader is relocked using commands from a video I watched on how to do it, it displays relocked when open.
however, now instead of getting the yellow error from before, I now get sent to the bootloader screen and nothing happens.
Edit: when I try to boot into recovery through the boatloads it gives me an error message saying it can't and takes me back to the white screen.
BriniaSona said:
TWRP is removed using a stuck recovery image
the bootloader is relocked using commands from a video I watched on how to do it, it displays relocked when open.
however, now instead of getting the yellow error from before, I now get sent to the bootloader screen and nothing happens.
Edit: when I try to boot into recovery through the boatloads it gives me an error message saying it can't and takes me back to the white screen.
Click to expand...
Click to collapse
I guess you missed the whole part about restoring your system partition to stock
From the backup you made after installing TWRP .
You need an untouched system partition and Stock recovery.
At this point you should look for the RUU for your phone
Sent from my HTC One M9 using Tapatalk
GG didnt make a backup.
Can you link me to one at all, and all the instructions needed to make things work. Sorry for the hassle, I really don't want to do this without help now, incase I mess things up more than they already are.
EDIT: this it it right? http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Except there's now Canada option.
EDIT 2: I wish it was as easy as BlackBerry which everyone seems to think it out of date, http://crackberry.com/install-leaked-os-autoloader
BriniaSona said:
GG didnt make a backup.
Can you link me to one at all, and all the instructions needed to make things work. Sorry for the hassle, I really don't want to do this without help now, incase I mess things up more than they already are.
EDIT: this it it right? http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Except there's now Canada option.
EDIT 2: I wish it was as easy as BlackBerry which everyone seems to think it out of date, http://crackberry.com/install-leaked-os-autoloader
Click to expand...
Click to collapse
Theirs a thread in the general forums for Canadian files
Sent from my HTC One M9 using Tapatalk
So I'm downloading the bell one and using download mode and adb to input the show commands?
''Fastboot output
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) version-main: 1.32.666.30
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001''
Edit: Didnt work, so I am using these commands, but now I need to s-off, so I'm going to do that now. http://forum.xda-developers.com/showthread.php?t=1907796
if you read this and I havent added and Edit: 2, then answer this.
what command erases everything and put it back to default, like how it was when i bought the phone.
Edit 2: re-unlocked the bootloader.
Device is giving me the same error as when I started. "this package of fir"htc_himaulatt" devices; this is a "htc_himauhl"
I downloaded a stock bell RUU. Went into adb and used
"fastboot update "filename""
I got an error saying there wasnt enough space.
EDIT: failed to load '0PJAIMG.zip': Not enough space
and when i try to sideload it it says the file can not be read.
Can someone just tell me what to do from the beginning, instead of telling me to look myself. Looking myself has only gotten me more lost and confused.
I need step by step instructions with links and files.
Please.
I just want my phone to be the way i bought it, No root, no bootloader changes, no twrp, just stuck everything.
MY phones current status.
Rooted, Bootloader Unlocked, Stock Recovery installed.
What do I do from there, where do I find the correct Bell RUU, how do I flash it, where does it go so it can be flashed.
BriniaSona said:
MY phones current status.
Rooted, Bootloader Unlocked, Stock Recovery installed.
What do I do from there, where do I find the correct Bell RUU, how do I flash it, where does it go so it can be flashed.
Click to expand...
Click to collapse
I think I found the correct RUU for your firmware version. The problem is you will have to pay if you want it since the website isn't for free. Sorry that I wasn't able to find a cheaper source. (Link)
Edit: Forget what I said. I just saw that there is a TWRP backup in this thread. Using it should be much cheaper than the RUU.

Android won't start and need help flashing

Hi,
I have bought a used HTC M9 on Kijiji (I'm in Québec, Canada)
It must be faulty because it kept randomly restarting (sometimes once, sometimes for periods of 20 minutes, which made it hardly usable)
After clearing the cache partition and factory resetting it a couple times, I decided to flash it.
What I did:
- enabled the developer mode and USB debugging
- unlocked the bootloader
- flashed TWRP
- flashed SuperSU v2.74-2
Now, Android won't boot. When I start the phone, I see the green HTC logo on a white background with a red text saying it's a development build, then after about 10 seconds it restarts to the same screen. Over and over again.
In download mode, I am able to see the device with fastboot, but adb does not show anything.
In recovery mode, it's the opposite.
The phone is still S-ON so I have tried S-OFF methods (moonshine and firewater), but the fact of not having fastboot AND adb working at the same time made them fail.
Here's my phone info:
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: ************
(bootloader) version-main: 3.38.666.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
Any help would be greatly appreciated...
Thanks in advance!
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Roobwz said:
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Click to expand...
Click to collapse
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
zzzer51 said:
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
Click to expand...
Click to collapse
You shouldnt use toolkits imo, no offence squabbi. You should just download the 2.64 file from chainfires thread and flash it in twrp. It isnt harder than that. Btw 2.64 was the only superSu that worked for me
Ok, I have been able to find a zip for 2.64 and will install it with TWRP when my phone's battery is drained out (it tried to boot on the OS and is currently stuck on the HTC logo...)
I have also tried installing files directly from the microSD
downloaded from:
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://androidruu.com/index.php?developer=M9
using fastboot flash zip zipfile.zip
but I get errors like
9 RU_SECURITY_FAIL
android-version information is missing
I'm not sure I'm trying to flash the right file anymore...
EDIT:
I have tried to flash both 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.30 and 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6 files by going to TWRP -> Install but I get the error message 'zip file is corrupt!' every time...
And when I try to flash with fastboot, I get "Invalid sparse file format at header magi"
EDIT2:
Ok, I have made some progress!
What I did:
1/ Downloaded the image from this page http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
2/ Formated my 8GB microSD card to exFAT (because the system image file is over 4GB)
3/ Extracted the system.emmc.win and boot.emmc.win files to the microSD card in path: E:\TWRP\BACKUPS\<myPhoneIDThatFastbootCanGiveYouIfYouTypeFastbootDevices>\Stock Bell
4/ Started the phone in recovery mode (TWRP)
5/ Tapped on Restore
6/ Selected the two files and hit Restore
7/ Performed a Factory reset (through TWRP, by tapping Wipe)
8/ Rebooted the phone in System mode
And Android started!
I'm not 100% sure it fully works as I haven't been able to finish the configuration yet (I don't have access to a wifi network where I am) so I will do that when I get home tonight.
But it looks a lot better than these past few days.
In the meantime, a quick question:
My bootloader is still unlocked. Can I leave it like that or should I re-lock it?
Thanks
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
shivadow said:
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
Click to expand...
Click to collapse
You can OTA with an unlocked bootloader but you need to be 100 % stock. It's always best to not relock bootloaders as if you get into problems, you'll not be able to flash stuff. The only time a locked bootloader is needed is when running RUU.exe while S-On. The SD card method works with an unlocked bootloader. I'd recommend to leave it unlocked
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
zzzer51 said:
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
Click to expand...
Click to collapse
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Roobwz said:
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Click to expand...
Click to collapse
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
zzzer51 said:
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
Click to expand...
Click to collapse
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Click to expand...
Click to collapse
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
zzzer51 said:
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
Click to expand...
Click to collapse
The service is remotely done over the computer, so you'll see everything that happens.
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free. Either that or s off (25$ as well), and you'll be able to convert your phone into a world wide edition model or dev edition. S off opens up a whole new world for you. Ex - you can flash exactly what you want (no need for Canadian firmware) and you're able to downgrade etc. The rest is up to you.
Roobwz said:
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free.
Click to expand...
Click to collapse
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
zzzer51 said:
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
Click to expand...
Click to collapse
That's kernel source I believe. Your only luck would be flippys thread in the general section
Skickat från min HTC One M9 via Tapatalk
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
zzzer51 said:
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
Click to expand...
Click to collapse
I would recommend upgrading to 3.xx for several reasons like doze, custom ROMs that are up to date etc. If you did the OTA from 1.x to 2.x, you shouldn't have any problems with the OTA to 3.x. in the worst case, just re flash the RUU or just convert the device to an European version.
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
zzzer51 said:
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
Click to expand...
Click to collapse
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Roobwz said:
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Click to expand...
Click to collapse
A looooot of stuff!
But even after flashing the original HTC recovery again, I get the same message.
And I can't access the recovery menu either.
Thanks

AT&T HTC M8 in desperate need of help, device wrecked/FUBAR

So roughly two years ago I decided to root my phone. I flashed TWRP, got S-OFF, and root. Well somebody hacked my phone and I freaked out. They were remotely downloading and inventorying all my devices' files, serial numbers, hardware info, accessing my camera, I mean everything, it was truly frightening the level of which whomever was doing this was able to to do it. I freaked out, went into TWRP, and started deleting everything that looked suspicious. I deleted my OS and probably a bunch of other things I shouldn't have on accident through TWRP. My device still has TWRP recovery functioning. I tried using ADB on my Windows 10 PC but I have no idea what I'm doing. I kept getting errors to the effect of "wrong version" etc. Being unable to use ADB I resorted to copying Viper OS to a flash card and I used TWRP to install it from flash. Once installed it "ran" but my Wifi radio did not work at all. When I tried to enable it in settings it stayed grey. Figuring I screwed up royally again, I decided to copy and paste a folder I created in 2014 with a TWRP recovery. It had the OS, cache, etc backed up. After using TWRP recovery it said I had no OS again. I'm freaking out, my phone is trashed, and I don't want to do anything else without a babysitter. I just want my original phone back, no custom roms, nothing. I don't want to turn S-ON because I know there is a possibility of bricking and quite frankly, I'm an idiot. Somebody just please walk me through what I need to do to get a fully functioning OS back on my phone. SD card methods preferred, as I can't get ADB to work or I'm too stupid to use it. I saw something mentioned that the firmware may need updating and that may have been the cause for the WiFi issue, since all I did was install Viper through a .zip through TWRP.
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
lgally80 said:
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
Click to expand...
Click to collapse
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
xunholyx said:
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
Click to expand...
Click to collapse
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Update 1:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Update 2:
Opened the original OS Viper I flashed, it was a .zip with boot also, so going to leave this new one alone and go ahead and flash as a whole...
Update 3:
Flashed as whole, last screen on install said successful, rebooted. On HTC screen, waiting to see what happens... 3 minutes into waiting...
Update 4:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed. You deserve just as many blowjobs as you do internets. Don't know what was wrong with that last Viper ROM but this did it. Many thanks. Not even going to bother with the new TWRP and everything else, my phone works as is and that's that. +1 for you mate.
lgally80 said:
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Click to expand...
Click to collapse
I did say to flash the ROM first to get back your OS, so.....
Anyway, that recovery version won't work until you update your firmware. Try 2.8.7.0 first, update your firmware, then you can use the 3.x.x.x recovery
I should have been clearer in my instructions
lgally80 said:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Click to expand...
Click to collapse
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
lgally80 said:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed.
Don't know what was wrong with that last Viper ROM but this did it.
Click to expand...
Click to collapse
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
redpoint73 said:
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
Click to expand...
Click to collapse
Yes I probably "should" update TWRP and my firmware, buuuut....
If it ain't broke, don't fix it.
Also in reply to your comments:
1. Flashing ViperOneM8_6.1.0.zip caused WiFi loss. Maybe Bluetooth also, don't remember. Flashing ViperOneM8_2.5.0.zip and now my phone is 100% functioning.
2. That "Old" firmware works fine now that it matches the ROM requirements, all radios functioning stable for several days now. I don't mind staying on older releases.
3. Nah I'm good, I use this M8 as a tool or entertainment device at home, and nothing else. It has no service, no AT&T signal here. Hasn't had service since 3 years after public release.
Anyway, thank you everyone who contributed. Anyone who's just showing up:
The Lesson of the Day - If your Hardware Radios do not function, the solution is your ROM probably requires a different Firmware revision than the one installed.
Cheers.

My htc 10 is dead ?

Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.
yldlj said:
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
ubadafatta said:
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
Click to expand...
Click to collapse
Since there Is no RUU and you re locked your Bootloader there's not much I can help you with sorry.
ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on
Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.011s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.080s]
finished. total time: 1.094s
this what i get when i try to flash unlocktoken or oem unlock bootloader or even when i try get_token_identifier
You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
ubadafatta said:
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on
Click to expand...
Click to collapse
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.
Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The threory of the OTA is fine but not in this case.
Cheers.
Click to expand...
Click to collapse
Yeah thanks. I deleted all my post because there's no point in arguing. Your correct I totally forgot what the OP problem was after all this. Thanks for the clarification.
Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.
Click to expand...
Click to collapse
It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
ayyu3m said:
Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Click to expand...
Click to collapse
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Mr Hofs said:
It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
Click to expand...
Click to collapse
ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I will have a look at it when i have more time, and let's not bash but learn ?
:highfive:
Cheers guys.
ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:
Yeah i got your PM. Thanks for that. After reading your PM i also knew how stupid i was being. And when i came to delete the post, they were already deleted by the thread administrators.
Sorry once more man. Wont happen again
yldlj said:
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:
Click to expand...
Click to collapse
ayyu3m said:
You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
Click to expand...
Click to collapse
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on
[email protected] said:
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on
Click to expand...
Click to collapse
Flash ruu
https://androidfilehost.com/?fid=673956719939830809
yldlj said:
Flash ruu
https://androidfilehost.com/?fid=673956719939830809
Click to expand...
Click to collapse
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%
[email protected] said:
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%
Click to expand...
Click to collapse
Yeah everyone I flash RUU it does bypass some things. Relocking bootloader usually causes problems and I don't know people still keep doing it. I would say flash twrp followed by leedroid but pretty sure you need an unlocked bootloader to flash twrp. Sorry but I'm out of ideas.

Categories

Resources