Database Develop

[Q&A][ROM][6.0.1] CyanogenMod 13.0 for Xperia T, TX, V

{
"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 now void.
*
* 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.
*/
About this Q&A thread for CyanogenMod 13.0
Use this area to ask anything you want related to CM-13.0,
but try not to spam everyone, always search for an answer before.​
CyanogenMod 13.0 for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3415827
Xperia TX (Hayabusa) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3418818
Xperia V (Tsubasa) : http://forum.xda-developers.com/xperia-t-v/v-development/rom-t3416938​
General Questions & Answers
Is root access included into CM ?
Yes. Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.​
Is the ROM suited for daily usage ? Google Apps compatible too ?
Yes completely. Nightlies and OpenGApps recommended.​
Can I flash CyanogenMod NIGHTLY and UNOFFICIAL without wipes ?
Yes you can.​
Should I flash SNAPSHOT builds when I'm on NIGHTLY ?
No, the Nightlies are already more up to date.
You can flash SNAPSHOT builds when you don't want to update often.​
Is the device encryption supported ?
State unknown. If you're coming from an older ROM
please read the details here : a07afb9660a86f702066003b8e81ab63789d1660​
When USB connected to a computer, I can't access the storage ?
The phone is in charge-only mode by default on Marshmallow,
due to a stronger security logic regarding unauthorized data access.
Swipe down the notifications and change the USB mode.​
I can't access the ROM's recovery with Volume-
You can either flash the boot.img from the newer Releases with "fastboot flash boot boot.img" or FlashTool,
or follow the instructions of the TWRP Recovery installation to update from TWRP.​
Due to an unknown issue in data, the partition still looks like a 2GB
Although very unlikely, it may be possible that your data had an error
that could not be fixed automatically by the time you did the UserData Unification.
Export the resize_userdata.zip from the CM-13 zip / install / unify_userdata,
and flash it from your recovery. If it works, problem solved.​
Against advices, I upgraded without GApps and now it crashes. Any way without factory reset ?
Yes there is, but nothing assures you'll manage to do it fully & preserve all your data...
Once booted, keep saying Ok to all "Unfortunately, ... has stopped",
pull-down the notifications panel, press the Settings icon,
go in Apps, menu, Show System, scroll to Setup Wizard (green Android logo),
Permissions, and activate Contacts + Telephone.
Later, some Play Store apps may need reinstalling.
If not ok, try this : CM Wiki
If still not, then I advise a clean factory-reset reinstallation...​

Current status of each device
Xperia T (Mint) : Fully working, stable, no known major issue remaining
Xperia TX (Hayabusa) : Fully working, stable, no known major issue remaining
Xperia V (Tsubasa) : Mostly working, RIL phone issues being worked upon

Just tried flashing cm-13.0-20160711-UNOFFICIAL-hayabusa.zip from basketbuild. Everything went fine, phone goes preparing applications, then it goes starting applications and it just waited the for a long time without proceeeding. Upon reboot phone is stuck on booting animation.
In previous builds from basketbuild:
* wifi/cell/gps/compass doesn't work;
* from the start sdcard wasn't available (fixed at 06 or 05);
* screen doesn't turn off and wasn't adjusting (until 08, now it turns off);
* when phone is off instead of charge level two text strings are displayed: "Charging", "??/100".
Apart from that everything went smoothly after updating from cm 12.1 - I haven't cleaned anything. Apps are working, youtube is playing video, ads are shown in games and I can install new apps. There was one reboot while GPlay was updating YouTube.
Ready for the new builds. If I have missed anything just name it.

How was the battery life in this rom.

too soon to comment for me.. just flashed it :laugh:

moly82 said:
too soon to comment for me.. just flashed it :laugh:
Click to expand...
Click to collapse
Will you leave comment later then...

Hayabusa released, details and links added.

Dn.Thanujaya91 said:
How was the battery life in this rom.
Click to expand...
Click to collapse
I can compare by going out for ingress. On previous build of 12.1 phone survived a hour and a quarter. Now it survives a hour and a half. This can be only my imagination though so I'll try to use it in the same pattern for a week or so.
On the other hand the phone overheats. This also may be my imagination as temperature here is near 38́°C (100°F) so everything overheats easily.

Hello, and that you for taking the time to tune your rom for this phone! One small question, is it possible to repartition the device to have only one single data partition, and build the rom accordingly(meaning emulated storage?) It is one big drawback on many sony devices of that time, and separate data and sdcard partitions.

anyone here have tried MultiROM for tsubasa? can you give me instruction for install or flashing it?

You can read about MultiROM inside my Huashan Xperia SP thread for it.
I'm not releasing it until it's finished, mostly touchscreen on Hayabusa & Mint being glitchy, so use hardware keys.

I accidently flashing SuperSU through TWRP, and now Im stuck in boot?
What should I do now? Clean Flash back the ROM?

EstherTakumi said:
I accidently flashing SuperSU through TWRP, and now Im stuck in boot?
What should I do now? Clean Flash back the ROM?
Click to expand...
Click to collapse
Just boot into recovery and flash the rom again. If you don't succeed, then wipe only system, and flash cm & gapps right after, and you should be fine ( your data will be untouched).

Klaus N. said:
Just boot into recovery and flash the rom again. If you don't succeed, then wipe only system, and flash cm & gapps right after, and you should be fine ( your data will be untouched).
Click to expand...
Click to collapse
Working great now! Thank

You suggested to move discussion about bricked phones due to WhiteNeos faulty TWRP image here in Q&A.
So it seems that I ran into this issue described here: http://forum.xda-developers.com/showpost.php?p=68100827&postcount=288
This should also explain why I am now unable to flash WhiteNeos Unofficial CM 12.1 builds (getting a missing crypto-footer issue) or a stock system image with Flashtool (just displays a FAILED message without further information even in debug log mode).
I was still able to flash all other .sin files in flashmode besides the failing system one though (amss_fsg, amss_fs_1, amss_fs_2, boot, cache, cust-reset.ta, fotakernel, kernel, partition and userdata).
Afterwards I rebooted into fastboot and flashed your TWRP 3.0.2 build as boot and it actually booted to it, however TWRP-3.0.2 was unable to mount most of the partitons, it succeded in flashing CM 13 after some playing around though.
It seems that some partitions or contents are still missing though as I am still unable to flash any other ROM besides your CM 13 version with the unified data partition.
My system is currently booting into CM 13 with the unified data partition but it's pretty useless for me as I'm getting constant black screen of deaths once the screen turns off for a few seconds.
Any suggestions, logs you want or maybe raw partition dumps I could try to flash?

I got a Xperia TX running Stock 4.3 (9.2.A.1.215) to install CM13 Only I need flash twrp-3.0.2-20160814-boot-hayabusa.img via flashtool or cmd and then the CM13.zip and OpenGapps? I've already unlocked the bootloader. I was using Windows Phone/Mobile for a year, So I'm quite lost.

DanielZRK said:
I got a Xperia TX running Stock 4.3 (9.2.A.1.215) to install CM13 Only I need flash twrp-3.0.2-20160814-boot-hayabusa.img via flashtool or cmd and then the CM13.zip and OpenGapps? I've already unlocked the bootloader. I was using Windows Phone/Mobile for a year, So I'm quite lost.
Click to expand...
Click to collapse
Yes, easiest way is to just flash the latest twrp img as boot (fastboot flash boot twrpimgfile),
then from there flash CM13, follow the instructions for the unification,
and finally flash CM13 and GApps, you're all set.

markus1540 said:
You suggested to move discussion about bricked phones due to WhiteNeos faulty TWRP image here in Q&A.
So it seems that I ran into this issue described here: http://forum.xda-developers.com/showpost.php?p=68100827&postcount=288
This should also explain why I am now unable to flash WhiteNeos Unofficial CM 12.1 builds (getting a missing crypto-footer issue) or a stock system image with Flashtool (just displays a FAILED message without further information even in debug log mode).
I was still able to flash all other .sin files in flashmode besides the failing system one though (amss_fsg, amss_fs_1, amss_fs_2, boot, cache, cust-reset.ta, fotakernel, kernel, partition and userdata).
Afterwards I rebooted into fastboot and flashed your TWRP 3.0.2 build as boot and it actually booted to it, however TWRP-3.0.2 was unable to mount most of the partitons, it succeded in flashing CM 13 after some playing around though.
It seems that some partitions or contents are still missing though as I am still unable to flash any other ROM besides your CM 13 version with the unified data partition.
My system is currently booting into CM 13 with the unified data partition but it's pretty useless for me as I'm getting constant black screen of deaths once the screen turns off for a few seconds.
Any suggestions, logs you want or maybe raw partition dumps I could try to flash?
Click to expand...
Click to collapse
When I flashed CM13 and CM14 I also had constant black screens and phone shut down randomly.
And because I wanted to prove to myself that these are not hardware faults I reverted to stock rom.
I flashed FTF image with Flashtool. I had to use older flashtool version as the latest couldn't finish the process and broke with errors.
Flashtool 0.9.18.6 did the job for me
Stock firmwares - http://forum.xda-developers.com/showthread.php?t=2648320
Initially it worked flawlessly but then, around 50% battery level, to my dissapointment random black screens of death happened again.
So it is either hardware fault, or something get messed while flashing the different ROM builds.

Hi there,
seems to me but 19 sept. update cm13 nightlies tree is not installing, crashing right after the recovery reports update started.
Anybody else?
Late edit.
Just realised somehow twrp was gone... reflashed it in fastboot mode, now everything is cool.
Thanks Adrian

It seems, that even the annoying behavior of the touchscreen in recovery will be fixed with the next nightly
@Adrian DC
You're really outstanding :good::good::good:

[ROM][UNOFFICIAL][9.0][tb8504f/x] LineageOS 16.0 for Lenovo TAB4 8

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), which is designed to increase performance and reliability over stock Android for your device.
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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera
Audio
FM radio
WLAN and USB tethering
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8504, https://github.com/lenovo-devs/android_device_lenovo_tb-common/tree/lineage-16.0-msm8937
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-tb8504
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo/tree/lineage-16.0-msm8937
2020-03-19
Fixed USB flash mounting when using OTG
mailru: lineage-16.0-20200319-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200319-UNOFFICIAL-TB8504.zip
Previous versions:
2020-03-13
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
mailru: lineage-16.0-20200313-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200313-UNOFFICIAL-TB8504.zip
2020-03-04
first release
mailru: lineage-16.0-20200304-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200304-UNOFFICIAL-TB8504.zip
How to install
You have to had TWRP installed from this thread TWRP and ROOT for Tab 4 8/10 (Plus) (TB-8704X/F/V,TB-X704L/F, TB-8504X/F, TB-X304L/F or one from link below
In TWRP clean Data if you coming from stock ROM and do Install of this ROM. If you have android 8 stock rom installed you have to format Data with data loss, because used encryption is incompatible with android 7.1
TWRP
Built from omnirom android 9.0 source (twrp 3.3.1), includes same kernel as Lineage build, with support for pstore (kernel logs after crash), exfat, ntfs, reboot to EDL mode.
mailru: twrp-3.3.1-1-TB8504.img
gdrive: twrp-3.3.1-1-TB8504.img
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][tb8504f/x] LineageOS 16.0 for Lenovo TAB4 8, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-tb8504
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2020-03-04
Last Updated 2020-03-19

hero - thank you

Can this be installed on my 8704v?

jcthrower said:
Can this be installed on my 8704v?
Click to expand...
Click to collapse
No, it is only for 8504, it has different SOC.
Update here
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing

highwaystar_ru said:
No, it is only for 8504, it has different SOC.
Update here
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
Click to expand...
Click to collapse
ok thanks for the response. Are you still planning on updating Lineage 16.1 for the 8704v?

Thank you so much for that rom, I'll be trying to flash it next week!
I have question - is there any possibility to get working stock Dolby atmos which is different from that one we can find in other threads
Or
You prefer Viper4android?
Edit: does Netflix work fluently?

Thanks a lot!
Installation went smooth, so far everything seems to be working.
Still need to set up the tab, but I'm glad I finally got rid of the Lenovo bloatware (like kidoz).
Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.

Update:
2020-03-19
Fixed USB flash drives mounting connected by OTG

Lucinde said:
Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.
Click to expand...
Click to collapse
If anyone else would have the same question: I found a workaround. You can create a new user via adb with the command "adb shell pm create-user --restricted <username>".
I didn't find a way to create the restricted profile from the settings menu, but once created, it can be managed via the menu.
In the meantime I installed some apps and so far, so good. From the limited time I worked with it, it seems to run smoother than with the stock ROM :good:

Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088

Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088

Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088

Thank you @Plant
I have never been trying to restore using fastboot commands, only by twrp.
The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot
Code:
fastboot format data
but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.
In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...
Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.
Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!

Managed to install Lineage on my TB-8504F, but it doesnt get past the Lineage boot animation, no matter how long I leave it.
Pushed TWRP to Recovery, formatted as required. Had to amend the Lineage image to remove the device checks, as although I definately have TB-8504F, it didnt like that TWRP reported it as TB_8504f - ?
Installed and installed GAPPS, cant get past load screen.
I do have a backup, so not concerned, but frustrated!
Any help appreciated

BigBrother84 said:
Thank you @Plant
I have never been trying to restore using fastboot commands, only by twrp.
The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot
Code:
fastboot format data
but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.
In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...
Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.
Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!
Click to expand...
Click to collapse
Sorry it took me so long to see this, but I had similar problems as you initially. It turns out you actually have to install TWRP to the tablet for it to mount /system properly, booting into it from fastboot doesn't work for some reason - that was what fixed it for me at least. It may be different for your device but I had to run the flash recovery command twice for it to stick..
Also want to say thanks to highwaystar_ru, the past few builds have been running great

Slack3r said:
It turns out you actually have to install TWRP to the tablet for it to mount /system properly
Click to expand...
Click to collapse
Thank you for that important information!
You suggest it may work on my tb-8504f If I install twrp using:
Code:
fastboot flash recovery PATCHTO/twrp.3.x.x.img
After that am I able to boot into twrp using
Code:
fastboot reboot recovery
or buttons combination? Hmh i tried to install TWRP using booted TWRP but stock recovery was booting instead of it. Strange...
Ok so let's imagine theoretically that I did it, but my problems aren't ending on it, I have to modify script installing LOS as @Plant said. (TWRP ERROR 7 - your device is tb_8504f zip is for tb-8504f)
With all that steps you think it may work?
OK, so let's imagine theoretically that it crashed one more time (why not). Am I able to restore everything with twrp installed if I will twrp backup all partitions? Or just reflash everything using MiFlash. Will fastboot flash recovery, modify device recovery permanently? Does MiFlash restores stock recovery? (what is the name of .img that I have to find into system package. Something like recovery.img)? Am I able to unzip just that file, or backup it using some fastboot command and transfer it to my computer?
Thank you for caring!

BigBrother84 said:
Thank you for that important information!
You suggest it may work on my tb-8504f If I install twrp using:
Code:
fastboot flash recovery PATCHTO/twrp.3.x.x.img
After that am I able to boot into twrp using
Code:
fastboot reboot recovery
or buttons combination? Hmh i tried to install TWRP using booted TWRP but stock recovery was booting instead of it. Strange...
Ok so let's imagine theoretically that I did it, but my problems aren't ending on it, I have to modify script installing LOS as @Plant said. (TWRP ERROR 7 - your device is tb_8504f zip is for tb-8504f)
With all that steps you think it may work?
OK, so let's imagine theoretically that it crashed one more time (why not). Am I able to restore everything with twrp installed if I will twrp backup all partitions? Or just reflash everything using MiFlash. Will fastboot flash recovery, modify device recovery permanently? Does MiFlash restores stock recovery? (what is the name of .img that I have to find into system package. Something like recovery.img)? Am I able to unzip just that file, or backup it using some fastboot command and transfer it to my computer?
Thank you for caring!
Click to expand...
Click to collapse
Yep, you'd need to flash TWRP via that fastboot command and boot to recovery by holding vol up/power. I put the ROM and gapps files on a MicroSD card which was picked up by TWRP.
I had similar problems with the ROM not being compatible after the first failed flash, you should be able to modify the updater-script file located at META-INF\com\google\android to include "tb_8504" as a compatible device. I didn't test this method however, as I reflashed the stock image which combined with installing TWRP on the device solved my issues.
If you need to, the full stock image can be flashed using QFIL and the instructions from here, but I'd recommend trying to restore the backup posted by Plant as the QFIL method can take some time to get figured out. I'm not sure how this compares to MiFlash but that would likely produce the same results.
Hope this helps!

screen rotation
Does anybody have problem with auto rotation for screen? In mine TB-8504F it doesn't work. Installed some apps which are testing sensors and none sensor responsible for screen rotation is vsible after flashing this system.
---------- Post added at 04:43 AM ---------- Previous post was at 04:24 AM ----------
If you will brick your device as me you can always use Qualcomm Flash Image Loader (QFIL) with proper files for your device. Note for mine works QFIL v2.0.0.1. Newer versions won't work with my device. It will load stock android 7 then under TWRP you can wipe and flash Lineageos. Firstly was bricked while was going from And 8.0 and not flashed but only booted TWRP. As mentioned above need to flash TWRP

I tried restoring the backup, but after I tried booting into system I got a black screen I can't fix. Power buttons don't work, I can't boot into recovery / anything else. No logos or text. It's like the battery is dead, but I can't power it on. Tried charging it, because the battery was around 10% when I tried restoring the backup, but I don't think that will help. Any other ideas? I think I lost this device for good.

Hi,
After coming from stock 8.0, I’ve got everything up and running which appears to run great.
However, I am struggling to get my PS4 controller working.
It will connect fine via Bluetooth, but no input is detected.
Any ideas?

[ROM][UNOFFICIAL][10.0][CPH1859/CPH1861] Pixel Experience and Plus [AOSP][06/06/2020]

{
"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"
}
Pixel Experience and Plus for Realme 1
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation).
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device.
What's working:
1. Boots
2. RIL(Calls,SMS,Data)
3. Wi-Fi
4. Bluetooth
5. Camera
6. Audio
7. Sensors
8. Flash
9. Brightness
10. GPS
11. Gcam (Dont download from Play Store, it wont work)
12. Hotspot
13. USB Tethering
14. DT2W
15. Face Unlock
Known issues:
1. Selinux is permissive.
2. Video codec issues in all Chromium based browser. Check 4th post for fix.
3. VoLTE.
Before Flashing:
1. Take a backup of your data.
2. Clean flash is recommended as of now.
3. Flash the shared TWRP only.
4. Always download latest build.
5. TWRP downloads (alternative one) and flashing instructions can be found in this git link.
6. Always read 2nd and 3rd posts.
Installation Instructions:
1. Clean Flash is recommended, Install TWRP and enter into it.
2. Wipe Dalvik, Cache, System, Data, Internal Storage.
3. Reboot to TWRP.
4. Flash Pixel Experience or Pixel Experience Plus ROM (Gapps are included).
5. Flash Magisk (v20.3 is recommended and is optional).
6. Wipe Cache and Dalvik after flashing.
7. Reboot to system and first boot will take time.
8. Done, you are in Pixel Experience or Pixel Experience Plus ROM and njoy.
Note:
1. In our testing only few versions of Magisk are working. So use the shared one only.
2. Working magisk versions:
Original - 20.1 and 20.3
Phh based - 20.3
3. Dont update magisk (you can update app though).
4. Use the shared TWRP only and dont use others (testings are based on the shared TWRP).
5. ROM is now stable for daily use, enjoy.
Downloads:
Pixel Experience (discontinued)
Pixel Experience Plus​
Pixel Experience: 10
Pixel Experience Plus: 10+
Security Patch Level: August 2020
Build Author: Naveen56
ROM Source Code: https://github.com/PixelExperience
Device Tree: https://github.com/CPH1859/Pixel_Experience_and_Plus
Kernel Source Code: https://github.com/CPH1859/android_kernel_oppo_mt6771
Information
[STABLE][ROM][10.0]Pixel Experience 10 and 10+, ROMs for Realme 1 [CPH1859/61]
Contributors:
1. Invincible-Venom
2. Naveen56
3. Phhusson
4. SamarV-121
5. vishalk17
Credits:
1. mmoreyrav
2. GSI Community
Testers:
1. venombiceps
2. Vijay996
3. MpS005
4. eldraco19
5. ahmadfahim0123
6. Mohit619
Thanks to:
1. Realme and Oppo,
2. Google and Android,
3. Lineage OS, Pixel Experience and other open source ROM developers,
4. XDA Developers.
ROM OS Version: Android 10
ROM Kernel: Linux 4.4.159
ROM Firmware Required: C.49 (Latest Version)
Based On: AOSP
Version Information:
Status: Stable
Release Date: 12-07-2020
Created: 12-07-2020
Last Updated: 16-08-2020

CHANGELOG:
Code:
16/08/2020
1. August Patch
2. Added OnePlus Screen Recorder
3. Added Face Unlock
4. Kernel up-streamed to 4.4.159
5. All changes of PE+ for the month of August.
Code:
13/07/2020
1. Fixed offline charging animation
2. July Patch.
Code:
06/06/2020
1. Initial Release.

Get into this link for some workarounds to the issues you are facing in all Realme 1 ROMs.
Pixel Experience is discontinued and PE+ will be continued. If you are still interested then you can use tress to update it monthly.

Thanks @Naveen56 for the support! Also add some screenshots

Any information regarding JIO VOLTE
I know that Volte might not be possible ever in realme 1. But JIOCALL app is also not working in any of the custom rom. I really want to use this rom , but the only thing stopping me is that my sms/calls will not work. Can you please share any info if you have to make jiocall app work..
---------- Post added at 08:15 AM ---------- Previous post was at 08:10 AM ----------
Somehow i got jiocall app working, and the sim was also registered and status was connected. But i am still not getting any calls/sms. And if i try to call, it says "use your default dialer, your device is already volte"."JioCall App should only be used to make rich calls". This means i can only call to the person who is using jiocall app.

Awesome work!

issues , fedbaack and question
sometimes some apps crash like whatsapp And is there OTA updates? and if there isnt

Zainullahk said:
sometimes some apps crash like whatsapp And is there OTA updates? and if there isnt
Click to expand...
Click to collapse
Are you using 15th August build?

MpS005 said:
Are you using 15th August build?
Click to expand...
Click to collapse
yes is there ota?

Zainullahk said:
yes is there ota?
Click to expand...
Click to collapse
15th build is the latest build for Pixel Experience. Did you try clean flashing rom again?
And OTA doesn't work in any rom as of now. Even if you get OTA in any rom (Bliss), then do not install it.

Can I update Google play patch?

zainullahk1 said:
Can I update Google play patch?
Click to expand...
Click to collapse
Yes, you can do Google Play System (Security) updates

Urgent!!!!
i clicked reset in pixel expierince and now i cant boot into my os it keeps booting into twrp i tried re flashing didnt work i tried this https://forum.xda-developers.com/lg-g5/how-to/android-booting-twrp-recovery-t3572200 it says conv disabled how do i enable conv!!

Zainullahk said:
i clicked reset in pixel expierince and now i cant boot into my os it keeps booting into twrp i tried re flashing didnt work i tried this https://forum.xda-developers.com/lg-g5/how-to/android-booting-twrp-recovery-t3572200 it says conv disabled how do i enable conv!!
Click to expand...
Click to collapse
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.

Just wanted to say how awesome this is.
Hey, I used the rom and it worked as intended and it was an awesome experience. Gotta say, you guys know your stuff. I am in love with the pixel experience plus as the bundle makes it very easy to flash and it works almost flawlessly(except for, of course VoLTE, @MpS005 user - https://forum.xda-developers.com/member.php?u=9393824 told me that the source for cellular network is closed in mediatek chips so it is really hard to activate VoLTE) but I love the ROM anyways and I must commend your hard work. Just want to say keep it up and I'll be waiting for when you guys crack the VoLTE problem. I am so in love with pixel experience that my next phone sure is going to be a pixel.

Naveen56 said:
Naveen56 said:
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.
Click to expand...
Click to collapse
sir me too got stuck in such kind of situation i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my hear....please share me the links
Click to expand...
Click to collapse

i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my heart...please share me the links

Naveen56 said:
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.
Click to expand...
Click to collapse
as a devloper you have to add this as a marked,this error as a priority for those who is flashing this rom now m getting twrp looping i even tried toflash other custom rom using recovery but that doesnt help me out seems now i have to flash ozip file please help

vishalv.vv469 said:
i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my heart...please share me the links
Click to expand...
Click to collapse
I feel sorry for that. You need to flash stock ROM through twrp. Then boot into stock ROM. And from here you can proceed to flash custom ROM. Anyway I don't recommend flashing this ROM now as it has no VoLTE and is outdated. Try other ROM that have VoLTE.

vishalv.vv469 said:
as a devloper you have to add this as a marked,this error as a priority for those who is flashing this rom now m getting twrp looping i even tried toflash other custom rom using recovery but that doesnt help me out seems now i have to flash ozip file please help
Click to expand...
Click to collapse
Yes, you have to flash Ozip and please check the twrp you flashed has this feature of flashing ozip and also leave some 3GB storage in the memory card as ozip has to be decrypted to zip.

[ROM][12][OOS CAM] CherishOS 3.4 for OnePlus 8T [OFFICIAL][2022-02-16]

{
"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"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH(for first install) :​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System
2nd Method(Using Sideload):
Note: You can't sideload with any recoveries, only some recoveries support sideloading this rom. I have provided one below
1. Download ROM zip from sourceforge and put it in adb folder
2. Download recovery.img from here
2. Put it in the folder where you have your adb files, and then open a terminal and execute the command
Code:
fastboot flash recovery recovery.img
3. Reboot to recovery
4. Choose "Apply update"
5.
Code:
adb sideload rom.zip
6. Reboot to recovery
7. Factory reset / Wipe all data
8. Reboot system
Dirty Flash(to update):​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Reboot to System
2nd Method(Using Sideload):
1. Download ROM zip from sourceforge and put it in adb folder
2. Reboot to recovery
3. Choose "Apply update"
4.
Code:
adb sideload rom.zip
5. Reboot to recovery
6. Reboot system
Download ROM(Gapps)
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
- @1249131356
- @chandu dyavanapelli
- Others who I forgot to mention
Based on Android 12.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me? (none)
Cherish-OS Source
Kernel Source
Telegram Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
​CherishOS for OnePlus 8T
Device: kebab
Maintainer: @Amsal1
Build Type: Official
ROM Kernel: Linux 4.19.225
Based On: AOSP
Android OS version: 12
Security patch level: January 2022
Version Information:
Status: Stable
Current Stable Version: 3.3.5
SELinux Status: Enforcing

Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!

Reserved

Amsal1 said:
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!
Click to expand...
Click to collapse
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why

Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake

Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use

Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing

Zekedw said:
Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use
Click to expand...
Click to collapse
The main thing you need to know for this device regarding A/B is that you need to have the latest firmware from Oneplus on both slots.
Run all your updates and then find the Lineage Wiki for kebab. There is a script there that will copy firmware to both slots so you can start flashing ROMs.

Zekedw said:
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing
Click to expand...
Click to collapse
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.

kjslabber said:
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.
Click to expand...
Click to collapse
I have actually repaired it from a boot loop many times. I've been modding and flashing for many years. It's just that this is my first a/b device and despite all the tutorials and research I've done it still hasn't worked. I'm not giving up tho, just wondering what I'm missing. I actually did get a couple roms to work. But I don't know why I'm not getting them to work now. More research I guess...

double tap to wake works while aod is on?

I have many problems trying to install these roms on my phone using sideload or twrp no matter what recovery I use. End up dumping files from payload bin and flashing individual files using fastbootd. Only handful of files to flash, not like oos rom. Almost foolproof. Just make sure you reboot to recovery and format data before booting to system.

GbnrVR said:
Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake
Click to expand...
Click to collapse
No. I mistakenly wrote face unlock in a hurry which is removed from OP now

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Yes. That is because A12 latest standards uses a different assert verification process (which is used to detect the device before loading packages into the recovery). TWRP and old recoveries are still using old asserts from A11 standards. I don't like to implement the old assert thus you can either flash using any fastboot installer script or fastboot enhanced. One tester confirmed me that lineage recovery also worked fine for him but I still recommend fastboot installer mode.

Muntasir Mahmud Saif said:
double tap to wake works while aod is on?
Click to expand...
Click to collapse
Yes.

Ivanherrero said:
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why
Click to expand...
Click to collapse
Have you tried changing monet colour through Cherish Settings->Themes->Custom Color?
Can you give more details, since I can't reproduce the issue and many of my testers have tested it for days and have no issues with changing monet colours.

Amsal1 said:
Yes.
Click to expand...
Click to collapse
can not find any payload.bin in the folders after extracting

All you need to do is change wallpaper. Color is controlled by wallpaper theme in a12.

Muntasir Mahmud Saif said:
can not find any payload.bin in the folders after extracting
Click to expand...
Click to collapse
Did you download the zip file or md5?

How To Guide [GUIDE]Xiaomi.EU ROMs Flashing Guide All Devices [Windows-Only]

XIAOMI.EU ROMs Flashing Guide:
MIUI 13 (Stable)
{
"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"
}
Requirements:
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers, android bootloader interface and click install.
Then go to your custom rom download thread and check the date of rom file.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of c: drive and connect your device to fastboot mode and double click on flash_all.bat
A cmd window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Follow flashing guide of twrp from here.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the.eu rom zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select eu rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to system.
Done.
Updating via Updater app: (ROM Type: Recovery)
(A Xiaomi.eu ROM must already be installed on your device)
Download Xiaomi.eu ROM zip file
Copy the ROM zip file to the internal storage
Updater -> Menu (...) -> Select update package
Select the ROM zip file
Confirm any dialogs
Done!
Installing with Fastboot: (ROM Type: Fastboot)
Download Xiaomi.eu ROM zip file
Extract the ROM zip to root of c : drive.
Connect phone ins fastboot to PC via USB cable
Run one of the installation scripts (according to your PC operating system):
- first_install_with_data_format - with data wipe, if you're flashing Xiaomi.eu ROM for the first time or downgrading.
- update_rom - without data wipe, if you're updating from an older Xiaomi.eu ROM.
Done!
Remember:
If you are going from MIUI 13 (or later) Weekly ROM to MIUI 13 Stable ROM, you are doing a downgrade, so format data is mandatory!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
MIUI 13 (Weekly)
Go to the sourceforge link of the rom and see the date of your rom. In this case it's alioth.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of c: drive and connect your device to fastboot mode and double click on flash_all.bat
A cmd window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Follow flashing guide of twrp from here.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to recovery.
Reboot to system.
Done.
Fastboot:
Unzip rom file to root of c: drive.
Go into folder.
Run fastboot installation script in folder according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
Done.
NOTE FOR ALL:
Make sure to always extract and move the stock rom folder in root of c: drive (this helps avoid flashing errors)The path should look something like this:
C:\spes_global_images_YourVersionhere
Also make sure the same to unzip xiaomi.eu rom folder in the root of c: drive:
C:\xiaomi.eu_multi_HMNote11_YourVersionHere
Then flash Xiaomi.EU according to instructions above.
Alternatively If you want you can flash india , eea , turkey , etc variants of stock rom instead of global , then flash xiaomi.eu according to the instructions above. But keep in mind that the release date of stock rom that you are flashing should be closest to the release date of xiaomi.eu weekly rom.
Must do all the process again if flashing a new rom
If you get a error like this: assert failed _dynamic partitions package_extract_file(dynamic_partitions_op_list) ERROR 1
Then go to the guide here and re do all the steps in the guide and when it comes to flashing twrp, then use twrp 3.6.1 to flash rom then flash twrp 3.7.0 according to the process in guide (if the rom you flashed is a12/a13) or use shrp 3.1 instead of using twrp after re doing all the steps and then flash rom.
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can cause problems such as reboots, apps crashing,etc as recovery is integrated into boot partition in which kernel is also integrated.

Hybrid ROMs: The End of Recovery/Fastboot ROMs
During this Chinese New Year holidays break from building ROMs, we could put some time into research and have developed a new format for our ROMs. We are proud to announce the Hybrid ROMs. Why "Hybrid"? Well, because those ROMs are both Recovery ROMs and Fastboot ROMs, all in the same package...
xiaomi.eu

NOSS8 said:
Hybrid ROMs: The End of Recovery/Fastboot ROMs
During this Chinese New Year holidays break from building ROMs, we could put some time into research and have developed a new format for our ROMs. We are proud to announce the Hybrid ROMs. Why "Hybrid"? Well, because those ROMs are both Recovery ROMs and Fastboot ROMs, all in the same package...
xiaomi.eu
View attachment 5820261
Click to expand...
Click to collapse
Updated ! Thanks !

what is your experience after flashing the ROM. The system eats 18GB of space (is this normal or just my phone?) and I don't know why and even though a lot of spam is going away with this rom there is a lot more

wasteoinc said:
what is your experience after flashing the ROM. The system eats 18GB of space (is this normal or just my phone?) and I don't know why and even though a lot of spam is going away with this rom there is a lot more
Click to expand...
Click to collapse
Did you do a clean flash?

NOSS8 said:
Did you do a clean flash?
Click to expand...
Click to collapse
I think I did, the phone was new and I did a fastboot install of the xiaomi.eu rom
But all this a/b system I don't pretend I get it much

wasteoinc said:
I think I did, the phone was new and I did a fastboot install of the xiaomi.eu rom
But all this a/b system I don't pretend I get it much
Click to expand...
Click to collapse
So you used first install.bat.
I don't have this device but on my 12 pro the system takes 13GB (Xiaomi Eu rom).

Does anybody have a lag issue in the control center? 90Hz feels like 60Hz

NOSS8 said:
Hybrid ROMs: The End of Recovery/Fastboot ROMs
During this Chinese New Year holidays break from building ROMs, we could put some time into research and have developed a new format for our ROMs. We are proud to announce the Hybrid ROMs. Why "Hybrid"? Well, because those ROMs are both Recovery ROMs and Fastboot ROMs, all in the same package...
xiaomi.eu
View attachment 5820261
Click to expand...
Click to collapse
Big woop. I don't want stock MIUI crapola. The whole point of XDA is better choices, not encouragement to return to the stock, bloated, ad-engorged OG software. The whole reason to buy a Snapdragon'd phone is ROMing. This will not make me go back.
EDIT: changed supposed stock MIUI users on XDA (everyone) to proven (me).

Sheist! said:
Big woop. No one, including me, wants stock MIUI crapola. The whole point of XDA is better choices, not encouragement to return to the stock, bloated, ad-engorged OG software. The whole reason to buy a Snapdragon'd phone is ROMing. This will not make me go back.
Click to expand...
Click to collapse
This is your opinion but not that of the 781 users of this version, for example.

Sheist! said:
Big woop. I don't want stock MIUI crapola. The whole point of XDA is better choices, not encouragement to return to the stock, bloated, ad-engorged OG software. The whole reason to buy a Snapdragon'd phone is ROMing. This will not make me go back.
EDIT: changed supposed stock MIUI users on XDA (everyone) to proven (me).
Click to expand...
Click to collapse
I also don't want the xiaomi crap but I also want to use my phone in a usefull way, not having to deal with all the issues other roms introduces.
In my old phone (xiaomi 4x) the miui.eu rom was quite good and you could improve on it by deleting xiaomi system apps that you didn't want to use. I don't know whats the story now, but Im trying to learn.
Somebody said that the A/B partitioning scheme bloats the GB in the system but still 18 seems a lot to me.
Im still a bit scared to flash magisk which is annoying because i really want to root my phone to get rid of ads and stuff

wasteoinc said:
I also don't want the xiaomi crap but I also want to use my phone in a usefull way, not having to deal with all the issues other roms introduces.
In my old phone (xiaomi 4x) the miui.eu rom was quite good and you could improve on it by deleting xiaomi system apps that you didn't want to use. I don't know whats the story now, but Im trying to learn.
Somebody said that the A/B partitioning scheme bloats the GB in the system but still 18 seems a lot to me.
Im still a bit scared to flash magisk which is annoying because i really want to root my phone to get rid of ads and stuff
Click to expand...
Click to collapse
Why are you scared to flash magisk ?
Btw , are you getting issues in which your device randomly reboots (with animation) sometimes and apps crash unnecessarily ?
I have no nfc Indian 6 64 variant and I get this issue in all .eu roms for my device .
These issues are nowhere to be found in other custom roms .

wasteoinc said:
I also don't want the xiaomi crap but I also want to use my phone in a usefull way, not having to deal with all the issues other roms introduces.
In my old phone (xiaomi 4x) the miui.eu rom was quite good and you could improve on it by deleting xiaomi system apps that you didn't want to use. I don't know whats the story now, but Im trying to learn.
Somebody said that the A/B partitioning scheme bloats the GB in the system but still 18 seems a lot to me.
Im still a bit scared to flash magisk which is annoying because i really want to root my phone to get rid of ads and stuff
Click to expand...
Click to collapse
Where are you getting ads

wasteoinc said:
I also don't want the xiaomi crap but I also want to use my phone in a usefull way, not having to deal with all the issues other roms introduces.
In my old phone (xiaomi 4x) the miui.eu rom was quite good and you could improve on it by deleting xiaomi system apps that you didn't want to use. I don't know whats the story now, but Im trying to learn.
Somebody said that the A/B partitioning scheme bloats the GB in the system but still 18 seems a lot to me.
Im still a bit scared to flash magisk which is annoying because i really want to root my phone to get rid of ads and stuff
Click to expand...
Click to collapse
Magisk installs a bit funky with the RN11 since I stayed on the crDroid recovery. I recall I had to do the adb sideload method. Go under the Add Update section. You still need the boot.img and vbmeta.img from your installed ROM.

Sheist! said:
Magisk installs a bit funky with the RN11 since I stayed on the crDroid recovery. I recall I had to do the adb sideload method. Go under the Add Update section. You still need the boot.img and vbmeta.img from your installed ROM.
Click to expand...
Click to collapse
You could have chosen apply update chosen your SD card then flashed magisk.zip

LolFlasherNoob said:
You could have chosen apply update chosen your SD card then flashed magisk.zip
Click to expand...
Click to collapse
Actually, the recovery would not recognize the external SD. Nothing changed on it. I did freak a bit until the sideload worked from PC. Still won't read it in the stock crDroid 9.2 recovery but every other place it does.
Edit: it is just the recovery that fails to read it. Apps within system read it fine, and it mounts. "unsupported filesystem exfat" as seen in recovery. I did not format in exfat, though.

LolFlasherNoob said:
...
Btw , are you getting issues in which your device randomly reboots (with animation) sometimes and apps crash unnecessarily ?
I have no nfc Indian 6 64 variant and I get this issue in all .eu roms for my device .
These issues are nowhere to be found in other custom roms .
Click to expand...
Click to collapse
No I had no such issues , I have the version with NFC. I finally got magisk and adaware so now I will cool a bit before trying something different. LineageOS seems not supported anymore and from the other custom roms still not sure if you get more issues than miui.eu