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.
Same as the title
You see Legal Information on Setting? It say the bootloader is already open
Need to unlock BL friends, please send my E-mail, I will reply to your message in the E-mail.
My E-mail: [email protected]
1944 said:
You see Legal Information on Setting? It say the bootloader is already open
Click to expand...
Click to collapse
Open does not mean unlocked. Open means you have root access. Unlock means you can access the recovery partition and flash anything you want with a custom recovery.
https://forum.xda-developers.com/meizu-mx/development/recovery-twrp-bl-unlock-m3-note-t3684052 See the tutorial
With G version (6.3.0.0G), lk does not have fastboot unlock cmd. I had disassembled 6.1.3.3G lk to check and confirmed. Instead, A version does have it because of nougut port (Ie, 6.3.0.2A fw).
I knew it because tried today. I rooted and run global.sh then install A version fw on my G version phone. The drawback is fastboot USB is no longer working. So winxp PC USB connections to m3note fail. Lucky the phone still working.
So if somebody told you G version can unlock bootloader, then you have to pay attention. I assumed you less likely got the A version phone but a G version instead. If you are lucky with A version, you can have a try. FYI the above disassembled A version of lk does have below cmd:
oem p2u
oem reboot-recovery
oem unlock
oem lock
oem key
oem lks
flashing unlock
flashing lock
flashing get_unlock_ability
Many more....
Regards.
Hi, I need help to install a working rom. Any build will do.
I have a P9 lite, 3gb, dual sim. Bought in Norway. I think Its called VNS-L31C432.
I updated to Nougat but the bluetooth does not work.
So i want another rom with bluetooth. But now Im stuck on VNS-L31C900B300.
The bootloader screen shows "Phone unlocked" (I unlocked it with SRKTool) and "FRP lock"
In developer setting the "enable OEM unlock" is off and grey color.
I cannot use the dload-method, I get "software install failed!"
I cannot install twrp with fastboot, I get "FAILED (remote: Command not allowed)"
I also tried to relock bootloader (fastboot oem relock *****************" but I get "FAILED (remote: root type is risk)".
Seem like SOMETHING is stopping me from messing more with the phone.
Please point me in the right direction, someone?
try to rollback with those 2 files i provide you,
1 st the small firmware and after the 1.6gb one ~ dont forget this !
http://download-c1.huawei.com/download/downloadCenter?downloadId=93788&siteCode=nl
http://download-c1.huawei.com/download/downloadCenter?downloadId=93803&siteCode=nl
magnemann said:
Hi, I need help to install a working rom. Any build will do.
I have a P9 lite, 3gb, dual sim. Bought in Norway. I think Its called VNS-L31C432.
I updated to Nougat but the bluetooth does not work.
So i want another rom with bluetooth. But now Im stuck on VNS-L31C900B300.
The bootloader screen shows "Phone unlocked" (I unlocked it with SRKTool) and "FRP lock"
In developer setting the "enable OEM unlock" is off and grey color.
I cannot use the dload-method, I get "software install failed!"
I cannot install twrp with fastboot, I get "FAILED (remote: Command not allowed)"
I also tried to relock bootloader (fastboot oem relock *****************" but I get "FAILED (remote: root type is risk)".
Seem like SOMETHING is stopping me from messing more with the phone.
Please point me in the right direction, someone?
Click to expand...
Click to collapse
Hello,
If you are already at your last chance
hope this will give you the "right direction"...
It looks very similar than your situation...
Regards:fingers-crossed:
https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Kcetin20 said:
try to rollback with those 2 files i provide you,
1 st the small firmware and after the 1.6gb one ~ dont forget this !
http://download-c1.huawei.com/download/downloadCenter?downloadId=93788&siteCode=nl
http://download-c1.huawei.com/download/downloadCenter?downloadId=93803&siteCode=nl
Click to expand...
Click to collapse
Thanks for answering
I placed the rollback file UPDATE.APP in dload folder on sd card and held volup+voldown+power.
It updated sucessful, then restarted. Then it started reset user data but stopped at 16% with "reset failed".
So I did not try to flash the main file.... Hmm..
And one more thing.
If I hold volup key when booting, I come to a EMUI screen where I can have a factory reset.
But factory reset fails at 18%. Dont know why.
wiping cache here works ok.
Dadditz said:
Hello,
If you are already at your last chance
hope this will give you the "right direction"...
It looks very similar than your situation...
Regards:fingers-crossed:
https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Click to expand...
Click to collapse
Thanks, man.
Yes it IS similar. But I fail at step 3 in relocking bootloader.
"fastboot oem relock ******************"
gives
FAILED (remote: root type is risk)
finished. total time: 0.006s
so I cannot continue the rest of the guide. :crying:
Cya all tomorrow. Here its bedtime.
Hi all, I had official MIUI Global 11 on Android 10 on a phone with unlocked bootloader and a recovery. I wanted to re-lock the bootloader, so I went to fastboot and I gave the command to lock it.
Obviously (but I didn't even imagine it) the devide DID lock, but now it doesn't start any longer. ""System destroyed" is the message.
What I want to get is one of these two results: having a working phone OR having everything erased.
What I have already tried is:
- installing a firmware via fastboot: failed because the bootloader is locked
- flashing single .img via fastboot: failed because the bootloader is locked
- erase partitions: failed because the bootloader is locked
- unlock again the phone via fastboot: failed
- unlock again the phone via Mi Unlock: failed because missing authorization in developer options
Let's add the fact that I don't have windows, but Mac, that reduces the available options.
ANY SUGGESTIONS?
You can use Platform tools in windows.As far as i know platform tools can be used both locked and unlocked bootloader.You can search on YouTube how to flash mi phones through platform tools.
francanna said:
Hi all, I had official MIUI Global 11 on Android 10 on a phone with unlocked bootloader and a recovery. I wanted to re-lock the bootloader, so I went to fastboot and I gave the command to lock it.
Obviously (but I didn't even imagine it) the devide DID lock, but now it doesn't start any longer. ""System destroyed" is the message.
What I want to get is one of these two results: having a working phone OR having everything erased.
What I have already tried is:
- installing a firmware via fastboot: failed because the bootloader is locked
- flashing single .img via fastboot: failed because the bootloader is locked
- erase partitions: failed because the bootloader is locked
- unlock again the phone via fastboot: failed
- unlock again the phone via Mi Unlock: failed because missing authorization in developer options
Let's add the fact that I don't have windows, but Mac, that reduces the available options.
ANY SUGGESTIONS?
Click to expand...
Click to collapse
I think that the only way to flash it successfully again is to use QPST ,but you need to open the phone remove battery and get 9008 port , check in YouTube.
I want to root my oneplus 8 pro IN2020. but when i try to unlock bootloader with
Code:
fastboot oem unlock
I have following error:
FAILED (remote: 'Flashing Unlock is not allowed)​Phone was have been installed and updated to latest version. No sim yet.
I'm using windows 10 and latest platform sdk.
Do you have any clues ?
I got the phone on banggood with oneplus sticker with MEID and CM sticker...
if it is a branded phone how to get bin file or unlock code. The unlock_token page is not available in my region...
on fastboot screen i do not have any bootloader version nor baseband version...
Did you connect your phone to the internet and enable Bootloader Unlocking in Developer Settings?
Good catch !
Many thanks....
No problem, seems to be a common mistake around here