Hello
My galaxy (i9192) just went dead. No custom roms or anything. It was working ok until battery discharged. Now it has 2,8V and wont charge.
Ive tried debrick images found here but none of them worked. Only "life sign" form this phone is QHSUSB device that showed up as Qualcomm HS-USB QDLoader 9008 after drivers installation.
Do you have any suggestions what else i can try?
Thanks in advance
Maybe your emmc get corrupted
Just like that?
BTW: if ive got debrick img flashed on the sd card and battery is discharged how should i turn it on? Using wall charger or connect it to pc? Should i press some buttons combination or it should boot itself automatically?
If emmc is corrupted and phone finds boot on sd card shouldn't it boot anyway?
Hey Guys,
I've a Samsung Galaxy S4 Mini (GT-I9192). It stopped working mid-day all of the sudden while it wasn't in use. The phone is just showing a black screen, & pressing the power button, it doesn't respond. The phone also doesn't respond when I try entering the download or recovery modes. When I connected the phone to the PC, it was identified as "Qualcomm HS-USB QDLoader 9008", & looking up on the internet for what does this mean, I found that it means that phone is bricked.
I never rooted this phone, & I tried to write two I9192 debrick images (One at a time of course ) on an external SD card using Win32DiskImager-0.9.5. However, turning on the phone with any of the two debrick images, the phone shows the following lines exactly, & no further progress takes place:
BOOT RECOVERY MODE
CHECK BOOT PARTITONS..
COPY FROM T-FLAH..
BOOT RECOVERY..
WRITE 139008 sectors..
I couldn't find a solution for this issue on the internet. So, any idea what is happening here & how can I solve this problem ??
Many thanks in advance
diaaamin said:
Hey Guys,
I've a Samsung Galaxy S4 Mini (GT-I9192). It stopped working mid-day all of the sudden while it wasn't in use. The phone is just showing a black screen, & pressing the power button, it doesn't respond. The phone also doesn't respond when I try entering the download or recovery modes. When I connected the phone to the PC, it was identified as "Qualcomm HS-USB QDLoader 9008", & looking up on the internet for what does this mean, I found that it means that phone is bricked.
I never rooted this phone, & I tried to write two I9192 debrick images (One at a time of course ) on an external SD card using Win32DiskImager-0.9.5. However, turning on the phone with any of the two debrick images, the phone shows the following lines exactly, & no further progress takes place:
BOOT RECOVERY MODE
CHECK BOOT PARTITONS..
COPY FROM T-FLAH..
BOOT RECOVERY..
WRITE 139008 sectors..
I couldn't find a solution for this issue on the internet. So, any idea what is happening here & how can I solve this problem ??
Many thanks in advance
Click to expand...
Click to collapse
My phone (Samsung Galaxy S4 mini Duos GT-I9192) is with the same problem, since 2016 October!!. But I know what happened. It was a virus!: In a day, when I turned on my wifi, an unexpected download started . . . , after about 5 seconds, several app's began stopping uninterruptedly, followed by message asking "OK". So, I forced the phone to turn off; waited some time, but when I pressed the power button, nothing happened and it remains like this until now! I have tried all of the things possible by pressing combination of buttons, but it is really hard bricked!!. I just hadn't courage to use any kind of (de/un)brick image yet, like you. I'm continuously researching in the internet and trying to learn how to solve this problem in a secure way. I have found something relating to unbrick qualcomm mobiles using QFIL, but we have to use other kind of archives other than thouse from GT-I9192 original rom, which made me with doubt if it will function.
If somebody understand better than us about it, please help us!
Thanks.
villaovb said:
My phone (Samsung Galaxy S4 mini Duos GT-I9192) is with the same problem, since 2016 October!!. But I know what happened. It was a virus!: In a day, when I turned on my wifi, an unexpected download started . . . , after about 5 seconds, several app's began stopping uninterruptedly, followed by message asking "OK". So, I forced the phone to turn off; waited some time, but when I pressed the power button, nothing happened and it remains like this until now! I have tried all of the things possible by pressing combination of buttons, but it is really hard bricked!!. I just hadn't courage to use any kind of (de/un)brick image yet, like you. I'm continuously researching in the internet and trying to learn how to solve this problem in a secure way. I have found something relating to unbrick qualcomm mobiles using QFIL, but we have to use other kind of archives other than thouse from GT-I9192 original rom, which made me with doubt if it will function.
If somebody understand better than us about it, please help us!
Thanks.
Click to expand...
Click to collapse
Qfil doesn't work with Samsung as far as I know. Even if it did you would have to have the files for your exact phone model.
But I'm going to continue researching. . .
Thank you.
hey villaovb. did you find anything or this problem?
So I have this Sprint Note 4. Haven't used it in forever since I got the Note 5. Anyway, so when I try to turn it on, it doesn't turn on, and the charging indicator doesn't turn on when plugged in. When I plug it in my PC it shows up as "Qualcomm HS-USB QDLoader 9008 (COM10)".... I read somewhere that apparently it's hard bricked and I need a debrick file to get it working again. Now I found some random files somewhere, so I decided to put them on the SD card. The phone vibrated, but didn't do anything, now it wont do anything anymore..
Can someone guide me and/or provide me with the proper debrick files for my Sprint Note 4?
Hi guys,
I am not sure what exactly happened. I was sitting around and listening to some music when my old Nexus 5X suddenly rebooted and stayed blank.
First guess - Battery. But that turned out to be quite wrong as I had charged it over night. Tried to get into fastboot mode or recovery mode; After the logo showing up and my beloved "This device isn't trusted" sign the screen went completely blank and that was the last sign of life. As it's got an USB port, I hooked the device up to a computer, found it to identify as "Qualcomm HS-USB QDLoader 9008".
Some research showed me that this is some kind of download mode, in terms of 'nothing works anymore' and you'd have to get your hands really dirty here to get at least somewhere.
So my educated guess would be bad memory or some corrupted filesystem and I'd have to reinitialize the phone to be able to fastboot or anything.
Tools already looked at:
LGUP - No joy; Device not found as this one requires something like a basic recovery mode which seems to be broken here
boarddiag - I was able to read from the memory using 'download' using a tot file I found somewhere online.
QPST - Found some prog_emmc_firehose_8992_lite_lge.mbn file, but I lack the patch and raw program files
Any ideas out there getting that bugger alive again?
Cheers
Rei
This is not a sign of download mode, your device hardbricked. As you have the firehose (I don't know if should work this) I found from another thread there the other files for QPST. I didn't tried that because this was released after I send my 5x to service (yes, for second time) due to hardbrick . https://drive.google.com/file/d/0B5EP5AzZNQxPcE52QWw2VloteUU/view
Hello all.
This phone [GT-I9195, S4 Mini] died about 4 years ago and I've always thought it was hardware related. The other day I found the phone again and i was hoping to pull some data off. I plugged it into my pc and came across the "qhsusb_dload" which turned out to be quite common. I installed a driver and it turned into qualcomm HS-USB QDLOADER 9008. I came across a unbrick IMG on this forum and used it on a micro sd which to my surprise actually made the phone vibrate and turn on the display. The following text appeared on the display:
https://imgur.com/PgzjwkP
Now I am at a complete loss on what to do next. Does mmc_read failed indicate a hardware failure?
Some help would be greatly appreciated. If im leaving required information out please let me know and I'll try to provide.
This was the debrick img. that was used
I have the same problem. The fact is that the memory has so many bad sectors that it has switched to read-only mode. And to launch you need to write to sectors, but the phone cannot write data.