Moto x play don't trun on after system update - X Play Q&A, Help & Troubleshooting

Hi,
During an android update (by OTA) my phone turnend off. Power button + volume down don't turn on the bootloader (nothing happens, I can only see a blackscreen).
Commands ADB and Fastboot don't work. Computer shows only a saying "Didnt recognized the USB device" or sometimes "Qualcomm HS-USB QDLoader 9008".
In the past the phone had TWRP and a lot of custom ROM's but I went back to stock.
Is it possible to flash it with PC? (With some kind of aplication like "smart phone flash tool")
Best regards!

You can't do anything. You lost your device. But if you find any solution then tell me.

bump

hubert987 said:
bump
Click to expand...
Click to collapse
You hard-bricked your device by Installing official OTA update in your unlocked device. This thing has happened to a lot of us unknowingly or by mistake. I did the same thing by mistake, I forgot about having an unlocked BL and flashed an official OTA update.
We basically fcuked up the bootloader/Fastboot I think and Motorola won't publish the required files to reflash it using Qfil.

Related

[Solved] A2017G totally Bricked

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.

[help] XT1572 can not power on after ota update

The phone battery was about 25%. I decided to do ota update. The phone was connected and charged by laptop. The process was successful. But when I selected and pressed restart to bootloader, the screen went black. The charger could not power it on, could not charge too (the phone was not hot). What happened to my phone, guys. Is there anyway to revive it? Sound was played when it connected to PC. But no device was showed.
Thankssssss
has anyone got the ramload and bootloader single image for X Style
What is the state of your phone?
Give us more info if you want any help. @mr_5kool
If your device powered off during the bootloader flash and all you get now is Qualcomm QDLoader... it's done, there is no blankflash file or other recovery method if you cannot get to fastboot. Sorry.
The pc now only shows hs-usb qdloader9008
@@
Bootloader dead
I need files to blankflash bootloader
Is there anyway to create 8992.mbn for X Style
mr_5kool said:
The phone battery was about 25%. I decided to do ota update. The phone was connected and charged by laptop. The process was successful. But when I selected and pressed restart to bootloader, the screen went black. The charger could not power it on, could not charge too (the phone was not hot). What happened to my phone, guys. Is there anyway to revive it? Sound was played when it connected to PC. But no device was showed.
Thankssssss
Click to expand...
Click to collapse
Sorry, don't know how to help with this device when it's in QDLoader 9008 mode, haven't seen blankflash for the XT157x.
Were you running stock 7.0 bootloader then downgrade and take a 6.0 OTA to brick the bootloader? Just curious.
Hope someone can help.
mr_5kool said:
The pc now only shows hs-usb qdloader9008
@@
Bootloader dead
I need files to blankflash bootloader
Click to expand...
Click to collapse
mr_5kool said:
Is there anyway to create 8992.mbn for X Style
Click to expand...
Click to collapse
No... Moto does not does not provide those files and all attempts to create or use a different one have failed.
Sorry, but it's just a brick now.
there's no way you can fix your phone now.. email motorola regarding this issue they might ask you to send your phone to some shop or service center
(if your country has one) and they might fix your phone.. but no guarantee about that also
you'll have to spend a lot for this fix..

Softbricked axon 7, need help !

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!

Bricked my Xiaomi Mi A1, Stuck in EDL 9008.

Hello everybody,
First off, I hate people who don't search on google before making a post, I have been searching for 4 days and I feel that it's appropriate to ask now.
I will make 2 parts to this thread, one will be a very fast explanation of what I did and the second part will be the same but a very thorough with a step by step process of what I messed up...
TL;DR: I was tired, late in the evening I flashed for some reason a Partition table of a Mi Note 3 on my Mi A1... I am now bricked and cannot access anything, fastboot, ADB, recovery nothing! I guess my phone is in EDL mode cause when I plug it in it flashes its led. "Qualcomm HS-USB QDLoader 9008" Is what I see in my device manager.
What do? oh, I forgot! I cannot access anything through any combination of buttons. I am stuck here, where I am!
The full thorough explanation for people who are bothered to read fully. (Includes my excuses for making noob mistakes, might be fun to read idk.)
Young me on a Sunday evening decides to reinstall magisk but this time with twrp cause I did it without twrp (yeah yeah I know). I was left without OTA's and after uninstalling anything that had something to do with Xposed or magisk I trashed it all. and stupid me thought that maybe? maybe? just maybe deleting Dalvik Cache would help me get my OTA's back after injecting my original ROM. This is where the fun begins.
I was not wanting to go through reinstalling magisk and all that to wipe the Dalvik Cache, I thought that that was my mission now, so I decided to search for methods that don't require root or being in the system, so some kind of fastboot or ADB command or something idk. I tried installing twrp and without my understanding that failed miserably and then I read some post where someone said that they flashed a mi note 3 partition table on their phone and something worked. Being the naïve little boii that I am, let's do that hey? Bam! bricked! I read somewhere I can open the phone and remove the battery and not having the tools is a mess, having to ask friends for some and voiding my warranty for something that probably won't work and after reading I understood that I'm in "EDL 9008 recovery" or something like that. I cannot boot into anything, I only have EDL 9008 to work with. I tried using Xiaomi's flasher tool and it would never respond to the initial hello packet (duuhh! I can't use ADB nor fastboot).
I know that this was stupid, I know! I learnt my lesson. If there is nothing we can do can I at least somehow get my internal storage data back? I deleted the backups from google drive for a short amount of time but randomly 5hrs prior to this sad story. All I have safe are now my contacts.
I hope you guys have some ideas! I feel like I'm fked but maybe with EDL 9008, there is a little glimmer of light?
P.S. If you guys somehow get me into fastboot I can flash a correct partition table back. My PC has all drivers so I can do this!
Sincerely, Micheal.
There is a way although i did tried it yet.
First of all sorry for my English.
Download latest MiFlash tool and qualcomm driver, this package contain both but not latest MiFlash so you should download lastest version from official site.
https://www.fshare.vn/file/H3R8M6OMRP2R
Download lastest stock rom.
You will need a good USB type C cable, dont use the one come with phone because you dont want to cut it in half.
Yes, that exactly what i said. Cut it in half, there are 4 small wire (or maybe 5 with type C?), remove it outer plastic and reconnect them.
Join the green and black cable, like you short circuit them, then plug your phone into PC with that cable without release green and black, wait for 5 sec then seperate them, the green and black.
Check device manager on your PC, you should hear device connect sound and qualcomm HS-USB QDLoader show up under Ports.
Open MiFlash and try to flash it.
You may want to check this video, although it in Vietnamese but you should understand the usb cable part.
https://www.youtube.com/watch?v=d5-1I9rWTiw
Hi, interesting situation. What about following this guide: http://en.miui.com/thread-235865-1-1.html ?
Its for some other phone, but try instaliing some drivers and you may get some signal of life.
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
m1shka said:
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
Click to expand...
Click to collapse
Yes, thats what I meant. Well, I dont know how to help you, wish you luck. I remember how I flashed wrong ROM for my S3 Mini and it was completly trashed, I'm glad that Xiaomi gives us at least some signs of life and hope.
And btw. I would rather charge the phone somehow - I hope it charges even in EDL mode, because if your phone dies while flashing with MiFlash, things can be even worse.
EDIT: I also found this guide, you can try it out: https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
m1shka said:
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
Click to expand...
Click to collapse
Wish you luck:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
did you try to hold more than 30 second ? and also , do you have flash log ?
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
So did you flash official stock ROM? Because I dont understand why doesnt it work... btw. when you flashed the ROM, did you lock bootloader?
Cant be battery dead?
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
EDIT: Maybe consider locking bootloader? Try it if youre on official stock.
EDIT 2: By flashing that ROM I guess you lost all data, but you can try to boot in TWRP without installing it and browse in file manager to see, if there is any data.
TrueMS said:
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
Click to expand...
Click to collapse
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
m1shka said:
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
Click to expand...
Click to collapse
As I said, you can try it, but when I flashed my Nougat stock ROM, i lost all the data. Or you can boot into TWRP and connect with USB to your computer to see the data in phone.
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
GVN.Gallus said:
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
Click to expand...
Click to collapse
None of the passwords I used worked.. I just factory reset it, thanks alot everybody. And now I will be more careful, don't flash anything weird. And backup!
I understood why I can't get the data back, if android fails at the encryption it jsut deletes everything!
My fone also in 9008 please can you guide me
I did the same what you have and it's on 9008 my flashing is successful but still my fone is not opening help me
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
How did you fixed i'm stuck in EDL?
SevenSlevin said:
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
Click to expand...
Click to collapse
i am in Qualcomm HS-USB QDLoader 9008 but i can't flash, it doesn't matter if the phone is on fastboot mode or turned off (i can't even turn it on)

hard bricked my moto g4 plus

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

Categories

Resources