CLOSED PER OP REQUEST
{
"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"
}
Download:
DOWNLOAD officail
Kernel source:
Source
Selinux Status:
Enforcing
MAJOR BUGS:
?
flash on your own risk.
FLASHING
flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
May the force be with you
XDA:DevDB Information
OmniRom, ROM for the Xiaomi Mi Pad 4
Contributors
darkobas, darkobas
Source Code: [url]https://github.com/omnirom/android_kernel_xiaomi_clover[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-01-13
Last Updated 2019-01-13
WOW, did you get an Mipad?
Thanks for the rom, need to test asap
Update: installs nicely, boots into black screen. Full wipe install
Update 2: no boot,LTE Mipad
NisseGurra said:
WOW, did you get an Mipad?
Thanks for the rom, need to test asap
Update: installs nicely, boots into black screen. Full wipe install
Update 2: no boot,LTE Mipad
Click to expand...
Click to collapse
so i cant guess whats going on.
recent gapps are derped again without correct permissions. use older ones. or try first just without.
darkobas said:
so i cant guess whats going on.
recent gapps are derped again without correct permissions. use older ones. or try first just without.
Click to expand...
Click to collapse
I tried with and without gapps, no luck. I guess its the LTE version that gives some bugs
NisseGurra said:
I tried with and without gapps, no luck. I guess its the LTE version that gives some bugs
Click to expand...
Click to collapse
you can munt /system in twrp and edit /system/etc/prop default
change ro.secure and ro.adb.secure to 0 and then adb logcat should work
darkobas said:
you can munt /system in twrp and edit /system/etc/prop default
change ro.secure and ro.adb.secure to 0 and then adb logcat should work
Click to expand...
Click to collapse
Will do, have to wait until tomorrow tho. Thanks for bringing omni to mipad, VERY nice addition.
Although i don't use gapps, the firmware boots fine :goodn my base (non LTE Mi Pad 4) model.
Thanks god!
Glad to see you here!:fingers-crossed:
Alex Kane said:
Although i don't use gapps, the firmware boots fine :goodn my base (non LTE Mi Pad 4) model.
Click to expand...
Click to collapse
I have a question, how do people live without Gapps? All the best games and apps are on the Play Store.
ibooth2004 said:
I have a question, how do people live without Gapps? All the best games and apps are on the Play Store.
Click to expand...
Click to collapse
MicroG
ok so new build is up. squashed a few bugs. wifi model is now super stable and everything seems to work.. please let me know if u come accross any bugs.
sadly no ideas about lte model... hope some1 can pitch in and do some work on the lte model on my device tree.
So selinux is enforcing, safety net pass out of the box, no need for magisk for this.
device will probably go official starting on sunday. take note that u can not dirty flash official over this builds.
I have a go tonight and try to provide you some logs on the LTE boot bug
Thany you for your awesome job, @darkobas. I followed your project since Oneplus One and 5. Very awesome to have this project on Clover.
Good news .
Waiting for official
darkobas said:
you can munt /system in twrp and edit /system/etc/prop default
change ro.secure and ro.adb.secure to 0 and then adb logcat should work
Click to expand...
Click to collapse
Any hint in this logcat?
(remove zip ext)
NisseGurra said:
Any hint in this logcat?
(remove zip ext)
Click to expand...
Click to collapse
push this https://drive.google.com/open?id=1fZsbW2JXYc_xU5Nc1nfzPo-ub-SNKFiQ to /vendor/lib64/
darkobas said:
push this https://drive.google.com/open?id=1fZsbW2JXYc_xU5Nc1nfzPo-ub-SNKFiQ to /vendor/lib64/
Click to expand...
Click to collapse
Tried it, still dark boot. Adb see the device and i think its seen by windows. I tried mokee boot img, it shows the boot-animation but don't boot into omni tho
NisseGurra said:
Tried it, still dark boot. Adb see the device and i think its seen by windows. I tried mokee boot img, it shows the boot-animation but don't boot into omni tho
Click to expand...
Click to collapse
are you sure its a clean flash ? log looks 'dirty'
darkobas said:
are you sure its a clean flash ? log looks 'dirty'
Click to expand...
Click to collapse
Wiped data, system and caches. Not sure twrp does an proper wipe tho. I have a look
Update: Full wipe: data, system. vendor. Device clean.
Installed latest Omni, reboot: same black scren during boot.
Added prop adb mod, new logs (attached)
Note: Screen backlit is on
Seems boot.img related?
Logcat: "06-14 15:36:54.456 1196 1253 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
06-14 15:36:54.464 1196 1196 E System : ******************************************
06-14 15:36:54.466 1196 1196 E System : ************ Failure starting system services
06-14 15:36:54.466 1196 1196 E System : java.lang.IllegalStateException: PMS compiler filter settings are bad.
06-14 15:36:54.466 1196 1196 E System : at com.android.server.pm.PackageManagerServiceCompilerMapping.checkProperties(PackageManagerServiceCompilerMapping.java:92)"
NisseGurra said:
Wiped data, system and caches. Not sure twrp does an proper wipe tho. I have a look
Update: Full wipe: data, system. vendor. Device clean.
Installed latest Omni, reboot: same black scren during boot.
Added prop adb mod, new logs (attached)
Note: Screen backlit is on
Seems boot.img related?
Logcat: "06-14 15:36:54.456 1196 1253 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
06-14 15:36:54.464 1196 1196 E System : ******************************************
06-14 15:36:54.466 1196 1196 E System : ************ Failure starting system services
06-14 15:36:54.466 1196 1196 E System : java.lang.IllegalStateException: PMS compiler filter settings are bad.
06-14 15:36:54.466 1196 1196 E System : at com.android.server.pm.PackageManagerServiceCompilerMapping.checkProperties(PackageManagerServiceCompilerMapping.java:92)"
Click to expand...
Click to collapse
since u have already wiped everything can you just try to format data partition ?
fastboot format userdata
but this will completely wipe all data..
Related
THIS IS AN OS WHICH I AM USING FOR DAILY USES AND NOW I AM SHARING WITH YOU GUYS.
{
"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"
}
" #DroidOnTime "
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.
*
*/
Stability and Performance
Lagfree with High Performance Results
Clutterless UI
Perfect Interface for every User
Enhanced default apps
Redesigned settings and QS panel
Full OMS support
Colour Engine Support
DotExtras !!
CLEAN FLASH :
USE TWRP TO FLASH
Download the latest build and GApps
Reboot to recovery
Make TWRP backup (EFS and MODEM partaion Necessary if SIM not Detected)
Wipe System, Data, Cache , Dalvik
Flash the latest build and GApps
Reboot
DIRTY FLASH :
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update) as long as the instructions of your
root solution do not state something else (="persistence on dirty flashing") !
Download ROM:http://www.mediafire.com/file/rn4e6jj13343to5/DOT-N-v1.2-20180411-n7100-UNOFFICIAL.zip
Download Gapps:
Note : Pico or Nano Gapps are recommended. We Don't prefer STOCK/HEAVY Gapps
OpenGApps
DO NOT EDIT OR MODIFY THIS ROMThank you. Hope you like it until I develop an oreo ROM.
XDA:DevDB Information
[ROM][7.1.2_r29] dotOS-v1.2 [N7100][28-12-2074], ROM for the Samsung Galaxy Note II
Contributors
santosh61
Source Code: https://github.com/DotOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LOS
Version Information
Status: Nightly
Created 2018-04-11
Last Updated 2018-04-11
Screenshots:
Downloading, will try it now
Upd. Flashed it abd the speed of system, animations is so incredible! I can just say one thing "WOW" ! nice work Santosh:victory:
Awesome work! @santosh61
Fantastic bro @santosh61, will download it and give you my feedback, and waiting for oreo, good luck dude
Keep going ??
Nice work !! @santosh61
Any bugs we have to know?
Standard nougat ones?
I got first problem with systemUI. Attached logcat. :silly:
Deleted
Downloading now. I hope this will last rom I will install
Me too got a bug.
I added extra tiles in qs.But now i cannot.When i press plus button on top or qs,the systemui crashes and restart it to lockscreen.
Everything except that works well.
hishamnoobie said:
Me too got a bug.
I added extra tiles in qs.But now i cannot.When i press plus button on top or qs,the systemui crashes and restart it to lockscreen.
Everything except that works well.
Click to expand...
Click to collapse
Yes same with me.
hishamnoobie said:
Me too got a bug.
I added extra tiles in qs.But now i cannot.When i press plus button on top or qs,the systemui crashes and restart it to lockscreen.
Everything except that works well.
Click to expand...
Click to collapse
Dxnxsh said:
Yes same with me.
Click to expand...
Click to collapse
Same here guys. I attached logcat file on previous page.
what root method have you used? Also, pico or Nano Gapps? Are you all(having qt problem) on magisk?
Hi
pls can help me I lost the( Not Registered On Network) when install this the Rom
AL-Hasani said:
Hi
pls can help me I lost the( Not Registered On Network) when install this the Rom
Click to expand...
Click to collapse
if you look in the OP (first post made by the developer) you will see this:
'''Make TWRP backup (EFS and MODEM partition Necessary if SIM not Detected)''
what does it mean?
Have you made a EFS and Modem backup with TWRP before flash the rom?
Then reboot to recovery and flash the back up back , because your EFS and Modem partition has been corrupted and you cannt be registerd to your mobile network.
if you dont have a EFS and Modem back up, the only way(s) I know to restore that are:
1. Reflash a known working rom that you previous had in your phone
after flash rom reboot in recovery and see if then you can take back your EFS and modem.
IF YOU DO, then your problem is solved. But if NOT,
2. FLASH STOCK ROM with odin, let it boot once and see if your sim card is recognized and you can registered to your network. If yes, flash TWRP with odin again.
Reboot in recovery, BACKUP your EFS and Modem partition, save it in 2-3 positions (ext sdcard, PC, cloud) and then continiue your custom rom flashing.
If in any of these need some help, just ask for more details
GOOD LUCK my friend
logosA said:
what root method have you used? Also, pico or Nano Gapps? Are you all(having qt problem) on magisk?
Click to expand...
Click to collapse
I'm using lineage su add-on.
nNeFeroN said:
I'm using lineage su add-on.
Click to expand...
Click to collapse
kernel? Stock? or something else?
I am on Hybrid Boeffla v9.8
logosA said:
kernel? Stock? or something else?
I am on Hybrid Boeffla v9.8
Click to expand...
Click to collapse
Everything is stock. Nothing has been change in system except installing su add-on.
I reflashed ROM, everything worked. But after few hours QS tiles settings started to crash again.
Maybe it is lineaguSu?
{
"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"
}
What is Project Treble?
Everything is explained here!
What's working:
Boots
Wifi
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
Sensors
GPS
RIL
VoLTE
What's not working:
Selinux is permissive
You tell me
Generic System Images:
Here
How to flash:
Use a TWRP with /vendor support
Wipe cache, dalvik-cache, system, vendor and data
Flash the required firmware
Flash the treble_lithium-xxxxxxxx-xxxx.zip
Select "Flash Image"
Flash a Generic System Image in system partition (arm64, A only)
Reboot
Special thanks:
Tranquilitysmile for testing and debugging
XDA:DevDB Information
Project Treble for the Xiaomi Mi Mix
Contributors
Psy_Man
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: 8.8.30
Based On: AOSP
Version Information
Status: Stable
Created 2018-05-01
Last Updated 2018-09-12
Screenshots:
Excellent looking forward to this
Add this line to build prop to enable navbar
Code:
qemu.hw.mainkeys=0
Great job, thanks
02.05.2018 build:
- Forced enable navigation bar (thanks @EvangelineDEV for pointing this out)
- Moved listen_platform_info.xml to /vendor
- Merged changes from LineageOS
Download build
This is awesome!
Thanks Pepsy!!!
Earphone does not work, is it a common problem ?
Great work!
woha, thanks @Psy_Man !
since this took me somewhat by surprise: how will the flashing-process with treble roms differ from the traditional way? after flashing the treble-zip (and doing a factory reset) for the first time, will it be possible to switch the generic system images without a factory reset every time like when switching a "traditional" rom? will you still continue your Pixel Experience rom or is Treble the way to go? and which TWRP meets the /vendor requirement? the TWRP-thread is a bit chaotic...
sorry for all those questions, really appreciate your work!
doumer said:
woha, thanks @Psy_Man !
since this took me somewhat by surprise: how will the flashing-process with treble roms differ from the traditional way? after flashing the treble-zip (and doing a factory reset) for the first time, will it be possible to switch the generic system images without a factory reset every time like when switching a "traditional" rom? will you still continue your Pixel Experience rom or is Treble the way to go? and which TWRP meets the /vendor requirement? the TWRP-thread is a bit chaotic...
sorry for all those questions, really appreciate your work!
Click to expand...
Click to collapse
I believe factory reset and wiping system and data are still needed between GSI's... But it should be tried...
Twrp by raupe-lunden.... Find it linked in most oreo roms threads op's I think.
For flashing generic procedure the instructions are linked right here in Psy_Man's OP
Using RR image, stuck at white android logo. Cannot go into OS, trying format data wipe all, result still same
Fusionist said:
Using RR image, stuck at white android logo. Cannot go into OS, trying format data wipe all, result still same
Click to expand...
Click to collapse
I cannot see logcat here. Ignored.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
I still dont know how people want us to solve these problems , if they dont provide logcat we cannot make magic and say OH this is!!!!!!! lol . Thanks Psy_Man for your treble work.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
Yup.
I also couldn't boot RR or AOKP... Will try and get logcats from the bootloop and share here a pastebin or the likes.
This treble advances for lithium I believe are awesome and undoubtedly the way to go.
Thanks again Psy_Man.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
Sorry for not provided logcat, I dont know how to getting logcat when my phone stuck at boot animation ? How can I get the logcat when stuck at boot?
Fusionist said:
Sorry for not provided logcat, I dont know how to getting logcat when my phone stuck at boot animation ? How can I get the logcat when stuck at boot?
Click to expand...
Click to collapse
If I recall correctly, running
Code:
adb -d logcat>mylogfile.txt
before the phone boots should wait until the phone boots and connects to the computer, provide you with a logcat, and save it to a file. (You won't see the output in the terminal, but the log file should be there. There's more information on this here.)
This looks great, good work! I'll try it in a bit and report back on how it works. Thanks again!
NLivingstonAP said:
If I recall correctly, running before the phone boots should wait until the phone boots and connects to the computer, provide you with a logcat, and save it to a file. (You won't see the output in the terminal, but the log file should be there. There's more information on this here.)
This looks great, good work! I'll try it in a bit and report back on how it works. Thanks again!
Click to expand...
Click to collapse
Many thanks ! I'll try it again
Hello i want to ask what is the benefit using the treble based custom rom? From what i know is the update is faster for oem eg samsung, lg or oem that used treble, but what is benefit using this on custom rom?
billyliem said:
Hello i want to ask what is the benefit using the treble based custom rom? From what i know is the update is faster for oem eg samsung, lg or oem that used treble, but what is benefit using this on custom rom?
Click to expand...
Click to collapse
You flash the treble compatible and then any GSI out there, that are cooked and usable for any treble enabled device. You don't need an aokp (or any other) cooked specifically for lithium.
I'm not responsible for whatever damage this could possibly cause to your device.
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to GSI For Galaxy M20 ONLY FOR M205F/M205G
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
Make sure you install TWRP : https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
If any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide Guide that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
All Sensors
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
Flash "GSI_Fix_boot.zip"
- STEPS FOR INSTALLING GAPPS
Download the appropriate OpenGapps.org
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- FOR INSTALLING FIXES:
Camera Fix (Flash only on NON Working GSIs)
- KNOWN BUGS:
Fingerprint
Bluetooth calls are broken
No Network bars (Calls/data works)
May be more, Let me know
Downloads. F.A.Qs below
XDA:DevDB Information
Guide on How to flash GSI, ROM for the Samsung Galaxy M20
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Current Stable Version: v1
Created 2019-03-05
Last Updated 2019-03-05
{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Generic System Image (GSI) : Github
Treble folder : Gdrive
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
amazing.
Awesome Bro. Nic work. Keep it up.
VoLTE is not working
harsinghal said:
VoLTE is not working
Click to expand...
Click to collapse
It will not work on any gsi
It work with m205fn?
kofa01 said:
It work with m205fn?
Click to expand...
Click to collapse
yes, it should work
prashantp01 said:
yes, it should work
Click to expand...
Click to collapse
it doesn't work, in TWRP i pres flash img and chosse system.img GSI but TWRP failed with errot 255...
maybe i doing wrong?
kofa01 said:
it doesn't work, in TWRP i pres flash img and chosse system.img GSI but TWRP failed with errot 255...
maybe i doing wrong?
Click to expand...
Click to collapse
On which gsi?
prashantp01 said:
On which gsi?
Click to expand...
Click to collapse
This is a problem with ROM. I tried to put the Pixel Experience, it started without problems.
But not work NFC.
On which ROM the NFC will work?
kofa01 said:
This is a problem with ROM. I tried to put the Pixel Experience, it started without problems.
But not work NFC.
On which ROM the NFC will work?
Click to expand...
Click to collapse
report it to pixel experience developer, with proper logs
T
This work on sm-m205g ?
isnu harajuku said:
This work on sm-m205g ?
Click to expand...
Click to collapse
yes it should work
AOSP and treble both did not work in the m205f version. It gets stuck in blootloder
My phone is stuck in boot screen after flashing the rom, can someone help me fix this issue? I flashed Phh-Treble 9.0
My phone model No. M205F
lifehacker03 said:
AOSP and treble both did not work in the m205f version. It gets stuck in blootloder
Click to expand...
Click to collapse
your M20 is already a trebled device
rafsun.khan said:
My phone is stuck in boot screen after flashing the rom, can someone help me fix this issue? I flashed Phh-Treble 9.0
My phone model No. M205F
Click to expand...
Click to collapse
take logcats and report to phh-treble developer
prashantp01 said:
take logcats and report to phh-treble developer
Click to expand...
Click to collapse
Any guide to get a logcat when the device is stuck at the android boot logo? Nothing shows up when I "adb devices" from PC.
Thanks but its official update original for m20
I'm mean wait to comes out the originally Android 9...
Or not coming.
Or update This Help me
Did someone sucsessfully install gsi rom on m20 ?
I tryed a couple of roms, allways bootloop
{
"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"
}
ArrowOS
ABOUT
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Tip: Select OEM -> Device,choose Arrow version, choose build type: "GAPPS" or "VANILLA" to download.
Read our blog article/post about:
* GAPPS and VANILLA variants
* Checking build integrity
ROM Source: https://github.com/ArrowOS
Kernel Source: source
XDA:DevDB Information
ArrowOS, ROM for the Xiaomi Redmi Note 4
Contributors
ganesh varma, kubersharma
Source Code: https://github.com/ArrowOS
ROM OS Version: Android 11
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest firmware
Based On: AOSP, CAF
Version Information
Status: Alpha
Created 2020-10-26
Last Updated 2020-10-26
WHAT WORKS?
Almost everything (Wifi, RIL, data, fingerprint, camera, flash, VoLTE (tested on Jio4G), bluetooth, tethering etc)
WHAT DOESN'T WORK?
SELinux is permissive
You tell me
Be sure to include a log : check how to
It's a fantastic rom. It all works perfectly. I only have one issue with the safety net of magisk.
But that's not a rom problem.
Thank you so much I'm excited
Today(27/10) I found out that the bluetooth calls They can't be heard. They have a very bad sound. I hope it is corrected in a future upgrade
Nice, thaks to dev.
Which recovery is recommended for flashing? Right now i'm using Orange Fox R11.
LiamLePew said:
Nice, thaks to dev.
Which recovery is recommended for flashing? Right now i'm using Orange Fox R11.
Click to expand...
Click to collapse
R11 are fine
Can´t flash GApps version. Phone reboot before finishing the installation. Try with Orange Fox R11 and TWRP, same thing.
LiamLePew said:
Can´t flash GApps version. Phone reboot before finishing the installation. Try with Orange Fox R11 and TWRP, same thing.
Click to expand...
Click to collapse
The GApps version zip, must be corrupt, cause Vanilla version, installed without issues.
LiamLePew said:
The GApps version zip, must be corrupt, cause Vanilla version, installed without issues.
Click to expand...
Click to collapse
Idk what happened but in my phone it installed just fine using twrp.
nikosss1 said:
Idk what happened but in my phone it installed just fine using twrp.
Click to expand...
Click to collapse
And mine, too.
In my case, phone power off just before finish the instalation, leaving the phone without system. Try with Vanilla and everything ends good.
LiamLePew said:
In my case, phone power off just before finish the instalation, leaving the phone without system. Try with Vanilla and everything ends good.
Click to expand...
Click to collapse
I had the same issue on my device. Have R11 recovery.
Which is the recommended GApps?
0
How can I use microg here to pass safety net test
Hotspot and tethering not working for me. It was working fine when I dirty flashed this over revenge OS. after clean flash it stopped working.
okchinmaya said:
I had the same issue on my device. Have R11 recovery.
Which is the recommended GApps?
Click to expand...
Click to collapse
I used FlameGaaps Full version.
---------- Post added at 03:34 AM ---------- Previous post was at 03:32 AM ----------
Seppppx said:
Just a reminder that using a ROM with permissive selinux is not a good idea.
https://android.stackexchange.com/q...elinux-is-in-permissive-mode-what-should-i-be
Click to expand...
Click to collapse
I suposed is why dev mention it in the beggining, so, the user decides to flash with this risk or not.
Hi guys,
Thanks dev from your work.!
I haven't made any changes for 3 years and I wouldn't want to go wrong.
Now I have lineageOS android 10 rom with TWRP recovery.
1.Reboot recovery
2.wipe system
3.wipe data
4.wipe cache / dalvik
5.flash ROM
6.flash gapps
7.flash magestik
8.reboot recovery
9.wipe cache / dalvik
10.reboot system.
Is these steps correct for the flash?
Do I have to flash the Twrp too?
Fix_ita said:
Hi guys,
Thanks dev from your work.!
I haven't made any changes for 3 years and I wouldn't want to go wrong.
[...]
Click to expand...
Click to collapse
Which version of TWRP do you have? Some of them may cause problems, so if you will have them, try to change recovery to other, eg. PitchBlack.
Atexor said:
Which version of TWRP do you have? Some of them may cause problems, so if you will have them, try to change recovery to other, eg. PitchBlack.
Click to expand...
Click to collapse
Thanks for the reply.
The twrp version is 3.3.1.0
Where can i find the pitchblack recovery?
I will definitely do a nandroid with twrp in case I want to go back. How should I behave?
Fix_ita said:
Thanks for the reply.
The twrp version is 3.3.1.0
Where can i find the pitchblack recovery?
I will definitely do a nandroid with twrp in case I want to go back. How should I behave?
Click to expand...
Click to collapse
I prefer KudProject edition instead of original TWRP (original caused me problems with installing newer ROMS): https://forum.xda-developers.com/re...recovery-pitchblack-recovery-project-t4120269
PitchBlack Recovery is there (based on TWRP), but I am not sure whether it support TWRP backups.
https://forum.xda-developers.com/re...overy-kudproject-s-unofficial-twrp-3-t4107121
You can flash firstly KudProject, make a backup and try to install latest ROM. Also you said that you weren't doing any canges for 3 years. You should update firmware because newer ROMS may be incompatible with older firmware and cause problems with WiFi or mobile data. You will find it there: https://xiaomifirmwareupdater.com/firmware/mido/
Thanks @Atexor.
I want to change rom because with my rom that I currently have lineageOS17.1 unofficial I have problems making the video call. It goes into a loop and I have to restart the device
{
"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, 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.
This is an unofficial LineageOS 20 build for the global version of Xiaomi Mi 9 SE (grus).
Requirements
Required firmware version is MIUI V12.5.1.0.RFBMIXM.
Required TWRP is provided in this post (see below) that returns the correct 'ro.product.device'.
Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed.
Twrp can't decrypt data in android 13, so you need to install updates via adb sideload.
Known Issues
Please tell me
Instructions
Flash TWRP recovery via fastboot
Boot to TWRP recovery (Vol UP + Power)
Format Data (backup sdcard before format) if MIUI was previously installed
Flash ROM (lineage-*.zip) via adb sideload (Advanced -> ADB sideload)
Flash Gapps (MindTheGapps-13.0.0-arm64 is recommended) via adb sideload
Reboot
Enjoy!
NOTES
Safetynet can pass on this ROM (without magisk).
Regardless of the actual security update date, android security update is always displayed as 2021-04-01 for safetynet passing.
Recommended camera app is GCam Port: BSG 8.1 that can handle all of three lenses.
Downloads
All: https://androidfilehost.com/?w=files&flid=327360
LineageOS 20: lineage-20.0-20230621-UNOFFICIAL-grus.zip
twrp: twrp-3.7.0_9-ky-grus.img
firmware: fw_grus_miui_GRUSGlobal_V12.5.1.0.RFBMIXM_c04478d703_11.0.zip
Sources
https://github.com/kyasu/android_device_xiaomi_grus
https://github.com/kyasu/android_kernel_xiaomi_sdm710
https://github.com/kyasu/android_vendor_xiaomi_grus
Contributors
LineageOS team, SDM710 Development team, kyasu
ROM OS Version: Android 13
ROM Kernel: Linux 4.9
Based On: LineageOS
Status: Stable
Created 2022-10-19
Last Updated 2023-06-21
Reserved
Thank you so much Kyasu for your hard work!
I think I will wait a few weeks before flashing the new a13 build, just to see if it's stable enough to "daily drive" it.
Clean flash recommended?
xchamelionz said:
Thank you so much Kyasu for your hard work!
I think I will wait a few weeks before flashing the new a13 build, just to see if it's stable enough to "daily drive" it.
Clean flash recommended?
Click to expand...
Click to collapse
Dirty flash over lineageos 19.1 is OK. I think this build is stable enough.
Signature Spoofing?
Build working very smooth without major issues.
Only thing i noticed, android auto not working anymore with my skoda. But this could also be caused by android auto..
Cheers
kyasu said:
Dirty flash over lineageos 19.1 is OK. I think this build is stable enough.
Click to expand...
Click to collapse
Could I update from the official LineageOs build (https://forum.xda-developers.com/t/rom-sv2-official-lineageos-19-1-for-xiaomi-mi-9-se-grus.4447307/) ?
thanks again kyasu. my fav dev)
divinae said:
Could I update from the official LineageOs build (https://forum.xda-developers.com/t/rom-sv2-official-lineageos-19-1-for-xiaomi-mi-9-se-grus.4447307/) ?
Click to expand...
Click to collapse
Formatting data is required, if you come from the official one.
I updated from your 19 and it works well but if I install magisk 25.2 from recovery the phone remains in infinite boot, any solution?
Humpfrey said:
Build working very smooth without major issues.
Only thing i noticed, android auto not working anymore with my skoda. But this could also be caused by android auto..
Cheers
Click to expand...
Click to collapse
Did you solve android auto problem? For me it's a blocker for upgrading
This firmware works like a champ. And it has a ver goog battery life too. Thanks Kyasu.
buteo said:
Did you solve android auto problem? For me it's a blocker for upgrading
Click to expand...
Click to collapse
Nope, I didnt.
Thank U! And I found a BUG:
I had change the option of 'Display cutout' in developer options, switch to another and switch back to default, repeated several times. Then I can see sawtooth in top round corner, nnusual color pixels can also be seen on the lock screen's top round concer. I try all what can I do to fix it: system option, AOSP mods, some magisk module... All of them are failed.
After wipe data in TWRP and reset all OS, it come back normal.
I found the real reason: turn off dark mode, then top corners of lock screen will show some color pixels.
hxlh50k said:
Thank U! And I found a BUG:
I had change the option of 'Display cutout' in developer options, switch to another and switch back to default, repeated several times. Then I can see sawtooth in top round concer, nnusual color pixels can also be seen on the lock screen's top round concer. I try all what can I do to fix it: system option, AOSP mods, some magisk module... All of them are failed.
After wipe data in TWRP and reset all OS, it come back normal.
Click to expand...
Click to collapse
how did you install magisk? I have tried all v25 versions from recovery but I get a bootloop.
fragga82 said:
how did you install magisk? I have tried all v25 versions from recovery but I get a bootloop.
Click to expand...
Click to collapse
Just adb sideload latest magisk.apk from github.
hxlh50k said:
Just adb sideload latest magisk.apk from github.
Click to expand...
Click to collapse
Thanks
I try
Humpfrey said:
Nope, I didnt.
Click to expand...
Click to collapse
for flashing did you change the package of gapps?
sickeye said:
for flashing did you change the package of gapps?
Click to expand...
Click to collapse
Sure
Humpfrey said:
Sure
Click to expand...
Click to collapse
weird, clean flash or dirty from last android 12.1 build?