Related
Hello,
THBK1-10 is a cheap dual system (Android 4.2.2 /Windows 8.1) tablet based on Bay Trail (Intel Atom Z3740D). More details http://www.thomsoncomputing.eu/dualboot.html
I'm trying to hack it, and especially get root and use non-signed zip in recovery. Basically i'm stuck at theses points, and i'm requesting directions to continue the work.
I have posted in W8 section, but obviously, this is no longer the place
General
------------
* i can use a work-around to write system (/system, /data) partitions
* i can flash signed updates via recovery
* google apps are working flawesly. Only thing is to keep original files (stock keyboard and layout)
-> i would like to flash non-signed zip via recovery, but i guess i have to build a custom recovery, or can i exploit something else ?
Root:
-------
* no auto root is working (z4root, towelRoot). Regarding towelRoot, i tryed each 8 common parameters, and i don't really know how to do others. I have also heard this is only working in 4.4.2+
* pushing su is not working. When i'm launching it, let's say from terminal, i have a code 255 return (-1). Tested with both arm and x86 version (i'm still wondering why arm su is also returning -1, i would have expect a non valid binary. Or perhaps my x86 version is bad ?
-> i'm still trying to dig this issue, and idea on how i could do ? i believe running SU was enough... but it seems not. Any idea ?
Many thanks !
Bump. the way it is booting is based on ramdisk images (one for normal android boot, one for android recovery).
I have acces to theses img, and i can, with hexedit (perhaps mounting them directly at a filesystem), view the whole init sequence.
My question is : what triggers the root invalidation ? AFAIK, everything is done as root (mounting FS, updating permissions, etc....). Basically i can't really figure how it is handled.
Thank you !
Solved !
Graveen said:
Solved !
Click to expand...
Click to collapse
Woaw ! I'm very happy to see that somebody tried and succeed to root the THBK1 ! Please can you share your method in a tutorial when you'll have time ? :laugh:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Yes ! I confirm ! Graveen has installed GAPPS on Thomoson THBK1 / Danew Dualboot tablet with sucess ! I'm not familiarised with linux environnement and realize it, but it requires some knowledges of linux command (coLinux especially)
Graveen is the only one users identified that it can put GAPPS on android environnement concerning this tablet.
Big thanks to him !
Graveen said:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Click to expand...
Click to collapse
7600
I own a Cube U100GT and it's one of the many Chinese brothers of your THBK1-10. But mine came only with W 8.1.
I just start looking for a dual boot solution and I'm happy to know that it's is possible.
I don't need root for while, just play some games and apps.
So the original Android "ROM" of the tablet can do the job.
My version have 64Gb SSD and I've already resize the Win partition to make room for a new system.
Where can I look for a dual boot tuto and find this Android version?
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: http://www.danew.com/support-pilotes-manuels.php?type=218&produit=219 but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Graveen said:
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Click to expand...
Click to collapse
The partition list is the standard for a windows installation (but no windows image on the end):
1: 300 Mb (Windows RE)
2: 100 Mb (System)
3: The rest (Windows). My SSD is 64Gb.
My tablet already comes with a dedicated keyboard cover, so I have full access to to UEFI Bios.
There's a lot of numbers:
Aptio Setup Utility Version 2.16.1242
Vendor - AMI
Core Version - 5.008
Project Version - 3BAGR 0.03
EC FW Version - 201401101A
Intel GOP driver - 7.0.1029
Sec RC Version - 00.05.00.00
TXE FW Version - 01.00.02.1060
I found the drivers pack for windows 8 and so I could install my PT-BR edition of W81. And reserve 20Gb at the end for another OS.
It's my first UEFI machine and I'm completely lost. There's a lot of options and I can't understand a quarter of that.
On the Tabletrepublic forum someone said that my bios recuse everything except a Windows pendrive. If is true, there's no way to put Android but changing/patching the UEFI.
Android x86 is for desktops right? And the Intel site, can I find Android images there?
Thank you. What i'll do is to check if my bios is identical to yours, because there are effectively numerous options. Then, i could finsh to dump my android partitions and let you play with them.
Honestly, the trick is the OS selection system, which is bring by the EFI bootloader (and certainly a dedicated partition). Once selection is done, another EFI bootloader (windows only) is called.
let's continue here: http://forum.xda-developers.com/showthread.php?t=2799404
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.
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
crDroid 6.2 ROM 15-01-2020
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
Boot into recovery
Wipe data, cache partitions to clean install. Wipe dalvik, cache to update previous crDroid.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.]
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.]
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
DOWNLOAD SF
DOWNLOAD AD
All ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK Many thanks to adi153!
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage-17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 24-12-2019 6.0 version
Last Updated 15-01-2020 6.2 (build3)
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
New build 15.01.2020, & many changes to the system. I'd like to get feedback on whether VOLTE is working? Thanks.
SYS update V1 out: 14-01-2020
Something wrong with the system updates, I moved it to the test directory.
Nice
Wow, a new rom... Thanks szanalmas, will give feedback after testing it
@szanalmas
Edit: Already tested your rom, so stable and smooth...
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Just that, still looking for other
Big thanks again for this nice rom
(Sorry for my bad english :v)
@szanalmas thanks ...for stable ROM.
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
From long time i was waiting for stable ROM. Thanks for your hard work.
@szanalmas thanks for make stable ROM :good:
while there are no bugs,
if there are bugs
I'll tell you later
thanks man i like crdroid
rom stable smooth did not find any bug after 2 hours use
Fadly357 said:
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Click to expand...
Click to collapse
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
szanalmas said:
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
Click to expand...
Click to collapse
Okay, will tell you as soon as possible if i found other
could you teach me rom build? i wanna learn and help
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
viethoang18 said:
could you teach me rom build? i wanna learn and help
Click to expand...
Click to collapse
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Fadly357 said:
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
Click to expand...
Click to collapse
I once used the magisk in TWRP but not this ROM. It worked for some.
But I didn't write in my post on my TWRP either now.
(I don't use magisk now.)
Use Canary: LINK
Or whatever.
szanalmas said:
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Click to expand...
Click to collapse
can i use Unbutu wls on windows ?
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Thank you very much feedbacks and thanks to everyone! :good:
Call volume on speaker is very high by default
@szanalmas Call volume on speaker is very high by default. Please set lower level by default. I hope in new build it willbe resolve.
Thanks...
ahmedhelmy71 said:
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Click to expand...
Click to collapse
This is what LINK is all about, and I still hold that the double-tap feature cannot be used for two things at once. What's interesting is that I can't find the ambient display double-tap menu option, and there's a separate one in Havoc ambient settings.
This is also an Official bug unfortunately.
*
cpglbitm said:
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
Click to expand...
Click to collapse
The SD card problem is very-very interesting.
What filesystem is in sd card?
Could you send us a logcat digest right after the phone is started?
Code:
adb logcat | grep vold > sdcardproblem.txt
viethoang18 said:
can i use Unbutu wls on windows ?
Click to expand...
Click to collapse
I don't know. I haven't used Windows for years, sorry.
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