unable to lock bootloader moto g4 plus :-> XT1643 - Moto G4 Plus Questions & Answers

I have moto g4 plus. recently i rooted it and everything worked fine
but when i applied the nougat ota upgrade
i m unable to downgrade it to mm stock ROM or stock ROM
neither, able to lock bootloader even cant flash with recovery
every time i flash it it shows "preflash validation failed " and "piv sign not valid " for the boot and recovery image
my stock ROM is not corrupt
one more thing it also display's "security version downgrade"
pls guys help me

1. enable developer option
2. enable oem unlock
3. get unlock code from motorola website
4. unlock via fastboot
Sorry, misread. I think you want to unlock BL.

Did you read XDA rules...? Did you search...?
There is already a thread for ReLock issue..
As you will read,
You can't downgrade bootloader if once updated...
Don't Mess with bootloader unless want a brick....
According to my views, there are no benefits for ReLocking unless want to sell phone and make buyer fool... LoL...

Related

[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.

[Solved] How to Re-lock Bootloader and go back to stock?

Hello,
I want to relock the bootloader and go back to stock.
I tried flashing stock firmware using fastboot.
fastboot oem lock begin
flashed stock firmware
fastboot oem lock
But Bootloader is still unlocked.
I got message as first flash full stock system. Something like that. Don't remember as I tried this a week ago.
Any help will be highly appreciated.
Thank you in advance.
Edit : I also tried the Windows tool provided by one of the members but it failed too.
I used the same to unlock in the first place.
I think it depends on what you want to achive. While you might be able to re-lock the bootloader (which means it can't be flashed without being unlocked again), you will never ever get rid of the unlock message again. This - to my understanding - is an efuse which is permanently set. If you want to remove the unlocked bootloader boot message, I'd stay unlocked and would just flash a different boot logo (logo.bin) where the unlocked gfx are replaced with the standard gfx thus showing the standard boot logo.
I would like to relock the bootloader altogether.
I don't think you can. You can lock it but you can't remove the warning that it has been tampered with.
I don't care about the warning.
I just want to re-lock it.
Flashing the Official firmware for my Country - India did the job.
Last time I tried with firmware for ASIA.
I don't see any reason for that to fail but you never know.
Thanks for replying.
hey can you give me the link for that rom im also using the indian version but unable to lock the bootloader

unlock after relock

several questions in no particular order:
Does the "OEM Unlocking" toggle do anything on the XT1572?
If I issue the fastboot OEM LOCK command after having sucessfully unlocked the device before, do I need to go through the full data wipe+send oem data+flash unlock code process again?
Lastly, I was able to flash the MM firmware for my Single SIM AISA model XT1572 despite having the bootloader locked (I think).
Is that normal that I can flash the official moto firmware using just fastboot without having to tweak with anything else?
I presume that since the digital signatures are correct the bootloader has no issue accepting the MM files.
Not quite the end of the world if I have to wipe everything and start over (it's only been a day) but I regret not knowing earlier. Nor did I expect to get this far with a relocked boot loader. Was trying to add SuperSU and found that while I can overwrite flash the stock recovery I cannot flash TWRP.
psyvenrix said:
several questions in no particular order:
Does the "OEM Unlocking" toggle do anything on the XT1572?
If I issue the fastboot OEM LOCK command after having sucessfully unlocked the device before, do I need to go through the full data wipe+send oem data+flash unlock code process again?
Lastly, I was able to flash the MM firmware for my Single SIM AISA model XT1572 despite having the bootloader locked (I think).
Is that normal that I can flash the official moto firmware using just fastboot without having to tweak with anything else?
I presume that since the digital signatures are correct the bootloader has no issue accepting the MM files.
Not quite the end of the world if I have to wipe everything and start over (it's only been a day) but I regret not knowing earlier. Nor did I expect to get this far with a relocked boot loader. Was trying to add SuperSU and found that while I can overwrite flash the stock recovery I cannot flash TWRP.
Click to expand...
Click to collapse
As far as I am concerned relocking the bootloader wont wipe your data and yes about the question regarding the stock firmware
PS: Dont relock your bootloader once you unlock it the warranty doesnt come back even if you lock it again

relock bootloader

What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
dhenewar said:
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
Click to expand...
Click to collapse
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
echo92 said:
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
Click to expand...
Click to collapse
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
dhenewar said:
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
Click to expand...
Click to collapse
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
echo92 said:
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
Click to expand...
Click to collapse
Thanx bro I will try it out .. yep bro I got it in service center n they told me .. No way of fixing it .. Aahh n that's it ? .well there was option change of hardware price was half of the phone cost ..better to buy new one ?

oem unlock bricked motog4 plus

I was using lineageos in my moto g4 plus. I wanted to flash stock again, so i did that. my bad I downloaded an update. After that i could pass the bootlaoder it shows an error message "failed to initialize partition table" . Recovery mode is also not working. since oem is locked i can not flash recovery, or any rom. what should i do to unlock the oem and flash a rom?
sunny_mathew said:
I was using lineageos in my moto g4 plus. I wanted to flash stock again, so i did that. my bad I downloaded an update. After that i could pass the bootlaoder it shows an error message "failed to initialize partition table" . Recovery mode is also not working. since oem is locked i can not flash recovery, or any rom. what should i do to unlock the oem and flash a rom?
Click to expand...
Click to collapse
almost the same here. my girlfriend´s moto g4 entered into bootloop, even though we havent tampered with custom roms, root or anything. so its got everything just like lenovo intented, rom, recovery, everything.
we managed to unlock oem at moto´s website, but since the system doesnt start, we cant enable it from developer options.
the bootloop takes us out of fastboot. and within fastboot we can scroll through the options but cant select any option.
is her phone a brick? or is there something we can do to save it?
we cant afford another phone nor tech service (right now), and she cant afford to be phoneless because of her job. so if anyone knows of anything it could help us a whole lot.
edit: also it doesnt charge

Categories

Resources