Question Stuck in fastboot mode which cannot access to recovery/ rescue mode - Google Pixel 7 Pro

My phone just got into fastboot mode this morning which I cannot access to recovery/ rescue mode. Everytime I choose the option it will bring me back to the fastboot screen.
I havn't unlocked the bootloader/ OEM previously. Anything I can do to make the phone start working again?

Hi,
What did you do to end up in this situation?
Good luck,
Sébastien.

5.1 said:
Hi,
What did you do to end up in this situation?
Good luck,
Sébastien.
Click to expand...
Click to collapse
Nothing! all I did was normal usage and it became bricked over the night. Onlything I did was leaving the phone being charged.

tonydigimon said:
Nothing! all I did was normal usage and it became bricked over the night. Onlything I did was leaving the phone being charged.
Click to expand...
Click to collapse
Android Flash Tool
flash.android.com
do this

jons99 said:
Android Flash Tool
flash.android.com
do this
Click to expand...
Click to collapse
Tried but it said the phone is not unlocked and therefore cannot be flash.

tonydigimon said:
Tried but it said the phone is not unlocked and therefore cannot be flash.
Click to expand...
Click to collapse
to supplement, it shows as below:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.

tonydigimon said:
Tried but it said the phone is not unlocked and therefore cannot be flash.
Click to expand...
Click to collapse
Can you boot into safe mode?

andy242 said:
Can you boot into safe mode?
Click to expand...
Click to collapse
No. I can't even see the google logo. It directly jumped to the fastboot page.

Supposedly, when I've seen instances like this before (stuck in fastboot mode, can't access recovery mode, locked bootloader, no oem unlock ticked), you might be able to forcibly change slots to the other one. There are 2 slots for this very reason -- supposedly to have a working one when things go to crap (but primarily for OTA and when that doesn't work out right).
IIRC, you don't need an unlocked bootloader to change slots...
If that doesn't work, I'm curious if you'd be able to get into recovery mode using the button combination vs. selecting it from fastboot mode......

simplepinoi177 said:
Supposedly, when I've seen instances like this before (stuck in fastboot mode, can't access recovery mode, locked bootloader, no oem unlock ticked), you might be able to forcibly change slots to the other one. There are 2 slots for this very reason -- supposedly to have a working one when things go to crap (but primarily for OTA and when that doesn't work out right).
IIRC, you don't need an unlocked bootloader to change slots...
If that doesn't work, I'm curious if you'd be able to get into recovery mode using the button combination vs. selecting it from fastboot mode......
Click to expand...
Click to collapse
You can't use fastboot commands to change slots when your bootloader is locked. And even if you could, the slot would not be bootable until you flashed the firmware onto it since these aren't dual boot devices. Only the last slot on which you flashed the firmware on will boot.

Lughnasadh said:
You can't use fastboot commands to change slots when your bootloader is locked. And even if you could, the slot would not be bootable until you flashed the firmware onto it since these aren't dual boot devices. Only the last slot on which you flashed the firmware on will boot.
Click to expand...
Click to collapse
I don't see why one would need an unlocked bootloader to change slots (especially considering it can happen on a locked bootloader when OTA's fail)...but I'll take your word for it.
But I understand things differently as @badabing2003 explained the two slot device aspect on these devices that, for the most part, the partitions are intact and accessible when either slot is active -- things depend differently on whether a slot can boot on them or not. If I understood correctly, one doesn't necessarily need to flash the firmware to make a particular slot to become bootable...
But I understood badabing2003's explanation in a very rudimentary sense so....I acknowledge I could very easily be under the wrong impression.....

Wouldn't slots change automatically upon boot failure? Isn't that the point?

simplepinoi177 said:
I don't see why one would need an unlocked bootloader to change slots (especially considering it can happen on a locked bootloader when OTA's fail)...but I'll take your word for it.
But I understand things differently as @badabing2003 explained the two slot device aspect on these devices that, for the most part, the partitions are intact and accessible when either slot is active -- things depend differently on whether a slot can boot on them or not. If I understood correctly, one doesn't necessarily need to flash the firmware to make a particular slot to become bootable...
But I understood badabing2003's explanation in a very rudimentary sense so....I acknowledge I could very easily be under the wrong impression.....
Click to expand...
Click to collapse
When you flash the factory image the system_other.img gets moved to the inactive slot, basically making that slot unbootable until you flash the firmware onto that slot.

krakout said:
Wouldn't slots change automatically upon boot failure? Isn't that the point?
Click to expand...
Click to collapse
The main point for having 2 slots (A/B partitions) is for seamless OTA updates.

simplepinoi177 said:
I don't see why one would need an unlocked bootloader to change slots (especially considering it can happen on a locked bootloader when OTA's fail)...but I'll take your word for it.
But I understand things differently as @badabing2003 explained the two slot device aspect on these devices that, for the most part, the partitions are intact and accessible when either slot is active -- things depend differently on whether a slot can boot on them or not. If I understood correctly, one doesn't necessarily need to flash the firmware to make a particular slot to become bootable...
But I understood badabing2003's explanation in a very rudimentary sense so....I acknowledge I could very easily be under the wrong impression.....
Click to expand...
Click to collapse
As @Lughnasadh says, only one slot is bootable, so switching even if it was possible don't help.
System of the inactive slot gets overwritten with optimized Dex files to be copied on first boot.
And even if one manually skips the system_other partition, avb doesn't allow you to boot on newer devices.
I managed to make it work on Pixel XL, but couldn't on newer devices.

tonydigimon said:
My phone just got into fastboot mode this morning which I cannot access to recovery/ rescue mode. Everytime I choose the option it will bring me back to the fastboot screen.
I havn't unlocked the bootloader/ OEM previously. Anything I can do to make the phone start working again?
Click to expand...
Click to collapse
if you cant use the volume buttons to access recovery from the bootloader, and you did nothing to the device, you should be able to return to google and get a new one depending on where you bought it

I got the same thing on my Pixel 7 Pro. Nothing would flash and my bootloader was unlocked. I just sent mine to Google last week and I'm currently waiting for them to send a replacement back.

Very weird. Wish I had a solution for you OP. Just goes to show an unlocked bootloader is a great fail safe to have in resurrecting a bricked device

Lughnasadh said:
And even if you could, the slot would not be bootable until you flashed the firmware onto it
Click to expand...
Click to collapse
The inactive slot holds the previous firmware build. In theory that shouldn't be a problem to switch the slots. But in most cases it ends up in a bootloop until you wipe /data because that partition has no slot.

krakout said:
Wouldn't slots change automatically upon boot failure? Isn't that the point?
Click to expand...
Click to collapse
Only right after an update. If the updated slot once is marked as "boot successfully" than the bootloader won't change to the inactive slot in case the active one is unbootable. It's only a rollback option for corrupted updates. But not a rollback for corrupted devices.

Related

[UNLOCK] Bootloader Unlock Package

Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.
The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse
i get a message saying "cant update from sd card?"
yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard
Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.
JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse

Unable to unlock bootloader (OEM unlocking disabled)

Hello,
I couldn't unlock the bootloader as the OEM unlocking's disabled and i can't access system! Everything's erased!
Any help????
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
junglism93 said:
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
Click to expand...
Click to collapse
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
eldeen said:
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
Click to expand...
Click to collapse
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
junglism93 said:
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
Click to expand...
Click to collapse
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
eldeen said:
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
Click to expand...
Click to collapse
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
AndroidNazi said:
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
Click to expand...
Click to collapse
Thanks for help, but could you please show me how to do that?
eldeen said:
Thanks for help, but could you please show me how to do that?
Click to expand...
Click to collapse
Make sure you have the latest fastboot. On the bootloader your phone will either say "slot a" or "slot b" and you should type "fastboot --set-active=b" if you are on slot a or "fastboot --set-active=a" if you are on slot b
still didn't fix the problem... any probable solutions please?

How To Guide [ROOT][GAPPS] Root and install GApps on stock Edge S/Chinese version

So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.

Question TMobile OP9 bootloader unlock process stuck

Hello,
I am trying to convert Tmobile OP9 to Global version and I am stuck at a basic step of getting the oem unlock code when trying to unlock the bootloader.
Details:
1. got my network unlocked from mobbdeep couple of weeks back.
2. Under Settings > "Network Unlock" status shows as unlocked
3. Installed the latest SDK as I am following the guide here to get the bootloader unlocked. When I boot in fastmode and run the oem command it stays at "waiting for device" and returns nothing.
Code:
fastboot oem get_unlock_code
When I run this, device list shows empty
Code:
adb devices
- Enabled USB debugging and stay awake options is checked from what I read on few posts
- When I restart the phone normally and then run "adb devices" it shows my phone listed
- Working on windows machine
What am I doing wrong here ?
TIA !!
PS: attached image shows the device state as Locked
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Superguy said:
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
Click to expand...
Click to collapse
Thanks for your response.
I tried that earlier assuming the same but it asked me to first flash the unlock token for which I am following the steps
I was however able to get the device listed after manually uninstalling/installing adb drivers
avid_droid said:
Check in device manager. If you have the yellow triangle on your phone in device manager just download android composite driver and update it through device manager/browse computer/ select unzipped folder and click OK.
Might be the issue
Click to expand...
Click to collapse
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
This thread was helpful as well. Thanks !
cass89 said:
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Click to expand...
Click to collapse
This thread was helpful as well. Thanks !
avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
FRNK8 said:
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
Click to expand...
Click to collapse
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Hey thanks for the heads up. I will
Would infact first go through the conversion steps to go back to Tmo just incase things go south.
avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Following the guide here, I just performed the bootloader unlock successfully. Per your suggestion, I want to backup the modem files before I proceed any further.
I cant seem to recollect how do I backup the modem files when I did the same conversion for OP6T. Can you please guide me here before I proceed with the next steps.
I tried installing the partitions backup but it wont allow me without root. I vaguely remember that I hadn't rooted my device the last time while backing up these files or is root needed ?
TIA !
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
craznazn said:
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
Click to expand...
Click to collapse
Can you help me with the steps to root ? Just want to be careful while doing so.
I saw some posts but that was related to the Tmobile OP9Pro(in my case its its Tmo Op9). The boot images were different so I didnt try to play around.
Thanks !
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
craznazn said:
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
Click to expand...
Click to collapse
Okay did this step.
Downloaded an copied stock image and the boot_patched image provided on the link and copied to my phones internal storage
Also as next step said, rebooted the phone
- went to Magisk app > install > selected boot_patched.img from internal storage
- phone restarted
- When I open the partitions backup app it still shows "device is not rooted" warning
What step did I miss ?
FRNK8 said:
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
Click to expand...
Click to collapse
do you have a link for the driver I'm having the same problem

How To Guide WARNING: Read BEFORE Locking Bootloader

DO NOT LOCK THE BOOTLOADER WHILE ROOTED!
When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader.
Locking the bootloader will not fix most issues. It will allow you to use apps that check for an unlocked bootloader without the need for any additional modification. That is the ONLY benefit.
If you still want to lock your bootloader, make sure you can say yes to each of the following:
1. Have you restored the stock boot.img / vendor_boot.img and the phone functions normally?
Spoiler: Restore Stock Boot
Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)
These images are NOT built from source. These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification. 18.0840.2202.231 18.0840.2201.226 18.0840.2112.211...
forum.xda-developers.com
Follow the instructions in the thread above.
Use only the boot and vendor_boot images.
Do NOT flash any images that end with "-magisk.img"
2. Have you made a backup of everything you do not want to lose when wiping the phone?
Spoiler: Make a Backup
The sdcard is part of the internal storage and is cleared by a factory reset
Copy everything you want to keep to a computer or USB-C storage device
Apps and settings can be backed up by enabling the Google Backup option
Open Settings
Select Google
Select Backup
Select Back up now
Wait for the backup to complete
3. Have you flashed raw firmware and made sure the phone and updates function normally?
Spoiler: Flash Raw Firmware
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Follow the instructions in the thread above.
If you perform a wipe, you may skip step 4.
4. Have you performed a factory reset and made sure the phone functions normally?
Spoiler: Factory Reset
Open Settings
Select System
Select Reset options
Select Erase all data (factory reset)
Follow the instructions
Once you have verified all of the above requirements, you are now ready to lock the bootloader.
Spoiler: Lock Bootloader
From the bootloader (volume up + power):
Code:
fastboot oem asus-csc_lk
Reserved for QA information
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
falhumai96 said:
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
Click to expand...
Click to collapse
Based on new information, it does seem possible to repair the issues caused by converting.
That said, this guide is still quite relevant. After all, most of the issues people were having were caused by unlocking the bootloader, converting, rooting, and locking the bootloader. The warning for possibility of not being able to unlock have been removed, but the info about restoring to stock before locking has been left.
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
chairman011 said:
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
Click to expand...
Click to collapse
@chairman011 what variant of the phone it is (e.g. CN or WW or US, ...etc.)? Also, when they returned it to you and you were able to unlock it again, was it on the original firmware (or any version in its lineage (i.e. not a ROM that's not original))?
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
nexusnerdgeek said:
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
Click to expand...
Click to collapse
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
falhumai96 said:
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
Click to expand...
Click to collapse
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
twistedumbrella said:
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
Click to expand...
Click to collapse
So, basically the bootloader unlock for tencent devices will always locked unless asus uodate their unlock app or has their been another way around it yet?
The unlock app should unlock the bootloader at least once. Unlocking it a second time has mixed results.
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
0v3rkill said:
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
Click to expand...
Click to collapse
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Andrologic said:
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Click to expand...
Click to collapse
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
0v3rkill said:
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
Click to expand...
Click to collapse
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Andrologic said:
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi there, I did follow and did the raw setup it did got me through the boot loop. However, its stuck on the system start up updating screen and stays in 0%.
Darn i thought im already dead! i didn't even know how i fixed it hahahaha! but its working now successfully downgraded to android 11 because its the only firmware i found and managed to make it work again combination of alot of research in google and here xda. working 100% imei two of them, finger print and sn are all intact. thanks guys
For these few reasons I have to give up root & lock the boot-loader: 1. Financial apps stop working from time to time causing much grief; 2. I've used root functionality precisely for nothing for a year I've had it; 3. It was getting all too complicated to keep up with it all.
(The original intention for unlocking/rooting was to get some sort of unofficial VoLTE and VoWiFi for the mobile operator of my choice; however, it didn't help. Then a newer firmware implemented VoLTE and VoWiFi! So my impatience, admittedly couldn't be known at that point in time, backfired.)
I've nothing to preserve on the phone, due to having a Moto G 5G backup phone. I only had it working with adb & fastboot in my Linux laptop (up to date Fedora 36). I had no working Windows laptop then. But I do now. However, adb on Windows says the device is "unauthorised" (as expected); fastboot in it doesn't list the device. So I might be limited to my Linux laptop only. The phone was previously working on the last A11 WW firmware fine.
I've tried to follow the steps from the original post of this thread. First one worked with vendor_boot, dtbo & boot images (used only 18.0840.2202.231 versions of them). Second N/A. With third step, flash_raw_and_wipe_data.sh fails by core dumping.
Right now, the phone boots to fastbootd & not further. Any help is much appreciated.
(I think I'm inching towards fully bricking this phone. I'm not there yet, but getting closer . It'd be nice to get it working again without root & with locked boot loader. Any help is much appreciated.)
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
nexusnerdgeek said:
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
Click to expand...
Click to collapse
Confirm that you can send fastboot commands to the device. It's a prerequisite for flashing the original boot img back or doing a RAW flash if boot looped. That's the very first step you need sorted and confirmed. Sounds like you may not be in the right Fastboot mode. The RAW version doesn't matter too much as long as it's in line with your device version, you just need it to get back up and can upgrade normally to other versions.

Categories

Resources