Database Users

TWRP for HTC One M9

From TeamWin
http://twrp.me/devices/htconem9.html

Fastboot method without root? Looks interesting.. ill try later that day.

nope not possible
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 1.308s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.328s
but i hope with unlocked bootloader its possible to flash recovery ?

Yes. You need unlocked bootloader.

crucky said:
nope not possible
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 1.308s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.328s
but i hope with unlocked bootloader its possible to flash recovery ?
Click to expand...
Click to collapse
Damn man you're lucky you didn't brick your new phone, make sure to do the research first - Adam

@Adam182 - that wouldn't brick it. Reason? It won't flash in the first place.

Mr_Bartek said:
@Adam182 - that wouldn't brick it. Reason? It won't flash in the first place.
Click to expand...
Click to collapse
Got 2.8.5.0 running on my test device...... :good:
Rooted. There are limitations. \system is not writeable, as was initially on the M8 until insecure kernels were released here. Titanium Backup can't write to removable sdcard yet. I still have a hornet's nest of diagnostic software running and I have to give it a wide berth because logging is required on test devices.
Wonder if anyone there will notice what I've done after the overnight logs......

hgoldner said:
Got 2.8.5.0 running on my test device...... :good:
Rooted. There are limitations. \system is not writeable, as was initially on the M8 until insecure kernels were released here. Titanium Backup can't write to removable sdcard yet. I still have a hornet's nest of diagnostic software running and I have to give it a wide berth because logging is required on test devices.
Wonder if anyone there will notice what I've done after the overnight logs......
Click to expand...
Click to collapse
I have a tool which can recompile/decompile a kernel easy! No commands, you're rooted, get the stock kernel and disable it's security through it? I hope it works (Worked on 5-6 Qualcomm devices) .... Look into my sign
-------------------------------------------
HIT Thanks if you like my post
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
[ZIP]Flashable zip to bypass lockscreen for LG E975
[TOOL]ANDROID's COMPLETE TOOLBOX
Info about my work:
1)Kernel tool (reported to work on MTK too, tested on Qualcomm)
2)Bypass forgotten lock-screen without a factory reset
3)A COMPLETE TOOL for android, easy as cake, reported to work on MTK&Qualcomm​

MZ_. said:
I have a tool which can recompile/decompile a kernel easy! No commands, you're rooted, get the stock kernel and disable it's security through it? I hope it works (Worked on 5-6 Qualcomm devices)]
Click to expand...
Click to collapse
How do I get the boot.img from the device?
UPDATE: I might have the image at this point. Stumbled my way through adb commands to get the block, used the instructions here to extract what I believe to be a boot.img. Not sure, though, and sure as hell not going to flash it......

hgoldner said:
How do I get the boot.img from the device?
Click to expand...
Click to collapse
Rooted yeah? Extract from /dev/block/platform/msm_sdcc.1/by-name/boot (I told the link about my phone, yours may vary)
-------------------------------------------
HIT Thanks if you like my post
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
[ZIP]Flashable zip to bypass lockscreen for LG E975
[TOOL]ANDROID's COMPLETE TOOLBOX
Info about my work:
1)Kernel tool (reported to work on MTK too, tested on Qualcomm)
2)Bypass forgotten lock-screen without a factory reset
3)A COMPLETE TOOL for android, easy as cake, reported to work on MTK&Qualcomm​

Boot.img from 1.32.401.8: https://mega.co.nz/#!LY4nSK4D!S2QQcT5RQ2zurniqTiIlAEfOPo2DzndkN0VL5BQlgRc

Mr_Bartek said:
Boot.img from 1.32.401.8: https://mega.co.nz/#!LY4nSK4D!S2QQcT5RQ2zurniqTiIlAEfOPo2DzndkN0VL5BQlgRc
Click to expand...
Click to collapse
Cool, now someone can unpack/repack it with mods and boot from it, please do not flash as we don't know the outcome, better than risking it, just boot
-------------------------------------------
HIT Thanks if you like my post
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
[ZIP]Flashable zip to bypass lockscreen for LG E975
[TOOL]ANDROID's COMPLETE TOOLBOX
Info about my work:
1)Kernel tool (reported to work on MTK too, tested on Qualcomm)
2)Bypass forgotten lock-screen without a factory reset
3)A COMPLETE TOOL for android, easy as cake, reported to work on MTK&Qualcomm​

There's no risk in flashing. If it doesn't work just reflash my boot.img.

Mr_Bartek said:
There's no risk in flashing. If it doesn't work just reflash my boot.img.
Click to expand...
Click to collapse
I think I did it, based upon instructions here.
At least I believe I have a boot.img. Filesize is 65,536KB, was block p065. Note, ROM version currently is 1.33.90605.315 on Verizon, not Mr_Bartek's version.

Don't flash my version on Verizon. That is a large partition for just boot.img. What command did you use?

Mr_Bartek said:
Don't flash my version on Verizon. That is a large partition for just boot.img. What command did you use?
Click to expand...
Click to collapse
From the thread, I did the following:
1. I figured out that the mountpoints were located in /dev/block/f9824900.sdhci
2. From that I concluded that boot was mmcblk0p65
3. Based upon that I did the following in a DOS box on a Win7 system with the M9 connected via USB with debugging enabled:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p65 of=/sdcard/boot.img
I then pulled the boot.img off the sdcard to my PC
Note that the problem right now is that the internal drive is encrypted (they asked me to test encryption) and I can't turn encryption OFF on the internal sdcard. I've turned it on and off repeatedly on the removable sdcard (and that's not operating properly either). As a result, when I boot to recovery, TWRP can't read the internal sdcard. It asks me (repeatedly) to decrypt, but it doesn't accept the password. I was able to run a Nandroid onto the removable sdcard and backed up boot that way, too.

there just was an OTA for german O2 variant
Maybe one wanna try to use that boot.img ?
Kugelfischmau said:
here you go:
OTA_HIMA_UHL_L50_SENSE70_O2_UK_1.32.206.15-1.32.206.6_release_426806c23qb1mi6by8irro.zip
Click to expand...
Click to collapse
//EDIT:
was able to extract the kernel out of that boot.img with @MZ_. img tool.
But from here on I can't do nothing. If one could get an M9 for @Lord Boeffla, I'm sure he would have a look

DroidShift79 said:
there just was an OTA for german O2 variant
Maybe one wanna try to use that boot.img ?
//EDIT:
was able to extract the kernel out of that boot.img with @MZ_. img tool.
But from here on I can't do nothing. If one could get an M9 for @Lord Boeffla, I'm sure he would have a look
Click to expand...
Click to collapse
Feeling pretty accomplished .. BTW can't you edit default.prop by that? It has option about ro.secure=1 (be default) ... Not sure but you could try? :/
-------------------------------------------
HIT Thanks if you like my post
-------------------------------------------
My work:
Spoiler
[TOOL]Kernel/Boot.img (un)packer
[ZIP]Flashable zip to bypass lockscreen for LG E975
[TOOL]ANDROID's COMPLETE TOOLBOX

default.prop looks like this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.adb.secure=1
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
persist.sys.usb.config=adboff
ro.zygote=zygote64_32
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0

DroidShift79 said:
default.prop looks like this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.adb.secure=1
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
persist.sys.usb.config=adboff
ro.zygote=zygote64_32
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0
Click to expand...
Click to collapse
Try to change first two values to 0 ... Worked for my LGE975 (but remember HTC's bootloader is different)
-------------------------------------------
HIT Thanks if you like my post
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
[ZIP]Flashable zip to bypass lockscreen for LG E975
[TOOL]ANDROID's COMPLETE TOOLBOX
Baseband Fix fir LG F180X converted to International E975

How to check status of dm verity? To make sure it's disabled.

Hello everybody! I recently bricked my s7e by trying to install the superman mod because I was jumping between two guides and just followed the chapter for flashing the new bootloaders and not the beginning about twrp and so on.
Now I've done everything more carefully and thoroughly and executed the file for disabling dm verity and encryption. However I want to know if it is really disabled because I don't want to make the same mistake and have to reset me device again. Can you guys help me with how I check the status of em verity and encryption? I've tried to reach but just finds posts about people having the verification fail issue.
Thanks

Anyone our there that can help me or give me an idea?

Open a TWRP root shell and type:
Code:
surya:/ # avbctl get-verity
verity is disabled.
surya:/ # avbctl get-verification
verification is disabled.

lebigmac said:
Open a TWRP root shell and type:
Code:
surya:/ # avbctl get-verity
verity is disabled.
surya:/ # avbctl get-verification
verification is disabled.
Click to expand...
Click to collapse
Does it have to be with TWRP because Pixel 5 A12 doesn't have TWRP yet

elong7681 said:
Does it have to be with TWRP because Pixel 5 A12 doesn't have TWRP yet
Click to expand...
Click to collapse
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release (see link in my signature). Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification

lebigmac said:
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release. Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification
Click to expand...
Click to collapse
Can you send me a link to where I can find your tools?

lebigmac said:
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release (see link in my signature). Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification
Click to expand...
Click to collapse
Trying to use this on a slightly more out of date system. Is it possible to get you to release your tools in 32bit?

strayedsoul2003 said:
Trying to use this on a slightly more out of date system. Is it possible to get you to release your tools in 32bit?
Click to expand...
Click to collapse
I'll try to compile a 32 bit version sometime in the future but I can't say when. Just subscribe to the thread in my signature and you should be notified if there's any update
Wish me luck! Thanks
elong7681 said:
Can you send me a link to where I can find your tools?
Click to expand...
Click to collapse
Just click the link in my signature

elong7681 said:
Can you send me a link to where I can find your tools?
Click to expand...
Click to collapse
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com

[Guide][Linux][H631] How to extract KDZ Firmware

A youtube video on this guide
Hello guys,
I rarely write guide and tutorials .so neglect my typos and gramatical mistakes
Today im gonna show you how to unpackLG H631 Kdz firmware so that you can stock deodexed,debloated rom.,
Lets get started
LINUX
Note: Python i required (v2.7)
Things Needed:
1) kdzextractor
2) Python/bash executable machine
Procedure:
1) First of all download your kdz firmware which you want to extract.
(folder path ex:~/Desktop/firmware)
2) Copy the downloaded Kdzextractor and place kdz firmware in the same folder.
ex:~/Desktop/firmware/Kdzextractor)
3) Open terminal and enter below commands.
Code:
chmod +x run.sh
./run.sh
4) Wait for the completion of the process and check for system folder on boot.img in your working directory
ex:~/Desktop/firmware/Kdzextractor/system
ex:~/Desktop/firmware/Kdzextractor/boot.img
5)8) Hell Yeah! you have successfully unpacked that kdz firmware
now you can make your own stock deodexed rom
Downloads For linux:-
Go to https://github.com/innfinite4evr/Kdzextractor
and click on that green button "Clone or Download"
and select "Download zip" to start download.
Credits:
--------------------------------------------------------------------------------
LGE KDZ Utilities
Copyright 2013 "IOMonster" (thecubed on XDA and GitHub)
Copyright 2016 Elliott Mitchell
--------------------------------------------------------------------------------
mergersystem.py is by Cybojenix <[email protected]>
Its just tweaked to work with boot.img's as mergerboot.py
-------------------------------------------------------------------------------
@Innfinite4evr for testing this method and writing that bash script to automate the process and to write this guide!!!!!​

system.img it creates has no files.

Unable to install Modules with Magisk Manager

For some reason I am unable to install any Modules. I've looked online for solutions and the only things I have found were to flash a module manually with TWRP and to check to make sure that the folder MagiskManager exists on your internal storage. The folder existed for me already and flashing manually did not work. Root access works fine however, I can use ABP, Titanium Backup, etc. just fine and Root Checker shows that I have Root properly installed. Here is what the log looks like.
- Copying zip to temp directory
- Installing Wireguard_installer-1.2.zip
- Mounting /system, /vendor
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
inflating: config.sh
inflating: module.prop
*******************************
+-+-+-+-+-+-+-+-+-+
|W|i|r|e|g|u|a|r|d|
+-+-+-+-+-+-+-+-+-+
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Found /data/adb/magisk_merge.img
- Mounting /data/adb/magisk_merge.img to /dev/tmp/magisk_img
! /data/adb/magisk_merge.img mount failed...
Failed!
! Installation failed
Also this module was last updated on the 23rd so I'm positive that it is up to date.
Phone: Motorola Moto G5 Plus
Edit: Some spelling mistakes and added some more information

I'm also facing same problem

In the official magisk thread:
"Some Motorolla devices' stock kernel ships with a flawed F2FS implementation. Change to a custom kernel with the fix or format data to ext4."
Basically Moto didn't do a good enough job with f2fs on our device, so magisk manager has trouble with mounting images. SU works, but modules can't install, and twrp flashed modules don't show up anywhere.
The only fix is installing a custom kernel with an f2fs fix, though too often I found custom kernels performed worse than stock.

bazinga137 said:
In the official magisk thread:
"Some Motorolla devices' stock kernel ships with a flawed F2FS implementation. Change to a custom kernel with the fix or format data to ext4."
Basically Moto didn't do a good enough job with f2fs on our device, so magisk manager has trouble with mounting images. SU works, but modules can't install, and twrp flashed modules don't show up anywhere.
The only fix is installing a custom kernel with an f2fs fix, though too often I found custom kernels performed worse than stock.
Click to expand...
Click to collapse
Ah that's unfortunate, however a few modules can be flashed straight from twrp that I've tried already. Don't remember which one I tried though because I bricked my device trying to flash Xposed from the Xposed app instead of the magisk compatible version, luckily though I managed to get it out of bootloop.

You must install http://forum.xda-developers.com/showthread.php?t=3577875
It's the F2FS bug prevention add on for Magisk (>=15.3)

nicolap8 said:
You must install http://forum.xda-developers.com/showthread.php?t=3577875
It's the F2FS bug prevention add on for Magisk (>=15.3)
Click to expand...
Click to collapse
I've just tried this and after flashing in TWRP I get the same errors

nicolap8 said:
You must install http://forum.xda-developers.com/showthread.php?t=3577875
It's the F2FS bug prevention add on for Magisk (>=15.3)
Click to expand...
Click to collapse
It worked perfectly with me.

[2020]Replace KingRoot v5.x or Kingo ROOT with SuperSU

This is for those who are unable to uninstall Newer KingRoot using old Methods like SuperSUMe Free and old terminal emulator method by Mr.W0lf and waiting to uninstall Newer Kingroot versions.... or want to remove Kingo ROOT in a simple way.
Features:-
-Removes Kingroot v5.x (tested on latest v5.3.7-197), Kingo ROOT
-Removes all files of King(o)root in whole device
-Installs SuperSU-v2.82-SR5 to /system without custom-recovery and force system even on 6.0+
-No need of manual updating of su binary
-Installs latest Busybox to /system/xbin
Requirements:-
==> Terminal Emulator
==> Below attached ZIP
Procedure:-
To uninstall completely the script deletes files multiple times.
Optionally Untick KingRoot in Settings App->Security->Device administrators->KingRoot
Method 1:-
1.Make a folder with name mrw in internal storage
Extract this zip in that mrw folder
2.Download Terminal Emulator and run following commands
Bash:
su
sh /sdcard/mrw/root.sh
3.After succeeded with Green text type following
Bash:
sh /sdcard/mrw/root.sh
After this, your device will reboot by installing SuperSU
If your device not rebooted, then try executing root.sh for 5 times...
If still not rebooted then try other method
4.After booted open Terminal Emulator app and type following
Bash:
su
sh /sdcard/mrw/root.sh
Method 2 :- by uninstalling KingRoot manually
Root again with KingRoot
and follow below procedure
1.Type
Bash:
su
in Terminal Emulator and go to KingRoot app
Tap on 3 dot and
choose settings and
choose remove root, untick keep backup option and unroot
Note:- If your device rebooted at time of unrooting, this method will not work
2.Go to Terminal Emulator and type following
Bash:
sh /sdcard/mrw/root.sh
Your device will reboot after that and rooted with SuperSU
Method 3 :- by using older version of KingRoot
Requires :- Android Version less than 5.0
1.Unintall Kingroot by going to KingRoot app
Tap on 3 dot and
choose settings and
choose remove root, tick keep backup option and unroot
2.Install older version of KingRoot eg v4.5.0 from apkmirror
and root with it
3.Follow Method 1
Method 4 :- by using Kingo ROOT instead of KingRoot
1. Probably your device will lose root of KingRoot after following above methods, so root your device with Kingo ROOT.
2.Follow Method 1
Method 5 :- by using Magisk Manager
Requires :- 1)Android Version greter than or equal to 5.0
2)Unlocked bootloader (else your device will soft brick)
1.Reroot with KingRoot
2.Install Magisk Manager
install Magisk by connecting to internet
and tap on install option
and choose Direct Install(Recommended)
3.Go to Terminal Emulator and type following
Bash:
su
and go to Kingroot app
4.Uninstall Kingroot as said in Method 2
5.Go to Terminal Emulator and type following
Bash:
sh /sdcard/mrw/root.sh
reboot your mobile, after reboot
Bash:
su
sh /sdcard/mrw/root.sh
Method 6 :- by using SuperSU Me pro
If replacing Kingroot with SuperSU method from above doesn't work for you
You can try SuperSU Me by @gatesjunior
Which will remove all Kingroot apps installed in your device
Download and install Super-Sume Pro apps
Forum link: http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Thats it...!
Thanks to @Mr.W0lf for this
If you want to create issue or suggest file edit through pull requests
Source:- https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU
SHA1 of v5.zip:- 5cb2508180a4edc12316acfd4cb0fb59ad4dd402
Donate:- https://www.paypal.me/hemanthjabalpuri
Enjoy !

Test zip for testers:-https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/archive/master.zip
Testers:-
People who has custom recovery and know some basic things about restoring nandroid backup and get out of soft brick can test by following procedure....
-Root with SuperSU by flashing super.zip in recovery....
-Go to settings of SuperSU and choose switch super user and reboot...
-Install latest Kingroot.apk from apkmirror....
-Install and select fix now below Root Auth Error
It will root with Kingroot...
Test the zip by following procedure in first post....
Send the root.log in /sdcard/mrw folder... by making a post in this thread
Developers:-
For app devlopers who want to make this as an app can see some source examples from
==> https://github.com/inX95/RmKingroot
==> https://github.com/EliteTutorials/Open-King-Remover

Kingroot FAQ:-
https://forum.xda-developers.com/an...ot-tool-android-2-x-5-0-t3107461/post60829420
All questions about SuperSU:-
https://forum.xda-developers.com/an...ot-tool-android-2-x-5-0-t3107461/post61857510
What are another easy ways to replace?
Note:- Need unlocked bootloader
-Search Custom Recovery(TWRP, CWM, PhilZ , etc) for your particular mobile
-Flash that recovery.img with app like Flashify, Rashr, Kernel Adiutor, ROM Installer, Root Essentials etc
-Boot into custom recovery and Flash SuperSU.zip or Magisk.zip
-Reboot and Enjoy.....
All about ROOTING
How to Root Any Device
How to Root Your Android
Best One Click Root Methods
Best Root Apps for Android
Best Apps for Rooted Android Devices
How to do Everything on Your Phone
XDA’s Top Picks for Everything

Older Versions:-
v4:- Changelog, Source ZIP
v3:-Changelog, Source ZIP
v2:- Changelog, Source ZIP
v1:- Initial, Source ZIP

Who use Kingoroot or superSU in 2019 just use magisk more simple and more efficiency...
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

black_file said:
Who use Kingoroot or superSU in 2019 just use magisk more simple and more efficiency...
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Click to expand...
Click to collapse
Yes, but many old devices does not have custom recoveries and also many people who use those devices does not have a PC to flash patched boot.img... and also some devices does not have firmware available too....
Many device's bootloader also locked...
If we install magisk then it will definitely soft brick..
since on a bootloader locked mobile tweaking recovery or boot partition will get result like brick
Thats why some people stick with King(o) root.....

Terminal Emulator app is another app or its BusyBox?

AndroPhobia said:
Terminal Emulator app is another app or its BusyBox?
Click to expand...
Click to collapse
Another app

Should i install busy box in xbin or bin?

AndroPhobia said:
Should i install busy box in xbin or bin?
Click to expand...
Click to collapse
Both of them will work

Done Twice and worked in a M4 SS4452 Android 5.1.1
Thanks

AndroPhobia said:
Done Twice and worked in a M4 SS4452 Android 5.1.1
Thanks
Click to expand...
Click to collapse
Hey thanks
I made a test branch in github for advanced users which contain 4 methods of replacing root and also contain Magisk flashing...
https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/archive/v3-Magisk.zip
at https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/tree/test

Older Versions:-
are available in 4th post

Updated to v4
Changes:-
-Replaced with Stericson 1.30.1 Busybox
-Fixed Arch Detection
-Try to fix force closes of KingRoot when removing by installing older version of KingRoot(v4.5.0)
-Fixed 64bit devices not rebooting after replace
-Removes debuggerd too
-More logging info
Full Changelog here
This update is NOT tested...
If you are tester not having KingRoot installed then see 2nd post for info..

Update v5-test:-
This update does not have any zip.
All the files are embedded in script file.
Just place root.sh somewhere and execute.
Those files are extracted at the time of usage in execution.
If you want to extract only files to see what are they, then execute
Code:
root.sh -x all
will extract files in working directory.
https://www.mediafire.com/file/9ir3fzipfsouimm/root.sh
If you are a tester and want to test this, then see 2nd post for details.

Anyone tried any of this on OnePlus 6T (A6013)?

I'd like to say thank you it works on my BOOX Max Carta, Android 4.4.4

fishman8 said:
I'd like to say thank you it works on my BOOX Max Carta, Android 4.4.4
Click to expand...
Click to collapse
Can you please telegram me at
https://t.me/HemanthJabalpuri
Thanks

Thanks worked for my Z1 Compact at Android 5.1.1.

it is not working well as I found