Develop Bugs

[Q] HTC One M8 HELP!

Hello, i must send my phone to service and need help.
My phone is rooted and i have custom recovery, i went from S-OFF to S-ON and locked the bootloader but forgott to install stock recovery.
Now i try to S-OFF with Sunshine again but it fails all the time:

Adrianiii said:
Hello, i must send my phone to service and need help.
My phone is rooted and i have custom recovery, i went from S-OFF to S-ON and locked the bootloader but forgott to install stock recovery.
Now i try to S-OFF with Sunshine again but it fails all the time:
Click to expand...
Click to collapse
So did you try to contact Sunshine team as per the instructions?

yes no help from them..

You'll need to unlock your bootloader at HTCDev if Sunshine won't work.... And obviously that's not a good idea if you're sending it in.
Not sure what you can do... You're a bit stuck.

Flash an untouched firmware for your device version with external_sd method. It'll install the stock recovery.

ckpv5 said:
Flash an untouched firmware for your device version with external_sd method. It'll install the stock recovery.
Click to expand...
Click to collapse
I did that and it worked, thx but my next prob is that i cant unroot my phone and in my bootloader i have status: Modified

Modified Status in Recovery

Hey guys !
As the title suggests. What does that mean? and how do i revert to official locked ?
I have s-on and have rooted and installed twrp, and cwm afterwards. And decided to go back to stock( because the current methods of changing to s-off are not working) by flashing through cwm a RUU backup. And flashing the stock recovery afterwards. I have also declined root access when prompted by cwm after RUU install.
What can I do to return to 100% stock ?
After entering fastboot The first text is ***MODIFIED*** and at os there is blank space. I want to return my phone to out of the box state.

sherbibv said:
Hey guys !
As the title suggests. What does that mean? and how do i revert to official locked ?
I have s-on and have rooted and installed twrp, and cwm afterwards. And decided to go back to stock( because the current methods of changing to s-off are not working) by flashing through cwm a RUU backup. And flashing the stock recovery afterwards. I have also declined root access when prompted by cwm after RUU install.
What can I do to return to 100% stock ?
After entering fastboot The first text is ***MODIFIED*** and at os there is blank space. I want to return my phone to out of the box state.
Click to expand...
Click to collapse
You need S-OFF. With S-ON you cannot remove the 'MODIFIED' text.

XSL-FO said:
You need S-OFF. With S-ON you cannot remove the 'MODIFIED' text.
Click to expand...
Click to collapse
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED

sherbibv said:
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED
Click to expand...
Click to collapse
You must S-OFF. Remove texts, unroot, relock bootloader and go S-ON.

sherbibv said:
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED
Click to expand...
Click to collapse
Doesn't matter, you can restore stock ROM until the cows come home. You won't be able to change the modified flag in the bootloader. You need S-OFF to change the text to "official" just like you'll need S-OFF to change the bootloader "locked" text to "Locked" and not "Relocked" if you relock the bootloader.
You will NOT be able to have it show the same way it was "out of box" if you do NOT have S-OFF.

So the only way is to buy the s-off service with 25$ right?

BerndM14 said:
Doesn't matter, you can restore stock ROM until the cows come home. You won't be able to change the modified flag in the bootloader. You need S-OFF to change the text to "official" just like you'll need S-OFF to change the bootloader "locked" text to "Locked" and not "Relocked" if you relock the bootloader.
You will NOT be able to have it show the same way it was "out of box" if you do NOT have S-OFF.
Click to expand...
Click to collapse
Sorry for the noob question, but what does modified imply ? What does it mean exactly?

sherbibv said:
Sorry for the noob question, but what does modified imply ? What does it mean exactly?
Click to expand...
Click to collapse
It means unlocked botloader and of course rooted. It means that you have tampered with the software.

XSL-FO said:
It means unlocked botloader and of course rooted. It means that you have tampered with the software.
Click to expand...
Click to collapse
But I can continue running like this without a problem right?
It won't cause any instability ?
And also, can I install OTAs?

sherbibv said:
But I can continue running like this without a problem right?
It won't cause any instability ?
Click to expand...
Click to collapse
Any at all. You can run it safely like this.

XSL-FO said:
Any at all. You can run it safely like this.
Click to expand...
Click to collapse
what about OTAs?

sherbibv said:
what about OTAs?
Click to expand...
Click to collapse
You will be able to recieve OTA's but if you want to install them you will need to go back to stock recovery. Easy. After OTA flash again a custom one.

XSL-FO said:
You will be able to recieve OTA's but if you want to install them you will need to go back to stock recovery. Easy. After OTA flash again a custom one.
Click to expand...
Click to collapse
I'm currently on stock recovery

sherbibv said:
I'm currently on stock recovery
Click to expand...
Click to collapse
It's ok. Keep it if you want.

sherbibv said:
I'm currently on stock recovery
Click to expand...
Click to collapse
Then you're fine.
Rooted, S-OFF, Modified status, none of those will prevent OTA updates. You MUST have stock reocovery and stock ROM for OTA updates i.e No changes to system files, no deleted apps, no xposed framework.
If all those are stock you can get and install OTA no problem. Don't even have to relock the bootloader for it.

BerndM14 said:
Then you're fine.
Rooted, S-OFF, Modified status, none of those will prevent OTA updates. You MUST have stock reocovery and stock ROM for OTA updates i.e No changes to system files, no deleted apps, no xposed framework.
If all those are stock you can get and install OTA no problem. Don't even have to relock the bootloader for it.
Click to expand...
Click to collapse
I had Xposed and still I was able to upgrade.

Thanks allot guys !
Have e great day ! :good:

sherbibv said:
Thanks allot guys !
Have e great day ! :good:
Click to expand...
Click to collapse
You too. Good luck.

[Q] back to stock

Yes i read threads over going back to stock but my question is a little bit different
I got a dutch T-mobile branded M8 after i did my first root i made a a backup from my phone with TWRP.
i can't get S-OFF, so my phone is still S-ON!
Now i got the problem that my HBOOT isn't updated since, this is giving me problems with newer versions of TWRP and so for CM12.
My thoughts were:
- flash my backup to my phone
- ? 1
- ? 2
- update it regulary via ota updates (guess my phone is updated to the latest hboot)
- Root my phone
- install any new rom
Frist my questons are for the questionmarks in my steps:
? 1: Should i un-root and relock my bootloader?
? 2: Anythinge else i missed?
Thanks in advance

samstar said:
i can't get S-OFF, so my phone is still S-ON!
Click to expand...
Click to collapse
You can't s-off, since sunshine says your phone is not supported? Or you don't want to pay for sunshine?
samstar said:
Frist my questons are for the questionmarks in my steps:
? 1: Should i un-root and relock my bootloader?
? 2: Anythinge else i missed?
Click to expand...
Click to collapse
1) No need to unroot or relock bootloader. But no system files can be modified in order to OTA. If you made the nandroid right after installing TWRP and root, without any other mods, you should be OK.
2) You also need to flash stock recovery to install OTA

redpoint73 said:
You can't s-off, since sunshine says your phone is not supported? Or you don't want to pay for sunshine?
1) No need to unroot or relock bootloader. But no system files can be modified in order to OTA. If you made the nandroid right after installing TWRP and root, without any other mods, you should be OK.
2) You also need to flash stock recovery to install OTA
Click to expand...
Click to collapse
Don't want to pay for sunshine, don't see the importance, just want to **** around with custom roms, never has been a great difference for me.
but the stock recovery, how do i get it? i donloaded one from a thread but just want to be sure it's alright

samstar said:
Don't want to pay for sunshine, don't see the importance, just want to **** around with custom roms, never has been a great difference for me.
Click to expand...
Click to collapse
If you want s-off, pay for it. Otherwise, don't. And I agree that if the goal is merely to update firmware, you don't need s-off in your case. As for the importance, s-off allows a number of things, including being able to flash radios, modified hboots, and unlock SIM. These may not be relevant or needed by you.
But to say you can't s-off is not correct. You just don't want to. When asking for help, its best to provide the most complete and correct information.
samstar said:
but the stock recovery, how do i get it? i donloaded one from a thread but just want to be sure it's alright
Click to expand...
Click to collapse
Download the stock recovery corresponding to your stock software number from this thread: http://forum.xda-developers.com/showthread.php?t=2701376

Need help with S-On HTC One M9...

I have an international stock HTC One M9. CID is: HTC__621 and firmware version: 210.709.1 - I've already found the stock recovery for 210.709.1 - I'm looking to install a custom ROM, but I may want to go back to stock later on. I found a TWRP stock backup for 210.709.1, but because I am S-ON, will I not have to manually flash the boot.img? I used winrar to look into the TWRP backup, and I could not find a boot.img. So, my question is: if I flash the TWRP backup using TWRP, will the boot.img automatically get flashed?

You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .

mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?

mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
There's no "boot.emmc.win" within the archive? I can't find it...

arif9m9 said:
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
Click to expand...
Click to collapse
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON. (I wasn't able to verify that since my phone is S-OFF.) So there should be no need to rename and manually flash the boot image if it's already inside the backup.
arif9m9 said:
There's no "boot.emmc.win" within the archive? I can't find it...
Click to expand...
Click to collapse
You can find the needed boot image in my signature.

Flippy498 said:
You can find the needed boot image in my signature.
Click to expand...
Click to collapse
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?

arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
If you use the backup from my signature you only need to follow the instructions on the first page of my google sheet to get back to stock.
Be warned: Since Android 5.1 you should only relock the bootloader if you are completely sure that your phone is able to boot to system and that you ticked the new option that allows a bootloader unlock (can be found in the developers options). Many users already got stuck with a non-booting phone that cannot be re-unlocked because they didn't fulfill these requirements. (Sidenote: If you only want to get back to stock to install new OTAs you don't need to relock your bootloader.)
Besides I read that some people stated that the AOSP roms of the M9 messed up their LTE reception (so that LTE was even unusable on other custom roms or stock rom). I don't know whether this problem is already fixed. Some weeks passed since I read about that problem so I suggest you to read the corresponding threads before you start flashing.

arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.

iElvis said:
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
Click to expand...
Click to collapse
My phone is S-ON, won't I have to flash the boot.img via fastboot?

arif9m9 said:
My phone is S-ON, won't I have to flash the boot.img via fastboot?
Click to expand...
Click to collapse
Flippy498 said:
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON.
Click to expand...
Click to collapse
iElvis said:
There is no need to flash the boot.img separately on this phone.
Click to expand...
Click to collapse
No, it's not needed. The only exceptions are backups that don't contain a boot image (like mine for example). That's why I created the google sheet with the instructions.

Flippy498 said:
No, it's not needed.
Click to expand...
Click to collapse
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?

arif9m9 said:
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
Click to expand...
Click to collapse
No.

Flippy498 said:
No.
Click to expand...
Click to collapse
But, I'm S-ON....

arif9m9 said:
But, I'm S-ON....
Click to expand...
Click to collapse
It hasn't been an S-on restriction since the M7.

iElvis said:
It hasn't been an S-on restriction since the M7.
Click to expand...
Click to collapse
Does that mean I can flash RUUs even if I'm S-ON?

arif9m9 said:
Does that mean I can flash RUUs even if I'm S-ON?
Click to expand...
Click to collapse
For your CID/MID, yes.

iElvis said:
For your CID/MID, yes.
Click to expand...
Click to collapse
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?

arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.

iElvis said:
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
Click to expand...
Click to collapse
When going back to stock, at which stage should I relock my bootloader?

arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
Because if you follow these guides your phone will state "locked" instead of "relocked" at the end. And that is only possible with S-OFF. Besides with S-ON you can only use RUUs with the same firmware version as your phone (or newer RUUs)*.
*Actually downgrades seem to be possible, too, but as far as I know only if the two first numbers of the firmware versions before and after the downgrade are the same. Like from 1.32.xxx.15 to 1.32.xxx.8 but not from 1.40 versions to 1.32 versions or from 2.xx versions to lower versions.
Edit: Looks like I didn't type fast enough.

No recovery.... ?

Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:

There is always a recovery installed. Either the stock one or the custom one. What does it do when you go to the recovery?

10rdan said:
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
Click to expand...
Click to collapse
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.

jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available

Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Click to expand...
Click to collapse
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?

10rdan said:
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
Click to expand...
Click to collapse
Yes i think it does work again. But that's a try and find out. There is always the possibility i could be wrong.
Edit :
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.

Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files.
Click to expand...
Click to collapse
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.

jollywhitefoot said:
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
Click to expand...
Click to collapse
That's new to me. Hopefully it isn't just tied to the developers edition then.
Thanks for the information

Mr Hofs said:
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Click to expand...
Click to collapse
I'll bare that in mind, will unlock tomorrow again and try newer twrp. Only reason I relocked was to run ruu to get phone running again.

jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
Where can I find 3.0.2.2, can only see 3.0.2.0 on twrp site?
Cheers
Edit.... Found it. ?

@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.

10rdan said:
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
Click to expand...
Click to collapse
I'm not exactly sure, but up until 3.0.2.2 Captain Throwback didn't even have the device and was working blind. I know he was trying different things to make it compatible with different variants, too, so in my mind that was a test build. I'm not sure why they have it on the downloads page. For me, I always download it from the download section of the twrp thread.