Related
This guide is outdated now. Please refer to the thread OPs of the respective projects.
Hi all, I am starting this thread with the very reason to educate and help newbies as well serve as a resource guide that could be used by all. I will try my best to update this thread often. You can ask any question regarding Moto Z2 Play aka albus here. Our XDA Community will try to help you. Make sure you always read before posting the same queries. If you're stuck in a problem, make sure you provide us with as much as information of what you were exactly doing and what happened along with your device details ofcourse.
Also remember that unlocking the bootloader will void your warranty. Relocking it won't give you back your warranty. If you are visiting a service center for repairs of any kind, they will come to know that you have unlocked your bootloader (you put a code on their site lol). But yea you can try your luck by visiting them after you lock your bootloader using the fastboot firmware.
No one, but you are responsible for whatever you do to your device. If something happens due to your ignorance or lack of backups or knowledge, only you are responsible, not the developer, not the XDA Community. Just read the respective posts, search (at XDA and at Google) before posting and you might probably find answers. Cheers.
Setting up adb/fastboot on your system:
These drivers are quite essential for every android user.
How to use?
Windows:
Minimal Fastboot/ADB: https://www.androidfilehost.com/?fid=745425885120698566
Just install the setup. Reboot your phone in bootloader mode (Power off and then press and hold power + vol down simultaneously) and connect via USB cable. On your computer, navigate to the directory where you installed them. Press shift+right click and choose Open Command Window / Powershell here. Type:
Code:
fastboot devices
If you get a serial number, fastboot is working.
For adb to work enable Developer Options and turn on USB Debugging on your device. Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Now authorize USB Debugging by allowing it (Choose something like Always trust)
Type this on your command window / powershell window:
Code:
adb devices
Again it should return a serial number.
If both these fail, you might consider rebooting your computer or even installing (MDM) motorola device manager. Make sure you don't have any crappy or outdated drivers. (Always keep your system upto date ) Anything else, you'll have to google up things.
Motorola Device Manager:
For more info regarding adb/fastboot open this: https://developer.android.com/studio/command-line/adb.html
Linux users might need to install it from their respective package manager repos, Ubuntu for example:
Code:
sudo apt install android-tools-adb && sudo apt install android-tools-fastboot
Arch Linux on the other hand:
Code:
yaourt -S android-tools --noconfirm
Similarly for the other distros.
Commands are the same. fastboot needs to be used with sudo.
Unlocking the bootloader:
Unlocking Bootloader
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
Unlocking Bootloader:
1- Register
Head to Motorola website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and register your E-Mail ID.
Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Head back to Main Settings Menu and go to Developer Options and switch the 'Allow OEM Unlock' option.
2- Getting Unique ID for each device
Reboot to Bootloader/fastboot mode (power off the device, then press the power and volume down buttons simultaneously).
On your computer, go to the directory where you installed the adb/fastboot drivers (or make sure this folder is in your $PATH to acess fastboot and adb system wide).
Open CMD/Powershell/bash in here. (Windows users might need to Shift+Right Click and choose "Open Command/Powershell Window here" , Linux users can open terminal as per their respective distro. Now , type
Code:
Code:
fastboot oem get_unlock_data
You will get something like this:
On a Windows Desktop, the returned string format would be:
Code:
(bootloader) 0240540162024205#4C4D3556313230
(bootloader) 30373as313630330df332323239#BD00
(bootloader) 8A672BA4746C2CE0a328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0240540162024205#4C4D355631323030373as313630330df332323239#BD008A672BA4746C2CE0a328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlocking the device:
Check if your device can be unlocked by pasting this string in the specific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page. Click on it and wait for the unique code to be sent to your mail.
After you got the code type the following :
Code:
fastboot oem unlock your_code
and wait your device to reboot !
Flashing TWRP Recovery:
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to format data once via twrp wipe options and reboot back to twrp for functioning of /data
Downloads : http://www.androiddevs.net/downloads/
Keep the twrp recovery file (.img extension) in the adb/fastboot folder
Reboot to bootloader, open cmd/bash and type:
Code:
fastboot flash recovery filename.img
(if you want permanent flash) or
Code:
fastboot boot filename.img
(if you want temporary
boot)
Now you must flash the verity disabler zip.
HIGHLY RECOMMENDED:
After the twrp is done and you have successfully rebooted to system, it is a good time to reboot to TWRP again and backup your phone. (System and Boot most necessary)
Flashing Stock ROM:
Will be updated as soon as the fastboot version of the stock ROM is available.
Unbricking your hard bricked/dead device:
Connect your device via the usb cable, extract this zip file to the adb/fastboot folder and then run:
blankflash.bat file if on windows; the .sh file if on linux.
Once this is completed, you must flash the full stock firmware via fastboot. This is MANDATORY.
Blankflash zip: http://cloud.vache-android.com/Moto/albus/blankflash/blankflash.zip
Reserved
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
OneArm said:
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
Click to expand...
Click to collapse
Yeah, I am not sure what is going on this time around with the VZW variant. Since the Droid Z was bootloader locked and the unlocked Z wasn't (but not VZW compatible) I am almost expecting the same here, but I keep being told that the unlocked version of the Z2 will work on Verizon so maybe they just don't care anymore. I mean, the unlocked Nexus 6 and VZW Nexus 6 were pretty much the same phone too, and both were bootloader unlockable.
The only thing that gives me pause from going out now and getting the VZW version vs the unlocked model (whenever its slated to come out) is that Motorola's Bootloader Unlock page doesn't have it listed (yet). Either it can be and they are behind on updating the list, or it can't... at which point the unlocked one will be listed with a (Except VZW Model) like the other phones have. But... if either version works on VZW... what's the point of making one unlockable and the other not? Seems like a waste of time.... of course VZW's past decisions on phones don't make sense in some aspects.
All I know is... I want one of these if they are unlocked. Once the keyboard mod is released I will be back to the nerdy bliss that is a sliding keyboard and making this phone the spiritual successor to the Droid 4.
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
---------- Post added at 06:05 PM ---------- Previous post was at 05:46 PM ----------
After installing TWRP it asked for the encryption password so I put it and it opened normal I went to restart> system, then appeared option to install the application twrp, I slipped it to be installed, then went on reboot> system and stopped on the screen Of bootloader unlocked .. help me: |
m.lucas said:
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
Click to expand...
Click to collapse
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
how should I proceed? My device has no ROM only TWRP installed. :s
m.lucas said:
how should I proceed? My device has no ROM only TWRP installed. :s
Click to expand...
Click to collapse
Start TWRP, and you can transfer zip file from PC by using "adb push"
"adb sideload" may work too.
yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Junior Passos said:
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
yunzo said:
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
Click to expand...
Click to collapse
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
tywinlannister7 said:
Reserved
Click to expand...
Click to collapse
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
@niteshpant kindly edit your post and remove the reserved post from the quote.
Moreover, the links will be added here as soon as the firmware is available.
Junior Passos said:
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Click to expand...
Click to collapse
As I wrote before, I have failed both of 54e6a79 and latest.
Error message on TWRP is same.
Have you met this message but rooted successfully after boot?
Today I tried system-mode SuperSU, and met boot failure which continues to show Motorola/lenovo logo.
It is different from dm-Verity failure (which shows unlock warning).
Stuck in TWRP, Help
I have successfully flashed the TWRP but now it is looping at TWRP and when try to do factory reset, in just seconds it is boot again and shows TWRP main screen again, moreover storage shows about 50000 mb in internal memory, secondly my memory card is not accessible, selection is not working only shows internal memory. As I think at this stage my bootloader(stock) is fine, original stock recovery is replaced by the TWRP 3110 . My factory Android rom is still there in my phone because twrp inernal memory option shows about 50000 mb space captured in internal storage. I have clear delvik and cache but all fails, how I can get the OS by the TWRP. I assume if my old OS has been erased then twrp should have give the "no OS install" massage but this is not happening in my case. Any help...... I am not doing something more due to complete device failure in this stage mainthing is this no factory rom image is available yet, very annoying issue.... regards
Hi guy
I recently got the bluboo s1 , I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the bluboo S1
Anyone knows if I can use the TWRP for the bluboo S1 or is there any other way to root my phone?
the phone runs pretty good , but when i listen music by bluetooh is always cutting off sound when is screen off. i think that is powersaver that set cpu to very low frequency .. so i need to root to change governador
thanks , sorry for my bad english
Root bluboo S1
Yes please... I want to root it too.
I need root my bluboo s1 too. Thx
You have to try this, Same processor, Same android v. We need to tey allways
bbfsonic said:
Hi guy
I recently got the bluboo s1 , I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the bluboo S1
Anyone knows if I can use the TWRP for the bluboo S1 or is there any other way to root my phone?
the phone runs pretty good , but when i listen music by bluetooh is always cutting off sound when is screen off. i think that is powersaver that set cpu to very low frequency .. so i need to root to change governador
thanks , sorry for my bad english
Click to expand...
Click to collapse
Try this please, my S1 is upcomming and i want to solve it before unbox hhhhb... (Madrid, airport barajas. Im on Toledo, spain.)fkng 32dys.. waiting it
"foro.root4ever/Tema-Tutorial-Elephone-P8-root-recoverys-roms-4443"
Its . Com
Root found!!! Bluboo s1 magisk v.14!!! 1rst im doned
bbfsonic said:
Hi guy
I recently got the bluboo s1 , I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the bluboo S1
Anyone knows if I can use the TWRP for the bluboo S1 or is there any other way to root my phone?
the phone runs pretty good , but when i listen music by bluetooh is always cutting off sound when is screen off. i think that is powersaver that set cpu to very low frequency .. so i need to root to change governador
thanks , sorry for my bad english
Click to expand...
Click to collapse
The 12 of OCT i will post a Guide for it.
Super easy.
Only need a patched stock boot.img image
And unlock the phone before flash it.
Fastguide:
Requisites...
Fastboot/adb tools and drivers
Firmware V10 (lastest update)
Unlock Bootloader
Start!!
Connect bluboo S1 on fastboot mode.
With adb/fastboot tool.
Write:
fastboot oem unlock.
Take your phone and press vol+ (same as accept unlock process)
Now your bootloader its free and your phone will FORMAT.
(Only keeping the system base)
Now with your bootloader open... Wait for reboot android UI.
Download the lastest Magisk Manager.apk (search on ggle "V5.3.0" works on my own) and install IT.
Download this file on mega. And remove ESPACES from-the-link (MOST IMPORTANT)
mega. nz /#!xQtwnR7S!h1vylwQd3u_lUZ4Cbkw_S8YOsL2VskIDuVfbNTTkEis
(Img Patched with magisk v14/stock boot.img from Bluboo S1 Compilation V10, android 7.)
Now if u have the .img from MEGA.. Rename it "boot.img" and place it on the "adb/fastboot" Folder
Open adb/fastboot tools, write:
adb reboot fastboot
And simple...wait for fastboot and write:
fastboot flash boot boot.img
Blablabla, OKAY!
And reboot it:
Fastboot reboot
And keep sure all has been doned on magisk manager check it.
Hi !
My S1 is not detected by ADB...But my Windows 10 did it, so i can't update the boot.img, can somebody help me please ?
Unlock bootloader
Mr.N0S said:
The 12 of OCT i will post a Guide for it.
Super easy.
Only need a patched stock boot.img image
And unlock the phone before flash it.
Fastguide:
Requisites...
Fastboot/adb tools and drivers
Firmware V10 (lastest update)
Unlock Bootloader
Start!!
Connect bluboo S1 on fastboot mode.
With adb/fastboot tool.
Write:
fastboot oem unlock.
Take your phone and press vol+ (same as accept unlock process)
Now your bootloader its free and your phone will FORMAT.
(Only keeping the system base)
Now with your bootloader open... Wait for reboot android UI.
Download the lastest Magisk Manager.apk (search on ggle "V5.3.0" works on my own) and install IT.
Download this file on mega. And remove ESPACES from-the-link (MOST IMPORTANT)
mega. nz /#!xQtwnR7S!h1vylwQd3u_lUZ4Cbkw_S8YOsL2VskIDuVfbNTTkEis
(Img Patched with magisk v14/stock boot.img from Bluboo S1 Compilation V10, android 7.)
Now if u have the .img from MEGA.. Rename it "boot.img" and place it on the "adb/fastboot" Folder
Open adb/fastboot tools, write:
adb reboot fastboot
And simple...wait for fastboot and write:
fastboot flash boot boot.img
Blablabla, OKAY!
And reboot it:
Fastboot reboot
And keep sure all has been doned on magisk manager check it.
Click to expand...
Click to collapse
When i press vol up to accept , it fails
Says
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 4.480s
:crying::crying:
bbfsonic said:
When i press vol up to accept , it fails
Says
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 4.480s
:crying::crying:
Click to expand...
Click to collapse
YEEEEES !!! it works Finnaly, i couldn't do it because is needed to go and activate OEM unlocking on developer options and follow the rest of tutorial !
Minimal ADB & Fastboot 1.4.3
JaMaYe said:
Hi !
My S1 is not detected by ADB...But my Windows 10 did it, so i can't update the boot.img, can somebody help me please ?
Click to expand...
Click to collapse
I get the job done using Minimal ADB & Fastboot 1.4.3 download/install it , drivers is included :good: Press (Y) key for everything
Sure itswork, but is a SYSTEMLESS Root, only for wifi tests, adblock works... Rarelly almost on 75% of apps allow it
but works
We need DEVELOPERS. CAN I HELP, but im not a rom chef.
---------- Post added at 06:46 PM ---------- Previous post was at 06:46 PM ----------
Sure itswork, but is a SYSTEMLESS Root, only for wifi tests, adblock works... Rarelly almost on 75% of apps allow it
but works
We need DEVELOPERS. CAN I HELP, but im not a rom chef.
Thank you all. I successfully unlock my S1.
And now, I want to remove FreeTouch and SCWeather. Because they are malware reported by Malwearbytes.
Please tell me how to do it?
rr0909 said:
Thank you all. I successfully unlock my S1.
And now, I want to remove FreeTouch and SCWeather. Because they are malware reported by Malwearbytes.
Please tell me how to do it?
Click to expand...
Click to collapse
You can remove them with malwarbyte, for exemple, or others applications which uninstall systems apps.
Can you give us a feedback of your unlocking please ? Everythings works great ? (wifi, caméra, 4G, ...)
I'm also struggling to remove the system apps after rooting. When I try to uninstall SCWeather or Freetouch using System App Remover (root) I get uninstall failed. Any other ideas for removing these apps.
Any ideas for now, i have disabled it... But this virus i think is made by bluboo and allow with it some apk's ad-works
For example some app downloaded in playstore got secrets, mirrors and redirections... Fckng ads jeje
I said it because... Some ads-apps will create on your screen more than a one **** with a cross in the upper corner.
Yesterday i have downloaded one apk on play store by the name
"navbar apps"
Its a great app for modify tha n.bar
Working by systemless root (our owned root) by great and patched with Lucky.P with buggy selinux permissons
It ask me for root permisson but we cant install busybox
And lucky patcher saids "no busybox found, lucky patcher its not working"
we have one thing or something wrong... Bluboo dont post any homemade development post's, any unlock for boot users or usefull guide's.. Anything guys...
WE Made IT - We SKATE it.
We can work for now, by testing our progress.
For now we are... 3, or 4 users with this great phone on this great forum.
Search somehelp.
We can made some progress.
Ty for all, ask for help guys if anyone know a romchef, scripter for selinux...
With experience on chinese mtk's helio tree devices.
And
If any modder, kitchen or...lool are bored, help us with this fantastic device.
here is a CWM recovery for our device https://www.androidfilehost.com/?w=search&s=bluboo+s1 can be flashed easily via fastboot, I get some issues with touchscreen trying to porting a TWRP, it`s not responsive and I don`t know much about nougat. This CWM don`t take a backup of rom but anyway...waiting for a TWRP.
For those who want root completely can install in recovery via adb sideload last version of Magisk v14.0 or supersu v2.82 too.
And to uninstall undesired apps just do it manually with a root file explorer like ESFile deleting corresponding files in /system/app, /system/priv-app, /data/app and deleting all cache files (just all) in /data/dalvik-cache/arm and arm64, reboot device. Be carefully selecting; Free Touch, CZWeather and launcher can be removed (put other) with their four themes
SubwayChamp said:
here is a CWM recovery for our device https://www.androidfilehost.com/?w=search&s=bluboo+s1 can be flashed easily via fastboot, I get some issues with touchscreen trying to porting a TWRP, it`s not responsive and I don`t know much about nougat. This CWM don`t take a backup of rom but anyway...waiting for a TWRP.
For those who want root completely can install in recovery via adb sideload last version of Magisk v14.0 or supersu v2.82 too.
And to uninstall undesired apps just do it manually with a root file explorer like ESFile deleting corresponding files in /system/app, /system/priv-app, /data/app and deleting all cache files (just all) in /data/dalvik-cache/arm and arm64, reboot device. Be carefully selecting; Free Touch, CZWeather and launcher can be removed (put other) with their four themes
Click to expand...
Click to collapse
Hi ! When I use adb sideload to root the phone with Magisk v14.0 or supersu v2.82 i have a message "Installation aborted" and off course i dont know why...
JaMaYe said:
Hi ! When I use adb sideload to root the phone with Magisk v14.0 or supersu v2.82 i have a message "Installation aborted" and off course i dont know why...
Click to expand...
Click to collapse
Be sure follow next: go to recovery, connect to device, go to install zip menu, install via adb sideload, then type in terminal to check if device if recognised: adb devices put and rename for short file magisk. zip inside adb folder and type adb sideload magisk. zip don'forget file extension
'Normal its same doogee mix you need decrypt your data for the root is in system and all apps work with supersu ,for adb you can use this programm adb automotic 0 command all its automatic just replace your file
Link: https://www.needrom.com/download/root-twrp-toolkit-doogee-bl5000/
Regards
PS: when you say decrypt data its easy
Envoyé de mon MIX en utilisant Tapatalk
The sheer amount of different android devices will make it really hard to get things rooted with one tap in the future. Most one tap roots already stoped working for a lot of my stuff.
I successfully unlock my S1, but it´s a SYSTEMLESS ROOT!
How do I get full root? I want delete some privates apk
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Try this
Planet Indigo said:
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Click to expand...
Click to collapse
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
KIBS2173 said:
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
Click to expand...
Click to collapse
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Planet Indigo said:
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
Click to expand...
Click to collapse
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Karamarov1 said:
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Click to expand...
Click to collapse
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
KIBS2173 said:
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Click to expand...
Click to collapse
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Try this
Planet Indigo said:
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Click to expand...
Click to collapse
Hi there,
So i was researching more about this tablet, turns out you can root by installing a custom recovery (TWRP) and from there you can install SUPERSU to achieve root for your tablet. I am not sure if this method works, but if your able to get the stock firmware and the stock recovery and the software to flash the firmware i think you might as well go ahead using that method.
THIS IS THE ARTICLE I FOUND ONLINE :
https://www.getdroidtips.com/how-to-install-twrp-recovery-on-teclast-t30-and-root-it-easily/
*MAKE SURE YOU FIND OUT IF THIS TABLET HAS A TWRP RECOVERY BEFORE DOING ANYTHING ELSE*
Thank you for looking into it, unfortunately that guide is for the Teclast T30 and the guy advises to only use it for that model. I don't own that tablet yet so I can't try any of the steps myself but I'm very interested in this particular model (16/9 ratio, hdmi out, dc charger in, etc...) so I was really hoping to find a tested working method to root it before I go ahead and purchase it.
i found this: https://www.getdroidtips.com/root-teclast-m16/
I rooted my Teclast M16 using Magisk. Simply unlocked the bootloader through adb/fastboot commands, then have magisk manager patch the boot image from firmware download and then flash it using adb/fastboot command line fastboot flash boot magisk_patched_boot.img reboot system and its rooted.
I haven't found a twrp recovery yet, but I'm thinking about trying my hand at building my own, despite being a noob.
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Hi. Have you got you on working twrp recoberto?
fdsafggg said:
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Click to expand...
Click to collapse
Hi.
I tried to unlock the bootloader .
adb devices command shows the m16.
I send the command "adb reboot bootloader" - the device enter in bootloader.
next I send the command "fastboot devices" and I get this:
PS E:\modified_fastboot> fastboot devices
???????????? fastboot
any help to make fast boot see the device?
Thank you
dcoelho said:
Cześć.
Próbowałem odblokować bootloader.
Polecenie urządzeń adb pokazuje m16.
Wysyłam polecenie "adb reboot bootloader" - urządzenie wchodzi w bootloader.
następnie wysyłam polecenie „urządzenia fastboot” i otrzymuję to:
PS E:\modified_fastboot> urządzenia fastboot
???????????? szybki start
jakakolwiek pomoc, aby szybki rozruch zobaczył urządzenie?
Dziękuję Ci
Click to expand...
Click to collapse
Hi, You bad comand when bootloader. When bootloader after comand: " fastboot oem unlock" , luck on skreen, push volume up, wait moment, after next comand:"fastboot reboot". After this command, the tablet will reset to factory settings with unlocked bootloader.
Hello everyone. I have TWRP for M16, everything is almost fine, after uploading it normally work on M16, except for touch not working, I did not check if it works with the mouse. Maybe someone will find it to correct it so that the touch works? I upload the file, it may be useful to someone. Regards RW
reupload boot.img
Hello everyone hope you are all keeping well.
Since I believe that many of you don't know about this, I've decided to share the steps I've done in order to root the OP 11R ( ACE 2 )
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
adb devices
adb reboot bootloader
(so your phone will reboot into fastboot mode)
fastboot flashing unlock
(device should now unlock)
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
2 - Download OP 11R stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Indian Boot.img A_0.8 - download
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
6 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
7 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
8 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
Why title says NORD 2T?
firoz3321 said:
Why title says NORD 2T?
Click to expand...
Click to collapse
MB ... typo
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
firoz3321 said:
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
Click to expand...
Click to collapse
Sorry but there is no msm tool available for new OnePlus devices. + You can use Fastboot enhance tool from github to recover softbrick , magisk is always recommended for rooting because of ease of steps and simple to use
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
saifsohel said:
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
Click to expand...
Click to collapse
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
shiki_senpai said:
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
Click to expand...
Click to collapse
Then remember to take a backup of the boot before rebooting. I messed up big time.
Thanks for the detailed information man. Can I know if bootloader unlock decreases widevine L1 to L3? As this was case with my OP6