Is there any way to bypass HTC's new pre-bootloader unlock permissions in developer options?
I'm trying to fix a soft-bricked phone that will only boot into download mode.
It is currently relocked, S-ON, stock recovery. I'm not sure what was done to get it in this state as I'm fixing for a friend.
I figure the only option to get back to stock (or working condition) is by acheiving S-OFF which entails:
1. Unlocking the bootloader
2. Flashing TWRP
3. Flashing any ROM in order to run Sunshine S-OFF
4. Proceed with stock RUU flashing
But the bootloader is the real roadblock right now. It blocks me at fastboot.
Related
Edit:
I didn't know you could run the RUU while the phone was in the bootloader. It boots fine now. Mods can delete this if they want.
Ok, so I have to bring my phone into Sprint so I needed to relock the bootloader and unroot the phone. I used the all in one tool to relock it and now it just constantly goes into the bootloader, no matter what option I pick. Does anybody have any ideas how I can get it out so I can unroot it and run the RUU?
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
shawnten said:
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
Click to expand...
Click to collapse
If the RUU doesn't work, the other two alternatives are to attempt to flash the stock system.img and stock boot.img through fastboot .. although I'm not sure this will work with S-ON, depends on whether or not the device is locked/unlocked via HTC's official method.
Also, the second alternative, could use the PG*zip file which is stored inside the RUU. the zip file can be extracted from the RUU and placed on the root of the sdcard. Then the bootloader will grab this file and flash, essentially performing the same thing as the RUU would.
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.
Hey Everyone! So i will be receiving my M8 i got used in the mail on monday and i'm doing some research because it is softbricked due to no OS being installed. It is (presumably) S-Off with Bootoader locked and "possibly" no custom recovery. What i'm planning to do is once the battery is charged completely.
-Connect it to my PC (windows)
-Power into fastboot
-Run the stock AT&T RUU and get everything running and up to date.
From there i will be unlocking the bootloader, custom recovery, root, and all the good stuff.
I'm just wanting to know from the way more knowledgeable folks then i when it comes to this stuff, is if this is the proper procedure. Is there anything else i should do first or after? Any help will be great! I'll know more tomorrow night on if recovery is installed or not, but i'm going with the opinion that there is no custom recovery, as i feel this would be harder.
any help would be GREATLY appreciated!
I agree with the above described approach. Especially since its not clear what the previous owner did (appears previously bootloader unlocked, s-off, then possibly a botched return to stock attempt?) its good to run the AT&T RUU to return to a full stock "baseline" image to all partitions.
Since you are going to run RUU, it doesn't matter whether custom recovery is currently installed or not. The RUU will install the stock recovery image.
After RUU, unlock the bootloader via HTCDev.com. Then install current version TWRP and flash SuperSU 2.46 to obtain root (older versions SuperSU won't work on Lollipop - common mistake).
redpoint73 said:
I agree with the above described approach. Especially since its not clear what the previous owner did (appears previously bootloader unlocked, s-off, then possibly a botched return to stock attempt?) its good to run the AT&T RUU to return to a full stock "baseline" image to all partitions.
Since you are going to run RUU, it doesn't matter whether custom recovery is currently installed or not. The RUU will install the stock recovery image.
After RUU, unlock the bootloader via HTCDev.com. Then install current version TWRP and flash SuperSU 2.46 to obtain root (older versions SuperSU won't work on Lollipop - common mistake).
Click to expand...
Click to collapse
Thank you so much Redpoint! I only have a small amount of knowledge with this area. I've sideloaded an OS over ADB due to a mistake i made with no OS on an old tablet, but never had to deal with possibly stock recovery with a locked bootloader, so knowing my approach will presumably work is a real relief.
Thank you again!!!:good::fingers-crossed: