Hi all! Want to ask if someone was able to boot A12b2 with DSU loader?
I am able to download it and reboot to it, but it boots me to "clear" android 11, same build version like is my actual Android...
What I am doing wrong ? My phone is bootloader unlocked and rooted... Btw, while selecting DSU image it says it is SPB2.2.....
Thanks
Related
Yesterday I thought I bricked my phone. I too also got stuck on the secure boot error 1003 boot loop. It happened when I tried to relock my bootloader with fastboot oem lock. Can anyone explain why that happened and if, after you obtain root, if it's possible to go back and relock the bootloader. I was attempting to get android pay working again, plus it flashes that message about having an unlocked bootloader. Is it possible to re-lock the bootloader after you have root, and if so, what did I do wrong. I finally restored back to factory using the lg bridge tool and download mode, which was a [email protected]#% to get into with a bootlooping phone.
Thanks in advance.
happimeal said:
Yesterday I thought I bricked my phone. I too also got stuck on the secure boot error 1003 boot loop. It happened when I tried to relock my bootloader with fastboot oem lock. Can anyone explain why that happened and if, after you obtain root, if it's possible to go back and relock the bootloader. I was attempting to get android pay working again, plus it flashes that message about having an unlocked bootloader. Is it possible to re-lock the bootloader after you have root, and if so, what did I do wrong. I finally restored back to factory using the lg bridge tool and download mode, which was a [email protected]#% to get into with a bootlooping phone.
Thanks in advance.
Click to expand...
Click to collapse
To answer your question, when you root the g4 on marshmallow using chainfire's systemless root, It on the fly flashes a different boot image, thus if you relock the bootloader after rooting the device on the 6.0 marshmallow firmware it will end up with the security error because the boot image has been "modified" and a modified image won't be allowed to boot if the bootloader is locked so the answer is unfortunately no you can't have a locked bootloader and have root at the same time, If you want to relock the bootloader on the 6.0 firmware to get rid of the boot image showing "unlocked bootloader" you should flash the KDZ for the 6.0 firmware in this case H81120i firmware and then go into developer settings and uncheck enable oem unlocking and also make sure you boot into fastboot mode, you can do this via the adb shell. another option to not have the "unlocked bootloader" show every boot would be to go back to the 5.1 firmware which did not have this. I hope this helps.
Thank you for a great explanation.
If you ask the people at xposed modules they may be able to do something maybe....
5.1 still displays bootloader unlocked message.
cschmid44 said:
To answer your question, when you root the g4 on marshmallow using chainfire's systemless root, It on the fly flashes a different boot image, thus if you relock the bootloader after rooting the device on the 6.0 marshmallow firmware it will end up with the security error because the boot image has been "modified" and a modified image won't be allowed to boot if the bootloader is locked so the answer is unfortunately no you can't have a locked bootloader and have root at the same time, If you want to relock the bootloader on the 6.0 firmware to get rid of the boot image showing "unlocked bootloader" you should flash the KDZ for the 6.0 firmware in this case H81120i firmware and then go into developer settings and uncheck enable oem unlocking and also make sure you boot into fastboot mode, you can do this via the adb shell. another option to not have the "unlocked bootloader" show every boot would be to go back to the 5.1 firmware which did not have this. I hope this helps.
Click to expand...
Click to collapse
I have installed h815 KDZ files using LGUP. When i reboot it still displays Bootloader unlocked message. I can not use bootloader unlock/lock guide as I have bootloader unlocked.
Any other means to get rid of the message.
bump for way to relock h815
I decided too unlock bootloader to get android pie because I was tired if waiting for it and since we get update every 5 months I thought might as well get root at the same time.
But now I cannot boot into twrp holding volume up , it insteads bring me to stock recovery.
I can boot twrp with adb using a computer but its encrypted and i have screen unlock off .
And I cant lock bootloader and unlock it on pie to start from scratch I think because oem unlock is locked in developper options
you need to use modded TWRP for EMUI 9, but it wont be able to decrypt as well,
TWRP are pretty much unusable on PIE,
but you doesnt need TWRP at all to root, just flashed the patched recovery ramdisk through fastboot. Next magisk update can be installed directly from the manager
and for the heads up, root on pie using recovery partition, so you can't have TWRP and root together
if you root, mean no TWRP
if you want TWRP, mean no root
as for oem unlock greyed out, its restored to normal on 9.0.0.168, i think you are on lower version of pie.
Hello, owner of a Xiaomi Mi A2 running the June update.
I recently unlocked the bootloader through "fastboot oem unlock" command. Ever since I am stuck in bootloop. I have managed to boot in TWRP using a specific img for the device, but I am not sure how to proceed. Is it possible to install a stock rom and start all over?
thymiosK said:
Hello, owner of a Xiaomi Mi A2 running the June update.
I recently unlocked the bootloader through "fastboot oem unlock" command. Ever since I am stuck in bootloop. I have managed to boot in TWRP using a specific img for the device, but I am not sure how to proceed. Is it possible to install a stock rom and start all over?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/help/strange-issue-mi-a2-t3945125
thymiosK said:
Hello, owner of a Xiaomi Mi A2 running the June update.
I recently unlocked the bootloader through "fastboot oem unlock" command. Ever since I am stuck in bootloop. I have managed to boot in TWRP using a specific img for the device, but I am not sure how to proceed. Is it possible to install a stock rom and start all over?
Click to expand...
Click to collapse
You should read this flashing guide first and then proceed further...
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
There is a link of how to unlock bootloader properly in the same thread so read that too... I think you missed the flashing unlock critical part during unlock bootloader process so if you are still in stock then do it first so that you can able to flash stock later or else it would be difficult for you to flash back stock..
Since I was able to get int fastboot I tried countless times locking and unlocking bootloader. After numerous retries I have also managed to install a stock rom I found online using the TWRP. And it did work. I got my phone back to working. Thank you anway.
After wiping the system partition when trying to make something work, I got stuck in fastboot mode with no os. I followed the advice given here but I think I flashed an incompatible os, and now my phone is locked, and when I try to boot it it tries to boot into miui then goes into recovery and says "This MIUI version can't be installed on this device." Nither miflash nor miunlock can do anything. Any ideas on how I can fix it?
bomjoe said:
After wiping the system partition when trying to make something work, I got stuck in fastboot mode with no os. I followed the advice given here but I think I flashed an incompatible os, and now my phone is locked, and when I try to boot it it tries to boot into miui then goes into recovery and says "This MIUI version can't be installed on this device." Nither miflash nor miunlock can do anything. Any ideas on how I can fix it?
Click to expand...
Click to collapse
Have you flashed latest Fastboot Rom with latest miflash tool?
Abdul M Ahmed said:
Have you flashed latest Fastboot Rom with latest miflash tool?
Click to expand...
Click to collapse
The Phone got locked when I flsahed the wrong rom with the miflash tool, and forgot to change it to clean all. Now I cannot flash a rom as the bootloader is locked.
bomjoe said:
The Phone got locked when I flsahed the wrong rom with the miflash tool, and forgot to change it to clean all. Now I cannot flash a rom as the bootloader is locked.
Click to expand...
Click to collapse
It doesn't matter whether the bootloader is locked or not with miflash. Give it a go with the correct rom.
As long as it's an official rom.
Turbine1991 said:
It doesn't matter whether the bootloader is locked or not with miflash. Give it a go with the correct rom.
As long as it's an official rom.
Click to expand...
Click to collapse
I tried, it says: error:FAILED (remote: Erase is not allowed in locked state) for clean all and clean all and lock.
For save user data it says: error:"Erase boot error"
Was there a way to flash without erasing, I cannot remember. But it sounds like you need to flash a rom version comparable to the current one (without wiping), boot, unlock bootloader.
I was locking my bootloader to try to reroot and pass safetynet. So, I factory reset it, set it up, and then went into the bootloader and typed "fastboot flashing lock". I selected yes to confirm the locking of my bootloader and then my phone rebooted. But now my phone says "Can't find valid operating system" and I can't boot into Android. i was able to unlock the bootloader again but now i don't have magisk installed and I can't even boot into Android to install anything. Is there anything i can do to fix this?
Yes, if you're bootloader is unlocked then you can fastboot flash (or use Chrome web based Android Flash Tool) factory images from https://developers.google.com/android/images
If you want to root extract the boot.img from the zip and patch with Magisk, then fastboot flash boot magisk_patched.img after you boot the phone once on stock unrooted kernel.
Thank you. I did it with the flash tool. Then later, it happened again and I realized I could use the boot.img. I'm glad these Google pixels are noob friendly.
Never lock your bootloader unless you know for a fact that you are on bone stock OEM firmware.