I got a new A2017G on B06 Marshmallow. It is brand new unrooted without bootloader unlock.
I placed the B10 Marshmallow EU official update.zip on root of storage and updated by SD card method.
However after reboot I am stuck on a black screen (attached photo) saying "Your device has failed verification and may not work properly"
What should I do? Sorry for my ignorance
Are you sure that model is a2017g (see on back)? A2017g is no more available to bay in last few month, except on gearbest for >500$.
AhmedHM said:
I got a new A2017G on B06 Marshmallow. It is brand new unrooted without bootloader unlock.
I placed the B10 Marshmallow EU official update.zip on root of storage and updated by SD card method.
However after reboot I am stuck on a black screen (attached photo) saying "Your device has failed verification and may not work properly"
What should I do? Sorry for my ignorance
Click to expand...
Click to collapse
You will have to reflash with a EDL file plenty of information on this around.......
svsavic said:
Are you sure that model is a2017g (see on back)? A2017g is no more available to bay in last few month, except on gearbest for >500$.
Click to expand...
Click to collapse
Yes it is A2017G, I got it in a local overstock clearance
stinka318 said:
You will have to reflash with a EDL file plenty of information on this around.......
Click to expand...
Click to collapse
As far as I understand EDL flash is for unlocked OEM bootloader, right? I have the out of box bootloader.
If you may refer me to the appropriate tutorial I would be grateful.
I have a A2017G with no root and locked bootloader.
try here.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
or here.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
AhmedHM said:
As far as I understand EDL flash is for unlocked OEM bootloader, right? I have the out of box bootloader.
If you may refer me to the appropriate tutorial I would be grateful.
I have a A2017G with no root and locked bootloader.
Click to expand...
Click to collapse
No it is for flashing stock rom regardless of bootloader status.
try to flash the Nougat B10 update in a same procedure! this should help.
you will find this update here on xda! search for -> axon 7 b10 download
I have tried everything on the forums to no avail.
No EDL, no FTM, no fastboot, nothing.
When I connect the device to the PC it lists in device manager as ZTE Handset Diagnostic Interface(DFU) (COM3) despite having installed all Qualcomm drivers.
Is this a 4th category brick? And how could it have occured by simply updating
via the official update.zip?
AhmedHM said:
I have tried everything on the forums to no avail.
No EDL, no FTM, no fastboot, nothing.
When I connect the device to the PC it lists in device manager as ZTE Handset Diagnostic Interface(DFU) (COM3) despite having installed all Qualcomm drivers.
Is this a 4th category brick? And how could it have occured by simply updating
via the official update.zip?
Click to expand...
Click to collapse
Try this first:
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Oki said:
Try this first:
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Click to expand...
Click to collapse
I kept getting the device registering in device manager in DFU mode. But I noticed that it briefly registers as QUSB_BULK before reverting to DFU. So I installed zadig winUSB driver and now it registers as QUSB_BULK when I turn on the device pressing all 3 buttons.
How can I proceed now?
AhmedHM said:
I kept getting the device registering in device manager in DFU mode. But I noticed that it briefly registers as QUSB_BULK before reverting to DFU. So I installed zadig winUSB driver and now it registers as QUSB_BULK when I turn on the device pressing all 3 buttons.
How can I proceed now?
Click to expand...
Click to collapse
Now you can proceed by uninstalling the Zadig driver and attempting a 4th category unbrick. i.e. using my DFU unbrick guide or trying your luck with an edl cable and Oki's guide.
If it were so simple as to get out of DFU by installing a Zadig driver we wouldn't have dfu guides
I sent it back to ZTE and hope they honour their warranty
AhmedHM said:
I sent it back to ZTE and hope they honour their warranty
Click to expand...
Click to collapse
they shouldn't actually. But they never check whether it's DFU or not, they just swap mobos.
If they find out, they'll charge you $80.
Choose an username... said:
they shouldn't actually. But they never check whether it's DFU or not, they just swap mobos.
If they find out, they'll charge you $80.
Click to expand...
Click to collapse
Why shouldn't they? It happened because of their official update installed from within the update app in the settings!?!?
AhmedHM said:
Why shouldn't they? It happened because of their official update installed from within the update app in the settings!?!?
Click to expand...
Click to collapse
Lol sorry, I confused threads
Related
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.
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.
rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...
I held the power and vol down and now it shows up under com ports so this is a good sign.
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...
5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?
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!
Dear Friends,
I had this problem...
Buy this phone with MM6.0.1 and after a week decide to update to N 7 with OTA. Process was clear and fast...
after another week and affording a lot of issues with clock, bluetooth, etc.. i decide to rollback to MM6.0.1
There's the problem... phone boots and do the presentation of images like it wants to enter, but stucks in the image of AXON...
Only can enter in a strange recovery, without shelters... only START, Restart Bootloader, Recovery mode(that does nothing), Power OFF, and Boot to FFBM
Anyone has a minimal idea that was happen? Don't want to wait an eternity to send back to china and wait to reapir, if anyone have a solution.
Images are an example of issue, you can see but no can do anything in the screens.
Thanks for your kindly cooperation folks!!!
tanoobx said:
Dear Friends,
I had this problem...
Buy this phone with MM6.0.1 and after a week decide to update to N 7 with OTA. Process was clear and fast...
after another week and affording a lot of issues with clock, bluetooth, etc.. i decide to rollback to MM6.0.1
There's the problem... phone boots and do the presentation of images like it wants to enter, but stucks in the image of AXON...
Only can enter in a strange recovery, without shelters... only START, Restart Bootloader, Recovery mode(that does nothing), Power OFF, and Boot to FFBM
Anyone has a minimal idea that was happen? Don't want to wait an eternity to send back to china and wait to reapir, if anyone have a solution.
Images are an example of issue, you can see but no can do anything in the screens.
Thanks for your kindly cooperation folks!!!
Click to expand...
Click to collapse
Version of MM is important! Was it on V1.0.0B10 or V1.0.0B11? If older, it was too old to go N and ZTE say do updates via SD card, not OTA. There are tools to recover it but I'm not up on them as mine is stock and carefully updated to B09 N so I will leave it to others well informed to explain recovery methods.
That's fastboot mode. No idea why it is booting to that screen. I assume you are locked so miflash is probably the easiest way to fix.
lafester said:
That's fastboot mode. No idea why it is booting to that screen. I assume you are locked so miflash is probably the easiest way to fix.
Click to expand...
Click to collapse
I try Miflash, but phone isn't recognized by PC or Miflash. I only see android with a yellow triangle. i'm searching for one idea or driver to make recognize my phone to PC and reflash all... do you have an idea?
RobboW said:
Version of MM is important! Was it on V1.0.0B10 or V1.0.0B11? If older, it was too old to go N and ZTE say do updates via SD card, not OTA. There are tools to recover it but I'm not up on them as mine is stock and carefully updated to B09 N so I will leave it to others well informed to explain recovery methods.
Click to expand...
Click to collapse
Mine was in V1.0.0B09
Find a way to unlock bootloader... connect phone to pc, and if not recognized open cmd and write: "fastboot oem unlock" this unlocks the twrp i had installed... thanks a lot to gandou63 from france... now i proceed to flash a rom, and after i told you how is going... thanks for the advices!!!
tanoobx said:
I try Miflash, but phone isn't recognized by PC or Miflash. I only see android with a yellow triangle. i'm searching for one idea or driver to make recognize my phone to PC and reflash all... do you have an idea?
Click to expand...
Click to collapse
Lol no, you have to put your phone in EDL mode. But maybe you can get to the recovery and flash another version first.
If you have an SD card, do this:
Turn the phone off, wait around 5 seconds and hold Volume Up and Power. It should boot into the recovery. You need to have the SD card inserted, with the B11 rollback package. select Install through sd card and install it.
If you don't have one, you need to get in EDL mode.
Connect the USB to the PC but not the phone.
Turn the phone off, wait around 5 seconds, then hold Volume Up and Volume Down (NOT power) and insert the USB cable on the phone. After that go to Device Manager and check that the phone appears (as Qualcomm HS-USB QDLoader 9008, in 'Ports (COM & LPT)'). Download an A2017G B11 FULL EDL package and flash it with miflash.
P.S. Is it an A2017G? If it is not, just use the packages from the model you have. I just read that 'send back to china' bit.
tanoobx said:
Mine was in V1.0.0B09
Click to expand...
Click to collapse
Here's the support page on the ZTE Australia website, I read this before doing any updates and have had a trouble free run to B09 N. Mine was on older firmware than B10MM when I purchased too.
http://www.ztemobiles.com.au/feature_AXON7.htm
The information will apply to any A2017G on older firmware. The latest shipments are now coming with B11 MM so they can go straight to B09 N.
I unboxed mine, turned on with B10MM update on an SD and updated it, then updated to B04. Didn't use it before it was on Nougat.
Choose an username... said:
Lol no, you have to put your phone in EDL mode. But maybe you can get to the recovery and flash another version first.
If you have an SD card, do this:
Turn the phone off, wait around 5 seconds and hold Volume Up and Power. It should boot into the recovery. You need to have the SD card inserted, with the B11 rollback package. select Install through sd card and install it.
If you don't have one, you need to get in EDL mode.
Connect the USB to the PC but not the phone.
Turn the phone off, wait around 5 seconds, then hold Volume Up and Volume Down (NOT power) and insert the USB cable on the phone. After that go to Device Manager and check that the phone appears (as Qualcomm HS-USB QDLoader 9008, in 'Ports (COM & LPT)'). Download an A2017G B11 FULL EDL package and flash it with miflash.
P.S. Is it an A2017G? If it is not, just use the packages from the model you have. I just read that 'send back to china' bit.
Click to expand...
Click to collapse
Thanks a lot for your kindly advice. I'll try...
Had to thanks all you guys for your advices... i unbricked my phone and all goes very well... Hugs for alls Guys!!!
hello ,
I had installed rescurssion remix rom on my phone and i had decided to change to stock rom. So I give my mobile to a mobile shop and they repaired and changed to stock rom.!!!!actually the problem is......after the repair of my mobile in the mobile shop when I switch power on it directly go to boot loader instead of showing boot logo..After that when it shows the update I updated . It suddenly HARD BRICKED.Only the white light near fingerprint sensor worked while charging. please help meee...:crying::crying::crying::crying:
please help me to make my mobile in good condition ........by solving the boot loader issue which shows as the start up...
If I've read your post correctly, you used an OTA update and that's when you had the white light blinking? When you connect your device to your computer, what is your device recognised as? Is it recognised as Qualcomm HS-USB 9008 or similar?
If so, you may wish to look at this guide to try to get your device fixed: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Do you know what the shop did for the repair, what stock ROM did they flash to your device?
echo92 said:
If I've read your post correctly, you used an OTA update and that's when you had the white light blinking? When you connect your device to your computer, what is your device recognised as? Is it recognised as Qualcomm HS-USB 9008 or similar?
If so, you may wish to look at this guide to try to get your device fixed: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Do you know what the shop did for the repair, what stock ROM did they flash to your device?
Click to expand...
Click to collapse
yes it recognize as Qualcomm HS-USB 9008 something like that
the shop has installed rom with build number NPJS25.93-14-18.....I think its april 2018 update
charuvilapauljohn said:
yes it recognize as Qualcomm HS-USB 9008 something like that
the shop has installed rom with build number NPJS25.93-14-18.....I think its april 2018 update
Click to expand...
Click to collapse
actually i did not know what did hey doo
what to do for the start up problem ith always starts with the boot loader
charuvilapauljohn said:
actually i did not know what did hey doo
what to do for the start up problem ith always starts with the boot loader
Click to expand...
Click to collapse
I'm confused by what help you're asking for, as you appear to be asking for help on how to fix a hard bricked device, and yet also asking for help on your device starting with the bootloader. If your device is fully hard bricked, then you wouldn't have a bootloader to boot to... Can I thus ask please is your device still in a blinking light state or are you now booting to the bootloader?
I asked you also in your other post if using fastboot oem fb_mode_clear would work in clearing the bootloader start: https://forum.xda-developers.com/showpost.php?p=76927663&postcount=421 However, if your device is truly hard bricked (and is in the Qualcomm HS-USB 9008 mode), then you need to try the blankflash as linked above, then re-flash the stock ROM - the NPJS25.93-14-18 April 2018 fastboot ROM and guide is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
thanks..it worked
It worked...thanks a lot...I installed NPJS25.93-14-18 rom....
Now there is another problem..both the sim and the finger print is not working
charuvilapauljohn said:
It worked...thanks a lot...I installed NPJS25.93-14-18 rom....
Now there is another problem..both the sim and the finger print is not working
Click to expand...
Click to collapse
That's because you phone model is changed to G4 only (not plus,) and lost 2nd IMEI... (Check in about section)
If it's changed to G4, follow,
Follow linked thread to solve: post #139, and better to read all posts to get correct information. (Turn pages to Download correct HW.img that's meant for your device model)
https://forum.xda-developers.com/mo...luss-model-changed-to-g4-lost-t3496912/page14
the hw.img file not working
____Mdd said:
That's because you phone model is changed to G4 only (not plus,) and lost 2nd IMEI... (Check in about section)
If it's changed to G4, follow,
Follow linked thread to solve: post #139, and better to read all posts to get correct information. (Turn pages to Download correct HW.img that's meant for your device model)
https://forum.xda-developers.com/mo...luss-model-changed-to-g4-lost-t3496912/page14
Click to expand...
Click to collapse
As I found a hw.img file for my xt1643.and i tried to install.The TWRP RECOVERY got struck.And the adb command prompt is not showing anything