Database Develop

[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?

Does patched boot.img Magisk work on MIUI V12.5.1.0? (Edit: Yes it does!)

Just curious if anyone has any insight as to whether I can use the Magisk app to patch the newest boot.img (12.5.1.0 global / Android 11 / mi9t pro) and whether it will go smoothly if I install it via fastboot flash boot patchedmagiskhere.img?
I just updated the device using the clean_all mode on MiFlash and everything looks to be working fine;
No TWRP or custom recovery installed
Bootloader in unlocked state
As the update is so new I just wanted to check if anyone had any experience before I go ahead. There's also the old method of flashing magisk as a .zip via TWRP which is now 'depreciated'. As the device says 'Ramdisk NO' it implies Magisk may need to be used in 'recovery mode' (i.e. patched recovery.img and vol+power on every boot) but it worked just fine in MIUI11 so I don't think that's right.
Update: If you've come here looking to find out how to do this then I added instructions in this post.

Can't find answers so I might try fastboot boot patched_magisk.img later today. In theory this'll let me test a patched boot.img instead of going in blind with fastboot flash boot patched_magisk.img so that the boot.img isn't flashed, just booted. If it works I assume I can probably just select Direct Install in Magisk.

droident said:
Can't find answers so I might try fastboot boot patched_magisk.img later today. In theory this'll let me test a patched boot.img instead of going in blind with fastboot flash boot patched_magisk.img so that the boot.img isn't flashed, just booted. If it works I assume I can probably just select Direct Install in Magisk.
Click to expand...
Click to collapse
Hey let me know if you find a solution for this.
I upgarded to this version via TWRP last night. Tried flashing Magisk via TWRP and it kept boot looping into TWRP.
Had to re-flash the rom again in order to boot into the system.
I tried patching the stock recovery image but couldn't get the system to boot into Magisk mode. Tried the Volume Up + Power and let go on splash screen combo but it kept going to stock recovery.
Any help would be appreciated. I'll go crazy having to use the phone without root.
Update: I tried what you mentioned. Manually booting patched boot image. No luck. After showing the MIUI logo for a long time it goes back to recovery. I guess it's basically the same as flashing via TWRP.

shajman said:
Hey let me know if you find a solution for this.
I upgarded to this version via TWRP last night. Tried flashing Magisk via TWRP and it kept boot looping into TWRP.
Had to re-flash the rom again in order to boot into the system.
I tried patching the stock recovery image but couldn't get the system to boot into Magisk mode. Tried the Volume Up + Power and let go on splash screen combo but it kept going to stock recovery.
Any help would be appreciated. I'll go crazy having to use the phone without root.
Click to expand...
Click to collapse
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock firmware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)

zgfg said:
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock formware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
Click to expand...
Click to collapse
This is what I have always done (patching boot). However it does not seem to be working with v12.5.1.0
I've just tried the Canary build of Magisk as well and no luck. The MIUI splash screen stays on for a while and then it goes to Recovery.
This never happened with any of the previous ROMS (Android 10)
Not sure if I'm doing something wrong.

shajman said:
This is what I have always done (patching boot). However it does not seem to be working with v12.5.1.0
I've just tried the Canary build of Magisk as well and no luck. The MIUI splash screen stays on for a while and then it goes to Recovery.
This never happened with any of the previous ROMS (Android 10)
Not sure if I'm doing something wrong.
Click to expand...
Click to collapse
You may have modules installed and enabled, that do no more work with the new firmware
If you didn't wipe/format Data, modules are still in: /data/adb/modules
(updating firmware does not affect there)
Use TWRP, go to that folder and add an empty file named: disable
(exactly as that), to each subfolder (each subfolder corresponds to one module, you may recignize them by folder names)
Then reboot with the patched boot.img
Later, manage your modules (enable, uninstall, update) from Magisk app (once you successfully boot to Magisk)

zgfg said:
You may have modules installed and enabled, that do no more work with the new firmware
If you didn't wipe/format Data, modules are still in: /data/adb/modules
(updating firmware does not affect there)
Use TWRP, go to that folder and add an empty file named: disable
(exactly as that), to each subfolder (each subfolder corresponds to one module, you may recignize them by folder names)
Then reboot with the patched boot.img
Later, manage your modules (enable, uninstall, update) from Magisk app (once you successfully boot to Magisk)
Click to expand...
Click to collapse
You Sir are an absolute LIFE SAVER!!!!!!!
Thank you!

I also patched magisk just fine . Thanks guys for sharing your experiences; it kinda reassured me it'd probably work - I was thinking booting a patched magisk boot.img might be safer so I did that first and it booted as expected. So I just returned to fastboot and flashed it properly. Installed a few modules (the essentials; ACC, Energized, Busybox), rebooted, we're all good ^_^
{
"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"
}
I think it's already been explained above me but for anyone who hasn't figured it out yet:
Find the recovery zip or fastboot files you updated with (if you don't have them still then go here but use the *exact* region and version - if your device isn't raphael then don't use these), open with 7zip/winrar/whatever and copy the boot.img from them to any folder on your phone. Open Magisk Manager, browse for where you copied it to and patch it; recovery mode box unticked. Then look for Magisk_patched_xxx.img (xxx part being whatever Magisk called it) in your /Downloads folder on your phone. Copy it back to your PC, fire up Tiny ADB & Fastboot.
Do a test-run with fastboot boot Magisk_patched_xxx.img first. If it boots up fine and Magisk shows as working, commit the changes by returning to fastboot with adb reboot fastboot and then the command fastboot flash boot Magisk_patched_xxx.img. Then power it up.
If the temporary boot test-run didn't work, obviously don't execute the flash boot command; power-cycling the phone will get it unstuck.
I should probably note I don't have TWRP (using stock recovery) and I don't know how that factors into this. This was done the day after a clean_all fastboot flash; read previous posts if you've used Magisk previously and updated with your data intact.

I would like to add here to use the boot.img patch method. Flashing magisk as a zip through the recovery will cause a bootloop.
Tested this on my Mi 9T Pro (12.5.1 global) with system encryption enabled.

FPSUsername said:
I would like to add here to use the boot.img patch method. Flashing magisk as a zip through the recovery will cause a bootloop.
Tested this on my Mi 9T Pro (12.5.1 global) with system encryption enabled.
Click to expand...
Click to collapse
I was tempted to do the same because it's the conventional way of installing Magisk and it's how it's always been installed.
That and mucking with something called boot.img sounds like a one-way trip to brick-street. I.e. boot.img makes me think bootloader or in other words, bad news. Although from what I've heard it turns out you can completely screw up the boot.img and you should still have access fastboot and recovery modes. But I didn't run into any problems flashing a new boot.img so I didn't find out .

droident said:
I was tempted to do the same because it's the conventional way of installing Magisk and it's how it's always been installed.
That and mucking with something called boot.img sounds like a one-way trip to brick-street. I.e. boot.img makes me think bootloader or in other words, bad news. Although from what I've heard it turns out you can completely screw up the boot.img and you should still have access fastboot and recovery modes. But I didn't run into any problems flashing a new boot.img so I didn't find out .
Click to expand...
Click to collapse
Men, patching the images is nothing new or exotic.
If you ever read Magisk guide from TJW (the aurhor of Magisk) you would well know that the method has been described there for many years (I personally used the method back since 2018 on other phones)
Besides, it has many practical advantages - if anything goes wrong you just flash the original (unpatched) image
Or, when Magisk updates (unfortunately, it does no more and who knows would it ever again, at least from the established channels like Stable or Canary), if there is a problem with the new Magisk - you just flash your previous version of img that was patched with the working version of Magisk and you are back in business
And there is also nothing impractical here - if you have proper TWRP (you do have for this phone) you don't need to flash the patched img from fastboot but simply from TWRP
You can also use TWRP backup boot.emmc.win instead of extracted boot.img - simply give boot.emmc.win to Magisk for patching (you don't need to rename it) and then flash it

So, guys, did the patched boot image worked for you? for me it did not boot up... :/

HValenti said:
So, guys, did the patched boot image worked for you? for me it did not boot up... :/
Click to expand...
Click to collapse
Of course it does work. But read carefully above. If you just upgraded without Factory reset, and if you had Magisk before, some modules (that remained installed to /data) may cause you the bootloop
And/or, you have to patch exactly the boot.img corresponding to your current firmware, not some from an older A10, etc

In such case, how do you remove the magisk modules after the update? Without root, there is no access to modules.

HValenti said:
In such case, how do you remove the magisk modules after the update? Without root, there is no access to modules.
Click to expand...
Click to collapse
Why don't you read the previous messages in this thread - post #6
Or see:
zgfg said:
Yes, it was asked/answered several times but let it be answered again
Besides adb, there are two other ways of disabling (or even uninstalling) the remained modules
You have to flash your patched boot.img, then
a) Reboott to Android Safe mode, then reboot again to 'normal' mode.
All modules will be disabled but also you will have to re-enable Magisk Hide again
b) Use TWRP (if appropriate for your device), Advanced, File Manager, go to /data/adb/modules and to each folder (foder = module, you can recognize modules by folder names or by reading the textual file module.prop you will find inside) put a file that must be named: disable (exactly as that)
Click to expand...
Click to collapse
Or simoly read the Magisk Wiki, available from Magisk Github (linked from Magisk app):
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com

zgfg said:
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock firmware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
Click to expand...
Click to collapse
My Ramdisk says "no" should I still patch boot.img?
not sure how to delete. It does work

Vanmanman said:
My Ramdisk says "no" should I still patch boot.img?
not sure how to delete. It does work
Click to expand...
Click to collapse
It says for everybode on MUII No for Ramdisk but it was discussed snd written everywhere and zillion times that Xiaomi users have to patch boot img

Can I somehow extract boot.img from phone without custom recovery and root?

Rejerf said:
Can I somehow extract boot.img from phone without custom recovery and root?
Click to expand...
Click to collapse
Download the full OTA for your phone, and from it, you can extract the boot.img.
Link for the OTA download and instructions on how to do it is provided here: https://forum.xda-developers.com/t/...-5-1-0-edit-yes-it-does.4299669/post-85271375

Please does someone upgraded succefully from 12.0.5.0 to 12.5.1.0 with root and without wiping data ?
If yes, how did you flashed the 12.5 ROM because TWRP recovery does no support MIUI 12.5 A11 encryption, so I guess flashing it from TWRP is not recomanded.
I am quite afraid to be forced to wipe everything and preserve root is mandatory for me so I did not tried to upgrade for now.
Thank you in advance.

Question Recovery A/B

Hi everybody,
I just got a ZenFone 8 16GB ram, I recently unlocked the bootloader and flashed TWRP.
So I've managed to flash LineageOS, but I'm not sure exactly what is going on. I wasn't able to flash the usual way via TWRP, but sideload via ADB. When reboot to Recovery, it reboots into Lineage Recovery.
I am somewhat aware that there is an A/B partition and this is my first A/B device, is there any way I can access TWRP? Or it has to run Lineage Recovery? Any way to only run 1x Recovery?

Devione said:
Hi everybody,
I just got a ZenFone 8 16GB ram, I recently unlocked the bootloader and flashed TWRP.
So I've managed to flash LineageOS, but I'm not sure exactly what is going on. I wasn't able to flash the usual way via TWRP, but sideload via ADB. When reboot to Recovery, it reboots into Lineage Recovery.
I am somewhat aware that there is an A/B partition and this is my first A/B device, is there any way I can access TWRP? Or it has to run Lineage Recovery? Any way to only run 1x Recovery?
Click to expand...
Click to collapse
As far as I know, Lineage overwrites TWRP with its own recovery, so you have to flash it again.

HyperCriSiS said:
As far as I know, Lineage overwrites TWRP with its own recovery, so you have to flash it again.
Click to expand...
Click to collapse
Hey thanks for the quick reply. I wasn't aware that was the case.
So this means that my "A" slot is now vacant and I will now need to reflash TWRP yes?
Thanks for your time.
Edit: Lineage Recovery shows that it's on "B" slot

Devione said:
Hey thanks for the quick reply. I wasn't aware that was the case.
So this means that my "A" slot is now vacant and I will now need to reflash TWRP yes?
Thanks for your time.
Edit: Lineage Recovery shows that it's on "B" slot
Click to expand...
Click to collapse
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
If you update the firmware on your device, it will flash new update to the opposite slot. usually a firmware.zip that is let´s call it a "full firmware.zip", such as lineage or the stock rom has recovery included. so you´re ending up with TWRP being "overwritten" in case you flash an update.
Unpack the payload.bin in any of those full firmware.zips via payload extractor on your pc. You´ll see all the .imgs contained. All of those partitions will be updated on the opposite slot if you flash the full firmware zip.
That means boot.img will be overwritten (magisk will be gone if you don´t choose the install magisk to inactive slot after OTA in magisk manager before rebooting the phone after the stock firmware.zip has flashed for example).

Freak07 said:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
If you update the firmware on your device, it will flash new update to the opposite slot. usually a firmware.zip that is let´s call it a "full firmware.zip", such as lineage or the stock rom has recovery included. so you´re ending up with TWRP being "overwritten" in case you flash an update.
Unpack the payload.bin in any of those full firmware.zips via payload extractor on your pc. You´ll see all the .imgs contained. All of those partitions will be updated on the opposite slot if you flash the full firmware zip.
That means boot.img will be overwritten (magisk will be gone if you don´t choose the install magisk to inactive slot after OTA in magisk manager before rebooting the phone after the stock firmware.zip has flashed for example).
Click to expand...
Click to collapse
Cheers thanks for your reply and explanation.
Appreciate your efforts and time taken to explain. Thanks for your time.
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?

Devione said:
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?
Click to expand...
Click to collapse
I don't know, but I guess if LOS supplied in form of payload.bin instead of many .img files then I think it's better to unpack all img's from there replace recovery and patched boot and "repack" it back if it's possible. At least that was the way I did that on Samsung phones. But there was only .tar archives, so that was much easier than .bin to repach which I think you will need some additional software.

Devione said:
Cheers thanks for your reply and explanation.
Appreciate your efforts and time taken to explain. Thanks for your time.
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?
Click to expand...
Click to collapse
I'm not sure about the current situation on unofficial lineage. I'm also not using it on my zf8 but from others phones, which should apply to zf8 as well.
I'm pretty sure official lineage builds have an inbuilt OTA mechanism. Unsure about the unofficial one. Better ask in the lineage thread.
However, you can boot to lineage recovery and flash the lineage.zip from there without wiping the device if you were previously on lineage and are just updating.
If you want to be rooted you need to patch the boot.img from this update (extract from payload.bin if not already available) and flash it via fastboot after updating.
By telling you to extract payload.bin I just wanted to visualize what's being updated during flashing a firmware.zip so you have a better idea how it works.

Hi there, thanks for the replies.
Sorry I wasn't being clear. By firmware updates I meant the official Asus firmware updates which are zips containing payload.bin.
What I really meant to ask was the possibility of updating the Asus firmware when still running a non Asus ROM eg LineageOS.
Earlier on I've tried to reflash TWRP over the existing LineageOS recovery and it didn't seem to work so not sure what I did wrong there. Device still boots to LineageOS and running Lineage Recovery on "B".
Thanks guys for your time and replies.
Edit - the goal at the end of the day I guess is to
1. run a custom ROM (LineageOS, GSI, Omni etc.)
2. run TWRP
3. able to update Asus firmware when available

hello everyone , sorry if I posted in the wrong place, searched and did not find,
ANDROIDE 10 A/B what is the name of the partition that is recovery?
guys, I have a k41s, on android 9,it went into recovery, it ta with root,,
I wanted you to tell me , on which partition the recovery is located, please.
{
"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"
}

[email protected] said:
hello everyone , sorry if I posted in the wrong place, searched and did not find,
ANDROIDE 10 A/B what is the name of the partition that is recovery?
guys, I have a k41s, on android 9,it went into recovery, it ta with root,,
I wanted you to tell me , on which partition the recovery is located, please.
View attachment 5478501
Click to expand...
Click to collapse

How To Guide [GUIDE] how to flash android 12-13 based gsi without bootloops

i have decided to post my personal procedure for flashing android 12 and android 13 gsi
all gsi that i will mention booted succesfull on my device (code M2103K19G)
i dont assume any responsability for possible bootloops. the procedure is 100%, if you follow will not have any problem
pre requisites:
bootloader unlocked
STOCK global miui13 installed. latest global is my favorite, but also other version works (no miui12, gsi could boot anyway, but maybe not)
magisk installed for testing the gsi before definitive flash (suggested but not necessary)
a pc with adb and fastboot installed + mtk driver
first step: choose your favorite gsi
my suggestions are: Spark a13.1 (my actual rom), crdroid 12.1 based, arrow 12.1 based, latest pphusson
download the gsi and test it via dsusideloader (you can try all gsi that you want). this is very important for verify have all what you need
in alternative read changelog of gsi or users feedback. the gsi that i have mentioned 100% boot guaranted
when you have chose the gsi wipe data and reboot phone to FASTBOOTD (i will not explain how to do, a modder must know this)
if you boot into fastboot cant flash system
download and extract fastboot stock rom
after this simply:
open image folder of your fastboot extracted rom
open a terminal (for linux user) or a cmd window (con win10 users)
flash vbmeta disabling dm-verity check typing: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
flash system.img (DONT ERASE SYSTEM PARTION!) typing: fastboot flash system system.img
flash stock kboot.img (or magisk patched for have root) typing; fastboot flash boot boot.img
reboot typing: fastboot reboot
no other commands needs, i'm 100% sure. tested directly by me
if you have made all steps correctly, and you have choosed and tested a good no wipe data is need and phone 100% boot
obviously, before flash gsi is important read the changelog of the rom for know bugs, function missing, fuction added, battery backup, performance, ecc ecc
for info about all gsi connect to official telegram channels
my favorites are pphusson channel and naz channel (the developer of my actual rom)
good look and dont ask me info about gsi. Ask directly to official telegran channel
READ WITH ATTENTION: this procedure is what i do every time i want to flash a gsi. i never encontered any bootloop, expect when a made wrong
thing like boot from slot b, flash a wrong boot.img image, flash a magisk module that is not compatible. so i dont will assume any responsability for damages to your device. it means that the problem isn't my procedure

PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help

this is the GSI img file that nned to flashed am i correct?
{
"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"
}

I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
fastboot flash system system.img
Click to expand...
Click to collapse

GrandEsquiRE said:
this is the GSI img file that nned to flashed am i correct?
Click to expand...
Click to collapse
No. Download suggestions unless you know how to solve bootloop.

up864 said:
No. Download suggestions unless you know how to solve bootloop.
Click to expand...
Click to collapse
Nvm, i'm already on corvus rn

viktak said:
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
Click to expand...
Click to collapse
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file

GrandEsquiRE said:
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
Click to expand...
Click to collapse
with dsu sideloader u can test gsi directly from xz file, no extraction is needed. is explained into the app

Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
Andyan will tell you
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
search if its BvN then its vanilla(no gapps) if BgN it has gapps

downlod arm64 bgN g=with gapps v=vanilla (no gapps)
slim version is no suggested for the gsi i have mentioned and tested
arm64= a/b device (like our)
a64= device with no dunamic partitions
i hope my guide could be helpfull to prevent a lot of possible bootloops
(also if my english is not perct, I tried to make it as easy and understandable as I could)

wetito said:
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
Click to expand...
Click to collapse
What rom is that? Can you give me the download link, and does fingerprint and 5g work?

This guide worked, thank you so much!

*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,

mg1122tt said:
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
Click to expand...
Click to collapse
thats exactly what I did. but no matter the branch/distro these new androids are so damn ugly chasing after ios and they're gettting uglier and bigger every update. .
I was mainly interested in newest GSI because of mKVM but didjt realise at the time that only two phones in the world c8rrehtlly posses requirements for it. Windows FTW!

Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
At what stage of the process? After what step?
In general, there is no time when you have to force reboot it. You can do the whole process using adb/fastboot commands as described in the OP.

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
install magisk fix for this issue, sometimes appear. u can find the guide in this forum section. the thread is gsi brightness fix

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