Hello,
I have a Moto G in 2014 (XT1069), one day we test impregnation 6.0 installed.
But I did downgrade to 5.0.2 for a long time.
Today I went to an OTA installation and it just died.
When connecting to the computer, it is recognized as
"QDLoader Qualcomm HS-USB 9008 (COM3)"
And the bootloader was corrupt, anyone can help me?
Sorry for my English.
:crying:
Hey
w_luiz said:
Hello,
I have a Moto G in 2014 (XT1069), one day we test impregnation 6.0 installed.
But I did downgrade to 5.0.2 for a long time.
Today I went to an OTA installation and it just died.
When connecting to the computer, it is recognized as
"QDLoader Qualcomm HS-USB 9008 (COM3)"
And the bootloader was corrupt, anyone can help me?
Sorry for my English.
:crying:
Click to expand...
Click to collapse
Any progress? im in the same situation.... if you find the solution post here please!
If your phone detects as QDLoader Qualcomm HS-USB 9008, You can do the below steps.
Note: First download BlankFlash.zip and RiffBox JTag Drivers and extract both.
1. Connect your phone to the PC, when you see "QDLoader Qualcomm HS-USB 9008" in device manager, right click it and update the driver [Go to the RiffBox JTag Drivers folder and select that driver file to update].
2. After successfull driver updation, now go to BlankFlash folder and run blankflash.bat file.
It will flash a bootloader file on your device. And you will be able to boot into bootloader mode.
From bootloader mode you can flash factory firmware.
Hope this helps you both.
Let me know what happens next.
ArtRahul said:
If your phone detects as QDLoader Qualcomm HS-USB 9008, You can do the below steps.
Note: First download BlankFlash.zip and RiffBox JTag Drivers and extract both.
1. Connect your phone to the PC, when you see "QDLoader Qualcomm HS-USB 9008" in device manager, right click it and update the driver [Go to the RiffBox JTag Drivers folder and select that driver file to update].
2. After successfull driver updation, now go to BlankFlash folder and run blankflash.bat file.
It will flash a bootloader file on your device. And you will be able to boot into bootloader mode.
From bootloader mode you can flash factory firmware.
Hope this helps you both.
Let me know what happens next.
Click to expand...
Click to collapse
Unfortunately this is moto g 1st gen blank flash :/
Miiick3y said:
Unfortunately this is moto g 1st gen blank flash :/
Click to expand...
Click to collapse
These files are not for Moto G 2gen?
Help
I don't think there's any other way. Move on to a new phone.
Sent from my XT1068 using Tapatalk
ayuda motog2 2014 xt1063
yo igual me paso yo tenia android 4.4.4 kikat pero yo veia que había salido hace poco tiempo android 5.0 o 5.1.1. y despues salio android 6.0 pues como no sabia como hera android lollipop 5.0 entoces actualize mi telefono a android 5.0 y entonces al finalizar la actualización se apago y no bol vio aprender
ayuda si alguien sabe una posible soluciom
Is there anyway this could be fixed or a new blankflash could be installed? My phone has the same issue :/
ArtRahul said:
If your phone detects as QDLoader Qualcomm HS-USB 9008, You can do the below steps.
Note: First download BlankFlash.zip and RiffBox JTag Drivers and extract both.
1. Connect your phone to the PC, when you see "QDLoader Qualcomm HS-USB 9008" in device manager, right click it and update the driver [Go to the RiffBox JTag Drivers folder and select that driver file to update].
2. After successfull driver updation, now go to BlankFlash folder and run blankflash.bat file.
It will flash a bootloader file on your device. And you will be able to boot into bootloader mode.
From bootloader mode you can flash factory firmware.
Hope this helps you both.
Let me know what happens next.
Click to expand...
Click to collapse
Any idea where to get blankflash.zip for Moto G2 XT-1068?
Related
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
yasteellutch said:
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
Click to expand...
Click to collapse
Connect phone to computer.
Take off battery. And wait.
Is your pc can detect your device on bootloader mode?
yasteellutch said:
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
Click to expand...
Click to collapse
Or google "Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 (if you have the right kind of rom)"
And use that method.
Yes
nhmanas said:
Is your pc can detect your device on bootloader mode?
Click to expand...
Click to collapse
My pc sees the phone in QDLoader 9008 mode
yasteellutch said:
My pc sees the phone in QDLoader 9008 mode
Click to expand...
Click to collapse
I don't know what that is but flash stock rom again via fastboot
General Mobile 4G Dual cihazımdan Tapatalk kullanılarak gönderildi
yasteellutch said:
My pc sees the phone in QDLoader 9008 mode
Click to expand...
Click to collapse
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
FindYanot said:
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
Click to expand...
Click to collapse
I shall try but I pray it works. I am literally stuck in Android Development without my phone, Emulators aren't good enough
My dear sir you are a freaking genius
You my friend are a genius. I dont know where you acquired these files. It works like brand new. Thank you sir. Thank you thank you thank you!!!!!!!!!!!!!!!!
One Problem.
FindYanot said:
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
Click to expand...
Click to collapse
The phone wont turn on with battery in. It only turns on when I use usb without battery
yasteellutch said:
The phone wont turn on with battery in. It only turns on when I use usb without battery
Click to expand...
Click to collapse
Try flash stock rom via fastboot from here
http://builds.cyngn.com/factory/crackling/cm-12.1-YOG4PAS33J-crackling-signed-fastboot.zip
FindYanot said:
Open https://cloud.mail.ru/public/NExC/qxFwsmmmV/Wileyfox Swift/Recover SW/
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction https://mega.nz/#!YUFiXRwI!PlPCplXY31Rje57IfmWucTbRY6d56nSU6de46cQxIqU
Click to expand...
Click to collapse
Hi @FindYanot , are you able to upload WileyfoxTool1.0 exe on your website and also MEGA? I can't register at 4pda.ru as I always fail the CAPTCHA, even when I use the Russian Keyboard Viewer on Mac.
I have obtained the Android One (General Mobile 4G LUZ17E Retail build) prog_emmc_firehose_8916.mbn , emmc_appsboot.mbn , patch0.xml , rawprogram_upgrade.xml , system.img , NON-HLOS.bin etc. files from Longcheer but I can't get into Emergency Download Mode from my hardbricked Swift, even when pressing Volume Up or Volume Down + Power when inserting USB cable. 'fastboot devices' doesn't list the phone when connected via USB cable, and QFIL 2.0.0.3 within QPST 2.7.429 Qualcomm 9008 2.1.0.5 on Windows 10 x86 gives me a Sahara error and RELINK / Woowellstrong Electronic co., ltd 9008 2.0.0.0 on Windows 8.1 x64 gives me an EDL error.
Thank you.
dabotsonline said:
Hi @FindYanot , are you able to upload WileyfoxTool1.0 exe on your website and also MEGA? I can't register at 4pda.ru as I always fail the CAPTCHA, even when I use the Russian Keyboard Viewer on Mac.
I have obtained the Android One (General Mobile 4G LUZ17E Retail build) prog_emmc_firehose_8916.mbn , emmc_appsboot.mbn , patch0.xml , rawprogram_upgrade.xml , system.img , NON-HLOS.bin etc. files from Longcheer but I can't get into Emergency Download Mode from my hardbricked Swift, even when pressing Volume Up or Volume Down + Power when inserting USB cable. 'fastboot devices' doesn't list the phone when connected via USB cable, and QFIL 2.0.0.3 within QPST 2.7.429 Qualcomm 9008 2.1.0.5 on Windows 10 x86 gives me a Sahara error and RELINK / Woowellstrong Electronic co., ltd 9008 2.0.0.0 on Windows 8.1 x64 gives me an EDL error.
Thank you.
Click to expand...
Click to collapse
Would you mind posting those files, why aren't you using the Swift recover files as findyanot posted it fixed my one, it w was seen as 9008 after I installed driver, I also removed battery before plugging to PC.
Sent from my SM-N920I using Tapatalk
hmsq said:
... why aren't you using the Swift recover files as findyanot posted it fixed my one, it w was seen as 9008 after I installed driver, I also removed battery before plugging to PC.
Click to expand...
Click to collapse
I have those files as well, and get the same problem even when removing the battery.
hmsq said:
Would you mind posting those files...
Click to expand...
Click to collapse
Will do when I have a chance!
I was on custom roms, but i wanted to back to stock, so when i was flashing the stock rom on my xt1776 sprint with adb fastboot, it doesnt boot anymore! After this, if i connect the phone on my pc, it recognize it like "Qualcomm HS-USB QDLoader 9008"
I used Qfil and others tools and can't fix it
No recovery, no fastboot, nothing
Anyone ideas?
Thanks
MarioMoncadaa said:
I was on custom roms, but i wanted to back to stock, so when i was flashing the stock rom on my xt1776 sprint with adb fastboot, it doesnt boot anymore! After this, if i connect the phone on my pc, it recognize it like "Qualcomm HS-USB QDLoader 9008"
I used Qfil and others tools and can't fix it
No recovery, no fastboot, nothing
Anyone ideas?
Thanks
Click to expand...
Click to collapse
use SP Flash Tool to reflash your stock rom
download it and download your official stock rom and connect it to pc
after flashing unplug your mobile from pc and power it on and replug and power on it will work
rashwanic said:
use SP Flash Tool to reflash your stock rom
download it and download your official stock rom and connect it to pc
after flashing unplug your mobile from pc and power it on and replug and power on it will work
Click to expand...
Click to collapse
Thanks, but are you sure that SP flash tools works also on snapdragon? i can swear that is only for mediatek devices
only for mediatek devices i guess
MarioMoncadaa said:
Thanks, but are you sure that SP flash tools works also on snapdragon? i can swear that is only for mediatek devices
Click to expand...
Click to collapse
only for mediatek devices i guess but try to google another flashing tool!
sorry if i couldn't help.
I can feel that my device was in the same case last week but it is with mediatek processor .
Moto E4 Plus XT1776 Hard Brick
Hi bro this model New CPU MSM8920 no solution internet but only one solution weit
does anyone have the stock rom for the 1776 boost or even sprint ? can not find it anywhere , all links that i can find are dead , H E L P P L E A S E
power of google
rein013 said:
does anyone have the stock rom for the 1776 boost or even sprint ? can not find it anywhere , all links that i can find are dead , H E L P P L E A S E
Click to expand...
Click to collapse
https://www.stockrom.net/2018/03/stock-rom-firmware-motorola-moto-e4-xt1761-android-7-1-nougat.html
https://www.stockrom.net/motorola
Hello, I am from Colombia and I need help so forgive my English I have a problem with my phone that is a moto g6 xt1925-2 I had unlocked the OEM to change the bootlogo but days later I got the update to android 9 via OTA and whatever it was updated, I did not want to turn it on anymore and when I connect it it only turns on the LED and it is detected as Qualcomm HS-USB QDLoader 9008 (COM6) please your collaboration would be very helpful. :crying::crying:
Try using a program Lenovo Moto Smart Assistant
support.lenovo.com/us/en/downloads/ds101291
And try using the recovery option, here is a guide: help.motorola.com/hc/apps/service/lmsa44/en-us/index.html?t=CGT1908243440
JuanMartinez02 said:
Hello, I am from Colombia and I need help so forgive my English I have a problem with my phone that is a moto g6 xt1925-2 I had unlocked the OEM to change the bootlogo but days later I got the update to android 9 via OTA and whatever it was updated, I did not want to turn it on anymore and when I connect it it only turns on the LED and it is detected as Qualcomm HS-USB QDLoader 9008 (COM6) please your collaboration would be very helpful. :crying::crying:
Click to expand...
Click to collapse
I'm in the same situation, unfortunately there is no definetly solution to a fullbrick, you may try this:
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
Use this blankflash file:
https://mirrors.lolinet.com/firmware/moto/ali/blankflash/
I'd tried but have an io error, in your case may work...
Greetings.
Hello everyone,
I recently stopped using my Nokia 8 in favor of my new iPhone 11. However, I wanted to keep it just so I have an emergency Android phone. I found an article that says that there is a possible way to update Nokia 8 via TWRP. Of course, I didn’t trust it, so I backed up my phone via TWRP. Here are the steps I took after back up:
- I deleted everything from the device including the OS, excluding SD
- I tried installing the image but it failed
- I then restored my backup
However, phone won’t boot even after I restored my backup. I followed these instructions (forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646/) to flash the stock firmware, but the OST LA program keeps giving me 0xc3b9 something like tool func not ready. Can anyone help me? Thanks in advance!
- I have my bootloader unlocked, if anyone’s wondering.
EDIT: I have followed the steps with more care, and I managed to advance to the flashing process, but it gets a new error; 0xc6DA
EDIT 2: I realized I don't have critical unlocked. I can't access my unlock.key since download link expired long ago. Is there any way I can unlock the critical at this moment?
Does your computer recognize your device in 9008 mode?
dongvatm said:
Does your computer recognize your device in 9008 mode?
Click to expand...
Click to collapse
How do I enter 9008 mode?
dongvatm said:
Does your computer recognize your device in 9008 mode?
Click to expand...
Click to collapse
UPDATE: It's recognized as HS-USB Diagnostics 9008
You must use OST LA 6.2.8 and firmware NB1-488 android 8.1. then update via emegency download. It works on EDL mode.
dongvatm said:
You must use OST LA 6.2.8 and firmware NB1-488 android 8.1. then update via emegency download. It works on EDL mode.
Click to expand...
Click to collapse
Do you have a link for OST LA 6.2.8 and its patch?
Link: https://fih-firmware.hikaricalyx.com/hmd_en.html
You can download ost LA and firmware at this link.
dongvatm said:
Link: https://fih-firmware.hikaricalyx.com/hmd_en.html
You can download ost LA and firmware at this link.
Click to expand...
Click to collapse
I get another error message that image upload with Sahara protocol failed - even though I have Qualcomm drivers
RaleBurazer said:
I get another error message that image upload with Sahara protocol failed - even though I have Qualcomm drivers
Click to expand...
Click to collapse
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
dongvatm said:
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
Click to expand...
Click to collapse
Yes, I do have that driver, and my phone is shown as 9008 device in device manager while I’m in EDL, however I get an error which said that image upload using Sahara protocol failed. Is there any fix for that?
QDloader 9008 not HS USB diagnostic 9008
dongvatm said:
QDloader 9008 not HS USB diagnostic 9008
Click to expand...
Click to collapse
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
RaleBurazer said:
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
Click to expand...
Click to collapse
You must download Qualcomm Usb driver. Use google to find it. Good luck
RaleBurazer said:
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
Click to expand...
Click to collapse
Does it work?
dongvatm said:
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
Click to expand...
Click to collapse
dongvatm said:
Does it work?
Click to expand...
Click to collapse
I managed to get Qualcomm QDLoader 9008, but I still get the “Image upload with Sahara protocol failed” error
RaleBurazer said:
I managed to get Qualcomm QDLoader 9008, but I still get the “Image upload with Sahara protocol failed” error
Click to expand...
Click to collapse
It's a good new if your computer recognize 9008 mode. Your phone's main is alive. Sahara failed because your phone is in EDL mode too long time. I don't know exactly how to fix it. The last hint: let take out your battery and insert again. Or Press and hold vol - + power 15-20s. Good luck
dongvatm said:
It's a good new if your computer recognize 9008 mode. Your phone's main is alive. Sahara failed because your phone is in EDL mode too long time. I don't know exactly how to fix it. The last hint: let take out your battery and insert again. Or Press and hold vol - + power 15-20s. Good luck
Click to expand...
Click to collapse
Now I managed to get rid of Sahara upload error, but I again got 0xc6DA error
Have you tried the instructions here: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Optimus_Toaster said:
Have you tried the instructions here: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
Update on the whole situation:
I managed to get to the download mode, and flash OREO NOVEMBER boot image on it. It successfully booted into Pie that I previously had installed. When I tried to follow the instructions given in the quoted post, I install November OTA successfully, but when I try to install December update, it says that I should use the 488K package. After I do that, it aborts the installation because there is no driver directory found. I think “Okay, November is fine” but when I try to reboot it goes into EDL. I again managed to flash the OREO boot image, and boot again into PIE (how is this possible?)
Also sidenote: WiFi doesn’t work. It didn’t work even after the first time I flashed Oreo boot. Can anyone perhaps provide me with a stock Pie boot image? Or does anyone know any other solution?
Back to stock - the aftermath
Hi all,
https://forum.xda-developers.com/showthread.php?t=4081895
(please read first and last post)
In short: I found some sketchy Android 10 update for Nokia 8, tried it out, did not work. Tried to restore my TWRP backup, did not work. Tried to bring back stock firmware via OST LA, did not work. I then flashed stock Oreo November 2018 boot image, and got into my Pie, but WiFi wasn't working. I then flashed pre-Magisk-rooted pre-TWRP-installed boot image, and WiFi works. However...
When my phone boots, it boots with Android logo instead of Nokia's
My phone is detected as Dual SIM, even tho it is not.
When I try to flash OTAs via TWRP, it doesn't work
I am looking for a solution on how to remove the Dual SIM problem and how to make my phone again boot with a classic Nokia logo. Any help? Thanks in advance!
Hi all, after lots of trial & error, I would like to share how I managed to unbrick my Redmi Note 8
original thread: https://forum.xda-developers.com/t/need-redmi-note-8-firehose-without-authentication.4031513/
many thanks to dxD7 who provided valuable info on how this worked for him
WARNING: this process requires you to enter EDL mode which means you have to separate backplate and short 2 pins on motherboard so USE AT YOUR OWN RISK! since its not quick&easy solution yet.. thanks Xiaomi!
Symptoms:
while pressing power button , the display backlight will turn on for approx a second and phone will vibrate and then turn off
while pressing power+volume- button, the phone will do the same as above but will show fastboot image for a second too
while phone is connected via cable its backlight will turn on for a second and thend turn off repeatedly..
tested on ginko, batch 2020.11 - but should work on other (older phones as well) not tested on 8T-willow but might work - some mention about it is in original thread
note that there is different kind of brick where after turning on the phone only the LED light blinks - it wasn't tested on that situtation but you can try it and pls let me know.
What you will need
clean windows without any previous ROM-flashing or android development drivers is recommended as it looks like windows is unable to fully uninstall previous drivers - they will reappear once device is connected
download xiaomi flash tool 20200314 from https://xiaomiflashtool.com/download/xiaomi-flash-tool-20200314
download QPST v2.7.480 from https://forum.hovatek.com/thread-22467.html
download fastboot ROM named ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz from https://bigota.d.miui.com/V11.0.11....XM_20201001.0000.00_9.0_global_389eff34c9.tgz
prog_emmc_firehose_Sm6125_ddr.zip from attachment
STEPS:
unpack ROM (for example to Desktop)
unpack prog_emmc_firehose_Sm6125_ddr.zip and place prog_emmc_firehose_Sm6125_ddr.elf from .zip into your unpacked ROM folder: /ginkgo_global_images_V11.0.11.0.PCOMIXM_20201001.0000.00_9.0_global/images/prog_emmc_firehose_Sm6125_ddr.elf (overwrite the old one)
run QFIL.exe and set it up similiarly like in this video (i know it's for 8T and but same principle is applicable here)
leave QFIL.exe running, you will need it later
now the tricky part. remove backlplate, connect phone using USB cable (prefferably stock cable that came with the phone and into USB2 slot) and short these 2 pins to get into EDL mode
{
"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 should hear windows sound of device plugged in. check in the device manager - it should report as unknown device QUSB_BULK_CID:XXXX_SN:XXXXXXXX
now run xiaomi flash tool 20200314 and it will prompt to install drivers so click Install and check if your unknown device now reports as QUALCOMM HS-USB QDLoader 9008 (if install process happended too fast and you cannot see the driver (this happened to me) please remove anything from MiFlash20200314\log folder and try again)
once the driver is installed, QFIL should show QUALCOMM HS-USB QDLoader 9008 instead of No Port Available
click on Download Content to flash firmware
now my 1st flash failed - I got Sahara Error, so I disconnected the cable, pressed all 3 buttons on phone for ~10seconds until screen blinked and phone vibrated
I connected cable again, shorted these 2 pins to get into EDL mode, pressed Download content again and now it worked (took few minutes) and Download Succeed
hold all 3 buttons for ~10seconds and phone should start up
to my knowledge the error you will get the most in QFIL is Sahara Fail. according to the internet, this might be due to many reasons (bad cable, bad usb port, antivirus running, wrong firmware or firehose or wrong driver but in my case it was the wrong driver - internet is full of various qualcomm driver but I had succes only with the one included in xiaomi flash tool 20200314 ) for more troubleshooting please use for example https://www.nirsoft.net/utils/usbdeview.zip check if your driver's version is same as on the attached image (2.1.0.5)
No reboot nor enabling unsigned drivers, running QFIL as administrator, disabling antivirus was needed in my case.
Maybe some of these steps are unnecesarry, maybe this guide can be written more understandably - sorry for that - i wrote is asap so I won't forget anything I did during process. Please feel free to modify it or I will try to improve it in the future if I brick my phone again and have more knowledge about it..
and I also need to figure out how to stick backplate to phone again so that it can be removed if needed while still preserving some kind of waterproof function..
EDIT: bricked my phone 3 more times aftrer trying to install RR but was able to recover from all of them again
UPDATE:
user Elinx stated that this happens only with 11-2020 batch and flashing FW 12.01 with recovery. So let's hope it won't happen on other batches..
It is also mentioned here (hope it helps):
see in this topic
and here too
mara91 said:
and I also need to figure out how to stick backplate to phone again so that it can be removed if needed while still preserving some kind of waterproof function..
Click to expand...
Click to collapse
I live in canada and I found a 2mm double sided tape on amazon for like 10$ made for electronics. I think that's what I'll buy, and I can come back with an update if it's good or not. https://www.amazon.ca/dp/B00BXYWXY8/
thanks either that or I'm thinking about B7000 glue which looks like many people are using for sticking battery cover
Thank you, I revived the Redmi Note 8 in the way you share.
u re welcome. good to see it works!
Hi, i will follow this process, but i have a different kind of brick, it`s completely dead, not vibrate, no led, nothing. The only sign of life is the sound in my pc when i connect/disconnect usb cable and i can see it in MiFlash as "COM3" and "QUALCOMM HS-USB QDLoader 9008" in QFIL.
It will work?
PD: i brick the phone after update to MIUI 12, ye i dont know how
nicolan004 said:
Hi, i will follow this process, but i have a different kind of brick, it`s completely dead, not vibrate, no led, nothing. The only sign of life is the sound in my pc when i connect/disconnect usb cable and i can see it in MiFlash as "COM3" and "QUALCOMM HS-USB QDLoader 9008" in QFIL.
It will work?
PD: i brick the phone after update to MIUI 12, ye i dont know how
Click to expand...
Click to collapse
I have the famous "Sharara" error, what did you do to solve it?
So i finally unbrick my phone! It´s alive ahaha. Thanks a lot, you are my new god.
The reason why i get Sahara error was becouse i have a old version of QPST/QFIL
Fantastic work. I waited about 50 days for the same so the official service could do this.
I'll bookmark your work if I need it again in the future
Cheers man. Thanks.
Nice work !
i saw a tutorial on how to enter EDL mode without opening the phone but i can't find it anymore
its here on xda, if you find it update your tutorial
I haven't tested this myself, but with unlocked bootloader you maybe can use the fastboot command:
fastboot oem edl
I haven't seen this with RN8 on XDA, but with RN7 Pro and Poco X3
thanks a lot, got my phone back.
how to remove back cover
Hey guys, could someone post an working qualcom driver ?
I´ve done everything but this damm SaharaServer Fail is killing me.
I got the Redmi note 8 .
Any hint ?
mara91 said:
Hi all, after lots of trial & error, I would like to share how I managed to unbrick my Redmi Note 8
original thread: https://forum.xda-developers.com/t/need-redmi-note-8-firehose-without-authentication.4031513/
many thanks to dxD7 who provided valuable info on how this worked for him
WARNING: this process requires you to enter EDL mode which means you have to separate backplate and short 2 pins on motherboard so USE AT YOUR OWN RISK! since its not quick&easy solution yet.. thanks Xiaomi!
Symptoms:
while pressing power button , the display backlight will turn on for approx a second and phone will vibrate and then turn off
while pressing power+volume- button, the phone will do the same as above but will show fastboot image for a second too
while phone is connected via cable its backlight will turn on for a second and thend turn off repeatedly..
tested on ginko, batch 2020.11 - but should work on other (older phones as well) not tested on 8T-willow but might work - some mention about it is in original thread
note that there is different kind of brick where after turning on the phone only the LED light blinks - it wasn't tested on that situtation but you can try it and pls let me know.
What you will need
clean windows without any previous ROM-flashing or android development drivers is recommended as it looks like windows is unable to fully uninstall previous drivers - they will reappear once device is connected
download xiaomi flash tool 20200314 from https://xiaomiflashtool.com/download/xiaomi-flash-tool-20200314
download QPST v2.7.480 from https://forum.hovatek.com/thread-22467.html
download fastboot ROM named ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz from https://bigota.d.miui.com/V11.0.11....XM_20201001.0000.00_9.0_global_389eff34c9.tgz
prog_emmc_firehose_Sm6125_ddr.zip from attachment
STEPS:
unpack ROM (for example to Desktop)
unpack prog_emmc_firehose_Sm6125_ddr.zip and place prog_emmc_firehose_Sm6125_ddr.elf from .zip into your unpacked ROM folder: /ginkgo_global_images_V11.0.11.0.PCOMIXM_20201001.0000.00_9.0_global/images/prog_emmc_firehose_Sm6125_ddr.elf (overwrite the old one)
run QFIL.exe and set it up similiarly like in this video (i know it's for 8T and but same principle is applicable here)
leave QFIL.exe running, you will need it later
now the tricky part. remove backlplate, connect phone using USB cable (prefferably stock cable that came with the phone and into USB2 slot) and short these 2 pins to get into EDL mode View attachment 5209521
you should hear windows sound of device plugged in. check in the device manager - it should report as unknown device QUSB_BULK_CID:XXXX_SN:XXXXXXXX
now run xiaomi flash tool 20200314 and it will prompt to install drivers so click Install and check if your unknown device now reports as QUALCOMM HS-USB QDLoader 9008 (if install process happended too fast and you cannot see the driver (this happened to me) please remove anything from MiFlash20200314\log folder and try again)
once the driver is installed, QFIL should show QUALCOMM HS-USB QDLoader 9008 instead of No Port Available
click on Download Content to flash firmware
now my 1st flash failed - I got Sahara Error, so I disconnected the cable, pressed all 3 buttons on phone for ~10seconds until screen blinked and phone vibrated
I connected cable again, shorted these 2 pins to get into EDL mode, pressed Download content again and now it worked (took few minutes) and Download Succeed
hold all 3 buttons for ~10seconds and phone should start up
to my knowledge the error you will get the most in QFIL is Sahara Fail. according to the internet, this might be due to many reasons (bad cable, bad usb port, antivirus running, wrong firmware or firehose or wrong driver but in my case it was the wrong driver - internet is full of various qualcomm driver but I had succes only with the one included in xiaomi flash tool 20200314 ) for more troubleshooting please use for example https://www.nirsoft.net/utils/usbdeview.zip check if your driver's version is same as on the attached image (2.1.0.5)
View attachment 5209555
No reboot nor enabling unsigned drivers, running QFIL as administrator, disabling antivirus was needed in my case.
Maybe some of these steps are unnecesarry, maybe this guide can be written more understandably - sorry for that - i wrote is asap so I won't forget anything I did during process. Please feel free to modify it or I will try to improve it in the future if I brick my phone again and have more knowledge about it..
and I also need to figure out how to stick backplate to phone again so that it can be removed if needed while still preserving some kind of waterproof function..
EDIT: bricked my phone 3 more times aftrer trying to install RR but was able to recover from all of them again
Click to expand...
Click to collapse
Hi, I tried to follow all of your steps. It flashed successfully but still not booting. still stuck at black screen. And it only just vibrates when I try to turn it on.
gracias , me salvaron.
no hay necesidad de quitar la tapa solo tengan presionado todos los botones y lo conectan así active el EDL .
akosizenmartin said:
... It flashed successfully but still not booting. still stuck at black screen....
Click to expand...
Click to collapse
From what I understand, this looks a specific problem with Board ID 3.29.
The reason could be that only the same Miui version or higher and same region can be flashed than the one with which the phone came.
Also flasshing without battery connection could help.
I too had this flashing backlight problem and found the reason why this happens.
It is only the november 2020 batch (11-2020) which has Miui 11.0.11
This batch can't be flashed with recovery to Miui 12.01 or 12.01 FW.
If you do this, your phone get this brick, while there isn't a single error with twrp flashing.
No fastboot, No recovery, No system anymore
You need EDL testpoint and patched firehose file to revive your phone.
With twrp, Flash Miui12.02 or higher , you will never notice this problem.
mara91 said:
así que haga clic en Instalar y verifique si su dispositivo desconocido ahora informa como QUALCOMM HS-USB QDLoader 9008 (si el
Click to expand...
Click to collapse
Israelleite said:
He hecho de todo, pero este maldito SaharaServer Fail me está matando.
Conseguí el Redmi note 8.
¿Alguna pista?
Click to expand...
Click to collapse
en la carpeta de qualcom hay otro bin entre hay entonces en esa carpeta está el QFLI e ise 2 veces y funcionó
uma