It ws esy unlocking the bl in g5s+ , what about the z3 play, wife surprised me with this phone, im liking it already, but would like to unlock the bl and eve tually gain root/custom recovery ?
Anyone?
Depends on the model you have specifically, certain ones cant be unlocked such as amazon version. But the steps are the same as all other android phone bootloader unlocks, Steps can be found on motorola website:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
The basics consist of:
enable developer mode
enable "OEM Unlock" in developer settings
fastboot into phones bootloader and run OEM unlock commands
copy unlock code from phone that you get using oem unlocking commands into motorola website
receive email from motorola with unlock "password"
enter password into adb terminal
phone will be wiped and bootloader unlocked
Thats what i thought, i went there just to see , looks the same as for my G5S+ , ill likely do this. Is there guide somewhere on instally magisk as im outdated ( an old chainfire guy) just need some hints , doesnt look like twrp works , what about clockwork mod? Thats fine as well, , any good roms? Think 9 is comming?
Magisk root is straight forward. You can either get a working boot.img for your device from a firmware package and patch/flash it yourself. Or boot NOT flash the twrp images from the twrp website and install the magisk zip that way. The twrp for this device hasn't been compiled for flashing. It boots but flashing it to your device will boot loop it. No custom ROMs that I know of but I'm just using stock with magisk and it's fine once you have root to delete the bloat ware apps and install tweaks from magisk.
Related
Per title, Nexus 6 will not get past the white "Google". I can get into recovery fine. But the bootloader is locked, so I cannot properly flash stuff. Attempting to unlock the bootloader, I'm told I need to enable the option in the settings menu that I cannot access.
Looks like I'm not the only one I have the same issue and nothing works
AndrewZorn said:
Per title, Nexus 6 will not get past the white "Google". I can get into recovery fine. But the bootloader is locked, so I cannot properly flash stuff. Attempting to unlock the bootloader, I'm told I need to enable the option in the settings menu that I cannot access.
Click to expand...
Click to collapse
is this happened after trying to install update with adb sideload?
I got my nexus 6 today and tried to sideload the ota zip file, but I had no luck and now my nexus can not boot. I had enabled the option for bootloader unlock but my big mistake was that i tried to factory reset the device from recovery and now the bootloader can't be unlocked.
supposed to be experience with nexus devices, but with the bootloader locked I don't know what to do.
any ideas guys?
psybill said:
is this happened after trying to install update with adb sideload?
I got my nexus 6 today and tried to sideload the ota zip file, but I had no luck and now my nexus can not boot. I had enabled the option for bootloader unlock but my big mistake was that i tried to factory reset the device from recovery and now the bootloader can't be unlocked.
supposed to be experience with nexus devices, but with the bootloader locked I don't know what to do.
any ideas guys?
Click to expand...
Click to collapse
Yeah I think that's what I may have done too. I was just trying to go back to 100% stock (ignoring 5.1 even).
And of course NOW the 5.1 image is up on Google's page.
Have the same situation: flash 5.1 OTA and then wiped system
Now I can't unlock bootloader (as system just cant boot) and can't flash stock image (as system.img can't be flashed with locked bootloader)
I do not want to believe this is a brick, but it is very likely it
Sadly I've just done the same thing. ADB updated from 5.0.1 to 5.1, and the system.img didn't copy correctly. Phone wont boot past the Google splash screen, and I can't flash a factory image to recover the phone, because in order to unlock the bootloader I have to enable the option in developer settings, which I can't get to because the phone wont boot!
I understand the purpose of having an extra layer of security to prevent malicious types from trying to flash factory images onto stolen devices, but surely any system that allows a user to brick a device simply by leaving a setting unchecked (in a hidden menu, no less!) is asking for trouble? Particularly on a developer orientated device like a Nexus.
It seems crazy that a developer can ADB the official Google Android OTA zip, using the official Google Android SDK, onto the official Google Android flagship device, and the simple corruption of one of the sent files can cause the device to become totally unusable. Surely, say, providing an option in the developer option settings to PIN protect the bootloader, rather than just preventing it from being unlocked all together, would be a more sensible choice?
For what it's worth, I explained my situation to Google, and they are replacing the phone under warranty. This is probably your best (or only) option at this stage.
Good luck, and please let me know if you do manage to find a work-around/ solution to your woes!
Ive done searching and just basically see alll sorts of other stuff. Im very familiar with rooting and modding. Done it now on 6 different phones. way back to the OG Droid.,.. This one is through the Jump program...... Id like to remain pure stock but root yet still have the ability to drop root when turning in the phone to get my g5 or v20. Root is all i want. no recovery or os..... The root will allow me to do viper audio, titanium and camera mods........ its H811 Tmobile running 20q pure stock.. please help..
MorbidMonkey101 said:
Ive done searching and just basically see alll sorts of other stuff. Im very familiar with rooting and modding. Done it now on 6 different phones. way back to the OG Droid.,.. This one is through the Jump program...... Id like to remain pure stock but root yet still have the ability to drop root when turning in the phone to get my g5 or v20. Root is all i want. no recovery or os..... The root will allow me to do viper audio, titanium and camera mods........ its H811 Tmobile running 20q pure stock.. please help..
Click to expand...
Click to collapse
yes its pure stock. you need to unlock bootloader .. and when return you need to relock it.
here are the commands for locking and relocking, and placing twrp temporary root it and then you are all set.
i use this method
go to where it says
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Going to try right now...actually better wait til after work tommorrow. Need it for alarm and tv time.. Just in case something happens.
raptorddd said:
yes its pure stock. you need to unlock bootloader .. and when return you need to relock it.
here are the commands for locking and relocking, and placing twrp temporary root it and then you are all set.
i use this method
go to where it says
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
MorbidMonkey101 said:
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
Click to expand...
Click to collapse
no dont downgrade i just used that post as reference the steps you need to use.. antirollback V3 (20o-20p-20q) (20i 10n this are V2.
yes install recovery use the same guide there..
use this recovery
https://dl.twrp.me/h811/
and rename it to twrp.img so the command should be renamed to twrp.img
have it on sd card. and hwen it boot you to twrp do install, then semlect botom right IMAGE and find the location the twrp is and select it and flash it , it will ask in a window select revocery .. and you are done with twrp installed permanent.
MorbidMonkey101 said:
To unlock first and add root i use this?
Bootloader OEM Unlock + Root:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
It wants me to downgrade and stuff. Is it possible to do it without downgrading? Also seems as alot of other posts say once your 20q you do not revert back to anything lower than 20o.. thats my concern.
Managed to get it unlocked.. Using that post.. Did not do the root part... So now.. Whats the next step? Install Recovery im sure. Then ROM... The plot thickens.
Click to expand...
Click to collapse
kk so i got it unlocked and rooted using that method.. but my phone reboots automatically every so often... what gives.. used adb to temp boot twrp...installed Su then rebooted...all done AFTER unlock
MorbidMonkey101 said:
kk so i got it unlocked and rooted using that method.. but my phone reboots automatically every so often... what gives.. used adb to temp boot twrp...installed Su then rebooted...all done AFTER unlock
Click to expand...
Click to collapse
Figured id say screw it.. I already unlocked and rooted.. might as well ROM it too.
im now running this mod. just unlocked and rooted using the method you told me.. then used twrp to install this ROM
https://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
Hi all,
I've purchased a used P20 Pro from a friend which has an unlocked bootloader and has been previously rooted. I normally keep my phones stock so I want to lock relock the bootloader (I have the code) but despite trying to follow various guides I have been unsuccessful.
Would anyone be able to guide me through the process of relocking the bootloader please?
The main reason I like to keep stock is manufacture updates etc and I don't have the knowledge to maintain a rooted phone.
R89B said:
Hi all,
I've purchased a used P20 Pro from a friend which has an unlocked bootloader and has been previously rooted. I normally keep my phones stock so I want to lock relock the bootloader (I have the code) but despite trying to follow various guides I have been unsuccessful.
Would anyone be able to guide me through the process of relocking the bootloader please?
The main reason I like to keep stock is manufacture updates etc and I don't have the knowledge to maintain a rooted phone.
Click to expand...
Click to collapse
I don't believe that an unlocked bootloader will prevent you from getting updates. As far as I know the only difference is the warning you get when you boot that "you can't trust the phone."
IF YOU BRICK YOUR PHONE IT'S YOUR RESPONSIBILITY
Don't know if there is another way but of you have fastboot and adb you can do it:
1. Make sure developer options are enabled
2. Connect your phone to the computer using USB cable.
3. Open a command window and type 'adb boot bootloader'
4. Once the device has booted into the bootloader mode type 'fastboot oem lock'
This WILL ERASE all your user data and you will have to configure everything from scratch. You will need the unlock code if you ever want to unlock it again so make sure you don't loose it.
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.