Hi,
I have once rooted my google pixel, but I changed my mind, and decided to unroot it and lock the bootloader.
I chose "lock" in the twrp menu, and I entered an endless loop.
Now the bootloader is locked and won't boot. The phone just splashes the initial screen and off, a few seconds after that, splashes the screen, and off,.....repeatedly. It looks like as soon as the initial "GOOGLE" screen appears, the phone resets itself.
I turned on with the volume down button on, and connect to the desktop computer (I use linux with adb and fastboot installed which work perfectly) and enter "fastboot flashing unlock", but it returns
Code:
$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.009s
I also tried to enter recovery mode, but it began to splash initial screen on and off again.
How can I recover from this situation?
Thanks in advance!
edit:
"fastboot flash recovery twrp-3.3.0-0-sailfish.img" now returns like this.
Code:
$ fastboot flash recover twrp-3*img
Sending 'recover' (31000 KB) OKAY [ 0.892s]
Writing 'recover' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.074s
edit2:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Thanks. I'll give it a try. I'm almost abandoning.....
junglism93 said:
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Click to expand...
Click to collapse
I tried it now. Most of the procedures were fine, but the important parts (write .img) failed. I attach the logfile. I abandoned....
maverick6664 said:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Click to expand...
Click to collapse
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
matusala said:
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
Click to expand...
Click to collapse
I've learned. "Don't root. Don't unlock bootloader."
@matusala you can unlock the bootloader and flash stuff as you did on the nexus line of devices. I'm on Q beta 5 with bl unlocked, I've had lineage running on it for a while and also had magisk etc installed. The key with these pixel A/B slot devices is that your system must be 100% stock before relocking the bootloader. If it is not It will end up bricked as you will no longer have a working boot image or recovery as they are in the same partition. The rule is to never relock the bootloader unless you are 100% sure that your system is 100% back to full stock.
I certainly won't be re locking my bootloader, ever!
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
matusala said:
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
Click to expand...
Click to collapse
I unlocked my bootloader back on stock pie, i have it on mine but it's greyed out as already unlocked so no idea on that one! My knowledge on A/B slot ain't great, it's just what I've read on here re the pixel bricking scenario so I didn't do the same when I unlocked my bootloader etc. I doubt running a separate ROM on each slot works as when you perform an update it will write to slot a or b (the slot you aren't using) and then hop onto the updated slot upon reboot, alsoif the update borks you can roll back to the previous slot and still have a working system.
That's about as far as my knowledge of it goes mate
Leaving the bootloader unlocked doesn't void the warranty or things like that, also it's a life saviour if *anything* goes wrong, even with official updates. Why not leaving that on?
The lesson here is not "don't root" or "don't unlock the bootloader", cause with an unlocked bootloader you can recover from pretty any kind of software malfunction.
Unfortunately, with a locked bootloader I've never seen anyone succesfully recover the device, cause you cannot send commands.
maverick6664 said:
I've learned. "Don't root. Don't unlock bootloader."
Click to expand...
Click to collapse
Hmmm......correction.
I would say:
"Root with caution. Otherwise don't root."
Rooting doesn't necessarily cause a trouble. Usually it helps. But my Google Pixel used to show alert screen message upon every boot. It's a bit messy.
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.
It seems these pixel phones are garbage compared to nexus line. Those were so much better!
matusala said:
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.!
Click to expand...
Click to collapse
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
TENN3R said:
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
Click to expand...
Click to collapse
I followed this guide and it worked. It unlocked my bootloader. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Now option is greyed out again in "off" position but it says "Bootloader already unlocked"
Maybe i got verizon model but in cell-unlocked state, because seller had written that it's unlocked. He meant provider lock of course.
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
junglism93 said:
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
Click to expand...
Click to collapse
Good luck @matusala from me also, and don't give in the first "Don't keep bootloader unlocked' alert screen!! Otherwise you might fall into a bad luck "bricked pixel" like me!
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
Nice to hear that. It was a good lesson to me. I have two xperia's (after google pixel dies, I bought one.) Somehow xperia's are not re-lockable. It is also mentioned in Sony Xperia forum. I guess it must be a warning from Sony. :laugh:
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
BTW, "adb oem lock" doesn't work with xperia. Sony seems to like leaving their products unlocked.
maverick6664 said:
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
I'm sure that is safe if you're updating from full stock to full stock, with mods on board a relock is almost suicidal and the threads about bricked pixels back that up.
If you don't like the warning screen, do what I do, don't watch your phone reboot
Click to expand...
Click to collapse
Hi, ever since bootloader unlock in my Zenfone 6 fingerprint crashes all apps that use it (like Settings or OneTimeInit). Currently running pure stock. If I relock it with asus-back it returns to life, however I'd like to keep this state after unlock too. After second lock I've removed all phone security in case something blocked fp reader from there but no luck. Any ideas?
Also, is there any way to unlock the bootloader n-th time without using that apk unlocker/without internet conenction? I know the relock command but things that unlock it like asus-go don't work.
Probably downgrading to pie and then upgrading to Q will fix it according to https://forum.xda-developers.com/zenfone-6-2019/help/relocked-zenfone-6-lockscreen-t4033321
Oh, I will downgrade it to Pie allright. Just bricked my phone and messed up dm verity on locked bootloader. I prefer Samsungs to play with...
Edit: You were right. I've unlocked it on Pie and works great. I don't know why xda search couldn't find that thread for me. Thank you.
Hello everyone ..
I have oneplus 8 with unlocked bootloader and rooted all was good but after relock bootloader and back to stok the fingerprint doesn't work , i get massage Enrollment was not completed, i tried flash rom again and unlocked bootloader but still not working i don't have any idea for this issue, please can you help me to solution this issue ? :crying:
same problem , up.
I've read the 25 or so pages from here as I'm in the same boat. It looks like a return to OnePlus for repair is the only solution https://forum.xda-developers.com/oneplus-8-pro/help/enrollment-problem-wont-register-t4089787
Hi,
I had the same problem with the fingerprint sensor.
As I received the phone I decided to unlock the bootloader. But as i realized that it'll take a while until TWRP provide a stable recovery, I decided to roll back.
Nothing what i tried (factory reset, etc.) brought the fingerprint sensor back. The OnePlus support couldn't (or didn't want to) help in this regards too.
Since I bought the phone via Amazon (de) I sent it back. I got my money back and bought a new one.
Cheers!
Up up up up
This bug should have never made it past quality control .
If OnePlus even have quality control.
And now you guys get to see first hand how completely **** their customer service is
No solution as yet. I am in the same boat.
Isn't this solved by flashing your (hopefully) backed up persist.img via fastboot?
As my device was rooted a month ago but couple of days ago I lost the L1 cirtification, today I updated to latest firmware by downloading full size by oxygen updater and updated it with in-device local update method. But even after the update my device's L1 cirtification is still not back and it's showing L3.
I rooted my device by flashing patched image with adb. Now I'm afraid locking bootloader might cause issues... Any suggestions how should I lock my bootloader. Somewhere I saw that lock option for bootloader in developer option cause bootloop/brick.
Btw my own lock is greyed.
Relocking the bootloader will definitely cause issues, maybe this thread can help?
XDHx86 said:
Relocking the bootloader will definitely cause issues, maybe this thread can help?
Click to expand...
Click to collapse
Yes I tried that already.
I have a moto g stylus XT2211DL and my friend somehow got it locked on the second setup screen. Cannot sign in to wifi or anything, it's not even FRP locked. I am able to bypass the screen using MTP and then maps to get to settings, but some settings are still locked like developer options, and you can't install apps. My question is, does anybody know which system app the device lock would be in so I can either disable or force quit so I can finish the setup and unlock all the features again?
here is the screen
How about factory reset it through stock recovery and try again?
Fytdyh said:
How about factory reset it through stock recovery and try again?
Click to expand...
Click to collapse
I tried that, but it just keeps going back to that screen :/ I even tried finding test points to get to BROM with no luck
r1pp3d2 said:
here is the screen
Click to expand...
Click to collapse
You have to set up the device using enterprise enrolment and that would bypass the locked screen limitation. I have the same phone and I experienced the same issue. That's the only way I got around it.
On the welcome screen, I guess where you select Language, tap on any empty space 6 times and your setup will be switched to enterprise enrollment or some type of enterprise management setup...
I just searched on google images for sample Android MDM QR Codes (images), then I scanned one with the phone and followed through with the setup.
That's how I got mine fully setup...
Of course, I intend to find a way to bootloader unlock it, unofficially, and flash out Tracfone firmware so I'm not worried... Just haven't been able to bootloader unlock unofficially yet... I'm still on here searching for a way.