Database Users

[Q] bootloader issues

So a while ago I rooted my phone but messed it up because I uninstalled a few too many system apps. I just dealt with it for a few months since I could still make calls (but not much else). I finally bit the bullet to look into flashing the stock rom again, but to do so it looked like I had to install a custom recovery, but to do that, unlock the bootloader. So I first unlocked the bootloader using motopocalypse (batch file didn't work but apk did), and got the expected BOOTLOADER UNLOCKED message at bootup, with fastboot saying unlocked, code 3. I then tried flashing CWM recovery via Rom Manager, and it seemed successful, but I was unable to boot to it either from the UI of ROM manager or from holding the buttons during bootup, it would just hang for a few more minutes than normal at the BOOTLOADER UNLOCKED screen, then boot up like normal. So I kept reading, found RSDlite, and was able to flash the stock rom, which I downloaded from the internet and the phone boots up fine, but now fastboot says locked, status code 2, and motopocalypse does not unlock it again (either the batch file or the apk), but I still get the BOOTLOADER UNLOCKED message at bootup. So I'm not sure if my bootloader is unlocked or not and if I can proceed with installing CWM recovery again, so i can make a full backup in case I mess something up again.
So how do I reunlock the bootloader, or verify if it's locked or not?

First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk

RikRong said:
First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
FB screen:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 00:54:39)
eMMC Info: Size 8GB
Device is LOCKED. Status code: 2
Battery OK
Transfer Mode:
USB connected
Fastboot reason: Reboot to bootloader
usb connected
I've tried reflashing with RSD previously but no change. I could try it once more if you want.
Not entirely sure what you're asking for with the firmware version, but the image I used was for android 4.4.2, version 183.46.10.XT907Verizon.en.US.

modemman11 said:
Device is LOCKED. Status code: 2
Click to expand...
Click to collapse
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!

To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Code 3 as well.
Sent from my XT907 using XDA Free mobile app

rahimali said:
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!
Click to expand...
Click to collapse
Yes, that's why I'm asking. So I've got one vote for unlocked, one for locked. As I said though, motopocalypse isn't working a 2nd time.
AndyYan said:
To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Click to expand...
Click to collapse
I would like to flash custom ROMs later down the road, but for now I just want to get the stock stuff going.
On a side note, the version of the image I downloaded was 183.x.x, but my mother, who has the same phone, purchased at the same time, and has never rooted it or anything, has version 182.something, and that is also the version I had before I started messing with the bootloader/recovery stuff. The two versions were released at the same time, but I don't know what determines which version you got if you just did OTA updates, or if it even matters. Speaking of OTA updates, the version I downloaded is prompting me to do an OTA update now to another 183.x.x version. I wonder if I'd be able to grab the 182.x.x ROM from my mom's phone without rooting it via fastboot or something.

The 182/183 does not matter regarding root/boot loader unlock its the .10/.15 that matters do not take the .15 without unlocking your boot loader....
We cannot teach people anything; we can only help them discover it within themselves.

So no other thoughts? What would happen if I flashed a custom rom/recovery with a locked bootloader? I tried flashing the ROM again and fb still says locked, code 2, and motopocalypse still doesn't do anything like it did the first time.

modemman11 said:
What would happen if I flashed a custom rom/recovery with a locked bootloader?
Click to expand...
Click to collapse
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
modemman11 said:
So how do I reunlock the bootloader, or verify if it's locked or not?
Click to expand...
Click to collapse
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock

lem22 said:
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
Click to expand...
Click to collapse
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.031s]
finished. total time: 0.031s
Still locked code 2 though. Looks like it wants an unlock code from Motorola's website, I tried following the steps to get the code but it says I'm not eligible for bootloader unlock. So unless there's another way to get the unlock code...

modemman11 said:
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
Click to expand...
Click to collapse
A "Code 0" locked device would refuse flashing an unofficial or older recovery. I have no idea about Code 2 though.

From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Same here, I can see what it means but cannot find any way to get back to code 3 other than using the unlock code from Motorola, which I am unable to obtain because it says I am not eligible. Surprising that someone hasn't cracked the unlock code yet or made a keygen, people are so eager to do it with pirated computer software before the software is even released.

I've read of someone getting locked status code 2 b4 from flashing an older gpt with rsd (if I remember correctly) I think all that was required to fix it and get unlocked again was to flash the latest gpt. Very important..... Are you sure when you were unlocked you didn't ota update to .15? Because flashing .10 gpt while on .15 may be what caused your false relock

Nope, no OTA update to .15. The ZIP I have of the rom does include the gpt.bin file with the same timestamp as all the other files. I suppose I could try reflashing the whole rom once again later...

Hmm strange, I went to find the old thread I read about the gpt relock issue but it's not exactly the same as your situation.
http://forum.xda-developers.com/showthread.php?p=51436123
Until now I didn't think relock was possible due to the way unlocking works. It's a physical change, a qfuse was blown when the motopocalypse apk was run the first time. It can't be unblown lol. Wish I knew what went wrong here.

Downgrade from 6.0 Indian Firmware to 5.1 EU Firmware. Is it possible?

Hi everyone,
I would like to know if is possible to dowgrande to a different country firmware (I'm not interested in the dual sim option). Anyone know if this is possible? I have a locked and non rooted moto x play. I've tried to follow this thread REMINDER HOW TO DOWNGRADE from 6.0 to 5.1.1, but the installation fail with this error:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse

lollo64 said:
Hi everyone,
I would like to know if is possible to dowgrande to a different country firmware (I'm not interested in the dual sim option). Anyone know if this is possible? I have an unlocked and non rooted moto x play. I've tried to follow this thread REMINDER HOW TO DOWNGRADE from 6.0 to 5.1.1, but the installation fail with this error:
Click to expand...
Click to collapse
Yes, downgrading is possible with unlocked bootloader (locked bootloader doesn't allow downgrading). The first 2 commands ("fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img") always fail when downgrading, and can be skipped without any issues, so if the error you got was for one of the first 2 commands just continue with the rest of the commands.

panart said:
Yes, downgrading is possible with unlocked bootloader (locked bootloader doesn't allow downgrading). The first 2 commands ("fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img") always fail when downgrading, and can be skipped without any issues, so if the error you got was for one of the first 2 commands just continue with the rest of the commands.
Click to expand...
Click to collapse
Thanks, I was start to supposing that the locked bootloader was the problem and you just confirmed. Unluckily right now I can't unlock the bootloader so I think I must wait for the release of the complete EU 6.0 Firmware.

lollo64 said:
Thanks, I was start to supposing that the locked bootloader was the problem and you just confirmed. Unluckily right now I can't unlock the bootloader so I think I must wait for the release of the complete EU 6.0 Firmware.
Click to expand...
Click to collapse
In your post you mentioned "unlocked" so i assumed you had unlocked the bootloader already. I'm afraid that downgrading is only possible if you unlock the bootloader, or you can wait for EU 6.0 full stock ROM to become available and try installing that (it might work as you'll be going from 6.0 ROM to 6.0 ROM).

panart said:
In your post you mentioned "unlocked" so i assumed you had unlocked the bootloader already. I'm afraid that downgrading is only possible if you unlock the bootloader, or you can wait for EU 6.0 full stock ROM to become available and try installing that (it might work as you'll be going from 6.0 ROM to 6.0 ROM).
Click to expand...
Click to collapse
Ooops, sorry. It was a typo, I've just fixed it. Yes, right now I'm waiting for the release of EU 6.0 full stock rom and then I'm going to retry to flash it!

lollo64 said:
Ooops, sorry. It was a typo, I've just fixed it. Yes, right now I'm waiting for the release of EU 6.0 full stock rom and then I'm going to retry to flash it!
Click to expand...
Click to collapse
Have you tried what panart said, about skipping the first 2 fastboot commands ?
I also downgraded to 5.1 skipping the first 2 lines and it was working fine.Only I had an unlocked bootloader at that moment ,but maybe it wil also works with a locked bootloader, not sure.

Sickaxis79 said:
Have you tried what panart said, about skipping the first 2 fastboot commands ?
I also downgraded to 5.1 skipping the first 2 lines and it was working fine.Only I had an unlocked bootloader at that moment ,but maybe it wil also works with a locked bootloader, not sure.
Click to expand...
Click to collapse
Yes, I've tried both. With and without the first two commands (fastboot flash partition gpt.bin / fastboot flash bootloader bootloader.img), but it fails in every case. Purposely I get the errors when I launch this commands:
Code:
- fastboot flash boot boot.img
- fastboot flash system system.img_sparsechunk.*
All the other instructions work fine.

http://forum.xda-developers.com/showpost.php?p=65423306&postcount=475
24.65-33 Full EU
You can flash it directly On any XT1562

Is it possible to relock the bootloader?

I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks

Yes. Flash complete stock everything, boot into bootloader, connect to PC, and "fastboot oem lock".

Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader

Kevinkuensken said:
Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader
Click to expand...
Click to collapse
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!

Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend

Kevinkuensken said:
Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend
Click to expand...
Click to collapse
Boot into bootloader, not EDL.

Erahgon said:
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!
Click to expand...
Click to collapse
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.

BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Locking it again is good for when you want to sell the device or send it in for warranty repair.

BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Yeah, the unlock procedure is the same as before. If you didn't restore the original boot image before the relock, then it's just a matter of booting into fastboot and unlocking the device. Note that this will cause your data to be wiped as well!

If you restore your boot.bin backup file from when your device was locked, does this lock the bootloader? "fastboot oem lock", "fastboot flashing lock" nor "fastboot oem device-info" does nothing for me. Is there any other way to check if your bootloader has been relocked?
Thanks

H0lmEd said:
I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks
Click to expand...
Click to collapse
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!

joaste said:
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!
Click to expand...
Click to collapse
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT

sauerkraut17 said:
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT
Click to expand...
Click to collapse
Thanks for the answer.
But there are a few files to flash before using that command according to this thread.
Doesn't anything need to be flashed again (e. g. stock files or anything)?

Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?

sauerkraut17 said:
Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?
Click to expand...
Click to collapse
My phone is only a few days old. I'm debating whether to keep it or not (considering the Mate 9, but the price is not the same - love the form factor and bigger screen though - sound won't be the same and I think I'll miss the MiPop button on the Axon (never thought that would happen )).
I'm on the latest MM (B10 - the A2017G model).
Following the mentioned thread, I got to the point of installing TWRP (the signed version), only to realize that besides making backups, there is not much else I can do with that without unlocking the bootloader. I really just wanted to flash supersu and install adaway fro the time being until development matured for this phone (maybe also play around with viper - had great results on my LG G4).

HI, I get the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock". Any way to fix this?

Guys, can anyone help me? I really need to lock the bootloader!
How can I fix the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock"?
I'm on MM B11 Stock.
https://i.imgur.com/fdkgYs6.jpg

Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.

Flash Recovery -> FAILED (remote: Command not allowed)

Hello Guys,
After serveral month with TWRP & other stuff I've flashed stock B161 today.
Now I want to flash TWRP because of SuperSU.
I opened Minimal ADB&Fastboot (Work's fine the last month) and booted in bootloader. Then I've typed:
fastboot flash recovery recovery.img
And got the alert:
FAILED (remote: Command not allowed)
Yes, Bootloader is unlocked.
OEM-Unlock is activated to.
Thanks for every help und sorry for bad english.

Playleyx said:
Hello Guys,
After serveral month with TWRP & other stuff I've flashed stock B161 today.
Now I want to flash TWRP because of SuperSU.
I opened Minimal ADB&Fastboot (Work's fine the last month) and booted in bootloader. Then I've typed:
fastboot flash recovery recovery.img
And got the alert:
FAILED (remote: Command not allowed)
Yes, Bootloader is unlocked.
OEM-Unlock is activated to.
Thanks for every help und sorry for bad english.
Click to expand...
Click to collapse
it's some kind of bug i think, it says it's unlocked, but it isn't, try unlocking again. it's only unlocked if you get a warning everytime you boot up the phone

mjz2cool said:
it's some kind of bug i think, it says it's unlocked, but it isn't, try unlocking again. it's only unlocked if you get a warning everytime you boot up the phone
Click to expand...
Click to collapse
My phone in fastboot show me bootloader unlocked but when boot up the phone that warning message dont show up.what that mean??its unlock or not????

Hipom said:
My phone in fastboot show me bootloader unlocked but when boot up the phone that warning message dont show up.what that mean??its unlock or not????
Click to expand...
Click to collapse
it's not unlocked if it says command not allowed.
try unlocking again, it should work after that
when you flash a stock rom, the bootloader gets locked again, but for some reason it still says unlocked in fastboot mode. it's probably to prevent you from restoring warranty after unlocking your device

Thank you!
You are right, the warning-message isn't there anymore.
I will try to unlock it again tomorrow, I hope that it work without problems.

Playleyx said:
Thank you!
You are right, the warning-message isn't there anymore.
I will try to unlock it again tomorrow, I hope that it work without problems.
Click to expand...
Click to collapse
Its works?
I have same problems ((((

Same problem
shmagiGEO said:
Its works?
I have same problems ((((
Click to expand...
Click to collapse
How did you do it ???

Playleyx said:
Thank you!
You are right, the warning-message isn't there anymore.
I will try to unlock it again tomorrow, I hope that it work without problems.
Click to expand...
Click to collapse
hello, i also have the same problem with huawei gt3 nmo l31 device. did you resolve the problem. please tell me if something worked

umunais said:
hello, i also have the same problem with huawei gt3 nmo l31 device. did you resolve the problem. please tell me if something worked
Click to expand...
Click to collapse
Yes it works. I had the same problem last night. L21 P9lite

umunais said:
hello, i also have the same problem with huawei gt3 nmo l31 device. did you resolve the problem. please tell me if something worked
Click to expand...
Click to collapse
as i said before in this thread, unlock the bootloader

FRP locked can be problem also. My experience.

I have this problem on honor7 but it happens when I try to erase a partition I
I also can't root I installed SuperSU with TWRP but no root access after reboot

pospi69 said:
FRP locked can be problem also. My experience.
Click to expand...
Click to collapse
I have that problem. Phone is unlocked and FRP locked. I am not able to flash TWRP. For the time being I am stucked. I get a message when booting that the phone is unlocked and unsafe and so on... Someone have a solution?
Skickat från min ONEPLUS A3003 via Tapatalk

Look on YouTube how to remove FRP lock! Its just small cheat in android. (FRP=FACTORYRESETPROTECTION)
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
I fixed that after some ways to fix. Try some of these on YT. It worked for me.

If I cannot get to the dialer, am I still able to unlock bootloader somehow? I do not have unlock code.

peskystats said:
If I cannot get to the dialer, am I still able to unlock bootloader somehow? I do not have unlock code.
Click to expand...
Click to collapse
same problam my honor bln-l21 frp lock not flash any thing recover , boot etc remot command error

How to install stock rom

I had several ROMs on my pP9 lite and after some time I decidet to unroot and go stock again. I don't remember how, but a locked the bootloader and installed stock rom.. everything OK, but after an OTA update I got no bluetooth and I can't install now any other rom cuz I lost my OEM unlock code and now I can't get it from Huawei... When I go to fastboot, I have PHONE Unlocked and FRP Unlocked too, but I can't flash the recovery... it's like the bootloader is unlocked, but it don't let me flash my EliteTWRP image... I get FAILED (remote: Command not allowed)
Any sugestions on how to fix this? I want to give this phone to my nephew, it is still a good phone for some games and whatsapp
thanks :angel:

ihavenokia said:
I had several ROMs on my pP9 lite and after some time I decidet to unroot and go stock again. I don't remember how, but a locked the bootloader and installed stock rom.. everything OK, but after an OTA update I got no bluetooth and I can't install now any other rom cuz I lost my OEM unlock code and now I can't get it from Huawei... When I go to fastboot, I have PHONE Unlocked and FRP Unlocked too, but I can't flash the recovery... it's like the bootloader is unlocked, but it don't let me flash my EliteTWRP image... I get FAILED (remote: Command not allowed)
Any sugestions on how to fix this? I want to give this phone to my nephew, it is still a good phone for some games and whatsapp
thanks :angel:
Click to expand...
Click to collapse
Hello,
even if it says it's unlocked, it's actually locked.
So you need to unlock it again if you want to flash stuffs...
Good luck
P.S.: About your other post... You cannot flash with dload method on android 7,
you need to use Elite recovery and HWOTA method or Huawei Recovery Updater to flash the firmware
you want. ( be sure you choose the correct firmware )
Cheers