[Help] Bootloop after updating, usb debugging not enabled. - Xiaomi Mi A1 Questions & Answers

Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.

Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.

Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com

Related

How do I unbrick a bricked P9Lite with a locked bootloader and without USB debugging?

Greetings all,
I recently got a P9 Lite but I bricked it trying to install a newer firmware on it (tried to go from 6.0 to 7.0). I've read various unbricking guides over the past two days but to no avail. I'd like to know what my options are at this point and if it is possible to unbrick it and bring it back to a usable state even if on a different rom.
How I got here:
The firmware that came with my phone was L23C605B120. I tried to update it to L23C605B362 and downloaded 2 zips (update.zip and update_data_full_VNS-L23_hw_la.zip). I unzipped update.zip into the dload folder of my sdcard and updated it via the dialer. The update installed and my device rebooted but now to this bootloop state.
What I can do:
If booting up normally, I end up in Huawei's erecovery. I can also boot to recovery mode where I can either "Wipe data/factory reset" or "Wipe cache partition". I can boot to fastboot & rescue mode but it says my phone and frp are locked. When pushing all three buttons I can boot to where the phone will attempt to update with the dload folder in the sd card again.
Stuff I have tried:
In erecovery when I select "download latest version and recovery", I can connect to my wifi but it always fails at "Getting package info failed". In recovery mode the factory reset fails and I don't think wiping the cache partition did anything meaningful. In fastboot & rescue mode it tells me to open HiSuite where there is a recover option but clicking it says "Your device is not supported for system recovery". I can see my device using fastboot on my computer but it seems almost useless here since its useful commands fail with "command not allowed" probably because my bootloader is locked. On my computer I installed the USB drivers adb needs and rebooted but adb cannot see my device presumably because I hadn't enabled USB debugging prior to getting bricked. At this point I'm downloading different roms to my sdcard and trying to flash with the 3 buttons method but pretty much all of them fail at 5% or 7% including the rom with the same version that my phone came with. The only one that doesn't fail at 5% or 7% is the rom I tried to flash that bricked my phone which fails at 99%.
So I cannot flash TWRP because my bootloader is locked, I cannot unlock my bootloader because adb cannot see my device, adb cannot see my device because I probably never enabled USB debugging and I cannot enable USB debugging because I cannot boot to the OS. At this point my only option seems to be trying to flash a working rom with my sdcard but I have yet to find one that works.
Where should I go from here and what are my options at this point? Is there a specific rom I should be looking for? Is there some intermediate downgrade rom I have to flash or is there a way to undo the update I just did? Is there a way to somehow enable USB debugging or to unlock my bootloader without it (perhaps via an exploit)?
Any help would be much appreciated!
TL;DR: title

System doesnt load after root attempt

Hi guys.
I had OP5 with stock everything unpdated on the oreo Android, then i decided to try to become root.
I have unlocked bootloader, installed twrp, formatted data and tried to install SuperSU.
After that i am stuck in current situation - after boot the phone warns me that the software could not have been "checked" and waits for 5 secs for loading to system. After that i just get a black screen with blue LED light diode active.
I CAN access fastboot and recovery.
What i have tried:
flashed twrp back to stock recovery - there i am not able to click "install from internal storage", however i tried to use adb sideload and tried to install OnePlus 5 OxygenOS 5.0.4, dowloaded from official site.
this gave me an error - total Xfer 1% - installation failed.
So i tried to install the same rom from twrp, there i got "this package is only for Oneplus 5 device" , which cheered me up a bit., but thats it.
I have no idea what can i do next, do you guys have any?
gygabyte123 said:
Hi guys.
I had OP5 with stock everything unpdated on the oreo Android, then i decided to try to become root.
I have unlocked bootloader, installed twrp, formatted data and tried to install SuperSU.
After that i am stuck in current situation - after boot the phone warns me that the software could not have been "checked" and waits for 5 secs for loading to system. After that i just get a black screen with blue LED light diode active.
I CAN access fastboot and recovery.
What i have tried:
flashed twrp back to stock recovery - there i am not able to click "install from internal storage", however i tried to use adb sideload and tried to install OnePlus 5 OxygenOS 5.0.4, dowloaded from official site.
this gave me an error - total Xfer 1% - installation failed.
So i tried to install the same rom from twrp, there i got "this package is only for Oneplus 5 device" , which cheered me up a bit., but thats it.
I have no idea what can i do next, do you guys have any?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Visit here and unbrick your device.

Phone bricked after installing LinageOS 17.1 - System UI Crashing

Hi,
Today I tried to install LinageOS 17.1 on my Huawei P10 lite (at start, still completely Stock Rom).
Unlocked bootloader following procedure in https://forum.xda-developers.com/p10-lite/how-to/p10-lite-bootloader-unlock-june-2020-t4113315, worked great.
Installed TWRP following https://forum.xda-developers.com/p10-lite/development/recovery-twrp-huawei-p10-lite-t3953890 ; also here, no problem.
Then I tried installing LinageOS following this thread https://forum.xda-developers.com/p10-lite/development/rom-lineageos-17-1-huawei-p10-lite-t4064115 . Here I ended up with the Linage OS System UI that constantly crashes, restarts, crashes again etc.
This problem is mentioned in the same thread but none of the solutions seems to work for me.
I tried to downgrade the TWRP to the older 3.3.1 and then redo the entire installation procedure => No success
Then I tried wiping and formatting all the caches/data that was mentioned during the thread + re-executing the entire installation procedure => Still no success.
Can anyone help me?
What could also be relevant:
In TWRP I cannot seem to copy data to the device, whenever I try to do that via the File Manager (I am using Linux Mint 20) I can see the device and its internal storage but transferring data is horribly slow (it would take 5 hours 45 minutes to transfer a 3 MB file) or just fail. I also tried this in a (virtualized) Windows 10 installation with the same results.
When earlier today (before having installed LinageOS) I tried to transfer files, it worked very well. Also, I tried it with multiple USB cables just in case it might have been a faulty cable.
Pushing a file via adb push doesn't work as the device shows up as "unauthorized". The installation of the patches (magisk, los_patches_warsaw, opengapps etc.) I did using ADB Sideload which seemed to work nicely as well - really making me thing that the USB transfer issue is not hardware-related...
Furthermore, I know this is a noob question but anyway: the procedure says "flash los_patches_warsaw.zip". How exactly should this be done? Copying the file to the internal storage from a PC (which I cannot do, see above) and installing it via TWRP Install? Flash via Fastboot (to what destination)?
Tx in advance!
I've had this issue as well, what I did was disabled dm-verity and forceencrypt using https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 after flashing system in fastboot and then I flashed los_patches_warsaw.zip from SD Card (MTP is broken in older twrp, use 3.4.0, also try this at your own risk).
Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?
Bart80TR said:
Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?
Click to expand...
Click to collapse
I think it's only possible by dirty flashing it, also a little correction for my last post, I meant internal storage not micro SD card.
it's a shame the original LOS 17.1 thread is closed.
My experience with WAS-AL00 (china version) on macOS:
After I flash LOS 17.1 ROM, "fastboot reboot recovery" doesn't reboot the device into recovery. Then I unplug the phone, and reboot into system, I came across system UI crashing constantly. After managing to get through to the main screen. Plug the phone, "adb reboot recovery", then flash los_patches_warsaw from microsd card (you need to copy the file to a microsd card and insert it into the phone). Then reboot system, this time the screen is black. only long press power button show three options "power off", "restart", and another one i don't remember. @KinteLiX 's method didn't work for me.
Then I tried stock recovery with openKirin (worked), Twrp 3.4.0.0 with openKirin (also worked, even though they state that only stock recovery works with their ROMs).
Last I tried twrp 3.4.0.0 with AOSP 10 from @DarkJoker360. It works.
Note: after flash the ROM, power off the phone, and long press three buttons volume up, volume down and power at the same time, and you will boot into twrp. If it shows update fail, then reboot and try to get into erecovery and wipe data/factory reset and then power off, long press three buttons simultaneously and you will be able to boot into twrp, if not, wipe data/factory reset again in erecovery (I accidentally found out about this. before this I was unable to boot into twrp after flashing any ROM, "fastboot reboot recovery" doesn't work). then do as the thread shows.
update: making a call doesn't work with AOSP 10 on my device.
The system crashing should come from the integratet AOD overlay....there should be a solution to solve that issue but i didnt rember the correct way how to. Just search in the p10 lite forum here on XDA.

TWRP problem

I was in twrp and backuped my device than i saw twrp app install for checking updates and thought ok swipe to install then my Onples 6T is now in an Bootloop in Twrp every 2 seconds the twrp logo pops up and instantly turns of
if i type fastboot devices in cmd nothing showed up
what should i do now?
Are you on stock or custom ROM? In TWRP you should stilll have connection to a PC to grab things off your phone. At this point I believe a factory reset will fix it? However you could try switching slots in TWRP and see if it will boot.
In the future definitely never install the TWRP app.

Bootloop after updating magisk

I have an asus zenfone 2 laser running android lollipop. I have turned the USB debugging on for my laptop.
I used to install kingoroot for rooting my phone, and it works fine.
For no particular reasons, i switched over to magisk and uninstalled the kingoroot apps.
The installation was successful, then the app asked me to update it via the app. I updated it, and then it asked me to do reboot.
I rebooted............and i got stuck in bootloop.
I got into the recovery mode and factory resetted the phone but i am still stuck with the bootloop.
I tried to install magisk uninstaller zip from sd card but the installation was unsuccessful
I tried to install the latest firmware from ASUS's official website from SD card and was unsuccessful
I tried to flash the latest TWRP to my device via flashboot. Since many tutorials out there have a TWRP Recovery mode to fix the problem which i don't hace at the time. i used "fastboot flash recovery TWRP.img" command and it said finish.
But it lead me to a new problem. I cannot use "power button+vol.down" key combination to access stock recovery mode. And the TWRP recovery mode doesn't come out as well.
One thing that i can use is the "power button+vol.up" key to access fastboot mode..
I stopped messing around with my devices for now so that i don't make the problems worse. I hope someone can help me out with this problem
BIG THANKS

Categories

Resources