hi, everyone , i m tring to revive my hard bricked oneplus 8 pro but without any luck i m getting "firehosecheckrsp failed errno 258" error , i tried every possible solution a did find (Drivers, Cable, USB 2 , other pc) , i m convinsed tha i shoud start search for a motherboard replacements (even that i coudnt find on the internet)
so please if anyone could help me (Phone stuck on EDL mode - recognised by pc but buttons combination doesn't work )
If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.
dladz said:
If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.
Click to expand...
Click to collapse
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error
ahmadOnePlus said:
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error
Click to expand...
Click to collapse
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed
jamescable said:
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed
Click to expand...
Click to collapse
+1 to this
You need these so the phone is detected correctly in windows. Here is a link.
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258
gcf81 said:
I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258
Click to expand...
Click to collapse
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)
Nick-Henkey said:
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)
Click to expand...
Click to collapse
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.
gcf81 said:
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.
Click to expand...
Click to collapse
Looking around, the North America version should be running international firmware (HD1905):
OnePlus 7T hardware variants
I was curious about the different hardware variants of the 7T and decided to ask support once EU launch went over and they kindly answered. HD1900: China HD1901: India HD1903: Europe HD1905: North America HD1907: T-Mobile USA
forum.xda-developers.com
I presume that you're using this MSM tool - https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/
Did you try all of the steps suggested by OP, yet?
Install drivers
Change to factory cable
Different USB port
Different Windows computer?
The only thread I could find where this problem was solved was on the OnePlus forum. The user completely removed and reinstalled the Qualcomm drivers (a different PC should handle that) - https://forums.oneplus.com/threads/solved-closed-trying-to-unbrick-op5t.956810/
Related
First of all, i have read some similar threads about this, and all advise diffrent solution besides the hardware mod, I have tried for 2 days all methods in Miui forums and none have worked for me except the hardware method.
My Device: Xiaomi Redmi Note 3 Pro / SD version.
State:
-would only show "Mi" logo when powered on.
-Would enter only Fastboot.
- No EDL mode
- No recovery
-bootloader locked
-In this state, you can't flash absolutely nothing with any software. (from fastboot).
Requirements:
- windows 7/ windows 10 x64 edition.
- ONLY LATEST version of miflash, from 2016 onward, so it has the required drivers and methods to work with the phone. (I have tried with older versions and it did not work, i thought there was no hope for my phone).
- one hard bricked Redmi Note 3 Pro
- any fersion of Stable FASTBOOT OFFICIAL rom. (.tgz extension) - I personally used kenzo_global_images_V7.2.3.0.LHOMIDA_20160129.0000.14_5.1_global_c85ba6c524.tgz
- medium disassembly skills,
- a lot of patience,
- minimum set of tools (one small cross screwdriver, 1-2 strong finger nails, good eyesight).
- one microusb cable
HOW TO:
1. uninstall all drivers and software related to the Xiaomi phone. (I ended up reinstalling windows 7 just to be sure all was gone - that is how desperate I became). To be sure this is done correctly, with the phone turned off, connect it to the computer.
Go into device manager, search in com ports, or wherever any drivers are installed for the phone, and uninstall all of them, ticking remove driver files also.
after doing this, hit refresh, and see if any drivers get installed again.
Repeat until there are no drivers installed, and the device will be without a driver.
2. Disconnect the phone and RESTART WINDOWS
3. Disable driver signature verification/enforcement:
a. in windows 7, this is easy: restart windows, hit f8 until a menu pops up where you can choose disable driver signature verification/enforcement.
b. in windows 10, it is a little bit longer, but: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ - Be careful, when choosing the option in the last menu, use F... keys, not number keys.
4. while in windows, in the bottom right corner, there should be a message saying "test mode"
5. install ONLY the LATEST VERSION of Miflash! you may get some messages about driver installation (2 times), allow installation!
6. RESTART WINDOWS
7. Prepare the phone!: I followed the video here, even I did not understand the language: http://choimobile.vn/threads/video-...o-snapdragon-650-fix-download-mode-edl.65098/
- First, I used my nail to open the phone up, just like in the video. It is great that the screen is not glued to the body, there are only some clips holding it in place!
- after opening the cover please be careful - there is a cable connecting the case to the mainboard - the fingerprint sensor.
- after this, unscrew the 7 or 8 screws as in the video.
- unlock the cables as in the video - please be sure not to disconnect all the cables.
- now, first get the antenna plastic cover outside of the way.
- after disconnecting the camera module, I would personally advise you to get the camera out of the way first, as there is a piece of foil glued between the mainboard and the underneath of the camera module (on the display)
- with great care, rise the Mainboard from the display.
- to have better access to the testpoint pins, I turned the Mainboard over the battery.
- now, connect the microusb cable to the phone.
8. connect the phone to the computer.
9. go into device manager and check if there are any devices installed, there should be under ports.... a device called Qualcomm HS-USB Diagnostics 900E.
10. Now comes the tricky part, switching the phone to EDL mode (emercency download)
look on the back of the motherboard of the phone to connect the 2 testpoint pins as in the video. You can use anything to do this. a metal wire, a small scissors, an untied paperclip... You will have to do this while device manager is opened, as you must check it when the driver changes to "qualcomm hs-usb qdloader 9008".
Please be careful when trying to connect the 2 pins not to touch any metal housing, ans this will restart the device each time.
Now, try and try and try until the driver changes to "qualcomm hs-usb qdloader 9008".
11. unzip the rom using 7 zip to a destination of your choosing. I advise as short destination as possible and no spaces used in the folder naming. I unpacked it in C:\rom\
12. Open Miflash
13. As per other many many instructions:
a. click browse - select the folder where you unpacked the rom (for me, c:\rom\)
b. click the arrow next to brows button and select advanced.
c. in the first field, navigate to the folder where the rom was unpacked and select flashall.bat
d. in the third field select prog_emmc_firehose_8976_ddr.mbn from the "images"folder in the folder whre he rom was extracted
e. field 7: rawprogram0.xml and field8: patch0.xml
f. Hit the Refresh button, the device should appear as a com port in the white field of Miflash.
g. just to be sure, tick also "flash all" in the bottom of miflash.
14. Hit the Flash button on Miflash and this should be the last step before powering up your revived Xiaomi Redmi Note 3.
This is what I learned in the past 2-3 days.
Different errors I got during the learning process and what i did to avoid them:
- different problems with drivers not installing correctly or showing different device names - just use the method i pointed out in the beginning to uninstall any driver previously installed on the computer, with the refresh in device manager and than uninstalling all.
- "end of package" error at second 2 while flashing in Miflash - you are using an older or an unsupported version of miflash, just use the latest one.
- not being able to flash anything while in fastboot - if you have a locked bootloader, on redmi note 3 snapdragon version, you simply won't be able to flash anything. end of story. this is the whole purpose of having a locked bootloader.
- trying to go into EDL mode using fastboot comand "fastboot oem eld" - this will not work for a really bricked device as was mine. the only solution is to go through the tespoint pin connection.
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Please move the thread into guides/tutorial section.
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
jujusito said:
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
Click to expand...
Click to collapse
please read through all the thread, don't just throw in a link. the method mentioned by you will not work on some bricked devices, including mine. this did not work for me, so I ended up disassembling the phone.
aabenroi said:
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Click to expand...
Click to collapse
I also applied for an unlock code, but this takes up to 15 days, and I have the phone for only 3 days . I could not wait for the code, I had to do something to revive it.
meangreenie said:
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Click to expand...
Click to collapse
I made a modified TWRP which will not cause hard bricks
Rajdip said:
I made a modified TWRP which will not cause hard bricks
Click to expand...
Click to collapse
great work! your modded twrp will no doubt save me when i forget i have to delete the emmc file in the future.
Dear, thank you for your contribution, this deserves to be a section more important, really saved my phone from the hard brick. Again very grateful
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
xdarkmario said:
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
Click to expand...
Click to collapse
maybe look for something like this?
http://choimobile.vn/Temp/Testpoint_Redmi_Note3_PRO_3.jpg
I doubt they will have much variance from xiaomi phone to phone to make it easy for factory / repair centers to fix many models... (I could be wrong though), other brands are probably different.
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
ilvmyname said:
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
Click to expand...
Click to collapse
links dead
Quick addition: if you're using Virtual Box, like me (on a mac), you need to enable USB 2.0 on the virtual machine. On Virtual Box, this means you have to add an extension pack. This might save you 48hrs, like it cost 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.
So, I side loaded build no. 13.8.26.76 to my phone, not knowing that it was meant only for the snapdragon 410 counterpart (mine is 615 one). It installed successfully until I rebooted and phone stayed dead. I think I hard bricked it
No logo, no charging, can't enter recovery or fastboot. No nothing... Connected device to PC, and windows doesn't recognize it.
Please help me....
sree27 said:
So, I side loaded build no. 13.8.26.76 to my phone, not knowing that it was meant only for the snapdragon 410 counterpart (mine is 615 one). It installed successfully until I rebooted and phone stayed dead. I think I hard bricked it
No logo, no charging, can't enter recovery or fastboot. No nothing... Connected device to PC, and windows doesn't recognize it.
Please help me....
Click to expand...
Click to collapse
Can you go to recovery mode ?? If yes please flash your device compatibility custom rom like RR rom ..if u cant go to even recovery mode..
RIP asus zenfone max Just Change your Motherboard of your phone
Thanks
Its dead u can recover i also had same issue ...mine works now ....email me [email protected]
Hello, I had a very little progress. I gave up about my asus zenfone max a year ago but glad that now looks like there's a hope in reviving my phone. I was able to download the right files to flash with QFIL. Most people here say that their PC detected QUALCOMM HS-USB QDLOADER 9008 but mine detect it as QUALCOMM HS-USB DIAGNOSTICS 9006. Due to excitement, I flashed it anyway and it created some memory partition on my hard drive whenever I plug the phone but QFIL gave me an error of :
** Download Fail: Switch To EDL Fail Failed to switch to Emergency Download Mode
I tried to google this error, some encountered it and was able to get a resolution by just removing the battery before plugging it in but our zenfone is with non removable battery. I have no luck yet. Anyone got suggestions ?
MJMarra34 said:
Hello, I had a very little progress. I gave up about my asus zenfone max a year ago but glad that now looks like there's a hope in reviving my phone. I was able to download the right files to flash with QFIL. Most people here say that their PC detected QUALCOMM HS-USB QDLOADER 9008 but mine detect it as QUALCOMM HS-USB DIAGNOSTICS 9006. Due to excitement, I flashed it anyway and it created some memory partition on my hard drive whenever I plug the phone but QFIL gave me an error of :
** Download Fail: Switch To EDL Fail Failed to switch to Emergency Download Mode
I tried to google this error, some encountered it and was able to get a resolution by just removing the battery before plugging it in but our zenfone is with non removable battery. I have no luck yet. Anyone got suggestions ?
Click to expand...
Click to collapse
Check my post for detailed instructions. And yes, I did face that issue and fixed it by reinserting the battery. It's a bit risky, but worth a try. Try watching some YouTube teardown videos
sree27 said:
Check my post for detailed instructions. And yes, I did face that issue and fixed it by reinserting the battery. It's a bit risky, but worth a try. Try watching some YouTube teardown videos
Click to expand...
Click to collapse
Oh Great! do you have a link of your instructions man? thank you! so I really have to dissassemble the phone?
MJMarra34 said:
Oh Great! do you have a link of your instructions man? thank you! so I really have to dissassemble the phone?
Click to expand...
Click to collapse
It's on my profile. I haven't mentioned the disassembly part since it was not required in general cases. Check my profile for the detailed instructions
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
MJMarra34 said:
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
Click to expand...
Click to collapse
Are you on fastboot mode? What is on your display?
Im still at the part with the QFIL. Im retrying it right now bruh.. hmmm
MJMarra34 said:
Im still at the part with the QFIL. Im retrying it right now bruh.. hmmm
Click to expand...
Click to collapse
If you're having trouble with QFIL, best thing to do is uninstall Qualcomm drivers, reboot, reinstall, try again. Repeat until you can flash without problem.
I had to uninstall many times. Don't lose hope. It takes a lot of effort
hey Sree. I noticed that it is being detected as Qualcomm HS-USB diagnostics 9006. So what I did is I forced driver to install Qualcomm HS-USB QDLoader 9008. I'm now having a Sahara error. I'll try reinstalling drivers but I have a quastion. Does QFIL version matter ?
MJMarra34 said:
hey Sree. I noticed that it is being detected as Qualcomm HS-USB diagnostics 9006. So what I did is I forced driver to install Qualcomm HS-USB QDLoader 9008. I'm now having a Sahara error. I'll try reinstalling drivers but I have a quastion. Does QFIL version matter ?
Click to expand...
Click to collapse
I don't know. I used the latest one. Try the version linked in my original post. Also, of you're getting sahara fail, it's ok. You're on right track. Uninstall driver, reboot and reinstall. It'll take hell a lot of tries, but will work eventually
Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Dr_Raider said:
Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Click to expand...
Click to collapse
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Choose an username... said:
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Click to expand...
Click to collapse
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Kantastisch said:
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Click to expand...
Click to collapse
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Choose an username... said:
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Click to expand...
Click to collapse
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Kantastisch said:
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Click to expand...
Click to collapse
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Choose an username... said:
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
Click to expand...
Click to collapse
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Kantastisch said:
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Click to expand...
Click to collapse
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Choose an username... said:
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Click to expand...
Click to collapse
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Kantastisch said:
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Click to expand...
Click to collapse
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Choose an username... said:
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Click to expand...
Click to collapse
THANKS SO MUCH , you saved my ass, it flashed without a problem and sorry for bothering you. Bootloader is locked now and it works fine. Thanks again!
Can i do anything if my lg g6:
can't access fastboot and download mode
won't load into rom (they may not be one afterall xD)
is only stuck on lg g6 thinq logo
pc doesnt see the device when plugging in
only thing i can do is hold power and volume- buttom to do a factory reset which is the way to access twrp (which is not loading in)
bootloader is unlocked
and ideas or throw this trash?
I have the same situation like this Would love someone to express their opinions on the situation.
Kerres said:
Can i do anything if my lg g6:
can't access fastboot and download mode
won't load into rom (they may not be one afterall xD)
is only stuck on lg g6 thinq logo
pc doesnt see the device when plugging in
only thing i can do is hold power and volume- buttom to do a factory reset which is the way to access twrp (which is not loading in)
bootloader is unlocked
and ideas or throw this trash?
Click to expand...
Click to collapse
BubisUK said:
I have the same situation like this Would love someone to express their opinions on the situation.
Click to expand...
Click to collapse
You guys can still unbrick by putting the phone in 9008 mode and using the QFil method mentioned here:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
(Thank the OP in the thread.)
OP above does warn that the method will not work for T-Mobile version of g6, H872.
Do make sure that phone is detected in 9008 mode when you connect to Windows PC. If it is not detected, you might have to put phone in 9008 mode by grounding the connection point on motherboard. You will need to remove the back glass, some screws and and connect the connection point located below flash for camera to the ground plate in phone as shown here:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-testpoints-edl-mode-9008-t3916962
(Thank the OP in the thread.)
Let's hope your phones are already detected in 9008 mode on PC so you don't have to open the back of phone. This is a bit complicated process and not many will be able to help you if you get stuck with anything, so best would be to read through the posts and making sure you understand all the steps before proceeding and asking OP in those threads if you get stuck. I have only used this method once and it worked for me. There is no visible indication when phone enters EDL mode by short circuiting the board. Have a device manager window open and phone connected to the PC via USB when you attempt short circuit so you know once it enters 9008 mode. Good Luck.
Android# said:
You guys can still unbrick by putting the phone in 9008 mode and using the QFil method mentioned here:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
(Thank the OP in the thread.)
OP above does warn that the method will not work for T-Mobile version of g6, H872.
Do make sure that phone is detected in 9008 mode when you connect to Windows PC. If it is not detected, you might have to put phone in 9008 mode by grounding the connection point on motherboard. You will need to remove the back glass, some screws and and connect the connection point located below flash for camera to the ground plate in phone as shown here:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-testpoints-edl-mode-9008-t3916962
(Thank the OP in the thread.)
Let's hope your phones are already detected in 9008 mode on PC so you don't have to open the back of phone. This is a bit complicated process and not many will be able to help you if you get stuck with anything, so best would be to read through the posts and making sure you understand all the steps before proceeding and asking OP in those threads if you get stuck. I have only used this method once and it worked for me. There is no visible indication when phone enters EDL mode by short circuiting the board. Have a device manager window open and phone connected to the PC via USB when you attempt short circuit so you know once it enters 9008 mode. Good Luck.
Click to expand...
Click to collapse
You ar a star I will try using the method you linked here, thank you and have a nice day