TEAM DEVDIGITEL PRESENTS LG V20 LS997 Sprint Stock-ish with Goodies
DOWNLOADS,MODS & RECOMMENDATIONS
AT BOTTOM OF MAIN POST
CHANGE-LOG IN POST #2
HELP ME POST #3
Read Before posting Issues
JUST LOOK HERE 1ST!
You've been Warned
PREQUISITS:
This is a DECRYPTED rom and requires that you are boot-loader unlocked and have access to twrp.
If you have not wiped your system and formatted data do so now, unless you want a brick...
After flashing the rom i suggest wiping cache and dalvik cache again then rebooting.
YOU NEED TO WIPE ALL DATA AND FORMAT DATA TO USE MY ROM
This is based of the ZV3 / ZV4 / ZV5 / ZV6 / ZV7 Images currently. Oct, Nov and Dec,Jan, May patched software's.
See here for the Dirty Santa root and where you gotta hit thanks at for his hard A$$ work
XDA LINK : https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
OK THE DISCLAIMER PART:
I can't be held responsible for the effects of this software, it was designed for testing purposes and fun.
Please make a backup, make sure you have a computer handy with adb and fastboot.
Please take sometime to read all documents before proceeding, you've been warned.
Installation Steps:
1.) Download desired Rom Version from below download link(s)
2.) Place Rom preferably on external SD card
3.) Reboot device into recovery either using Busybox, shell command, or from device powered off method. (instructions in post#3)
4.) Once in recovery its HIGHLY recommended to install on a clean device. Select Wipe, Then advanced,
put check marks next to System, Dalvik-Cache, Data, Cache
5.) Once wipe is completed, back up one step and choose FORMAT DATA, it will require you to type YES to complete.
6.) When completed return back to Main TWRP screen, Click Mount and make sure System and Data are mounted.
7.) Choose Install then Navigate to where you placed Rom ( You made need to choose SD as the storage location if you put on SD )
9.) Install Rom and wait for it to complete. Once done, select reboot and WAIT.
10.) Once on home screen you will need to manually activate your device, either go and do a Profile update in settings, or dial ##update#
This will need to be done anytime you flash a ROM as the activation information gets bypassed on my roms and most importantly ENJOY !
NOTICE:The install process will take some time (Approx 15 Min), later builds have zip-align at boot to help with de-odexed speeds, the boot logos have also been turned of on some newer builds so don't freak out, just wait until you hear the Voice assistant start her speech.
At this point the screen will be out of wack( ZV7 This is Fixed) , many moving colors and such, this is normal due to using sprints boot.img with the debug boot-loader that gave us the unlocked / root ability. Once you hear the Voice assistant start up, cover the proximity sensor near the front camera and lock the screen. Once both the top and main screen go black, just unlock the screen and continue with setup. The static image will re-occur on any full re-boot. To avoid this check out the Modified Kernels post for Alt. Kernels that resolve this. Be aware I do NOT support these other images, and i'm unable to help with issues you have if you choose that route. Please post in the Kernels page where you got the Kernel for best support!
DOWNLOADS
--------Software Version ZV7--------MAY SEC PATCH--------
( Magisk Manager 4.3.3 is for Official builds before Version 13;
Magisk Manager 5.0 Is for Beta Builds V13 and newer; both are attached to Change-log Post )
Version 9.0 D De-Odexed ( Magisk 13.xx + Debloated + Viper + Busybox + Tweaks + Mods etc)
Download (Beta-Magisk 13.xx): https://www.androidfilehost.com/?fid=673368273298966589
MD5: d52463b02ce7b90ddab63a6984209f6d
Version 9.0 C De-Odexed (Full Bloat, No Added Apps, Un-rooted)
Download: https://www.androidfilehost.com/?fid=817550096634781477
MD5: 827ae5e7f6b5ffc890e6653d6a16b1fb
Version 9.0 B Odexed ( Magisk 13.xx + Debloated + Viper + Busybox + Tweaks + Mods etc)
Download (Beta-Magisk 13.xx):https://www.androidfilehost.com/?fid=817550096634781064
MD5: e5e436a93e5491e4d555347390dbcdb1
Version 9.0 A (Rooted) Odexed (Full Bloat, No Added Apps, Rooted W/ Magisk 13.xx +BB )
Download: https://www.androidfilehost.com/?fid=961840155545572409
MD5: 37b479e05962b96a04f8c999c60626f1
Version 9.0 A(Non-Rooted) Odexed (Full Bloat, No Added Apps, Un-rooted)
Download: https://www.androidfilehost.com/?fid=961840155545571944
MD5: 8faf5213f7a21b75bab18727628aa6ea
--------Software Version ZV6--------FEB SEC PATCH--------
( Make sure to D/L the Magisk Manager 4.3.3 Attached to Change-log Post )
Version 8.0 E De-Odexed ( Magisk 11.6 + SuperSU + Debloated + Viper + Busybox + Tweaks + Mods etc )
Download Link:https://www.androidfilehost.com/?fid=961840155545572383 [/I]
Version 8.0 D De-Odexed ( Magisk 11.6 + Debloated + Viper + Busybox + Tweaks + Mods etc )
Download Link: https://www.androidfilehost.com/?fid=673368273298951670
MD5 : 010ed860fa7713980d95b19d7ef15758
Version 8.0 C De-Odexed (Magisk 11.6 + Busybox Full Bloat, No Added Apps )
Download Link: https://www.androidfilehost.com/?fid=817550096634766377
MD5 : 679031216e491668e6515b2b80b0d091
Version 8.0 B Odexed ( Magisk 11.6 + Debloated + Viper + Busybox + Tweaks + Mods etc )
Download Link: https://www.androidfilehost.com/?fid=817550096634766376
MD5 : b254fb5d4f9ccb19f8a56ce2eeb98e35
Version 8.0 A Odexed (Magisk 11.6 + Busybox Full Bloat, No Added Apps )
Download Link: https://www.androidfilehost.com/?fid=745425885120728713
MD5 : a2c2eb5b08ea9e7a35197f59259b7b5a
--------Software Version ZV5--------DEC SEC PATCH------
Version 7.5C Magisk V11.5 + 3Minit + ModControl+ModInstaller
( Make sure to D/L the Magisk Manager 4.3.3 Attached to Change-log Post )
MagiskSU Download Link: https://www.androidfilehost.com/?fid=817550096634756180
SuperSU Download Link: https://www.androidfilehost.com/?fid=457095661767149785
Version 7.0 MagiskSU + 3Minit + ModControl
( Make sure to D/L the Magisk Manager 4.3.3 Attached to Change-log Post )
Download Link: https://www.androidfilehost.com/?fid=745425885120713763
" To use Mod Control app, you must move it to /system/priv-app/ "
Version 6.5 (MAGISK V11.1) ZV5 Debloated, Deodexed, Crazy Build.prop, Init.d, BusyBox, Speedtweaks & More)
BASE OPTION 1 : MagiskSU Download Link: https://www.androidfilehost.com/?fid=673368273298930272
BASE OPTION 2 : SuperSu Download Link: https://www.androidfilehost.com/?fid=673368273298930271
Version 5.5 L (ZV5 Deodexed Debloat Medium Crazy Build.prop Init.d tweaks, battery and speed modded, su, bb, init-d, su.d)
Download Link: https://www.androidfilehost.com/?fid=529152257862698451
Version 5.0 K (ZV5 Deodexed Stock ZV5, No Bloat Removed/ BB,SU,,Build.prop only)
Download Link: https://www.androidfilehost.com/?fid=529152257862696925
Version 5.0 J (ZV5 Deodexed Debloat Medium Crazy Build.prop Init.d tweaks, battery and speed modded, viper, su, bb, init-d, su.d )
Download Link: https://www.androidfilehost.com/?fid=385035244224414280
Version 4.0 II (ZV5 Odexed Debloat Medium Crazy Build.prop Init.d tweaks, battery and speed modded)
Download Link: https://www.androidfilehost.com/?fid=673368273298924951
Version 4.0i ( ZV5 Odexed FULLBLOAT, Su, Root Switch and Viper only mods.
Download Link: https://www.androidfilehost.com/?fid=385035244224412300
Version 4.0HHH (ZV5 Odexed Debloated V3 Mods Moved to New Base)
Download Link: https://www.androidfilehost.com/?fid=745425885120699739
Base ZV5 Untouched - Not rooted
Download Link: https://www.androidfilehost.com/?fid=457095661767148407
-------Software Version ZV3--------OCT SEC PATCH-------
"Older Builds No longer supported"
Version 3.0F (ZV3 Deodexed/Debloated/INIT.D,BB,Speed,Viper,Mods)
Download Link: https://www.androidfilehost.com/?fid=457095661767128014
Version 2.0E (ZV3 ODEX/ROOTED/Debloated/INIT.D/BB/FM/Speed/Viper)
Download Link: https://www.androidfilehost.com/?fid=385035244224410664
Version 1.0D (ZV3 ODEX/ROOTED/Debloated)
Download Link: https://www.androidfilehost.com/?fid=385035244224410155
Version 1.0A (ZV3 ODEX/UNROOTED/Factory/NotTouched)
Download Link: https://www.androidfilehost.com/?fid=673368273298921373
------------------------------------------------------------------------------------
Twrp Recovery Project
XDA Link: https://forum.xda-developers.com/v20/development/recovery-twrp-3-1-0-0-touch-recovery-t3603760
Kernel/Boot.img Repo
XDA Link: https://forum.xda-developers.com/v2...-s-carrier-t3533426/post70430173#post70430173
Radio/Modem/Baseband Repo
XDA Link: https://forum.xda-developers.com/showpost.php?p=70430236&postcount=2
Mod Control By @Zacharee1
XDA Link: https://forum.xda-developers.com/v20/themes/mod-aosp-signal-bars-t3551350
MODS / FEATURES & Extras For DevDigitel Roms
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*
Open Gapps Project :
Link:http://opengapps.org/
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*
Custom SystemUI Mods / Mod Control:
XDA Link:
https://forum.xda-developers.com/v20/themes/mod-aosp-signal-bars-t3551350
Playstore Link: https://play.google.com/store/apps/details?id=com.zacharee1.modcontrol
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
DualBoot Patcher (SnapShot)
XDA Link: https://forum.xda-developers.com/showthread.php?t=2447534
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
3Minit Clock & Battery
3Minit Battery: https://forum.xda-developers.com/sho....php?t=2799958
3Minit Clock: https://forum.xda-developers.com/and...-v1-0-t3400221
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Viper4Arise:
XDA Link : https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
My Viper4Arise Magisk Flashable : https://forum.xda-developers.com/v20/themes/flashable-mod-viper4arise-magisk-simple-t3578075
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Magisk 11.6
XDA Link: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Dual Audio Mod (Earpeice + Speaker )
XDA Link : https://forum.xda-developers.com/v20/themes/stereo-speaker-mod-t3499521
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Updated Stereo mod with High Impedance forced on HiFi Dac.
Made for ZV7 update.
https://forum.xda-developers.com/sho....php?t=3637449
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Hotspot Mod
XDA Link: https://forum.xda-developers.com/v20/themes/rooted-enable-hotspot-t3523662
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Fluence UHD Patch
XDA Link: https://forum.xda-developers.com/android/software/fluence-uhd-t3571875
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Shortcut Master Lite
Playstore Link: https://play.google.com/store/apps/d...cutmaster.lite
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Make ANY Quick Setting Tile :
Play Store Link: https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Emoji Switcher:
(Aroma-Installer)
XDA Link: https://forum.xda-developers.com/v20/themes/aroma-1-click-emoji-changer-10-to-pick-t3499517
(Flashable Zips)
XDA Link: https://forum.xda-developers.com/v20/themes/flashable-release-outlined-ios-unicode-t3545726
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Enable Google Assitant:
XDA Link: https://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Google Phone & Contacts
XDA Link: https://forum.xda-developers.com/v20/themes/root-nougat-google-dialer-app-v20-t3526735
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
Silent Camera Mod
XDA Link: https://forum.xda-developers.com/v20/themes/root-roiddroidvoid-s-silent-lg-v20-t3530206
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
BUGS:
* Voided Warranty Via LG
* PASS SAFETY-NET WITH MAGISK ONLY ROMS ( NOT SUPERSU )
* Static on 1st boot ( FIXED ON ZV7) that requires proximity sensor hack ( Werewolf Kernel Fixes this but adds longer boot time)
Be aware alternative kernels will break things in my Rom, by changing your kernel I can no longer help troubleshoot your issues
as I am not the developer for the kernel you choose, my stock-kernels are included with the Rom and work perfectly minus static.
* SUHIDE BY CHAINFIRE NOT WORKING ON ANY DEC PATCH FORWARD
* Must Remove LG Setup Wizard to use the additional users, hangs on setup without removing, this also messes with call-ui somewhat, when in
a call you cant leave it normally, you must hit the 3 dots in right corner and choose contacts, then you can hit home and browse phone will in
call. Not sure why these 2 are connected here, but its the case anyways.
* Device may lose System/Carrier settings after flash, do ##update# or ##brand# and let device re-activate.
*Please do not Re-Host my work or Re-use my work without Proper credits,
as well as a link back here for support etc. Otherwise its opensource so do as you please*
Developer(s):
@Team DevDigitel
@me2151
Contributor(s) :
@Zacharee1 - SystemIi edits AOD, All the ModControl Stuff etc - Thanks Bro!
@SaintZ93 - Provided the tools / work to build the Stock boot.img's from LG source, patched the STATIC!
My GitHub : https://github.com/Team-DevDigitel/DevDigitel-V20.git
Built Using: Assayeds Kitchen & SuperRs Kitchen. Great Tools For Any DEV!
*Stable Status*
Special Thanks To:
This was only achievable due to @me2151 and his awesome Work.
@me2151 - LS997 / Booloader Unlock Dirty Santa / Boot.img / ZV3&5 Bases,Please make sure to visit the dirty Santa forum and put a thanks for him and donate to HIM if you can afford to.
As well as @jcadduono for the tools and tons of work with source he has done!
@Tilde88 - Files / Related Testing / Deodexing
@Chainfire - Root/Su and the CF.lumen app see here : https://forum.xda-developers.com/showthread.php?t=2711912
Magisk&Tools: @topjohnwu See: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
As Well the Unofficial Magisk Devs : @Captain_Throwback, @Didgeridoohan and @DodoGTA @Deic See: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Viper4Arise Team Thanks : @guitardedhero, @ahrion, @Ben Feutrill , @A.R.I.S.E. Sound Systems
JRummyApps for the great boot-animations app from google play. Found here : https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations&hl=en
------------------------------------------------------------------------------
CHANGE LOG:
VERSION 1.0 ( Labled D) ZV3
- Stock Odexed
- Debloated,
-Su &Su.d
-No Encypted
-Stock Lg apps re-loaded
-Cf.lumen adjuster,
-ton of edits, cleanup and more.
- All the stock features are included for sprint users
IE: PRL and Profile updates , HFA , WIFI CALLING, Comfort view, YouTube fixes etc.
Version 2.0 ( Labled E) ZV3
-Odexed
-Now includes Viper for Android
-Init- supported
-adb / su.d - supported
-Fm Radio - Fixed
-Speed Edits
-Build Prop Edits
-Update Script Rewrite
-Busy Box and all parts in xbin by default
-Deleted more bloat -still got some more to go
-Super compressed ( file size was consistent to last file even with more added )
-Zipaligned
Rooted with SuperSU / Not updated to latest but ill get it there next time around
more that im not thinking oF
Version 3 (Labled F) ZV3 ( Last Revsion to ZV3)
-Deodexed
-Updated SuperSU
-Updated build / Prop / System
-Cleaned up a little more
-Base is no DEODEXED
-minor tweaks/bug fixes
-super compression for size
- This will pass safetynet with attatched app. Install, give root
Permissions.. Check stop all superuser deamons. Reboot and enjoy!
Version 4 (Labled HHH) ZV5
-Odexed Base
-Viper4Android *bug fix
-Busybox implemented on flash now
-Su.d
-No setup-wizard included (straight to homescreen) must update profile to re-activate device.
-Stock Lightweight base
-Fast First Boot
-(mirrors all mods on version 3 minus deodexing)
-Root Switch Installed
-Cleanup
-New build.prop
-ZV5 Boot.img
-Faster running system then ZV3
Version 4 ( Labled i ) ZV5 Odexed Fully Stock (Base)
-Full ZV5
-Odexed
-GoogleNow
- Viper
- Build.prop edits
- GoogleNow
- Multi-User
- Cf Lumen (included in system)
- SuperSu "Chainfire Version"
- BusyBox,
- Build.prop
- Init-d and many tweaks being used
- Su.d,
- Sqlite
- RootSwitch - 1.3.3.2 (included in system)
-Viper4Android
Version 4 ( Labled II ) ZV5 Odexed Medium Debloat
-Odexed Base
- Viper
- Build.prop edits
- GoogleNow
- Multi-User
- Cf Lumen (included in system)
- SuperSu "Chainfire Version"
- BusyBox,
- Build.prop
- Init-d and many tweaks being used
- Su.d,
- Sqlite
- RootSwitch - 1.3.3.2 (included in system)
Version 5 ( Labled J ) ZV5 De-odexed Medium Debloat
- Now Deodexed
- Deodexed
- Minimal SetupWizard Used Vs No setup Wizard
- Viper
- Build.prop edits
- GoogleNow
- Multi-User
- Cf Lumen (included in system)
- SuperSu "Chainfire Version"
- BusyBox,
- Build.prop
- Init-d and many tweaks being used
- Su.d,
- Sqlite
- RootSwitch - 1.3.3.2 (included in system)
- Clean Install recommended due to removal of .odex systemwide
- 1st boot is long, be patient, its running my zip-align on 1st boot and optimizing all the new apks, it will sit on lg logo longer then usual, just wait!
Version 5 ( Labled k ) ZV5 De-odexed No Removal of Bloat (mirrors I)
- Fully Stock
- Deodexed
- GoogleNow
- Build.Prop
- Su, Su.d, Init-d, Busybox included.
- Multi-User
- Clean Install recommended due to removal of .odex systemwide
- 1st boot is long, be patient, its running my zip-align on 1st boot and optimizing all the new apks, it will sit on lg logo longer then usual, just wait!
Version 5.5 ( Labled L ) ZV5 De-odexed Medium Debloat
- Deodexed
- Debloated, 99% of google apps/unessential Lg apps gone
- Added All LG apps back, even ones never included on V20
- Minimal Setup-Wizard Used Vs No setup Wizard
- Build.prop edits
- Deodexed
- GoogleNow
- Multi-User
- Cf Lumen (included in system)
- SuperSu "Chainfire Version"
- BusyBox,
- Build.prop
- Init-d and many tweaks being used
- Su.d,
- Sqlite
- RootSwitch - 1.3.3.2 (included in system)
- Clean Install recommended From versions Prior to ( J ) or any non-deodex version
Version 6.5 ( Magisk Rom ) ZV5 De-odexed Medium Debloat
- Fully Re-wrote installer process, had to make order changes, added DATA install vs system install of additional apps
- Two (2) Versions PHH or SuperSu, PHH is built into Magisk Manager
- PHH Magisk/Root hide works without error & passes safetynet, SuperSu doesn't pass safetynet still
- Debloated, 99% of google apps/unessential Lg apps gone
- Added All LG apps back, even ones never included on V20
- Magisk Manager V11.1
- Minimal Setup-Wizard Used Vs No setup Wizard
- Build.prop edits
- Multi-User
- Deodexed
- GoogleNow
- Cf Lumen ( Now a user-app that can be easily removed)
- BusyBox & Magisk Systemless BB
- Init-d,
- Su.d ( Now located in Magisk Directory by default)
- Sqlite
- RootSwitch - Removed from all Magisk builds as its not needed
- Clean Install recommended From versions Prior to ( J ) or any non-deodex version
- 1st boot is long, be patient, its running my zip-align on 1st boot and optimizing all the new apks, it will sit on lg logo longer then usual, just wait!
Version 7.0 MagiskSU + 3Minit + ModControl+ModInstaller+ViperAddons
*Magisk will need to be installed from Playstore to avoid bugs
* Added Viper4Arise Profiles, DDC, Kernel - Now you just need to install the driver Via Magisk and it will be pre-setup and working with a good base.
*Updated ModControl and ModInstaller was added to google play versions,
the mod control should be moved to system/app using the mod installer
*Added updated 3minit resources, systemui, quicktools, sbsignuture etc.
Version 7.5B/C MagiskSU + 3Minit + ModControl
Clean or Dirty Flash OK!
If error code 7 occurs, unmout system and data and re-flash.
Mod Control By @Zacharee1
XDA Link: https://forum.xda-developers.com/v20...-bars-t3551350
-Introduction of ModControl:
This is a new app being built directly for the V20! This is going to be the epicenter for mod adjustments that have just been made. Mod control can actually revert EVERYTHING that has been done to the ui! This can give the user complete control over the design aspect of their device without having to flash diffrent mods and reboot constatly. This app contails a ton of options and everything is sperated from eachother to provide the most custom experience ever on our V20 handsets! You must manually move the app from userapp to system app " /system/priv-app to be exact. As well as you need to give the app permission to modify storage as it replaces files on the fly to accomplish the changes.
This app is being funded by TeamDev to get into the playstore, this is purely to provide more convienece and allow the app to OTA update as we continue to tweak and modify the app. There will be 0 adverts placed in modcontrol and will be free for life. I have tagged the creator in main op multiple times so you guys can go over there and read up on the app, its progress, post feedback, as well as make REQUESTS!!! This is a awomse feature i'm proud to be a part of and hope you guys share the enjoyment here! This is also where the updated app apks are being posted for the time being until the app is approved by google! You may see a donate option appear in the app over time, please consider donations to the project but by all means do not feel obligated. The donations would be diretly to the modcontrol creator and are purely to help motivate him and cover is coffee and costs/time!
-3minit Battery & 3minit clock added to SystemUI
3minit battery has 10000's of battery icons to choose from, as well as the option to remove the battery completely.
-3minit clock can be adjusted in many ways:
center,left,right as well as 1000's of combos for time,date etc.
- Added "Userdata" to install the following apps.
*Viper4Arise (Requires The magisk module installed to work)
*MagiskManager
*ModControl - Now a system app in V7.5B or later
* Viper profiles now added to userdata
3minit will function without this app but this is the heart of the main mods!
*CF Lumen
- Re-wrote updater script to now wipe batterystats on flash, as well to re-mount, and redo busybox install. "userdata" now being installed for additional apps vs "system"
-Added inid.d into boot.img as well as Magisk retains init.d mods for systemless. Done to avoid some init.d scripts from being skipped.
-Added fully busybox run parts to system, sqlite, and a few others. This way all flashable zips should be functional with our device, regardless if magisk busybox's systemless interface works.
-Many other tweaks that i probably forgot but will add as i see fit
ZV6 Builds
Version 8.0 A Odexed (Magisk 11.6 + Busybox Full Bloat, No Added Apps )
Placeholder
Version 8.0 B Odexed ( Magisk 11.6 + Debloated + Viper + Busybox + Tweaks + Mods etc )
Placeholder
Version 8.0 C De-Odexed (Magisk 11.6 + Busybox Full Bloat, No Added Apps )
Placeholder
Version 8.0 D De-Odexed ( Magisk 11.6 + Debloated + Viper + Busybox + Tweaks + Mods etc )
Placeholder
Version 8.0 E De-Odexed ( Magisk 11.6 + SuperSU + Debloated + Viper + Busybox + Tweaks + Mods etc )
Placeholder
ZV7 Builds
Version 9.0 A Odexed ( Full Bloat, No Added Apps, Un-rooted )
Placeholder
Version 9.0 B Odexed ( Magisk 13 + Debloated + Viper + Busybox + Tweaks + Mods etc )
Placeholder
Version 9.0 C De-Odexed (Full Bloat, No Added Apps, Un-Rooted )
Placeholder
Version 9.0 D De-Odexed ( Magisk 13 + Debloated + Viper + Busybox + Tweaks + Mods etc )
Placeholder
HELP ME PLEASE FOR ISSUES AND FIXES!
PLEASE READ THESE BELOW BEFORE POSTING WITH A ISSUE, EXPECIALLY TO DIRTY SANTA ETC!!
YOU WILL BE IGNORED IF ON THE LIST!!!
==================================
I Flashed Magisk But No Root?
=====================================
Two ways to approach this one:
Re-flash the whole Rom without wiping. Reboot.
-OR-
Pull the Magisk11.zip from inside the rom under the
/Magisk/Magisk11.zip directory, and flash it by itself and Reboot.
==================================
How do I get into recovery
=====================================
pull battery and put it back in
hold volume down and power.
when lg logo shows up click power and re hold it while still holding vol down.
if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in TWRP.
====================================
Stuck in a endless boot loop to twrp
=======================================
1.)Do it from twrp:
Make sure system and data are mounted with Twrp.
We need to clear out some directories causing issues. Once mounted partitions are verified go to advanced and use the file explorer buit into TWRP.
We need to delete the entire "Fota" and "Misc"
locations.
They are located under these locations
Don't worry if they aren't all there.
Delete any/all of these:
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Then reboot from TWRP. This should fix the issue.
Or
2.)Requires Pc and Fastboot setup already.
Pull battery and put back in, hold vol down and pulg into pc
phone will boot to Fastboot*
Now on pc send these commands via command prompt
Fastboot erase misc
Fastboot erase fota
Fastboot erase cache
Fastboot reboot
still stuck? go back to fastboot as stated above
Try this as well
fastboot erase system
unplug and pull battery and put it back in,
dont plug back in, lets try to get into recovery,
hold volume down and power.
when lg logo shows up click power and re hold it while still holding vol down.
if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in twrp.
restore backup or re-flash a rom again..
Good-Luck!
===================================
Locked out of device after restore / dirty flash
pin # / pattern / Fingerprint wont work?
=======================================
Steps:
Boot into Twrp ( if you dont know how see above steps on how to access twrp
Using the TWRP file manager navigate to this location
/data/system/locksettings.db
delete this file and reboot device, your pin/lock is now gone.
==============================
Some apps wont login or work
===================================
These may also quire the troublesome app to be uninstalled first/and re-installed after steps completed. This is semi generic.
Alternative 1:
Download this app from the playstore to
download the latest versions of google play services,
Link: https://play.google.com/store/apps/details?id=com.weberdo.apps.serviceinfo
Open app and use it to force a update
It gives you 3 options to do so
once done reboot into recovery and clear cache and dalvik-cache
this should resolve the issue once completed
Alternative 2:
Try fully un-rooting. This will require you go into the settings
and choose full unroot. When super su asks to replace with stock image,
say no. The phone will need to reboot after it has complete. Once rebooted
try to login to the application and see if it worked. If yes then get everything logged in and then pull the supersu zip from the rom (this will be in the rootzip folder) Take it and flash it using twrp. It will reboot atleast once. Do not disrupt the process!
Alternative 3:
Depending on build you now have the alternative option to switch to fully Magisk and the phh superuser app. This is still some uncharted territory with Magisk and what exactly it does to force hide root. In the Magisk manger app you can choose to hide root. This may be buggy but have the app downloaded and go to sign in after enabling this option. If this works you are more then likely fighting the battle with safetynet and its not something I currently have much support or full understanding of. Goodluck!
=====================================
Hostpot/Tether Settings Missing
Other SystemUI things gone
======================================
Its best to do this on wifi but do it as you wish
Steps:
go to dialer
enter ##27269# (##BRAND#)
Hit Yes if prompted to do so,
the phone will reboot and add the carrier branded files back
and replace the systemui setup with the correct one!
Other Codes that do the same thing essentially : ##UPDATE# ##72786#
These will not erase any user data, so dont be worried!
=====================================
Storage Showing 0mb in Twrp? Device cant wipe any data?
=======================================
This may show error 150 in twrp when trying to wipe any data.
All of your data is gone either way, this will hopefully fix the device.
Steps: This requires twrp access still,
Go under wipe,
and choose Advanced wipe,
once there choose repair/change file system
after clicking repair file system you will now see all of your storage options here.
The storage will need to be wiped with the EXT4 Option.
You must only select 1 at a time, and they all must be wiped to resolve this issue.
Do each one down the list, and wipe every storage location 1 by 1. Once done,
back out and check to mount each partition. This show now be successful.
I would go ahead and flash a clean rom or go and restore from a backup.
*This can also fix issues with some sd cards being corrupted*
=====================================
Cant Get Service? No Calls or Text But LTE works?
=======================================
Try this:
How to manually program:
https://forum.xda-developers.com/v20/help/manual-program-sprint-ls997-v20-t3557676
How to write your prl:
https://forum.xda-developers.com/v20/how-to/how-to-write-prl-to-v20-t3559010
More to come......
I'll have to give it a few more minutes, but I appear to be stuck on the first boot. Was already dirtycow'd. Did a clean install of this rom. First boot, it got to LG screen rebooted, past LG screen into static, behind the static is mostly white with some yellow and black lettering (sprint logo) and it appears just frozen there. I'm aware first boot takes a while. It's been an abnormally long time without any change at all - 10 minutes and change or so. I'll give it a bit longer but I'm pretty sure it's froze up.
---------- Post added at 01:14 PM ---------- Previous post was at 01:09 PM ----------
Yeah pretty certain this isn't going anywhere. I would've been into the android optimizing apps progress bar screen well before now on first boot.
---------- Post added at 01:28 PM ---------- Previous post was at 01:14 PM ----------
Yep definitely stuck, left it almost half an hour. So, like I said, I was on dirtycow and the sprint rom from that thread (so I'd already formatted data, had TWRP & root obviously). I wiped cache, dalvik, system, and data. Installed rom. Wiped cache & dalvik again and rebooted. Looks like I have to figure out the button combo to get into recovery for this phone. I've just been using adb reboot recovery but adb is no longer able to see the device (I tested @Tilde88's attempt at a rom the other day and was able to access adb while frozen in a similar spot).
qstarin said:
I'll have to give it a few more minutes, but I appear to be stuck on the first boot. Was already dirtycow'd. Did a clean install of this rom. First boot, it got to LG screen rebooted, past LG screen into static, behind the static is mostly white with some yellow and black lettering (sprint logo) and it appears just frozen there. I'm aware first boot takes a while. It's been an abnormally long time without any change at all - 10 minutes and change or so. I'll give it a bit longer but I'm pretty sure it's froze up.
---------- Post added at 01:14 PM ---------- Previous post was at 01:09 PM ----------
Yeah pretty certain this isn't going anywhere. I would've been into the android optimizing apps progress bar screen well before now on first boot.
Click to expand...
Click to collapse
make sure to clean wipe and make sure you mounted system prior to flash. First boot does take some time, and will take 10-20 minutes to fully install and boot up. Be patient but if its on the sprint boot animation its on its way to fully boot from previous tests. Maybe wipe and re-install? I just wiped system fully with fast-boot and flashed again to double check things.
correct i did not add adb to the kernel because its skipps so fast you can never hit it on boot up, there is no hardware key combo to enter recovery,
pretty much if its stuck and wont boot, go to fastboot - fastboot erase system, then run step 3 from dirty santa and it will replace the boot.img and the recovery and allow adb again. Id wipe and try again with a clean flash, ive put it on 3 new devices so far and all 3 booted clean after about 15 min or so..
old
My bad, false alarm. I pulled the battery and gave it another shot at booting without doing anything else and sure enough I was at the initial setup screen in about 5 minutes.
Team DevDigitel said:
make sure to clean wipe and make sure you mounted system prior to flash. First boot does take some time, and will take 10-20 minutes to fully install and boot up.
Click to expand...
Click to collapse
Yep, clean wipe, sys was mounted, install script appeared to run without issue, waited more than 25 minutes. I have flashed and restored a handful or two of times so far on the v20 so I kind of had an idea what to expect (obv. every rom can be different, computers act weird, etc). Looked like it had frozen up but maybe it was just taking extra, extra long.
Team DevDigitel said:
correct i did not add adb to the kernel because its skipps so fast you can never hit it on boot up, there is no hardware key combo to enter recovery,
pretty much if its stuck and wont boot, go to fastboot - fastboot erase system, then run step 3 from dirty santa and it will replace the boot.img and the recovery and allow adb again. Id wipe and try again with a clean flash, ive put it on 3 new devices so far and all 3 booted clean after about 15 min or so..
Click to expand...
Click to collapse
Huh, I did not realize there's no hardware combo for recovery. I kept reading hold volume down and power and do a little dance at the right second but I tried a bunch of times and couldn't hit it. In some places I read that brings you to a choice to factory reset and you have to select and confirm and then it will boot into TWRP..
Thank you for that info on adb during boot (I was about to try fastboot before just giving it another shot at booting up), and the ROM of course (I've been F5'ing this subforum for the last 2 days waiting lol, also big thanks to @me2151 and @Tilde88).
qstarin said:
My bad, false alarm. I pulled the battery and gave it another shot at booting without doing anything else and sure enough I was at the initial setup screen in about 5 minutes.
Yep, clean wipe, sys was mounted, install script appeared to run without issue, waited more than 25 minutes. I have flashed and restored a handful or two of times so far on the v20 so I kind of had an idea what to expect (obv. every rom can be different, computers act weird, etc). Looked like it had frozen up but maybe it was just taking extra, extra long.
Huh, I did not realize there's no hardware combo for recovery. I kept reading hold volume down and power and do a little dance at the right second but I tried a bunch of times and couldn't hit it. In some places I read that brings you to a choice to factory reset and you have to select and confirm and then it will boot into TWRP..
Thank you for that info on adb during boot (I was about to try fastboot before just giving it another shot at booting up), and the ROM of course (I've been F5'ing this subforum for the last 2 days waiting lol, also big thanks to @me2151 and @Tilde88).
Click to expand...
Click to collapse
YEY, was starting to loose my high from getting it put on xda, glad you got it resolved. Hope you enjoy!
And yeah its been about 48 hours without sleep here, trying everything and anything to get the boot.img right and me5153 had one ready instantly lol! hes the real champ here, im just putting it together and making little tweaks, i wish i knew him in person wed be neck deep in some fun over the weekend for all his work~!
And so it starts
Says Esqueue, with a huge grin on his face.
So, can I just get this straight before I flash....
I'm currently running the 996 stock ROM on my Sprint ls997. In order for me to install, is it as simple as wipe Dalvik, System, Data, Cache then flash the zip?
Seems like a noob question but with talk of other boot images I got a little confused.
Just a heads up guys. I kinda got ZV5 going
Curious, how did you get Wifi calling working again? Did you have to make changes to the kernel or some system files - or was it working off the bat? Just wanting to see if it's possible to fix it for other variants, like the AT&T H910.
N1ghtr08d said:
So, can I just get this straight before I flash....
I'm currently running the 996 stock ROM on my Sprint ls997. In order for me to install, is it as simple as wipe Dalvik, System, Data, Cache then flash the zip?
Seems like a noob question but with talk of other boot images I got a little confused.
Click to expand...
Click to collapse
Yep, that simple. Thought I was stuck until I tried turning it off and back on again. It's working great so far.
Thank you sir
---------- Post added at 04:40 PM ---------- Previous post was at 04:40 PM ----------
Or ma'am..... I don't know who you are, lol. ?
oooh. I will try this shortly. Is FM working?
As far as the Wifi calling, Prl Profile, Sprint features, Comfortview,
This was related to the Boot.img or also called the kernel, This is a device specific item that each phone would need to be
fixed and edited to work with your device/carrier. Honestly i was stuck and @me2151 had figured a way to get it to work correctly.
I have not tested Fm tuner, please let us know if it works!
as far as install procedure, please wipe all, also run the format data also, this is critical coming from the us996 roms, it needs to be clean clean clean for the first boot, all additional updates can be dirty flashed but thats on you if it FC's and is buggy.
Ill be trying to work with the other Devs here to continue to bring updates as long as i physically have the LG V20, once its EOL and ive gotten the next device ill depreciate this rom or allow a long term member to maintain or close it as fit.
Im def excited tho, this was a long 48 hours of code.. Hotspot mod is in the works, trying to get a flashable update zip out here shortly for that, but if you go to Q&A their is way to mod it yourself to get hotspot going without my help.
heres his quoted text""" @pdaddy
Download Shortcut Master Lite.
https://play.google.com/store/apps/d...cutmaster.lite
Open, click 3 dots in top right.
Click Search.
Type "apn".
Scroll and look for: com.lge.hiddenmenu.ModemProtocol.Apn.Settings
Click on it and launch it.
On Sprint it will say Access Points.
Then it has Sprint LTE Internet.
Click it and scroll down to Apn type.
Add ,dun to the end of everything on that line. (Example: default,mms,supl,hipri,dun)
Click the 3 dots in the top right and click save.
fyi : i added a old old old busybox to system/xbin { this was a mistake } go ahead and file browse and remove it prior to installing busybox from playstore to system/xbin
The reason im putting this out here is the device will not boot into recovery using rebootrecovery.sh script. Its hitting the old busybox install and failing. sorry =)
Please see below a pm from a junior member. For those looking for the FM radio fix please follow link in thread. I will be adding these into version 2.
@asyncsrc Hi there,
I just wanted to say thank you so much for creating this thread. I attempted to reply to the thread, but i got a response saying my account is too new. Having said that, I can confirm that it works on my LS997 device (WiFi calling, Youtube, etc).
For the FM radio, I used TWRP and installed the package (https://forum.xda-developers.com/attachment.php?attachmentid=3964077&d=1481366148)
Sourced thread here: https://forum.xda-developers.com/v20/help/fm-radio-u996-t3507818
The radio starts up fine with my headphones plugged in, and I'm able to listen to some local stations.
Thanks again!
Team DevDigitel said:
I'm Proud to present a Rom for the LS997 SPRINT !
This was only achievable due to @me2151 and his awesome stock-ish sprint kernel.
Please make sure to visit the dirty Santa forum and put a thanks for him and donate to HIM if you can afford to.
This is based of the ZV3 / ZV4 Images. I'm working to get the info from the ZV5 image and add a update.
See here for the Dirty Santa root and where you gotta hit thanks at for his hard A$$ [email protected][email protected][email protected][email protected]
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
PREQUISITS:
This is a DECRYPTED rom and requires that you are bootloader unlocked and have access to twrp.
If you have not wiped your system and formated data do so now, unless you want a brick...
YOU NEED TO WIPE ALL DATA AND FORMAT DATA TO USE MY ROM
Ok and the disclaimer part : I can't be held responsible for the effects of this software, it was designed for testing purposes and fun only on my free time. Please make a backup, make sure you have a computer handy with adb and fastboot and take some time to read all documents before proceeding, you've been warned.
TEAM DEVDIGITEL PRESENTS -
VERSION 1.0 - Stock Odexed, Debloated, Su, Su.d, No Encypted, Stock Lg apps re-loaded
Cf.lumen adjuster, and a ton of edits, cleanup and more. This is just the first run, and has only a few test flashes done.
Its seems to be smooth and responsive. All the stock features are included for sprint users IE: PRL and Profile updates , HFA , WIFI CALLING, Comfort view, YouTube fixes etc.
After flashing the rom, the phone will boot up with a static multi color screen, wait until you hear the phone get to the home-screen, click the power button to lock screen, once its locked and black the upper screen should show up with static only, cover the camera/proximity sensor and wait a few seconds and unlock the screen. This will only happen if you re-boot the device, other-wise its good to go.
Version 1.0 ODEXED/ROOTED -
Download Link: https://www.androidfilehost.com/?fid=385035244224410155
------------------------------------------------------------------------------------
Developer : @Team DevDigitel
and also
Thanks To:
@me2151 - LS997 / Booloader Unlock / Su / Boot.img
@Tilde88 - Files / Related Testing
@Chainfire - Root and the CF.lumen app see here : https://forum.xda-developers.com/showthread.php?t=2711912
---------------------------------------------------------------------------------
Mods and Extras : Such as bring back stock apps, or add hotspot mod will be coming soon!
Click to expand...
Click to collapse
It is working however it booted up wanting an android update. How to I remove the update reminder and block it from checking.
Related
Beware of googleys
FRANK
Layers
Day/Night theme switcher from first M preview
Init.d support
Advanced reboot
SuperSu 2.52 flashed with the rom
Volume rocker wake
Volume rocker cursor control
Long press quick settings control
Stock Like feel, please don't ask for features
Installation
Roms can change from update to update that sometimes you can dirty flash but if you have errors that other users don't then you will have to clean flash
First Time Installation:
Download the ROM and Other Optional files below.
Connect your Nexus 5 to the PC and transfer all the zips to the root of your device’s storage.
Reboot into recovery mode (Shut down, press VolDown + Power buttons. In bootloader mode, select Recovery mode)
Wipe the following partitions: System, Data and Cache
Install the ROM zip file
Let it boot. Setup now and wait for the ROM to settle.
Reboot into Recovery again and Install the remaining zip files.
Updating from previous version:
1.Download the ROM and Other Optional files below.
2.Connect your Nexus 5 to the PC and transfer all the zips to the root of your device’s storage.
3.Reboot into recovery mode (Shut down, press VolDown + Power buttons. In bootloader mode, select Recovery mode)
4.Wipe the following partitions: Dalvik-cache and Cache
5.Install the ROM zip file
6.Reboot now
7.Let it boot. Setup now and wait for the ROM to settle.
8.Reboot into Recovery again and Install the remaining zip files.
9.If have issues with dirty flash, reboot and redo steps wiping DATA also
Sources
Hammerhead GPL Kernel Source: prebuilt aosp marshmallow n5 kernel in aosp source
Rom Source: Click here
Changelog
Code:
10-19
Minor update
enable systemui tuner by default
add scanning menu into location
speed up recent app back
sprint fix included
Copy pasta from mako changelog
10-15-15
Minor update
added aldy's kernel in and turned back on usb-otg in fstab (n4)
added minkin text layout engine in thanks to @ckret for pointing it out (hammerhead had this already)
10-14-15
bug fixes!!!
some changes on the device tree so anyone using it should update
can build with clang now thanks to @ckret for pointing out the fixes (we are still gcc compiled)
Fixed downloads dark theme thanks to Branden M
Fixed supersu and layers icons being off on the dark theme, thanks Branden again
ambient display color layers inversion fix up ported from lollipop
Fix annoying usb mounting to computer (Thanks to snak3ater pointing this out to zephik)
10-13-15 update-1
added volume rocker wake (in settings/display to turn on)
add volume rocker cursor control
added animation transition animations of .25 and .75
set default animation speeds to .75
added long press recent button switches to the last app
removed the spinner from optimizing apps dialogue so it is quicker at dexopting
added long press on quick settings tile takes you to their settings menu
minor sepolicy fixes
disabled the after flash image verification (was breaking multirom flashing)
10-13 build
Fixed mac address bug thanks to this pull request
https://github.com/marshmako/device_lge_mako/commit/49b11281e25e434d7f56c4677e663e8dff87ccad
Fix a bad copy pasta of the init usb midi support
12-12
Added ambient display and full rotation
removed some debugging code
sped up a few things
Frank 10-12-15 with theme switcher, update 1
added google exchange services included in the build, it replaces exchange2
should be able to remove the layers manager icon from the launcher now
removed cell broadcast receiver
added the locked update receiver commit
beanstown found a line to set doze power saving mode that was set to off in aosp so turn it on
https://www.androidfilehost.com/?fid=24052804347836304
10-12 theme switcher update
added day/night theme switcher back to dev settings like what was in M dev preview 1 (only does settings, bluetooth and package installer so we will have to expand on this for layers), will prob move the switch out to the dashboard below layers or some place later.
added https://github.com/BenzoRom/framewor...54a3aa73367bde which should give core google apps default permissions out the box (you might still have setup wizard bug though)
Your current layers themes will only work properly in light mode
new in 10-11-2015
Removed art optimize everything till we have fully deodexed gapps
advanced reboot
init.d support
supersu and layer manager embedded in setting (you need layers manager of course) (forgot to add the hide icon part )
too tired for the rest so just read the commit history if you wanna know more https://github.com/marshmako/platfor...b5b1c3bc4419da https://github.com/marshmako/platfor...6896b4d256a871 pretty much just kanged a bunch of commits from zephik there.
new in update 1.
fixed init.d, removed aosp clock and aosp mms apps. Use updated and better google versions
added missing files for miracast
Downloads
Current Build = https://www.androidfilehost.com/?fid=24052804347841653 10-19-15
Gapps = https://www.androidfilehost.com/?fid=24052804347841244 Txuki
or
Gapps = https://www.androidfilehost.com/?fid=24052804347841070 banks
Backup Gapps down below if those don't work
gapps without setup wizard if you get wizard fc upon boot thanks to barome (modifed version without setup wizard of above)
just access play store to be able to log in with your google account
http://renderserver.net/?dl=6455ad109b871809d8f34b25a92f6904
For those interested in the commits for the theme switcher
https://github.com/marshmako/platfo...mmit/da669b1ebda7ee8ac7a39d181eb944290ce9ea72
https://github.com/marshmako/platfo...mmit/00b529c60d31e554b9c090c03f02ce06a652135a
https://github.com/marshmako/platfo...mmit/3c683a0124129bda309615a281fc3feb3ec58fde
https://github.com/marshmako/platfo...mmit/22c13d6bfd5dee4843a6fdca953350d7f56b7066
https://github.com/marshmako/platfo...mmit/4f298e8f8ab2c08f0e8c4ae92da72b01e0db6b5d
https://github.com/marshmako/platfo...mmit/4136e2ff29a84be80f8bf7f83a357fb0342e6718
Click to expand...
Click to collapse
Current layers themes will only work on light themes until adapted
OT talk is welcomed in my threads and development is done in the open. I encourage involvement in the project in any way.
Please do not complain about OT, it encourages a fun and relaxed environment
Like the work I did, consider donating. I'm currently not working so it helps feed me
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BPFLE54YPRV92
Yes, my PayPal account is thatguy32404, I like to keep my banking stuff separated from my social account
XDA:DevDB Information
[L][5.0] Frank N5 - Aosp builds in testing [1-11-2015], ROM for the Google Nexus 5
Contributors
sykopompos, bgill55
Source Code: https://github.com/marshmako
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Stable
Created 2015-02-27
Last Updated 2015-10-19
Reserved
[/HIDE]
nexus devices threads
Mako
http://forum.xda-developers.com/nexus-4/development/lpv-79-mako-port-beta-t2807446
deb
http://forum.xda-developers.com/nex...e/l-android-lpv-dev-deb-t2856915#post55016443+
flo
http://forum.xda-developers.com/nex...id-lpv-dev-flo-enhanced-t2856920#post55016534
hammerhead
http://forum.xda-developers.com/google-nexus-5/development/l-android-lpv-dev-n5-enhanced-t2856934
Look @vomer 's op for a general FAQ for L preview as those apply here along with other downloads for radio, bootloader, etc (maybe looking for my permissive boot.img or art tweaks, they are there)
http://forum.xda-developers.com/google-nexus-5/development/rom-n5-l-developer-preview-t2796003
good morning.. i will try in multirom.. thx a lot!
Best regards
Craxx
Send from my Nexus 5 with Tapatalk
Woot woot! Glad it is stable now. Kudos and great job!
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
Question. Can we now straight flash L kernels without you modifying the ramdisk? Like code blue, arkenstone etc etc?
eluspo said:
Woot woot! Glad it is stable now. Kudos and great job!
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
Question. Can we now straight flash L kernels without you modifying the ramdisk? Like code blue, arkenstone etc etc?
Click to expand...
Click to collapse
Nope. Still need the any kernel version because of how heavy of ramdisk edits that there is.
The whole ramdisk is aosp and modified for permissive selinux so flashing a boot image will crash out the whole system.
@ramjet73 is working on a ramdisk injector to replace the ramdisk in kernels that do a complete boot.IMG
WOw.... downloading .... :laugh:
sykopompos said:
Nope. Still need the any kernel version because of how heavy of ramdisk edits that there is.
The whole ramdisk is aosp and modified for permissive selinux so flashing a boot image will crash out the whole system.
@ramjet73 is working on a ramdisk injector to replace the ramdisk in kernels that do a complete boot.IMG
Click to expand...
Click to collapse
I think im going to use your modified code blue kernel for now. Thanks a lot for bringing this smoothness to n5 L.
I forgot to add in the op and will. If you are coming from the official L preview, you might experience a bunch of force closes on first boot. Just reboot about twice and it will settle down.
This is some funkiness involving selinux getting switched over to permissive.
eluspo said:
I think im going to use your modified code blue kernel for now. Thanks a lot for bringing this smoothness to n5 L.
Click to expand...
Click to collapse
shhhhh there isn't supposed to be any modified versions of his kernel distributed outside his thread, u saw how grumpy he got that we even did a test one
Will I loose my SD card by flashing this
Sent from my Nexus 5 using xda premium
sykopompos said:
shhhhh there isn't supposed to be any modified versions of his kernel distributed outside his thread, u saw how grumpy he got that we even did a test one
Click to expand...
Click to collapse
Okay haha i will be discreet about it. We dont him attacking this thread ??
stewartk said:
Will I loose my SD card by flashing this
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
It will behave exactly like the preview would when it comes to the sdcard so no you shouldn't. I don't have a n5 so o don't know if that behavior is in the preview or not.
I haven't heard anyone say anything about it on mako coming from kit kat
eluspo said:
Okay haha i will be discreet about it. We dont him attacking this thread ??
Click to expand...
Click to collapse
Yes please. He made his wishes clear. Ramjet is working in the injector which will do a reverse anykernel basically and replace the ramdisk like I did in the test.
This could be solved if the L kernel guys made a anykernel version instead of a full boot image so it wouldn't touch my ramdisk.
A lot of the magic that makes it so smooth is in the ramdisk.
sykopompos said:
Yes please. He made his wishes clear. Ramjet is working in the injector which will do a reverse anykernel basically and replace the ramdisk like I did in the test.
This could be solved if the L kernel guys made a anykernel version instead of a full boot image so it wouldn't touch my ramdisk.
A lot of the magic that makes it so smooth is in the ramdisk.
Click to expand...
Click to collapse
Okay okay haha. I can definitely feel that magic in this rom.
eluspo said:
Okay okay haha. I can definitely feel that magic in this rom.
Click to expand...
Click to collapse
Well I believe you were on the left over bunny stew so you could see the difference between the ramdisk difference and the the rest so you should be able to tell how much just the ramdisk does and then the evolution to what it is now and what makes it the complete picture.
Bet you love those 20 second boot times though
Anyways, time to get some sleep. It has been a long night and I'm hitting the caf stuff at every turn in the 1+1 L port and it is giving me a headache just thinking about it.
I'm gonna hang out with my son all day tomorrow so I won't really be on
sykopompos said:
Well I believe you were on the left over bunny stew so you could see the difference between the ramdisk difference and the the rest so you should be able to tell how much just the ramdisk does and then the evolution to what it is now and what makes it the complete picture.
Bet you love those 20 second boot times though
Anyways, time to get some sleep. It has been a long night and I'm hitting the caf stuff at every turn in the 1+1 L port and it is giving me a headache just thinking about it.
I'm gonna hang out with my son all day tomorrow so I won't really be on
Click to expand...
Click to collapse
Thanks man! Get some sleep. Have fun with your son.
Just flashed, works flawlessly, thanks for this great build!
BTW guys, you can use SuperSU, I just haven't gotten around to merging it in to replace koush's before SuperSU worked properly when fully permissive. Just make sure you use 2.02 or higher
Just an FYI, permissive just logs and doesn't actually deny anything so you will see the avc denied in logcats but it does go through.
I gotta tune the policy for hammerhead as I just did a basic aosp one for it
How would I get the home button to work. Its there just doesn't work
Sent from my Nexus 5 using xda premium
First, let's give credit where credit is due. @ZeNiXxX and @SKULSHADY are the developers of this ROM. Additional credit goes to @phhusson and @Dil3mm4 as well as:
LineageOS Team (https://www.lineageos.org)
AICP (https://www.aicp-rom.com)
MSM-Xtended Team (https://forum.xda-developers.com/one...0-pre-t3693585)
Crdroid (https://crdroid.net)
Omnirom (https://omnirom.org)
And all the other Developers, Testers, Donators and Users.
The source code which can be reviewed and continued too can be located here https://github.com/Havoc-OS and https://github.com/Havoc-Devices You can request features https://goo.gl/forms/b8rY79XtUZnd5ji42 Announcement are made here https://t.me/Havoc_OS and additional support can be requested here https://t.me/havocofficial. Finally, the official Havoc-OS page can be located here https://sourceforge.net/projects/havoc-os/files The original official thread is actually located here and was originally posted by @EnesSastim and an updated thread can be found here originally posted by @mountaser halak I, myself, @MotoX4 did full testing in verifying the support of MotoX4 having tested on several XT1900-1 (both Andriod One, Amazon Moto Retail, and * Project FI).
However, the purpose of this thread is only to bring awareness that MotoX4 users (such as yourself) do have another ROM to choose from and to include full instructions on how to install this on your MotoX4 device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Not working:
Tethering
- You tell me
FEATURES:
Code:
[SIZE="4"][B][U][SIZE="5"]General:[/SIZE][/U][/B]
System-wide Rounded UI
Full OMS support
System-wide burn-in protection
Spectrum support
Compiled using SDCLANG
Razer Phone lock/unlock sounds
OTA support
Signature spoofing
Micro-G support
[SIZE="5"][B][U]Included Apps:[/U][/B][/SIZE]
AdAway
Google Calculator
Google Markup
Lean Launcher
[SIZE="5"][B][U]Settings:[/U][/B][/SIZE]
[B][U]Battery:[/U][/B]
Battery performance profiles
Sensor block per-package
Wakelock blocker
Alarm blocker
Optimal charge level alert
[B][U]Display:[/U][/B]
Live display (Day/Night/Outside)
Colour profiles (sRGB, DCI-P3)
Font manager
Ambient display
Always on display
Expanded desktop
[B][U][SIZE="5"]Havoc Settings:[/SIZE][/U][/B]
[B][U]Status Bar:[/U][/B]
Quick pulldown
Smart pulldown
Tap to sleep
Brightness control
Battery icon styles
Bluetooth battery status
Battery bar
Battery saver color
Clock & date options
Statusbar logo
No sim network hide
Disable no sim icon
Volte icon
Network icon customization
Net activity
Custom carrier label
System icons
[B][U]Panels:[/U][/B]
Power menu tweaks
Volume dialog tweaks
[B][U]Quick Settings:[/U][/B]
Brightness slider customization
QS panel footer customization
QS layout editor
Custom header images
[B][U]Notifications:[/U][/B]
Disable fc notifications
Force expanded notifications
Disable immersive mode messages
Kill app button in notification
Screen-on notifications
Toast icon
Toast animation
Toast icon color
Toast text color
Heads up toggle
Heads up timeout
Heads up blacklist
Heads up stoplist
Snooze timer
Statusbar ticker
Ticker animation
In-Call vibration options
Less annoying in-call notifications
[B][U]Recents:[/U][/B]
Stock recents customization
Clear all button customization
Memory bar
Recent styles
Hide apps from recents
Icon pack
Immersive recents
Recents layout (Stock/Grid/Android Go)
OmniSwitch
Slim recents
[B][U]Interface:[/U][/B]
Berry styles (Light/Dark/Black/Auto)
Blur personalization
Dashboard suggestions
Dashboard conditions
Screen stabilization
[B][U]Lockscreen:[/U][/B]
Charging info
Hide statusbar
Lockscreen elements visibility
Notification count
Lockscreen colors
Clock and date options
Lockscreen alpha
Double tap to sleep
Wake and unlock
Ambient display music ticker
Ambient display bottom view (Weather/Battery/None)
Music cover art
Music visualizer
Disable power menu
Disable qs panel
Fingerprint vibration
FP unlock on boot
Face auto unlock
Custom bottom shortcuts
[B][U]Navigation:[/U][/B]
Navigation mode(Stock/Smartbar/Fling)
Dynamic navbar color
Pulse
[B][U]Buttons:[/U][/B]
Swap back and recents
Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer)
Accidental touch
Power menu customization
Long press power button torch
Disable buttons
Button backlight customization
Hardware keys customization
Swap volume buttons with rotation
Volume keys for media volume
Playback control
[B][U]Gestures:[/U][/B]
Three finger screenshot
Pie control
App circle bar
Gesture anywhere
Screen-on gestures
Touchscreen gestures
[B][U]Animations:[/U][/B]
System Animations
Android P animations
Disable animations
QS tile animations
Listview animations
Custom Bootanimation
Screen off animation
[B][U]System:[/U][/B]
SELinux mode Toggle
Smart Pixels
Suspend actions
System app remover
Allow untrusted overlays toggle (for Substratum Support)
CPU info overlay
[B][U]IME Settings:[/U][/B]
Selector notification
Auto keyboard rotation
Disable fullscreen keyboard
[B][U]Weather:[/U][/B]
Weather service settings
Statusbar weather
Lockscreen weather
[B][U]Miscellaneous:[/U][/B]
Screenshot editor
Wake on plug
Pocket detection
Camera shutter sound
Disable safe headset volume
Launch music App on headset Connection
Scrolling cache
Events[/SIZE]
How to install Havoc-OS on Moto X4
!! Please read before proceeding !!
Download the latest Official TWRP https://dl.twrp.me/payton/. - You want the .img file.
Restart your phone to your bootloader. - You do this by pressing and holding both your phone's power button and the lower volume key at the same time.
Once at your phone's bootloader, from your Windows Command Prompt (as administrator) or from your Linux Terminal (as root) run the following command to load TWRP:
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste the example posted here).
!! You will be wiping everything because regardless if you are coming from stock or a different ROM as this ROM works best with a full wipe !!
Note: If upgrading this ROM a full wipe is not necessary. See upgrade instructions below.
Regardless of what ROM you are coming from (stock or not), format your DATA.
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Regardless of what ROM you are coming from (stock or not), select "advanced wipe" to wipe your device (select all partitions).
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
If coming from stock:
Download "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Upload "Copy Partitions Zip" to your phone using the "ADB Push" command to /sdcard/ (run as admin if on windows or as root if on Linux).
Code:
adb push copy-partitions-payton.zip /sdcard/
Now INSTALL "Copy Partitions Zip"
Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
Download the firmware for your phone
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
Latest firmware for payton_fi android 9 from PPW29.69-26 - courtesy @ptn107
firmware-29.69-26_payton-fi_xt1900-1.zip
Unzip on your computer.
User flash_all.bat if on windows as administrator OR ./flash_all.sh if on Linux as root.
Reboot your phone to bootloader
Continue:
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download and locate the latest Amr64 A/B ROM located here: https://sourceforge.net/projects/havoc-os/files/arm64-ab/ - NOTE: You want the ROM that comes without Gapps. You can install Gapps after (see instructions below).
Extract the zip (XZ file) onto your computer. -- I suggest the free and open source program 7zip https://www.7-zip.org/
You will upload these files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img /sdcard/
In TWRP select Install *
Select Install image
Locate your .IMG file and flash it to "SYSTEM"
* TWRP troubleshooting:
A small group of individuals has reported that TWRP will not correctly install IMG files directly. If you're one of those few people a manual install may work for you.
First wipe your phone again
Reboot back to bootloader. - Stay at bootloader
As an administrator on windows or as root on Linux run this command
Code:
fastboot -u flash system Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste the example posted here).
Credit to @*.jpg for this solution.
NOTE: Do NOT yet install Gapps. See instructions below.
After a successful install, REBOOT your phone.
Congratulations, you're done!
If adding Gapps: -- Read me
Your phone will work perfectly fine without Gapps. But if you do want to install Apps and use Google products and services; I recommend the minimal Gapps install known as Pico. You can learn about the many different Gapps flavors by visiting the Open Gapps Wiki found here https://github.com/opengapps/opengapps/wiki/Package-Comparison
Let your phone boot the ROM for the 1st time. - !! IMPORTANT !! You want to fully boot your phone and let the ROM load for the 1st time before installing Gapps.
After your phone as successfully booted up and loaded the ROM, reboot back into recovery
Download the latest Gapps - https://opengapps.org
Upload the zip to your phone
Install Gapps
Wipe cache/dalvik
Additionally, if you're one of those paranoid people who want to keep your distance away from Google (to each their own, but I love me some Google ) you do have the following alternatives.
https://apkpure.com/
https://en.uptodown.com/android
https://f-droid.org
Just remember that these are unofficial sources and you take the risk that can potentially come with them.
UPGRADING - How to upgrade this ROM.
Also known as a dirty upgrade, you do not need to wipe everything and start over. However, if this dirty upgrade fails a fresh install is recommended.
Download the latest ROM
Reboot into recovery
Install your new .img file
Wipe cache/dalvik
Reboot
If all has gone well you're done! If not, a full wipe and install are recommended.
* Project Fi
If you do not have Google Project Fi as your cellular provider, you can ignore this.
The Google Project Fi app will inform you that you cannot activate using this GSI/Rom. Assuming, you have already previously activated your phone before trying out new GSI/ROM's, you can technically, safely ignore this warning as you will still be able to send and receive calls, text, data, etc... and continue to use the Project Fi app to manage your account. However, if this is your first time activating or you simply wish to be sure you get the latest carrier and tower updates (recommended), this fix is for you.
First let's give credit where credit is due. @Sass86oh for originally coming up with this fix here and a personal thanks to @johnjingle for pointing this out to me here.
Google Project Fi Fix
You will need to make a minor and yet important edit to your system before installing the Project Fi app. If you have already installed the Project Fi app before making this edit, you should close the app, clear both the app's cache and clear the app's storage, then proceed to uninstall the Project Fi app.
Using your preferred root text editor navigate to /system/
Locate the file build.prop
Carefully make the following changing, listed below, to the file build.prop
!! Important !! Double check you have correctly made the correct changes.
Save your changes
REBOOT your phone
Go to: Setting > System > About
Verify that your device model is a Moto x4
Install Project Fi
Open Project FI and proceed with the activation
Congratulations, you're done!
!! IMPORTANT !! These values are CASE SENSITIVE which means if you type "Payton" rather than "payton" it will NOT work !! Be sure you double-check what you type before saving !!
Locate and edit to match. -- Do NOT rush (Do NOT be in a hurry). This is something you want to carefully take your time with.
Code:
ro.product.model=Moto x4
ro.product.brand=Motorola
ro.product.name=payton
ro.product.device=payton
ro.product.manufacturer=Motorola
ro.build.product=payton
ro.opa.eligible_device=true
Headphone jack fix found here. credit: @abrfilho
????
Battery is great in this rom, here I just can't change color profile and use the wide lens, is there a way to fix that?
I followed the instructions closely but still can't boot up. Always return to bootloader after I flash the image. Latest twrp, I did notice that the slot don't change.
abrfilho said:
Battery is great in this rom, here I just can't change color profile and use the wide lens, is there a way to fix that?
Click to expand...
Click to collapse
On other roms installing moto camera is supposed to work with 2nd camera. I haven't tried it, just read it.
SchmilK said:
On other roms installing moto camera is supposed to work with 2nd camera. I haven't tried it, just read it.
Click to expand...
Click to collapse
Yeah, when I was using phh's Pie AOSP I was able to use the wide lens, even on modded GCam, but here I'm not able. ?
I already installed Moto Camera here.
For some reason, the .img file wouldn't install from TWRP, but flashing it from bootloader finally worked after several attempts. I ended up using the copy partitions installer and it finally worked. I was coming from Lineage 15.1 so I don't know whether this can help anyone else. I look forward to giving Havoc a try!
*.jpg said:
For some reason, the .img file wouldn't install from TWRP, but flashing it from bootloader finally worked after several attempts. I ended up using the copy partitions installer and it finally worked. I was coming from Lineage 15.1 so I don't know whether this can help anyone else. I look forward to giving Havoc a try!
Click to expand...
Click to collapse
How can you do that? I think I can't just fastboot flash havoc.....img right?
I installed via TWRP, but I am stuck at the android loading screen. I will try to re-flash I guess.
khanhlinh said:
How can you do that? I think I can't just fastboot flash havoc.....img right?
Click to expand...
Click to collapse
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
I rebooted to TWRP and installed the OpenGapps 9.0 micro version which went smoothly.
Code:
fastboot -u flash system [*your GSI here*].img
This command worked for me. I'm setting up TiBu and the remainder of my apps now.
---------- Post added at 12:35 PM ---------- Previous post was at 12:15 PM ----------
Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img doesn't appear to be rooted. I don't want to foul anything up by installing an alternate root by mistake. Is there somewhere in the ROM to activate it or is it okay to flash Magisk? (Or SuperSU or whichever)
*.jpg said:
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
I rebooted to TWRP and installed the OpenGapps 9.0 micro version which went smoothly.
This command worked for me. I'm setting up TiBu and the remainder of my apps now.
---------- Post added at 12:35 PM ---------- Previous post was at 12:15 PM ----------
Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img doesn't appear to be rooted. I don't want to foul anything up by installing an alternate root by mistake. Is there somewhere in the ROM to activate it or is it okay to flash Magisk? (Or SuperSU or whichever)
Click to expand...
Click to collapse
You can flash Magisk without a problem.
khanhlinh said:
I followed the instructions closely but still can't boot up. Always return to bootloader after I flash the image. Latest twrp, I did notice that the slot don't change.
Click to expand...
Click to collapse
I am having the same issue, except I get to the android text sometimes. I have tried installing the rom with gapps and w/out.
Not sure what I am doing wrong I came from Lineage trebelized and I did wipe everything even internal storage. Should be simple.
*.jpg said:
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
Click to expand...
Click to collapse
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
absaget0 said:
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
Click to expand...
Click to collapse
I only managed to enter system with GApps version by disabling all networks (removing SIM and not connecting to wifi), but everytime prompted some login, I could configure without a problem using the normal version with GApps flashed.
absaget0 said:
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
Click to expand...
Click to collapse
Same issue for me, I finally got both to boot, but I am now stuck at checking info too.
Nice work bro... Please keep it live and update it time to time
johnjingle said:
Same issue for me, I finally got both to boot, but I am now stuck at checking info too.
Click to expand...
Click to collapse
can you skip if you turn the phone off and on again?
xdacinq said:
can you skip if you turn the phone off and on again?
Click to expand...
Click to collapse
unfortunately no. at the same position i got the loop. But the Version without gapps worked.
Well, I'm puzzled why some of you are having so many issues. I had 3 MotoX4's to play with and all of them worked without issue. Granted, all 3 are XT1900-1 devices and I wouldn't imagine a big different between XT1900-1 through 7. Did this with the original Amazon Moto Retail (the one which says Moto and not Andriod One), plus the Andriod One I got from Motorola and finally the Project Fi phone too (also an Andriod One edition), but none of them had the issues some of you are reporting. -- Which is why I felt confident sharing this in this forum.
I will add that I always used the ROM without Gapps included (and later installed Gapps after adding the ROM). Gapps tends to update often and I wanted to start fresh with the latest edition, so I installed the Rom without Gapps, confirmed that all was working, and then rebooted back into recovery and installed Gapps (as instructed in post 1).
For the few of you reporting issues... Perhaps start from scratch (as if coming from stock) and see if that resolves things.
I included this in the instructions and someone who sent me a PM made it clear where they were making mistakes. -- DO NOT install Gapps right away. Load the ROM 1st (let your phone boot up the ROM as if you're done and then reboot and install Gapps). I made this clear in my instructions and I think some folks are ignoring that little bit (those of you getting the "checking info" message).
Disclaimer: I am not responsible for anything bad that may occur with your device, but I will take all the credit you can give me if it works for you!
After some months of hard work I would like to present MIUI ROM for our device (Teclast T8)! It was ported by me from Xiaomi MIPAD 3. There are still some bugs I can't fix yet. So, just test it and let me know about issues/bugs i missed. I hope you will enjoy this ROM
This version is only for flashing via TWRP! (it can be found here https://forum.xda-developers.com/android/help/twrp-root-custom-recovery-teclast-t8-t3892647)
Version Information
Status: stable!
Created: 12.03.2019
Updated: 06.07.2019
Android version: kernel 3.18.35, android 7.0 Nougat
What's done/features
Added ROOT (Magisk)
No bugs with battery statistics (like it was on stock ROM)
Unique MIUI design and customization (navbar and more)
Special icon pack (from another Xiaomi device)
New useful functions (split screen)
All main modules work (camera, wifi, BT, etc)
All Apps (MiVideo , etc) should be updated to the latest version for correct work !
Bugs
Double tap to awake function
Gestures
No fingerprint :crying:
Average battery consumption (device doesn't go to sleep mode) - SOLVED!
Installation
Download firmware to internal storage
Reboot into TWRP
Do this wipes in Wipe section: system, cache, dalvik,data
Reboot recovery: go to reboot section -> choose Reboot recovery
Go to install section and choose .zip package
After installation completed just reboot device and enjoy
If you face error "failed to mount system" or something like this after installation completed - don't mind it and reboot
Fixes
1) Battery draining fix
Finally, this fix is permanent!
Download all required files in internal memory, link is below.
After that open magisk manager and go to Modules.
Choose Init.d-Injector_v2.3, wait until installation is completed and reboot your device.
Make init.d folder in system/etc so the full file path should be system/etc/init.d.
Place fingerprint_fix script in init.d folder and set equal permissions for both file and folder: 0755 , it should look like "П".
Reboot your device and enjoy
Screenshots
Download
The link is here - https://drive.google.com/drive/folders/1NPupJhBmRJRtHfGkk6aQ40KO_YMiQSEw?usp=sharing
If you would like to support further development - https://www.paypal.me/teclastT8development
MIUI firmware development is stopped.
Nice work!
Thank you!!
I have tested the ROM for several weeks and the result, to be a beta, is frankly good. On the negative side, only highlight that I couldn't add any widget. When I give to add widget, only 1x1 size is available. I couldn't put the clock with the weather, for example.
Please, keep it up, do not forget about MIUI, and thank you very much for your work!
Sword900 said:
Disclaimer: I am not responsible for anything bad that may occur with your device, but I will take all the credit you can give me if it works for you!
After some months of hard work I would like to present MIUI ROM for our device (Teclast T8)! It was ported by me from Xiaomi MIPAD 3. There are still some bugs I can't fix yet. So, just test it and let me know about issues/bugs i missed. I hope you will enjoy this ROM
This version is only for flashing via TWRP! (it can be found here https://forum.xda-developers.com/android/help/twrp-root-custom-recovery-teclast-t8-t3892647)
Version Information
Status: BETA (NOT for everyday usage)
Created: 12.03.2019
Android version: kernel 3.18.35, android 7.0 Nougat
What's done/features
Added ROOT (Magisk)
No bugs with battery statistics (like it was on stock ROM)
Unique MIUI design and customization (navbar and more)
Special icon pack (from another Xiaomi device)
New useful functions (split screen)
All main modules work (camera, wifi, BT, etc)
All Apps (MiVideo , etc) should be updated to the latest version for correct work !
Bugs
Double tap to awake function
Gestures
No fingerprint :crying:
Average battery consumption (device doesn't go to sleep mode)
Installation
Download firmware to internal storage
Reboot into TWRP
Do this wipes in Wipe section: system, cache, dalvik,data
Reboot recovery: go to reboot section -> choose Reboot recovery
Go to install section and choose .zip package
After installation completed just reboot device and enjoy
If you face error "failed to mount system" or something like this after installation completed - don't mind it and reboot
Screenshots
Download
The link is here - https://mega.nz/#!ywokTQ5Z!vyvKy28V2ssQkXdHeh_uotVhhwBfPxm8xyOnnSMn7nI
If you would like to support further development - https://www.paypal.me/teclastT8development
P.S For now MIUI firmware development is stopped due to my studing and "busy days"
Click to expand...
Click to collapse
nerojdn said:
Thank you!!
I have tested the ROM for several weeks and the result, to be a beta, is frankly good. On the negative side, only highlight that I couldn't add any widget. When I give to add widget, only 1x1 size is available. I couldn't put the clock with the weather, for example.
Please, keep it up, do not forget about MIUI, and thank you very much for your work!
Click to expand...
Click to collapse
Thanks for your feedback! I didnt't check widgets, so I will but later. . . For now, I assume that this problem is connected with original MIpad firmware as if it is still in development. The biggest problem in this ROM is battery draining and I don't know how to fix it. Let me know if you find any other issues.
P.S. You also can check other stable ROM, e.g Pixel Experience. It has not been tested yet by other users except me. You can find the link in TWRP thread.
Finally, MIUI becomes a stable ROM!
So, test it again and let me know if you find any other critical issues.
Hi, I'm looking for a cheap tablet for web browsing and watching videos. was thinking of picking up a used nexus 9 for about $70. I know older devices run slow I guess cause of aging ram that doesn't perform as well as it use to. I'm wondering if it would be slow or would it perform like it was when it was newer?
One word answer. Maybe!
slightly longer answer. As long as it`s still used regularily the n9 is a ideal tablet. Battery may need replacing and an upto date rom is a must. Mine still holds its own 5 years on.
quit a bit slow. last year i used it to study. I think It should be upgrading to 4Gb memory
doop said:
One word answer. Maybe!
slightly longer answer. As long as it`s still used regularily the n9 is a ideal tablet. Battery may need replacing and an upto date rom is a must. Mine still holds its own 5 years on.
Click to expand...
Click to collapse
I ended up buying one on ebay last night. probably keep the stock rom on it but remove forced encryption.
For this price is a good device...yes, it can run yet well (in my opinion,the ram memory was the problem on this device)
_N9, for run better and perform better,my opinion is: Remove forced encryption / Install FireIce kernel / Install Gov-Tuner Project / some build.prop tweaks - Stay in stock rom,it works more stable than any custom rom...(only Slim Stable 7.1.2.build.2.0 works very fine)
Slim Rom downloads: https://slimroms.org/#/download
(you can remove some applications,which are not used frequently and consuming pores from the system)
* because of a little ram on this device,we only install the necessary applications! stay away especially from social applications,like facebook etc..
__ DM-VERITY, FORCED ENCRYPTION : https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
__ https://forum.xda-developers.com/nexus-9/orig-development/kernel-fire-ice-t2930451 (FireIce kernel)
__ https://forum.xda-developers.com/an...mod-gov-tuner-project-29th-june-2016-t3407828 (GovTuner)
[ Gov-Tuner_4.1.1 .zip : https://mega.nz/#!NrAEEKAR!rx3FN_nELKK43C_LWSk0cOUqZGIK2daUZLzREAojWFw
Gov-Tuner_4.2 .zip : https://mega.nz/#!MuJEBYAI!DMsG_H-IKsVKNxIp_A0AWEpTcC9atiAQc2-xR4cJpSU ]
(maybe you need,depending on what you want : Universal Init.d Injector & kernel sepolice patcher : https://zackptg5.com/android.php#disverfe )
https://forum.xda-developers.com/android/general/guide-build-prop-tweaks-t3376962 (use it with extreme caution!)
I had tried every other way and custom rom,and no one was running on my device so well like this way (Ι don't have the device anymore)
[we can Install Vanced Tube instead of the official youtube app:
https://forum.xda-developers.com/android/apps-games/app-youtube-vanced-edition-t3758757 ]
__ screenshots : https://postimg.cc/gallery/29qbhczpa/
Τhis is just my opinion,and it means nothing more than that!
sry for english
daitalos said:
For this price is a good device...yes, it can run yet well (in my opinion,the ram memory was the problem on this device)
_N9, for run better and perform better,my opinion is: Remove forced encryption / Install FireIce kernel / Install Gov-Tuner Project / some build.prop tweaks - Stay in stock rom,it works more stable than any custom rom...(only Slim Stable 7.1.2.build.2.0 works very fine)
Slim Rom downloads: https://slimroms.org/#/download
(you can remove some applications,which are not used frequently and consuming pores from the system)
* because of a little ram on this device,we only install the necessary applications! stay away especially from social applications,like facebook etc..
__ DM-VERITY, FORCED ENCRYPTION : https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
__ https://forum.xda-developers.com/nexus-9/orig-development/kernel-fire-ice-t2930451 (FireIce kernel)
__ https://forum.xda-developers.com/an...mod-gov-tuner-project-29th-june-2016-t3407828 (GovTuner)
[ Gov-Tuner_4.1.1 .zip : https://mega.nz/#!NrAEEKAR!rx3FN_nELKK43C_LWSk0cOUqZGIK2daUZLzREAojWFw
Gov-Tuner_4.2 .zip : https://mega.nz/#!MuJEBYAI!DMsG_H-IKsVKNxIp_A0AWEpTcC9atiAQc2-xR4cJpSU ]
(maybe you need,depending on what you want : Universal Init.d Injector & kernel sepolice patcher : https://zackptg5.com/android.php#disverfe )
https://forum.xda-developers.com/android/general/guide-build-prop-tweaks-t3376962 (use it with extreme caution!)
I had tried every other way and custom rom,and no one was running on my device so well like this way (Ι don't have the device anymore)
[we can Install Vanced Tube instead of the official youtube app:
https://forum.xda-developers.com/android/apps-games/app-youtube-vanced-edition-t3758757 ]
__ screenshots : https://postimg.cc/gallery/29qbhczpa/
Τhis is just my opinion,and it means nothing more than that!
sry for english
Click to expand...
Click to collapse
Can I use nexus root toolkit to remove forced encryption on my nexus 9 running android 7.1.1? I notice where it says select the android build you are currently running, mine isn't there. is it safe to use the "any build" option. and follow the directions in this video? https://www.youtube.com/watch?v=lFVpr6IoL-Q&feature=emb_title
Gabe3 said:
Can I use nexus root toolkit to remove forced encryption on my nexus 9 running android 7.1.1? I notice where it says select the android build you are currently running, mine isn't there. is it safe to use the "any build" option. and follow the directions in this video? https://www.youtube.com/watch?v=lFVpr6IoL-Q&feature=emb_title
Click to expand...
Click to collapse
the Rootjunky in video he knows well & has experience ...BUT ! Look at the title of video carefully ...Says "Lollipop data Encryption"...your android version is N
also,this video is from 2014 ! therefore, very old file
So,my opinion is : you can use TWRP & DM-VERITY & FORCEENCRYPT DISABLER file + magisk (or su) , very easy... - recommended
daitalos said:
the Rootjunky in video he knows well & has experience ...BUT ! Look at the title of video carefully ...Says "Lollipop data Encryption"...your android version is N
also,this video is from 2014 ! therefore, very old file
So,my opinion is : you can use TWRP & DM-VERITY & FORCEENCRYPT DISABLER file + magisk (or su) , very easy... - recommended
Click to expand...
Click to collapse
sounds complicated, guess I have alot of searching to do.
Gabe3 said:
sounds complicated, guess I have alot of searching to do.
Click to expand...
Click to collapse
It's not complicated at all.... you just start with the right series - right way
1-unlock bootloader
2-Install TWRP
3- Install slim stable 7.1.2 - [ Nano Gapps /disable encrypt/ magisk (or su) ]
4- Flash FireIce kernel
5-Flash Gov-Tuner (download Universal Init.d Injector & kernel sepolice patcher(or better The SELinux Switch) to change SeLinux to permissive( https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502 )
,download kernel adiutor from playstore & use it, etc...
It takes a little time, but no need hurry of course
daitalos said:
It's not complicated at all.... you just start with the right series - right way
1-unlock bootloader
2-Install TWRP
3- Install slim stable 7.1.2 - [ Nano Gapps /disable encrypt/ magisk (or su) ]
4- Flash FireIce kernel
5-Flash Gov-Tuner (download Universal Init.d Injector & kernel sepolice patcher(or better The SELinux Switch) to change SeLinux to permissive( https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502 )
,download kernel adiutor from playstore & use it, etc...
It takes a little time, but no need hurry of course
Click to expand...
Click to collapse
I did steps 1 and 2, then I installed fed patcher v8. but I'm not sure if it worked. heres a screenshot. also I ran this adb command "adb shell getprop ro.crypto.state" and it said its encrypted.
I wiped everything except the system partition before flashing fed patcher. after some research, I think I'm suppose to use the format data option?
Gabe3 said:
I did steps 1 and 2, then I installed fed patcher v8. but I'm not sure if it worked. heres a screenshot. also I ran this adb command "adb shell getprop ro.crypto.state" and it said its encrypted.
I wiped everything except the system partition before flashing fed patcher. after some research, I think I'm suppose to use the format data option?
Click to expand...
Click to collapse
It looks like your device hasn't decrypted...
I know well fed patcher & I've used it in the past on N9...BUT! personally I choose Universal DM-Verity, ForceEncrypt.... (this is just my opinion and nothing else)
anyway , you must read carefully in fed patcher OP > "How do I use it?" & "What do I need to make this work?"
.... and just, follow the instructions..I think it will work without any problems
For any questions about "fed patcher" you will ask in the thread before doing anything on the device !!
https://forum.xda-developers.com/an...-fed-patcher-v8-forceencrypt-disable-t3234422
** https://forum.xda-developers.com/showpost.php?p=63550803&postcount=3
** https://forum.xda-developers.com/showpost.php?p=76374722&postcount=172
daitalos said:
It looks like your device hasn't decrypted...
I know well fed patcher & I've used it in the past on N9...BUT! personally I choose Universal DM-Verity, ForceEncrypt.... (this is just my opinion and nothing else)
anyway , you must read carefully in fed patcher OP > "How do I use it?" & "What do I need to make this work?"
.... and just, follow the instructions..I think it will work without any problems
For any questions about "fed patcher" you will ask in the thread before doing anything on the device !!
https://forum.xda-developers.com/an...-fed-patcher-v8-forceencrypt-disable-t3234422
** https://forum.xda-developers.com/showpost.php?p=63550803&postcount=3
** https://forum.xda-developers.com/showpost.php?p=76374722&postcount=172
Click to expand...
Click to collapse
I figured it out, had to format data.
I haven't touched encryption, used ADB though to reduce installed apps ( for user 0 ) to 65, old nexus 9 more responsive & can be left on for days at a time whilst idle, more RAM available for user too. Also, all those removed apps aren't trying to 'phone home' with Telemetry now. Used for browsing & downloading movies it's perfectly acceptable.:good:
GravityBox - all-in-one tweak box - Xposed module for devices running Android 11
Version 11.0.5 [R]
Version for JellyBean is available in this thread: https://forum.xda-developers.com/showthread.php?t=2316070
Version for KitKat is available in this thread: https://forum.xda-developers.com/showthread.php?t=2554049
Version for Lollipop is available in this thread: https://forum.xda-developers.com/showthread.php?t=3037566
Version for Marshmallow is available in this thread: https://forum.xda-developers.com/showthread.php?t=3251148
Version for Nougat is available in this thread: https://forum.xda-developers.com/showthread.php?t=3653953
Version for Oreo is available in this thread: https://forum.xda-developers.com/showthread.php?t=3739929
Version for Pie is available in this thread: http://forum.xda-developers.com/showthread.php?t=3908768
Version for Q is available in this thread: http://forum.xda-developers.com/showthread.php?t=3974497
READ THIS POST CAREFULLY BEFORE PROCEEDING ANY FURTHER
Introduction
The app utilizes Riru-EdXposed Magisk module which uses original Xposed Framework API created by rovo89.
!!!!!! WARNING !!!!!!
This module utilizes EdXposed Framework which is still in early development stage and may contain bugs or might not be fully compatible with the system of your Android device. I take no responsibility for any issues arising from using GravityBox with EdXposed and strongly recommend creating a full backup of your device before activating the module.
Requirements
- Magisk v21 or later
- Riru v23 or later (Magisk module)
- EdXposed Manager (Application)
- Avoid using Resource hooking support if possible (Can be disabled in EdXposed Manager settings)
Installation
This procedure assumes you have working Magisk installation.
1) Install Riru module in Magisk Manager
2) Install and run EdXposed Manager app and download Riru-EdXposed module v5.1.3.x or later (currently Alpha/Canary)
3) Install downloaded Riru-EdXposed module in Magisk Manager
5) Reboot and open EdXposed Manager app to check if EdXposed works and is active
6) Install GravityBox and enable it in EdXposed Manager
7) Reboot and profit
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
- Keyboard app (e.g. Gboard) in order to be able to use "Volume key cursor control" feature
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.
Feature highlight
--- Lockscreen tweaks
--- QuickSettings tile management with additional tiles
--- Statusbar tweaks
--- Navigation bar tweaks
--- Pie controls
--- Power tweaks
--- Display tweaks
--- Phone tweaks
--- Media tweaks
--- Hardware/navigation key actions
--- GravityBox Actions - interface for 3rd party apps
--- Notification control (per-app notification LED/sounds/vibrations)
--- Fingerprint launcher
--- Advanced tuning of Framework and System UI parameters
... and many more
Compatibility
GB's main concept is to make most of the preference changes to be done on the fly without need to reboot a device to achieve custom-ROM like experience.
This means it is not possible to "completely deactivate" particular feature if it causes trouble on your device or if you installed GB because you want to use only one particular feature you can't find elsewhere.
This results in issues on ROMs/devices that have parts that are diverting from default Android implementation too much, or are running heavily modified custom ROMs.
If you experience weird issues after installing GB, even if you didn't activate a particular feature, it is not because of GB is broken, it is because it is not compatible with your ROM.
It is very similar to a situation when you installed ROM built from source for Nexus to some Xperia device - it won't work.
GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source, and you are missing a certain feature, your best option is to go ask creators of those ROMs to implement those additional features. Supplementing missing features on well-known custom ROMs built from source by installing xposed modules (especially complex ones) is definitely not a good way to go and can cause more trouble than good.
GB being a complex module, it shouldn't be combined with other complex modules often racing for the same goal. They can conflict/fight on the same playground and there's no way you can deterministically say which one's going to win. They can even lose both.
So in summary:
- this module is designed to run on vanilla or close-to-vanilla Android 11 (AOSP)
- officially supports devices/systems it was developed and tested on
- Samsung, HTC, MIUI, Xperia, Lenovo, etc. are NOT supported. It is not guaranteed this module will work on these at all so try at your own risk. This module is simply too complex to support all kind of ROM brands that were vastly modified by vendors.
- DO NOT USE WITH CUSTOM ROMS MODULE WAS NOT EXPLICITLY DESIGNED FOR
- I will not implement any exceptions that will adapt this module to a specific custom ROM. Please, do understand, it is unmanageable.
- I will not provide any support for devices violating these compatibility rules
GravityBox [R] has been designed for and tested on
- Pixel 3a running Google OS
- OnePlus 7Pro running Oxygen OS 11
Reporting bugs
If possible, please use Github issue reporting interface for reporting bugs.
If you experience problems with certain feature, provide the full-detailed info that can help me
to reproduce the bug and attach logs that can be exported from EdXposed Manager app.
Real-time logging can be performed by using ADB: adb logcat -s EdXposed-Bridge
In case you experience SystemUI crashes or other apps Force Closing, or device soft reboots, attach logcat from time
crash occurs. (use adb logcat *:E or your favorite logcat app from Play Store).
Please, don't attach big logs. Only the portion where error is clearly seen.
Disable all other xposed modules before reproducing bug to make sure it is really GravityBox related
Remember, this app was developed and tested on one particular device so it is not guaranteed that it will work flawlessly on yours.
Multilanguage support
Volunteers are welcome to translate GravityBox to other languages.
Preferred way is to use GitHub interface to fork your own copy of GravityBox, make changes and then send pull request against original repository.
Anoter way is to simply download this file: https://github.com/GravityBox/GravityBox/raw/r/GravityBox/src/main/res/values/strings.xml
Use Notepad++ to edit strings and then send me edited file so I can include translations into next release.
Source code
GravityBox is opensource. Sources are available in my gihub: https://github.com/GravityBox/GravityBox/tree/r
If you're a dev and have some ideas for additional features, feel free to fork it, work on it and send the pull requests.
Copyright notice
https://github.com/GravityBox/GravityBox/blob/r/NOTICE
Support development
Coding, maintaining and supporting this project costs me a lot of my precious time. If you find this project useful, you are more than welcome to support its development via donation. This form of support is meant to compensate for my time dedicated to the community + eventually, help me to afford newer device to keep up with AOSP evolution thus providing continuous support as Android evolves. Thanks!
Info about premium features and PayPal transaction ID verification system
1) Those who supported development via PayPal donation can use their PayPal transaction ID to unlock premium features.
As of v2.9.5, there are three premium features:
- Backup/restore of GB settings.
- Ultimate notification control
- Advanced Tuning
2) If you contributed to the project by providing translations, code fragments, or by any other way
you can apply for a free transaction ID by contacting me via PM.
3) Be aware that there's a system that can identify potential transaction ID
abuse. E.g. when one ID is being used by more users. Such IDs will get blocked automatically.
In case you own more devices, you can use one transaction ID on up to 10 of them.
4) If you are using your own custom builds of GB for personal use, you will get hash mismatch
upon verifying your ID as verification system accepts requests only from official releases of GB.
If you want to be able to verify IDs with your custom build, contact me via PM so I can setup
a special hash for your build.
If you are using a custom build that you provide for broader group of users (e.g. in a custom ROM),
it is necessary to ask for new hash everytime your new custom version is released for public use.
These rules are based on mutual trust so please, do not violate them.
Credits
- RikkaW for creating and maintainng Riru Magisk module
- solohsu & MlgmXyysd for creating and maintaining EdExposed Magisk module
- @frank93 for donating Pixel 3a for development
- @bgcngm for his code contributions to the project
- @MohammadAG for Xperia specific contributions to the project
- @rovo89 for his ultimate Xposed framework and "Volume keys to skip track" mod
- @peptonib for starting me up with this project
- @simmac for app icon
- @romracer for Motorola specific code contributions
- @firefds for Samsung specific code contributions
- CyanogenMod project
- ParanoidAndroid project
- Slim, RootBox, AOKP, OmniROM projects
- Sergey Margaritov for ColorPickerPreference
- ArthurHub for Image cropping library
- All those who provided translations for different languages (Mr.Premise, peptonib, kidmar, ch-vox, romashko, Indiant, lelemm, oicirbaf, unavix, LuHash, WedyDQ10, mp3comanche, awaaas, liveasx, samsonbear, Eric850130, xtrem007, benjoe1, asmb111, Fatih Firinci, ...)
- and finally, all those who keep the project alive by supporting me via donations (you know who you are)
Changelog
https://github.com/GravityBox/GravityBox/blob/r/CHANGELOG.txt
Changelog 11.0.5 - 08/08/2021
- Lockscreen: added option to blur media artwork on lockscreen (thanks to robbins)
- Navbar: allow cursor control keys in gestural navbar
- Dialer: adjusted for compatibility with the latest Google Dialer
- Properly identify OnePlus 8T as device running OxygenOS ROM (thanks to F-i-f)
--- should improve compatibility significantly
Developed and tested on:
- Pixel 3a running Google OS
- OnePlus 7Pro running Oxygen OS 11
Current issues
- Display: Expanded Desktop - immersive modes not working
- Key actions: Home double-tap not working
- Lockscreen: Changed custom carrier text won't appear immediately
- Custom Battery indicator: stock battery may appear for a while after the reboot
- ... + potentially others mainly device/system variation specific
Removed features
- GPS and SlimKat tiles - location modes (battery saving/high accuracy/device) no longer exist in Android 11
- Audio Recording tile - background recording of audio not possible in Android 11
Download
https://github.com/GravityBox/GravityBox/releases/tag/v11.0.5_r
Settings
It is possible to restore settings that were backed up in GravityBox [Q]
Simply transfer "GravityBox" folder from internal storage of one device to internal storage of another device.
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
- Keyboard app (e.g. Gboard) in order to be able to use "Volume key cursor control" feature
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.
Credits
@frank93 for donating Pixel 3a for developemnt
Commit history
Commit history for transition from 11.0.4 to 11.0.5
@C3C076
Mate, you did it. Congratulations.
Can't wait to try it out.
Really appreciate your efforts in bringing this to us 11ers.
Cheers
2021 is looking good! Thank you so much. Working flawlessly on my pixel 3a
@C3C076
THIS is the first gift I've received of the new year. Thank you, sir!!!
Now, that's pretty awesome!
And the January update from Google should drop soon as well.
Thanks a lot @C3C076!
Got my Github notification this morning about the [R] pre-release! Just now updated my Pixel 4 XL from 08-2020 (Android 10) to 09-2020 (Android 11) using my keep root / seamless update method with no problems. Everything working perfectly fine! All I had to do was first disable GravityBox [R] in EdXposed Manager, and disabled Kirisakura AK3 (kernel) module helper in Magisk Manager. Upgraded to Android 11 with no issues at all, and everything system and root-wise seems to work perfectly fine. My current running list of Magisk / Xposed modules: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84193393
(I'm hoping @Ghisy finds this helpful, hehe)
Though I'm gonna play it safe and OTA each month, instead of factory image (sans "-w" flag) jumping. Gonna work my way up to the current firmware, then test out GravityBox [R] - thanks so much @C3C076! The fact that so many people like me have held off on upgrading to the latest Android version just based on your work should speak volumes! I'll report back once I'm able to actually play around with GB[R] some. The baby's starting to wake... :O
edit: my son rolled over, coo'ed, and faceplanted back to sleep <3
- Also should note, I was on Kirisakura 5.2.6 kernel before. Now on 6.6.0, all is well!
- Also wanted to note, SafetyNet was passing (with my current configuration) on 09-2020 build with no further modifications necessary. I just finished updating up to 12-2020, and SafetyNet is still passing . Activating GravityBox module now, and will further report back!
edit 2: Seems verrrry stable so far! The only thing I found that didn't work properly (or rather, worked 80% correctly) was for an option that I don't even normally use, and accidentally toggled, haha. Under QuickSettings management -> Tiles per header, each option works fine, but when selecting 8, it still only shows 7.
Other than that, at least as far as the options that I personally use, everything seems fine! I didn't get a chance to test out every function affected by my set of GB options in such a short time, of course, but I will certainly report if there are any issues. And of course I won't list every single option I ticked off, but attached is my backup file / preferences of my current config for anyone who may be curious. Again, keep in mind that compared to the vast functions GB offers in totality, I only use what I use so of course I can't account for the entirety of GB. But from what I've tested so far, it seems damn stable and this has made my transition to Android 11 pretty much seamless!
and @Ghisy, I'll send you some more details when I get a chance, certainly well before the weekend. Though if it's any consolation, in total the actual updating process only took me about an hour, if not less! Probably took me more time to actually download the files and prep, lol. XD
i5lee8bit said:
Just now updated my Pixel 4 XL from 08-2020 (Android 10) to 09-2020 (Android 11) using my keep root / seamless update method with no problems.
[...]
My current running list of Magisk / Xposed modules: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84193393
(I'm hoping @Ghisy finds this helpful, hehe)
[...]
Activating GravityBox module now, and will further report back!
Click to expand...
Click to collapse
Ha, thanks!
I'd be interested in your seamless update process if you don't mind sharing! Although I might go the image (sans -w) route instead.
Not sure I'll update until the week-end, I don't have much time on weekdays.
Ghisy said:
Ha, thanks!
I'd be interested in your seamless update process if you don't mind sharing! Although I might go the image (sans -w) route instead.
Not sure I'll update until the week-end, I don't have much time on weekdays.
Click to expand...
Click to collapse
see my edit above =)
But I also wanted to separately post a big finding of great news (at least for me)! - The volume key cursor control option now seems to persist through reboots, without needing to toggle the option again after reboots! Not sure, tbh, if this was fixed on [Q] already due to / as a side effect of the big Riru / EdXposed updates, but at least I can confirm that it definitely works on [R] now as intended. Woohoo!
Also @C3C076, donated an extra $10 USD via PP (20485146561217901). You're already very generous for enabling Family Library, and this should cover for installing the unlocker on my backup/secondary Android devices as well as my wife's phone. I also figured it would be better to donate via PP than disabling Family Library and purchasing again from Play Store, assuming higher fees from Google.
i5lee8bit said:
see my edit above =)
But I also wanted to separately post a big finding of great news (at least for me)! - The volume key cursor control option now seems to persist through reboots, without needing to toggle the option again after reboots! Not sure, tbh, if this was fixed on [Q] already due to / as a side effect of the big Riru / EdXposed updates, but at least I can confirm that it definitely works on [R] now as intended. Woohoo!
Also @C3C076, donated an extra $10 USD via PP (20485146561217901). You're already very generous for enabling Family Library, and this should cover for installing the unlocker on my backup/secondary Android devices as well as my wife's phone. I also figured it would be better to donate via PP than disabling Family Library and purchasing again from Play Store, assuming higher fees from Google.
Click to expand...
Click to collapse
Thanks. Your support is very much appreciated. Too kind. Interesting find about volume key cursor control. As you can see in the 2nd post I listed it there as currently not working . Looks like I'll have to take a look again. Do you use whitelist (App list mode enabled in EdXposed settings) ?
i5lee8bit said:
see my edit above =)
Click to expand...
Click to collapse
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
frank93 said:
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
Click to expand...
Click to collapse
If I can share my experience. I applied standard system update procedure from settings being on Pie (had it on your pixel to bring update for GB for Pie). This went without uninstalling magisk etc. I simple went incrementally from Pie through Q up to R and then several security update. Only after I was in the latest update I grabbed boot.img from corresponding system image, patched it using magisk and then flashed using fastboot. All apps and settings were preserved from Pie.
thanks. sounds about "right", your last step is basically what i’ve been doing as well previously (the "system update" never worked for me though, but i didn’t care too much). there must be something fishy going on with my device then. i’ll try again soon.
(in the end i wouldn’t even mind being without root for a few bootups inbetween, so .. i’ll flash the stock boot image and try booting android 11 then. if it works, i can try getting back root just as well afterwards i guess.)
frank93 said:
thanks. sounds about "right", your last step is basically what i’ve been doing as well previously (the "system update" never worked for me though, but i didn’t care too much). there must be something fishy going on with my device then. i’ll try again soon.
(in the end i wouldn’t even mind being without root for a few bootups inbetween, so .. i’ll flash the stock boot image and try booting android 11 then. if it works, i can try getting back root just as well afterwards i guess.)
Click to expand...
Click to collapse
Yeah, note that I never flashed full rom image. I went using standard system update from settings. In the end it was only patched boot.img I flashed.
okay, apparently not even a "real" firmware update (using the original stock boot image) works for me. loops back to bootloader 2-3 seconds after the google-logo. so i guess there’s something else wrong with my device/system.
i’ve "updated" back to the latest/last android 10 for now (there the firmware upgrade/downgrade works!?), and i’ll scratch my head another time i think. thanks for your input though!
i5lee8bit said:
and @Ghisy, I'll send you some more details when I get a chance, certainly well before the weekend. Though if it's any consolation, in total the actual updating process only took me about an hour, if not less! Probably took me more time to actually download the files and prep, lol. XD
Click to expand...
Click to collapse
Thanks, I appreciate it! You took one for the team and shared interesting info too! *(air) high five*
C3C076 said:
Thanks. Your support is very much appreciated. Too kind. Interesting find about volume key cursor control. As you can see in the 2nd post I listed it there as currently not working . Looks like I'll have to take a look again. Do you use whitelist (App list mode enabled in EdXposed settings) ?
Click to expand...
Click to collapse
I use App List mode, but not White List mode, as I use the Pass SafetyNet option (so basically on Blacklist mode). Because I also have GPay working and all (I've linked to that thread before, it's the one I linked with my list of active modules). Hahaha, I didn't even realize you put in the 2nd post about it not working - weird! Definitely working for me though, using these current configurations.
frank93 said:
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
Click to expand...
Click to collapse
Since I'm sure others may find it useful, I'll post it here. Also, @C3C076 may find it useful to follow this concept, assuming things are similar for Pixel 3a (I've been a long time HTC user, up til U12+ and only then switched to Pixel phones, 4 for wife and 4 XL for me to be exact).
My firmware update procedure is basically predicated on restoring the stock boot and dtbo (dtbo in case custom kernel flashed) images for your current build, which restores the stock firmware (and therefore recovery) and "unroots" / stock-ifies the phone without removing any of your Magisk or EdXposed configs, which allows you to simply boot into recovery and apply (sideload) OTA zip from stock recovery. Before booting back into system after OTA flash, reboot back into bootloader and flash the new build's Magisk-patched boot image, and when you boot up into system, voila, seamless, intuitive, and relatively safe update to new firmware version. Worst case scenario, if you bootloop you just flash the stock boot image (or even better, a modified Magisk Core Only boot image) and fix whatever is causing the problem.
Here is a link to my guide for September 2020 build, which was the first Android 11 build. There's a bunch of additional notes due to the major update at the time, though some of the info is a bit outdated. I assumed everyone at the time was on a very specific versions of firmware, Magisk, EdXposed, and even modules, etc. But if you read, especially the 2nd post, you can certainly understand how it all works and how we could apply the process from any firmware version. Here's the thread: https://forum.xda-developers.com/t/...0-009-coral-magisk-stock-boot-images.4160787/
- I recommend giving the procedure a read, as you should be able to understand the intuition behind the process I use.
As we're already (assuming) on latest Magisk, Magisk Manager, EdXposed, Riru, etc. etc, we don't need to worry as much about compatibility of our installed modules before OTA'ing. So basically, I condensed down what needs to be disabled, in my case, to the old GravityBox module (obviously), and the old Kirisakura (my kernel on Q) kernel helper Magisk module. You would also want to disable any modules, Magisk and EdXposed, that may not be compatible with [R] yet.
So here was my update procedure, from here on, coming from August 2020 build already on Magisk 21.2 and up to date EdXposed / Riru / etc. modules - SPECIFICALLY FOR PIXEL 4 XL "CORAL"
(OPEN THE "SPOILER" TO VIEW!):
Spoiler: Pixel 4 XL (and by extension and intuition, hopefully other Pixel series) keep-root / updating guide-procedures
NOTE: The files I provide are specifically only for Pixel 4 XL!! You will need to obtain the correct files for your own device to follow this procedure, but the same idea should be able to be applied!
First, I downloaded the boot and dtbo file(s) for Aug. 2020 thru Dec. 2020 builds. Here's a link to my AFH uploads for these files: P4XL Boot / DTBO files
Then, I patched each month's boot image with Magisk 21.2, and put them to the side.
There's only stock dtbo.img for 08-2020 because dtbo will remain stock throughout the updating procedure, fyi.
Actually, hell, for Pixel 4 XL "Coral" users, to make your life extremely easy, I've uploaded all the files you'll need to follow this here!! - LINK HERE
And OTA files from Google servers: LINK#2 HERE
Disabled GravityBox [Q] module in EdXposed Manager / Uninstall GravityBox [Q]
(Don't bother installing GravityBox [R] yet)
Disabled Kirisakura AK3 Kernel Helper module in Magisk Manager
(you'll also want to disable any modules that potentially may not work with [R])
-- Reboot once to finalize disabling the modules --
(Don't boot back into system until this section is done, to ensure all root, settings, mods, etc. are retained - this is basically the 2nd post of the September guide I linked earlier)
- Reboot into Bootloader mode -
fastboot flash boot 08-boot.img
fastboot flash dtbo 08-dtbo.img
(these steps revert recovery to stock)
- Reboot into Recovery mode-
(when No Command / Android icon shows up, hold power button and tap volume up to get to recovery menu)
Choose option: Apply update from ADB
adb sideload (09-2020 OTA zip).zip
after OTA zip flash completes, REBOOT BACK TO BOOTLOADER
fastboot flash boot 09-patched.img
- NOW REBOOT INTO SYSTEM! -
When your phone boots back into Android (11), you will be rooted, with all mods and settings retained. And if you passed SafetyNet before with the right combination of mods and settings, it should still pass now. While you can, I wouldn't yet bother installing GravityBox [R] quite yet. Let's first continue to incrementally upgrade until we're at 12-2020 (or 01-2021 depending on when you're reading this). Basically, just make sure the Android System Update notification (sorry, I don't remember exactly the notification label, but you'll know when you see it) indicates the update completed before proceding.
Now we just repeat my OTA update procedure again, except no need to flash stock dtbo images, as we're not doing anything (like flashing custom kernel) in this short amount of time that modifies the dtbo partition.
Reboot into bootloader mode
fastboot flash boot 09-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (10-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 10-patched.img
Boot to system
Allow time for the system update notification to indicate update was completed.
Reboot into bootloader mode
fastboot flash boot 10-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (11-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 11-patched.img
Boot to system
Allow time for the system update notification to indicate update was completed.
Reboot into bootloader mode
fastboot flash boot 11-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (12-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 12-patched.img
Boot to system
EDIT: Google released January 2021 firmware update, literally minutes after (or maybe while??) I was posting this! Here is my January 2021 easy update guide for Pixel 4 XL: https://forum.xda-developers.com/t/...5-003-coral-magisk-stock-boot-images.4213263/
Allow time for the system update notification to indicate update was completed.
Install GravityBox [R], activate module, reboot one more time, have fun!!
Also install custom kernel or whatever else you might need to do as well.
To be honest, I kinda rushed this post, so I'll re-read it later and make sure I didn't make any little mistakes. But hopefully if you read my guides threads and stuff (like, actually read it), the entire concept should be very clear and intuitive to you! Assuming other Pixel phones (at least AB Pixel devices) have similar partitioning schemes, this should be very useful knowledge to have, as it makes updating to new firmware versions incredibly easy and low risk. Good luck, I hope this huge post helps some people / makes a better day for someone! =)
EDIT: @frank93, seeing your linked post, I see you have a Pixel 4a. Unfortunately you obviously can't use the exact files I provided / linked, but you should still be able to follow the same procedure. Just grab the OTA's, plus the full factory images, pull the necessary boot and dtbo files from the factory images, and Magisk patch the boot images for each month, and name / organize all the files and put them aside on your computer. You should still be able to follow my procedure, but with your files. I hope it works for you with no problems if you decide to try it!
Has anyone tried one plus 8t?
...aaaand Pixel January 2021 update just dropped
Awesome! 2021 is looking good! Donation sent! Keep up the awesome work bro! Working flawlessly on my Pixel 3xl