Related
Mine motog5s updated to stock fw and root uninstalled after it it hangs on boot screen. I flashed stock fw again with fastboot but after restart mobile didn't display anything not even vibrate just blinking notification when connect usb wire . how to unbrick only shows qualcomm hs dloader 9008 what to do, pls. reply.
You cannot log into fastboot mode?
qualcomm hs dloader 9008 = EDL mode, you should be able to restore with QFIL: https://forums.lenovo.com/t5/MOTO-E-1st-Gen/Moto-E-Not-Boot-Up/td-p/3231144 but it looks like motorola doesn't provide the files ... most likely you'll need a service center
Do not use QFIL. To unbrick, we need the blankflash file for G5S. And it is not on the Internet yet. Do not use the blankflash of any other models. Your best bet is to take the phone to a service center.
---------- Post added at 11:46 AM ---------- Previous post was at 11:46 AM ----------
Did you try holding the power down button and turning on the phone to enter bootloader?
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
ASHDCBZ said:
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
Click to expand...
Click to collapse
You downloaded the unlock key from Moto website by giving them your device serial number. That's how they know you unlocked bootloader. Service center won't help you. But fortunately, there is a way to revive your phone. But I'm not getting the blankflash file anywhere.
Tell me what exactly did you do to your phone.
Thank you,
Ok I just flahsed & tried stock roms, root & custom roms. Then I flashed stock rom of mine region firmware npp26.102.19 then motorola gave the updates to npp26.102.55-1 Dec. patch. Then next day new update came Feb patch npp26.102.55-4 just after it mobile started hanging & when restart it stuck on boot, not booting just stuck on boot animation. I tried TWRP recovery it said encrypted then I entered the unlock pin then it shows all the folders. Then I again fastboot npp26.102.19 to solve the issue but after flashing & restart it did not boot nor screen on no vibration tried several times but no response, when connect with pc or charger a white notification light blinking only & it detected as QHUSB_BULK something like that then I searched for it & install driver then shows as qualcomm dloader 9008.
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
ShattrdChain said:
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
Click to expand...
Click to collapse
Hmmmmmmmm
Please provide blankflash soon file I'll try.
there is no notification light on my g5s. what is blinking on yours?
Andrew Joseph said:
there is no notification light on my g5s. what is blinking on yours?
Click to expand...
Click to collapse
Next to front flash right side a white light is blinking. Try pressing power button then it will show.
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Andrew Joseph said:
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Click to expand...
Click to collapse
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
does this only happen when you root your phone?
Can someone Help Us?
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
brunovsc said:
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
Click to expand...
Click to collapse
Yes tried this & other blank flash it show only this-----
Failed identify board. Wrong package?
ERROR: error loading package
FAILED: qb_flash_singleimage()->error loading package
other tried this also----------
Found this can anyone try
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
qfil also not flashing sahara error.
I have tried this but there's an error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
ASHDCBZ said:
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
Click to expand...
Click to collapse
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
brunovsc said:
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Same error shows in Qfil.
Andrew Joseph said:
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
Click to expand...
Click to collapse
So is it not switch on or displaying anything.
Hello,
I'm using Redmi Note 5 pro. Recently my device went on boot loop. Whenever I tried to restart, it was showing MI Logo for long time, nothing happens. I'm not able to enter into recovery mode as well (Vol Up + Power). But I can go to Fastboot mode (Vol down + power key).
Mine is not bootloader unlocked and I dont think I have enabled OEM Unlocking from the settings.
I tried downloading the ROM from below URL (Rom for Fastboot flash) -> whyred_global_images_V11.0.3.0.PEIMIXM_20191108.0000.00_9.0_global
http://c.mi.com/in/miuidownload/detail?guide=2
http://update.miui.com/updates/v1/fullromdownload.php?d=whyred_global&b=F&r=global&n=
When I check, whether the fastboot devices is showing mine or not, I can see my device listed
In another forum, I can across this, before flashing using MiFlash, they asked to download the Edl.cmd file from the below link and run it. I did that as well.
https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
After that, when I select the downloaded ROM, and try to flash it with MiFlash (v2019.12.6.0), it keep showing the below line. but its not getting errored out. progress bar keeps going till the end but it stays with the below status. Attached the screenshot as well.
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
Any help with will be much helpful! Thanks in advance!
I think flashing via fastboot on unlocked bootloader is not possible
Hi, you mean locked bootloader is not possible?
If yes, is there a way to fix the phone?
Thanks in advance!
karthik623521 said:
Hi, you mean locked bootloader is not possible?
If yes, is there a way to fix the phone?
Thanks in advance!
Click to expand...
Click to collapse
The way i see is Edl flash mode (wait for a proper answer)
I accidentally locked my chinese whyred while flashing global rom using miflash.
The only thing that worked for me was EDL flash chinese rom using QFIL following the tutorial here: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I had to use chinese rom for 360 hours until I could unlock the bootloader again.
You need to flash the rom version that matches your device origin (global, china, india, russia, etc..)
tsarig said:
I accidentally locked my chinese whyred while flashing global rom using miflash.
The only thing that worked for me was EDL flash chinese rom using QFIL following the tutorial here: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I had to use chinese rom for 360 hours until I could unlock the bootloader again.
You need to flash the rom version that matches your device origin (global, china, india, russia, etc..)
Click to expand...
Click to collapse
Hello, Thanks for letting me know about this method. I tried this but I'm not able to find my devices showing in Device Manager as "qualcomm hs-usb qdloader 9008" (I'm trying with fastboot mode as am not able to go to Recovery mode)
I tried installing the Qualcomm QDLoader 9008 driver using the method shown in the below link
https://www.99mediasector.com/install-qualcomm-hs-usb-qdloader-9008-install/
1. tried direct installation of exe - didn't work)
2. there was manual method which asked me to reboot in edl mode using the command fastboot oem edl - but this shows error saying FAILED (remote: 'Device is already locked!')
//attached screenshot for reference
Thanks!
karthik623521 said:
Hello, Thanks for letting me know about this method. I tried this but I'm not able to find my devices showing in Device Manager as "qualcomm hs-usb qdloader 9008" (I'm trying with fastboot mode as am not able to go to Recovery mode)
I tried installing the Qualcomm QDLoader 9008 driver using the method shown in the below link
https://www.99mediasector.com/install-qualcomm-hs-usb-qdloader-9008-install/
1. tried direct installation of exe - didn't work)
2. there was manual method which asked me to reboot in edl mode using the command fastboot oem edl - but this shows error saying FAILED (remote: 'Device is already locked!')
//attached screenshot for reference
Thanks!
Click to expand...
Click to collapse
You're in fastboot. not EDL mode.
EDL Testpoint - https://youtu.be/dYVR5BgNwG0
Connect the usb cable to both phone and pc, disconnect the battery flex cable, short the two EDL testpoint, and connect the battery flex cable. it will take some practice.
Also, there is a limited time in EDL mode to start flashing, if you too late you will have to repeat again.
Use this tutorial https://youtu.be/ikGsxf_s-zw
It seems shorting pins and edl flashing is the only way for reviving ur phone pal
Good luck
Hi all,
I have a T-Mobile Revvlry that I’ve been trying to flash lineage os to. It was unlocked and now after so many tries, it is oem locked
I went through all the unlock bootloader process before and was able to flash but always no os installed are you sure you want to proceed.
Slots a and b were confusing and so I changed the slot to a for flashing but this time the bootloader screen changed along with the serial number and now it is oem locked and can do nothing now .
I tried to boot twrp but no success. How can I oem unlock?? I tried the command fastboot oem unlock and fastboot flash etc but it is denied and that I need a code. Which I do have but don’t know how to use it now.
glossallalia said:
Hi all,
I have a T-Mobile Revvlry that I’ve been trying to flash lineage os to. It was unlocked and now after so many tries, it is oem locked
I went through all the unlock bootloader process before and was able to flash but always no os installed are you sure you want to proceed.
Slots a and b were confusing and so I changed the slot to a for flashing but this time the bootloader screen changed along with the serial number and now it is oem locked and can do nothing now .
I tried to boot twrp but no success. How can I oem unlock?? I tried the command fastboot oem unlock and fastboot flash etc but it is denied and that I need a code. Which I do have but don’t know how to use it now.
Click to expand...
Click to collapse
Did you follow the preinstall instruction and use copy-partitions-20210323_1922.zip?
if not that's what caused the problem.
You will need to use a blankflash to fix
Search for Channel blankflash there are some here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but you may need a newer one
The device will need to be in Emergence Download Mode (EDL Mode)
Use
Code:
fastboot oem blankflash
or
boot twrp (use full twrp file name)
Code:
fastboot boot twrp.img
and use
Code:
adb reboot edl
EDL Mode is just a black screen, and
Windows device manager will see it as a Qualcomm device (attached)
If it says ..._bulk... you need the Qualcomm drivers
Thank you! Yes I did follow the preinstall instruction and used copy-partitions-20210323_1922.zip several times. But obviously messed it up somehow.
I was missing some of the things you mentioned so I’ll work on that and thanks again!
sd_shadow said:
Did you follow the preinstall instruction and use copy-partitions-20210323_1922.zip?
if not that's what caused the problem.
You will need to use a blankflash to fix
Search for Channel blankflash there are some here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but you may need a newer one
The device will need to be in Emergence Download Mode (EDL Mode)
Use
Code:
fastboot oem blankflash
or
boot twrp (use full twrp file name)
Code:
fastboot boot twrp.img
and use
Code:
adb reboot edl
EDL Mode is just a black screen, and
Windows device manager will see it as a Qualcomm device (attached)
If it says ..._bulk... you need the Qualcomm drivers
Click to expand...
Click to collapse
Blankflash did work to blank the screen. But <adb reboot edl > came back with ‘no devices/emulators found’.
I do have the Qualcomm drivers
glossallalia said:
Blankflash did work to blank the screen. But <adb reboot edl > came back with ‘no devices/emulators found’.
I do have the Qualcomm drivers
Click to expand...
Click to collapse
No, you only use "adb reboot edl" if "fastboot oem blankflash" didn't work.
Now use the blankflash file.
sd_shadow said:
No, you only use "adb reboot edl" if "fastboot oem blankflash" didn't work.
Now use the blankflash file.
Click to expand...
Click to collapse
Ok, when I do the blankflash, there is the blank screen, however I can't communicate with the device after that and if I have lineage.zip or copy-partitions-etc...zip, how could I flash it or what is the next step? I'm new at this - I started this a year ago, after, gave up for a while.
Thanks!
glossallalia said:
Ok, when I do the blankflash, there is the blank screen, however I can't communicate with the device after that and if I have lineage.zip or copy-partitions-etc...zip, how could I flash it or what is the next step? I'm new at this - I started this a year ago, after, gave up for a while.
Thanks!
Click to expand...
Click to collapse
If you have run the blank-flash.bat and it worked the device will reboot to bootloader.
If the device remains in EDL Mode, the blankflash failed, you may need a newer version.
You may need to do some searching in the forums for a newer version.
sd_shadow said:
If you have run the blank-flash.bat and it worked the device will reboot to bootloader.
If the device remains in EDL Mode, the blankflash failed, you may need a newer version.
You may need to do some searching in the forums for a newer version.
Click to expand...
Click to collapse
thanks - blank-flash.bat worked and i'm back to flashing again - I sideload copy-partitions-etc.zip and the lineage.zip and there is 'no os installed...' this happens every time, and before as well. When I 'start' from the fastboot flash mode, it starts to draw the lineage symbol, then goes back to bootloader.
glossallalia said:
thanks - blank-flash.bat worked and i'm back to flashing again - I sideload copy-partitions-etc.zip and the lineage.zip and there is 'no os installed...' this happens every time, and before as well. When I 'start' from the fastboot flash mode, it starts to draw the lineage symbol, then goes back to bootloader.
Click to expand...
Click to collapse
what is the file name of lineage.zip?
sd_shadow said:
what is the file name of lineage.zip?
Click to expand...
Click to collapse
LineageOS17.1Modified.img.xz
I went to Motorola website and flashed the firmware to restore the phone to its original state. I'll try lineage again in future and thank you!
Okay, I messed up.
Device OP9Pro EU version.
Used Updater and updated to O12 and device went to Fastboot mode.
Tried:
to flash/boot twrp - no luck
found fastboot restore rom in 4PDA, flashed, restarted back to fastboot
manually fastboot flash - extracted Oxygen rom with payload dumper - back to fastboot.
Trying to find a way from fastboot to EDL to use msmtool.
HAS ANYONE IDEAS?
ptr21 said:
Okay, I messed up.
Device OP9Pro EU version.
Used Updater and updated to O12 and device went to Fastboot mode.
Tried:
to flash/boot twrp - no luck
found fastboot restore rom in 4PDA, flashed, restarted back to fastboot
manually fastboot flash - extracted Oxygen rom with payload dumper - back to fastboot.
Trying to find a way from fastboot to EDL to use msmtool.
HAS ANYONE IDEAS?
Click to expand...
Click to collapse
Use the MSM unbrick tool and bring it back to android 11!
herrieberry said:
Use the MSM unbrick tool and bring it back to android 11!
Click to expand...
Click to collapse
I cant enter edl mode. Key combinations are useless. Any time I connect phone to PC, it goes to fastboot mode.
It brings you back to android 11.2.2.2 (Razorcortex)
power of the phone
plug in the phone to pc
start msm tool
press vol up, vol down and power button together for a few seconds
tools starts updating the phone
herrieberry said:
It brings you back to android 11.2.2.2 (Razorcortex)
Click to expand...
Click to collapse
How to do - I'm stuck in fastboot, cant enter edl.
herrieberry said:
power of the phone
plug in the phone to pc
start msm tool
press vol up, vol down and power button together for a few seconds
tools starts updating the phone
Click to expand...
Click to collapse
The phone is off.
Any time I connect it ti PC fastboot boots up, no way to enter EDL.
Try to connect it first and then power of?
herrieberry said:
Try to connect it first and then power of?
Click to expand...
Click to collapse
No luck.
I can power off from fastboot menu, 3 seconds and it restarts in fastboot again.
fastboot erase userdata or
fastboot format userdata
MrSteelX said:
fastboot erase userdata or
fastboot format userdata
Click to expand...
Click to collapse
Did.
Back to fastboot again.
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
that should help to msm phone to working order
MrSteelX said:
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
that should help to msm phone to working order
Click to expand...
Click to collapse
Thanks, but the phone is still stuck in fastboot mode.
I cant enter EDL.
I power off the phone and when I connect phone to PC, it still boots to FASTBOOT, whatever keycombination I use. Every time.
Get msm up and ready.. Click box to use "lite firehose." then power off ur phone from fastboot.. While holding vol buttons plug in and quickly click enum and soon as it says connected click start. I've had samw problem with msm constantly turning phone on. Eventually u will get it. Click box for firehose lite and u shld be good
Shooter7889 said:
Get msm up and ready.. Click box to use "lite firehose." then power off ur phone from fastboot.. While holding vol buttons plug in and quickly click enum and soon as it says connected click start. I've had samw problem with msm constantly turning phone on. Eventually u will get it. Click box for firehose lite and u shld be good
Click to expand...
Click to collapse
I got it... almost.
I established connection, started to flash and DEVICE NOT MATCH IMAGE error appeared.
I am sure I have EU device 2123, selected eu from droplist in MSMtools.
Now What?
Did u click box for "use firehose lite".? If so u either can try unchecking sha256 check or try to find msm for EU
lemonadep_22_E.05_210324.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
ptr21 said:
I got it... almost.
I established connection, started to flash and DEVICE NOT MATCH IMAGE error appeared.
I am sure I have EU device 2123, selected eu from droplist in MSMtools.
Now What?
Click to expand...
Click to collapse
With this options it' s working for me
Option Target select EU
Something I figured out on my 9Pro is that it would only stay in EDL mode for about 10 seconds if nothing was done. It would then boot into recovery or fastboot. Here's how I got mine to work, with the phone powered off I got the MSM tool all set up to go. If your phone is starting up as soon as you plug the cable in make sure you're holding vol up and down while plugging in, otherwise pwr+vol up+vol down. As SOON as the device connects hit the start button on msm tool (if you wait msm tool would not start because the phone was no longer in edl mode). The flash then went through and I was back to Android 11. Hope that helps.
It took a few tries but I got it to work.
Hi there, I am encountering the following issue.
It is a hindi op9 pro
The situation:
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
Any ideas or advice? Plz help
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
it keeps on cycling back to 9008 so what you meant by xbl or abl is broken? Any solution ?
Renate said:
Can you locate the Firehose loader?
Click to expand...
Click to collapse
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
My msm tool from that
Renate said:
Have you tried various USB problem solving, different cables, different ports?
Click to expand...
Click to collapse
Yes I think it is no issues with my cable
Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
FOR MORE DETAILS
I tried upgrading my device using fastboot firmware according to the following according to this article
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
when I reached to put commands in cmd and wrote
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
then reboot by
fastboot reboot fastboot
it gets stuck in edl mode and no anything showing just " Qualcomm HS-USB QDLoader 9008" showing in the device manager, appearing and disappearing about every five seconds
so the situation is
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in the device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Click to expand...
Click to collapse
Fastboot commands already worked and I used them to upgrade my phone according to the article above, so when finished, I put a reboot command, and then it got stuck on EDL mod, so I tried to repair it using MSM tool it always says Sahara communication failed, any way to fix it plz my phone is new
Click to expand...
Click to collapse
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Renate said:
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Click to expand...
Click to collapse
thank you but is there a video explaining it bcz I am a noob in this stuff plz.
or you can contact my device using TeamViewer and try to fix it plz.
I don't know your partitions well enough.
If it wants a two stage reflash with 1/2 by (abl) fastboot and 1/2 by (recovery) fastbootd then you need a working recovery and I'm not sure that you have one.
The original post didn't indicate that you were able to reach/use fastboot.
I jumped on this because it seemed to be about USB/Sahara which I know something about.
We need the advice of somebody who knows more about your model.
Sorry
Can you tell how you ended up in this state? If you are a noob, why did you start wipe stuff from your phone without knowing how to what you are doing?
I would guess you thought a custom rom sounded nice but you don't have a clue what to do when things are starting to go south..
Edit: We, as a community always try to help out as much as we can but (and there is a BIG but) you have to understand the basics before you even start to do stuff or you will learn the hard and in some cases expensive way.
Read and do research at least for a few month, like reading most of the threads here and try to figure out how things work.
recovered my noodlep a week ago using this:
How to recover your device after flashing incorrect DDR xbl images
No matter how you are experienced or skilled in flashing ROM's, the things sometimes just happens. And you are here now... Even I was aware which DDR model was my device, yes.. I did it :D - flashed by mistake DDR4 xbl.img to my DDR5 noodlep...
forum.xda-developers.com
You may want to check it out....
Best luck. and don't worry. Just follow the steps and you'll recover your device.