Hi there,
I finally got around to try unlocking my axon/root/custom rom and ran into problems right in the beginning.
I'm using the Axon Toolkit 1.1.1 (that should fully work with A2017G) and followed the steps to unlock the bootloader (as afaik fastboot isn't working on the G-Variant before unlock/TWRP).
So I chose option 6-unlock, MiFlash launches and I have to select the folder with the files to flash, following the instructions of the toolkit.
For the record - I'm on MM B08.
The unlock files the AxonToolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' containing a fastboot.img.
Can I use these files or are they only for the A2017U (as the name would suggest)??
My first thought is 'No', but then if the Toolkit is supposed to fully support the A2017G?
There is a also another downloadable file from a different thread called 'TWRP_UnlockBootloader_by_DrakenFX.zip' (by DrakenFX for Generic Device/Other), which sounds more like it, BUT:
This one is normally flashed with TWRP, not MiFlash.
In this thread one would use tenfar's signed (but containing a bug) version of TWRP to install that file BEFORE the bootloader is unlocked.
I'm however keen to jump the flawed version and
- unlock first
- flash TWRP
- flash above fastboot enabler
- flash modem/custom rom (RR) etc.
So could someone please confirm:
With a 2017G (6.0MM B08) is it possible to
- Unlock the bootloader first without using tenfar's 3.0.2 TWRP?
- Which Unlock file should I use? The first one? Or can I use the generic (second) one with MiFlash or TWRP only?
- If that works, did you simply go Advanced Options<Flash boot/bootloader/modem/recovery<choose recovery partition<select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img with the Toolkit? (or did you e.g. have to install adb 1.4.2 first to get twrp on the device via adb)
Thanks a lot for the help everyone - I know there are a lot of Guides out there, unfortunately (and I was reading through the whole threads for all of them) it gets more confusing with each one, as they all do things slightly differently, for slightly different versions, etc.
The Toolkit seems like a great start to simplify things a lot, but there is no step-by-step guide how to exactly use it for the 2017G (using what files).
The guide using the toolkit for the A2017G uses it in command line mode - that didn't work for me. Not sure if it's using an older version, but as soon as I start the tool with a command line, it kills the existing process and comes up with the dialog (I'm also on Win7 32-bit, using 32-bit MiFlash)...
@Whoooo?
This guide is suited for you:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
There are some steps that could be simplified, but there are all OK.
Personally I think A2017G is not working well with MiFlash (several problems: difficulty to recognize the phone, MiFlash software is touchy,
many versions, need time window in EDL mode, receive hello packet error etc...). The above guide did not mention MiFlash neither.
Do not use Qualcomm bulk drivers that gives you Qualcomm HS-USB QDLoader 9008 for use with MiFlash.
Recommendation: Use Zadig (http://zadig.akeo.ie/) to have WinUSB driver for QUSB_BULK. So probably you need to uninstall the driver first ("adb reboot edl", then start Windows
device manager, Uninstall and delete the driver Qualcomm HS-USB QDLoader 9008). Unplug and replug the phone, it will appear under unknown device QUSB_BULK.
Run zadig to install driver (select the WinUSB driver) => the phone will appear OK under USB peripheral:
it will be able to receive command from axon7tool in EDL mode.
To answer your questions:
>With a 2017G (6.0MM B08) is it possible to
>- Unlock the bootloader first without using tenfar's 3.0.2 TWRP?
Yes you can do that, before installing TWRP. You can also as in the guide, install TWRP first, then unlock bootloader.
Note: if you choose to unlock the bootloader first, then you can directly install latest TWRP 3.1.1-0 (unsigned) without the need to install the signed tenfar's TWRP first as with locked bootloader, then upgrade TWRP to 3.1.1-0.
The guide is applicable for any version of MM up to V1.0.0B11.
>- Which Unlock file should I use? The first one? Or can I use the generic (second) one with MiFlash or TWRP only?
If you follow the above mentioned guide, you do not need any of these files.
>- If that works, did you simply go Advanced Options<Flash boot/bootloader/modem/recovery<choose recovery partition<select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img with the Toolkit? (or did you e.g. have to install adb 1.4.2 first to get twrp on the device via adb)
You want to install TWRP? Follow the mentioned guide.
My own remarks on top of the guide :
Part A) step 15): Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK".
You should see the phone correctly installed thanks to Zadig and not unknown device with yellow cross.
Steps 16 to 19 could be skipped (since you can have full ROM image to restore boot/recovery if needed: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547).
Step 20) In command, type "axon7tool -w recovery": this means you should have in the directory the file recovery.bin which is exact copy of twrp_rec_tenfar.img.
Attention to enable file extension display in Windows.
Part B) steps 1 to 13 could be skipped and replaced by:
Boot into TWRP : either "adb reboot recovery" or Power + Vol Up.
Inside TWRP, flash TWRP_UnlockBootloaderPackage_by_DrakenFX.zip
https://androidfilehost.com/?fid=24723757092307343
to enable fastboot (this patch aboot and fastboot so fastboot command to unlock bootloader will be accepterd).
Then follow steps 14 to 18.
Note: if you do not enter TWRP immediately in step 17) after unlock procedure, maybe you will boot to system (Android),
and probably password asked, cancel, boot to TWRP and format data (ext4fs): Power + Volume Up (or if you can boot to system, type command "adb reboot recovery").
Note: important: in TWRP do not allow system modifications. If you allow system modifications and not flash no-verity-opt-encrypt-5.1.zip
or not flash SuperSU 2.79 immediately, you will get in trouble at boot.
Now update TWRP (if not yet done): boot in to TWRP, Install, Image, choose latest TWRP 3.1.1-0 taken from
https://eu.dl.twrp.me/ailsa_ii/
File twrp-3.1.1-0-ailsa_ii.img
md5 94018d5d92a89657ccd0420a0464859b
then check "boot partition".
Reboot to recovery and check that TWRP is the latest.
Done. Now with unlocked bootloader and TWRP latest version, you can do anything with the phone
(backup/restore, install latest stock Marshmallow or Nougat with TWRP https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069,
flash SuperSU2.79 for root, install custon ROM with TWRP...).
dnlilas said:
@Whoooo?
This guide is suited for you:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
There are some steps that could be simplified, but there are all OK.
Personally I think A2017G is not working well with MiFlash (several problems: difficulty to recognize the phone, MiFlash software is touchy,
many versions, need time window in EDL mode, receive hello packet error etc...). The above guide did not mention MiFlash neither.
Do not use Qualcomm bulk drivers that gives you Qualcomm HS-USB QDLoader 9008 for use with MiFlash.
Recommendation: Use Zadig (http://zadig.akeo.ie/) to have WinUSB driver for QUSB_BULK. So probably you need to uninstall the driver first ("adb reboot edl", then start Windows
device manager, Uninstall and delete the driver Qualcomm HS-USB QDLoader 9008). Unplug and replug the phone, it will appear under unknown device QUSB_BULK.
Run zadig to install driver (select the WinUSB driver) => the phone will appear OK under USB peripheral:
it will be able to receive command from axon7tool in EDL mode.
To answer your questions:
>With a 2017G (6.0MM B08) is it possible to
>- Unlock the bootloader first without using tenfar's 3.0.2 TWRP?
Yes you can do that, before installing TWRP. You can also as in the guide, install TWRP first, then unlock bootloader.
Note: if you choose to unlock the bootloader first, then you can directly install latest TWRP 3.1.1-0 (unsigned) without the need to install the signed tenfar's TWRP first as with locked bootloader, then upgrade TWRP to 3.1.1-0.
The guide is applicable for any version of MM up to V1.0.0B11.
>- Which Unlock file should I use? The first one? Or can I use the generic (second) one with MiFlash or TWRP only?
If you follow the above mentioned guide, you do not need any of these files.
>- If that works, did you simply go Advanced Options<Flash boot/bootloader/modem/recovery<choose recovery partition<select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img with the Toolkit? (or did you e.g. have to install adb 1.4.2 first to get twrp on the device via adb)
You want to install TWRP? Follow the mentioned guide.
My own remarks on top of the guide :
Part A) step 15): Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK".
You should see the phone correctly installed thanks to Zadig and not unknown device with yellow cross.
Steps 16 to 19 could be skipped (since you can have full ROM image to restore boot/recovery if needed: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547).
Step 20) In command, type "axon7tool -w recovery": this means you should have in the directory the file recovery.bin which is exact copy of twrp_rec_tenfar.img.
Attention to enable file extension display in Windows.
Part B) steps 1 to 13 could be skipped and replaced by:
Boot into TWRP : either "adb reboot recovery" or Power + Vol Up.
Inside TWRP, flash TWRP_UnlockBootloaderPackage_by_DrakenFX.zip
https://androidfilehost.com/?fid=24723757092307343
to enable fastboot (this patch aboot and fastboot so fastboot command to unlock bootloader will be accepterd).
Then follow steps 14 to 18.
Note: if you do not enter TWRP immediately in step 17) after unlock procedure, maybe you will boot to system (Android),
and probably password asked, cancel, boot to TWRP and format data (ext4fs): Power + Volume Up (or if you can boot to system, type command "adb reboot recovery").
Note: important: in TWRP do not allow system modifications. If you allow system modifications and not flash no-verity-opt-encrypt-5.1.zip
or not flash SuperSU 2.79 immediately, you will get in trouble at boot.
Now update TWRP (if not yet done): boot in to TWRP, Install, Image, choose latest TWRP 3.1.1-0 taken from
https://eu.dl.twrp.me/ailsa_ii/
File twrp-3.1.1-0-ailsa_ii.img
md5 94018d5d92a89657ccd0420a0464859b
then check "boot partition".
Reboot to recovery and check that TWRP is the latest.
Done. Now with unlocked bootloader and TWRP latest version, you can do anything with the phone
(backup/restore, install latest stock Marshmallow or Nougat with TWRP https://forum.xda-developers.com/axon-7/development/stock-rom-a2017g-twrp-flashable-images-t3599069,
flash SuperSU2.79 for root, install custon ROM with TWRP...).
Click to expand...
Click to collapse
What?? Zadig drivers never worked for me on MiFlash. Also if you restart the EDL mode (vol up+dn+power) if you do something and it fails, it will probably work. I've been using MiFlash a lot on A2017G and don't have all those problems you mentioned
Using Controllerboy's guide would be better though, true
Hi there,
And thanks a lot both of you!
I think that pins down my problem:
- I cannot use Controllerboy's guide as the linked axontool works only on Win64 and the Toolkit for Win32 doesn't support command line...
- I managed to get the QUSB_Bulk driver installed, but MiFlash needs Qualcomm HS-USB QDLoader 9008?? Can anyone confirm this? And how do I get these back again?
- Still not sure if the 'A2017U_FASTBOOT_UNLOCK_EDL' is the right file to flash - I noticed the trial Toolkit (v1.2) has a different one?
So I either now need a guide to use the newest Toolkit version, or get MiFlash running with the right file (starting with the Unlock)...
Whoooo? said:
Hi there,
And thanks a lot both of you!
I think that pins down my problem:
- I cannot use Controllerboy's guide as the linked axontool works only on Win64 and the Toolkit for Win32 doesn't support command line...
- I managed to get the QUSB_Bulk driver installed, but MiFlash needs Qualcomm HS-USB QDLoader 9008?? Can anyone confirm this? And how do I get these back again?
- Still not sure if the 'A2017U_FASTBOOT_UNLOCK_EDL' is the right file to flash - I noticed the trial Toolkit (v1.2) has a different one?
So I either now need a guide to use the newest Toolkit version, or get MiFlash running with the right file (starting with the Unlock)...
Click to expand...
Click to collapse
Did you mean that you run Windows 32-bit so you can't use axon7toolkit (64-bit)?
To get back Qualcomm HS-USB QDLoader 9008 needed for MiFlash, in EDL mode, in Windows device manager, uninstall the driver QUSB_BULK and check option delete the driver. Unplug and replug the phone, then under unknown device QUSB_BULK install the Qualcomm HS-USB QDLoader 9008 driver from Qualcom bulk driver (qcser.inf).
dnlilas said:
Did you mean that you run Windows 32-bit so you can't use axon7toolkit (64-bit)?
To get back Qualcomm HS-USB QDLoader 9008 needed for MiFlash, in EDL mode, in Windows device manager, uninstall the driver QUSB_BULK and check option delete the driver. Unplug and replug the phone, then under unknown device QUSB_BULK install the Qualcomm HS-USB QDLoader 9008 driver from Qualcom bulk driver (qcser.inf).
Click to expand...
Click to collapse
Hi there,
Yes, the version you linked doesn't work on Win 32 - hence I#m using this one: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Unfortunately it doesn't seem to support command line.
I reinstalled the Qualcomm drivers - MiFlash now detects the phone, but when I try to select the package it first complains 'cannot find script', then it shows an error 'cannot receive hello package' and times out after trying to reset the status... aaargh
Whoooo? said:
Hi there,
Yes, the version you linked doesn't work on Win 32 - hence I#m using this one: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Unfortunately it doesn't seem to support command line.
I reinstalled the Qualcomm drivers - MiFlash now detects the phone, but when I try to select the package it first complains 'cannot find script', then it shows an error 'cannot receive hello package' and times out after trying to reset the status... aaargh
Click to expand...
Click to collapse
For MIFlash problems, I already mentioned. I cannot even get MiFlash to recognize my phone, while similar tool like Qualcom Qfil/QPST can without problem.
You said "the version you linked doesn't work on Win 32" : I did not understand. Which one, axon7tool-1.5-win64.exe ? This is command line tool only.
dnlilas said:
For MIFlash problems, I already mentioned. I cannot even get MiFlash to recognize my phone, while similar tool like Qualcom Qfil/QPST can without problem.
You said "the version you linked doesn't work on Win 32" : I did not understand. Which one, axon7tool-1.5-win64.exe ? This is command line tool only.
Click to expand...
Click to collapse
Hi there,
Yes, that's (one of) my problem(s), the axon7tool-1.5-win64.exe doesn't work (even in command line) on Win 7 32-bit. At least for me...
EDIT:
Aaaaaargh: MiFlash, 'Run as Admin' and the fastboot package flashed successful.... no problems by the looks of it.
Also no idea how to check if the bootloader is really unlocked...
OK I did not realize that you are running Windows 7 32-bit, this is why axon7tool-1.5-win64.exe (64-bit) of course could not be run.
I think the best for you is manage to find out a computer running Windows 64-bit and use axon7tool-1.5-win64.exe (EDL mode, QUSB_BULK WinUSB driver) to install TWRP (tenfar). Once TWRP installed, you can then use your Windows 7 32-bit to unlock bootloader, upgrade TWRP, flash stock ROM, flash custom ROM etc... all using TWRP as I mentioned previously.
OK, got it (I think I will post a guide here soon, clarifying some things) -
I now hav unlocked bootloader and TWRP 3.1.
Question, with dm-verity, do I swipe to 'allow modifications' before flashing e.g. RR? Or do I flash a non-stock kernel first (or does RR use a different one)? And if, which one?
Sorry for the stupid question, I haven't read up on dm-verity before...
https://twrp.me/devices/zteaxon7.html
I was trying to flash modified recovery image using magisk after that my phone is dead almost.
My phone don't boot in to android. I can't charge my phone because I get message on the beginning
my system is moddifyed my phone shut down automatically after 5 seconds, also i can't unlock bootloader via fastboot i get information "unlock operation is not allowed" .
I have Leeco 650x with mtk helio x27.
I only flashed modified recovery in magisk after that I disabled usb debug and oem unclock. after restart my phone I can't unlock my bootloader and I can't continue bootup to android.All I need to do is restore somehow original recovery.
But how to do that without unlocked bootloader in my situation?
I try to flash new Rome using flash tool but I have error 0xC0030003
Is here any powerful person to solve the problem.
It looks like you flashed firmware for wrong device. Settings say x650 instead of x720 (I am assuming you have x720). I think your best bet is probably the QFIL restore.
https://www.google.com/amp/s/forum....to/guide-unbrick-le-pro3-tested-t3622340/amp/
If you do not have an x720, please disregard this post.
I have 650x with mtk processor 100 procent. I only flashed modified recovery in magisk after that I disabled usb debug and oem unclock. after restart my phone I can't unlock my bootloader and I can't continue bootup to android.All I need to do is restore somehow original recovery.
But how to do that without unlocked bootloader in my situation?
I try to flash new Rome using flash tool but I have error 0xC0030003
LucasNoob said:
I have 650x with mtk processor 100 procent. I only flashed modified recovery in magisk after that I disabled usb debug and oem unclock. after restart my phone I can't unlock my bootloader and I can't continue bootup to android.All I need to do is restore somehow original recovery.
But how to do that without unlocked bootloader in my situation?
I try to flash new Rome using flash tool but I have error 0xC0030003
Click to expand...
Click to collapse
You need to find the LETV X650 Scatter file. I do not know those phones very well. A X600 file may work, you will need to do a lot of research before attempting or you can damage your partitions.
Here is a link for the firmware. https://fapgem.com/video/4tnZoa0H9Q...-firmware-eui-5925s-install-via-fastboot.html
There is a chance that if you can get your PC to see the phone that you may be able to flash the stock firmware. It will not hurt to try it. Again , read extensively before doing anything.
There is a website called Android brick. They have an article on unbricking your phone but I could not access the link. Just Google, or use DuckDuck Go and search Letv X650 Scatter file unbrick.
I just now found this, which may be your solution: https://stephaniefulke.blogspot.com/2015/09/how-to-flash-unbrick-your-mediatek.html
Good luck
Hi,
recently I hardbricked mi Mi5s. After reading and trying a lot of things, I managed to unbrick it. So, I left this as a guide of things to try in case someone else hardbricks it.
How did I brick it:
I was trying to fix finger sensor by flashing in EDL mode fastboot ROMS, in order to reflash persistent.img . I accidentally flashed a mi5 (gemini) ROM on the mi5s. After that, the PC recognised the device only as "hs-usb qdloader 9008" in the Windows Device Manager, associated with a COM port. (In my pc, it was COM7 or COM8).
How did I unbrick it:
I disabled integer_checks (following the androidbrick guide provided below) and installed new driver for qdloader 9008.
After that, I used miFlashTool (https://www.xiaomiflash.com/download/) and flashed latest global stable fastboot rom (https://en.miui.com/thread-5927598-1-1.html)
Note: if miFlashTool crashes, create a folder in miflash folder, and rename it to "log".
If you don't have a unlocked bootloader, you *must* use the test-point trick. (Use a deep flash cable) .
Links:
Driver that worked: https://www.mediafire.com/file/so0uvkd6nm6ie1m/Driver_x64.cab/file (x64) & https://www.mediafire.com/file/ryjc83s2ku6mmh5/Driver_x86.cab/file (x86)
Although it didn't work for me (i suspect thats becouse i hadn't installed the driver above), guide to use Qualcomm QFIL: https://en.miui.com/thread-432217-1-1.html
Another guide to Qualcomm QFIL: https://www.androidbrick.com/ultima...s-are-unbrickable-qhsusb_dload_qpst_qfil_edl/
If the PC doens't detect the mobile after installing that driver, it means that you're NOT into EDL mode. If you can't enter fastboot or EDL mode, you need a Deep flash cable. You can fabricate yourself one (there are youtube tutorials for that) using a test-point , or you can buy one from Aliexpress: https://es.aliexpress.com/item/PHON...290.html?spm=a2g0s.9042311.0.0.594263c0eXl7Lh
Guide to understand how EDL works and how to exploit it: https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
Other useful links: https://forum.xda-developers.com/mi-5s/help/stupid-mistake-mi5s-bricked-t3725331
Other useful links: https://www.youtube.com/watch?v=Ds2Bp2TBizc
Other useful links:https://www.htcmania.com/showthread.php?t=1204227&page=5 (Spanish post)
Other useful links: https://www.youtube.com/watch?v=Mp_VdEqi0rc
Good luck!
Thank you for this great guide. Have a good day
is you fingerprint works after edl flashing?
Fastboot is no longer displayed, the screen remains dark. But I hear that the device is recognized. I use a depp flash cable.
MiFlash 20191206
port 9
status: try to reset status
after 18 sec flashmessage: write time out, maybe device was disconnected.