Database Info

Google Pixel in crashing during boot - oem disabled so I can't unlock it again

So I installed twrp root on my Pixel and got annoyed at the fact my phone kept telling me to relock my bootloader. I did what it told me. But beforehand I decided to disable oem. I've researched for hours trying to figure out if I can enable it from CMD on PC but nothing works. I'd appreciate it if someone could help me.

FalseFriendsGaming said:
So I installed twrp root on my Pixel and got annoyed at the fact my phone kept telling me to relock my bootloader. I did what it told me. But beforehand I decided to disable oem. I've researched for hours trying to figure out if I can enable it from CMD on PC but nothing works. I'd appreciate it if someone could help me.
Click to expand...
Click to collapse
You may need to reflash back to stock via ADB or you could try this thread to jumpstart OEM unlock again https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
If you get back up and running just ignore that relock bootloader, I've never relocked it once root and twrp are installed, I'd only relock the bootloader if I've gone back to full stock.
Good luck
Sent from my Pixel using XDA Labs

Need help - "The system has been destroyed"

So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.

You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.

boxof said:
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
Click to expand...
Click to collapse
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash

Azev said:
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
Click to expand...
Click to collapse
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
Mackay53 said:
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Click to expand...
Click to collapse
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!

boxof said:
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
Click to expand...
Click to collapse
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.

nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
Unless you have got unlock permission and linked phone to account you can't unlock.

Unlock like how you would normally - put the phone into fastboot, connect it to your PC, and run the mi unlock tool. For this to work, hopefully you have associated your device to a mi account and have met the unlock requirements ie. surpassed the waiting period. Otherwise you're out of luck as there is no other ways (that i know of) to register the device now as you can't get into the system.
As a last resort you can try opening up the back of the phone and flash new firmware using the test point if unlocking is not possible. I'm not sure how or where the testing point is located exactly, but it's a possible solution that i found while researching when my device was bricked. Good luck!

nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
u say u can only access to fastboot..
How about pressing volume up and power button? can u enter in stock mi recovery with mi assistant options?

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?

bricked lg v50 sprint variant.

so, i was following the guide for the bootloader unlocking process and succeeded. rooting process is what bricked my phone, unfortunately.
i loaded the patched magisk image in to boot_a like it said, and hoping that everything would have went well, it did not.
now phone will not boot. recovery modeis broken. adb does not recognize my device, and i have no clue how to get to edl mode from there.
as far as im aware, there is no kdz for the lg v50 sprint variant. (v450) unfortunately.
can anyone help me?
i feel like im SOL
It's not my main phone, but I really like the cameras on it. Was just looking to rid it of lgs software.

Which abl you used to unlock?The one provides for LG G8 is untested for sprint V50,it's highly you missed something,you need get into the abl's fastboot mode to flash back the original kernel

@Vortex said:
Which abl you used to unlock?The one provides for LG G8 is untested for sprint V50,it's highly you missed something,you need get into the abl's fastboot mode to flash back the original kernel
Click to expand...
Click to collapse
It boots into fastboot as soon as it boots up. So there's hope. Adb just doesn't recognize my phone. The thread said it worked, and everyone else who had the sprint v50 said it worked. So I don't know what went wrong

I didn't use the file for the g8.

Beefybeardedbear said:
It boots into fastboot as soon as it boots up. So there's hope. Adb just doesn't recognize my phone. The thread said it worked, and everyone else who had the sprint v50 said it worked. So I don't know what went wrong
Click to expand...
Click to collapse
Where is the thread?I didn't see any talked about V50,only G8's,the adb will not recognize because it's fastboot mode,you need the fastboot.exe to do further operations,not the adb

@Vortex said:
Where is the thread?I didn't see any talked about V50,only G8's,the adb will not recognize because it's fastboot mode,you need the fastboot.exe to do further operations,not the adb
Click to expand...
Click to collapse
,
Ah, I see. I have the fastboot.exe in my platform tools folder.
The link is https://forum.xda-developers.com/t/...YteGJNSWxEZlhydFpfWm9telNEbUhFZ1pFQlJ6amZORlg.

Beefybeardedbear said:
,
Ah, I see. I have the fastboot.exe in my platform tools folder.
The link is https://forum.xda-developers.com/t/...YteGJNSWxEZlhydFpfWm9telNEbUhFZ1pFQlJ6amZORlg.
Click to expand...
Click to collapse
Good it seems using the rencently appeared lge programmer with G8X ES abl,are you get original phone from sprint ?It's unlocked someway more violent before for sprint model.Have you flashed the abl back?I suggest you follow the bootloader unlock section carefully https://bbs.lge.fun/thread-121.htm

@Vortex said:
Good it seems using the rencently appeared lge programmer with G8X ES abl,are you get original phone from sprint ?It's unlocked someway more violent before for sprint model.Have you flashed the abl back?I suggest you follow the bootloader unlock section carefully https://bbs.lge.fun/thread-121.htm
Click to expand...
Click to collapse
I haven't as I am at work, currently. I will try once I am back home. I mean, it seems as easy as just flashing stock boot_a.bin to the boot partition, right? Or am I wrong?

Beefybeardedbear said:
I haven't as I am at work, currently. I will try once I am back home. I mean, it seems as easy as just flashing stock boot_a.bin to the boot partition, right? Or am I wrong?
Click to expand...
Click to collapse
Yes,just patched the ramdisk file is not enough,you have to deal with dmverity or something else,the root aquirement on android had became much more complex than the early days because the damn google always try to block this routine,even the SuperSu had gave up fighting

@Vortex said:
Yes,just patched the ramdisk file is not enough,you have to deal with dmverity or something else,the root aquirement on android had became much more complex than the early days because the damn google always try to block this routine,even the SuperSu had gave up fighting
Click to expand...
Click to collapse
yeah, i know. back in the old days, there were even apps like king root to give you root permission. damn google acts like we cant just have freedom. they are starting to act like apple now

Beefybeardedbear said:
yeah, i know. back in the old days, there were even apps like king root to give you root permission. damn google acts like we cant just have freedom. they are starting to act like apple now
Click to expand...
Click to collapse
I sincerely suggest you buying some Chinese ODM 5G phones instead of these hell-like phones,It's all carrier unlocked and free to flash with the same Snapdragon Platform like oneplus Xiaomi.

@Vortex said:
I sincerely suggest you buying some Chinese ODM 5G phones instead of these hell-like phones,It's all carrier unlocked and free to flash with the same Snapdragon Platform like oneplus Xiaomi.
Click to expand...
Click to collapse
well xiaomi and all those other brands are banned. i have a oneplus 6t for when i want to flash and customize.

Beefybeardedbear said:
well xiaomi and all those other brands are banned. i have a oneplus 6t for when i want to flash and customize.
Click to expand...
Click to collapse
i also have oneplus 8. but bootloader is locked unless i get my phone sim unlocked. but thats after i pay off the phone

You just need to find a V50 Sprint device from another user or your friend, then backup all partitions, back them up, then flash to your device.
Note: ignore imei partitions

How would I flash it? Through fastboot and adb? I've already found one.

hello?

You flash them through fastboot by giving the following command:
fasboot [file name i.e abl_a] [file location]
Alternatively if you can go back to EDL/QFIL/9008 mode, you can load through the software

Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?

geee0h said:
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
Click to expand...
Click to collapse
Unfortunately, I haven't even tried. And I've given up. Going to chinese brands now. They are way easier to root and rom. Like oneplus and xiaomi. You could try the method above that a member mentioned.

geee0h said:
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
Click to expand...
Click to collapse
Get KDZ Tools
unzip the kdz
look for abl_a.img abl_b.img laf_a.img laf_b.img xbl_a.img xbl_b.img xbl_config_a.img xbl_config_b.img
flash it on fastboot. If you have follow the guide to unlock, you should have backed up all these files.
hope this helps.

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