Develop Bugs

[Q] How to tell if it'll work on your phone.

How can I tell if a "s3" rom ok for a i747?
For example I got this LS-LP-v4.1-2015-05-01-liquid_d2tmo.zip from androidfilehost.
sgh-i747 is d2tmo but there's very different from a i9300 d2tmo
I found this in the metadata file
Post-build=samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys
Which suggests it's the wrong radio for me.
I'm pretty sure this one would brick.
I'm having issues with APN not working on some roms, for example LS 3.2 fails but LS 3.1 works.

Searching zips, I found some things to answer this...
Rom: DU_LTE_4.4.4_2014029-2318.V8.1-OFFICIAL.ZIP
File: \META-INF\com\google\android\updater-script
Code:
getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo" ||
Code:
ifelse(is_substring("I747", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/gsm/* /system/"));
Test: Flashed fine, booted, have not tested further yet.
Rom: LS-LP-v4.1-2015-05-01-liquid_d2tmo.zip
The only d2tmo and i747 references were in binary files.
The update script does no hardware verify checks.
This rom is not going on my i747.

It should work till you wanna use radios, that's where you should see complications
Sent from my Nexus 7 using Tapatalk

Upgrading the radio did solve the issue I was having with blank APN when using DU 8.1
Trail blazed.
What I learned.
For reference only.
The radio baseband upgrade process is easy enough, but comes with warnings:
1) Upgrade your recovery first (TWRP or CWM)
2) Once updated, you might not be able to go back.
3) Best to have an extra backup phone.
[ROM] Dirty Unicorns 4.4.4 [7/20] link to 7.8
Last post shows new maintainer deadman96385, link to v7.8....
[ROM][4.4.4] Dirty Unicorns [v7.8] #1
Working download link DU_d2lte_4.4.4_20140815.v7.8-OFFICIAL.zip
Which radio is recommended?
-- Make Sure You Have A Custom Recovery.
-- Wipe Everything But Your External/Internal Storage.
-- Move the ROM Zip To Your Device.
-- Flash It And Reboot.
-- Once the ROM Boots, Reboot Back Into Recovery.
-- Flash The Recommend Gapps and ENJOY!​No idea.
For a noob, upgrading the radio is not a consideration here.
This is missing -- Make sure your radio is compatible.
I recommend this for all XDA ROM threads, not just this one.
Almost every Custom ROM thread has ????? about the radio issues.
[ROM][4.4.4] Dirty Unicorns [v7.8] Post #155
Nice link to baseband upgrade info...
[Firmware][4.4.2] NE4/NE6/NF2/NH2 Recovery Flashable Firmware #1
DocHoliday77:To flash the base 4.4.2 firmware [I747 UCUFNE4 - AT&T] to your device​[Firmware][4.4.2] NE4/NE6/NF2/NH2 Recovery Flashable Firmware #104
enewman17:For those trying to update from old firmware like LK3 which is 3 updates behind.
I suggest those incrementally update till 4.4
I747 LK3 4.1.1 -> I747 MG2 4.1.2 -> I747 MJB 4.3 ​[Firmware][4.4.2] NE4/NE6/NF2/NH2 Recovery Flashable Firmware #139
DocHoliday77 :Boot TWRP and flash, Factory reset, Reboot, Open SuperSU and let it disable Knox.
Once rooted, DO NOT UPDATE SuperSU!
​[ROM][4.4.4] Dirty Unicorns [v7.8] #250
jayharper08:The thread was closed by a senior mod "Closed per OP's request"​[ROM][4.4.4] Dirty Unicorns [v7.8] #245
Omega Hunter:"At least 8.1 left us with a fairly solid ROM. (Though for some reason I get random black-screen-of-deaths.)"​/irony
[ROM][4.4.4] Dirty Unicorns [v7.8] #136
spaceman860 15th September 2014:Link to DU downloads... has no d2 http://download.dirtyunicorns.com/files/
Maybe d2 has a special folder.
I found \misc\Timetogetdirty.apk ? Probably the boot animation.
The thread mentions g+ download links, but g+ is just a haystack to hide needles in.​Related Playstore links:
Network Signal Info
https://play.google.com/store/apps/...telnet&feature=nav_result#?t=W251bGwsMSwyLDNd
GetRil (nice but the only s3 it knows is i9300)
https://play.google.com/store/apps/...getril&feature=nav_result#?t=W251bGwsMSwyLDNd
Looks like the DU 7.8 is the best bet for DU on S3.
But I'm thinking SlimKat or LiquidSmooth now.
What did DocHoliday77 mean by Once rooted, DO NOT UPDATE SuperSU! ??

Clues said:
Upgrading the radio did solve the issue I was having with blank APN when using DU 8.1
What did DocHoliday77 mean by Once rooted, DO NOT UPDATE SuperSU! ??
Click to expand...
Click to collapse
couldnt say. unless someone else chymes in. @DocHoliday77 has been M.I.A. for some months now.
thanks for the update though.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

Originally Posted by Clues
Upgrading the radio did solve the issue I was having with blank APN when using DU 8.1
What did DocHoliday77 mean by Once rooted, DO NOT UPDATE SuperSU! ??
Click to expand...
Click to collapse
mrrocketdog said:
couldnt say. unless someone else chymes in. @DocHoliday77 has been M.I.A. for some months now.
thanks for the update though.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
I think ChainFIre made a flurry of SuperSu updates that resolved issues found with the release of the NJ/NH bootloaders. I definitely recall people being advised to update SuperSu in other instances since that time. I have continually updated SuperSu, BUT I am on an older bootloader.

[RECOVERY][TWRP][dragon]

April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !
https://twrp.me/google/googlepixelc.html
I would like to continue this thread for publishing test builds and other troubleshooting.
Once the changes are stable and tested I will merge them into TeamWin github for the next official build.
Known issues:
- FBE (file based encryption) is not working correctly, pls use FDE (full disk encryption) instead.
fwtool
The "fix fastboot" advanced menu item has been removed as it's not part of the official TWRP sources.
The fwtool is still existing (/sbin/fwtool) - only the menu item has gone.
If you need the fwtool, to fix fastboot, you can use it like before, but now you have to type the command into terminal inside TWRP.
For more details, pls have a look here .. http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
Installation:
Please install the new version from your current TWRP.
Pls make a "reboot to recovery" once you have installed the new version.
Of course you can install it via fastboot too.
Sources:
https://github.com/TeamWin/android_device_google_dragon
https://github.com/omnirom/android_bootable_recovery
DOWNLOAD:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
Have fun!
XDA:DevDB Information
[TWRP][dragon], Tool/Utility for the Google Pixel C
Contributors
followmsi
Version Information
Status: Stable
Current Stable Version: 3.3.1-2
Stable Release Date: 2017-04-01
Created 2016-06-17
Last Updated 2023-01-11

Changes:
Official 3.7.0_9-1 (2023-03-25)
- Exclude MTP
- Restore stock values for init.recovery.dragon.rc
- Enable Screen Timeout
https://dl.twrp.me/dragon/twrp-3.7.0_9-1-dragon.img.html
Official 3.7.0 (2022-10-10)
- New official version -> https://twrp.me/site/update/2022/10/10/3.7.0-released.html
Official 3.6.2 (2022-06-01)
- New official version -> https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
Official 3.6.1 (2022-03-10)
- New official version -> https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
Official 3.6.0 (2021-11-28)
- New official version -> https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
Official 3.5.2 (2021-04-07)
- New official version -> https://twrp.me/site/update/2021/04/07/twrp-3.5.2-released.html
Official 3.5.1 (2021-03-17)
- New official version -> https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Official 3.5.0 (2020-12-31)
- New official version -> https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html
Official 3.4.0-0 (2020-06-22)
- New official version -> https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Official 3.3.1-2 (2020-03-01)
- Script updates to improve encryption -> Thanks to updateing from Team Mokee !
Official 3.3.1-1 (2020-01-27)
- Script updates for Android 10
- Added more languages
- Fixed build issues
- New Kernel
Official 3.3.1-0 (2019-05-19)
- New official version
Official 3.3.0-0 (2019-04-10)
- New official version
Official 3.2.3-0 (2018-07-29)
- New official version
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Official 3.2.2-0 (2018-06-30)
- New official version
* DRM changes
Official 3.2.1-0 (2017-12-18)
- New official version
Official 3.2.0-0 (2017-11-29)
- New official version
Official 3.1.1-1 (2017-09-15)
- Including all changes for Oreo and for better en/decryption from unofficial V1 and V2
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O-v2.img (2017-09-11)
- New "pulldecryptfiles.sh" to copy all "bin" and "lib64" files from system/vendor partitions.
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O.img (2017-07-31)
- Official TWRP Nougat ramdisk mixed with new Oreo kernel binary to support Android 8.0 (SDcardFS .. etc.)
Official 3.1.1-0 (2017-05-17)
- Upgrade to 3.1.1-0
Unofficial 3.1.1-0 (2017-05-14)
- Latest TWRP changes (3.1.1)
- Latest kernel sources (2017-05-12)
- Latest LineageOS changes (Android 7.1.2)
Official 3.1.0-0 (2017-04-01)
- Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.
3.1.0-2
- Custom installer script problems should be fixed now.
3.1.0-1
- Removed all the FBE changes - will take longer to get it running on dragon
- Added NTFS-3G support for NTFS R/W -> USB-OTG
- Used new kernel binary with changed F2FS config
3.1.0-0
- @dees-Troy just tagged version 3.1.0 - made a new version based on latest sources.
- Added some more config changes for FBE.
3.0.3-4
- Used latest TWRP and AOSP soruces and enabled some features for FBE encryption.
3.0.3-3
- Added "Data (incl. storage)" partition for usb-otg backup of "complete" data partition
- fstab modification (usb-otg -> auto)
3.0.3-2
- F2FS enabled
- tegra-3.18 kernel -> v170210 (ntfs + f2fs enabled)
3.0.3-1
- Based on Android 7.1.1 AOSP -> android-7.1.1_r14
- Based on TWRP branch for Android 7.1
- tegra-3.18 kernel -> v170208 (ntfs + f2fs enabled)
v23
- Based on Android 7 AOSP -> android-7.0.0_r3
- Based on TWRP branch for Android 7
- tegra-3.18 kernel -> v160907
v22
- Based on Android 7 AOSP -> android-7.0.0_r1
- Based on TWRP branch for Android 7
- chromeos-3.18 kernel -> v160823
- Maybe not fully working as v21 due to new sources.
v21
- Added BRIGHTNESS PATH ... Thx to @ggow
v20
- Added Battery PATH ... Thx to @ggow
v19
- "Failed to unmount `/system `(Device or resource busy)" - Finally fixed now
- New versioning
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
v17
- "Failed to unmount `/system `(Device or resource busy)" - Not fully fixed - hopefully soon !
- chromeos-3.18 kernel -> v160618
v16
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617

Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app

DarthDestroyeis said:
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the feedback ..
Did you install something before .. maybe still mounted from before ?
Or you just made the backup only ?
Which partitions did you backup ? .. system as well .. or just data ?
Pls post recovery.log on pastebin.com .. helps a lot !
Thanks

http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk

DarthDestroyeis said:
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
It´s always system which is complaining .. no other partitions, correct ?
Thanks ... will have a look.

Yup... just the system partition.

Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?

N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again

ilpolpi65 said:
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
Click to expand...
Click to collapse
You did flash system-vendor update.zip via fastboot ?
No good idea.
The kernel and the TWRP are fine to flash via fastboot, but not the system.img and vendor.img.
Like written on first page of the updatr.zip thread.
Pls install the package via TWRP.
Or use unmodified stock image from Google for fastboot.
For recovery bootloop I know only "fastboot reboot".
I had the bootloop once myself, as I still was on M, but the command did help me.

YevOmega said:
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
Click to expand...
Click to collapse
I am not the OTA User
As I know, the tool "flashfire" from Chainfire should handle the whole OTA process smoothly.
The Update.zip packages I do anyway, because I am used to it .. over the years.
Did this for Nexus Flo ... Nexus 10 as well.
For Pixel C I just publish them, because nobody as else is doing it.
Look in Flo and manta xda .. They have these packages too, done by others.
Because of all the problems with OTA .. in the past ..and still today.
Today we have systemless root and regular OTA...times are changing.
Maybe it's time for something like flashfire in the next time ..

sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)

ilpolpi65 said:
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
Click to expand...
Click to collapse
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..

followmsi said:
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
Click to expand...
Click to collapse
True... It's really strange..but..pixel c too is a strange device...
anyway thanks for your help !

DarthDestroyeis said:
Yup... just the system partition.
Click to expand...
Click to collapse
v17
- "Failed to unmount `/system `(Device or resource busy)" - fixed now
- chromeos-3.18 kernel -> v160618
Please have a try with v17.
My problems are gone .. no more warning messages while doing backup or restore.
"Failed to unmount `/system `(Device or resource busy)"
Pls test as well !
Thanks

sorry for all this quick releases today .. this is the last one for now !
but when something new is working .. I would like to share it with you ...
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
Enjoy !

Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work

redukt said:
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
Click to expand...
Click to collapse
Today I have made 3 backups and restores
No problems or messages so far ..
But pls test on your device as well .... On Pixel C you never know
Cheers

Ok, will test it now without wipes

redukt said:
Ok, will test it now without wipes
Click to expand...
Click to collapse
Hopefully

Dirty Unicorns 10.6 what is correct vendor image?

Just installed Dirty Unicorn version 10.6 and flashed latest vendor image from the DU site which was mtc20k buti still get the 'wrong venor image' message everytime i boot up.
is that the correct image? i can't find a later one...
does it matter? i don't mind if it is just a cosmetic thing, and i have tested calling and SMS and all seems fine. are there any negatives to having an outdated vendor image.
thanks all

beardyone said:
Just installed Dirty Unicorn version 10.6 and flashed latest vendor image from the DU site which was mtc20k buti still get the 'wrong venor image' message everytime i boot up.
is that the correct image? i can't find a later one...
does it matter? i don't mind if it is just a cosmetic thing, and i have tested calling and SMS and all seems fine. are there any negatives to having an outdated vendor image.
thanks all
Click to expand...
Click to collapse
Did you try Flashing the vendor image before flashing the ROM?

beardyone said:
Just installed Dirty Unicorn version 10.6 and flashed latest vendor image from the DU site which was mtc20k buti still get the 'wrong venor image' message everytime i boot up.
is that the correct image? i can't find a later one...
does it matter? i don't mind if it is just a cosmetic thing, and i have tested calling and SMS and all seems fine. are there any negatives to having an outdated vendor image.
thanks all
Click to expand...
Click to collapse
Ignore the message, but MTC20K is the proper vendor for DU 10.6. If you want, you could always read the build.prop for the rom in /system and match that.
Sent from my Nexus 5X using Tapatalk

Same problem here, after upgrading to last DU 6.0.1 (10.6).
And I have the following lines in my build.prop that match "MTC20". None of them has a "K"… Strange
Code:
ro.build.id=MTC20L
ro.build.display.id=du_bullhead-userdebug 6.0.1 MTC20L eng.mazda.20160909.170844 test-keys
ro.build.description=bullhead-user 6.0.1 MTC20F 3031278 release-keys
ro.build.fingerprint=google/bullhead/bullhead:6.0.1/MTC20F/3031278:user/release-keys
BUILD_DISPLAY_ID=MTC20L

MikeolD said:
Same problem here, after upgrading to last DU 6.0.1 (10.6).
And I have the following lines in my build.prop that match "MTC20". None of them has a "K"… Strange
Code:
ro.build.id=MTC20L
ro.build.display.id=du_bullhead-userdebug 6.0.1 MTC20L eng.mazda.20160909.170844 test-keys
ro.build.description=bullhead-user 6.0.1 MTC20F 3031278 release-keys
ro.build.fingerprint=google/bullhead/bullhead:6.0.1/MTC20F/3031278:user/release-keys
BUILD_DISPLAY_ID=MTC20L
Click to expand...
Click to collapse
Not strange when DU and many other AOSP releases are often based on the latest source. Nexus 6P uses MTC20K Marshmallow sources so we get that on the 5X for this month.
Sent from my Nexus 5X using Tapatalk

I got the same error, although i have flashed MTC20K vendor image.... any advice???

With the vendor from the august build (MTC20F) no problems.

[KERNEL] Stock Kernel + SafetyNet Patch

Stock Pixel 2 XL/Pixel 2 Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.112
Suitable for build(s): All August 2019 builds
Suitable for devices(s): Pixel 2 XL (taimen) | Pixel 2 (walleye)
I compiled the stock kernel for the Pixel 2 XL/Pixel 2 and applied the SafetyNet patch by sultanxda. The kernel name says wahoo, which is the unified kernel that works on both taimen (Pixel 2 XL) and walleye (Pixel 2) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post (check the Downloads tab). Older versions can be found HERE.
XDA:DevDB Information
Stock Kernel + SafetyNet Patch, Kernel for the Google Pixel 2
Contributors
iissmart
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-18
Last Updated 2017-12-11

I want to apply this patch to my Huawei P9, but obviously can't use this one kernel. How would I go about applying the patch to my kernel? What programs / apps are needed?

Updated OP with the 8.1.0 kernel for December 2017 builds.

Hey anyone else having issues with windows defender seeing this as a virus when trying to download?

iissmart said:
Updated OP with the 8.1.0 kernel for December 2017 builds.
Click to expand...
Click to collapse
Works like a champ! Thanks so much!

Updated OP with the latest kernel for January 2018 builds.

Jan Security Patch
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
Could the safetynet patch be be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?

rweddy1 said:
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
Could the safetynet patch be be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?
Click to expand...
Click to collapse
What I do is revert back to the stock boot image (found here), reboot and let the phone install the OTA, then flash the new patched kernel.
I don't think it's possible to have the phone install an OTA successfully with a custom kernel, unfortunately.

iissmart said:
What I do is revert back to the stock boot image (found here), reboot and let the phone install the OTA, then flash the new patched kernel.
I don't think it's possible to have the phone install an OTA successfully with a custom kernel, unfortunately.
Click to expand...
Click to collapse
I didn't even think about that, thank you very much! I am all good now.

Can the kernel zip be flashed directly from twrp on the phone rather than extracting and using fastboot?

I've updated OP with the mid-month update to r0.18.

Anyone know if ViperAudio works with this ROM?

xD3CrypTionz said:
Anyone know if ViperAudio works with this ROM?
Click to expand...
Click to collapse
It's a kernel. Try viper and let us all know.

----REDACTED----

xD3CrypTionz said:
Did not try stock kernel but I have elementalx kernel with the Viper4Android Magisk module v2.9.
Click to expand...
Click to collapse
I haven't tried no. I'm happy with the sound on my phone.

Updated OP for February 2018.

Updated OP for March 2018.

Anyone else seeing issues with fast charging with Patched Kernel?
I have a run a few test & looks like patched kernel is not charging as fast as sock.
See below:
Patched Kernel: Battery at 82% when plugged in
After 10 min @ 86% After 20 min @ 89%
Stock Kernel: Battery at 82% when plugged in
After 10 min @ 90% After 20 min @96%
Again testing was done with same charger, same apps running, etc.

Updated OP for April 2018. I believe there is a confirmed issue with fast charging in the previous kernels - please test with this one and let me know if it still exists.

Updated OP for May 2018.

Firmware DUMP Android Q WW-17.1810.1910.68

Hi. guys.
This is the Firmware dump for Android Q.
Include 4 scripts who flash the FW into both slots ( A and B) (choose only one... "
USE AT YOUR RISK
Use it only if you are on Q .63 version or after.
Official source Android Q Here
To be sure you have 50% battery min before....
Do touch anything before script is finish
So reboot to bootloader
Use the good script into the folder extracted:
For Linux users, if you want a full flash use:
Code:
./script
or if you're on custom ROM and want only needed files, use:
Code:
./Update_script
For Windows Users, click on for all partitions
Code:
flash-all-partitions-fastboot.bat
or if you're on custom ROM and want only needed files, use:
Code:
Update-partitions-fastboot.bat
Enjoy with Android Q and Customs Roms
ZS630KL software Image：WW_17.1810.1910.63 for WW/IN only, *EU/RU/JP exclude int this FOTA version
*Special notice: This upgrade patch only allows to upgrade from Android P 16.1220.1909.194 version to Android Q 17.1810.1910.63 version. The other firmware version can't use this upgrade patch to upgrade.
Improved Item:
1.Upgrade to Android 10
2.Support Google Play System update
3.Added fully gestural navigation in Display setting
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please buckup your important data before system upgrading.
Click to expand...
Click to collapse
Version .68
System update
Optimized the mechanism of system update.
Optimized the system stability.
Audio
Improved the sound quality.
Click to expand...
Click to collapse
Download Link
My FW Dump .68

OP updated with .68 version
Add 2 new scripts for only one Update if you're on custom ROM.