I'm trying to unlock the bootloader on my dna that's on 2.06 firmware. Please do not tell me to use moonshine, I have to unlock my bootloader first before trying. I've already had issues with it.
I unlocked my bootloader on earlier firmware (1.xx - I forget the exact version) so I have an old Unlock_code.bin from HTCDev. I already have SuperCID (all 1's), so I figured I didn't need to use jcase's newer method, which said it only worked on devices on 1.x anyway. I went through HTCDev anyway to make sure I could still unlock, but when I put in my device identifier token, I got error 160: MID not allowed.
As I said, I could just use the old Unlock_code.bin, but I want to do this the right way. Do I have to run jcase's exploit (even though it's only supposed to be for 1.x), or should I just use my old unlock code?
SOLVED
The answer is yes, you can use your old Unlock_code.bin, and you may have to. This will only work if you previously unlocked the bootloader and got SuperCID.
Related
Hello all, I used the htc unlock method, but I am not able to flash a different radio version.
Does anyone know how to do that?
(Just booting into bootloader does not do the trick like it would normal unlock methods)
Thanks.
Anyone?
Sent from my PG86100 using XDA App
have you tried the commands
adb reboot bootloader
fastboot boot recovery.img
and flashing the radios from fastboot? or FlashimageGUI (which probably will not work for radios)
I have been wondering this myself. I have not heard of any methods that have come up to allow this recently. Same thing goes for splash images as I havent seen any method for those.
I have an idea of how it may be possible though. Perhaps someone else with a bit more knowledge can chime in to let us know if it is possible or not.
Anyhow.
Being officially unlocked I don't believe that ROOT is an issue like it is on an unofficial method. I know typically you would NOT accept an OTA to prevent the loss of ROOT. However, being an officially unlocked device, I am not sure if it matters.
I know that when I unlocked my device I had to manually unlock it, then I installed my recovery, then I simply flashed SU to it. My thought is that you can take the OTA. If the OTA doesn't work, you may have to re-lock the device, then run the OTA. But I believe the OTA would be safe. Once OTA completed, then flash your unlock token again, put recovery back on, then flash SU again.
Or I believe you could also wait for the new RUU instead of an OTA. Put on stock ROM, re-lock, run RUU, re-unlock, install recovery, flash SU.
The problem is that you may not be able to flash back to the previous radio once you are done.
Any thoughts on this?
UPDATE: I recently (like two minutes ago) learned that an RUU will not update a radio. I was under the impression that they did. Since it will not, I guess the RUU method will not work. Still curious about the OTA method though.
From the HTCDev Q and A:
HTCDev said:
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
yousefak said:
From the HTCDev Q and A:
Click to expand...
Click to collapse
Well, yeah. The S stays on to protect the radio.
But the S would be on regardless if you never rooted to begin with, but an OTA would allow the radio to update. So, my thought is that you can potentially take an OTA with the HTC unlock method and get the new radio.
If it were me, I would save my titanium file to my PC (just as a precaution), I would re-lock my device using fastboot oem lock, then I would run the RUU that matches my current software version. This would return me to stock/unrooted. At this point you should be able to accept an OTA. The OTA updates your radio/software/etc. Once you update, flash the unlock token again, then flash the superuser binary back onto the phone. Now, this would be contingent that HTC doesn't go back on their word and they dont push an OTA that prevents you from unlocking the phone.
Now, Ill admit I am not a developer, so I am not an expert, but it is my understanding that once it is unlocked putting root on the phone is pretty straight forward. You don't have to come up with a root method such as revolutionary, etc. It should simply allow Superuser because it is unlocked. If this is not the case, then Ill admit that my thought process is flawed. However, if it is the case, then why not return to stock, take an OTA, unlock, re-root, use titanium? Like I said, may not be able to return to previous radio, but why would you anyhow?
mildlydisturbed said:
have you tried the commands
adb reboot bootloader
fastboot boot recovery.img
and flashing the radios from fastboot?
Click to expand...
Click to collapse
Can someone tell me how exactly to accomplish the above?
I ran these commands and the it said "Installing update..." but the radio remains the same.
Thanks again.
I am wanting to relock and unroot my phone temporarily to test some things.
Here is my question. I've read several differet ways to relock a bootload and unroot, I was just wanting to make sure I got this right - it seems pretty straight forward. (BTW I'm rooted via regawmod's rooter and I am s-on)
1st - I load to fastboot and run "fastboot oem lock"
2nd - flash RUU
3rd - you're done.
Another question: I've seen someone say you can download the official RUU from the htcdev website. I've never been able to find it there though - I've scoured the whole site. I have found the source code but not the RUU.
That being said, I do have access to the official RUU installer from HTC that Sprint Service & Repair centers use. That would work right?
Thanks.
Nevermind. I got balsy and did it anyway. It worked.
Same situation what did you do to relock the bootloader and unroot your phone and did it get rid of super Su?
Please I'm very curious to know been wondering for months now
I just bought a att htc one off Craig's list and it is tampered/relocked. The phone boots straight into fastboot and there is no operation system on phone. I tried to use ruu to get it back to stock but it freezes at checking hash 5percent. I also tried to fastboot the ruu zip but it had an error verify 12 signatures. Are there any other suggestions that I could try to get an os back on this phone or is this phone pretty much bricked?
Unlock bootloader, install twrp recovery, sideload a rom zip.
There are numerous existing threads that describe how to do each step, just spend a little time reading first.
cschmitt said:
Unlock bootloader, install twrp recovery, sideload a rom zip.
There are numerous existing threads that describe how to do each step, just spend a little time reading first.
Click to expand...
Click to collapse
I don't think I can unlock the relocked bootloader without the token correct? Is there any other way to unlock a locked bootloader without the htcdev token?
crazyfied said:
I don't think I can unlock the relocked bootloader without the token correct? Is there any other way to unlock a locked bootloader without the htcdev token?
Click to expand...
Click to collapse
Yes, you'll need an unlock token.
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...??
BBEgo said:
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
Click to expand...
Click to collapse
Wonders_Never_Cease said:
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...
Click to expand...
Click to collapse
That's weird.... I thought I posted this in the Q&A forum. I was just in there looking for it and I thought it'd gotten deleted or something. Oh well.
Mods, please feel free to correct my goof.
I didn't use HTCDev to unlock. I just did Sunshine and it handled everything. S-off, unlock, and root - Talk about painless! After that I installed a custom recovery (Philz) and I was off to the races.
So I decided to SuperCID my phone so I can install whatever I want. No problem.
Then I tried to install 5.0.1 firmware (4.16.1540.8) so I could run SkyDragon, but the firmware posted on page 1 in the thread would not install- 4.16.1540.8
Kept giving me "FAILED (REMOTE:24 parsing android-info fail)"
I was able to install 4.16.401.9 with no major headaches, once I found a sensible upgrade path. That one is working fine, but I don't understand why 4.16.1540.8 would not install.
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
So now I'm S-off, locked bootloader, PhilZ recovery (put it back on with Flashify), SuperCID, on Lollipop, and I guess everything is ok. But I still don't understand why the phone wouldn't take the firmware.
Any ideas? Thanks in advance.
If you ran sunshine on it,you can run it again i believe on that same device. It should unlock it again,if not then can try htcdev as it also uses fastboot to unlock as long as you can get adb to show needed code.
BBEgo said:
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
Click to expand...
Click to collapse
In the past (at least on my One X EVITA) my understanding was that s-off meant that all security was bypassed. Meaning that bootloader check was effectively bypassed.
This isn't the case for the M8. From what I can tell a LOCKED bootloader still prevents you from flashing anything that isn't signed (anything "unofficial") even if s-off.
However, having an UNLOCKED bootloader doesn't seem to affect anything while s-off. Meaning you can do things like RUU when UNLOCKED (which normally needs to be LOCKED or RELOCKED if s-on).
In short, I don't ever recommend relocking the bootloader if s-off on this device. There isn't any reason to, as far as I can tell. Meaning, having an UNLOCKED bootloader doesn't prevent you from doing anything. However, a RELOCKED bootloader does (even when s-on) prevent some things.
Ok I have 2.49 and no money to buy sunshine at the moment. Is there a way to root and install recovery without S-off? I am on 2.49 Hboot. Verizon HTC Max
very much so sir! i m not sure about carrier versions like your verizon device, but i am using the international one max...and the outline of the procedure is standard and you can find many tutorials on it. here it is briefly:
1. goto htc's dev site, register your device as a dev device, and you will get an unlock code
2. use the unlock code to quickly unlock the bootloader
3. with bootloader unlocked, you can flash any recovery you want
4. with recovery, you can flash the superuser or supersu packages to root
thats it!
s-off gives you some more flexibility, but its not necessary for most modding/tinkering purposes. i have done all but s-off, and haven't yet found a compelling use case for myself in which i would be forced to get s-off...so far!
all the discussions you see on the forum talking about troubles with hboot 2.49 are in the context of achieving s-off. hboot 2.49 does NOT keep you from unlocking bootloader and all that jazz. its specifically a hurdle in the steps to achieve s-off.
finally, there are some doubts about htc's stated versus effective policy regarding warranty status of devices that have received unlock codes from htc's dev site. might want to read up about the pros and cons if you want to be sure about the effect of the bootloader unlocking steps on your warranty.
edit: and i'll also mention here for completeness that unlocking bootloader disables the fingerprint scanner. as always, theres a lot of topics/discussions here on the forum about all the details. i believe the consensus is to lock the bootloader AND clear the "tampered" flag. some say the bootloader status must be "locked" as opposed to "relocked", which is where s-off might become necessary...or some such! haven't quite done any steps yet to enable my fingerprint scanner. don't want to hijack your thread, but that would be my next question if i was you and had just read my post!
Sent from my HTC One max using XDA Free mobile app
ASCIIker said:
very much so sir! i m not sure about carrier versions like your verizon device, but i am using the international one max...and the outline of the procedure is standard and you can find many tutorials on it. here it is briefly:
1. goto htc's dev site, register your device as a dev device, and you will get an unlock code
2. use the unlock code to quickly unlock the bootloader
3. with bootloader unlocked, you can flash any recovery you want
4. with recovery, you can flash the superuser or supersu packages to root
thats it!
s-off gives you some more flexibility, but its not necessary for most modding/tinkering purposes. i have done all but s-off, and haven't yet found a compelling use case for myself in which i would be forced to get s-off...so far!
all the discussions you see on the forum talking about troubles with hboot 2.49 are in the context of achieving s-off. hboot 2.49 does NOT keep you from unlocking bootloader and all that jazz. its specifically a hurdle in the steps to achieve s-off.
finally, there are some doubts about htc's stated versus effective policy regarding warranty status of devices that have received unlock codes from htc's dev site. might want to read up about the pros and cons if you want to be sure about the effect of the bootloader unlocking steps on your warranty.
edit: and i'll also mention here for completeness that unlocking bootloader disables the fingerprint scanner. as always, theres a lot of topics/discussions here on the forum about all the details. i believe the consensus is to lock the bootloader AND clear the "tampered" flag. some say the bootloader status must be "locked" as opposed to "relocked", which is where s-off might become necessary...or some such! haven't quite done any steps yet to enable my fingerprint scanner. don't want to hijack your thread, but that would be my next question if i was you and had just read my post!
Sent from my HTC One max using XDA Free mobile app
Click to expand...
Click to collapse
So I am on Verizon and when I try to unlock through HTC dev it gives me error. I have used the htc dev to unlock many htc devices over the years. I dont remember the error but I am 100% sure HTC dev unlock will not work with my version which is 2.49 and 4.4.2. So I wish you were right I would already be there. Thank you for your in depth post
Problem solved!
Bought sunshine!