Related
Hello!
As title says i bricked my Axon :crying:
I followed http://forum.xda-developers.com/showpost.php?p=68738854&postcount=100 (and the german one that linked to this one) but couldnt do the fastboot unlock.
So i couldnt finish this and my phone required a pin number to start android: bootet and started up but wanted a pin code to start/enter system.
Wasnt able to fix that with googling for answers so i went back to edl mode and rewrote my backup boot/recovery images with axon7backup.
Had no errors with that but it wont start now:
After the ZTE Logo the display goes black but it connects as "handset diagnostic interface (DFU) (ComX)" to my computer.
I fiddled around with driver installing etc and forced the HS-USB QDLoader 9008 on it but no luck, axon7backup/root can not connect.
When i did the actual flashing yesterday it never connected with the hold both vol-keys and connect usb way either, always had to reboot into edl via adb.
I cant boot anything else (no twrp/recovery) it just goes to the diagnostic interface mode.
Thanks in advance
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Starvirus said:
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Click to expand...
Click to collapse
Thanks. I tried it but it wont go to FTM. Only goes to diagnostic com port.
It seems i cant even turn it off. The little red light on the front is on the whole time .
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
adb don't show your device?
Starvirus said:
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
Click to expand...
Click to collapse
Oh ok. I expected ftm to work from vol-down and power-button till restart.
@adb: sadly no connection possible since it goes straight to Comport Connection.
Edit:
Couldnt make that work. It was off and i connected the usb. So it showed me the loading battery picture where i cant do anything. held the vol-down the whole time. But as soon as it had some battery it went straight to comport-connection again
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
nsabir said:
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
Click to expand...
Click to collapse
Hi,
couldnt fix it myself so i had to send it in.
Unless some tool/rom was released in the last few months to fix it yourself i would guess your device is bricked.
Hi I have almost the same problem, I tried to unlock bootloader and now I don't have the recovery, I can boot and use my mobile but I can't restore it or update it because I don't have the recovery
I try whit axon7tool to restore the recovery but I got a error.
MaxRink said:
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
Click to expand...
Click to collapse
Hi, do you have any idea, if there will be such a flashtool to work with DFU mode? I'm thinking that there are a lot of guys have bricked their devices (including me).
((
First of all, i live in Bangladesh. I asked a relative of mine who lives in Sweden to buy me this phone. So, there is no way for me to send this phone back to ZTE.
Now let me explain how i got into this huge mess. I installed twrp successfully using this post - https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
i only followed part A of this post. Then i needed to root. so i tried to flash supersu 2.79 first but failed. Then i tried to flash supersu 2.65 as someone commented that they failed with 2.79 but succeeded with 2.65. However, after flashing supersu 2.65 i soft bricked my phone. i could still access twrp 3.0.2. After a while, i downloaded b08 update.zip and tried to flash it through twrp but failed. then i saw this post - https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
and this post - https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And tried to update twrp to 3.03. which then hard bricked my phone. now i cannot access anything. when i try to start my phone it shows the zte logo for a second and the whole screen goes blank with the red led.
same thing happens with volume up+power and volume down+power. And there is no way to turn the phone off. So, i waited a whole day for the phone to empty it's battery and tried to boot to edl mode using volume up+down but Qualcomm HS-USB QDLoader does not appear. The only thing i can get to connecting to my computer is handset diagnostic interface.
Now only a brilliant dev can help me. So can someone PLEASE Help me.
Also i've found this post is very similar to my problem https://forum.xda-developers.com/axon-7/help/bricked-a2017g-b03-help-please-t3487635
Update: Fixed using this post >> https://forum.xda-developers.com/ax...ory-brick-repair-manual-t3585898#post71764940
& this >> http://4pda.ru/forum/index.php?showtopic=814221&st=0#entry60102671
Why can't you boot into EDL mode?
That's strange to me...
Did you try another computer to see if it pops up there?
Then try to reflash recovery if you can...
Abiram26 said:
Why can't you boot into EDL mode?
That's strange to me...
Did you try another computer to see if it pops up there?
Then try to reflash recovery if you can...
Click to expand...
Click to collapse
yes i have. but in the device manager, instead of Qualcomm HS-USB QDLoader, Handset Diagnostic Interface appears.
Furthermore, computers does not recognize any adb device when i connect my axon 7
what do i do???
Edit: when i uninstall Handset Diagnostic Interface from device manager and then connect my phone with both volume keys pressed, at first qusb_bulk appears but after automatic installation of hardware software it's Handset Diagnostic Interface all over again
Well I did some Google'ing for you and I guess the things in these threads might be your best bet:
http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://forum.xda-developers.com/showthread.php?t=2163493 )
http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
However all these methods are not tested with the Axon 7 and seem pretty risky to me...
If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.
I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.
I don't think I can really help you here, sorry :s
PS: If you are going to try these risky methods; don't blame me if it goes wrong...
EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)
Perhaps they can give you the right tools to unbrick your Axon7
Abiram26 said:
Well I did some Google'ing for you and I guess the things in these threads might be your best bet:
http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://forum.xda-developers.com/showthread.php?t=2163493 )
http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
However all these methods are not tested with the Axon 7 and seem pretty risky to me...
If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.
I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.
I don't think I can really help you here, sorry :s
PS: If you are going to try these risky methods; don't blame me if it goes wrong...
EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)
Perhaps they can give you the right tools to unbrick your Axon7
Click to expand...
Click to collapse
:crying::crying::crying::crying:
if only i could boot into edl mode
I don't think your phone is in such a dire condition. I was contacted by @raystef66 only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.
If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?
Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?
Send me a PM with your Hangouts, let's see if I can help.
Controllerboy said:
I don't think your phone is in such a dire condition. I was contacted by @raystef66 only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.
If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?
Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?
Click to expand...
Click to collapse
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do??
Edit: after seeing this post - https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???
Please Help
nsabir said:
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do??
Edit: after seeing this post - https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???
Please Help
Click to expand...
Click to collapse
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Oki said:
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Click to expand...
Click to collapse
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??
Oki said:
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Click to expand...
Click to collapse
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??
nsabir said:
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??
Click to expand...
Click to collapse
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.
What can you do?
1. read the whole thread, not just the opening post. As advised.
2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.
3. Unlock your A2017G phone.
4. enjoy flashing and reflashing all the multiple roms, patches, etc.
Oki said:
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.
What can you do?
1. read the whole thread, not just the opening post. As advised.
2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.
3. Unlock your A2017G phone.
4. enjoy flashing and reflashing all the multiple roms, patches, etc.
Click to expand...
Click to collapse
Sir, i don't u understand my problem properly. Let me give u a thorough description.
When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.
When i press volume up+power same thing happens.
When i press volume down+power same thing.
And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.
Then if i press volume up+down at the same time and insert usb red led turn on.
And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"
But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.
If i use Zadig to install winusb driver then the yellow sign disappears.
U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.
I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.
2017 DFU mode investigation
Bricked A2017G
These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.
That's why i'm asking the help of experts. Please help me.
I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.
I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only old ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.
And there are different guides for different models.
This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.
And sorry for my english, i tried my best.
nsabir said:
Sir, i don't u understand my problem properly. Let me give u a thorough description.
When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.
When i press volume up+power same thing happens.
When i press volume down+power same thing.
And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.
Then if i press volume up+down at the same time and insert usb red led turn on.
And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"
But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.
If i use Zadig to install winusb driver then the yellow sign disappears.
U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.
I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.
2017 DFU mode investigation
Bricked A2017G
These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.
That's why i'm asking the help of experts. Please help me.
I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.
I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.
And there are different guides for different models.
This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.
And sorry for my english, i tried my best.
Click to expand...
Click to collapse
Can you boot into the bootloader by pressing the button combination?
Oki said:
Can you boot into the bootloader by pressing the button combination?
Click to expand...
Click to collapse
No i cannot. Everything seems to be pointing back to DFU mode.
I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G
nsabir said:
No i cannot. Everything seems to be pointing back to DFU mode.
I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G
Click to expand...
Click to collapse
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:
http://www.myzte.cn/forum-1037-1.html
and the tutorials:
http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243
Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help
PS: RMA chinese http://rma.zte.com.cn/
Altomugriento said:
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:
http://www.myzte.cn/forum-1037-1.html
and the tutorials:
http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243
Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help
PS: RMA chinese http://rma.zte.com.cn/
Click to expand...
Click to collapse
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
nsabir said:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
Click to expand...
Click to collapse
Do you find something useful? I think I find someone in that forum, exactly in your position, all the answers pointing to RMA for the fix, sorry, maybe later can take another look and search for a solution.
Enviado desde mi ZTE A2017U mediante Tapatalk
nsabir said:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3551590
Enviado desde mi ZTE A2017U mediante Tapatalk
Altomugriento said:
https://forum.xda-developers.com/showthread.php?t=3551590
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
Thank you for the link. But i tried this miflash tools weeks ago.
Here is the full guide in my opinion for the mi flash tool.
http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Unfortunately, the A2017G does not have 9008 port. It has ZTE's own Handset Diagnostic Interface (DFU) (ComX) for which i need the latest version of ZTE firmware flasher. At the moment only ZTE have this. So, my bricked phone is a lost cause.
I think I fucced up pretty badly this time...
I was on LOS, wanted to get back to stock, for some reason wiped and rebooted...
Infamous DFU mode. I can't get to FTM (tried power + vol down and it only turns on, scrolls a little and turns off), and I wasn't able to use axon7tool using zadig. No recovery at all, no fastboot, nothing...
I've installed QDLoader 9008 drivers and MiFlash actually recognizes the... thing. Can anyone tell me if this is worth trying/what I have to do? Thanks
P.S I have no way of returning it to ZTE
Edit: The miflash thing didn't work as expected, can't find programmer file
Look like you kill yourseft this time.
You have to enter EDL with any cost, or at less FTM - let batttery drain up and try again.
Otherwise, people say somethings about a DIY EDL cable, but I not really sure
tamahouse02 said:
Look like you kill yourseft this time.
You have to enter EDL with any cost, or at less FTM - let batttery drain up and try again.
Otherwise, people say somethings about a DIY EDL cable, but I not really sure
Click to expand...
Click to collapse
I've found this QPST thing from Qualcomm, also heard that the only thing missing is the programmer which is not released. It detects my device, reports it is a Sahara Memory Dump, and that's pretty much that. I hope that people is actually looking into this
Also I noticd that in the first seconds when it is seemingly installing, it says it is a Sahara Download. Does that help?
I also wanted to know, is there a main thread for this sort of thing? I've seen @tenfar 's thread but there is nothing to do on A2017G's
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
I know you're already active in this thread, but I don't know if you understand it in depth. You must open your device to enter into edl mode. In edl you can flash twrp and are back in business. So your only way to enter edl is to open your brick as described.
Thank you, however i wanna be extra cautious here. When I have to connect the test point to ground, do I connect it with the SIM slot? What is valid as ground?
If MiFlash recognizes it you should be able to flash a stock Rom. The I have the A2017U so I could be wrong
supergear said:
If MiFlash recognizes it you should be able to flash a stock Rom. The I have the A2017U so I could be wrong
Click to expand...
Click to collapse
It's all done, thank you though. I disassembled the whole thing and did the short to ground thing, and after literally 30 tries it flashed the damn thing
Hi, and please tell me there's something that can be done to help. I have the AT&T V35 and was really happy to see the bootloader was unlockable, so I went ahead and downloaded QFIL and thought I was following the step by step directions for putting it into the correct download mode. There were no issues at all, but I did have a few more things open on my laptop that were partially covering the directions that could have led to my problem. There was a part of the directions where there are 6 or so partitions that needed to be backed up and substituted, I only saw 2. That's when I thought I was finished and proceeded to reboot the phone, having only 2 of the partitions saved and that caused me issues because now I can plug the phone into any USB port and the computer doesn't even recognize anything there. Also the top left corner just says "..ANY BUTTON TO REBOOT PHONE".
I think if I could get it into download mode or something I could at least reflash the .kdz file and replace the damaged firmware with good firmware, but I got to get the drivers to recognize the phone even being plugged into the USB port first. It seems like I'm going to have to repair it with Octoplus at this point, but maybe someone here has a better option, as I do not have the Octoplus or any other JTAG equipment to use. Any thoughts?
This has been answered by several people, if you can search the forum. In the original root thread, OP cmrntnnr (original post) and vlad48 (post #11) talks about it. I also provided some information regarding this in post #74. If you get stuck post in the thread instead of private message so others can see it. Make sure you thank the contributors. Here is the thread link:
https://forum.xda-developers.com/lg...loader-unlock-root-instruction-t4052145/page8
Edit: Also, you shouldn't need Octoplus or JTAG since the engineering bootloader is out and QFil can be used to fix almost any state the phone is in. Just follow instructions to get in QFil mode (may take several tries because it is tricky, hard key combination), flash the files for abl_a and laf partitions, you can use the ones i provided. Just remember once bootloader and laf partitions are restored, even if phone can't finish booting, you can still put it into download mode by holding the vol+ button while plugging in the USB cable.
ELutts said:
Hi, and please tell me there's something that can be done to help. I have the AT&T V35 and was really happy to see the bootloader was unlockable, so I went ahead and downloaded QFIL and thought I was following the step by step directions for putting it into the correct download mode. There were no issues at all, but I did have a few more things open on my laptop that were partially covering the directions that could have led to my problem. There was a part of the directions where there are 6 or so partitions that needed to be backed up and substituted, I only saw 2. That's when I thought I was finished and proceeded to reboot the phone, having only 2 of the partitions saved and that caused me issues because now I can plug the phone into any USB port and the computer doesn't even recognize anything there. Also the top left corner just says "..ANY BUTTON TO REBOOT PHONE".
I think if I could get it into download mode or something I could at least reflash the .kdz file and replace the damaged firmware with good firmware, but I got to get the drivers to recognize the phone even being plugged into the USB port first. It seems like I'm going to have to repair it with Octoplus at this point, but maybe someone here has a better option, as I do not have the Octoplus or any other JTAG equipment to use. Any thoughts?
Click to expand...
Click to collapse
The official way to unlock the bootloader has been unavailable for just over a year, since LG ended their developer program as of 01/01/2022 and you now can't apply for an unlock file anymore.
Searching for a work-around I found this: https://drfone.wondershare.com/unlock/lg-bootloader-unlock-how-to.html
I have tried as best I can to follow these instructions and fail because I can't get my device to enter Qualcomm EDL 9008 mode by any keypress combination, or ADB or fastboot command from OS (Windows and Linux tested). I suspect my edition of the phone doesn't have EDL, or the method of accessing it is not correct in all instructions I've seen. I can get in to fastboot, and LG download mode (which shows in device manager as LGE AndroidNet USB Serial Port), but not Qualcomm ADL 9008 mode which should show in device manager as Qualcomm HS-USB QDLoader 9008.
I'd rather not brick my device, but it is a spare, and I thought I'd try and soup it up with a newer AOSP-Extended before maybe gifting to my partner.
AND!! I'm suspicious of the instructions in the first place! At the bottom, it advertises a piece of software to something related. As a Windows technician in my day job, I see this too often, can't solve bluescreen error 0x123abc45 just download this trialware to fix your PC!!
Try "adb reboot edl" from adb, anyway yes that site is not good
Hey, thanks for coming back to me.
I have tried that, but have just repeated right now to remind myself the outcome, which is, phone reboots as normal. Does not enter EDL mode. Windows and Linux.
Cheers
Anne-d'Royd said:
I suspect my edition of the phone doesn't have EDL, or the method of accessing it is not correct in all instructions I've seen
Click to expand...
Click to collapse
Isn't the method to access EDL on the G6 through shorting two pins on the mobo?
LG G6 TestPoints for EDL Mode (9008)
Simple af. Just short them. For incase that doesn't work;
forum.xda-developers.com
Also, that guide is just a re-worded one for the LG G7 One, not the G6, which use different processors. An engineering bootloader for the LG G6 has not leaked yet, and likely will not leak since it's been 6 years.
LG G7 One Bootloader Unlock [How-to]
Disclaimer: Do this at your own risk, blah blah blah. Brick your phone its on you.. Just a quick tutorial on bootloader unlocking the G7 One. Lots of the info in here can be found in other areas of XDA. *****Read full post before...
forum.xda-developers.com
Hey thanks for the input!
I'm reluctant to go in since the glass is splintered on the back of the unit, that's the main reason I changed my phone nearly 2 years ago.
There are enough varying instructions of there to suggest that EDL on that phone can be accessed by I think five methods.Two methods involve commands from PC, one method is button press combinations whilst connected to PC, another is a special EDL cable and then lastly, the test points.
The guides I've seen explaining the keypress routine says it works for a range of LG phones with qualcomm chips, including the G6 but I have they're wrong. Example:
Dont bother with dr phone. I previously used it to backup my phone. It wanted me to pay to restore but all it did was create a zip of my internal storage.
I think it is highly unlikely that they have a secret way of unlocking one of the hardest to unlock bootloaders on a phone.