Related
I found a way to install twrp on my mi max with locked bootloader using EDL mode.
NB! This will reformat the phone so you should take a backup if you got something you want to keep on the phone.
NB! DO THIS ON YOUR OWN RISK!!!
To get into EDL mode I followed thi guide:
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
I turned off the phone and pushed vol+and- and connected the usb to the PC.
Then I installed the qualcom drivers I found here:
http://xiaomitips.com/download/qualcomm-qdloader-usb-drivers/
In device manger update the drivers that has name QHSUSB_BULK when the phone is in EDL-mode with the quallcomm-drivers
The driver should be installed and you can see added in Ports as Qualcomm HS-USB
I downloaded a fastbootimage
http://bigota.d.miui.com/6.6.23/hydrogen_images_6.6.23_20160523.0000.23_6.0_cn_5ab5ac0aba.tgz
I also downladed twrp:
http://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-0-touch-recovery-t3388073
I used 7zip to unpack fastbootimage.
Inside I found the folder with images and a recovery.img file. I renamed twrp file to recovery.img and replaced the one in images.
I then used miflasher and flashed the fastbootimage using clean option.
The flasher I used: can be found here:
http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
On flasher program the device should be recognized as COMXX when the Qualcomm drivers.
If the device id is a hexnumber and not COM10 the flashing in EDL mode will not work.
After flashing I diconnected the phone from pc and rebooted into recovery "power and vol+"
Now I had TWRP and could wipe and install ROMS etc.
I installed the ROM I found here
https://xiaomi.eu/community/threads/6-6-23.32335/
This was a much better ROM than the china-rom
Nice... Did your bootloader get unlocked after you flashed the eu global ROM?
nijel8 said:
Nice... Did your bootloader get unlocked after you flashed the eu global ROM?
Click to expand...
Click to collapse
Its still locked, but as you got twrp it really doesn't matter
I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!
Survivor1990 said:
I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!
Click to expand...
Click to collapse
You use the Miflasher when telephone is in EDL-mode. I used http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
I didn't pack the ROM again. I had to browse into the catalog with the flasher which has files like flash.all
I see no reason why a Cyanogenmod for max shouldn't work as long at you flash it with twrp
Okay I did not know about this third Tool. I will try it when I am at home in the evening. Thank you very much!!
My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working
tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)
same for me!
g_BonE said:
tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)
Click to expand...
Click to collapse
Did the flashing give you the developer version of miui?
I don't know if it has something to say. I had the oem unlock option set in developer section on settings.
Are you sure the phone stayed in EDL mode and not in Fastboot? A black screen with a little mi icon
Or that the recovery.img was really swapped with the twrp?
It worked on 2 phones I tried.
Survivor1990 said:
My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working
Click to expand...
Click to collapse
Doesn't look like it flash with EDL and qualcom drivers. Does it says device is a com port in the flasher utility?
I found this that might help. I had enabled usb debugging:
Be sure to Enable USB Debugging:-
Go to About phone > tap MIUI version at least 7 times to activate the Developer options. Go to Additional settings > Developer options > USB debugging > Enable it.
Before proceeding: Disable Driver Signature Enforcement in Windows 7/8/10 64-Bit
USB Data cable from your set.
Battery is charged at least 50%.
Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.
Survivor1990 said:
Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.
Click to expand...
Click to collapse
You need the qualcomm drivers
https://goo.gl/CPa5jd
To install the drivers follow this guide when connected in edl-mode:
http://en.miui.com/thread-235865-1-1.html
Follow point 5 and in point 6 use the drivers you have downloaded
There is no need to flash the entire partition set to install TWRP. It is enough to flash a single "recovery" partition using edited rawprogram0.xml, removing all partitions except "recovery" and either specifying TWRP image file name in "filename=" or renaming TWRP image file to "recovery.img".
patch0.xml must be edited too to remove all "<patch>" tags.
Additionally, flashing a modified "boot" image may be required.
I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!
Survivor1990 said:
I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!
Click to expand...
Click to collapse
Thanks for det update, I added an URL to the flasher on the first post
After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB
alexecus said:
After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB
Click to expand...
Click to collapse
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk
iJohnny said:
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked. I thought the partitioning got corrupted after I flashed using EDL. Glad TWRP was able to provide a quick fix
I got this working on my Helium 64gb Mi Max.
Please note that the instructions above is for the 32gb Hydrogen Mi Max. What I did differently is to get the recovery.img out of a Helium image.
Hi everyone,
This guide is intended for only snapdragon version of Lenovo devices which supports QFIL (Qualcomm Flashing Tool). For MediaTek Devices, you need different tools.
However, please understand that the device which I had to test in length was LENOVO K5 PLUS and thus, recovery, stock images and development is for K5 plus. As long as you have stock rom, custom recovery or custom rom of your specific device which you own, you can follow this guide for any snapdragon device but booting your device into DIAG mode might need different commands.
TABLE OF CONTENT
Recover Your Device
EFS
Driver Guide
TWRP
Root
Backup device
Stock and Custom Roms
Future Issues
FAQ
Credits
(Don't know what is brick or ANDROID BASICS, click here to quickly go through them) HIGHLY RECOMMENDED
Code:
This guide is for those who understand the risk of their actions.
I have fully tested this guide and I found no issues, however,
I am not responsible for world wars, broken phones,
flying machines, dead SD cards, [B]girlfriend breakups[/B]
or any damage by your actions and only join in the forum
with [B]popcorn[/B] to enjoy myself at your suffering in case you
didn't follow the instructions and later blamed me for it.
IMPORTANT :
I suggest you start this guide by directly going to POST 5 BACKUP FULL DEVICE before you intend to do any experiments with your device. Make a FULL BACKUP WHICH IS HIGHLY RECOMMENDED OR YOU WOULD NOT BE ABLE TO USE OTAs LATER) Requires no root
DRIVERS ARE MUST HERE
You can simply download all the drivers from post three and install them all. In case you have troubles, you can refer HERE for more details.
WHAT YOU NEED
1. DRIVERS
2. USB DEBUGGING
3. ADB
4. TOOLS & STUFF (all in attachments)
5. Little Common Sense
6. Zero Skills
USB DEBUGGING ON
1.Activate the Developer options (Settings> About phone> Device Information> to tap 7 times in Build number)
2. Enable USB debugging (Settings> Developer> USB Debugging)
3. Enable OEM unlock (Settings> Developer> Unlock OEM)
4. Done
SETUP A WORKING ADB
Download platform tools from here in attachment
Extract them to any location.
Navigate to the location where you have extracted platform.zip
Hold crtl+shift on keyboard and then use your mouse to right click on an empty area of the folder.
Select open command prompt here
An cmd window will open
You are ready to go
Alternatively,
if that does not work for you. Simply download the platform.zip and extract it to C:/platform-tools.
Rename platform tools folder to adb
Go to cmd from start menu
Type in these commands until you see C:\> in cmd.
You will need to type twice most probably.
Code:
cd..
cd..
then type the following once you are at C:\>
Code:
cd adb
You will be in ADB folder, which will be now like C:\adb>
Now you have a working adb
RECOVER YOUR BRICKED DEVICE
There are actually 3 methods in theory to recover your phone. However,I also found that sometimes you can not flash your device using download mode and in this case, fastboot mode is the only route which means you will need to use TWRP or find a method to go into EDL from fastboot. So after you brick your device, your device can present in the following states.
No recovery or download mode but fastboot mode
Download mode
Recovery mode
Phone goes into download mode on its own
Possible Solutions
TWRP Method if you have a custom recovery or only fastboot(tested and works)
QFIL (tested and works) if you can boot into download mode
Lenovo Updater (untested)
ONLY FASTBOOT ACCESSIBLE NO DOWNLOAD/ RECOVERY.
Phone goes directly into download mode but QFIL unable to flash at all. Need to find a way to boot into EDL. Currently under working. Check this here Gold for those who need to boot to edl from fastboot
Fail with status when trying to flash using QFIL
Code:
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Two ways possible. Flashed TWRP and it worked by restoring previous backup. Works like a charm
Fastboot to edl needs some work. If that could be achieved. It will be brick proof.
TWRP METHOD
Pre Requisites
Fully working TWRP with root (preferable)
backup of your device (highly recommended) or download stock flashable roms HERE
STEPS
Boot into fastboot mode (bootloader) by switching off your phone and then press volume - and power
Flash TWRP recovery using fastboot commands HERE
Flash your previously made backup using RESTORE function in TWRP
To flash recovery partition, you will need to select flash IMG instead of preset ZIP when you navigate to INSTALL. You will find it on lower left side
DOWNLOAD STOCK RECOVERY FOR YOUR DEVICE HERE
You will need to unroot your device as well from supersu settings if you want to return to FULL STOCK
In case you only have fast boot mode and no recovery AND no download mode
Pre Requisites
You must have a fully working TWRP and possibly rooted
flashable zips of your stock roms or any previously made backup
STEPS
Simply place your update.zip in your sd card if you are using stock images
Or you can copy your previously made TWRP backup in sd card
Restore using TWRP if you have a backup
or flash via TWRP if you are flashing stock Images
Done
I highly suggest you wipe your device in TWRP including system
QFIL METHOD
Download stock image for your device. Make sure you choose the correct file for your device or you can hardbrick your device
Install QPST and QFIL software from attachments.
You may need to install Microsoft Tools which are provided in attachment for QPST to work
I assume that you have already proper drivers installed
Extract your device stock images in any given location of your choice but prefer it like D:/stock images etc
Open QFIL from start menu
Refer to image attachments 1,4,5,6,7 for the next steps
Browser Programmer Path and navigate to where you have extracted stock images.
Select the file with the given extention .(firehose)
Next load XML file and select the image.
It will ask for another file which you will be able to locate in the same folder\
Connect your device and see if the port is detected as QD LOADER
Select DOWNLOAD under LOAD XML
Sit back and enjoy. It should take 5-10 minutes
NOTES FOR QFIL
Bootloader Method does not seem to work. Even after changing drivers and replacing them.
Works with keys too. Hold Volume + and power after switching off device and select download!
Requires EDL method
Lenovo Serial driver required
Adb reboot edl
Then install drivers for Qualcomm port
Flash as instructions
Erase Misc after flash
Wait for device to turn on
STATUS : COMPLETE
Last updated 26.08.16
EFS
Pre Requisites
Installed drivers. ( See Next posts for detailed guide.)
Enable USB debugging. See first post
Working ADB (Download from attachment)
You will need to move to the location where you have extracted adb.zip
Hold crtl+shift + mouse right click and select open command prompt here and then you can give commands.
Root
[*] Recovery
TWRP BACKUP
I find this method most superior to all others.
Download recovery from this forum. All credits to the developer to make it possible
DOWNLOAD IT FROM HERE. TWRP WITH EFS BACKUP AND MORE
After downloading the recovery, using a working adb. Enter commands
Does not require root
Code:
adb devices
adb reboot bootloader
fastboot boot LenovoA6020_TWRP-3.0.2-r3_7M.img
You will boot into recovery with Russian translation. Change translation to your local language as shown in attachments TWRP 1 and TWRP 2.
Make EFS and all other backup and keep it safe.
I suggest you copy this to your PC before you plan to do something else with your device.
Done
Enable DIAG MODE on your device using adb.
Code:
adb shell
su
setprop sys.usb.config diag,adb
Once your phone is in DIAG mode, you can utilise these methods for QCN.
QCN is a file that holds all your data regarding your signals, bluetooth, wifi, imei etc
If you lose it without a back, it may be very hard to fix your phone.
For first two methods, you need to be in DIAG mode. For the last two, you can make a backup on your mobile. All four methods require root.
QCN EXTRACTION BY QFIL
Simply open QFIL on your PC.
You will see
QPST>Tools> QCN backup and Restore.
Select Backup in your desired location
Done
QCN backup by QPST other tools.
1.First time you are trying to make a backup of your QCN using this method, you will need to add DIAG port which you enabled via adb commands in QPST.
For that , go to QPST>BIN>QPSTConfig. You might need to go to show all ports before you are able to add it.
2.Next go to, QPST > Bin> QPSTServer.exe
3.A globe would appear in taskbar. Click on it and select software download from the tab
4.Select port of your diagnostic mode in backup tab of software download.
5. Once in software download, backup your current QCN
4. Done
Backup by blocks
This is a better method to make a backup. You can either use adb commands or simply download PARTITION BACKUP APP from play store. This will automatically backup your partitions.
PARTITION BACKUP TOOL PLAYSTORE LINK
XDA FORUM LINK FOR ANY QUERIES
These are ways to check your device for partitions manually. You can make backup of these yourself as well.
Detailed guide is given here
Code:
adb shell
cat /proc/partitions
[B]OR[/B]
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
make sure you replace dw_mmc with your device partiton. (I have not checked it yet)
[B]OR[/B]
adb shell
cat /proc/partitions
adb remount
adb shell "su" "" "mount -o remount,rw /system"
adb push parted /system/bin/parted
adb shell
chmod 0755 /system/bin/parted
parted /dev/block/mmcblk0
print
Backup by tar.gz and Img
For this method you will need to download EFS BACKUP from playstore and then you can make a backup. I recommend make backup in all three formats.
EFS BACKUP PLAYSTORE
XDA FORUM LINK FOR THE APP
That's all you need for a good EFS Backup. Good Luck!
DRIVERS GUIDE
On Windows, it will automatically detect all drivers.
Make sure your device is attached to PC, before you install these drivers.
You may need to download drivers for ADB and QDLOADER which are all provided in Lenovo Usb driver.
So Installing these driver will be enough for you and you may need to manually select drivers for rest from lenovo folder
For ADB drivers use LENOVOUSB DRIVER 1.1.16 if your device is not detected by Windows.
For QHUB drivers use these in attachment named QDLOADER HS USB DRIVER.
Simply Install them and you are good to go.
INCASE YOUR DEVICE IS NOT DETECTED
All drivers are contained in these folder C:\Program Files (x86)\LenovoUsbDriver on your PC.
Go to My computer> Properties? Device Manager and see if you have any unknown devices like shown in attachment.
If you have, then I suggest you install manually.
Select unknown device and go in its properties.
Next go to drivers tab and select update drivers
Select Browse my computer for drivers
Let me pick from the list of devices
Select have disk
Move to folder C:\Program Files (x86)\LenovoUsbDriver
You will see that there are many folders.
ADB contains all ADB and Bootloader drivers
Use ADB folder if you are installing drivers for adb / fastboot/ bootloader.
Make sure you have usb debugging and device connected when you are installing these drivers. You have to be in normal mode for adb drivers
.
You can check if you have working adb by typing
Code:
adb devices
To download fastboot / bootloader drivers, simply first boot your device into fastboot.
Turn off device
hold power and volume down
Now try to install fastboot drivers
Serial Contains EDL drivers (Download mode drivers)
Select unknown device and go in its properties.
Next go to drivers tab and select update drivers
Select Browse my computer for drivers
Let me pick from the list of devices
Select have disk
Move to folder C:\Program Files (x86)\LenovoUsbDriver
You will see that there are many folders.
Use Serial if you are in download mode / EDL mode.
Working adb is required for this
You can go into EDL mode directly from adb commands by
Code:
adb reboot edl
OR
You can power off device
hold power and volume up
Select download mode and you are in EDL/ Download mode.
Now you can install drivers from above method
Make sure you select QDLOADER 9008 while installing EDL drivers.
How to enable QHUB drivers if no unknown/ undetected device is seen
Sometimes, your device is not detected in QFIL and you have all drivers installed and there is no unknown device in my computers> device manager.
For this, you will need to attach your device first.
Go to Device Manager by going into my computer properties
Look for ADB Interface drivers in device manager.
Update drivers for ADB interface and replace it with QDLoader HS USB driver.
If it asks for any permission, allow it.
In case your windows do not allow you to install these drivers , you need to turn off Digital Signature Verification in windows
run cmd as run as administrator
Type in these commands
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Restart
Then try again to reinstall drivers
To re-enable device verification on Windows
Code:
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Good luck
ROOT AND TWRP
HOW TO ACTIVATE USB DEBUGGING
1. Activate the Developer options (Settings> About phone> Device Information> to tap 7 times in Build number)
2. Enable USB debugging (Settings> Developer> USB Debugging)
3. Enable OEM unlock (Settings> Developer> Unlock OEM)
4. Connect the phone with the USB cable to the computer
5. Install the drivers that come on the CD cell partition.
TWRP:
Download TWRP from HERE or TWRP WITH EFS BACKUP AND MORE
Copy it to the folder where abd is installed.
On working adb, type in these commands
Code:
adb reboot bootloader
fastboot flash recovery LenovoA6020_TWRP-3.0.2-r3_7M.img
OR
fastboot flash recovery TWRP-k5-3.0.2-r2_shreps.img
This will permenantly flash twrp instead of Stock recovery.
If you just want to boot it once. check backup guide by using this command instead
Code:
fastboot boot <file name>
ROOT
Download the ZIP file SuperSU v2.76 and save it in the micro SD card.
Restart the phone in recovery mode:
Turn off the phone, then turn it on while pressing the volume up button. a screen appears with various options and choose "recovery".
You can even boot by adb commands using
Code:
adb reboot recovery
[*]
When opening the recovery, select Install and locate the file you downloaded just now.
Confirm execution flashing, restart the phone and voila!
ORIGINAL POST HERE
Editing the post with permission
BACKUP GUIDE
I HIGHLY RECOMMEND TO BACKUP YOUR DEVICE BEFORE YOU NEED TO EVEN ROOT YOUR DEVICE OR FLASH TWRP . IF YOU FAIL TO DO THIS, YOU WILL HAVE TROUBLE UPDATING YOUR PHONE VIA OTA ESPECIALLY IF YOU ROOT YOUR DEVICE
THIS IS MUST AS YOU CAN ALWAYS EASILY REVERT BACK TO YOUR ORIGINAL STOCK STATE IN CASE YOU NEED IT.
Download TWRP from HERE or Download recovery from this forum. All credits to the developer to make it possible DOWNLOAD IT FROM HERE. TWRP WITH EFS BACKUP AND MORE
YOU DO NOT NEED ROOT
I suggest you use the second TWRP as it supports more partitions than the first one.
Open working adb
TYPE IN
Code:
adb devices
adb reboot bootloader
fastboot boot LenovoA6020_TWRP-3.0.2-r3_7M.img
OR
fastboot boot TWRP-k5-3.0.2-r2_shreps.img
You will be booted into recovery.
Select Read only mode
Go to backup
Backup all partitions by selecting all of them
Swipe to confirm.
Make sure you have about 6GB for a full backup
You can skip user data if you do not want user apps backup
Nothing will be changed unless you enable system modification. So on first boot, simply do not enable system modification and go to backup and then backup all partitions. Keep these safe in case you need them.
Keep it in a safe place
HOW to restore back to your stock using TWRP. HERE
EFS Professional
doesnot work for me. Anyone can check by updating their busybox ? I couldnot on supersu 2.76 without updating busybox
CUSTOM ROMS
PACMAN
CYANOGENMOD 13
SOME HERE ON A RUSSIAN FORUM
STOCK ROMS
SOME HERE ON A RUSSIAN FORUM
Shreps said:
Stock Firmwares:
Firmware collection Thanks to @vache
Firmware collection, 2nd Mirror by @Shreps
TWRP Backups of Stock ROM:
A6020a40 - S027_160519_ROW
A6020l36 - S032_160401_LAS
Click to expand...
Click to collapse
Stock Rom guide to know which is your device by region
[*]American Models
Lenovo K5 Plus dual sim 6020l36 MSM8939v2 SD 616
Lenovo K5 Plus single sim 6020l37 MSM8939v2 SD 616
[*]European Models
Lenovo K5 Plus 6020a46 MSM8939v2 SD 616
[*]Asia Models
Lenovo K5 Plus 6020a46 MSM8939v2 SD 616
Lenovo Lemon 3 K32C36 MSM8939v2 SD 616
[*]Latin America ( Brazil, Chili )
Lenovo K5 dual sim A6020l36 MSM8939v2 SD 616
Some problems of the future. World war? Mobile mind control
OTA FAIL
ERROR 101 System doesnot allow change of carriers
download lenovo smart assistant
Install it and try to update it using this. If it does not update, find update package in lenovo tool folder
C:\Program Files (x86)\LenovoSmartAssistant\LenovoSmartAssistant\plugins\75fc9be6-29e6-495f-8c0a-93f9e1971133
Extract it and find system.zip and your country ota (both) in the sequence
Country.ota.zip (image taken from QPST)
Country2Default.ota.zip (image taken from QPST)
System.zip (image taken from FullOTA)
Does not flash with no error but system not updates and shows update again
Must flash system using QFIL
I used Indian firmware as I couldnot find for my region and thus I always had the error. Can not switch carriers.
I went to recovery and then 0>OTA> Flashed India OTA
Checked for system updates and this time it worked fully.
You can check which is supported by ####6020# in dialer
THIS IS GOLD. DO NOT MISS IT AT ALL
http://lenovo-forums.ru/forum/624-lenovo-k5-plus/
Credits
@Shreps for TWRP/ Custom roms and all his development efforts @samuro625 for TWRP and Rooting instructions @scritch007 cyanogenmod 13
@ more coming soon
@ anyone i left ? PM me and I will be happy to add your name!
@dongordo @axal Stock Firmware information
JUST WANT YOUR NAME FOR NO REASON ? PM and I will add it under this heading
Nice thread ?
Envoyé de mon Moto G (4)
Where on the Qualcomm site can one find the QIFL / QPST? Is it part of the Hexagon SDK?
Hnk1 said:
Custom roms
PACMAN
CYANOGENMOD 13
Orignal Sock Roms
Stock Rom guide to know which is your device by region
American Models
Lenovo K5 Plus dual sim 7020l36 MSM8939v2 SD 616
Lenovo K5 Plus single sim 7020l37 MSM8939v2 SD 616
European Models
Lenovo K5 Plus 7020a46 MSM8939v2 SD 616
Lenovo K5 7020a40 MSM8939 SD 415
Asia Models
Lenovo K5 7020a40 MSM8939 SD 415
Lenovo K5 Plus 7020a46 MSM8939v2 SD 616
Lenovo Lemon 3 K32C36 MSM8939v2 SD 616
Lenovo K5 note K52t38 Mediatek MT6755 Helio P10
Latin America ( Brazil, Chili )
Lenovo K5 dual sim A6020l36 MSM8939v2 SD 616
Click to expand...
Click to collapse
Wrong info. A7020 is K5 Note with MTK SoC.
Envoyé de mon Moto G (4)
Phylum said:
Where on the Qualcomm site can one find the QIFL / QPST? Is it part of the Hexagon SDK?
Click to expand...
Click to collapse
It is a took which was leaked and it is not officially available to you unless you manufacturer devices like samsung, lenovo etc
Download it from the first post. I have attached it in two posts!
Shreps said:
Wrong info. A7020 is K5 Note with MTK SoC.
Envoyé de mon Moto G (4)
Click to expand...
Click to collapse
Just to remember you guys, these methods DON'T WORK on A6020l36. Don't try this on your phone if it's this model, but if you did (like me), here is how to unbrick your phone.
https://www.youtube.com/watch?v=6pF2nT2SsHg
rafaellancas said:
Just to remember you guys, these methods DON'T WORK on A6020l36. Don't try this on your phone if it's this model, but if you did (like me), here is how to unbrick your phone.
https://www.youtube.com/watch?v=6pF2nT2SsHg
Click to expand...
Click to collapse
I think you are mistaken. I have QFIL method in my guide which is used by the user in the video.
Hnk1 said:
I think you are mistaken. I have QFIL method in my guide which is used by the user in the video.
Click to expand...
Click to collapse
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).
rafaellancas said:
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).
Click to expand...
Click to collapse
Really?
Sent from my Lenovo A6020a46 using XDA-Developers mobile app
Is this software almost the same as XIAOMI MIFLASH (it has EDL flashing mode) ???
Any hope for Vibe X3 etc? getting it dirt cheap and I need a new phone
rafaellancas said:
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).
Click to expand...
Click to collapse
It should work flawlessly. I do not see why! Did you do as instructed ?
JoZ3 said:
Really?
Sent from my Lenovo A6020a46 using XDA-Developers mobile app
Click to expand...
Click to collapse
nguyenlucky said:
Is this software almost the same as XIAOMI MIFLASH (it has EDL flashing mode) ???
Click to expand...
Click to collapse
Well, I have not tested this with a XIOAMI device with QFIL. In theory it should work, but I have always preferred MIFLASH as it is designed specifically for Xiaomi devices. Most of snapdragon devices has an emergency download mode.
minigreen said:
Lenovo K5 Plus single sim 6020l37 MSM8939v2 SD 616
Click to expand...
Click to collapse
Do you want me to add it to the guide ? Which region is your device from ?
kkn_13 said:
Any hope for Vibe X3 etc? getting it dirt cheap and I need a new phone
Click to expand...
Click to collapse
What do you mean ? QFIL should work on all lenovo devices (snapdragon) provided you have proper stock images which are specific to your device. Google is your friend ? TWRP and development is not currently my aim for any device yet. As i did all my experiments using a K5 plus so I could write in length about it specifically.
Hnk1 said:
It should work flawlessly. I do not see why! Did you do as instructed ?
Well, I have not tested this with a XIOAMI device with QFIL. In theory it should work, but I have always preferred MIFLASH as it is designed specifically for Xiaomi devices. Most of snapdragon devices has an emergency download mode.
Do you want me to add it to the guide ? Which region is your device from ?
What do you mean ? QFIL should work on all lenovo devices (snapdragon) provided you have proper stock images which are specific to your device. Google is your friend ? TWRP and development is not currently my aim for any device yet. As i did all my experiments using a K5 plus so I could write in length about it specifically.
Click to expand...
Click to collapse
Thank you for your time man! Twrp does not work with my phone (I mean, I can install it, and root/flash some stuff, but it definatelly does not work for flashing any of the images uploaded here, including the backups or the pac/cyanogenmod roms, they all give the same compatibility erros as the roms were not made for this phone). I followed the instructions, wiped system/data/dalvik, tried to flash, compatibility erros. There is no way of backup too, since it crashes at the ending. I'm starting to think that my phone is not the a6020l36 (even though it says that on a label under my battery, on my phone's setup and also on the box), but some variant made for my country only. And I know that are brazillians that claim to make it work on their phones, but since there's no way to guarantee that we really have the same phone, I don't now what to do. The QFIL stock rom (that I got from another place too, the ones uploaded here don't work either (another reason to think that my a6020l36 is different from the ones people claim to work here)). Thank you again for your time.
******************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!!!!
I'm new to MiUi and request for some help.I have a Redmi Pro which came preloaded with a ROM from a vendor. I managed to flash Chinese Developer ROM 7.6.10 on the phone. I want to use miui.eu ROMs as there is no other global ROM for Redmi PRO. I have requested and been granted permission for unlocking my device however the unlock tool doest detect my phone in fastboot mode. USB debugging is enabled. the phone appears as 'connected' when I use version 1 of the unlock program but prompts me to use a newer version when i click on un lock. I can access the device and it's contents in MTP mode. attached is a screenshot of the Unlock tool page. I've removed and reinstalled drivers for the device but it still appears as not connected. I checked in ADB, the device does appear in fastboot mode.
I have a Grand Prime Duos (SM-G530H), currently running an Android version 4.4.4 and I wanted to install a custom ROM to have a higher version of Android. (Tried installing LineageOS 17.1 from itexpert.120, but any custom ROM with a higher version of Android would do)
Problem 1: No custom recovery seems to work.
I installed the TWRP app and tried to flash 4 different versions of their recovery images (from twrp-3.7.0_9-0-fortuna3g.img to twrp-3.4.0-0-fortuna3g.img) and all of them resulted in a unless glitched gray recovery screen.
I also tried the CWM app but it fails to download a recovery image for the device, tried looking online for a image file but didn't find one either.
In the end I reverted the recovery to the default one that I had backed up.
Problem 2: ADB works but fastboot doesn't.
I downloaded the ADB tools to try and flash the ROM from my computer instead. The ADB commands work, but when the device enters recovery mode the fastboot commands don't work. ("fastboot devices" doesn't even list the device)
Went to check the drivers. Most tutorials say to open the device manager and look for the phone device with an exclamation mark and update the driver with ones downloaded from the official site. To my surprise the device doesn't show up at all in the device manager (not even with an exclamation mark). Trying to install the drivers anyway says it's already installed.
The Odin software showed the same problems, detects the device when it's on, but doesn't detect it when in recovery mode.
Problem 3: Error when installing directly through the recovery mode options.
This probably wouldn't work for technical reason I'm not aware of, but I went and tried anyway. On the default recovery mode there are 2 options, apply update from ADB and apply update from external storage. Tried both, the first using the command "adb sideload <lineage rom file>" and the second using the ROM file in a SD card. Both begin to unpack and install the file but after a while throw an error "E: failed to verify whole-file signature", then the device boots to the usual OS.
So, is there anything else I can try? any other recovery images or hacks that won't give me the glitched recovery that TWRP had? Or another method to install a ROM without fastboot? Maybe using another file format in problem 3?
OBS: the device is rooted and has no "OEM unlock" options in its settings
delete the samsung usb drivers and install an older version. only way you can flash custom recovery is with odin. only way to flash custom rom is with custom recovery. fastboot and sideload wont work, this isnt a nexus
You think the reason why the custom recovery was glitched is because it was flashed through the TWRP app and not Odin? Seems unlikely. Is there any non-TWRP recovery image for my model you can point me to?