Database Users

[Guide] Un-brick both (Soft/Hard) bricked Zenfone 2 ze550ml/ze551ml.

Unbrick Zenfone 2 ze550ml/ze551ml​Tutorial how unbrick (save) a cable suspended Zenfone 2 (lost bootloader) absolutely can not use or connect ADB recovery, fastboot to perform the operating system reload. Have to say this is the measure of last resort that you can perform with the Zenfone his second before the machine is required to submit to ASUS support.
How to know that your Zenfone 2 is bricked ?
>> Device can not start, only logo ASUS quite awhile now off. If you use keyboard shortcuts to access cluster bootloader (droidboot), display the cable connection icon which is usually called "the hanging cable."
Device can not connect to your computer regardless of whether in any mode (including ADB, fastboot), this leads to not be able to use ADB fastboot.
Cause: Loss bootloader
Damaged in a bootable partition.
-Most Of the cases are droidboot.img can flash the wrong file by other files as boot.img, recovery.img or get confused by any other machine on the line.
-Case Rare than natural bootable partition defective (not by you impact) or in some cases droidboot.img flash file into the machine suddenly collapsed sources can also occur.
The issue of "hanging cable screen" on Zenfone 2:
-Not Like Zenfone front lines, as his son Zenfone 6 was holding here, he was not sure the cable hanging screens you skipped bootloader, I can still access the bootloader, normal recovery. While on Zenfone 2, once encountered this phenomenon, make sure the machine's bootloader has been lost, this time ADB and fastboot recovery is meaningless.
How to unbrick?
This section explains how unbrick, you do not need sports references may skip and go to parts made right. You are using the Zen series (fone / pad) platform using Intel chips may also refer to similar application for its line, of course, will not be quite the same.
-When Your units with brick Zenfone 2, meaning lost bootloader (in this case), you can not lead to any use fastboot mode to flash the ROM file anymore. Typically, in this case, then one would have to use some special tools to be able to load directly into memory (memory) of the lower level as the bootloader using box, the second in the testpoint or the second machine sprung straight into memory ... However, for the mobile Intel chips sales are done with relatively simple parts, they provide a driver called IntelSocUSB available, when necessary Equipment using bootloader, you could still lose the connection with your computer via lower IntelSoc mode for use in emergencies.
IntelSoc edge-side connection, you also need to use additional software xFSTK Downloader, the tool support is simply loaded bootloader instead of using complex command lines. Unlike the methods used img file, which is when you already have a bootloader, as available "basis" can thus use only 1 img file. In contrast when used xFSTK Downloader you must have 2 file dnx_fwr.bin and ifwi.bin firmware, bootloader file same file simultaneously in the form of a new bin can be loaded into the device.
-Once You have successfully loaded bootloader can easily use tools like ADB fastboot nap ROM or ASUS FlashTool to bring "life" to return to the their Zen2 then.
Perform:
You must perform sequential follow the steps indicated below, a process steps will include many small, you also need to do before the next turn. Since there are many different levels and its brick is just so normal users can not list them all the way, I will try to extend to all cases that may occur, you just follow the sequence guidance, if encountered other problems please cmt for further discussion.
Step 1: Install the driver and connect mode IntelSocUSB IntelSoc
-This Is the driver help with a computer connected to your Zen2 IntelSoc mode as mentioned above. Because of this special driver, on some machines running windows 8 / 8.1 / 10 you can not install the normal way is that to add a little more tricks, not too hard, I'll complete list Under.
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
drive.google.com/file/d/0B2oMRhweQ4CHbURUNk1ZTHI2Mjg/view?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
If you're using Windows 8 / 8.1:
-On Keyboard press Windows + I to show charm bar bar in the right corner, click on the item setting.
Choose "Change PC Settings" to enter the PC Settings.
Choose the General tab and navigate to Advanced Startup section, continue click Restart now.
This force will reboot windows and allows you access to the advanced mode, in turn selected the following items: Troubleshoot - -Startup Settings Advanced Options and then click the Restart button to restart the computer.
-Continue Press 7 on the keypad to access the installation mode allows drivers.
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
If you're using Windows 10:
-On Keyboard press Windows + I or click Start, select Settings.
-In The Settings window, select the Update & security.
-Continue Choose recovery and click "Restart now".
-When The computer has access to the Advanced screen, how similar startup with Windows 8 above.
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
1.2 Connect with computer IntelSoc Zenfone 2:
After driver installation step above 1.1 as successful you are in a window like this, do not click Next yet. Now you must complete step IntelSoc connection before installing xfstk downloader.
-The Device manager: right-click the Computer icon, select Manager, find the device manager.
-In Device manager, to IntelSOC, click the down side, you only see the present only one item is Intel SoC driver.
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables.
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
-This Is a required step to complete before performing next.
Ash back window IntelSOC earlier installation, click Next and Finish.
1.3 Installing xfstk-downloader:
Download xFSTK Downloader v1.7 here:
drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view?usp=sharing
-Download And install with a setup similar to IntelSoc Driver guided above is, simple installation process does deserve to be noted.
-That's It step 1.
Step 2: Use the Downloader to reload the bootloader xFSTK
This is a tool to support the new bootloader loaded into memory chip straight soc IntelSoc mode.
XFSTK load Downloader v1.7:
drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view?usp=sharing
-The Necessary files:
ZE551ML: drive.google.com/file/d/0B2oMRhweQ4CHR21YaDdXdUNlOGs/view? Usp = sharing
ZE550ML: drive.google.com/file/d/0B2oMRhweQ4CHcHg4WXJQckFGOTA/view? Usp = sharing
After downloading the necessary files extract to a separate folder 3 file dnx_fwr.bin, ifwi.bin, bootloader.
-Open XFSTK Downloader, first passed MRD tab A0 / B0 + A0 + CRC as shown Moor.
-Then Go to Options to change the value in the Value section Override Flag GP 0x80000807. Click OK is complete initial preparation.
This force remains connected to the phone cable.
Begin the process of loading the bootloader:
+ First in turn selected item Firmware FW 2 cells and IFWI DNX 2 dnx_fwr.bin and ifwi.bin file.
+ Section IFWI: skip the first box, in the box looking to file droidboot_dnx.img.POS_sign.bin Image OS, here is our bootloader files.
Now let's go to the Device Status section below, this section shows the number of connected IntelSoc, you need at least one device is connected. If in step 1 you do succeed, make sure xFSTK Downloader also get equipment, if not retry the connection cable.
Just click on the download button to start Begin implementation.
-Here You may see error faild continuity however kept calm to software performance. Until now informed SUCCESS as shown below, then congratulate you, our problem is almost solved.
The process is loaded bootloader successful restart when you will not see another familiar ASUS screen but instead is a 4 color, just like some TV stations stop broadcasting on TV.
Shortcuts in bootloader test can not yet see. Now you can load the ROM via fastboot mode / droidboot and know.
-If Not know how to do this, see step 4. If the flash ROM or flash via fastboot not finished still not on the operating system, your computer would be heavier than normal, continue to step 3.
-Note: Hanging cable phenomenon will appear again if you are not successful flash ROM. Each drawing shows the cable hanging out, you need to perform this step 2.
Step 3 (if applicable): Using ASUS FlashTool reloaded raw files.
Here's how to load ROM via fastboot mode is considered as the most supportive.
Download ASUS FlashTool 1.0.0.14: the previous version can not support Zenfone 2.
https://drive.google.com/open?id=0B4uMV7GwfDAEYm5RWTFydXZWOTQ
Download firmware for ZE551ML 2.20.40.194 raw format here:
https://drive.google.com/file/d/0B0v_vGzEh1G5WU1QTzlTOExIekU/view
Version for ZE550ML 2.20.40.155 raw format here: https://yadi.sk/d/XAUyR8eRtuKdA
Installing ASUS FlashTool resembles IntelSoc describes how to install the above, you also need to fully implement the steps before the installation on your Windows 7.8.10 will not repeat again.
-To Phone droidboot mode / fastboot, connected computer, enable ASUS FlashTool.
ASUS FlashTool -On screen, in the model of your selected device (ZE551ML / ZE550ML). Part wipe data option. Click the button next to wipe data section to find raw files downloaded above.
Below current frame connected devices, if not try to wait for a few minutes, plug in the cord, if not you are required to reinstall the driver IntelUSB (this does not lead his popularity and link again).
-Click Select your device and press the Start button to begin implementation.
Firmware loading process long-range 5 to 10 minutes. Then the machine will automatically boot into the operating system, if successful, congratulations to you.
Note: It is possible at this stage you will not succeed with the process of loading raw files, the software itself runs completely without any notice. If this process occurs too 30p then your job is forced to withdraw cable.
-Mark Whether the file import process may not succeed but at least Flash Tool ASUS sent commands resize partitions, if the command is successful, then the partition on the device has been fixed and you was able to load the ROM type fastboot okay, do the next step 4 preview successful offline.
Step 4: Use a rechargeable Fastboot img file.
The last pitch to bring life back to the two of you here Zenfone.
-There Bootloader means you can use fastboot to flash ROM img format already.
Img -Download the latest ROM for Zenfone 2 here:
-Choose The appropriate ROM version (ZE551ML / ZE550ML) and download all the files in that directory, links to download: mega.nz/#F! K4MHiAgL! DVuOKeH3eokcwPSNI79ffw! Xwc0BJrY
-Use Manager winrar or any unzip the archive file will be system.img system.zip
-Copy Boot.img, droidboot.img, recovery.img, system.img in the folder C: \ adb adb install directory or your.
-file SplashImage here:
fshare.vn/file/2KIL3GQ1NZN2
General similarity copied to the folder with the other files.
Open ADB made the following statement:
Code:
fastboot flash splashimage splashimage.img
fastboot fastboot flash droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot

Added to index, thanks for your work!

cmendonc2 said:
Added to index, thanks for your work!
Click to expand...
Click to collapse
My another Guide to Recover Fastboot of bricked Zenfone 2 ze551ml
http://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337

Thank u very much for this tutorial
Z008

Raw firmware link added for ze550ml users

is it normal for my "MOOREFIELD" to appear temporarily?
Should i continue despite my detect = 0 since it appear temporarily?

I have a few corrections that I have to figure out myself in order to get through, I hope these are a translation problems and can be solved easily.
First of all, the links for Z008 (raw image) is misspelled and contains bad characters (the "*"s). And the Fastboot image link is misspelled too or broken, either of them, therefore, I had to look in the index for those.
Then, The Asus Flash Tool AFT the version provided is 1.0.0.7 which is very old and doesn't support our phones, then I had to look up for the newest one (or even compatible) which is 1.0.0.14. Then the flashing instructions in xFSTK are confusing because there are 3 files to flash (explained better on the other post) FW DnX is the Dnx, IFWI is IFWI, OS DnX is blank and OS Image is the droidboot. That is much simpler.
The part of the explanation of how to use the AFT is almost unredeable. It's just simple as choosing the model, choose to Wipe Data (yes), look for the raw image, selecting the phone with its serial number (btw, the installation of the drivers was a little messy since the AFT Install couldn't install them).
Don't misunderstand this reply, this guide was very useful to me, but I correct this for the ones that encounters this problem. I succeed unbricking my zenfone after it went to the USB Logo by itself (I still don't know why would this happens since I didn't touch the fastboot, but it clearly shows that this cases could happen to anyone).

nanofives said:
I have a few corrections that I have to figure out myself in order to get through, I hope these are a translation problems and can be solved easily.
First of all, the links for Z008 (raw image) is misspelled and contains bad characters (the "*"s). And the Fastboot image link is misspelled too or broken, either of them, therefore, I had to look in the index for those.
Then, The Asus Flash Tool AFT the version provided is 1.0.0.7 which is very old and doesn't support our phones, then I had to look up for the newest one (or even compatible) which is 1.0.0.14. Then the flashing instructions in xFSTK are confusing because there are 3 files to flash (explained better on the other post) FW DnX is the Dnx, IFWI is IFWI, OS DnX is blank and OS Image is the droidboot. That is much simpler.
The part of the explanation of how to use the AFT is almost unredeable. It's just simple as choosing the model, choose to Wipe Data (yes), look for the raw image, selecting the phone with its serial number (btw, the installation of the drivers was a little messy since the AFT Install couldn't install them).
Don't misunderstand this reply, this guide was very useful to me, but I correct this for the ones that encounters this problem. I succeed unbricking my zenfone after it went to the USB Logo by itself (I still don't know why would this happens since I didn't touch the fastboot, but it clearly shows that this cases could happen to anyone).
Click to expand...
Click to collapse
I will try to update all the links and make my post more clear as soon as possible .
Thanks for doing corrections in my post .

Unfortunately, I've encountered some other issues after I succesfully unrbricked my Zenfone. I must say that I quite step away from some of the steps since after I flashed the RAW Image file on the AFT I successfully boot into system. That means I skipped the flashing of the other img droidboot, boot, recovery and system images provided. Then, when I tried to flash TWRP back again, I noticed that even though the flash was succeed, trying to boot in recovery mode lead me back to fastboot mode, pointing out that recovery partition is still damaged. Maybe I need to flash the RAW again to repartition, but since the phone works now I don't want to touch anything again. I can still flash things through fastboot though, the Xposed, the root image, etc. But it seems like I don't have a recovery functional.
The sources for this are still very poor and we need to bring it all the things that the Russian, Vietnam and Chinese forums were posting all this time about the ubrick thing, maybe there's something that I've missed.
Did anyone try to download the system images from that Mega page? I found the link somewhere but the compressed files seems to be corrupted (for the Z008), I would appreciate if anyone else can confirm this.

issue with serial no.
AFT fail to flash coz of serial don't match with actual serial no. of phone
any solution

aniruddha007 said:
issue with serial no.
AFT fail to flash coz of serial don't match with actual serial no. of phone
any solution
Click to expand...
Click to collapse
Which version of AFT are you using?
Explain what do you mean with "doesn't match" I didn't have to check the serial number at any point.

http://mega.nz/#F! K4MHiAgL! DVuOKeH3eokcwPSNI79ffw! Xwc0BJrY
Link dead, new link pls

nanofives said:
Which version of AFT are you using?
Explain what do you mean with "doesn't match" I didn't have to check the serial number at any point.
Click to expand...
Click to collapse
it checks for serial no. of device n fails
so i tried to flash twrp.img using fastboot but got an error "flash_cmds error!"
plz help me guys

As this is an error that was not reported when I was reading through all the foreign forums, I have to state the obvious since I don't have a particular answer.
I assume at this point that you have all the proper drivers, therefore the AFT shouldn't recognise the device. So... what I think is, is your phone in fastboot mode? (I mean the fastboot mode with the 4 colours instead of the ASUS Logo). Maybe there could be a failure in the process of unbricking with the xFSTK downloader.

Add source
please add source bro, this's my tut
amtech. vn/threads/un-hard-brick-zenfone-2-giai-phap-cuu-may-cuoi-cung-truoc-khi-den-trung-tam.370362/
remove blank after "."
---------- Post added at 07:48 PM ---------- Previous post was at 07:44 PM ----------
And thanks for translating :angel:
---------- Post added at 07:58 PM ---------- Previous post was at 07:48 PM ----------
aniruddha007 said:
it checks for serial no. of device n fails
so i tried to flash twrp.img using fastboot but got an error "flash_cmds error!"
plz help me guys
Click to expand...
Click to collapse
you can't use fastboot to flash img file because some partitions still have error.
You must use AFT, try check your cable and run AFT as Admin.
---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------
@nanofives
it show the 4 colours because it have no splashimage

yes its in fastboot mode
nanofives said:
As this is an error that was not reported when I was reading through all the foreign forums, I have to state the obvious since I don't have a particular answer.
I assume at this point that you have all the proper drivers, therefore the AFT shouldn't recognise the device. So... what I think is, is your phone in fastboot mode? (I mean the fastboot mode with the 4 colours instead of the ASUS Logo). Maybe there could be a failure in the process of unbricking with the xFSTK downloader.
Click to expand...
Click to collapse
oh yes its in fastboot with 4 colour

I have problems in 4-color screen.
Everything I do ok.
I need help from you ...
Thank you very much

What are you trying to do? The process is stuck somewhere?
Enviado desde mi ASUS_Z008 mediante Tapatalk

@salsav3i
Bro i didn't knew that this is your guide , i got this guide in Vietnamese language from my friend who lives in Vietnam

Hi, does this lock my bootloader?

Redmi 3 Pro Considerations - Flash global ROM with BOOTLOADER LOCKED

I've tried some things on my Xiaomi Redmi 3 Pro and I want to share them if helpful for someone.
I've done all this with Xiaomi.eu Rom and SMIUI
///// I'm not accountable for any problem on your phone, do it at your own risk! \\\\\​
1 - Button combinations (unplugged from pc):
vol+ & vol- & power = force shutdown if in fastboot or download mode, if powered-on it's a restart
vol- & power = from switched-off phone goes in fastboot (from there you can launch another combination: vol+&vol- while launche cmd: fastboot.exe reboot)
vol+ & power = preload\ bootload mode (the yellow screen where to choose recovery\ fastboot\ download mode)
2 - For any type of problem \brick \ bootloop be sure before about this:
A) if you run the phone in fastboot mode, check if you can see it in fastboot command line from pc (cmd: fastboot devices)
B) if you run the phone in download mode, check if you can see it from miflash
If these point are ok this means the pc is ready to see the phone if you softbrick it or it goes in bootloop.
You will be always able to run it in fastboot mode, then download mode, an flash any rom to the phone that works.
3 - What you need?
Install last version of MiFlash, here a guide: http://en.miui.com/thread-272376-1-1.html
Install MiPCSuite in english, here the link: http://pcsuite.mi.com/
If you have problems with ADB, install ADB drivers, here the link: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 or http://forum.xda-developers.com/showthread.php?t=2317790
If you have problems with hs-usb qdloader 9008 driver, try to install from here: http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Download and upack Android.Image.Kitchen for Windows, from here: https://mega.nz/#!McAj2SZT!E4XS7II27BjkjSHS2vcBnE6Tgvl8IZBhCD2wEKBchpA
Download TWRP 3.0.2.0 for MiFlash: https://mega.nz/#!cF4VVQiY!zrq2DTQRBX3UHRPOXN1dDNWiTn5tnoPxUfrHF_Rsnq4
Download ROM from different links:
http://en.miui.com/a-234.html (miui china stock, BL Locked)
https://www.androidfilehost.com/?w=files&flid=36337 (Xiaomi.eu with Gapps, no Bloatware, BL unlocked)
http://smiui.net/kitchen.php(Xiaomi.eu + other stuff)
Install Notepad++
4 - Prepare ROM:
As suggested by the user Jack0190 there are ROMS where is not needed to mod this files, like for "Xiaomi redmi3 pro locked multilanguage" roms.
Searching on web you can find them quickly, just be aware that there are some roms that have problems with SIM recognize. This comes from an old Thai \ Indian MIUI.
I've seen first this thread on en.miui, http://en.miui.com/thread-276565-1-1.html , where explains how to modify ROM to change the bootloader check. The guide explains very good how to modify the "boot.img" file of roms.
So just follow those steps.
I've seen that you can do it for both types of rom, for Recovery and MiFlash too.
For the recovery ROM, you have a file to open in 7Zip, copy the "boot.img" from it, modify it as explained in the guide, and re-copy in the zip file again.
While for the one for Miflash, it's easier; extract the rom, copy the "boot.img" file from \image folder, modify it with, and change it in the original folder. Then flash it with Miflash.
5 - Connect phone in Fastboot with pc:
One thing that always will save you is the ability to connect phone in fastboot mode.
Before start the phone in fastboot mode with cable unplugged (point 1).
Once you've installed Miflash, go on it's directory folder (C:\Program Files\Xiaomi\MiPhone\), and run cmd from there (shift+right mouse click).
Connect phone to pc.
Then run command "fastboot.exe devices" and if the result under the line on left is a code, the phone is recognized
6 - Force Download Mode from fastboot:
To force the phone to go in dowload mode, first run it in fastboot (point 5), check if it's recognized (point 2-A), then type but don't run command "fastboot.exe reboot".
Now push vol+ & vol- in the same time, and now run the command.
If it runs in the right mode, you can see it's connected by device manager under "Ports (COM &LPT)" section.
You will see "qdloader 9008 driver" with a COM port installed. The same port you will see in Miflash if you run it and push the "refresh button".
7 - Flash Job:
A) First you need to flash the recovery, TWRP, and to do this you should already have done this things:
Install Miflash, MiPcSuit
Your phone is right seen in fastboot and in Miflash in download mode.
You have downloaded the right versione of TWRP for MiFlash.
B) Flash TWRP with Miflash
Select in Miflash the button "Browse" and go to the folder "\Image"where you have extracted the TWRP zip
Click "Refresh"
Click "Flash"
Wait to complete (If it fails sending hello packets, it's because it's too much time the phone is in download mode, in this case, switch it off, e restart in Download mode and re-do all )
C) Copy modified ROM:
Now, I've done this step by OTG connection but there are more ways to do it:
Connec and mount an USB Drive in OTG
Push it by ADB
Copy it by SD card
If the old ROM still works, copy it in MTP connection
if none of this options is available, flash the Rom with Miflash, flash again TWRP recovery, run recovery, wipe cache and dalvik (factory reset option under "Wipe") and try to run system, it should run last system flashed.
D) Flash modified rom by recovery
E) Restart in system (It could take long time, even 10 minutes, so just wait for it)
Thanks to all users\ people helped me with different guides from XDA and other forums.
I' m sorry for no image, but it's not an official guide.
If something is wrong I'll change it asap, but don't blame me, these are just advices.
If it's not enough clear, search it on web.
If there are grammar errors, the Image verification confirms "I'm not a robot"
If you don't find the answer, then it's 42.

After mod, i can flash rom update from recovery?
Inviato dal mio GT-I9505 utilizzando Tapatalk

Just wanted to say thank you - This guide works. I tried it with a new redmi 3 pro with locked bootloader. You can skip step 4 if you want to, because there are some prepared images available (search for "xiaomi redmi3 pro locked multilanguage" and you will find them).
Also to note: The first boot of the new system took some long time (~ 10-minutes), so don't get frustrated. As long as there's the android logo with the three dots wandering around, everything should work fine.
- Jack

RuLe89 said:
After mod, i can flash rom update from recovery?
Inviato dal mio GT-I9505 utilizzando Tapatalk
Click to expand...
Click to collapse
not sure about this, I've flashed the last version available, so i don't have updates for now to test.
But i think that it could overwrite files modified.
This is what in some guides tells.

Jack0190 said:
Just wanted to say thank you - This guide works. I tried it with a new redmi 3 pro with locked bootloader. You can skip step 4 if you want to, because there are some prepared images available (search for "xiaomi redmi3 pro locked multilanguage" and you will find them).
Also to note: The first boot of the new system took some long time (~ 10-minutes), so don't get frustrated. As long as there's the android logo with the three dots wandering around, everything should work fine.
- Jack
Click to expand...
Click to collapse
Thanks to you, I've updated with what told. I've tried some of ROMs for locked bootloader, but was an Indian \ Thai version, and I had issues with SIM, no recognize.
That's why it was needed for me to use other rom for unlocked bootloader.

Hi, thanks for the guide. It seems like it'd be the only decent I could come across for my problem.
The only thing is that everytime I try to flash any ROM/image through MiFlash, I get the error:
Code:
Error loading type libary/DLL.(0x80029c4a: wait port ready to use <time in seconds>)
So far I haven't found anything or anyone that could help me with this. Can any of you help me out here? That'd be much appreciated.
Thanks~
----------------------------------
::Edit::
Alright, turns out I just had to do this:
1. Uninstall the Qualcomm drivers
2. Reboot Windows into "test mode"/Disabled driver signature enforcement
3. Reinstall the Qualcomm drivers
4. Flash device (phone in download mode)
5. Be very pacient. Waiting through the phone's boot phase
(took about 10 minutes; if it takes more than 15 minutes, then something is probably wrong. Try to enter download mode and flash it again.)
6. Redmi 3 working again
Okay, so, this worked for me, it doesn't mean it'll necessarily work for you!
This was done with a locked bootloader and MiFlash 2015.10.28.0

Doogee X5 Max Pro Root Recovery OTA

******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-

i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD

I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard

It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.

pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp

Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.

pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img

Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000

XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.

Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...

How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20

i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !

Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?

Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?

rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?

ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/

I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.

Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/

This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74

Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!

[Guide] Flash Stock Rom Asus Zenfone 2 ZE551ML

Hey Guys. This guide will help you if
1. If Using Custom Rom and want to revert to latest stock rom.
2. If Stock Rom got corrupted or became laggy.
3. You want to reinstall stock rom.
Warning:
1. Method 1 require unlocked bootloader. If you want to unlock then go Here . Method 2 doesn't. Don't worry.
2. This will clean your phone just like new phone.
3. First read the post twice carefully then proceed.
4. ALL .bat FILES TO BE RUN IN FASTBOOT MODE ONLY, IF YOU DON'T KNOW ABOUT FASTBOOT MODE THEN GOOGLE "HOW TO GET FASTBOOT MODE IN ASUS ZENFONE 2
5. I may change name of files in folder. Use common sense to identify them.
Pre-requisites:
1. Charge your phone atleast 60%.
2. Backup any important data you might not wanna loose to either sd card or usb drive or pc.
3. Copy the rom zip in the sd card of your phone. (The one with size in GB)
4. Android USB Driver should be installed already, if it is not then install all drivers in the "Drivers Folder".
5. Enable USB Debugging.
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it
says "You are a developer now". Then go to "Settings" you will find "Developer Options", open it and enable "USB Debugging"
4. Common sense, patience.
Download Link:
For Method 1
Click here Android Filehost
Download these folders: TWRP, STOCK RECOVERY, STOCK ROM, DRIVERS
For Method 2
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Procedure:
METHOD 1​Step 1. Flash TWRP recovery if not installed by using "TWRP.bat" (Given in twrp folder) in fastboot mode or bootloader mode whatever you call it.
Step 2. Go to Twrp recovery then choose "wipe" then choose "Advance wipe" and tick everything except "SD card or external sd card". then swipe to wipe.
Step 3. Go to fastboot/bootloader mode and flash stock recovery running appropriate .bat file. It is given in "Stock Recovery" folder.
Step 4. When the command executes from the above step, Go to "recovery" by pressing volume down button, then press "power" button.
Step 5. You will see a dead android logo. Nothing else. Then go to stock recovery options.
If you don't know how then use following methods
Method 1:
When you see a dead android bot with an error press and hold power button, then (while holding power button) quickly press Vol up and release and then release power button..
Method 2:
Go to fastboot mode. Connect your device and open command prompt there. Then Type
Code:
fastboot erase cache
Step 6: You should see stock recovery options. Then choose "Update from sd card" and select the rom zip you pasted in SD card.
(If you don't have sd card, then paste rom in internal memory and don't tick "internal storage" in twrp in step 2) But micro
sd is preferable.
Step 7: Wait. Your phone may take 20-30 or more minutes. So leave it on charging.
METHOD 2​Step 1: Download and Install all drivers given in download folder. Download RAW firmware for your phone. See above in download links.
Step 2: Install "ASUS FLASH TOOL"
Step 3: Go to fastboot/bootloader mode on your phone. Run asus flash tool, select your phone model and browse for the raw firmware. Check wipe all data. And start the process.
Step 4: Wait for program to say successful. If it takes more than 30 minutes. Disconnect your phone and check phone if rom installed or not.
If this process does not work. Then switch methods.
If you have any questions, problems .. Just Comment it.
Every Suggestion welcomed. Also you can join telegram group to get help and help others.
MOD EDIT: LINK REMOVED
If the guide works for you or you want to thank me for development of tools then you can donate me via
Paypal paypal.me/KapilTapsi (You can donate any amount, It will be of great help)
FAQ
1. Having problems with device connection? like waiting for device.
Sol. Make sure you have enabled USB Debugging (Not applicable for BL Unlocking and TWRP Flashing)
Uninstall all drivers previously installed on computer(every driver of any device)
Reboot your computer. And then install all drivers given in the driver folder.
If the problem persists, try different computer and different usb cable.
2. Facing permission denied in fastboot mode or while running script files.
Sol. Try disabling your lock screen security to none.
File Credits:
1. RealYoti

Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Click to expand...
Click to collapse
Thanks for suggestion. But the reasons​ are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.

Kapil Tapsi said:
Thanks for suggestion. But the reasons​ are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Click to expand...
Click to collapse
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Click to expand...
Click to collapse
It is a guide only. Users are free to choose from where to download. Thats it. I only shared my collection.

E: footer wrong
E: footer wrong
Installation aborted
I need your help!
I follow the instructions in Method 1 but the device give me this error message when I try to update via SD-card...
May I know whats the solution?
Rom used: Fastboot Rom WW-4.21.40.327
Thank you very much!

kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks, finally got it

Hey...when I get to part 6 I get this Error >>
footer is wrong
signature verification failed
installation aborted

Hey..I also Tried Flashing with the method 2 it was installing but i got an error after

Man, this thread saved my ass. thank you for all your time all!

I have the Asus Zenfone 2 ZE551ML with sound issues, (it's only when the phone rings that the speaker works) and I put it into recovery mode to wipe cache/data, but it got stuck while doing that and I forced it off. But now, it's stuck at the Asus Boot logo with the rotating icon underneath.
Please help!!!!

Hello, my 551ml has stock LP, it's rooted with bootloader unlocked and Xposed installed. If I want to install the latest MM with through the raw flashing tool, should I install the MM bootloader first or it is included into the raw file? Thank

just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks

stevegtrlmk said:
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
Click to expand...
Click to collapse
use asus flash tool

damn my asus flash tool says error flashing image failure.... (remote not allowed to flash this partion)
ow btw i already bricked it cause it only does boot fastboot lol no more android
how do i flash it back again i need to send the phone back to amazon by 18/05 lol i mean i can just send it back and say also that it wouldnt boot cause i tried to reset it to get my touchscreen to work but yeah lol dont want them to refuse my retour

No way to simple flash the stock rom through/keeping twrp in the device, like I do with other Custom Roms?

Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?

euphrodil said:
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
Click to expand...
Click to collapse
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk

Kapil Tapsi said:
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Click to expand...
Click to collapse
Ok thanks, i'll look for a thread that explain this.

euphrodil said:
Ok thanks, i'll look for a thread that explain this.
Click to expand...
Click to collapse
did you find any?
i want to remove the lineageos and install latest stock LP but i have no clue how to do it

[BEGINNERS GUIDE][Lollipop 5.1.1 .236] Root,Backup TA, UBL, Install Recovery

NOTE: DON'T HOLD ANYONE RESPONSIBLE IF SOMETHING GOES WRONG DURING THE PROCESS!
This thread contains full information you might need for rooting, backing up TA partition, unlocking bootloader, installing custom recovery, installing custom rom etc.
Some notes below, read them
-I try to keep this thread clean so people have easier time navigating. @derjango has ALOT of info and fixes on his THREAD which is related to this one, give it a read
-Read comments if you have problems. You may find answer and fix there by other users. I wrote this thread few months after I did these steps to my phone so I likely made mistakes (e.g. I forgot or got some steps wrong). If you do see those mistakes or have problems that nobody else has, feel free to ask in comments.
-We will use legit rooting methods and not those sketchy one click root apps
-These instructions may apply for other z line devices but you will have to find ftf files for your own device
-Written for 14.6.A.1.236 firmware but it will work on any version that you have currently.
0. PREPARATIONS
Backup all your data (photos, videos, contacts etc.)
Fully charge your battery
Enable USB debugging
Download the following:
Latest XperiaCompanion from HERE (for drivers mainly)
Sony flashtool from HERE
Follow THIS thread to install adb drivers
Navigate to your C:\Flashtool\drivers and run Flashtool-drivers
Select Flashmode drivers, Fastboot drivers and Xperia Z1 Compact drivers and click install
Now download THIS and THIS and put it in C:\Users\username\.flashTool\firmwares
(Windows 8/8.1/10 users can try - THIS fix if you can't install flashtool drivers)
1. FLASHING .108 FIRMWARE
1.1. Run Flashtool and click on lightning button, make sure flashmode is selected and hit Ok
1.2. In left window click on + symbol until you find 14.4.A.0.108
1.3. Under wipe check both options
1.4. Click Flash
1.5. Wait
1.6. Follow the on screen instructions
(You can release vol- when you see activity in flashtool window)
(If you get device disconnected just unplug phone and repeat all from step 1.1)
1.7. Don't touch anything until blue progress bar disappears. You should see Device disconnected> Device connected in flash mode.
(Don't worry if bar gets stuck near end just let it do it's thing)
1.8. Disconnect phone and reboot
1.9. Done!!!
(Do only basic setup, we won't be staying on this rom for long)
2. ROOTING .108 FIRMWARE
2.1. Make sure USB debugging is enabled
2.2. Download THIS Easy Root Tool by zxz0O0
2.3. Unzip and run install.bat
2.4. Download SuperSu apk form HERE put it in internal storage and install it.
2.5. Update binary normally.
2.6. Done!!! You should have root now.
(Download Root Checker to make sure you do)
3. TA PARTITION BACKUP
(NOTE: This is absolutely not necessary and is only needed if you plan to go back to stock firmware AND use BionZ, X-Reality and Music ID/Gracenote. TA partition and DRM keys stored inside get erased when you unlock bootloader.
3.1 Download THIS Backup TA v9.11 by DevShaft
3.2. Extract and run Backup-TA.bat. You should see backup>TA backup.zip in main folder where you extracted
3.3. Backup whole folder to cloud since you can't flash someone's else backup if you loose yours
3.4. Done!!!
(Read linked thread for useful information and FAQ)
4. UNLOCKING BOOTLOADER
4.1. Dial *#06# on your device. You will see your IMEI code
4.2. Go HERE and scroll to bottom
4.3. Under select device select Z1 Compact and enter your IMEI code
4.4. Check the 2 boxes and click on submit. You will get your unlock code. Copy it to clipboard
4.5. Run Flashtool again and click on "BLU" button
4.6. Connect phone in flashmode.
4.7. When prompted, enter your unlocking code that you copied form SONY website
4.8. Click unlock.
(Follow any instructions that flashtool gives you. I don't remember if there are any after this)
4.9. Done!!! Your bootloader is unlocked!
5. FLASHING RECOVERY
This is how I did it. You can try to skip step 5.2. If it doesn't work try again following all steps
5.1. Download THIS TWRP by 115ek and extract recovery image in new folder
5.2. Run Flashtool and flash 14.6.A.1.236 just like you did with .108 in first step (If you have problems here see THIS comment)
5.3. Now without rebooting or disconnecting your phone flash THIS open bootloader with flashtool just like you flashed system ftf-s.
5.4. Disconnect your phone and press volume up and connect your data cable. You should see blue led.
5.5. Now enter that folder where you extracted recovery image and press shift and right click in empty window area and select Open Command window here (Powershell for windows 10 users should work fine I think. Never used it)
5.6. Type "fastboot flash recovery recovery.img" and hit enter.
5.6 Done!!! You should have your recovery now.
To reboot to recovery first disconnect your phone and hold volume down and power button. Release power button when phone vibrates but keep holding volume down until you see twrp logo.
AND THAT IS IT
Now that you have your recovery and unlocked bootloader you can flash whatever roms, kernels, mods that you want for your phone.
Thanks to:
derjango for his thread mentioned above
munjeni For supplying open bootloader ftf and for giving me support with my problems
Androxyde For Flashtool
Snoop05 For ADB driver tool
zxz0O0 For Root tool And PRF Creator tool
DevShaft For Backup TA tool
115ek For TWRP
[NUT] For XZDualRecovery
kulvertti For SuperSu Dummy

Placeholder

I'm really struggling to get past unlocking the bootloader and starting to get quite confused.
Sony Companion is up to date.
Flashtool installed and used to flash .108 firmware.
Device is rooted using Easyroot tool.
Supersu installed and binary updated.
When I go to run BLU in Flashtool it prompts me to connect my device whilst holding the volume-down button (so flash mode). A couple of seconds after doing that it prompts me to re-connect the device whilst holding the volume-up button (so fastboot mode), but nothing happens. Blue LED is on the device, but Flashtool does absolutely nothing.
When I check Flashtool-driver it does fail to install the AndroidUsbDeviceClass driver, but when I run the 15-second ADB Installer it completes successfully - plus I was able to flash the firmware earlier so I don't see why I'd now have a driver issue.
Any ideas? It's starting to drive me crazy.

Here is what you can try.
Connect your phone to pc and in command prompt type adb reboot bootloader or hold vol+ and connect your phone
Your phone will be booted to fastboot now
Now type fastboot devices
You should see
XXXXXXXXXblabla fastboot
If you see this that means that your phone is recognized in fastboot by your pc.
If you see <waiting for device> or something else go to your device manager while still in fastboot
IIRC you should see under other devices something like saXXXX or something
You can tell me what exactly it says or you can fix it yourself by googling that number and adding fastboot driver and update it manually through device manager
If you decide to do it yourself make sure you link me website where you link me thread where you found driver and write down instructions so other people can see it
If you have any other problems feel free to reply
Also i just noticed that i didn't include that you lose ta partition when ubl and since you don't have ta backup make sure you make one. You never know when you might need it

Ok, thanks for that I definitely had a problem with driver installation so followed the steps in this video - https://www.youtube.com/watch?v=fcz4o6fpDGc
Now I am a bit stuck on flashing recovery.
5.2. Run Flashtool and flash 14.6.A.1.236 just like you did with .108 in first step --- do I also check both options under Wipe? will this not remove root?
5.3. Now without rebooting or disconnecting your phone flash THIS just like you did with system ftf-s. --- not sure what I'm meant to do here

Glad you fixed that problem
Flash that file through flashtool just like you flashed system ftf
Also yes that will remove root but we had that root only to backup ta and unlock bootloader. Since you unlocked bootloader and you install twrp you can easily root any rom

I get the "'fastboot' is not a recognised ..." error when trying to flash recovery - using Windows PowerShell as I'm on Win10.
EDIT: running CMD then moving to the location of where ADB was installed and contains Fastoot.exe worked.
Thanks for the guide!

scanz said:
I get the "'fastboot' is not a recognised ..." error when trying to flash recovery - using Windows PowerShell as I'm on Win10.
Click to expand...
Click to collapse
That means you don't have fastboot drivers installed. Here is temporary fix that got me out of frustrating situations when i can't install drivers systemwise
https://mega.nz/#F!aBoUXI5Q!RmxLAO638aHNJKLwo00Hew
If it downloads as zip first unzip it and run command prompt/powershell in that folder or in powershell type cd and drag that folder, that should do the same.
fastboot will now be recognised as command
this also includes adb drivers

Just wondering, I'm trying to get Magisk running after finishing the steps in your guide, but it does not pass any of the SafetyNet checks - even basicIntegrity check comes back false. Have you any ideas or experience with this? If so perhaps you could include it as part of the guide

If you get cts fasle that means you flashed rom that comes with supersu preinstalled. You could try installing rom without magisk and removing su then flashing mahgisk.
Not sure about integrity tho. I heard that xposed can cause problems with that.

colaigor said:
5.3. Now without rebooting or disconnecting your phone flash THIS with flashtool just like you flashed system ftf-s.
Click to expand...
Click to collapse
I get this:
23/015/2018 22:15:07 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
23/015/2018 22:15:07 - INFO - Preparing files for flashing
23/015/2018 22:15:07 - INFO - Please connect your device into flashmode.
23/015/2018 22:15:08 - INFO - Opening device for R/W
23/015/2018 22:15:08 - INFO - Device ready for R/W.
23/015/2018 22:15:08 - INFO - Reading device information
23/015/2018 22:15:08 - INFO - Unable to read from phone after having opened it.
23/015/2018 22:15:08 - INFO - trying to continue anyway
23/015/2018 22:15:08 - INFO - Phone ready for flashmode operations.
23/015/2018 22:15:08 - INFO - Opening TA partition 2
23/015/2018 22:15:08 - INFO - Start Flashing
23/015/2018 22:15:08 - INFO - No loader in the bundle. Searching for one
23/015/2018 22:15:13 - INFO - Processing loader.sin
23/015/2018 22:15:13 - INFO - Checking header
23/015/2018 22:15:13 - ERROR - Processing of loader.sin finished with errors.
23/015/2018 22:15:13 - INFO - Ending flash session
23/015/2018 22:15:13 - ERROR - null
23/015/2018 22:15:13 - ERROR - Error flashing. Aborted
23/015/2018 22:15:14 - INFO - Device connected in flash mode
Click to expand...
Click to collapse

Are you sure you installed flashtool and other drivers? I can't think of any other cause for this problem right now

I flash 14.6.A.1.236 without problems using flashtool, so drivers should be ok; maybe why I'm using a Mac istead Windows?

_Pano_ said:
I flash 14.6.A.1.236 without problems using flashtool, so drivers should be ok; maybe why I'm using a Mac istead Windows?
Click to expand...
Click to collapse
Found this boot bridge for mac users. you may try it and see if it works. Can't really tell you anything about drivers on mac since i never touched one.
Also mega file may be corrupted. You can try downloading from this comment where i downloaded openbl from
Do you have windows machine to try flashing ?

yes, I try tomorrow using Windows 10, thanks

colaigor said:
Found this boot bridge for mac users. you may try it and see if it works. Can't really tell you anything about drivers on mac since i never touched one.
Also mega file may be corrupted. You can try downloading from this comment where i downloaded openbl from
Do you have windows machine to try flashing ?
Click to expand...
Click to collapse
ok, I flash .236 linked in your first post and then without rebooting or disconnecting the device I flash openbootloader and I see:
24/020/2018 09:20:14 - INFO - Closing TA partition
24/020/2018 09:20:14 - INFO - Ending flash session
24/020/2018 09:20:14 - INFO - Flashing finished.
24/020/2018 09:20:14 - INFO - Please unplug and start your phone
24/020/2018 09:20:14 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
24/020/2018 09:20:16 - INFO - Device connected in flash mode
24/022/2018 09:22:15 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
24/022/2018 09:22:15 - INFO - Preparing files for flashing
24/022/2018 09:22:15 - INFO - Please connect your device into flashmode.
24/022/2018 09:22:15 - INFO - Device connected in flash mode
24/022/2018 09:22:16 - INFO - Using Gordon gate drivers version 3.1.0.0
24/022/2018 09:22:16 - INFO - Opening device for R/W
24/022/2018 09:22:16 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
that's all? 1 second flash?

_Pano_ said:
that's all? 1 second flash?
Click to expand...
Click to collapse
Sorry for late answer.
Does it work? I don't remember how much it took to flash tbh

colaigor said:
Sorry for late answer.
Does it work? I don't remember how much it took to flash tbh
Click to expand...
Click to collapse
yes, after various attempts: after flashing .236 I had to disconect and reconnect the phone in order to flash openbootloader; otherwise it doens't flash

thank you for these tutorials..I now have a rooted z1compact lollipop 5.11 locked bootloaders..My question is how can I debloat my phone..I want to uninstall other system apps that I don't need and I want to install xposed on my own..sorry I am newbie

xjhayar09 said:
thank you for these tutorials..I now have a rooted z1compact lollipop 5.11 locked bootloaders..My question is how can I debloat my phone..I want to uninstall other system apps that I don't need and I want to install xposed on my own..sorry I am newbie
Click to expand...
Click to collapse
You can download Titanium backup from playstore and delete all that you dont need and keep what you nees. Also you can find twrp flashable script that deletes all bloatware. Just sreach xperia lolipop debloat script on xda.