Related
Introduction:
Hello
My work colleague got a ZTE Nubia Z5S Mini NX403A on AliExpress a few days ago. The phone came with a lot of preinstalled Chinese apps he didn't need and the Google Apps were not available so we decided to make a clean stock ROM of the device. It's my very very first ROM and althought I read a lot of documentation on this place I still have to read more to learn. The phone is not mine and I don't know if I will update it at all.
The official ROMs of the device can be found at http://www.nubia.cn/service.php?sid=5.
This ROM is based on the Android 4.4.2 - 1.25 stock version.
These are the changes so far:
Recovery eliminated so it won't be overwritten when installing the ROM
Removed Baidu apps
Removed Baidu Input and set AOSP as Default
Removed Chinese apps
Removed Nubia Wizard (if Gapps are installed, Google Wizard will show up)
Added Android AOSP sounds along the Nubia ones
Edited build.prop file so the phone's default language will be English
I am not sure if I will keep working on it since the phone is not mine, but I hope I can make the following changes:
Replace bootup.wav sound with a nicer one
Replace boot animation
Make own gapps that match with the Nubia layout (at least the PlayStore)
Add a occidental APN list and remove the APN chinese list
Edit the list of search providers inside the browser
Edit desktop layout. At the moment, when the phone is started for the first time, the apps are not sorted
Known issues:
Installed apps from the Google Play Store will get duplicated on the desktop
Go to Play Store settings and disable "add icons to desktop" optionIf you already have several duplicated ones. Just go to "Apps" in the Settings menu. Find Launcher3 and delete the app settings
ROM Link:
http://www.mediafire.com/download/a2uvlzzuelvk12q/MOD-NX403A_4.4_update_H125.zip Only for NX403A
Gapps:
I guess you can use any Gapps compatible with Android 4.4.2. Google Apps Minimal Edition will work well
Stock Recovery:
Stock Recovery 4.4 to 4.2 (Use this for 4.2 stock ROMs)
Stock Recovery 4.2 to 4.4 (Use this for 4.4 stock ROMs)
Root:
SuperSU 2.46
Instructions:
Once a recovery installed, flash the ZIP
Flash Gapps
Flash Root (optional)
Wipe Data, Cache, Dalvik (Shouldn't be needed in most cases)
Notes:
Since the ROM wasn't heavily modified it might be possible to flash it with the stock recovery. I used TWRP version 2.6.3.0
Rom for zte
I need full rom for zte z5s mini NX404H, help me
Please.
Note as a reminder:
Download the 3 files:
MOD-NX403A_4.4_update_H125.zip -> ROM
NX403A_4.4_to_4.2_recovery_V1.zip -> recovery 1
NX403A_4.2_to_4.4_recovery_V1.zip -> recovery 2
I tested them, with the device: zte nubia z5s mini nx406e
and they didn't work, not even the recovery.img by themselves.
even this one didn't work: Recovery 2.6.3.0
taken from> here
tested with version: Android Debug Bridge (adb) 1.0.32 ( should I try another version ? )
albertocastillo2001 said:
Introduction:
Hello
My work colleague got a ZTE Nubia Z5S Mini NX403A on AliExpress a few days ago. The phone came with a lot of preinstalled Chinese apps he didn't need and the Google Apps were not available so we decided to make a clean stock ROM of the device. It's my very very first ROM and althought I read a lot of documentation on this place I still have to read more to learn. The phone is not mine and I don't know if I will update it at all.
The official ROMs of the device can be found at http://www.nubia.cn/service.php?sid=5.
This ROM is based on the Android 4.4.2 - 1.25 stock version.
These are the changes so far:
Recovery eliminated so it won't be overwritten when installing the ROM
Removed Baidu apps
Removed Baidu Input and set AOSP as Default
Removed Chinese apps
Removed Nubia Wizard (if Gapps are installed, Google Wizard will show up)
Added Android AOSP sounds along the Nubia ones
Edited build.prop file so the phone's default language will be English
I am not sure if I will keep working on it since the phone is not mine, but I hope I can make the following changes:
Replace bootup.wav sound with a nicer one
Replace boot animation
Make own gapps that match with the Nubia layout (at least the PlayStore)
Add a occidental APN list and remove the APN chinese list
Edit the list of search providers inside the browser
Edit desktop layout. At the moment, when the phone is started for the first time, the apps are not sorted
Known issues:
Installed apps from the Google Play Store will get duplicated on the desktop
Go to Play Store settings and disable "add icons to desktop" optionIf you already have several duplicated ones. Just go to "Apps" in the Settings menu. Find Launcher3 and delete the app settings
ROM Link:
http://www.mediafire.com/download/a2uvlzzuelvk12q/MOD-NX403A_4.4_update_H125.zip Only for NX403A
Gapps:
I guess you can use any Gapps compatible with Android 4.4.2. Google Apps Minimal Edition will work well
Stock Recovery:
Stock Recovery 4.4 to 4.2 (Use this for 4.2 stock ROMs)
Stock Recovery 4.2 to 4.4 (Use this for 4.4 stock ROMs)
Root:
SuperSU 2.46
Instructions:
Once a recovery installed, flash the ZIP
Flash Gapps
Flash Root (optional)
Wipe Data, Cache, Dalvik (Shouldn't be needed in most cases)
Notes:
Since the ROM wasn't heavily modified it might be possible to flash it with the stock recovery. I used TWRP version 2.6.3.0
Click to expand...
Click to collapse
What Android Debug Bridge (adb) version did you work with ?
I tested it with Android Debug Bridge (adb) version 1.0.32
SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge (G925xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
- Stock recovery (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G925F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (manual control, added "Record" button)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Reserved
There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<
Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
>> SYSTEMLESS_DevBase_v1.3.zip <<
Huawei P9 Custom Rom - for EVA-L09 - EVA-L19 - EVA-L29
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*MagicRainbow*
Version 4
as usual in two Editions:
Magisk Edition and SuperSU Edition
German Thread: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p9.2808/huawei-p9-rom-android-7-0-emui-5-0-1-magicrainbow-v4-by-tecalote.859343.html
I'm happy to present you my fourth version of MagicRainbow ROM for P9-EVA
Requirements:
P9 EVA-L09 - EVA-L19 - EVA-L29 - without mobile provider branding (like Vodafone)
unlocked Bootloader
minimum official Huawei background firmware b394
TWRP 3.1.1-1 by oldDroid - extended Version: https://www.androidfilehost.com/?fid=673791459329067086
Note: In Settings of TWRP on the last Tab disable "keep vendor mounted" but enable "Exclude OEM-Path from data wipe"
Phone must be encrypted because this ROM is based on EMUI (TWRP has encryption support) - if your data partition is decrypted, ROM cannot be installed properly because the script mount your data as encrypted. If you come from EMUI based ROM or official Firmware data is encrypted by default
Developer Options enabled, in these settings enabled OEM-Unlock and: A) ADB Debugging in charging mode - B) USB Debugging (in this order, or it will not stay enabled)
Changelog:
European Firmware b398 based for EVA-L09 - with patch.zips for L19-c432 – L19-c185 – L19-c636 – L29-c636 – L09-c636 – L09-c185 Note: EVA-L09 need no patch, but the other models/cust need this patch immediately after flashing the Rom without Reboot to system - but with reboot of TWRP (for fixing the mountpoints after ROM installing)
Magisk-Edition: Magisk v16 - preinstalled modules (required):SELinux Permissive-Script 1.2 - Busybox 1.28.1 by osmOsis - Huawei Property Fix 1.3 - KernelAudiutorReborn allows to emulate init.d
Safetynet-Workaround look in the description for Magisk
SuperSU-Edition: SuperSU 2.82 SR5 - init.d Support - modified launch_daemonsu.sh for SELinux Permissive - BusyBox 1.28.1 by osmOsis
"Advanced Settings" - made personally by KangV well known as "K-Settings" - ported in MRv4 from chinese Firmware b399 - optional flashable zip separate for SuperSU-Editon and for Magisk-Edition - please support this project in credits section. These settings allow you the maximum of customization. In SuperSU-Edition you can enable in Advanced-Settings /more settings/Xposed Framework last v89 by rovo89 (and of course, a lot of more...)
Note: If you enable Xposed Framework - after reboot (which takes bit longer than usual) you must reboot your phone once again (only one times) and Xposed will be and stay enabled (you can disable Xposed with same settings)
In Magisk-Edition this setting is not active (cause it breaks safetynet)
To disable chinese letters after flashing this mod in statusbar - open Advanced Settings /Notification settings and disable "Show statusbar Lunar"
Known BUG: Dont use "Hide navigation bar" - it works only on chinese Brands.
In Europe you should not use: "Disable Google Services"
Note: Do not change DPI in developer options (this can brick your device) if you use KangV Settings - change DPI only with KangV Advanced Settings!
Note: Do not flash KangV-Settings before first reboot to System. You can do it after first setup, but dont change the EMUI Launcher to alternative Launcher (example: Nova Launcher) before you have flashed KangV-Settings (if you decide to use KangV Mod)
With KangV Advanced Settings PMPlusApp will be installed (this App dont work on Stock Roms) With PMPlus you can enable in Phonemanager (on second page) the feature: Auto-Launch It is a powerful Autostart-Manager (which can help you also to save battery) that gives you full auto launch control over all Apps - but you must manually allow them to start automatically or not, on boot or in the background.
Note: If you enable this mod - you must enable important Apps into auto launch, example: Magisk Manager /SuperSU must be enabled in "Auto Launch" - and additional in Secondary launch management!, if not you cannot manage Root-Requests! WhatsApp, Viber, Telegram - all these apps you must enable in "Auto Launch" or they do not work properly. Some Apps like Amazon needs also an extra setting in "Auto Launch, called "App secondary launch" (this will only be displayed if you use apps that need it)
To enable this mod open PMPlus, use install button, soon it is succesful installed - close PMPlus and uninstall this App. After open Phone Manager and on second page you will find "Auto Launch"
Note: This mod is not uninstall able, once enabled!
Both Edition of MRv4-ROM have modified services.jar - the maximum of acces to external SD is enabled (TitaniumBackup dont neeed "DocumentProvider" but can use Filesystem storage - Ext. SD Card)
App-Twin: more apps than usual are enabled for cloning (WhatsApp, Telegram, Skype and a lot of more...)
Only the main Google (Core) Apps are installed in system, all others are installed so that they can be uninstalled via Settings /Apps. Same with added Apps - all of them uninstall able via Settings /Apps. If you need more Google Apps you can install them with Playstore (dont flash any GApps)
Added: Facebook Lite and Skype Lite (both can work in 2G/3G and 4G and saves a lot of battery
VIPER4AndroidFX and Dolby/Atmos with preinstalled Driver
Some beautiful Designs included: IOS11 - Sky Blue - Galaxya - XDA Exklusive - AegeanSea - Blue Pixel - Mate 10 (Mountains)
Security-Patch-Level: 01.02.2018
Installation-Guide:
1) Your official Huawei Background-Firmware must be updated to minimal b394 (which is available for all models/cust) - for updating use please my Post from MRv3 #3: https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
Note: Your Fingerprint HWEVA/xxx/xxx:user/release-keys (which you can see with apps like "My Device") on MagicRainbow v3 will show you ...b394 - but that does not mean your background official Firmware is b394 ! You see this information, because MagicRainbow v3 is based on b394 same as MagicRainbow v4 is based on b398.
But important is - which build was your last official Firmware. For example: If you had flashed MRv3 over MRv2 (which was based on b386) your background Firmware is b386 ! And this Firmware is too old and cannot be compatible with the Custom ROM MagicRainbow v4 which is based on b398. Custom ROM and Background Firmware should be similar the same build. Personally, I always update first to the last available firmware for my device before flashing my own Custom Rom
But if you have updated your Firmware to b394 - before you have installed MagicRainbow v3 - or if you come right now from Stock Firmware b394, b395, b397... then there is no need to update the firmware now and you can flash the MagicRainbow v4 directly - but with Unroot (if your Phone is rooted) AND with the neccesary wipes!
2) Before update your Firmware (or for clean flash) you must backup your apps and data (you can use Huawei Backup and/or TitaniumBackup - in every case make backup only from user-apps and not from system apps/components)
Backup also the important folders from your internal storage (WhatsApp folder, DCIM and so on...) - and copy them back to internal storage after updating the Firmware...
For Chat/Net-Call Apps like Viber, WhatsApp use inside Chat-Backup on GoogleDrive. If you reinstall these apps and registrate them new with your phone number, backup will be found automatically and you are able to restore chat-history.
3) For the next steps I now assume that your firmware is up to date Download now all Files you need - ROM.zip - patch.zip (if you need it for different cust/model than EVA-L09c432) - KangV-Settings.zip and copy it to your external SD.
4) Delete on your Phone your Fingerprint(s) and PIN(s)
5) If your device has Root - flash Unroot with TWRP - for Magisk: http://tiny.cc/latestuninstaller - for SuperSU flash UPDATE-unSU-signed.zip from this site: https://forum.xda-developers.com/showpost.php?p=63615067
6) Go back to main menu in TWRP and use WIPE /Advanced Wipe - for clean flash wipe: Dalvik/ART-Cache, Cache, data, system, vendor - for dirty flash exclude: data from wipe
7) Flash ROM - next step (8) is only important if you have another model/cust than EVA-L09c432
8) If you have another (like L19c432, L29c636.....) - you must REBOOT TWRP now (TWRP /Reboot /RECOVERY) - dont reboot to system! After TWRP is rebooted, go to install and flash the RIGHT patch.zip which match your model/cust. (EVA-L09c432 dont need this step.) In every case: no need to wipe Dalvik/Cache after the flashings
9) Reboot phone (first start needs about 10 minutes) - dont flash KangV Settings before first Reboot to system
10) Setup your Phone - disable "send systemdata to Google" (save battery)
11) Disable “automatic system updates” in developer options (save battery)
Safetynet-Workaround in Magisk-Edition:
1) If you made clean flash - during first setup at the point you enable your Google Account - disable "sending system-data"
2) After first setup safetynet check with Magisk Manager will show you - ctsProfile and basicIntegrity=false - so dont check now :laugh:
3) Enable Developer Options and in these settings enable A) ADB Debugging in charging mode - B) USB Debugging (in this order, or it will not stay enabled)
4) Reboot your Phone - after reboot, cts-profile and basicIntegrity=true
- Now we go to make Playstore certified:
5) Open Playstore and disable Play Protect
6) SET YOUR PHONE INTO FLIGHT-MODE!
7) Open native settings /apps and (right down) more: Show system processes - click on every following app and delete in storage-section: cache and data (some of them show you: manage space - in this case use "Delete all data"):
Google App
Google Play services for Instant Apps
Google Playstore
Google Play-Services
Google Services Framework
Huawei ID or Huawei Mobile Services (which is the same)
8) Reboot your Phone
9) If you get a message after Restart "Your backup-account is not set yet" - DONT enable it now!
10) DISABLE FLIGHT-MODE NOW - and wait until you have full network-access (open Browser for testing)
11) Now you can enable your backup-account (message is shown in statusbar)
12) Open Playstore - If you are facing a problem when you open Playstore (showing just a blank site) - open Settings /Apps /Playstore /storage - but this time wipe only Cache inside, after Reboot your Phone. Soon P9 is restartet, Playstore should work proberly and it should be certified
13) If you are using Apps (like banking apps and so on) which requires safetynet - enable them in Magisk Hide - BEFORE you start these apps first time - after reboot phone and then you can start these apps first time.
Note: If you did all these steps and ctsProfile /or basicIntegrity is false (red) - one User of this Rom (L19c432) found a trick which solved his issue: https://forum.xda-developers.com/showpost.php?p=75796309&postcount=595
14) If you use in Phonemanager "Auto-Lauch" (enabled with PMPlus - see description KangV Advanced settings) - you must enable Magisk-Manager in Auto-Launch and in Secondary launch management!
15) You can update to newest Magisk 16.1 using following method: https://forum.xda-developers.com/showpost.php?p=75845280&postcount=87
Download ROM:
ROM - MagicRainbow-4_magisk.zip: https://www.androidfilehost.com/?fid=746010030569959046
MD5: c0856ddabf79312376ec5f90e52087ab
KangV-Settings_magisk.zip: https://www.androidfilehost.com/?fid=746010030569959103
MD5: 47ec7117a403af004e43c42cecde2b36
ROM - MagicRainbow-4_supersu.zip: https://www.androidfilehost.com/?fid=746010030569959091
MD5: 0ba05c096f4caa09afbe373d2986801d
KangV-Settings_supersu.zip: https://www.androidfilehost.com/?fid=673956719939824958
MD5: 4e197148bd00f4bb14ae7253d3f00a91
Download Patches (EVA-L09c432 dont need this!)
MD5-checksum is also shown on Android Filehost during download, please check your downloaded files if they match with this checksum.
Note: A very required point is - If you have another model/cust than EVA-L09-C432 and you must flash Patch.zip do it with following steps:
1) After flashing Rom - go back to main menu of TWRP, go to Restart /but NOT system - Restart RECOVERY
2) Then flash patch.zip and after reboot Phone first time. If you don't restart Recovery between, patch will not installed properly and some apps may not work then.
Information: I have decided to make new patch.zips because there are problems with safetynet (in the Magisk Edition). Once these are done, I will post the new links here.
L19-c432-patch.zip: https://www.androidfilehost.com/?fid=890129502657588204
L19-c185-patch.zip: https://www.androidfilehost.com/?fid=746010030569959118
L19-c636-patch.zip: https://www.androidfilehost.com/?fid=890129502657588206
L29-c636-patch.zip: https://www.androidfilehost.com/?fid=673956719939824987
L09-c636-patch.zip: https://www.androidfilehost.com/?fid=890129502657588201
L09-c185-patch.zip: https://www.androidfilehost.com/?fid=818070582850497993
HAVE MUCH FUN WITH THIS ROM
Many thanks to KangV for Advanced-Settings
If you like Advanced Settings made by KangV - you can support him: https://www.paypal.me/KangVIP
If you like *Magic-Rainbow* ROM and want to support the project, feel free to donate https://www.paypal.me/Tecalote
Many thanks and credits:
@OldDroid - TWRP with DECRYPTION SUPPORT for P9
@guitardedhero(Viper/Atmos)
@HootanParsa (MiXplorer)
@Chainfire - SuperSU
@topjohnwu (systemless Xposed Framework and Magisk)
@dkionline - Custom Roms for P9
@Blackball - Custom Roms for P8 - P9 - P 10 - P10Plus - Mate 9
@osm0sis – BusyBox for Android NDK
@ SuperR. – Best Kitchen I have ever seen
XDA:DevDB Information
MagicRainbow, ROM for the Huawei P9
Contributors
Tecalote
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: official Firmware b394 up to b398
Based On: EMUI (encrypted)
Version Information
Status: Stable
Current Stable Version: MagicRainbow v4.0
Stable Release Date: 2018-03-05
Created 2018-03-06
Last Updated 2018-03-14
Pictures and additions - tomorrow
Credits:
All Credits go to @Atarii for his special EMUI-Recovery for P9 EVA (L09 / L19 /L29). Users had reported, it is working also on P9+ VIE (L09 / L29) - but it will not work on other devices. Following method is based on this modified EMUI-Recovery.
Thanks to @zgfg He inspired me to do this post.
This Guide show you how to go back from Custom ROM to original Huawei EMUI Firmware. You can use this method also for updating/downgrade your Firmware - but only on Android 7. Also users of Lineage OS or RROS can use this method to return to Stock Firmware.
It can not be used for downgrade to Android 6 /or upgrade to Android 7 (this can brick your device) and it will not debrand your device!
Requirements: Unlocked Bootloader, installed TWRP, inserted SD Card (ExFat filesystem format recommended) -
Enable Developer Options and inside enable first ADB Debugging in charging mode and then USB Debugging - OEM Unlock must also be enabled!
Do a backup as usual if you change your system to another (Backup your Apps /data and also data from internal storage!)
Follow the steps on the instructions!
Not required: Root
Required: I would recommend to UNROOT your device before flashing the Firmware-Update and you should delete your Fingerprint /PIN /Password
How it works:
1) First you need one of those zip files (depended to your device):
Download HWOTA.zip for P9 and P9+ EVA/VIE-L09: [url]https://www.androidfilehost.com/?fid=962187416754474573[/URL]
md5: 98e141ca6d6ccc262d22288490a5eeea
Download HWOTA.zip for P9 EVA-L19: [url]https://www.androidfilehost.com/?fid=962187416754474574[/URL]
md5: e90b5b4d14d9808bb0626dbd77bb452f
Download HWOTA.zip for P9 and P9+ EVA/VIE-L29: [url]https://www.androidfilehost.com/?fid=673956719939834215[/URL]
md5: 5fad3c1971c45ad7b9a72ab2e8cc9404
2) Unzipp the HWOTA.zip on your PC - HWOTA folder contains 2 Files:
L(xx)_Recovery.img
(dependend to your device for example: L09_Recovery.img)
HWOTAUpdateSCRIPT.zip
3) Do not use internal Storage of your Phone! Create a folder in the main directory of your EXTERNAL SD with the name: HWOTA
4) Copy L(xx)_Recovery.img and HWOTAUpdateSCRIPT.zip into the HWOTA folder on your external SD.
5) Search for the correct FullOTA-MF Firmware for your Device /Cust and download the 3 firmware zip files. See Guide below...
6) Copy the 3 Firmware zip files into the HWOTA folder on your external SD:
update.zip
update_data_full_public.zip(The third zip file has different names dependend to your device: update_full_EVA-L09_hw_eu.zip / update_full_EVA-L19_hw_eu.zip / update_full_EVA-L19_hw_meafnaf.zip / update_full_EVA-L29_hw_spcseas.zip...) - Rename only this third zip file to the general name:
update_full_hw.zip
6) Your HWOTA folder on the external SD is now prepared!
7) Disconnect USB cable from your P9
8) Boot to TWRP and from HWOTA folder flash only: HWOTAUpdateSCRIPT.zip
9) The phone reboots to EMUI recovery and automatically installs the firmware. After 57% it takes a while, do not worry. As soon as the update has been performed 100%, the system will be restarted
10) Open settings /advanced settings/ Backup and restore and do a data Factoryreset with wipe of internal Storage
11) Once the factory reset is 100% in EMUI recovery, the phone restarts. At this moment, press the VOL + key until the EMUI Recovery boots again
12) Do Wipe Cache Partition and Reboot to System
13) Look into settings /about phone and enjoy - and if you want to stay on original firmware, now everything is done.
14) On some Firmwares the Bootloader will get closed - in case you want to open Bootloader again, enable Developer options and open them. First enable "Allow ADB Debugging in charge only mode" and then "USB Debugging" (in this order USB Debugging stays enabled) and very important: Enable "OEM Unlock". Enter your Unlock Code with ADB in Fastboot Mode. Let the phone doing the low-lewel-wipe and do not disconnect the Phone from USB, the wipe should be done with 100% (important)- if not: open settings /Advanced settings /Backup & reset /Factory data reset with enabled "erase internal storage"
15) To flash TWRP, enable Developer Options again / OEM Unlock is enabled (but greyed out) /enable ADB Debugging and USB Debugging and then flash TWRP in Fastboot Mode.
16) Enjoy
How to find the Firmware:
A) You can not use FullOTA-MF-PV or OTA-MF - you can use only FullOTA-MF firmware for this method.
The firmware for your device consists only of three zip files. But the differnt possibilities for downloading the firmware can show you four / sometimes five zip files if the Build is made for two or three models. For example for L09 /L19 and L29 or for L09 and L19.
You need in every case update.zip and update_data_full_public.zip and third zip must match your device - and you have to rename it:
Examples:
If you own L09-c432 you choose update_full_EVA-L09_hw_eu.zip - and rename this update_full_hw.zip
If you own L19-c432 you choose update_full_EVA-L19_hw_eu.zip - and rename this: update_full_hw.zip
If you own L19-c185 you choose update_full_EVA-L19_hw_meafnaf.zip - and rename this: update_full_hw.zip
If you own L19-c636 you choose update_full_EVA-L29_hw_spcseas.zip- and rename this: update_full_hw.zip
B) For searching your firmware you enter always model name and cust version from your device - for example:
EVA-L09C432 or EVA-L19C432 or EVA-L19C185 or EVA-L29C636 ....
Note: You can not install L19c636 Firmware if you own a L09c432 device ....
C) Which Firmware should I use?
For the users of MagicRainbow v4 I recommend to use the firmware that was installed before MRv4. Same for the users of MagicRainbow v3.
From there you can update if necessary.
Note: There can not be any impossible "version jumps". For example, it is not possible to update from b386 directly to b398. Firmwares depend on prerequisite versions. For example with EVA-L09c432 you can switch from b386 to b394 and then: b397 -> b398 -> b399. It is recommended to use approved versions, otherwise Playstore is not certified. For example, EVA-L09c432 currently has the rollout b399 - that means, the firmware is approved.
If you do not succeed in updating with this method, then you have done something wrong, or the download of the zip files is buggy, or the version did not fit. Nothing bad can happen if an update fails, but TWRP must be reinstalled. Then you can try it with a different version that fits your firmware. But you can not use firmware that does not match your model /cust - this can brick your device!
D) There are three ways to download the firmware and it is up to you, which you use of it
1. Firmware Finder - Android App on Playstore:[url]https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder&hl=us[/URL]
2. Direct Link: [url]http://pro-teammt.ru/firmware-database/?firmware_model=EVA-L09C432&firmware_page=0[/URL]
3. Firmware Finder for PC: [url]https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146[/URL]
Instructions for v4 have that new section Playstore Certified but Magisk Hide section (from v3 Instructions) are omitted - Magisk Hide is no more needed?
Maybe you can also copy/paste the Statusbar Lunar note for K-Settings (if Chinese letters still persist).
In case of installing from L09 c432 b394 -> MR v3, upon going back to stock b394 (by HWOTA), is it necessary to update in two steps b397 -> b398 or it can be flashed only one HWOTA for L09 c432 b398.
zgfg said:
Instructions for v4 have that new section Playstore Certified but Magisk Hide section (from v3 Instructions) are omitted - Magisk Hide is no more needed?
Maybe you can also copy/paste the Statusbar Lunar note for K-Settings (if Chinese letters still persist).
In case of installing from L09 c432 b394 -> MR v3, upon going back to stock b394 (by HWOTA), is it necessary to update in two steps b397 -> b398 or it can be flashed only one HWOTA for L09 c432 b398.
Click to expand...
Click to collapse
Magisk Hide for some required components is preset!
You just enable Apps which requires safetynet (Banking Apps and so on) in Magisk Hide and reboot phone before you start these Apps first time.
Direct update from b394 to b398 didn't work for me and I got problems to update after trying the short way.
L09 c432 b394 -> MR v3 - going back to stock b394 (by HWOTA), then b397 then -> b398!
Statusbar Lunar note for K-Settings is included in description of KangV Settings
Hi,
What is difference between v3 and v4?
mnv12345 said:
Hi,
What is difference between v3 and v4?
Click to expand...
Click to collapse
I didn't install yet but you can check post #1 ChangeLog.
E.g. based on b398 (for c432) with Feb Sec patch, latest Magisk components and so
zgfg said:
I didn't install yet but you can check post #1 ChangeLog.
E.g. based on b394 (for c432) with Feb Sec patch, latest Magisk components and so
Click to expand...
Click to collapse
Where did you read based on b394? - I have written there and it is based in b398.
February Sec Patch is also written there..
Tecalote said:
Where did you read based on b394? - I have written there and it is based in b398.
February Sec Patch is also written there..
Click to expand...
Click to collapse
Of course b398, lapsus
mnv12345 said:
Hi,
What is difference between v3 and v4?
Click to expand...
Click to collapse
It contains the Features of b395 - 3D Camera Plugin
and newest Security Patch Level from b398 (February) - it has some optimations for Battery Life - Magisk Edition has newest Magisk v16 - SuperSU Edition has newest Xposed Framework (to enable from KangV Advanced Settings, sone more Apps added (but uninstall able from settings /apps)
Read Post #1 please
I'll hope you upload all files to change to v4.
My stock Rom is c185B387
Tecalote said:
Huawei P9 Custom RomSafetynet-Workaround in Magisk-Edition:
1) If you made clean flash - during first setup at the point you enable your Google Account - disable "sending system-data"
2) After first setup safetynet check with Magisk Manager will show you - ctsProfile and basicIntegrity=false - so dont check now :laugh:
3) Enable Developer Options and in these settings enable A) ADB Debugging in charging mode - B) USB Debugging (in this order, or it will not stay enabled)
4) Reboot your Phone - after reboot, cts-profile and basicIntegrity=true
- Now we go to make Playstore certified:
5) SET YOUR PHONE INTO FLIGHT-MODE!
6) Open native settings /apps and (right down) more: Show system processes - click on every following app and delete in storage-section: cache and data (some of them show you: manage space - in this case also DELETE ALL DATA):
Google App
Google Play services for Instant Apps
Google Playstore
Google Play-Services
Google Services Framework
Huawei ID or Huawei Mobile Services (which is the same)
7) Reboot your Phone
- if you get a message "Your backup-account is not set yet" - DONT enable it now!
8) DISABLE FLIGHT-MODE NOW - and wait until you have full network-access (open Browser for testing)
9) Now you can enable your backup-account (message is shown in statusbar)
10) Open Playstore - it is certified
11) If you are using Apps (like banking apps and so on) which requires safetynet - enable them in Magisk Hide - BEFORE you start these apps first time - after reboot phone and then you can start these apps first time.
Click to expand...
Click to collapse
I made it and Play Store stoped working. It searching updates for years and nothing else happen.
And second case. After clean flash via TWRP I lost TWRP and had to reflash it again. Is it normal?
hapnik said:
I made it and Play Store stoped working. It searching updates for years and nothing else happen.
And second case. After clean flash via TWRP I lost TWRP and had to reflash it again. Is it normal?
Click to expand...
Click to collapse
Playstore must just create new cache. Just open settings /apps and wipe in storage only cache at this point.
Reboot phone and it should work again.
Normally you loose not TWRP with clean flash. I never heard this.
But if you wipe internal storage included in the wipes you loose normally settings of TWRP.
That's why I do a wipe if internal storage with an extra step and reboot Recovery between the next wipes.
jonathanhenry81 said:
I'll hope you upload all files to change to v4.
My stock Rom is c185B387
Click to expand...
Click to collapse
I can upload HWOTA.zips for newest Firmware c185b387 tonight (but late)
Tecalote said:
I can upload HWOTA.zips for newest Firmware c185b387 tonight (but late)
Click to expand...
Click to collapse
Just take time you need
jonathanhenry81 said:
Just take time you need
Click to expand...
Click to collapse
I answered here: https://forum.xda-developers.com/showpost.php?p=75780638&postcount=557
You said your model is L19c185 and last official Firmware was b387.
In this case you must first update to b394 - after to b396 (you can't go directly to b396, it would fail)
The downloads and the Guide how to do you will find here:
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
Be careful to download the right two zips.
I wish you success
Note: b396 is latest official Firmware for your device.
After it is installed (with factory reset and wipe of internal storage from settings) you can flash MRv4 (read Guide before)
Tecalote said:
I answered here: https://forum.xda-developers.com/showpost.php?p=75780638&postcount=557
You said your model is L19c185 and last official Firmware was b387.
In this case you must first update to b394 - after to b396 (you can't go directly to b396, it would fail)
The downloads and the Guide how to do you will find here:
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
Be careful to download the right two zips.
I wish you success
Note: b396 is latest official Firmware for your device.
After it is installed (with factory reset and wipe of internal storage from settings) you can flash MRv4 (read Guide before)
Click to expand...
Click to collapse
I read the guide https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
and I'm not clear, I have MR V3 at this time. but before that update to stock B387 .. now to change MR v4 first I have to update and should I start with B387 or B394 ???
as the post says; first B387.
jonathanhenry81 said:
I read the guide https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
and I'm not clear, I have MR V3 at this time. but before that update to stock B387 .. now to change MR v4 first I have to update and should I start with B387 or B394 ???
as the post says; first B387.
Click to expand...
Click to collapse
I think b394 should be okay.
On L09 it is also working to update from b386 to b394
Hi a small question, once I have returned from MRv3 to stock. I am assuming that TWRP will need to be re-flashed! Is this correct?
DH
bubba_66 said:
Hi a small question, once I have returned from MRv3 to stock. I am assuming that TWRP will need to be re-flashed! Is this correct?
DH
Click to expand...
Click to collapse
Yes, that's correct - because the Update flash Stock Recovery (without no update possible)
After Update reflash of TWRP is necessary.
But sometimes Bootloader get closed and in this case unlock Bootloader is required..
Hello everyone,
I'm one of the few unfortunate to end up and stick with a Chinese variant of Galaxy S6 model SM-G9200. This particular model (SM-G9200) comes in 2 variants(CSC): The Hong Kong (TGY) version (last ROM G9200ZHU2ERK2 Nov.2018 v7.0) packed with Google Apps and all the goody goods, and the China (CHC) version (last ROM G9200ZCU2ERK2 Nov.2018 v7.0) with fewer features and which I happen to own.
Both are virtually the same phone with just different firmware. As some of you may know, the Chinese ROMs don't include Google Apps package due to local restrictions and naturally I've downloaded the Hong Kong variant but this is where I got stuck. The HK ROM won't flash through Odin and it fails at flashing sboot.bin while the phone saying "SECURE CHECK FAIL (BOOTLOADER)". This generally indicates that I attempt to flash the wrong ROM but SamMobile says the SM-G9200 has 2 CSC ROMs in which only the CN version seems to work in Odin. I've already unlocked the bootloader with CROM apk (link provided) but with no use still. I've also tried a .pit file for the HK variant but I get "SECURE CHECK FAIL (PIT)". Also, some have suggested a 4-file method of flashing but that's no where to be found.
Now I know that I could just stick with the CN ROM and root with CF-Auto-Root (link here), then flash the GApps but it goes much deeper than that. What I usually do with Samsung phones in the past was to just flash TWRP in Odin (link here) then flash/debloat/modify files only through TWRP because it won't modify the system files and break dm-verity, SafetyNet, SELinux and other Knox security as these are crucial for another app that I'm used to, the Barclays Mobile Banking app. This app won't work without Google Play Services and won't work if the phone is/was rooted in any way, even after a unroot and full restore. TWRP won't do the trick because as soon as I mount the /system partition, it goes through a boot loop (the bootloader detects that dm-verity tree hash check fails and resets itself). One trick that I use to bypass this is to repack the boot.img patched earlier by CF-Auto-Root generated bootloader (link provided) and flash it. However this method doesn't work either as the ROM is in Custom mode again and SafetyNet is missing. Maybe the rom lacks this feature altogether.
I've literally searched the entire internet for resources (Google, Baidu, xda, chinese forums) to get as much insight and files I can gather but my search went as far as it goes.
In conclusion, I've opened this thread to ask for help from the broader community and maybe research additional mods & root methods like Magisk and how to flash the HK or any ROM. My theory is that the block is related to Odin Mode's "Secure Download: Enabled". Please don't reply with things like "please root my phone", "pm please help"..... as I've already provided with all the possible files and what we need is a constructive discussion on how to bust open this phone.
Courtesy to those who made those tools. Their name is in he filename or link source. All files are relevant to the GM-G9200 CN model.
Conclusion
Alright guys, after a lot of research and hard work I came with the best solution. It turns out that there is no way to flash the TGY firmware, however this is not a problem. The solution that I found would be to manually install Open Gapps from TWRP recovery. So here are the instructions to get a clean rom with Google Play and no root traces for banking apps:
- Flash your original ROM with Odin.
- As soon as that finishes, go to recovery and choose "wipe /data" to clear any modified files left out.
- Flash TWRP provided from this post.
- In TWRP you do all the work, firstly you need to make space for Gapps so delete unnecessary apps. You will find a list of apps you can and can't delete in "Knox Out.txt".
- Now flash OpenGapps zip and you may also customise it to install only required apps.
- Now that you modified /system you have to disable dm-verity. Flash the "no-verity-withSE.zip".
- All done! Now you got a phone with Google Play Certified status and passing all SafetyNet & Root checks.
After using the S6 Duos for a while and testing literally every feature I have to say that it is worth using it. However, it does have a few issues which I've yet to fix. so you may want to consider them.
- Not all languages are available. Certain UI elements & apps might not be translated when using an unsupported language.
- I cannot hide the data type indicator (4G/3G) even after disabling Mobile Data, and Dual SIM mode really clogs up the status bar (5 items).
- VoLTE does not work on some networks (UPDATE! Needs to change customer.xml to add the IMS settings and other carrier related features) and Wifi Calling does not work at all because ePDG subsystem is missing on this phone.
- Floating Messages UI crashes when WeChat app is installed. However the feature works flawlessly, only the UI control in Advanced Settings doesn't.
- Maps for SHealth and other apps use the Chinese Amap instead of Google Maps. (UPDATE! Needs to change customer.xml and change Country and Region for your specific language).
- Phone number locator a.k.a Caller ID is only in Chinese.
Hi, Alex.
I have been having issues trying to use gapps on my samsung s6 dous China. I have been unable to use my google acccount on the phone after all the processes. I flashed android 7, twrp and installed gapps, then no verify. The processes went fine, but cant still activate my google account. Can u please point me to anything I am missing and also the version of the android OS and posibly download link you used on your phone. Thanks.
alexceltare2 said:
Alright guys, after a lot of research and hard work I came with the best solution. It turns out that there is no way to flash the TGY firmware, however this is not a problem. The solution that I found would be to manually install Open Gapps from TWRP recovery. So here are the instructions to get a clean rom with Google Play and no root traces for banking apps:
- Flash your original ROM with Odin.
- As soon as that finishes, go to recovery and choose "wipe /data" to clear any modified files left out.
- Flash TWRP provided from this post.
- In TWRP you do all the work, firstly you need to make space for Gapps so delete unnecessary apps. You will find a list of apps you can and can't delete in "Knox Out.txt".
- Now flash OpenGapps zip and you may also customise it to install only required apps.
- Now that you modified /system you have to disable dm-verity. Flash the "no-verity-withSE.zip".
- All done! Now you got a phone with Google Play Certified status and passing all SafetyNet & Root checks.
Click to expand...
Click to collapse
I went through the entire process and all went well until I tried to sign in through google play. It did the checking info screen and then went blank. No error messages. Has Google started blocking gapps?
abdullahik said:
Hi, Alex.
I have been having issues trying to use gapps on my samsung s6 dous China. I have been unable to use my google acccount on the phone after all the processes. I flashed android 7, twrp and installed gapps, then no verify. The processes went fine, but cant still activate my google account. Can u please point me to anything I am missing and also the version of the android OS and posibly download link you used on your phone. Thanks.
Click to expand...
Click to collapse
dervxerox said:
I went through the entire process and all went well until I tried to sign in through google play. It did the checking info screen and then went blank. No error messages. Has Google started blocking gapps?
Click to expand...
Click to collapse
Make sure you have also selected to install "WebView" in the Gapps list. So the 'gapps-config.txt' looks something like this:
Code:
# Pico+
#CalSync # Install Google Calendar Sync (if Google Calendar is being installed)
#DialerFramework # Install Dialer Framework (Android 6.0+)
GoogleTTS # Install Google Text-to-Speech Engine (Micro+ on 5.0-, Pico+ on 6.0+)
#PackageInstallerGoogle # Install Package Installer (Android 6.0 only & Android 8.0+)
# Nano+
BatteryUsage # Install Device Health Services (Android 7.1+)
#FaceDetect # Install Face Detect Library
#FaceUnlock # Install Trusted Face
Markup # Install Markup (ARM64 + Android 9.0+)
Search # Install Google App (excluding excludes GoogleNow/PixelLauncher)
Speech # Install Offline Speech Files
Wellbeing # Install Digital Wellbeing (Android 9.0+)
# Micro+
CalendarGoogle # Install Google Calendar
ExchangeGoogle # Install Exchange Services
Gmail # Install Gmail
GoogleNow # Install Google Now Launcher (Android 4.4 only) (requires Search)
PixelIcons # Install Pixel Icons (Android 7.1 only)
PixelLauncher # Install Pixel Launcher (Android 5.0+) (requires Search and Wallpapers)
Wallpapers # Install Google Wallpapers (Android 5.0+)
# Mini+
CalculatorGoogle # Install Google Calculator (Android 5.0+)
CarrierServices # Install Carrier Services (Android 6.0+) (required for Google Messages)
ClockGoogle # Install Google Clock
Maps # Install Google Maps
Messenger # Install Google Messages (except on tablet devices) (requires Carrier Services)
Photos # Install Google Photos
TagGoogle # Install Google Tags (Android 5.0+)
YouTube # Install YouTube
# Full+
Books # Install Google Play Books
Chrome # Install Chrome
CloudPrint # Install Cloud Print
Drive # Install Google Drive
Keep # Install Keep Notes
Movies # Install Google Play Movies & TV
Music # Install Google Play Music
NewsStand # Install Google News
PlayGames # Install Google Play Games
Talkback # Install Android Accessibility Suite
# Stock+
AndroidAuto # Install Android Auto (Android 5.0+)
CameraGoogle # Install Google Camera (Android 6.0+)
ContactsGoogle # Install Google Contacts (Android 5.1+)
DialerGoogle # Install Google Phone (Android 6.0+)
Duo # Install Duo
GooglePay # Install Google Pay
KeyboardGoogle # Install Gboard
PrintServiceGoogle # Install Print Service Recommendation Service (Android 7.0+)
StorageManagerGoogle # Install Smart Storage (Android 7.0+)
Translate # Install Google Translate
VRService # Install Google VR Services (Android 7.0+)
#WebViewGoogle # Install Android System Webview (Android 5.1+) (WebViewStub is installed on Android 7.0+)
#WebViewStub # Install Android System Webview (Stub) (Android 7.0+) (See note with WebViewGoogle)
# Super+
ActionsServices # Install Actions Services (Android 9.0+)
BetterTogether # Install Better Together (Android 9.0+)
DMAgent # Install Google Apps Device Policy
Docs # Install Google Docs
Earth # Install Google Earth
Fitness # Install Google Fit
GCS # Install Google Connectivity Services (Android 5.1+) (excluding also excludes ProjectFi)
Hangouts # Install Hangouts
Indic # Install Google Indic Keyboard
Japanese # Install Google Japanese Input
Korean # Install Google Korean Input
Pinyin # Install Google Pinyin Input
ProjectFi # Install Project Fi (Android 5.1+)
Sheets # Install Google Sheets
Slides # Install Google Slides
Street # Install Google Street View
Zhuyin # Install Google Zhuyin Input
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use this Guide at your own risk there is no warranty or guarantee.
How to Root the H910 and install the Lemon Drop Rom?
1. Disable real time scanning, on the windows virus scanner. Download all the files, save terminal emulator to your microsd card the other two save on your computer, unzip dirtysanta, install usb drivers if using windows. Root your H910 with this guide.
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
2. [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) Note: before you flash the KDZ to downgrade your firmware make a DUMP backup with LGUP all files. You don't need to DUMP system or cache. It will have your EFS.
3. On step3.bat wait for phone to reboot from fastboot mode, when you see the LG logo, pull the battery. Do a factory reset and that will load TWRP How to factory reset the Lgv20.
4. Then format data. Very important, you format data with the older version of twrp that is with dirtysanta.
5. Then power off phone.
Note: This next part is for the H910, you need to get your version of twrp for your model of Lgv20. Latest version of twrp link at the bottom of page
6. Download twrp for the H910 twrp-3.7.0_9-0-h910.img
7. With the phone powered off, hold the down volume button and plug in usb to computer and phone.
fastboot flash recovery twrp-3.7.0_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
8. Then you want to format data once more with the new version of twrp.
9. power off phone
10. Then go to: [Lemon Drop] A [Debloated] & [DeGooged] [Stock] [Oreo] [Rom] for the H910 & Most Lgv20 phones.
(archived)
Install Oreo on the H910 & debloat ALL lgv20 phones.
Any Lgv20 phone can debloat go to step 13. H910 phones start at step one.
If you are having issues downloading the rom you can try this download manager for Firefox.
Turbo Download Manager
1. Download the following files. And put them on the sdcard.
twrp-3.3.1-0-h910.img
H910_20g_Oreo_full_rooted.zip
h910oreomodem.img
H910_1.0-ezV2020.zip new kernel
adreno+5xx+-+v313+rev23+-+non-treble.zip new gpu drivers
Magisk-v19.0.zip (direct link to github)
MagiskManager-v7.1.1.apk (direct link to github)
2. Restart phone into recovery. (aka twrp)
3. Then install twrp-3.3.1-0-h910.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
4. Reboot phone into Recovery
5. Click wipe then Swipe to factory reset
6. Install H910_20g_Oreo_full_rooted.zip
7. Then install h910oreomodem.img (The img file you can flash with twrp you just need to select Install Image, select the file and choose modem)
8. Then install twrp-3.3.1-0-h910.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
9. Then install Magisk-v19.0.zip
10. Then install adreno+5xx+-+v313+rev23+-+non-treble.zip
11. Then install H910_1.0-ezV2020.zip then wipe dalvik cache
12. If you do not want to debloat Stock Oreo, then go to step 16. Otherwise to go step 14.
13. Any Lgv20 Reboot into twrp. Do steps 14, 15, 17, 18. Can debloat numbers 10 - 18
14. Click on Mount, make sure Mount system partition read-only is unchecked. Mount System. Then open up file manager under advanced.
15. If you want to debloat the H910 phone, these 18 lines can be safely deleted with the trwp file manager. Note these 17 lines should be removed before first boot H910.
01. "/system/priv-app/AMBS" bloatware at&t backup and sync messaging
02. "/system/priv-app/ATT_Lookout" bloatware att lookout
03."/system/priv-app/ATT_AppSelect" bloatware installs unwanted apps in background.
04. "/system/priv-app/ATT_DeviceHelp" bloatware
05. "/system/priv-app/ATT_IQI" bloatware
06."/system/priv-app/ATT_RemoteSupport" bloatware
07. "/system/priv-app/ATT_SNT" bloatware
08. "/system/priv-app/MetricService" bloatware
09. "/system/vendor/app/ATT_HotSpots" bloatware
10. "/system/priv-app/EdenService" bloatware
11. "/system/priv-app/LGDMSClient" OTA Updates
12. "/system/priv-app/LIAInformant" bloatware
13. "/system/app/LGATCMDService" OTA Updates
14. "/system/app/LGFOTA" OTA Updates
15. "/system/vendor/app/SecProtect" bloatware
16. "/system/vendor/bin/triton" It's an antivirus program, slows the phone down.
17. "/system/vendor/bin/tftp_server" Prevents phone from downloading any updates
18. "/system/priv-app/GCUV" Blotware some kind of LGE sign in portal, looks like it may cause a battery drain also.
16. Restart and run setup and update Magisk v23.0 confirmed working.
17. Disable MLT/LDB Use a root file manager
required folders:
/system/vendor/overlay/com.lge.mlt
/system/priv-app/LGLDB
open: "/mpt/enable" change "1" to "0"
change file permissions for "/mpt/enable" to 0444
reboot
18. done
Recommended twrp options for backup.
Boot
Recovery
System Image
data (excl. storage)
EFS
Fimrware
LAF/Download Mode
Optional packages to debloat H910 and ALL Lgv20 phones.
LG Messaging is required, to run the setup, first boot. Most other apps that are not on the list, you can just disable them in Oreo.
If for what ever reason you need to reinstall an app all you need to do is unzip the rom H910_20g_Oreo_full_rooted.zip and locate the "system" file and rename to "system.img" mount it on your computer and copy back the folder to the same location on the phone, reboot. Keep in mind this is the "/system" directory on the phone. File permissions 0644 for apk file.
Free root file manager no ads
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
ALL Lgv20 phones can debloat #07 - #32.
H910 phones can debloat #01 - #31.
These folders can safely be removed.
01. "/system/priv-app/ATT_DriveMode" ATT Drive Mode
02. "/system/priv-app/ATT_CallerNameID" ATT Caller Name ID
03. "/system/vendor/app/DirecTV_Remote" DIRECTTV Remote
04. "/system/vendor/app/DirecTV" DIRECTTV
05. "/system/vendor/app/ATT_UBER" Uber
06. "/system/priv-app/MyATT" My At&t app
07. "/system/app/EditorsSlidesStub" Google Slides
08. "/system/app/EditorsSheetsStub" Google Sheets
09. "/system/app/EditorsDocsStub" Google Docs
10. "/system/app/Music2" Google Play Music
11. "/system/app/Videos" Google Play Movies & TV
12. "/system/app/Drive" Google Drive
13. "/system/app/YouTube" YouTube
14. "/system/app/Maps" Google Maps
15. "/system/app/LatinImeGoogle" Google keyboard
16. "/system/app/Photos" Google Photos
17. "/system/vendor/app/facebook" Facebook
18. "/system/priv-app/facebook-installer" Facebook App Installer
19. "/system/vendor/app/facebook-appmanager" Facebook App Manager
20. "/system/app/Hangouts" Google Hangouts
21. "/system/priv-app/LGEmail" LG Email
22. "/system/app/GoogleInApps" Google In Apps
23. "/system/vendor/bin/xtra-daemon" info
........"/system/vendor/etc/xtra_root_cert.pem"
........"/system/vendor/etc/cacert_location.pem"
24. "/system/app/SDEncryptionHelper" SD Encryption Helper, I don't use SD Encryption.
25. "/system/app/WfdService"
......"/system/bin/wfdservice"
......."/system/etc/init/wfdservice.rc"
......."/system/app/atfwd"
......."/system/vendor/bin/ATFWD-daemon"
........"/system/vendor/etc/init/[email protected]"
.........'/system/vendor/bin/wifidisplayhalservice"
Screen Share may not work, if removed. Been reports of people using this app to hack into the phone, and view everything on your screen via wifi or LTE data reddit
26. "/system/vendor/app/SVIService" This app messes with the auto brightness. With it removed, you can change your brightness level with auto brightness enabled. If it's to bright, turn down the brightness and the phone will remember that setting, next time in the same light level.
27. "/system/etc/init/atrace.rc"
This is for debugging the kernel. Kernel trace logs are stored at "/data/anr/" you can delete them if you want. This slows boot time down and takes up memory. The phone makes a log about the size of 700MB each boot.
28. "/system/priv-app/LGBackup" Slows phone down use twrp to backup up
29. "/system/priv-app/BackupRestoreConfirmation" Slows phone down use twrp to backup up
30. "/system/vendor/overlay/com.lge.sizechangable.weather" Uses cpu cycles
31. "/system/priv-app/LGWeather" Uses cpu cycles
32. "/system/priv-app/Lookout T-Mobile Lookout
Credits, A Special Thank You
@ezzony - for the ezV2020 kernel. XDA
@askermk2000 - for the MK2000 kernel. XDA
@me2151 for DirtySanta. XDA
@clsA for the H910 v20g rom. XDA
@runningnak3d for a great H910 root guide. XDA
@darkknight200 for the H910 Oreo modem drivers. Download Link
at hardreset.info on how to factory reset the Lgv20
at TeamWin TWRP, for TWRP.
at the people over at Magisk, for an Opensource Root.
at XDA, for a Great Platform.
And everyone else that I may have missed that helped with the Lgv20.
Thank you all, for helping make the Lgv20 phone one of the best rooted phones of all time.
how fast is the performance like pubg
DesrtSailor said:
how fast is the performance like pubg
Click to expand...
Click to collapse
I have never played pubg so I cant tell you, I can tell you the UI is faster and I do have one game on my phone Reckless Racing 3 and it seems to play a little faster and does not skip frames that I can see. But keep in mind that the Lgv20 is not the fastest phone around it's a 2016 model. But my guide will help you get the fastest experience out of your phone.
did u run geekbench scores or antutu
how is compared to nougat
DesrtSailor said:
did u run geekbench scores or antutu
how is compared to nougat
Click to expand...
Click to collapse
Yeah I got some benchmarks. I should have uploaded them but I was still working on my guide. Sorry don't have Nougat.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone has the H91020I update, could I use this method to root? Or I am out of luck.
HAMSATHI said:
My phone has the H91020I update, could I use this method to root? Or I am out of luck.
Click to expand...
Click to collapse
That's a good question, unfortunately I don't have the answer, please ask in this forum.
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
I am so glad I waited, this guide sounds like exactly what I am looking for! I'll be attempting this tonight on my backup AT&T V20 variant. Thank you
Dream Reality Syndrome said:
I am so glad I waited, this guide sounds like exactly what I am looking for! I'll be attempting this tonight on my backup AT&T V20 variant. Thank you
Click to expand...
Click to collapse
Your welcome.
Darnrain1 said:
Your welcome.
Click to expand...
Click to collapse
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Dream Reality Syndrome said:
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Click to expand...
Click to collapse
I have had that happen before with AFH. I used firefox and just pressed retry a lot. Let me think about this maybe I can just upload the files to xda.
Darnrain1 said:
I have had that happen before with AFH. I used firefox and just pressed retry a lot. Let me think about this maybe I can just upload the files to xda.
Click to expand...
Click to collapse
okay I am uploading the files to xda but my upload speed is not that fast. I think this will take an one hr or two. As for package manager and Mixplorer you still should download the apps from the developers.
Dream Reality Syndrome said:
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Click to expand...
Click to collapse
xda does not allow me to upload the 2.5 gb file. I guess it's to large.
Try firefox and if the download stops press retry and it should continue where it left off. As for using another version you can try but I recommend H910 V20g it seems to be stable.
Darnrain1 said:
xda does not allow me to upload the 2.5 gb file. I guess it's to large.
Try firefox and if the download stops press retry and it should continue where it left off. As for using another version you can try but I recommend H910 V20g it seems to be stable.
Click to expand...
Click to collapse
I will try your method tonight. Thank you for trying!
Dream Reality Syndrome said:
I will try your method tonight. Thank you for trying!
Click to expand...
Click to collapse
Try this downloading extension for Firefox. I was having issues also but this worked for me.
Multithreaded Download Manager by jingyu9575
T
Darnrain1 said:
Try this downloading extension for Firefox. I was having issues also but this worked for me.
Multithreaded Download Manager by jingyu9575
Click to expand...
Click to collapse
This worked out perfectly, thank you!!
My H910 V20 has been up for 18 + days can counting. Very stable install of Oreo.
Darnrain1 said:
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use this guide at your own risk there is no warranty or guarantee.
This guide will walk you through step by step on how to install Oreo on the H910.
I assume that your phone is already rooted. If not, click on this link below.
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
You may be wondering why I used v20g version when there is an v20h version out. The v20g version is very stable. And most of the updates from g to h are most likely just carrier updates not OS updates. I went with version 19.0 of Magisk because it's very stable, newer versions may prevent your phone from booting.
How to install Oreo on the H910 with Root
Make sure you have a backup of all your important files from the internal storage before you start. We will be reinstalling the android operating system.
Note: If you have trouble downloading the files you can try this Firefox downloading extension.
Multithreaded Download Manager by jingyu9575
1. Download the following files. And put them on the sdcard. You can use MIXplorer or another root file manager of your choice you just need to be able to install the file manager from the sdcard (no internet).
recovery-twrp-h910-2018-10-18.img
H910_20g_Oreo_full_rooted.zip
h910oreomodem.img
MK2000 kernel 2.0
Magisk Uninstaller
Magisk 19.0
Magisk Manager 7.1.0
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
Package Manager
2. Restart phone into recovery. (aka twrp)
3. Install recovery-twrp-h910-2018-10-18.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
4. Reboot phone into Recovery.
5. Do a format, then do a standard wipe.
6. Install H910_20g_Oreo_full_rooted.zip
7. Then install h910oreomodem.img (The img file you can flash with twrp you just need to select Install Image, select the file and choose modem) Then select Install Zip.
8. Then install H910_v2.0-mk2000.zip
9. Then wipe dalvik cache
10. Then install Magisk-v19.0.zip
11. Then reinstall recovery-twrp-h910-2018-10-18.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
12.. Reboot phone into System.
13. Then after the phone boots up into the setup screen click next and disable cell and wifi data. Internet need's to be off for this whole process.
14. Click next it will ask you to enable but just skip everything.
15. When you get to home screen, put the phone in airplane mode.
16. Open the LG file manager and install MiXplorer from the sdcard and give it root access. (Or use any root file manager you like, as long as you can install the file manager from the sdcard offline.)
17. Open your root file manager go to (root) /system/priv-app/
18. I deleted some folders, this will make your phone run faster. (Bloatware)
ATT_DeviceHelp
ATT_IQI
ATT_Lookout
ATT_CallerNameID
ATT_AppSelect
ATT_RemoteSupport
ATT_SNT
19. Reboot your phone but stay in airplane mode for now.
20. Install com.smartpack.packagemanager_45.apk (aka package manager) from the sdcard.
21. Open Package Manager give it root access, go to system and do a search for the following updates and Uninstall them. (Updates will break your phone because it's rooted.)
com.lge.android.atservice
com.lge.lgdmsclient
com.lge.lgfota.permission
22. Open Magisk go into settings and disable, Check for Updates. I would recommend just staying with Magisk 19.0 it's stable and works well with Oreo.
23. Congratulations on completing the installation process. You can now enable cell data and wifi.
Note: Don't uninstall the built in weather app, it will cause second screen to crash and make your phone unusable. I would recommend using package manager to disable the apps you don't want, that way you can always re-enable them. Also the Amazon app takes up a lot of battery power. The Amazon app is is not well optimized for android at the time of writing this guide.
There is a bug in the latest version of chrome and web view that makes the screen flicker on some apps. To fix this you need to disable chrome and enable chrome and check do not auto update in the play store, and don't update chrome. I use the Kiwi browser it's based off of chromium and you can install chrome extensions.
I have found a fix for the flickering you have to install the updated graphics driver. This driver is for oreo only lgv20, after you flash in twrp you must wipe dalvik cache.
[10/27][Adreno][OREO][Vulkan]Driver for Snapdragon 820/1[V313 REV23 | V330 REV3]
To fix the image retention install this shell script.
LGv20 fix image retention, aka screen burn in. shell script (root only)
Apps & Tweaks. All apps & tweaks are free to use or open source.
Thermal Throttling Fix LGv20 (Stock root only) (fix thermal throttling for gaming)
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager) (Root file manager, free to use & no ads, there is a paid version on google play store if you want to support the dev.)
[GUIDE] Best Battery Life Possible (Disable LDB & Logging will increase speed of phone) This guide is for the LG G6 but will work with lgv20 phones, NOTE do not change the screen resolution go to the line that says Disabling LDB.
Package Manager (system app uninstaller)
Clock (Deskclock is a fork of the AOSP clock, so it offers all its functions) Good alarm clock.
LGv20 fix image retention, aka screen burn in. shell script (root only) (shell script to fix the screen burn in aka image retention on lgv20.)
Disable find my device administrator account. (Shell script to disable device administrator account.)
Disable lock screen service administrator account. (Shell script to disable lock screen service administrator account.)
Swap memory disabler (Disable zram on lgv20 Magisk Module.)
Sleep Timer (Sleep Timer helps you fall asleep while listening to music or podcasts. When the timer stops, audio playback is gradually lowered then paused.)
[APP] CpuFloat [March27] Floating cpu, gpu, temperatures, deep sleep, network monitor (Shows cpu info and float's on the screen.)
Simple Gallery Pro (Great gallery app for all your photos.)
Build Prop Tweaks
(just copy and past every thing below in /system/build.prop file at the very bottom save and reboot. With this tweak I recommend you have zram enabled.)
# Tweaks
# better multitasking
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_age=5000
ro.vendor.qti.sys.fw.bservice_limit=5
# extend battery life
wifi.supplicant_scan_interval=180
Issues I had with my lgv20
I had some issues with a magisk module called zram_manager, The apps I had open were acting funny and I had to close them and open them back up again. I don't recommend that magisk module for the lgv20. I just use the stock zram.
I was having a odd issue with the files on my sd card. My file extensions were getting renamed to .0 such as song.mp3.0 so I could not play my music. It was VLC or vanilla music player. I uninstalled both and so far the issue has not returned. For now I am just using MiXplorer to play my music and watch videos on my phone. Update so far it's been a month and no issues with the renaming of my songs.
Click to expand...
Click to collapse
Works 99%, except no data (T-Mo, AT&T H910) - modem file? Anyone else found a solution to no data? (Calls OK, just no network data)
TomJ2 said:
Works 99%, except no data (T-Mo, AT&T H910) - modem file? Anyone else found a solution to no data? (Calls OK, just no network data)
Click to expand...
Click to collapse
I have AT&T, 4G LTE data works. But if you using an AT&T phone on T-Mobile then that may be why the data is not working.
This is what I found on the internet.
Will an unlocked H910 AT&T model support T-Mobile wi-fi calling?
MORE ATT CRAP TO GET RID OF
In order to completely disable fota. i had to get rid of the following (i deleted anything in the system folder with fota in the file name):
/system/apps/lgfota
/system/etc/fota
/system/etc/terms/fota
/system/lib/libfotajni.so
/system/lib64/libfotajni.so
/system/etc/permissions/com.lge.fota.xml
There's also extra att bloatware to get rid of:
/system/app/vvm_att
/system/vendor/app/facebook-appmanager
/system/vendor/app/facebook
/system/vendor/app/directv_remote
/system/vendor/app/directv
/system/vendor/app/att_uber
The only att app you want to leave on the phone is /system/vendor/app/att_hotspots; wifi calling will not work without it.
Now, get ready for some weird stuff....
GOOGLE CRAP TO KEEP
These folders are split up among /system/app and /system/priv-app
googlepackageinstaller (keep to be able to install apk's)
googleextshared (phone boot loops without this)
googleextservices (phone boot loops without this)
webviewgoogle (aurora store at this moment seems to only work with the webview that came with the stock rom and it's browser and will work with no others)
chrome (aurora store at this moment seems to only work with the webview that came with the stock rom and it's browser and will work with no others)
Here's where it gets weirder, but if i figured it out for everyone, it wasn't easy...
GOOGLE CRAP TO GET RID OF AND KEEP WIFI CALLING FUNCTIONAL
This next part is specifically for degoogling and maintaining wifi calling without having google try to update apps the moment you get connected to wifi. I did this in two stages...
PART 1
Get rid of the following:
These folders are split up among /system/app and /system/priv-app
youtube
editors slides
editors sheets
editors docs
photos
maps
hangouts
phonesky
music
videos
google pay
gmail
latininlmegoogle
drive
calculator
velvet
driveactivator
tag
GoogleBackupTransport
GoogleContactsSyncAdapter
googlecalendarsyncadapter
google tts
hotwordenrollment (all hotword enrollment folders)
google in apps
talkback
GoogleFeedback
GooglePartnerSetup
GoogleOneTimeInitializer
SetupWizard
PART 2
After part 1 is complete
A. Boot into android.
B. Connect to wifi.
C. Activate wifi calling.
D. Verify wifi calling works (call your phone, have another phone call your phone, either or for that test).
E. Go into android settings and disable google play services and google framework, restart phone, then confirm wifi calling still works.
F. Reboot phone into twrp, remove gmscore and googleservicesframework (again, you'll find these folders among system/app and /system/priv-app).
G. Congratulations, you've degoogled as much as possible without clawing at the walls wondering why wifi calling isn't working after you degoogled.
MICROG?
Microg works very well on this phone. Microg is pretty much fake google services so you can still run normal apps from the play store.
1. Reboot into twrp and flash nanodroid patcher patckage. This patches the phone to allow signature spoofing; a requirement of microg.
2. Flash nanodroid microg package.
3. Reboot into android.
4. Open microg settings.
5. Go into "self-check" inside of microg settings, allow everything and check off all the boxes in there.
6. Get out of self-check and go into "google device registration" and turn that on.
7. Update to the latest version of aurora store since the nanodroid package include an old one.
8. Go into aurora store after you updated it, allow all it requires, keep it with the "session installer".
9. Once aurora store initial setup is complete, go into "blacklist manager" and check off all the boxes in there.
A. Aurora store will mistake microg as outdated and want to wipe it out with a google play services installation.
B. You don't want aurora store upgrading any of the android operating system files on your phone.
C. Doing this ensures that any app you install from aurora store afterward won't be blacklisted, and aurora store gets relegated for apps you installed and updates for those apps.
10. Consider installing fdroid so you can keep aurora store regularly updated with the newest version.
11. Congratulations, you've degoogled as much as possible without losing wifi calling and still run apps from the play store.
SHORTER BOOT TIME AND SHUTDOWN TIME
Delete the following to shave seconds off boot and shutdown time (your phone will have no more start up noise, turn on 5 seconds faster, and have no more shutdown animation since att's attempt at visualizing a shutdown was very odd).
/system/media/bootanimation.zip
/system/media/shutdownanimation.zip
You can actually get rid of the media folder, but do that if you don't want user interface sounds, or your typical alarm noises (and that's how you don't wake up to a silent alarm the next day if you delete this folder).