Develop Bugs

[Q] Nandroid back up of TMOB 101 version 4.28.707.10?

hi fellows as the title says ..dose anyone had an nandroid back or stock rom for this version i serched around the internet and i find no usefull info about this version 4.28.707.10 or this cid T-MOB 101...i brought this phone in china and now i dont know which version can fit and make me revert back to stock so i can update it to JB ...so if anyone has any info on it or you have any links to that perticular download please post it here so i can get it ...thanks in advance

Nani2000 said:
hi fellows as the title says ..dose anyone had an nandroid back or stock rom for this version i serched around the internet and i find no usefull info about this version 4.28.707.10 or this cid T-MOB 101...i brought this phone in china and now i dont know which version can fit and make me revert back to stock so i can update it to JB ...so if anyone has any info on it or you have any links to that perticular download please post it here so i can get it ...thanks in advance
Click to expand...
Click to collapse
look right here, http://forum.xda-developers.com/showthread.php?t=1975140 , there is a 2.17 version for that CID :good:

Can i still flash the rom with different version and have same cid no?
matt95 said:
look right here, http://forum.xda-developers.com/showthread.php?t=1975140 , there is a 2.17 version for that CID :good:
Click to expand...
Click to collapse
thanks for the reply man its a great idea for keeping everything in one place but my problem is my cid is T-MOB 101 and version is **.**.707**(4.28.707.10) and the version there is **.**.111.** so the question is can i still flash that nandroid ?? because i see in lots of post that cid and the version should match to get back to stock isn't that right ??

Nani2000 said:
thanks for the reply man its a great idea for keeping everything in one place but my problem is my cid is T-MOB 101 and version is **.**.707**(4.28.707.10) and the version there is **.**.111.** so the question is can i still flash that nandroid ?? because i see in lots of post that cid and the version should match to get back to stock isn't that right ??
Click to expand...
Click to collapse
you only need to match the CID, that nand should work on your phone, you need to match the RUU and not the nand what's your HBOOT version actually?

My HBOOT
matt95 said:
you only need to match the CID, that nand should work on your phone, you need to match the RUU and not the nand what's your HBOOT version actually?
Click to expand...
Click to collapse
My HBOOT is 0.94.0000 which is very old one i guess as now there are many new one i just want to go back to stock but i can update my h boot and then the install JB from there ..

Nani2000 said:
My HBOOT is 0.94.0000 which is very old one i guess as now there are many new one i just want to go back to stock but i can update my h boot and then the install JB from there ..
Click to expand...
Click to collapse
well you need a certain HBOOT to run the 2.17 nand... but i don't remember which was the required HBOOT for 2.17. the best thing would be to update the HBOOT to the latest version and then flash the nand backup

matt95 said:
well you need a certain HBOOT to run the 2.17 nand... but i don't remember which was the required HBOOT for 2.17. the best thing would be to update the HBOOT to the latest version and then flash the nand backup
Click to expand...
Click to collapse
can you tell me how can i do that ?? becasue the hboot also require me revert to stock rom and lock the phone to finish it aint that the thing ??? or is there any other way i can do that ?? actually there is an update of hboot for my cid..i tried flashing it but it didnt worked for me ...

Yeah, you need to be locked. When you unlock again, it will wipe the phone
Take a nandroid backup and then
fastboot oem lock
Then try hboot update again.

BenPope said:
Yeah, you need to be locked. When you unlock again, it will wipe the phone
Take a nandroid backup and then
fastboot oem lock
Then try hboot update again.
Click to expand...
Click to collapse
so what you mean is first i need to falsh the nandroid back up and then update my Hboot by relocking my phone ??

Nani2000 said:
so what you mean is first i need to falsh the nandroid back up and then update my Hboot by relocking my phone ??
Click to expand...
Click to collapse
no, you first need to update the hboot and then flash the nand backup

matt95 said:
no, you first need to update the hboot and then flash the nand backup
Click to expand...
Click to collapse
yes that's the problem i am on a coustom rom ARHD .so my que is should i have to be on stock rom to update my hboot or i just relock the phone and flsh the hboot ?? and i have another problem when i try to flash the firmware to update my hboot it says your version dosent match so it cannot complete so ...what should i do now ?

Thanks for the help
matt95 said:
no, you first need to update the hboot and then flash the nand backup
Click to expand...
Click to collapse
i just flash the firmware that is there with the nandroid back but it says error maybe the version is not similer for updating my hboot well i think i should either wait for anyone to develop a bypass for hboot or just stay in ics for ever but anyway thanks for helping me with more info .:laugh:

What is the output of
fastboot getvar version-main

BenPope said:
What is the output of
fastboot getvar version-main
Click to expand...
Click to collapse
i'll post all the things so you can have a better idea of whats my phone made of !
D:\HTC ONE X BACK UP\Fastboot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.94.0000
(bootloader) version-baseband: 5.1204.163U.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.707.10
(bootloader) serialno: HT25HW101180
(bootloader) imei: 353043053829837
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s

But that version-main doesn't exist!
What's
fastboot oem readcid

BenPope said:
But that version-main doesn't exist!
Click to expand...
Click to collapse
yeah, that's quite unusual

matt95 said:
yeah, that's quite unusual
Click to expand...
Click to collapse
seems like i have an unusual phone ...well i got oem cid as T-MOB 101

BenPope said:
But that version-main doesn't exist!
What's
fastboot oem readcid
Click to expand...
Click to collapse
yes i know that is not there i even checked in chinese websites there all i can find is that this phone belongs to asiapacific i dont know what they mean by that my ime suggest its from germany!! what a mess with this phone and i cannot go back to stock cuz when i got the phone i dont know much about backing up so i just let some guy who is better than me in andriod to falsh a custom rom cuz i dont want to use that chinese version phone with lot of stupid apps which i cannot uninstall at that moment and now i dont have the back up and i am stuck with no updates nothing ....

Might be worth a go:
http://www.4shared.com/zip/ZnUXbKbq/firmware_2171113.html
http://www.4shared.com/zip/lwUAtyRu/Nandroid_2171113_T-MOB101.html
Or are we going in circles?

BenPope said:
Might be worth a go:
http://www.4shared.com/zip/ZnUXbKbq/firmware_2171113.html
http://www.4shared.com/zip/lwUAtyRu/Nandroid_2171113_T-MOB101.html
Or are we going in circles?
Click to expand...
Click to collapse
thanks for trying mate ...i just flash the firmware through fastboot flash zip firmware.zip i didnt nandroid back up it though because its told me that i should update my h boot first which i cannot because of the its say's failed error remote blocked and the one i did is the one you provided . so now i really dont know how can i make it work ?? ca

[Q] CM11 M9 to Stock

Hi,
I have an UK HOX which is running CM11. I am giving it my father and want to revert to stock beforehand. I don't have a nandroid backup & can't seem to find one which will work. Is this possible or will I be stuck on CM?
I'm currently on HBOOT 1.36 & radio 5.1204 (not sure if that's relevant). Please let me know if there's more info I can provide.

GX45 said:
Hi,
I have an UK HOX which is running CM11. I am giving it my father and want to revert to stock beforehand. I don't have a nandroid backup & can't seem to find one which will work. Is this possible or will I be stuck on CM?
I'm currently on HBOOT 1.36 & radio 5.1204 (not sure if that's relevant). Please let me know if there's more info I can provide.
Click to expand...
Click to collapse
give the result from command fastboot getvar version-main and then we will see

Thanks,
version-main: 3.14.206.27

GX45 said:
Thanks,
version-main: 3.14.206.27
Click to expand...
Click to collapse
now you must find nandroid backup with this numbers for One X or ask @T3nd3rB33£ to upload for you

Here's the link to the post,
http://forum.xda-developers.com/showthread.php?p=55550765
Hope it helps

GX45 said:
Thanks,
version-main: 3.14.206.27
Click to expand...
Click to collapse
This is what you search and don't forget to say thanks to T3nd3rB33£

Thanks to you both!

Hi just read the thread properly, I have confused you in my pm, Thant is right, your on hboot 1.36 so you need my nand not glenbrownies. This is the stock nand from before the jb update which has the hboot version 1.1? You will need to update in settings about phone check for updates and you'll then have sense 5 installed.
You can install a nand which has a lower hboot version but not a nand that has a higher hboot version.

T3nd3rB33£ said:
Hi just read the thread properly, I have confused you in my pm, Thant is right, your on hboot 1.36 so you need my nand not glenbrownies. This is the stock nand from before the jb update which has the hboot version 1.1? You will need to update in settings about phone check for updates and you'll then have sense 5 installed.
You can install a nand which has a lower hboot version but not a nand that has a higher hboot version.
Click to expand...
Click to collapse
No worries. Thanks a million for the help
Can I just get one last noob question out the way - in the nandroid backup folder, are they both the stock boot.img and recovery.img I need to flash after restoring? Or do I need to find a separate stock boot & recovery img?

I've successfully reverted back to stock. Only issue I have now is that the official OTA update won't install. It downloads and boots into the stock recovery, then about a third of the way up the progress bar the process stops and the recovery icon changes to the red triangle with the exclamation mark in it.
I've also tried it again after doping a factory reset with no luck. Any experience with this happening?

GX45 said:
I've successfully reverted back to stock. Only issue I have now is that the official OTA update won't install. It downloads and boots into the stock recovery, then about a third of the way up the progress bar the process stops and the recovery icon changes to the red triangle with the exclamation mark in it.
I've also tried it again after doping a factory reset with no luck. Any experience with this happening?
Click to expand...
Click to collapse
you must to put the stock recovery for 3.14 base

T3nd3rB33£ said:
Hi just read the thread properly, I have confused you in my pm, Thant is right, your on hboot 1.36 so you need my nand not glenbrownies. This is the stock nand from before the jb update which has the hboot version 1.1? You will need to update in settings about phone check for updates and you'll then have sense 5 installed.
You can install a nand which has a lower hboot version but not a nand that has a higher hboot version.
Click to expand...
Click to collapse
Thant said:
you must to put the stock recovery for 3.14 base
Click to expand...
Click to collapse
I've flashed the stock recovery & still no joy. Also tried flashing the 'firemware.zip' file from the OTA and trying to install the it manually with no success, either.

GX45 said:
I've flashed the stock recovery & still no joy. Also tried flashing the 'firemware.zip' file from the OTA and trying to install the it manually with no success, either.
Click to expand...
Click to collapse
take the recovery.img from firmware.zip and flash it report back the backup must be with the same numbers like your

Thant said:
take the recovery.img from firmware.zip and flash it report back the backup must be with the same numbers like your
Click to expand...
Click to collapse
Just flashed the recovery from the firmware.zip file & the OTA update fails at same stage.
My bootloader is unlocked, should it be relocked for this to work?
Edit: Relocked bootloader & tried with the same result. I noticed the hboot img file in the 'firmware' zip is a higher version than mine (1.36) ... Would it be worth flashing this then trying again?

GX45 said:
Just flashed the recovery from the firmware.zip file & the OTA update fails at same stage.
My bootloader is unlocked, should it be relocked for this to work?
Edit: Relocked bootloader & tried with the same result. I noticed the hboot img file in the 'firmware' zip is a higher version than mine (1.36) ... Would it be worth flashing this then trying again?
Click to expand...
Click to collapse
don't use the recovery from OTA update use previos one or this for your main version and must be recovery for your main version
other way is to lock the bootloader flash firmware.zip then flash custom rom or stock nandroid backup. But you need to see your main version again after flashing the zip

Thant said:
don't use the recovery from OTA update use previos one or this for your main version and must be recovery for your main version
other way is to lock the bootloader flash firmware.zip then flash custom rom or stock nandroid backup. But you need to see your main version again after flashing the zip
Click to expand...
Click to collapse
Here's the 'getvar all' info
version: 0.5a
version-bootloader: 1.72.
version-baseband: 5.1204.
version-cpld: None
version-microp: None
version-main: 4.18.206.4
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: O2___001
devpower: 92
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Now the wifi and SIM card/mobile data won't work. Where do I go from here?

GX45 said:
Here's the 'getvar all' info
version: 0.5a
version-bootloader: 1.72.
version-baseband: 5.1204.
version-cpld: None
version-microp: None
version-main: 4.18.206.4
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: O2___001
devpower: 92
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Now the wifi and SIM card/mobile data won't work. Where do I go from here?
Click to expand...
Click to collapse
Now you must unlock your bootloader flash Philz 5.15.9 find nand backup 4.18.206.4 copy to sd card install it flash boot.img and flash recovery from OTA and you are full stock or you can install custom rom near to stock like Maximus HD or ARHD or som kitkat roms

Thant said:
don't use the recovery from OTA update use previos one or this for your main version and must be recovery for your main version
other way is to lock the bootloader flash firmware.zip then flash custom rom or stock nandroid backup. But you need to see your main version again after flashing the zip
Click to expand...
Click to collapse
Thant said:
Now you must unlock your bootloader flash Philz 5.15.9 find nand backup 4.18.206.4 copy to sd card install it flash boot.img and flash recovery from OTA and you are full stock or you can install custom rom near to stock like Maximus HD or ARHD or som kitkat roms
Click to expand...
Click to collapse
Awesome, that's worked! Got the JB update restored, runs great! It does say there's another update to install but I get an HTC error saying basically the device is rooted (I installed the new recovery & relocked bootloader, it's def not rooted anymore) but I don't care to be perfectly honest.
Thank you guys so much for all your help!

[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

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 )

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.