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.
Hi everyone,
I have made a terrible mistake... I flashed twrp before unlocking my bootloader. The phone boots then shows a message like "please update to the authorized image", and the get stuck into bootloader, do you have any idea how to recover that, because now we need to login on the phone to get bootloader unlock code and, obviously, I can't.
I flashed twrp by doing, once rooted with kingroot, dd if=/path/to/twrp.img of=/dev/block/by-name/recovery.
When I try to flash with fastboot I get FAILED (remote: Command not allowed), is any alternative flasher available or another way to get the unlock key? I thought about useragent modification to make huawei website thinks it's the phone. So if anyone could send me is useragent by PM I'd be thankful.
Hi all
I searched this, but I question here,
1 - When you unroot , put stock and update an ota, it blocks the bootloader?
2 - and the when unlocked, format all to factory?
3 - In what moment the bootloader is blocked? only when first unlock is done?
Thanks in advance, I have an honor 7 and I Know how it works, but this honor 8 L09?
1. probably
2. u can prevent factory reset if unlocked earlier
3. idk what the question means
LastStandingDroid said:
1. probably
2. u can prevent factory reset if unlocked earlier
3. idk what the question means
Click to expand...
Click to collapse
3 - well, the main question is if in every ota update , it locks the boootloader and when unlock, format all ...this is the main question
in honor 7, I unroot, apply the ota and root again with no problems
sorry for my english
deadko said:
3 - well, the main question is if in every ota update , it locks the boootloader and when unlock, format all ...this is the main question
in honor 7, I unroot, apply the ota and root again with no problems
sorry for my english
Click to expand...
Click to collapse
lock bootloader i can't tell, if it does u can unlock the bootloader and again, and straight after flash TWRP it won't wipe the internal SD
Hi. bought an al-10 from china which apparently is flashed. There are a few things not working on phone so apart from trying to get help from seller, i have attempted the flashing myself. i have gone thru a few threads and watched TK vid on flashing twrp and rooting and roni on unlocking bootloader. now, considering the device is flashed i understand the bootloader is still unlocked (in fastboot says phone unlocked). in dev options there is no OEM unlocking option. i cannot get lock state through the code in dialler. when i try to flash twrp, sending recovery OKAY, writing recovery FAILED <remote: command not allowed> so cannot really get to rooting stage
Thank you for the time.
ptwarecki said:
Hi. bought an al-10 from china which apparently is flashed. There are a few things not working on phone so apart from trying to get help from seller, i have attempted the flashing myself. i have gone thru a few threads and watched TK vid on flashing twrp and rooting and roni on unlocking bootloader. now, considering the device is flashed i understand the bootloader is still unlocked (in fastboot says phone unlocked). in dev options there is no OEM unlocking option. i cannot get lock state through the code in dialler. when i try to flash twrp, sending recovery OKAY, writing recovery FAILED <remote: command not allowed> so cannot really get to rooting stage
Thank you for the time.
Click to expand...
Click to collapse
And the device is? Did u use fastboot flash recovery recovery.img
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
And the device is? Did u use fastboot flash recovery recovery.img
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
Hi.
Sorry device is honor 8 frd-al10.
It was fastboot flash recovery twrp_cn.img
I have just received a message from seller stating it was flashed with eu firmware. I have it as frd c900b120. Should i be using the image for FRD-L09 or FRD-L19 in this case ?
Thank you.
Hello mates!
Yesterday I accidentally bricked my phone and I spent ours and ours on this and others forums to find solution but without succes, so here is what was happen:
I was on L21C432B380 firmware, stock, bootloader locked, without root acces. So I tried to flash ROM 7.1.2 AOSP by Meticulus. I followed step by step guide. I succesfully unlocked bootloader using fastboot. Then I flashed TWRP again using fastboot so I can downgrade to EMUI 4.X and that was succesfull also. After that I flashed oem-info using TWRP and flashed stock UPDATE.ZIP using three button method, both succesfully but when phone tried to boots up It shows message "No OS installed".
My entire system and data was deleted, there is no recovery, bootloader is again locked, I have only managed to get into fastboot mode using adb
Every single command I tryed to run in cmd results in this message: "FAILED (remote: Command not allowed)
Somehow I need to install Firmware using fastboot but don't know how cause bootloader is again locked
My knowledge about this things is above average but I cannot "google" the problem
Please help and thanks in adavnce
Tomislav Veličanstveni said:
Hello mates!
Yesterday I accidentally bricked my phone and I spent ours and ours on this and others forums to find solution but without succes, so here is what was happen:
I was on L21C432B380 firmware, stock, bootloader locked, without root acces. So I tried to flash ROM 7.1.2 AOSP by Meticulus. I followed step by step guide. I succesfully unlocked bootloader using fastboot. Then I flashed TWRP again using fastboot so I can downgrade to EMUI 4.X and that was succesfull also. After that I flashed oem-info using TWRP and flashed stock UPDATE.ZIP using three button method, both succesfully but when phone tried to boots up It shows message "No OS installed".
My entire system and data was deleted, there is no recovery, bootloader is again locked, I have only managed to get into fastboot mode using adb
Every single command I tryed to run in cmd results in this message: "FAILED (remote: Command not allowed)
Somehow I need to install Firmware using fastboot but don't know how cause bootloader is again locked
My knowledge about this things is above average but I cannot "google" the problem
Please help and thanks in adavnce
Click to expand...
Click to collapse
Hello man,
Dont know why u do that (downgrade to MM)...
Explicitly written for flash AOSP 7.1.2 to be on emui5 (were u was)...
Flashing oem also relocked your bootloader (written ton of times in threads)....
Now using fastboot re-unlock bootloader re-flash TWRP.
If u maked a full backup just use it, otherwise try to follow this guide..
https://forum.xda-developers.com/showpost.php?p=73619842&postcount=44
Hope u will resolve.
Regards
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
pootler said:
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
Click to expand...
Click to collapse
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
sd_shadow said:
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
Click to expand...
Click to collapse
THanks for the reply.
Strange, thought I had already updated this
I went back to stock firmware and decided to flash with fastboot all individual files.
At some point, I got the same ''verification failed' but the command line suggested flashing system, boot, and ( something else, cant remember) again.
i did this this, and this time, no errors occured, and I had a complete install, with a locked bootloader, and no bootloader warning screen.!
Yay - result
Thanks again for your advice - I will remember it for the future.