Database Users

Bricked for good?

Hi, I tried to push the 4.3 update and unroot my device through Wugfresh kit and all went well. But when it initially booted, I had this constant popup saying that "Bluetooth Share has stopped working" making the device unusable as it was stuck on the welcome screen. So, I rebooted into bootloader and tried to use the "Unroot + Stock" option saying my device had a soft brick and flash 4.2.2. But now nothing starts, it stays on the Google screen and that's it. I am however able to boot into recovery. I've checked the manual way of doing it but it says my USB debugging needs to be turned on (but I can't boot into the OS to do that)... To top it up, my computer isn't recognizing my device. I've used mskip's toolkit as well, no go. Are there any solutions or is my table gone for good?
Thanks
Oh yeah I tried again with Wugfresh it says this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You need to install this to use ADB in recovery.

Thanks, I've downloaded those drivers and followed the instruction for windows 8 but still adb doesn't recognize my device and I cannot boot into the device to change it to debugging mode as I cannot go past the Google screen =\ any other ways to make it recognize my device?
my brother has a nexus 7 do you guys think if I deleted all the drivers and put his into debugging mode it'll install drivers for mine too?

What you installed is needed to use ADB while in recovery. Here is the latest Android Composite ADB Interface Driver from SDK that you need for use of ADB while booted and fastboot in bootloader.
http://d-h.st/kDu
You do not need USB debugging to use ADB while in recovery or fastboot.

Username invalid said:
What you installed is needed to use ADB while in recovery. Here is the latest Android Composite ADB Interface Driver from SDK that you need for use of ADB while booted and fastboot in bootloader.
http://d-h.st/kDu
You do not need USB debugging to use ADB while in recovery or fastboot.
Click to expand...
Click to collapse
Hi, thanks again. However, I have no idea what to do with those files (the drivers) with ADB

Install or update through device manager.

I had a similar issue. My pc went to BSOD in the middle of writing system. To made it worse, fastboot stopped working altogether. My solution was to do the flashing from my Linux partiton. I know it's a crazy advice, but linux commands never fail, and you won't need drivers at all.
Still, try to use the "flash-all.bat" from the factory image, and stay away from toolkits.

When I plug in my nexus in (while in bootloader) on my device manager this pops up but then I try to update the drivers it says it can't update unknown device

You may have to disable Window's Driver Signature Enforcement.

I do not have a linux partition I'm using a windows 8 and I have 2 other PCs with win7 and xp. My windows 8 digital signature checking is disabled.
EDIT: plugging my bro's nexus did not make mine get recognized by the PC. I am installing linux on my other PC just to see if it works + i've never used linux so a new experience

running it on ubuntu 12.04 did not help either =\ while in bootloader in terminal I type in adb devices and not devices are listed under "List of devices attached"

When you are in boot loader mode you need to use fastboot instead of adb, I.e. try:
fastboot devices
(I suppose you have the latest SDK installed ...)
Sent from my Nexus 7 using xda app-developers app

Well guys, I've been doing this for about 12 hours straight lol and I'VE FINALLY DONE IT THROUGH UBUNTU OMG I LOVE UBUNTU! YES!!! Thank you all for the amazing support and advice! Much appreciated. Thank you ALL! :highfive:

It's not as if your device was bricked in the first place
Installing the drivers in Ubuntu is very easy using "sudo apt-get install android-tools".

Can't boot into recovery or system

I flashed the latest chinese 7.1.1 and it bootloops. So I tried going into recovery to wipe/reinstall and found that it wasn't working. The led blinks 3 times and the phone turns off.
I can boot into bootloader, but Windows is not recognizing my device, it just says "Android" under device manager.
Any ideas how to fix this?

have you tried EDL method to restore your original firmware?

otaconremo said:
have you tried EDL method to restore your original firmware?
Click to expand...
Click to collapse
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing

bornlivedie said:
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing
Click to expand...
Click to collapse
try to remove the previous drivers on windows or reinstall another qcom driver. or maybe try from another computer. unless it gets 9008 mode in windows, you can't do anything on it.

otaconremo said:
try to remove the previous drivers on windows or reinstall another qcom driver. or maybe try from another computer. unless it gets 9008 mode in windows, you can't do anything on it.
Click to expand...
Click to collapse
Already did all those things
tried multiple installations of windows, multiple drivers
QUSB_BULK is installed but MiFlash or axon7root won't detect it

Dumb question but did you try booting normally? Power button only, no vol buttons.
Should take you to the ZTE logo followed by the bootloader unlocked screen.

You said you can boot into bootloader, right? Did you try fastboot commands? If fastboot works, try flashing stock boot and recovery from yoir previous rom and reboot to recovery.

t2jbird said:
Dumb question but did you try booting normally? Power button only, no vol buttons.
Should take you to the ZTE logo followed by the bootloader unlocked screen.
Click to expand...
Click to collapse
Yes, i can see the bootloader screen and go into fastboot.
otaconremo said:
You said you can boot into bootloader, right? Did you try fastboot commands? If fastboot works, try flashing stock boot and recovery from yoir previous rom and reboot to recovery.
Click to expand...
Click to collapse
Windows is not recoginizing the phone while in fastboot. It just says "Android" under device manager. Can't make it work with google usb drivers.
I need the correct drivers to flash the firmware while in EDL mode.

bornlivedie said:
Yes, i can see the bootloader screen and go into fastboot.
Windows is not recoginizing the phone while in fastboot. It just says "Android" under device manager. Can't make it work with google usb drivers.
I need the correct drivers to flash the firmware while in EDL mode.
Click to expand...
Click to collapse
Possibly it is a driver issue. Maybe try disabling driver signature in windows? Just google it.

otaconremo said:
Possibly it is a driver issue. Maybe try disabling driver signature in windows? Just google it.
Click to expand...
Click to collapse
It's off...
I just reinstalled windows 10 and now this is happenning:
Windows 10 recognizes my device as Handset Diagnostic Interface(DFU) (COM3) after installing the QUSB_BULK driver
forcing the QUSB_BULK drivers is not working, as it says that windows couldn't verify the compatibility of the drivers, installs them anyway, and shows the device as COM10 and no tool detects the phone....

Try reading this thread. They're discussing about drivers here as well.
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
And here's another one i came across with.
https://forum.xda-developers.com/axon-7/help/fastboot-recognizing-phone-bootloader-t3492201

I also had trouble with the drivers when trying to unlock the bootloader. It wasn't easy.
I had to put the phone in CD mode to install the supplied drivers. It's a must.
Then I followed the guide and some guys' extra comments on the post to unlock the G variant. It was tricky... I suggest you read that guide and "choose an user name" comment here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379/page32

I have terrible experience between Windows 10 and axon's driver - it's not work with any reason.
Try with again with Windows 7 (or at least Windows 8.1) , it may work for you.

bornlivedie said:
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing
Click to expand...
Click to collapse
If you're able to connect to EDL then is driver is the issue... Try connecting from your friend pc...
I always go using the below method to get in EDL mode.. If you haven't tried... Check this as well
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried flashing the chinese firmware as well without b15 bootdtack... But able to boot to recovery.. But the version of twrp shows as 3.0N 1...i thought it's a glitch and flashed the recovery 3.04.1 and it showed correctly... Don't know it helps at this level
Sent from my ZTE A2017U using Tapatalk

`SBR` said:
If you're able to connect to EDL then is driver is the issue... Try connecting from your friend pc...
I always go using the below method to get in EDL mode.. If you haven't tried... Check this as well
I tried flashing the chinese firmware as well without b15 bootdtack... But able to boot to recovery.. But the version of twrp shows as 3.0N 1...i thought it's a glitch and flashed the recovery 3.04.1 and it showed correctly... Don't know it helps at this level
Click to expand...
Click to collapse
3.0.N1 came from the bootstack. If I remember correctly, it's one that unjustified_dev compiled to go with it.

i probably hard bricked a1 open for any ideas ( only launch in edl mode)

Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver

hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.

onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?

Need some help for a bricked pure

I have not touched this phone in a year, so forgive me if im rusty.
I embarked on a project of compiling slimroms 7.1.2 for this device a year ago, and made a rom that made it onto the device. Now, Here is my mistake. At the time when i built the rom, the nougat bootloader for this device was not out yet(i think, as my bootloader is on a0.4d aka dated 2016-11-30) Giddy that i had finally built a custom rom that worked, i hurriedly flashed the device through the recovery(twrp at the time) and thats when the issues happened. The device will not charge past 1 percent, and in an effort to fix, without knowing that my outdated bootloader was the issue, i decided that installing stock recovery was the best option. BIG MISTAKE. as i now cannot flash anything in recovery. i keep getting signature verification failures and what not.
With that backstory out of the way, here is my issue. I cannot flash anything in fastboot, because when i connect the device to windows i get
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Yes i have updated the drivers and when i install the motorola drivers manually i get this:
Code:
This device cannot start. (Code 10)
A request for the USB device descriptor failed.
this is the single most thing that is keeping me from reviving this device. I have tried using linux, but the device just doesnt show up. I have tried multiple usb cables. so i know thats not the issue. any help would be very appreciated.
UPDATE: i have done some digging around and no loader files are working. (using a 32gig class 10 microsd). Also, It is on stock recovery so i cannot flash anything other than stock images, which if i am correct, none are recovery flashable, only the otas are. When i try to flash an ota it doesnt work because it is expecting stock apps in system, which are not there since i am on a slimrom rom.
TLDR: i have stock bootloader and recovery, (24.49-18-8/4) but have a non rooted slimrom 7.1.2 which shows up in windows as get device descriptor failed(unknown device). if there was a way to root slimrom 7.1 without usb and with stock recovery that would help alot.

Have you tried the method to revive the phone in Qualcom mode (error 9008)?

mr_5kool said:
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
Click to expand...
Click to collapse
Can you link me to a thread that has that info please?
When I am in bootloader and hit the power button on the qcom option my phone just boots into the slimroms option with no change in the USB side

Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860

mr_5kool said:
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
So my issue is worse than that. It shows up on the computer as "device descriptor get failed" so I am unableble to use that method unless I can force it into qdloader mode

Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA

mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
When i try to install this driver, it says that it is incompatable for my device
I will try again when i get home tomorrow though

mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
Alright, When i try to install this driver i get this
View attachment 4594365
And this is the error i have on any machine
View attachment 4594369

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!

mr_5kool said:
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
Click to expand...
Click to collapse
its quite alright. i think that i bricked the phone while trying to use an unsupported bootloader, therefore bricking the mainboard
Its noones fault but my own, so i will chalk this one up to a loss lol

EDL Mode HD1925

So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!

I always power off my phone. Then hold both volume buttons down and plug it in. MSM tool sees my phone and hit start.

which Qualcomm drivers you installed ? because my phone is not connecting with MSM tools ....

I'm having the same issues. Anyone find a fix?

Charles: said:
I'm having the same issues. Anyone find a fix?
Click to expand...
Click to collapse
I installed twrp recovery software to go into EDL mode after that all works fine and connected

Zain ul Abedin said:
I installed twrp recovery software to go into EDL mode after that all works fine and connected
Click to expand...
Click to collapse
Which TWRP?? Did you load it via Fastboot and use Fastboot commands? Are you A11? Which Qualcomm drivers?

I basically forget that , but search about it . And install TWRP in your phone

otoyayamaguchi said:
So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!
Click to expand...
Click to collapse
I think it's supposed to only last for a few seconds. Pull up the MSM Tool and pay attention to the "Status of Connection" field for any of the COM lines in the MSM Tool. When you connect, it should say "Connected" for one of those lines. If that happens at all, then you're good to proceed. Make sure you have TMO selected in the drop-down, click "Enum" once you plug in your device, then click Start. Try to do this quickly. Let me know if this helps.

I am having the same problem with my 7T Pro McLaren, the pc recognizes it but msm tool does not, someone has already found the way
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I had the same issue. One easy fix is switching from a USB 3.0 port to USB 2.0 port. The other method that worked for me is a little more of a process.
1) Have MSM open
2) Connect phone to PC
3) Power phone off
4) Then, the moment it powers down, hold the vol +, -, & power button
5) Keep holding it. Your PC will make a sound notifying you that it's detected the phone, but you want to keep
holding the buttons until you hear it being detected for the second time.
6) Release buttons.
Hopefully that makes it stay in EDL mode for you.

I wrote on this somewhere, but you can try having the program open and placed at the right settings, then move quickly once the phone is in EDL mode. Not ideal but worked for me. Once the process begins it won't exit out of EDL mode in my experience.

hii, from most tutorial i have seen so far, the com number is show in the msm tool upon starting the program, most the two msm tools i have tried so far dont show com number... and its not detecting my phone.