This process has been done with the HTC International version available in Australia.
Im sure everyone would appreciate follow up from others to confirm which versions of the phone this process works with.
The process below assumes a small amount of familiarity with HTC unlock process AND WILL WIPE THE DATA FROM YOUR PHONE!
The process is basically the same as ever with a few variations
Install adb
Go to http://www.htcdev.com/bootloader and sign up, click unlock bootloader
In the device selection drop-down select "any other supported device"
Boot into "Download Mode" - Which is the equivalent of fastboot. (shutdown your phone, hold power+volume down until you boot into this mode). This is the mode with the black background and red text
Connect phone to PC, and issue "fastboot oem get_identifier_token"
Copy the code into the returned by adb into space on HTCs website
Get the email, download the attachment and issue "fastboot flash unlocktoken Unlock_code.bin"
I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.
Always good to know we can root the new flagship
Super-Veloce said:
I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.
Click to expand...
Click to collapse
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Really?? Damn..
I keep getting:
Code:
C:\WINDOWS\system32>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Tried it on 2 different systems :S
What mode was your phone in? Were you in download mode? Or in the bootloader?
daveh86 said:
What mode was your phone in? Were you in download mode? Or in the bootloader?
Click to expand...
Click to collapse
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...
EndoSurf said:
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...
Click to expand...
Click to collapse
Thanks, I've added a note in my comment that mentions that download mode is the one with black background and red text.
And how i will make it S-Off?
Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
By being patient... the device is not even available in most regions yet, give developers a little time would you.
For Verizon test M9's, can't even pull identifier token. Fastboot command yields "FAILED (remote: unknown command)," which is interesting because I used fastboot to successfully flash TWRP then root.
jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Is there a way to s-off? Ive seen some have already done it, but how?
Test devices come S-OFF.
hgoldner said:
Test devices come S-OFF.
Click to expand...
Click to collapse
Or you can give the Phone to a shop / repair centre to s-off it
In Germany you can do it at:
http://www.gsm-europe.de/epages/635...3/Products/htc_soff/SubProducts/htc_soff-0001
Its a shop in Berlin they do s-off and supercid
And they can do it on the Onde M9
Only bad thing they cant Unlock bootloader it without HTC Dev.
So You get your phone back with S-Off and with Super Cid but Boodloader is Locked and you must Unlock it via HTC dev
because for Unlock via Fastboot you need root on Android 5
I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?
Prasad said:
I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?
Click to expand...
Click to collapse
Didn't notice any loss after unlocking M9 ..
jauhien said:
Didn't notice any loss after unlocking M9 ..
Click to expand...
Click to collapse
Thank you! Now I can confidently proceed when the device arrives in a couple hours.
Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
you're gonna have to wait a while for that
Been a long time since I unlocked a bootloader. But I don't lose any OTA functionality do I?
Sent from my HTC One M9 using XDA Free mobile app
Related
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
I have a moto x pure pre release phone. It was a model that was issued before the initial release of moto x pure. I have tried to get the unlock code with no success. I get a failed error message. I have tried this on windows 10 and Linux. I can successfully recognize the device on fastboot and adb. However, no unlock code. I am now thinking somehow the phone is locked and unable to get this code. I'm thinking about selling this phone and getting a new one. I would like any feedback if you think I will have the same issue or if the pre release may be locked.
Sent from my Nexus 6 using XDA Free mobile app
I had no issue unlocking a phone bought directly from Motorola on November.
jcasares said:
I had no issue unlocking a phone bought directly from Motorola on November.
Click to expand...
Click to collapse
Was it a pre-release version? My guess is no.
Did you go into settings and flip the unlock switch? Hard to help when you don't list the steps you took to unlock.
lafester said:
Did you go into settings and flip the unlock switch? Hard to help when you don't list the steps you took to unlock.
Click to expand...
Click to collapse
I installed Android sdk and Motorola driver. Then enabled USB debugging and checked OEM unlock. Then booted into bootloader. Then typed fastboot OEM get_unlock_data. Then it fails to get information.
brholt6 said:
Was it a pre-release version? My guess is no.
Click to expand...
Click to collapse
It is special phone specifically designed to show off the phone before launch.
droc83 said:
I installed Android sdk and Motorola driver. Then enabled USB debugging and checked OEM unlock. Then booted into bootloader. Then typed fastboot OEM get_unlock_data. Then it fails to get information.
Click to expand...
Click to collapse
Eng boot loader by chance ? Did you try fast oem unlock?
Sent from my SM-T810 using Tapatalk
I was simply answering his doubt about purchasing a new one and facing the issue of unlocking the bootloader again.
He won't have this issue anymore with a unit purchased from Motorola.
dottat said:
Eng boot loader by chance ? Did you try fast oem unlock?
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
What does fast oem unlock do? Do you mean fastboot oem unlock? I didn't try either one.
droc83 said:
What does fast oem unlock do? Do you mean fastboot oem unlock? I didn't try either one.
Click to expand...
Click to collapse
Yes dang keyboard.
Sent from my XT1575 using Tapatalk
droc83 said:
It is special phone specifically designed to show off the phone before launch.
Click to expand...
Click to collapse
Ya, I wasn't asking what a pre-release version was. I think you misread.
dottat said:
Yes dang keyboard.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I tried fastboot oem unlock. It is asking for a code which I can't get.
Did you go to moto and request unlock?
The code you need you can get it on the Motorola support site (I believe this).
jcasares said:
The code you need you can get it on the Motorola support site (I believe this).
Click to expand...
Click to collapse
I need the code from my phone to do this. That is where my trouble is. Everytime I enter fastboot oem get_unlock_data it gives me this.
C:\SDK\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
lafester said:
Did you go to moto and request unlock?
Click to expand...
Click to collapse
They won't help with unlocking my bootloader. They just refer to a website on how to do it. I have told them I believe something is wrong with the phone but they don't want to help with this. I think I am going to just give up and sell the phone and cut my losses.
So why dont you actually follow the process for Bootloader unlock on Moto's Site?
droc83 said:
I need the code from my phone to do this. That is where my trouble is. Everytime I enter fastboot oem get_unlock_data it gives me this.
C:\SDK\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Did you try flashing the stock factory images in fastboot, then rebooting and trying the process once more? You could have an odd boot loader version or something.
Sent from my XT1575 using Tapatalk
dottat said:
Did you try flashing the stock factory images in fastboot, then rebooting and trying the process once more? You could have an odd boot loader version or something.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Do you have a link on how to do this?
fkofilee said:
So why dont you actually follow the process for Bootloader unlock on Moto's Site?
Click to expand...
Click to collapse
I did follow these steps. However, I have to send them a code from my phone which I cannot get.
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
fastboot oem config fsg-id " "
Click to expand...
Click to collapse
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.
ChazzMatt said:
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.
Click to expand...
Click to collapse
mcg24.251-5-5
Fantastic. Yeah, I figured that had to be typo.
Will make a lot of people happy.
I will try now
KARIM9377 said:
I will try now
Click to expand...
Click to collapse
Yes, great news, right?
jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?
TheSt33v said:
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?
Click to expand...
Click to collapse
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.
Oh My Lord. @jcase and @autoprime do it again! Even though mine is unlocked my replacement 32gb isnt and this may make me buy a new screen for it to use! Looks like i know what im doing on my day off tomorrow. Transplanting this screen back onto its orginal donor and unlocking that sucker
autoprime said:
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.
Click to expand...
Click to collapse
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
no, pressing volume down or vol dwn + pwr should not interfere with sunshine.
whichever method people find easier.. i'd assume not everyone will be able to catch it on the initial reboot after sunshine completes.
i'd just avoid pressing buttons while sunshine is still running.. but once the screen shuts off have at it.
also, not sure how it is with the turbo but on my g4 play i do not have to force a 'power down' while phone is in bootloop. i just wait for bootloop cycle to turn screen off and then quickly press the button combo to go into fastboot (volume down + power for g4 play).
Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****
FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
killer520 said:
Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****
Click to expand...
Click to collapse
ChazzMatt said:
FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
Click to expand...
Click to collapse
Those instructions were in autoprime's OP, so they did make it into my guide.
need more help
TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one
KARIM9377 said:
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one
Click to expand...
Click to collapse
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.
TheSt33v said:
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.
Click to expand...
Click to collapse
thanks for your help
can you please update the TWRP
KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
What @TheSt33v said.
This link is to the most recent TWRP with @bhb27 mods for our Quark phones. @bhb27 is our official TWRP maintainer. He's why our TWRP has official status. But he also builds personalized versions which include some features/mods for our phones that other TWRP versions do not have, mods specifically for our Quarks. His modded versions are always better than the versions on the TWRP website (which again are only there due to his efforts).
On that page below you want the modded TWRP with the most recent date -- will always be the one listed at the bottom.
https://www.androidfilehost.com/?w=files&flid=39562
need help
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
i need stack firmware to flash it with my locked droid turbo xt1254 MCG24.251-5-5 with tool to falsh it
For now, S-OFF from SunShine on the htc u11 is temporary. Changes you make while S-OFF will stay, they are not temporary, just the S-OFF flag is. All the same features, with exception of the ability to use custom hboot/aboot. Seriously, aboot patchers, don't bother trying at this point. Once you reboot into Android or Recovery, the device will reset back S-ON.
Changing mid, changing cid, downgrading etc all still work fine. If you want to change it a second time, just run sunshine again.
If/when a forever s-off comes, those with temp s-off will be upgraded at no cost.
jcase said:
For now, S-OFF from SunShine on the htc u11 is temporary. Changes you make while S-OFF will stay, they are not temporary, just the S-OFF flag is. All the same features, with exception of the ability to use custom hboot/aboot. Seriously, aboot patchers, don't bother trying at this point. Once you reboot into Android or Recovery, the device will reset back S-ON.
Changing mid, changing cid, downgrading etc all still work fine. If you want to change it a second time, just run sunshine again.
If/when a forever s-off comes, those with temp s-off will be upgraded at no cost.
Click to expand...
Click to collapse
Thanks man. I been holding off unlocking for a while waiting for this to come.
Many thanks @jcase for explanation. What about 2PZC RUU zip files flashing in case of temporary S-OFF? You know device reboots many times. Can we convert my devices to different variants?
Sent from my HTC U11 using XDA Labs
blueberry60 said:
Many thanks @jcase for explanation. What about 2PZC RUU zip files flashing in case of S-OFF? You know device reboots many times. Can we convert my devices to different variants?
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
It only clears if booting into android or recovery. You can reboot into download/bootloader without clearing it
jcase said:
It only clears if booting into android or recovery. You can reboot into download/bootloader without clearing it
Click to expand...
Click to collapse
Deleted
Sent from my HTC U11 using XDA Labs
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
what's wrong with that? it is the same for me since I unlocked the bootloader. 2 months ago. both unknown and modified.
also can confirm now all works, changed CID twice (don't ask)
velimirchek said:
it is the same for me since I unlocked the bootloader. 2 months ago. both unknown and modified.
Click to expand...
Click to collapse
Same here.
velimirchek said:
changed CID twice (don't ask)
Click to expand...
Click to collapse
Why did you change CID twice?
Kisakuku said:
Same here.
Why did you change CID twice?
Click to expand...
Click to collapse
Because of @tbalden and you
I changed to 060 and then to 622.
Kisakuku said:
Is it safe to flash custom splash images?
Click to expand...
Click to collapse
I'll answer my own question. No issues flashing custom splash images in bootloader (nb0) or download mode (zip with android-info.txt), but obviously can't use recovery-based scripts (no S-OFF in recovery). Splash images made for the 10 work fine, since the screen resolution hasn't changed.
Kisakuku said:
I'll answer my own question. No issues flashing custom splash images in bootloader (nb0) or download mode (zip with android-info.txt), but obviously can't use recovery-based scripts (no S-OFF in recovery). Splash images made for the 10 work fine, since the screen resolution hasn't changed.
Click to expand...
Click to collapse
Thanks, I would have answered you but was sleeping
qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
OpenDSP should show unknown while s-on, that is normalm. Modified is normal as well, as you have an unlocked modified phone. You can clear that with a ruu most likely
My understanding with S-Off was that the bootloader can be unlocked and relocked without HTC noticing - is that the case?
For what it's worth I've not had a device fail on me over the years, but given their recent change of policy towards unlocking, the the screen issues and etc, I've not placed a custom ROM on this phone incase it does go all wrong and I need the warranty...
Could someone please confirm?
Doughnut said:
My understanding with S-Off was that the bootloader can be unlocked and relocked without HTC noticing - is that the case?
Click to expand...
Click to collapse
Support for S-OFF Locked is coming at some point in the future.
Follow this thread thanks Jcase for your hard work
jcase said:
OpenDSP should show unknown while s-on, that is normalm. Modified is normal as well, as you have an unlocked modified phone. You can clear that with a ruu most likely
Click to expand...
Click to collapse
Nope, flashing RUU and even relocking bootloader it stays modified.
velimirchek said:
Nope, flashing RUU and even relocking bootloader it stays modified.
Click to expand...
Click to collapse
At least on the HTC 10 S-OFF/Inlocked/Modified became S-OFF/Unlocked/Official after flashing a RUU Using the SD card method. It didn't when using an exe. Maybe this needs permanent S-OFF.
Sent from my HTC U11 using XDA Labs
Changed CID to superCID and... and I think there isn't much more that we need to do with S-OFF.
The downside of this method is the possibility to lose the ability go get S-OFF with future updates.
qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
velimirchek said:
Nope, flashing RUU and even relocking bootloader it stays modified.
Click to expand...
Click to collapse
will look into it
SunShine v3.5.8
Enhanced HTC U11 S-OFF Support
Is anyone tried to unlock bootloader of there nothing phone 1
hasnainali2404 said:
Is anyone tried to unlock bootloader of there nothing phone 1
Click to expand...
Click to collapse
I can't wait to get my hands on the device.
Think you can unlock the bootloader with fastboot/adb (same as with Nexus/Pixel/Oneplus-devices) no?
Hey!
After enabling OEM Unlock in the developer options, the commands to unlock it are:
fastboot flashing unlock
fastboot flashing unlock_critical
Hope this helps.
What about relocking?
Krullendhaar said:
What about relocking?
Click to expand...
Click to collapse
same commands, just change "unlock" with "lock" ^^.
I like old OnePlus brand/Carl Pei for that, Root Friendly
No Knox, No 169 hours Waiting Period or Forbidden Unloack Bootloader.
It's premature to say whether this will be possible or not, as the Phone(1) was released only 5 days ago.
But knowing Carl, I think that everything will be allowed on this smartphone so that it can be used by many people.
It will be a while before we have a custom recovery and therefore can develop around the Phone(1).
But the kernel is already available for developers which is a good sign.
Post with link for Phone(1) Kernel
@gigantino said:
Hey!
After enabling OEM Unlock in the developer options, the commands to unlock it are:
fastboot flashing unlock
fastboot flashing unlock_critical
Hope this helps.
Click to expand...
Click to collapse
Thanks man, definitely helps
Sib64 said:
It's premature to say whether this will be possible or not, as the Phone(1) was released only 5 days ago.
But knowing Carl, I think that everything will be allowed on this smartphone so that it can be used by many people.
It will be a while before we have a custom recovery and therefore can develop around the Phone(1).
But the kernel is already available for developers which is a good sign.
Post with link for Phone(1) Kernel
Click to expand...
Click to collapse
if you're a developer ,know this, I love you guys for the stuff you domake us proud
Does unlocking bootloader wipe my data? If yes, is there a way to circumvent this?
abrattic said:
Does unlocking bootloader wipe my data? If yes, is there a way to circumvent this?
Click to expand...
Click to collapse
Yes!! No!!
abrattic said:
Does unlocking bootloader wipe my data? If yes, is there a way to circumvent this?
Click to expand...
Click to collapse
Yes! Unlocking your phone will always wipe your data!
And No! if you want to unlock your phone, there is no way around the data wipe at the moment
Is it able to retain L1 status after unlock?
After unlocking (without root, unmodified partitions):
I still have L1 wildvine ("DRM Info").
Safetynet CTS profile match fails.
I'm missing play protect certification.
I can still apply OTAs. (just did 1.1.0 -> 1.1.2)
dedors said:
After unlocking (without root, unmodified partitions):
I still have L1 wildvine ("DRM Info").
Safetynet CTS profile match fails.
I'm missing play protect certification.
I can still apply OTAs. (just did 1.1.0 -> 1.1.2)
Click to expand...
Click to collapse
You need to install Magisk (and also root your device) in order to install Universal safetynet fix module and ofc actually pass safetynet. Worked fine on my device.
I have unlocked many phones but never used this command "fastboot flashing unlock_critical"
Why do we have to use that command aswell?
bariz143 said:
I have unlocked many phones but never used this command "fastboot flashing unlock_critical"
Why do we have to use that command aswell?
Click to expand...
Click to collapse
You don't need to.
bariz143 said:
I have unlocked many phones but never used this command "fastboot flashing unlock_critical"
Why do we have to use that command aswell?
Click to expand...
Click to collapse
If you have read my tuto with all the process and explanations , you would have seen this point that concerns your question:
12-Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
Click to expand...
Click to collapse
Sib64 said:
If you have read my tuto with all the process and explanations , you would have seen this point that concerns your question:
Click to expand...
Click to collapse
So as long as I flash ROMS i don't have to use that command. Only for modem.and so on.
bariz143 said:
So as long as I flash ROMS i don't have to use that command. Only for modem.and so on.
Click to expand...
Click to collapse
Since my HTC Hero, it's the 1st time that I have inserted this command