Database Users

[HOW-TO] bootloader unlock 4.67.651.3 OTA

1. Unlocking bootloader via htcdev.com (selecting All Other Supported Models)
2. Flashing recovery via fastboot (./fastboot flash recovery cwm-4.0.1.4-supersonic.img)
3. Reboot recovery and flash latest su.
4. Profit.
PROOF:
Code:
[email protected] ~/evo_s-off $ ./fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
===========bla-bla-bla=============
---checking my e-mail for Unlock_code.bin---
[email protected] ~/evo_s-off $ ./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
OKAY
[email protected] ~/evo_s-off $ ./fastboot flash recovery cwm-4.0.1.4-supersonic.img
sending 'recovery' (3074 KB)... OKAY
writing 'recovery'... OKAY

this is very strange. nobody interested in unlocking bootloader?

there is no official info, but works fine for me.

I'm one of the ones on the newest ota. This helps out a lot, thank you

I already have root, but I am rooting someone else's phone that has new hboot. Thanks!
Sent from my PC36100 using Tapatalk

people with unlocked bootloaders please leave comments here.

Total noob mistake.
OK i ended up updating my evo to the new 4.67.651.3 update. big mistake
I ended up stumbling across this post. (thx wardriva)
I was able to unlock the bootloader and use the ADB method mentioned in this thread to flash recovery.
after looking around I came across brad560's thread and flashed the deodex'ed rom with no problems.
so far everything is working. I also kept looking around and came across the Collection Project (thx Tommytomatoe) and flashed the hot spot hack by SOS. so far its working.
still looking to see if someone has found a workaround with the S-OFF or if revolutionary will support it.
Thx to all the DEV's.

wardriva said:
this is very strange. nobody interested in unlocking bootloader?
Click to expand...
Click to collapse
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)

coldroy said:
still looking to see if someone has found a workaround with the S-OFF or if revolutionary will support it.
Click to expand...
Click to collapse
you don't need S-OFF with unlocked bootloader. you can flash any rom you want with any kernel you wish. i just checked.

Tekn010933 said:
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
Click to expand...
Click to collapse
what are you talking about? the latest OTA let us unlock bootloader.

wardriva said:
what are you talking about? the latest OTA let us unlock bootloader.
Click to expand...
Click to collapse
my fault, apologies reading to fast and totally thinking rooting instead unlocking??lol!

hmmm. From the little bit I had read on Evo 3d forum, I thought that even with unlocked bootloader, s-on means no flashing of kernels? Or maybe it's different on 3d cuz it uses EMMC ? Does a custom kernel remain after reboot?
Would love clarification from anyone who knows better than I. Thanks.
Also, this comes just in time for evos EOL status lol. Coincidence ?
Sent from my PC36100 using xda premium

Can you still write to the system or uninstall bloatware with the unlocked bootloader (which is still S-ON)?

To answer some people's questions unlocking with the HTC tool allows you to write to boot(kernel), recovery, and system. This means you can flash custom recovery and ROMs to your hearts content. You will still require official HTC signed updates to change: bootloader, radio, nv, pri, wimax, etc because technically you are still S-ON.
Here is the FAQ from HTC on unlocking the bootloader: http://htcdev.com/bootloader/faq
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse

shortydoggg said:
Can you still write to the system or uninstall bloatware with the unlocked bootloader (which is still S-ON)?
Click to expand...
Click to collapse
Just curious about the new bootloader, because based on past bootloaders I've had,
If you are rooted, but still S-ON, you can delete any bloatware (system apps) that you want, but after rebooting the phone it all returns. Why, because there is a backup of how your partitions were on the phone that cannot all be flashed unless you are S-OFF. When you're S-ON, any changes you made to the original partitions, (especially recovery and system if system is done inside the operating system) will be voided the next time you reboot the phone. That is also why you would need to connect your phone to your computer every time you needed to flash a custom ROM (if this is still the case with the new bootloader), because the backup (stock Recovery) is always restored on reboot.
You can change the system partition outside of the operating system by recovery, however; which is the reason why you can still flash custom ROMs (if the new bootloader behaves the same as the older ones).
I'm just curious if anyone with the new (unlocked) bootloader with S-ON can confirm this.

shortydoggg said:
Just curious about the new bootloader, because based on past bootloaders I've had,
If you are rooted, but still S-ON, you can delete any bloatware (system apps) that you want, but after rebooting the phone it all returns. Why, because there is a backup of how your partitions were on the phone that cannot all be flashed unless you are S-OFF. When you're S-ON, any changes you made to the original partitions, (especially recovery and system if system is done inside the operating system) will be voided the next time you reboot the phone. That is also why you would need to connect your phone to your computer every time you needed to flash a custom ROM (if this is still the case with the new bootloader), because the backup (stock Recovery) is always restored on reboot.
You can change the system partition outside of the operating system by recovery, however; which is the reason why you can still flash custom ROMs (if the new bootloader behaves the same as the older ones).
I'm just curious if anyone with the new (unlocked) bootloader with S-ON can confirm this.
Click to expand...
Click to collapse
S-ON + Locked means that all partitions(other than data / sdcard) are write protected. The only way to write to the partitions is with an official OTA or RUU signed by HTC. The reason why "deleted" items return after reboot is because the deletion never actually occurred on the partition itself. It was temporary because the write was blocked by the security.
S-ON + Unlocked means that HTC removed the write protection from: boot, recovery, and system.
For HTC's official FAQ see my post immediately before yours.

illogos said:
To answer some people's questions unlocking with the HTC tool allows you to write to boot(kernel), recovery, and system. This means you can flash custom recovery and ROMs to your hearts content. You will still require official HTC signed updates to change: bootloader, radio, nv, pri, wimax, etc because technically you are still S-ON.
Here is the FAQ from HTC on unlocking the bootloader: http://htcdev.com/bootloader/faq
Click to expand...
Click to collapse
Or get a stock(4.67-Android 2.3.5) ROM that has -Signature Verification disabled which will allow you to update the radios and such.
Is how it use to be done

.Elite_The_King. said:
Or get a stock(4.67-Android 2.3.5) ROM that has -Signature Verification disabled which will allow you to update the radios and such.
Is how it use to be done
Click to expand...
Click to collapse
thanks Cap. but I was not rooted before OTA. and after OTA there is no other way to root or flash custom ROM.

WIP Guide for achieving S-OFF after unlocking Bootloader with HTCDev.com
[GUIDE][WIP] How to achieve S-OFF after unlocking 2.18 HBOOT with HTCDev.com - No More Watermark! )
Still working on the details, but a shell of the instructions is there .

Tekn010933 said:
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
Click to expand...
Click to collapse
DISCLAIMER: I'm a noob in this root world.....and enjoying the freedom to use my phone as I choose.
With that said, if you do not recommend updating OTA, then how would a person do such? I'm asking for my friends who are run stock on their phones.

[Q] problems with CWM recovery

Hello everyone. I've been reading about CM7 and find this:
http://forum.xda-developers.com/showthread.php?t=1257574&highlight=cm7+no+nightly
So i started to do the step by step and i'm stucked in the 3rd step "current rom backup" when i see" android recovery" and press volume up It says " failed to boot 2 starting rsd", and nothing happens. I've to take the battery Out and everything runs normal.
Any ideas?
Sorry about my english thanks!

Hi, probably you CWM or Kernel is corrupted, try to install it again e probably you´ll get successful...

soadcma said:
Hi, probably you CWM or Kernel is corrupted, try to install it again e probably you´ll get successful...
Click to expand...
Click to collapse
i'd unistall cwm from aplications, but it still the same.
cwm was flashed, is there a way to unflash it?

I would use fastboot and reinstall romracers recovery

If you flash CWM recovery you need to unlock your bootloader.
I had the same problem, unlocking it fixed it.

Since this gets asked every other day, here is a more complete explanation.
A locked bootlloader verifies that the recovery partition is correctly signed by Moto.
The CWM does not have this signature. So when you flashed that, the bootloader tosses the error that recovery will not load.
Either:
Follow instructions elsewhere to unlock your bootloader
or
Flash back to a stock recovery.
This same thing could happen if you flash a ROM that changes the kernel, boot partition or partition table (to a non moto signed one) to a device with a locked bootloader. That is why some ROMs require an unlocked bootloader and some do not. The system partition is not signed, so much can be safely changed w/o unlocking. A recovery or kernel can not use custom versions w/o unlocking.
Here is a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=1262266

pienne said:
If you flash CWM recovery you need to unlock your bootloader.
I had the same problem, unlocking it fixed it.
Click to expand...
Click to collapse
Thanks for answer, i will unlock the bootloader

exwannabe said:
Since this gets asked every other day, here is a more complete explanation.
A locked bootlloader verifies that the recovery partition is correctly signed by Moto.
The CWM does not have this signature. So when you flashed that, the bootloader tosses the error that recovery will not load.
Either:
Follow instructions elsewhere to unlock your bootloader
or
Flash back to a stock recovery.
This same thing could happen if you flash a ROM that changes the kernel, boot partition or partition table (to a non moto signed one) to a device with a locked bootloader. That is why some ROMs require an unlocked bootloader and some do not. The system partition is not signed, so much can be safely changed w/o unlocking. A recovery or kernel can not use custom versions w/o unlocking.
Here is a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=1262266
Click to expand...
Click to collapse
Thanks for answer, i'm Out Of town, so when i came back i will do It and I will ley you know.
Thanks!

[Q] Anyone knows the difference between bootloader 4.13 and 4.18 ?

Bootloader is the last thing I would like to touch unless it is absolutely necessary. So is wondering what is the key changes that warrant to flash it.

chimpanzeexda said:
Bootloader is the last thing I would like to touch unless it is absolutely necessary. So is wondering what is the key changes that warrant to flash it.
Click to expand...
Click to collapse
I've been wondering the same... Also, excuse my ignorance, but bootloader is not updated when you do OTA from 4.21 to 4.22 ? It has to be update separately?

dalanik said:
I've been wondering the same... Also, excuse my ignorance, but bootloader is not updated when you do OTA from 4.21 to 4.22 ? It has to be update separately?
Click to expand...
Click to collapse
I upgraded mine using the adb sideload method, and it also changed my bootloader to 4.18. I don't know if there are any significant changes, but I think its best to upgrade to the latest bootloader as you will have the latest and greatest, and most development will stem using 4.18 anyway. So just upgrade.

dalanik said:
I've been wondering the same... Also, excuse my ignorance, but bootloader is not updated when you do OTA from 4.21 to 4.22 ? It has to be update separately?
Click to expand...
Click to collapse
I'm also wondering... by the way, dalanik, the bootloader IS updated via the OTA... it's in the UPDATER SCRIPT. (And it's how I got updated).
Code:
...
....
ui_print("Writing bootloader...");
package_extract_file("bootloader.raw", "/dev/block/platform/sdhci-tegra.3/by-name/USP");
...
..
Interestingly, in the FLASH-ALL.bat/sh script, in the FACTORY IMAGE of JDQ39, the new bootloader is flashed by the more traditional method, using fastboot...
Code:
..
...
fastboot flash bootloader bootloader-grouper-4.18.img
fastboot reboot-bootloader
...
..
----
Anyway, I've subsequently NANDROID restored back to my 4.2.1 based CyanogenMod ROM... with the updated bootloader... only issue is, when in FASTBOOT mode, the Vol UP/DOWN keys, when USB plugged in (to PC or charger, it doesn't matter), sometimes become non-responsive - meaning I can't select recovery, for example. It's a minor quirk, easily resolved by disconnecting and then reconnecting again.
What we need here, is a BOOTLOADER guru; some guy, who knows everything there is to know about BOOTLOADERS... I'm sure there is one out there, somewhere.
Rgrds,
Ged.

If you update your N7 OTA, everything will be updated. You DO NOT NEED to update the bootloader. It's a whole package that is ready for installation.

But I cannot use OTA without reverting back a number of things
I would assume bootloader in android is just the equivalent of GRUB. The reason I don't want to touch it is that it is if I am not mistaken the supervisor of the device so if I get a bad flash, I would lose access to it even in fastboot.

GedBlake said:
Interestingly, in the FLASH-ALL.bat/sh script, in the FACTORY IMAGE of JDQ39, the new bootloader is flashed by the more traditional method, using fastboot...
Click to expand...
Click to collapse
In fact, the bootloader actually flashes it in place in both instances.
"USP" (or "staging") is kind of a garbage partition - do a dd (read dump) of yours right now and you will easily convince yourself that the bootloader ain't in there.
Whenever a hardware reset occurs, the bootloader regains control of the device. I have to presume that on every hardware reset cycle, the existing bootloader inspects the USP. Clearly it can not simply blind-flash whatever is in there; that would suggest that the the bootloader blob thrown into USP has a MIC (crypto Message Integrity Check) and the existing bootloader can perform a signing check on it.
Don't know if the same is true of a fastboot flash - but then who wants to run an experiment where they purposely flash garbage into the bootloader in order to find out?
On other (HTC) devices I had, the bootloader would inspect (bootloader version) strings stored in the misc partition, and resolutely refuse to flash factory ROM files if it got a whiff of a potential downgrade install. That was easily overcome by byte-patching the misc partition from a rooted OS, though.
[speculation]With this USP -> real_bootloader_location funny business going on, I am wondering - if the MIC key is version stepped (that is, the public key provided in the current version of the bootloader is updated with every revision, and the *next* version of the bootloader is signed with this key) then this would create a upgrade-only-lockstep sequence.[/speculation]
Has anybody ever downgraded their bootloader - either with a "recovery-flashable zip", or fastboot? Just curious.

bftb0 said:
Has anybody ever downgraded their bootloader - either with a "recovery-flashable zip", or fastboot? Just curious.
Click to expand...
Click to collapse
I have downgraded my bootloader for my N7 from some version to the 3.44 then upgraded to 4.13 then upgraded to 4.18. The reason I downgraded I cannot remember.
And no I did not use a recovery flashable zip, I went into fastboot and flashed it with an img.

Updates through custom recovery with a locked bootloader possible?

If I locked my bootloader, can I update SuperSU (zip) or TWRP (img) using TWRP --> Install?
I'm already aware that it won't allow me to flash custom ROMs, custom recoveries or use fastboot commands.
What does having a locked bootloader prevent me from doing?
Thank you

AndrewDam said:
If I locked my bootloader, can I update SuperSU (zip) or TWRP (img) using TWRP --> Install?
I'm already aware that it won't allow me to flash custom ROMs, custom recoveries or use fastboot commands.
What does having a locked bootloader prevent me from doing?
Thank you
Click to expand...
Click to collapse
The better question is why would you have a locked bootloader? If you have any kind of boot loop or error you will end up with a paper weight that will have to be sent off for repairs when its easily fixed with an unlocked bootloader.

murphyjasonc said:
The better question is why would you have a locked bootloader? If you have any kind of boot loop or error you will end up with a paper weight that will have to be sent off for repairs when its easily fixed with an unlocked bootloader.
Click to expand...
Click to collapse
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).

AndrewDam said:
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).
Click to expand...
Click to collapse
I would say it's much more likely you brick your phone due to having a locked bootloader than someone else getting their hands on your phone and actually having the knowledge to cause trouble for you.

to relock your bootloader you must have FULLY STOCK firmware back on your device, relocking with anything in the phone being custom can result in a paperweight

Having a rooted phone is more vulnerable than a unlocked bl phone. Dont lock bl back unless you are full stock (I would still say dont though)

AndrewDam said:
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).
Click to expand...
Click to collapse
It's more secure, sure. But if you take care of your phone it doesn't fall into the wrong hands. Plus, if you have TWRP installed still a tech savvy thief (one who understands what a locked bootloader means) can easily flash a ROM and boot into the phone. As sometime else pointed out, the chances of you ending up with a brick are higher than the chances of someone getting your phone.
Sent from my Nexus 6P

Ok that makes sense to not lock the bootloader. Thanks for the information everyone!

How to re unlock bootloader

If go to stock and relock bootloader for OTA, what is procedure to unlock again? Do you go back to the Moto site for a new code, or will they expect you to have the original unlock code (thus you could be outta luck if you bought the phone used , with an unlocked bootloader.)

The procedure is the same as when you first unlocked, although if you have the original unlock code you can skip getting a new one from Moto's site (it's the same code anyway), same rules apply, it will wipe everything and you must have OEM Unlocking in Developer options enabled as when the bootloader is relocked this option is turned off and must be turned on again manually.
Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc).

"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?

hometech99 said:
"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?
Click to expand...
Click to collapse
Here ya go..
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

hometech99 said:
"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?
Click to expand...
Click to collapse
Just look in my sig... if you read there are links to firmware, and instructions to lock and flash, or just flash the factory image. I would recommend flashing the complete system image though, not just the pieces.

acejavelin said:
I would recommend flashing the complete system image though, not just the pieces.
Click to expand...
Click to collapse
..but your flashboot instructions show the pieces. Did you modify the process, and get the whole system image?
Thanks!

hometech99 said:
..but your flashboot instructions show the pieces. Did you modify the process, and get the whole system image?
Thanks!
Click to expand...
Click to collapse
No, I meant each piece of the full image, don't skip any parts.