I've been having a problem with an S4 Mini recently. A few weeks ago, it stopped booting whatsoever. I tried the "debrick.img" method but it only said that there was an error flashing to the eMMC. At that point in time, I was assuming it had a dead eMMC and I had to buy a new motherboard. I brung it out again a few hours ago and it booted, except it is stuck in a bootloop. If I try to enter recovery mode, it says "BOOTING RECOVERY MODE..." in the top left corner, then says "No command.". After a few seconds it then reboots.
I have attempted using Odin to flash TWRP but the same error occurs with the device, like it wasn't even flashed with TWRP. I did also try to flash a stock ROM, but to no avail. It's just stuck in this boot loop.
The Odin logs say that the flash was successful, so I don't see how it could be failing. Right now, it is sitting right next to me, vibrating, showing the manufacturers screen and then rebooting. All I can assume at this point is the eMMC is dead, and I should buy a new motherboard.
If there is any fix to it, I would really appreciate you could tell me so I can attempt to get it working again.
UPDATE: I just attempted to take the battery out to try and reflash the Stock ROM but now, it's showing the QHSUSB_DLOAD driver. This happened the last time and a friend told me that this is a dead eMMC and the device is basically now a brick. Hopefully this is just temporary and the device decides to be nice and function again. Fingers crossed!
UPDATE 2: I was doing some research and something appeared in Device Manager called "Qualcomm HS-USB QDLoader 9008 (COM5)". I googled the driver and apparently it is a sign of a bricked Qualcomm Snapdragon. I'm going to try the unbricking steps and hope that this is the problem, and I don't need to buy a new mainboard.
I can only say good luck man, hope you fix it without changing motherboard.
Funey__ said:
I've been having a problem with an S4 Mini recently. A few weeks ago, it stopped booting whatsoever. I tried the "debrick.img" method but it only said that there was an error flashing to the eMMC. At that point in time, I was assuming it had a dead eMMC and I had to buy a new motherboard. I brung it out again a few hours ago and it booted, except it is stuck in a bootloop. If I try to enter recovery mode, it says "BOOTING RECOVERY MODE..." in the top left corner, then says "No command.". After a few seconds it then reboots.
I have attempted using Odin to flash TWRP but the same error occurs with the device, like it wasn't even flashed with TWRP. I did also try to flash a stock ROM, but to no avail. It's just stuck in this boot loop.
The Odin logs say that the flash was successful, so I don't see how it could be failing. Right now, it is sitting right next to me, vibrating, showing the manufacturers screen and then rebooting. All I can assume at this point is the eMMC is dead, and I should buy a new motherboard.
If there is any fix to it, I would really appreciate you could tell me so I can attempt to get it working again.
UPDATE: I just attempted to take the battery out to try and reflash the Stock ROM but now, it's showing the QHSUSB_DLOAD driver. This happened the last time and a friend told me that this is a dead eMMC and the device is basically now a brick. Hopefully this is just temporary and the device decides to be nice and function again. Fingers crossed!
UPDATE 2: I was doing some research and something appeared in Device Manager called "Qualcomm HS-USB QDLoader 9008 (COM5)". I googled the driver and apparently it is a sign of a bricked Qualcomm Snapdragon. I'm going to try the unbricking steps and hope that this is the problem, and I don't need to buy a new mainboard.
Click to expand...
Click to collapse
Did you solve it? I'm having the same problem
Related
I've tried searching and there doesn't seem to be a solution to this problem for this device.
Yesterday I was flashing ROMs, namely AICP, but I accidentally pressed Reboot to Bootloader in CWM. I got stuck in bootloop after that and it kept returning to recovery. I google'd for a solution and found this(androidforums-.-com-/esteem-all-things-root/478814-how-get-out-clockworkmod-recovery-bootloop.html), which I downloaded and foolishly flashed (devices unsimilar). Flash is successful, and I reboot my phone.
It now will not show the LG splash screen, nor will it enter Download Mode. When connecting the device via USB, it does not seem to add a COM port on the computer. What it does do is try to install a driver named QHSUSB_DLOAD which fails to install.
Could someone please help me solve this problem? Thanks..
dylanraga said:
I've tried searching and there doesn't seem to be a solution to this problem for this device.
Yesterday I was flashing ROMs, namely AICP, but I accidentally pressed Reboot to Bootloader in CWM. I got stuck in bootloop after that and it kept returning to recovery. I google'd for a solution and found this(androidforums-.-com-/esteem-all-things-root/478814-how-get-out-clockworkmod-recovery-bootloop.html), which I downloaded and foolishly flashed (devices unsimilar). Flash is successful, and I reboot my phone.
It now will not show the LG splash screen, nor will it enter Download Mode. When connecting the device via USB, it does not seem to add a COM port on the computer. What it does do is try to install a driver named QHSUSB_DLOAD which fails to install.
Could someone please help me solve this problem? Thanks..
Click to expand...
Click to collapse
Hate to say two things to you bro:
1) You didn't search very hard, because there was a related thread on page 3 with "QHSUSB_DLOAD" in the title
http://forum.xda-developers.com/showthread.php?t=2781522
I forgive though, but just letting you know.
2) You're screwed. The phone is hard bricked. No way to get it back to life.
How do I know? Well, look who's the creator of the thread just linked to.
Read the entire thread. It's not very long.
PS: PM me if your phone is still under warranty and you want advice on how to get it replaced. If you still aren't under warranty, then you're doubly screwed.
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
GoonReb0rn said:
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
Click to expand...
Click to collapse
Update: I spent the past two days trying to solve this and I'm at a standstill in progress. It seems that my phone was one that suffered SDS with a corrupt eMMC chip so I've lost both my firmware and recovery but I can still get into Download mode. It also seems like I have lost my PIT table and I am just completely unable to flash the PIT file back to the phone for some reason. Does anyone have any ideas on how I could just factory reset my phone or reinstall my partition table so that i can get a simple recovery installed? Please help
Exact same issue!
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
dkinniburgh said:
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
Click to expand...
Click to collapse
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
GoonReb0rn said:
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
Click to expand...
Click to collapse
I was lucky having most of my info already backed up. I also had just upgraded another line, so I had a new phone to work with. It just sucks having to switch everything over to a new phone, reloading all the apps etc.
Hello,
My gf s4 mini is having some strange problems.
First it suddenly shutted down and doesn't give any signs of live, so I maked debrick sdcard and it booted, showing that there is something wrong with mmc.
Tried to flash with odin, but it failed... so left it for some time. When i tried another time it booted and showed s4 mini boot logo, so i wanted to flash it with stock firmware.
Progress bar is moving to end, Odin display: PASS! and then it is rebooting and not booting.
I tried booting recovery, and it shows twrp and rebooting about 5sec after showing twrp logo.
So i repeated this process and it still shows twrp logo...
I haven't seen something like this, so there is my question:
Is there something I can do, cause i read lots of threads and nothing works?
I guess it is dead mmc chip, but maybe i'm wrong and there is some solution.
Thanks in advance!
refresh
Maybe you can try jtag. But if your phone's warranty still continues, I recommend you give it Samsung service
Sorry for my bad English
Sent from my GT-I9190 using Tapatalk
Hello !
I'm trying to unbrick the i9195 of a friend.
Basically it was on official stock ROM, and from one day to the next it didn't go past the bootloader, stucking into a bootloop.
When trying to enter recovery, it bootloops and still gets stuck in bootloader.
I can only flash files with ODIN. I tried to flash another Stock ROM, and I tried to flash TWRP recovery. For both tries, I can't boot, whether it's system or recovery.
I don't even know what Android version was installed before it crashed, I guess it doesn't matter. Bootloader displays "V2" so it might be 4.4.2
I've some experience in flashing, Qualcomm HS-USB QDLoader 9008 etc. but this time I think that's beyond me.
Maybe I forgot some steps, so I'm looking for some help or any information... It seems like a faulty hardware for me
Thank you in advance and have a nice day !
Cheers
The mom needed a device and I dug out my ol OP3 (rooted). It was stuck in a boot loop and I decided to flash it back to the original factory settings. But from there on it would never boot into RECOVERY only into FASTBOOT. So with ADB still working I used the many available "Mega Unbrick Guide for A Hard Bricked OnePlus 3". The main problem was it would load and then faced with 3 errors upon trying to boot. Corrupted MD5, error with recovery and something else. I never had a problem with the drivers part and the main hang up was with either using the x64 or the x86 driver. But with no luck neither worked and always showed the same FAIL.
After many hours of no luck, during a load the phone disconnected on its own and the computer showed that something changed and no longer recognized the previous connected device.
Now resulting in no response to any action of any combination of buttons. Please explain how this can happen again, and could possibly be prevented in the future. I have rooted may devices with loads of help from the XDA community and have now experienced my first hard brick..kinda embarrassing when I told the mom she would have a killer device in about an hour resulting in full embarrassment!
After leaving it on the charger for a bit, it still was able to connect to the computer and run yet an UNSUCCESSFUL install with MSM download tool v3.0.
Thanks guys for reading.
@adjday
Try THESE