Mi A2 Lite reboot loop - Xiaomi Mi A2 Lite Questions & Answers

I was trying to flash vanilla AOSP GSI and everything was going as expected.
After that, I flashed "disable force encryption" and the fingerprint gestures files among with magisk and pico gapps and the phone started rebooting after a single freeze of 2 or 3 seconds right after the initial boot.
Actually I made several tries with different combinations trying to figure out what was causing that behaviour and I noticed that it used to happen patching "fstab.qcom" file in "/vendor/etc" path as stated in this guide, always keeping a backup of the original "fstab.qcom".
At some point my device started rebooting even after restoring the old "fstab.qcom" so I flashed the stock rom via fastboot but it didn't solve the problem, then I also tried to flash in edl mode (enabled with "fastboot oem edl") but no way, the phone keeps rebooting without letting me finish even the initial setup.
I can access fastboot, edl and recovery. I can also flash TWRP but I can't turn off the phone.
I don't know what else to do, please help me
Sorry for me being a big noob and for my unclear english.

Related

Realme X2 freezes and restarting every 15secs after updating to RMX1993EX_11.C.14

i updated my phone yesterday since there's a new update available and after an hour it restarted and keeps on restarting after 15secs. Even i do something or not, or even in safe mode.
i tried extracting all my files using twrp but upon checking that i still have fastboot bootloader (unlocked) but my twrp is gone and its back to colorOS recovery. i tried online update to keep my data but still the problem continues. i tried flashing twrp using adb but its not detecting my phone since it can only open for 15 secs before it restarts again. but i managed to see that OEM unlocking and usb debugging is turned on im running out of options here. i cant just reflash a new rom/ota without getting my files. any chance anyone can help. Thanks XDA!
jvincent2713 said:
i updated my phone yesterday since there's a new update available and after an hour it restarted and keeps on restarting after 15secs. Even i do something or not, or even in safe mode.
i tried extracting all my files using twrp but upon checking that i still have fastboot bootloader (unlocked) but my twrp is gone and its back to colorOS recovery. i tried online update to keep my data but still the problem continues. i tried flashing twrp using adb but its not detecting my phone since it can only open for 15 secs before it restarts again. but i managed to see that OEM unlocking and usb debugging is turned on im running out of options here. i cant just reflash a new rom/ota without getting my files. any chance anyone can help. Thanks XDA!
Click to expand...
Click to collapse
UPDATE:
i gave up all my files just make my phone works
i tried changing stock OS to custom ROM (lineage,Evolution) still getting the same issue that its still restarting after 15 secs or just after wifi connection in the setup.
also tried format data, formats cache, dalvic, system and data in twrp then back to fastboot.
since ""--disable verity" is unrecognizable what i did is just flash is "fastboot flash vbmeta vbmeta.img" then flash twrp then flash the rom again but still im getting the same outcome.
tried going back to stock (got the ozip file from realme)but getting zip compatibility error and after i deleted compatibility.zip then getting error 7 so tried deleting asserts from updater-script but still getting no where so i tried using orange fox recovery. it does install but still the issue persist.
any other ideas for me to try guys?
TIA
You must be flashing wrong file.
jvincent2713 said:
UPDATE:
i gave up all my files just make my phone works
i tried changing stock OS to custom ROM (lineage,Evolution) still getting the same issue that its still restarting after 15 secs or just after wifi connection in the setup.
also tried format data, formats cache, dalvic, system and data in twrp then back to fastboot.
since ""--disable verity" is unrecognizable what i did is just flash is "fastboot flash vbmeta vbmeta.img" then flash twrp then flash the rom again but still im getting the same outcome.
tried going back to stock (got the ozip file from realme)but getting zip compatibility error and after i deleted compatibility.zip then getting error 7 so tried deleting asserts from updater-script but still getting no where so i tried using orange fox recovery. it does install but still the issue persist.
any other ideas for me to try guys?
TIA
Click to expand...
Click to collapse
It seems like you're flashing incorrect OS version onto your device. Note there are 3 different versions of realme x2. i.e rmx1991, rmx1992, rmx1993 with each having different versions of their own.
I've seen rmx1992ex here on xda for custom roms but my device came with rmx1992aex version.
So check your's and flash correct file.
maxs8007 said:
It seems like you're flashing incorrect OS version onto your device. Note there are 3 different versions of realme x2. i.e rmx1991, rmx1992, rmx1993 with each having different versions of their own.
I've seen rmx1992ex here on xda for custom roms but my device came with rmx1992aex version.
So check your's and flash correct file.
Click to expand...
Click to collapse
Got the same problem. My X2 is RMX1993.. i think i updated the wrong firmware. My current build number is RMX1993EX_11_C.12 Not sure if it's the same but I've got a feeling that it's not.. found a guide on how to flash the stock rom but the problem is that everytime I use ADB. Reboot to bootloader the phone just restarting. And I think my bootloader is also locked. Any suggestions? Really need your help.

Question OP 9 Pro stuck on infinite loop using LineageOS

Hi all,
I'm coming back to Android after an absence and would like to run Lineage on a new US unlocked 9P. I followed the directions in the Lineage OS website and unfortunately the phone now is stuck in a constant animation of the blue circle moving left over the arc, and there isn't much I think I will be able to do about it until the battery runs out.
Here's what I did as per the directions:
-got and installed adb and fastboot from the Windows zips from Google
-added the install location to the path enviro variable
-installed the Universal ADB driver from Github
-activated USB debugging and OEM unlocking on the phone
-got the phone repeatedly into fastboot mode but then got stuck since 'fastboot devices' didn't show anything
-got bailed out by another thread here that one needs to check for updates with phone connected and Win will download the relevant USB drivers. Thanks!
-unlocked the bootloader
-downloaded and flashed the 18.1-20210803 recovery img
-sideloaded the copy-partitions 20210323 zip and it got stuck at 47% just like the website said
-did the factory reset
-sideloaded the the LOS 2020210803 zip to the phone and rebooted
When I rebooted it just plays the animation I mentioned at the beginning, so it looks like it's stuck in a permaloop.
I should mentioned that after I flashed recovery and booted into the normal Oxygen mode it would take much longer to boot so perhaps there was something already creating the loop.
I am grateful for any assistance.
Thanks,
How long have you left it? First install of Lineage spins for ages
I think I left it for an hour or so. Thanks for the info - I just turned it on and will let it spin for a while and see what happens.
I let it run until the battery died. I fully recharged it and am letting it run again. Same result of blue circle tracing arc to the left.
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
lexcimer said:
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
Click to expand...
Click to collapse
Everytime you flash a new rom you need to wipe data after
Anytime that happens you just go back into recovery and wipe data a few times and it should work after that.
It would've been due to encryption. Each time you flash a new rom you need to wipe userdata which removes your lock and also removes encryption. If you try to install a rom without doing this first, the rom cannot access that partition, because it doesn't yet know the unlock code/pattern, which is why it just gets stuck trying to do so.
Thank you to the 3 posters above, and I appreciate DJ Sub's explanation, makes sense in hindsight and I'll keep it in mind for the future.
PS - I'm glad to be back to the Android modding community, it's refreshing to be able to steer what OS my phone is running
I had the same problem (also a couple of different boot loop problems) when flashing LineageOS.
I did many things, so can't say for sure which one helped me to fix that, but the things I did were:
Restore from boot loop via MSM tool flashing EU image.
Updating that OxygeneOS to the latest using internal updater.
Repeating the LOS installation process several times in different conditions to isolate the source of the problem. I was changing LineageOS package, OpenGapps package, etc.
One of the problems I've found was that latest OpenGapps package (July 28th if I'm correct) was causing the boot loop on first start (very similar to what you're describing):
Phone tries to boot showing the LOS animation.
It goes for several minutes.
Then the phone vibrates, reboots and it continues from the start.
If I'm not mistaken, it was fixed by using the version from July 24th. The latest package also were removed from the OpenGapps page later AFAIR.
Second problem was after the successful boot. The phone was rebooting from the first setup wizard, booting to recovery (or some other partition) and proposing to make a factory reset.
Not sure which of my steps solved this, but I was updating back to the last LOS package watching closely that I'm flashing the same slot on each step and also making sure that slots are properly copied from one to another with the corresponding script.
Even in the most stable setup I was probably having some setup wizard loop problems, so I was skipping account setup steps and doing that manually later.
I'd say that installing LOS on OnePlus 9 Pro was most difficult and problematic installation in my experience and I did that a lot previously: HTC Wildfire S, THL 5000, Zuk Z1, Xiaomi Mi 5s, Xiaomi Mi 9T (Redmi K20) and several other devices.

Phone boot loops when I don't install magisk

I have a weird situation going on with my phone
My phone is Chinese Pack and I had Xiaomi Eu MIUI 12 previously
I tried flashing MIUI 11 Stable China rom on it using TWRP
when I installed the rom, TWRP didn't get deleted and my phone started to bootloop, so I flashed magisk and the bootloop was gone and I could boot my device after flashing magisk.
Now I want to sell my phone and I'm trying to flash everything back to normal, get rid off TWRP and Magisk and lock the bootloader as well using MiFlash
the phone is running on V11.0.5.0.PCACNXM and I'm trying to flash the same rom using MiFlash and lock bootloader, but at first, it says device mismatch
and when I delete the first 2 lines of flash_all_lock.bat which causes this problem, something else happen
check the attached image
when I press the flash button, this screen comes up and nothing changes except the timer that goes up, and when I remove the phone cable, the phone boots normally without any problem, practically, MiFlash doesn't change a thing
any solution that can help me unlock Bootloader, remove Twrp and Magisk?
Already tried different versions of MiFlash and an app called XiaomiADBFastbootTools.jar, nothing again
P.S: while flashing with XiaomiADBFastbootTools.jar, I get the same message but after removing the cable, the error changes to "current device anti-rollback version is greater than this package", which is nonsense because I have the same ROM on phone already.

Weird restarting issue on some A13 roms

Hi,
There has been an issue that riddles me, and I can't understand why it happens.
I've use Evolution X A13 (from here XDA), then try to switch to crdroid 9.3 (also here from xda)
Since I'm not encrypted, the usual steps I take were
1. clear fingerprints + pattern
2. reboot twrp
3. wipe from twrp
4. flash the rom
5. flash the DFE
6. reboot system
I rarely root. Even if I root, I always do it after first or many reboots after.
Now the weird thing happened.
crdroid 9.3 + nikgapps passed the boot until the setup wizard appeared, but then it's automatically rebooted by itself. Not hard reboot, it's similar like soft reboot (it's showing crdroid logo, back to setup wizard). Then it keeps soft rebooting (showing setup wizard for a moment then goes soft reboot again), so I never able to pass the google setup wizard.
I tried to clean addon.d with survival script removal, it didn't help as well. It kept soft rebooting a moment after setup wizard showed up.
I thought it was nikgapps problem. However it's not.
I do the usual wipe, now with system + vendor + metadata wipe
Flash crdroid alone without gapps, same problem. Made it to lineage wizard, then it's never ending soft reboot again.
I tried with several another rom not listed in here XDA (derpfest, ancientos), same problem. Made it to google setup wizard, a very short moment after, it enters never ending soft reboot.
The weird thing is, if I flash EvoX (latest now is 7.8) again, the issue doesn't occur, so it's the only rom which allows me to finish setup and I can use right now.
Things I haven't tried:
1. Format data and flash without DFE (I'm sure it's not DFE problem, usually problem already arose before the rom logo showed up)
2. Use adb to skip the setup wizard (I don't think it will help since crdroid without gapps also ends up soft reboot)
3. Vanilla official lineage (tried vanilla crdroid, same issue)
4. Revert back to original miui 12.5
My device is redmi note 8T.
Is there anyone facing the same issue before?
x3r0.13urn said:
Hi,
There has been an issue that riddles me, and I can't understand why it happens.
I've use Evolution X A13 (from here XDA), then try to switch to crdroid 9.3 (also here from xda)
Since I'm not encrypted, the usual steps I take were
1. clear fingerprints + pattern
2. reboot twrp
3. wipe from twrp
4. flash the rom
5. flash the DFE
6. reboot system
I rarely root. Even if I root, I always do it after first or many reboots after.
Now the weird thing happened.
crdroid 9.3 + nikgapps passed the boot until the setup wizard appeared, but then it's automatically rebooted by itself. Not hard reboot, it's similar like soft reboot (it's showing crdroid logo, back to setup wizard). Then it keeps soft rebooting (showing setup wizard for a moment then goes soft reboot again), so I never able to pass the google setup wizard.
I tried to clean addon.d with survival script removal, it didn't help as well. It kept soft rebooting a moment after setup wizard showed up.
I thought it was nikgapps problem. However it's not.
I do the usual wipe, now with system + vendor + metadata wipe
Flash crdroid alone without gapps, same problem. Made it to lineage wizard, then it's never ending soft reboot again.
I tried with several another rom not listed in here XDA (derpfest, ancientos), same problem. Made it to google setup wizard, a very short moment after, it enters never ending soft reboot.
The weird thing is, if I flash EvoX (latest now is 7.8) again, the issue doesn't occur, so it's the only rom which allows me to finish setup and I can use right now.
Things I haven't tried:
1. Format data and flash without DFE (I'm sure it's not DFE problem, usually problem already arose before the rom logo showed up)
2. Use adb to skip the setup wizard (I don't think it will help since crdroid without gapps also ends up soft reboot)
3. Vanilla official lineage (tried vanilla crdroid, same issue)
4. Revert back to original miui 12.5
My device is redmi note 8T.
Is there anyone facing the same issue before?
Click to expand...
Click to collapse
Battery issue maybe? Is it fine when the device connected to the charger? If yes, then 100% the battery, to be exact its the fuse on the bms.
Edit: already answer your question about battery before lol, you already replaced your battery right so isnt the battery then.
Maybe you can try take a logs with adb and see what's going on
SkyFlex said:
Battery issue maybe? Is it fine when the device connected to the charger? If yes, then 100% the battery, to be exact its the fuse on the bms.
Edit: already answer your question about battery before lol, you already replaced your battery right so isnt the battery then.
Maybe you can try take a logs with adb and see what's going on
Click to expand...
Click to collapse
lol, man, I've replaced the battery, it's like new again now. The back covered got replaced as well since I was sloppy removing the old glue.
Anyway, isn't adb logcat useless since every restart it's resetting? And dmesg was supposed to help debug kernel related issue? I'm not sure whether this is a kernel issue since flashing other kernel didn't help and one rom made it successfully (evox).
I tried to access adb while it's soft rebooting, but it won't recognise my phone (my guess because I haven't enabled the usb debugging, but how do I enable it while having a soft reboot?)
x3r0.13urn said:
lol, man, I've replaced the battery, it's like new again now. The back covered got replaced as well since I was sloppy removing the old glue.
Anyway, isn't adb logcat useless since every restart it's resetting? And dmesg was supposed to help debug kernel related issue? I'm not sure whether this is a kernel issue since flashing other kernel didn't help and one rom made it successfully (evox).
I tried to access adb while it's soft rebooting, but it won't recognise my phone (my guess because I haven't enabled the usb debugging, but how do I enable it while having a soft reboot?)
Click to expand...
Click to collapse
Yea probably usb debugging isnt enabled since you just reflash the rom. If usb debugging is enabled, you can get log when the phone boot up ( start capturing at boot animation )
There is kmesg, but nowdays I think its console-ramoops in /sys/fs/pstore, you need to get it when the phone restarted and not easy to read compare to dmesg/logcat
In evox there is no problem at all? No random reboot or some apps get force closed?
Are you using latest firmware? But again, you successfully flash the rom and boot up to the setup screen.
SkyFlex said:
Yea probably usb debugging isnt enabled since you just reflash the rom. If usb debugging is enabled, you can get log when the phone boot up ( start capturing at boot animation )
There is kmesg, but nowdays I think its console-ramoops in /sys/fs/pstore, you need to get it when the phone restarted and not easy to read compare to dmesg/logcat
In evox there is no problem at all? No random reboot or some apps get force closed?
Are you using latest firmware? But again, you successfully flash the rom and boot up to the setup screen.
Click to expand...
Click to collapse
Yes, of course at the latest firmware, the device has stopped receiving update long ago.
No, evox has no problem at all. My guess some rom uses the same device tree, which causes the soft reboot, while evox use their own device tree which has no issue.
I tried to disable setup wizard but it's not avail since I can't access adb while the device soft rebooting. If I do that in twrp adb, these commands yielded error, stating "settings" is unknown
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
- Formatting data, always, either before of flashing the ROM or previously to reboot.
- Check if the vendor is based on Miui or AOSP, given the case, it would be needed to wipe it previously to flash the ROM.
- Updating the firmware to the latest version.
- Flashing the stock ROM as based prior to flash the ROM.
Found 2 other roms which works without soft rebooting. Unfortunately, they're not on XDA neither. It's risingos and alphadroid. Unfortunately, NFC is broken in risingos and it has serious gcam issue. Alphadroid seems work like EvoX.

Crashing problem after installing /e/OS

Hi,
I bought a Moto G 5g Plus and instantly unlocked the bootloader to install /e/OS. I did everything exactly like the guide and everything worked, except that it randomly froze for some seconds and then restarted. Because of that, I tried installing LOS for microg but ran into the same issue. After that I wanted to install stock firmware with Motorola's own RSD software, but it couldn't set the phone to fast boot, so I tried to do it with the batch file included in the firmware zip just to see that recovery mode and fastboot now both show the no command error. After restarting, somehow /e/OS started (no clue how or why) and that's the point where I'm stuck.
I can't reinstall because of the recovery thing, and my OS is unusable because of the crashes. I would guess it's some background service that's crashing it, but I'm not an expert. Did someone have this issue in the past and can help me with this?
Thanks!

Categories

Resources