Hello Guys,
I am trying to relock the bootloader of MiA1 but if I type command- "fastboot oem unlock" then my mobile cause stuck on bootloop. The same thing also happens with AIO Tool.
So please help me if anyone knows how to relock bootloader again? And also let me know whether unlocking bootloader affect warranty or not?
I know one method to lock bootloader that is, you can install stock ROM by mi flash tool but I need to install magisk and that require to unlock bootloader and if I unlocked once then unable to relock again.
The command in fastboot is fastboot oem lock
Have you done some modifications to the stock boot.img file, such as using magisk or something else?
goofball2k said:
The command in fastboot is fastboot oem lock
Have you done some modifications to the stock boot.img file, such as using magisk or something else?
Click to expand...
Click to collapse
yes
Dipesh17 said:
yes
Click to expand...
Click to collapse
Simply use MIflashtool bro. Flash a nougat fastboot rom via MIFlashtool. Choose option to lock and all
Rajeev said:
Simply use MIflashtool bro. Flash a nougat fastboot rom via MIFlashtool. Choose option to lock and all
Click to expand...
Click to collapse
Bro I need to install Magisk and Magisk need twrp and twrp need to unlock bootloader.
Now once I unlocked bootloader then I am unable to relock bootloader.
I tried miflashtool and fastboot oem lock command but none of them works for me.
What's wrong here I didn't understand, help me please
Dipesh17 said:
Bro I need to install Magisk and Magisk need twrp and twrp need to unlock bootloader.
Now once I unlocked bootloader then I am unable to relock bootloader.
I tried miflashtool and fastboot oem lock command but none of them works for me.
What's wrong here I didn't understand, help me please
Click to expand...
Click to collapse
U did something wrong bro. MI Flashtool can lock bootloader easily with a full firmware flash
Dipesh17 said:
Bro I need to install Magisk and Magisk need twrp and twrp need to unlock bootloader.
Now once I unlocked bootloader then I am unable to relock bootloader.
I tried miflashtool and fastboot oem lock command but none of them works for me.
What's wrong here I didn't understand, help me please
Click to expand...
Click to collapse
Not sure if I understood correctly, but it seems that you want to have Magisk + TWRP + locked bootloader. That is simply not possible. For locked bootloader you must have stock ROM (no root, in fact absolutely no modification).
Dipesh17 said:
Bro I need to install Magisk and Magisk need twrp and twrp need to unlock bootloader.
Now once I unlocked bootloader then I am unable to relock bootloader.
I tried miflashtool and fastboot oem lock command but none of them works for me.
What's wrong here I didn't understand, help me please
Click to expand...
Click to collapse
Bootloader lock is like a door.
If its open you can put nice things like magisk, root, modification like custom rom and kernel.
Now if you try to relock it it won't lock until and unless you take all the modifications out.
Hope this helps.
If you need technical information just let me know
flash stock boot.img and then probably you will be able to lock bootloader. I have done the same way.
mahla13 said:
flash stock boot.img and then probably you will be able to lock bootloader. I have done the same way.
Click to expand...
Click to collapse
With Nougat i flashed stock image selecting "save user data" and i had bootloader relocked without losing data. Root and twrp were gone. I don't know if it is so with Oreo.
So you need TWRP and Magisk root but want a locked bootloader? That just isn't a possible combination.
To install TWRP, you need unlocked bootloader.
If you need root and TWRP, you need to leave the bootloader unlocked.
You can't have both worlds bro. If you unlock and install Magisk and other stuff, you simply can't relock bootloader. That's why you get bootloop
alkesh95 said:
Bootloader lock is like a door.
If its open you can put nice things like magisk, root, modification like custom rom and kernel.
Now if you try to relock it it won't lock until and unless you take all the modifications out.
Hope this helps.
If you need technical information just let me know
Click to expand...
Click to collapse
Thanks man I'll try it on nougat. Please tell me one more thing, unlocking bootloader cause lose warranty or not?
Dipesh17 said:
Thanks man I'll try it on nougat. Please tell me one more thing, unlocking bootloader cause lose warranty or not?
Click to expand...
Click to collapse
Some people might say yes some might say no.
It depends on manufacturer.
OEMs don't explicitly say that it won't void your warranty.
So its grey area.
I am going to email Xiaomi about this and update this thread when i get reply.
Had various experiences with unlocked bootloader. So better to follow safe path.
Edit: Called xiaomi helpline two times.
1st said it will void warranty
2nd said it won't.
Emailed them.
I chatted with a support representative and they said that unlocking bootloader won't void the warranty
nicolasmart said:
I chatted with a support representative and they said that unlocking bootloader won't void the warranty
Click to expand...
Click to collapse
That's just what he said it to you. I got two responses.
Support representatives aren't authorised to send you sms or mail.
If there's an issue with your device (Unlocked BL) and you took it to service center. They might say out of warranty due to bootloader unlocking and what would be your reply to that?
Support representatives said it won't void warranty.
You can't back it up with anything since you dont have any proof of that conversation.
So unless it is written somewhere by xiaomi. Words are just words.
Is it possible to unlock the bootloader, root, make some minor modifications (activation of camera api, copying fm radio apk to system folder, etc), unroot, and finally relock (flashing stock boot.img before, of course) ?
I want to have it unrooted because of bank payments, banks apps and streaming TV apps, but I would like to have proper camera and fm radio... Is it possible??
erunamor said:
Is it possible to unlock the bootloader, root, make some minor modifications (activation of camera api, copying fm radio apk to system folder, etc), unroot, and finally relock (flashing stock boot.img before, of course) ?
I want to have it unrooted because of bank payments, banks apps and streaming TV apps, but I would like to have proper camera and fm radio... Is it possible??
Click to expand...
Click to collapse
Short answer:no.
Long answer: locked bootloader must have stock system and boot partition. Stock boot image will boot only unmodified system partition. However you can have bank and streaming apps with Magisk - use systemless modifications and magisk hide feature.
Lock bootloader after uninstalling Magisk in Mi A1
Thank you for information about Mi Flash Tool but I wanted to ask if it is possible to relock boot loader in Mi A1 after uninstalling Magisk by fastboot commands ?
I haven't tried locking again ,but I wanted to relock again so...
Why oem unlocking appears grey, now why is that am not able to install magisk
alkesh95 said:
Some people might say yes some might say no.
It depends on manufacturer.
OEMs don't explicitly say that it won't void your warranty.
So its grey area.
I am going to email Xiaomi about this and update this thread when i get reply.
Had various experiences with unlocked bootloader. So better to follow safe path.
Edit: Called xiaomi helpline two times.
1st said it will void warranty
2nd said it won't.
Emailed them.[/QUOTE
How to unlock oem unlock,
It appears grey
I unlocked mi account
And installed pixel camera and later I changed the settings in camera from Nexus 6p to pixel and it got stuck, and I uninstalled the application, now oem unlocking appears grey, how to unlock oem
Below It appears bootloader is unlocked, but oem cant be unlocked
Click to expand...
Click to collapse
Related
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.
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.
Hi all,
I am trying to re-lock my bootloader, but my fastboot commands aren't working. It says "remote error command not found."
I am running stock b19 (7.1.1) unrooted. The only thing modified is the bootloader, which is unlocked.
How do I fix this error. I installed the ADB drivers. I do not know what is causing this error. Any help will be appreciated.
TheWoerbler said:
Hi all,
I am trying to re-lock my bootloader, but my fastboot commands aren't working. It says "remote error command not found."
I am running stock b19 (7.1.1) unrooted. The only thing modified is the bootloader, which is unlocked.
How do I fix this error. I installed the ADB drivers. I do not know what is causing this error. Any help will be appreciated.
Click to expand...
Click to collapse
I think fastboot commands were disabled in b19. There's no harm in keeping it unlocked unless you're wanting to use Android Pay (in which case Magisk can hide the unlocked bootloader), or you're needing to return the phone for warranty reasons.
bluestudy said:
I think fastboot commands were disabled in b19. There's no harm in keeping it unlocked unless you're wanting to use Android Pay (in which case Magisk can hide the unlocked bootloader), or you're needing to return the phone for warranty reasons.
Click to expand...
Click to collapse
So I installed the factory image from ZTE's website, which uninstalled twrp and SuperSU (which I knew it would), but I am still unable to use fastboot commands. What might be causing this problem?
As far as I know you need to rollback and flash DrakenFX's fastboot command zip in order to be able to use fastboot again.
iNaruX said:
As far as I know you need to rollback and flash DrakenFX's fastboot command zip in order to be able to use fastboot again.
Click to expand...
Click to collapse
So I changed some settings in Windows Device Manager, now fastboot is working...kinda. I type "fastboot oem lock" and it hangs up for 5 seconds and gives me the error "FAILED (command write failed (Unknown error))...
I solve one problem, and another pops up... Thoughts?
EDIT: In regards to DrakenFX's fastboot command zip, where would I get that? Is it the full systemstock?
I read this guide for the Axon7 A2017G, but the zips used are for the A2017U.
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
The first couple of steps restore the bootloader and get fastboot commands up and running via EDL mode.
iNaruX said:
I read this guide for the Axon7 A2017G, but the zips used are for the A2017U.
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
The first couple of steps restore the bootloader and get fastboot commands up and running via EDL mode.
Click to expand...
Click to collapse
I am currently running B29 (6.0.1). Will this still work, even though I am on a different version of Android? Or should I update to B19?
Oh...if you are on MM this should work for you.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Just flashable zip in Recovery, no need for EDL.
I'm not an A2017U though...
iNaruX said:
Oh...if you are on MM this should work for you.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Just flashable zip in Recovery, no need for EDL.
I'm not an A2017U though...
Click to expand...
Click to collapse
Just for clarification: I am trying to LOCK my bootloader, not UNLOCK. Sorry if I've been unclear. I need to RE-LOCK my bootloader...everything else is stock (recovery, no SuperSU, etc.)
P.S. Thank you for your help, I really appreciate you taking the time.\
EDIT: AHHHHHHHHHHHHH I GOT IT!!!!! Thank you so so much!!! I really appreciate your help, you have no idea!! I followed the last guide you sent me and replaced "unlock" with "lock." You're the best, man...or woman!
TheWoerbler said:
Just for clarification: I am trying to LOCK my bootloader, not UNLOCK. Sorry if I've been unclear. I need to RE-LOCK my bootloader...everything else is stock (recovery, no SuperSU, etc.)
P.S. Thank you for your help, I really appreciate you taking the time.\
EDIT: AHHHHHHHHHHHHH I GOT IT!!!!! Thank you so so much!!! I really appreciate your help, you have no idea!! I followed the last guide you sent me and replaced "unlock" with "lock." You're the best, man...or woman!
Click to expand...
Click to collapse
Haha cheers, I think you got it, I sent that guide just to enable fastboot commands, glad it worked :good:
I need to re-lock the bootloader on my A2017U. I put in a warranty repair claim with ZTE for a dead SIM2 slot. They said if I could relock it to stock, they would not charge the $79.99 out-of-warranty fee.
My only concern with the guides above is that I'm on the RR Nougat ROM. Will any of the links above work for me?
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.
TheBoozer said:
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.
Click to expand...
Click to collapse
This guide should do the trick: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
soren25 said:
This guide should do the trick: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Click to expand...
Click to collapse
Thank you very much for your help, I am now back to stock B15. The only thing left for me is to relock the 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 ?
I don't want to unlock the bootloader again and i don't like this update because it doesn't have google discover.. what can i do?
You can just stay on current version.
Or just install via fastboot and fastboot ROM
yaro666 said:
You can just stay on current version.
Or just install via fastboot and fastboot ROM
Click to expand...
Click to collapse
Without unlocking the bootloader? How?
Ok, so you stated that bootloader is locked, I thought you are considering locking it again.
In that case you have no option, but unlocking bootloader to flash different miui ROM
yaro666 said:
Ok, so you stated that bootloader is locked, I thought you are considering locking it again.
In that case you have no option, but unlocking bootloader to flash different miui ROM
Click to expand...
Click to collapse
I did exactly that. Thank you.