Related
For those who want to get in on CM12 pronto, here is a straight-from-CM-source build. The usual disclaimers: I'm not responsible for anything going wrong, including but not limited to bricking your tablet, requiring reflashes, or the NSA spying on you.
I will update this post with new builds as I create them every day or two, depending on what changes are merged: http://review.cyanogenmod.org/#/q/status:merged+branch:cm-12.0,n,z
If something doesn't work, I doubt I can help you, I'm not developer. I just ran the build and installed it on my Nexus 7 to see if it works (it does!). No cherry picks, just merged CM ROM/Kernel. However, if something doesn't work, post it.
What works: Everything stock plus a few CM features.
What's broken: Some people report data connection problems
What's here (1/03+):
Battery % indicator in notification bar, choosable icon
A bunch of behind the scenes stuff
Trebuchet
Status bar brightness control
Single-down swipe for settings panel for swipes on the right side of status bar
Privacy Guard (including Privacy section in settings)
CM File Manager
Advanced Reboot
CM Superuser controls
Double-tap status bar or lockscreen slider to sleep
Notification light controls (including custom lights for individual apps)
Codec enhancements
Option not to have the screen wake on plug
ADB over network
Voice wakeup
Lots of CM app Material design changes
Requirements:
Latest bootloader installed via fastboot
The ROM from here: 1/06 - https://www.androidfilehost.com/?fid=95887005526787409
Old versions:
1/05 - https://www.androidfilehost.com/?fid=95887005526786861
1/04 - https://www.androidfilehost.com/?fid=95887005526786862
1/03 - https://www.androidfilehost.com/?fid=95864024717074739
12/31 - https://www.androidfilehost.com/?fid=95864024717072947
12/29 - https://www.androidfilehost.com/?fid=95864024717071892
12/24 - https://www.androidfilehost.com/?fid=95864024717069216
12/22 - https://www.androidfilehost.com/?fid=95864024717068185
12/21 - https://www.androidfilehost.com/?fid=95864024717067734
12/19 - https://www.androidfilehost.com/?fid=95864024717066366
12/17 - https://www.androidfilehost.com/?fid=95857557620393232
12/18 - https://www.androidfilehost.com/?fid=95857557620393643
GAPPS: http://d-h.st/l6z
Latest TWRP
Instructions:
The usual: Backup, Wipe, Flash Zips.
If you have problems downloading files after you flash this, follow the steps listed here: http://forum.xda-developers.com/showpost.php?p=57295498&postcount=89
I DID NOT DO ANY OF THIS WORK. ALL THE CREDIT GOES TO:
The CM Team
Chainfire
TheMuppets
The testers: nazafalas, skynet11
Cheers
I tried the 12/17 build but got bootloop city even though I had already been running a Lollipop ROM. I was grilling some buffalo wings (woohoo!) at the time so I had waited well over 20 minutes. I'm trying again so I can try to grab a logcat if it doesn't boot this time.
Edit: Oh snap! This time it booted! Thanks for your hard work to everyone involved ��
The LTE radio seems a bit wonky, being disabled until I toggle airplane mode on and off again (after which it seems to work fine). Also, it gives some 5-digit number for my carrier as opposed to saying "Verizon Wireless." I tried to grab a logcat but it didn't contain anything useful. Sorry ?
bootloop
lolo696 said:
bootloop
Click to expand...
Click to collapse
Flash again. Someone else had the same problem. Let me know if it persists.
skynet11 said:
The LTE radio seems a bit wonky, being disabled until I toggle airplane mode on and off again (after which it seems to work fine). Also, it gives some 5-digit number for my carrier as opposed to saying "Verizon Wireless." I tried to grab a logcat but it didn't contain anything useful. Sorry ?
Click to expand...
Click to collapse
Carriers have unique ID codes. Apparently matching up those codes to their respective carriers hasn't been done yet.
Thanks for the heads up on the radio.
Wipe cache and dalvik is needed for first install, then no problem with boot.
Works good, thanks
Working fine. Thanks for supporting DEB
Working VERY fine. No radio issues for me, German APNs seem to be in order, as well.
deb build
Full wipe works best from km 4.04. Great so far with everything working to plan. Not used cm since my Xoom days.
First of all, THANK YOU for supporting deb! :fingers-crossed:
I tried to dirty flash over an existing AOSP install first (I know, bad Ambious) and obviously it didn't boot very well (it actually started deodexing, then stuck at 'Starting apps').
So then I went back to recovery, full-wiped, flashed clean.... and nothing. Endless boot (people throw the term 'bootloop' around where it's actually just a boot hang).
Tried clearing cache, dalvik, fix permission even - to no avail.
I also can't logcat because the CM default requires manual authorization... :/
(I have everything backed up so it's no biggy, I just really wanted to try it).
Any tips?
Ambious said:
First of all, THANK YOU for supporting deb! :fingers-crossed:
I tried to dirty flash over an existing AOSP install first (I know, bad Ambious) and obviously it didn't boot very well (it actually started deodexing, then stuck at 'Starting apps').
So then I went back to recovery, full-wiped, flashed clean.... and nothing. Endless boot (people throw the term 'bootloop' around where it's actually just a boot hang).
Tried clearing cache, dalvik, fix permission even - to no avail.
I also can't logcat because the CM default requires manual authorization... :/
(I have everything backed up so it's no biggy, I just really wanted to try it).
Any tips?
Click to expand...
Click to collapse
flash your previous ROM again, flash CM12 over it, and if it gets stuck on "starting apps" again just do a normal reboot. It's really weird how a simple reboot after one of these lockups works better than starting over from scratch. I've only rarely ever seen this be the case, and I've been flashing custom ROMs since the Eclair days.
Bum, now stuck in boot whatever, I'll try a reflash later.
skynet11 said:
flash your previous ROM again, flash CM12 over it, and if it gets stuck on "starting apps" again just do a normal reboot. It's really weird how a simple reboot after one of these lockups works better than starting over from scratch. I've only rarely ever seen this be the case, and I've been flashing custom ROMs since the Eclair days.
Click to expand...
Click to collapse
Amazing how the simplest of solutions sometimes pass by us.
It actually worked
Thanks!
Can some people test GPS for me? Thanks!
Worked fine for me last night even indoors.Not got round to a reflash today though so on kk at the moment, not sure why it wouldn't boot up this morning even with a soft reboot.
Clean flashed 19 build and gapps, all working as it should,no issues with 3g,GPS or videos so far.????
GPS works great for me ?
Mmmm battery stats saying 4hours left o 82%, better watch that.
As soon as you turn it off and back on it goes into bootloop or sticks on upgrading app.
After flashing the latest version( pa_i9300-5.1-20150528.zip) in recovery, 'Reboot System' reboots to recovery itself. Weird! So I flashed the earlier version(pa_i9300-5.1-20150520.zip) and it rebooted to system and it works. Now I get the OTA update in 'Paranoid OTA' app for the latest version that gave me problems. If I install,
1. Will there be any issues with reboot or any other related issues?
2. Should I reinstall installed apps after update?
Thanks
Not sure if related but I installed pa_i9300-5.1-20150520.zip some time ago on my i9300, everything has been working nicely. Then came the 28th update and another one earlier this month... but installing those updates just resulted in a crash after installing (as in the boot screen looping). Now my system just popped up with an 20150619 update so I thought to try again, but again it download and installs just to loop the boot screen. This time thought I afterwards decided to re-install superSU and my boeffla kernel, that seemingly did something as the phone booted and update. Now maybe this is something one have to do for each update for it to work? I'd love to know for the future as I'm no expert on this, though if you have something similar maybe that's what is required.
Organizer21 said:
Not sure if related but I installed pa_i9300-5.1-20150520.zip some time ago on my i9300, everything has been working nicely. Then came the 28th update and another one earlier this month... but installing those updates just resulted in a crash after installing (as in the boot screen looping). Now my system just popped up with an 20150619 update so I thought to try again, but again it download and installs just to loop the boot screen. This time thought I afterwards decided to re-install superSU and my boeffla kernel, that seemingly did something as the phone booted and update. Now maybe this is something one have to do for each update for it to work? I'd love to know for the future as I'm no expert on this, though if you have something similar maybe that's what is required.
Click to expand...
Click to collapse
I think flashing the Kernel as you did after the dirty flash will help. But the there is no stable Kernel available for CM12.1, even the Boeffla you are using is in the alpha stage, no support yet! So how is the battery life and stability with Boeffla Kernel?
Hi,
I am running RR 5.8.3, v. from 23-04-17.
I was forced to set fluencetype for the past few flashes to null or something, because otherwise I did not have sound during calls.
Right now the call quality is unbearably bad. It was not THAT bad on older ROMs, before I had to disable this fluence-thingie.
I want to upgrade the ROM, but what else am I supposed to improve the voice quality? I could not find a decent source.
Factory reset -> VoLTE patch -> RR ROM -> GAPPS?
Anything else? Some people wrote "updade your firmware" - how am I supposed to interpret it? Install MIUI Rom? So, like flash it from TWRP and replace it with RR 2 minutes later? I am alergic to MIUI.
This topic kind of explains it, but links are down and content might be outdated:
https://forum.xda-developers.com/redmi-note-3/how-to/android-n-permanent-volte-fix-10000-t3541922
Up
Up.
Right now I am stuck on a bootloop with rom's logo. I can access TWRP and flash stuff just fine, but I cannot load the system. Restoring from backup has failed.
I have installed 7.7.7 firmware - https://www.androidfilehost.com/?fid=673368273298969813
and booted to the system. It did not recognize my PIN and locked my card. Unlocked it with PUK on another device, but still the same.
Flashed newest RR with GAPPS and reflashed the firmware. Bootlooping begun.
Tried different ROMs, tried a different firmware - https://www.androidfilehost.com/?fid=673368273298969055
What should be the "next step"?
I was able to fix it, but man this was my last flash of this device. My next step was to brick the device, had to start from stratch after that. Never had so many different issues... I will rot on current ROM till Pixel 2 arrives.
Hi everyone,
My phone has this restarting loop issue after flashing either Candy7 or CM13 ROM. Not sure if this is bootloop error because It got pass the Huawei booting logo, but as soon as it finish loading the Google App and go to the OS home screen it restart again and again. Worth noting that the phone restart from ROM loading logo (the blue face for CM13 or the Google Dot for Candy7), not all the way back from Huawei booting logo.
First I use TWRP to factory reset wipe, then advance wipe /system, /data, /cache / Dalvik, then install new ROM + Gapp, and got the sucess message, then reboot to system.
I also tried with out Gapp to save loading time, and it restart again when get to OS home screen.
Please advise what may cause this.
No issue when i restore back to B322 EMUI 3.1
I have US version unlocked MT2-L03, B322 version, unlocked bootloader, rooted, TWRP 3.1.1.0 installed.
I made a video clip of the looping: https://www.youtube.com/watch?v=Y7kRpdGN2qA
I'm going through the EXACT same thing. I tried CM13, CM14 and even CandyRom, and the same thing happened more or less. Even if I got the ROMs running for a while, eventually that LOD (Loop of Death) would hit and I'd have to again reflash. I'm now back to B322 (Lollipop) for stability.
Given that the SAME thing is happening on all those ROMs, it's leading me to think that perhaps there is a software issue with my phone. Not sure if this helps, but I do think it could be the way I updated to Lollipop (B322) from the original Jelly Bean (B148). I've done a LOT of digging, and it looks like the way I did it was not quite right, even though my phone has worked fine all this time.
Here is the XDA post that seems to detail the correct upgrade path to B322:
https://forum.xda-developers.com/ascend-mate2/help/how-to-update-unlocked-mt2-l03-to-t3422775
Basically, it looks like the correct path should be B148 (Jelly Bean) --> B309 (Lollipop) --> B322 (Lollipop)
Being rather new, I just flashed to B322 right off of B148. I am now wondering if this could be the source of my problems. Especially since I keep getting the "Error 7" for "unknown bootloader" whenever I use TWRP 3.1.1 to flash LineageOS or CandyRom.
But, if you successfully used TWRP 3.1.1 to flash, that means your bootloader was recognized (I got the Error 7). If that's the case, then we're both having the same issue and something else is indeed the culprit.
I strongly suspect that "something else" could be GAPPS. I've experimented with several GAPPS packages, and noticed that right before crashing and the dreaded infinite loop, something glitched involving Google apps.
Desperately want to leave Lollipop since Oreo is about to drop meaning we Android L users are in for a world of hurt if we can't migrate soon. :-\
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
My phone has been rooted for over a year now, I've had many roms on it doing that time. This loop started with a app I updated from the play store. Not sure it may be substratum will look into it when I have more time..
These problems is because of the room. Try to install lineageOs.
Thanks Kevinoriej,
Same looping issue on LineageOS, after loading to OS homescreen , phone restart.
Also get error 7, and manually remove "assert" lines in the ROM script in order to flash.
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
I believe the Error 7 message is because your bootloader is showing as "unknown". I downloaded an app from the Playstore that gave me my device's technical info, and sure enough, my bootloader is listed as "unknown". I forwarded a question to Huawei's EMUI team asking them if that happened due to unlocking it (using Huawei's official unlocking request). Still waiting for a replay. In order to get any of the ROMs to install, I had to downgrade TWRP to 2.8.7.0. Any version above that would trigger Error 7.
Out of curiosity, I then downgraded and flashed CandySix (with a corresponding GAPPS package) - and sure enough, the same looping happened. And again when I flashed CM13 AND LineageOS. The phone would successfully boot, get to the actual Start screen, and then boot again. I could NEVER predict exactly what triggered this. Also, I tried installing ROMs without GAPPS, and that didn't go well for me (couldn't get any of them to load properly without flashing a GAPPS package for some reason).
Something goofy seems to be happening between Google services and the custom ROMs on this phone. I'm not sure what's triggering it, but given the sheer number of different ROMs I've tried - ALL of which have the EXACT SAME ISSUE - I strongly suspect there is indeed a GAPPS problem lurking somewhere.
As a side note - I reflahsed B322 (restoring from backup) and the phone is again as stable as it has always been.
Is there an EMUI GAPPS package for Marshmallow and/or Nougat (i.e., pulled from Mate 7, 8 or 9) available for download? I'm game for testing.
RE: MT2 boot loop
(*** SEE POST #25 FOR UPDATED FIX!***)
I just noticed this thread, wish I found it earlier. I recently posted my discussion of the boot loop (and fix) here:
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345/page14
Bratzilla was right when he said in his post, "I strongly suspect there is indeed a GAPPS problem lurking somewhere".
Thanks EndlessFall,
please help to check this link: github(dot)com/opengapps/arm/releases/download/20170811/open_gapps-arm-7.1-pico-20170811.zip
no files listed.
RE: dead link for Open GApps previous versions & boot loop fix
Strange, it seems that in the past day Open GApps has purged their GitHub archive. The "Older Releases" button at their website still redirects to the GitHub repo, but it no longer displays any version other than the current one.
As long as it does not violate any policy, I can always post a copy of the Open GApps 08/11/17 ARM 7.1 Pico package.
Although I have not tried other GApps distributions (Delta, Beans, etc), in theory there is no reason why they shouldn't work, as long as Google Play Services is not newer than v11.3.02. I recommend the minimal GApps available. Installing "pico" was an important part of isolating, and simplifying the search for, the culprit.
As I mentioned in my original post, I tested all versions of Google Play Services on apkmirror newer than v11.3.02 (build format 436 for MT2L03), up until 08/26. All newer builds induced an immediate boot loop. A future version may resolve the boot loop issue and work fine on the MT2L03, but it does not seem to be available as of today.
Have been running custom ROMs on my MT2L03 for years. Boot looping problem began for me two weeks ago when I completely wiped/formatted my CandyROMs v7.1.2 06/15 install and flashed MDMower's 08/19 LineageOS. Began digging deep into the cause (knowing MDMower would not release garbage) and discovered the connection to Play Services. Have been running MDMower's LineageOS & CandyROMs v7.1.2 ever since without any issues.
Remember to use MDMower's TWRP v3.1N0-0, it is much more stable on the MT2L03.
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
RE: MT2 boot loop fix (workaround)
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
hondaman82 said:
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
Click to expand...
Click to collapse
EndlessFall said:
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
Click to expand...
Click to collapse
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
RE: new ROM builds, GApps, & boot loop issue
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing (at least for me). Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
MT2-User said:
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Click to expand...
Click to collapse
EndlessFall said:
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing. Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
Click to expand...
Click to collapse
Thanks!
RE: return of boot loop
Sorry to hear that Hondaman82.
I can only speak from my own experience, which is that my MT2L03 has been stable for the past 2 weeks using Open GApps pico dated no later than 08/11. It is possible that your Google Play Services was auto-updated to a version newer than v11.3.02 (inducing the loop), but you won't be able to tell because you can't boot the corrupted OS to read the version number in app settings. If my boot loop returns, I'll do an ADB pull from TWRP to examine the Play Services package version (curious to see if there is an update correlation).
Goes to show what I mentioned yesterday, which is that the root cause is likely some incompatibility between the ROMs customized for MT2L03 and Play Services that can only be fixed by a commit to the ROM source code, a script, patch, or change to Play Services.
Let's see what happens, perhaps MDMower would be willing to offer his expertise? I visited Matt's website, GitHub and XDA profile, but it seems difficult to contact him directly....
hondaman82 said:
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
Click to expand...
Click to collapse
RE: preventing Google Play Services auto-update
(***SEE UPDATED FIX IN POST #25!***)
For those of you willing to experiment further, there is a method that supposedly disables Google Play Services from updating. This might allow you to "lock in" v11.3.02 until there is a proper fix for the boot loop:
https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832
Basically, this involves using a root file manager to create two empty folders entitled "com.google.android.gms-1.apk" and "com.google.android.gms-2.apk" in the "\data\app" directory, causing auto-update to fail.
I haven't used this hack, try at your own risk!
Of course, this works off of the assumption that updating Google Play Services beyond v11.3.02 is the only factor involved in the boot loop. I just haven't dug deep enough...
Mine (Candy 0725 build) went into LOD by itself a moment ago
Does anyone have a B322 TWRP backup ZIP? I as of this morning have 2 MT2 phones dead. One went into LOD about 3am and the other about 4am.
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
iJaviXR said:
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
Click to expand...
Click to collapse
Check my POCO F1 Ultimate Collection & Guides. Try to Clean Install Pixel Experience for example, according my guide (u need to format data also). Let me know how it goes.
Tried Android 10 and 11 Pixel Experience, tried with stock and NG Kernels. Still stays forever in the first load of the SO.
Just got the properties file from XiaomiADBFastbootTools. Maybe someone can see something wrong on it.