Develop Bugs

[Q] Go back to stock

Hi there.
I was wondering if anyone could help me. I want to go back to stock recovery to perform an OTA (4.4.4). I'm currently using ViperOne m8 2.5. My Cid is called HTC_Y13. But I couldn't find it anywhere.
What to do?
I'm Danish by the way. My phone is a One M8 and I believe it's the international model..
Kind Regards René Bundgaard

RenBund88 said:
Hi there.
I was wondering if anyone could help me. I want to go back to stock recovery to perform an OTA (4.4.4). I'm currently using ViperOne m8 2.5. My Cid is called HTC_Y13. But I couldn't find it anywhere.
What to do?
I'm Danish by the way. My phone is a One M8 and I believe it's the international model..
Kind Regards René Bundgaard
Click to expand...
Click to collapse
here's the steps to get you back to stock
download this > https://mega.co.nz/#!VcZAgIgT!flJca5C_hRl6pgAn5EXp4qbJCl0ONjZB8PHNylw5f3Y
while it's downloading go into TWRP and choose Backup
uncheck everything except boot ... do the backup
this will create a folder on your sdcard TWRP/BACKUPS/your_Serial_no/Todays date
when the download is complete extract it to the Todays date folder. Make sure it's just files in the folder and no folders
now boot back to TWRP and choose restore and restore the backup / make sure system and boot are checked.
the last step is to put back the stock recovery
use this one > http://d-h.st/WB4
you flash it the same as TWRP
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
your phone should now be back to stock and ready for OTA update

RenBund88 said:
Hi there.
I was wondering if anyone could help me. I want to go back to stock recovery to perform an OTA (4.4.4). I'm currently using ViperOne m8 2.5. My Cid is called HTC_Y13. But I couldn't find it anywhere.
What to do?
I'm Danish by the way. My phone is a One M8 and I believe it's the international model..
Kind Regards René Bundgaard
Click to expand...
Click to collapse
COLLECTION of Stock backup's
Your CID is HTC__Y13 you can download any x.xx.401.x backup from that thread.
The WWE (World Wide English) nandroid backups have the same main version build numbers. All these nands have the main number that is based on the x.xx.401.xx build and all these CIDS are compatible
HTC__001
HTC__E11
HTC__102
HTC__203
HTC__405
HTC__Y13 <<<THERE IS YOUR CID
HTC__304
HTC__A07
HTC__002
HTC__016
HTC__032
HTC__J15
HTC__M27
HTC__A48
HTC__K18
Click to expand...
Click to collapse
Download any x.xx.401.x backup (HTC__001 will be fine) and backup through correct custom recovery(Philz if it was Philz, TWRP if it was a TWRP created backup).
You can also download any x.xx.401.x stock recovery for your device OR you can grab the latest stock recovery from the OTA(Copy OTA.zip to your PC and extract the recovery.img file inside the firmware.zip).

Returning Stock
I'm also a little bit confuse with all information. I've been tryng to solve my ROM problem about 2 days.
I have flashed the ARHD 21.0 on my phone but a lot of errors are happening (common ones like no Wi-fi and other more annoying like extended reboot time). I'm trying to get back to the stock ROM to perform a update of my firmware but I'm kind of very lost in the forum.
My getvar is like:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm very afraid to flash something wrong because everything went wrong with me. What version should I flash? I guess my phone is the International version (since I'm a brazilian and HTC don't sell phones here)
Thanks in advance.

BernardoMorais said:
I'm also a little bit confuse with all information. I've been tryng to solve my ROM problem about 2 days.
I have flashed the ARHD 21.0 on my phone but a lot of errors are happening (common ones like no Wi-fi and other more annoying like extended reboot time). I'm trying to get back to the stock ROM to perform a update of my firmware but I'm kind of very lost in the forum.
My getvar is like:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm very afraid to flash something wrong because everything went wrong with me. What version should I flash? I guess my phone is the International version (since I'm a brazilian and HTC don't sell phones here)
Thanks in advance.
Click to expand...
Click to collapse
No I guess your phone is an International version, not because you're Brazillian but because your CID says "HTC__001" which is International. Like You no doubt read in the 2 posts just above yours, download a nandroid backup for your device and restore it via the correct custom recovery. I even put a link to the thread with the nandroid collection in my first post here!!!
Just download the nandroid for your device, it'll be the 1.54.401.x backup seeing as you're still on the 3.16bootloader. 3.18 was 4.4.3 and 4.4.4 is 3.19 so you're probably still on 1.54.401.x. Download the 1.54.401 backup and restore in custom recovery. Afterwards just flash back the stock recovery.img
Make sure recovery.img is in your adb folder and boot into bootloader and use fastboot flash recovery recovery.img <That'll give you stock recovery again and you can reboot back into OS and download/install and update the OTA/Firmware as it comes all the way to 3.28.401.6/7

BerndM14 said:
No I guess your phone is an International version, not because you're Brazillian but because your CID says "HTC__001" which is International. Like You no doubt read in the 2 posts just above yours, download a nandroid backup for your device and restore it via the correct custom recovery. I even put a link to the thread with the nandroid collection in my first post here!!!
Just download the nandroid for your device, it'll be the 1.54.401.x backup seeing as you're still on the 3.16bootloader. 3.18 was 4.4.3 and 4.4.4 is 3.19 so you're probably still on 1.54.401.x. Download the 1.54.401 backup and restore in custom recovery. Afterwards just flash back the stock recovery.img
Make sure recovery.img is in your adb folder and boot into bootloader and use fastboot flash recovery recovery.img <That'll give you stock recovery again and you can reboot back into OS and download/install and update the OTA/Firmware as it comes all the way to 3.28.401.6/7
Click to expand...
Click to collapse
Sorry man, but I did. I read the post before mine. But I like I said, I'm trying to do this about 2 days and everything went wrong, so I thought that the version HTC__Y13 could have a different procedure that HTC__001.
I'm not the kind of user that thinks the problem is just happening to him. I read a lot of things but seems that more I read, more doubt I get.
Anyway, thank you very much for the fast answer. I will try what you said. :good:
Just one doubt. My ROM is 4.4.4 and my bootloader is 3.16. Is this wrong?

BernardoMorais said:
Sorry man, but I did. I read the post before mine. But I like I said, I'm trying to do this about 2 days and everything went wrong, so I thought that the version HTC__Y13 could have a different procedure that HTC__001.
I'm not the kind of user that thinks the problem is just happening to him. I read a lot of things but seems that more I read, more doubt I get.
Anyway, thank you very much for the fast answer. I will try what you said. :good:
Just one doubt. My ROM is 4.4.4 and my bootloader is 3.16. Is this wrong?
Click to expand...
Click to collapse
Yes, the 4.4.4 ROM MUST have 3.28.xxx.x firmware in order to function properly. You're still on much older firmware which is why you have excessively long boot up times, wifi/data problems(Outdated radio) etc. In order for the ARHD 21.0 to work correctly you must be on the correct firmware(4.4.4 android version, 3.28.401.6/7 <<<If you're international version which you are). This has been the case for some time now, you can do an easy google search "htc one m8 xda ..." along with something like "slow boot up" etc and you'll see that all of them had the same problems, outdated firmware.
Which is why you'll have to go back to stock and do the OTA updates as it comes. If you were S-OFF you could have done it manually and flashed the firmware manually but since you're S-ON you can't do it. Flashing Radio firmware you'll need to either be a) S-OFF or b) Official HTC OTA.

BerndM14 said:
Yes, the 4.4.4 ROM MUST have 3.28.xxx.x firmware in order to function properly. You're still on much older firmware which is why you have excessively long boot up times, wifi/data problems(Outdated radio) etc. In order for the ARHD 21.0 to work correctly you must be on the correct firmware(4.4.4 android version, 3.28.401.6/7 <<<If you're international version which you are). This has been the case for some time now, you can do an easy google search "htc one m8 xda ..." along with something like "slow boot up" etc and you'll see that all of them had the same problems, outdated firmware.
Which is why you'll have to go back to stock and do the OTA updates as it comes. If you were S-OFF you could have done it manually and flashed the firmware manually but since you're S-ON you can't do it. Flashing Radio firmware you'll need to either be a) S-OFF or b) Official HTC OTA.
Click to expand...
Click to collapse
Thanks man! I'm now on 3.28.401.6.
Before your post, I hadn't understood that I needed restore from 1.54.401.x backup (I almost restore 3.28.401.7).
Firewater didn't work in my device, so I have to pay $25 to be S-OFF (and $25 is a lot of money when converting to reais - currency of Brazil)
I will come back tomorrow to give you Thanks (reach my max today).
PS: The 3.28.401.7 update didn't arrive to my device.

Confused!!!
I'm really confused!! I'm not that hardcore at all..
All i want is to update from 4.4.3 to 4.4.4 so I can Update from ViperOne 2.5 to 3.0.
I tried to flash a Stock Recovery called "stock_recovery_1.54.401.5_recovery.img" and I think it succeeded. Hard to see a difference. But I followed a guide made by Sakitech on Youtube. Then I searched for any updates. But it said "No update currently available". So I just flashed the custom Recovery again.
Sorry.. But I'm a Dummy

I am having some major issues too. Im just wanting to go back to stock so I can use sunshine to S-off my phone. My CID is ORANG001 so i got a nandroid backup 1.54.61.5 which is the correct stock and the corresponding stock recovery, all went well but not only does Sunshine still refuse to work, if i take any OTA updates, the first installs ok but then my wifi wont work, ie the switch will not turn green it just goes grey, any ideas!!?!!?

RenBund88 said:
I'm really confused!! I'm not that hardcore at all..
All i want is to update from 4.4.3 to 4.4.4 so I can Update from ViperOne 2.5 to 3.0.
I tried to flash a Stock Recovery called "stock_recovery_1.54.401.5_recovery.img" and I think it succeeded. Hard to see a difference. But I followed a guide made by Sakitech on Youtube. Then I searched for any updates. But it said "No update currently available". So I just flashed the custom Recovery again.
Sorry.. But I'm a Dummy
Click to expand...
Click to collapse
I think I can help you. After all my mistakes, I think I have learn something.
To update to 4.4.4 (and for ViperOne 3.0) you need to update your firmware first. To do that, you have 3 options:
1) S-OFF and update your firmware by flashing a simple file.
2) S-ON and search your EXACTLY modelid and cidnum on this thread
3) -That one BerndM14 help me in previous posts - Check your firmware and return your phone (ROM and Recovery) to stock basing on firmware version. This post explain better.
Like BerndM14 said to you, it is just necessary you to download any x.xx.401.x backup AND any x.xx.401.x stock recovery. After that, follow the instructions of the second question of the post. You will unzip the backup and inside, find a file called 'boot.emmc.win' or 'boot.win'. You have to flash this (fastboot), do a full wipe and then restore the backup (custom recovery). After all you return to bootloader (rebooting) and flash the recovery with this:
fastboot flash recovery <recoveryName>
That it. At least, what I understand. Any advanced user could confirm this informations?

BernardoMorais said:
I think I can help you. After all my mistakes, I think I have learn something.
To update to 4.4.4 (and for ViperOne 3.0) you need to update your firmware first. To do that, you have 3 options:
1) S-OFF and update your firmware by flashing a simple file.
2) S-ON and search your EXACTLY modelid and cidnum on this thread
3) -That one BerndM14 help me in previous posts - Check your firmware and return your phone (ROM and Recovery) to stock basing on firmware version. This post explain better.
Like BerndM14 said to you, it is just necessary you to download any x.xx.401.x backup AND any x.xx.401.x stock recovery. After that, follow the instructions of the second question of the post. You will unzip the backup and inside, find a file called 'boot.emmc.win' or 'boot.win'. You have to flash this (fastboot), do a full wipe and then restore the backup (custom recovery). After all you return to bootloader (rebooting) and flash the recovery with this:
fastboot flash recovery <recoveryName>
That it. At least, what I understand. Any advanced user could confirm this informations?
Click to expand...
Click to collapse
I think I got a Little closer now. Let med undrstand this S-OFF right. Does that make everything a lot easier??
I tried flashing Again yesterday, but without any luck. I downloaded a major stock backup zip file, but I'm not sure how to flash it. I wish I could Just hand it over to someone, but I vant find anyone here in Denmark who is cabable at doing this. ?.
I think The biggest problem is that i dont know where, when and what to flash ?

Peggy1104 said:
I am having some major issues too. Im just wanting to go back to stock so I can use sunshine to S-off my phone. My CID is ORANG001 so i got a nandroid backup 1.54.61.5 which is the correct stock and the corresponding stock recovery, all went well but not only does Sunshine still refuse to work, if i take any OTA updates, the first installs ok but then my wifi wont work, ie the switch will not turn green it just goes grey, any ideas!!?!!?
Click to expand...
Click to collapse
Any ideas guys!? would it have something to do with differant firmware version, ie when the ota is installed it is sitting on an incompatable
firmware version? i know you should flash the boot.emmc.win file before restoring a stock rom but how do i do that with an ota?

RenBund88 said:
I think I got a Little closer now. Let med undrstand this S-OFF right. Does that make everything a lot easier??
I tried flashing Again yesterday, but without any luck. I downloaded a major stock backup zip file, but I'm not sure how to flash it. I wish I could Just hand it over to someone, but I vant find anyone here in Denmark who is cabable at doing this. ?.
I think The biggest problem is that i dont know where, when and what to flash ?
Click to expand...
Click to collapse
I think S-OFF let the things much more easier. My m8 is S-ON so I don't know a lot of this, but there is some tutorial about firewater. If this tool doesn't work for you (like happen to me), you will have to pay $25 for Sunshine. From what I read, this method is guaranteed to get S-OFF.
With S-OFF, you will find some posts with updates of the firmware. So you don't have to go back to stock to update it.
To continue from where you stop, you have to follow this post. Like I said before, download any x.xx.401.x backup AND any x.xx.401.x stock recovery and follow the instructions of "How do i restore the stock nandroid backup" question (same post).
You don't flash the major stock backup zip file. You RESTORE it, on your custom recovery (TWRP or Philz) according from which recovery the backup was made (for example, if you download this one: 1.54.401.5 - TWRP Thanks to Fisha21. This backup was made on TWRP so you have to restore it on TWRP. But before restore, you need to flash the "boot.img or boot.emmc.win" file that is INSIDE this backup zip file. After that you make a full wipe in recovery and then RESTORE the major backup (remember, you don't restore the zip file, you have to unzip it on your phone like is said on the "How do i restore the stock nandroid backup" question of the post).
After all, you will flash the recovery of the same version that you download on the same post.
---------- Post added at 09:27 AM ---------- Previous post was at 09:20 AM ----------
Peggy1104 said:
Any ideas guys!? would it have something to do with differant firmware version, ie when the ota is installed it is sitting on an incompatable
firmware version? i know you should flash the boot.emmc.win file before restoring a stock rom but how do i do that with an ota?
Click to expand...
Click to collapse
You looked your firmware version, befere restore the 1.54.61.5 version? You have to check the CID AND the main version of your phone, like it said on the beggining of the post:
Take the main version number and CID and check if it exists in the collection below ! If it doesn't you can always make a request here.

BernardoMorais said:
I
You looked your firmware version, befere restore the 1.54.61.5 version? You have to check the CID AND the main version of your phone, like it said on the beggining of the post:
Take the main version number and CID and check if it exists in the collection below ! If it doesn't you can always make a request here.
Click to expand...
Click to collapse
My main version number is 2.26.61.5 I think but I asked weather using 1.54.61.5 would be OK and was told it would be fine as its *.**.61.* based backup. Is this incorrect as they use a different firmware base?? Is this whats causing my issues??
Sent from my HTC One (M8)

Peggy1104 said:
My main version number is 2.26.61.5 I think but I asked weather using 1.54.61.5 would be OK and was told it would be fine as its *.**.61.* based backup. Is this incorrect as they use a different firmware base?? Is this whats causing my issues??
Sent from my HTC One (M8)
Click to expand...
Click to collapse
Honestly, I don't know. Why don't you know exactly your main-version? It is empty when you run "fastboot getvar version-main" ?

BernardoMorais said:
Honestly, I don't know. Why don't you know exactly your main-version? It is empty when you run "fastboot getvar version-main" ?
Click to expand...
Click to collapse
Because I'm at work and can't check to be 100% sure I know its definitely 2.26.61.* just not sure what the last number is. Feel like I have ended up with a phone that is going to be stuck in its current state forever now, can't upgrade, can't downgrade. What a mess
Sent from my HTC One (M8)

Peggy1104 said:
Because I'm at work and can't check to be 100% sure I know its definitely 2.26.61.* just not sure what the last number is. Feel like I have ended up with a phone that is going to be stuck in its current state forever now, can't upgrade, can't downgrade. What a mess
Sent from my HTC One (M8)
Click to expand...
Click to collapse
And if you flash the recovery and restore a new backup of your current version (COLLECTION of Stock backup's) ?
After the OTA, your wi-fi stop work but what about your mobile internet?
I don't know what can actually happen, just giving you ideas

BernardoMorais said:
And if you flash the recovery and restore a new backup of your current version (COLLECTION of Stock backup's) ?
After the OTA, your wi-fi stop work but what about your mobile internet?
I don't know what can actually happen, just giving you ideas
Click to expand...
Click to collapse
That's where I got the stock nandroid from, orang001 1.54.61.5 TWRP. Got the matching recovery, all flashed correctly but then like you say after a OTA my WiFi stopped working, mobile data is fine. The WiFi toggle in settings, won't switch over to green, just goes grey.
Sent from my HTC One (M8)

BernardoMorais said:
I think S-OFF let the things much more easier. My m8 is S-ON so I don't know a lot of this, but there is some tutorial about firewater. If this tool doesn't work for you (like happen to me), you will have to pay $25 for Sunshine. From what I read, this method is guaranteed to get S-OFF.
With S-OFF, you will find some posts with updates of the firmware. So you don't have to go back to stock to update it.
To continue from where you stop, you have to follow this post. Like I said before, download any x.xx.401.x backup AND any x.xx.401.x stock recovery and follow the instructions of "How do i restore the stock nandroid backup" question (same post).
You don't flash the major stock backup zip file. You RESTORE it, on your custom recovery (TWRP or Philz) according from which recovery the backup was made (for example, if you download this one: 1.54.401.5 - TWRP Thanks to Fisha21. This backup was made on TWRP so you have to restore it on TWRP. But before restore, you need to flash the "boot.img or boot.emmc.win" file that is INSIDE this backup zip file. After that you make a full wipe in recovery and then RESTORE the major backup (remember, you don't restore the zip file, you have to unzip it on your phone like is said on the "How do i restore the stock nandroid backup" question of the post).
After all, you will flash the recovery of the same version that you download on the same post.
---------- Post added at 09:27 AM ---------- Previous post was at 09:20 AM ----------
You looked your firmware version, befere restore the 1.54.61.5 version? You have to check the CID AND the main version of your phone, like it said on the beggining of the post:
Take the main version number and CID and check if it exists in the collection below ! If it doesn't you can always make a request here.
Click to expand...
Click to collapse
I Flashed a file named boot.emmc.win from inside the unzipped backup. I moved the file to my adb_fastboot folder and flashed it this way: fastboot flash recovery boot.emmc.win
Then I had trouble gaining access to custom recovery (TWRP) so I tried flashing the custom recovery again. I got in! Made a full wipe, chose "install", twrp > BACKUPS > Serialnumber > Backup.zip. But it failed!!!!! It was missing a md5 file???
I'm starting to regret all this root-mess

One M8 won't OTA update on stock

I restored my M8 International Unlocked Dual SIM Version to stock through a nandroid backup and then flashed one of the recoveries I found online but my phone won't update through OTA. I then tried restoring different backups. Some of which worked and some didn't even boot.
I finally came to the conclusion that it was because of the HBOOT version and maybe the version-main.
I want to know:
1- Understand version-main.
2- How can I know which nandroid backup is right for me. (and if possible point me to the right ones for me).
I searched quite some time but couldn't turn up with a complete answer. Forgive me if I missed something.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__J15
(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: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

GeekOmar said:
1- Understand version-main.
2- How can I know which nandroid backup is right for me. (and if possible point me to the right ones for me).
[/CODE]
Click to expand...
Click to collapse
I don't own the dual SIM, and can't speak that specifically on it. But what I can say:
1) Main version is the firmware number. It won't change when you restore a nandroid.
2) You will want a nandroid that matches your firmware number. If you are trying to flash backups for the "regular" (single SIM) M8, these will never work on your phone. Dual SIM nandroids are probably pretty limited.

GeekOmar said:
....but my phone won't update through OTA.
Click to expand...
Click to collapse
What's the error ?
Is it stuck on red triangle ? If yes, press & hold volume up button and press power button once. This will get you to recovery and read what error that you have there.

redpoint73 said:
I don't own the dual SIM, and can't speak that specifically on it. But what I can say:
1) Main version is the firmware number. It won't change when you restore a nandroid.
2) You will want a nandroid that matches your firmware number. If you are trying to flash backups for the "regular" (single SIM) M8, these will never work on your phone. Dual SIM nandroids are probably pretty limited.
Click to expand...
Click to collapse
Thank you Redpoint,
I bricked my phone before, and was able to fix it using the backups and recovery from the below link and everything was fine, I was able to install two OTAs and get lollipop.
http://forum.xda-developers.com/htc-one-m8/help/rooted-m8-dual-sim-bricked-s-t2979774
But now, when I restore that backup and original recovery, then install any OTA update, the screen becomes black. I know the phone is working fine as I can hear the sound when pressing the volume key or when someone calls. But no screen! The link above is to a thread made by me and the only difference i can see between that time and now is the HBOOT version and the radio/baseband. This is driving me crazy!
ckpv5 said:
What's the error ?
Is it stuck on red triangle ? If yes, press & hold volume up button and press power button once. This will get you to recovery and read what error that you have there.
Click to expand...
Click to collapse
The screen just becomes black. Phone works fine as I can hear incoming calls.

Come on people, is it that hard! There must be something that can be done.
Sent from my HTC One_M8 dual sim using XDA Forums

GeekOmar said:
Come on people, is it that hard! There must be something that can be done.
Click to expand...
Click to collapse
This is sounding really rude. How about asking nicely?
Nobody here is getting paid for their time, or sitting at their computer 24 hours a day to help you. You need some patience.
Plus, the dual SIM version is not terribly common/popular, so getting the specific help and files needed may be a challenge. Folks here are helping as much as they can, when they can.
Its hard enough, that you can't figure it out, right?
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
GeekOmar said:
But now, when I restore that backup and original recovery, then install any OTA update, the screen becomes black.
Click to expand...
Click to collapse
What backup and what OTAs specifically? The statement is to vague for me to see what you did.
List the version of the backup (link to a link to a link doesn't help me) and what version OTAs did you try.
Where did you get the OTA files from (specific post, if applicable)?
GeekOmar said:
the only difference i can see between that time and now is the HBOOT version and the radio/baseband.
Click to expand...
Click to collapse
This means your firmware is different for before. This is not a minor thing, its a huge difference.

GeekOmar said:
The screen just becomes black. Phone works fine as I can hear incoming calls.
Click to expand...
Click to collapse
That's because you restored a very low version of backup when you have a high version firmware installed.
What I understand here, you restored 1.45.401.12 but your firmware is 4.30.401.15
When you restore a backup (when your device is S-On), the lowest version that may work on your device is 3.33.401.6 but not 1.45.401.12.
And the correct version to restore is 4.30.401.15
If you don't have this 4.30.401.15 backup and unable to find it for now, just to have a good running device, you can install custom ROM made for your device.
I believe this is a good one : http://llabtoofer.com/2015/05/08/htc-one-m8-dual-sim-maximushd-3-0-0/
(note : you should have made your own backup when you first fixed your previous problem)

redpoint73 said:
This is sounding really rude. How about asking nicely?
Nobody here is getting paid for their time, or sitting at their computer 24 hours a day to help you. You need some patience.
Plus, the dual SIM version is not terribly common/popular, so getting the specific help and files needed may be a challenge. Folks here are helping as much as they can, when they can.
Its hard enough, that you can't figure it out, right?
Click to expand...
Click to collapse
I didn't mean to sound rude. What I meant by my last post, was to encourage readers as I know it is a challenge and I wanted them to share their thoughts. I assure you that I AM grateful for your help otherwise I wouldn't thank you for your first post which suggested to restore a nandroid backup for a dual SIM which I already did.
Anyway, please accept my apologies for this misunderstanding.
What backup and what OTAs specifically? The statement is to vague for me to see what you did.
Click to expand...
Click to collapse
I restored the same backup that I used to fix my phone the first time. It is currently deleted but it said it was version 1.45.401.12. Which worked flawlessly and I was able to install OTA updates.
The update I'm trying to install currently is version: 3.33.401.6. for Android 4.4.4. It is an over the air update by the phone it self.
ckpv5 said:
That's because you restored a very low version of backup when you have a high version firmware installed.
What I understand here, you restored 1.45.401.12 but your firmware is 4.30.401.15
When you restore a backup (when your device is S-On), the lowest version that may work on your device is 3.33.401.6 but not 1.45.401.12.
And the correct version to restore is 4.30.401.15
If you don't have this 4.30.401.15 backup and unable to find it for now, just to have a good running device, you can install custom ROM made for your device.
I believe this is a good one : http://llabtoofer.com/2015/05/08/htc-one-m8-dual-sim-maximushd-3-0-0/
(note : you should have made your own backup when you first fixed your previous problem)
Click to expand...
Click to collapse
I'm keeping ROMs as a last option
How do you suggest I update my firmware?
Again, all are thanked for their valuable contributions.

This should help you : http://forum.xda-developers.com/htc-one-m8/help/m8-dugl-lollipop-upgrade-unlocking-t3098463

GeekOmar said:
Anyway, please accept my apologies for this misunderstanding.
Click to expand...
Click to collapse
No worries, your apology is accepted. And I gave you your first "Thanks" too!
I look at most all new posts in this section, and respond if I have something to contribute when I have the time (and ckpv5 looks to operate very much the same way). So the lack or response was due to me not being online, and otherwise unable to spend the time on XDA (and nagging won't change that). Therefore, "bumping" a thread to the top is usually not necessary. Or if you choose to do so, try to pose it as a polite appeal for help (in the form of a question, and using the word "please" can work wonders).
The way you posted it, sounded more like you were making a demand or giving orders.
GeekOmar said:
I restored the same backup that I used to fix my phone the first time. It is currently deleted but it said it was version 1.45.401.12. Which worked flawlessly and I was able to install OTA updates.
The update I'm trying to install currently is version: 3.33.401.6. for Android 4.4.4. It is an over the air update by the phone it self.
Click to expand...
Click to collapse
Did you install the 2.xx.401 OTA before trying 3.33.401? Because this is mandatory (OTAs need to be installed in sequence, and you can't skip any).
GeekOmar said:
How do you suggest I update my firmware?
Click to expand...
Click to collapse
Your main version, hboot, and radio numbers given in your top post all indicate you are on the current Lollipop firmware.
The issue is getting a ROM on the phone that matches the firmware, as ckpv5 has given you suggestions on how to do (4.30.401 nandroid is what you want, if you can find it).
You may be confusing "firmware" with "ROM", as they are not the same thing.

He can use one version lower 3.33.401.6 too.
And he can find that 3.33.401.6 backup in the link that I posted above.

Did you install the 2.xx.401 OTA before trying 3.33.401? Because this is mandatory (OTAs need to be installed in sequence, and you can't skip any).
Click to expand...
Click to collapse
I update as the phone asks. I abide by what it is asking.
Your main version, hboot, and radio numbers given in your top post all indicate you are on the current Lollipop firmware.
The issue is getting a ROM on the phone that matches the firmware, as ckpv5 has given you suggestions on how to do (4.30.401 nandroid is what you want, if you can find it).
You may be confusing "firmware" with "ROM", as they are not the same thing.
Click to expand...
Click to collapse
What I understand now, is that I got the firmware of Lollipop but I am still running Kitkat. Couldn't find any 4.30.401 nandroid.
ckpv5 said:
This should help you : http://forum.xda-developers.com/htc-one-m8/help/m8-dugl-lollipop-upgrade-unlocking-t3098463
Click to expand...
Click to collapse
I tried, that method. Flashed the rom, and it asked me to install Lollipop, which is good. But when flash stock recovery lock the bootloader. It boots straight to fastboot!

GeekOmar said:
I tried, that method. Flashed the rom, and it asked me to install Lollipop, which is good. But when flash stock recovery lock the bootloader. It boots straight to fastboot!
Click to expand...
Click to collapse
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.

ckpv5 said:
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.
Click to expand...
Click to collapse
I flashed the stock recovery so I locked the bootloader to install the OTA. Don't you need a locked boot loader to install an OTA?
Man, don't make me feel stupid more than I do now. I'll get a Nokia and then kill myself. [emoji30] [emoji379]
I'll try one of your recoveries as soon as I'm home.
ckpv5 said:
Why relock bootloader ? It's not needed. Unlock it again as you need to flash correct recovery.
Boot back to fastboot usually happen when you flash wrong recovery especially a recovery meant for other device.
From where you get the recovery ? You only mentioned somewhere on the net.
Use 3.33.401.6 recovery or 4.30.401.15 recovery. Either one should work. You can get them in link in my signature.
Click to expand...
Click to collapse
Sent from my TF700T using Tapatalk

GeekOmar said:
I flashed the stock recovery so I locked the bootloader to install the OTA. Don't you need a locked boot loader to install an OTA?
Click to expand...
Click to collapse
No .. no need a relocked bootloader for OTA. (doesn't matter your device is S-On or S-Off)
Relocked bootloader only needed when your device is S-On and you want to :
1. Install a HTC RUU
2. Install a HTC signed firmware

ckpv5 said:
No .. no need a relocked bootloader for OTA. (doesn't matter your device is S-On or S-Off)
Relocked bootloader only needed when your device is S-On and you want to :
1. Install a HTC RUU
2. Install a HTC signed firmware
Click to expand...
Click to collapse
Understood.
Ok, so I flashed that stock rom you mentioned earlier and and one of your stock recoveries and Voila! Everything is perfect, except WiFi. When I turn on WiFi, it says "Turning on.." and stays like this indefinitely. Any idea?

Well, I have tried everything to fix the WiFi problem to no avail. Finally I got fed up and decided to use the room you provided. Thanks ckpv for your help. I appreciate it.
Sent from my TF700T using Tapatalk

GeekOmar said:
Well, I have tried everything to fix the WiFi problem to no avail. Finally I got fed up and decided to use the room you provided. Thanks ckpv for your help. I appreciate it.
Sent from my TF700T using Tapatalk
Click to expand...
Click to collapse
I don't have your device version so I can't confirm anything why the wifi won't work on your device.
Anyway .. when you want to try again - see this : http://forum.xda-developers.com/showpost.php?p=56681264&postcount=113
a nandroid backup that you can restore and install the stock recovery and try to OTA again.

ckpv5 said:
I don't have your device version so I can't confirm anything why the wifi won't work on your device.
Anyway .. when you want to try again - see this : http://forum.xda-developers.com/showpost.php?p=56681264&postcount=113
a nandroid backup that you can restore and install the stock recovery and try to OTA again.
Click to expand...
Click to collapse
I'll give it a try.
Thank you for your help, you've done enough.
Sent from my HTC One_M8 dual sim using Tapatalk

A problem with my m8? I will not start

Hy guys, i hope someone can help me with this one.
I try the other days to root my phone, and all got smoth, then i update my firmware because WiFi will not work and i read somewhere that will be problem. And i update my firmware too, all was good, everything instaled sucefull but when i try to open it stay blocked on main screen. How to make more clear than that? The phone freeze where the HTC logo appear, i can't do anything more than that.
Some info i can get from fastboot:
*** Software status: Modified ***
*** RELOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.21.213311491.A04G
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-3.11.1700.5
eMMC- boot 2048MB
I think when i installed the firmware the proces delete everything on my phone, i dont have recovery or anything else. Can someone help please to restore to stock? Or at least to a soft that my phone to work?
Thanks! (And sorry for my bad english, not my first language)

pant3ras said:
Hy guys, i hope someone can help me with this one.
I try the other days to root my phone, and all got smoth, then i update my firmware because WiFi will not work and i read somewhere that will be problem. And i update my firmware too, all was good, everything instaled sucefull but when i try to open it stay blocked on main screen. How to make more clear than that? The phone freeze where the HTC logo appear, i can't do anything more than that.
Some info i can get from fastboot:
*** Software status: Modified ***
*** RELOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.21.213311491.A04G
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-3.11.1700.5
eMMC- boot 2048MB
I think when i installed the firmware the proces delete everything on my phone, i dont have recovery or anything else. Can someone help please to restore to stock? Or at least to a soft that my phone to work?
Thanks! (And sorry for my bad english, not my first language)
Click to expand...
Click to collapse
You still have KitKat firmware, as shown by your OS version. You CANNOT flash a modified firmware package while S-On. You need to either run a signed RUU, or go back to stock and use HTC's/your carrier's OTA updates.

Do you have a stock ruu? or maybe how to s-off? because i cant find anywhere firewater.
Maybe this will help with something:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s

So can anybody can help me? Please i am stuck on this. And when i want to flash the RUU from AT&T i still get the error 155: Unknow Error. Can someone help me? Please.

What firmware did you try to flash? It looks like it was GPE firmware.
Is your bootloader screen black or white now?

My bootloader screen it's black, it's that important?...
And the firmware was download from HDRevolution website.

pant3ras said:
My bootloader screen it's black, it's that important?...
Click to expand...
Click to collapse
Yup, that's very important. Black hboot screen is the GPE version (and white is Sense version hboot). You at least partially flashed a GPE firmware. This isn't supposed to happen with s-on (firmware for other versions should be blocked). But I do remember a while back, a few folks having the same issue; where a GPE firmware or RUU partially flashed (with s-on) and caused some problems.
pant3ras said:
And the firmware was download from HDRevolution website.
Click to expand...
Click to collapse
That doesn't help. Quite a few firmwares are posted there. What specific number firmware did you flash? Did you flash the firmware number (3.11.1700.5) shown OS number on your hboot screen?
---------- Post added at 12:03 PM ---------- Previous post was at 12:03 PM ----------
pant3ras said:
And when i want to flash the RUU from AT&T i still get the error 155: Unknow Error.
Click to expand...
Click to collapse
What RUU (file name) are you trying to flash?

redpoint73 said:
That doesn't help. Quite a few firmwares are posted there. What specific number firmware did you flash? Did you flash the firmware number (3.11.1700.5) shown OS number on your hboot screen?
Click to expand...
Click to collapse
The firmware i flash was 3.11.1700.5 yes.
redpoint73 said:
What RUU (file name) are you trying to flash?
Click to expand...
Click to collapse
That from the official page, this one:
"RUU_M8_UL_L50_SENSE60_ATT[email protected]_40.45.C33065.00_F_release_446225_signed_2"
And also i was trying with this one:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 I dont know where exactly i find this one, but this one like the one above give me the same error, now and before trying rooting my htc.

pant3ras said:
The firmware i flash was 3.11.1700.5 yes.
Click to expand...
Click to collapse
I don't know why you flashed this. Not only is it not current firmware (Kitkat, as another noted before), but its not even for your version (its GPE version firmware, as I mentioned).
pant3ras said:
That from the official page, this one:
"RUU_M8_UL_L50_SENSE60_ATT[email protected]_40.45.C33065.00_F_release_446225_signed_2"
Click to expand...
Click to collapse
That is the proper RUU for the AT&T version; and your bootloader is relocked, as it should be for RUU.
So I think the problem is the GPE firmware you flashed before.
Try flashing the proper firmware first, then RUU again, and hopefully that will work.
I can't find the 4.28.502.2 firmware. But 4.28.502.1 firmware is posted on the following. Use the Full stock firmware. Hopefully, this is close enough to 4.28.502.2 to work.
EDIT: Forgot to post the firmware link: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml
pant3ras said:
And also i was trying with this one:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 I dont know where exactly i find this one, but this one like the one above give me the same error, now and before trying rooting my htc.
Click to expand...
Click to collapse
That RUU will not work, anyway. Its for the Developer Edition, so the only way to run it would be to change your CID (s-off required, and working OS is needed to s-off).
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
pant3ras said:
or maybe how to s-off? because i cant find anywhere firewater.
Click to expand...
Click to collapse
Firewater was discontinued by its devs in December 2014. Since it has an online component (needed to connect to servers), it won't work even if you find the firewater binary.
Sunshine is the only current working s-off method, and as I mentioned, it requires a working OS to work.

redpoint73 said:
I don't know why you flashed this. Not only is it not current firmware (Kitkat, as another noted before), but its not even for your version (its GPE version firmware, as I mentioned).
Click to expand...
Click to collapse
I flash that firmware because have my cidnum and modelid, and i read that the firmware need to have the same cidnum and modelid.
redpoint73 said:
I can't find the 4.28.502.2 firmware. But 4.28.502.1 firmware is posted on the following. Use the Full stock firmware. Hopefully, this is close enough to 4.28.502.2 to work
Click to expand...
Click to collapse
Where can i find this firmware?
And i didn't know that firewater doesnt work anymore, and sunshine i think you have to pay 25$ per month, right?

pant3ras said:
I flash that firmware because have my cidnum and modelid, and i read that the firmware need to have the same cidnum and modelid.
Click to expand...
Click to collapse
Yes, firmware needs to have the same CID and MID. But the 3.11.1700.5 firmware doesn't go with your CID and MID (CWS__001 and 0P6B12000)
"1700" firmwares (such as 3.11.1700.5) are for the Google Play Edition (GPE) with CID of GOOGL001 and MID of 0P6B17000.
Proper firmwares for your AT&T CID and MID will have the number "502" in the position x.xx.502.x
pant3ras said:
Where can i find this firmware?
Click to expand...
Click to collapse
Sorry, forgot to post the link. I had the page open, and everything: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml
pant3ras said:
And i didn't know that firewater doesnt work anymore, and sunshine i think you have to pay 25$ per month, right?
Click to expand...
Click to collapse
That's right. And as I already stated, sunshine requires a working OS, which you don't have. And since getting the OS working again seems to be the main reason you want to get s-off, you see its quite pointless.

redpoint73 said:
Sorry, forgot to post the link. I had the page open, and everything: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml.
Click to expand...
Click to collapse
No problem And to flash this firmware i can do it like this:
f you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Click to expand...
Click to collapse

pant3ras said:
No problem And to flash this firmware i can do it like this:
Click to expand...
Click to collapse
Yes, exactly.

redpoint73 said:
Yes, exactly.
Click to expand...
Click to collapse
I get this error when i try to flash the firmware:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1826418688 bytes
sending 'zip' (57484 KB)...
OKAY [ 2.570s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.611s
Click to expand...
Click to collapse

pant3ras said:
I get this error when i try to flash the firmware:
Click to expand...
Click to collapse
You used the "full stock" firmware 4.28.502.1, correct? Not the "Combined, No wipe" one?
You can also try the 3.42.502.1 firmware.

redpoint73 said:
You used the "full stock" firmware 4.28.502.1, correct? Not the "Combined, No wipe" one?
You can also try the 3.42.502.1 firmware.
Click to expand...
Click to collapse
Yes, i use the full stock firmware. Now i will try with 3.42.502.1
Later edit: I get the same error when i try with the 3.42.502.1 stock

pant3ras said:
Yes, i use the full stock firmware. Now i will try with 3.42.502.1
Later edit: I get the same error when i try with the 3.42.502.1 stock
Click to expand...
Click to collapse
Those might be unsigned firmwares, but I thought they were signed.
I think your options at this point:
1) Find signed firmwares of the versions I recommended.
2) Unlock the bootloader again, flash TWRP again, then flash a 3.xx based custom or stock ROM (which will have working WiFi). Then s-off by sunshine so you can fix the firmware (will allow an unsigned firmware to be flashed).
Another thing to note, when you flashed the GPE firmware, it reverted the recovery back to stock recovery. Which is why you no longer have custom recovery.

redpoint73 said:
Those might be unsigned firmwares, but I thought they were signed.
I think your options at this point:
1) Find signed firmwares of the versions I recommended.
2) Unlock the bootloader again, flash TWRP again, then flash a 3.xx based custom or stock ROM (which will have working WiFi). Then s-off by sunshine so you can fix the firmware (will allow an unsigned firmware to be flashed).
Another thing to note, when you flashed the GPE firmware, it reverted the recovery back to stock recovery. Which is why you no longer have custom recovery.
Click to expand...
Click to collapse
And how i can unlock the bootloader again? and flash the TWRP?

pant3ras said:
And how i can unlock the bootloader again? and flash the TWRP?
Click to expand...
Click to collapse
Unlock the bootloader by HTCDev.com. Then flash TWRP with fastboot.

redpoint73 said:
Unlock the bootloader by HTCDev.com. Then flash TWRP with fastboot.
Click to expand...
Click to collapse
Ok, i succed to instal the TWRP and i unlock the phone, but i have no ideea what rom to instal. Can you help me with that please? I'm scare i will broke my phone again if i install something on my own again )

Cant update to Official Marshmallow with Custom Kernel

Hey Guys,
I just bought a used HTC One M8 and love the phone. Unfortunately the phone was rooted and ran with a CM Nightly, the camera didnt work, the flash neither and so on. Im no big fan of custom Firmware if the stock experience has all the features I need in the phone. Coming from Android 4.2, Marshmallow is certainly enough.
So I grabbed a Stock 4.2 Backup and flashed it. Then I went through all the OTA´s. I had to flash the kernel because it was still custom, but I couldnt find the stock one, so I got ElementalX. It all went alright until I got to Lollipop (and I dont like Lollipop at all, the version before was much more pleasing to me).
I dont get the OTA if I search for it and after asking google I found that you have to be Bootloader locked to get the OTA. Does anyone know why HTC decided to do it with Marshmallow but no other OTA before? Anyway i locked my bootloader, but then it didnt boot. It always booted into the bootloader. After a quick search it seems that it happens when you are not full stock (i guess because of my kernel?).
I then tried to flash the Marshmallow OTA over recovery, but it said I got an error, because the update expects another Version.
What are my options now? Ideally I want stock Marshmallow, Sense or Play Edition I dont care, but since my phone is Sense I think its way easier. I dont want root, because Pokemon Go blocks it (y i know the workarounds, but they could ban people for that or make the workarounds not work) and because I want my Camera and Speakers to work perfectly.
Has anyone the stock Lollipop Kernel for me to flash so I can lock the bootloader again? Is there anything I did wrong? Please guys, I need your help, because I really really enjoy this phone coming from a Galaxy Nexus!
Here are Screenshots of the System Info:
vaZeEK2.png
ZyUB9yp.png
These are the Imgur Codes, because I cant post external links having less than 10 Posts
Thanks for any Reply! I really appreciate this community since I rooted my Nexus

My responses below in red font:
wollen said:
So I grabbed a Stock 4.2 Backup and flashed it. Then I went through all the OTA´s. I had to flash the kernel because it was still custom, but I couldnt find the stock one, so I got ElementalX.
This doesn't make much sense. The stock backup you restored would have (should have) included the stock kernel. And the subsequent updates would have also updated (replaced) the kernel. I don't see how it could have still been a custom kernel after restoring the backup, and the OTA updates. I think you are mistaken on this.
I dont get the OTA if I search for it and after asking google I found that you have to be Bootloader locked to get the OTA.
This is false, and wherever you got this info from, its incorrect. MM OTA will install fine with an unlocked bootloader (but probably not with a custom kernel). You only need to relock the bootloader to flash RUU, which is a very different animal.But that may be the source of confusion, as folks often mix up the requirements for OTA vs. RUU.
Anyway i locked my bootloader, but then it didnt boot. It always booted into the bootloader. After a quick search it seems that it happens when you are not full stock (i guess because of my kernel?). Not booting after relocking the bootloader has nothing to do with not being stock, or having custom kernel. No boot after relocking is normal, expected, and happens even if fully stock. Relocking expects the RUU to be run.
I then tried to flash the Marshmallow OTA over recovery, but it said I got an error, because the update expects another Version.
Not sure, but I would guess the custom kernel is the reason for the OTA failure. I would think the custom kernel would trip the "Modified Software" flag.
What are my options now?
Click to expand...
Click to collapse
If you are currently bootloader locked, and the intent is to go full MM stock, you may just be best off running RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) if you need help finding the right RUU.
Normally, I would warn that the RUU wipes all the data from the phone; but I think you already did that when you relocked the bootloader.
There are other paths forward, such as unlocking the bootloader again, and flashing stock TWRP backup and stock recovery. But it would probably be more steps to end up at the same place.
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
I now see from your screenshots, that you seem to have the O2 version of the M8. I don't know if there is an RUU for that version. If not, you may indeed need to unlock the bootloader again (either try the same unlock bin code, or get a new one via HTCDev.com), flash TWRP back onto the phone, then restore the stock TWRP backup 4.20.206.2 from here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
After that, restore the stock recovery 4.20.206.2, and you should be able to OTA to MM.
But again, I'd like to see the getvar output to make sure this is the best way forward (the data presented in the phone settings is not always accurate, depending on what you flashed).

When I flashed the Stock ROM, the WiFi stopped working. I searched in the Internet and someone said that the kernel could be wrong. I was very surprised because i also thought that the ROM overrides the kernel. But when i looked in phone settings there was a custom kernel. When I flashed the ElementalX the WiFi worked again. When I upgraded my way up to Lollipop I had to flash the ElementalX Kernal several times because WiFi almost always stopped working after an OTA.
Here is my getvar Output:
Why do I have to delete Serial and IMEI, because of hacking attempts?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___102
(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: d9e7383b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I hope you are sure about your thesis, because OTAing from 4 to 5 took several hours
But even when its wrong thank you so much for help so far!!

Again, my comments in red font:
wollen said:
When I flashed the Stock ROM, the WiFi stopped working. I searched in the Internet and someone said that the kernel could be wrong. I was very surprised because i also thought that the ROM overrides the kernel. But when i looked in phone settings there was a custom kernel.
When you say stock ROM, do you mean a stock TWRP backup, like the ones in the link I provided in my last post? If its a TWRP backup you restored, its possible you forgot to restore boot.img contained in the backup file. In the Restore section of TWRP, you need to select System and Boot.img when restoring a stock TWRP backup. In that case, its indeed possible that whatever kernel was there before, was not over-written by the stock kernel.
When I flashed the ElementalX the WiFi worked again. When I upgraded my way up to Lollipop I had to flash the ElementalX Kernal several times because WiFi almost always stopped working after an OTA.
I'm not sure why that happened. You shouldn't have to flash a custom kernel after an OTA update. Maybe having a custom kernel on the phone when trying to OTA, mucked things up somehow.
Here is my getvar Output:
Why do I have to delete Serial and IMEI, because of hacking attempts? Something like that. Those numbers are personal info, and can be used by others for nefarious purposes.
I hope you are sure about your thesis, because OTAing from 4 to 5 took several hours
I don't see how me being right or not has anything to do with the OTA taking a long time.
Click to expand...
Click to collapse
---------- Post added at 03:07 PM ---------- Previous post was at 03:02 PM ----------
Your getvar data confirms what I stated before. I don't think the O2 version has RUU, so I suggest trying the following:
redpoint73 said:
unlock the bootloader again (either try the same unlock bin code, or get a new one via HTCDev.com), flash TWRP (2.8.7.0) back onto the phone, then restore the stock TWRP backup 4.20.206.2 from here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 Be sure to restore both System and boot.img this time (its in the instructions)!
After that, restore the stock recovery 4.20.206.2, and you should be able to OTA to MM.
Click to expand...
Click to collapse

So I should now flash the provided TWRP Backup using the Boot.img and then all should work? So the Boot.img is no extra step just the normal way to do it? The first time I did all thing with the One M8 All in One Tool Kit.
And yeah Sorry about that thing with taking a long time, I think it was my way to get the steam off of having to go through all this today ^^.
EDIT: Just saw your edit, will do exactly that and tell if it has worked
Thank you so much for your help so far!

redpoint73 said:
I don't think the O2 version has RUU...
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24369303960686241

Or another possible method, is:
1) Keep the bootloader locked for now.
2) Flash firmware 6.13.206.5 as posted here. Instruction on how to flash on the bottom of the thread.
3) Unlock the bootloader again
4) Flash TWRP 3.0.2
5) Restore the backup 6.13.206.5 from here. Again, make sure you restore both system and boot partitions.
6) Reboot, and you should be on MM. No need to flash stock recovery, unless HTC releases any more OTA (which is unlikely).

My Bootloader is unlocked because I couldnt start the phone, so I had to unlock it. I just Flashed TWRP 2.8.7.0., but now there seems to be a RUU. Is it better to use the RUU and if yes, what do I do with it? Just flash it with TWRP and then proceed to OTA?

ckpv5 said:
https://www.androidfilehost.com/?fid=24369303960686241
Click to expand...
Click to collapse
Nice. There's the RUU for 4.20.206.2
Keep the bootloader locked and run this. Easiest way (if you have an SD card) is:
1) Rename to 0P6BIMG.zip
2) Put the file on SD card.
3) Insert card into phone
4) Reboot into bootloader, and it should run the RUU automatically
After that, reboot and see if the OTA update comes through.
---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------
wollen said:
My Bootloader is unlocked because I couldnt start the phone, so I had to unlock it. I just Flashed TWRP 2.8.7.0., but now there seems to be a RUU. Is it better to use the RUU and if yes, what do I do with it? Just flash it with TWRP and then proceed to OTA?
Click to expand...
Click to collapse
I guess whether you restore a stock TWRP backup, or RUU is a tossup at this point. You would need to relock the bootloader to RUU. But it might be less daunting, if the instruction to restore a TWRP backup looks confusing to you.
But you run the RUU using the method I stated above (or if you don't have an SD card, le me know and I can tell you the fastboot method). You can not flash the RUU with TWRP.

Ok I will relock and use the RUU!
I have an SD Card but no Reader, so my only way is to have it inside the phone to get files on there. Is it a problem?
I would now:
- Put the Zip on the SD Card
- Take the SD Card out
- Relock the Bootloader
- Insert the SD Card
- Let the magic happen
Is it safe and right for me to do it that way?

wollen said:
So I should now flash the provided TWRP Backup using the Boot.img and then all should work? So the Boot.img is no extra step just the normal way to do it? The first time I did all thing with the One M8 All in One Tool Kit.
Click to expand...
Click to collapse
If you restore a TWRP backup, you check the boxes for the partitions you want to restore. You need to check both system (ROM) and boot (kernel).
However, if you flashed something with the toolkit, I don't think it was a TWRP backup, but probably a flashable ROM zip. In that case, the kernel flashes automatically.
Flashing a ROM is different from restoring a TWRP backup.
Also, I would advise against using the toolkit. It hasn't been updated in over a 2 years. It causes more problems than it solves; and everything it does, you can be done yourself manually. The toolkit is also the reason your main version is blank in getvar and on the bootloader screen (OS number). Toolkit installs a very old, obsolete version or TWRP which wipes out the OS (firmware) number. It should say 4.20.206.2.
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
wollen said:
Ok I will relock and use the RUU!
I have an SD Card but no Reader, so my only way is to have it inside the phone to get files on there. Is it a problem?
Click to expand...
Click to collapse
That's fine. My understanding, the phone is currently working. So you can download the RUU direct to it, or use it to transfer the RUU to the SD card from your computer.

wollen said:
Ok I will relock and use the RUU!
I have an SD Card but no Reader, so my only way is to have it inside the phone to get files on there. Is it a problem?
I would now:
- Put the Zip on the SD Card
- Take the SD Card out
- Relock the Bootloader
- Insert the SD Card
- Let the magic happen
Is it safe and right for me to do it that way?
Click to expand...
Click to collapse
Adding a post, to bump. This is a test.

wollen said:
I would now:
- Put the Zip on the SD Card
- Take the SD Card out
- Relock the Bootloader
- Insert the SD Card
- Let the magic happen
Is it safe and right for me to do it that way?
Click to expand...
Click to collapse
You should be able to just leave the SD card in the phone.
Basically, any time the phone is booted into bootloader, and it sees a file on the SD card named 0P6BIMG.zip, than it will try to install it.
But I suppose it doesn't hurt to take the card out, on the off-chance that relocking the bootloader wipes the SD card (its not supposed to, but hey you never know).

Sigh.. Im slowly losing hope..
I tried to copy the RUU to my SD card, but Windows gives me an error all the time. Even when I try to copy it to the Phones Storage. Images and the old ROM are easy to copy, maybe it´s because of its size? The RUU is 1.6gb and the old rom 1.2gb for example.
The Error message is as follows, translated by me from german:
Element can not be copied.
The device does not respond or the connection has been disconnected.
I tried Google Search but did not find anything, because the Card works with alle other files. Is there a way to apply the RUU from the PC?

So I just did the method over TWRP and it worked. Thanks so much for helping me through this, I would have never made it with out you!

How to Unroot my HTC One M8?

Hello everyone, I wanted to unroot my phone, I have read other posts on this topic but I am still confused. The getvar results of my phone are as follows:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
I bought this phone brand new locked to Rogers. I didn't want to mess anything up by downloading the wrong stock recovery. Thanks!

How is it rooted? SuperSu? Magisk?

maultasche said:
How is it rooted? SuperSu? Magisk?
Click to expand...
Click to collapse
Good question.
And also to the OP, what is the exact eason for unrooting?

maultasche said:
How is it rooted? SuperSu? Magisk?
Click to expand...
Click to collapse
It is rooted using SuperSu, and the reason for unrooting is that I have been having a few problems with the phone and want to see if unrooting will help, but it is probably just something wrong with my power button. Sometimes when I press it, the phone thinks I long pressed the power button.

SuperSu has an option in settings to unsu. There might also be a flashable zip somewhere in the Su-thread to remove SuperSu completely.
But your issue sounds like a hardware issue. I don't think unrooting will help.

maultasche said:
SuperSu has an option in settings to unsu. There might also be a flashable zip somewhere in the Su-thread to remove SuperSu completely.
But your issue sounds like a hardware issue. I don't think unrooting will help.
Click to expand...
Click to collapse
Ok I thought so but I feel like I might as well try at this point, sorta wanted to unroot it anyways. So If I got into SuperSu and click on FUll Unroot, that should be all I have to do? Won't have do anything else like follow this guide:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Because that was the most confusing part. Thanks

gurkang10 said:
Ok I thought so but I feel like I might as well try at this point, sorta wanted to unroot it anyways. So If I got into SuperSu and click on FUll Unroot, that should be all I have to do? Won't have do anything else like follow this guide:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Because that was the most confusing part. Thanks
Click to expand...
Click to collapse
That guide is for people going back on stock via TWRP if they don't have a backup at hand or want to update stock ROM and/or firmware.
It should be enough to use the unroot option in SuperSu.

maultasche said:
That guide is for people going back on stock via TWRP if they don't have a backup at hand or want to update stock ROM and/or firmware.
It should be enough to use the unroot option in SuperSu.
Click to expand...
Click to collapse
Thank you so much for your help!

maultasche said:
That guide is for people going back on stock via TWRP if they don't have a backup at hand or want to update stock ROM and/or firmware.
Click to expand...
Click to collapse
That being said, the OP is still on Lollipop firmware (and presumably stock Lollipop ROM) and it could use an update to Marshmallow (the latest/last update provided by HTC). That can be done either by restoring stock TWRP backup that was linked, then OTA update. Or will RUU.
RUU would be a complete factory re-image (although it also wipes the phone). This might eliminate the possibility that the power button issue is being caused by a software problem. Although it does sound like a hardware problem to me. I haven't heard of any similar issue being cause by software.

Ok I have one more question, I am using Android Revolution HD on my phone, do I have to do anything to get rid of that or will using the unroot option in SuperSu still be enough

redpoint73 said:
That being said, the OP is still on Lollipop firmware (and presumably stock Lollipop ROM) and it could use an update to Marshmallow (the latest/last update provided by HTC). That can be done either by restoring stock TWRP backup that was linked, then OTA update. Or will RUU.
RUU would be a complete factory re-image (although it also wipes the phone). This might eliminate the possibility that the power button issue is being caused by a software problem. Although it does sound like a hardware problem to me. I haven't heard of any similar issue being cause by software.
Click to expand...
Click to collapse
So at this point I have already lost root access by doing what the other poster suggested. If I wanted to do this would I still be able to?

gurkang10 said:
So at this point I have already lost root access by doing what the other poster suggested. If I wanted to do this would I still be able to?
Click to expand...
Click to collapse
Root isn't required to do either of the things I mentioned, no. I mentioned two different approaches:
a) Restore stock TWRP backup (then OTA update to Marshmallow): Does not require root, but requires having TWRP installed, which you should still have after unrooting.
b) RUU: this is an official HTC tool, does not require root. Just run the RUU
Method "b" is probably the more straightforward method, but would wipe all data from the phone.

redpoint73 said:
Root isn't required to do either of the things I mentioned, no. I mentioned two different approaches:
a) Restore stock TWRP backup (then OTA update to Marshmallow): Does not require root, but requires having TWRP installed, which you should still have after unrooting.
b) RUU: this is an official HTC tool, does not require root. Just run the RUU
Method "b" is probably the more straightforward method, but would wipe all data from the phone.
Click to expand...
Click to collapse
I ended up going with method "a" but when I get to flashing the stock recovery it gives me this message :
D:\platform-tools>fastboot flash recovery 4.20.631.2_recovery.img
target reported max download size of 1826418688 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.482s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.498s

gurkang10 said:
I ended up going with method "a" but when I get to flashing the stock recovery it gives me this message :
D:\platform-tools>fastboot flash recovery 4.20.631.2_recovery.img
target reported max download size of 1826418688 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.482s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.498s
Click to expand...
Click to collapse
First of all, you did all the steps up to this point? Because flashing the stock recovery is step #11 of the instructions.
Second, why did you choose 4.20.631.2? Based on the info in your top post, the current version is 4.16.401.10
So you want to restore the stock TWRP backup with that same number (4.16.401.10) and the stock recovery 4.16.401.10

redpoint73 said:
First of all, you did all the steps up to this point? Because flashing the stock recovery is step #11 of the instructions.
Second, why did you choose 4.20.631.2? Based on the info in your top post, the current version is 4.16.401.10
So you want to restore the stock TWRP backup with that same number (4.16.401.10) and the stock recovery 4.16.401.10
Click to expand...
Click to collapse
Yes I did all the steps to that point. And the reason I chose 4.20.631.2 is that this was the only one available for my original CID, which is rogers in Canada

gurkang10 said:
Yes I did all the steps to that point. And the reason I chose 4.20.631.2 is that this was the only one available for my original CID, which is rogers in Canada
Click to expand...
Click to collapse
Your original CID is irrelevant. It's gone and replaced with SuperCID 11111111. It still has the Model ID (MID) for Rogers, but I believe that will be bypassed by SuperCID (and therefore MID won't matter) when you try to install the Marshmallow update. At least that is what happens most of the time.
Restoring the 4.20.631.2 backup and corresponding stock recovery, I don't think will work. The OTA update will detect your current firmware version is 4.16.401.10, which conflicts the software and recovery versions (4.20.631.2), and the update will fail.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
gurkang10 said:
writing 'recovery'...
FAILED (remote: not allowed)
Click to expand...
Click to collapse
On the bootloader screen on the phone, does it say LOCKED, RELOCKED, or UNLOCKED near the top of the screen?

redpoint73 said:
Your original CID is irrelevant. It's gone and replaced with SuperCID 11111111. It still has the Model ID (MID) for Rogers, but I believe that will be bypassed by SuperCID (and therefore MID won't matter) when you try to install the Marshmallow update. At least that is what happens most of the time.
Restoring the 4.20.631.2 backup and corresponding stock recovery, I don't think will work. The OTA update will detect your current firmware version is 4.16.401.10, which conflicts the software and recovery versions (4.20.631.2), and the update will fail.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
On the bootloader screen on the phone, does it say LOCKED, RELOCKED, or UNLOCKED near the top of the screen?
Click to expand...
Click to collapse
It let me restore the backup with no problem.
It says locked

Ok I got it to work, just needed to unlock it again, so I downloaded SuperSu, unclocked the device, then flashed the recovery

redpoint73 said:
Your original CID is irrelevant. It's gone and replaced with SuperCID 11111111. It still has the Model ID (MID) for Rogers, but I believe that will be bypassed by SuperCID (and therefore MID won't matter) when you try to install the Marshmallow update. At least that is what happens most of the time.
Restoring the 4.20.631.2 backup and corresponding stock recovery, I don't think will work. The OTA update will detect your current firmware version is 4.16.401.10, which conflicts the software and recovery versions (4.20.631.2), and the update will fail.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
On the bootloader screen on the phone, does it say LOCKED, RELOCKED, or UNLOCKED near the top of the screen?
Click to expand...
Click to collapse
I am now going to download the 4.16.401.10 stock backup , didn't try updating my device with the other backup. So now I am going to use the backup, flash the recovery, then lock the device and lastly unroot my phone. Hopefully all goes to plan, thanks for your help

Ok so the problem I have with using the 4.16.401.10 stock backup is that I don't get LTE data now, just 4G even though my access points are correct.