Database Users

[Root any Moto G] with screenshots [Simple Method|Well Explained]

Hi...
This is the tutorial to root any Moto G
To root any Moto G, three basic steps need to be followed... you can either do them manually or use a tool do them for you. It is advised to follow them manually so that if there's some bug in the tool you don't get into any trouble.
CAUTION - You will lose all data and files so better back them up.
For Google Play edition devices, the process is same and only the recovery.img file is different. For GPe CWM Advanced Edition recovery go here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ and select falcon_gpe and download the latest one.
For AT&T and Verizon models don't do anything written above. Just download the Towelroot app. Its a one click root app and doesn't require a PC. Itis trustworthy but is not guaranteed to work but you must give it a try since it won't do any harm and claims of never bricking a phone. Please reply with the result and your android and kernel version.It will probably not work on phones build after June 3 but you can give it a try. You can download it from the website https://towelroot.com
The three steps are :-
1) UNLOCKING THE BOOTLOADER
2) FLASHING CUSTOM RECOVERY
3) INSTALLING SuperSu.zip FILE THROUGH RECOVERY. (SuperSu is acknowledge as the best app to give superuser and root rights)
UNLOCKING THE BOOT LOADER - The instructions to unlock the boot loader are given in the official Motorola website here https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a . Don't be scared by their warnings.
UPDATE - There currently seems to be an issue with unlocking the bootloader on devices running 4.4.4 though it works for 4.4.2. The issue is with Motorola and is that, the unlock code given by the company is showing an error. They are fixing it and it may take some time though you can give it a try as it won't do any harm. Or you can downgrade the boot loader to 4.4.2 and then unlock it.
As confirmed by the Motorola agent, the problem of unlocking bootloader on 4.4.4 has been fixed
FLASHING CUSTOM RECOVERY :-
To flash a custom recovery, you need these things
1) PC and a USB data cable
2) Android SDK ( developer.android.com/sdk/index.html ) For flashing recovery only SDK is needed but it's your wish if you want to download the ADT bundle. After downloading and unzipping the sdk , open the SDK manager and download only the platform tools for this.. rest is your wish..... and separately download ADB tools and fastboot and extract them minimal-adb-and-fastboot.software.informer.com/1.1/
3) Recovery.img file - You can either use CWM foum.xda-developers.com/showthread.php?t=2563599 or CWM advanced editionforum.xda-developers.com/showthread.php?t=2639583 or TWRP forum.xda-developers.com/showthread.php?t=2561757. EDIT - If your phone had come pre installed with 4.4.4 then use only CWM Advanced Edition. CWM Advanced Edition doesn't make backup on XT1033
4) Motorola drivers https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
5) Enable USB Debugging mode in your phone by going to Settings-About Phone and then tap the build number until you get the toast 'You are a developer'. Now go to Settings again and you will see a new Developer Options there. Go there and enable USB debugging.
6) Have at least 25% of charge on your phone.
After getting all these things:-
1) Download the recovery.img file to your PC and copy paste it to android SDK/platform tools folder.
2) Boot your phone to fastboot mode by first switching it off and holding the volume down and power button for 3 seconds.
3) When in fastboot mode, connect your phone to pc, go to the platform tools folder, there pres shifft and right mouse click simultaneously and select 'open command prompt window here'.
4) In the command window enter
Code:
fastboot devices
If it shows a number and fastboot then we are good..
5) Then enter
Code:
fastboot flash recovery recovery.img
( where in recovery.img the recovery is the name of your recovery file. Example if the name of recovery file is ABC then enter fastboot flash recovery ABC.img)
5) Press enter and if the command prompt window displays the message okay then the recovery is successfully flashed.
6) Now just boot your phone to recovery mode through fastboot mode by following the on screen instructions and in recovery mode select Reboot System Now to reboot your phone normally.
(see attached images below for screenshots)
INSTALLING SuperSu
To install SuperSu :-
1) Download SuperSu zip file download.chainfire.eu/452/SuperSU/ and transfer it to your phone
2) Reboot to recovery via fastboot.
3) Select install zip and select choose from SD card.
4) Locate the file and install it.
5) Now reboot your phone.
YUP.. YOU ROOTED YOUR PHONE!
Download any root checker app from the Play Store to check whether your phone is rooted or not.
If you get into any trouble, please contact and don't forget to hit thanks if it helped
Consider rating the thread by going to the option 'rate thread' which is located above the thread on the right side. You can also participate in the poll

I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app

sisqoboy said:
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Yup dude...this works for sure..!
I also added screenshots.. check them out.

Meuuks13 said:
Yup dude...this works for sure..!
Click to expand...
Click to collapse
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks

motocruiser said:
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
Click to expand...
Click to collapse
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.

And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app

xrilex said:
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have Verizon I see. The only you will probably face is unlocking the bootloader.. Oh, wait first let me laugh... lol...OK....At one point of time you couldn't unlock the bootloaders for AT&T and Verizon and then we were blessed by the 'one click root' app by the famous hacker geohot called TowelRoot. This app claims to root all the AT&T and Verizon devices with just a click. You don't even need a PC. Just download the app and in the app chick 'make it rain'. Though this is not guaranteed to work but must give a try as it won't do any harm but there's a chance of bricking the phone but you can easily recover from a soft brick by flashing the stock firmware.
Towelroot - https://towelroot.com/
P.S. - Please reply if you tried this and if it didn't work reply with your android version and kernel version. Well reply with your android version and kernel version anyway.
Edit- I added it to the OP

Meuuks13 said:
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
Click to expand...
Click to collapse
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self

motocruiser said:
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
Click to expand...
Click to collapse
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?

Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!

t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell which android version your phone came preinstalled with and what recovery you used.
Also when you reboot to recovery, after the blank screen do you see the android logo lying down with a red triangle?

t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell your phone's android version and the recovery you used and what did you enter at the command prompt?

Meuuks13 said:
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Click to expand...
Click to collapse
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks

motocruiser said:
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
Click to expand...
Click to collapse
Testdrive image?

Meuuks13 said:
Testdrive image?
Click to expand...
Click to collapse
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image

motocruiser said:
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
Click to expand...
Click to collapse
So basically you want to downgrade the bootloader and then unlock it?
Well if you are on KitKat you can downgrade the bootloader by flashing 4.3 , then unlocking the bootloader and then updating to KitKat

Thanks for the guide. I've already recommended it to someone who was having problems.

jselene said:
Thanks for the guide. I've already recommended it to someone who was having problems.
Click to expand...
Click to collapse
Cool.

Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566

JDCGW said:
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I got something wayyyy better than that!
I let you remove that sign and use the pics given here forum.xda-developers.com/moto-g/themes-apps/shareboot-logos-t2875147 or you can give me the pic you want and I will make it in such a way that you can use it.

[GUIDE] [NOOB Friendly] Root and Install TWRP on HTC One M9

Mod information 2018-07-29
This method described below is outdated and following the guide might end in a bootloop if users are currently using the latest firmware.
​
This is a guide on how to root the HTC One M9.
Your M9 must have an unlocked bootloader. There is currently not a way to unlock the bootloader, so unless your phone comes with an unlocked bootloader, you will need to wait until HTC updates www.htcdev.com to unlock the M9 bootloader.
Video Guide: Video
Link to the correct TWRP to use thread by Captain_Throwback READ DISCLAIMERS!: http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
Link to TWRP page in general: http://twrp.me/devices/htconem9.html
Link to correct SuperSU to flash: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Unlocking the bootloader. (Thanks -markus-)
- Login into HTCdev
- Unlock Bootloader
- Get Started
- On "Select Your Device" Select "All Other Supported Models"
- Begin Unlock Bootloader
- Legal Terms "Proceed to Unlock Instructions
- On Phone pressing Volume Down + press Power to boot in "HTC download mode" (black Background)
- Connect Phone via USB
- CMD: fastboot oem get_identifier_token
- Copy and paste the token in Textfield "My Device Identifier Token:"
- You will receive an Email with "Unlock_code.bin
- CMD: fastboot flash unlocktoken Unlock_code.bin
- Press Volume Button to secelt Yes for Unlock bootloader
If your bootloader is unlocked, follow these steps.
Download and install ADB/Fastboot using 15 second ADB/Fastboot installer.
Plug in the One M9, enable USB debugging.
Open up command prompt, type
Code:
adb devices
Code:
adb reboot download
Code:
fastboot flash recovery C:\Users\XDADev\Downloads\TWRP.img
Replace C:\Users\XDADev\Downloads\TWRP.img with the path where the twrp.img is located for you.
Power off your device. Now, to boot into recovery mode.
Press and hold Volume Down button, then press the Power button to switch on your phone and release it, but keep holding the Volume Down button.
Select boot to recovery on the screen that appears(bootloader)
Download SuperSU.zip
Make sure you have an SD Card in your phone, then do
Code:
adb push C:\Users\XDADev\Downloads\UPDATE-SuperSU-v2.46.zip /sdcard
Once again, replace C:\Users\XDADev\Downloads\UPDATE-SuperSU-v2.46.zip with your path.
On your device, click Install, then at the top of the screen it should say Internal Storage or SDCard. If it does not say SD Card, click it and change it to SD Card.
Now find SuperSU.zip, click on it, and swipe to flash it.
Once SuperSU is done flashing reboot the phone, and open up SuperSU. You are now rooted!
If this helped you, feel free to click Thanks below.

Awesome! Thanks, I'll get a quick tutorial video up once I get my hands on an M9

FYI I'm pretty sure you can't root with the version of TWRP that's currently uploaded. It doesn't have writing to the system partition enabled. If you look in the recovery fstab, system is mounted as emmc.
You'll have to wait until an alternate version is uploaded for this to work. Someone will need to confirm whether rooting will completely break the ability to take an OTA too.
EDIT: There's also this disclaimer on the device page: "NOTE: Installing TWRP can break your ability to receive updates from HTC."
EDIT 2: The other question is whether unlocking the device will allow system to be written to at all in the OS, or only while in recovery. I think once some people have the device in their hands, some of these questions can finally be answered.

Captain_Throwback said:
FYI I'm pretty sure you can't root with the version of TWRP that's currently uploaded. It doesn't have writing to the system partition enabled. If you look in the recovery fstab, system is mounted as emmc.
You'll have to wait until an alternate version is uploaded for this to work. Someone will need to confirm whether rooting will completely break the ability to take an OTA too.
EDIT: There's also this disclaimer on the device page: "NOTE: Installing TWRP can break your ability to receive updates from HTC."
EDIT 2: The other question is whether unlocking the device will allow system to be written to at all in the OS, or only while in recovery. I think once some people have the device in their hands, some of these questions can finally be answered.
Click to expand...
Click to collapse
Test devices are S-OFF.....but bootloader locked. Go figure.

I have a t mobile M9 rooted
Hello I was able to unlock the bootloader from dev site and was able to install TWRP. I was able to install super SU and now i'm rooted!
here is my reddit post. http://www.reddit.com/r/htcone/comments/303ys2/just_got_my_hands_on_a_tmobile_htc_m9/

Worked for me
But to flash successfull recovery you have to boot to "htc download mode", the black background!
If you see white background you are on bootloader, here you are not able to flash TWRP Recovery, you will get the message "FAILED (remote: cannot flash this partition in s-on state)"
So boot to "download mode" an it work

trying this tomorrow.
Is there any way to virginize the device if I don't want it to be rooted anymore ?

DroidShift79 said:
trying this tomorrow.
Is there any way to virginize the device if I don't want it to be rooted anymore ?
Click to expand...
Click to collapse
Pull the stock recovery image before you flash TWRP. I neglected to do so (but I do have my Verizon device rooted with TWRP.
One problem, TWRP can't read or write to encrypted sdcards, either internal or removable.
My name is Harold and I'm a flashaholic.....

-markus- said:
Worked for me
But to flash successfull recovery you have to boot to "htc download mode", the black background!
If you see white background you are on bootloader, here you are not able to flash TWRP Recovery, you will get the message "FAILED (remote: cannot flash this partition in s-on state)"
So boot to "download mode" an it work
Click to expand...
Click to collapse
Markus, what device do you have.. international, verizon?

k1moe said:
Markus, what device do you have.. international, verizon?
Click to expand...
Click to collapse
I got it from O2 Germany CID is O2_102

Three questions:
1. Do I really have to buy an SD card to do this?
2. How do you boot to download mode?
3. Should the bootloader be unlocked before or after installing TWRP and rooting, or does it not matter?

1. Every XDA developer has one..
2. Choose REBOOT from the shut down menu, then when display turns black - press and hold hardware button volume - ..
3. That will save you from frustration..

jauhien said:
3. That will save you from frustration..
Click to expand...
Click to collapse
Thanks. You mean unlock bootloader first right?

-markus- said:
I got it from O2 Germany CID is O2_102
Click to expand...
Click to collapse
Um.. how do you have unlocked your bootloader? I got my M9 from Vodafone Germany (retail unit) and via HTCdev im not able to unlock BL

This will work on the u.s. m9 versions? Thanks
Sent from my SM-N910T using XDA Free mobile app

xda23 said:
This will work on the u.s. m9 versions? Thanks
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
The TWRP *should* work on all variants. Only way to know for sure is to try it .

k1moe said:
Um.. how do you have unlocked your bootloader? I got my M9 from Vodafone Germany (retail unit) and via HTCdev im not able to unlock BL
Click to expand...
Click to collapse
- Login into HTCdev
- Unlock Bootloader
- Get Started
- on "Select Your Device" i used "All Other Supported Models"
- Begin Unlock Bootloader
- Legal Terms "Proceed to Unlock Instructions
- On Phone pressing Volume Down + press Power to boot in "HTC download mode" (black Background)
- Connect Phone via USB
- CMD: fastboot oem get_identifier_token
- Copy and paste the token in Textfield "My Device Identifier Token:"
- You will receive an Email with "Unlock_code.bin
- CMD: fastboot flash unlocktoken Unlock_code.bin
- Press Volume Button to secelt Yes for Unlock bootloader
- thats it
I hope i could help you

Unlocked the bootloader and flashed TWRP...
SuperSU 2.46 isn't getting root...
When flashing it appears to be successful...
But then when the phone reboots there is no root access...
SuperSU - gives this error
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!
Anyone else have this problem or know a workaround.

jbm76 said:
Unlocked the bootloader and flashed TWRP...
SuperSU 2.46 isn't getting root...
When flashing it appears to be successful...
But then when the phone reboots there is no root access...
SuperSU - gives this error
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!
Anyone else have this problem or know a workaround.
Click to expand...
Click to collapse
How did you install SuperSU?
I put the Zip-File on internal Storage and boot from recovery and installed it.
I did not use the way about "adb push SuperSU-v2.46.zip /sdcard" because i don't have an SD-Card at moment.

-markus- said:
How did you install SuperSU?
I put the Zip-File on internal Storage and boot from recovery and installed it.
I did not use the way about "adb push SuperSU-v2.46.zip /sdcard" because i don't have an SD-Card at moment.
Click to expand...
Click to collapse
same as you did...

[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB

[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB
Hi !
Quick info: I am not a novice when it comes to rooting / unlocking bootloader / installing TWRP or CWM / installing Xposed Frameworks, etc
I will make this short and sweet.
My Info :
- Axon 7 Gold - A2107U (US variant) with Update B29 installed (A2017UV1.0.0B29)
- Minimal ADB and Fastboot
- Windows 7 x64 Home premium
Here are the steps I have done:
1-
I installed the ADB drivers and Qualcomm WWAN drivers on my computer.
2-
Under Developers settings, I have enabled "OEM Unlocking".
3-
Using Axon7backup.exe, I created 2 backup files: "stock_recovery_backup.img" and "stock_boot_backup.img"
4-
Rebooted in bootloader using "adb reboot bootloader", (my device was listed). I first tried "fastboot oem unlock" then tried "fastboot flashing unlock", both returning "Unknown Command".
HERE IS WHERE I AM CONFUSED:
Normally, anyone would Unlock to bootloader THEN install TWRP, but from what I've seen with Axon7, some people say that Installing TWRP is "required" to unlock the bootloader.
I've seen some say that they have successfully rooted / unlocked bootloader with the B29 update, but I don't see any zip files or threads for the B29.
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you !

Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you ![/QUOTE]
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) I am assuming you already have the tool downloaded since you used it to create the backup files so just follow the same instructions to boot into edl mode, then open a command window where the tool is located. Then execute:
Code:
axon7backup.exe
to start the tool and then
Code:
axon7root.exe -p # -r
where # is your COM Port # in Device Manager. The tool will flash the signed version of TWRP with ZTE's signature from the leaked firehose onto your Axon 7.
2)Hold down volume up and power to exit download mode and boot into recovery which should now be TWRP.
3) Download the bootloader unlock zip from @DrakenFX: https://www.androidfilehost.com/?fid=529152257862665656. Flashing the zip will replace your fastboot image with the one from B20_boot.
4) After you have flashed the zip, reboot to bootloader and just execute
Code:
fastboot oem unlock
and you are good to go!

^^The stock fastboot does not support the unlocking command. There's another fastboot image in the bootloader unlock thread that gets flashed first. *THEN* you can issue the unlock command.
I've been messing with android at least since late 2009 and have seen many variants of unlocking processes. This one is new for me too.

bkores said:
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) Go to this thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204. Download @tenfar's tool for A2017U B20(axon7root.exe not axon7backup.exe). There is no tool for B27 or B29 because the OP is no longer active but it will still work(I have tested.)
Click to expand...
Click to collapse
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
EDIT: Should I do following command ?: reboot disemmcwp (to remove protect write, or it's no longer necessary? )

Boutchoo said:
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
Click to expand...
Click to collapse
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool. And yes you should do "reboot disemmcwp" if you want to be able to make changes to /system

bkores said:
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool.
Click to expand...
Click to collapse
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password *NEVER MIND- FORMATED CELL, NOW WORKS*
Edit3: Do I need to flash SuperSU or is it pre-packaged ?

Boutchoo said:
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password
Click to expand...
Click to collapse
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened. For some reason ZTE screwed up encryption to the point where if you backup data in TWRP with a pin/password/pattern enabled and then restore from it you will get a data decryption prompt where no password would work, not even your own. If you get this you have no choice but to wipe your data and then do either a Google restore during setup or use Titanium Backup(after you flash SuperSU) if you have it. In the future if you want to backup your data and until ZTE fixes it, you have to disable your pin/password/pattern first.

bkores said:
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened.
Click to expand...
Click to collapse
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?

Boutchoo said:
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Click to expand...
Click to collapse
Flash SuperSU

bkores said:
Flash SuperSU
Click to expand...
Click to collapse
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.

Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)

bkores said:
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
Click to expand...
Click to collapse
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.

Boutchoo said:
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Click to expand...
Click to collapse
The modified boot image allows people without an unlocked bootloader to have root however if your bootloader is unlocked you should not do it as you will have the data decryption issue.

Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
Try 2.65

[X01BD] Can't install TWRP after unlocking with Official UnlockTool

Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks

Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
Guys, no one to help or assist?

Mr147 said:
Guys, no one to help or assist?
Click to expand...
Click to collapse
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?

X10MINISTER said:
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
Click to expand...
Click to collapse
Yes, everything done.
Still no success.

Mr147 said:
Yes, everything done.
Still no success.
Click to expand...
Click to collapse
Did ur unlocking bootloader succeed?

Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...

X10MINISTER said:
Did ur unlocking bootloader succeed?
Click to expand...
Click to collapse
I guess it did because when I reboot it I get that bootloader unlocked splash screen.

Tyakrish said:
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
Click to expand...
Click to collapse
Tried everything except 2, none worked. I'll drop them a query over twitter like you say, let's see what their reply is.
I am on stock recovery, non working bootloader but unlocked, and stock rom unrooted.
I think Pie update may give some insight on fixing this.

Mr147 said:
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Click to expand...
Click to collapse
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..

X10MINISTER said:
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
Click to expand...
Click to collapse
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.

Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)

Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Click to expand...
Click to collapse
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work

#ArtFuL said:
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
Click to expand...
Click to collapse
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".

So is it done?

Mr147 said:
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
Click to expand...
Click to collapse
See I recommend please use Linux (Manjaro or Ubuntu) , Windows will have driver issues forever and ever

had same issue after fota update UL-ASUS_X01BD-WW-15.2016
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Thanks , this method work me. had same issue after fota update UL-ASUS_X01BD-WW-15.2016.1902.192-user
Click to expand...
Click to collapse

I've the same problem too. Let me know if you've configure it out. Thanks.

Okay @Mr147, I've fix this. I checked Windows Update and there was a pending ASUS driver update. I downloaded it and now I can use the fastboot commands.

Anyone that can fix this problem? I also experience this.

Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
I suggest to Unlock with unofficial step, or read the post https://www.blocknesia.com/2019/04/unlock-bootloader-dan-install-twrp-asus-zenfone-max-pro-m2.html

Root without unlocking bootloader

Hi,
I'd like to root my zenfone 2 laser (ze550kl z00ld). I've been trying to unlock the bootloader with the Asus app (version 9.0.0.3) for a few days but it fails every time as for many other users (can't post urls but several threads on asus zentalk forums). I can't find version 9.1.0.0 of the tool unfortunately. However, it looks like I could root the phone without unlocking the bootloader because I can use adb to reboot to fastboot mode (adb reboot bootloader from pc command line) as I have enabled developer mode with usb debugging and the computer is allowed on the phone.
Am I right to do this?
- download latest twrp recovery image for phone model (twrp-3.3.1-0-Z00L.img from dl.twrp.me) on computer
- connect phone to computer (linux OS) & reboot to fastboot mode
- flash twrp image via
Code:
flashboot flash recovery twrp-3.3.1-0-Z00L.img
from computer
- simultaneously reboot the phone from computer via
Code:
fastboot reboot
while simultaneously holding down the volume down key on the phone
- this should allow me to reboot into twrp recovery from which I can flash the supersu app zip dowloaded from supersu.com and copied from the computer onto the phone's sd card root
Does this seem correct to you? Is this likely to succeed or should I continue trying to unlock the bootloader?
Thank you very much!

DrWaste said:
Hi,
Does this seem correct to you? Is this likely to succeed or should I continue trying to unlock the bootloader?
Thank you very much!
Click to expand...
Click to collapse
Hello
You won't be able to install TWRP without unlocking the bootloader.
The official unlocking tool is very buggy, and pretty much useless since it never works.
I recommend you follow this unofficial method.
https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
You should be able to unlock the bootloader in less than 5minutes. Just enable adb, boot into fastboot and run the code available in that thread, and it should do the trick.
After unlocking, then you can install TWRP and then Magisk, if all you want is to have root.

Hello,
FHC1998 said:
I recommend you follow this unofficial method.
https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
Click to expand...
Click to collapse
There's something I don't understand. On the first message of that thread it says:
You MUST be rooted to use this method.
Click to expand...
Click to collapse
That can't work for me as my phone isn't rooted.
It says to follow other methods given in another thread to try to root the phone beforehand. I'd read all these threads before. There are three which give a guide to root the zenfone 2 laser ze550kl. One requires to first unlock the bootloader (feels like I'm going round in circles here...) and the other two link to a firmware patch which used to be hosted on mega.nz but aren't available anymore.
I'd love to go the easy way and unlock the bootloader first before flashing twrp recovery and then rooting, but it seems like that's just not possible because all the guides are obsolete, or am I missing something more subtle?
Thanks!

DrWaste said:
Hello,
There's something I don't understand. On the first message of that thread it says:
That can't work for me as my phone isn't rooted.
It says to follow other methods given in another thread to try to root the phone beforehand. I'd read all these threads before. There are three which give a guide to root the zenfone 2 laser ze550kl. One requires to first unlock the bootloader (feels like I'm going round in circles here...) and the other two link to a firmware patch which used to be hosted on mega.nz but aren't available anymore.
I'd love to go the easy way and unlock the bootloader first before flashing twrp recovery and then rooting, but it seems like that's just not possible because all the guides are obsolete, or am I missing something more subtle?
Thanks!
Click to expand...
Click to collapse
If I recall correctly, the root part is only used to make the partitions backup with adb shell.
The bootloader unlocking part (the two line code that goes "echo ....") doesn't need it.
I used this tutorial a long time ago, so take this info with a grain of salt.
The problem is that this phone is almost 4 years old now, so most links are not being updated or dead.
So it might be worth a shot trying to run that code without root. (By my understanding, root does not alter the fastboot binaries, so it should not be necessary).
In any case, I might have a backup of a patched system IMG somewhere on my computer. I'll try searching for it and if I find I'll upload it to you.

Hello,
FHC1998 said:
If I recall correctly, the root part is only used to make the partitions backup with adb shell.
The bootloader unlocking part (the two line code that goes "echo ....") doesn't need it.
I used this tutorial a long time ago, so take this info with a grain of salt.
The problem is that this phone is almost 4 years old now, so most links are not being updated or dead.
So it might be worth a shot trying to run that code without root. (By my understanding, root does not alter the fastboot binaries, so it should not be necessary).
In any case, I might have a backup of a patched system IMG somewhere on my computer. I'll try searching for it and if I find I'll upload it to you.
Click to expand...
Click to collapse
OK, I'll give a shot that way. If you do find the system image that would be cool.
Thanks.

Hello,
FHC1998 said:
If I recall correctly, the root part is only used to make the partitions backup with adb shell.
The bootloader unlocking part (the two line code that goes "echo ....") doesn't need it.
I used this tutorial a long time ago, so take this info with a grain of salt.
The problem is that this phone is almost 4 years old now, so most links are not being updated or dead.
So it might be worth a shot trying to run that code without root. (By my understanding, root does not alter the fastboot binaries, so it should not be necessary).
In any case, I might have a backup of a patched system IMG somewhere on my computer. I'll try searching for it and if I find I'll upload it to you.
Click to expand...
Click to collapse
Nope, seems to require root to modify the hex value of byte 16 on the boot device (I presume that's what the command does, there's no man accessible via adb shell but that's what that dd command does on unix machines). I can't even, as normal user, list /dev/block or even /dev:
Code:
1|[email protected]_Z00L_63:/ $
count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo <
dd: /dev/block/bootdevice/by-name/devinfo: Permission denied
1|[email protected]_Z00L_63:/ $ ls /dev
/dev: Permission denied
Bummer, really hoped it would work. Back to unlocking the bootloader via the buggy Asus app it seems, or chucking the phone out of the window maybe...
Thanks for your help anyway :good: