Related
Hi,guys!I've had some trouble now.
I've unlocked bootloader before on N5x, but I accidentally locked it up again today.I want to use the "fastboot oem unlock" command,it doesn't work.
Now,when I open the phone,it only shows fastboot mode . And I can't start,recovery,boot anymore. My phone can only stay on this page which shows"Your devixe is corrupt.It can't be trusted and may not work properly" with a red exclamation mark.
How can I do now ? Looking forward to your reply.
Which rom you were in?
freq_ency said:
Which rom you were in?
Click to expand...
Click to collapse
I didn't flash any other rom before，just use original rom .My phone is made in KOREA.
Can you boot into bootloader(not recovery)? power +volume down.
Then try checking for fastboot devices.
freq_ency said:
Can you boot into bootloader(not recovery)? power +volume down.
Then try checking for fastboot devices.
Click to expand...
Click to collapse
When I open the phone ,there is a interface which is bootloader with a green robot lying on the ground.
xavierfoo said:
When I open the phone ,there is a interface which is bootloader with a green robot lying on the ground.
Click to expand...
Click to collapse
Just under that does it say "fastboot mode" in red?
If so does fastboot recognize the device?
fastboot devices <-- this is the command to check.
Also command prompt needs to be run as administrator in windows for fastboot to work properly.
freq_ency said:
Can you boot into bootloader(not recovery)? power +volume down.
Then try checking for fastboot devices.
Click to expand...
Click to collapse
Thank you anyway， I have solved this problem according to this post.
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Darke5tShad0w said:
Just under that does it say "fastboot mode" in red?
If so does fastboot recognize the device?
fastboot devices <-- this is the command to check.
Also command prompt needs to be run as administrator in windows for fastboot to work properly.
Click to expand...
Click to collapse
Thank you anyway， I have solved this problem according to this post.
http://forum.xda-developers.com/nexu...brick-t3251740
xavierfoo said:
Thank you anyway， I have solved this problem according to this post.
http://forum.xda-developers.com/nexu...brick-t3251740
Click to expand...
Click to collapse
Glad you got it sorted
So you have 32gb nexus?
freq_ency said:
So you have 32gb nexus?
Click to expand...
Click to collapse
No ,my N5x is 16GB. I used the TOT of 32GB directely,it works.
Oh is it! It will rewrite data partition. It's ok. Thanks.
I recently purchased a used Pixel C. The previous owner stated that the bootloader is unlocked but he never flashed anything. It is running stock. I want to re-lock to the bootloader to do away with the annoying message upon boot up. What is the appropriate fastboot command? Some posts make mention of new fastboot commands. Thanks
reboot on fastboot mode
type: fastboot flashing lock
wait for format userdata
done
Solved
Thanks. That worked perfectly.
Hmmm... My bootloader is unlocked and the developer option is grayed out to lock it.
If I follow these commands to lock via fastboot ("fastboot flashing lock") I get the following error:
FAILED (remote: Enable OEM unlock is not set)
geekdaddy said:
Hmmm... My bootloader is unlocked and the developer option is grayed out to lock it.
If I follow these commands to lock via fastboot ("fastboot flashing lock") I get the following error:
FAILED (remote: Enable OEM unlock is not set)
Click to expand...
Click to collapse
Settings>Developer options>Enable OEM Unlocking
tabormeister said:
Settings>Developer options>Enable OEM Unlocking
Click to expand...
Click to collapse
Thanks -- but that option is greyed-out.
No longer a problem for me since I think I'll probably run rooted with the final rev of lineageos +microg and Magisk. So I need to stay unlocked anyhow.
geekdaddy said:
Thanks -- but that option is greyed-out.
No longer a problem for me since I think I'll probably run rooted with the final rev of lineageos +microg and Magisk. So I need to stay unlocked anyhow.
Click to expand...
Click to collapse
I just flashed LOS17.1 yesterday and HOLY crap it's great. Good call.
I was trying to install the google camera and then relocking the bootloader.
i uninstalled magisk manager and in the adb command prompt terminal i typed fastboot oem lock and my phone displays system has been destroyed.
please help as fast as possible.
fayadfyzer said:
I was trying to install the google camera and then relocking the bootloader.
i uninstalled magisk manager and in the adb command prompt terminal i typed fastboot oem lock and my phone displays system has been destroyed.
please help as fast as possible.
Click to expand...
Click to collapse
Flash stock rom with mi flash but before you have to unlock again bootloader
HTCDevil said:
Flash stock rom with mi flash but before you have to unlock again bootloader
Click to expand...
Click to collapse
I have the same problem, so how can I unlock the bootloader being that it has no system for this ?
ItaloIanetta said:
I have the same problem, so how can I unlock the bootloader being that it has no system for this ?
Click to expand...
Click to collapse
So if you cannot boot to bootloader by pressing power and volume down at startup, you can try to enter recovery by pressing power and volume up. Then if it says no command hold the power button and press volume up one time. Now you should enter recovery. then from here you can try to enter bootloader.
Then flash your image via Miflash
TJ1999 said:
So if you cannot boot to bootloader by pressing power and volume down at startup, you can try to enter recovery by pressing power and volume up. Then if it says no command hold the power button and press volume up one time. Now you should enter recovery. then from here you can try to enter bootloader.
Then flash your image via Miflash
Click to expand...
Click to collapse
the point it is, how can i flash via MiFlash, even they request the bootloader unlocked, when I begin the flash, they show the error, that nothing can do because the bootloader are locked, the program can't do nothing, i open device, initializing the phone on EDL mode, but, when flash system is done, from edl mode, they stuck on boot loop.
---------- Post added 3rd November 2018 at 12:06 AM ---------- Previous post was 2nd November 2018 at 11:49 PM ----------
TJ1999 said:
So if you cannot boot to bootloader by pressing power and volume down at startup, you can try to enter recovery by pressing power and volume up. Then if it says no command hold the power button and press volume up one time. Now you should enter recovery. then from here you can try to enter bootloader.
Then flash your image via Miflash
Click to expand...
Click to collapse
I can enter the fastboot mode, I can enter the recovery mode, but the device does not respond to anything and gets bootloop
Ok, you said you can enter edl mode even the bootloader is locked right?
How did you do this? You said you opened device, did you short the two test points. I have a similar Problem.
Seems like there are other Posts with different problems at the beginning which are now facing the same problem as we do, after some flashing:
https://forum.xda-developers.com/mi-a2-lite/help/mi-a2-lite-suddenly-damaged-t3861467 (my Problem)
https://forum.xda-developers.com/mi-a2-lite/how-to/xiaomi-mi-a2-lite-hard-brick-t3861576
fayadfyzer said:
I was trying to install the google camera and then relocking the bootloader.
i uninstalled magisk manager and in the adb command prompt terminal i typed fastboot oem lock and my phone displays system has been destroyed.
please help as fast as possible.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=78066196&postcount=6
EASY FIX for this problem!...go again into fastboot mode....POWER button + Volume DOWN - in the command prompt on the PC type: fastboot oem unlock
system erases all the data and starts again had the same problem! i installed magisk to enable camera2pi, so today i got the mi mix 3 and i thought hmm lets lock the bootloader mi a2 lite and erase all the data so i can pass it further to my mum and she´ll get fresh updates! unfortunately, when i did fastboot oem lock, it said "system .blablabla..destroyed" ! Now everything workds fine again!
dappolino said:
EASY FIX for this problem!...go again into fastboot mode....POWER button + Volume DOWN - in the command prompt on the PC type: fastboot oem unlock
system erases all the data and starts again had the same problem! i installed magisk to enable camera2pi, so today i got the mi mix 3 and i thought hmm lets lock the bootloader mi a2 lite and erase all the data so i can pass it further to my mum and she´ll get fresh updates! unfortunately, when i did fastboot oem lock, it said "system .blablabla..destroyed" ! Now everything workds fine again!
Click to expand...
Click to collapse
You can also flash stock rom with Miflash tool and choose the option at the right bottom to "clean all and lock" after flashing you've got stock rom and relocked bootloader
Hey new to android and looking for root my pixel 2 xl.
Following this guide https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Using windows 10, ADB and fastboot version 29.0.6-6198805, android version 8.0.0 security patch level Sept 5, 2017.
OEM unlocking and USB debugging checked.
Enter command "adb reboot bootloader" takes me into the bootloader screen.
Enter command "fastboot flashing unlock_critical" gives me error "FAILED (Write to device failed (Too many links))" "fastboot: error: Command failed"
Phone resets.
Have searched past threads suggesting to use different USB ports and cables. Tried several cables and every port with no luck. Any idea whats causing the error? Thanks
ente2323 said:
Hey new to android and looking for root my pixel 2 xl.
Following this guide https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Using windows 10, ADB and fastboot version 29.0.6-6198805, android version 8.0.0 security patch level Sept 5, 2017.
OEM unlocking and USB debugging checked.
Enter command "adb reboot bootloader" takes me into the bootloader screen.
Enter command "fastboot flashing unlock_critical" gives me error "FAILED (Write to device failed (Too many links))" "fastboot: error: Command failed"
Phone resets.
Have searched past threads suggesting to use different USB ports and cables. Tried several cables and every port with no luck. Any idea whats causing the error? Thanks
Click to expand...
Click to collapse
Did you try just
fastboot flashing unlock first?
Tulsadiver said:
Did you try just
fastboot flashing unlock first?
Click to expand...
Click to collapse
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
ente2323 said:
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
Click to expand...
Click to collapse
Maybe trying to update your firmware to something closer to current. You're about 3 years out of date....
ente2323 said:
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
Click to expand...
Click to collapse
Are you using Powershell or command prompt for your interface?
Badger50 said:
Are you using Powershell or command prompt for your interface?
Click to expand...
Click to collapse
I'm using command prompt.
Tulsadiver said:
Maybe trying to update your firmware to something closer to current. You're about 3 years out of date....
Click to expand...
Click to collapse
ente2323 said:
I'm using command prompt.
Click to expand...
Click to collapse
Then i would suggest that you update your firmware via OTA as Tulsadiver suggested. Then try your unlocking command "fastboot flashing unlock"
The critical one is no longer needed after the 9.0 update. Good luck. :good:
ente2323 said:
I'm using command prompt.
Click to expand...
Click to collapse
Do you see your serial number when you type:
fastboot devices
Badger50 said:
Then i would suggest that you update your firmware via OTA as Tulsadiver suggested. Then try your unlocking command "fastboot flashing unlock"
The critical one is no longer needed after the 9.0 update. Good luck. :good:
Click to expand...
Click to collapse
Thanks I will consider upgrading the firmware if there is no other solution. I am going to see if I can solve the problem on 8.0 for now.
Tulsadiver said:
Do you see your serial number when you type:
fastboot devices
Click to expand...
Click to collapse
Entering the command "fastboot devices" gives me nothing. When I try "adb devices" my serial number is displayed.
ente2323 said:
Thanks I will consider upgrading the firmware if there is no other solution. I am going to see if I can solve the problem on 8.0 for now.
Entering the command "fastboot devices" gives me nothing. When I try "adb devices" my serial number is displayed.
Click to expand...
Click to collapse
Are you in fastboot mode or bootloader mode when your typing "fastboot devices"???
Badger50 said:
Are you in fastboot mode or bootloader mode when your typing "fastboot devices"???
Click to expand...
Click to collapse
I'm not sure of the difference. The screen I attempt to unlock reads FastBoot Mode in red. Fastboot devices is now displaying my phones serial. Adb devices no longer displays serial.
I cannot remember if I had fastboot mode loaded earlier when I attempted the command "Fastboot devices". It is now displaying serial when enter the command while in fastboot mode.
ente2323 said:
I'm not sure of the difference. The screen I attempt to unlock reads FastBoot Mode in red. Fastboot devices is now displaying my phones serial. Adb devices no longer displays serial.
I cannot remember if I had fastboot mode loaded earlier when I attempted the command "Fastboot devices". It is now displaying serial when enter the command while in fastboot mode.
Click to expand...
Click to collapse
Fastboot mode, or bootloader mode as some call it, is when you enter it when the phone is shut off with the power + volume down buttons, or from ADB reboot bootloader when your phone is on. ADB devices will not work in fastboot/bootloader mode. Conversly speaking, fastboot devices will not work while your in your OS with the phone on. All your fastboot commands must be done from fastboot/bootloader mode. :good:
I'd try out the pixel all in one tool, it makes these things dummy proof. But really, take the OTA and get your phone updated first.
Hi everyone, I recently bought a 2xl pixel and it's updated to Android 10, and I want to change rom (basically why I like to see how much can be done)but I have the problem that it is Verizon version, I have tried to unlock it with the methods I have seen, but I have seen that it depends on the Android version.I would like to know if there is a way to unlock the OEM unlock in order to unlock the bootloader. My model is the Google Pixel 2XL 128GB. Thanks in advance
Joseft1 said:
Hi everyone, I recently bought a 2xl pixel and it's updated to Android 10, and I want to change rom (basically why I like to see how much can be done)but I have the problem that it is Verizon version, I have tried to unlock it with the methods I have seen, but I have seen that it depends on the Android version.I would like to know if there is a way to unlock the OEM unlock in order to unlock the bootloader. My model is the Google Pixel 2XL 128GB. Thanks in advance
Click to expand...
Click to collapse
Sorry to say, if your device is a Verizon carrier variant (not purchased directly from Google), then you will not be able to unlock the bootloader at this time (or likely ever)....
To be sure:
after enabling "Developer Options" if you can't enable the "OEM UNLOCKING" toggle, your bootloader is not unlockable.
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
check if you have the last fastboot version - platform-tools_r33.0.1
bengoodall.raw said:
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
Click to expand...
Click to collapse
Have you checked Device Manager to see if there's any unknown devices?
bengoodall.raw said:
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
Click to expand...
Click to collapse
Assuming you're using the latest adb & fastboot versions, what happens when you type "fastboot devices"? Does it show your device?
CZ Eddie said:
Assuming you're using the latest adb & fastboot versions, what happens when you type "fastboot devices"? Does it show your device?
Click to expand...
Click to collapse
Yep, shows my device
Sometimes it does but when I unplug then replug it shows adb bootloader interface
razercortex said:
Have you checked Device Manager to see if there's any unknown devices?
Click to expand...
Click to collapse
Yep I have the latest version
GabrielSousa said:
check if you have the last fastboot version - platform-tools_r33.0.1
Click to expand...
Click to collapse
bengoodall.raw said:
Yep, shows my device
Click to expand...
Click to collapse
Does it work with ANY fastboot commands at all?
Such as "fastboot reboot"?
bengoodall.raw said:
Yep I have the latest version
Click to expand...
Click to collapse
Try running those commands on another PC and let us know if it works.
CZ Eddie said:
Does it work with ANY fastboot commands at all?
Such as "fastboot reboot"?
Click to expand...
Click to collapse
Nope, that doesn't work either
Didn't work either 🫤
razercortex said:
Try running those commands on another PC and let us know if it works.
Click to expand...
Click to collapse
bengoodall.raw said:
gives me an error.
Click to expand...
Click to collapse
Screenshot of the error?
I had similar issues and found out it was because I was executing the commands in the bootloader instead of fastbootd mode. Try running them in fastbootd mode instead?
GloriamSemper said:
I had similar issues and found out it was because I was executing the commands in the bootloader instead of fastbootd mode. Try running them in fastbootd mode instead?
Click to expand...
Click to collapse
Ermm, you're SUPPOSED to run the commands in "bootloader" mode, not fastbootD mode.
I'm kind of curious how unlocking the bootloader worked but using other commands doesn't.
ekin_strops said:
Ermm, you're SUPPOSED to run the commands in "bootloader" mode, not fastbootD mode.
Click to expand...
Click to collapse
I know wierd, right? None the less, certain fastboot commands were only successful for my 2127 in fastbootd