i bricked my realme 5 rmx1971 pro by flashing stock twrp rom to my devices. It is not booting at all. No fastboot no recovery. devices shows as qualcomm h in s-usb Qloader 9008 in ports. help would be really appreciated. I have tried differnt tools like msms tool crack , which gives sahara communication error. for qfil tool where to find firehose patch0 files.
bgaonkar96 said:
i bricked my realme 5 rmx1971 pro by flashing stock twrp rom to my devices. It is not booting at all. No fastboot no recovery. devices shows as qualcomm h in s-usb Qloader 9008 in ports. help would be really appreciated. I have tried differnt tools like msms tool crack , which gives sahara communication error. for qfil tool where to find firehose patch0 files.
Click to expand...
Click to collapse
If your phone is in warranty, you can get it fixed from authorised service centre for free.
If not in warranty, you will be charged for unbricking , like 1K INR.
You can also unbrick it online, search youtube, get numbers and contact. You will be charged around 1K.
Or
Wait till someone makes the device specific files to flash it through QFIL or MSM.
ATB.
SAME
Related
Hi. My phone is realme 5 pro and I've been using custom rom recently and decided to go back to stock rom. I was successfully able to go back to stock rom and then tried to flash a custom kernel which destroyed my boot.img . I was confused on what to do and accidentally locked my bootloader. Now my phone will only turn on and turns off for around 20 seconds. I can't perform fastboot, recovery mode, or open my device. I did some research and found that the only way to restore my device from its state is using edl mode(which I don't know how to use). I follow some tutorials about edl and I was able to make my device appear as "QUALCOMM HS-USB QDLoader 9008" and doesn't know what to do next.
Can I still be able to revive my device without going to a repair shop? And if possible, can you guide me?
Any answers will be appreciated!
To flash device in EDL mode you need to use msm tool then flash your stock ROM.
You need proper driver to use msm tool with your device while in EDL mode.
If you're not sure what you're doing then just give it to a professional.
Goodluck.
I brick realme 5 last year and I give it to repairing shop they opened whole parts and fixed why how that happens?
SAAAAAMMMEE Problem !! did you find a fix ?
Hello XDA Members,
Please help me i have hard bricked oneplus 8 IN2017 Tmobile while installing Custom pixel Experience ROM
and now MSM tool Unbrick tool not working its shows download complete but phone is not booting after showing oneplus logo phone goes to EDL mode.
also i am not able to flash stock fastboot rom because bootloader is locked. Please help me how to unbrick this phone
Try MSM again, on a different PC and with a different USB cable *if* you can.
Aside from that contact OnePlus.
Was this your first time using MS download tool? Have you succesfully flashed to stock with MSM before?
yes i have used msm many times and tried on different PCs nothing is working
msm tool shows successfully download complete and now i am receiving this error (PIC attached)
i think i have messed up partitions.
I have a hard bricked OP9 and have tried alot of different guides from here or other ressources.
The problem is somewhere in the process something is not supported and the how to dies there.
MSM download tool prompts that says "Packed image not exists!"
OP9 LE2113 version (EU Version i guess)
Phone is black screen and can not be detected through ADB or fastboot. Either through the Qualcomm HS-USB QDloader 9008 Drivers.
Before it bricked it was unlocked (bootloader) Not sure it is anymore
Can someone send me a link or guide that can guide me the right direction?
Try the Oneplus 9 Pro India recovery tool. I know it doesnt make sense, but its the only thing that has worked for many, including myself and I have a OP9 5G North America.
Once recovered, the OS will boot but buggy. You can then restore to correct image via twrp full zip
Ill try that this evening, ill let u know ill turn out.
I typically run into sahara connection because i dont have connection through ADB of fastboot
#gorilla p
Try the Oneplus 9 Pro India recovery tool. I know it doesnt make sense, but its the only thing that has worked for many, including myself and I have a OP9 5G North America.
Once recovered, the OS will boot but buggy. You can then restore to correct image via twrp full zip
Click to expand...
Click to collapse
i have used this link
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/ India version
And at the moment it is booting.
Unticked reboot and SHA check, This is indeed a good day !
Ive got a working phone again,
I will mark this thread as solved
Hi all,
My OP8T got stuck at fastboot screen ,i tried several ways from msm tool finally found that all fastboot file available in the net was for kebab and mine is kona. So the msm tool returns "param preload" with "device not match image" error.While searching more about the difference found that kebab comes with 855qc and lpdram4 but kona comes with 865qc and lpdram5. Im now stuck n fastboot screen more than a week. Can anyone guide me or point me for this device fasboot rom??? Or else how to recover fom this? Need urgent help.
Arunraj90 said:
Hi all,
My OP8T got stuck at fastboot screen ,i tried several ways from msm tool finally found that all fastboot file available in the net was for kebab and mine is kona. So the msm tool returns "param preload" with "device not match image" error.While searching more about the difference found that kebab comes with 855qc and lpdram4 but kona comes with 865qc and lpdram5. Im now stuck n fastboot screen more than a week. Can anyone guide me or point me for this device fasboot rom??? Or else how to recover fom this? Need urgent help.
Click to expand...
Click to collapse
Does it connects to a PC?
If it does type fastboot reboot edl
It connects to PC thats why its returning this error na, and in port it shows qualcom 9008. All drivers were installed corretly . If kona oneplus8T fastboot vailable can someone share.
Arunraj90 said:
Hi all,
My OP8T got stuck at fastboot screen ,i tried several ways from msm tool finally found that all fastboot file available in the net was for kebab and mine is kona. So the msm tool returns "param preload" with "device not match image" error.While searching more about the difference found that kebab comes with 855qc and lpdram4 but kona comes with 865qc and lpdram5. Im now stuck n fastboot screen more than a week. Can anyone guide me or point me for this device fasboot rom??? Or else how to recover fom this? Need urgent help.
Click to expand...
Click to collapse
The OnePlus 8T code name is kebab, but you won't find that name on the phone itself. But it's used in LineageOS and in custom rom/recovery builds.
The SoC of the 8T is called kona and you'll see this on the bootloader screen and in some system properties like ro.product.board.
The 8T has a Snapdragon 865 5G chipset.
Earlier versions of the 8T used DDR4 storage, newer ones use DDR5.
I've found that l often have to reinstall drivers for the 8T on my PC when things go wrong. So if your PC isn't properly recognising your phone, it may be helpful to reinstall the appropriate driver.
And one more point: don't post the same question in multiple places. See rule "5. Create a thread topic or post a message only once" in https://forum.xda-developers.com/t/xda-developers-forum-rules.4200559/
Device name in ports shows correctly. Msmdownloader also detecting after preprocessing returns with "Device not match image". Tried EU IN O2 roms, but same error occurs. o if anyone knows the exact problem kindly help. And also kindly share working driver for one plus 8T for msm downloader, so that i can check again.
Arunraj90 said:
Hi all,
My OP8T got stuck at fastboot screen ,i tried several ways from msm tool finally found that all fastboot file available in the net was for kebab and mine is kona. So the msm tool returns "param preload" with "device not match image" error.While searching more about the difference found that kebab comes with 855qc and lpdram4 but kona comes with 865qc and lpdram5. Im now stuck n fastboot screen more than a week. Can anyone guide me or point me for this device fasboot rom??? Or else how to recover fom this? Need urgent help.
Click to expand...
Click to collapse
Change the data cable and install drivers manually again L2 drivers try on different USB port
jahanzaiblohani said:
Change the data cable and install drivers manually again L2 drivers try on different USB port
Click to expand...
Click to collapse
Tried original cable, Ambrane brand cable, Samsung cable. Can you share me the drivers? What is L2 drivers?
jahanzaiblohani said:
Change the data cable and install drivers manually again L2 drivers try on different USB port
Click to expand...
Click to collapse
Tried original cable , samsung cable, and one 3rd party branded cable no use. Can you share me the driver? What is L2 drivers?
Here is the log file of msmdownloader. This is the latest one. Can anyone find what's the problem?
Arunraj90 said:
Tried original cable , samsung cable, and one 3rd party branded cable no use. Can you share me the driver? What is L2 drivers?
Click to expand...
Click to collapse
I got the QCOM driver I use from here: https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
And the one I downloaded is shown in the attached screenshot. I used that one because it's newer than the bottom one and is for 64-bit Windows.
So i tried to flash some firmware for a custom rom with enhanced fastboot. afterwards the phone booted into EDL mode and only EDL mode. i cant get bootloader, fastboot, recovery, or even system boot. before when this has happened msm tool worked well, but now ive tried 4 diff msm tool repacks, 2 diff versions of QFIL. MSM tool gets stuck on "start download firehose binary". then errors out to "sahara communication failed". QFIL errors to "qdssloader fail" or "924 sahara protocol error" and " qsahara server fail". the github edl utility reports "sahara in unknown mode, resetting". ive tried many cmd utilities, python utilities, qualcomm utilities, etc. idk if its completely gone or if there is a way to save it such as switching boot slots without fastboot? i have tried the EDL python utility and it says process completed on boot slot switching but still the same EDL only boot and unresponsive flashing attempts. i have tried like 30 different methods and 2 OSes to try and remedy this issue. i also have telegram and discord for one on one help: @rivapeeva riva!#0451
Have you tried the Indian MSM tool? I thought I was boned when I was messing with my phone a couple of weeks ago, and that was the only thing that worked for me.
riva! said:
So i tried to flash some firmware for a custom rom with enhanced fastboot. afterwards the phone booted into EDL mode and only EDL mode. i cant get bootloader, fastboot, recovery, or even system boot. before when this has happened msm tool worked well, but now ive tried 4 diff msm tool repacks, 2 diff versions of QFIL. MSM tool gets stuck on "start download firehose binary". then errors out to "sahara communication failed". QFIL errors to "qdssloader fail" or "924 sahara protocol error" and " qsahara server fail". the github edl utility reports "sahara in unknown mode, resetting". ive tried many cmd utilities, python utilities, qualcomm utilities, etc. idk if its completely gone or if there is a way to save it such as switching boot slots without fastboot? i have tried the EDL python utility and it says process completed on boot slot switching but still the same EDL only boot and unresponsive flashing attempts. i have tried like 30 different methods and 2 OSes to try and remedy this issue. i also have telegram and discord for one on one help: @rivapeeva riva!#0451
Click to expand...
Click to collapse
Are you TMobile or global 9?
Frosthaxx said:
Are you TMobile or global 9?
Click to expand...
Click to collapse
tmobile
posar said:
Have you tried the Indian MSM tool? I thought I was boned when I was messing with my phone a couple of weeks ago, and that was the only thing that worked for me.
Click to expand...
Click to collapse
i tried the UE tool, the indian tool, the na tool, the tmobile tool, and the conversion tool.
riva! said:
i tried the UE tool, the indian tool, the na tool, the tmobile tool, and the conversion tool.
Click to expand...
Click to collapse
Indian msm tool works on lite Firehose. Then use TMobile India mod and you can from there do what you need to do. Caution however. Doing the Indian trick makes your bootloader to the Indian bootloader but all functions will still work. You just can't use normal msms anymore
Unfortunately the bricking your describing is what happened to me because I goofed something. But I was able to get back using this to TMobile India after Indian. Then using the bootloader unlock guide in TMobile.a few update scenarios, then eventually evolution x. Unless someone has a better way there's not much written about this situation. I had to figure it out myself
IF ANYONE needs info on how i managed to fix this, please dm me or add my socials. If you flashed the wrong xbl/xbl_config files and now your sahara/firehose doesnt work, feel free to reach out. it took me 4 days straight of surfing and downloading and trial and error.
Unfortunately I don't think my issue can be fixed. There isn't anything specifically on fixing Indian region bootloader. Once that's done I think it's sol but it still works normal. I had to however because my brick also wasn't reading the USB either. It was a very odd situation. And I've modded and given advice on multiple phones. I'm glad you got yours working though. Doesn't bother me though
Phone works and the India mod get me back where needed. But others that haven't flashed the Indian msm tool could benefit from your find