I have discovered multiple ways of downgrading ZenFone 2 Laser out of which two methods proved out to be easy and reliable. Both methods have been tested and are working.
Method 2 doesn't require root while method 1 needs root access.
Pre-requisite: Stock firmware zip file. You can find download links from index thread for all variants.
WHILE THIS GUIDE HAS VERY LESS CHANCES OF MESSING UP YOUR DEVICE, HUMAN ERROR CAN ANYWAY HARM THE DEVICE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO ANY DEVICE. YOU ARE DOING THIS AT YOUR OWN RISK
METHOD 1: Requires ROOT-
Short instruction:
Some users say you can downgrade by renaming the OTA zip to correspond to a higher version but that will NEVER work because the update script has this line
(!less_than_int(1457089250, getprop("ro.build.date.utc"))) || abort("Can't install this package (Fri Mar 4 19:00:50 CST 2016) over newer build (" + getprop("ro.build.date") + ").");
Click to expand...
Click to collapse
The recovery reads ro.buid.date.utc value from buid.prop. If the value is less than the value in updater-script (like the value highligted in above quote) any recovery will not flash it, neither stock nor custom. Just increaase the value of ro.build.date.utc (in build.prop) to any value higher than the value in updater-script and then flash the zip via recovery.
Detailed Instructions:
1. Open updater-script from the firmware zip. It will be found in /META-INF/com/google/android inside the .zip
2. look at the first line (!less_than_int(1457089250, getprop("ro.bui....
3. The value 1457089250 is taken as an example, your updater-script may have a different value. Keep a note of this value.
4. Install any root file manager like ES file explorer (if you dont have already)
5. Goto /system (the system folder) using the root file manager. Grant root access if prompted
6. Open buid.prop file as text and look for the line "ro.build.date.utc=1446585430"
1446585430 is taken as example, your phone will have a different value.
7. Now increase this value in build.prop to any number greater than the value you noted from updater-script
for example, if my updater-script has 1457089250 this value and buil.prop has 1446585430 this value, I will simply change the value in build.prop to 1546585430 or 1448585430 or 1457089251. Any number greater than 1457089250 will work in my case.
8. Now reboot to recovery (vol down + power)
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Method 2: Without root, requires computer
Short instructions:
As I mentioned earlier, recovery reads "ro.build.date.utc" But you can bypass this check by erasing system partition.
Just do
Code:
fastboot erase system
from fastboot mode and then flash the zip from recovery
Detailed Instructions:
1. Install Asus drivers to your computer. (link in index thread)
2. Download adb_fastboot.zip and extract its contents
3. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold "volume down Up" button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
4. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
5. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
6. On command prompt type
Code:
fastboot devices
and hit enter
and check if it is detecting your device.
7. Then type
Code:
fastboot erase system
(this will erase your current OS, you are warned!)
8. After it is done type
Code:
fastboot oem reboot-recovery
to boot into recovery mode
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Successfully downgraded to 1.16.40.763 from 1.17.40.1234 without root
Thanks!
sziraqui said:
I have discovered multiple ways of downgrading ZenFone 2 Laser out of which two methods proved out to be easy and reliable. Both methods have been tested and are working.
Method 2 doesn't require root while method 1 needs root access.
Pre-requisite: Stock firmware zip file. You can find download links from index thread for all variants.
WHILE THIS GUIDE HAS VERY LESS CHANCES OF MESSING UP YOUR DEVICE, HUMAN ERROR CAN ANYWAY HARM THE DEVICE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO ANY DEVICE. YOU ARE DOING THIS AT YOUR OWN RISK
METHOD 1: Requires ROOT-
Short instruction:
Some users say you can downgrade by renaming the OTA zip to correspond to a higher version but that will NEVER work because the update script has this line
The recovery reads ro.buid.date.utc value from buid.prop. If the value is less than the value in updater-script (like the value highligted in above quote) any recovery will not flash it, neither stock nor custom. Just increaase the value of ro.build.date.utc (in build.prop) to any value higher than the value in updater-script and then flash the zip via recovery.
Detailed Instructions:
1. Open updater-script from the firmware zip. It will be found in /META-INF/com/google/android inside the .zip
2. look at the first line (!less_than_int(1457089250, getprop("ro.bui....
3. The value 1457089250 is taken as an example, your updater-script may have a different value. Keep a note of this value.
4. Install any root file manager like ES file explorer (if you dont have already)
5. Goto /system (the system folder) using the root file manager. Grant root access if prompted
6. Open buid.prop file as text and look for the line "ro.build.date.utc=1446585430"
1446585430 is taken as example, your phone will have a different value.
7. Now increase this value in build.prop to any number greater than the value you noted from updater-script
for example, if my updater-script has 1457089250 this value and buil.prop has 1446585430 this value, I will simply change the value in build.prop to 1546585430 or 1448585430 or 1457089251. Any number greater than 1457089250 will work in my case.
8. Now reboot to recovery (vol down + power)
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Method 2: Without root, requires computer
Short instructions:
As I mentioned earlier, recovery reads "ro.build.date.utc" But you can bypass this check by erasing system partition.
Just do
Code:
fastboot erase system
from fastboot mode and then flash the zip from recovery
Detailed Instructions:
1. Install Asus drivers to your computer. (link in index thread)
2. Download adb_fastboot.zip and extract its contents
3. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
4. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
5. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
6. On command prompt type
Code:
fastboot devices
and hit enter
and check if it is detecting your device.
7. Then type
Code:
fastboot erase system
(this will erase your current OS, you are warned!)
8. After it is done type
Code:
fastboot oem reboot-recovery
to boot into recovery mode
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Click to expand...
Click to collapse
Currently iam on marshmallow. My phone is zenfone laser 550kl. Iam having some problems with the marshmallow recovery because of that when doing apply update from sd card it is resulting an error.
Failed to mount/asdf.
So i like to flash the lolipop recovery while iam on the marshmallow and then do apply update from sd card. I like to go back to the 1.13 lolipop firmware
Is it possible to to flash the lolipop recovery while iam on marshmallow. If possible. Help me how to do that
ThanveerAliSayed said:
Currently iam on marshmallow. My phone is zenfone laser 550kl. Iam having some problems with the marshmallow recovery because of that when doing apply update from sd card it is resulting an error.
Failed to mount/asdf.
So i like to flash the lolipop recovery while iam on the marshmallow and then do apply update from sd card. I like to go back to the 1.13 lolipop firmware
Is it possible to to flash the lolipop recovery while iam on marshmallow. If possible. Help me how to do that
Click to expand...
Click to collapse
"Failed to mount /asdf" error is harmless you will get that error even on latest twrp. You can ignore the error and use the MM stock recovery like normal. Recovery will do its job it can format, install updates, clear cache and everything, you just need to ignore that /asdf error
But you can use any stock recovery from any firmware version lower than or equal to your current firmware version. Drawbacks: You cannot apply update to MM OTAs if your recovery version doesn't match the current firmware version.
Going back to stock 1.13 is a bad idea. I would recommend you to stay on MM since it has many performance improvements.
But still if you want to go back to lollipop, consider downgrading to the last lollipop update i.e. v1.17.40.1531
Xda Tips: 1. Never quote the entire OP (the main post here, called original post)
2. Don't say thanks, instead hit the :good: button
3. Use "Post Reply" option on top if you want to reply to a post. Use @username to gain attention of a user
sziraqui said:
"Failed to mount /asdf" error is harmless you will get that error even on latest twrp. You can ignore the error and use the MM stock recovery like normal. Recovery will do its job it can format, install updates, clear cache and everything, you just need to ignore that /asdf error
But you can use any stock recovery from any firmware version lower than or equal to your current firmware version. Drawbacks: You cannot apply update to MM OTAs if your recovery version doesn't match the current firmware version.
Going back to stock 1.13 is a bad idea. I would recommend you to stay on MM since it has many performance improvements.
But still if you want to go back to lollipop, consider downgrading to the last lollipop update i.e. v1.17.40.1531
Xda Tips: 1. Never quote the entire OP (the main post here, called original post)
2. Don't say thanks, instead hit the :good: button
3. Use "Post Reply" option on top if you want to reply to a post. Use @username to gain attention of a user
Click to expand...
Click to collapse
I got a 412 mb ota update some days before. I downloaded it. Apply it for proceed. Then it start checking system as usual phone restarted. But update did not happened. Instead this same error show up. Then i can only reboot system. Got an update failed message.since that when i check for updates iam not even getting any. May be it will be solved by a factory reset .but even if i get an ota. The update wont proceed .because the recovery wont allow me to do that
And also that wipe cache partition also results the same error .so without solving this error i cant update to the latest MM too :/ .
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Flash that recovery with fastboot
Wipe /system in fastboot
Reboot to recovery and update with the stock ROM .zip
Or
Even easier, use Sziraqui's fastboot ready .IMG files and just flash them via fastboot.:good:
where can i find the recovery file in Stock rom
4llerbuntu said:
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Thanks for the Information, Can you please help to find the recovery file in Stock rom.
Click to expand...
Click to collapse
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
4llerbuntu said:
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
Click to expand...
Click to collapse
Hi, I see only boot.img in the zip file. Is there a hidden recovery?
4llerbuntu said:
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
Click to expand...
Click to collapse
I see only boot.img file , i didn't find any recovery.img file, in case if you have already done this probably yes then please share us the steps to get recovery from Stock rom.
4llerbuntu said:
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Flash that recovery with fastboot
Wipe /system in fastboot
Reboot to recovery and update with the stock ROM .zip
Or
Even easier, use Sziraqui's fastboot ready .IMG files and just flash them via fastboot.:good:
Click to expand...
Click to collapse
I cant find any recovery.img in the firmware zip. :/
Can you detaily explain that fastboot method as it is for flashing the lolipop recovery for downgrading to 1.13.
Iam a beginner in android. This is my first android phone.
murat124 said:
Hi, I see only boot.img in the zip file. Is there a hidden recovery?
Click to expand...
Click to collapse
I found out that recovery for each firmware is available here. You should use a desktop browser to use this website.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
ThanveerAliSayed said:
I found out that recovery for each firmware is available here. You should use a desktop browser to use this website.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
Click to expand...
Click to collapse
Thank you.
Can ZE551KL use the recovery.img from ZE550KL? My ZE551KL has the extra 1700(AWS) band.
Please where are you guys downloading your stock rom from?
The stock zip is NOT flash-able like a custom ROM .zip. That's not how it works. If the Roms you have are custom recovery flash-able, they are not the OEM rom, they have been modified.
All the Roms I have come with a recovery.img file...
Then again if I have to explain how to use fast boot to flash the recovery, there is a good chance you shouldn't be messing around with fast boot.......
---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------
murat124 said:
thank you.
Can ze551kl use the recovery.img from ze550kl? My ze551kl has the extra 1700(aws) band.
Click to expand...
Click to collapse
no it cannot. Do not try it
Weird ..... I can find recovery.img
Can anyone explain me detail. How to flash recovery only. My bootloader is not unlocked. Someone said that i need to unlock bootloader to flash the stock recovery
ThanveerAliSayed said:
Can anyone explain me detail. How to flash recovery only. My bootloader is not unlocked. Someone said that i need to unlock bootloader to flash the stock recovery
Click to expand...
Click to collapse
You don't need to unlock bootloader for flashing stock recovery that you downloaded from the above mega drive.
To flash the recovery.img (or any .img) You need to have Adb and fastboot files in your pc as well as Asus Zenfone drivers installed
All info and downloads for adb and fastboot can be found here
Search and download Asus ZenFone 2 laser drivers.
Once you have your pc setup with these tools,
With Administrator priveleges, locate the folder where adb.exe and fastboot.exe files are present. Hold down shift key and right click on that folder and select "open command window here". Then reboot your phone to fastboot mode [power off, hold vol up +power, release power when logo appears]
Connect your device to pc.
Type the following command on cmd
Code:
fastboot devices
Output should be something like this
Code:
FCAHSJSJJAKAK fastboot
This command will check if your device is connected or not
If output is blank, device is not being detected.
To flash recovery.img, copy the recovery.img file to the same folder where fastboot.exe exists and then type
Code:
fastboot flash recovery recovery.img
Output is easy to understand, if it says [OKAY] then flashing succeeded
Tried downgrading ze551kl by fastboot erase system then installing .zip from Asus website (via sdcard). All of the Asus updates except the earliest fail with 'fota return code 403'.
1.14.40.550 installs ok but then boots (gets as far as displaying the wallpaper), gives an error message in german (looks like 'android media process stopped') and goes into boot loop. Anyone seen this before?
Also, any way to build a recovery.img from the Asus update files?
invalid boot image whenever i flashed stock recovery,any one know why ?
What i do is flash the stock recovery and flash relock bootloader.
Leftrand said:
invalid boot image whenever i flashed stock recovery,any one know why ?
What i do is flash the stock recovery and flash relock bootloader.
Click to expand...
Click to collapse
I think OP needs a small correction to enter into FASTBOOT you need to press volume up and power instead of volume down and power buttons
---------- Post added at 05:45 PM ---------- Previous post was at 05:38 PM ----------
Related
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
_______________________________________________________________________________
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Thank you for posting this. I tried three other methods to get root back before this, and none of them worked. This one did the trick without any problems at all. Thanks again!
Wug's Nexus Root Toolkit 1.9.4
kyoshiro22 said:
Wug's Nexus Root Toolkit 1.9.4
Click to expand...
Click to collapse
I know there's Toolkit's out there, but this is for those who choose to take the "Fastboot" approach.
gestevez1213 said:
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP[ - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Click to expand...
Click to collapse
This is NOT working.... I tried it 3 times on 2 devices
papayayoghurt said:
This is NOT working.... I tried it 3 times on 2 devices
Click to expand...
Click to collapse
What part are you stuck at?
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
I used chainfires auto root for the N5 (stock lollipop Boot loader). Worked great. Just download to a PC put phone into boot loader and run the bat file. I can't link but a quick google will find it for you.
Sent from my Nexus 5 using Tapatalk
andrelessa said:
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
Click to expand...
Click to collapse
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Personally, I'm using the autoroot from chainfire. Works like a charm, no custom recovery is needed (I have the stock recovery).
gestevez1213 said:
What part are you stuck at?
Click to expand...
Click to collapse
Everything is working, but then SuperSU can´t find a Binary.
gestevez1213 said:
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Click to expand...
Click to collapse
Yes, I read somewhere that TWRP need this...
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Are you running the official lollipop release? It should work with that. Delete the app, and try again.
Just put your phone in bootloader and run cf-autoroot from windows if you dont want twrp.
I have twrp but its not working like that
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Had the same issue and needed to flash the updated kernel from chainfire : https://www.androidfilehost.com/?fid=95747613655047375
Why are you trying to do this the hard way? Just use chainfire's autoroot.
It works perfect and it's literally one command
fastboot boot CHautoroot.img (or whatever the file name is)
cf-auto-root is the way
I agree, just use cf-auto-root. You should be good to go in no time.
Just for FYI, if you already have unlocked bootloader, it won't wipe your data, if you are concerned.
CF-auto-root roots N5 without modifying your kernel. I believe, if you flash the SuperSU in TWRP, it would modify the kernel. It's nothing bad, but if you want to remain "stock" and don't want to reflash stock ROM later to get the OTA, just use "Full unroot" from SuperSU app and you are stock and ready for next OTA.
I have encrypted the storage on my Nexus 5. Will CF-Auto-Root wipe my storage?
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
I have the same error.
"Cyanogendmod.Org / Install CM for z3c / Unlock Your Xperia Z3 Compact" <--- That's the URL somehow.
Followed this instruction. Got myself the 12.1 .zip and .img.
I get error installaing the .zip and the .img isn't even an option:
The old rom is infinitly loading in that blue/purple wave line.
I then turn the phone off by holding down the power button until the phone restarts.
My history:
>Pressing up and down on the button rockers.
>Cyanogen Recovery starts.
>I choose "Wipe data/factory reset".
>I choose "Apply update".
(Apply from ADB doesn't work as it seems as ADB has no access for USB debugging. That's why install it from an external SD)
>Install "cm-12.1-20160918-NIGHTLY-z3c.zip" or its copy that I named "update.zip".
Error message:
[CAN'T POST PICTURE BECAUSE XDA HAS VERY FUNNY MEME RULES XDDD]
Private message maybe...? Can I send you guys URL pics via PM?
How can I get out of this loop?
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
marshalpear said:
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
Click to expand...
Click to collapse
I definitly want CyanogenMod 12.1 on my Z3C. Is it still possible?
I hope you can decypher the URL h t t p : / / t i n y u r l . c o m / j 6 4 u 8 u a
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
marshalpear said:
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
Click to expand...
Click to collapse
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
If you are on CM recovery, then there is the problem. AFAIK you can't flash anything through that, so you have to push TWRP on your device using fastboot and then flash AOSP/CM rom you want.
SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
More info about my error:
h t t p : / / t i n y u r l . c o m / z b e v y u 2
Each version of step #3 doesn't work. Still trying to figure out how to get TWRP...
marshalpear said:
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
Click to expand...
Click to collapse
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
SYLVER SECOND said:
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
Click to expand...
Click to collapse
OK, your problem is that you messed up your system, so wiping it is not gonna solve this issue. You need to download a stock firmware file (an FTF file) and flash it through Flashtool, because your device name seems to be "." which is why you were getting "error 7". As for the recovery.img, you will use it to flash TWRP recovery on your phone. TWRP app doesn't work correctly if you don't flash it to your recovery partition so do as follows:
1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work. :good:
marshalpear said:
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
Click to expand...
Click to collapse
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Cirra92 said:
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
marshalpear said:
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
Click to expand...
Click to collapse
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Cirra92 said:
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Click to expand...
Click to collapse
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
marshalpear said:
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
Click to expand...
Click to collapse
Logical step, didn't think about it that way, I assumed OP knew how to enter recovery
"1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work."
K, so I guess I'm finished with #1 and #2. Sorry, had a ****-ton of chores to do. Before I progress, I wanted to send you guys
this pic:
https://img3.picload.org/image/rdricord/unbenannt.png
Is the root access necessary, or can I progress?
That's the sites I've used, if anybody wonders why something is the way it is right now:
http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
http://forum.xda-developers.com/showpost.php?p=66275965&postcount=2029
http://forum.xda-developers.com/showpost.php?p=60001557&postcount=829
Von "Sony Mobile Flasher by Androxyde":
"23/023/2016 22:23:52 - INFO - Root access denied
23/024/2016 22:24:07 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:12 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:13 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
23/024/2016 22:24:14 - INFO - Root access denied"
FlashTool says the firmware has been flashed so I don't understand what are you trying to do after that? After flashing the FTF file you should flash TWRP through "FASTBOOT". Then follow the instructions.
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
SYLVER SECOND said:
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
Click to expand...
Click to collapse
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
marshalpear said:
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
Click to expand...
Click to collapse
K, cool feature. Got it all set up now, but back to the main subject:
Is it even possible to install CyanogenMod 12.1 on Sony Z3C?
First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit
As tennear has noted, do NOT backup or restore the EFS partition.
Never restore EFS using TWRP. You will lose its contents and probably your IMEI.
@tennear Thanks for the heads up. I'll remove that part from my guide.
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.
Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk
i can't found same file u can upload again?
Yeah.... most links are dead. Does anyone else have them?
Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.
Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.
Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.
Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?
I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.
Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.
Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now
*DON'T FLASH BACK TO NOUGAT IF YOU ENJOY USING YOUR PHONE*
Ok guys ive made my return and im happy to bring the oreo ota with me.!
Steps to install if your on a rom.
1. Use this flash all link Here
2. After finished and setup your going to need a pc and sideload knowledge
3. Download these ota files
Latest August https://drive.google.com/file/d/1OhWZPTWcuo7zRu9bjiezjKEZxreOk6v7/view OREO
4. Get your phone into recovery mode.
4.a the file is gonna have a lot of letters please do not rename or it wont work
4.b before you get into recovery you will see a dead Android. This IS normal. Your going to want to hold power and push volume up. It's a split second kinda thing. Not something you guys forever. Hot that a few times if it doesn't work the first time.
5 your going to want to go to in recovery to apply update via adb for the August one
6. run the command adb sideload (now drag the file to the command prompt and press enter)
7 if all good you will see a verifiying update the step 1/2 when you see that your fine.
8 Let it do its thing and at the end you may see and error about a drive disregard that.
9 now follow steps 4-7 again but with Oreo ota
10 reboot your system and now you should have oreo!
If your stock locked and never been cocked you can try to install the same method above without using the flash all and if it works congrats if not unlock your bootloader and use the method above.
if any help is needed contact me @ [email protected]
HOW TO ROOT
1. DOWNLOAD THIS. https://drive.google.com/file/d/1zz3Fl9m4-_ozWW1U3ww_e6K_cHPPEMSv/view?usp=drivesdk
2. FASTBOOT BOOT OR FLASH IT RUNNING "FASTBOOT BOOT /PATH/TO/BOOT.IMG" OR FASTBOOT FLASH /PATH/TO/BOOT.IMG
3. REBOOT AND PROFIT.
TWRP 3.2.1-0 Bootable and Permanent
Bootable Fastboot boot this *ONLY FOR OREO*
*Permanent is broken* Use boot able
Unencryption for oreo
Encryption Remover *FOR OREO ONLY*
*Must format then flash*
OREO FLASH ALL OREO *YOU CAN ONLY FLASH THIS AFTER YOU HAVE TAKEN THE OTA* *IF YOU FLASH THIS AND YOU HAVENT AND YOUR PHONE BLOWS UP PLEASE VIDEO IT SO I CAN POST IT ON HERE AND SHOW WHAT NOT TO DO*
Thank to @XirXes for the ota files
There is no root available as of yet we need a boot image to get root once there is one we will have roms and root coming.
Screenies
Here you go
Installation went smooth. thanks for the OTA.
now towait for the root and all will be set
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
No. As of right now Oreo starts you clean when you do this
Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
I recommend (from experience) not trying that.
Making a test twrp real quick
Damn...thanks for your work
joemossjr said:
Making a test twrp real quick
Click to expand...
Click to collapse
Looking to this!
Oreo build is almost as fastest as the Flash [emoji3][emoji16]
Sent from my Moto Z (2) using Tapatalk
Thanks, @joemossjr ! It installed for me too. In my case, for some reason, I had to rename it to update.zip before adb sideload would work, but I'm not sure why. Oreo, yayyyy!
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
where's the TWRP, so only use a fastboot flash boot image.zip?
joemossjr said:
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
Click to expand...
Click to collapse
I could, do you have the TWRP link?
---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------
What I wanted to do was boot slot _b rooted 7.1.1 and copy slot _a stock Oreo, but it nagged me about potentially bricking in fastboot after fastboot set_active _b (i.e., due to invalid bootloader, etc.). A bootable TWRP straight to recovery would solve the issue. All I wanted to do was get a copy of Oreo boot_a, but adb as non-root user does not have permission to dd copy /dev/block/bootdevice/by-name/boot_a . So, yay for bootable TWRP!
@jhofseth please write me on hagnouts
please message me on hangouts people who want to help [email protected]
When you brick and have to go to a leaked 8.0 image
Unable to flash update
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
Code:
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
failed to open driver control: no such file or directory
installation aborted
also when selecting install from ADB it says
Code:
Supported API: 3
stopping adbd...
failed to open driver control: no such file or directory
failed to open driver control: no such file or directory
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Shiro12 said:
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
also when selecting install from ADB it says
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Click to expand...
Click to collapse
Do you go completely stock?
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 29.08.2019] Added new download locations for raw images
[Update 07.01.2019] Added more current raw image for ZS620KL WW 80.30.96.111
[Update 25.10.2018] Added raw image for ZS621KL.
[Update 09.08.2018] Updated for 80.11.37.95 and future versions.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as of 20.07.18 is 80.11.37.86. Newer versions will work too!
This guide is written for firmware 80.11.37.86. If you do not want to upgrade/downgrade to 80.11.37.86 you will need to use the firmware (zip file from ASUS) you are on in all the steps.
If you upgrade your firmware to a newer version AFTER rooting it you will lose root! You will need to patch the boot.img of the new firmware again > follow the rooting guide.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty! Currently there is no method known to relock it!
You will get a warning message about your unlocked bootloader at every boot.
You will no longer receive OTA updates but you can download the new firmwares directly from Asus.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware (ZS620KL WW):
WW 80.10.8.54
https://www.androidfilehost.com/?fid=1899786940962570681
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
WW 80.30.96.111
https://www.androidfilehost.com/?fid=1899786940962570682
https://drive.google.com/file/d/16OgxiPFSDJwhitnqJaITuO-XPOrg_7q9/view
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by amscova.
raw firmware (ZS621KL):
https://addrom.com/raw-rom-unbrick-for-asus-zenfone-5z-zs621kl/
https://www.androidfilehost.com/?fid=1899786940962570680
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by B Nath.
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware from 80.11.37.86 up with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this. There is currently no method know to relock the bootloader.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
flashall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide, GSPD and amscova for providing the ZS620KL raw image links and B Nath for finding the ZS621KL raw image.
Nice Theard
Thank You for your work
Upgrade after rooting
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.
isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
Click to expand...
Click to collapse
Process is too long. I am working on unofficial Unlock Tool so that we can retain the warranty.
For downgrading, there is a tool for that. For me, fastboot codes may mess up the system/cache partitions.
If anyone wanna test my unlocking tool, feel free to PM me via Telegram
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward
mihaitaiosub said:
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.
Click to expand...
Click to collapse
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.
isthisadagger said:
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.
Click to expand...
Click to collapse
And is not possible to root again whith method described on this thread?
mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
This is why we need TWRP.
mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
It is possible with Magisk Manager 5.8.3.
isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as iof 20.07.18 is 80.11.37.86.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
This guide is written for firmware 80.11.37.86. If you do not want to upgrade to 80.11.37.86 you will need to use the firmware you are on in all the steps.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty!
You will get a warning message about your unlocked bootloader at every boot.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware:
https://drive.google.com/file/d/1ogbQeeNDRPFCb9jl3kpRDK_DmsneQ0xL/view?usp=drivesdk
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware up to 80.11.37.86 with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
patchall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide and GSPD for providing the raw image name.
Click to expand...
Click to collapse
Does unbricking lock the bootloader back since we will be flashing a raw a file.
With Magisk Manager 5.8.3 the whole guide works like a charm
THX
My Zenfone 5z isn't being detected in fastboot mode, kindly help with correct driver softwares, my PC is running on Windows 10
Update : I got my phone to detect in fastboot
How to wipe cache partition
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks
chandru.biradar2 said:
Does unbricking lock the bootloader back since we will be flashing a raw a file.
Click to expand...
Click to collapse
No.
kelly66 said:
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks
Click to expand...
Click to collapse
Honestly killing the cache rarely helps things.
hi guys how to do this on Macbook pro? Any clues?
shantanudl said:
hi guys how to do this on Macbook pro? Any clues?
Click to expand...
Click to collapse
I do not have any experience with mac os but if you want to root:
Adb/fastboot is available for mac os. All you need to do is find a tool to extract the boot.img from the payload.bin.
If you want to downgrade/unbrick: You would need to convert the bat/cmd files in the full firmware to some shell scripts and exchange the fastboot.exe.
How do I un-root, re-lock bootloader?
ferez said:
How do I un-root, re-lock bootloader?
Click to expand...
Click to collapse
unroot: You press "uninstall" in magisk manager or install an updated firmware without patching boot.img or downgrade.
I have not tried re-locking the bootloader.
So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens
jens13 said:
So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens
Click to expand...
Click to collapse
You won't get OTAs + your warranty is voided (due to unlocking Officially)
Yes, you can update your phone by sideloading the zip from ASUS Support Website