Related
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).
hi everyone.. i recently bought a used htc m8 and it is already rooted and therefore i cannot get the OTA lollipop update..
it is running android revolution HD 8.1 and clockworkmod..
I have no idea about rooting and unrooting and what the names i just mentioned above mean.. someone please help me get back to stock firmware... or help me convert my phone into google play edition lollipop...
please tell the method by which i can get rid of clockwordmod permanently and get back to stock firmware..
thanks in advance
hassaan08 said:
hi everyone.. i recently bought a used htc m8 and it is already rooted and therefore i cannot get the OTA lollipop update..
it is running android revolution HD 8.1 and clockworkmod..
I have no idea about rooting and unrooting and what the names i just mentioned above mean.. someone please help me get back to stock firmware... or help me convert my phone into google play edition lollipop...
please tell the method by which i can get rid of clockwordmod permanently and get back to stock firmware..
thanks in advance
Click to expand...
Click to collapse
Click this link. It will tell you how to convert your phone to GPE.
xunholyx said:
Click this link. It will tell you how to convert your phone to GPE.
Click to expand...
Click to collapse
sure
just help me please.. i have been trying for days now and i havent been able to fix my phone... every method i try i get stuck at one point or another....
hassaan08 said:
sure
just help me please.. i have been trying for days now and i havent been able to fix my phone... every method i try i get stuck at one point or another....
Click to expand...
Click to collapse
Okay. The instructions are in the link. Where are you getting stuck?
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
EddyOS said:
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
Click to expand...
Click to collapse
yes i do.. i tried a few things but got stuck in between cos i dont know this stuff in depth..
I tried to unroot by downloading the stock firmware for my phone..
the method i was following was to match my cid number etc which i got through getvar with the firmwares on xda.. that bit i did well but the method i was following said that now i had to copy and paste this firmware in my phone in the backups folder of clockwordmod.. now i couldnt find that folder.. even though the backup i made is occupying space on my phone but i cannot locate it when i try to copy paste the downloaded firmware..
can you tell me where i can find that or tell an alternate way to do this thing?
OK, can you connect your phone when in the bootloader and then use the command fastboot getvar all to get information about your phone and post it up here (making sure you hide the IMEI and serial number, of course)
EddyOS said:
OK, can you connect your phone when in the bootloader and then use the command fastboot getvar all to get information about your phone and post it up here (making sure you hide the IMEI and serial number, of course)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA13G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__002
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
is this what you were asking for?
Indeed! OK, if you want go back to 100% stock, running on Sense as if you just got it out the box you can do the following:
First, download these files to the same location as fastboot:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249 (doesn't need renaming)
1. Relock your bootloader - fastboot oem lock
2. Once done, reboot the bootloader to confirm it says 'RELOCKED' - fastboot reboot-bootloader
3. Once relocked, reboot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the RUU ZIP using the HTC fastboot app - htc_fastboot flash zip ruu.zip
5. It will go through a few passes but once complete reboot the phone to the bootloader - fastboot reboot-bootloader
6. Once back at the bootloader, go into recovery and you should get the stock recovery not CWM. Hold volume up and press power to get the recovery menu and do a factory reset
7. Once the reset has finished, reboot the phone
You should now be working again on 100% stock Lollipop
help needed, new to rooting stuff
Hi forum members. This is my first post and and i am an infant in unlocking and rooting stuff. The reason I am researching these things is because of my HTC one m8. I got this phone used from a seller 6 months ago. I was expecting OTA updates but did not receive any till date. I am still running on 4.4.2 . So, after a bit of searching on forums, I learned about a thing called boot loader. And checked mine. To my surprise it was TAMPERED , UNLOCKED AND S-ON. Now I really don't know what that means. Some suggested to check if it's rooted, installed root checker and it said "device is not rooted" .
Can anyone pLease help me And explain me what all this means as it will be greatly appreciated.I only want to have OTA updates And need stock android. Thanks in advance
Best to start your own thread, and post up the same details as the OP in post #8, rather than confusing things in someone else's thread
EddyOS said:
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
Click to expand...
Click to collapse
Read his OP. He asked how to convert, so I linked him. How is that bad advice?
Sorry for being off topic.
xunholyx said:
Read his OP. He asked how to convert, so I linked him. How is that bad advice?
Sorry for being off topic.
Click to expand...
Click to collapse
That was the second request, the first being to get it back to stock. I was just saying that if they're not familiar with rooting HTC devices then converting to GPe could potentially brick the device
It worked... thank you so much..
i hope liverpool get into the top 4 this season
hassaan08 said:
It worked... thank you so much..
i hope liverpool get into the top 4 this season
Click to expand...
Click to collapse
I'm an Arsenal fan but thank you anyway!
hey again
i unrooted my device and it seemed fine then but since day one the device is highly unstable.. I did the hard reset several times but have not been able to fix the problem.. suddenly all the data vanishes from the device and some features get locked ( brightness, power saver and others too). Please suggest what i should do?
Is there a way I can re-flash the stock lollipop with a different RUU file?
Nope, if you still have issues when stock you have a faulty phone
these are definitely sofware issues.. for example one in ten times when i format my device it starts working totally fine... but after a few days the same problem re-appears... the problem is that htc zoe add keeps popping up again and again.. and when it starts i cant adjust the brightness or the power saver options.. the rest of the phone works fine....
can you please suggest if i should convert my phone to GPE? or will it be too difficult a process for a rookie like me?
Sounds like a faulty phone, get it replaced
Hello,
As mentioned in the title, I have a HTC one m9 which I have somehow bricked by attempting to install supersu. I flashed a rom that was horribly slow, so I wanted to flash my stock rom after I have flashed the other rom. It was a RUU so I relocked my bootloader, but the update failed because I am S-ON. Whenever I try to unlock my bootloader again it asks me if I want to unlock and that would void my warranty everything as normal but would then restart and still be relocked. Also, whenever I try to boot normally it takes me to bootloader. Any help would be appreciated! (No SD card I have.)
fastboot getvar all:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.32
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__J15
Thank you!
MikeTheGamer said:
Hello,
As mentioned in the title, I have a HTC one m9 which I have somehow bricked by attempting to install supersu. I flashed a rom that was horribly slow, so I wanted to flash my stock rom after I have flashed the other rom. It was a RUU so I relocked my bootloader, but the update failed because I am S-ON. Whenever I try to unlock my bootloader again it asks me if I want to unlock and that would void my warranty everything as normal but would then restart and still be relocked. Also, whenever I try to boot normally it takes me to bootloader. Any help would be appreciated! (No SD card I have.)
fastboot getvar all:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.32
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__J15
Thank you!
Click to expand...
Click to collapse
Have you tried to download from
http://www.htc.com/us/support/rom-downloads.html
And reinstall the stock 6.01 using download mode through your bootloader?
mcarden2006 said:
Have you tried to download from
And reinstall the stock 6.01 using download mode through your bootloader?
Click to expand...
Click to collapse
I have, but will try redownloading and attempting again. Got the unknown error I think it was code 105
I'm trying to get this: http:././dl3.htcdotcomslashapplication/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe?_ga=1.172299883.913399690.1483411382
also I noticed this is hima UL not UHL, will it still work?
MikeTheGamer said:
I have, but will try redownloading and attempting again. Got the unknown error I think it was code 105
I'm trying to get this: http:././dl3.htcdotcomslashapplication/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe?_ga=1.172299883.913399690.1483411382
also I noticed this is hima UL not UHL, will it still work?
Click to expand...
Click to collapse
Do you have s-off? I had the same error code when I tried to install the wrong one. I have an at&t HTC so I downloaded from the top. You have to make sure oem unlock and debug mode are check on the developer option from your phone. Reboot into download mode and should work like a charm. When I installed supersu I had to go back to 2.65 version or use magisk root.
mcarden2006 said:
Do you have s-off? I had the same error code when I tried to install the wrong one. I have an at&t HTC so I downloaded from the top. You have to make sure oem unlock and debug mode are check on the developer option from your phone. Reboot into download mode and should work like a charm. When I installed supersu I had to go back to 2.65 version or use magisk root.
Click to expand...
Click to collapse
As I mentioned I have S-ON. If there's any way I can make it S-OFF with fastboot or something I'd be glad to, and bootloader is stuck at relocked.
MikeTheGamer said:
As I mentioned I have S-ON. If there's any way I can make it S-OFF with fastboot or something I'd be glad to, and bootloader is stuck at relocked.
Click to expand...
Click to collapse
I know a lot of people complain but I paid 25$ and used sunshine. It worked like a charm and I have s-off. Now I'm finally free ?
mcarden2006 said:
I know a lot of people complain but I paid 25$ and used sunshine. It worked like a charm and I have s-off. Now I'm finally free
Click to expand...
Click to collapse
I would have tried, but I have no access to android. Please read the whole thread
MikeTheGamer said:
I would have tried, but I have no access to android. Please read the whole thread
Click to expand...
Click to collapse
What I was saying is after you get your phone up and running you can do it.
mcarden2006 said:
What I was saying is after you get your phone up and running you can do it.
Click to expand...
Click to collapse
Oh, yeah, no problem Until then though, I have S-ON and at 52% of the RUU download. Will right back soon!
MikeTheGamer said:
Oh, yeah, no problem Until then though, I have S-ON and at 52% of the RUU download. Will right back soon!
Click to expand...
Click to collapse
Just remember magisk root is really easy but supersu install the 2.65 and not the 2.78 or 2.79. They will just keep bootlooping the phone.
mcarden2006 said:
Just remember magisk root is really easy but supersu install the 2.65 and not the 2.78 or 2.79. They will just keep bootlooping the phone.
Click to expand...
Click to collapse
Thank you! Guess I should have looked better before flashing supersu...
Anyway, do you have any other solutions if this doesn't work? I'm really paranoid and afraid that I cannot fix my phone this time. I usually go through this stuff a lot but I usually fix it easily too, but this time it's been a few days and I'm really frustrated.
MikeTheGamer said:
Thank you! Guess I should have looked better before flashing supersu...
Anyway, do you have any other solutions if this doesn't work? I'm really paranoid and afraid that I cannot fix my phone this time. I usually go through this stuff a lot but I usually fix it easily too, but this time it's been a few days and I'm really frustrated.
Click to expand...
Click to collapse
Well, It failed. Error code 155 UNKNOWN. I believe the reason is S-ON and probably locked bootloader. Any help please?
MikeTheGamer said:
Thank you! Guess I should have looked better before flashing supersu...
Anyway, do you have any other solutions if this doesn't work? I'm really paranoid and afraid that I cannot fix my phone this time. I usually go through this stuff a lot but I usually fix it easily too, but this time it's been a few days and I'm really frustrated.
Click to expand...
Click to collapse
Do you have twrp installed? One time I formatted everything by accident including the boot loader. It took me awhile to fix everything but I did. One time I had to install a custom rom and then I was able to go to stock. Its usually just trial and error. That's what I love android so much because of the freedom.
---------- Post added at 06:29 PM ---------- Previous post was at 06:29 PM ----------
mcarden2006 said:
Do you have twrp installed? One time I formatted everything by accident including the boot loader. It took me awhile to fix everything but I did. One time I had to install a custom rom and then I was able to go to stock. Its usually just trial and error. That's what I love android so much because of the freedom.
Click to expand...
Click to collapse
Sorry it took me awhile but I had to walk the dog.
mcarden2006 said:
Do you have twrp installed? One time I formatted everything by accident including the boot loader. It took me awhile to fix everything but I did. One time I had to install a custom rom and then I was able to go to stock. Its usually just trial and error. That's what I love android so much because of the freedom.
---------- Post added at 06:29 PM ---------- Previous post was at 06:29 PM ----------
Sorry it took me awhile but I had to walk the dog.
Click to expand...
Click to collapse
My bootloader is relocked, and won't unlock again. As I said before, goes through all the normal stuff and then reboots to bootloader and stays relocked. Therefore, I cannot access recovery.
You haven't unlocked the bootloader yet? Its free and helps you step by step using this site.
http://www.htcdev.com/bootloader/
That's usually the first thing I do. The key it provides you in the terminal is very picky so make sure there are no spaces.
mcarden2006 said:
You haven't unlocked the bootloader yet? Its free and helps you step by step using this site.
http://www.htcdev.com/bootloader/
That's usually the first thing I do. They key it provides you in the terminal is very picky so make sure there are no spaces.
Click to expand...
Click to collapse
I have unlocked it before, I said it's "relocked" I have the unlock bin, but it's just stuck there.
MikeTheGamer said:
I have unlocked it before, I said it's "relocked" I have the unlock bin, but it's just stuck there.
Click to expand...
Click to collapse
Do you have the drivers installed and using the terminal under administrator mode? I installed mine using 15 second adb fastboot installer.
I'll try reinstalling adb, and I have HTC sync manager, so I'm sure I have the right HTC drivers. one second.
MikeTheGamer said:
I'll try reinstalling adb, and I have HTC sync manager, so I'm sure I have the right HTC drivers. one second.
Click to expand...
Click to collapse
Usually I use the power shell terminal when you press shift and right click on the folder. It never failed me that way.
mcarden2006 said:
Do you have the drivers installed and using the terminal under administrator mode? I installed mine using 15 second adb fastboot installer.
Click to expand...
Click to collapse
The problem he is likely to run into is that the HTC fast boot checks the os to see if unlocking is allowed. I made the same mistake myself trying to get back to stock to install nougat. I have hima_ul w s-on and the uhl version didn't take on my phone. I imagine Mike will need the uhl version ruu. Put the phone in fastboot, then run the ruu. Make sure that you have a .doc viewer installed (open office will suffice). I found the ruu will bomb out silently it you don't. It's some error thrown by the ARWizard contained in the ruu.
You can also teach out to HTC support. They can reset the device for you.
Hi all,
my (SIM unlocked, Vodaphone branded) HTC M8 was purchased secondhand via eBay and worked fine with a Virgin Mobile SIM and 128GB microSD card for many months. Unfortunately its USB socket eventually became very iffy, making it extremely difficult to recharge reliably and/or connect to a Windows laptop. It had been OTA update to Marshmallow during my time of usage. I bought an HTC 10 intending to give the M8 to my brother, but after a period of lack of use the M8 failed normal boot, recovery etc., ending up with:
*** Software status: Modifiied ***
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.161.4
eMMC-boot 2048MB
Dec 1 2015,16:56:09.0
I have attempted to follow (as best I could) the thread
https://forum.xda-developers.com/htc-one-m8/help/htc-m8-stuck-boot-t3342079
but seem to only have unlocked the bootloader successfully.
(i.e. *** UNLOCKED ***, now)
fastboot getvar all
currently returns:
version-microp: None
version-main: 6.12.161.4
version-misc: PVT SHIP S-ON
serialno: ************
imei: ***************
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: VODAP001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
I had downloaded recovery_6.12.161.4.img from:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
but having successfully executed a:
fastboot flash recovery recovery_6.12.1614.img
this does not seem to have installed TWRP, so that:
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
will boot into TWRP.
fails to boot into TWRP. What have I done wrong here, please?
P.S. I'm an old-school mainframe (Network) Sysprog and long-term PC hobbyist, but Android and Linux-like OSes and terminology really confuse me, as do the somewhat opaque "how-tos" that I've tried to read and understand.
Thanks in advance.
A quick follow-up correction:
fastboot flash recovery twrp-3.0.0-0-m8.img
was what I should have downloaded and done. TWRP now bootable as the recovery image.
Copying the TWRP-6.12.161.4 extracted directory over to the M8's internal storage TWRP\... directory now. Sorry guys.
Try a nougat rom. Sees if it will boot up
ChristopherXI said:
Try a nougat rom. Sees if it will boot up
Click to expand...
Click to collapse
Nougat? That's Android v7, no? I don't think I'll be able to get the OTA update yet. I'll need to get the Vodaphone SIM unlock sorted first.
GT3guy said:
Nougat? That's Android v7, no? I don't think I'll be able to get the OTA update yet. I'll need to get the Vodaphone SIM unlock sorted first.
Click to expand...
Click to collapse
it will boot . just unlock your bootloader flash twrp recovery then flash any rom and check . if you cant do it then pm me i will do it for you on team viewer
jahanzaiblohani said:
it will boot . just unlock your bootloader flash twrp recovery then flash any rom and check . if you cant do it then pm me i will do it for you on team viewer
Click to expand...
Click to collapse
Well, thanks, but I'm trying to get it back to "factory state" to send it to HTC for repair of that annoyingly problematic USB socket. That makes it almost unusable.
GT3guy said:
I had downloaded recovery_6.12.161.4.img from:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
but having successfully executed a:
fastboot flash recovery recovery_6.12.1614.img
this does not seem to have installed TWRP
Click to expand...
Click to collapse
You are misunderstanding the linked thread. What you tried to do, is to flash stock HTC recovery (recovery_6.12.1614.img).
You need to flash custom recovery TWRP, in order to restore a stock TWRP backup from ckpv5's thread.
---------- Post added at 09:07 AM ---------- Previous post was at 09:04 AM ----------
GT3guy said:
Nougat? That's Android v7, no? I don't think I'll be able to get the OTA update yet. I'll need to get the Vodaphone SIM unlock sorted first.
Click to expand...
Click to collapse
No such thing as a Nougat stock ROM for the M8. The previous post is referring to custom AOSP ROMs, which is the only type of ROM that has Nougat for the M8.
But I don't necessarily see this as a good suggestion. The stock TWRP backup should restore and boot fine, if you follow the instructions properly, and can get the files onto the phone (may be difficult with a broken USB port).
---------- Post added at 09:09 AM ---------- Previous post was at 09:07 AM ----------
GT3guy said:
Well, thanks, but I'm trying to get it back to "factory state" to send it to HTC for repair of that annoyingly problematic USB socket.
Click to expand...
Click to collapse
Since sending to HTC for repair is the intention, I think you are wasting your time. I highly doubt this phone has any warranty any longer, due to it's age (most warranties are only 1 year from original purchase) and also the fact that is was purchased 2nd hand.
HTC will repair the port for a fee, and in the process restore stock ROM.
redpoint73 said:
You are misunderstanding the linked thread. What you tried to do, is to flash stock HTC recovery (recovery_6.12.1614.img).
You need to flash custom recovery TWRP, in order to restore a stock TWRP backup from ckpv5's thread.
---------- Post added at 09:07 AM ---------- Previous post was at 09:04 AM ----------
No such thing as a Nougat stock ROM for the M8. The previous post is referring to custom AOSP ROMs, which is the only type of ROM that has Nougat for the M8.
But I don't necessarily see this as a good suggestion. The stock TWRP backup should restore and boot fine, if you follow the instructions properly, and can get the files onto the phone (may be difficult with a broken USB port).
---------- Post added at 09:09 AM ---------- Previous post was at 09:07 AM ----------
Since sending to HTC for repair is the intention, I think you are wasting your time. I highly doubt this phone has any warranty any longer, due to it's age (most warranties are only 1 year from original purchase) and also the fact that is was purchased 2nd hand.
HTC will repair the port for a fee, and in the process restore stock ROM.
Click to expand...
Click to collapse
1) Yes, I subsequently realised that I hadn't flashed the correct recovery image, as per post #2. I successfully flashed the TWRP recovery, then successfully restored the TWRP 6.12.161.4 backup., and then flashed the 6.12.161.4 recovery image. All was mostly OK (apart from the lengthy "optimizing nn of 164 applications", re-entering data etc.), but it would occasionally crash subsequently and reboot, and seems to get stuck after the initial Vodafone and then HTC active displays (GIFs?) with just a white screen and the green HTC text.
2) I was less interested in the latest Nougat (v7) firmware, but I did vaguely understand that it might not be available as an OTA update or as a "stock" (HTC?) package.
3) Do you have any ballpark figure for the HTC repair fees? And would you happen to know how/where I would send it? I had a really good conversation with a HTC support guy about what to do beforehand (remove SIM and MicroSD holders, factory reset to clear personal data), but he omitted the "to where" information. The M8 went rogue before I could get around to enquiring again.
Thanks for your succinct reply.
GT3guy said:
3) Do you have any ballpark figure for the HTC repair fees? And would you happen to know how/where I would send it?
Click to expand...
Click to collapse
I haven't seen a $ figure for a USB port repair specifically. I think I've seen around $150-300 US (no idea where you are located) for some repairs. Higher end being full motherboard replacement, which they may tell you is needed, anyway. No idea if they dink around with just replacing the USB port.
Obviously, at the higher end of that repair fee, you practically may as well just buy something like a brand new OnePlus 5.
You may investigate getting the port repaired by a local shop. Probably be a lot cheaper (less than $100) although with less certainty of a working phone afterward. You might be coming back here, and getting help from us to restore the software once the USB port is repaired (HTC will return the phone fully working - but at a price).
As for where to send (if you decide on HTC service) you should contact HTC again. The service address will vary by your location, and they will probably need to collect your details, address, give you an RMA number, etc. I don't suspect you can just throw it in a box, and send it to them. Not following the process will probably delay getting it back, at a minimum; or even (at worst) cause it to get lost forever.
To round out this thread, HTC wanted the price of a new 'phone, so I bought an HTC 10 and forgot about trying to get my old 'phone back (it was a cheap eBay purchase).
GT3guy said:
To round out this thread, HTC wanted the price of a new 'phone, so I bought an HTC 10 and forgot about trying to get my old 'phone back (it was a cheap eBay purchase).
Click to expand...
Click to collapse
The 10 is a great device. You've made a wise choice. The audio quality on it is outstanding!
Hi,
First of all, this was supposed to be my first flash. So I am very new and confused. (I get that you probably have loads of those... I am sorry)
I got a HTC One M8 that was already rooted and S-OFF, had SuperCID and everything. And I hate the 4.4.4 Android, plus no OTA updates are available to me (when I tried to check, it gets stuck). So I wanted to flash in a LineageOS 16.0. I unlocked the bootloader, got TWRP 2.8.7.0, pasted the Lineage 16.0 ZIP file, and wanted to flash it. But, I got an error "Error executing updater binary in zip [zip filename]", and so I went to check the instructions to install.
https://forum.xda-developers.com/htc-one-m8/development/rom-lineageos-16-0-htc-one-m8-t3837538
Here it says this:
- Reboot to recovery (TWRP by @Captain_Throwback) - Direct link
- Wipe /system, /data and /cache
- Install LineageOS zip package
and I did that to see if it changes anything, Nope, it didn't. I tried to reboot the phone to get it fixed (someone in another thread suggested getting an md5 file for it).
And after the reboot I am stuck on HTC logo screen, can't shut it down at all. I can't use ADB because it doesn't see the device, so I can't getvar all. I do remember that my version-bootloader was 3.19.0.0000, but that's all.
I am not asking for a full guide on what to do, because it's probably impossible, but can anyone at least tell me how to proceed next? I'd love to turn off the phone and at least try to do something with TWRP. (I didn't have a backup, yes I am an idiot)
EDIT: Holding volume up and power button to do the reset just turns off the screen for a few secs then goes to HTC logo screen again.
Okay, I waited for it to discharge so I can get to the bootloader. I will post getvar when it charges.
EDIT: here we go
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I basically just want anything to work now, even stock will be okay (but 6.0 at least)
1st edit your last post & remove your IMEI/MEID unless you want it stolen...
when you wiped /system in TWRP & your zip didn't flash, u lost your ROM
easiest way to get the phone back up & working is to flash the RUU, looks like you currently have 3.30.651.2 (very old)
here is the 3.30.651.2 exe version: https://androidfilehost.com/?fid=95784891001604379
or to update to the latest version 6.20.651.3:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
OMJ said:
1st edit your last post & remove your IMEI/MEID unless you want it stolen...
Click to expand...
Click to collapse
Yeah, I forgot, thanks for reminding.
So do I just run the .exe with my phone plugged in my PC while in bootloader? Or do you mean TWRP/adb flashing?
gr0za said:
Yeah, I forgot, thanks for reminding.
So do I just run the .exe with my phone plugged in my PC while in bootloader? Or do you mean TWRP/adb flashing?
Click to expand...
Click to collapse
yes, run exe from pc while connected to phone
OMJ said:
yes, run exe from pc while connected to phone
Click to expand...
Click to collapse
3.30.651.2 worked, 6.20.651.3 did not ( I tried it first). To be honest I'm so damn glad it works, because I ain't a Sprint user, but somehow Orange works. Got all the bloaty Google Aps that I don't give an f about, but at least it's working. Hopefully I can go to 6.20 next, I'm gonna try. BTW, will flashing GApps remove all the unnecessary Sprint apps? Or do I have to do something different with it? (I don't need neither the GApps not the Sprint apps, but this phone seems to be a Sprint one and I guess I have to deal with it)
EDIT: yeah, 6.20 doesn't work, it gives me Error 155 - Error updating ROM. I remember hitting up HTC live support once in desperation, and the guy told me I have to upgrade to Lollipop first. But where do I even find a RUU for that?
gr0za said:
3.30.651.2 worked, 6.20.651.3 did not ( I tried it first). To be honest I'm so damn glad it works, because I ain't a Sprint user, but somehow Orange works. Got all the bloaty Google Aps that I don't give an f about, but at least it's working. Hopefully I can go to 6.20 next, I'm gonna try. BTW, will flashing GApps remove all the unnecessary Sprint apps? Or do I have to do something different with it? (I don't need neither the GApps not the Sprint apps, but this phone seems to be a Sprint one and I guess I have to deal with it)
EDIT: yeah, 6.20 doesn't work, it gives me Error 155 - Error updating ROM. I remember hitting up HTC live support once in desperation, and the guy told me I have to upgrade to Lollipop first. But where do I even find a RUU for that?
Click to expand...
Click to collapse
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
GApps probably only adds Google apps, I doubt it removes anything. once you get up to 6.20, you can root the phone (I recommend Magisk) then use a file explorer like Root Explorer to mount /system & then delete the bloat u dont want. You can also do this in twrp.
the other option is to flash a custom ROM that removes the bloat....my ROM removes bloat but retains pertinent Sprint apps
OMJ said:
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
GApps probably only adds Google apps, I doubt it removes anything. once you get up to 6.20, you can root the phone (I recommend Magisk) then use a file explorer like Root Explorer to mount /system & then delete the bloat u dont want. You can also do this in twrp.
the other option is to flash a custom ROM that removes the bloat....my ROM removes bloat but retains pertinent Sprint apps
Click to expand...
Click to collapse
Alright, once I flashed the Sprint RUU, all of a sudden I have OTA updates. I'm getting to 6.20 now, so everything's fine.
Yeah, I will consider removing them the way you said. Also, I don't really need any Sprint apps, as I am not a Sprint client anyway, but I reckon some are better left unchecked. Much, much appreciated for the help and the links.
gr0za said:
(bootloader) version-main: 3.30.651.2
Click to expand...
Click to collapse
This was the main problem with flashing Lineage, your firmware (hboot, radio, etc.) was much too old. The current ROMs are not compatible with the old firmware. Now that you're updated to Marshmallow, I'll bet Lineage will install correctly (of course, you need to install TWRP again, etc.).
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
gr0za said:
Holding volume up and power button to do the reset just turns off the screen for a few secs then goes to HTC logo screen again.
Click to expand...
Click to collapse
Hold vol up and power button to force a reboot. The moment the screen goes dark, signaling it is about to reboot, slide your finger from vol up, to vol down, and don't let go. This should get you into bootloader.
As long as the screen comes on, you can get into bootloader. Exception is, if your vol rocker is broken!
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
OMJ said:
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
Click to expand...
Click to collapse
Version check is okay if the RUU is same or greater version number (and skipping versions is usually okay). You can't go backwards (downgrade), is all.
There was a peculiar requirement on Marshmallow RUUs for US carrier versions of the M8. It is required to flash the appropriate Marshmallow firmware by fastboot, before the RUU would work, if coming from Lollipop or lower.
redpoint73 said:
This was the main problem with flashing Lineage, your firmware (hboot, radio, etc.) was much too old. The current ROMs are not compatible with the old firmware. Now that you're updated to Marshmallow, I'll bet Lineage will install correctly (of course, you need to install TWRP again, etc.)
Click to expand...
Click to collapse
Are you sure of this? I have a Sprint variant. And I found conflicting info whether Lineage works on Sprint or doesn't work.
gr0za said:
Are you sure of this? I have a Sprint variant. And I found conflicting info whether Lineage works on Sprint or doesn't work.
Click to expand...
Click to collapse
Not 100%, as I don't personally own the Sprint version M8. But what I can say:
1) The Lineage 16 thread says: "Builds are compatible with all M8 single SIM variants (m8ul, m8vzw and m8spr)."
Now the identifier "m8spr" isn't a correct one I've ever seen attached to the M8. But I think they mean the Sprint variant. Correct product ID would be M8_whl.
2) Instance of custom ROMs not working on M8 CDMA variants (Sprint and Verizon) are mainly due to the fact that those variants use a different Sense kernel. So mostly only applied to Sense ROMs. AOSP ROMs (in particular Lineage) which use their own kernel, work okay with the CDMA variants, far as I've seen.
3) Your firmware is so out to day, it will not work with any of the current ROMs. And when I say current, I mean any from the past several years. You should definitely update the firmware in any case, as it will cause lots of problems with custom ROMs, and no good reason to stay on the old firmware. Once firmware is updated, it is not hard to flash TWRP and try Lineage again. I think it will work, and there is certainly no harm in trying, even if it doesn't. The worst case scenario is that you flash a more updated (Marshmallow) version of the stock Sprint ROM. Which is still better than where you started with all this.
redpoint73 said:
2) Instance of custom ROMs not working on M8 CDMA variants (Sprint and Verizon) are mainly due to the fact that those variants use a different Sense kernel. So mostly only applied to Sense ROMs. AOSP ROMs (in particular Lineage) which use their own kernel, work okay with the CDMA variants, far as I've seen.
3) Your firmware is so out to day, it will not work with any of the current ROMs. And when I say current, I mean any from the past several years. You should definitely update the firmware in any case, as it will cause lots of problems with custom ROMs, and no good reason to stay on the old firmware. Once firmware is updated, it is not hard to flash TWRP and try Lineage again. I think it will work, and there is certainly no harm in trying, even if it doesn't. The worst case scenario is that you flash a more updated (Marshmallow) version of the stock Sprint ROM. Which is still better than where you started with all this.
Click to expand...
Click to collapse
I updated the firmware. I now have this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-main: 6.20.651.3
But the SIM doesn't work with Lineage anyway, just flashed in anew and tried. The old Sprint 6.0 ROM that I RUU'd has the same issue. Could it be the radio version, or the firmware? Because it used to work, with some troubles, but still.
gr0za said:
Could it be the radio version, or the firmware? Because it used to work, with some troubles, but still.
Click to expand...
Click to collapse
The radio is part of the firmware. Not sure why your SIM would have troubles with the newer radio (if that is the case).
You can try this: https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
Or you can try flashing back to RUU 3.30.651.2 and see if there is any change.
redpoint73 said:
The radio is part of the firmware. Not sure why your SIM would have troubles with the newer radio (if that is the case).
You can try this: https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
Or you can try flashing back to RUU 3.30.651.2 and see if there is any change.
Click to expand...
Click to collapse
Omg, how come I didn't see this thread. Thanks so much, I will try once I get back home.
I hope this thread isn't problematic, because I moved the goalpost since creating it. But I'd rather not create a thread every time I have a problem...
gr0za said:
I hope this thread isn't problematic, because I moved the goalpost since creating it. But I'd rather not create a thread every time I have a problem...
Click to expand...
Click to collapse
The problems are all related, and probably the same root cause (Sprint version, firmware, etc.). I agree it is most appropriate to keep everything to this one thread.