Related
GETTING YOUR ULTRA ROOTED AND
READY FOR FLASHING
This guide should in theory make your Ultra ready for flashing custom ROMs, and with that said...
...here comes the warning: If you follow the steps contained herein
Your warranty is now voided. I/we are not responsible for bricked devices, or whatever you might end up with.
TABLE OF CONTENTS
Warnings
ROOT KitKat (Android 4.4.4)
Back up TA Partition
Install Recovery
Unlock the Bootloader
Install Custom ROM
Using Flashtool
Back to Stock
Handy Links
Glossary
Misc.
Warnings:
Backup your TA partition before unlocking your bootloader - you will lose DRM keys and other stuff during the unlock
Unlocking the Bootloader will wipe your phone, so backup your stuff
Never Flash a FTF to a ZU GPe - it will kill it
Your warranty is now VOID
ROOT KitKat (Android 4.4.4):Rooting 4.4.4
FTFs
14.4.A.0.108
14.4.A.0.118
To root KitKat we have a handy tool called Easy Root by @zxz0O0. This tool will root all modern Xperia devices running KitKat. Please read the thread.
To use this tool first upgrade to one of the above FTFs or use Sony's PC companion to update the phone to Android 4.4.4
Instructions:
What you get
Root
Access to /system rw
Requirements
USB debugging enabled
Settings => About phone => Click 7 times on Android Build to unlock developer options
Unknown sources enabled
Settings => Security
adb drivers installed
How to use
Download the latest version and extract it
Start your device and plug it to your computer
Run install.bat and follow the instructions on screen
Install SuperSU by Chainfire (recommended!)
Congratulations! You should now be rooted.
Don't forget to make a donation or thank the OP in the original thread
Rooting Pre 4.4.4
Upgrade to one of the 4.4.4 FTFs listed above to save any hassle
Rooting The GPe
GPe Owners: Do not try and flash any FTFs to your device. You will BRICK it with no way to recover it.
Go to this thread and follow the steps.
Back up TA Partition:The TA partition is the "Trim Area". There are lots of things stored in here like root certs, revoked certs, DRM keys, current firmware version,... the list goes on. What we are concerned about here is with the DRM keys. Some service centres will not service a Sony device if these are missing. Unlocking the BL will erase these.
Once you lose these keys, you can't get them back, so backup the TA and upload it to your Dropbox etc
You will need Backup TA for Sony Xperia by @DevShaft Please read the thread.
Instructions:
Download the latest version of Backup TA.
Extract the ZIP file to a folder location of your choosing.
Navigate to the folder location of Backup TA.
Make sure no other script or application which is using ADB is running.
Make sure the device is booted in normal mode (the way you normally use it).
Run Backup-TA.bat
Read the last paragraph of the license before continuing.
Read the information and follow the instructions given by the tool.
Don't forget to make a donation or thank the OP in the original thread
Install Recovery:
Download the latest version of @[NUT]'s Dual Recovery
Instructions:
Make sure you have USB debugging turned ON.
download ZU-lockeddualrecovery[VERSION]-BETA.installer.zip from http://nut.xperia-files.com
Windows:
unpack at C: or somewhere you will remember!
navigate to the resulting directory and look for install.bat, double click it to run;
Linux:
unpack in your home folder with 'unzip ZU-lockeddualrecovery[VERSION]-BETA.installer.zip'
navigate to the resulting directory and 'chmod +x install.sh', then execute it, follow instructions.
Your phone WILL reboot when installation has completed and it will go into the default recovery for the first boot.
Reboot to system from recovery to allow the installer to clean up after installation (it is safe to skip this step).
Enjoy DUAL RECOVERY!
Don't forget to make a donation or thank the OP in the original thread
Unlock the Bootloader:This will wipe your phone, so backup your stuff
You only need to unlock the bootloader if you want to run either a custom kernel or a custom ROM. Most ROMs based on the Sony releases will run on a locked bootloader.
Instructions:
Go to Sony's Developer site
Request the unlock key and check your mail straight away. Email is quick these days.
Open the latest Flashtool on your computer
Click the "BLU" icon
Follow the steps and enter your unlock key
Install Custom ROM:To install a custom ROM you will have to complete the steps above (ROOT, Back up the TA Partition, and Unlock the Bootloader) you dont need to have installed recovery but it will help you make a backup of the current state of your device.
After the above are done:
Backup current software with custom recovery (TWRP or cwm - use the same recovery the the new ROM uses*)
Downlod ROM
Extract boot.img from within the .zip
Flash the boot.img (not absolutely necessary but will mean you are on a recovery that is tested to work with the ROM)
In fastboot mode use either flashtool or the fastboot commands
- If you want to use the boot.img's recovery to make a back up of the current software/state of the device use:
Code:
fastboot boot boot.img
- or if you just want to flash the kernel and recovery to flash the ROM use:
Code:
fastboot flash boot boot.img
fastboot reboot
Wipe Data
Wipe Cache
Wipe Delvik Cache
Flash ROM
Reboot
*CM based ROMs normally use CWM. Slim and Omni based normally use TWRP
Using flashtool:Please use this very good guide: Flashtool XZU
Back to Stock:
To get back to pure stock Sony there are several things that need to be done:
Make sure you have root
Backup any data/photos/etc on the phone
Restore your TA backup with the TA backup tool above
If you are on a custom kernel or ROM you ZU will not boot at this stage
Start flashtool and load a FTF
Start the flash and wait for the onscreen instructions to connect the ZU
Connect your ZU in flashmode
With the ZU powered off
Connect to PC while holding the volume down key
Flash will start
Wait for flash to complete
Handy Links:FTFs: The FTF depository thread
Flashtool: http://flashtool.net
SuperSU: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Glossary:FTF: A flashable package of Sony's stock firmware. These can be found in The FTF depository thread
TA Partition: The TA partition is the "Trim Area" there are lots of things stored in here like root cert, revoked certs, DRM keys, current firmware,... the list goe on. What we are concerned with is the DRM keys. Some service centres will not service a Sony device if these are missing. Unlocking the BL will erase these.
Bootloader or BL: This is the thing that loads Android. To run a custom ROM (non Sony) you have to unlock this
Root: You are GOD
boot.img: The kernel and recovery (on Xperia)
XDA:DevDB Information
Z-Ultra Root Guide, Tool/Utility for the Sony Xperia Z Ultra
Contributors
blueether, H. E. Pennypacker, adfurgerson, LordManhattan, [NUT], geohot, many others
Version Information
Status: Stable
Created 2014-11-13
Last Updated 2015-01-01
Reserved
As always, very informative blueether.
Questions:
(1) Does this mean we no longer need to downgrade/upgrade/restore imei etc?
(2) Unlocking the bootloader is a requirement for installing any rom? No way around this?
(3) I understand the need for the disclaimers but rooting/unlocking BL doesn't automatically void your warranty does it?
unidentifier said:
As always, very informative blueether.
Questions:
(1) Does this mean we no longer need to downgrade/upgrade/restore imei etc?
(2) Unlocking the bootloader is a requirement for installing any rom? No way around this?
(3) I understand the need for the disclaimers but rooting/unlocking BL doesn't automatically void your warranty does it?
Click to expand...
Click to collapse
1/ was only needed on 4.2
2/ added a line
3/ ring Sony and say this: "I rooted my ZU, and now it won't boot. Can you fix it for me?" what do you think their response will be?
With the warranty question: I asked because I'm more concerned about the cracked glass issues than bricking the device because I couldn't follow instructions. Thanks again for the instructions.
I may sound dumb but if I am only interested in root just for link2sd feature & foldermount to overcome internal storage limitation by transfering to SD card then do I have to follow all steps ? or only first 2 step will do i.e. Root & install SU.
I will just root it & don't want to touch TA or Bootloader as not planning to update with custom rom. please suggest that even for rooting do I need to backup TA / unlock bootloader.
also will new update of Android Lollipop will wipe my root or will I be able to upgrade to lollipop in later on stage with Root.
please reply on this.
Nice with an updated version. Do speak up if you need some help with anything.
anandbohra said:
I may sound dumb but if I am only interested in root just for link2sd feature & foldermount to overcome internal storage limitation by transfering to SD card then do I have to follow all steps ? or only first 2 step will do i.e. Root & install SU.
I will just root it & don't want to touch TA or Bootloader as not planning to update with custom rom. please suggest that even for rooting do I need to backup TA / unlock bootloader.
also will new update of Android Lollipop will wipe my root or will I be able to upgrade to lollipop in later on stage with Root.
please reply on this.
Click to expand...
Click to collapse
My XZU hasn't arrived but my experience with other phones is that root alone should allow you to use link2sd and fouldermount.
Can't speak to OTA updates being blocked on rooted phones..
anandbohra said:
I may sound dumb but if I am only interested in root just for link2sd feature & foldermount to overcome internal storage limitation by transfering to SD card then do I have to follow all steps ? or only first 2 step will do i.e. Root & install SU.
I will just root it & don't want to touch TA or Bootloader as not planning to update with custom rom. please suggest that even for rooting do I need to backup TA / unlock bootloader.
also will new update of Android Lollipop will wipe my root or will I be able to upgrade to lollipop in later on stage with Root.
please reply on this.
Click to expand...
Click to collapse
Yes if you just need root the only go that far
OTA will probably fail with root, and flashing a FTF will wipe root when L arrives
rooting is not working. stops as there is no tr.apk included. In the guide there is nothing about tr.apk needed to be downloaded as well as that you need to donate before you can download. I dont mind to donate but I need to know it will work.
krystan said:
rooting is not working. stops as there is no tr.apk included. In the guide there is nothing about tr.apk needed to be downloaded as well as that you need to donate before you can download. I dont mind to donate but I need to know it will work.
Click to expand...
Click to collapse
Are you only wanting to root, or do you plan to install recovery also?
blueether said:
Yes if you just need root the only go that far
OTA will probably fail with root, and flashing a FTF will wipe root when L arrives
Click to expand...
Click to collapse
Thank you very much for your prompt reply.
will post my experience once I receive my piece & just plain root it.
anyhow as per google Lollipop might take another 4-5 months for Xperia Z Ultra (might be May-15)
Thanks every one.
anandbohra said:
Thank you very much for your prompt reply.
will post my experience once I receive my piece & just plain root it.
anyhow as per google Lollipop might take another 4-5 months for Xperia Z Ultra (might be May-15)
Thanks every one.
Click to expand...
Click to collapse
Just roo should be fine
We are getting close to haveing a working AOSP L, give it a few days I guess (but pleas dont clog this thread up with L stuff for now
All my previous Sumsang phones were on custom ROMs.
But with SonyXZU I just want to root, for now
krystan said:
All my previous Sumsang phones were on custom ROMs.
But with SonyXZU I just want to root, for now
Click to expand...
Click to collapse
Darn I was going to suggest using the dualrecovery installer for locked bootloaders and then flashing supersu from here.
http://forum.xda-developers.com/xpe...de-root-android-4-4-4-ver-14-4-0-108-t2801587
I have the towelroot apk that I downloaded a few days ago, but not sure what you would need to do with it.
adfurgerson said:
Darn I was going to suggest using the dualrecovery installer for locked bootloaders and then flashing supersu from here.
http://forum.xda-developers.com/xpe...de-root-android-4-4-4-ver-14-4-0-108-t2801587
I have the towelroot apk that I downloaded a few days ago, but not sure what you would need to do with it.
Click to expand...
Click to collapse
Thank you adfurgenson
If I do dualrecovery will I be able to get 5.0?
Or only manually?
krystan said:
Thank you adfurgenson
If I do dualrecovery will I be able to get 5.0?
Or only manually?
Click to expand...
Click to collapse
I am pretty certain that you have to go back to stock to receive the OTA, but I think that would apply also if you only rooted. Flashing an ftf file with flashtool without checking the boxes to wipe data is what I have seen recommended to get back to stock. I hate giving an answer I am not one hundred percent sure is correct so I will call on some experts, @blueether or @HEPennypacker can you confirm this is correct please.
adfurgerson said:
I am pretty certain that you have to go back to stock to receive the OTA, but I think that would apply also if you only rooted. Flashing an ftf file with flashtool without checking the boxes to wipe data is what I have seen recommended to get back to stock. I hate giving an answer I am not one hundred percent sure is correct so I will call on some experts, @blueether or @HEPennypacker can you confirm this is correct please.
Click to expand...
Click to collapse
meh, can't be bothered writing a reply. What you said will work if/when the OTA fails
OK more of a reply...
unless the OTA is only very minor it will normally fail even if the ZU just rooted
ADB Drivers and Sony PC Companion
ADB
Trying to prep the computer before the XZU arrives. The sticky mentions ADB drivers.
Are these the best ways to get them or are there better options?:
15 Second ADB Installer: http://goo.gl/ixQyom
Minimal ADB and Fastboot: http://goo.gl/EuGtRo
PC COMPANION
Link to Sony PC Companion
http://support.sonymobile.com/global-en/xperiazultra/tools/pc-companion/
Root the M4 Aqua E2303 Locked Bootloader/Install TWRP on 2.167/3.92
Before we begin:
Make sure you have the following:
•A Windows PC
•Flashtool (https://drive.google.com/file/d/0B_d8uWGbkaetTnhWX0J5UG5hN28/view?pref=2&pli=1)
•The .128 firmware (https://drive.google.com/file/d/0BzVQf67OZ9NtMFotOXRycTZoSlk/view?pli=1)
•Patience
•A good internet connection
•15 to 20 minutes
• The M4 Aqua Root Toolkit (https://www.dropbox.com/s/edse0h6b02odzn1/rootkitXperia_E23xx.zip?dl=0)
•ADB Drivers (https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view?pref=2&pli=1)
•TWRP Toolkit (https://www.dropbox.com/s/yomdwq3p2le9hvi/M4Aqua-lockedTWRP-0.1-installer.zip?dl=0)
How are we going to do it:
The procedure is pretty straight forward, as the M4 Aqua is only on Android™ 5.0 we can take the kernel of the older versions of firmwares so we could root the device, while keeping the firmware version to the newest release (2.167/3.92). The method has been only tried on the E2303, there may be chances of it working for the E2306.
Let's begin! Part 1, Changing the Kernel:
First, we need to install the latest Flashtool version (link above), after you proceed with the installation of Flashtool, you need to install the Flashtool drivers, which can be found in C:/Flashtool/drivers or the path you selected flashtool to be installed. Once you open Flashtool drivers you want to select FLASHMODE DRIVERS, this is only so that the M4 will be recognised while in flashmode. After the drivers have been installed, you want to move the downloaded .128 firmware to C:/Users/*YourName*/.flashtool/firmwares or you can use the other method I will show later. Once you have done that you want to open Flashtool and wait for the Sync to finish. After that has finished, you will see a lighting icon in the top-left corner, you want to press the icon and select flashmode, now the second method, at the top you will see a path leading to the generic .tft folder in which Flashtool belives the .ftf files are located by default. You can change that by pressing the button on the right and lead the program to the path of the .128 ftf file. After you have selected your .tft file you will see on the right a lot of options *everything that the .ftf file contains*, if you want to keep the data on your device you can tick the first two options, a bit down on the right you will see a lot of options, including system.bin, you want to tick everything EXCEPT for the kernel.sin, this is the most crucial part. After that is done you want to let the program prepare the files, mean while you want to power off your M4 Aqua, after the process on Flashtool is done you want to press the VOLUME DOWN button while connecting the phone to the PC, once you see the green led light you can leave the button, if everything was done right the process of flashing should begin. If everything went well the kernel should be flashed and the phone should safely power on. Now we can proceed to the second part. Rooting the phone.
2ND METHOD
You can downgrade to .128 firmware and download the .167 or .92 firmware and update everything except for the kernel. You can do this by going into Flashtool, and doing the steps above but TICKING the kernel.sin. Try this if the first method doesn't work.
Part 2, Rooting the phone:
Now that we have changed the kernel we can use the root toolkit to root the device. Download the root toolkit from the link above, but before you do anything you want to go to Settings>About Phone, scroll down to Build number and press it 7 times, after that is done you want to go back to Developer options, and you want to tick USB Debugging, after you have done that you need to install the ADB Drivers from the link above, after that is done you can connect the phone to the computer, now you want to extract the toolkit and run install.bat *No administrator rights needed*, and then you should see a screen on your phone asking if you want to trust the computer, you want to tick the box saying always and you want to press yes, now the rooting process should begin and your phone to be rooted. After this is done we can proceed to the part 3, installing TWRP
Part 3,Installing TWRP:
Now, that we have root we can install TWRP using another toolkit. This part is optional but if you want any custom ROM's you need this. This part is the easiest, you need to download the toolkit from the link above and just run the script. We don't need any additional steps as we did them in Part 2.
If everything went well you should now be rooted and have TWRP with a locked bootloader and on the newest firmware.
In case of bricking you can use the Sony PC Companion tool and repair my phone/ tablet option. YOU WILL LOSE ANY DATA SAVED ON YOUR PHONE.
sir , can this apply to D2353?
I have only tried on E2303, but you use the right .ftf files the procedure should work
im flashed 128 kernel on 3.92, phone not booted stuck boot animation..
fix this after root random reboots? im rooted on 128 and upgrade 3.92 by twrpreroot, phone randomly reboots..
edit: im flashed 128 kernel on 2.167, phone not booted
osman.by said:
im flashed 128 kernel on 3.92, phone not booted stuck boot animation..
fix this after root random reboots? im rooted on 128 and upgrade 3.92 by twrpreroot, phone randomly reboots..
edit: im flashed 128 kernel on 2.167, phone not booted
Click to expand...
Click to collapse
Root and flash stock kernel tft u use
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
d0mokun said:
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
Click to expand...
Click to collapse
When i upgraded from 128 to 167, phone works well but random reboots. Any fix this issue?
Clean install of .167 and .92. Flashing the .128 kernel causes the blue boot animation to hang (the start up sound cuts off half way). Flashing the previous kernel back over works.
Same happens when I flash .128 then everything but the kernel from .167 and .92.
Unsure what the FSC script option does, but yes or no makes no difference.
d0mokun said:
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
Click to expand...
Click to collapse
EDIT: Someone re-uploaded the M4 rootkit: http://forum.xda-developers.com/m4-aqua/general/guide-t3130092/post65486499#post65486499
bootloop on E2303 Tried both methods
Hey all. Trying to root my E2353 on 26.1.A.1.112. Ran install.bat with all drivers installed, with adb, but all I'm getting is this. Any suggestions?
drunkenlo said:
Hey all. Trying to root my E2353 on 26.1.A.1.112. Ran install.bat with all drivers installed, with adb, but all I'm getting is this. Any suggestions?
Click to expand...
Click to collapse
enable usb debugging and unlock the phone and accept the popup message when plugged in
Jevinruv said:
enable usb debugging and unlock the phone and accept the popup message when plugged in
Click to expand...
Click to collapse
I have usb debbugging enabled and the phone unlocked but I don't get a popup message. Tried disabling and re-enabling usb debugging but still nothing.
drunkenlo said:
I have usb debbugging enabled and the phone unlocked but I don't get a popup message. Tried disabling and re-enabling usb debugging but still nothing.
Click to expand...
Click to collapse
Revoke USB Debugging authorization from developer Settings
Random Reboots
Any fix for the random reboots as of yet?
could u fix the dropbox link, it isnt working for me - Error (429)
This account's links are generating too much traffic and have been temporarily disabled!
I'm getting an error when installing the flashmode drivers, it just says failed after I tick the box and continue. Can anybody help me please? I've tried rebooting my PC, running as admin and even tried compatibility options but it doesn't help.
osman.by said:
When i upgraded from 128 to 167, phone works well but random reboots. Any fix this issue?
Click to expand...
Click to collapse
kgalv419 said:
Any fix for the random reboots as of yet?
Click to expand...
Click to collapse
If your random reboots usually happen while downloading or updating apps in the play store, you should try this. Make sure you backup your data first just in case.
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Hello. Please help. I got softreboot everytime I try to call someone
Sent from my E2303 using Tapatalk
Hello,
thank you for this guide. I have a question: why not extracting the old kernel and just flashing the kernel.sin?
Hey guys,
My honor 7 is still at the B100 update. I always wanted to update to other versions but wasn't able to.
My phone was rooted and ofc if you update then it won't work. It always fails at rebooting and brings it back to twrp recovery (including bootloop). After a couple of times using volume + and powerbutton it will sometimes bring it to EMUI erecovery, and by then I can start my phone the normal way.
So now I unrooted my device by a full uninstall in superSU. But still the updates won't work.
Then I did a factory reset, but still no succes in updating my device (still getting twrp bootloop).
So now i'm following this guide: http://forum.xda-developers.com/honor-7/general/guide-how-to-update-to-marshmallow-6-0-t3349497 and http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
After following the steps in "[Guide] How To Update To The Latest Marshmallow 6.0 From B180" I get stuck at step 7.
I don't know what kind of command prompt I should use. I am using my windows command prompt and directed it to the extracted path (step 6).
In step 7 I need to use the fastboot flash functions but the cmd prompt doesn't recognise the functions. So I'm guessing I'm using not the right kind of cmd (do iI need to use like adb program or something)?
For the guide: "[Guide For Beginners] - How To Update, Root, Tweak, and Fix Honor 7"
In step 2 I need to go into the bootloader menu by using volume + and powerbutton. For me it will go into EMUI erecovery.
Summary:
What have I done:
- unrooted my device by full uninstall SuperSU (any rooted apps won't work)
- factory reset my device
- edit1: tried also to put marshmallow version in sd/dload and installing it local. No succes again.
Problems:
- unable to update my device, it will never install the update.
- when the device is rebooting for update installation it will get into a twrp bootloop.
- problems in guides steps.
I hope someone is able to help me with these problems.
poooopie said:
Hey guys,
My honor 7 is still at the B100 update. I always wanted to update to other versions but wasn't able to.
My phone was rooted and ofc if you update then it won't work. It always fails at rebooting and brings it back to twrp recovery (including bootloop). After a couple of times using volume + and powerbutton it will sometimes bring it to EMUI erecovery, and by then I can start my phone the normal way.
So now I unrooted my device by a full uninstall in superSU. But still the updates won't work.
Then I did a factory reset, but still no succes in updating my device (still getting twrp bootloop).
So now i'm following this guide: http://forum.xda-developers.com/honor-7/general/guide-how-to-update-to-marshmallow-6-0-t3349497 and http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
After following the steps in "[Guide] How To Update To The Latest Marshmallow 6.0 From B180" I get stuck at step 7.
I don't know what kind of command prompt I should use. I am using my windows command prompt and directed it to the extracted path (step 6).
In step 7 I need to use the fastboot flash functions but the cmd prompt doesn't recognise the functions. So I'm guessing I'm using not the right kind of cmd (do iI need to use like adb program or something)?
For the guide: "[Guide For Beginners] - How To Update, Root, Tweak, and Fix Honor 7"
In step 2 I need to go into the bootloader menu by using volume + and powerbutton. For me it will go into EMUI erecovery.
Summary:
What have I done:
- unrooted my device by full uninstall SuperSU (any rooted apps won't work)
- factory reset my device
- edit1: tried also to put marshmallow version in sd/dload and installing it local. No succes again.
Problems:
- unable to update my device, it will never install the update.
- when the device is rebooting for update installation it will get into a twrp bootloop.
- problems in guides steps.
I hope someone is able to help me with these problems.
Click to expand...
Click to collapse
You have to flash stock recovery.
Sent from PLK-TL01H
Thanks! I feel so stupid that I haven't done that. It works great now and I've the latest version.
Hello guys. I have a problem with my Z2. Recently and unfortunately i have updated to 6.0.1 and now i want root access on my phone to install viper4android but i couldn't find any solution. I will give all the information and you can suggest me what to do.
Phone: Sony Xperia Z2
Model: D6503
Build Number: 23.5.A.0.575
Kernel: 3.4.0-perf-g43a728
Bootloader: Not unlocked but in service menu shows it can be unlockable (however official sony site doesn't show my phone to get the code)
What should I do in this case?
If I need to downgrade, I am okay with 5.1.1 but I don't know how to downgrade with locked bootloader.
If this is the case how do i downgrade?
Is there anyway to unlock bootloader at the moment for sony devices?
Is there any root method for 6.0.1 or will be soon for Z2?
Anything could work please help..
PS: English is not my native sorry for mistakes. Thank you all.
Another topic with this question.
So, for downgrade, you don't need unlocked bootloader, just use Flashtool program, install drivers for device and Flashmod and flash FTF for your device model.
For now, no way to root Android 6 with locked bootloader.
You can always unlock the bootloader, once in service menu is positive status (Yes).
If you want to unlock bootloader, use official metod for example, but don't need for this (unlock bootloader, flash custom kernel and ....), , only to install sound mod.
That is the problem, look at official sony web site, my device is not on the list for bootloader unlock. So can you offer me a guide how to downgrade to 5.1.1, a noob friendly guide.
1. Download and install the program flashtool by Androxyde. - http://www.flashtool.net/downloads.php
2. Install drivers from installation folder /Drivers - Driver for model Xperia and Flashmod drivers.
3. Download FTF file for YOUR MODEL DEVICE with 5.1.1 from here for example:
http://forum.xda-developers.com/showthread.php?t=2759934
and copy to folder with Flashtool/ Firmwares
4. Start Flashtool and click on Flash icon.
5. Choose Flashmod (not Fastboot), and find the FTF, that you download before with 5.1.1
6. Follow the guide in the program Flashtool and all will be the OK,
xhanty said:
Hello guys. I have a problem with my Z2. Recently and unfortunately i have updated to 6.0.1 and now i want root access on my phone to install viper4android but i couldn't find any solution. I will give all the information and you can suggest me what to do.
Phone: Sony Xperia Z2
Model: D6503
Build Number: 23.5.A.0.575
Kernel: 3.4.0-perf-g43a728
Bootloader: Not unlocked but in service menu shows it can be unlockable (however official sony site doesn't show my phone to get the code)
What should I do in this case?
If I need to downgrade, I am okay with 5.1.1 but I don't know how to downgrade with locked bootloader.
If this is the case how do i downgrade?
Is there anyway to unlock bootloader at the moment for sony devices?
Is there any root method for 6.0.1 or will be soon for Z2?
Anything could work please help..
PS: English is not my native sorry for mistakes. Thank you all.
Click to expand...
Click to collapse
Hey man,first,you need to downgrade to KK (.314 it´s the best one) and then root and install recovery,then update to LP .232 or .264 and then go to MM,follow the instructions that Monipeev gave to you (but choose .314 fw) and then follow this guide: http://forum.xda-developers.com/xpe...ck-d6502-03-23-4-0-546-completeguide-t3171219 Hope you get it
Bro i don't want MM right now. I just want root access so if its 5.1.1 i am okay with that. Monipeev i will try your method and notify you about the result tomorrow.
Monipeev said:
1. Download and install the program flashtool by Androxyde. - http://www.flashtool.net/downloads.php
2. Install drivers from installation folder /Drivers - Driver for model Xperia and Flashmod drivers.
3. Download FTF file for YOUR MODEL DEVICE with 5.1.1 from here for example:
http://forum.xda-developers.com/showthread.php?t=2759934
and copy to folder with Flashtool/ Firmwares
4. Start Flashtool and click on Flash icon.
5. Choose Flashmod (not Fastboot), and find the FTF, that you download before with 5.1.1
6. Follow the guide in the program Flashtool and all will be the OK,
Click to expand...
Click to collapse
Okay after this how do i root the easiest way? kingroot one click apk ? or you suggest something else for locked bootloader bro ?
Go through the steps of Root compilation .264 Android 5.1.1, with a version of the application Kingroot that uses the author of the video.
After root success, replace Kingroot with SuperSu.
Root Android 5.1.1, .264
https://www.youtube.com/watch?v=ZJ6OPXN3M0g
Monipeev said:
Go through the steps of Root compilation .264 Android 5.1.1, with a version of the application Kingroot that uses the author of the video.
After root success, replace Kingroot with SuperSu.
Root Android 5.1.1, .264
https://www.youtube.com/watch?v=ZJ6OPXN3M0g
Click to expand...
Click to collapse
thank you bro for helping, i've got an error message while flashing
29/032/2016 14:32:05 - INFO - Start Flashing
29/032/2016 14:32:05 - INFO - Processing loader.sin
29/032/2016 14:32:05 - INFO - Checking header
29/032/2016 14:32:05 - ERROR - Processing of loader.sin finished with errors.
29/032/2016 14:32:05 - INFO - Ending flash session
29/032/2016 14:32:05 - ERROR - null
29/032/2016 14:32:05 - ERROR - Error flashing. Aborted
29/032/2016 14:32:05 - INFO - Device connected in flash mode
what do i do...
If you use last version on Flashtool 0.9.22.2, download old version and try again.
Monipeev said:
If you use last version on Flashtool 0.9.22.2, download old version and try again.
Click to expand...
Click to collapse
it was about drivers. i have installed all of the drivers (even those i don't need) in flashtool folder. also windows installed semc and somc drivers by itself and i have successfully flashed. i hope i dont get bootloop because its been 2 minutes and im still waiting for it come to menu btw i didn't wipe the userdata and applog while flashing.
Edit: just a last thing how do i replace kingroot with supersu, i can google it but since you are guiding me through this
Edit2: okay no bootloop awesome, now the only thing left to do is rooting. thank you so much for your help bro. i will notice you if i have a problem again. i hope this thread will be helpful for others too like me
I think if you follow this guide, you will finish ok:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
there is a program called superSuMe apk. does it work ? any idea ?
I'm sorry, but I have no experience with this app.
At least that is described in its description.
wow now i get ''unfortunately the process com.android.media has stopped'' message and phone keeps resetting..
Edit: i think i will reflash with wipe options..
Surely it would be better.
its done
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com