Hello,
I tried to install a new ROM on my phone (for the first time).
I unlock it with (unlock.bin) and checked with adb command if it is unlocked.
I installed TWRP. I boot myphone in factory mode, and TWRP started. But I failed install to ROM...
So now I have a problem :
If I try to access to TWRP : I boot in factory mode, select "yes" twice, and my phone boot a second time again and lock on the screen "LG".
I told me I can reinstall it with adb, but adb can't see phone connected on my computer (because no os)
Do you have a solution ?
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
Android# said:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
Click to expand...
Click to collapse
Thank you for the link. I don't understand step 2 :
Step 2) Install QDLoader Driver (Select the driver for your system, 32 or 64-bit)
Use The new Signed driver.
in the archive(download in google drive) I don't found the exe, so I download and install QDLoader driver from internet.
But what does that mean "use the new signed driver" ? edit: how I use (NEW)(Signed)9008 Drivers.rar ?
edit: In my driver management I didn't see Qualcom HS-USB
GameKoyColor said:
Thank you for the link. I don't understand step 2 :
Step 2) Install QDLoader Driver (Select the driver for your system, 32 or 64-bit)
Use The new Signed driver.
in the archive(download in google drive) I don't found the exe, so I download and install QDLoader driver from internet.
But what does that mean "use the new signed driver" ? edit: how I use (NEW)(Signed)9008 Drivers.rar ?
edit: In my driver management I didn't see Qualcom HS-USB
Click to expand...
Click to collapse
Sorry for late reply. If I remember correctly, phone has to be connected to the computer in EDL mode for you to see the Qualcom HS-USB. Also, you just unzip the .rar file and driver is there. Sorry, I did this long time ago and I think once I connected the phone in EDL mode with the PC, it showed up in device manager and I installed the driver to it.
Related
hi guys i ve a problem.
i ve wiped system data cache, and then i wiped my sd card (why am i so stupid)
now the phone is in twrp, but in fastboot the computer can't find it, he gave me a message "enable USB debug".
what can i do?
thanks
sorry for bad english i'm italian
If are trying to use fast boot, then you need to boot into the boot loader. Recovery is different.
Sent from my iPad using Tapatalk
Somehow when it comes to Recovery's and people with bad English they call the recovery "He", it actually makes it funny in a way.
Fastboot only is in the bootloader.
Sent from my Nexus 4 using xda app-developers app
narger said:
hi guys i ve a problem.
i ve wiped system data cache, and then i wiped my sd card (why am i so stupid)
now the phone is in twrp, but in fastboot the computer can't find it, he gave me a message "enable USB debug".
what can i do?
thanks
sorry for bad english i'm italian
Click to expand...
Click to collapse
For starters, if you got any questions, post in the Q&A section: http://forum.xda-developers.com/forumdisplay.php?f=1909
Download Universal Naked Driver here: http://forum.xda-developers.com/showthread.php?t=1996051
or you can search for Google USB Driver. Extract them into a folder.
And then you need to boot your phone into fastboot/bootloader mode, connect the phone to your pc. Open Device Managers, right click the unidentified "Nexus 4", choose update drivers.
Locate the driver in the directory above, let it install.
After you completed the installation, fastboot should works normally.
ksilver89 said:
For starters, if you got any questions, post in the Q&A section: http://forum.xda-developers.com/forumdisplay.php?f=1909
Download Universal Naked Driver here: http://forum.xda-developers.com/showthread.php?t=1996051
or you can search for Google USB Driver. Extract them into a folder.
And then you need to boot your phone into fastboot/bootloader mode, connect the phone to your pc. Open Device Managers, right click the unidentified "Nexus 4", choose update drivers.
Locate the driver in the directory above, let it install.
After you completed the installation, fastboot should works normally.
Click to expand...
Click to collapse
i've instllaed universal naked driver, now in device managers i found "Google Nexus 4 Bootloader Interface".
i put it in fastboot, but the "fastboot devices" command doesn't find nothing!
(sorry again for english)
narger said:
i've instllaed universal naked driver, now in device managers i found "Google Nexus 4 Bootloader Interface".
i put it in fastboot, but the "fastboot devices" command doesn't find nothing!
(sorry again for english)
Click to expand...
Click to collapse
You need a newer version of fastboot, if you downloaded it from Android SDK, open SDK Manager and update the "Android SDK platform-tools".
Edit:
Or you can use the zip file attached below... by the way, this is rev17 (not the latest version).
Edit2:
Opps, reupload.
ksilver89 said:
You need a newer version of fastboot, if you downloaded it from Android SDK, open SDK Manager and update the "Android SDK platform-tools".
Edit:
Or you can use the zip file attached below... by the way, this is rev17 (not the latest version).
Click to expand...
Click to collapse
You need the ADB USB DLL Drivers has well also with ADB.exe.
Sent from my Nexus 4 using Tapatalk 4
Hi, i was playing with my yota2 and think i messed up the radio files, now the phone is dead, no vibration no screen light, nothing.
i tried some methods and was able to get the phone recognized as 'Qualcomm HS-USB QDLoader 9008' but dont know what to do. btw i opened up the phone, is there anyway to revive it or should i just order another one?
Thanks alot
Try flashing it with yotaflasher. Post any errors if they occur.
Hi
My phone does not get recognized. When trying to use yotaflasher it is stuck at 'waiting for device'
yotafree said:
Hi
My phone does not get recognized. When trying to use yotaflasher it is stuck at 'waiting for device'
Click to expand...
Click to collapse
Your adb drivers are not loaded on your laptop/PC , there are many threads about this on here. You cannot do a fastboot flash without these drivers.
Run an adb command from a DOS "cmd" window on your laptop to check this, this is explained on here.
i had a hardbrick yotaphone2 also. only qualcomm 9008 detected. had tried all the way to flash it back due to wrong rom being flashed. please advice....no fastboot, tried power off and volume down, tried kick out from EDL mode...tried qualcomm flasher which support EDL flashing but downloaded rom cannot flash due to only img and bin file, there is no rawprogram xml file.....anybody have dumped rom for this phone?
Thank you but did you forget to add the link which command to run ??
Parmo100 said:
Your adb drivers are not loaded on your laptop/PC , there are many threads about this on here. You cannot do a fastboot flash without these drivers.
Run an adb command from a DOS "cmd" window on your laptop to check this, this is explained on here.
Click to expand...
Click to collapse
Thank you but did you forget to add the link which command to run ??
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
Just got an Axon 7. I want to root and install TWRP.
I have:
A2017U B25 Completely Stock
Windows 10 64bit
I've installed Qualcomm drivers, and put this device in EDL mode, and it shows up as COM4 in Device Manager, but I cannot get for the life of me, MiFlash to recognize this phone when I'm in EDL Mode.
I could officially update this via SD card i guess, but I don't have an SD Card at the moment.
Why won't MiFlash recognize this? I've tried 2 cables, both USB 2.0 and USB 3.0 ports in the back of the computer. What gives?
kaivorth said:
Just got an Axon 7. I want to root and install TWRP.
I have:
A2017U B25 Completely Stock
Windows 10 64bit
I've installed Qualcomm drivers, and put this device in EDL mode, and it shows up as COM4 in Device Manager, but I cannot get for the life of me, MiFlash to recognize this phone when I'm in EDL Mode.
I could officially update this via SD card i guess, but I don't have an SD Card at the moment.
Why won't MiFlash recognize this? I've tried 2 cables, both USB 2.0 and USB 3.0 ports in the back of the computer. What gives?
Click to expand...
Click to collapse
If your system is working you shouldn't need an SD card... Just get the zip, get the update.zip from it, and put it in the root of the internal storage.
If you can't:
Go to the Device manager, right click on the Qualcomm HS-USB QDLoader 9008 thingy, Properties, check that the data rate is set at 115200 or 128000. (those numbers are out of memory, but i think they're right). If that was right, then leave Device Manager open, keep MiFlash prepared, and hold the 3 buttons (power and vol + and -) until device manager refreshes, then attempt to flash
Choose an username... said:
If your system is working you shouldn't need an SD card... Just get the zip, get the update.zip from it, and put it in the root of the internal storage.
If you can't:
Go to the Device manager, right click on the Qualcomm HS-USB QDLoader 9008 thingy, Properties, check that the data rate is set at 115200 or 128000. (those numbers are out of memory, but i think they're right). If that was right, then leave Device Manager open, keep MiFlash prepared, and hold the 3 buttons (power and vol + and -) until device manager refreshes, then attempt to flash
Click to expand...
Click to collapse
Perfect!
I had renamed the zip file update.zip and didn't realize there was a zip file in a zip file already called update.zip. Now I'm on B19!
Now I still can't seem to install the Qualcomm Drivers properly. When I go to enter DFL mode, it shows up as a Handset Diagnostic Device still. Won't show up as the qualcomm driver I installed.
download the lastest MiFlash pls
kaivorth said:
Perfect!
I had renamed the zip file update.zip and didn't realize there was a zip file in a zip file already called update.zip. Now I'm on B19!
Now I still can't seem to install the Qualcomm Drivers properly. When I go to enter DFL mode, it shows up as a Handset Diagnostic Device still. Won't show up as the qualcomm driver I installed.
Click to expand...
Click to collapse
You mean EDL? Right click on the ZTE diagnostic driver and click on Uninstall device, and tick Delete driver software
After that hold power and vol+ and - until the new device appears
---------- Post added at 07:07 PM ---------- Previous post was at 07:06 PM ----------
kurey said:
download the lastest MiFlash pls
Click to expand...
Click to collapse
that makes zero sense
My phone has no OS. Factory reset is unavailable to my knowledge (attempted volume up and power).
I can go into fastboot and TWRP, but I can't seem to install the stock OS nor Lineage OS. In fastbootmode, I see the following
Product name - AILSA_II
Variant - MTP eMMC
Bootloader version -
Baseband Version -
Serial Number 9e28c2da
Secure Boot - enabled
Device State - unlocked
Click to expand...
Click to collapse
I cannot use ADB commands. My phone isn't listed under ADB devices. EDL does not work. However in Fastboot mode, MiFlash recognizes a device 9e28c2da. Whenever I try to flash a full EDL however, miflash brings up errors saying it cannot find script and it cannot find file.
When attempting to install in TWRP, I get the respective errors "Invalid zip file format!" for "A2017U_B19-NOUGAT_FULL-EDL.zip" when I try to install the stock. When I try to install Lineage, I get "E3004L This package is for device: ailsa_ii,axon7; this device is ."
I am able to successful install A7LOSv1_UniversalBootStack.zip as well as the UniversalBootstack by DrakenFX. I then install OreoModem.zip after that, but the phone won't let me install any OS afterwards.
Am I trying to install the wrong arrangement of files? What can I do to get an OS back on my phone?
Firstly it sounds like the drivers need an update.
Try updating the USB drivers and try Zadig drivers as well.
Your PC/laptop should see your phone as ...
"Qualcomm HS-USB QDLoader 9008"
In the device manager on Windows. If you are using Miflash it should see it as Com 4 or similar.
Make sure you have the correct Edl package for your phone eg: A2017G, A2017U or A2017.
Extract the Edl package using WinZip or Winrar and take note of the folder name and location.
Boot your phone into Edl mode, via button, adb command or using the Edl tool by @djkuz
Open Miflash tap refresh, if it sees com4 or similar you are good to go.
Tap the browse button and pick the Edl package location on your PC/laptop and then tap flash.
The flash will take a few minutes and when done you will get a green flash success.
Unplug your phone and press and hold the power button till it boots.
Hope this helps
If you get stuck,
I have an Edl help page here >
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
There are many others on XDA too