• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root HELP!!! hard bricked one sv k2_cl computer reconigze the phone as Qualcomm HS-USB QDLoader 9008

Im having this same problem but mine was cause by flashing the stock recovery using this method in terminal emulator because my computer doesnt pick up my phone in fastboot.

su

dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21

It's possible you made a typo when typing it in the terminal - the command you are sharing right now is absolutely correct, but you must be S-Off for it to work. Try flashing your boot.img to your boot partition to insure you didn't make a typo and accidently installed the recovery to your boot partition. Our boot partition is mmcblk0p20.
 
  • Like
Reactions: JohanToGood
Upvote 0
It's possible you made a typo when typing it in the terminal - the command you are sharing right now is absolutely correct, but you must be S-Off for it to work. Try flashing your boot.img to your boot partition to insure you didn't make a typo and accidently installed the recovery to your boot partition. Our boot partition is mmcblk0p20.

I would flash my boot.img but i cant get the phone on and if i plug it in to the computer it shows up as Qualcomm HS-USB QDLoader 9008
 
Upvote 0
I would flash my boot.img but i cant get the phone on and if i plug it in to the computer it shows up as Qualcomm HS-USB QDLoader 9008

Sounds like you managed to hard brick your device. Either you flashed a wrong image (which I highly doubt is the probable cause here) or you mistakenly wrote to another partition by accident and pretty much borked your device. Been reading up on what pops up for you and it seems it isn't promising to fix your device. Some devices (very small list) seem to have support for fixing this issue, but since I am personally unfamiliar with this I cannot help, and I don't think there is anyone else on here with this device that can either (this includes over on XDA as well). You may just need to do some extensive research on how other devices overcame the problem and adapt their solution to your own device. Some development work may be involved for you though. Otherwise, your phone is merely a paperweight right now.

Code:
 u0_a71@android:/ $ cat /proc/emmc
dev:        size     erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p35: 54fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 0dfffe00 00000200 "cache"
mmcblk0p37: 49fffe00 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p38: 1097fe000 00000200 "fat"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p32: 01900000 00000200 "carrier"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p31: 00040000 00000200 "skylink"
mmcblk0p32: 01900000 00000200 "carrier"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 04729a00 00000200 "reserve"
u0_a71@android:/ $
 
  • Like
Reactions: JohanToGood
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones