Database Info

Google Pixel Verizon bootloop, Lock bootloader

I lock bootloader on Verizon Google Pixel when my device have TWRP and i have brick! Device Loading up to logo Google on 1 sec and reboot. Fastboot work, but i don't unlock bootloader. In recovery is don't enter. Please help me!

https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.

kkjb said:
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
Click to expand...
Click to collapse
There is still no solution to this problem? ((

Unlock again.

lafester said:
Unlock again.
Click to expand...
Click to collapse
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"

Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
Put the phone in fastboot mode, then run `fastboot flashing unlock` from a PC. If it says unlocking not allowed, you're out of luck, it's a brick now. Never lock your phone without being 100% stock on both slots

Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.

lafester said:
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
Click to expand...
Click to collapse
In this topic https://forum.xda-developers.com/pi...bootloader-t3540772/post77016940#post77016940 man has unbrick Pixel XL, but i think that method will work on Pixel.

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?

Anyone managed to root lg k51?

I can't find anything definitive about whether it's rootable or not

Same here i tried every root app possible and failed.

just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work

Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.

Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?

sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.

Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?

sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.

I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.

Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>

sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.

mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.

sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?

Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop

jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.

Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.

Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.

Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?

I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?

TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true

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

Question Can´t access to fastboot

I am trying to unlock my nord ce 2 bootloader but everytime I try to access bootloader mode, it says something like Unlock_Verify_device ok and then reboots
how can I unlock the bootloader? Same happens on my nord 2. Oem unlocking is enabled and I have no selection of advanched startup options. I have magisk boot.img to flash

Can't say I experienced that myself. The message you got looks promising. The 'unlock_verify_device ok' message means you're getting to fastboot. But I'm not sure why it's rebooting. Do you have enough time to run the command 'fastboot devices'?
Also, what version is your firmware?
Here is the guide I used when I was unlocking the bootloader: https://www.droidwin.com/how-to-unlock-bootloader-on-oneplus-nord-ce-2/

I am running android 12 beta on oxygenos
Edit: fastboot doesn´t even find the device
Oh, now it tells that serial is not match. what's going on?

so? Can anyone help? Phone keeps saying that serial is not match and then reboots. Is this phone just a joke or something? Gonna buy samsung if yes.

What model is your phone? I wasn't aware of the Android 12 beta being available for the Nord CE 2. Another thing to try is this tutorial to manually install the OnePlus drivers: https://www.droidwin.com/fix-android-device-not-showing-in-fastboot-mode/

Was looking on the nord ce 1 xda Forum. It's only recently that a few roms and twrp are starting to appear, so there is hope. IMO oneplus need to take £$50 off the price, more users = more chance of getting more development

mr_munch said:
Can't say I experienced that myself. The message you got looks promising. The 'unlock_verify_device ok' message means you're getting to fastboot. But I'm not sure why it's rebooting. Do you have enough time to run the command 'fastboot devices'?
Also, what version is your firmware?
Here is the guide I used when I was unlocking the bootloader: https://www.droidwin.com/how-to-unlock-bootloader-on-oneplus-nord-ce-2/
Click to expand...
Click to collapse
I don't have fastboot on my device Nord ce 2 ..when I type fastboot reboot bootloader then it directly reboot into my device ..Please somebody help me.Im on current Android 12.1 version

neilop7 said:
I don't have fastboot on my device Nord ce 2 ..when I type fastboot reboot bootloader then it directly reboot into my device ..Please somebody help me.Im on current Android 12.1 version
Click to expand...
Click to collapse
Fastboot is stuffed on this device. There's no longer a way to make fastboot work.

burningcreation said:
Fastboot is stuffed on this device. There's no longer a way to make fastboot work.
Click to expand...
Click to collapse
I wanna unlock bootloader..is there any way to unlock ?

neilop7 said:
I wanna unlock bootloader..is there any way to unlock ?
Click to expand...
Click to collapse
No unfortunately.

burningcreation said:
No unfortunately.
Click to expand...
Click to collapse
Did you able to unlock bootloader?

neilop7 said:
Did you able to unlock bootloader?
Click to expand...
Click to collapse
No I am not able to unlock the bootloader either. There is currently nothing we can do.

Hi everyone, any update on this? Did someone manage to unlock the bootloader?

If I'm not mistaken. You can rollback to android 11 to get it back.

I'm currently facing the same problem, so I tried rolling back and have downloaded over 20 rollback zips now, and extracted them. All won't work, it reboots in recovery. And it is like fastboot just doesn't exist. So yeah they probably messed it up.
I'm so sad, I switched from Iphone to Oneplus partly because of the rooting options. So sad
Can I do this trough adb or not?

NiekKamer0105 said:
I'm currently facing the same problem, so I tried rolling back and have downloaded over 20 rollback zips now, and extracted them. All won't work, it reboots in recovery. And it is like fastboot just doesn't exist. So yeah they probably messed it up.
I'm so sad, I switched from Iphone to Oneplus partly because of the rooting options. So sad
Can I do this trough adb or not?
Click to expand...
Click to collapse
You don't extract it though. You just rename it by removing the _Rollback at the end.
See here: https://droidwin.com/downgrade-oneplus-nord-ce-2-from-android-12-to-android-11/