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.

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.

Root to flash TWRP?

I have a doubt that,In some of the devices we can install twrp using adb commands without rooting our device. But in many new generation devices there are always posts or videos about, first rooting the devices and then installing twrp.
So, what are the reasons that we don't directly flash twrp on moto g5 using adb commands, and first we prefer getting device unlocked by getting unlock code.
And for my general doubt can anyone please explain me what does "unlocking a bootloader" means and what does "OEM" means. Also if i unlock OEM using developer options it doesn't show up in the bootloader menu.
I request to please explain elaborately as I am just new to all this.

To flash Twrp you need unlocked bootloader. Rooting has nothing to do with it, that is OS side. If bootloader is unlocked, you can fastboot flash Twrp. However, I suggest if you are unsure but want to have custom ROMs, you should use the tool that does it all for you.
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
This tool will get your unlock information which you must submit on the moto unlock site. They will send you email with your bootloader key. Once you unlock bootloader through the tool, you can also flash twrp through the tool. When you have flashed twrp, you must wipe data in twrp and flash SuperSU to get past the data encryption. There is plenty of info around here on these subjects, I would suggest to read very carefully all the guides before continuing.

Moto G4 plus bootloader question

Hi to all members,
I want to relock my G4 plus bootloader, I tried the guides to relock however seems there was a problem locking the bootloader after april 2018 securuty patch ( stock android 7 )
Any way to lock this bootloader ?
Many thanks

When you're relocking your bootloader, what errors are you encountering?
Make sure that OEM unlocking is enabled in Settings>Developers options, and also what device do you have? If your bootloader version is B1:07 you can use the April 2018 firmware. However, if your bootloader version is B1:09 you must use the Oreo firmware to relock - you cannot lock your bootloader with firmware older than the bootloader and you cannot downgrade the bootloader.

echo92 said:
When you're relocking your bootloader, what errors are you encountering?
Make sure that OEM unlocking is enabled in Settings>Developers options, and also what device do you have? If your bootloader version is B1:07 you can use the April 2018 firmware. However, if your bootloader version is B1:09 you must use the Oreo firmware to relock - you cannot lock your bootloader with firmware older than the bootloader and you cannot downgrade the bootloader.
Click to expand...
Click to collapse
Thank you Echo92,
So i flashed with Oreo 8.1.0 and still have bootloader message on screen on start up.. my bootloader version is B1.09 my device is moto g4 plus xt1642 with security patch Dec 1st 2018... What am I doing wrong ?
thanks

mercuryrob said:
Thank you Echo92,
So i flashed with Oreo 8.1.0 and still have bootloader message on screen on start up.. my bootloader version is B1.09 my device is moto g4 plus xt1642 with security patch Dec 1st 2018... What am I doing wrong ?
thanks
Click to expand...
Click to collapse
Alright, what commands are you using to lock your device? Are you using the OEM lock script or do your commands list include the three OEM lock commands?
Can you also confirm that your OEM unlocking toggle is on (in settings>developer options)?

echo92 said:
Alright, what commands are you using to lock your device? Are you using the OEM lock script or do your commands list include the three OEM lock commands?
Can you also confirm that your OEM unlocking toggle is on (in settings>developer options)?
Click to expand...
Click to collapse
Ok many thanks, my oem unlocking is greyed out ( says Bootloader is already unlocked )
I am using minimal adb and fastboot ( watched a Youtube video saying put the unzipped firmware ( Oreo 8 TWRP-athene-8.1.0-OPJ28.111-22 ) into the adbfolder and open a cmd but there is no oem lock script there !
Thanks

mercuryrob said:
Ok many thanks, my oem unlocking is greyed out ( says Bootloader is already unlocked )
I am using minimal adb and fastboot ( watched a Youtube video saying put the unzipped firmware ( Oreo 8 TWRP-athene-8.1.0-OPJ28.111-22 ) into the adbfolder and open a cmd but there is no oem lock script there !
Thanks
Click to expand...
Click to collapse
Mind if I ask which Youtube video you used?
That firmware zip you mentioned does not seem suitable for locking the bootloader (if it's a TWRP flashable zip as implied in the name, you cannot lock your bootloader with that). I would recommend getting the stock Oreo firmware from here https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 In addition, you could either download the OEM lock script as mentioned in that thread (it's separate to the firmware usually) or use the listed commands in the thread's procedure to lock your bootloader. I've used this firmware and those commands to re-lock my XT1642 (on the retgb software channel).
Whilst you're downloading the above firmware, also you may wish to root your device with magisk (you will have to temporarily boot into TWRP and flash magisk), which might also activate your OEM unlocking toggle. Ensure you're also signed into your Google account on your device. That should hopefully enable your OEM unlocking toggle and then permit your device's bootloader to be lockable again.

echo92 said:
Mind if I ask which Youtube video you used?
That firmware zip you mentioned does not seem suitable for locking the bootloader (if it's a TWRP flashable zip as implied in the name, you cannot lock your bootloader with that). I would recommend getting the stock Oreo firmware from here https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 In addition, you could either download the OEM lock script as mentioned in that thread (it's separate to the firmware usually) or use the listed commands in the thread's procedure to lock your bootloader. I've used this firmware and those commands to re-lock my XT1642 (on the retgb software channel).
Whilst you're downloading the above firmware, also you may wish to root your device with magisk (you will have to temporarily boot into TWRP and flash magisk), which might also activate your OEM unlocking toggle. Ensure you're also signed into your Google account on your device. That should hopefully enable your OEM unlocking toggle and then permit your device's bootloader to be lockable again.
Click to expand...
Click to collapse
Many thanks Echo,
This was the youtube video I watched - https://www.youtube.com/watch?v=qouoo1zGIJs&t=145s
I shall try the link you provided and post my results.
Once again many thanks

Sorted now !
mercuryrob said:
Many thanks Echo,
This was the youtube video I watched - https://www.youtube.com/watch?v=qouoo1zGIJs&t=145s
I shall try the link you provided and post my results.
Once again many thanks
Click to expand...
Click to collapse
All done ! Bootloader locked reflashed using your link . Many thanks Echo

Did I completely brick my T-Mobile 6T?

Hello, I recently purchased the T-mobile version of the 6T (bad idea) that had a locked bootloader, and tried to flash it to the international version so I can root the device. I followed this post in hopes of achieving it. The device will no longer boot. The screen quickly flashes with a Oneplus logo with "fastboot mode" underneath then I am met with this error: "Build version and HW is not match!". Is it completely bricked? Can I flash back to a T-Mobile OS?
If it is truly bricked I am curious if someone could explain why it may have happened. As in, has T-Mobile changed some the checks involved with flashing to the international version? Or was it because the device was running the latest Oxygen OS, is it impossible to downgrade this way? I am genuinely curious and want to take this as a bitter learning experience.
Thanks for your input.

It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.

Pain-N-Panic said:
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Click to expand...
Click to collapse
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7

Did you get it all figured out? If not here's a semi detailed version of what I had to do with my tmobile 6t, because I had issues as well. Mainly my phone not showing up in msm tool. Only wanted to work after it had Android 9. Also I had little sleep the night I did this so I'm trying to recall the best I can.
Assuming your phone shows in msm tool at this point
Used msm tool to flashed older A9 ops https://androidfilehost.com/?fid=11410963190603895067
Boot in and enable adb and oem bootloader unlock
Boot to bootloader and unlock it
Flashed first A10 OOS https://androidfilehost.com/?fid=4349826312261819701
Flashed 10.3.7 to both slots with twrp https://androidfilehost.com/?fid=10763459528675591630
Flash rom
Flash Magisk
Profit
Some of this could be redundant, but my late night research and trial and error paid off.

GoldfishSnack said:
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Click to expand...
Click to collapse
Well I'm glad you were able to get it up and running. I highly suggest unlocking that bootloader as soon as you can....having an unlocked BL is key to getting out of a lot of bricked situations.