[ROM][RAV*/SOFIA*][11][UNOFFICIAL] PixelExperience (Plus) [AOSP] - Moto G Power ROMs, Kernels, Recoveries, & Other De

[ROM][RAV*/SOFIA*][11][UNOFFICIAL] PixelExperience (Plus) [AOSP] - Moto G Power ROMs, Kernels, Recoveries, & Other De

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for [RAV*/SOFIA*]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
Face unlock
Lights
Sound/vibration
Known issues
FM Radio
You tell me
Downloads
Link to Post
Installation
Link to Post
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 11
Security patch level: November 2021
Build author/Device Maintainer: AbsoluteZeroEdge
Kernel Source: https://github.com/S4muel007/kernel_motorola_trinket
Device Source: https://github.com/ph4n70m-404/device_motorola_sofiar
Vendor Source: https://github.com/ph4n70m-404/vendor_motorola_sofiar
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Contributors
Vache for initial device and vendor sources + TWRP
ph4n70m & Beetle84 for tons of building help
S4muel007 for kernel
Thanks awesome peeps
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2021-11-20
Last Updated 2021-11-21

Download Links
TWRP
TWRP - Credit to Vache
https://drive.google.com/file/d/1SwiiptkODqLTnDF1GRknYrF2g2yPxdJY/view
Pixel Experience
11/20/2021 Build - Initial Build
https://drive.google.com/drive/folders/1pdStP6Rnph19wIu_plpDwjRa124yJvNK?usp=sharing
11/21/2021 Build - Added Moto Camera 2
https://drive.google.com/drive/folders/1dSnZUiuK5TlOEtZU8oQIbjjV-TxJgFyr?usp=sharing

Installation
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
FastbootD
1) Extract rom zip and open cmd prompt in the extracted folder
2) Reboot into fastbootd
Code:
fastboot reboot fastboot
3) Flash images
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
4) Format data
Code:
fastboot -w
5) Reboot, profit.
TWRP
1) Boot to bootloader
2) Flash TWRP (included download above)
Code:
fastboot flash recovery_a twrpfile.img
fastboot flash recovery_b twrpfile.img
3) Flash the rom
4) Format Data (not factory reset)
5) Reboot, Profit
5.1) (Optional) If magisk is desired flash it in TWRP after first boot

Reserved

I would like to try this but I have a question:
Is this rom for sofia or sofiar? The title of the post says sofia but the download link says sofiar.
which is it? I have the U.S. retail version of the Moto G Power, which is sofia.

classic757 said:
I would like to try this but I have a question:
Is this rom for sofia or sofiar? The title of the post says sofia but the download link says sofiar.
which is it? I have the U.S. retail version of the Moto G Power, which is sofia.
Click to expand...
Click to collapse
Yes it should work,
In the title it shows rav*/sofia* for wildcards meaning any rav*, or sofia* device

AbsoluteZeroEdge said:
Yes it should work,
In the title it shows rav*/sofia* for wildcards meaning any rav*, or sofia* device
Click to expand...
Click to collapse
Okay thank you. If I give it a try I will let you know how it goes.

I originally installed Beetle84's Havoc Rom, which he/she no longer supports, on my Moto G Power 2020 XT2041-4 using FlashbootD, but, soon, my battery life diminished until it barely lasted a day. So, I tried to flash the new Lineage 18.1, but it failed and I had to Rescue my device. It's now running the stock Android 11 (A!11) Rom. Other Cooks have suggested that I can't flash another Rom until I downgrade the device to A10, which I haven't been able to do. I wanted to try Vache's Moto Flash Tool, but I can't find instructions online. Do I have to downgrade to A10 to flash this Rom? If not, can I just follow the above instructions which are similar to Beetle84's instructions I successfully followed when I flashed his Havoc A11 Rom? Also, how does this Rom compare to Havoc?
Thanks

jhford said:
I originally installed Beetle84's Havoc Rom, which he/she no longer supports, on my Moto G Power 2020 XT2041-4 using FlashbootD, but, soon, my battery life diminished until it barely lasted a day. So, I tried to flash the new Lineage 18.1, but it failed and I had to Rescue my device. It's now running the stock Android 11 (A!11) Rom. Other Cooks have suggested that I can't flash another Rom until I downgrade the device to A10, which I haven't been able to do. I wanted to try Vache's Moto Flash Tool, but I can't find instructions online. Do I have to downgrade to A10 to flash this Rom? If not, can I just follow the above instructions which are similar to Beetle84's instructions I successfully followed when I flashed his Havoc A11 Rom? Also, how does this Rom compare to Havoc?
Thanks
Click to expand...
Click to collapse
unfortunately yes you have to downgrade to a10 for the rom to boot
for downgrade instructions it's rather self explanatory. just drop ur stock 10 firmware zip in the firmware folder and start the flash
after u downgraded just use the installation guide above
And for how it compares, Not sure. It's basically AOSP but with google apps, It's like havoc but more bare and made for pixel fans that want the pure pixel experience
if u want more features I would definitely point u towards ph4n70m's havoc build

AbsoluteZeroEdge said:
unfortunately yes you have to downgrade to a10 for the rom to boot
for downgrade instructions it's rather self explanatory. just drop ur stock 10 firmware zip in the firmware folder and start the flash
after u downgraded just use the installation guide above
And for how it compares, Not sure. It's basically AOSP but with google apps, It's like havoc but more bare and made for pixel fans that want the pure pixel experience
if u want more features I would definitely point u towards ph4n70m's havoc build
Click to expand...
Click to collapse
Thank you, but I don't understand this: "just drop ur stock 10 firmware zip in the firmware folder and start the flash." So, can you please give me specific downgrade instructions. I've tried and failed at least 6 times.

jhford said:
Thank you, but I don't understand this: "just drop ur stock 10 firmware zip in the firmware folder and start the flash." So, can you please give me specific downgrade instructions. I've tried and failed at least 6 times.
Click to expand...
Click to collapse
Well, in moto flash tool's root directory it has a firmware folder to place your device's stock firmware for it to flash, after that is done open up the tool and select the stock 10 package u placed

AbsoluteZeroEdge said:
Well, in moto flash tool's root directory it has a firmware folder to place your device's stock firmware for it to flash, after that is done open up the tool and select the stock 10 package u placed
Click to expand...
Click to collapse
I have done that both zipped and unzipped several times and it has always failed. Maybe I downloaded the wrong firmware. I got it from lolinet. Do you have a link for the correct A10 firmware for Moto G Power 2020 XT2041-4?
BTW, since I'm now stock A11, I used Nova Launcher v6.x - new.version 7.x is incompatible with many of my widgets - today.to make the UI look identical to my rooted and rommed Nexus 7 2013 deb tablets, and it's pretty livable. Plus, Android Auto now works perfectly and never did when the phone was rooted and rommed. Food for thought.
[Edit] I flashed Vache's TWRP. I'd be pretty happy if I could make a Nandroid backup of my current stock setup. Have you done that?
Thanks again

jhford said:
I have done that both zipped and unzipped several times and it has always failed. Maybe I downloaded the wrong firmware. I got it from lolinet. Do you have a link for the correct A10 firmware for Moto G Power 2020 XT2041-4?
BTW, since I'm now stock A11, I used Nova Launcher v6.x - new.version 7.x is incompatible with many of my widgets - today.to make the UI look identical to my rooted and rommed Nexus 7 2013 deb tablets, and it's pretty livable. Plus, Android Auto now works perfectly and never did when the phone was rooted and rommed. Food for thought.
[Edit] I flashed Vache's TWRP. I'd be pretty happy if I could make a Nandroid backup of my current stock setup. Have you done that?
Thanks again
Click to expand...
Click to collapse
What's Moto Flash Tool's output? And I can't really decide the correct firmware for you phone, u need to see what software channel your phone is and select it here: https://mirrors.lolinet.com/firmware/motorola/sofia/official/
for nandroid backup well I'm not really sure, haven't done one before. a quick google search should do something for you.

AbsoluteZeroEdge said:
What's Moto Flash Tool's output? And I can't really decide the correct firmware for you phone, u need to see what software channel your phone is and select it here: https://mirrors.lolinet.com/firmware/motorola/sofia/official/
for nandroid backup well I'm not really sure, haven't done one before. a quick google search should do something for you.
Click to expand...
Click to collapse
Here's how I used Moto Flash Tool (MFT). Pasted A10 firmware in firmware folder. Connected phone in bootloader mode. Double clicked the MFT exe. A blank DOS window popped up and disappeared. That's it.

jhford said:
Here's how I used Moto Flash Tool (MFT). Pasted A10 firmware in firmware folder. Connected phone in bootloader mode. Double clicked the MFT exe. A blank DOS window popped up and disappeared. That's it.
Click to expand...
Click to collapse
make sure it's in a path with no spaces, i recommend putting it in a folder with of course no spaces again on any drive's root

AbsoluteZeroEdge said:
make sure it's in a path with no spaces, i recommend putting it in a folder with of course no spaces again on any drive's root
Click to expand...
Click to collapse
I followed you suggestion and only moved the folder to the root of C:\ that hosts the exe and the firmware, etc. folders. I double clicked the exe and for the first time, a usable batch file DOS window opened. So, it appears that I have a working setup. However, I'm going to think about rooting/romming this phone again, because I don't want to lose Android Auto (AA) again. But AA only works with a USB wired connection in my car, and I ordered an AAWireless device which should obviate the wired connection and allow my rooted/rommed phone to connect. I'll test it, and, if so, I'll flash your Rom Immediately.
Thanks for putting up with me.

I flashed this rom to my retail Moto G Power (2020) that was purchased from Google Fi. I make it to the Google logo screen on boot and it just sits there with the progress bar perpetually scrolling. Any advice?

NobleX13 said:
I flashed this rom to my retail Moto G Power (2020) that was purchased from Google Fi. I make it to the Google logo screen on boot and it just sits there with the progress bar perpetually scrolling. Any advice?
Click to expand...
Click to collapse
First boot usually takes a while, if it hasn't booted within 10 minutes it's stuck. Make sure you did a Format and not only a Wipe as well

Thanks. Upon further inspection when I executed a fastboot -w it wiped the data partition but did not format it. I'll try this again as time permits.
AbsoluteZeroEdge said:
First boot usually takes a while, if it hasn't booted within 10 minutes it's stuck. Make sure you did a Format and not only a Wipe as well
Click to expand...
Click to collapse

NobleX13 said:
Thanks. Upon further inspection when I executed a fastboot -w it wiped the data partition but did not format it. I'll try this again as time permits.
Click to expand...
Click to collapse
Yeah, fastboot -w usually has problems. Good luck!

Related

ROM: Sony AOSP 8.1 (H3113) (unofficial)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sony AOSP project
Disclaimer
I'm not liable for anything YOU do to YOUR device, YOU are doing it and it's YOUR device.
What is it?
It's a project developed and maintained by Sony Xperia Developers team.
You can get more informations here: https://developer.sony.com/develop/open-devices/
Can I build it by myself?
Sure, just follow these instructions and have patience!
What works and what doesn't?
According to this official page, almost everything seems to be fine.
How can I flash it?
Follow these steps:
Unlock the bootloader (this will erase your data and will void warranty): https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Setup fastboot on your PC (there are many guides for this step)
Download and unpack the zip archive
Open a shell into the folder containing unpacked files
Run these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (it’s not necessary to flash userdata every time)
Download and unpack the corresponding vendor image from here: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open a shell into the folder containing unpacked image
Run this command:
fastboot flash oem SW_binaries_for_Xperia_xxxxx.img (where "xxxxx" varies depending on the file)
(optional) In case you want to flash GApps, Magisk or other mods, you can use TWRP: https://forum.xda-developers.com/xa2-ultra/development/recovery-twrp-3-2-1-0-touch-recovery-t3774193
Reboot the device and enjoy!
Download link
You can get the builds from my AFH folder: https://androidfilehost.com/?w=files&flid=269497.
I haven't done any change to Sony's source code, these are vanilla builds.
Credits
All credits go to Sony and Google.
XDA:DevDB Information
Sony AOSP, ROM for the Sony XA2 Ultra
Contributors
axxx007xxxz
Source Code: https://github.com/sonyxperiadev
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-05-08
Last Updated 2018-05-08

Reserved
NOTE: I'm in no way associated with Sony, these are unofficial builds and are made for pesonal usage.
Also, these builds are untested so I can't assure they're going to work!

Reserved 2
Post reserved for future usage.

Reserved 3
Post reserved for future usage.

Reserved 4
Post reserved for future usage.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r20
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 81032020581dd636ab9d7f8414609bad07332288
Last commit of sonyxperiadev/kernel: 1df958f2943c6c5cae31018e42d2f42e8a55c4b3
Last commit of sonyxperiadev/device-sony-nile: c775da101d57377979cdcb79b1ba1b5bbd3739a4
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=818222786056029296.

It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).

Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying. And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it.
Click to expand...
Click to collapse
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.

roirraW "edor" ehT said:
I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.

Casserole said:
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Click to expand...
Click to collapse
You're welcome! I'm not suggesting that you flashing Magisk or anything is the cause of this on this ROM, it's just related to changes in Android 8.1 and that it doesn't really necessarily mean there's something wrong. I'm sure there are ways around it, but since I'm not a developer and I don't know what triggers it, I don't know.

Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?

tombassi said:
cool down dude !! XDA is not the correct please for these bad words. if you don't know what you are doing that is not the Developer fault and if you need no bugs stay with the stock ROM.
Click to expand...
Click to collapse
Thanks! With "almost everything seems to be fine", I meant that most of the main parts (should) work.
Camera is a known problem on Sony devices due to DRM keys getting erased on bootloader unlock.
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Click to expand...
Click to collapse
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
then reboot the phone and test.
These come directly from H4113 makefile, I can't assure you everything will be fine after this, but you can give it a try.
As per the fingerprint, it's currently broken on all variants, I'm sorry.
mirco_pa said:
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
Click to expand...
Click to collapse
Sony website reports it as currently not working on AOSP, I'm sorry.

axxx007xxxz said:
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Click to expand...
Click to collapse
I think SD card problem was related to something else, because it started working after reformatting.
But there were also problems with SIM card, it worked on first boot, but after removing and inserting it again device shown that there were no signal, so your solution may be helpful in this situation. I can't test it due to limited amount of time, though.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r26
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 1c992d7f3f2ef8d0b53397e23227e10489e40bec
Last commit of sonyxperiadev/kernel: ab6fd5b1a4126cfdd4391eefe8eba17eb6626781
Last commit of sonyxperiadev/device-sony-nile: 7d57c76da9ce47849429347e77e013781e63db2f
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=890278863836285554.

Can you build one for H4113? You shood have files for it too

Thanks axxx007xxxz for sharing these builds! They helped me recover Android on my completely wiped h3113 pioneer. Both the 8.0 and 8.1 build work for me. Downloading them to my PC was the hardest part, for some reason the download often fails.
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Thank you!
roirraW "edor" ehT said:
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I get the same error message right after booting, also without root. It's annoying, but I guess I can live with it.
P.S. As I'm a new user, I cannot use links yet. Please use these footnotes instead:
*: https[colon]//developer[dot]sony[dot]com/develop/open-devices/downloads/software-binaries
**: https[colon]//developer[dot]sony[dot]com/develop/open-devices/guides/aosp-build-instructions/build-aosp-nougat-8-1-oreo-4-4/#tutorial-step-6

1. parts of android which are closed source, graphics driver for example. you won't see them.
2. eng should give you more debugging options, like working adb logcat without enabling developer options which is sometimes needed while you're porting android to new device and there's just black screen on the phone for example. correct me if i'm wrong.
3. flashing worked through twrp for me but i had to build unsingned zip.
regarding the internal problem message, just ignore it.

davidhozic said:
Can you build one for H4113? You shood have files for it too
Click to expand...
Click to collapse
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Nonstop decay said:
Downloading them to my PC was the hardest part, for some reason the download often fails.
Click to expand...
Click to collapse
Unfortunately, Android File Host is problematic sometime.
Nonstop decay said:
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Click to expand...
Click to collapse
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.

axxx007xxxz said:
I can make a H4113 build if you want to test it though.
Click to expand...
Click to collapse
Just wondering aside from not being supported in Sony's open device program what exactly is needed to get the H3223 from getting AOSP 8.1 built for it? I can't imagine the kernel being much different on the H3223 from any of the other XA2 Ultra single sim models, right?

axxx007xxxz said:
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Unfortunately, Android File Host is problematic sometime.
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
Click to expand...
Click to collapse
Yes plese make a build for H4413, i get so many random errors and every time i fix an error there appears another. And is the build for this model supposed to work with h4113? Aren't the boot images incompatible?

[OFFICIAL] [NIGHTLIES] LineageOS 16.0

Reserved

Reserved

Thank you， ota ：）

How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras

7bob said:
How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras
Click to expand...
Click to collapse
Check again.

Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?

zidemizar said:
Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?
Click to expand...
Click to collapse
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.

npjohnson said:
Check again.
Click to expand...
Click to collapse
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?

7bob said:
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?
Click to expand...
Click to collapse
Just follow general guidelines. We already had testers and upgrading from 15.1 to 16.0 didn't cause any issues. Obviously, if you do run into an issue, it is suggested to clean flash first to see if it was a borked update

npjohnson said:
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.
Click to expand...
Click to collapse
Do you have a screenshot showing that it shows under screenlock settings?
Also what gaaps did you use when installing, I used the reccomended mindthegaaps and it kept giving me errors related to pixel apks.

link if image does not work
https://imgur.com/a/1eoVcgk
This is what shows under my screenlock setting, I do not have the setting that allows me to lock the phone using the fingerprint reader, this is from a fresh Lineage 15.1 installation with mindthegaaps, nothing else is installed on it. Had the same issue with lineage 16

Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.

Now I have installed los 16 and it was instructive for me. Learning by doing. After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP? I'm on slot b now and on system_a is nothing. If I want update later, I have to do just flash the zip over TWRP and then reboot it and then maybe flash gapps again, because it's the first update on slot_a? Hope that's works because the encoding problem. Don't have the key.

AmazerG said:
Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.
Click to expand...
Click to collapse
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
allrightlite said:
After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP?.
Click to expand...
Click to collapse
Remove your fingerprint and screen lock method prior to entering TWRP. If you came from a stock ROM you must format data before flashing LOS. Updates can be done automatically with the updater, or manually thru recovery. The latter requires more time with no added benefits. Also encryption is enabled with custom ROMs.

So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done

I have tries at this moment to update over the lineage updater in settings and it's stopping with installation error. After try to reboot to TWRP it's endet up in reboots. But LOS16 stats normally again after press power button a little bit. Now I try again to update. Presumably it isn't working again. I think I will reflash twrp first and try then over this to update. Good idea or what's going wrong on my phone?
I must do new install. All broken. Holy crap. Hope this time I get it working.

7bob said:
So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done
Click to expand...
Click to collapse
what are the steps to update from firmware 8.0 to LineageOS 15.1 or 16, please
unlock bootloader, twrp, magisk (no problem),
My phone locks the boot loader again when I try to install a custom ROM
my firmware (TWRP, magisk)
RETAIL/NASH_RETAIL_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
in any way I thank you :good:

Ok, I have found out how get it working. Updater app not working here, always installation error after end of update process. Don't know why. So now I have a way found out, which seems to be working every update. Go to TWRP, flash los16 new zip and, this is very important (understand it very late xD) don't forget to flash twrp installer zip directly after los 16, because otherwise on the other slot is the stock recovery again. So, after this boot to the other slot with twrp directly from your phone and flash gapps every time, every update. Here I forgot it and nothing of the play store and co. was working anymore. Android Framework ID was away, too. Is there an easier way to update over TWRP or do I have to do so? And what happend to, backup wasn't possible to restore, maybe cause thought encoding?
The new update process with A/B is not easy to understand directly But the rom is a beast, very very good. Why I update and switch to los16? That's easy, because the bluetooth bugs on stock oreo was terrible (and no 8.1-batterie icon ) and lags on few drm videos and here and there. Speed of the UFS-flash going slower and slower, no its 3 times faster again. This phone works really great with LOS16. Very good work! It's not easy to understand all, but I will get it in my brain
Edit: There is another point, which could be interesting. Netflix shows error on start up (15001) and this even though safety net is passed. Hm.. Have downloaded from play store. Maybe older version does do this job, don't know.

Ace42 said:
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
Click to expand...
Click to collapse
Is there anything different between Sprint Z2 force and Tmo ones in terms of hardware such as lack some band or what?

[ROM] Dirty Unicorns 14.7 {Bonito} (09/13/20)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_bluecross
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Reboot and ENJOY!
If you have a device that does not use TWRP
Download boot.img and ROM zip from DU server
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Reboot and ENJOY!
If you're just updating DU on a device without TWRP
Download ROM zip from DU server
Reboot into recovery and select Apply update from ADB to flash the zip
Reboot system now and ENJOY!
**All bugs and feature requests must be reported to JIRA**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Bonito
Other Links:
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/
Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel 3a XL
Contributors
NYCHitman1, jbats
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13
Created 2020-08-08
Last Updated 2020-09-13

Thank you so much!
I've used nothing but DU since March and I'd like to thank you for your continued work on our device. Hopefully now more people will find and appreciate your efforts!

Sweet a new rom to try out

@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.

41rw4lk said:
@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.
Click to expand...
Click to collapse
Currently, no. However, we are planning to do this in the future.

Just flashed & loving it so far. Great to see the team still working. I'm trying to remember the first phone I flashed dirty on. Maybe htc m8. It was so long I don't recall

I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation

godpowerrr said:
I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation
Click to expand...
Click to collapse
We're not making anymore variations of the boot animation. We have a light version and a dark version. That's good enough for us.
As for the lack of customization, we include what we find useful. We're never going to be one of these cookie cutter kitchen sink ROM's you see littered across XDA. If you would like to make a particular feature request, check the OP for instructions on how to do so.

FYI
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.
Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
Code:
C:\Users\Russell\Downloads\Android\ADB and Fastboot>adb sideload du_bonito-v14.6-20200808-1220-OFFICIAL.zip
serving: 'du_bonito-v14.6-20200808-1220-OFFICIAL.zip' (~47%) adb: failed to read command: No error
In recovery
Code:
Step 1/3
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
E:Error in /sideload/package.zip (status 1)
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.

ssurell said:
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.
Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
In recovery
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.
Click to expand...
Click to collapse
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.
TWRP does not work on Q for Pixel 3 and 4.
Please do some research before messing with the device further.

NYCHitman1 said:
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.
TWRP does not work on Q for Pixel 3 and 4.
Please do some research before messing with the device further.
Click to expand...
Click to collapse
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery

ssurell said:
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery
Click to expand...
Click to collapse
Unfortunately, it doesn't. The flash-all script only flashes to the active slot on the device, so you would have to manually change slots and run said flash-all script again to be completely up to date. As for the platform-tools versions, I believe 30.0.4 is the latest revision available at this time. Might be a good idea to download that and delete everything else you have.
Outside of this, our flashing instructions are very clearly labeled and should get you through the process of flashing DU as long as you follow the instructions that are applicable to you.

ROM is running great. Do we have to do a full wipe or can we just clear cache between uodates

sjpritch25 said:
ROM is running great. Do we have to do a full wipe or can we just clear cache between uodates
Click to expand...
Click to collapse
You don't have to wipe at all between updates. It's written in the OP. Please read the instructions.

Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!

champ784 said:
Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!
Click to expand...
Click to collapse
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.

Download from DU site fails
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?

NYCHitman1 said:
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.
Click to expand...
Click to collapse
Yeah that's what I figured. The second Android R releases, I don't see anyone caring ??

socksi said:
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?
Click to expand...
Click to collapse
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.
I will reach out to our webmaster and have him look into it. Stay tuned.

NYCHitman1 said:
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.
I will reach out to our webmaster and have him look into it. Stay tuned.
Click to expand...
Click to collapse
It fails even when using a VPN tunnel. Most probably it's not my Internet connection.
Maybe some kind of GEO blocking? I'm from Germany.

Development [CLOSED][ABANDONED] [OFFICIAL] [Rosemary/Secret/Maltose] Project Kasumi 1.x for Redmi Note 10S

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Another weebified custom ROM aiming to be a home for weebs - Based on Project Materium, an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Click to expand...
Click to collapse
We offer vanilla, GApps and AuroraOSS variants. If you install a vanilla variant, the only supported GApps package is MindTheGapps (GApps/AuroraOSS builds are not available for a few devices due to space issues).
Download & instructions:
Install MIUI 12.5 if you have updated to anything Android 12.
Fully install custom recovery of your choice.
Flash the ROM. You can also sideload it with ADB if you want to.
!!! If you'll flash Magisk, you'll need to enable "Reflash (recovery) after installing a ROM" after choosing the ZIP as well !!!
After flashing, reboot to recovery.
Format data.
Flash Magisk if you want to.
Reboot to system and enjoy!
Download (Taken down due to discontinuation)
IMPORTANT: If you are coming from another ROM, you need to format data (TWRP > Wipe > Format Data > *type "yes"*).
IMPORTANT: If you want to keep Magisk after each OTA, you need to make it flash to inactive slot **right before rebooting** (Magisk > Install (In "Magisk" card) > Install to inactive slot)
About:
Features:
Latest security patches merged from LineageOS
SafetyNet passing unconditionally without Magisk/with kdrag0n's SafetyNet fix
Many optimizations coming from Stellar OS/Project Materium/droid-ng
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more! (We accept suggestions!)
What's working:
Almost everything
Bugs:
Microphone doesn't work when speaker is enabled during calls.
You tell me.
Sources are available at https://github.com/ProjectKasumi and https://github.com/Kasumi-Devices
Full list of device sources used;
Device tree
Linux kernel tree used
Vendor tree for proprietary blobs
ROM Founded By: Yuki (AITEx64)
ROM Developed By: Beru Hinode
ROM Designed By: Ayuko, Qirkl and UsiF.
ROM OS Version: 1.3 "PoPiPa" R2
ROM Kernel: Customized Linux 4.14.186 from MiCode
ROM Firmware Required: MIUI 12.5.16.0.RKLMIXM (Global)
Based On: Project Materium 1.0 (LineageOS 18.1)
Version Information
Status: Discontinued
Last Stable Version: 1.4 "PoPiPa"
SELinux Status: Permissive
Initial Release Date: July 20, 2022

poggers! atleast some buildbot didn't post it this time

J6idot said:
poggers! atleast some buildbot didn't post it this time
Click to expand...
Click to collapse
It wasn't even their build, they just took my build and posted it away! XD

Let's goo. Very awesome work here

Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...

solidamage said:
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
Click to expand...
Click to collapse
I could never get used to MIUI myself so I feel you. For custom ROMs, there are quite a lot built (buildbotted) with practically the same bugs as well; you can check them out in respective Telegram groups/channels!

Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon

i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
It happens to me too ... Any advice?

Is this available on Android 12?

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?

Oxydeme said:
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Click to expand...
Click to collapse
yup did all the steps in the thread

nintendobuster420 said:
yup did all the steps in the thread
Click to expand...
Click to collapse
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked

Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc

nintendobuster420 said:
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
Click to expand...
Click to collapse
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
still no fast charge, will keep it tough
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
@HistoriaXV @nintendobuster420 hope you could success flash in the next days

Oxydeme said:
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
Click to expand...
Click to collapse
System reports "Charging slowly" but my battery fully charges from ~10% in just 1.5~2 hours.

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
I have recently pushed a boot fix about this, you can flash it and format data to get it fixed.

Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
I use the OFOX from Woomy and it works with it too, so it's not recovery fault.
You mentioned firmware requirement there, good shot! Glad to see someone that's not from the development team finally noticing it!

Oxydeme said:
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
Click to expand...
Click to collapse
The vbmeta required is shipped along with the ZIP itself, so whether if you disable it or not, you can always keep verity enabled AS LONG AS YOU DON'T MODIFY ANYTHING INCLUDING INSTALLATION OF TWRP. The boot problem was due to some missing permissions required with Lawnchair 12.0, which was platform-specific issue. I have mitigated it as the lead developer of Kasumi and now just waiting for LineageOS to merge August '22 ASB on their Lineage 18.1 branches to ship newer builds. Until then, I have placed a little flashable that you can slap in on the recovery. It's global (means will work on all devices with latest Kasumi build installed). In fact, all it does is just putting the new permission XML file.
Oxydeme said:
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Click to expand...
Click to collapse
Not at all. Even though I have Secret, everything should be around the same across all variants, given that Woomy also tested it only for NFC during initial bringup before.
Oxydeme said:
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
Click to expand...
Click to collapse
The dedication and the hassle... My God, it's just pure inspiration to me. XD
Oxydeme said:
still no fast charge, will keep it tough
Click to expand...
Click to collapse
As I said previously, it's what system reports presumably due to some SEL denials. I tried to get as many as possible sorted out, still no luck. But just as a fact, it actually is fast charging.
Oxydeme said:
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
Click to expand...
Click to collapse
Well, thank you I guess. ^^;
Before I begin with replies to these, just referring to "dude", I'm a girl so I would prefer you calling me with "dudess" or "dudette" instead. Again, all up to you. No forces here.
The debloat is rather Lineage talent, I really just based on Materium and added things on top.
That 13 GB system partition is something that's coming from partition values from source, so whatever you do unless you flash GSI, it will always be 13 GB. See GitHub:Kasumi-Devices/[email protected]/BoardConfig.mk (Partitions section, BOARD_SYSTEMIMAGE_PARTITION_SIZE flag) for more info.
Eh, I still can't find a way to get CPU info properly, I guess it's related to kernel? Unsure though.
And some more tweaks will come as well, just stay tight! I'm working hard on another update! ;3

Sambit0789 said:
Is this available on Android 12?
Click to expand...
Click to collapse
Unfortunately no. Kasumi 1.x.x are all Android 11. Android 12 Kasumi will be possible only once our internal tests will be done and I finally finish working on Kasumi v2. Hundreds hyped, gradually widening audience, looking into the release of it. xD

Question Xiaomi EU rom

My phone has arrived and in few days, I ll attempt to switch to the EU ROM
(I ve bought a CN unit, which arrived nice and sealed in its box)
So, I ll attempt to follow this guide to the letter: https://xiaomi.eu/community/threads/howto-install-fastboot-image.64508/
Heading over to sourceforge, I can see that the latest stable releases for my phone are one from AUG and one from MAY i.e.
xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip
2022-08-05
xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot.zip
2022-05-13
But according to that guide, it says "download latest fastboot" image. And thats the older one released in MAY (V13.0.12.0...)
So I presume I cannot use the latest V13.0.13.0 (released in AUG) for this method!?
Is there a fastboot (V13.0.13.0) in the making, so perhaps I could wait a little longer for that?
Or do I just use the one released 6 months ago?

jstoner said:
My phone has arrived and in few days, I ll attempt to switch to the EU ROM
(I ve bought a CN unit, which arrived nice and sealed in its box)
So, I ll attempt to follow this guide to the letter: https://xiaomi.eu/community/threads/howto-install-fastboot-image.64508/
Heading over to sourceforge, I can see that the latest stable releases for my phone are one from AUG and one from MAY i.e.
xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip
2022-08-05
xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot.zip
2022-05-13
But according to that guide, it says "download latest fastboot" image. And thats the older one released in MAY (V13.0.12.0...)
So I presume I cannot use the latest V13.0.13.0 (released in AUG) for this method!?
Is there a fastboot (V13.0.13.0) in the making, so perhaps I could wait a little longer for that?
Or do I just use the one released 6 months ago?
Click to expand...
Click to collapse
Without functional TWRP in A12, Xiaomi Eu rom provided roms in Fastboot .zip.
Now that there is a TWRP, the roms are in Zip.
Either you use a Fastboot .zip and update via Ota or you install the Twrp and flash the rom.
For updates you must go through the Ota and not flash directly with the TWRP.

NOSS8 said:
Without functional TWRP in A12, Xiaomi Eu rom provided roms in Fastboot .zip.
Now that there is a TWRP, the roms are in Zip.
Either you use a Fastboot .zip and update via Ota or you install the Twrp and flash the rom.
For updates you must go through the Ota and not flash directly with the TWRP.
Click to expand...
Click to collapse
Regarding TWRP, do I get the latest version (skkk) or the one from TeamWin? (because both are intended for 11 Ultra I think - codenamed "star")
My guess is skkk, which also says "A12"
Then I can use "xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip", which seems to be latest
I plan to use this guide - I hope it is accurate (it says "unofficial"!)

jstoner said:
Regarding TWRP, do I get the latest version (skkk) or the one from TeamWin? (because both are intended for 11 Ultra I think - codenamed "star")
My guess is skkk, which also says "A12"
Then I can use "xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip", which seems to be latest
I plan to use this guide - I hope it is accurate (it says "unofficial"!)
Click to expand...
Click to collapse
Official here:
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/

NOSS8 said:
Official here:
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/
Click to expand...
Click to collapse
Just done the same thing yesterday. Use 3.70_12-v6.5_A12-star-skk.img. I had problems with fastboot V13.0.12.0.SKACNXM_v13-12-fastboot had failed status read failed (too many links) errors. But think that's just my adb setup in Windows 11. So just used fastboot to boot twrp. Then in twrp flashed twrp to ramdisk reboot to recovery and flashed xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip formatted data reboot to systsem. Working V13.0.13.0. I ended up just copying V13.0.13.0.zip and twrp to a flash drive mounted OTG in twrp and installed. Only because of issues with laptop.

NOSS8 said:
Official here:
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/
Click to expand...
Click to collapse
no, by "unofficial" I meant the Guide ;-)
(if it would work if I followed that guide to the letter - as I m not too tech savvyy)

jstoner said:
no, by "unofficial" I meant the Guide ;-)
(if it would work if I followed that guide to the letter - as I m not too tech savvyy)
Click to expand...
Click to collapse
The installation remains the same
https://forum.xda-developers.com/t/twrp-mi-11-pro-ultra-mars-star.4280313/
If you install a xiaomi Eu rom (twrp included) check the version of Twrp and update it if necessary.

NOSS8 said:
The installation remains the same
https://forum.xda-developers.com/t/twrp-mi-11-pro-ultra-mars-star.4280313/
If you install a xiaomi Eu rom (twrp included) check the version of Twrp and update it if necessary.
Click to expand...
Click to collapse
Now, I ve backed up everything and was about to flash the phone to latest stable MIUI
But just realised v14 was released in the meantime, in December
But for the 11 Ultra, there is only weekly ROM available (no stable)
Looks like I ll have to extend my wait
As for v13, I can still see that the latest is xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip
I wonder - will there be another v13 release for this phone?
Should I go with this latest v13 or wait for the first stable v14 (star) release?
Sometimes, having been presented with choices, makes it so hard to decide! But for sure, I need a stable build for this phone..

jstoner said:
Now, I ve backed up everything and was about to flash the phone to latest stable MIUI
But just realised v14 was released in the meantime, in December
But for the 11 Ultra, there is only weekly ROM available (no stable)
Looks like I ll have to extend my wait
As for v13, I can still see that the latest is xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip
I wonder - will there be another v13 release for this phone?
Should I go with this latest v13 or wait for the first stable v14 (star) release?
Sometimes, having been presented with choices, makes it so hard to decide! But for sure, I need a stable build for this phone..
Click to expand...
Click to collapse
Whether Weekly or stable, both are based on the Chinese rom.
For the stable you will have to wait while Xiaomi releases the rom.
I use the Weekly when available and they are really "stable".
Note that if you install a Weekly and move to the stable you will have to format the data.
Also going from A12 to A13, formatting the data is not mandatory but I recommend it.

NOSS8 said:
Whether Weekly or stable, both are based on the Chinese rom.
For the stable you will have to wait while Xiaomi releases the rom.
I use the Weekly when available and they are really "stable".
Note that if you install a Weekly and move to the stable you will have to format the data.
Also going from A12 to A13, formatting the data is not mandatory but I recommend it.
Click to expand...
Click to collapse
Ah, OK - so there's no 'stable' MIUI v14 for the 11 Ultra yet? I get it..
As for the format consideration, I m a huge fan of clean installs too. I guess I ll go with v13 for the time being, as I don't have much of a time luxury to wait for the official stable v14..

Seems like it v14 (stable) has just been released for the 11 Ultra!
xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip
But is this ROM meant to be installed via fastboot or twrp?
In my mind, it is still not clear what the difference is between fastboot and twrp
I can only presume that twrp is essentially a GUI (vs just typing commands in fastboot!?) But I m not really sure anymore
I ve been an Galaxy S series user over the last years. Back then, I used to flash a new ROM via "Odin". Was that using the twrp method or fastboot? I m sorry, but I m totally confused now
Since twrp is an extra software that needs to be installed on the phone - isn't that come with any drawbacks? What is the more 'clean' approach to installing an MIUI on the 11 Ultra?

jstoner said:
Seems like it v14 (stable) has just been released for the 11 Ultra!
xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip
But is this ROM meant to be installed via fastboot or twrp?
In my mind, it is still not clear what the difference is between fastboot and twrp
I can only presume that twrp is essentially a GUI (vs just typing commands in fastboot!?) But I m not really sure anymore
I ve been an Galaxy S series user over the last years. Back then, I used to flash a new ROM via "Odin". Was that using the twrp method or fastboot? I m sorry, but I m totally confused now
Since twrp is an extra software that needs to be installed on the phone - isn't that come with any drawbacks? What is the more 'clean' approach to installing an MIUI on the 11 Ultra?
Click to expand...
Click to collapse
Yep, TWRP avoids typing command lines.https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/
Two version of roms:
Rom.Fastboot.zip to install with a pc with the Bat file included in the rom folder.
Provided this way if no working TWRP.
Rom.Zip to install via OTA.
If this is a first installation you will have to install the TWRP first then TWRP / wipe format data type Yes (this will erase all your data) and reboot to the TWRp and flash the rom, then the updates will be done via OTA/TWRP.

NOSS8 said:
Provided this way if no working TWRP.
Click to expand...
Click to collapse
So basically you imply that recovery (TWRP) is the preferred path
If I understood correctly, the biggest (?) advantage of chosing a recovery ROM (instead of a fastboot one) is the benefit of having OTA afterwards, right? (and maybe simplicity of having the GUI - that is TWRP)
Now, to put this the other way - what's the disadvantage of chosing the recovery ROM over a fastboot one? Is there any? (other than the need to have to install an 'extra layer' - that is TWRP)
So that ROM that was just released (xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip) is a recovery ROM. right? If so, the latest twrp (v3.7.0 from https://eu.dl.twrp.me/star/) will work for this brand new MIUI 14?

jstoner said:
So basically you imply that recovery (TWRP) is the preferred path
If I understood correctly, the biggest (?) advantage of chosing a recovery ROM (instead of a fastboot one) is the benefit of having OTA afterwards, right? (and maybe simplicity of having the GUI - that is TWRP)
Now, to put this the other way - what's the disadvantage of chosing the recovery ROM over a fastboot one? Is there any? (other than the need to have to install an 'extra layer' - that is TWRP)
So that ROM that was just released (xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip) is a recovery ROM. right? If so, the latest twrp (v3.7.0 from https://eu.dl.twrp.me/star/) will work for this brand new MIUI 14?
Click to expand...
Click to collapse
For Xiaomi EU roms regardless of whether they are in ZIP or Fastboot.zip only the way of installing them is different.
For Stock roms, those in Recovery are used for updating or troubleshooting, they only contain the essentials, unlike those in Fastboot containing all the Imgs of the phone.
For the TWRP, you must take into account the version of Android A12 or A13, not Miui13 or 14.
The link https://eu.dl.twrp.me/star/ is obsolete, the one I posted is the official one developed by SKKK.
xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip
use
twrp-3.7.0_12-v6.9_A13-star-skkk.img
The first boot of the rom takes 5/8 minutes.

NOSS8 said:
For Xiaomi EU roms regardless of whether they are in ZIP or Fastboot.zip only the way of installing them is different.
For Stock roms, those in Recovery are used for updating or troubleshooting, they only contain the essentials, unlike those in Fastboot containing all the Imgs of the phone.
For the TWRP, you must take into account the version of Android A12 or A13, not Miui13 or 14.
The link https://eu.dl.twrp.me/star/ is obsolete, the one I posted is the official one developed by SKKK.
xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip
use
twrp-3.7.0_12-v6.9_A13-star-skkk.img
The first boot of the rom takes 5/8 minutes.
Click to expand...
Click to collapse
I ll prob do it in the weekend
From what I read, I also have to unlock the bootloader and from a security PoV, I m not really happy about that, but no way around it. Just can't live with the stock CN ROM
Not sure if unlocking the bootloader takes time or if it is instateneous (via the MI website)
As for my concerns over the method (twrp vs fastboot), it would seem that the fastboot is probably more 'clean'
No disrespect towards the developers who made the twrp possible - thus making it so much easier for people to fiddle with ROMS on their mobile and at no cost, but regardless of that, it is still an extra piece of software that resides on the phone. Just the way I understand it. Again, not looking down at twrp
What do you mean by "fastboot containing all the imgs..."?
Isn't it one single image per phone model?
Or did you mean to say 'features' or 'apps'?
Personally, I d be more interested in less/apps/fancy features (except for security of course)

jstoner said:
I ll prob do it in the weekend
From what I read, I also have to unlock the bootloader and from a security PoV, I m not really happy about that, but no way around it. Just can't live with the stock CN ROM
Not sure if unlocking the bootloader takes time or if it is instateneous (via the MI website)
As for my concerns over the method (twrp vs fastboot), it would seem that the fastboot is probably more 'clean'
No disrespect towards the developers who made the twrp possible - thus making it so much easier for people to fiddle with ROMS on their mobile and at no cost, but regardless of that, it is still an extra piece of software that resides on the phone. Just the way I understand it. Again, not looking down at twrp
What do you mean by "fastboot containing all the imgs..."?
Isn't it one single image per phone model?
Or did you mean to say 'features' or 'apps'?
Personally, I d be more interested in less/apps/fancy features (except for security of course)
Click to expand...
Click to collapse
As said above, this only concerns stock roms(recovery/fastboot), not xiaomi Eu roms, whether in Zip or Fastboot, it's the same, only the installation method differs.
Unlocking the bootloader takes at least 168 hours before finalization (time to study a bit).
The latest Stable or Weekly versions are in Zip, so with TWRP.
Unlock
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html

Unfortunately, the more I read, the more I m getting kind of disappointed with things 'Xiaomi'
In order to get the unlock process started (1 week..really??), I need to download the MI drivers. OK
So I m trying to search "official" MI drivers and they are nowhere to be found!
All I get is this https://xiaomidriver.com/ which claims to host the official drivers (!)
How can this be for the image of a reputable brand?
How can Xiaomi not hosting themselves all these useful tools like all other major vendors do (in their own domain!)?
How me, as an end user, is supposed to verify authenticity of a driver found on a xyz domain claiming to be the official one?
What's more, at the bottom of this page it says "xiaomidriver.com is not endorsed or affiliated to Xiaomi..."
I mean seriously???
I purchased this phone for its hardware capabilities but is there nothing more than that?
I mean, I get Xiaomi not wanting to encourage people mess with the ROMS. After all, some will end up bricking their phone and then they ll chase up Xiaomi for this
But Xiaomi not hosting something as so very basic as a USB driver??? This can't be right
Even that official page kindly provided by NOSS8 earlier, states "ensure your PC has necessary Mi USB drivers and platform tools" Well...where am I supposed to get these from? The first random site I google up?
........
After bashing my head around this, I eventually found an official link (from miui.com), for obtaining the flash tool from which I can do a workaround to extract the drivers....c'mon!!

jstoner said:
Unfortunately, the more I read, the more I m getting kind of disappointed with things 'Xiaomi'
In order to get the unlock process started (1 week..really??), I need to download the MI drivers. OK
Click to expand...
Click to collapse
It is very simple.
The installation of the drivers is done with Mi Unlock (gear at the top right) then check:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also download platform tools which would be useful for installing TWRP or performing certain Fastboot operations.

@NOSS8 I tried installing xiaomi.eu Rom MIUI14 on the Mi 11 pro. It booted and everything but whatsapp and camera was not working. Whatsapp not syncing, camera asks for SD card?
So I decided to downgrade to MIUI 13 from Aug 2022 the version in this post above. This is what I did:
1. Fastboot TWRP latest skkk for A12.
2. Flash from TWRP last stable MIUI 13 Rom
3. Phone restarts fine but goes in to loop after connecting to wifi. Please note I have done format data before and after flash
4. I rebooted the ROM to recovery it asks for pin, then says wrong password, failed mount.
Please advise. What should I do? I am happy to toll back to MIUI13 as I am not sure what is going on with MIUI 14. How do solve this problem? Many thanks

It's better to use fastboot when doing downgrade/rollback android or Miui version .

Database Develop

welcome