Database Users

[Auto ToolKit][BL Unlock][Magisk&SuperSU][Xposed] Zenfone 2 ToolKit [Z00A/Z008/Z00X]

Last update: 14.10.2017
Fantastic news
No more waiting for manually signed magisk, supersu or twrp versions from now on. Just install any new version and use the image signature fix action in the troubleshoot menu of the toolkit. :good:
Next level reached
No more waiting for special zenfone 2 patched xposed for magisk. Got my own zip to do some hex patching. You can either use one of the (already patched) xposed versions from the toolkit or download xposed for magisk and use the xposed patcher in the troubleshoot menu.
z00x users please read this post https://forum.xda-developers.com/showpost.php?p=72298931&postcount=214
Introduction
This is a windows batch toolkit for automated actions like bl unlock, flash, root, xposed, sideload tasks, ... for your ze551ml/ze550ml/zx551ml.
I hope you find it useful. Check the tabs above for more screenshots, downloads, review ...
Note:
This tookit works well for a lot of situations, but I need feedback especially for the new supported devices ze550ml and zx551ml. Please go on and try the toolkit, then leave a message on this thread, do a review or just vote.
Before you try any action in the menu, check that the device informations are shown.
Features
​
Supports ZE551ML, ZE550ML, ZX551ML
​
Device status and connection information
​
Automated actions
​
Bootloader unlock
​
Flash boot/recovery images (twrp, stock)
​
Fix wrong or missing image signatures!!
​
Root / unroot Magisk & SuperSU
​
Xposed for Magisk (install / uninstall)
​
Patching xposed for magisk for zenfone 2 (if installed the unpatched xposed for magisk by mistake)
​
Compatible with most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
Currently integrated Tools
​
v14.0 (default) and v14.2
​
SuperSU 2.79SR3 / 2.82 (default) / 2.82SR5
​
TWRP 3.0.3-M4 / 3.1.1 (default)
​
Xposed for Magisk v87.3 / v88.0 (default)
​
Stock boot/recovery support of most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
​
adb/fastboot 1.0.32 (optional: 1.0.36)
Installation instructions
Do a clean start:
​
Download the latest base package
​
Extract to your desired location. It will extract a "ze551ml toolkit" directory with all files.
​
(Optional / If the automatic download of the device specific files fails) Download the device specific packages and extract it directly to the "ressources" directory
To run the toolkit just execute "ze551ml toolkit.bat" (no admin rights are needed).
Usage instructions
Prerequisite:
​
Ensure that you have installed device usb drivers (e. g. see: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/ )
​
Ensure that you have one of the latest MM firmwares for your device installed.
​
Ensure that you have enabled USB Debugging in Developer Options
​
Even if only a few actions could be really harmful to your data: Get a backup!
Then:
​
Run ze551ml_toolkit.bat
​
Check device status information & see if toolkit really likes your device
​
If your bootloader is still locked: Unlock it first with menu B -> choice U
​
(Optional) Choose your desired versions of the integrated tools in menu O.
​
(Recommended) Flash twrp with menu F -> choice T. If you want to try a newer twrp version, change it first in menu O
​
Check all the other nice functions of the toolkit
Downloads
Main: xda devdb archive
Mirror 1: https://mega.nz/#F!u8JhhY7T!9PryiRdjVSFf-O4erijDWg
Mirror 2: https://drive.google.com/drive/folders/0B4r2bJ3AgndSRVl5djNPNV9Qbkk?resourcekey=0-i9dHUezdzckVemi93NlYLA&usp=sharing
File structure:
​
ze551ml-toolkit-<VERSION>-base.zip - contains the base toolkit package without any device specific files
​
z00a*.zip - contains all device specific files for Z00A (ZE551ML)
​
z008*.zip - contains all device specific files for Z008 (ZE550ML)
​
z00x*.zip - contains all device specific files for Z00X (ZX551ML)
Changelog
Code:
[B]v1.3[/B]
Current changelog: 14.10.2017
[added] xposed for magisk v88.0
[new] Patching xposed for magisk for zenfone 2 (if installed the unpatched version by mistake)
Code:
[B]v1.22[/B]
Current changelog: 08.10.2017
[added] magisk v14.2
[removed] magisk v13.3
[fixed] xposed for magisk v87.3
[new] Fix wrong or missing image signatures!!
[fixed] Better support for encrypted devices
Code:
[B]v1.1b9[/B]
Current changelog: 22.09.2017
[added] magisk v14.0
[removed] magisk <v13.3
[removed] twrp 3.0.2-M1
[updated] magisk uninstaller
Code:
[B]v1.1b8[/B]
Current changelog: 19.07.2017
[added] magisk v13.3
[updated] magisk uninstaller
[new] action to download latest mirror file which is used to get some stock files updates
Code:
[B]v1.1b6[/B]
Current changelog: 13.07.2017
[added] magisk v13.2
[removed] magisk v13.1
[fixed] twrp detection
[modified] magisk manager will now be extracted from zip and installation will be forced after sideload
Code:
[B]v1.1b5[/B]
Current changelog: 11.07.2017
[added] magisk v13.1
[removed] magisk v13 betas
[fixed] minor fixes in supersu actions
Code:
[B]v1.1b3[/B]
Current changelog: 02.07.2017
[added] 2 magisk v13 beta versions
[removed] magisk <v12
[updated] xposed installer
[added] 2 more twrp versions
[fixed] hardened detection of installed twrp version (still needs root or already booted twrp for that)
[fixed] changed the way the toolkit downloads files
Code:
[B]v1.0b10[/B]
Current changelog: 04.04.2017
[added] magisk v12.0
[updated] fixed some help messages
Code:
[B]v1.0b8[/B]
Current changelog: 21.03.2017
[added] support for more devices: z00a, z00d, z00x
[added] automatic download for device files if needed
[added] magisk v11.6
[added] twrp 3.0.3-M4 (for encrypted devices or android n installations
[added] backup efs function
[added] integrity check
[modified] menu structure
[updated] changed some help messages
Code:
[B]v1.0b2[/B]
Current changelog: 14.02.2017
[modified] menu order
[disabled] usage of system installed platform tools, internal are forced now
[fixed] boot2recovery could have been failed in some cases
[fixed] timing problems in wipe routine
[added] validations added to each boot states
[removed] twrp 3.0.3.2
[adjusted] code / function names
Code:
[B]v0.9[/B]
Current changelog: 07.02.2017
[added] new twrp 3.0.3.2
[added] new magisk v11.1
[disabled] second disclaimer
[disabled] bootloader status in device overview at the top as I haven't found a secure way to detect a locked/unlocked bootloader yet.
[removed] magisk v10.2
[removed] twrp 3.0.3-N
Code:
[B]v0.7[/B]
Current changelog: 02.02.2017
[added] boot to safe mode
[added] wipe menu
[added] new twrp 3.0.3-N and platform tools 1.0.3.6 (no default yet. versions can be switched in troubleshoot menu for testing)
Code:
[B]v0.5[/B]
Current changelog: 31.01.2017
[added] each action shows some information about what's going to happen now
[changed] each action must be confirmed to be executed. if you don't need that, enable auto-yes in troubleshoot menu
Code:
[B]v0.3p1[/B]
Changelog: 28.01.2017
[fixed] added missing magisk manager to installation procedure
Thanks to/Credits
Code:
:: > shakalaca
:: > chainfire
:: > topjohnwu
:: > twrp
:: > social-design-concepts
:: > phhusson
:: > say99
:: > Deathschythe33
:: > ggrandou
:: > gerasiov
You'll find more credits inside the source code.
I hope i didn't forget anyone. If so please report.
XDA:DevDB Information
Zenfone 2 ToolKit [Z00A/Z008/Z00X], Tool/Utility for the Asus ZenFone 2
Contributors
rummsbumms
Version Information
Status: Stable
Current Beta Version: 1.3
Beta Release Date: 2017-10-14
Created 2017-01-28
Last Updated 2018-07-31

Reserved

Reserved

What makes this different with @Giovix92's tool?

Yes, same question as above. What makes it different from ZE55xML_Modder by Giovix92

@krasCGQ @fred_gaou
i think that main difference is that this toolkit supports the last 3 MM firmware versions and works automatically for all tasks, so user interaction is reduced to wait & perhaps read

@rummsbumms
Question 1: would you suggest to run ze551ml_toolkit.bat as admin or not?
Question 2: did you personally test all root method provided by toolkit: SuperSU, Magisk+SuperSU, Magisk+phh superuser? Did you succeed to properly unroot all of them? Will you suggest one method rather than another?
Question 3: did you test custom ROM install via TWRP such as last LineageOS after unlock bootloader and install TWRP with your toolkit?
Question 4: What is "Auto Packages" supposed to mean? What does it do? According to script code, it seems to unroot and restore stock bootloader. That's why I don't understand the Auto Packages term.
====
To avoid having to get always the same questions like
How to root for the 1st time or safely upgrade firmware and root again…?
How to get back to a clean stock device?
What does this menu entry really do?
etc.
I would suggest some guide lines to help users in the 1st post as well as in a "how to.txt" file along the toolkit or in the batch itself as a menu entry named "Help" or "FAQ" or else.
====
FEATURES REQUEST
# Add FACTORY RESET DEVICE menu entry. This will imply:
Code:
fastboot erase userdata
fastboot erase cache
# Add Erase /system, /data and /cache menu entry, may be useful before installing a ROM. This will imply:
Code:
fastboot erase system (I guess it will work only if bootloader have been unlocked)
fastboot erase userdata
fastboot erase cache
or a complete wipe that will format the partitions too
Code:
fastboot -w
# Add a way to Back up and restore EFS, see this thread.
# And +1 to the post below about ifwi.
====
I would suggest also in the 1st post as well as in a "how to.txt" that the functions be more detailed. Example:
I see you chose to use adb/fastboot 1.0.32 version. Just to let you know that Minimal ADB and Fastboot v1.42 provide a more up to date adb and fastboot (the last 1.0.36). Why do you use this old 1.0.32 version?
====
I didn't test ZE55xML_Modder by Giovix92 or this toolkit yet, but just by reading the batch file, I can tell your code is way more elegant and skilled and should avoid the magisk root bug that ZE55xML_Modder users encounter.
====
And why checking if ADB is installed as system-wide since your toolkit already provides local adb/fasboot ? What's the point to add this "unnecessary" step ?
====
Great Work ! :good:
I will test your toolkit very soon and give feedback. I hope to get answers from you in the meantime.
Regards

What would be ideal , if possible to add
Is ..
An ifwi version detector
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs

@fred_gaou
You gave some nice questions&suggestions!
About your questions:
You don't need the batch to run as admin as I don't use any function that needs admin rights.
Yes, I've tested all root functions and switched between single supersu, magisk with phh and magisk with supersu, but of course always with running the unroot task first. my personal favorite is magisk with phh b/c of the magisk hide. that's what i need for some banking apps :angel:
Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
The other points:
Giving more guidelines/hints in this thread&toolkit is a good point. I'll try to add this as soon as possible. :good:
Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.

timbernot said:
What would be ideal , if possible to add
Is ..
An ifwi version detector
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs
Click to expand...
Click to collapse
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.

Hi,
I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?
I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM

rummsbumms said:
Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
Click to expand...
Click to collapse
Well, I'm still on stock LP so I would not be a good adviser. I trust the experienced users that switch and update ROM weekly so they will give useful feedback soon. Since some guys on LineageOS used Giovix modder to unlock bootloader and install ROM via TWRP, I guess it's currently the way to go.
rummsbumms said:
The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
Click to expand...
Click to collapse
I get it now. It could be a useful section in future to run sequential commands at once.
rummsbumms said:
Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
Click to expand...
Click to collapse
Yes it is wise. I just provided the command because it was implemented in Giovix Modder and often reported as a way to clean up before flash all stock in other device. Don't know for 551.
rummsbumms said:
I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.
Click to expand...
Click to collapse
Detail is good to know. What OS do you use: 7, 8.1 or 10? If 1.0.32 works fine on every version, there is no point to risk to break anything using 1.0.36.
Thanks for your answers.

rummsbumms said:
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.
Click to expand...
Click to collapse
Thinking about it now a bit more , it maybe tail end for this problem .
The actual problem people were having was they thought they had cm13 with M BL , actually they had the LP bootloader cm13 . They would be in a working system then flash 14.1 / 7.1 builds then , brick their devices .
They forget they never upgraded bootloader and with having 6.0.1 M in build information in settings, presumed they had upgraded bootloader at some point but didn't .
Maybe , to prevent the tail enders from performing such tasks again , maybe a simple addition like a warning , like build date which in cm 13 , to check.. if before July 2016 and have IFWI version 0094.0173 unlocked . Then you could direct them to say a return to stock option , flashing back boot and recovery for say on 551 LP 2 20 40 .196 Version , then possibly install the full ROM from say a link or something like ...Then info to upgrade to stock M before returning back to tool to unlock updated to the latest M.
But like mentioned , we maybe at the tail end of this problem.
Probably related to 95% of the bricking threads here for zenfone.
Anyway thanks for taking interest

Deathschythe33 said:
Hi,
I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?
I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM
Click to expand...
Click to collapse
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.
Is your bootloader still locked?

Thank you so much for your awesome ToolKit, works flawlessly !!
<3

v0.5 is out

rummsbumms said:
v0.5 is out
Click to expand...
Click to collapse
thanks, can you simply make 3 downloads complete for the 3 mm versions? now is a bit confusing with this updating/base files.
I don't think that 80mb would be a problem to download, everyone have at least a dsl line, we are not talking of gbs, thanks

v0.7 is out
@fred_gaou: I've tested with win10. 1.0.3.2 works fine and will be default, but I've added 1.0.3.6 too. perhaps someone could test on other machines as i still have problems using it and don't know whats the problem.
@holymoz: I've made a additional "full" package which contains all files. the "base" version still only contains the latest mm firmware files.
@timbernot: Still thinking about it. Maybe some kind of decision tree asking for the problem could lead the user to an action that could cure the problem. I'll keep it on my todo list.

V0.5 works okay on my device with win 10 . i will test later the new build thanks

rummsbumms said:
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.
Is your bootloader still locked?
Click to expand...
Click to collapse
Hello @rummsbumms,
Thank you for taking your time to respond. Yup, my phone's bootloader is still locked. Everything in this phone is "official" including the freaking official bloatwares. I love the HW specs of this phone, but the bloatwares are F***ing crazy!

[OFFICIAL] OxygenOS Open Beta 19 for OnePlus 3T (Android O)

Hey everyone,
Back again with some new builds for you all to play with.
Please fill out our survey on UX & UI here:
https://goo.gl/forms/iroOfnsOv080FNnb2 .
Changelog:
Launcher
Optimized and enhanced application shortcut menu
Optimized shelf visual style
Gallery
Add a photo map to view photos by location
UI enhancements and other optimizations
Contacts
Added emergency information (ICE) to your personal information
System
Wireless hotspot management optimizations
Support for aptX/aptX HD
UI fixes for Quick Settings
Fixed slow charging issues
Optimized Wi-Fi performance and security
Optimized battery usage statistics
Updated Android Security Patch
Other bug fixes and optimizations
Known issues:
Sometimes the long press will not activate on the home screen. If you encounter this issue, please make sure to report the issue, and then restart your phone. The issue should then be gone.
Notice
If you want to revert back to the last Open Beta N build (OnePlus 3 Open beta 24 or OnePlus 3T Open Beta 15) you will need to flash the special build provided below. Because of the nature of downgrading from a major version, this will cause you to lose partial data.
Instructions and Info:
The build will wipe app and cache data, but Internal Storage will be saved (ie: pictures and files)
Users who revert their device back to the special build can still OTA update the device to Android O build at a later date.
Steps to revert:
Download special build
Copy to Internal storage
Reboot to recovery Mode to install
Choose “Install from Local”
Choose the downloaded build to install
Special builds for latest Android N Open Beta builds(S3 Link):
OnePlus 3 OBT 24: http://oneplusroms.s3.amazonaws.com...331527&Signature=To19RC9ggWaciPH4zT5CUyapN68=
OnePlus 3T OBT 15: http://oneplusroms.s3.amazonaws.com...337224&Signature=BEA4IHd/rVFqoPd2gh7EvwaoSeg=
Please keep in mind that this is beta software. These builds are sometime not as stable as our official OTAs generally are. By installing this update, you accept the potential risks.
And please remember to tell us about any bugs you may find using the bug report forums, found here. https://forums.oneplus.net/feedback/
Please note:
If you have already flashed an Open Beta (you are currently running the latest Open Beta) you will receive this new build as an OTA. If you ARE NOT running open beta software and would like to, please refer to the flashing instructions and the full ROM found in the downloads page here: http://downloads.oneplus.net/
Once you migrate to the Beta path, you will continue to receive Open Beta OTAs. You will NO LONGER receive the regular Official Stable OTAs.
Moving back to the Official OTA path from the Beta path will require a full install and clean flash (FULL WIPE of all data and cache)
Make sure to let us know how you feel about the beta builds here too, we are watching.
Never Settle :fingers-crossed:
>>>> Confused on How to take logs, look here

Everyone is invited to join my Telegram Group for the latest updates:
https://telegram.me/OnePlusHub
Downloads:
Open Beta 19: Official
Blu_Spark TWRP
Stock Recovery: Official Server
SuperSU Or Magisk
Installation: Stock or Custom Recovery :fingers-crossed:
Stock Recovery:
Download Full Beta 16 Zip and place it on internal
Reboot to Stock OOS Revovery
Wipe Cache
Select ROM Zip to Flash from internal
Wipe Cache
Reboot to OS
Custom Recovery | TWRP Users :good:
Needed Oreo Compatible TWRP
Download Full Beta 16 Zip and place it on internal
Reboot to compatible TWRP
Wipe Dalvik , System, Data & Cache (Clean Flash coming from Custom ROM) | Wipe Dalvik & Cache (Dirty Flash from Previous OOS ROM)
Select ROM Zip and Swipe to Flash
Flash SuperSU
Wipe Dalvik & Cache
Reboot to OS :fingers-crossed:
If you get DM Verity:
Downloads:
Firmware OOS 4.0.2
Reboot to TWRP
Flash 4.0.2 Firmware
Reboot to bootloader and connect your phone to your PC and execute the below commands in command prompt:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Reboot to TWRP
Flash Firmware of your current OOS version or Dirty Flash Full Zip
Reboot System :fingers-crossed:

Funk Wizard said:
Hi All,
As the update for Hydrogen OS 7.1.1 is released its just a matter or time OOS gets the same
Source: http://www.oneplusbbs.com/forum.php?mod=viewthread&tid=3257661&extra=page=1&filter=typeid&typeid=114
Download Hydrogen OS based on 7.1: http://www.h2os.com/download
I will update the thread once the build is released as its under testing as we speak :fingers-crossed:
Click to expand...
Click to collapse
:good:

even i tried to flash but couldnt get Google play store and stuff any luck

Waiting eagerly for OOS 7.1.1 @Funk Wizard

Thanks for the update
Sent from my ONEPLUS A3010

is there any round icon support?

t-shock said:
is there any round icon support?
Click to expand...
Click to collapse
I am not sure if you mean to check if OOS has a built in round icon theme but as far as i am aware the answer is not yet.

Complete video guide Installation / GOOGLE play services .
https://youtu.be/krpcM7isdlE

Nice,
Thanks OnePlus.

Dhairya said:
even i tried to flash but couldnt get Google play store and stuff any luck
Click to expand...
Click to collapse
Even H2OS has built-in Google Play Service. It just has been disabled and hidden by default. You can install Google Play Store or any GApp which requires google account and sign in. The full framework will enable automatically.

12.3 for oos? Why get china first?

Schrotty35 said:
12.3 for oos? Why get china first?
Click to expand...
Click to collapse
Well, One Plus are a Chinese company!

B3501 said:
Well, One Plus are a Chinese company!
Click to expand...
Click to collapse
Yes but this sucks.

I just hope ee will not have to wait month for them to release kernel sources...

Bring it on

Any clue if this can be dirty flashed over default?
Just too lazy to reinstall everything.

How i can change the number of title in notification pannel ?

maddler said:
Any clue if this can be dirty flashed over default?
Just too lazy to reinstall everything.
Click to expand...
Click to collapse
Hehe..Is not even released yet

cultofluna said:
Hehe..Is not even released yet
Click to expand...
Click to collapse
LOL! Wrong thread!!!
Thanks anyway

[ROM+KERNEL+TWRP][Ticwatch Pro(Catfish)(Catshark-4G)]+[Ticwatch C2(Skipjack)[9Aug20]

-[Ticwatch Pro 4G/LTE (EU) (Catshark)-PWDD.190617.059]-[30-5-2020]
- [Ticwatch Pro 2020 (Catfish-Ext)-PMP2.191203.001]-[22-6-2020]
- [Ticwatch Pro (Catfish)-PWDD.190617.074]-[09-8-2020]
#############################
- [Ticwatch Pro 4G/LTE (USA) (Catshark)-PWDD.190617.032]-[DISCONTINUED]-
-[Ticwatch C2 (Skipjack)-PWDS.190618.001.B4]-[DISCONTINUED]
-[Ticwatch E2 (Tunny)-PWDS.190618.001.B3]-[DISCONTINUED]
#############################
Code:
****Disclaimer****
[COLOR="Red"][B]WARNING: IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS. I accepts no responsibility for any damage to your device. Please read the instructions and notes before flashing anything[/B][/COLOR]
IF YOU LIKE MY WORK AND WANT TO BUY ME A COFFEE
DONATE-ME-HERE​
###################
REQUIREMENTS
###################
- Ticwatch Pro, Ticwatch Pro 4G, Ticwatch Pro 2020 Ticwatch C2 and Ticwatch E2 ONLY INTERNATIONAL VERSION. It may also work on Chinese version too but I haven't test it personally.
- An unlock bootloader, working driver and working adb/fastboot
- You can download ADB/FASTBOOT from here Download: ADB/FASTBOOT
- Custom recovery TWRP- (Se download section below)
###################
HOW TO FLASH- STEPS
###################
(FOLLOW EITHER THE INSTRUCTIONS FROM MEGA FOLDER OR THE STEPS BELOW)
- Download the latest ROM, latest vendor, latest Magisk and busybox - (Everything are include in the MEGA folder)
- Attach your watch to your PC and enable USB Debugging from settings menu. Ensure adb/fastboot is working. Please Google and see "how to enable debugging from settings menu".
- Extract the vendor folder and go inside the folder (Here you will find vendor.img and twrp.img + other files)
(You have to flash the vendor image and format userdata and cache)
- Boot your watch into fastboot/bootloader mode by applying the following code.
Code:
- adb devices
- adb reboot bootloader
- fastboot flash vendor vendor.img
- fastboot format userdata OR fastboot erase userdata
- fastboot format cache OR fastboot erase cache
- fastboot boot NAME-OF-THE-TWRP.img (Se the name of the twrp.img)
- Now move the ROM, Magisk and busybox to your watch.
- Flash the ROM and reboot. If you prefer root then
- Flash busybox and finally Magisk (IMPORTANT flash ROM, then Busybox and Magisk in this order)
NOTE
- When rebooting your watch, IF a Prompt come up and asking about installing twrp bla.bla then un-mark both lines/ then click on DO Not Install
- Let your device boot up, then connect your watch to your phone and finish the initial setting
- Open Magisk Manager and go to settings and set Automatic Response to Grant, Uncheck updates and Superuser notifications to None
- Reboot and enjoy
###################
ROM AND KERNEL FEATURES-
See latest changelog here
###################
DOWNLOAD
[DECRYPTION KEY]
Code:
iZbWXMs8vabDW1szJz1hgg
OPTIONAL
TO INSTALL KERNEL CONTROL APP WEAR OS
Code:
- Download the KernelAudiutor4Wear.apk from above link and move it to your adb folder.
- adb devices
- adb install KernelAudiutor4Wear.apk
MAGISK/BUSYBOX/APP-KERNEL-CONTROL
DOWNLOAD LATEST MAGISK FROM HERE
DOWNLOAD LATEST BUSYBOX FROM HERE
KERNEL CONTROL APP WEAR OS
###################
BACK TO STOCK ROM
See Mega folder for Stock images
Code:
[[B]DECRYPTION KEY[/B]]
iZbWXMs8vabDW1szJz1hgg
[B][SIZE="4"]STEPS[/SIZE][/B]
- fastboot flash aboot aboot.img
- fastboot flash boot boot.img
- fastboot flash recovery recovery.img
- fastboot flash vendor vendor.img
- fastboot flash system system.img
- fastboot format userdata OR fastboot erase userdata
- fastboot format cache OR fastboot erase cache
- fastboot reboot
##############################
Source/GitHub
##############################
-Source
-Source
-Source
###################
IF YOU LIKE MY WORK AND WANT TO BUY ME A COFFEE
DONATE-ME-HERE
###################
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Maxr1998 Big thanks for giving me knowledge and your great work for Asus Zenwatch_3 and your great github guide.
@topjohnwu for his great effort (Magisk)Thank you so much
@SuperR.R for the great kitchen
@YashdSaraf for the busybox (I edit a bit to make it work for Ticwatch-pro)
Sultan Al Sawaf for his patch
Mobvoi, Google and Qualcomm for providing us the kernel source.
Please always support devs and others (soon).

/*
* Your warranty is now void.
* I am not responsible for bricked devices, bootloop and dead SD cards,
* YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Click to expand...
Click to collapse
Download : TWRP For Catshark 4G/LTE
Source Device Tree: Device Tree For Building TWRP
###############################
###############################
How to get the Gpay back...
1-https://pastebin.com/HKV7cj7H
2-https://forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3821013/page172
3-https://www.youtube.com/watch?v=UKxGfNxRjo4&t=320s
4-https://forum.xda-developers.com/showpost.php?p=79637148&postcount=1720
Be aware for this in future....19 April 2020
https://mobile.twitter.com/topjohnwu/status/1245956080779198464

Very happy! Really looking forward to.

waiting English rom for China version

janjan said:
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
DONATE ME HERE
DONATE-ME​Special thanks to:
If you can, donate and respect all the devs and enjoy
@Maxr1998 Big thanks for giving me knowledge and your great work for Asus Zenwatch_3 and your great github guide.
@topjohnwu for his great effort (Magisk)Thank you so much
@superR for the great kitchen
Ticwatch and Google for providing kernel source.
Please always support devs and others (soon).[/SIZE][/B]
Contributors
janjan, JANJAN
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Stable Release Date: 25/7/2018
Click to expand...
Click to collapse
Sorry, where do you take the original Kernel and ROM source code? I didn't find them.
Thanks in advance

vietdh said:
waiting English rom for China version
Click to expand...
Click to collapse
I wait too, and there are no references, the same the Chinese version.
Where references I burn from impatience
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
alucard_24 said:
Sorry, where do you take the original Kernel and ROM source code? I didn't find them.
Thanks in advance
Click to expand...
Click to collapse
We wait for the reference while they are absent

ready for up ROM

alucard_24 said:
Sorry, where do you take the original Kernel and ROM source code? I didn't find them.
Thanks in advance
Click to expand...
Click to collapse
3.18-oreowear-dr works fine.
tempter_alex said:
I wait too, and there are no references, the same the Chinese version.
Where references I burn from impatience
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
We wait for the reference while they are absent
Click to expand...
Click to collapse
Uploading soon.
vietdh said:
ready for up ROM
Click to expand...
Click to collapse
Hehe need to upload source and fix some issues first. Will be up soon.

janjan said:
3.18-oreowear-dr works fine.
Click to expand...
Click to collapse
So no official source code has been released by TicWatch.
Thanks

What is that? No firmware?

alucard_24 said:
So no official source code has been released by TicWatch.
Thanks
Click to expand...
Click to collapse
https://android.googlesource.com/kernel/msm.git/+/android-msm-catshark-3.18-oreo-wear-dr
have no idea why they call it catshark
tag project branch device
android-wear-8.0.0_r0.24 kernel/msm android-msm-catshark-3.18-oreo-wear-dr Catfish

janjan said:
https://android.googlesource.com/kernel/msm.git/+/android-msm-catshark-3.18-oreo-wear-dr
have no idea why they call it catshark
tag project branch device
android-wear-8.0.0_r0.24 kernel/msm android-msm-catshark-3.18-oreo-wear-dr Catfish
Click to expand...
Click to collapse
Thank you very much

Thanks for your rom,
and this is the wear os global version? Not the china vwersion?
I want a global version but I have a china version ticwatch pro

Have one of these being delivered soon. Things specific to the device (like dual screens) still will work?

jinhaihan said:
Thanks for your rom,
and this is the wear os global version? Not the china vwersion?
I want a global version but I have a china version ticwatch pro
Click to expand...
Click to collapse
Yes. Global version..based on stock imsges
3dux said:
Have one of these being delivered soon. Things specific to the device (like dual screens) still will work?
Click to expand...
Click to collapse
Yes. Everything is working. TWRP, Kernel and ROM. I am going to upload everything today. Working to get the source up and update my GitHub.

Can someone please help me in finding the steps to unlock the bootloader for TicWatch Pro Chinese version.

janjan said:
Yes. Global version..based on stock imsges
Yes. Everything is working. TWRP, Kernel and ROM. I am going to upload everything today. Working to get the source up and update my GitHub.
Click to expand...
Click to collapse
Hahaha it is perfect!! I will flash it in some days later, and If work fine I will donate
oh , can it get ota update?

manishsoni7689 said:
Can someone please help me in finding the steps to unlock the bootloader for TicWatch Pro Chinese version.
Click to expand...
Click to collapse
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you can skip this)

I am new to xda.
How do I download twrp and rom?
The links are broken to me.
I have a Ticwatch Pro Chinese version. I would like to flash a international ROM.

otto_naka said:
I am new to xda.
How do I download twrp and rom?
The links are broken to me.
I have a Ticwatch Pro Chinese version. I would like to flash a international ROM.
Click to expand...
Click to collapse
We wait, we wait. We wait for))))

[ROM][9][OFFICIAL] LineageOS 16.0 for P2

Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
If you are coming from LineageOS 15.1 with f2fs userdata, you need to format the userdata partition! Read the second post for more information.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on kuntao
Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want. Recommended nano package)
Required TWRP recovery
twrp-3.2.3-20190209-kuntao.img
Official root addon
LineageOS Extras
Changelog:
Changes for kuntao
Bug reports:
How to submit a bug report
LineageOS GitLab
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to LineageOS
XDA:DevDB Information
Official LineageOS 16.0 for P2, ROM for the Lenovo P2
Contributors
mikeioannina, highwaystar_ru
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Any version of stock 6.0. Recommended: P2a42_S251_171107_ROW
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-04-13
Last Updated 2019-06-17

Upgrade instructions from LineageOS 15.1
Lenovo used a very old version of f2fs which is incompatible with latest f2fs version of 3.18 kernel. In order to keep the device updated with the latest features, it was necessary to upgrade f2fs with the downside of existing users need to format the userdata partition. If you want to keep your userdata, follow these steps. Keep in mind any apps using the keystore will be broken and you will need to clear their app data and set them up from scratch. If you used ext4 for userdata, you can simply upgrade without any breakage.
If you want to keep and migrate your 15.1 data and internal storage contents (only on incoming official builds!):
1. backup userdata in your current TWRP and take an internal storage backup on your PC.
2. reboot to bootloader
3. fastboot flash recovery twrp-3.2.3-20190209-kuntao.img
4. reboot to recovery by holding vol up + vol down + home + power buttons
5. main menu -> wipe -> format data
6. main menu -> reboot -> reboot recovery
7. flash lineage zip (and gapps/whatever else you want)
8. restore userdata backup and internal storage backup
9. delete /data/system/locksettings.db, you will have to set your lockscreen protection again when it boots
If you want a completely clean install just skip steps 1, 8 and 9.
I tested this process and it worked coming from lineage-15.1 or stock ROM.

Yeah! Thaaaaaanks Mike!

Thanks dude . Love your work

Thanks a lot mike!

AWESOME! Thank you.

I can't find the official Lineage OS 16 file?

tanzeel.ahmed1306 said:
I can't find the official Lineage OS 16 file?
Click to expand...
Click to collapse
Incoming !!!

@mikeioannina
* deleted

M too cant find file Lineage OS 16
tanzeel.ahmed1306 said:
I can't find the official Lineage OS 16 file?
Click to expand...
Click to collapse
M too cant find file Lineage OS 16

Los 16.0 is replacing 15.1 so build will probably come tomorrow. I think.

At 8:00 UCT
So one hour and a half.
https://www.lineageoslog.com/build
https://www.lineageoslog.com/16.0/kuntao
Sorry! Unfortunately I was wrong.

So if I already have ext4 data partition I can simply install the new 16.0 update without having to migrate the data etc?
Do I need the new recovery too?

Normally the build of the images starts on sunday 8utc am, so 10am my time. we'll see ^^ thx mike!
@philje123 i will test it out, as soon as the rom is available. i am too on ext4 already, i am using the new twrp since february, even with the 15.1 build. i will try to simply upgrade from 15.1 to 16, so i don't have to reinstall all apps. i will write, if it was working for me.

philje123 said:
So if I already have ext4 data partition I can simply install the new 16.0 update without having to migrate the data etc?
Do I need the new recovery too?
Click to expand...
Click to collapse
Yes, you need new recovery, but flashing new recovery do NOT wipe your data. It contain a newest format of f2fs format. On TWRP page you have a guide, how to flash it step by step on your phone without meet do plug your phone to PC.

Thanks Mike waiting for awesome

Should we expect a build this sunday at 10 am european time ?

robbedoes007 said:
Should we expect a build this sunday at 10 am european time ?
Click to expand...
Click to collapse
I thing about 1 pm CEST (European Time)

I remember last year on presentation 15.1 it took a couple of days before we could download after announcement.
Mikes work is awesome. But his timing
But anyway, I'm looking forward for this rom and I thank all the developers :good:

i mean it depends, when the build for the 16 roms is starting everyday, but according to this site https://www.lineageoslog.com/build/scheduler we will get nightly builds, instead of weekly ones.
so that means, daily snapshots, like we had with 15.1 from july till november, before we only got one update a week. but no matter when, i am just happy that 16 is finally here ;D
no matter if we have to wait another day or not for the first build. but still - it's just amazing how much love the p2 gets. it is still one of the best, if not THE best device i've ever had. perfect performance for daily usage, even with slight gaming and i only need to charge my device once or twice a week. that's incredible! my device is now over 2 years old and my battery still lasts 4~6 days with one charge <3 best phone ever created hahahaha - and thx to people like mike, it is up to date too =) i hate lenovo as brand, when it comes to software updates, but the hardware is awesome, for that price tag...

[Aljeter] [03rd June 2019] TWRP 3.3.1-0 Moto G6 Play

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
PHP:
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Changelog For 3.3.1-0
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
Install Guide:
For non rooted and rooted phones
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Brain
Download https:// drive .google.com/file/d/1-1MQqE42zIoLnqbYx-JTRQtVtnIV85Rt/view?usp=sharing (Remove space)
Put phone into fastboot mode (hold vol down + power button)
Connect phone to PC
Open a command prompt where you have fastboot and the TWRP image file located
Type the following in command prompt:
PHP:
fastboot flash recovery twrp-3.3.1-0-aljater.img
Note: For Windows 10 users who use the powershell and not cmd
The command will become:
PHP:
./ fastboot flash recovery recovery.img
Note: Test if it works in the JETER variant (I do not have that device, I have the ALJETER variant)
XDA: DevDB Information
twrp, Tool/Utility for the Moto G6 Play (Aljeter)
Contributors
TWRP Team
Me
Version Information
Status: Stable
Stable Release Date: 2019-06-03
Created 2019-06-03
Last Updated 2019-06-03

So this will allow flashing of A/B roms?

kwiksi1ver said:
So this will allow flashing of A/B roms?
Click to expand...
Click to collapse
I am not bad Moto G6 Play as the Moto G6 only have a / Vendor type A partition, you can also install custom rom (GSI) from an image file.
In the same way, I will try to compile a TWRP that supports the partition / vendor as a defect so that a custom roms GSI installation can be performed from a zip file.

Thread cleaned!
Kanged work must be addressed by developer himself using the report button or contacting any Mod. Future public posts will be cleaned again and users will be addressed.
Thank you

Will this TWRP be available on unofficialtwrp.com/
Do you know if there will ever be a official TWRP for Moto G6 Play?
I ask because I have enough experience to follow guides, but not enough to be security smart, which is ironic as I want a custom ROM to move away from Googles spying and bloat.

DulfaGreyny said:
Will this TWRP be available on unofficialtwrp.com/
Do you know if there will ever be a official TWRP for Moto G6 Play?
I ask because I have enough experience to follow guides, but not enough to be security smart, which is ironic as I want a custom ROM to move away from Googles spying and bloat.
Click to expand...
Click to collapse
To install a Custom ROM you do not need an build official TWRP , because in my opinion the cell phone should go better with the 64bit architecture and thus the device would be more useful, but since currently there is no support for the device itself, you can try installing a GSI ROM, apparently everything works, in LineageOS 16 Moto Actions do not work.

Don't use this.. yes it works, because the developer made sure of it, but this isn't the developer,
This guy was kindly helped by the developer and then stole that developers work. Then turned around and posted it here, risking all of your devices since he has no clue about it, just for a little attention.
Nice guy right?

If it seems like he's talking gibberish, it's cause he is. He has no clue how any of this works. But yes an official is in the works. In the meantime, thank god this guys an idiot and didn't erase his footsteps, suck it Allan

Alan1231999 said:
To install a Custom ROM you do not need an build official TWRP , because in my opinion the cell phone should go better with the 64bit architecture and thus the device would be more useful, but since currently there is no support for the device itself, you can try installing a GSI ROM, apparently everything works, in LineageOS 16 Moto Actions do not work.
Click to expand...
Click to collapse
I have installed custom roms before and as starkiller2 pointed out you make no sense. My question was about the security and quality control of what you have offered -which for all I know could be invasive or broken. Hence I was seeking some kind of verification of legitimacy; which you have given me albeit the opposite of what you may have intended.
It appears that some concern is shared by starkiller2 -thanks

I maintain my stance that Allan can choke on it

Give a link to twrp 3.3.1 I can not download

bronislav808 said:
Give a link to twrp 3.3.1 I can not download
Click to expand...
Click to collapse
That's because it was stolen work bud.

Why is this thread even up? @mods

Kuntitled said:
Why is this thread even up? @mods
Click to expand...
Click to collapse
When I tried taking my first guide thread down a mod told me they don't remove posts for archival purposes or something like that. Might be different though for the situation involved with this thread though

Kuntitled said:
Why is this thread even up? @mods
Click to expand...
Click to collapse
The mods were supposedly "investigating" it but never did anything. And Allan's ***** ass disappeared