Hi all,
Does any of you have the answer for the above mentioned ?
Please advice
Nope, you have to relock manually after flashing the RUU. Do not relock ever unless you RUU first.
I thought flashing a fresh firmware will lock back the bootloader automatically.
What a waste, in this case HTC service centre people will know we have modified the software via unlocking bootloader
Related
Will I get the official OTA update if I have unlocked the bootloader via HTCdev method? Actually, I unlocked the bootloader via HTCdev on my sensation which is still in Android 2.3.4. (At that point I didn't know that doing that would not allow supercid and all that stuff.)
If I will get the update.. I just wanted to know after the official OTA update from HTC, will it be a like a new phone? (yeah, i know it will be factory reset.. but i wanted to know if my bootloader, rooting and etc. Will that remain?)
I want the all the rooting and unlocked bootloader not to stay so that i can start afresh with Revolutionary and flash one of the Sense 4 ROMs.. Please help!!
Thank you!
vipulnj said:
Will I get the official OTA update if I have unlocked the bootloader via HTCdev method? Actually, I unlocked the bootloader via HTCdev on my sensation which is still in Android 2.3.4. (At that point I didn't know that doing that would not allow supercid and all that stuff.)
If I will get the update.. I just wanted to know after the official OTA update from HTC, will it be a like a new phone? (yeah, i know it will be factory reset.. but i wanted to know if my bootloader, rooting and etc. Will that remain?)
I want the all the rooting and unlocked bootloader not to stay so that i can start afresh with Revolutionary and flash one of the Sense 4 ROMs.. Please help!!
Thank you!
Click to expand...
Click to collapse
Yes you will receive OTA and bootloader will remain **unlocked**. All you need to receive OTA is stock rom, stock recovery and original cid (S-OFF or S-ON doesn't matter).
By the way if you are still on android 2.3.4 most probably your Hboot is 1.18 that means you can S-Off using Revolutionary and then supercid, root etc.. (you can revert easily to original cid and stock recovery anytime).
If you upgrade to ICS 4.0 with Hboot 1.27 you won't be able to S-OFF and supercid unless someone will find a solution. Actually Hboot 1.27 is not supported by Revolutionary.
Ota to ICS 4.0 will not factory reset your phone. Your data and apps will be untouched.
Honestly I don't understand if you are rooted or not. Unlocking bootloader by HtcDev doesn't mean you are rooted. Could you please clarify?
Hope it helps.
I have hboot 1.18, with bootloader unlocked using HTC Dev, and I'm running ARHD with stock kernel.
Revolutionary gives me the zerg root error, so I used HTC Dev method. But now I'm unable to use the tacoroot method because my bootloader is unlocked. I tried relocking the bootloader, but that gives me a security warning and I can't boot my phone normally without unlocking it again.
Can someone please tell me how to upgrade to ICS now?
I'm a noob and I don't want to experiment too much and brick my phone.
crimsonedge03 said:
I have hboot 1.18, with bootloader unlocked using HTC Dev, and I'm running ARHD with stock kernel.
Revolutionary gives me the zerg root error, so I used HTC Dev method. But now I'm unable to use the tacoroot method because my bootloader is unlocked. I tried relocking the bootloader, but that gives me a security warning and I can't boot my phone normally without unlocking it again.
Can someone please tell me how to upgrade to ICS now?
I'm a noob and I don't want to experiment too much and brick my phone.
Click to expand...
Click to collapse
hmm by relocking you mean fastboot oem lock ?
that should not give security warning...
also before trying tacoroot ...you should flash stock recovery first...any GB stock recovery would do...(fastboot flash recovery recovery.img)
I had a NANDROID backup which I made just after unlocking the bootloader and rooting my phone. I restored that backup before relocking (fastboot oem lock) but it gave me the security warning.
Also, what if I relock the bootloader and then run a BG RUU? Would that work?
With all the bootloader unlocking and flashing up to different RUU's, etc..
Will there be a way that someone might be able to come up with a procedure to revert back to complete stock?
Just wondering if you get going flashing roms and encounter a problem where you will need to exchange or take back your phone, a way to get it to stock form.
thanks
1.change you cid back to your original one.
2. relock your bootloader.
3. flash a ruu..
niceppl said:
1.change you cid back to your original one.
2. relock your bootloader.
3. flash a ruu..
Click to expand...
Click to collapse
Has anyone came up with a way to change the cid back to stock
and I thought if you were on 1.85, you simply couldnt flash a prior ruu
joho5 said:
Has anyone came up with a way to change the cid back to stock
and I thought if you were on 1.85, you simply couldnt flash a prior ruu
Click to expand...
Click to collapse
one you have unlocked your bootloader, your phone will either say unlocked or relocked. There's nothing that we can do about that. even if you changed the CID back to the AT&T one.
SuperCID means you can flash any RUU you want
gunnyman said:
one you have unlocked your bootloader, your phone will either say unlocked or relocked. There's nothing that we can do about that. even if you changed the CID back to the AT&T one.
SuperCID means you can flash any RUU you want
Click to expand...
Click to collapse
So I guess the best we can do is flash the stock ruu at the time and relock it and hope for the best.
joho5 said:
So I guess the best we can do is flash the stock ruu at the time and relock it and hope for the best.
Click to expand...
Click to collapse
you worried about returning a phone? It's been my experience that they don't look.
My device is S-OFF and I'm running unlocked bootloader, custom recovery, and custom ROM.
I'm going to be returning it so I want to restore to completely stock (including S-ON). Any guides for this?
RedBullet said:
My device is S-OFF and I'm running unlocked bootloader, custom recovery, and custom ROM.
I'm going to be returning it so I want to restore to completely stock (including S-ON). Any guides for this?
Click to expand...
Click to collapse
Not exactly an all in one. Start here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
The method for turning S-On and relocking can be found here: http://forum.xda-developers.com/showthread.php?t=2745257 near the bottom of the first post
Dottat's pre-rooted RUUs can be found here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
My advice would be to flash a pre rooted RUU, Lock the bootloader, turn s-on then flash the stock RUU that matches the pre-rooted RUU. Don't forget to do a factory reset at the end as the RUUs are no-wipe.
I would say that turning s-on should be the last thing you do. Get the phone the way you want it. Flashed back to stock, locked bootloader and whatever else you want to do. Then make sure it's all the way you want it. Once you know for sure, then turn s-on. If you turn it on before you flash back to stock and you should somehow end up with it rooted or the have the tampered flag set, whatever the case may be (I've seen plenty of posts where something like this has happened), you'll be out of luck and not be able to fix it. Do it all and then turn s-on. That's my thinking anyway.
robocuff said:
I would say that turning s-on should be the last thing you do. Get the phone the way you want it. Flashed back to stock, locked bootloader and whatever else you want to do. Then make sure it's all the way you want it. Once you know for sure, then turn s-on. If you turn it on before you flash back to stock and you should somehow end up with it rooted or the have the tampered flag set, whatever the case may be (I've seen plenty of posts where something like this has happened), you'll be out of luck and not be able to fix it. Do it all and then turn s-on. That's my thinking anyway.
Click to expand...
Click to collapse
flashing the Stock RUU is the LAST thing you do, to remove root. You need root to turn s-on
edit: you need root to lock the bootloader, but not go S-on. In any event The steps Dottat outlines in his thread says to go S-on first then ruu the stock image
I am considering relocking the bootloader for my HTC U12+. I unlocked it a long time ago (out of habit I guess). So my phone is completely running stock without any modifications. I want to relock the phone to get widewine back to L1, so I'll get Netflix updates and such.
A few questions about relocking that I couldn't find an answer to.
1. When I relock the bootloader will it do a factory reset to the phone? I'm asking because unlocking did.
2. If later on I decide to unlock the relocked bootloader again, do I have to get another unlock-code from HTC? Or is unlocking a relocked bootloader a simpler procedure?
So I decided to do the relocking. During the relocking procedure I was being told on the screen that the phone will be wiped if I continue. It remains to be seen how I'll unlock it later on if I want to.
lvl3 said:
I am considering relocking the bootloader for my HTC U12+. I unlocked it a long time ago (out of habit I guess). So my phone is completely running stock without any modifications. I want to relock the phone to get widewine back to L1, so I'll get Netflix updates and such.
A few questions about relocking that I couldn't find an answer to.
1. When I relock the bootloader will it do a factory reset to the phone? I'm asking because unlocking did.
2. If later on I decide to unlock the relocked bootloader again, do I have to get another unlock-code from HTC? Or is unlocking a relocked bootloader a simpler procedure?
Click to expand...
Click to collapse
2. You have to to go through the HTCDev website procedure (not sure if you can reuse the previous Unlock_code.bin file).
is it possible to get "locked bootloader" instead of "relocked bootloader" and get rid of system status modified?
maslaq said:
is it possible to get "locked bootloader" instead of "relocked bootloader" and get rid of system status modified?
Click to expand...
Click to collapse
No.