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 guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.
yldlj said:
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
ubadafatta said:
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
Click to expand...
Click to collapse
Since there Is no RUU and you re locked your Bootloader there's not much I can help you with sorry.
ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on
Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.011s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.080s]
finished. total time: 1.094s
this what i get when i try to flash unlocktoken or oem unlock bootloader or even when i try get_token_identifier
You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
ubadafatta said:
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on
Click to expand...
Click to collapse
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.
Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The threory of the OTA is fine but not in this case.
Cheers.
Click to expand...
Click to collapse
Yeah thanks. I deleted all my post because there's no point in arguing. Your correct I totally forgot what the OP problem was after all this. Thanks for the clarification.
Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.
Click to expand...
Click to collapse
It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
ayyu3m said:
Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Click to expand...
Click to collapse
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Mr Hofs said:
It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
Click to expand...
Click to collapse
ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I will have a look at it when i have more time, and let's not bash but learn ?
:highfive:
Cheers guys.
ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:
Yeah i got your PM. Thanks for that. After reading your PM i also knew how stupid i was being. And when i came to delete the post, they were already deleted by the thread administrators.
Sorry once more man. Wont happen again
yldlj said:
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:
Click to expand...
Click to collapse
ayyu3m said:
You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
Click to expand...
Click to collapse
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on
[email protected] said:
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on
Click to expand...
Click to collapse
Flash ruu
https://androidfilehost.com/?fid=673956719939830809
yldlj said:
Flash ruu
https://androidfilehost.com/?fid=673956719939830809
Click to expand...
Click to collapse
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%
[email protected] said:
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%
Click to expand...
Click to collapse
Yeah everyone I flash RUU it does bypass some things. Relocking bootloader usually causes problems and I don't know people still keep doing it. I would say flash twrp followed by leedroid but pretty sure you need an unlocked bootloader to flash twrp. Sorry but I'm out of ideas.
Dear friendly xda-developer people,
my HTC One M8 went out because of an empty battery. When I restarted, it only boots the bootloader. The security mode isn't working as well. I tried all I could think of and now I just want to install the original OS on the phone in hope that it will work again.
When I boot up the phone it says it is "OS-6.12.161.4". I am from Germany and I guess it is a vodafone branded HTC. So I do not find the right software on the official US website. I tried to google a different version and all I could find was a software to which the phone anwsers when I try to install the .zip via SD-card "Image Update Fail! Device halted due to Large Image update fail!"
I will post the complete screen of the boot below.
Any ideas what I could do? I tried to update it via PC, that didn't work as well. I think I need the right software and the one I found might just be the wrong one. I also tried to unlock it, but relocked it because I read, that I can not install the original software if it is unlocked.
If I can not install the original os: Is it possible to install something else that just works like the original OS? I can not use Google Products than?
I am really thankful for any advice.
Greetings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is the background of this device? Did it have a stock "official" HTC ROM on there when you had the "no OS" issue? Was it ever bootloader unlocked before you unlocked it to try to solve this problem?
Best for us to see more details about the phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
ghostmag said:
I tried to google a different version and all I could find was a software to which the phone anwsers when I try to install the .zip via SD-card "Image Update Fail! Device halted due to Large Image update fail!"
I tried to update it via PC, that didn't work as well. I think I need the right software and the one I found might just be the wrong one.
Click to expand...
Click to collapse
You absolutely need to use an RUU (ROM Update Utility) that is intended for your M8 version's (Vodaphone) carrier ID (CID) as well as the version number 6.12.161.4. Another version number means it is made for a different CID, and will fail by definition. HTC phones are quite strict about version number checking.
In your case, I don't think that there exists an RUU for the Vodaphone version. But you can install the stock OS by other means (see below).
ghostmag said:
If I can not install the original os: Is it possible to install something else that just works like the original OS?
Click to expand...
Click to collapse
While your Vodaphone version M8 doesn't have an RUU, there is another way to get back to the stock ROM. You can unlock the bootloader again, than install TWRP and a stock TWRP backup from the collection.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to do through Step 9, then reboot and it should boot to the OS. The remaining steps were only for getting official OTA updates (which is no longer relevant).
ghostmag said:
I can not use Google Products than?
Click to expand...
Click to collapse
I think you mean a ROM straight from Google? Google doesn't make complete ROMs for any device, except for Pixel devices (and the old Nexus devices). For any other device manufacturer, at least some part of the ROM needs to be customized for the specific hardware configuration. But you do have some options, if you want a ROM that is more lightweight then the HTC Sense interface:
Even though we don't have a "pure" Google ROM; what we do have for the M8, is something called the Google Play Edition (GPe). Which even though made by HTC, is designed to feel like a "pure Google" ROM. Once you have the bootloader unlocked and TWRP installed, you can install this the same way as a custom ROM. Follow the part of the thread labelled "Flashable GPe ROM". You can't flash as an RUU, since you are s-on.
https://forum.xda-developers.com/showthread.php?t=2708589
Another option is Lineage custom ROM. Lineage custom ROM is somewhat similar to a Google OS. Although at this point, it does have enough modifications, that I can't really consider it a "pure Google" experience. But it is much more lightweight than a Sense ROM. Very similar to installing the GPe ROM, once you have the bootloader unlocked, install TWRP and flash the ROM.
redpoint73 said:
What is the background of this device? Did it have a stock "official" HTC ROM on there when you had the "no OS" issue? Was it ever bootloader unlocked before you unlocked it to try to solve this problem?
Best for us to see more details about the phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
You absolutely need to use an RUU (ROM Update Utility) that is intended for your M8 version's (Vodaphone) carrier ID (CID) as well as the version number 6.12.161.4. Another version number means it is made for a different CID, and will fail by definition. HTC phones are quite strict about version number checking.
In your case, I don't think that there exists an RUU for the Vodaphone version. But you can install the stock OS by other means (see below).
While your Vodaphone version M8 doesn't have an RUU, there is another way to get back to the stock ROM. You can unlock the bootloader again, than install TWRP and a stock TWRP backup from the collection.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to do through Step 9, then reboot and it should boot to the OS. The remaining steps were only for getting official OTA updates (which is no longer relevant).
I think you mean a ROM straight from Google? Google doesn't make complete ROMs for any device, except for Pixel devices (and the old Nexus devices). For any other device manufacturer, at least some part of the ROM needs to be customized for the specific hardware configuration. But you do have some options, if you want a ROM that is more lightweight then the HTC Sense interface:
Even though we don't have a "pure" Google ROM; what we do have for the M8, is something called the Google Play Edition (GPe). Which even though made by HTC, is designed to feel like a "pure Google" ROM. Once you have the bootloader unlocked and TWRP installed, you can install this the same way as a custom ROM. Follow the part of the thread labelled "Flashable GPe ROM". You can't flash as an RUU, since you are s-on.
https://forum.xda-developers.com/showthread.php?t=2708589
Another option is Lineage custom ROM. Lineage custom ROM is somewhat similar to a Google OS. Although at this point, it does have enough modifications, that I can't really consider it a "pure Google" experience. But it is much more lightweight than a Sense ROM. Very similar to installing the GPe ROM, once you have the bootloader unlocked, install TWRP and flash the ROM.
Click to expand...
Click to collapse
First of all: Thank you very very much for your time and effort answering me. I highly appreciate that.
I will try to deliver fastboot getvar-data as soon as I am able to get back to a Windows or Ubuntu PC.
I now was able to install a TWRP backup. Your link is very helpful.
Sadly, my sound isn't working anymore now. I guess every 20 reboots or so it does work, but I can not replicate that.
Also I can not make videos and can not record audio. I then tried to install Cynagenmod which had the same problem and then I tried Lineage OS which had the same problem as well.
Do you have an idea what I can do to fix that? I read about upgrading radio, but that sounds like an easy-to-brick-my-phone way.
In case that helps: Background of the phone is just stock "official" HTC ROM as far as I know.
Since I was able to install other OS, the part of the screenshot above where you can read "OS-6.12.161.4" is just "OS" and nothing else anymore.
Regarding the topic that I wanted the original firmware: I thought Gapps are only available on official firmware. Since I know that a custom OS can run them as well, I do not care about the OS. I thought LineageOS and Cynagenmod were both lovely and would try out everything that does the job.
Any idea how it is possible that the sound / recording videos and sound don't work with three different OS?
Greetings
My responses below in red font:
ghostmag said:
Sadly, my sound isn't working anymore now. I guess every 20 reboots or so it does work, but I can not replicate that.
Also I can not make videos and can not record audio. I then tried to install Cynagenmod which had the same problem and then I tried Lineage OS which had the same problem as well.
Might be a firmware issue. When I say "firmware", I am referring to a specific package (usually a file named firmware.zip) that contains certain partitions necessary for the ROM to work (radio, hboot, recovery, and others), but does actually not contain the ROM itself. On that note, it is probably best for you to stop thinking of the term "firmware" as interchangeable with the ROM. If you mean ROM, just say ROM. No need to call it something else, and doing so will just cause confusion. It is best to use specific terms (stock ROM, RUU, stock TWRP backup, etc.).
Random sound or video issues can sometimes be a result of old/damaged firmware. It is probably useful to flash the firmware (more on this below).
Do you have an idea what I can do to fix that? I read about upgrading radio, but that sounds like an easy-to-brick-my-phone way.
You can't flash a radio (alone) with s-on. And not worth getting s-off ($25 US by sunshine app) just to flash a radio. What you can do, is flash the whole firmware zip, and see if that helps. But I'd like to get the full getvar output, to make sure which firmware is the correct one for your version M8. As you mentioned, flashing the wrong radio can be catastrophic.
In case that helps: Background of the phone is just stock "official" HTC ROM as far as I know.
Since I was able to install other OS, the part of the screenshot above where you can read "OS-6.12.161.4" is just "OS" and nothing else anymore.
What version TWRP did you install? If you followed the guide closely, you should have used TWRP 2.8.7 or later. No number being shown for OS version is sometimes a result of flashing Lineage (known bug), or an old version of TWRP.
Click to expand...
Click to collapse
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
I got the getvar all reaction now:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
The first time I tried working with TWRP I installed an older version - sadly don't remember which one. I installed a version of Cynagenmod with it. Then I accidentally crashed TWRP somehow so I had to install it again so I am using 3.3.0-0 right now because I thought it's best to install the newest version I could find.
Should I try again installing a different version of TWRP?
Sidenote: I now have the problem that WLAN doesn't work a lot of times. I need to reboot around 5 times so WLAN works. I guess that is another issue because of the mistakes I made while installing different OS.
Thanks again for your time.
ghostmag said:
The first time I tried working with TWRP I installed an older version - sadly don't remember which one. I installed a version of Cynagenmod with it. Then I accidentally crashed TWRP somehow so I had to install it again so I am using 3.3.0-0 right now because I thought it's best to install the newest version I could find.
Should I try again installing a different version of TWRP?
Click to expand...
Click to collapse
TWRP 3.3.0-0 should be okay. I agree, using the latest version is typically the best thing to do.
What I would try, is the following. Note that you will lose all data on the phone when you do this, so plan accordingly, if there is any data on the phone you want to keep (backup to cloud, computer, etc.):
1) Flash the firmware fw_6.12.161.4 from here (instruction on how to flash firmware, near the bottom of the post): https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2) After flashing firmware, you will need to unlock the bootloader again. Either use the same unlock bin code you used before (flash with fastboot command). Or go through the process on HTVDev.com, to get a new code.
3) Flash TWRP back to the device (flashing stock firmware wipes TWRP, so you need to put it on there again).
4) Restore stock TWRP backup 6.12.161.4, using TWRP. https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Not sure if this will solve your problems, but I'm hoping it will. This process will put a stock ROM and corresponding firmware on the device (a clean slate, as it were).
redpoint73 said:
TWRP 3.3.0-0 should be okay. I agree, using the latest version is typically the best thing to do.
What I would try, is the following. Note that you will lose all data on the phone when you do this, so plan accordingly, if there is any data on the phone you want to keep (backup to cloud, computer, etc.):
1) Flash the firmware fw_6.12.161.4 from here (instruction on how to flash firmware, near the bottom of the post): https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2) After flashing firmware, you will need to unlock the bootloader again. Either use the same unlock bin code you used before (flash with fastboot command). Or go through the process on HTVDev.com, to get a new code.
3) Flash TWRP back to the device (flashing stock firmware wipes TWRP, so you need to put it on there again).
4) Restore stock TWRP backup 6.12.161.4, using TWRP. https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Not sure if this will solve your problems, but I'm hoping it will. This process will put a stock ROM and corresponding firmware on the device (a clean slate, as it were).
Click to expand...
Click to collapse
Dear friend,
I followed your guide and right now I am at step 3)
While looking for the newstest TWRP.img-file the phone is booting Android and is installing Apps right now. I even heard at startup sound. Is it possible, that I won't need the following steps and it just got the stock firmware from my last install?
ghostmag said:
I followed your guide and right now I am at step 3)
While looking for the newstest TWRP.img-file the phone is booting Android and is installing Apps right now. I even heard at startup sound. Is it possible, that I won't need the following steps and it just got the stock firmware from my last install?
Click to expand...
Click to collapse
Yes, it is possible you don't need to do anything further.
As I warned before, be careful about using the term "firmware". It seems you are using it synonymously with "ROM" again. If you accomplished Step 1 (as designated in my last response) you flashed the stock firmware. The stock ROM should still be there from the TWRP backup you restored previously. Nothing you have done so far, would have overwritten the stock ROM that you restored, so it is still there.
You previously restored the proper number 6.12.161.4 stock TWRP backup?
redpoint73 said:
Yes, it is possible you don't need to do anything further.
As I warned before, be careful about using the term "firmware". It seems you are using it synonymously with "ROM" again. If you accomplished Step 1 (as designated in my last response) you flashed the stock firmware. The stock ROM should still be there from the TWRP backup you restored previously. Nothing you have done so far, would have overwritten the stock ROM that you restored, so it is still there.
You previously restored the proper number 6.12.161.4 stock TWRP backup?
Click to expand...
Click to collapse
Yes, I did and it all works fine now. Even the battery is much better than before.
Thank you very very much for your time and help. If you ever come to Germany, let me know and I will buy you a drink or something
Kind regards and have a good life
ghostmag
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.