Develop Bugs

how to unbrick dead redmi 1s

I am flashing wrong ROM on my redmi 1s .my phone was not able to switch on ,not charging, no bootloader,no fastboot mode totally crashed. I pressed volup+power,voldown+power not going to any mode.When I connected to PC,it recognized Qualcomm qdloader driver. I am flash to ROM with mi flash tool it recognised COM10 PORT When I flash official stock ROM I got error not flashing.is there any way to flash ROM on my device.I am searched on google I found Qualcomm flash tool,how to flash ROM with Qualcomm flash tool pls help me

naveen3186 said:
I am flashing wrong ROM on my redmi 1s .my phone was not able to switch on ,not charging, no bootloader,no fastboot mode totally crashed. I pressed volup+power,voldown+power not going to any mode.When I connected to PC,it recognized Qualcomm qdloader driver. I am flash to ROM with mi flash tool it recognised COM10 PORT When I flash official stock ROM I got error not flashing.is there any way to flash ROM on my device.I am searched on google I found Qualcomm flash tool,how to flash ROM with Qualcomm flash tool pls help me
Click to expand...
Click to collapse
Man, you are not the only one in this situation, I accidentally erased the f*cking 'tz' partition. If you are on linux, connect the phone to USB, the preloader will find that the whole of the data is messed up and put the phone into bulk mode. In bulk mode, the partitions of the phone is exposed as such so you can copy files into it. DONT DO IT WITHOUT RESEARCH. BUT I AM NOT SURE HOW TO RESTORE IT. If I get tz.img instead of tz.mbn, I will be able to 'dd' it. I dont think I can 'dd' a mbn file.

..

generex144 said:
Man, you are not the only one in this situation, I accidentally erased the f*cking 'tz' partition. If you are on linux, connect the phone to USB, the preloader will find that the whole of the data is messed up and put the phone into bulk mode. In bulk mode, the partitions of the phone is exposed as such so you can copy files into it. DONT DO IT WITHOUT RESEARCH. BUT I AM NOT SURE HOW TO RESTORE IT. If I get tz.img instead of tz.mbn, I will be able to 'dd' it. I dont think I can 'dd' a mbn file.
Click to expand...
Click to collapse
MIflash actually works , just b on new miflash version(which capable of switch 9008-9006 mode)...
it may gives errors many times...
tips to b successfull flash..
1. charge battery with external charger (most imp. )
2.if ur using pc, connect usb to motherboard usb port.( backside ports of cabinet)
3.try changing usb cables (sounds stupid but actually worked for me, as phone wont stay in 9006/9008 mode if usb signal drop)
dd wont work until u have access to fastboot/adb..

another way is make deep flash cable..
dnt wrry its very easy

Brick - Mobile does not wake up / Black Screen / EDL Mode HS-USB 9008

Hello sirs, I hope you can help me.
I have a mi6 that turned into a brick. Hold the buttons to it to give restart / download mode or put it to load. He does not respond to anything.
However,
By putting it on your computer it recognizes you as Qualcomm QDLoader 9008.
I wonder if I can recover it yet. or unfortunately it turned a paper weight.

DL Xiaomi flash tool and flash fastboot rom. It will be fine.

icrunchbanger said:
DL Xiaomi flash tool and flash fastboot rom. It will be fine.
Click to expand...
Click to collapse
I tried to do this form, downloaded all the miui site drivers, adb fastboot and cualcomm driver.
How to run my flash with a last method with the xiaomi global mi6 I got the following error:
"Cannot receive hello packet Xiaomi Device"
The program tried a few more times and nothing more.
What can I be doing wrong? Do you have another option? because he is in what they call DeadBrick (I discovered this term only now, after searching the forums)

XeeXa said:
I tried to do this form, downloaded all the miui site drivers, adb fastboot and cualcomm driver.
How to run my flash with a last method with the xiaomi global mi6 I got the following error:
"Cannot receive hello packet Xiaomi Device"
The program tried a few more times and nothing more.
What can I be doing wrong? Do you have another option? because he is in what they call DeadBrick (I discovered this term only now, after searching the forums)
Click to expand...
Click to collapse
I know, i was there. Reboot your computer and start again.

I restarted and tried again.
I formatted and installed only the drivers and the error continues.
I tried with miflash 2015 until version miflash2017

I think, you device isn't in EDL mode. You open back cover of device. Make test point for QDL 9008. Then, you flash fastboot rom by Mi flash tool. It's very simply. I made it for unbrick my Mi6 several times.
See video here.
https://youtu.be/vSNRQdUuNYw

bahuy2003 said:
I think, you device isn't in EDL mode. You open back cover of device. Make test point for QDL 9008. Then, you flash fastboot rom by Mi flash tool. It's very simply. I made it for unbrick my Mi6 several times.
See video here.
Click to expand...
Click to collapse
Is this the only way to put the phone in edl mode?

Yes, it's only way for Mi6, which is locked bootloader.

{Solved}I gotta super slim brick !!!!

I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Solved: Use the first blank flash from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175

mookiexl said:
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Click to expand...
Click to collapse
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
mookiexl said:
Solved: Use the first blank flash to from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
Click to expand...
Click to collapse
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?

Technical said:
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Click to expand...
Click to collapse
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.

Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment

Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
Before connecting the phone, start the blankflash program. Maybe you have to repeat it a couple of times. Also try different cables, ports and computers.

Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

mookiexl said:
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Click to expand...
Click to collapse
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?

LØNEWØLF said:
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
Click to expand...
Click to collapse
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go: https://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0! ???

Dany XP said:
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go:
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0!
Click to expand...
Click to collapse
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens

LØNEWØLF said:
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
Click to expand...
Click to collapse
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?

Dany XP said:
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Click to expand...
Click to collapse
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?

LØNEWØLF said:
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
Click to expand...
Click to collapse
Uh...good question

My Mi a2 lite Have A Big Problem " usb can't recognize" EDL / FastBoot

Greetings first
S.A
I flashed PA10 on My Mi a2 lite and worked greet but i entered to recovery rom to check something and when i restart to system i did press on Install TWRP if isnt installed ... i got bootloop when he booted to system
i connected the phone to Mi flash but when i connect him to pc FastBoot showing " usb can't recognize "
Same when i Enter EDL MODE ( pin Test ) " usb can't recognize "
The Problem not from Cable i tryd 6 cable same problem
Help me please and sorry for prolongation & English

M3Do0 said:
Greetings first
S.A
I flashed PA10 on My Mi a2 lite and worked greet but i entered to recovery rom to check something and when i restart to system i did press on Install TWRP if isnt installed ... i got bootloop when he booted to system
i connected the phone to Mi flash but when i connect him to pc FastBoot showing " usb can't recognize "
Same when i Enter EDL MODE ( pin Test ) " usb can't recognize "
The Problem not from Cable i tryd 6 cable same problem
Help me please and sorry for prolongation & English
Click to expand...
Click to collapse
reinstall the drivers ,provided with MiFlash ,if the problem presists ,change the usb to another on your pc

nikoman1987 said:
reinstall the drivers ,provided with MiFlash ,if the problem presists ,change the usb to another on your pc
Click to expand...
Click to collapse
Still Dont work 3 computer and 1 PC Cafe same problem
the last usb device you connected to this computer malfunctioned and windows does not recognize it
Help please i got this MSG from / Fast boot / EDL

M3Do0 said:
Still Dont work 3 computer and 1 PC Cafe same problem
the last usb device you connected to this computer malfunctioned and windows does not recognize it
Help please i got this MSG from / Fast boot / EDL
Click to expand...
Click to collapse
sorry ,never faced that kind of issue ,try installing different drivers ,because if the device malfunctioning ,then driver issue or hardware...

PC cant detect my phone

i flash pixel experience plus and latest firmware and now my phone stuck in fastboot mode and wont detect on my pc.. i cant see it on device manager either.. whenever i try to restart it goes to stucked twrp logo.. can someone help me here?

aidenskcyu said:
i flash pixel experience plus and latest firmware and now my phone stuck in fastboot mode and wont detect on my pc.. i cant see it on device manager either.. whenever i try to restart it goes to stucked twrp logo.. can someone help me here?
Click to expand...
Click to collapse
You just have to update drivers from device manager.
Follow this, you can use the fastboot drivers either from Xiaomi or Google (if you already have them installed)
If you don't have the Android with exclamation mark, you can do it the same as shows the latest image.

SubwayChamp said:
You just have to update drivers from device manager.
Follow this, you can use the fastboot drivers either from Xiaomi or Google (if you already have them installed)
If you don't have the Android with exclamation mark, you can do it the same as shows the latest image.
Click to expand...
Click to collapse
Before i got stuck in fastboot my phone doesn't really detected in my pc even on other computers with fastboot drivers. USB File Transfer not working too, it's only charging. I'm using Havoc OS 4.8 rom and this firmware.

aidenskcyu said:
Before i got stuck in fastboot my phone doesn't really detected in my pc even on other computers with fastboot drivers. USB File Transfer not working too, it's only charging. I'm using Havoc OS 4.8 rom and this firmware.
Click to expand...
Click to collapse
And did you try what I posted? Probably you need to check which drivers you have actually installed, some of them are sometimes redundant and not necessary, what you need is the Google ADB/fastboot that it is in the Google site, and regards Xiaomi all is in the Mi flash tool and Mi Unlock tool, see to the option to install the drivers hoping that you don't need the Qualcomm 9008-USB drivers.
Of course, this is assuming that you have a data cable not only a charger cable and the issue is not with the ROM itself.

Use known good data cable!!!
Does the phone see the connection?
Is it configured properly?!!!
Try another port.
Reboot, reboot, reboot...
Event manager, check for error messages.
Disk management>scan for new disks, open from here!
Device management, update driver, rollback driver... reboot.
Meh, play with it...

SubwayChamp said:
And did you try what I posted? Probably you need to check which drivers you have actually installed, some of them are sometimes redundant and not necessary, what you need is the Google ADB/fastboot that it is in the Google site, and regards Xiaomi all is in the Mi flash tool and Mi Unlock tool, see to the option to install the drivers hoping that you don't need the Qualcomm 9008-USB drivers.
Of course, this is assuming that you have a data cable not only a charger cable and the issue is not with the ROM itself.
Click to expand...
Click to collapse
can you give me the file for fastboot? now its showing “Unknown USB Device (Device Descriptor Request Failed)”

aidenskcyu said:
can you give me the file for fastboot? now its showing “Unknown USB Device (Device Descriptor Request Failed)”
Click to expand...
Click to collapse
Are you sure your device is actually in fastboot mode with that issue "Device Descriptor Request Failed"?
The drivers are in the Mi Flash tool, when you install the tools you can see the option to install the drivers that are already included in the Mi unlock tool.
From there, just follow the steps indicated in the pictures to update them.

SubwayChamp said:
Are you sure your device is actually in fastboot mode with that issue "Device Descriptor Request Failed"?
The drivers are in the Mi Flash tool, when you install the tools you can see the option to install the drivers that are already included in the Mi unlock tool.
From there, just follow the steps indicated in the pictures to update them.
Click to expand...
Click to collapse
i tried it but it has exclamation mark in android bootloader interface.

aidenskcyu said:
i tried it but it has exclamation mark in android bootloader interface.
Click to expand...
Click to collapse
It's not showing here an exclamation mark,
Can you upload the right SS?,
Also Did you install the fastboot drivers either from Mi Unlock tool or Mi Flash tool?

Try to install ADB and FastBoot drivers for redmi note 8

If Dosent work text here

SubwayChamp said:
It's not showing here an exclamation mark,
Can you upload the right SS?,
Also Did you install the fastboot drivers either from Mi Unlock tool or Mi Flash tool?
Click to expand...
Click to collapse
yes i did install it

aidenskcyu said:
yes i did install it
Click to expand...
Click to collapse
All is here in this same sequence.

i dont know why i get this error code 10.

aidenskcyu said:
i dont know why i get this error code 10.
Click to expand...
Click to collapse
Upload the same as my pictures 2 and 3 from your device manager, from the picture 2 you can use either from Xiaomi or Google.
Delete that Kedacom USB driver and replace for the proper ones, here you have the right guide https://xiaomifirmware.com/guides-and-tips/delete-kedacom-usb-device-driver-pc/

SubwayChamp said:
Upload the same as my pictures 2 and 3 from your device manager, from the picture 2 you can use either from Xiaomi or Google.
Delete that Kedacom USB driver and replace for the proper ones, here you have the right guide https://xiaomifirmware.com/guides-and-tips/delete-kedacom-usb-device-driver-pc/
Click to expand...
Click to collapse
somehow it got detected as android bootloader interface. it got detected too in miflash and tried to flash but i got stucked in flashint system.img. after a while it shows timeout error and after that i flash twrp recovery but i got a message that my battery is very low to flash it. will my phone charge in fastboot? because it keeps bootlooping now if ii dont go on fastboot mode

aidenskcyu said:
somehow it got detected as android bootloader interface. it got detected too in miflash and tried to flash but i got stucked in flashint system.img. after a while it shows timeout error and after that i flash twrp recovery but i got a message that my battery is very low to flash it. will my phone charge in fastboot? because it keeps bootlooping now if ii dont go on fastboot mode
Click to expand...
Click to collapse
Well, at least you got your device showed, no?
To power off the device you can put it in fastboot mode, after of approximately 10 minutes if the device is not attached to your PC, it'll power off, then you can charge it.
But if your device reacts to the power charger trying to boot to nowhere, then fastboot will charge the battery but very, very slowly.
Do you have bootloader unlocked? Why not flashing it through EDL mode?, you don't need battery power to do that.