Database Users

Can an ota zip be flashed via twrp or cwm?

Ok so basically my question is can twrp or cwm flash an ota update.zip? I'd like to remove a couple things from the kk ota. Zip and flash via cwm or twrp If possible....
Tapatalk'n it from my XT907 (MoKee 4.4.4) on Page Plus Cellular.

thewraith420 said:
Ok so basically my question is can twrp or cwm flash an ota update.zip? I'd like to remove a couple things from the kk ota. Zip and flash via cwm or twrp If possible....
Tapatalk'n it from my XT907 (MoKee 4.4.4) on Page Plus Cellular.
Click to expand...
Click to collapse
As long as you have root and an unlocked bootloader, everything should be fine. Since you're on KitKat, root your phone with towelroot and unlock your device with motopocalypse.
Edit: oops! I though you were talking about something else (I need to get some sleep.) Custom recoveries does not flash ota updates. Are you trying to remove bloatware?

Nah I was just looking at the zip and noticed the radio from the zip used a series of patches to bring the modem partition up to date and I wanted to try and apply it over my working ics radio on Page Plus in hopes it could stick the flash. Tz and gpt wouldn't be able to flash anyway though since they can't be downgraded I was going to remove them from the zip. This would make the signature mismatch so I hoped twrp or cwm could flash it
Tapatalk'n it from my XT907 (MoKee 4.4.4) on Page Plus Cellular.

thewraith420 said:
Nah I was just looking at the zip and noticed the radio from the zip used a series of patches to bring the modem partition up to date and I wanted to try and apply it over my working ics radio on Page Plus in hopes it could stick the flash. Tz and gpt wouldn't be able to flash anyway though since they can't be downgraded I was going to remove them from the zip. This would make the signature mismatch so I hoped twrp or cwm could flash it
Tapatalk'n it from my XT907 (MoKee 4.4.4) on Page Plus Cellular.
Click to expand...
Click to collapse
Probably the best bet would be to modify the FXZ xml file to only include what you would like to flash, but this has potential to go bad fast.
EDIT: You could reference these files to see how to edit them... but I probably wouldn't flash these files, because I don't know if they are compatible with xt907. http://forum.xda-developers.com/showthread.php?t=2022296

5.0.1 OTA for ROOTED Shield Tablets (DL Provided)

***For US LTE Tablet***
Here is a .zip you can flash to update to 5.0.1 from 5.0. The OTA was pulled from my device which I factory reset to 4.4.4. It will remove root and it will reflash the stock recovery, but it will NOT relock your bootloader. Make backups! Flash at your own risk! I am not responsible for any damage that occurs.
The reason why the new 5.0.1 OTA does not flash for rooted users is a sha1 hash is generated from the system partition. If it doesn't match what the hash should be from the factory, it fails out. Removing these checks will break your device because of the new differential update method employed, which is why these sha1 hashes are so important. The .zip I have is a standard update (not differential) and can be flashed with any recovery you want
Here is a link:
https://drive.google.com/file/d/0B_iRndxSfhpXRjBXY3FXUG1tNDA/view?usp=sharing

Thanks for your explanation! Any chance for providing the same zip for eu lte?

So is this a modified zip or is it just the full version from nvidia's server?

The rest of the world - LTE - version of the 5.0.1 update is here:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29082_493.9700.zip
Flashed fine with ClockworkMod Recovery.
If you were rooted, you need to re-root afterwards.

any zip for wifi only tablet?

Adrixan said:
The rest of the world version of the 5.0.1 update is here:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29082_493.9700.zip
Flashed fine with ClockworkMod Recovery.
If you were rooted, you need to re-root afterwards.
Click to expand...
Click to collapse
I need a little help how to flash via CWM and if i flash it will my data be erased? Plus how to reroot once i update? I have root and unlocked bootloader running 5.0

What do you have to do to root after installing this?

RollWii said:
I need a little help how to flash via CWM and if i flash it will my data be erased? Plus how to reroot once i update? I have root and unlocked bootloader running 5.0
Click to expand...
Click to collapse
It did not reset my tablet, just like an OTA update should.
You will lose root and the custom recovery though.
To get it back, just follow the fine guide in the forum again: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
TheCrowing said:
What do you have to do to root after installing this?
Click to expand...
Click to collapse
You just have to reinstall the custom recovery as detailed in the forum thread: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064 and from there flash SuperSU again.

Adrixan said:
It did not reset my tablet, just like an OTA update should.
You will lose root and the custom recovery though.
To get it back, just follow the fine guide in the forum again: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
You just have to reinstall the custom recovery as detailed in the forum thread: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064 and from there flash SuperSU again.
Click to expand...
Click to collapse
So basically all i need to do is
1) install cwm again since i updated to lollipop and have root
2) downlaod the update and install via cwm
3) reroot using the root.img etc etc and flash super su etc etc
4) reinstall cwm
Am i going the right path?

RollWii said:
So basically all i need to do is
1) install cwm again since i updated to lollipop and have root
2) downlaod the update and install via cwm
3) reroot using the root.img etc etc and flash super su etc etc
4) reinstall cwm
Am i going the right path?
Click to expand...
Click to collapse
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1

Adrixan said:
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Click to expand...
Click to collapse
Ok so its the same process like when i updated from kitkat to lollipop. One last question do i need to use the boot.img again?

RollWii said:
Ok so its the same process like when i updated from kitkat to lollipop. One last question do i need to use the boot.img again?
Click to expand...
Click to collapse
I never came into a situation, where i had to use some extra boot.img.
When I got my shield recently, I directly updated to 5.0 before rooting and only did the update to 5.0.1 with a previously rooted device.
So, I'd assume, if you are on 5.0 rooted, my instructions should work for you.
And careful, as mentioned above, my link is for the Rest of the world LTE version! (not us!)

Adrixan said:
I never came into a situation, where i had to use some extra boot.img.
When I got my shield recently, I directly updated to 5.0 before rooting and only did the update to 5.0.1 with a previously rooted device.
So, I'd assume, if you are on 5.0 rooted, my instructions should work for you.
And careful, as mentioned above, my link is for the Rest of the world LTE version! (not us!)
Click to expand...
Click to collapse
Oh good that you mentionedim using US Unlocked LTE so your file wont work on mine?

RollWii said:
Oh good that you mentionedim using US Unlocked LTE so your file wont work on mine?
Click to expand...
Click to collapse
No, but the File from the guy, who started this thread should work for the U.S. LTE version following the same instructions as I just gave.

How long should it be sitting at the NVIDIA screen after flashing the update?
It went after a couple minutes.

Adrixan said:
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Click to expand...
Click to collapse
sorry but i forgot how to flash the SUperSU update.zip how and where can i find it again?

New Factory Image and Custom Recovery

So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?

geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess

MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.

bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr

Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...

MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.

geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.

MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.

I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img

Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.

mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????

mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?

rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.

In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.

mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.

[ROOT] Root for Stock MRA58N (System/Systemless) (Wi-Fi/LTE)

The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.

When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?

Are the attached zip files for the wifi model only?

I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?

Jeltel said:
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Click to expand...
Click to collapse
You can revert to stock boot and stock recovery to apply OTA
corkiejp said:
Are the attached zip files for the wifi model only?
Click to expand...
Click to collapse
Yes, I can make a LTE compatible version though.
sejmand said:
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Click to expand...
Click to collapse
Yes, and yes

topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Yes, I can make a LTE compatible version though.
Yes, and yes
Click to expand...
Click to collapse
A LTE compatible version would be great!!!

topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Click to expand...
Click to collapse
So that's a no

I flashed factory image MRA58N (system gets encrypted, because it wasn't under MRA58K)
then twrp
then systemless-root (boot.img)
then superuser 2.56.....
EVERYTHING WORKS FINE:
encrypted with root!

how to flash boot.img (command for flashing)
topjohnwu said:
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
how to flash boot.img for system less (partition ?)

Lightnyboy said:
how to flash boot.img for system less (partition ?)
Click to expand...
Click to collapse
Unzip systemless-root.zip which will give you a "boot.img" file.
Then while in fastboot
"fastboot flash boot boot.img"
Anyone have the boot files for LTE yet?

Nice. Could you add the link to CF original post in systemless root.

thebrainkafka said:
Nice. Could you add the link to CF original post in systemless root.
Click to expand...
Click to collapse
topjohnwu said:
[*]Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
[*]Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
Already linked? Click on "this thread" above!

Updated for LTE... Sorry for the late update.

Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow

topjohnwu said:
Updated for LTE... Sorry for the late update.
Click to expand...
Click to collapse
Thanks for the modified boot images for LTE, I linked back here from my thread in Q&A forum.

have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?

madbat99 said:
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
Click to expand...
Click to collapse
I haven't run N version yet as my N9 is finally working without lags/reboots. But, the lure of the close all recent apps button (and very successful experience with xposed/gravity box on N5 after a year) in GB was too great. It works beautifully!
This may seem off-topic, but since root is required, maybe readers can allow exception.
Sent from my Nexus 9 using Tapatalk

chesterchen said:
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
Click to expand...
Click to collapse
You don't need to extract twrp.img, you should flash the full image "twrp-2.8.7.1-flounder.img".
That version should not ask for PIN anymore.
Note: system-less is still experimental

If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!

maximumentropy said:
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
Click to expand...
Click to collapse
Reflash the stock image then you're good

New ZE551KL locked bootloader/no root MM

Hi,
I've just got a new ZE551KL (z00td) with a locked bootloader and no root. Since the phone have the latest android 6.0.1 build I have difficulty to root it and unlock the bootloader. I did many research and I think it's really confusing. It seem to root my phone I need an unlocked bootloader but to unlock it I have to root my phone. The last interesting thing I've found for my phone is to flash a pre-rooted system.img & boot.img ( http://www.asus.com/zentalk/thread-80274-1-1.html ) but I also get stuck here since the guide tell me to flash both and I can only find the system.img.
I would like to know if there's any guide to root & unlock my bootloader on my ZE551KL. Thanks a lot!

It's a pain, but you may have to roll back to an earlier version of the firmware...back to lollipop. There are instructions in one of the threads on how to do that. I was able to unlock before the marshmallow update with the official unlock utility from Asus. Once you are unlocked, the easiest way to root is just to either boot twrp.img (previously downloaded and extracted to the adb folderon your computer) using fastboot (lots of threads here with instructions, too) and install supersu.zip. Or if you want to install twrp as your recovery, you can flash it from fastboot, then flash the zip of supersu. If you need more help, I am no expert by any means, but I have done this with my own ze551kl and might be able to give you some more hints.
Personally I would avoid the prerooted images as I had a lot of trouble with them and nearly bricked my phone by trying them out.

Thanks a lot for your reply! That's what I'm trying right now. I'm rolling back to lollipop from an official rom file from asus website. So far, I tried to flash it with stock recovery but it said that I cannot install a older version on top of a newer one. I did an downgrade of the recovery and now I'm waiting for the flash.

cilk said:
Thanks a lot for your reply! That's what I'm trying right now. I'm rolling back to lollipop from an official rom file from asus website. So far, I tried to flash it with stock recovery but it said that I cannot install a older version on top of a newer one. I did an downgrade of the recovery and now I'm waiting for the flash.
Click to expand...
Click to collapse
Excuse me, how did you do the downgrade of the recovery? Can you share the .img with me? I have TWRP installed with locked bootloader

I've found older stock recovery on this site : https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
Credit to ThanveerAliSayed in XDA

Well it seem that I cannot downgrade, the latest recovery don't want to install a lower version and when I try to get a older stock recovery I still cannot downgrade since it get stuck at verifying image update package.
Also I've noticed that my version is 21.40.1220.1698 and so far I can't find anything related to this version for rooting or unlocking bootloader. Even the official firmware on asus website for the ZE551KL is older than this version and I couldn't flash it. I had to get it from https://asus.kremowka.xyz/categories/show/2 because I've soft bricked my device. I'm still trying to find a solution...

cilk said:
I've found older stock recovery on this site : https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
Credit to ThanveerAliSayed in XDA
Click to expand...
Click to collapse
I would NOT use this stock image for ze551kl. There is one for the 601 and the 550 but not 551kl. I will find the thread with the first stock recovery posted that I used and post the link in a while. Give me a chance to find it. I would roll back to it, then upgrade to the stock firmware listed in the unlocker notes. Once it's unlocked, you can go to the last lollipop before marshmallow and flash it. I would then factory reset, then flash marshmallow. After you have it working, then flash twrp (or just boot it in adb) as I said above and flash supersu.
I will warn you that a lot of people have had trouble unlocking and this might not work to unlock.
---------- Post added at 09:09 PM ---------- Previous post was at 08:55 PM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=3585486&d=1450811354 here is the link to stock for the very first stock firmware. I followed a video posted on YouTube from "themobileshots" on returning to stock from cm13. I doubt you can flash the stock recovery without flashing twrp first, then flashing from there. There are a lot of people in this forum that can help and most are pretty patient. Don't give up.

Finally I got my phone unlocked and rooted and it was too easy ...
I used fastboot to flash TWRP ( http://forum.xda-developers.com/zen...e601kl-official-marshmallow-wwv21-40-t3424903 ) and after that I flashed the latest CM13 from TWRP to gain root and unlocked my bootloader with this guide http://forum.xda-developers.com/zen...de-unlock-bootloader-asus-unlock-app-t3405850
I never though I could flash TWRP with a locked bootloader but it worked very well.

cilk said:
Finally I got my phone unlocked and rooted and it was too easy ...
I used fastboot to flash TWRP ( http://forum.xda-developers.com/zen...e601kl-official-marshmallow-wwv21-40-t3424903 ) and after that I flashed the latest CM13 from TWRP to gain root and unlocked my bootloader with this guide http://forum.xda-developers.com/zen...de-unlock-bootloader-asus-unlock-app-t3405850
I never though I could flash TWRP with a locked bootloader but it worked very well.
Click to expand...
Click to collapse
Well, I have TWRP with locked bootloader and tried to unlock the bootloader with that guide in CM13. I didn't work for me
long2ski said:
I would NOT use this stock image for ze551kl. There is one for the 601 and the 550 but not 551kl. I will find the thread with the first stock recovery posted that I used and post the link in a while. Give me a chance to find it. I would roll back to it, then upgrade to the stock firmware listed in the unlocker notes. Once it's unlocked, you can go to the last lollipop before marshmallow and flash it. I would then factory reset, then flash marshmallow. After you have it working, then flash twrp (or just boot it in adb) as I said above and flash supersu.
I will warn you that a lot of people have had trouble unlocking and this might not work to unlock.
---------- Post added at 09:09 PM ---------- Previous post was at 08:55 PM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=3585486&d=1450811354 here is the link to stock for the very first stock firmware. I followed a video posted on YouTube from "themobileshots" on returning to stock from cm13. I doubt you can flash the stock recovery without flashing twrp first, then flashing from there. There are a lot of people in this forum that can help and most are pretty patient. Don't give up.
Click to expand...
Click to collapse
I tried to do a lot of things to get back to Stock ROM but they didn't work. I watched that tutorial but the files belongs to ZE550kl, so any other ideas? :crying:

niveku said:
Well, I have TWRP with locked bootloader and tried to unlock the bootloader with that guide in CM13. I didn't work for me
Click to expand...
Click to collapse
Me too the first time I tried to unlock my bootloader in CM13 it didn't worked. I followed the guide and I did this :
Phone connected to the computer with USB debug and using ADB :
Code:
adb shell
su
Then I followed the backup procedure and I did the magic command to unlock it :
Code:
echo -ne "\x01" | dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo
After I rebooted in fastboot so see if my device was unlocked but no it was still lock. I did two adb reboot with these command :
Code:
fastboot oem adb_enable
fastboot oem adb_enable
You have to do these twice.
After this my bootloader was still locked but I did a normal reboot and tried the magic command and voila! Bootloader unlocked.
niveku said:
I tried to do a lot of things to get back to Stock ROM but they didn't work. I watched that tutorial but the files belongs to ZE550kl, so any other ideas? :crying:
Click to expand...
Click to collapse
If you have the ZE551KL like me you have to use file for a Z00T. You can check this page to know which device is a Z00T : http://forum.xda-developers.com/zenfone-2-laser/general/index-zenfone-2-laser-variants-t3369569
In my case I also had some difficulty to go back to Stock since I couldn't find the right firmware for mine because my android version is 21.40.1220.1698 and you have to flash the same version. The only place I found it was there https://asus.kremowka.xyz/categories/show/2 under the ZE601KL

cilk said:
In my case I also had some difficulty to go back to Stock since I couldn't find the right firmware for mine because my android version is 21.40.1220.1698 and you have to flash the same version. The only place I found it was there https://asus.kremowka.xyz/categories/show/2 under the ZE601KL
Click to expand...
Click to collapse
i see there is a mm unlock apk for the ze601kl there also...i wonder if that would work on the ze551kl.

niveku said:
Well, I have TWRP with locked bootloader and tried to unlock the bootloader with that guide in CM13. I didn't work for me
I tried to do a lot of things to get back to Stock ROM but they didn't work. I watched that tutorial but the files belongs to ZE550kl, so any other ideas? :crying:
Click to expand...
Click to collapse
The video is for the 550 but the process is the same for the 551kl (zootd). I downloaded the stock firmware at the bottom of the page on the Asus support page https://www.asus.com/support/Download/39/1/0/23/SZCx58yhB5Jst0yI/32/ , extracted it, grabbed the boot.IMG from there and put it on my memory card along with the stock recovery from the link above (renamed it recovery.img) and the full firmware (drag the original, leave it zipped). Then I did as the video says and wiped in twrp, flashed the boot and recovery, wiped cache, then flashed the firmware. It took awhile for the process to complete. Hope this helps.

cilk said:
Code:
fastboot oem adb_enable
fastboot oem adb_enable
You have to do these twice.
After this my bootloader was still locked but I did a normal reboot and tried the magic command and voila! Bootloader unlocked.
If you have the ZE551KL like me you have to use file for a Z00T. You can check this page to know which device is a Z00T : http://forum.xda-developers.com/zenfone-2-laser/general/index-zenfone-2-laser-variants-t3369569
Click to expand...
Click to collapse
Well, somehow that worked! Thanks, you should make a new post as a tutorial, I'm sure people will find that usefull.
Edit: Has someone rooted stock MM?

niveku said:
Well, somehow that worked! Thanks, you should make a new post as a tutorial, I'm sure people will find that usefull.
Edit: Has someone rooted stock MM?
Click to expand...
Click to collapse
Yes I'm currently writing one
For the stock MM yep I did it. I just installed the stock one after my bootloader was unlock and followed a tutorial here for root. I really like the stock Asus, way better than the samsung with touchwiz in my opinion.

beenkenobee said:
i see there is a mm unlock apk for the ze601kl there also...i wonder if that would work on the ze551kl.
Click to expand...
Click to collapse
So, to recap. If you are at the latest update, and have never previously unlocked bootloader or rooted your phone. The ASUS provided unlock tool won't work on the latest update. With it locked you can't install custom recovery or downgrade the firmware to an older version so that you can unlock it. Catch 22. Screwed until ASUS releases an update to their unlock tool or someone figures something else out. Or am I missing something? Cause I've been trying to do something with my kids phone for two days now and no luck here doing anything. Bout 8 million guides and files around the net and none of em seem to do squat in my situation. Any comments? Let's hear em.
waltsmith

beenkenobee said:
i see there is a mm unlock apk for the ze601kl there also...i wonder if that would work on the ze551kl.
Click to expand...
Click to collapse
great find I was able to unlock my ZE551KL MM with that tool

steadydecline said:
great find I was able to unlock my ZE551KL MM with that tool
Click to expand...
Click to collapse
it really worked?
cool!
no hiccups or problems?