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).
Hello,
I've just received my One M8 some days ago. It came with Lollipop and I immediately did a system update to 6.0 Marshmallow.
Next step was unlocking bootloader and rooting it by installing LeeDroiD (based on stock Sense). At this point I discovered that the phone did not want to connect to my car audio and my bluetooth speakers. The One M8 simply does not show these devices. It DOES see my Moto G and my laptop computer's bluetooth which implicates that BT is not 100% broken. Sadly I can not say if it ever worked well, because I did not check with original HTC Android.
System information:
Bootloader unlocked, S-ON
HBOOT: 3.19.0.0000
Radio: 1.29.214500021.12G
Open-DSP: v51.2.2-00593-M8974_FO.1015
OS: 6.12.401.4
I've also tested bluetooth on CM13.0 and a SkyDragon version of stock Sense ROM, but same result.
Not being able to use my hands free calling in my car makes this devices a useless brick for me
Is it possible that the initial system update did not work properly? I'm thinking about flashing a 6.12.401.4 RUU (altough I'm already on this firmware) what might get hard, because I'm S-ON and Sunshine keeps telling me that my ROM is not stock enough.
As far as I know I can not flash a RUU of the same version when I'm not S-OFF. But in order to get S-OFF, I need a stock Android system...
Any ideas? I'm ready for anything
dyfk3l said:
Is it possible that the initial system update did not work properly? I'm thinking about flashing a 6.12.401.4 RUU (altough I'm already on this firmware)
Click to expand...
Click to collapse
RUU is what I would try, for 2 reasons:
1) RUU is a "cleaner" way to update, it re-writes all partitions. OTA often just patches what has changed, plus migrates user data, which can often lead to random issues.
2) It sounds like you went straight to a custom ROM. So its best to RUU to a full "stock" baseline, then see if you still have the problem.
Be aware that RUU will wipe the phone, so backup any data you want to keep accordingly.
dyfk3l said:
As far as I know I can not flash a RUU of the same version when I'm not S-OFF. But in order to get S-OFF, I need a stock Android system...
Click to expand...
Click to collapse
RUU of the same version is fine (for "repair" such as in your case) with s-on. The limitation is running an older version RUU, which is only possible with s-off.
A RUU update worked for me!
Thank you for the note that flashing the same version is fine on S-ON. It was no problem; after that I could easily S-OFF via root and Sunshine.
Bluetooth is working fine now! I never was a friend of OTA updates and I never will be. So it was the right way going the clean way. :good:
Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.
kalel29 said:
Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.
Click to expand...
Click to collapse
For download mode SD card method:
Make sure you're using an external SD card, not internal storage.
Make sure SD card is formatted properly.
Make sure file is named 100% correctly and is meant for that specific carrier /model.
No reason it shouldn't work.
Sent from my HTC6545LVW using Tapatalk
kalel29 said:
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Click to expand...
Click to collapse
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.
Flippy498 said:
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.
Click to expand...
Click to collapse
Yes I flashed the one for my operator. Can I flash another RUU?
About your links, I'll check them when I get back from work. Thanks.
Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.
Flippy498 said:
Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.
Click to expand...
Click to collapse
Hi again, the phone is giving me this error :
im still lost ,hope this helps to point me in the right direction.
Code:
D:\Francisco\Desktop\HTC\fastboot_adb\fastboot_adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.44.600.1
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: HTC__332
all:
finished. total time: 0.033s
Thanks
You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.
Flippy498 said:
You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.
Click to expand...
Click to collapse
Ok,thanks, and yes,the RUU I was trying to flash I the telcel one.
I'm going to tell my fiend that he needs to pay in order to get his phone working.
Thanks again for everything. Have a nice day.
Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.
kalel29 said:
Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.
Click to expand...
Click to collapse
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.
Flippy498 said:
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.
Click to expand...
Click to collapse
The phone has the ICE rom,Twrp and superSU,I think it's a sense-based rom, sorry I can't give you more info, as I said I'm new in flashing HTC, but I'm learning thanks to you.
ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.
Flippy498 said:
ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.
Click to expand...
Click to collapse
So basically, no matter what rom I flash,sense or no sense based, I will need sunshine in order to have a working baseband?
No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.
Flippy498 said:
No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.
Click to expand...
Click to collapse
Finally i have signal again,flashed slim 6 and monokernel. Thank you so much,i've learned something new about HTC now im going to return the phone to my friend,also i explained what you told me in order to have a sense based rom.
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.
I've done this whole custom rom thing back when I got the phone in 2014 or so, since then I've done no other modifications. Installing AR 53.1 was straight forward to me, DL it, put it into the SD and use TWRP to install, ect... I also tried Viper, however, I'm having some performance issues with it.
I wanted to go back to stock so I found v5 of the stock recovery for my phone, the phone runs much, much better, but I want v6 (marshmallow). I tried for a good couple of hours to find what I wanted without much luck, so I thought I would give another custom rom a try, this is where I don't know what to do.
I need HTC M8 6.12.XXX.XX firmware. The folks of LeeDrOiD say I need this firmware installed. I cannot find any kind of 6.12 firmware. I don't know if this firmware needs to be specifically for my version of the phone which is Rogers (Canada) or if any will work. I was hoping someone here can help me find this firmware, or tell me if I even need it, thank you.
Carrier - Rogers (Canada)
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: 11111111
(bootloader) version-main: 4.16.401.10
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
LeeDrOiD
https://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
There are many ways to update firmware ... and not necessarily 6.12 firmware .. any 6.xx firmware.
But I give you the simplest and proper as you need the full firmware not some modded one so everything firmware wise will be up-to-date
1. Install full htc signed Rogers firmware - 6.13.631.7
You can get the fw_6.13.631.7.zip here : https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2. After the firmware is installed, install the latest TWRP 3.0.2-0
https://dl.twrp.me/m8/
3. Install your custom ROM
4. done
Note : no need to relock bootloader as you have a S-Off device (assuming from the SuperCID on your bootloader as you posted above).
Oh wow, thank you. I cant tell you how long I've tried to find this on google, I've looked for rogers firmware, to stock firmware, I can't believe it didn't show that list. Thank you.
I removed everything from my Internal and SD storage using TWRP, I would now flash the firmware then from there install the rom correct? I'll go search up on how to do that then. Also, I would be grabbing the CID ROGER001? My CID is just the 1s, I just want to confirm.
Again, thank you.
Why want to remove everything .. no need.
And no need to change anything even CID ... just follow the steps I said above .. that 1,2,3,4
that's all you need to do , don't make it complicated.
Read the link, it has how to install firmware.
Ah, my understand (not much) was that I needed the new firmware before installing the rom. Alright then, time to do this.
I still cant thank you enough. If only google showed that thread...
EDIT:
Im S-OFF unlocked. I dont need to lock it?
I edited my post as I'm not familiar with that ROM.
It may not have stock kernel.
It's better, firmware first and ROM later
SpaceGold said:
EDIT:
Im S-OFF unlocked. I dont need to lock it?
Click to expand...
Click to collapse
Please read my post #2 above .. already mentioned about S-Off.
Good luck, got to go now
Thank you, take care.