Database Users

OEM Unlocked

After unlocking the bootloader a month ago or so and installing tpxmm , I noticed oem unlock under developer options was disabled.
Well I had to enable oem unlock to disable device protection to reinstall tpxmm.
Should this be set to disabled now after install?
Sent from my XT1575 using Tapatalk

Doesn't matter. That setting only affects whether you can use the "fastboot oem unlock" command. Since your bootloader is currently unlocked, that setting will have no affect.

divinemyth99 said:
Doesn't matter. That setting only affects whether you can use the "fastboot oem unlock" command. Since your bootloader is currently unlocked, that setting will have no affect.
Click to expand...
Click to collapse
Old thread, but still relevant.
Are we sure about this? If "OEM unlocking" is disabled, does Moto's bootloader not block flashing certain images? I have read about other devices not allowing modification with this setting disabled, including flashing back to stock. The solution was restoring a full backup of stock in TWRP, then booting stock and enabling OEM unlocking.
Can anybody confirm if this is the case with the MXPE?

quakeaz said:
Can anybody confirm if this is the case with the MXPE?
Click to expand...
Click to collapse
That's the phone I have.
In Android OS, Developer Settings -> Allow OEM Unlocking is Off, but boot loader was previously unlocked and I have TWRP 3.0.0 installed. Rebooting to bootloader shows
Code:
Device is UNLOCKED. Status code: 3
Software status: Modified
I was able to upgrade to TWRP 3.0.2 using fastboot despite the Developer Settings- > Allow OEM Unlocking setting.
Re-locking the bootloader and restoring to stock as a bit of a process for another thread and if your bootloader shows "Device is LOCKED" then you will need to change the setting in Android before fastboot oem unlock will work. I've never had to change the setting since then, though, and every factory reset in android set it back to Off.

divinemyth99 said:
That's the phone I have.
In Android OS, Developer Settings -> Allow OEM Unlocking is Off, but boot loader was previously unlocked and I have TWRP 3.0.0 installed. Rebooting to bootloader shows
I was able to upgrade to TWRP 3.0.2 using fastboot despite the Developer Settings- > Allow OEM Unlocking setting.
Re-locking the bootloader and restoring to stock as a bit of a process for another thread and if your bootloader shows "Device is LOCKED" then you will need to change the setting in Android before fastboot oem unlock will work. I've never had to change the setting since then, though, and every factory reset in android set it back to Off.
Click to expand...
Click to collapse
Thank you for the info. Have you tried flashing stock recovery with the setting off? If so, no issues?

quakeaz said:
Thank you for the info. Have you tried flashing stock recovery with the setting off? If so, no issues?
Click to expand...
Click to collapse
Not in a log time, so I just tried just now and did the following.
Installed factory recovery
booted into factory recovery
wiped cache (I couldn't remember how to get the menu in the factory recovery, so that took a while =D)
booted into android
rebooted back to boot loader
flashed twrp
booted into recovery to verify twrp installed and is functional
Everything seems to be working.

divinemyth99 said:
Not in a log time, so I just tried just now and did the following.
Installed factory recovery
booted into factory recovery
wiped cache (I couldn't remember how to get the menu in the factory recovery, so that took a while =D)
booted into android
rebooted back to boot loader
flashed twrp
booted into recovery to verify twrp installed and is functional
Everything seems to be working.
Click to expand...
Click to collapse
You flashed stock recovery with the OEM unlocking option turned off, correct? That's what I was reading on a Hauwei device was the problem. With the setting turned off in stock, it wouldn't let him flash stock recovery image. He had to restore via twrp backup.

quakeaz said:
You flashed stock recovery with the OEM unlocking option turned off, correct? .
Click to expand...
Click to collapse
Yes, I left the OEM unlocking option in Developer Settings turned off through the whole process. I haven't turned that setting on since I originally unlocked my bootloader back in January.

Hard/soft brick

I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum

jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/

That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.

https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.

wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc

Was finally able to get into recovery, so all is well. Thanks for the help yall

OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?

gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc

My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?

I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.

Relocking the bootloader and returning to stock ROM

Hey guys, I was planning on sending my Axon 7 in to get a new battery since I'm going to be keeping this for a very long time(until its successor maybe) and I was wondering if there is a way to relock the bootloader to do so?
Here's my original plan to do so:
• Repartition to my original GPT from treble
• Wipe everything (format data, clean internal storage)
• put it into EDL mode and flash B19 with MIFlash(only one with fastboot commands)
• Try the procedure by going into developer options, enable OEM unlock, reboot to fastboot mode, type in "fastboot oem lock"
• Profit?

I was just thinking about doing this earlier today for the same reason, and while I am no expert, that was the same thought process I was going by for returning to full stock. Although someone more experienced, such as @Oki, might be able to provide a more confident answer to if this is the best/proper way.

KH_Lionheart said:
I was just thinking about doing this earlier today for the same reason, and while I am no expert, that was the same thought process I was going by for returning to full stock. Although someone more experienced, such as @Oki, might be able to provide a more confident answer to if this is the best/proper way.
Click to expand...
Click to collapse
Glad I wasn't the only one thinking about this process. Its relieving. I might just shoot him a PM and ask for his input on the matter.

troy5890 said:
Glad I wasn't the only one thinking about this process. Its relieving. I might just shoot him a PM and ask for his input on the matter.
Click to expand...
Click to collapse
Well, I prefer to answer questions in the forum instead of PM, this way the community could benefit from the outcome of the thread. Just mention me by typing @Oki and I will be notified about someone mentioning me.
---------- Post added at 12:25 ---------- Previous post was at 12:23 ----------
troy5890 said:
Hey guys, I was planning on sending my Axon 7 in to get a new battery since I'm going to be keeping this for a very long time(until its successor maybe) and I was wondering if there is a way to relock the bootloader to do so?
Here's my original plan to do so:
1. Repartition to my original GPT from treble
2. Wipe everything (format data, clean internal storage)
3. put it into EDL mode and flash B19 with MIFlash(only one with fastboot commands)
4. Try the procedure by going into developer options, enable OEM unlock, reboot to fastboot mode, type in "fastboot oem lock"
5. Profit?
Click to expand...
Click to collapse
No need for step 1. Flashing a Full EDL package of a stock rom will repartition the GPT to the stock configuration.

Oki said:
Well, I prefer to answer questions in the forum instead of PM, this way the community could benefit from the outcome of the thread.
---------- Post added at 12:25 ---------- Previous post was at 12:23 ----------
No need for step 1. Flashing a Full EDL package of a stock rom will repartition the GPT to the stock configuration.
Click to expand...
Click to collapse
Thank you Oki for the response and you're right. Having it answered here is better for the community as whole. Do the rest of the steps look pretty good to you after flashing the full EDL package?

troy5890 said:
Thank you Oki for the response and you're right. Having it answered here is better for the community as whole. Do the rest of the steps look pretty good to you after flashing the full EDL package?
Click to expand...
Click to collapse
I am planning to complete the unlock / restore to stock guide by including the relock procedure. For doing so I believe the best method is:
1. Full format of data and cache partitions to EXT4
2. Flash The factory ROM. This is Android M ROM
3. Flash patched fastboot for Android M (as if you were going to unlock)
4. Boot the system, enable developers menu, and in that menu enable OEM unlocking and USB debugging options.
5. in your computer prompt type adb reboot bootloader
6. in your computer write fastboot devices to ensure it is in fastboot mode.
7. Type fastboot lock or fastboot oem lock or fastboot oem lock-go. I do not remember the exact command right now but one of them will be recognized.
8. Reflash the same EDL package to have a locked Axon 7 with the original firmware.
9. Enter stock recovery (VolUp+Power) and do a factory reset.

Oki said:
I am planning to complete the unlock / restore to stock guide by including the relock procedure. For doing so I believe the best method is:
1. Full format of data and cache partitions to EXT4
2. Flash The factory ROM. This is Android M ROM
3. Flash patched fastboot for Android M (as if you were going to unlock)
3. Boot the system, enable developers menu, and in that menu enable OEM unlocking and USB debugging options.
4. in your computer prompt type adb reboot bootloader
5. in your computer write fastboot devices to ensure it is in fastboot mode.
6. Type fastboot lock or fastboot oem lock or fastboot oem lock-go. I do not remember the exact command right now but one of them will be recognized.
Click to expand...
Click to collapse
This method looks quite helpful. I did notice that you said flash back to Marshmallow. I remember relocking and unlocking on B19, but I think I might just do that to make sure I don't mess anything up.

troy5890 said:
This method looks quite helpful. I did notice that you said flash back to Marshmallow. I remember relocking and unlocking on B19, but I think I might just do that to make sure I don't mess anything up.
Click to expand...
Click to collapse
You can use N if you want. The problem with N is the removal of edl boot using the key combo. It is very useful in case something fails. Booting edl mode using the button combo helps you recover it easily.

Oki said:
You can use N if you want. The problem with N is the removal of edl boot using the key combo. It is very useful in case something fails. Booting edl mode ising the button combo helps you recover it easily.
Click to expand...
Click to collapse
I recall B19 has the EDL combo still intact when I would use it. I'll see if I can try that out in a few days, but I'll definitely keep that in mind if something goes wrong.

Oki said:
I am planning to complete the unlock / restore to stock guide by including the relock procedure. For doing so I believe the best method is:
1. Full format of data and cache partitions to EXT4
2. Flash The factory ROM. This is Android M ROM
3. Flash patched fastboot for Android M (as if you were going to unlock)
4. Boot the system, enable developers menu, and in that menu enable OEM unlocking and USB debugging options.
5. in your computer prompt type adb reboot bootloader
6. in your computer write fastboot devices to ensure it is in fastboot mode.
7. Type fastboot lock or fastboot oem lock or fastboot oem lock-go. I do not remember the exact command right now but one of them will be recognized.
8. Reflash the same EDL package to have a locked Axon 7 with the original firmware.
9. Enter stock recovery (VolUp+Power) and do a factory reset.
Click to expand...
Click to collapse
I might be having to do this as my phone as of last night will not connect to mobile networks at all suddenly and for seemingly no reason.
Could I do the full wipe, reboot to fastboot from recovery, then do the relock (while I still have easy access to it), then since I'll still have a bootstack with ELD button combo installed, use MiFlash to flash B35 from djkuz's edl tool thread? If not, by following this list should I flash B29 which is the oldest M firmware from his thread had they already removed fastboot with that one?

KH_Lionheart said:
I might be having to do this as my phone as of last night will not connect to mobile networks at all suddenly and for seemingly no reason.
Could I do the full wipe, reboot to fastboot from recovery, then do the relock (while I still have easy access to it), then since I'll still have a bootstack with ELD button combo installed, use MiFlash to flash B35 from djkuz's edl tool thread? If not, by following this list should I flash B29 which is the oldest M firmware from his thread had they already removed fastboot with that one?
Click to expand...
Click to collapse
I ended up relocking the bootloader by doing the following
1. Repartition the vendor if you are running treble and backup your internal storage
2. Wipe the device in Twrp by Data, dalvik cache, System ,etc
3. Reboot into EDL mode, open MiFlash and flash the B19 EDL zip(don't flash TWRP afterwards for it to have the stock recovery)
4. Unplug, wait 2-3 seconds, reboot by holding the power button and get past the setup from Mifavor.
5. Go into developers mode and enable USB debugging(your phone should still be unlocked, so the option to enable oem unlocking should be greyed out).
6. Reboot into the bootloader and plug it in to the computer
7. Pull up your command prompt from your computer, make sure you have ADB and fastboot drivers installed, and make sure you put in "fastboot devices"
8. If it shows up, then type "fastboot oem lock" and your phone will go black and reboot to recovery for it to wipe your internal storage. After that is completed, you should be back to a locked bootloader on B19 firmware. If you want to upgrade to B35, you can perform the software upgrade in the settings to get there.

Got stuck on Android one logo

Hello sir,
Recently my internal storage got almost full ,it flashed repeated warnings that "some system functions may go wrong,please freeup some space".I just did not paid much attention to it and proceeded to download a file when my internal storage level was less than 100 mb and then suddenly my phone got switched off.when I tried to switch it on it got stuck in the middle with Android one logo .please help me to solve this problem as I don't to lose my data.

Hi Rakesh,
Is you issue get resolved?
I have also got warnings of internal storage full in my MI-A1 and after that my phone got switched off. I also tried to switched on and it got stuck at android one logo.
Please help me out if your issue get resolved?

Try booting in TWRP and using the file manager to delete some user data to make space.

barrack1 said:
Try booting in TWRP and using the file manager to delete some user data to make space.
Click to expand...
Click to collapse
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.

saurabhsh23 said:
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.
Click to expand...
Click to collapse
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.

manpildo said:
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.
Click to expand...
Click to collapse
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?

saurabhsh23 said:
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?
Click to expand...
Click to collapse
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.

manpildo said:
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.
Click to expand...
Click to collapse
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.

saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
Click to expand...
Click to collapse
Yes, unlocking bootloader wipes data.

saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.
Click to expand...
Click to collapse
No, if you wipe your phone through recovery you won't need to flash anything. It just deletes all your stuff without touching the system.

Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713

Any update here please?
vaibhav08 said:
Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713
Click to expand...
Click to collapse

Guys pls help me i got stuck on boot logo i want to flash stock rom pls help me

I'm in the same boat. Unable to access developer options as phone won't boot and its stuck at the android one logo.
Fastboot oem unlock gives error Flashing Unlock is not allowed.
Is there anyway around this?

I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.

Face_11 said:
I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.
Click to expand...
Click to collapse
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking

jack_21 said:
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking
Click to expand...
Click to collapse
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s

Face_11 said:
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
Click to expand...
Click to collapse
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery

jack_21 said:
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery
Click to expand...
Click to collapse
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.

Face_11 said:
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.
Click to expand...
Click to collapse
If you see a triangle, you are in recovery mode
You need to press a button combination to see options, Search on Google for that

[HELP] Bootloader relocked, won't unlock, boots directly to fastboot

Help, I'm in a real state. I was happy on US997 Fulmics, with root, etc, but decided to try Stock Oreo. I upgraded, didn't like the substratum issues, and restored my Nandroid backup. As others discovered, this means the fingerprint doesn't work. I googled, and saw "just factory reset", so I went into my settings and selected "Factory Reset". This took me to TWRP, because of course, but then when I rebooted system, it took me back to TWRP. After some hours of trying to fix this by flashing various ROMs, I came across the advice to try this command in TWRP Terminal:
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
Click to expand...
Click to collapse
(except I had to add "/soc" after /platform)
Now my bootloader is locked, and its bootloop directly to Fastboot, and type in "fastboot flash unlock unlock.bin" but it returns "FAILED (remote: oem unlock is not allowed)". I can get into Download mode, and I've tried loading two stock Nougat KDZ files, and it still just brings me to Fastboot, right around 80% in the upload process. I can hold volume and get to the recovery prompt, choose erase, I see a brief window of "Erasing" and then its back to Fastboot.
Please, any help is super appreciated!

I'm back trying to fix this after very little sleep, and am at least trying to ask the right questions.
Are there other Fastboot commands I could be using?
Could I have wiped the boot partition, and that's why it goes to Fastboot when it starts?
Is there a way to restore the boot partition using LGUP?
Are there other ways to unlock the bootloader now?
I see in red letters "Please check "Enable OEM unlock in Developer options" in Fastboot, but I can't get into Android to do that, is there anyway to do enable that from within Fastboot or Download?
Is there a KDZ I could flash that has it enabled?
I'm so upset about breaking this through my own idiocy, and really don't want to have to purchase a new phone right now, so I'm definitely willing to throw a few bucks to anyone who knows a sequence of steps to get me working again!

You need to put it in qc9008 mode and do with jtag box

If u can boot into fastboot mode then all hope is not lost. Try using the official LG bridge app for pc, idk if itll work with an unlocked bootloader device but its worth a try, in the app under the update phone tab there is an option "update error recovery" just connect your phone in fastboot mode, select that option, and follow the app instructions. It should atleast take u back to stock. where u can probably start fresh.