Hey guys,
I am trying to unlock my bootloader on my OP 7 pro Global version. i am currently running android 12 and hate it so much i am trying to downgrade back to 11.
In order to do this i need to unlock my bootloader and flash the old os... but I keep getting this weird error.
When i run command "fastboot oem unlock" i receive -
FAILED (remote: 'Device cannot be unlocked for technical reason.')
fastboot: error: Command failed
When i run "fastboot devices" i can see my device.
under developer setting i have all ready toggled allow oem unlock...
nothing seems to get around this issue and i am currently stuck and have no idea what else to try.
The MSM Tool should help you. Worked for me. I converted my T-Mobile variant, to Global using it. Follow the guide, and the MSM tool will flash your phone back to stock, with bootloader locked once again.
Edit: I should note, the tool will wipe your phone, so backup obviously.
DaveImagery said:
The MSM Tool should help you. Worked for me. I converted my T-Mobile variant, to Global using it. Follow the guide, and the MSM tool will flash your phone back to stock, with bootloader locked once again.
Edit: I should note, the tool will wipe your phone, so backup obviously.
Click to expand...
Click to collapse
Yes thank you! i was gonna write here that i eventually put my phone in edl mode and downgraded through msm tool to OOS 11.
Thank you!
no new for TWRP 3.7, still doesn't works on A12.
Also, A12 BL can't be unlocked for now.
Related
I wanted to share my experience with working with a T-MO G4 (H81120i) that I had rooted, unlocked the bootloader, and had a custom ROM. My goal was to return it to stock so that I can turn it in(to jump). I tried:
The 2014 LG Flash tool. It failed out multiple times with a "Cannot connect to server" error.
LG Bridge tool which failed multiple times too. The device was not recognized.
LGUP which was reccommended by someone. I have no idea how you would flash or restore wit hthat tool. So, that was a dead end.
So, what worked?
I downloaded the flashable complete zip for the stock t-mo G4(20i) and then left it at that. Its still showing bootloader unlocked on startup so I asm wondering about setting going into fastboot and OEM locking or relocking. The question is...is this last step necessary?
gpmartinson said:
I wanted to share my experience with working with a T-MO G4 (H81120i) that I had rooted, unlocked the bootloader, and had a custom ROM. My goal was to return it to stock so that I can turn it in(to jump). I tried:
The 2014 LG Flash tool. It failed out multiple times with a "Cannot connect to server" error.
LG Bridge tool which failed multiple times too. The device was not recognized.
LGUP which was reccommended by someone. I have no idea how you would flash or restore wit hthat tool. So, that was a dead end.
So, what worked?
I downloaded the flashable complete zip for the stock t-mo G4(20i) and then left it at that. Its still showing bootloader unlocked on startup so I asm wondering about setting going into fastboot and OEM locking or relocking. The question is...is this last step necessary?
Click to expand...
Click to collapse
its only if you want to send to LG... so they wont noticed it was bootloader unlocked.... if you relock it will you .. take a video of it...
someone claim it can be relocked... mines locked... so if it can be relocked then i would unlock it..
but it will be nice to see a video that it can be done...
http://forum.xda-developers.com/tmobile-g4/help/relock-bootloader-h811-t3372970
If anybody wants to no how I did it let me no I can spread the love takes bout 20 min of ur time
Okay so this is what u do is go download msm tool and follow his guide after that ,u go here https://forums.oneplus.com/threads/android-q-developer-preview-3-for-oneplus-7-pro-and-7.1076548/. And download lastest beta do the local upgrade and it will boot u into the new beta ROM which u will have no data don't freakout just go to settings tap build number 7 times or what not then go to developer options scroll down u will see oem uUnlocking and u can click on it to enable it then go to fastboot and unlock bootloader then u go back to the first link and download full rollback package and flash it in local upgrade to ,when it gets done ur bootloader will still be unlocked so down load twrp installer and the img , fastboot the twrp img then reboot it brings you back to twrp flash magisk n boom u got root on T-Mobile with unlocked bootloader you very welcome
How about sharing it here, unless its illegal?
Yes, a new method is known. It’ll be posted here later today. That’s the current plan, anyway. Hopefully someone doesn’t post it first; I have a way to make the method better (permanent, can relock bootloader and unlock again without redoing the method).
Just doing stuff this weekend, haven’t had time. Will have time tonight though.
Please share!
Hijacking this thread to say we (XDA Portal) have also discovered a way, which is what DTop is referring to. If any T-Mobile OP7 Pro user wants to try it, DM me.
Wish we could find faster ways to Sim unlock lol
Ok, doing this currently with wife's phone as avoiding the 7 day wait with Oneplus is ideal. Just got her device sim unlocked today so its a win overall now.
Go here - https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947 grab the two mega links using decryption codes found in second post. this will convert you to international firmware and you can follow the OP's guide.
Edit: can confirm that DP3 let me bootloader unlock without a unlock token. Thank you to @fowler82
It's been updated to 13x4 I've managed to get 13x3 through the oxygen updater app.
There was a method to unlock network on tmobile op 6t. I ve tried to do same on 7 pro. But getting fastboot error saying “flashing is not allowed for critical partition”. Anyone can help?
This method:
2 unlock bootloader
3 type this commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Отправлено с моего iPhone используя Tapatalk
akyl001 said:
There was a method to unlock network on tmobile op 6t. I ve tried to do same on 7 pro. But getting fastboot error saying “flashing is not allowed for critical partition”. Anyone can help?
This method:
2 unlock bootloader
3 type this commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Отправлено с моего iPhone используя Tapatalk
Click to expand...
Click to collapse
I am not a fastboot expert, but I strongly suspect running those commands will just erase your modem firmware and leave you with a non-working modem = no network connection
Jaco2k said:
I am not a fastboot expert, but I strongly suspect running those commands will just erase your modem firmware and leave you with a non-working modem = no network connection
Click to expand...
Click to collapse
On oneplus 6t, there was no problem. You re getting fully unlocked phone on both sim trays.
any news about whith that
I am pretty sure I lost the ability to use mobile sim one way or another I think after I deleted these and then like a dummy clicked in settings sim lock password or whatever it is called that locked me out and I needed to get my oil code from the carrier
Jaco2k said:
I am not a fastboot expert, but I strongly suspect running those commands will just erase your modem firmware and leave you with a non-working modem = no network connection
Click to expand...
Click to collapse
Partitions that are not marked _a or _b are never updated through any system update
In other words whatever that command does is unrecoverable and historically this command was used to erase IMEI
Hello everyone before anything I hope everyone is ok and safe in this difficult time.
Now I ask. Does this still work? My TMobile oneplus 7 pro is on the official international 10.3.2GM.21AA. if it still work is it safe to downgrade directly to the DP3 to do this?
gunfan said:
Hello everyone before anything I hope everyone is ok and safe in this difficult time.
Now I ask. Does this still work? My TMobile oneplus 7 pro is on the official international 10.3.2GM.21AA. if it still work is it safe to downgrade directly to the DP3 to do this?
Click to expand...
Click to collapse
Follow these instructions. It still works.
https://www.xda-developers.com/t-mobile-oneplus-7-pro-root-tutorial/
dirty2k9 said:
Follow these instructions. It still works.
https://www.xda-developers.com/t-mobile-oneplus-7-pro-root-tutorial/
Click to expand...
Click to collapse
Thank. Will try it.
It worked fast and easy on my first try. I'm on 10.3.1.GM21AA with an unlock bootloader. Now let's see if I can muster the courage to install twrp magisk and a rom.
Things have change so much since cyanogen. I'm so afraid to brick. Anyways thanks for the help.
i just poasted a moded msm i made that all you need to do is flash it then enter fastboot command
With the Moto Z, after I returned the phone to stock (flashed stock firmware and locked the bootloader), I'd be able to flash stock firmware with the flashing locked.
Not so with the Motorola One Zoom. In other words, flashing stock and re-locking didn't return the phone to its pristine state. Even when flashing stock firmware over stock firmware, I have to unlock the bootloader.
Differences I observed: on the bootloader screen, when re-locked the Z would show "oem_locked" again. On the One Zoom, it shows "flashing_locked" instead. I'm pretty sure it showed "oem_locked" before unlocking.
WIth the Z, every time I wanted to unlock the bootloader, I had to issue "fastboot oem unlock" followed by the unlock code. The code isn't necessary with the re-locked One Zoom.
In other words, maybe it was a one-way trip. It seems that the phone won't return to its original state, it looks it's modified for good. And I'm afraid this means bye-bye to automatic updates.
Am I missing something here?
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
rafikowy said:
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
Click to expand...
Click to collapse
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Whammamoosha said:
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Click to expand...
Click to collapse
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
rafikowy said:
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
Click to expand...
Click to collapse
Don't bother, I have mine. Thanks.
I would like the flash script if someone would share it
Help with unlocking bootloader
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Bodeman12345 said:
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Click to expand...
Click to collapse
In the settings for developers you gave permission for Factory Unlock?
ilia3367 said:
In the settings for developers you gave permission for Factory Unlock?
Click to expand...
Click to collapse
I enabled the setting to unlock oem bootloader is that the same?
Bodeman12345 said:
I enabled the setting to unlock oem bootloader is that the same?
Click to expand...
Click to collapse
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
Code:
fastboot devices
If the device is detected, enter the command:
Code:
fastboot getvar all
And copy the result here.
ilia3367 said:
yes.
Click to expand...
Click to collapse
Yes I did that
Bodeman12345 said:
Yes I did that
Click to expand...
Click to collapse
Answer the other questions, please!
diculpe por que mi pc no ve el fastboot de mi one zoom?
ilia3367 said:
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
If the device is detected, enter the command:
And copy the result here.
Click to expand...
Click to collapse
I used this youtube video
I dont know where it is manifactured but I live in the netherlands.
I dont get the 3th question
I will do the commands in a couple minutes
Hey all,
I have the Moto One Zoom running on Android 9.
Also, It's Rooted with Magisk and have Riru EdXposed installed, can I install my OTA updates without bootloop or do I have to Uninstall Magisk, relock bootloader and factory reset/flash stock firmware to get latest OTA updates?
Any feedback is appreciated.
Thanks
I tried to install Android 12 Developer Preview 3 on my Pixel 5 via OTA Sideload but it failed at 94% with the message 'adb: failed to read command: No error' on cmd and 'Install from ADB completed with status 0' on phone.
After this when I try to boot, I get the following message: 'Can't find valid operating system. The device will not start.' (attached image)
I'm able to access the bootloader but when I tried going into recovery mode through the bootloader, it shows the same message: 'Can't find valid operating system. The device will not start.'
Seems like the recovery is corrupted as well.
Unfortunately I had not enabled OEM unlocking in the developer options before trying to install the Developer Preview, which is now not letting me unlock the bootloader.
Please help me fix the issue or help me find a way to unlock the bootloader without enabling OEM unlock.
Thanks in advance.
I had the same thing happen to me just now. Have you managed to figure anything out?
Nothing from my side, since bootloader is locked I can't flash the system image and I can't unlock bootloader because my OEM unlock is turned off in developer settings and the Recovery and Rescue mode are also corrupted.
I contacted Google support and their only solution was to bring it in for service as my device is still under warranty.
I'm in the same boat here with a Pixel 4a 5G. Got to 94%.
First time I've experienced an issue while sideloading. . .
Contacted google support and they are shipping me a refurbed replacement... disappointed, to say the least.
Not sure what to make of this, it's developer preview and now beta. Issues will possibly occur and it warns you of such.
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As an additional this let me get my phone back to loading the custom ROM I was on, to then reenable debugging mode, I then rebooted back into fastboot mode and used Googles online factory restore mode to flash stock ROM back on and I was back up and running
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
leddra3k said:
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
Click to expand...
Click to collapse
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
V0latyle said:
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
Click to expand...
Click to collapse
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
leddra3k said:
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I am aware. However, this tool does not function like adb and is not meant for flashing factory images like the Android Flash Tool is. The Pixel Repair Tool works specifically from Rescue Mode.
leddra3k said:
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
Click to expand...
Click to collapse
It sounds like your Platform Tools may be out of date. Current version is 31.0.3, Aug '21.
Hello everybody
I need to know if there is a method to unlock the bootloader for an Oneplus Nord N100 but the BE2015 model (Metro PCS by T-Mobile) because I have not found out how to do it in this Forums
My smartphone is running Android 11 by an update (version 11.0.9.BE82CF).
My goal is to unlock the bootloader in order to install TWRP for a future custon ROM
Thanks to everybody and excuse my English.
Happy 2023
If I understand correctly you have to have the phone for 180(?) days and then "OEM unlock" will be available in developer settings. Then you have to request en unlock token from T-Mobile. (I don't have an american phone, I'm not 100% on the method)
You can get an unstable TWRP for this phone, but it will have very limited functionality. And custom ROMs is basically a forgotten dream on this phone.
Basically what you can do is sideload Magisk through TWRP (you have to use adb sideload command) and some people have installed GSI ROMs.
thomaskmaagaard said:
If I understand correctly you have to have the phone for 180(?) days and then "OEM unlock" will be available in developer settings. Then you have to request en unlock token from T-Mobile. (I don't have an american phone, I'm not 100% on the method)
You can get an unstable TWRP for this phone, but it will have very limited functionality. And custom ROMs is basically a forgotten dream on this phone.
Basically what you can do is sideload Magisk through TWRP (you have to use adb sideload command) and some people have installed GSI ROMs.
Click to expand...
Click to collapse
Really I bought the phone already unlocked, it has the "OEM unlock" function in the "Developer options". Because I didn't buy the phone directly from T-Mobile it's impossible to request the unlock token, so better I continue using it normally until I can buy another phone (I didn't comment but I live in Cuba...)
Thanks anyway for your answer...
Salutes
juancrod68 said:
Really I bought the phone already unlocked, it has the "OEM unlock" function in the "Developer options". Because I didn't buy the phone directly from T-Mobile it's impossible to request the unlock token, so better I continue using it normally until I can buy another phone (I didn't comment but I live in Cuba...)
Thanks anyway for your answer...
Salutes
Click to expand...
Click to collapse
I think you might be able to load a European/Global ROM through MSM tools. Then you can use OEM unlock command without token. Rummage through the N100 forums here and you can find guides.
thomaskmaagaard said:
I think you might be able to load a European/Global ROM through MSM tools. Then you can use OEM unlock command without token. Rummage through the N100 forums here and you can find guides.
Click to expand...
Click to collapse
I already searched and the ROMs are for BE2011/BE2013 models and mine is BE2015. My fear is to brick the phone in the process because it has a modified ROM especially for T-Mobile, thanks anyway
juancrod68 said:
I already searched and the ROMs are for BE2011/BE2013 models and mine is BE2015. My fear is to brick the phone in the process because it has a modified ROM especially for T-Mobile, thanks anyway
Click to expand...
Click to collapse
Have you checked this?
thomaskmaagaard said:
Have you checked this?
Click to expand...
Click to collapse
thanks bro, I will read it carefully tomorrow... the goal is to change for a Global ROM and then unlock the bootloader in order to install TWRP, isn't? salutes
juancrod68 said:
Hello everybody
I need to know if there is a method to unlock the bootloader for an Oneplus Nord N100 but the BE2015 model (Metro PCS by T-Mobile) because I have not found out how to do it in this Forums
My smartphone is running Android 11 by an update (version 11.0.9.BE82CF).
My goal is to unlock the bootloader in order to install TWRP for a future custon ROM
Thanks to everybody and excuse my English.
Happy 2023
Click to expand...
Click to collapse
If all you want to do is unlock the bootloader I think you can just do this.
** WARNING: YOUR DATA WILL BE WIPED **
1. enable developer options -> oem unlock
2. start adb
3. adb reboot fastboot
4 fastboot oem unlock
if step 4 fails then try
5. fastboot reboot fastboot
6. fastboot oem unlock
The phone will show a screen to confirm unlocking. YOUR DATA WILL BE WIPED.
7. fastboot reboot
The phone should reboot. Unfortunately It will display an annoying message warning the bootloader is unlocked for quite a while before it boots into system from now on.
BTW: I had problems with twrp 3.5 for Nord N100 floating around these forums. Latest is twrp 3.7 which I'm still suspicious of. All of my flashing using TWRP on the N100 has resulted in bricking.
My successful flashes have been with fastboot.
I use TWRP on another phone and it works like a dream.
Hi,
In step 3, do
adb reboot bootloader
This will reboot in the ancient fastboot, not fastbootd. This is in this mode that you can unlock the bootloader.