So my mi mix 2 was working perfectly fine running PixelExperience until some hours ago it rebooted and now won't boot again.
When I try to boot it gets to the MI logo, stays there for some seconds and after that reboots to TWRP, and any time I try to do something in TWRP it errors to "Unable to mount storage". I've tried with 4 different ROMs soo it's not from that, and I reflashed TWRP with fastboot. No luck there either. Any suggestions would be helpful
Android 11? Do a format data because your storage is likely encrypted, its a common issues on most of A11/R Chiron's ROM.
Related
Long story short:
EDIT: I somehow magically (after 2 hours of trying) got into recovery, cleaned and wiped everything and booted into MIUI. Switched to CM 12.1, leaving this thread for anyone that experiences the same problem.
1. I was running CM11-R24, with an early version of the Xcelerate kernel. All was fine and well but today it restarted on its own a couple of times. It would enter a bootloop that I managed to get out of by going into recovery and rebooting from there.
2. Bootloop happened again, couldn't get into recovery.
3. Installed newest twrp recovery via fastboot. No change.
4. Managed to hardbrick my phone by installing a wrong .img of a global version.
5. Managed to revert back to a softbrick by installing the right (hopefully) global version of my mobile phone.
6. I did manage to read a logcat inbetween and I remember there being something about the kernel settings being nulled to default, because there was a failed boot 2 times in a row.
Links:
Hard-brick to soft-brick procedure I followed - http en.miui.c o m thread-54139-1-1.html
Used global version: Singapore 50? Going to try other versions
Settings in MiFlash tool (using 2014.11 version). - http postimg.o r g /image/hh122e54j
Current problems:
1. When powering up the phone, it will not go beyond the Mi logo.
2. When trying to enter recovery (volup+power) I enter another loop. It is normally 10-15 seconds of Mi logo, power down, 3-5 seconds of Mi logo, power down. Repeat. I do not stop holding the recovery combination while this happens.
3. I have installed via fastboot all of these recoveries - TWRP 2830, TWRP 2860, Philz latest recovery. After installing each of them, I can not enter recovery mode again. Flashing a new recovery doesn't seem to change that.
I have access to fastboot, currently I installed the stable fastboot rom version "armani_images_JHCCNBH45.0_4.3_cn_e7e373f319".
I can not get adb to recognize the device, only fastboot. Can't get a logcat because of it. If you think I might be doing it wrong, please walk me through the process.
How do I get it back to working condition? The phone was bought in Bulgaria from a retailer, but I don't know which country it was originally shipped from, only that it's a WCDMA version.
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
ford.sushil said:
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
Click to expand...
Click to collapse
Oh oh oh don't be rude everyone has his own priorities and financial limitations
Bootloop
Dude, I have the same problem, can you help plus?
Hey, guys. :victory:
I had the ROM LineageOS on my Zenfone 2 (ZE551ML), but I was factory reset by setting the cellphone instead of using the recovery mode. With that, my cell phone looped through the TWRP. I tried everything, clean the cache, clean the system, reinstall Lineage, finally tried to reinstall the ROM stock. But I thought it was taking too long (more than 10 minutes in the same process), so I hung up and tried to call the cell phone again, but it was on the black screen, just vibrating. :crying:
I was able to solve this problem by reinstalling the firmware and stock ROM using xFSTK and ADB Fastboot (I could not use the Asus Flash Tool, I did the whole process manually).
Now, I have another problem, for a change. The stock ROM is Android Lollipop, on the Asus website has update for Android Marshmallow, including already managed to upgrade before migrating to Lineage. But now, when I restart the system to upgrade, it goes into fastboot mode and when I try to get into recovery mode it goes back to the fastboot or when I put in normal boot it starts without updating. I tried to install TWRP again but it is looped in Fastboot and I need to do all the procedure I did before to recover the phone.
Has anyone had a problem like this or do you have any idea how to solve it?
P.S. Sorry for any English error. Google translator. :B
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.
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.
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.