Develop Bugs

Can't manage to unlock my nexus bootloader succesfully

Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks

How about you
a) Flash an official rom via stock recovery and try it then
b) Ask this question in the Questions and Answers section instead of the Development section because I don't see any development relevant information in this post...

gevenerof said:
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
Click to expand...
Click to collapse
Try using the Gnex Toolkit posted on the development page as a sticky.

since u can't use fastboot (and the toolkit is useless in this case), i think u should try odin

THIS IS NOT DEVELOPMENT
Do not post question threads here
Read forum rules before posting threads
Thread moved
FNM

First of all, use ANY toolkit (Mine's in the description ^^)
Then unlock your bootloader (Open cmdthe type:
Code:
fastboot oem unlock
You'll need ADB/fastboot drivers installed, though...)

There's no point using a toolkit, how it sounds to me is you somehow messed up a partition when flashing the update.
As someone already said try flashing an ota update through the stock recovery (if you have stock recovery)
It was probably the bootloader that got messed up when your power went.
Try flash a new bootloader too, see how that goes.
Fastboot flash bootloader filename.img

I am having the exact same issue. Trying to flash, format or dare i even say erase won't do anything to the bootloader, trying to access recovery on mine it says failed, trying to unlock the bootloader through oem unlock, prompts the failed : remote unknown error code. :S

use the galaxy nexus toolkit to unlock bootloader, root

Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.

Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Thats true, every tool kit i have tried has failed, even fastboot commands, at least the latter tell you that it fails. Where can i download the bootunlocker app? Does my Nexus 7 have to boot into the rom to do this? Because mine can't. :S

Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Incorrect.
Signed images will flash correctly with a locked bootloader.

Jubakuba said:
Incorrect.
Signed images will flash correctly with a locked bootloader.
Click to expand...
Click to collapse
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it

AndiS21 said:
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
Click to expand...
Click to collapse
Ask Google or Samsung, they have the keys to sign it. Also, this is the galaxy nexus forums.
Sent from my i9250

OP, OMAP flash?

Your device is corrupt. It can't be trusted and will not boot

Hi friends
Please give me suggestion or guide how to solve problem about handset booting after mistakenly handset OEM locked through fastboot
It enter to fastboot mode but not going to recovery mode or restart in system mode
Is there any solution
If yes then please help me

fastboot oem unlock ?

Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed

This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Edit: Just noticed the part about your device will not boot. You need to find the system image and flash it. I read somewhere today that OnePlus just released the system image for 4.7.4.

Can you unlock again?

@op, IMHO the best possible solution will be to flash stock rom image and stock recovery if required but I think when you flash stock image it will also flash stock recovery.

When you turn off the phone and boot it with VOLUME UP plus POWER, this should send you straight away to Fastboot. Try if you can unlock again, otherwise... bad luck - you'll need a restore session with 1+.

the Doctor said:
This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Click to expand...
Click to collapse
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!

jonsat said:
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!
Click to expand...
Click to collapse
After looking into it further, I agree with you. That's what I get for having a bootloader-locked Samsung device for two years. I must be getting rusty!
Yes, the bootloader can be re-locked. There may still be a tamper flag as with previous OnePlus devices. But having a locked bootloader with non-OEM software would likely cause the problem he is describing. So, he needs to flash the factory image from bootloader.

I've requested to 1+support for restore remote session
Support send me file link and l2 will assist me in within 2 days

DO NOT RELOCK BOOTLOADER UNLESS U READ UP FIRST!!!!!, its worth just waiting the few seconds after reboot, then to go and try to relock the bootloader

I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.

kaihansen2001 said:
Can you unlock again?
Click to expand...
Click to collapse
Yes ive unlock Bootloader

Rdxsammm said:
I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.
Click to expand...
Click to collapse
How did you do it? can you guide me too?

sam razzy said:
How did you do it? can you guide me too?
Click to expand...
Click to collapse
Have you dumpling files and MSM download tools for oneplus 5t
If you have then restore op5t after success it work as new mobile.
But you can get basic dumpling file from oneplus support remote session.
You have to create ticket and chat with oneplus support

oneplus 5 device corrupt and it cant be trusted and will not bootr

hrushi0130 said:
oneplus 5 device corrupt and it cant be trusted and will not bootr
Click to expand...
Click to collapse
Did you by any chance re-lock the bootloader with a custom recovery and custom ROM flashed?

It's because of custom recovery.
Just flash stock recovery image before locking the bootloader.
This fixed for me.

Rdxsammm said:
Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed
Click to expand...
Click to collapse
You unlocked bootloader, flashed rom (custom) and relocked bootloader? Never lock your bootloader on a custom rom! Just enter fastboot again flash twrp (manual/force reboot recovery), copy internal storage to pc then wipe/format everything. Format data. Factory reset then flash latest official rom and reboot

Trying to Flash January OTA

I still haven't received the January Security Update, so i tried updating via the OTA. But i get the following error message. When i type adb reboot recovery. Its like my stock recovery is broken because i get a no command error. My phone isnt' recognized in win10 anymore. Anyone else having this issue? My bootloader is unlocked. Not sure why that would matter.

Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version

It maybe a bad data cable I had the same issue kinda cable must have put out to much power or something next day I tried it and everything worked.
Adb wouldn't work but fastboot commands would sometimes then next day was able to do all the commands to root and install kernal
Sent from my Pixel 2 XL using Tapatalk

sjpritch25 said:
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
Click to expand...
Click to collapse
The boot loader not matching usually means you did not fully unlock it. I would bet you did unlock, but skipped unlock critical. You need the second one to be able to flash the bootloader. Otherwise you can only flash the same bootloader.

sjpritch25 said:
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
Click to expand...
Click to collapse
Saw this same issue with another user on another thread. First of all, do you have OEM unlocking and USB debugging turned on in developer options?
Did you already run BOTH bootloader unlocking commands?
Since your OTA and factory image flash didn't work, you'll need to go back to the factory image you were on before you started this process.
If your able to get this all accomplished, then you can proceed to the January update. Best of luck :good:

How do I go about fully unlocking the bootloader? My phone came with 8.0. I do recall that after unlocking I got the mo command booting into recovery.

I do have OEM unlocking turned on

sjpritch25 said:
I do have OEM unlocking turned on
Click to expand...
Click to collapse
And you ran both bootloader unlocking commands?
---------- Post added at 04:06 AM ---------- Previous post was at 04:00 AM ----------
sjpritch25 said:
I do have OEM unlocking turned on
Click to expand...
Click to collapse
You probably should read this thread my friend.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Thanks. I see things I didn't do correct

I had to re flash december ota and now i just got done flashing January. Had to wipe phone again though to fix the unlocked bootloader.

sjpritch25 said:
I had to re flash december ota and now i just got done flashing January. Had to wipe phone again though to fix the unlocked bootloader.
Click to expand...
Click to collapse
unsuccessful updated to January image. I updated adb and still got the corrupt bootloader message. flashed december image and have a phone again. I guess, I might need to relock the bootloader and then unlock again? my current working bootloader is TMZ12a. The January image is TMZ12b i believe and for some reason its not working.

sjpritch25 said:
unsuccessful updated to January image. I updated adb and still got the corrupt bootloader message. flashed december image and have a phone again. I guess, I might need to relock the bootloader and then unlock again? my current working bootloader is TMZ12a. The January image is TMZ12b i believe and for some reason its not working.
Click to expand...
Click to collapse
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.

sjpritch25 said:
I still haven't received the January Security Update, so i tried updating via the OTA. But i get the following error message. When i type adb reboot recovery. Its like my stock recovery is broken because i get a no command error. My phone isnt' recognized in win10 anymore. Anyone else having this issue? My bootloader is unlocked. Not sure why that would matter.
Click to expand...
Click to collapse
Don't do adb reboot recovery.
Turn it off, hold volume down, press power, and when bootloader screen shows, move volume button to choose Recovery.
When little green Android symbol shows, press Power, then Volume Up for a moment. You're now in Recovery.
Choose Apply Update from ADB, then follow instructions here: https://developers.google.com/android/ota
It will update you without wiping.

michaelbsheldon said:
Don't do adb reboot recovery.
Turn it off, hold volume down, press power, and when bootloader screen shows, move volume button to choose Recovery.
When little green Android symbol shows, press Power, then Volume Up for a moment. You're now in Recovery.
Choose Apply Update from ADB, then follow instructions here: https://developers.google.com/android/ota
It will update you without wiping.
Click to expand...
Click to collapse
Or adb reboot bootloader if you happen to be there but yes most of the time I just hit power to bring up restart then I hold volume down till it loads into bootloader
Sent from my Pixel 2 XL using Tapatalk

TonikJDK said:
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
Click to expand...
Click to collapse
I didn't have that & that was the issue earlier. I've done that & device was wiped again. Let me try those commands & I'll post them

TonikJDK said:
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
Click to expand...
Click to collapse
bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.038s]
finished. total time: 0.048s

sjpritch25 said:
bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.038s]
finished. total time: 0.048s
Click to expand...
Click to collapse
Download the full factory image. Not just the OTA. Open the flash-all.bat file and look near the end and edit out the -w and save it.
As long as you remove the -w that will flash the whole factory image but save your date, apps and set up.
So after the edit put it back in fastboot mode and run the flash-all.bat file.

Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker

sjpritch25 said:
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
Click to expand...
Click to collapse
Have you verified the sha-256 of the image you downloaded to ensure it's not corrupt?
Goto https://developers.google.com/android/images and copy the SHA-256 checksum from the Full Image you downloaded and compare it to the file downloaded here: http://onlinemd5.com/
- Make sure to choose sha-256 on the md5 site. This will rule out if the downloaded image you have is corrupted or not.

sjpritch25 said:
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
Click to expand...
Click to collapse
what version of adb/fastboot are you using ?
adb version
fastboot --version
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
michaelbsheldon said:
Don't do adb reboot recovery.
Click to expand...
Click to collapse
Why should they not do that ?

Pixel XL Android P DP4 soft brick

Hi,
Like the title says, my Pixel XL is bootlooping.
The only thing that works is getting to bootloader, I can't even get to recovery without it booting again. The biggest problem is that it's OEM locked and obviously I can't unlock it via developer options.
Is there any way to unlock it without booting to the OS?

Don't Ask said:
Hi,
Like the title says, my Pixel XL is bootlooping.
The only thing that works is getting to bootloader, I can't even get to recovery without it booting again. The biggest problem is that it's OEM locked and obviously I can't unlock it via developer options.
Is there any way to unlock it without booting to the OS?
Click to expand...
Click to collapse
OEM unlock must be toggled before unlocking bootloader or CMD won't work, Can't you flash stock OTA in the recovery? https://developers.google.com/android/ota You can sideload the zip and should flash it to save your device once you get into the OS unlock your bootloader and avoid a situation like this again

liam_davenport said:
OEM unlock must be toggled before unlocking bootloader or CMD won't work, Can't you flash stock OTA in the recovery? https://developers.google.com/android/ota You can sideload the zip and should flash it to save your device once you get into the OS unlock your bootloader and avoid a situation like this again
Click to expand...
Click to collapse
Thanks, but like I said - I can't get into recovery mode and the phone is OEM locked.

Don't Ask said:
Thanks, but like I said - I can't get into recovery mode and the phone is OEM locked.
Click to expand...
Click to collapse
Sorry missread... My bad Contact Google sounds like an RMA job for this one

Hey, if you can get into the bootloader, there's a high chance you can use fastboot. Using a computer to install adb/fastboot and then using the command line to run
`fastboot reboot recovery` (without the ticks)
Worth a shot, but if you can't get into recovery, I'm afraid the recovery might be failing as well.

khoanguyen96 said:
Hey, if you can get into the bootloader, there's a high chance you can use fastboot. Using a computer to install adb/fastboot and then using the command line to run
`fastboot reboot recovery` (without the ticks)
Worth a shot, but if you can't get into recovery, I'm afraid the recovery might be failing as well.
Click to expand...
Click to collapse
I've tried that as well with no success, it simply starts boot looping again.
I read somewhere about EDL mode, does something that like actually work for the Pixel?

Don't Ask said:
I've tried that as well with no success, it simply starts boot looping again.
I read somewhere about EDL mode, does something that like actually work for the Pixel?
Click to expand...
Click to collapse
Hey, yeah I looked into EDL mode. No luck unfortunately, looks like it requires special files manufacturers only have access to. Is there any way you can do a RMA?

OEM Locked, and Device is corrupt. Unfixable?

So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.

kschmitz4 said:
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
Click to expand...
Click to collapse
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.

Josh McGrath said:
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Click to expand...
Click to collapse
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.

kschmitz4 said:
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
Click to expand...
Click to collapse
Try
fastboot erase userdata and
Fastboot erase cache
Let me know if that works or not we will move on. Probably won't work since it's bootloader locked
You may have to contact OP and while you're at it, get the MSM tool for us all :good:

It says erase is not allowed in locked state . I think this is probably all she wrote for this one. I think I'm just going to send it back tbh, the whole reason I was trying to root it was because it didn't work with Sprint like they said it would. and I was wondering if I could find a way too make it work with custom software. Thanks for trying

Are you able to flash one of these Fastboot ROMs?

Maybe Sideload can work!
https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t here is official stock file.
https://forums.oneplus.com/threads/how-to-do-flash-through-adb-sideload.509377/
https://www.the***********.com/sideload-ota-update-stock-recovery-adb/
Please refer above links for your knowledge purpose maybe it can help.....

I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.

kschmitz4 said:
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
Click to expand...
Click to collapse
I ended up needing to flash the fastboot 10.0.3 firmware and was able to do a local upgrade to 10.0.4 that way, then flashing a patched boot.img via fastboot

I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?

kschmitz4 said:
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
Click to expand...
Click to collapse
How did you flash twrp with it oem locked??That doesnt make sense

I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.

kschmitz4 said:
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
Click to expand...
Click to collapse
You should have no issues reflashing the stock images

I cannot flash anything. Because my OEM state is locked.

Boot to Stock Recovery ?
Holding for a long time Volume Down + Power Buttons while booting your phone ?

Volume down plus power button takes me to "Your device is corrupt and will not boot"

kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Looks like you will need the MSM tool to fix this issue. You'll have to contact OP support and they will remote in your PC, load their software and flash it 100pct back to stock.
Also, disconnect them before they can delete the MSM tool so we can have it here in the community

kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Press volume up/down and power, reboot to fastboot. Unlock bootloader again. Install update from settings, reboot and install it again. (local install)
Factory reset in setting, reboot fastboot, lock bootloader. Reboot and untick unlock bootloader in developer settings.

Don't know if it's too late but I believe there's a working MSM tool now