Develop Bugs

Prep M8 for donation (factory restore)

Hi all,
So I have my old M8 doing nothing (switched to Note 4)...
It's running a custom venom rom, and basically I want to put it completely back to factory state.
If you could help a guy that's moderately good at this stuff, I would be greatly appreciated.
Thanks!!

Post the output from fastboot getvar all and we'll tell you what to do

Thanks for that, err - I haven't got the tools installed any more, could you point in the direction of the tools again sorry!

Ok, getvar just sits at waiting for device...?

Ok sorry, turns out I'm just rusty!
(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:
(bootloader) imei:
(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
all: Done!
finished. total time: 0.020s

1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM

Done, and thanks!

Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks

Shozuki said:
Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks
Click to expand...
Click to collapse
No other way, only sunshine.
But you don't need S-Off to revert to stock with that thread guide, you need to relock bootloader then follow all the steps.
The only thing is without S-Off, your bootloader will show RELOCKED instead of LOCKED.

Ah cool, minor.
Thanks

S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!

EddyOS said:
S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!
Click to expand...
Click to collapse
Indeed, but I'm literally giving it my uncle and let him use it.
If I may ask one more thing though, when sending the ruu.zip
I get:
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 3(s)
Any ideas??
Thanks for your help sirs.

That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?

EddyOS said:
That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?
Click to expand...
Click to collapse
Unfortunately it's still unlocked, but I can't seem to change that either. I'm using minimal adb and fastboot, but the htc_bootloader is in the folder.
Am I supposed to use that from the start, as I only see reference in the final stage.
Apologies, if I'm misreading!
EDIT, I followed the guide starting with recovery which kept failing... That must be the issue...
from your guide EDIT: Thread I meant:
"Well lord knows what's going on here...
I started by flashing the recovery to the one linked here. It won't boot into recovery at all it just sits at "entering recovery..."
I was using a venom custom rom and TWRP 2.8.5.0 touch recovery.
I can boot into the phone, use fastboot and adb - but can't go any further in restoring the handset back to factory... All help appreciated."

ckpv5 said:
1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM
Click to expand...
Click to collapse
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.

crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
Yeah, That guide is for EU M8's only...
really struggling getting mine back to factory...

crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
That depends. Are you s-off? If so, you can run a WWE RUU, and go back to basically stock. WWE is compatible with Rogers. You won't get OTAs though. You'll have to update firmware manually, but with s-off, that's easy to do.

My apologies, I failed to use my eyes.
All solved. Many thanks!!

Shozuki said:
My apologies, I failed to use my eyes.
All solved. Many thanks!!
Click to expand...
Click to collapse
What was it?

EddyOS said:
What was it?
Click to expand...
Click to collapse
Well basically I was following the instructions as if I were S-Off.
Instead I just to use: fastboot oem lock and completely skimmed over the text failing to read it!
My uncle is happy now and thats fine with me!
Thanks for your help!

Hard bricked or what is there any solution helppppppp

i will show you the pics of the phone he only boot in hboot no htc logo no nothing ;] i was tryin a lots of methods no one of them works;] dont have recovery , and its locked and s-on im about to crazy ;] try downgrades ruu thru sd card but everytime says THE MAIN VERSION IS OLDER early i was boot some update thru sd card , update start but in the beggining BOOTLOADER - FAIL PU and update abort no one ruu cant start only says main version is older ;] my htc is not rooted and locked bootloader I DONT KNOW WHAT TO DO I TRY EVERYTHING POSSIBLE TO FIX IT BUT NO LIGHT IN THE TUNNEL ;[ I WILL POST NOW THE FASTBOOT GETVAR ALL if you can help me to fix this hard bricked phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.34.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH45SWW03613
(bootloader) imei: blablablabla
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
or give me some correct ruu that will not give me MAIN VERSION IS OLD

pipaigoleko said:
i will show you the pics of the phone he only boot in hboot no htc logo no nothing ;] i was tryin a lots of methods no one of them works;] dont have recovery , and its locked and s-on im about to crazy ;] try downgrades ruu thru sd card but everytime says THE MAIN VERSION IS OLDER early i was boot some update thru sd card , update start but in the beggining BOOTLOADER - FAIL PU and update abort no one ruu cant start only says main version is older ;] my htc is not rooted and locked bootloader I DONT KNOW WHAT TO DO I TRY EVERYTHING POSSIBLE TO FIX IT BUT NO LIGHT IN THE TUNNEL ;[ I WILL POST NOW THE FASTBOOT GETVAR ALL if you can help me to fix this hard bricked phone
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.34.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH45SWW03613
(bootloader) imei: blablablabla
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
or give me some correct ruu that will not give me MAIN VERSION IS OLD
Click to expand...
Click to collapse
Don't have your model 816, mine is single SIM a5_chl but this forum link had some answers for someone else with your model. Luckily your not really "hard bricked" because you can still enter hboot/fastboot but I understand why you say that. Hard bricked is when your phone is literally an expensive paperweight. Luckily you still have access to your boatloader and that's where most problems can get fixed. By the way what specifically happened that caused this issue? You're boatloader is locked and your not rooted so pure stock right with stock recovery but you can't get into recovery?
http://forum.xda-developers.com/desire-816/help/a5ul-unable-to-flash-ruu-t3294835
Also if you press the power button to select hboot you should go to fastboot mode where you can use volume key to select recovery then press power button to enter.
Below is a link to stock RUU's for yours and other models but you'll need stock recovery installed and working before they can be run. Hopefully your stock recovery is still there just need a different way to enter it i.e. Boatloader or key presses. Only flash your specific versions firmware.Try the one your were currently on before trying one older.
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/

cant go recovery
thoctor said:
Don't have your model 816, mine is single SIM a5_chl but this forum link had some answers for someone else with your model. Luckily your not really "hard bricked" because you can still enter hboot/fastboot but I understand why you say that. Hard bricked is when your phone is literally an expensive paperweight. Luckily you still have access to your boatloader and that's where most problems can get fixed. By the way what specifically happened that caused this issue? You're boatloader is locked and your not rooted so pure stock right with stock recovery but you can't get into recovery?
http://forum.xda-developers.com/desire-816/help/a5ul-unable-to-flash-ruu-t3294835
Also if you press the power button to select hboot you should go to fastboot mode where you can use volume key to select recovery then press power button to enter.
Below is a link to stock RUU's for yours and other models but you'll need stock recovery installed and working before they can be run. Hopefully your stock recovery is still there just need a different way to enter it i.e. Boatloader or key presses. Only flash your specific versions firmware.Try the one your were currently on before trying one older.
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/
Click to expand...
Click to collapse
i cant enter recovery at all ;[

pipaigoleko said:
i cant enter recovery at all ;[
Click to expand...
Click to collapse
still dont have luck with the stocks i try most of them on sdcard hboot ;[[[[

pipaigoleko said:
i cant enter recovery at all ;[
Click to expand...
Click to collapse
So you went into fastboot mode and when you press your power button to select hboot what happens?
Below is a link to a forum for the a5_ul with a link to the stock recovery. Verify this is your version then try flashing it using ADB/fastboot on your P.C. and your phone in fastboot mode. Do you have USB debugging selected in your phone developer options settings?
http://forum.xda-developers.com/desire-816/general/single-sim-816x-a5ul-stock-recovery-t2862637

thoctor said:
so you went into fastboot mode and when you press your power button to select hboot what happens?
Below is a link to a forum for the a5_ul with a link to the stock recovery. Verify this is your version then try flashing it using adb/fastboot on your p.c. And your phone in fastboot mode. Do you have usb debugging selected in your phone developer options settings?
http://forum.xda-developers.com/desire-816/general/single-sim-816x-a5ul-stock-recovery-t2862637
Click to expand...
Click to collapse
i cant turn my phone on even i dont have htc logo start in hboot yes i have now will try to flash ;] i think i have debugging but my device show is only in fastboot and dont list my device only fastboot , BUT IM LOCKED BOOTLOADER AND S-ON CRAZY STUCKING IN BOOT MENU ;] CAN I INSTALL MANUALLY RECOVERY ? BECAUSE I ADB DONT LISTED MY DEVICE

pipaigoleko said:
i cant turn my phone on even i dont have htc logo start in hboot yes i have now will try to flash ;] i think i have debugging but my device show is only in fastboot and dont list my device only fastboot , BUT IM LOCKED BOOTLOADER AND S-ON CRAZY STUCKING IN BOOT MENU ;] CAN I INSTALL MANUALLY RECOVERY ? BECAUSE I ADB DONT LISTED MY DEVICE
Click to expand...
Click to collapse
Did you have the HTC drivers installed on your P.C. or Linux computer?
flashing it using SDK Toolkit /ADB fastboot is doing it manually. The other method is to name the file a specific way so that your phone recognizes it but I have never used this method before. I downloaded the portion of the SDK Toolkit I needed, ADB/fastboot and had the HTC Windows drivers installed from HTC sync manager then put the recovery zip file into my ADB folder in my P.C. then opened command prompt from my ADB folder and typed fastboot flash recovery"name of zip file".img with my phone in fastboot and it flashed. This is what you should try and I'll link some instructions below. Good luck.
http://androidforums.com/threads/cd...ry-image-via-fastboot-or-from-sd-card.385358/
Also if ADB isn't recognizing your phone and you do have the drivers installed then it may be because of what's happened to your phone and then you would need to try and flash from your SD card with the file properly named for your version so that fastboot on your phone will recognize and flash it. I don't know what the proper name is for your version but a lot of the time it's already properly named. How did you lose your recovery in the first place with a locked boatloader and no root?
I must be getting tired. I believe you need an unlocked boatloader to flash a recovery image so you might not be able to flash it. If you can't get into your recovery thru H boot, press power button, volume button to select recovery, enter by pressing power button, then your going to need to flash the stock RUU or zip file with the stock recovery included in the file as you can flash an RUU with the boatloader locked. The issue is will the signed file recognize your firmware as it is now and flash? Wish this was my expertise but I've only flashed RUU files to start my devices clean again not to fix a problem.

nd if im not usb debugged because dont see adb devices only fastboot recognize my device ;[[[ im in big stuck ... i'll say again LOCKED , S-ON , MAYBE NO USB DEBUGGING , STUCK IN BOOTLOADER , AND RUU SAYS MAIN VERSION OLDER ;[

pipaigoleko said:
nd if im not usb debugged because dont see adb devices only fastboot recognize my device ;[[[ im in big stuck ... i'll say again LOCKED , S-ON , MAYBE NO USB DEBUGGING , STUCK IN BOOTLOADER , AND RUU SAYS MAIN VERSION OLDER ;[
Click to expand...
Click to collapse
I know my friend I read it the first time and I understand all that. I'd try the flash with your recovery zip and see if that works. If not then you'll need to flash stock RUU's until you find one that will work but only ones meant for your version . Did you click that one link I gave that was to a forum here in XDA because that forum looked like it was very similar to your problem ?
This one below
http://forum.xda-developers.com/desire-816/help/a5ul-unable-to-flash-ruu-t3294835

http://forum.xda-developers.com/desire-816/general/0p9cimga5ulk44desiresense60htceurope1-t2946515
Download the zip from the thread
Rename it to 0P9CIMG.zip
Copy it to your sdcard
Put the sdcard into your phone
Boot into HBoot, it will recognize an update and confirm
After this, you will be on stock kitkat, but you can make upgrade to lollipop

I'm uploading a RUU for this device right now.
I'll send you a pm once it's done
Do you need Stock recovery too?

nukaru said:
I'm uploading a RUU for this device right now.
I'll send you a pm once it's done
Do you need Stock recovery too?
Click to expand...
Click to collapse
ok im waiting ; ] ty YES I DONT HAVE RECOVERY I JUST NEED TO DOWNGRADE FROM 2.34.401.2 I GUESS BUT EVERYONE RUU SAYS MAIN VERSION IS OLDER

TobiBot said:
http://forum.xda-developers.com/desire-816/general/0p9cimga5ulk44desiresense60htceurope1-t2946515
Download the zip from the thread
Rename it to 0P9CIMG.zip
Copy it to your sdcard
Put the sdcard into your phone
Boot into HBoot, it will recognize an update and confirm
After this, you will be on stock kitkat, but you can make upgrade to lollipop
Click to expand...
Click to collapse
I TRY IT MAN BEFORE BUT AGAIN SAME THING MAIN VERSION IS OLDER HERE'S THE PICS SEE

hey i try with 0P9CIMG_A5_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.34.401.2_Radio_1.101.111011.20.0123_10.28.4149A.00L_release_449710_combined_signed.zip device try to update but again BOOTLOADER -- FAIL PU BEFORE LUCKY TO ACCEPT ANOTHER UPDATE BUT GIVE ME THE SAME -- BOOTLOADER - FAIL PU

That's exactly what happened to my device. RUU is still uploading.
I'll send the recovery, RUU and a guide once it's done uploading

nukaru said:
That's exactly what happened to my device. RUU is still uploading.
I'll send the recovery, RUU and a guide once it's done uploading
Click to expand...
Click to collapse
yes but im not sure having usb debugging ....only fastboot recognize device adb dont ;] how to install recovery with no debugging but..if RUU dont give me fail pu will be nice

My fastboot didn't work either, but I got the device working again after flashing stock RUU.

nukaru said:
My fastboot didn't work either, but I got the device working again after flashing stock RUU.
Click to expand...
Click to collapse
ok buddy im waiting to try ; ]

I should be back home in about 5h, upload is in progress, should be done by the time I get back home.

luka.miskovic said:
there is a script caled misctool used to change main version number, google can help u find it. use it to change main version to 1.00.000.0 and than u can flash any version RUU
Click to expand...
Click to collapse
Thanks for the assist TobiBot. I don't have this version of phone and didn't catch this forum link when I was looking thru XDA. O.P. says he is flashing this way and not from ADB/fastboot and still keeps getting the" older version" notice. I read the whole forum you linked to and found this a few pages in. His radio I.D. is invalid in Getvar all he posted so maybe your suggestion combined with the above posters quote he can make it work. Hopefully just the fix you linked to will do it but if not this might get him the rest of the way.
---------- Post added at 09:02 PM ---------- Previous post was at 08:56 PM ----------
TobiBot said:
http://forum.xda-developers.com/desire-816/general/0p9cimga5ulk44desiresense60htceurope1-t2946515
Download the zip from the thread
Rename it to 0P9CIMG.zip
Copy it to your sdcard
Put the sdcard into your phone
Boot into HBoot, it will recognize an update and confirm
After this, you will be on stock kitkat, but you can make upgrade to lollipop
Click to expand...
Click to collapse
Oops sorry forgot to link to your post when thanking you. He's got reinforcements now too so that's good. The more the better.
---------- Post added at 09:14 PM ---------- Previous post was at 09:02 PM ----------
luka.miskovic said:
yes it does, but when u are using it it wont show u successfuly changed and u can not view current main version from it. but command "misctool w 1.00.000.0" does what it is supposed to. I tested on a5_ul with 4.4.2 and 5.0.2
Click to expand...
Click to collapse
The last quote above from the Misctool suggestion. Never tried it or heard of it but all options should be looked at to fix O.P.'s problem. Hopefully the last poster's help fixes it and this idea is moot but at least it's linked here for the next guy.
Good luck pipaigoleko !

[q] Htc one m8s (qul), can't seem to boot

Hi guys,
After a lot of reading and searching without any luck, this seems the last resort for me. This is the problem.
A week ago or so, I got the marshmallow update on my Phone, htc one m8s. Before this update, i managed to do a custom recovery and root etc. Then I heard about the update and installed an RUU again, restoring the Phone back to stock (renamed RUU zip to 0PKVIMG and copied that into my sd card; after that the stock recovery went all fine).
After the marshamallow update, I tried to do custom recovery again. Somehow it didnt work and i couldnt get the custom recovery working. It flashed fine, booted the img, but wouldnt start the recovery. I tried different varriants of twrp etc. Nothing worked. So that is problem number 1.
The second problem is, dat I think is that I have used a wrong version of recovery boot. Now the Phone wont start after the bootlogo.
The third is, that I cant install stock again, using the method above. I am getting the message; device halted due to large image (...) etc.
Can someone help me please? I would just be happy getting back to stock and be able to use my device again.
Thank you in advance.
Here is my device info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: (deleted)
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__031
(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: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001

First - edit & delete the imei no. from your post.
Your problem is more or less is the same as this one - http://forum.xda-developers.com/htc...-one-m8-wont-update-boot-to-recovery-t3385874
Read thru that thread .. the only difference is you need to find 2.10.401.1 firmware.zip
Check http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245 to see whether you can find the 2.10.401.1 firmware.zip there
* I requested moderator to move your thread to M8s section.

ckpv5 said:
First - edit & delete the imei no. from your post.
Your problem is more or less is the same as this one - http://forum.xda-developers.com/htc...-one-m8-wont-update-boot-to-recovery-t3385874
Read thru that thread .. the only difference is you need to find 2.10.401.1 firmware.zip
Check http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245 to see whether you can find the 2.10.401.1 firmware.zip there
* I requested moderator to move your thread to M8s section.
Click to expand...
Click to collapse
Thanks for your reply! I changed the info.
I really canty find the 2.10.401.1 firmware.zip for m8s. I can find for m9 etc. So I am stuck here. Maybe you know where to find it?
Thanks in advance!

You can find it in the 2nd link that I gave above. It's an OTA zip, you need to extract out the firmware.zip from the 2.10.401.1 OTA.
I can help to upload for you so you don't need to download the whole 1.2 gb OTA for a few mb firmware.zip but you have to wait when I'm home in next 3 hours.

ckpv5 said:
You can find it in the 2nd link that I gave above. It's an OTA zip, you need to extract out the firmware.zip from the 2.10.401.1 OTA.
I can help to upload for you so you don't need to download the whole 1.2 gb OTA for a few mb firmware.zip but you have to wait when I'm home in next 3 hours.
Click to expand...
Click to collapse
Thank you! I managed to flash it via sdcard.
Now I want to do a custom recovery and root the device. What would be the right recovery for this device and how can I check that myself in the future?
Thanks in advance.

Faiq said:
Thank you! I managed to flash it via sdcard.
Now I want to do a custom recovery and root the device. What would be the right recovery for this device and how can I check that myself in the future?
Thanks in advance.
Click to expand...
Click to collapse
Great that you fixed your main problem.
About custom recovery and how to root I think it's best you check the thread that I linked earlier - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
Reason is I don't have this device, only M8 not M8s.
Main thing is use only recovery meant for M8s which you can find a few versions there and install SuperSU.zip that you can get from here : http://forum.xda-developers.com/showthread.php?t=1538053

ckpv5 said:
Great that you fixed your main problem.
About custom recovery and how to root I think it's best you check the thread that I linked earlier - http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
Reason is I don't have this device, only M8 not M8s.
Main thing is use only recovery meant for M8s which you can find a few versions there and install SuperSU.zip that you can get from here : http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Thanks dude, you helped me out a lot with this. My Phone is working now with custom recovery and rooted. Just one last question, so I can finally rest my case.
So getting back to stock, is just flashing the whole OTA file again via sd card i.e. 0PKVIMG or flashing it with fastboot, with the instructions u mentioned above right? Doest it matter whether the devices is unlocked and do i have to flash stock recovery again? or flashing the firmware does the work to gain stock recovery again?

Faiq said:
So getting back to stock, is just flashing the whole OTA file again via sd card i.e. 0PKVIMG or flashing it with fastboot, with the instructions u mentioned above right? Doest it matter whether the devices is unlocked and do i have to flash stock recovery again? or flashing the firmware does the work to gain stock recovery again?
Click to expand...
Click to collapse
No ... that's wrong.
You should have made a non-rooted stock nandroid backup with the custom recovery before you root it. Just restore the backup and install stock recovery to return to stock.
Anyway .. maybe later, there will be RUU for your version. Always check that thread of RUU collection.

Hi guys anybody can help me ? My Htc one m8 has been bricked i can't flash stock ruu

Hi guys anybody can help me ? My Htc one m8 has been bricked i can't flash stock ruu please help me
this are my fastboot getvar all value :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****
(bootloader) imei: ******
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
so my bootlader is locked with security warning and software status : modified

Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?

redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8

redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
when i unplugged the phone from charger this problem occurred i didn't flash any RUU later and my phone is unrooted .

mamali0067 said:
when i unplugged the phone from charger this problem occurred .
Click to expand...
Click to collapse
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
mamali0067 said:
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
Click to expand...
Click to collapse
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?

redpoint73 said:
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
Click to expand...
Click to collapse
yes of course it's about 1.6 GB and in my bootloader it say LOCKED

mamali0067 said:
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
Click to expand...
Click to collapse
Is this a zip format RUU? If so, cut/paste the exact commands you used.

redpoint73 said:
Is this a zip format RUU? If so, cut/paste the exact commands you used.
Click to expand...
Click to collapse
yes the RUU is a zip file , but i flashed that RUU perefer in finding right RUU thread and faced with remote : 12 signature verify fail

mamali0067 said:
i flashed that RUU perefer in finding right RUU thread
Click to expand...
Click to collapse
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!

redpoint73 said:
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
Click to expand...
Click to collapse
Okay dude , so help me here !

mamali0067 said:
Okay dude , so help me here !
Click to expand...
Click to collapse
You didn't provide the info I asked for: cut/paste the exact commands you used

redpoint73 said:
You didn't provide the info I asked for: cut/paste the exact commands you used
Click to expand...
Click to collapse
Yes , I have been cutted and pasted the command

[SOLVED] Just restore to stock

SOLVED - THANKS!
Dear community,
Goal: I want to put a HTC One M8 device into stock. The phone used to be unlocked before and had a custom rom (think it was LineAge).
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Please understand, that I am very new to the topic and have read a lot of stuff, tutorials and because of so many different information and missing experience from my side, I am not sure what to do.
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.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: -0.000s​
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s​
Think because the bootloader is locked?
I have really no clue how to proceed.

gskill150 said:
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Click to expand...
Click to collapse
Probably correct, that mostly likely, you restored the wrong TWRP backup version (not compatible with the firmware on the phone - firmware is not the same thing as the ROM or TWRP backup - that part may be confusing).
What version number TWRP backup did you restore (using the guide)?
gskill150 said:
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s​
Think because the bootloader is locked?
Click to expand...
Click to collapse
Yes, this is because you relocked the bootloader. You can't flash a custom recovery with a locked or relocked bootloader, by definition.
But relocking the bootloader is not part of the guide, in regards to restoring a TWRP backup. What exactly were you trying to accomplish the relocking the bootloader?

I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories. I would try this next. Or what do you recommend?
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Thanks and best regards

gskill150 said:
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
Click to expand...
Click to collapse
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
gskill150 said:
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories.
Click to expand...
Click to collapse
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
gskill150 said:
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Click to expand...
Click to collapse
In short, yes, that is the current version number of the firmware on the phone.
When "firmware" is discussed for this device, it does not refer to the ROM or OS number. But rather, firmware is a small file that is needed for the ROM to work and includes hboot, radio, and a number of other partitions (Bluetooth, WiFI), but does not contain the ROM itself. This is confusing, as some folks like to use the terms "firmware" and "ROM" interchangeably. At least for this device, you should wipe that notion from your mind.
Flashing a custom ROM or restoring a stock TWRP backup will not touch firmware, as flashing a ROM by TWRP will only change the system and boot.img partitions, and not touch things like hboot, radio. And flashing a ROM in TWRP will also not affect the version number reported in getvar. That number will only change if you flash firmware.zip or RUU.
RUU is a complete factory image (40+ partitions) which also includes firmware. Some folks will call the RUU the "stock ROM" but you can now see, it is much more than that.
A little confusing, right?

First of all, many thanks for your detailed help and sorry for providing incomplete information from my side. This topic is really hard to understand and confuses me a lot. Sorry for that.
redpoint73 said:
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
Click to expand...
Click to collapse
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
Click to expand...
Click to collapse
Sorry for that - as written I am new to the topic and was mixing up things that do not belong together (RUU, ROM, firmware). Again in a few words: phone used to have LineAgeOS (CustomRom) and I just wanted get rid of it and restore the original android version as if I had bought the phone completely new
I tried it through TWRP because I found this tutorial here in the forum and thought this would be the right path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
Click to expand...
Click to collapse
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
Click to expand...
Click to collapse
I meant the RUUs from the other guide I have just posted above
A little confusing, right?
Click to expand...
Click to collapse
To be honest, now it is completely clear to me thanks to your really good explanation. Thanks mate!
So I could go for the ruu.zip flashing path to achieve what I want right?

gskill150 said:
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
Click to expand...
Click to collapse
That is the right number stock backup to restore (same number as firmware number - version main in getvar). I don't know why you are having issues with WiFi and Bluetooth.
Might be a problem with the firmware. Flashing RUU is probably the best approach. Not only will it restore the stock ROM, but also restore stock firmware. Which hopefully will resolve your WiFi and Bluetooth issue.
gskill150 said:
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
So I could go for the ruu.zip flashing path to achieve what I want right?
Click to expand...
Click to collapse
That RUU should be okay. Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).

redpoint73 said:
Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
Click to expand...
Click to collapse
Hi, thanks for your reply. I will give it a try! :good:

gskill150 said:
Hi, thanks for your reply. I will give it a try! :good:
Click to expand...
Click to collapse
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!

gskill150 said:
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
Click to expand...
Click to collapse
You're quite welcome. Glad it worked for you.

Hello guys,
I have an HTC one m8 , I have been running a rooted device with custom rom which has been working terribly on my device...Now I want to return to stock rom, I have relocked bootloader and it's on s-on...I have tried out diverse RUU but all seems not working...I'm always getting this error in the process "rom update utility cannot update your andriod phone"" which i guess the ruu's have been using are not compatible with my phone...I would so much appreciate if anyone can get me the RUU executable file for my device that will be compatible with it........ Here is the fastboot getvar all details....Your prompt responses will be appreciated
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: S**********6
(bootloader) imei: 35*************7
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s

Jjohnson0830 said:
I have tried out diverse RUU but all seems not working...
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
Click to expand...
Click to collapse
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.

redpoint73 said:
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
Click to expand...
Click to collapse
Ok, pls where can i get the stock TWRP backup and how am i going to return to stock using it?
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again

Jjohnson0830 said:
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Click to expand...
Click to collapse
No, you really don't. Please.