Related
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
Hi,
Apparently, I'm misunderstanding something. I'm trying to root my 2XL. I have unlocked the phone successfully, I believe. I have the notification screen at bootup. When I get to the task of flashing a factory image, I get the Failed notification, "FAILED (remote: Flashing is not allowed for Critical Partitions)". This occurs after ... writing 'bootloader_b'.
I was able to get Magisk installed but only 14.0 and I don't have root.
I haven't rooted anything in over 5 years so most of this stuff is pretty foreign.
Any advice would be welcome.
fastboot flashing unlock
then
fastboot flashing unlock_critical
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
slingblade01 said:
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
Click to expand...
Click to collapse
Unlock critical first then flash 8.1. Make a backup because this will wipe user data.
I am already unlocked and flashed 8.0 manually. I went to flash 8.1 today and got the OPs error. Are you saying that fastboot flashing unlock_critical will also wipe data? Damn that sucks if true.
SirVilhelm said:
I am already unlocked and flashed 8.0 manually. I went to flash 8.1 today and got the OPs error. Are you saying that fastboot flashing unlock_critical will also wipe data? Damn that sucks if true.
Click to expand...
Click to collapse
Oh yeah! It's definitely true. Unfortunately
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thx you saved my life <3
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I get an error saying "device already unlocked" but it still won't let me flash my bootloader... (Hope you're still active here...)
clarkcant said:
I get an error saying "device already unlocked" but it still won't let me flash my bootloader... (Hope you're still active here...)
Click to expand...
Click to collapse
Are you on Pie or Oreo? Is your platform-tools up to date? Have you tried different USB A to USB C cables and ports?
uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thanks man u saved my life. btw im not using a pixel, im in a xiaomi a3 but it worked!!
It doesnt work ....Help me to unlock critical
sadatkabir55 said:
It doesnt work ....Help me to unlock critical
Click to expand...
Click to collapse
Without details from you, we can't help you. For example, are you on the latest update? What else did you try? What worked for you and what didn't? Seriously, we can't read your mind. We can't see your phone. We can't perform miracles. It's a bit tiresome to have to ask you for things you should have already provided so we CAN help you.
Since you haven't given any details for anyone to go on, all I can tell you is that depending on the version of Android you are running, the "unlock critical" command may no longer be required, in which case you will get a message when executing the command.
I did not notice this was the forum dedicated to Pixel devices, sorry. I re-did my message in the Oneplus Nord dedicated forum regarding my issue that, however, seems to be the same as the one people encountered here.
Here is the link if anyone feels like helping me : https://forum.xda-developers.com/t/...itions-need-assistance-details-below.4274551/
slingblade01 said:
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
Click to expand...
Click to collapse
yeah he was like in 1 min
I have oneplus 8 5g IN2017. I was flashing the global rom.I unlocked the bootloader. but fastboot flashing unlock is taking too long. It just keep running and did'nt finish. Please guide. I am so tired of this.
Also Device is stuck in bootloader.
Khateeb2110 said:
I have oneplus 8 5g IN2017. I was flashing the global rom.I unlocked the bootloader. but fastboot flashing unlock is taking too long. It just keep running and did'nt finish. Please guide. I am so tired of this.
Click to expand...
Click to collapse
You'll need to read about your own phone. This thread is about the Pixel 2 XL. Different manufacturers tend to have different ways to unlock the bootloader.
Also, people who follow this thread are unlikely to know about OnePlus. Find a OnePlus-thread to ask for help.
Hi everyone, first of all, it's not a big problem, but it's annoying.
I've flashed a stock rom MM from another website(from my country) and it has a little problem: when i disable wifi connection, instead of showing the wifi disabled icon, it shows a similar icon to when i don't have mobile signal. And when i start the device for the first time with that rom, it comes with mobile data enabled as all the other roms, but even if i turn off mobile data, it still shows the 4G symbol above the mobile signal.
Is there anyone with a real stock rom for this device? Mainly marshmallow, but if you also have nougat, i would like it too.
Thank you
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
It also lockes the bootloader, idk if thats a huge problem, otherwise i need to search
SupahCookie said:
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
It also lockes the bootloader, idk if thats a huge problem, otherwise i need to search
Click to expand...
Click to collapse
Is it really needed to lock bootloader again? If not, what are the commands that I should fastboot? Just the necessary commands to flash stock 7.1.1 again, please!
Thanks in advance!
xdaVTU said:
Is it really needed to lock bootloader again? If not, what are the commands that I should fastboot? Just the necessary commands to flash stock 7.1.1 again, please!
Thanks in advance!
Click to expand...
Click to collapse
Use all the code until the first fastboot oem fb_mode clear,
The lines under there is for locking the phone
SupahCookie said:
Use all the code until the first fastboot oem fb_mode clear,
The lines under there is for locking the phone
Click to expand...
Click to collapse
I also need to use fastboot oem fb_mode clear or just the codes above it? And, do you like which is the security patch level of that rom?
xdaVTU said:
Is it really needed to lock bootloader again? If not, what are the commands that I should fastboot?
Click to expand...
Click to collapse
Just stop before fastboot oem lock. Everything is flashed then.
xdaVTU said:
I also need to use fastboot oem fb_mode clear or just the codes above it? And, do you like which is the security patch level of that rom?
Click to expand...
Click to collapse
November
Is there no easy way to relock the bootloader without using the MSM Tool (which I've never done)? I relocked it in the normal way, fastboot oem lock, but that resulted in a "device is corrupt and will not boot" error. I unlocked it and it's fine, but... I want to re-lock it.
dmarden said:
Is there no easy way to relock the bootloader without using the MSM Tool (which I've never done)? I relocked it in the normal way, fastboot oem lock, but that resulted in a "device is corrupt and will not boot" error. I unlocked it and it's fine, but... I want to re-lock it.
Click to expand...
Click to collapse
On OOS? Run a full local upgrade to whatever your current version is and try again
Yeah, it was just running stock firmware... Ok, so full local upgrade and try fastboot oem lock again?
Worth a try I guess, thanks!!!
The local update is running now, hope it works since the MSM Tool gives me a "failed to start" "because of a side by side configuration" error... lol. Sheesh, never experienced trouble relocking a device before.
dmarden said:
Yeah, it was just running stock firmware... Ok, so full local upgrade and try fastboot oem lock again?
Worth a try I guess, thanks!!!
Click to expand...
Click to collapse
Just factory reset once and then lock from fastboot > fastboot OEM lock > Select Yes to confirm and the device will lock the bootloader and reboot into OS
No dice... same error... what the heck?!
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
null0seven said:
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
Click to expand...
Click to collapse
It wouldn't let me install the downgrade APK (maybe because it is not on A12), but I am downloading the downgrade/rollback package and will try it.
null0seven said:
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
Click to expand...
Click to collapse
No dice... I presume because it's an older version it needs that APK.
Ok... this is resolved, even if I don't know how. I literally just tried it a third time and it worked. *shrug*
Thanks to those that responded.
dmarden said:
Ok... this is resolved, even if I don't know how. I literally just tried it a third time and it worked. *shrug*
Thanks to those that responded.
Click to expand...
Click to collapse
This is how I always did it
Hello, i unlocked the bootloader of my motorola one action. And i installed lineage 18.1 official, but i want to lock the bootloader again. i tried locking the bootloader using this help thread https://forum.xda-developers.com/t/...-2019-ask-any-question-noob-friendly.4010875/ but it din't work. Can somewone help me?
raphaelgamer981 said:
Hello, i unlocked the bootloader of my motorola one action. And i installed lineage 18.1 official, but i want to lock the bootloader again. i tried locking the bootloader using this help thread https://forum.xda-developers.com/t/...-2019-ask-any-question-noob-friendly.4010875/ but it din't work. Can somewone help me?
Click to expand...
Click to collapse
NEVER lock a phone with custom firmware installed. This usually leads to bootloops.
georg3_ said:
NEVER lock a phone with custom firmware installed. This usually leads to bootloops.
Click to expand...
Click to collapse
No, I Didn't try to lock the bootloader with a custom firmware.
raphaelgamer981 said:
No, I Didn't try to lock the bootloader with a custom firmware.
Click to expand...
Click to collapse
What are the steps you took before relocking the bootloader?
In my experience, relocking the bootloader should be the last thing you do, after you've got a working/bootable stock ROM.
arsradu said:
What are the steps you took before relocking the bootloader? In my experience, relocking the bootloader should be the last thing you do, after you've got a working/bootable stock ROM.
Click to expand...
Click to collapse
So, after i installed the latest stock rom, the device worked normally, but after waiting a while for the oem lock option appear in development options, it din´t show up. so i just gave up and installed lineage 19.1 but if i can i want to lock the bootloader again.
Raphael, I think you might have quoted my post twice, but didn't add an actual answer. Or maybe I'm super blind and I can't see it.
arsradu said:
Raphael, I think you might have quoted my post twice, but didn't add an actual answer. Or maybe I'm super blind and I can't see it.
Click to expand...
Click to collapse
ohh sorry, i tried replying to your post in my ipad 3 and it din´t show up any caracters.
raphaelgamer981 said:
So, after i installed the latest stock rom, the device worked normally, but after waiting a while for the oem lock option appear in development options, it din´t show up. so i just gave up and installed lineage 19.1 but if i can i want to lock the bootloader again.
Click to expand...
Click to collapse
So, the OEM lock/unlock thing comes with a pretty big caveat, and you need to be aware of it: loss of data.
Every time you lock or unlock your bootloader, a wipe data is triggered.
Now, for as far as I know, to lock the bootloader, you need two things:
1. Stock ROM. Don't do this on a custom ROM!
2. following command, in Terminal/Cmd Prompt
fastboot oem lock
Of course, you need to be in fastboot mode, so if you're not, and if you're booted and connected via USB (USB debugging needs to be ON and RSA fingerprinting accepted), do:
adb devices
It should display your device here. This is just to make sure ADB is working properly.
adb reboot bootloader
At this point, the phone should reboot into bootloader, so now you can do the lock command
fastboot oem lock
Data should be erased and, in case it doesn't automatically boot up, you can reboot the phone.
Don't worry about the OEM unlocking option in Developer Options. You just make sure the stock ROM is functional before attempting to relock the bootloader.
arsradu said:
So, the OEM lock/unlock thing comes with a pretty big caveat, and you need to be aware of it: loss of data.
Every time you lock or unlock your bootloader, a wipe data is triggered.
Now, for as far as I know, to lock the bootloader, you need two things:
1. Stock ROM. Don't do this on a custom ROM!
2. following command, in Terminal/Cmd Prompt
fastboot oem lock
Of course, you need to be in fastboot mode, so if you're not, and if you're booted and connected via USB (USB debugging needs to be ON and RSA fingerprinting accepted), do:
adb devices
It should display your device here. This is just to make sure ADB is working properly.
adb reboot bootloader
At this point, the phone should reboot into bootloader, so now you can do the lock command
fastboot oem lock
Data should be erased and, in case it doesn't automatically boot up, you can reboot the phone.
Don't worry about the OEM unlocking option in Developer Options. You just make sure the stock ROM is functional before attempting to relock the bootloader.
Click to expand...
Click to collapse
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
raphaelgamer981 said:
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
Click to expand...
Click to collapse
raphaelgamer981 said:
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
Click to expand...
Click to collapse
But why do you say it didn't work? Do you get an error at any point during the process?
arsradu said:
But why do you say it didn't work? Do you get an error at any point during the process?
Click to expand...
Click to collapse
no, i run the command and it asks for changing the oem lock setting in developer options, i reboot the phone and run through the setup process. Then when i enable developer options and check the oem lock option, it is greyed out.
Is it greyed out in the on or off position? Can you attach a screenshot? I don't remember the operations sequence... But I think the option was automatically switched back to the original position (off) when you lock the bootloader. I could be wrong though. So...when you run the "fastboot oem lock" command, it asks you to....what?
Set the option to on or off? Some screenshots from both the PC, with the message, and the developer options might help to clarify this.
arsradu said:
Is it greyed out in the on or off position? Can you attach a screenshot? I don't remember the operations sequence... But I think the option was automatically switched back to the original position (off) when you lock the bootloader. I could be wrong though. So...when you run the "fastboot oem lock" command, it asks you to....what?
Set the option to on or off? Some screenshots from both the PC, with the message, and the developer options might help to clarify this.
Click to expand...
Click to collapse
it is greyed in the on position, i can´t add a screenshot because i am in lineage 19.1 with root and the option shows up,when i run the command in cmd, it says to me to check the oem lock option in developer options
raphaelgamer981 said:
it is greyed in the on position, i can´t add a screenshot because i am in lineage 19.1 with root and the option shows up,when i run the command in cmd, it says to me to check the oem lock option in developer options
Click to expand...
Click to collapse
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
ok thanks for your help!
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
hello, so i want to lock the bootloader again, how do i install the stock rom back?
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
so after running the fastboot oem lock command, it asked this in the cmd
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.080s]
finished. total time: 0.080s
when i rebooted the phone, it showed the screen saying that the bootloader was unlocked. also i had to re run the command because it was going to erase my phone but that din´t happend, after going to developer options the option was still greyed out.
The last 3 days i've tried some roms from here.first i've unlocked the bootloader in developer menu,then from fastboot with the unlock key provided by motorola website,i've tried different rom,didnt like that i cannot use bank apps.so i went for locking.full reset,adb enable,reboot bootloader,full flash stock rom (last one from Motorola),reboot to check,adb enable, reboot bootloader,run command " fastboot oem lock " once ,it asked for confirmation due to data loss,then run command " fastboot oem lock " once more,then reboot to os.everything went ok,device dont show that was unlocked