Development [KERNEL] [OFFICIAL] [MIUI/AOSP] [UNIFIED] LegionX V2.0 - By Venom_Stark

Development [KERNEL] [OFFICIAL] [MIUI/AOSP] [UNIFIED] LegionX V2.0 - By Venom_Stark - Redmi Note 10

« Changelogs »
[ Latest Release Changelog ]
Check Post #2 (click number) for changelogs
« NOTES »• In MIUI / MIUI based ROMs, kernel version will show "Unavailable" because MIUI doesn't support long names (because I used proton clang and lld) but kernel working perfectly you can see name in FKM tough.
• It's AIMING on Performance, stability,..
• If you can't flash with TWRP , use FK manager to flash it "root required".
• KCAL works fine .Everytime you changed value in KCAL just screen off (Don't power off) and open screen .
New value will apply.
• If your device not booting to system just bootloop or fastboot only. Don't panic. re-flash your rom file without wiping data. And please report here with the name of rom and any details.
• If you update TWRP recovery, reflash the kernel again too.
• You don't need to Wipe data ! Only cashe and Dalvik.
• Report for any bugs/issues with logs if available.
« DOWNLOADS »Latest Stable Build (LegionX V2.0):
• Click here to download LegionX V2.0 (MIUI/AOSP)
Previous Stable build:
• Click here to download V 1.0-LTO (AOSP Only) Build
« INSTALLATION »1- Download Kernel & save it on internal storage.
2- Boot to recovery (TWRP).
3- Flash the kernel zip file.
4- Wipe Cashe & Dalvik. “Don't Wipe Data”
5- Reboot to system.
NOTE: For pixel experience rom, use this Guide:
Spoiler: GUIDE FOR Pixel experience Rom
IT'S can safely installed on Pixel experience. Just follow this:
1- Boot TWRP recovery with this command:
Code:
fastboot boot twrp.img
2- Don't Install ramdisk or anything just go to LegionX Kernel on your storage and flash it.
3- Wipe Cashe & Dalvik.
4- Power Off then power on your device.
Done.
« CREDITS »• Kernel by: @venom_stark , Thanks
• Thanks to @ZIDAN44 , @CloudedQuartz ,@cyberknight777 & @Shararti1 .
• Thanks @AnomYT for Banner
• XDA-OP: @Abdullah.Csit
• #All testers.
• GitHub Source Link: https://github.com/venom-stark/mojito...

SHOW YOUR SUPPORT BY HITTING LIKE
Click to expand...
Click to collapse

#Kernel Changelogs 2021/9/03:
Code:
LegionX v2.0:
-schedtune_assist: Cleanup and update
-sched/tune: Only force UX tasks to big cores
-f2fs: Enlarge min_fsync_blocks to 20
-diag: Add timer to make sure wakelock no stuck
-fs: Reduce cache pressure
lib/string: optimized memcpy,memmove, memset
-arm64: Import latest memcpy()/memmove() implementation
-ARM64/dts: qcom: Disable CoreSight DT entries for sdmmagpie
-scsi: ufs: Scrap Qualcomm's PM QoS implementation
-scsi: ufs: Scrap Qualcomm's PM QoS implementation
-msm: adreno: Relax CPU latency requirements to save power
-sched/fair: fix misfit with PELT
-qos: Don't allow userspace to impose restrictions on CPU idle
-mmc: Disable SPI CRC
-iommu: msm: Rewrite to improve clarity and performance
-PM: sleep: Don't allow s2idle to be used
-rcu: Speed up calling of RCU tasks callbacks
-Enable JUMP_LABEL and added some jump lebel patches
Spoiler: Old changelog
Code:
➡️ 2021/8/4 |
• MIUI not supported in this update ( On V2.0 will get update)
• Used LTO binary optimization
• Complied using proton clang with lld linker.
• Performance improvement
• Battery backup improvement
#Thread Changelog:
// 2021.august.4 //
- Introduce the new LOGO
- Kernel Updated ! 2021/8/4
- Added new note about MIUI in new update To «NOTES» section (IMPORTANT)
//

Can i flash this for MIUI EU rom?

lakshmish said:
Can i flash this for MIUI EU rom?
Click to expand...
Click to collapse
Yes

Abdullah.Csit said:
#Thread Changelog:
// 2021.july.22 //
- Added new note To «NOTES» section about KCAL (IMPORTANT)
//
Click to expand...
Click to collapse

Okay, lets try flashing this one

IMHO, this kernel is a little bit better than Neternal in battery utilization. Anyway tanx to the devs.

Pachunko said:
Okay, lets try flashing this one
Click to expand...
Click to collapse
Glad to know if it success

Anish Louis said:
IMHO, this kernel is a little bit better than Neternal in battery utilization. Anyway tanx to the devs.
Click to expand...
Click to collapse
Which rom?

Abdullah.Csit said:
Glad to know if it success
Click to expand...
Click to collapse
Unfortunately it wasn't, fastboot too. I quit kernels for good I guess.
EDIT: Maybe I need to flash latest stock firmware? Just an idea.

You must have a broken system. Flash Miui from MiFlash with cleanup and then reload the desired custom ROM. This will align all partitions.
Kernel tested on PE+, camera error persists.

Wouldn't it be obvious if a system is broken? crDroid is working flawlessly atm.

StaryMuz said:
You must have a broken system. Flash Miui from MiFlash with cleanup and then reload the desired custom ROM. This will align all partitions.
Kernel tested on PE+, camera error persists.
Click to expand...
Click to collapse
Reported to developer
Developer answer : “Ok I will flash PE+ now and test camera.”
Tested : Camera working perfectly on PE+.
Pachunko said:
Wouldn't it be obvious if a system is broken? crDroid is working flawlessly atm.
Click to expand...
Click to collapse
At less test flashing Latest firmware it won't be hard and it's good for your device anyway.

Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.

Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
Just use fastboot recovery OTA tool flash CRdroid with it. Then wait till you boot in TWRP
Wipe data
Flash kernel
Reboot system
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com

Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
It's a dynamic virtual A/B phone traditional way of flashing won't work.
First flash los recovery
Fastboot flash boot LosRecovery.img
Then boot to los recovery and format data.
Then click apply updated and flash rom thorough sideload..
After flashing rom reboot and rom will boot.
Then install twrp
Type command - fastboot boot twrp.img
After booting to twrp then go to advance click "flash current twrp". Then reboot system.
Then open twrp like normally by pressing vol+ and power button (you know)
Then flash kernel.
Edit: Don't need to flash TWRP in rom in which it pre-installed.

venom_stark said:
It's a dynamic virtual A/B phone traditional way of fishing won't work.
First flash los recovery
Fastboot flash boot LosRecovery.img
Then boot to los recovery and format data.
Then click apply updated and flash rom thorough sideload..
After flashing rom reboot and rom will boot.
Then install twrp
Type command - fastboot boot twrp.img
After booting to twrp then go to advance click "flash current twrp". Then reboot system.
Then open twrp like normally by pressing vol+ and power button (you know)
Then flash kernel.
Click to expand...
Click to collapse
I think he doesn't need to flash twrp again since CRdroid included TWRP.
Best way is using fastboot tool to flash his recovery rom
My regards

Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
the critical error is, you don't start the ROM after installing the rom.
flash the rom, start the rom, create a password/pattern so you get /data encryption key (you can disable it right after, but let system set it up once)
then, start flashing the rest. (installing gapps however might be necessary before booting it up for the fist time, idk)
if system can't decrypt /data, you will end up in a bootloop and/or fastboot loop.

I
Abdullah.Csit said:
I think he doesn't need to flash twrp again since CRdroid included TWRP.
Best way is using fastboot tool to flash his recovery rom
My regards
Click to expand...
Click to collapse
Yeah I forgot. But flashing through LOS or PE recovery will give 100% success boot.

I can't flash stock now at all... I get this error in mi flash:
error: Writing 'metadata'
FAILED (remote: 'Flashing of metadata is not allowed in snapshotted state')
so phone is bricked, not sure what to do. I can only get to fastboot currently

Related

[ROM][Unofficial][20180617]CarbonROM | cr-6.1 [payton]

Credits
Moto X4 is getting some custom rom love, because @erfanoabdi worked in BEAST mode and created the trees for this device, even though he does not own the device.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware zip so both slots have the firmware, when you boot after flashing, you WILL have a bootloop or even a brick.
Warning 4 : This is an Engineering build, which means it's pre rooted and all apps have access to root. Only the SU binary is missing.
Warning 5 : Kernel is permissive.
This is an initial release and it WILL have bugs. If your phone is a daily, and you cannot afford downtime or random reboots then please do not flash.
I am new to this, DO NOT expect fixes on the fly. Post logcats and I will see what I can do.
{
"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:
/*
* 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 Carbon ROM :
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Not Working :
[*] Engineering Build - you will get a strict mode red-rectangle flash.
no moto onenav gestuers
You tell me
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Video is for LineageOS, but process is same for Carbon ROM as well.
Video
Moto X4 A/B Slots Explained
Steps
1. Download the ROM, TWRP (zip and Image), Gapps (optional) from Downloads section. Place TWRP image zip in same folder as where you have fastboot.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model). Boot into bootloader mode.
Flash the firmware with the flash_all.bat (Windows) file or the flash_all.sh (Linux & Mac) (See links on Post #2).
Windows
Code:
flash_all.bat
Mac/Linux
Code:
./flash_all.sh
Tested only on XT1900-1 on Android 8.0 model for now. Feel free to try on other models. Check for any errors in the process, DO NOT proceed if you have any errors. Once flashed successfully, reboot into Android to make sure all is well.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
3. Wipe internal data. Reboot back into bootloader mode and run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work). Make sure to remove your external sdcard before doing this. Once done, REBOOT into Android to make sure all is well. Skip all the setups.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
4. Transfer ROM zip and TWRP zip to internal memory of device. Reboot device into bootloader mode.
5. Boot to TWRP using fastboot. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot boot twrp-3.2.1-1-payton.img
Mac/Linux
Code:
./fastboot boot twrp-3.2.1-1-payton.img
5. Once booted into TWRP, click on Install - and select TWRP zip transferred in Step 1. Once done, Reboot back into system to check all is well.
6. Boot into TWRP again (reboot device, keep volume down pressed while device is rebooting. When you see bootloader mode, let go of volume down. Press volume up until you see recovery mode, press power button to select. Now you will boot into TWRP recovery).
8. Once in TWRP. Go to Wipe and swipe to factory reset. Go back, select Install and select Linage OS Rom zip, also add the TWRP zip file and click on install. Once done, wipe cache/dalvik.
Do note, recovery is built into kernel with our device so flashing any rom or kernel will result in TWRP being overwritten. DO NOT flash Magisk (any root package) or Gapps. Once ROM (and optional TWRP) have flash successfully, go to main menu :-
Now you have two options. If you WANT gapps do step 9. else go to 10. If you install gapps after booting into rom, gapps will crash. So, make your choice now.
9. Go back to TWRP main menu. Click on reboot, note down the slot you are on and select recovery.
You will now boot back into TWRP recovery. Click on reboot, and you should be on the other slot. Go back to main menu, transfer the gapps package to internal memory and install gapps.
10. Go back to TWRP main menu. click on reboot and select bootloader.
11. Once in bootloader mode. issue below command.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
Once done, reboot.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
11. To ROOT, booting into Android once is necessary whether you want gapps or not. After booting into Android once reboot back into TWRP, and then flash your root package zip, reboot and enjoy.
How to Update
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Coming from Another custom ROM, have already flashed firmware zip
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
Wipe -> Swipe to factory reset
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
How to go back to stock
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Downloads :
TWRP (Zip + Image, Download 3.2.1-1): TWRP for Payton
ROM : Unofficial Carbon ROM (payton)
Gapps : OpenGapps
Magisk : Stable Magisk
Notes :
Only Clean Installation Please
Bug Report Without logs means nothing
3rd PARTY ADDONS/MODS :
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
Reporting Bugs :
DO NOT Report bugs if you installed Xposed.
DO NOT Report bugs about Magisk Modules.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format above may be ignored.
Sources :
Carbon ROM
Device tree :
moto-sdm660-common
payton
Kernel :
moto-msm8998
Vendor tree :
moto-sdm660-common
payton
XDA:DevDB Information
Unofficial Carbon ROM cr-6.1 for Payton, ROM for the Moto X4
Contributors
erfanoabdi, mightysween, gee one, Lineage Team, Carbon Team
Donations
Donate to Carbon ROM
Buy me Coffee.
ROM OS Version: 8.1.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: No Requirements
Based On: AOSP
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-17

Firmwares
Firmwares
https://forum.xda-developers.com/showpost.php?p=76775043&postcount=2

mine002
Changelog
17th June 2018
* fixed FM radio
* userdebug build (no more red border) Thanks again @erfanoabdi

Excellent work. What would you say are the main differences between Carbon and Lineage?

sizz-lorr said:
Excellent work. What would you say are the main differences between Carbon and Lineage?
Click to expand...
Click to collapse
Lineage is pure stock android, whereas Carbon offer some customizations! I have not tried the ROM yet, i am on RR right now! But as far as I know, it is going to be stable! :fingers-crossed:

I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------

NetSpeedZ said:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
Click to expand...
Click to collapse
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.

brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Copy that. I don't have lock screen enabled, just the 'screen saver' that shows when phone senses motion nearby and shows the clock, etc.
Appreciate the clarification.
------------

New build is up.
Changelog in post 2.

brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------

NetSpeedZ said:
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
Click to expand...
Click to collapse
I did whatever the default in TWRP was, backup and restore. I googled what I should do but there wasn't anything definite. I did get an error 255 from resting the Bluetooth thing so i just omitted it.

I'm on the fence looking at these new custom ROMs available for our X4, so please help me clarify a few points:
1) does Lineage have the option to set navigation bar height? If I'll take the plunge I'm interested in having a navigation bar narrower than Android' standard;
2) is it possible to tweak the kernel with Kernel Adiutor or something similar?
3) is it possible to install and use Moto Display in some way?
Thanks!
P.S. Plese bear with me as I'm asking the same questions all over the three custom ROMs threads.

One button navigation
Is one button navigation still not working on this rom?

superj1018 said:
Is one button navigation still not working on this rom?
Click to expand...
Click to collapse
not yet.

[CLOSED][ROM] [12.1] [OFFICIAL] NusantaraProject v4.4 [22-04-2022]

{
"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"
}
"NusantaraProject v4.4"
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
"4.4 Selat Muria"Muria Strait is a strait that once existed and connected Java and Muria Island. This strait was once a bustling trading area, with trading cities such as Demak, Jepara, Pati, and Juwana. In around 1657, river deposits that emptied into this strait were carried to the sea so that the strait was getting shallower and disappeared, so that Muria Island merged with Java Island.
"Source, Main changelog on the source of each version update"
• v4.0 Surabaya - https://nusantararom.org/4-0-surabaya
• v4.0-1 Surabaya - https://nusantararom.org/4-0-1-surabaya
• v4.1 Shodanco - https://nusantararom.org/4-1-shodanco
• v4.2 Sabang - https://nusantararom.org/4-2-sabang
• v4.3 Seinendan- https://nusantararom.org/4-3-seinendan
• v4.4 Selat Muria - https://nusantararom.org/4-4-selat-muria
"Recommend Using Latest Recovery"
CLEAN FLASH:1. Reboot Recovery → Wipe Dalvik Cahce, Data & Cahce
2. Flash ROM & GApps (Optinal)
4. Format Data by Type "Yes" → Reboot System
DIRTY FLASH:1. Reboot Recovery
2. Flash ROM & GApps (Optinal)
3. Wipe Dalvik Cahce & Cahce
3. Reboot System
"UPDATE: 19/02/2022"
• Vanilla Version [MD5: 69f08f1560025cb2e236b4c2d738b83e]
CHANGELOGS:• April 2022 ASB
• Enforcing SELinux
• Tune ZRAM performance
• Enabled ZRAM writeback
• Kang AIDL vibrator service from Ronin
• [POWER] Updated power HAL from R7 RUI3
• [POWER] Boost stune on app launch
• [POWER] Allow raising sched_boost to 6 levels
• [POWER] Boost foreground to maximum when launching an app
• [POWER] Added & Improve interaction hint
• [POWER] Improve power HAL configs from Begonia
• Fix/Cleanup deprecated overlays items
• Fix KPOC/offline charging (w/Pixel-Charging)
• Metadata partition corruption protection
• Import props configuration from RMX2001_C18
• Add support for f2fs on userdata & cahce partition
• Entire C code is now optimised with armv8-2a-dotprod
• Inc. FaceUnlock, QuickTap & Touchscreen Gestures
• [Additional] Update path for CABC (rUI-2)
• [Additional] Update WM. LayoutParams (FPSInfo)
• [NOTE] Only Vanilla Build
• [NOTE] Use NikGApps A12L/SL (https://s.id/14y28)
NOTE:• Only Vanilla Build
• Use NikGApps A12L/SL (https://s.id/14y28)
• If you flash from rUI1.0: Flash ROM → Flash TWRP RUI2.0 → Format Data & Reboot!
"Frequently asked question"
1. Nusantara ROM is based on?
Ans. Its based on AOSP
2. Do we need to flash Gapps?
Ans. Yes if Nusantara ROM Vanilla does not come with prebuilt gapps.
3. When will be the next update! Any ETAs?
Ans. There will be regular updates as and when the team is ready to push a new update. Kindly do not ask for ETAs.
4. I need this feature/ I found some bugs!
Ans. Firstly if u find any bug then please check with your add-ons like magisk module, zips, etc u flashed and whether its related or no. Though if your sure that its from rom side then kindly grab a Logcat and report to me just mention on reply.
"Thanks to"
Dirty Unicorns especially @alexcruz, AOSP, LineageOS, MSM Xtended, Havoc OS, Evolution X, AOSiP, and all the other ROMs & DEVs
• Rom: Nusantara Project v4.2 (Android 12)
• Device: RM6785 (Realme 6/6i(Indian)/6s/7/Narzo/Narzo 20 Pro/Narzo 30 4G)
• Security patch level: April 2022
• Build author/Device Maintainer: officialputuid
• All Source : realme-mt6785-devs & psionicprjkt

Sir by installing this rom I face error 1 I can't install this rom so for now I installed nusantara 3.4 but sir you are doing great work making roms for realme 6 thank you sir

And sir I am very depressed corvus os will not come for realme 6 because the developer Himanshu Tyagi has left it so I also want that you take the responsibility of corvus os rom and make corvus os also for realme 6 please sir you are great please make corvus os for realme 6 I want corvus os

i got error (updater process ended with error :1) during flashing rom v4.0
is there any fix ?

LittleBoyB29 said:
i got error (updater process ended with error :1) during flashing rom v4.0
is there any fix ?
Click to expand...
Click to collapse
Use latest OrangeFox recovery

Sir I install this rom by orange fox recovery but sir I don't like orange fox recovery there is no option to wipe the system only data and after Installing the rom I was not able to format data so I install sky hawk recovery to format data and orange fox recovery also take much time to load so please make sure that in the next update of this rom it supports sky hawk recovery I only like sky hawk recovery pls sir

NGUAASHUTOSH said:
Sir I install this rom by orange fox recovery but sir I don't like orange fox recovery there is no option to wipe the system only data and after Installing the rom I was not able to format data so I install sky hawk recovery to format data and orange fox recovery also take much time to load so please make sure that in the next update of this rom it supports sky hawk recovery I only like sky hawk recovery pls sir
Click to expand...
Click to collapse
All features you mentioned are all available in orangefox recovery, you are lazy to read and search!

officialputuid said:
All features you mentioned are all available in orangefox recovery, you are lazy to read and search!
Click to expand...
Click to collapse
That is ok but I was not able to format data after flashing your rom in orange fox recovery so that is bug of orange fox recovery and the rom is great sir thanks for making but the gaming mode is missing

officialputuid said:
Use latest OrangeFox recovery
Click to expand...
Click to collapse
it worked thanks for this amazing rom

After Flashing, Orange Recovery Fails to decrypt my Data partition. Any idea? Also, can you add F2FS support? Thank you
Edit: Face unlock isn't available for some reason?

Hi, I just wanted to check, clicking through to the changelog mentions camera as "partial" and Extra cameras on the not working section. I am guessing this means that the wide, portrait and Macro camera are not available to use?
Out of curiosity, are people daily driving this, how are you finding it?
Thanks to OP for keeping devices like these alive with updates.

MegaAndy said:
Hi, I just wanted to check, clicking through to the changelog mentions camera as "partial" and Extra cameras on the not working section. I am guessing this means that the wide, portrait and Macro camera are not available to use?
Out of curiosity, are people daily driving this, how are you finding it?
Thanks to OP for keeping devices like these alive with updates.
Click to expand...
Click to collapse
Yups, only main/primary cam work.

Can't install the rom, error 4 with orange fox r11-04

unlokomukuerdo said:
Can't install the rom, error 4 with orange fox r11-04
Click to expand...
Click to collapse
R11.1_1_RUI1.0 is the latest stable, installs it perfectly for me.

BUG: When I go to Advanced Reboot, and select Recovery, the phone goes into a boot loop and won't boot either the recovery nor the rom. I have to do a full Restore with SPFlash Tools.
Nusantara 4.0-1
OrangeFox Recovery R11.1_1_RUI1.0

roberto888 said:
BUG: When I go to Advanced Reboot, and select Recovery, the phone goes into a boot loop and won't boot either the recovery nor the rom. I have to do a full Restore with SPFlash Tools.
Nusantara 4.0-1
OrangeFox Recovery R11.1_1_RUI1.0
Click to expand...
Click to collapse
ofc will brick, u need change recovery to based rui 2.0 (this rom based RUI2.0)
Note:
* If u flash from rUI1.0:
Flash ROM → Flash TWRP RUI2.0 → Format Data!

officialputuid said:
ofc will brick, u need change recovery to based rui 2.0 (this rom based RUI2.0)
Note:
* If u flash from rUI1.0:
Flash ROM → Flash TWRP RUI2.0 → Format Data!
Click to expand...
Click to collapse
Ah, that makes sense. Thanks!

can it be installed in RMX2061?

everything works perfect,
But in home screen and app switches does not look so much smooth,
Otherwise 10/10 marks ..
How to improve this
May I have to use magisk or any modules for that or this is in inbuild settings if have then tell me which one..
I tried everything but not work..
Thanks again for developing this rom..
Salute for this devloper

Flashed the 4.1 version through twrp, and there are no issues whatsoever. Everything running smoothly, really enjoying it so far!
One question though, is face unlock not available for this rom? Because i remember android 10 and 11 had them by default but i can't find any settings on this one, for future updates maybe?

[ROM] [OFFICIAL] [STABLE] [R] DotOS 5.2.1 [MOTO X4 - PAYTON] [23/11/2021]

View attachment 5438975
" #DroidOnTime "
ROM Version: 5.2.1
Device: PAYTON
Maintainer: AADITYAZEO
Build Status: OFFICIAL
View attachment 5438991
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.
Click to expand...
Click to collapse
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration."
View attachment 5438997
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
View attachment 5438999
CLEAN FLASH/First Time Installation :
01. Download the ROM, Firmware and GApps from the links above.
02. If you're coming from Oreo Flash the PIE Firmware (Factory Image or Firmware ONLY) for your device.
03. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
04. Create backup. i.e. EFS
## YOU ONLY NEED THIS STEP ONCE.. When updating Firmware's ##
05.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"
06. Flash the ROM and TWRP installer.
07. Choose Reboot -> Recovery
08. Install GApps & Magisk.
09. Reboot -> Bootloader
10. fastboot -w
11. Reboot and Enjoy.
*Note-1: Slots, ROMS install to opposite (inactive) slot
If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
*Note-2: Firmware's
* Recommended to install to "Slot A" unless you have PIE firmware fully installed on "Slot B" (you can achieve this with Firmware ONLY Links or copypartitions.zip ran from Slot A after a full stock update)
DIRTY FLASH :
1.Download the latest build.
2.Reboot to recovery.
3.Flash the latest build along with the twrp.
4.reboot to recovery. (very Important)*
5.flash optional packages like gapps and magisk.
6.Wipe Cache.
7.Reboot.
Note: If upgrading from 5.0.* to 5.1.* a clean flash is required.
Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.
View attachment 5439003
CLICK ME
View attachment 5439005
COMPLETE CHANGELOG : https://changelogs.droidontime.com/
View attachment 5439007
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
Project Lighthouse
And all other open-source Devs/Teams.
View attachment 5439009
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Sipun Kumar - Developer/Maintainer
Special thanks:
Manish Bajpai - Web Developer
Important Links
If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM
Donate to device maintainer. - Donate - https://www.paypal.me/jackvortexhd
dot OS source
dotOS-Device Sources
{
"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"
}
Telegram Group
Telegram Channel
Website
Downloads page
REPORTING BUGS !
As soon as the problem occurs, take a LOGCAT!
for more READ THIS
and do not forget to send it to us
View attachment 5439011
Contributors: AadityaZeo
Source Code: https://github.com/DotOS
GitHub : - https://github.com/aadityazeo
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.2.1
Stable Release Date: 23-11-2021

Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.

Same problem be my.

Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Which Verison of twrp you're using?

Aaditya ZeO said:
Which Verison of twrp you're using?
Click to expand...
Click to collapse
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, booting to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.

Randy Power said:
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, boring to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Click to expand...
Click to collapse
There're quite few things which you need to remember.
1st
2nd
If you were stuck on boot logo, you should perform fastboot - w in bootloader.
3rd - as per your comment u want vanilla edition. So i suggest u to stick with two 3.5xxx (latest prior to version 3.6xx) and follow the steps as stated below
a) completely wipe the phone
b) rom + twrp
c) reboot to recovery
d) wipe data in twrp
e) reboot to system.
This should work as I've also installed vanilla Verison with same process.

Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?

Randy Power said:
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Click to expand...
Click to collapse
I don't think it matters, I've use twrp 3.2 and 3.6 to install gapps and had no issues in either case.

I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.

Randy Power said:
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Click to expand...
Click to collapse
Can you try to install gapps version for once?

I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed

After the above, I formatted data from twrp. It completed without errors, so I rebooted to system.
Result: Still stuck on spinning planets.

Randy Power said:
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
nope this shouldn't be the output after the fastboot -w.

Aaditya ZeO said:
nope this shouldn't be the output after the fastboot -w.
Click to expand...
Click to collapse
I appreciate that. I've tried many combinations of formatting data in TWRP, which seems to work. Resizing the partition and fsck on the partition work fine, all in TWRP. I can even copy files from /externalsd to /sdcard, and the fs survives a reboot.
However, fastboot -w always fails (error shown above), and booting the system gives spinning planets animation forever.
I'd be grateful for pointers on fixing the fastboot -w problem, if that is what's needed.

Hello
I installed dotOS 5.2.1 and when it's time to enter the PIN code it says that the sim card is locked. Tried both PIN and PUK, but none works. What should I do?

OK, so I solved it by basically following these instructions:
However, I now have a new problem. If I power off the phone while the USB charger is connected, it restarts the phone instead. And if it's powered off and I connect the charger, it turns itself on. This didn't happen with Android 9. How can I fix it? I do not want my phone to switch itself on when charging.

Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Are you flashing to the appropriate slot?

For those having problems with the phone rebooting after a few seconds after upgrading from an Android 9 rom:
You might need to upgrade the modem firmware. That happened to me while upgrading from Lineage 16.0 to Lineage 18.1. After investigating a bit, I figured out the problem happened when connecting to the mobile network or (sometimes) wifi.
This is (roughly) how I solved the problem:
- flash your choice of recovery/system (not needed if already done - if you do this later your updated firmware might be overwritten)
- download the latest payton stock rom from lolinet's obsolete phones archive
- unzip and cd to unzipped folder
- connect phone and reboot to bootloader
- make sure you have fastboot and run the following commands (adapt to your OS as needed):
mfastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot erase carrier
fastboot erase userdata (I did it after backing up my data, but I think it was not necessary)
fastboot erase ddr
fastboot reboot
- have fun!
Notes:
- you might just flash a subset of the binaries above, I flashed what I thought was needed. The original reddit thread mentioned only NON-HLOS.bin and fsg.bin
- after having tried many things I ended up with dotOS 5.2.1 and will try it for a while
References
- this reddit comment
- Method 2 at rootmygalaxy

rodrigopitanga said:
Are you flashing to the appropriate slot?
Click to expand...
Click to collapse
I think yes. It's been a few weeks now, so my memory on the details is fuzzy. But I'm familiar with the A/B monkey business, copy partitions, etc. And flashing lineage worked out successfully. Thank you for the reply.

Does adoptable storage work?

[RECOVERY][UNOFFICIAL]TWRP 3.6.0 for 2020 Galaxy Tab A7 10.4[SM-T500]

Code:
/*
* Disclaimer
*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*/
Introduction
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
TWRP version: 3.6.0_11
For device: gta4lwifi
Device tree: https://github.com/pazos/android_device_samsung_gta4lwifi
Maintainer/Authors build: paziusss
Known limitations
FBE encrypted storage (Internal Data) not able to be decrypted in TWRP.
Changelog
2021-12-08:
Added: exfat support
Added: mass storage support
Fixed: USB composition rules
Supressed audit messages in logcat
Misc changes (see device tree for details)
2021-12-05: Initial release
Motivation and credits.
AFAICT there're two TWRP builds on xda for the SM-T500, made by ragarcia87 and agreenbhm
The main motivation for Yet Another TWRP build was getting fastboot working, so we can follow official instructions to flash GSI builds on our devices.
Credits to u/agreenbhm for the device tree: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Credits to u/ragarcia87 for the thread, which I used as a template for this one
Installation Instructions
Spoiler
From computer:
Download Odin Flashable Tar from bellow
Put tablet into Odin Download Mode
Flash Blank vbmeta via Userdata
Flash Odin Flashable Tar via AP
From TWRP:
Download recovery.img from below
Copy recovery.img to device
Install > Install Image > recovery.img to Recovery
Reboot > Recovery
Flashing system/vendor/product/odm partitions
Spoiler
Logical partitions are read only from TWRP. If you want to flash them you'll need to reboot in fastbootd.
Boot in TWRP
Go to reboot and select fastboot.
Wait until you see a TWRP dialog saying "entered in fastboot"
Once you flashed all desired partitions reboot to recovery
In recovery wipe -> format data.
Notes on GSI flashing:
/product partition is unused in GSI builds. You can flash an empty image to gain 1GB for other logical partitions.
/system partition will be resized to the size of the GSI image you're flashing.

Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?

Hi Magendanz. Thanks for your feedback.
I have no issues mounting the MicroSD card. Do you have some logs?
Updated DT link!
About the device tree: I'm having trouble pushing the changes to github because my slow connection. Will see if I got them pushed somehow. If not I will revert blobs to agreenbhm version.
Magendanz said:
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Click to expand...
Click to collapse

paziusss said:
I have no issues mounting the MicroSD card. Do you have some logs?
Click to expand...
Click to collapse
Here's the log...

Hi!
Indeed, I didn't test with exfat. Should be fixed soon. Also adb sideload don't work in the version attached.
I will make the changes ASAP and give a better commit history in device tree

Hi. Device tree updated with support for exfat and ADB sideload fixed.
Will upload the binaries in a few hours!

Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.

stompysan said:
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
Click to expand...
Click to collapse
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet

Hi. I've updated recovery binaries and added a changelog.
Please report the issues you find.

paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
Will it work with Pixel Experience?

EdwardTCM said:
Will it work with Pixel Experience?
Click to expand...
Click to collapse
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.

paziusss said:
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
Click to expand...
Click to collapse
Alright Thanks

paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping

paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Edit: Maybe this is happening because of the ROM being A only

EdwardTCM said:
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
Click to expand...
Click to collapse
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.

thank you for twrp and fastboot but i noticed that most gsi images are bugy no brightness or randemly rebooting

paziusss said:
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
Click to expand...
Click to collapse
OOOH I thought it was A Only

EdwardTCM said:
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY

EdwardTCM said:
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
Click to expand...
Click to collapse
Btw the wifi doesn't work

One Issue when downgrading to TWRP 3.5 is that it will boot loop

[ROM][OFFICIAL] LineageOS 20 weeklies for Xiaomi Poco F1

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:

Device tree source code: LineageOS/android_device_xiaomi_beryllium
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
WiFi Display
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Poco F1 variants.Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v12.0.3.0 global stable package.
Device wiki:
Official wiki link
Downloads:
Official download links
Installation:
Follow instructions found in the respective wiki page

Is this a System-Ext-Rom?

Chris_Kaos79 said:
Is this a System-Ext-Rom?
Click to expand...
Click to collapse
Yes

Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?

I updated to LOS 20 via dirty flash from LOS 19.1 (following the official procedure: https://wiki.lineageos.org/devices/beryllium/upgrade)
It worked flawlessly!

AtomicStryker said:
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
Click to expand...
Click to collapse
NGK has some problems for now, wait for update or use orange fox...

AtomicStryker said:
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
Click to expand...
Click to collapse
I know this is off-topic, but I guess you used Reignz V3.6.2 that he tested for A13 support?
Interesting that apparently A13 again uses other encryption than A12? I though now with A13 FBE would be the new standard but there is something new again?
So official 3.7.0 TWRP will not work with A13 I guess.
Looking forward to jump to A13 this weekend based on all the positive feedback so far - thank you bgcngm for your hard work!

hello there,
I've just dirty flashed LOS20, and I'm having problems connecting anything via bluetooth, any idea how to fix this without clean installing?
Another question, I'm using MindTheGapps 13 as recommended here, but I was looking for something the minimum google services, do you think I can use NikGapps?
Thanks

alright, I couldn't fix it, I had it reinstalled clean. Everything is working nicely and the new camera is a very welcome improvement.
I'm still facing issues with bluetooth though. I'm able to use it and connect normally, but when listening to audio, it seems that the connection is weak, and I can often hear cuts in the connection, or noise. Anyone having the same?

AtomicStryker said:
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
Click to expand...
Click to collapse
This problem is a known issue since the day before yesterday. Several people are experiencing this with the upgrade from 19.1 to 20. For now, running the stock kernel should be fine.

Installation GuidesOfficial way of installation can be found at OP.
Installation Guides:
Clean Install via TWRP:
Backup your data to PC or SDCard if you have.
Downland:
Spoiler: These files
- TWRP by REIGNZ v2 [twrp-beryllium-v3.7.0-A12-V2.img] - [Current Bugs/Issues & Workarounds]
- Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
- Optional A13 GApps of your choice.
Boot, flash and reboot to TWRP. [Check Install Custom Recovery Guide]
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, System_EXT, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Reboot to recovery once again (needed due to a current issue with TWRP by REGINZ) and then Format data > type yes.
Transfer the files you previously downloaded into Internal Storage, while you are connected and into TWRP from PC to your Device. If you have SDcard or USB OTG you can also use that.
[TWRP by REIGNZ have an issue, if PC doesn't recognize the device, press in twrp menu, Advanced > File Manager > and find and select sdcard folder aka Internal Storage > go back and now your pc should be able to recognize the device]
Flash ROM > GApps. NOTE: ROM IS FORCE ENCRYPTED
[Optional] Flash LineageOS recovery by pressing "Install Image > Navigate and Select the LineageOS Recovery > Flash it to recovery partition.
Reboot and Enjoy!
[Optional] In case you want to change Kernel to NGK or SC [SE version - aka System_Ext], flash it after the first boot of the ROM.
[Optional] In you case you want Root, flash Magisk after the first boot of the ROM.
SafetyNet & Certified Play Store:
Official LineageOS doesn't pass SafetyNet or have certified Play Store by default. [Read here why]
Root your device with Magisk and Follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
OTA Upgrade/Update:
Warning
Only use OTA if you are encrypted. Simply go to updater and press install, everything will be automatic.
Dirty Installation via TWRP:
{Manually Upgrade/Update the ROM}
Download:
Spoiler: These files
- TWRP by REIGNZ [twrp-beryllium-v3.7.0-A12.img] - [Current Bugs/Issues & Workarounds]
- Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
- Optional A13 GApps of your choice.
Wipe System, System_Ext, Dalvik ART/ Cache, Cache, Vendor.
Flash ROM > GApps > [Optional]Magisk.
Reboot and Enjoy!
Notes:
If you want to flash DFE use TWRP by REIGNZ based on A9. (not A12) [Not recommended be decrypted]
If you encounter Fastboot issues read the guide/fix in my thread.
You can translate the ROM in Crowdin.
Check my threads:
Spoiler: My threads
- POCO F1 Ultimate Collection & Guides
- Android Ultimate Collection & Guides
- ReVanced & ReVanced Extended - Guides & Useful Links
- Windows Ultimate Collection & Guides

pmcmm said:
I'm still facing issues with bluetooth though. I'm able to use it and connect normally, but when listening to audio, it seems that the connection is weak, and I can often hear cuts in the connection, or noise. Anyone having the same?
Click to expand...
Click to collapse
I had to unpair my existing bluetooth devices and re-pair them, (presumably because the upgrade changed the phones bluetooth ID) but it seems to work perfectly for me.

- I am on this ROM since 01.01, no major issues so far.
- Just FYI, DFE zip (Disable Force Encryption) from Retrial collection doesn't seem to work on this ROM. For the sake of testing, I tried both A13 DFE and the older zip (which worked on LOS19.1) with clean installations. When I check in the settings, the phone was encrypted every time, no matter what I do.
- On the other hand, I can report that unofficial TWRP A12 by Reignz (twrp-beryllium-v3.7.0-A12.img) can decrypt storage on LOS20.
- One small glitch I found: If I lit up the screen (press power button) while charging, the phone stays on the lockscreen with the display on, never turning off by itself. Of course if I press power button or double tap I can turn it off. Also if I just disconnect power cable, display turns off in few seconds like it should. But if I just press power once and leave it, it will stay on the lockscreen forever.
- Bluetooth is fully working for me. I am using 2 different BT headsets for few hours every day. Not a single issue so far.

marsa47 said:
- Just FYI, DFE zip (Disable Force Encryption) from Retrial collection doesn't seem to work on this ROM. For the sake of testing, I tried both A13 DFE and the older zip (which worked on LOS19.1) with clean installations. When I check in the settings, the phone was encrypted every time, no matter what I do.
- On the other hand, I can report that unofficial TWRP A12 by Reignz (twrp-beryllium-v3.7.0-A12.img) can decrypt storage on LOS20.
Click to expand...
Click to collapse
The DFE not seem to working with the TWRP by REIGNZ based on A12. Instead you should try to flash DFE via TWRP by REIGNZ but based on A9.
The purpose of A12 based twrp is to decrypt A12+ encrypted ROMs. If you don't need encryption (which I recommend everyone to use encryption), then use TWRP by REIGNZ A9 and flash DFE.

any way to get F2FS working ? With flashed fstab i get recovery reboot and without i get a bootloop

Is it important to fastboot the required xiaomi firmware first? Coming from 19.1.

MagnesG said:
Is it important to fastboot the required xiaomi firmware first? Coming from 19.1.
Click to expand...
Click to collapse
I assume u already have it. No need.

noah001 said:
any way to get F2FS working ? With flashed fstab i get recovery reboot and without i get a bootloop
Click to expand...
Click to collapse
Flash a kernel with with f2fs support,

Do "long loading while taking picture from whatsapp-bug" still occurred????

123r4ka456 said:
Do "long loading while taking picture from whatsapp-bug" still occurred????
Click to expand...
Click to collapse
I get the following behavior:
1st try: click on photo button: nothing happens (but no hang)
2nd try: click on photo button: photo is immediately taken and can be sent, no hang
So: not really running without issues, but no hang
Maybe this is helpful

Better Mobile App

welcome