Develop Bugs

[Q] Somehow Installed Custom ROM without S-OFF; Don't Know How to Get Back

Hello! I have somewhat a... Unique problem, you could say. I bought the HTC One (M8) in early June and fell in love with it. Sadly, as most things do with me, it got old. I wanted to spice up my phone without paying for a whole new one, so I said "What about a custom ROM?" I wanted to get Cyanogenmod 11. So, I rooted my device, then installed the Cyanogenmod 11 snapshot for the HTC One M8. I somehow installed CM without changing the bootloader security to S-OFF, and then realized that CM didn't have support for the BoomSound speakers or the Duo camera (basically the only non-software features of the M8). After about a week I wanted to switch back, so I tried and failed multiple times, always able to return to CM 11 thankfully. As I tested things I learned that it was the S-ON that was denying me to reinstall stock Sense 6. So, here's my question: How do I get to S-OFF, or back to stock sense 6? I tried Firewater, and since the OTA that came pre-installed with the device patched Firewater, I'm out of luck. Any suggestions or help would be great! Thank you!
(If this is a repeat question, I will gladly cooperate and delete the thread, just let me know!)

You can get S-Off using SunShine. Go to theroot.ninja only downside is it costs $25, but it's well worth it. Sorry if I didn't answer the question completely.

That is a possibility. Thank you for the feedback!
Sent from my One M8 using XDA Free mobile app

trandazzo1998 said:
Hello! I have somewhat a... Unique problem, you could say. I bought the HTC One (M8) in early June and fell in love with it. Sadly, as most things do with me, it got old. I wanted to spice up my phone without paying for a whole new one, so I said "What about a custom ROM?" I wanted to get Cyanogenmod 11. So, I rooted my device, then installed the Cyanogenmod 11 snapshot for the HTC One M8. I somehow installed CM without changing the bootloader security to S-OFF, and then realized that CM didn't have support for the BoomSound speakers or the Duo camera (basically the only non-software features of the M8). After about a week I wanted to switch back, so I tried and failed multiple times, always able to return to CM 11 thankfully. As I tested things I learned that it was the S-ON that was denying me to reinstall stock Sense 6. So, here's my question: How do I get to S-OFF, or back to stock sense 6? I tried Firewater, and since the OTA that came pre-installed with the device patched Firewater, I'm out of luck. Any suggestions or help would be great! Thank you!
(If this is a repeat question, I will gladly cooperate and delete the thread, just let me know!)
Click to expand...
Click to collapse
You could always give Sunshine a shot, it cost $25 but is a sure shot to work. I've recently used it on my new M8 when Firewater failed and it worked wonders, rooted + S-OFF/Bootloader unlocked in about 5-10 minutes. Very simple, only reason it took me so long was I was confused for some reason.

I think you should be able to return to stock without S-Off. What's the output of
fastboot getvar all
We don't need your IMEI or serial number.

BenPope said:
I think you should be able to return to stock without S-Off. What's the output of
fastboot getvar all
We don't need your IMEI or serial number.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 99000499029029
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_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: d4c3cae5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.014s

Hmmm, that TWRP issue that erases version-main is a pain.
You should be able to restore somebody else's backup.
Check the backups thread for something that matches your CID SPCS_001. With that hboot I'm assuming something fairly new.

Hmm SPCS_001 is Sprint if I remember correctly,maybe u can try to go to Sprint m8 thread

BenPope said:
Hmmm, that TWRP issue that erases version-main is a pain.
You should be able to restore somebody else's backup.
Check the backups thread for something that matches your CID SPCS_001. With that hboot I'm assuming something fairly new.
Click to expand...
Click to collapse
hdorius said:
Hmm SPCS_001 is Sprint if I remember correctly,maybe u can try to go to Sprint m8 thread
Click to expand...
Click to collapse
Does anyone know where I can find a SPCS_001 backup? I couldn't see any on the main backup thread or the Sprint HTC One M8 thread.

You should be able to simply flash a sense rom like viper or ahd or insertcoin.
Though not stock rom.... They are close to stock and will let you use the features you want.
Sent from my HTC One_M8 using XDA Free mobile app

shohratshankar said:
You should be able to simply flash a sense rom like viper or ahd or insertcoin.
Though not stock rom.... They are close to stock and will let you use the features you want.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
When I try to flash through Fastboot I get this:
target reported max download size of 1830215680 bytes
sending 'zip' (1414650 KB)...
OKAY [ 43.255s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 43.264s
And when I do it through my recovery (CWM) I got:
Zip flashed unsuccessfully
BUT since I now installed TWRP it worked? So thank you for asking me to try again because it did work.

[Q] Unfortunately camera stopped

Hi there,
I am using an HTC One M8. I was using a SkyDragon ROM (SkyDragon+M8+v+3.1+WWE+Sense+7.zip). It was buggy as hell, the phone seemed to be happy for a while but as time went on it just slowed down and slowly camera performance started to degrade. Eventually the camera simply wouldn't work. I view this as a software related issue. I thought maybe it would be better to change to a different more recent ROM so I installed ViperOneM8 4.3.0 and got the phone running again. The camera still doesn't work.
I've searched on Google for a fix to this issue but most posts either suggest a clearing of the camera cache (which didn't work) OR a factory reset (which I didn't do because I just installed a new ROM, so same thing right??) OR they suggest tweaking some setting in your LastPass Manager or other password management tools (I don't have these installed).
I've tried other camera apps to see if it can get working but no other camera app works either, they all give similar errors, "Camera not working", OR "Can't connect to camera", and so on....
I don't believe this to be a hardware failure, it must be a software fault because everything was fine until I unlocked the boot loader and started installing custom ROM's. Any help will be greatly appreciated. Oh and in case anyone is curious I am on the latest version of TWRP, and I have repaired permissions (not that its necessary). Thanks for the help guys
Regards,
Saragn

Did you make a nandroid of you stock ROM? If so, restore it and see if the camera issue persists.
If not, why the heck not???

redpoint73 said:
Did you make a nandroid of you stock ROM? If so, restore it and see if the camera issue persists.
If not, why the heck not???
Click to expand...
Click to collapse
Hi...I didn't make a NANdroid backup of the stock ROM. In hind sight I probably should have.

Try ruu to go back to stock and see if that makes a difference.... If in stock it doesn't work then you might have a hardware defect

danial.aw said:
Try ruu to go back to stock and see if that makes a difference.... If in stock it doesn't work then you might have a hardware defect
Click to expand...
Click to collapse
It's a hardware fault. I have a 3rd party app that is not a camera app BUT allows you to upload pics into the app via a camera function. When you hit the button to take a pic it connects to the camera but the picture is just stripes and purple haze. It's heat damage, I think.

Saragn said:
It's a hardware fault.
Click to expand...
Click to collapse
There is no way you can be sure of that, if you don't return to stock. It doesn't seem you've done any troubleshooting to confirm its not software or firmware. In particular, the firmware is the bridge between software and hardware, and can be fooling you into thinking its a hardware issue. And the fact the problem arose after flashing ROMs (and going from old ROMs to recent ROMs) is highly suspicious, and almost certainly means you firmware is outdated.
What is your hboot number?

redpoint73 said:
There is no way you can be sure of that, if you don't return to stock. It doesn't seem you've done any troubleshooting to confirm its not software or firmware. In particular, the firmware is the bridge between software and hardware, and can be fooling you into thinking its a hardware issue. And the fact the problem arose after flashing ROMs (and going from old ROMs to recent ROMs) is highly suspicious, and almost certainly means you firmware is outdated.
What is your hboot number?
Click to expand...
Click to collapse
Hi,
HBOOT number is: HBOOT-3.19.0.0000
Ok so maybe I should have mentioned why I thought its a hardware failure issue. When I unlocked the bootloader and installed the SkyDragon ROM the camera was fine, there was no issue with it whatsoever. That was for about a month. Then as time went on the camera app would cause the phone to seriously slow down when I tried using the camera. It would hang for up to two minutes, you would not be able to switch the phone off or do anything. When it did that you had to leave it to let it get over what ever was going on and then a restart would get the phone back to normal.
Then, after weeks and weeks of that, the camera eventually just died and would not start at all and that's where I am now with it. The next problem I have is that I do not know how to return to stock, I made no "NANDroid" backup of it before I installed the SkyDragon ROM. I didn't see anything on any of the forum "how-to" documents speak about doing a NANDroid backup, had I seen it I'd have done it.
So in short, I have done "some" troubleshooting, maybe just not to the level that you are comfortable with. So do you understand now why I think it's a hardware fault?
Thanks for the replies.
Saragn

Saragn said:
So do you understand now why I think it's a hardware fault?
Click to expand...
Click to collapse
Do you understand why I might be skeptical of that? See from your first post:
Saragn said:
I don't believe this to be a hardware failure, it must be a software fault because everything was fine until I unlocked the boot loader and started installing custom ROM's.
Click to expand...
Click to collapse
It seems your story is changing. Or at the least, you didn't give the full story to begin with, which makes it hard for us to help.
I'd still recommend returning to full stock. It certainly doesn't hurt, and helps to eliminate the possibility that its a software issue. You've now probably spent more time giving excuses to not return to stock; than it would have actually taken to do so.
Either find your stock nandroid for your CID from the collection here: http://forum.xda-developers.com/showthread.php?t=2701376
Or run the RUU if there is one for your CID.

redpoint73 said:
Do you understand why I might be skeptical of that? See from your first post:
It seems your story is changing. Or at the least, you didn't give the full story to begin with, which makes it hard for us to help.
I'd still recommend returning to full stock. It certainly doesn't hurt, and helps to eliminate the possibility that its a software issue. You've now probably spent more time giving excuses to not return to stock; than it would have actually taken to do so.
Either find your stock nandroid for your CID from the collection here: http://forum.xda-developers.com/showthread.php?t=2701376
Or run the RUU if there is one for your CID.
Click to expand...
Click to collapse
Well, yes, of course the story is changing because what I have experienced with the phone since posting this has made me think otherwise. It's been some time since the first post. At first I thought it was software but then the cues I got from the device seemed more hardware related. Being human my mind is allowed to change. My follow up posts have clearly explained everything.
I never discounted the idea of returning to stock, neither did I make excuses for not wanting to I don't think. You have a very funny way of helping someone mate, either way I do appreciate it, maybe not your tone, but that's irrelevant. Thank you for responding and helping out I do appreciate it.

@Saragn: a custom rom is just that. its been modified, hacked, changed, upgraded. it was built on the devs own phone which means it works perfect (unles he says why it doesnt) on that exact model.
even if you have that model its possible that there are minor differences that cause that rom to not work perfect on yours.
as @redpoint73 says, the only way really now is to go back completely to stock and try it again.
if it works then you will just have to try different roms until you find one that works for you.
if it doesnt, its almost certianly hardware and you need to return it. which will require it to be stock anyway.
this is a good time to learn how to take a nandroid backup so you can easily swap back again to try something else.
p.s. check out @redpoint73 thanks count. at least 3834 people on here appreciate what hes doing to help here and are obviously not bothered about his 'tone'

gazzacbr said:
@Saragn: a custom rom is just that. its been modified, hacked, changed, upgraded. it was built on the devs own phone which means it works perfect (unles he says why it doesnt) on that exact model.
even if you have that model its possible that there are minor differences that cause that rom to not work perfect on yours.
as @redpoint73 says, the only way really now is to go back completely to stock and try it again.
if it works then you will just have to try different roms until you find one that works for you.
if it doesnt, its almost certianly hardware and you need to return it. which will require it to be stock anyway.
this is a good time to learn how to take a nandroid backup so you can easily swap back again to try something else.
p.s. check out @redpoint73 thanks count. at least 3834 people on here appreciate what hes doing to help here and are obviously not bothered about his 'tone'
Click to expand...
Click to collapse
Hi,
Pardon the length of time it has taken me to reply. I was away on business for a while so couldn't really pay much attention to the phone. Ok so my CID number is HTC__016. Also, if I do a "getvar all" I get the following:
C:\>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-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__016
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.173s
I've looked for an RUU exe or zip that works. The RUU packages for this specific version (4.16.401.10) all come out corrupt. I've downloaded various versions from all over this forum, other forums, I think I've downloaded over 10GB in total, 7 or 8 different downloads and they all come out corrupt and so the RUU process doesn't work. I'm not sure where else to get an actual RUU file that works and that isn't corrupt.
Any ideas? Not sure what to do next. Thanks guys.
PS...Never mind about the tone, its how I read it....doesn't matter!

Saragn said:
Hi,
Pardon the length of time it has taken me to reply. I was away on business for a while so couldn't really pay much attention to the phone. Ok so my CID number is HTC__016. Also, if I do a "getvar all" I get the following:
C:\>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-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__016
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.173s
I've looked for an RUU exe or zip that works. The RUU packages for this specific version (4.16.401.10) all come out corrupt. I've downloaded various versions from all over this forum, other forums, I think I've downloaded over 10GB in total, 7 or 8 different downloads and they all come out corrupt and so the RUU process doesn't work. I'm not sure where else to get an actual RUU file that works and that isn't corrupt.
Any ideas? Not sure what to do next. Thanks guys.
PS...Never mind about the tone, its how I read it....doesn't matter!
Click to expand...
Click to collapse
ALSO....I've checked this thread: http://forum.xda-developers.com/showthread.php?t=2735235 and it doesn't seem to work. I can't get the device to be S-OFF as the thread suggests and it also doesn't show up as LOCKED....it still shows UNLOCKED. So I'm a bit lost now.

Saragn said:
ALSO....I've checked this thread: http://forum.xda-developers.com/showthread.php?t=2735235 and it doesn't seem to work. I can't get the device to be S-OFF as the thread suggests and it also doesn't show up as LOCKED....it still shows UNLOCKED. So I'm a bit lost now.
Click to expand...
Click to collapse
hi, the thread you are quoting there is for going completely back to stock for selling or rtm for repair.
you dont need to go that far.
S-ON/OFF is the security lock, you dont need to bother with that for what you are doing.
LOCKED/UNLOCKED is for the bootloader. you unlocked it to flash a custom rom now you have to relock it to go back to stock.
you will need to relock the bootloader for this if you are still S-ON but this can be done easily through fastboot usb on the phone and 'fastboot oem lock' from a command prompt.
if you have the right stock zip file for your phone you can flash it back to stock anyway by renaming it to 0P6BIMG.zip, copying it to the sd card and booting to hboot.
hboot it will check the file then ask if you want to install it.
note that you can open and view the zip file but cannot safely extract anything from it. it is probably not corrupt.
check the MD5 if you want to be really sure.
an ruu.exe can be done from windows but there are not many of those around.
(anyone else reading here please correct me if i am wrong)

gazzacbr said:
hi, the thread you are quoting there is for going completely back to stock for selling or rtm for repair.
you dont need to go that far.
S-ON/OFF is the security lock, you dont need to bother with that for what you are doing.
LOCKED/UNLOCKED is for the bootloader. you unlocked it to flash a custom rom now you have to relock it to go back to stock.
you will need to relock the bootloader for this if you are still S-ON but this can be done easily through fastboot usb on the phone and 'fastboot oem lock' from a command prompt.
if you have the right stock zip file for your phone you can flash it back to stock anyway by renaming it to 0P6BIMG.zip, copying it to the sd card and booting to hboot.
hboot it will check the file then ask if you want to install it.
note that you can open and view the zip file but cannot safely extract anything from it. it is probably not corrupt.
check the MD5 if you want to be really sure.
an ruu.exe can be done from windows but there are not many of those around.
(anyone else reading here please correct me if i am wrong)
Click to expand...
Click to collapse
Hi...Thanks for the response.
Ok so I've done all of that, oem lock...I have confirmed on multiple ROM's that I cannot open the zip file. When you try open it simply to view the contents windows says it cannot open the file as it is corrupt. I'm fairly certain I know how a zip file works and how to tell when the archive is corrupt. I tried each file on more than one computer and they all say the same thing so the file locations, mostly listed on threads on this forum, all result in faulty downloads. I have a big pipe at the office so can download anything fairly quickly. So I don't know where to find a zip file that works....I have done the whole renaming to 0P6BIMG.zip but the file does not work, none of them do...I've tried several downloads from several different locations and they are all corrupt.
Really, it can't be that much of a challenge to get back to stock. I don't know why the oem lock doesn't work but they device stays unlocked...the bootloader screen confirms this.

Hi,
not sure why the bootloader will not relock.
only other alternative is to pay $25 for sunshine and get S-OFF then you can install the rom without relocking the bootloader.
maybe if you mention the exact names of the stock roms you have tried, i assume they were from the xda rom collection, in that thread and check if someone has already used one of them.
did get the MD5 and check that out?
there is only one rom for mine (dual sim) which i downloaded before and that works perfectly, but as i said, i can actually open the zip file but just not extract it.

HTC m8 not starting up correctly. Tried everything i can think of and find.

Hello there!
I have now searched and searched and come upon many great threads in this massive forum however i have yet to find a solution to my current problem. Every time i have went here i have always managed to find something to help me fix my phones over the years but this this time I've hit a wall it seems.
What happened was that my phone started to crash the google apps like gallery etc. No big deal at first but then i decided to do a factory reset thinking that might fix the problem but then my phone just starts up to the HTC logo and throws several different error messages that Google.xxx.xxx could not start/has crashed. IF i click these away they appear after a while again and the phone will be stuck like that.
I can start the phone in fastboot mode to be able to use ADB etc..
The phone is currently bootloader unlocked and with S-on
Now this is what i have done:
First of all the phone wasn't in debugging mode when it crashed so I'm guessing its still not which might complicate the matter further.
* Using a TWRP.img file i managed to get the phone in to the TWRP mode on the phone. (Fastboot boot TWRPfilename.img)
I do not have any TWRP files on my phone nor any apps this was all from the files on the PC. I just mention this because thats the only sign of life the phone has given me so far.
*I tried to go in from the adb shell and enabling it using the following code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
I have no idea as to if it worked or not but the phone rebooted again.
* Tried to reflash with the right RUU for my phone with the right CID thanks to guides on this forum -- i get error 159 (this is because the CID is wrong from what ive read in other threads)
* Tried changing the CID to 11111111 but that did not work i got another error doing that:
C:\adb>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 3
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 0
(bootloader) sdhci_open: id=0
(bootloader) Initializing MMC host data structure and clock!
(bootloader) mmc slot#2 clock enabled
(bootloader) sdhci_set_clock: slot 2, freq 192000000
(bootloader) GPLL0 is enabled
(bootloader) clock_update_cfg_sd is done
(bootloader) sd clock set done
(bootloader) sdhci_set_bus_width: bus width 0
(bootloader) sdhci_clk_supply: freq 400000
(bootloader) Decoded CID fields:
(bootloader) Manufacturer ID: 2
(bootloader) OEM ID: 0x544d
(bootloader) Product Name: SA16G
(bootloader) Product revision: 1.1
(bootloader) Product serial number: 37A24E6D
(bootloader) Manufacturing date: 10 2013
(bootloader) sdhci_clk_supply: freq 50000000
(bootloader) sdhci_set_bus_width: bus width 1
(bootloader) Done initialization of the card
(bootloader) erase_grpsize: -16777216
(bootloader) erase_grpmult: 261077976
(bootloader) wp_grpsize: 0
(bootloader) wp_grpen: 0
(bootloader) perm_wp: 0
(bootloader) temp_wp: 0
(bootloader) [Tuxera][Error] No exFAT partition found
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.132s]
finished. total time: 0.132s
* Tried flashing from a .zip file with the fastboot commands.
ALL of these things I have tried with the bootloader locked and unlocked. (if this is any important info)
The phone ran the 6.12.401.4 version at the moment of the crash and that's what shows in the RUUs ive tried as well. Also the phone is not rooted.
Now is there a way to completely flush the phone out of any info and just reinstalling it like you can do with windows on a PC for example since whatever i try is met by an error message or a failed flash etc..?
some more info about the phone from getvar:
(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: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__Y13
(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.028s

1. remove your serial & imei no. on your post
2. http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
3. relock bootloader with command -
fastboot oem lock
fastboot reboot-bootloader
4. http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

Thank you for your fast reply!
I have removed the lines from the post as you said and tried your links unfortunately without success. This is why im hoping you like a challange! hehe.
This is the result from the cmd when trying to flash the new RUU:
C:\Users\Genocide\Desktop\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
I followed your steps 1 by 1 downloaded all needed files and installs etc... Something is terribly wrong with my device it seems.
Any further ideas?

Did you skip no.3 ?
Why it is zipp not zip ?
Try again ..
If still fails, tomorrow I'll give you another method.. already in bed.

oh! ive done goofed!
It was my bad with some **** spelling there.
IT WORKED!!
I thank you sooooo much from the bottom of my heart I was sure my phone was unsaveable for a moment.
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
I'm just curious on how you could spot the problem so that i can learn more about how it works.
Thanks again! Truly great work!

Sambeg said:
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
Click to expand...
Click to collapse
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.

redpoint73 said:
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
Click to expand...
Click to collapse
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
redpoint73 said:
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
Click to expand...
Click to collapse
I think this is where all else failed since all the ones i tried had either the ADB or a file called only Fastboot.exe not this one that said HTC_fastboot.exe
redpoint73 said:
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Click to expand...
Click to collapse
I tried all the solutions in both locked/relocked state just to be sure i had no real understanding of this before but I am now enlighten thanks to you
redpoint73 said:
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.
Click to expand...
Click to collapse
Yeah those things are clear for me as well. I just had the problem with the RUU not working for me. Thanks again for all the help and the good information provided even after my problem has been solved

Sambeg said:
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
Click to expand...
Click to collapse
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Only if you are still curious why the RUUs didn't work, of course. I understand its somewhat of a moot (or purely academic) point, now that the phone is working.

redpoint73 said:
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Click to expand...
Click to collapse
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3

Sambeg said:
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Click to expand...
Click to collapse
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
Third RUU: As you know, this isn't for your phone. You can run it a million times, and it will still fail every time; as its intended to fail since the CID and MID on your device doesn't match what the RUU is looking for. The only way to run this RUU is to s-off and change your phone's CID and MID.
Forth RUU: Again, not for your phone. Plus, the Sprint version, which has partition differences from your M8 version (and most other M8 versions). You absolutely should stay away from any Sprint or Verizon firmware, as if they do manage to flash, will often lead to a radio brick on your device.
This would never flash anyway with s-on, and the safeguards of the CID and MID did their job and saved you, in this case.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.

redpoint73 said:
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.
Click to expand...
Click to collapse
Yes indeed this cleared up most of my suspicions as well as i said i knew the 3rd and 4th was wrong from the get go it was more of a test..
Thank you for all this good info i feel like im starting to get a good grip on whats good and whats working etc... I really appreciate it! Thumbs up indeed.
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.

Sambeg said:
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.
Click to expand...
Click to collapse
You can only change the CID (and also MID) with s-off.

redpoint73 said:
You can only change the CID (and also MID) with s-off.
Click to expand...
Click to collapse
Right as I thought then Well thanks again for helping out and clearing up my questions.
I shall now retire from this thread in peace

HELP, m8 stuck in bootloop at "starting apps."

hi i've got a huge problem with my htc m8. it wont boot anymore and always keeps on beeing stuck on "android is starting... starting apps." after an optimization of 167 apps. have been pulling an all nighter and im at the end of the rope unfortunatly =(.
i alrdy hard reset it several times. through bootloader factory reset, as well as recovery and wipe data/fac reset. i only can stop the bootloop by pressing power+volume up and switching into bootloader. it also takes forever to optimize the 167 apps....
after having read a few threads here and elsewhere i also did 2 recoverys with 0P6BIMG.zip with an miniSD card through bootloader/fastboot and once through htc_fastboot with RUU.zip through the CMD in win10. in all 5 cases the phone tells me it successfully "recovered"/reset its system but it still always starts again with optimizing 167 apps and then beeing stuck on "starting apps...".
the m8 is ***locked*** and S-ON with software status official. OS- 6.12.401.4. i never customized the android os and bought it brand new.
(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: 6.12.401.4
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s
im grasping for straws here guys (desperately). appreciate all the help i can get. there are a lot of people here who seem to be experts in this. i am totally new to this and really hoping for guidance. thanks in advance!

I`ve had a similar issue today, while trying to revert my phone from an update to GPE Rom.
I was able to reboot my phone, and get back to the bootloader, and from there I flashed to a stock rom.
What I did was, volume up + power, and just when the phone turned black, I pushed the volume down button, and it entered the bootloader instantly.
Sorry if it didn`t help you out much, but I was stuck in the updating apps, and was able to get off rebooting loop only like that, I was stuck for about an hour on that!
Good luck!

Chubbiebr said:
I`ve had a similar issue today, while trying to revert my phone from an update to GPE Rom.
Click to expand...
Click to collapse
The OP has a stock device, so the situation is really not similar, nor have the same solution.
In addition, what the OP neglected to post here (but posted in another thread) is that his issue was caused by dropping the phone, and going major physical damage. No amount of software fixes is going to help the OP:
http://forum.xda-developers.com/showpost.php?p=67417831&postcount=1761
Chubbiebr said:
I was able to reboot my phone, and get back to the bootloader, and from there I flashed to a stock rom.
What I did was, volume up + power, and just when the phone turned black, I pushed the volume down button, and it entered the bootloader instantly.
Sorry if it didn`t help you out much, but I was stuck in the updating apps, and was able to get off rebooting loop only like that, I was stuck for about an hour on that!
Click to expand...
Click to collapse
What exactly did you try to flash (file name) and flash it how (TWRP, fastboot, etc.).?
What was the original condition? "revert from an update to GPE Rom" really isn't specific enough.
Were you on a GPE ROM, or did you fully convert to GPE using RUU (2 very different things)/ Bootloader screen is black or white?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
In addition, what the OP neglected to post here (but posted in another thread) is that his issue was caused by dropping the phone, and going major physical damage. No amount of software fixes is going to help the OP:
http://forum.xda-developers.com/showpost.php?p=67417831&postcount=1761
Click to expand...
Click to collapse
i didnt drop the phone. a 2.5 kg plate dropped on it. and i also dont think its interior is broken because of that. only the display glass is broken. the phone was working fine for hours until i tried to use the front camera and the camera app froze up. up to that point all functions were normal apart from the visuals of the broken display glass. even the touchpad/digitizer and colours of the display are working at 100%.
because of that frozen camera app i rebooted the phone. thats when it started to bootloop. the bootloader is also working fine. dislay is still working fine. it just wont boot beyond optimizing apps....
the only hardware problem that could be is: if the front camera is mailfuntioning. can it stop the android os from booting? thats the only explanation it could have for a bootloop hardware wise. if thats not the case its purely a software problem

HTC M8 Logo loop issue
Hi There
Were u able to find a fix for the below issue. Am also having the same problem with M8.

nithinrv said:
Hi There
Were u able to find a fix for the below issue. Am also having the same problem with M8.
Click to expand...
Click to collapse
You dropped a 2.5 kg plate on your M8, and caused physical damage also, like the OP? You tried to flash the RUU through htc_fastboot and SD card methods?
Please don't just post you have the "same problem" without giving any details. My experience, that these issues are never exactly the same (simply too many variables: different CIDs, version numbers, causes for the issue) and if you don't give any details, nobody can provide the proper help.
At a minimum, describe what events led to the current condition (and what that condition is), what you've tried (specific steps, file names, etc.) and the specific outcomes (error messages, other outcomes). Also do fastboot getvar all, and post the output (delete IMEI and serial number before posting).

even i had the same prob..i fixed it by wiping the cache partition..
get into bootloader menu ..go to recovery..and then after the red exclamatory sign appears..keep pressing power button and hold and release volume up button..you will get the wipe cache partition option.
do dat and ur phone will reboot

power and volume up press.

roker22 said:
power and volume up press.
Click to expand...
Click to collapse
Is this a question or a statement? The last post already says power + vol up.
Do you realize you responded to a thread that hasn't been active for over 2 years (August 2016)? Worthwhile contribution is always appreciated. But you decided to make this your first post to xda?

HTC M8: failed to load drivers (wifi and sim)

Hi all,
My gfs phone has had some recent issues with her phone.
First: wifi would be dropped, unable to even turn on the wifi. Error: unable to load drives, reason unknown (19)
So I rooted, unlocked, and flashed with GPE. Worked fine for a few months. Then the same issue occurred, so I flashed again....it got fixed again.
Then last night, it dropped the mobile network. Just kept saying install SIM card.
I did full wipe with TWRP. Tried to reload a GPE rom and it gets to the setup stage. Right away I get "unable to load driver" error. The phone keeps asking me to install SIM card; eventhough there is one in there. And if I skip that step, it won't let me turn wifi....
Is the phone dead? It was originally locked to Rogers in Canada...
Tried GPE, S-ROM, Viper....all coming up with same error of not being able to detect SIM or turn on WIFI during setup....
Any help would be appreciated!
Thanks

Would more info be helpful here?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.631.7
(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: 0P6B16000
(bootloader) cidnum: ROGER001
(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!
I was able to get sim recognition working by doing a data format, factory wipe, then GPE-ROM re-install, but WIFI still knocked out.
Any suggestions?

So, tried flashing back with a TWRP stock backup
CID ROGER001
MID 0P6B16000
6.13.631.7
Then reverted to stock 6.13.631.7 recovery.
Everything booted fine, then "unable to load driver error 19" came up again.
Wifi and bluetooth basically greyout and freeze everytime I try to turn them on.
Any suggestions as to what I can try next?

So figured out the issue.
Needed to update to latest firmware. Thought I had done that when I flashed back to stock.
Missed the step to relock bootloader before flashing firmware with fastboot.
Firmware update went through, and voila....everything up and running...for now.

I'm experiencing very similar problem myself. It seems like the phone was updated ota but it just bugs way too much. When i try to turn on wifi it says failed to load driver, if i turn the air plane mode on and off, and then try to connect to wifi i again get the error, the phone freezes and is stuck in bootlops.
I'm not experienced in flashing but i would like to try to troubleshoot the problem myself. I've heard about the ruu but i'm not sure about my phone variant, and also, do i need root or any type of unlock to reflash my phone to stock ? Tnx.
PS: I bought phone on ebay and it seems like it is running the correct version of stock sense rom.

petarcrncec said:
I'm experiencing very similar problem myself. It seems like the phone was updated ota but it just bugs way too much. When i try to turn on wifi it says failed to load driver, if i turn the air plane mode on and off, and then try to connect to wifi i again get the error, the phone freezes and is stuck in bootlops.
I'm not experienced in flashing but i would like to try to troubleshoot the problem myself. I've heard about the ruu but i'm not sure about my phone variant, and also, do i need root or any type of unlock to reflash my phone to stock ? Tnx.
PS: I bought phone on ebay and it seems like it is running the correct version of stock sense rom.
Click to expand...
Click to collapse
Bro did you read sticky on top which says FREQUENTLY ASKED QUESTIONS ? Much of what you want to know is already there?
Anyway to start off , You turn off the the phone and hold volume down + power button for a few (say 10) seconds and note what it says and post it here.and before you ask,no its not that dangerous

Knightofrepublic said:
Bro did you read sticky on top which says FREQUENTLY ASKED QUESTIONS ? Much of what you want to know is already there?
Anyway to start off , You turn off the the phone and hold volume down + power button for a few (say 10) seconds and note what it says and post it here.and before you ask,no its not that dangerous
Click to expand...
Click to collapse
I have read FAQ and there is no specific question related to my problem there. I have found a few people having wifi issues and unexpected shutdowns but non of them were able to fix it. Most of them just returned the phone which led me to believe the problem might be coming from the hardware side. I've already tried cleaning the cache partition and multiple hard resets, and nothing helped. I know it is not dangerous to enter recovery, as I said, I have read the FAQ. The only method of retrieving the phone variant i found was typing getvar in the cmd thingy which can again be false, depending on the flashed software/kernel/radio or whatever (yes i don't distinguish between radio and kernel really. I'm a noob as I said). I tried googling about the RUU and the root permition and didn't find anything usefull accept for the fact that phone has to be S-on, which my phone is.
So, I did do my research, but i can't go through 400 or so pages of help thread to find a specific question, that might not be even there in the first place so i asked it here.
Sorry for your time and long post, but I will return the phone tomorow, because I really can't know whether the device is defected or not, better safe than sorry.

well if you can return it then its a good way to do be safe,but as the OP said he solved his problem by updating his firmware . I was going to do suggest just that.l,but as you said you did your research it turned out nothing useful and you have it all figured out anyway ,so good luck

Knightofrepublic said:
well if you can return it then its a good way to do be safe,but as the OP said he solved his problem by updating his firmware . I was going to do suggest just that.l,but as you said you did your research it turned out nothing useful and you have it all figured out anyway ,so good luck
Click to expand...
Click to collapse
Thanks, I'll need it in case the seller tries to scam me again

I experience same problem with my HTC Desire 826 it also says that it fails to load driver unknown reason I have multiple times hard reset it I have not rooted I have upgraded to Marshmallow but also experiencing the same problem it's also get heated my WiFi and bluetooth is not working please help me

sabir.786 said:
I experience same problem with my HTC Desire 826 it also says that it fails to load driver unknown reason I have multiple times hard reset it I have not rooted I have upgraded to Marshmallow but also experiencing the same problem it's also get heated my WiFi and bluetooth is not working please help me
Click to expand...
Click to collapse
You are in the wrong forum
Anyway this issue on the m8 fixed by updating the firmware ask in your device forum about the firmware
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
You are in the wrong forum
Anyway this issue on the m8 fixed by updating the firmware ask in your device forum about the firmware
Click to expand...
Click to collapse
I have search for my device its not in ur forum plz help me

What is the solution to this erorr? Error: unable to load drives, reason unknown (19)? i have the same