Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also
amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!
I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...
Related
So I've just received my axon 7 a2017g. It came with b06 installed. I'm trying to unlock boot loader without success. Can't get to edl mode. In cmd the device is unauthorized though I've enabled oem unlock and sub debugging. Installed the drivers from sub debugging. I have Windows 10 64 bit. I get to recovery with volume up plus power I select to reboot to bootloader with no success. It only restarts. Tried also with b10 and b08.
Any suggestions ?
ItsNewDroid said:
So I've just received my axon 7 a2017g. It came with b06 installed. I'm trying to unlock boot loader without success. Can't get to edl mode. In cmd the device is unauthorized though I've enabled oem unlock and sub debugging. Installed the drivers from sub debugging. I have Windows 10 64 bit. I get to recovery with volume up plus power I select to reboot to bootloader with no success. It only restarts. Tried also with b10 and b08.
Any suggestions ?
Click to expand...
Click to collapse
Why bootloader? Isn't there a way to do it via EDL (from system, do adb reboot edl)? On Controllerboy's guide maybe? Maybe you think that the device doesn't get to EDL because it seems like it's totally powered off. Just try again.
As of fastboot, it was removed on Nougat, not sure if they removed it before though
Choose an username... said:
Why bootloader? Isn't there a way to do it via EDL (from system, do adb reboot edl)? On Controllerboy's guide maybe? Maybe you think that the device doesn't get to EDL because it seems like it's totally powered off. Just try again.
As of fastboot, it was removed on Nougat, not sure if they removed it before though
Click to expand...
Click to collapse
Did not understand you. Where in system to do and reboot?
The phone is turned onand connected the the pc and I've enabled oem unlock and usb debugging.
The device won't boot to edl after I enter adb reboot edl. So I tried in recovery screen to get to the bootloader menu but pressing reboot loader it just restarts
ItsNewDroid said:
Did not understand you. Where in system to do and reboot?
The phone is turned onand connected the the pc and I've enabled oem unlock and usb debugging.
The device won't boot to edl after I enter adb reboot edl. So I tried in recovery screen to get to the bootloader menu but pressing reboot loader it just restarts
Click to expand...
Click to collapse
You have to have adb and fastboot installed. Run "adb reboot edl" from your computer while the phone is on, it should ask you if you want ADB to be allowed to do stuff, then poof. Go to the Device manager and check that there's a Qualcomm HS-USB QDLoader 9008 under Ports (COM&LPT)
Choose an username... said:
You have to have adb and fastboot installed. Run "adb reboot edl" from your computer while the phone is on, it should ask you if you want ADB to be allowed to do stuff, then poof. Go to the Device manager and check that there's a Qualcomm HS-USB QDLoader 9008 under Ports (COM&LPT)
Click to expand...
Click to collapse
Can you direct me where to get the adb and fastboot? I've rooted a lot of phones but this one seems unfriendly
ItsNewDroid said:
Can you direct me where to get the adb and fastboot? I've rooted a lot of phones but this one seems unfriendly
Click to expand...
Click to collapse
You rooted a lot of phones and don't have ADB lol
Search for 15 seconds adb installer
I already have it installed. It says unauthorized when I run adb devices
ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Unplug the phone, turn it off. Hold only the 2 volume buttons (DON'T TOUCH POWER) and insert the USB-C (plugged to the PC in the other end ofc) while holding the two volume buttons. then check device manager
This should get you to EDL
---------- Post added at 12:44 AM ---------- Previous post was at 12:40 AM ----------
ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Okay after you do that last thing you should get to EDL. Download Zadig, uninstall the Qualcomm QDLoader drivers and tick Delete driver software too. Then go to Zadig and install the driver. After that hold the 3 buttons (pwr, vol) until the led flashes or your PC makes a sound, wait 5 seconds, and you'll be able to run axon7tool.exe -r gpt boot recovery
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
ItsNewDroid said:
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
Click to expand...
Click to collapse
That's extremely weird...
Well I guess there's no harm trying to downgrade to marshmallow B03. Download that ancient ROM from raysteff's download center. I did the whole process there. Maybe you'll get fastboot too
---------- Post added at 01:13 AM ---------- Previous post was at 01:10 AM ----------
ItsNewDroid said:
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
Click to expand...
Click to collapse
Thinking about it it's not that weird, I think you're not getting the Zadig part. Did you install the driver through Zadig? How's the device reported aa when on EDL? If you installed the driver properly it should be listed as QUSB_BULK under USB something
Sure I'm not doing something right.
First I did not have Qualcomm drivers installed
I'm in edl with volume buttons and sub. open zadig and install wcid.
From here I did not get it. Hold all buttons vol÷power?
ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Like this ?
"adb devices" command:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx unauthorized
When enabling USB debugging then with USB cable connected, there is a popup in your phone, asking to authorize
your phone (with digital signature etc..). You need then to authorize it. Afterwards, your phone will be recognized
with 'adb devices" output as :
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx device
xxxxx is your device id. You must have status "device" and not "unauthorized"
dnlilas said:
Like this ?
"adb devices" command:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx unauthorized
When enabling USB debugging then with USB cable connected, there is a popup in your phone, asking to authorize
your phone (with digital signature etc..). You need then to authorize it. Afterwards, your phone will be recognized
with 'adb devices" output as :
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx device
xxxxx is your device id. You must have status "device" and not "unauthorized"
Click to expand...
Click to collapse
Yes I know that a message should popup but it doesn't. What can I do?
I have oconnection options like charging, mpt etc.
Should I choose something perticular?
And why it doesn't reboot to bootloader from recovery menu?
I really think something is wrong with the device.
Where can I find a2017g b03? In every post the link to zte's website that only have b11 and nougat.
Sorry for all the questions as I said this device gives me a hard time.
I've had opo op3 lg g5 le max 2. Non of theme gave me hard time like this one
ItsNewDroid said:
Yes I know that a message should popup but it doesn't. What can I do?
I have oconnection options like charging, mpt etc.
Should I choose something perticular?
And why it doesn't reboot to bootloader from recovery menu?
I really think something is wrong with the device.
Where can I find a2017g b03? In every post the link to zte's website that only have b11 and nougat.
Sorry for all the questions as I said this device gives me a hard time.
I've had opo op3 lg g5 le max 2. Non of theme gave me hard time like this one
Click to expand...
Click to collapse
Please check periodically USB debugging option. I encountered similar problem as your, and before the popup that confirms USB debugging
for the phone, the option is set back to disabled. So maybe you have to check again this option, unplug and replug the phone, choose option MTP,
this should help to have the confirmation popup. Anyhow you must have to reach status "device" which means your phone is able to connect using ADB.
For A2017G B03, it is not necessary, B11 is OK for unlock, TWRP or root using the current guide.
However if you really need it (A2017G B03, B06, B09):
https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
I suspect that my laptop is causing me trouble as also my g5 will not prompt me with authorization.
I'm gonna use a different laptop without any drivers installed. Can someone tell me all the drivers needed for the a2017g in chronological order so there won't be any conflicts?
In other tutorials they don't mention Qualcomm's driver but in othrrs they are needed.
This phone makes me so frustrated.
So please a step by step from new how to connect to adb on a total new pc. From there I hope I'll manage.
Thanks to all who replied. It's much appreciated.
Here the same problem with an A2017G model. Phone worked with the latest LineageOS, was rooted and got an unlocked bootloader, and with flashing to the the new B04 update phones ends up in a loop.
I can get into the stock recovery and when i choose "reboot system now" i get a screen wich tells you to lock your bootloader.
In recovery a can also choose "apply update from adb" or "apply update from sd card". With the first option i can flash a rom but at 25-30% adb ends up with an error.
With the second option i get a message "Sorry, can`t sdcard upgrade", and tryed several sd cards.
Phone will NOT boot into Android so i can`t change USB debgugging or something.
I can get in EDL mode and after "axon7tool -r gpt boot recovery" in adb the phone reboots with no errors and gets in a loop again. Grrrrr..... Very frustrating with a non working phone!
the_cyberspace said:
Here the same problem with an A2017G model. Phone worked with the latest LineageOS, was rooted and got an unlocked bootloader, and with flashing to the the new B04 update phones ends up in a loop.
I can get into the stock recovery and when i choose "reboot system now" i get a screen wich tells you to lock your bootloader.
In recovery a can also choose "apply update from adb" or "apply update from sd card". With the first option i can flash a rom but at 25-30% adb ends up with an error.
With the second option i get a message "Sorry, can`t sdcard upgrade", and tryed several sd cards.
Phone will NOT boot into Android so i can`t change USB debgugging or something.
I can get in EDL mode and after "axon7tool -r gpt boot recovery" in adb the phone reboots with no errors and gets in a loop again. Grrrrr..... Very frustrating with a non working phone!
Click to expand...
Click to collapse
The command "axon7tool -r gpt boot recovery" only backups your boot and recovery (-r = read, so of course only files *-backup.bin are created inside your PC directory, no change to the phone).
Since you have stock recovery, did you apply the full ROM A2017G-N-B04 (australian) from here:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 ?
dnlilas said:
Since you have stock recovery, did you apply the full ROM A2017G-N-B04 (australian) from here:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 ?
Click to expand...
Click to collapse
Yes but get an error in adb: cannot read 'rom.zip'
the_cyberspace said:
Yes but get an error in adb: cannot read 'rom.zip'
Click to expand...
Click to collapse
Did you try installing the ROM zip from inside the stock recovery?
dnlilas said:
Did you try installing the ROM zip from inside the stock recovery?
Click to expand...
Click to collapse
I can choose "apply update from ADB" and "apply update from SD card". When i choose the option from SD card i get a error: "sorry, can`t sdcard upgrade" and when i`m flash the rom in adb: "cannot read 'rom.zip' ".
Hello everyone,
So I've read that I can re-lock the bootloadder and tried to do it.
First I have flashed b10 and flashed the su so I wont loose TWRP. I entered fastboot with adb and then I typed fasstboot oem lock, I got a message on the pc with ok.
Since then I cannot boot to the phone.
The phone shows the zte logo for 0.5 seconds but not booting and with constant red led.
Tried power + vol up, power + vol down, all three buttons, vol up + vol down and then connect to pc - nothing at all. The phone wont get past this 0.5 second zte logo.
In all connections I have listed above the phone shows in device manager as QUSB_BULK. At first it was with yellow acclamation mark and then I installed the zadig driver. Now it is connected "normally".
What can I do?
Please refer me to the right tutorial or guide me.
Thanks
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)
dnlilas said:
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)
Click to expand...
Click to collapse
I'll try to do it but yesterday tried to go to edl or recovery in cmd no device found. Tried to flash recovery but it hangs on "waiting for device" so I don't thing I can get to these edl, recovery, fastboot status.
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
I'll try all these guides and update with results
dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
So for sure I'm doing something wrong. Can you please guide me with this tool?
Ironically you helped me unlock the bootloader and I need your assistance relocking it.
Edit: I have the 3 files backed up from the unlocking procedure they should help no?
The phone is not recognized in any adb status edl or fastboot
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
QuantumFluxx said:
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
Click to expand...
Click to collapse
I don't want to keep twrp or anything. I want to sell the phone so all I want.t is to go back to locked stock phone.
I cannot boot to recovery or fastboot or edl. If I could I would use miflash and flash b10 and be done with it
I think that the initial problem arose when you flashed SU and tried to relock the bootloader with TWRP installed
What does Windows Device Manager show when you connect the phone to your PC?
Update: sorry bud. I totally missed that bit in your OP. DOH! Will update.
Update:
Have you seen this?
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
https://forum.xda-developers.com/showpost.php?p=70948893&postcount=28
Sorry that I can't be of more help...
I think what went wrong with my device is that after flashing stock b10 I flashed su so I won't lose twrp. Now when I tried to lock the boot loader made a conflict as I could not have locked bootloader and this version of twrp (for unlocked device). Now I just need to find a way to flash stock recovery (I have a backup from the unlocking procedure) without edl or fastboot as I cannot seem to find a way to enter these states (cause I have no recovery) I'm hoping it makes sense (pretty early in the morning)
So no one can help?
I can't believe the phone is beyond repair
@ItsNewDroid
Sorry I do not have solution, just some idea.
It "seems" that you cannot boot to either system, recovery, bootloader, EDL! adb/fastboot commands are not recognized.
There is still hope since your phone is still recognized somehow as QUSB_BULK (not unknown device) with Zadig driver under USB device.
So you can try to uninstall Zadig WinUSB driver and use Qualcomm bulk drivers so that the phone appears under COM port as Qualcomm HS-USB QDLoader 9008.
If you get 9008 then you are in EDL mode, and MiFlash could be used to flash.
Qualcomm bulk drivers, MiFlash... are available from Download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
The problem is to find available "EDL packages" recognized by MiFlash to flash.
These packages could be stock recovery, signed TWRP, or full ROM (any version, MM, or Nougat).
This would allow booting to either recovery or system.
The problem is that I did not see many such packages for A2017G, but only for A2017U.
You may have to ask other members how to build such "EDL packages" (for ROM, sometimes it is called "fastboot ROM").
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Edit 2: So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?
ItsNewDroid said:
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Click to expand...
Click to collapse
Oh no, you unfortunately got the dreaded DFU (device firmware mode).
Looks like it a serious brick. Some topics and articles:
https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
https://community.zteusa.com/thread/14699
https://www.reddit.com/r/Axon7/comments/5oqgfj/a2017g_bricked_cannot_get_past_dfu_mode/
https://www.youtube.com/watch?v=nqF3nr3y-Eg
@dnlilas
Man there are changes!
So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?
Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Edit: the screen capture you took is the bootloader menu (equivalent to come into with "adb reboot bootloader").
When in bootloader, I believe you can use Volume-Up and Volume-Down to navigate (to go to recovery, system, bootloader or other mode). Validate with Power button. It is important to remember how to get to this bootloader menu.
dnlilas said:
Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Click to expand...
Click to collapse
I held the 3 buttons not connected to power or pc. As soon as I felt the vibration before zte logo I let go of the vol up button and it booted to fastboot.
I dont want to unlock the bootloader I want to sell the phone ( this is the reason I came to this situation) I tried to boot to recovery from this menu but it could not.
My guess is that I have twrp recovery and as the bootloader is locked it can not boot.
I need either a twrp for LOCKED bootloader or a stock recovery.
I'm searching the forum but could not find.
You are a wizard! Every time you reply I have good news :good::laugh:
@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!
dnlilas said:
@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!
Click to expand...
Click to collapse
So this is the new situation: adb devices phone is not recognized. Fastboot devices device IS recognized. Issuing axon7tool - w recovery I get device not connected failed to connect. Any idea?
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
inwarse said:
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
Click to expand...
Click to collapse
You downloaded the KENZO (this is not oneplus2! ) TWRP and flashed it on another phone (oneplus2), just normal that it doesn't work and your phone is messed up.
If you can enter fastboot (vol up and power button to boot) you can rescue your phone:
-enter fastboot (vol up + power, while phone is completely off, u can also hold it until you can see "fastboot" written on the screen)
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
If something is not clear, use google, because this is most likely basic stuff you have to know when flashing your phone
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
inwarse said:
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
Click to expand...
Click to collapse
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
wertus33333 said:
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
Click to expand...
Click to collapse
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Oh, the link is dead, sry for that. try this one (GDrive links are up and working).
inwarse said:
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Click to expand...
Click to collapse
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Do you still have TWRP? If yes go to TWRP and shut down the phone there, afterwards you should be able to enter qualcomm mode again.
otherwise you have to try (i think 10s power button will shut the device completely down). You should be able to enter qualcomm mode if the device is fully shut off (your scenario sounds as if the device is not fully shut off when u connect it to the pc).
Just to go sure: You are absolutely sure to have a oneplus2, are you?
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Could you resolve the issue?
wertus33333 said:
Could you resolve the issue?
Click to expand...
Click to collapse
nope. kept running into issue after issue, so got dejected and gave up.
I have an A2017U, Android 7.1.1, build B35, on MiFavor 4.2 and was looking to upgrade to 5.2/Oreo. I get stuck because I can't boot into EDL mode. I have not unlocked the phone but do have developer options & USB debugging enabled. If I boot with vol up + vol down + power, nothing happens even if I wait 120 seconds. I get a slowly flashing red dot. ADB works fine -- my device is recognized -- and "adb reboot EDL" reboots the phone, but not into EDL mode, just into standard mode. MiFlash doesn't see the phone.
I'm clearly doing something wrong but I'm at a loss what, given how simple the instructions are.
prestonmcafee said:
I have an A2017U, Android 7.1.1, build B35, on MiFavor 4.2 and was looking to upgrade to 5.2/Oreo. I get stuck because I can't boot into EDL mode. I have not unlocked the phone but do have developer options & USB debugging enabled. If I boot with vol up + vol down + power, nothing happens even if I wait 120 seconds. I get a slowly flashing red dot. ADB works fine -- my device is recognized -- and "adb reboot EDL" reboots the phone, but not into EDL mode, just into standard mode. MiFlash doesn't see the phone.
I'm clearly doing something wrong but I'm at a loss what, given how simple the instructions are.
Click to expand...
Click to collapse
Try "adb reboot edl" from a booted phone.
EDL actually IS a black screen, usually without an LED though it might be red. Open Device manager and check under "unrecognized devices", or under "Ports (COM & LPT)". Should be there. If it is under Ports and it is callee Qualcomm HS-USB QDLoader 9008 then MiFlash should work
What are you planning to do? EDL back to B19 then unlock? Just curious
Choose an username... said:
Try "adb reboot edl" from a booted phone.
EDL actually IS a black screen, usually without an LED though it might be red. Open Device manager and check under "unrecognized devices", or under "Ports (COM & LPT)". Should be there. If it is under Ports and it is callee Qualcomm HS-USB QDLoader 9008 then MiFlash should work
What are you planning to do? EDL back to B19 then unlock? Just curious
Click to expand...
Click to collapse
I plan to update to Oreo/MiFavor 5.2.
How do I issue the command from a phone? I know how to use ADB from a PC but not from a phone. That is what I have done -- enable developer options, connect the phone, verify that it is connected (adb devices) and then issue the command (adb reboot EDL).
Use the Edl tool by Djkuz
Install it to PC or laptop with all updated drivers
Open edl tool with run as admin
Boot your phone into ftm
Turn your phone off
Press and hold vol dn + power till you see ftm screen
Plug in your phone
Follow the on screen till it detects your phone
Select unlock then edl fix
Edl tool is here
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
prestonmcafee said:
I plan to update to Oreo/MiFavor 5.2.
How do I issue the command from a phone? I know how to use ADB from a PC but not from a phone. That is what I have done -- enable developer options, connect the phone, verify that it is connected (adb devices) and then issue the command (adb reboot EDL).
Click to expand...
Click to collapse
Yes, but what are you going to do BEFORE updating to MF5.2?
you can't edl mifavor 5.2 because you will break stuff, besides you need an unlocked bootloader or you'll DFU brick your phone and you'll have to throw it in the trash.
I meant to issue adb reboot edl from your pc but with your phone on
On a side note, I recommend not using EDL Tool or axon7toolkit to unlock your phone. EDL Tool has a much better track record than other apps but it still has margin for error. The best way to unlock an A2017U is get a B19 EDL package and install it with MiFlash, then enter Fastboot and do "fastboot oem unlock".
Worked!
Syberclone said:
Use the Edl tool by Djkuz
Install it to PC or laptop with all updated drivers
Open edl tool with run as admin
Boot your phone into ftm
Turn your phone off
Press and hold vol dn + power till you see ftm screen
Plug in your phone
Follow the on screen till it detects your phone
Select unlock then edl fix
Edl tool is here
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
That worked, thanks!
Ive used all of the Axon 7 tools as well as adb commands and all work well in there own ways.
Script errors or command errors can be an issue as well as some software (ROMs, recovery and boot imgs) a few times I've had to edit a zip or img to make it work.
After a few boot loops on my HTC.
Is there an official MiFavor Update on 5.2?
My phone is still on 4.2 and can't find any updates.
SebaSnow said:
Is there an official MiFavor Update on 5.2?
My phone is still on 4.2 and can't find any updates.
Click to expand...
Click to collapse
only for Chinese (A2017) phones. It's 8.0 mifavor with the new mf5.0 interface (way more Chinese-looking). If you want to install it on a G or U you'll have to use one of the packages made for them (Usually for an update from other model to work you need to change its modem file to the one that your model uses, i.e. swap the chinese modem with the G's).
Hi guys,
I am having an issue with my OnePlus 8 Pro and I hope you can help me. I am open to all suggestions.
My phone bricked after trying to flash a custom rom. I have access to fastboot mode and TWRP. I am operating a linux machine and have windows10 running in virtualbox. I don't know if this is the reason but when I am trying to boot in to EDL mode (ony possibility is via TWRP) my device does not pop up in devicemanager. I followed all the steps in the thread about the MSM tool. When I try to get in to EDL mode with the hardware butons and the original cable from OnePlus I can not get in to EDL mode at all. Tried different cables and different USB ports on my computer but with no success. The correct qualcomm drivers are installed in windows so in theory it should work. Because of this I can not use the MSM tool to get my phone up and running. It simply does not pop up as a qualcomm device in devicemanager when I reboot in EDL mode.
I tried to flash the fastbootrom for my oneplus8 pro but after the last command it restarts and gets into stock recovery. In the command window it says 'waiting for any device' and nothing happens (I waited for about 20 minutes). In the post is mentioned: If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end. Because nothing seems to happen I saw further in the post If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.There is no option available to wipe data and cache/ erase everything in the recovery menu. When I choose to reboot to recovery in the recovery menu my phone powers off. The other option is to reboot into fastbootmode. When I do that there is an error in the command window FAILED Flashing is not allowed for Critical Partitions. I don't know how to fix this. I tried both Linux to flash the fastboot rom manually and in windows also and with the flash-all.bat file. Everytime I end up in fastboot mode when I boot up my phone.
Instead of trying to flash the original OS with the fastbootrom I tried to flash different custom ROMS but somehow it will not install any ROM at all...the device reboots everytime to fastboot mode. Last option I tried is a different recovery. I flashed lineage recovery and tried to flash Lineage OS and AICP and this resulted also in only able to boot into fastboot mode.
I spend a lot of time on the web trying to figure out what is wrong and how to fix it but I have not found a solution yet.
Is there a solution available to get my phone up and running?
SakasakaHeyhey said:
Hi guys,
I am having an issue with my OnePlus 8 Pro and I hope you can help me. I am open to all suggestions.
My phone bricked after trying to flash a custom rom. I have access to fastboot mode and TWRP. I am operating a linux machine and have windows10 running in virtualbox. I don't know if this is the reason but when I am trying to boot in to EDL mode (ony possibility is via TWRP) my device does not pop up in devicemanager. I followed all the steps in the thread about the MSM tool. When I try to get in to EDL mode with the hardware butons and the original cable from OnePlus I can not get in to EDL mode at all. Tried different cables and different USB ports on my computer but with no success. The correct qualcomm drivers are installed in windows so in theory it should work. Because of this I can not use the MSM tool to get my phone up and running. It simply does not pop up as a qualcomm device in devicemanager when I reboot in EDL mode.
I tried to flash the fastbootrom for my oneplus8 pro but after the last command it restarts and gets into stock recovery. In the command window it says 'waiting for any device' and nothing happens (I waited for about 20 minutes). In the post is mentioned: If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end. Because nothing seems to happen I saw further in the post If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.There is no option available to wipe data and cache/ erase everything in the recovery menu. When I choose to reboot to recovery in the recovery menu my phone powers off. The other option is to reboot into fastbootmode. When I do that there is an error in the command window FAILED Flashing is not allowed for Critical Partitions. I don't know how to fix this. I tried both Linux to flash the fastboot rom manually and in windows also and with the flash-all.bat file. Everytime I end up in fastboot mode when I boot up my phone.
Instead of trying to flash the original OS with the fastbootrom I tried to flash different custom ROMS but somehow it will not install any ROM at all...the device reboots everytime to fastboot mode. Last option I tried is a different recovery. I flashed lineage recovery and tried to flash Lineage OS and AICP and this resulted also in only able to boot into fastboot mode.
I spend a lot of time on the web trying to figure out what is wrong and how to fix it but I have not found a solution yet.
Is there a solution available to get my phone up and running?
Click to expand...
Click to collapse
Sounds like a Qualcomm driver issue. You need that for msm
jamescable said:
Sounds like a Qualcomm driver issue. You need that for msm
Click to expand...
Click to collapse
I am affraid so jamescable. I was hoping for a fix via fastboot mode...
What is strange is that flashing another recovery via fastboot is no probleem but a Rom is... don't know why my device is doing this.
SakasakaHeyhey said:
I am affraid so jamescable. I was hoping for a fix via fastboot mode...
What is strange is that flashing another recovery via fastboot is no probleem but a Rom is... don't know why my device is doing this.
Click to expand...
Click to collapse
You can only install Qualcomm drivers in windows, not linux
jamescable said:
You can only install Qualcomm drivers in windows, not linux
Click to expand...
Click to collapse
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
Click to expand...
Click to collapse
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately
Click to expand...
Click to collapse
SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
Click to expand...
Click to collapse
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume up AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately
Thanx jamescable. I am going to do this as you described later this week and will post an update in this thread.
Have a nice day friend!
jamescable said:
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume up AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately
Click to expand...
Click to collapse
Hi jamescable,
Just done exactly as above...my devices boots into edl mode, but msm tool does nothing and in devicemanager my device does not pop up either. I do not hear a sound when I plug in the One+ cable...tried different usb ports on the computer also.
Do you have any ideas what I can do more?
SakasakaHeyhey said:
Hi jamescable,
Just done exactly as above...my devices boots into edl mode, but msm tool does nothing and in devicemanager my device does not pop up either. I do not hear a sound when I plug in the One+ cable...tried different usb ports on the computer also.
Do you have any ideas what I can do more?
Click to expand...
Click to collapse
It has to be a driver issue then. Windows in virtual machine obviously won't work for this
jamescable said:
It has to be a driver issue then. Windows in virtual machine obviously won't work for this
Click to expand...
Click to collapse
O no then I really have a problem....I only have linux as an operating system....I thought windows in a virtual machine running does the trick but I guess I am wrong.