Develop Bugs

flash rom with unlocked bootloader

So from what I see you are able to flash a sense ROM with s on and a unlocked boot loader. Can I do this with my droid incredible? Its rooted with cwm and a unlocked boot loader. If so can I use a sense 4.0 ROM? Also I think I have to flash boot.IMG from fast boot right?

Trozzul said:
So from what I see you are able to flash a sense ROM with s on and a unlocked boot loader. Can I do this with my droid incredible? Its rooted with cwm and a unlocked boot loader. If so can I use a sense 4.0 ROM? Also I think I have to flash boot.IMG from fast boot right?
Click to expand...
Click to collapse
If you have cwm installed you can flash any rom made for the incredible.
No you do not need to flash anything from hboot except cwm, which you say you already have.

cmlusco said:
If you have cwm installed you can flash any rom made for the incredible.
No you do not need to flash anything from hboot except cwm, which you say you already have.
Click to expand...
Click to collapse
i still have S-on does this hurt it?

Trozzul said:
i still have S-on does this hurt it?
Click to expand...
Click to collapse
No it will not hurt anything, you only need root/custom recovery to flash a rom. However i would suggest you think about going s-off, as it can come in handy if something goes wrong. It also allows you to flash recoveries, radios, splash screens, ..., thru hboot.

So then what's the point of s-on?
Sent from my Inspire 4G using xda app-developers app

Trozzul said:
So then what's the point of s-on?
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
S-on (Security On) is just a way for htc to lock down the bootloader to stop you from flashing unsigned images and messing up your phone. Along the way enough htc customers expressed the desire to be able to put custom roms on their phones that htc listened and came up with the unlockable bootloader. Unlocking the bootloader however does not turn all bootloader security off, but meerly allows you to flash unsigned recovery and boot images. All other images are still locked and can only be flashed with a signed image from htc. So they let you flash a custom recovery, which in turn allows you to flash roms and kernels. But they still keep important things like the bootloader it self, the misc partition, etc locked so you cant brick your phone. At least not as easily.

So what I'm going to do is make a nand backup then factory reset from cwm then flash a ROM and I shouldn't brick my phone? I thought of the because my HTC inspire 4g(or the HTC desire HD) had a unlocked boot loader and cwm and was able to flash ROMs but I had to fast boot flash the ROMs boot.IMG do you know why I don't have to do it with this phone?
Sent from my Inspire 4G using xda app-developers app

Trozzul said:
So what I'm going to do is make a nand backup then factory reset from cwm then flash a ROM and I shouldn't brick my phone? I thought of the because my HTC inspire 4g(or the HTC desire HD) had a unlocked boot loader and cwm and was able to flash ROMs but I had to fast boot flash the ROMs boot.IMG do you know why I don't have to do it with this phone?
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
No im not sure why, but you dont have to. Just backup, wipe and flash the new rom.

cmlusco said:
No im not sure why, but you dont have to. Just backup, wipe and flash the new rom.
Click to expand...
Click to collapse
thanks for the help!

[Q] do i need s off for installing custom roms

i am a little confused .... i rooted my desire hd and installed cwm recovery..... bootloader is unlocked but i couldnt get s off..... can i just install custom roms by putting zip in sd card and apllying that zip from cmw recovery or do i need s off !!!!!
thanks in advance

assasin196 said:
i am a little confused .... i rooted my desire hd and installed cwm recovery..... bootloader is unlocked but i couldnt get s off..... can i just install custom roms by putting zip in sd card and apllying that zip from cmw recovery or do i need s off !!!!!
thanks in advance
Click to expand...
Click to collapse
No you do not technically need to be s-off. If you have cwm installed just install rom zip from there

thekool11 said:
No you do not technically need to be s-off. If you have cwm installed just install rom zip from there
Click to expand...
Click to collapse
what basically is s off????

assasin196 said:
what basically is s off????
Click to expand...
Click to collapse
In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag.
Click to expand...
Click to collapse
Quoted from here

If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.

bananagranola said:
If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
sir how to do that.... i have unlocked bootloader i need to flash rcmix energized rom... how to flash boot.img and where do i find it????

Extract the ROM, than flash the boot.img, but I would consult in the ace think tank thread b4 you do something because I might be wrong
Sent from my Inspire 4G using xda premium

Look for instructions in post #7 of the link in my signature.

PLZ HELP
hey guys
i have a htc sensation rooted + unlocked bootloader + clockworkmod installed but NO s-off so can i install custom roms
If YES then can anyone tell me which rom is the best?:good:

Salman03 said:
hey guys
i have a htc sensation rooted + unlocked bootloader + clockworkmod installed but NO s-off so can i install custom roms
If YES then can anyone tell me which rom is the best?:good:
Click to expand...
Click to collapse
Your in the wrong place my friend, you might want to look here for Roms for your device

My xposed modules sent working is it because I don't have s off? I'm rooted with twrp any advise

1st timer question....

Ok im nexus user but my sister gave me her old DHD to give it to my father but i can't root that $#$!#$ device...im on 3.13.163.3 software no root no s-off (whatever this is) and im not sure what version i have to download from htcdev to downgrade to hboot2.....anyone can help???

Ok i manage to unlock the bootloader with upgrading hboot....i dont have sdcard can i remove soff without one???so i can normally flash roms??cause i flash "RandomROMv101" i also fastboot flash the boot.img after that....but i didnt manage to boot to rom....it takes me to twrp!!!

If your bootloader is S-On unlocked, you need to flash the boot.img from fastboot each time you flash a ROM.

bananagranola said:
If your bootloader is S-On unlocked, you need to flash the boot.img from fastboot each time you flash a ROM.
Click to expand...
Click to collapse
On fastboot is show a purple line sais unlock something...but one line bellow sais sON...can i s-off it without sdcard??

Why do you want S-Off?

bananagranola said:
Why do you want S-Off?
Click to expand...
Click to collapse
To be able to flash boot without flasthboot....i cant flash nothing now...for 4.1 roms i need to flash something else??i flash them through twrp after that i flash boot.img through fastboot but it send me straight to recovery

pikachukaki said:
To be able to flash boot without flasthboot....i cant flash nothing now...for 4.1 roms i need to flash something else??i flash them through twrp after that i flash boot.img through fastboot but it send me straight to recovery
Click to expand...
Click to collapse
What version of TWRP are you running? What ROM are you trying to flash? Are you full wiping? How are you flashing the boot.img? Are there any error messages?

bananagranola said:
What version of TWRP are you running? What ROM are you trying to flash? Are you full wiping? How are you flashing the boot.img? Are there any error messages?
Click to expand...
Click to collapse
This happent to me for the 1st time...but it needed format system too....not sure maybe it isnt inside the update-script file!!!now its all good....so whats exacly soff is doing??i didnt need to flash boot with fastboot

pikachukaki said:
This happent to me for the 1st time...but it needed format system too....not sure maybe it isnt inside the update-script file!!!now its all good....so whats exacly soff is doing??i didnt need to flash boot with fastboot
Click to expand...
Click to collapse
I have no idea what you're saying.

bananagranola said:
I have no idea what you're saying.
Click to expand...
Click to collapse
I had to wipe system too...i only making factory reset that didnt wipe system...all roms i have used wipe system through update-script...anyway now its all good...but why i didnt need to flash boot.img through fastboot?

look here http://forum.xda-developers.com/showthread.php?t=2367322

questions about returnig to stock - warrenty

I have to get 100% stock for warrenty.. my devices is s-off, custom recovery, bootloader unlocked and custom rom. Will i get to stock with these steps: ?
- flash the stock rom (from my nadroid backup)
- flash the stock recovery
- set the bootloader to "locked"
- go back s-on
do i need an unlocked bootloader to get s-on ("writesecureflag 3) ?
Thanks!

If you used htcdev to unlock the boot loader, this can be a problem since HTC can see it!

MICH_** said:
I have to get 100% stock for warrenty.. my devices is s-off, custom recovery, bootloader unlocked and custom rom. Will i get to stock with these steps: ?
- flash the stock rom (from my nadroid backup)
- flash the stock recovery
- set the bootloader to "locked"
- go back s-on
do i need an unlocked bootloader to get s-on ("writesecureflag 3) ?
Thanks!
Click to expand...
Click to collapse
Have you tried looking at this thread? http://forum.xda-developers.com/showthread.php?t=2735235

MrKhozam said:
Have you tried looking at this thread? http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
Yes i have Do i have to flash the whole firmware? Or is it enough to flash te stock recovery? should be okay i think..

MICH_** said:
Yes i have Do i have to flash the whole firmware? Or is it enough to flash te stock recovery? should be okay i think..
Click to expand...
Click to collapse
If you're already on stock Sense 6 before doing these steps, I would think flashing stock recovery is enough. Then you can manually boot into the OS and do a factory reset from within the settings, before sending it off for warranty repairs.

MrKhozam said:
If you're already on stock Sense 6 before doing these steps, I would think flashing stock recovery is enough. Then you can manually boot into the OS and do a factory reset from within the settings, before sending it off for warranty repairs.
Click to expand...
Click to collapse
okay, thank you! do you think i should go s-on? (i heard about may risks when going back s-on)

MICH_** said:
okay, thank you! do you think i should go s-on? (i heard about may risks when going back s-on)
Click to expand...
Click to collapse
You can try spoofing S-ON status through hboot. I have not tried this before, so proceed with caution. You can read about it here: http://forum.xda-developers.com/showthread.php?t=2708721.

MrKhozam said:
You can try spoofing S-ON status through hboot. I have not tried this before, so proceed with caution. You can read about it here: http://forum.xda-developers.com/showthread.php?t=2708721.
Click to expand...
Click to collapse
Does it work to flash files (.zip & recovery) with a locked bootloader but s-off? And is it possible to get s-on with a locked bootloader?
Okay, thanks guys! I just "stocked" my phone The only thing that´s left is s-off. Do you recommend to go back s-on?

I successfully returned my M8 back to full stock (no root, locked bootloader and S-On). I wrote about my experiences here: http://forum.xda-developers.com/showpost.php?p=55374704&postcount=7

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.