Develop Bugs

How to skip(bypass) Google sign-in NSTV Pro 2019 with any firmware versions!

*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana

Wow you know how long I have been waiting for this?
I did not test it yet but I will soon, hopefully today. Will work with both Dev image and regular image?
Thanks @mrhamed
By the way, Do you know if this method also works on a 2017 Pro 16gb version?

This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
{
"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"
}

mrhamed said:
This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
Click to expand...
Click to collapse
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?

cHECKjAM said:
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?
Click to expand...
Click to collapse
It's my device screen.
I don't like to lock-bootloader, so AI not works at this time, I'm testing "MagiskHide Props Config" to try hide the booloader-state and I hope enable AI with unlocked bootloader:
https://forum.xda-developers.com/showpost.php?p=83972471&postcount=4626

@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
What Im hoping is that bluetooth will work. Because when I flash the dev image earlier and used the ↑ ↑ ← ← method and choose skip setup, bluetooth has not been working. Can not find any bluetooth devices when i search for them. The same problem on 2 different devices.
So now Im trying this method right now to see if it works better.
If it does not work I need to try the the none-developer image instead.
However this method seems to bootloop.. Im not sure whats happening.. I see the nvidia logo and then reboots again and same..
---------- Post added at 08:31 PM ---------- Previous post was at 08:26 PM ----------
The steps I took:
I boot to TWRP first through bootloader.
Format and wipe all partitions basically making it totally fresh.
Then I boot to bootloader and run the flash-all without the reboot continue.
Then I boot back to TWRP and mount system.
Then pull the file and append the line, then push it back.
Then reboot to system.
Now bootloop...
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..

cHECKjAM said:
@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..
Click to expand...
Click to collapse
-Remove "ro.setupwizard.mode=DISABLED" from (end of file: system/build.prop).
-Try to bootup completely and setup ethernet with internet connection. then power off device.
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
I hope it works.

If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk

mrhamed said:
If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk
Click to expand...
Click to collapse
I dont get any method working..
The other thread with the "how to root" is lacking so much details and steps I have no idea how it is supposed to be done..
So I tried flashing the totally default dev image 8.2 . Everything boots and goes in to the setup mode
From there if I unplug ethernet I cant go anywhere.. I then reboot to bootloader and from there boot in to twrp.
Mount the system and modify the prop file as you said. then reboot to system again. Still cant bypass setup.
I also tried the exact same with flashing the vb skip image instead of default vbmeta
same result..
And it is painfully long process and every new try is a pain.
Can you please buddy please:
Write a step by step n exactly how to from scratch:
Flash 8.2 image + root + bypass google setup entirely..

Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Hey buddy..
I have not had time until now to try this again.. My shield has been semi-bricked since last try and have not been able to use it until now. So maybe can look in to getting this working during the vacation.
Have you gotten any better idea on how exactly to make this work? I followed all your steps last time and failed twice..

Is there anyone out there except for @mrhamed that has got this method working?
If so please share any real tutorial/steps/guide or whatever that can help.. thanks

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Are you MIA?

EDIT: oops. wrong thread.

8.2.3 - 2019 Pro here, removing ethernet works like a charm.

LifelessLife said:
8.2.3 - 2019 Pro here, removing ethernet works like a charm.
Click to expand...
Click to collapse
Maybe you can explain a bit more?

mrhamed said:
*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana
Click to expand...
Click to collapse
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
I think 9.0.0 broke alot of things we have been taking for granted. if not using a Google account is that important to you, best to go ahead and revert back for now.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system

mrhamed said:
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
Click to expand...
Click to collapse
Just pulled the build.prop again and the setupwizard was still disabled. Did a reboot and still requires Google sign in. Guess its back to 8.2.3.

I have no more idea and it should works!
add more options to build props:
ro.setupwizard.network_required=false
ro.setupwizard.wifi_required=false
ro.setupwizard.enable_bypass=1
ro.setupwizard.mode=DISABLED

[GUIDE] 8.2.3 + Magisk root + MagiskHide + TWRP

Based on the work done in https://forum.xda-developers.com/t/how-to-root-and-install-magisk-on-nstv-2019-pro-v8-2-0.4189567/
User friendly guide written for Windows. Bash script for Linux flashing edited as well, but guide is focused on Windows users.
Enhanced upscaling is confirmed to work, have not been able to confirm AI upscaling (Unsupported content). Dolby Vision unconfirmed as I do not yet have a TV that supports it. If someone can verify if this works or not I will update this post accordingly.
Prerequisites:
USB-A male to USB-A male cable.
USB mouse.
USB drivers: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Android SDK: https://developer.android.com/studio/releases/platform-tools
Premade archive: https://drive.google.com/file/d/1XDzQyWviwVbjxNRsWJ8pG-HPSKW-Kzyl/view?usp=sharing
Unlocking the bootloader:
Go into Settings > Device Preferences > About.
Select "Build" several times until "You are now a developer!".
Go into Settings > Device Preferences > Developer options.
Activate USB debugging.
Connect one end of your USB-A to USB-A cable into the port furthest away from the HDMI on your SHIELD TV and the other into your computer.
Open a command shell (command prompt, powershell, bash, etc) on your computer.
Navigate to where you extracted the Android SDK.
Run command:
adb devices
Confirm that your device appears in the list of devices. If not this may be due to:
USB cable not connected properly. Check cable.
Device not recognized. Reinstall drivers/restart computer. Generic Android USB drivers may work if NVIDIA doesn't.
Run command:
adb reboot bootloader
Wait for fastboot to start.
Run command:
fastboot devices
Confirm that your device appears in the list of devices. If not see above reasons.
Run command:
fastboot oem unlock
Flashing:
On your computer navigate to where you have extracted the archive from the post.
Run command:
flash-all.bat
If all goes well you should be rebooted into TWRP recovery once the procedure is done.
Connect your USB mouse to the USB port closest to the HDMI port on your SHIELD TV.
Slide to unlock.
Go into Mount.
Select "Enable MTP".
Move "Magisk-v23.0.zip" from the downloaded archive to your SHIELD TV.
Select "Disable MTP".
Go into Install.
Select "Magisk-v23.0.zip" and install it.
Go into Reboot.
Select "System".
Getting Magiskhide to work:
Install Termux from Google Play.
Open Termux and run:
su
cat >/data/post-fs-data.d/bootfix-post.sh
resetprop ro.boot.verifiedbootstate orange
Press Ctrl+d.
Run:
chmod +x /data/post-fs-data.d/bootfix-post.sh
cat >/data/service.d/bootfix-service.sh
resetprop ro.boot.verifiedbootstate green
Press Ctrl+d.
Run:
chmod +x /data/service.d/bootfix-service.sh
Open Magisk (Settings > Apps > See all apps > Magisk > Open)
Select the shield icon on the bottom bar.
Enable MagiskHide
Reboot system
ALL DONE!
Sources of the premade archive contents are the following:
Android SDK: https://developer.android.com/studio/releases/platform-tools (fastboot)
The following Shield ROMs from https://developer.nvidia.com/gameworksdownload#?search=2019&tx=$additional,shield:
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.1.0 (vbmeta_skip.img)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.2.0 (mdarcy.dtb.img)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.2.3
Latest TWRP recovery from https://twrp.me/nvidia/nvidiashieldandroidtv2019.html (recovery.img)
Latest Magisk from https://github.com/topjohnwu/Magisk/releases

reboot to recovery command fails with error and doesnt reboot to twrp. manually booting twrp from fastboot via fastboot boot recovery.img works

can someone explain the "MagiskHide" section of the guide? i dont have those .sh files present in /data/ . Should i just create them with the resetprop commands as the content? i just dont see where you even got those from

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes

Can this work on the 2017 model?

Is this the most updated guide also for the magisk hide section whats the easiest way to copy and paste this all in terminal .

albinoman887 said:
View attachment 5402781
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes
Click to expand...
Click to collapse
Did you get around to make that guide?
Im struggling getting around the cts check.

albinoman887 said:
View attachment 5402781
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes
Click to expand...
Click to collapse
Did you get around to make that guide?
Im struggling getting around the cts check.

bolme123 said:
Did you get around to make that guide?
Im struggling getting around the cts check.
Click to expand...
Click to collapse
Ahh crap... I'll be totally honest I completely forgot . I'll get that done by the time I go to bed today. . to be honest though I think what might have done it was I changed my device fingerprint using MagiskPropsConfig module and chose the one for sheid that's included with your IPTV service ... Other than that I just made sure there was no like things exposed that didn't need to be and removed

albinoman887 said:
Ahh crap... I'll be totally honest I completely forgot . I'll get that done by the time I go to bed today. . to be honest though I think what might have done it was I changed my device fingerprint using MagiskPropsConfig module and chose the one for sheid that's included with your IPTV service ... Other than that I just made sure there was no like things exposed that didn't need to be and removed
Click to expand...
Click to collapse
Thank you man, you nudged me in the right direction.
I was able to successfully pass the ctsCheck, and i accumulated new knowledge, thanks man!
Have a blessed day.
Before i go along with my day, did you have any success with LSPosed?
I''m gonna check now if i'm able to disable the SECURE_FLAG without tripping the SafetyNet.

bolme123 said:
Thank you man, you nudged me in the right direction.
I was able to successfully pass the ctsCheck, and i accumulated new knowledge, thanks man!
Have a blessed day.
Before i go along with my day, did you have any success with LSPosed?
I''m gonna check now if i'm able to disable the SECURE_FLAG without tripping the SafetyNet.
Click to expand...
Click to collapse
has anyone gotten AI- Upscaling to work ?

tokoam said:
has anyone gotten AI- Upscaling to work ?
Click to expand...
Click to collapse
no just the enhanced

Nvidia Shield TV pro 2019 :
I did all the steps and I have this error
I start again several times the same problem
Pasteboard - Uploaded Image
Simple and lightning fast image sharing. Upload clipboard images with Copy & Paste and image files with Drag & Drop
pasteboard.co
in start there is the following message...
Photobox | Online Photo Printing & Personalised Photo Gifts
Make stories from your photos. Print photos online or create personalised gifts with Photobox, the photo specialists. Photo Books, Prints, Canvases, more.
www.photobox.co.uk

So, any idea what to do when having diligently followed along and the result is those errors and now a Shield that can't boot and doesn't respond to ADB/Fastboot calls...
I can't believe I just blindly followed along and now my favourite thing in existence is bricked. I use it literally 24/7. Any ideas?

jamiethomaswhite said:
So, any idea what to do when having diligently followed along and the result is those errors and now a Shield that can't boot and doesn't respond to ADB/Fastboot calls...
I can't believe I just blindly followed along and now my favourite thing in existence is bricked. I use it literally 24/7. Any ideas?
Click to expand...
Click to collapse
its not bricked, and you didnt follow along else you wouldn't be in your current state. I literally just did this on my 2019 shield pro coming from the private beta without issue. The OP instructions need a few updates but most of those steps you should be familiar with anyway if you're going to be modding your devices
I lied, infinite loop, seems some derpy protection is getting tripped
0bin - encrypted pastebin
0bin is a client-side-encrypted alternative pastebin. You can store code/text/images online for a set period of time and share with the world. Featuring burn after reading, history, clipboard.
0bin.net

aouamed said:
Nvidia Shield TV pro 2019 :
I did all the steps and I have this error
I start again several times the same problem
Pasteboard - Uploaded Image
Simple and lightning fast image sharing. Upload clipboard images with Copy & Paste and image files with Drag & Drop
pasteboard.co
in start there is the following message...
Photobox | Online Photo Printing & Personalised Photo Gifts
Make stories from your photos. Print photos online or create personalised gifts with Photobox, the photo specialists. Photo Books, Prints, Canvases, more.
www.photobox.co.uk
Click to expand...
Click to collapse
its because Android is retarded and the script needs modified. After that error it should have booted into system setup, simply reboot into bootloader and `fastboot boot recovery.img` then continue onto installing magisk

Thank you for your reply...
I succeeded rooted my NSTV 2019 Pro v8.2.3
NVIDIA SHIELD ANDROID TV 2019 Pro Recovery OS Image 8.2.3
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.1.0 (vbmeta_skip.img)
TWRP : twrp-3.5.2_9-0-mdarcy.img
Magisk : Magisk v23.0 'beta'
Tested :
Safetynet checks pass fine...
reboot with magiskhide without probleme script 'bootfix-post.sh' 'bootfix-service.sh'
Demo mode work only Enhanced Mode
Other work well ...
Thank xda

Any solution for unlimited loading android splashscreen after enabled MagiskHide in Magisk after reboot shield?

Enable MagiskHide :
open PowerShell :
adb shell
su (confirm permission with remote control )
cat >/data/adb/post-fs-data.d/bootfix-post.sh
resetprop ro.boot.verifiedbootstate orange
Press Ctrl+d:
chmod +x /data/adb/post-fs-data.d/bootfix-post.sh
##############################
cat >/data/adb/service.d/bootfix-service.sh
resetprop ro.boot.verifiedbootstate green
Press Ctrl+d:
chmod +x /data/adb/service.d/bootfix-service.sh
Reboot system

do i need to have the nvidia controller/gamepad for this? everything that needs to adb or fastboot, so far, works but ill get to a screen and itll ask to confirm something and so on. except i dont have the gamepad. if you guys say i need one, of course ill go buy one but in the mean time, if not, how are you going through it?
edit:
also, does 8.2.0 or 8 .2.3 matter? the first time, i did do it on 8.2.3 but had to restart because i didnt have a gamepad.

[ROM][UNOFFICIAL][A10][F500,LS991,H81x,US991,VS986] LineageOS 17.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
​**** These builds are for both: official unlocked and UsU'd devices **** ​UsU? http://bit.do/unlockg4​
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #8 for how to upgrade your bootloader stack witbout lgup).
.... and for your convenience I have alternatively created TWRP flashable files for that !!!! (click)
in particular that means this thread is for:
F500 (UsU'd)
H810 (UsU'd)
H811
H812 (UsU'd)
H815 (official unlocked or UsU'd)
H819 (UsU'd)
LS991 (UsU'd)
US991 (UsU'd)
VS986 (UsU'd)
Latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything!
Installation
This single very first step is for UsU'd devices only:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N might not work)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Optional (f-droid is already included): Flash GApps (10.0 - ARM64) if you like to use google apps
Optional (if you want root): Flash Magisk (ensure you read FAQ #1 when using Magisk though)
Boot (will take a bit on first boot!!!)
Enjoy
Features
Pure LineageOS ROM experience
F-Droid included (Open Source alternative to Google Play)
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
It wasn't until Pie felt stable enough for everyday use that I released it publicly, but I still can't test everything on my own, so a lot of things only show up after a release.
So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Download
Get your builds from my leech server
https://leech.binbash.rocks:8008/lineage/17.1
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
see commits at github or ideally you join my matrix or telegram groups (see topic "Support")
Credits
LineageOS
aoleary (cam fix, bunch of fixes needed for a10 bringup)
DevUt (cam fix, being a punch ball)
tullyp (cam fix, vs986 fixes & tests)
and more..
Sources
build manifest
Support
Post in this thread
Quick support by [Matrix] || build notification by [Matrix]
Quick support by Telegram: sfX_Android || build notification in sfX_ci

Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it.
Often selinux can cause issues so try that at very first:
Code:
adb shell
su
(or "adb root" when enabled in developer settings)
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If that does not solve your issue follow the logcat GUIDE to provide a valid log depending on what your issue is.
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official LOS builds?
TL;DR answer is: no.
Background:
LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
For sure we do not met all and the most problematic one will be the kernel reqs as do provide a good battery life and a fast kernel kessaras had made unacceptable (for LOS) changes regarding several parts of that requirement topic. So a new kernel (branch) is needed to remove all the improvements we made which are not accepted. This process alone can take weeks (if you do not want to loose every good thing here). A much easier approach here would be to build a "just working" LOS stock kernel without any improvements and fixes and tell everyone: "Flash LOS, then a TITAN kernel afterwards". So while that might be the easier approach it will nevertheless take time to do that kernel and include the reqs + sec patches to the day.
Besides that a bit work is needed to fulfill some of the others like that.
Other then that and that is one of the most important things here:
Even when the device was accepted going official in the past (14.1... long time ago..) an incredible amount of changes happened to get oreo and now pie running. All these will be put to the test. Which actually means every commit we made will be discussed (worst case, yea, but ..) and changed. That can be from a simple "the commit message is wrong" to "pls re-write the code here". You maybe get an idea that this process is nerve-wracking (for me) and costs a lot of my free time.
Before RIL has been fixed (which had happened in the end of June 2019 first) it would have been impossible, I guess.
Now the base is fine, we could put a big amount of time into going to official to get finally ........ yea, what?
Well.. I would free resources on my build and leech server (I don't care - atm)
I would save bandwidth (I don't care - atm)
I would not need to tamper around anymore with (i.e jenkins) build issues (I don't care - atm)
you?
you would get a (LOS signed) build with a slow kernel, bad battery life and all the goodies missing... unless I build LOS kernels to bring those things back.
ok but to be honest. I can fully understand that request and I would feel better by myself when I were you. You do not know me so are my builds trustworthy ? Who knows. I could be a bad guy. :fingers-crossed:
Besides that I wrote above "I don't care - atm" so that might change in the future right? Correct.. there is no guarantee how long I can provide new builds or offer them on my leech server. There is nothing at the horizon that this might change soon but who knows? I can say that I am incredible happy with my OnePlus 6T and - believe it or not - I run STOCK OxygenOS here.. Why? It is just enough for me. So no need to do any dev there - which means all my dev time is still going here - to the G4. It is also a personal project to learn stuff around the Android eco system and woa.. who knows maybe Q came one day to the G4 as well..
... and yea official builds would give you some kind of guarantee that builds will happen - while that might change with my unofficial builds some day.
So.. as said in the TLDR above: No I personally do not have any plans in going official for the described reasons.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
Q #04: Google Play shows that my device is not "certified" - how can I fix that?
First of all you must be on the latest build. I fixed that from the latest July (2019) builds on.
If your issue persists click here to proceed:
The second thing is you must not be rooted by the LOS root addon (afaik). Magisk has its own protections to ensure you stay certified but I hadn't the time to test the LOS root-addon.
You also need to know that google play remembers your devices last state so if you are on the latest build and still having that issue do this and it will be certified again:
android settings -> apps -> find play store -> clear data (yes data, not cache) -> reboot -> open play store -> wait 2..5 minutes -> check certified state again
Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
You need a ROM with pstore fully enabled and working (pstore = debug kernel panics/oops happened in a ROM)!
All builds starting from 2019-08-15 on support pstore due to: commit#1, commit#2, commit#3
This is a 2-site change if you want to make use of it in TWRP you must install the latest TWRP "PREVIEW" release as well (TWRP is only able to show pstore logs when the ROM is able to write them so I needed to fix pstore in the ROM first (see above commits #1 + #2 )).
Besides those 2 patches these kernel configs were set: PSTORE
You can check if a ROM does support writing pstore logs by:
as soon as possible on a fresh boot:
Code:
adb shell
dmesg | grep "ramoops|pstore"
Code:
[ 0.000000] cma: Found [email protected], memory base 0x000000001fe00000, size 2 MiB, limit 0xffffffffffffffff
[ 0.000000] cma: CMA: reserved 2 MiB at 0x000000001fe00000 for ramoops_mem
[ 0.200846] cma: Assigned CMA region at 0 to ramoops.78 device
[B][ 3.957553] console [pstore-1] enabled
[ 3.957939] ramoops: attached [email protected], ecc: 16/0[/B]
[ 3.958079] drv probe : 200 ramoops 3744
[ 6.262463] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts
or (if you are not fast enough) this ensures mostly the same check:
Code:
adb shell
ls -la /dev/pmsg0
Code:
crw-rw-rw- 1 camera camera 254, 0 2015-01-05 04:54 /dev/pmsg0
If you get no output your ROM does not support pstore logs.
From now on when you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM):
1) reboot (without taking out the battery!) to either TWRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Q #07b: How can I provide a clean boot log?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?! Read here how:
If you don't mind you can use lgup as long as you do not have an UsU'd device! For UsU devices follow the UsU FAQ #20 instead of this one!!!!!
If you just wanna upgrade the bootloader stack without loosing data: Check the OP of this thread because:
it has a link to TWRP flashable files for updating your bootloader with 1 click ..
Anyways if you still want to go on doing it manually instead of the easy way then:
Download a KDZ of your device model.
Keep in mind that there a frankenstein devices out there (means refurbished devices with mixed hardware inside so you think u have model XXX as it was shown in Android but the mainboard is NOT the same!).
How to identify a Frankenstein device? Read FAQ #21 in the UsU thread.
IMPORTANT: Check the ARB of that KDZ (SALT v3.11 will show the ARB of a KDZ on extract!) - If you are unsure - DO NOT PROCEED. you can easily hard brick your device if!
Extract that KDZ with SALT - DO NOT USE ANY OTHER TOOL FOR EXTRACTING! The known windows tools like LG Firmware extract does not extract what we need here and not in the way we need it! So do not use that! You have been warned..
Open a terminal in the directory where you SALT backup before flashing UsU (or your extracted KDZ) is.
Then put your device in fastboot mode and type these commands (you have another file extension? read FAQ #24 of the UsU thread):
Again this guide is NOT for UsU'd devices!!!
Code:
fastboot flash aboot aboot.bin
fastboot flash factory factory.bin
fastboot flash hyp hyp.bin
fastboot flash modem modem.bin
fastboot flash pmic pmic.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
Alternative with TWRP (if the above fastboot cmds work for you no need to do this!):
Again this guide is NOT for UsU'd devices!!!
Code:
Boot TWRP
adb push factory.bin /tmp/
adb push hyp.bin /tmp/
adb push modem.bin /tmp/
adb push pmic.bin /tmp/
adb push rpm.bin /tmp/
adb push sbl1.bin /tmp/
adb push sdi.bin /tmp/
adb push sec.bin /tmp/
adb push tz.bin /tmp/
adb push aboot.bin /tmp/
adb shell sync
adb shell "dd if=/tmp/factory.bin of=/dev/block/bootdevice/by-name/factory"
adb shell "dd if=/tmp/modem.bin of=/dev/block/bootdevice/by-name/modem"
adb shell "dd if=/tmp/hyp.bin of=/dev/block/bootdevice/by-name/hyp"
adb shell "dd if=/tmp/pmic.bin of=/dev/block/bootdevice/by-name/pmic"
adb shell "dd if=/tmp/rpm.bin of=/dev/block/bootdevice/by-name/rpm"
adb shell "dd if=/tmp/sbl1.bin of=/dev/block/bootdevice/by-name/sbl1"
adb shell "dd if=/tmp/sdi.bin of=/dev/block/bootdevice/by-name/sdi"
adb shell "dd if=/tmp/sec.bin of=/dev/block/bootdevice/by-name/sec"
adb shell "dd if=/tmp/tz.bin of=/dev/block/bootdevice/by-name/tz"
adb shell "dd if=/tmp/aboot.bin of=/dev/block/bootdevice/by-name/aboot"
Download this verify tool to ensure the flashing was successful: [ATTACH]4687157[/ATTACH] ([URL="http://leech.binbash.it:8008/misc/verifyflash.zip"]mirror --> verifyflash.zip[/URL])
Usage:
extract verifyflash.zip
adb push verifyflash.sh /tmp/
adb shell chmod 755 /tmp/verifyflash.sh
adb shell /tmp/verifyflash.sh
Read the output of the flashing on the screen and in your terminal. Do NOT flash anything else! Just the above - but ALL of the above! (if you miss a single file you will HARD BRICK)
If something is failing do NOT continue and try to re-do the above commands. if it still fails write in this thread or better come into IRC (when between Monday and Friday)!
If something failing here it WILL brick your phone.
Q #9: A life without Google?! Read here how:
A life without Google ? Is that possible ? ...and why you should consider it ?
So why? That's easy to answer and if those are worth it depends totally on your personal needs:
1) BATTERY. Google services are draining a LOT of your battery, so to get the most out of your battery you should abandon Google gapps
2) PRIVACY. Almost all Google apps phoning home to Google! You don't care about that? You really should. You have nothing to hide? Oh dear believe me you have no idea how much of your private data you do NOT want to share. Keep also in mind that you give your private data not to a company only , there are always humans behind and what they do.. You do not believe me? Read on
BREAKING NEWS:
You can go on with the following steps or simply head-over to /e/ OS which is LOS but completely Google-Free + microG fully working pre-installed:
check it out here!
WARNING:
The last build supporting this spoofing method was 20210307. Everything later has that patch removed. Sorry for any inconvenience but maintaining that patch took more time then thought and for those who really care about privacy there is now /e/ OS available containing full microG support. I will leave the instructions here for those who cannot or do not want to switch to /e/ OS.
So if you feel one or both reasons might fit your personal needs here are some first steps to go (if you do NOT want to switch to /e/ OS):
1) all my builds come with FDroid which is a special app store containing just free open-source apps. As this might be a very limited I recommend to install Aurora from here which is a frontend for Google play. So search in FDroid for "Aurora Store" and let it install. Start Aurora and choose anonymous!!! and you can install everything from play as before.
2) install the microG repo in FDroid. Just open that link from your G4 and it will install the repo:
https://microg.org/fdroid/repo?fing...EB6DAB39B73157451582CBD138E86C468ACC395D14165
3) due to the fact that many apps depends on Google services as backend you need to do 2 things now:
a) developer options -> scroll down to signature spoofing and enable it *(read FAQ #11 why)
b) Download the current stable "Services Core" apk from here: https://microg.org/download.html and install it like that:
Code:
adb install com.google.android.gms-[REPLACETHIS].apk
c) if you have root:
Code:
adb shell
su
mount -o remount,rw /system
exit
adb push /tmp/com.google.android.gms-[REPLACETHIS].apk /system/priv-app/GsmCore.apk
if you do not have root, boot to TWRP now and mount system, then:
Code:
adb push /tmp/com.google.android.gms-[REPLACETHIS].apk /system/priv-app/GsmCore.apk
4) Install a location backend provider to make location services work without Google (yea Google is spying you..).
There are several available, just search for them in F-Droid:
Apple UnifiedNlp Backend uses Apple’s Wifi database.
LocalGsmNlpBackend uses downloaded GSM Cell data (local)
LocalWifiNlpBackend uses (on-device generated) WiFi data (local)
Déjà Vu Location Service uses (on-device generated) WiFi + GSM Cell data (local) * recommended
MozillaNlpBackend uses Mozilla Location Services * recommended
Radiocells.org UnifiedNlp Backend uses Radiocells.org
Also install a reverse location backend:
- e.g. NominatimNlpBackend (currently the only I know)
5) Now it's time to configure microG. Go in the app drawer and open microG settings:
you will be prompted or a notification is showing for setting permissions, go through all of them and choose allow.
UnifiedNlp settings:
- Configure the location backend service (choose the one you installed in step 4)
- Configure the address lookup backend (choose the one you installed in step 4)
Go back to the main screen of microG:
Choose Self-Check:
- Tap "System grants signature spoofing permission" and you wou get a request for allowing that (which you should do..)
- Tap Battery optimizations ignored to ensure microG is function properly
- Ensure "UnifiedNlp is registered in system" is checked (if not repeat the above steps for pushing the APK to system/priv-app)
- Ensure "Location Backends" is checked (if not repeat UnifiedNlp settings above)
Read the installation wiki for microG and install whatever else you might need:
- https://github.com/microg/android_packages_apps_GmsCore/wiki/Installation
6) reboot & re-do the self-check in microG settings
7) ensure the location service is *NOT* set to GPS-only (for LOS that means enable battery saving)
8) some general things now:
you might need to switch to alternatives sometimes. I use Waze instead of Google maps even though Google would work (but I don't like the Google spys). I use FairEmail as I love my privacy and supporting open-source. Usually you can find always an alternative, often paid apps offer activations and buying without Google play and that is often even cheaper (e.g. AquaMail costs 39€ on play and 30€ on their website etc).
There is one thing which really hurts me when it comes to gapps-less life: no smart lock. I really enjoyed it but for me the both reasons above have more weight then this.
So as you can see a life without Google has its advantages but also some changes are needed. If it's worth it depends on you. I can just recommend it
Q #10: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #11: I'm scared about that microG , I don't want to expose my phone so is this LOS version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my LOS is different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always. That's what I don't like.
I want the user to decide if he wants to take the risk or not and not exposing a feature for everyone even when they don't need it.
That's why the user must enable it explicitly in developer options before it gets activated (as described in FAQ #9).
All details of the implementation and why can be found here:
https://github.com/steadfasterX/android_signature_spoofing
https://github.com/Suicide-Squirrel/issues_pie/issues/30
Q #12: The ROM is lagging and/or the device gets very hot/warm, what can I do to help fixing that?
Ensure you read and understand about the ILAPO first.
If you encounter any overheat or lagging issues follow this:
Code:
adb shell
logcat -b all -d | egrep -i "thermal|kill" > /sdcard/Download/log.txt
ps -A >> /sdcard/Download/log.txt
free -m >> /sdcard/Download/log.txt
logcat -b crash -d >> /sdcard/Download/log.txt
exit
adb pull /sdcard/Download/log.txt
Share the log.txt as an attachment of your reply (bc txt is fine for that) or - as usual - by your favorite paste service
Q #13: I have graphic glitches / issues, what can I do?
My builds using skiaGL instead of OpenGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
Is there any fix for skiaGL coming? No, details here .
To check if your current ROM version is using skiaGL do this:
Code:
adb shell getprop debug.hwui.renderer
If you get an empty result it means skiaGL is active.
If for any reason you wanna go back and enforce OpenGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer opengl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=opengl" >> /system/build.prop
sync
reboot

Reserved

Hooray​
Special credits and thanks to @aoleary , @tullyp and @DevUt (and well me..) we now see Android 10 coming to the G4! We had A10 running since 1 and a half year already but were not able to fix the camera. Due to the never ending tests by @tullyp and @aoleary plus @DevUt 's C knowledge they finally fixed that camera! That was a very long journey until now but hey here we are! Without @tullyp we might never seen this coming and he also was a great help when it comes to vs986 fixes and tests - so thanks again dude
TL;DR:
praise these guys
LOS 17.1 is very stable imho and well almost everything should work. Due to the camera issue we stopped working on other more minor issues (like NFC etc) but I still wanted to release LOS in the current state. It is not enforcing atm but I know you guys usually do not care anyways all that is on the todo list and might come anytime.
Check out all current known issues here
Jenkins has been setup now with LOS 17.1 and you can always find information and the current build state here
Other then that: have fun and consider joining my channels if you have any questions or need help.
Cheers
sfX

Greetings, sfx, everyone else.
Updated with full wipe from PIE. *
Seems a lot faster. Fantastic job.
* Quick question, is encryption working? Had to do full wipe because A10 was not accepting my encryption password from Pie.
Regards. Thank you very much for this breakthrough in our older phone.

hteles said:
Greetings, sfx, everyone else.
Updated with full wipe from PIE. *
Seems a lot faster. Fantastic job.
* Quick question, is encryption working? Had to do full wipe because A10 was not accepting my encryption password from Pie.
Regards. Thank you very much for this breakthrough in our older phone.
Click to expand...
Click to collapse
pls see the OP and here 1 post above yours:
tip: check out "untested core features/functionalities"

Hey.
Will try soon later to encrypt the phone. Just downloaded all my Spotify playlists a few hours ago so i can ear music while working.
My G4 is my "music center" , no SIM is inserted. Auto Brightness it is working.
Don't know about the others unknowns ( Hotspot, calls .. )

can i use 4 core kernel boot on this rom?

theartanis said:
can i use 4 core kernel boot on this rom?
Click to expand...
Click to collapse
You can with any ROM . Just follow the x cores guide.

Hi sfx, great build!! I first time ever solved g4 battery consumpion problem. Unbelivable!

After flashing this ROM, my phone does only boot to TWRP recovery. If I select reboot to system, it reboots to recovery. If I power it down and up, it reboots to recovery. If I reboot to fastboot then reboot, it reboots again to recovery !!!!!! I'm getting mad, sorry.
So I have re-installed the previous LineageOS 16.0 and... it boots up normally to Android !
So what am I doing wrong with this version 17.1? I have the H815 official unlocked btw.
EDIT ---------------------------------
I have tried both version 17.1 of 17 February and 3 February and none of them works on my H815.
So I'm simply moved back to version 16.0 that works.

Real-Baso said:
After flashing this ROM, my phone does only boot to TWRP recovery. If I select reboot to system, it reboots to recovery. If I power it down and up, it reboots to recovery. If I reboot to fastboot then reboot, it reboots again to recovery !!!!!! I'm getting mad, sorry.
So I have re-installed the previous LineageOS 16.0 and... it boots up normally to Android !
So what am I doing wrong with this version 17.1? I have the H815 official unlocked btw.
EDIT ---------------------------------
I have tried both version 17.1 of 17 February and 3 February and none of them works on my H815.
So I'm simply moved back to version 16.0 that works.
Click to expand...
Click to collapse
FAQ #6 step 2 -> share the pstore log if avail
and do FAQ #7
Also ensure u have the latest PREVIEW recovery (pie) installed and share the recovery log too (see my sig)

how good the chance is a H818N variant can work with this rom?

hkdoublecat said:
how good the chance is a H818N variant can work with this rom?
Click to expand...
Click to collapse
It will work perfectly fine - if you ever find a way to unlock it.

bluetooth not working properly and booting time massive. Over a minute with lg logo and after that normal lineage booting. H815 unlocked officially.

Anyone else having trouble with the reliability of the proximity sensor turning off the display?
Never mind if it's fine for you, then it's due to my dirty install...

Development [ROM][OFFICIAL][13] StatiXOS v6.2 [alioth/aliothin]

{
"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"
}
StatiXOS for Redmi K40 | Mi 11X | POCO F3 (alioth/aliothin)​
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
Changing the intensity of haptics does not work.
Battery stats in Settings show nothing.
Please report anything else you run into!
Spoiler: Download StatiXOS Here!
Primary
Spoiler: How To Flash
Detailed Flashing instructions in Post #3
Download the fastbootimage zip
Unlock your bootloader, and reboot to bootloader
Type in
Bash:
fastboot format:f2fs --fs-options=casefold,projid
[This will format all of the data in your phone including internal storage (photos, files, everything!)] (Skip this step if you are coming from a previous build)
Connect your phone to PC and type in
Bash:
fastboot update statix_alioth-XXXXXX-13-v6.1-TIRAMISU-img.zip
(XXXXXX denotes the date of the build)
Wait for a while until the flashing process completes, it will reboot your device
Enjoy!
Note: This ROM has GApps!
Spoiler: Stay in touch with our Telegram channels!
Official Releases & Announcements Channel
Android version: 13
Linux Kernel Version: 4.19.157
Source code: GitHub
Kernel Source code: GitHub
Code Review: Gerrit

Changelogs
6 February 2023
Initial build
7 February 2023
February 2023 Security patch
11 February 2023
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
23 April 2023
April Security Patch
Upgraded blobs to MIUI 14.x
Better pickup sensor implementation
Multi-Gen LRU enabled by default
Several Battery optimisations
5 May 2023
May Security Patch
Fixed the random reboot issues faced by some users

Detailed Flashing instructions:
NOTE: These instructions are for first time users only! If you are upgrading from previous StatiX Builds, you DO NOT NEED TO FORMAT DATA!
To flash StatixOS, you need these pre-requisites:
A PC with ADB/Fastboot installed
Redmi K40/Mi 11X/POCO F3 device
USB Cable
StatiXOS Build
Backup your internal storage before this process.
This guide assumes you are coming from MIUI 13.x with an unlocked bootloader.
For Windows Users:
Download SDK platform tools for Windows (do not use the latest platform tools, use any older than the r34) and extract it to anywhere you like.
Install ADB/Fastboot Drivers
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, navigate to the extracted platform-tools
In the folder you need to check if there are some dll files and a few executables (.exe files). We're majorly concerned with adb.exe and fastboot.exe.
Whilst pressing Shift key, Right click in the folder, and there shall be an option to "Open powershell window here" or "Open Command Prompt here"
In the powershell window, type in .\adb.exe devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about, just repeat the command)
Once the device is authorised, type in .\adb.exe reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Now ensure your drivers are proper. Type in .\fastboot.exe devices. If it shows nothing, it means that your drivers are not proper, google search on how you should fix them as it is out of the scope of this guide. Once you get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in .\fastboot.exe format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in .\fastboot.exe update ''path\to\StatiXOS\Build\zip'' (replace path\to\StatiXOS\Build\zip with actual path to the fastboot images zip file) Pro Tip: You can right click and copy the zip and then paste into powershell window. Make sure you paste in between the quotes ' '.
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
For Linux Users:
Install adb and fastboot according to your distro, and install proper udev rules.
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, open Terminal
In the terminal window, type in adb devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about)
Once the device is authorised, type in adb reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Type in fastboot devices, you'll get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in fastboot format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in fastboot update ''path/to/StatiXOS/Build/zip'' (replace path/to/StatiXOS/Build/zip with actual path to the fastboot images zip file).
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!

Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
NOW FIXED By using Post no. 10
I wish you well with this rom and look forward to future updates
many thanks Murali

johnr64 said:
Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
I wish you well with this rom and look forward to future updates
many thanks Murali
Click to expand...
Click to collapse
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method.
Always having a PC is a good thing when flashing a ROM, as you can quickly restore your device to a working state without any worries if your device goes into bootloop (which should not happen with statix).

do you have some screenshots for this on poco f3? please post them

Update!
Changelog:
February 2023 security patch
Download from OP

exodius48 said:
do you have some screenshots for this on poco f3? please post them
Click to expand...
Click to collapse
Screenshots have been attached to OP

m_vaisakh said:
Update!
Changelog:
February 2023 security patch
Download from OP
Click to expand...
Click to collapse
Murali,
Your FAST.

Hi Murali,
I use a small standalone ADB program to install Temporary Recovery.
I have modified it a bit and added some basic adb FastBoot commands,
i have now included your install files as well:
-------------------------- UPDATED ! -------------------------
Now confirmed working
================================================================================
. ---------- Connect your phone to a PC in FASTBOOT mode to use this program ----------
.
.
Select Option:
.=========
.
1) Install TWRP Recovery (Remember to MOUNT SD Card in TWRP, wait 3 seconds and plug in your OTG adaptor)
2) Install OrangeFox Recovery (Remember to MOUNT SD Card in OFRecovery, wait 3 seconds and plug in your OTG adaptor)
3) Fastboot Devices
4) Reboot Bootloader
5) Reboot Recovery
6) Reboot
7) ADB Command line:
8) (WARNING)------------------ Format:f2fs
9) (WARNING)------------------ Install Statix_alioth-XXXX-XXXX XXXX-TIRAMISU-img.zip
10) Exit
.
.
. -To enter FASTBOOT, Power Off your Phone followed by Pressing and holding the Power and Volume down Buttons for 3 seconds,
.
.------------- Please read the INSTALL.txt file ---------------
.
Type option:
================================================================================
Also included in the .7z file are Magisk V25.2 and Migrate-GPE.
Download and unzip:
Statix-XXXX-XXXX-TIRAMISU + TEMP TWRP - OrangeFox (FASTBOOT) V1.0
Download Statix_Alioth-XXXX-XXXX-TIRAMISU, Rename it to rom.zip
and copy into the Statix_Alioth-XXXX-XXXX-TIRAMISU + TWRP - OrangeFox (FASTBOOT) V1.0.7 Folder.
Using this method, it is now easy to install this ROM as Murali explained and add Recovery if needed,
Thank you Murali for all your hard work,
I hope users find this little proggie helpful.

Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from OP

m_vaisakh said:
Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from
Apps in playstore not updating . always shows try again. Facebook messanger chats not loading .
Click to expand...
Click to collapse

Doesn't look like a statix issue to me. Did you format data using the given commands?

m_vaisakh said:
Doesn't look like a statix issue to me. Did you format data using the given commands?
Click to expand...
Click to collapse
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.

gulmeli said:
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.
Click to expand...
Click to collapse
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.

m_vaisakh said:
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.
Click to expand...
Click to collapse
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this

gulmeli said:
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this
Click to expand...
Click to collapse
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.

m_vaisakh said:
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.
Click to expand...
Click to collapse
Thank You Very much. it works fine now thanks again for the beautiful rom for great device.

Hi,
I tried the rom today,
the things i found:-
it seems to take a long time between the Poco F3 Logo and the boot animation,
i wasn`t able to find Face Unlock in the security setting,
Using the "Standalone ADB program" has made a massive difference,
as it simplifies every thing for me.
The rom is good but is in need of some TLC (Tender Loving Care),
I look forward to the next update,
Thank you again for all your hard work

m_vaisakh said:
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method...
Click to expand...
Click to collapse
I think you could explain also that this ROM uses vendorboot-as-recovery.

How To Guide CPH2451 Rooters Please refrain to g96818 guide to Improve the Init_boot method.

Hey guys, i have tested the new method posted by g96818 and it works perfect.
Since he has more experience than me with OnePlus rooting I'll delete this post soon.
My fear is the future proofing of my method and i understand that his method is better in the case of future updates and less risky.

Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.

hitzzzzzzzz said:
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
Click to expand...
Click to collapse
Hey man, but there is a full OTA for that, you just need to subtract the info you need from it.
Since i dont have that device, i dont want to tell you what to do.

Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451

scott.hart.bti said:
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
Click to expand...
Click to collapse
Yeah that's true that would be nice.

Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device

scottlam1 said:
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
Click to expand...
Click to collapse
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable

blasbenoit said:
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me and other guys in this forum.
Important notes to consider: A big thanks to azsl1326 he got us the Patched Init_boot to make this possible.
-You need to unlock the bootloader of your device. This means you'll lose the data ect ect ect.
-People are losing Netflix access after this process, right now we haven't found a "cure" for this, but is pretty normal if you have root a Oneplus device before, when i found the fix i'll edit this right away.
-I'll write this for experts and newcomers a like just in case so they don't have to start asking for simple questions.
-After the root some people have the issue that they cant use security like passwords, fingerprint...ect ect. (as of now the only fix they have is to reset everything and doing the rooting again for 2+times). If i find the "cure" i'll let you guys know.
Spoiler: Issues connecting your device to the PC?
To some people the USB debugging is not working at all, because the phone turn it off after you try to use it or connect it to the PC.
I personally had this issue so i just workaround it. This is what i did:
1- Connect the OnePlus to the same network as your PC.
2- Turn On Wireless debugging on your OP11 and select Pair device with pairing code:
3- Then use this on your PC after you open CMD of course:
Then put the code you have.
The check with this command to see if it is connected:
Now that it is connected you can enter bootloader and connect it to your PC in that mode normally with:
OK now back to the deal:
1- Download the latest platform tools from here:
-Unzip it and put it in the desktop for easy access.
2-The bootloader
Spoiler: Unlock the Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"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"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
3- Flashing the Init_Boot.img
In this case i'll provide the already patched Init_boot.img for A07!!! so you don't have to look for it, is attached to this thread.
Download the img and put it in the same folder as the platform tools for easy access.
Spoiler: Magisk Canary
After you enter the device.
1. Dowload the Magisk Canary version from this link:
2. Install it on you device.
Spoiler: Opening CMD (Command Prompt)
After you got everything in place open the platform folder and type CMD on the location box, then press Enter.
If that doesn't work, just open CMD and type:
CD and write the location of the platform folder to get it to work.
Now to the "flashing"
Enter the bootloader like before to start, now type this:
The above command should automatically flash the init_boot to both the slots. However, if you face any issues while executing that command, then you could also manually specify the slots while flashing. Like this:
And
4-Restart your phone and check the magisk canary app that everything is OK.
Spoiler: Bypassing Safetynet
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
Download a safetynet check just to be sure.
And thats pretty much it, if you guys find some issues after the root, please post them here so i'll start adding more and more info about it for future references and fixes.
Click to expand...
Click to collapse
You are so helpful! This worked flawlessly!

ChrisFeiveel84 said:
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
Click to expand...
Click to collapse
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key

scottlam1 said:
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
Click to expand...
Click to collapse
i never use adb over wifi sorry

Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?

H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first

ChrisFeiveel84 said:
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
Click to expand...
Click to collapse
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated

H4X0R46 said:
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
Click to expand...
Click to collapse
I didn't have an issue with my lock screen and stuff. I also didn't do anything to the phone other than unlock bootloader and root. Once I did this my lock screen and fingerprint and stuff wasn't an issue at all. Maybe I got lucky.

H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
The password issue has nothing to do with rooting, it is caused by unlocking the bootloader. Before you do any rooting, first lock and unlock the bootloader 3 times. After the third time, you can set the password (or pin, or pattern/etc) and THEN do the actual rooting.

Do you have boot.img instead i rather have temp root

i accidentally pushed the patched init boot img to phone before updating, now i keep getting failed system update, any way to revert back to original A06 init_boot.img so i can take update and then come back and root

SappyHanger said:
Do you have boot.img instead i rather have temp root
Click to expand...
Click to collapse
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.

blasbenoit said:
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
Click to expand...
Click to collapse
can you point me to the init boot image on A06, i accidentally pushed the patched a07 version to a06 w/o updating to a07

So I did the above and magisk turns into a green android icon and won't start. It did start before I flashed the init boot.... ?? Tried to re-install magisk, same thing. green icon.....
Do I need to sideload magisk? (adb sideload Magisk-v25.2.zip) ???