Database Users

[INTERNATIONAL]Unlock Your Bootloader!

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

Stuck on Google Logo, Can't Unlock Bootloader

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.

[Root && Unlock] Droid Turbo 6.0.1 mcg24.251-5-5

@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

RE-LOCK the bootloader possible?

Hi!
I've recently unlocked my bootloader as I wanted to root the phone.
However, I'm planning to sell it and want to revert it.
I've tried "fastboot oem lock", but this soft bricked my phone so I had to unlock it again.
Is it possible to relock the bootloader or at least get rid of the booting message "the bootloader is unlocked and software integrity cannot be guaranteed, etc..."...

vessk0 said:
Hi!
I've recently unlocked my bootloader as I wanted to root the phone.
However, I'm planning to sell it and want to revert it.
I've tried "fastboot oem lock", but this soft bricked my phone so I had to unlock it again.
Is it possible to relock the bootloader or at least get rid of the booting message "the bootloader is unlocked and software integrity cannot be guaranteed, etc..."...
Click to expand...
Click to collapse
Ensure that unroot first before locking the bootloader.
The command you used worked for legacy devices. New devices including the OP8 series use the 'fastboot flashing lock' command.
P.S. If you have questions, please post them under the OnePlus 8 Pro Q&A section.

Use MSM tool. This will ensure that the software is 100% clean and in a new state.

Lossyx said:
Use MSM tool. This will ensure that the software is 100% clean and in a new state.
Click to expand...
Click to collapse
+1

Lossyx said:
Use MSM tool. This will ensure that the software is 100% clean and in a new state.
Click to expand...
Click to collapse
It will, but MSM is a low-level flashing utility and thus only recommended for unbricking.
For some very odd reason, I was able to break my phone's proximity sensors after using it the second time.
I wouldn't personally advise it to be a go-to solution for something that could be easily done via a bunch of commands. Just me two cents. ✌

DJBhardwaj said:
It will, but MSM is a low-level flashing utility and thus only recommended for unbricking.
For some very odd reason, I was able to break my phone's proximity sensors after using it the second time.
I wouldn't personally advise it to be a go-to solution for something that could be easily done via a bunch of commands. Just me two cents. ✌
Click to expand...
Click to collapse
I understand what you mean. But if that's the case then you would want to advise somebody to un-root, then run the adb command to remove any and all left over magisk modules, then factory wipe, then lock the bootloader.
Personally have ran the MSM tool 3 times due to poor flashes and it's been perfect.
I think the risk is much much higher if you plan to downgrade your OS. If not then you'll be absolutely fine.
Plus it's quicker

dladz said:
I understand what you mean. But if that's the case then you would want to advise somebody to un-root, then run the adb command to remove any and all left over magisk modules, then factory wipe, then lock the bootloader.
Personally have ran the MSM tool 3 times due to poor flashes and it's been perfect.
I think the risk is much much higher if you plan to downgrade your OS. If not then you'll be absolutely fine.
Plus it's quicker
Click to expand...
Click to collapse
I did mention unrooting first. Magisk will automatically take care of the modules when that's done. But yes, if someone did forcibly mount the system (not sure if it's possible anymore with dynamic partitions) and altered it, then that requires extra care.
As for a factory wipe, that'll be done at the same time when the bootloader is locked. So, that's why I suggested just unrooting and locking the bootloader straightaway.
Anyways, the suggestions you provided are equally valid as well.

DJBhardwaj said:
I did mention unrooting first. Magisk will automatically take care of the modules when that's done. But yes, if someone did forcibly mount the system (not sure if it's possible anymore with dynamic partitions) and altered it, then that requires extra care.
As for a factory wipe, that'll be done at the same time when the bootloader is locked. So, that's why I suggested just unrooting and locking the bootloader straightaway.
Anyways, the suggestions you provided are equally valid as well.
Click to expand...
Click to collapse
No mate you're wrong there im afraid. That is not always the case
Hence the actual requirement for a magisk removal command.
Magisk does not always clear up left overs, that's a well known problem.
But hey that's my advice.
Plus the wipe before hand is to eliminate anything that may have stuck similar to magisk modules.
It can happen.
Tbhi think he'll be fine either way.

dladz said:
No mate you're wrong there im afraid. That is not always the case
Hence the actual requirement for a magisk removal command.
Magisk does not always clear up left overs, that's a well known problem.
But hey that's my advice.
Plus the wipe before hand is to eliminate anything that may have stuck similar to magisk modules.
It can happen.
Tbhi think he'll be fine either way.
Click to expand...
Click to collapse
But sometimes, it is also the module developers to blame. That's why merging the modules into the official repository is difficult.
John has strained on this often. He recently removed EdXposed from the official repo:
https://twitter.com/i/web/status/1350590699113115648
As for wiping, it's all the same if you do it just before the relock command or let the command do it for you. The same thing is gonna happen either way, so it feels redundant to perform a factory reset right before locking the bootloader. This is what I was trying to convey earlier.
And yes, agreed. He'd probably be fine, given that we have provided various points to look out for before locking the bootloader.

DJBhardwaj said:
But sometimes, it is also the module developers to blame. That's why merging the modules into the official repository is difficult.
John has strained on this often. He recently removed EdXposed from the official repo:
https://twitter.com/i/web/status/1350590699113115648
As for wiping, it's all the same if you do it just before the relock command or let the command do it for you. The same thing is gonna happen either way, so it feels redundant to perform a factory reset right before locking the bootloader. This is what I was trying to convey earlier.
And yes, agreed. He'd probably be fine, given that we have provided various points to look out for before locking the bootloader.
Click to expand...
Click to collapse
I think he'll be fine.
An yea R-ice doesn't remove properly especially if you don't remove the theme first

Enable OEM Unlocking/Debloat Script for Tmobile/Sprint

all you have to do is extract the zip file, make sure your phone has adb debugging enabled, plug it into the computer, and run the script and it will debloat your phone and enable you to slide the oem unlocking toggle in developer options that was previously greyed out
********WARNING*********
this script will remove the keyboard app from your phone leaving you without a way to type, i dont know which exact package it is but you can always look them up and just remove that line from the script. otherwise make sure you have a usb-otg cable and keyboard to use or a program like Vysor/scrcpy or you wont be able to type. just reinstall gboard or whatever other keyboard you use and it will be fine

PrivyetCyka said:
Thank you. Tested is working to enable the OEM unlocking on T-Mobile phone.
Click to expand...
Click to collapse

Just getting the unlock token from Oneplus. Successfully flash and unlocked bootloader. Is it have any way to unlock network?
Update:
Have been flash global rom 10.5.7 and the update to beta global rom, network still locked.
Fastboot erase modemst1 and modemst2 also can't unlock network.

Hey does this mean what I think it means. Can you unlock a bootloader and convert to global if your phone is network locked? Can someone explain how I can unlock bootloader after enabling oem unlocking?

Yes, can covert to Global but sim remain locked.
Follow this link to covert.

Thank you. I went ahead to start the process and the oem unlock switch worked after some trouble having my pc recognize my phone in fastboot. Submitted it through oneplus and waiting on an unlock token. OP has my thanks for creating this script. Been waiting for this since I got the device. Surprised there isn't more interaction on this thread.
hendavi said:
Yes, can covert to Global but sim remain locked.
Follow this link to covert.
Click to expand...
Click to collapse

I don't know why this script doesn't work on my device and can't unlock my device OEM. Do you need to pay attention to when using this script? Does the device need to disconnect the network?

runcieliao said:
I don't know why this script doesn't work on my device and can't unlock my device OEM. Do you need to pay attention to when using this script? Does the device need to disconnect the network?
Click to expand...
Click to collapse
As I done before if you have wipe all data and start your phone without sign in google account it wont work. You need to sign in a google account then run the script.

hendavi said:
正如我之前所做的那样，如果您已擦除所有数据并在不登录 Google 帐户的情况下启动手机，它将无法正常工作。您需要登录一个 google 帐户，然后运行该脚本。
Click to expand...
Click to collapse
thankyou

Does anyone know if this works on Android 11?
Edit: Just wound up going for it and it worked flawlessly, Ungrayed the OEM Unlocking on my T-Mobile device that they wouldn't unlock

hendavi said:
Yes, can covert to Global but sim remain locked.
Follow this link to covert.
Click to expand...
Click to collapse
Anyone know what actually locks the sim slot? And how can it persist even on Global rom? On Tmo devices there is a "Device Unlock" app that gets deleted after you sim unlock the phone by carrier.
But global rom doesn't have the proprietary unlock app, so what is actually keeping it locked? Does the modem have the locking instructions in it?

Yes, something like that which is impossible to remove.

SimplisticXDA said:
Yes, something like that which is impossible to remove.
Click to expand...
Click to collapse
The previous OP devices it was possible after flashing Int. rom.
Question is where/how did they place the restrictions now. It had something to do with the modem after the t-mo app unlocks the phone.
But I don't think backing up and restoring a modem from an unlocked OP8 and flash it to locked OP8 will work as intended anymore.
I guess no one cared enough to reverse engineer this again

hendavi said:
Just getting the unlock token from Oneplus. Successfully flash and unlocked bootloader. Is it have any way to unlock network? View attachment 5421891
Update:
Have been flash global rom 10.5.7 and the update to beta global rom, network still locked.
Fastboot erase modemst1 and modemst2 also can't unlock network.
Click to expand...
Click to collapse
what does your unlock bin look like cause mine looks like jibberish? tried flashing mine and it said it cant verify it

Snekxs said:
what does your unlock bin look like cause mine looks like jibberish? tried flashing mine and it said it cant verify it
Click to expand...
Click to collapse
I think is same if open with notepad

hendavi said:
I think is same if open with notepad
Click to expand...
Click to collapse
Yeah mine looks the same. Did you flash it from your computer or flashed from your device's storage?

Snekxs said:
Yeah mine looks the same. Did you flash it from your computer or flashed from your device's storage?
Click to expand...
Click to collapse
Flash from computer. ..

hendavi said:
Flash from computer. ..
Click to expand...
Click to collapse
weird been doing that and no luck at all