Database Develop

[Q] After flashing TWRP, XT1063 only boots to the unlocked warning screen

My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!

Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?

Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.

But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.

Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.

Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.

Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img

I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.

Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery

I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.

Oh, did you check the md5 checksum of your download?

Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?

Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers

I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!

Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery

Questions/concerns about CM12.1 + rooting + unlocking bootloader

Hey guys
So I just bought a new Z3C and I'm planning on rooting it and installing CM12.1 on it. But before that I wanna make sure I perfectly understood the entire process. So if anyone could help by answering/confirming some of the things below, I would really appreciate that.
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Thank you very much.

arsradu said:
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Click to expand...
Click to collapse
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
arsradu said:
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Click to expand...
Click to collapse
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
arsradu said:
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Click to expand...
Click to collapse
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
arsradu said:
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Click to expand...
Click to collapse
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
arsradu said:
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
Click to expand...
Click to collapse
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
arsradu said:
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Click to expand...
Click to collapse
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.

MyPictures said:
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
Click to expand...
Click to collapse
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.

arsradu said:
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
Click to expand...
Click to collapse
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?

MyPictures said:
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
Click to expand...
Click to collapse
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk

arsradu said:
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
Did you install the drivers properly and on which Operating system are you flashing it?

MyPictures said:
Did you install the drivers properly and on which Operating system are you flashing it?
Click to expand...
Click to collapse
I would say yes. I mean...after googling a bit, I saw that I actually don't need to just "ignore" that message asking to press the Back button, but to actually press Volume Down instead. Which I did. And I was able to go into Flash Mode. (Flash Tool says "device connected in Flash Mode"). The device was properly recognized in MTP mode. Still, I had to manually install the Flash-tool drivers to get it recognized in flash mode, as well. Not sure why...
I mean, if the phone was properly recognized without manually installing anything (Windows downloaded and installed its own drivers), why the hell do I need to install custom drivers to get it recognized in flash mode? By the way, this "flash mode" is similar to Samsung's "Download Mode", for as far as I could see. And, just like on Samsung's devices, the access is made by pressing the Volume Down upon booting up.
Anyway, even though the device is now recognized in flash mode, I still get an error trying to flash stock 4.4.4.
I get this:
Code:
14/014/2015 21:14:34 - INFO - Please connect your device into flashmode.
14/016/2015 21:16:28 - INFO - Device disconnected
14/017/2015 21:17:03 - INFO - Device connected in flash mode
14/017/2015 21:17:03 - INFO - Opening device for R/W
14/017/2015 21:17:03 - INFO - Reading device information
14/017/2015 21:17:03 - INFO - Unable to read from phone after having opened it.
14/017/2015 21:17:03 - INFO - trying to continue anyway
14/017/2015 21:17:03 - INFO - Start Flashing
14/017/2015 21:17:03 - INFO - Processing loader.sin
14/017/2015 21:17:03 - INFO - Checking header
14/017/2015 21:17:03 - ERROR - Processing of loader.sin finished with errors.
14/017/2015 21:17:03 - INFO - Ending flash session
14/017/2015 21:17:03 - ERROR - Error in processHeader : 1 : Incorrect function.
14/017/2015 21:17:03 - ERROR - Error flashing. Aborted
14/017/2015 21:17:03 - INFO - Device connected in flash mode
And after a while, it automatically reboots in normal mode.
Windows version is Windows 10. But I'm not sure that's the problem here since, as I said, the device does get recognized both in MTP and flash modes. Also, for as far as I could see, other people are having the same issues on other versions of Windows.

Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.

MyPictures said:
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
Click to expand...
Click to collapse
Yes, I'm running FlashTool64.exe since I'm running a 64-bit version of Windows.
The device is correctly recognized in flash mode (after manually selecting the driver installed with flash-tool). See the attached image for more info.
But indeed maybe I got the wrong firmware. Problem is that I'm not really sure which one should I choose.
I got one called D5803_23.0.1.A.5.77_Customized_FR.ftf. I don't mind it that it's in French. All of them have English anyway.
Also, I saw one for UK here called D5803_23.0.A.2.105_UK.ftf. Seems to be different.... I will try with that as well.
Update: same error with that UK firmware, as well.
Update2: Well I'm half way there. Got 4.4.4 installed and got it rooted. YAY. Still trying to figure out why adb is not correctly running when trying to backup TA.
Update3: ok, backup done too!
Update4: the boot.img that comes with CM12.1 doesn't seem to have a recovery.... Or if it does, I couldn't boot in it so I can flash CM12.1.
I tried the one from Doomlord (Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img) and that seems to be based on CWM v6.0.4.7.
Problem with that is that, even though I can boot into recovery, I can't flash CM12.1. It says error status 7. Any idea why or how to fix this?

I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).

MyPictures said:
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
Click to expand...
Click to collapse
Might be. The problem is the device is not correctly recognized upon flashing (it says the device is "Aries" but the ROM is for D5803, D5833, z3c LOL), due to the check made within the updater-script (first line). For as far as I could see, this is a known issue... Not sure why it hasn't been fixed by now.
Anyway, removing that line will get the ROM installed successfully (at least with THAT recovery).
So I'm on CM12.1 , been for a few days now (thank you for your help), and I was wondering if there are any "permanent" recoveries (compatible with CM12.1, of course) that I can flash, something that can give me the ability to boot into recovery (and not Cyanogen Recovery, since that one sucks) and do things like nandroid backup (I know TWRP and CWM can do that, but I couldn't find any permanent version of those (or maybe I just didn't dig deep enough), and I'm not sure they are compatible with CM12.1) and formatting /system. The last one is really important for a clean installation of the ROM, especially since it doesn't look like it's done by the ROM itself.

[GUIDE] Marshmallow Root Guide for ZE500KL

ATTENTION!
You MUST read all the guide BEFORE doing it, if you do it without reading all of it first you may ends up bricking your phone!
Prerequisites:
Asus ZE500KL (may work on ZE500KG, but haven't tested, do it on your own risk) on Marshmallow, NOT LOLLIPOP!
Also, it must have fully booted AT LEAST one time, otherwise, you'll soft-brick it.
If your phone is not on Marshmallow, you can use THIS guide instead​Download and put the unlocker zip file and the SuperSu zip file in the phone
How To:
1 - Install adb and fastboot driver (follow THIS guide)
Now you can connect the phone to your computer​2 - Reboot in fastboot mode with one of the following method:
a -Volume Up while booting up​b -With adb, after enabling USB debugging in developer settings, using:
Code:
adb reboot bootloader
Now that you are in bootloader, you have to boot in TWRP,
download THIS recovery (is the twrp one) and boot in to it, using this command:
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
Code:
fastboot boot TWRP-x-x-x-x.img
(Obviusly the recovery name must be the one you downloaded)
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
It should automaticaly enter in recovery.
Now you MUST flash FIRST ZE500KL_BootloaderUnlock.zip, otherwise you'll brick your phone
Btw, the recovery will mount your phone's memory, so you can put now the files in the phone, if you forgot to do it before​
AFTER you installed the unlocker zip, you can install the SuperSu zip
When the install is complete, clear the cache and reboot your phone, now you can enjoy your root!
Downloads:
Latest @MiauLightouch TWRP - 3.0.0.2 Mirror
Latest SuperSu zip - 2.65 Mirror
Bootloader Unlocker (from @MiauLightouch original post) - Mirror
Credits:
@MiauLightouch for pretty much everything
@LuK1337 , @luca020400 and everyone on #titandev for being awesome

So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?

MuzgontarAco said:
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
Click to expand...
Click to collapse
I would recommend Z00L/T, you will get cm13, official unlock at least.

You Say " May Work On ZE500KG" Is ze500kg already receive Marshmallow Update?

MiauLightouch said:
I would recommend Z00L/T, you will get cm13, official unlock at least.
Click to expand...
Click to collapse
thanks for the advice but my choices are poor with about 5 phones in this price range with this one looking waay better.. getting it via contract so yeah..

How to install supersu zip? Tia.

Working! Have you tried to flash Viper4Android? On lollipop this will break Call recording and FM Radio, maybe this will not be a problem on MM?

Seanjhon027 said:
How to install supersu zip? Tia.
Click to expand...
Click to collapse
Inside TWRP there is a big "Install" button, press it and select the zip

what is the meaning of booted

mohamedelkholy said:
what is the meaning of booted
Click to expand...
Click to collapse
context?

until you saw the lock screen, that's what "booted".

stuck waiting for device
C:\Users\Clynt\Desktop\Android M>adb reboot bootloader
C:\Users\Clynt\Desktop\Android M>fastboot boot twrp.img
< waiting for device >
Ok I don't know where I get wrong but I got this error.
Img file name is ok because I renamed it.
Drivers were installed already.
Developers mode is enabled already.
Windows 7 64bit
Tried rooting this using lollipop and everything went well.
thanks!
UPDATE: i got it. it has something to do with the drivers.

Without opening the bootloader.
Notice. I have not tried it.
http://www.asus-zenfone.com/2016/05/how-to-root-asus-zenfone-2-laser-ze50kl-marshmallow.html?m=1

thanl you man i have rooted my zenfone 2 laser

Thanks very much for this guide and your work.

Can I install the new update v13.10.7.1 when I opened bootloader.

The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia

thanks
thks TS
now my phone its rooted

Muminek111 said:
Without opening the bootloader.
Notice. I have not tried it.
No... when trace a perequisite link Given..
you really need to unlock bootloader first
wulfe13 said:
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
Click to expand...
Click to collapse
i think isnt permanent, this step is needed to boot into twrp then flashing a unlockBL..
to make permanent.. the command must "fastboot flash recovery twrp_X.X.X.X.img"
but make sure to unlock bootloader first...
CMIIW
Click to expand...
Click to collapse

Is it me or everytime I reboot the device after rooted, it's going back to unrooted?
Root is a success tho, great job, OP!
Edit: okay, not every reboot, but after several reboots, then it went back unrooted

[Pie/Oreo/Nougat] How to root your Z2 [ALL]

Since no guide has been updated with information on official TWRP for root and backup reasons, I thought I'd create one.
DISCLAIMER:
To do this method requires you to unlock your bootloader. Your warranty is now void. This method assumes you have basic knowledge of ADB and Fastboot commands and know how to recover your device if you accidentally type a wrong command and now boot to TWRP and can't boot to system. If you cannot recover from this, Read up on guides to "return to stock" and familiarize yourself on how to recover your device should something go wrong.
There are two methods for root. You can flash TWRP to your boot image to be able to reboot to TWRP without a PC, or just a temp boot so you can just have root and not TWRP. I'll put in brackets the minor differences.
1: Get ready
Download latest build of TWRP img file from their website.(Previous link is to their instructions and device specific patches, download page is HERE.) {download the latest zip if you want to flash TWRP}
Download what you want on your phone (SU, Magisk, etc)
2:
Hook phone up to your PC, be sure you have latest adb/fastboot drivers. (I do not support windows related questions. If you have latest drivers, you'll have no issue with the below commands, Linux just works for this kind of thing)
3:
Navigate to your directory that has that img downloaded. (windows, shift right click and say "open command prompt here")
Type the below commands, and terminal output should be similar: (I.E. this is a copy/paste of terminal)
Main thing to remember is "Fastboot boot {filename}.img"
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot boot twrp-3.2.1-1-nash.img
downloading 'boot.img'...
OKAY [ 0.841s]
booting...
OKAY [ 5.135s]
finished. total time: 5.976s
[email protected]:~/Downloads$
BE SURE TO DO BOOT AND NOT FLASH!!! (If you ask why you can no longer boot to system, I'll let you know you missed this line.)
5:
You're now in TWRP!
It will ask you for your password. This is your PIN or password to unlock your phone. Enter it.
TWRP has now decrypted your storage to read the zip file(s) you put on your phone!
Go to install and navigate to your directory where you put that file
Install Magisk/SU/TWRP/whatever you please.
(Note: some root zips require a factory reset)
6:
Reboot!
You're Done congratulations!
Attached are images if they help you see you're doing the right thing.
Special thanks @erfanoabdi @invisiblek @npjohnson @joemossjr @jbats
Without the above people a lot of what's above woudn't have been possible for this device specifically. Also, thanks to everyone who pitched in to get a device over to invisiblek. Leaps and bounds have been done since that donation. And thanks to the other devs who have invested in this phone and their time to help out.
(Quoted from Nathan Chance)
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.

Random issues post:
SU does some wonky edits to the ramdisk. It is highly suggested to flash Magisk for root.
Some have reported needing to wipe data after flashing Magisk. If you can't boot after flashing Magisk, just go back into recovery (can be twrp or stock) and wipe data/factory reset to boot again.

Note: we do not have a recovery partition. Never flash the img file! Download the flashable zip if you want twrp on your phone and flash per OP instructions.

Awesome thanks

I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo

droidgreg said:
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
Click to expand...
Click to collapse
Be sure to mount system under the "mount" button

I need the OCX27.1 oreo. I did a return to stock flashall to OCX27 and now reflashed TWRP and Magisk and boots fine but I lost baseband and IMEI

Added warning to OP that some root zips require a data wipe.

I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.

will4958 said:
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
Click to expand...
Click to collapse
This guide assumes you can unlock your bootloader. Since Verizon and AT&T feel they have a right to lock down their devices, this guide won't work. That is why I voted with my wallet and left Vz after my M7 due to them putting phone OEM's privates in a vice and forced them to lock out those carrier variants.

Has this method been tested with OCX27.1 Oreo on TMO?

droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
It probably hasn't been tested, but it should work in theory.

Uzephi said:
It probably hasn't been tested, but it should work in theory.
Click to expand...
Click to collapse
I was on 27.1 when I attempted to root and got into a bootloop and lost my baseband when I flashall back to stock OCX27. I have a feeling 27.1 update isn't compatible with this method and cannot be downgraded to even OCX 27 Oreo

so no go on 27.1 twrp? I have root on 27.1 TMO obtained post update. Obtained by fastbooting the nash twrp and running magisk 16.zip. No needing to format data or anything
I was just wondering about the installable twrp zip. I am coming from samsung development so all this A/B partitioning and some of the other partitions are new to me.
As soon as I can get twrp on the phone and feel comfortable recovering. The kernels and roms will start coming.
Feels strange not having odin to save my ass

droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
tested and working

mattlowry said:
tested and working
Click to expand...
Click to collapse
Have you actually flashed installer.zip to install TWRP or just booted TWRP and only flash magisk or SU for root without installing TWRP?

I fastboot booted the twrp. I didn't try the installer. What is it?

Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.

luponcooper said:
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
Click to expand...
Click to collapse
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).

Uzephi said:
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Click to expand...
Click to collapse
Thanks a lot uzephi for answering.
I have the 6gb ram and 64gb model, XT1789-05. I try whit no succes to install Magisk (Error1) so i made a factory reset but still doesn't boot, stays in M logo.
Im super noob, can you guide me? i dont know how to recover the boot.img.
excuse my english.

Stock Owens XT1775, just got notice update is ready to install - root first or after?

Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?

jdsmn21 said:
Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
Click to expand...
Click to collapse
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.

You do not want to root first. Update then root as doing an ota while rooted may loose your root status or worse!

Goose03 said:
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
Click to expand...
Click to collapse
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??

jdsmn21 said:
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
Click to expand...
Click to collapse
Np. Take your time. Thanks. Yes, that is what you do to unlock. Then for flashing twrp it's like you have but make sure to match the last part "recovery.img" to whatever the recovery is named. If your recovery is named twrp.img the command is:
fastboot flash recovery twrp.img

If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334

koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?

jdsmn21 said:
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
Click to expand...
Click to collapse
Phh SU is not needed since Magisk gives you all the necessary root and features. dmnoverity is not needed. I recommend you allow twrp system write access.

koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?

jdsmn21 said:
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
Click to expand...
Click to collapse
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs

Goose03 said:
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?

jdsmn21 said:
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
Click to expand...
Click to collapse
It is not normal to have it boot straight to twrp or the bootloader rather than the rom unless you do so manually.
Have you triedbplaying with the settings in Magisk Manager? There is an option to hide Magisk from your choice of apps. There is also a couple other options in the settings to hide things as much as possible. If you have Xposed installed it won't pass a safteynet check.
Sent from my Moto E (4) Plus using XDA Labs

XT1775 rom's is possible install on XT1776 ?

almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
You could. I've flashed xt1775 firmware to my xt1776 to get a backup of the system to make a twrp flashable from. I don't recommend it, but if you only flash the system and not the modem and oem it should provision data services. Why do you ask exactly?
Sent from my Moto E (4) Plus using XDA Labs