Hello all
I've a S4 mini rooted twrp installed. running touchwiz based custom rom from a long time.
day b4 yesterday i found it s.off when i turned it on. it stucked on SAMSUNG LOGO.
then i boot into recovery mode its twrp installed, there i saw internal memory 0MB. and in the mean time it was not taking charging.
and now.. it doesn't turn on, charge, or anything. If i plug it into a pc I get a sound from Windows 10 saying the USB device has been connected but nothing from the S4 mini itself.
any help?
inder23 said:
Hello all
I've a S4 mini rooted twrp installed. running touchwiz based custom rom from a long time.
day b4 yesterday i found it s.off when i turned it on. it stucked on SAMSUNG LOGO.
then i boot into recovery mode its twrp installed, there i saw internal memory 0MB. and in the mean time it was not taking charging.
and now.. it doesn't turn on, charge, or anything. If i plug it into a pc I get a sound from Windows 10 saying the USB device has been connected but nothing from the S4 mini itself.
any help?
Click to expand...
Click to collapse
i m getting sound of connecting my s4 mini to pc thats all.... plz any dev look in to this matter
inder23 said:
i m getting sound of connecting my s4 mini to pc thats all.... plz any dev look in to this matter
Click to expand...
Click to collapse
I think 0Mb suggests it was originally a corrupted partition as you were able to use TWRP to see 0Mb. Which flashing stock might have fixed.
But now it won't charge or boot might suggest something worse like failed hardware or hard brick.
But perhaps, as windows is seeing it (I forget now if Windows will detect usb on bricked phone, as luckily I've never had this), it may just be that you have run the battery down too low so now it won't recharge.
IronRoo said:
I think 0Mb suggests it was originally a corrupted partition as you were able to use TWRP to see 0Mb. Which flashing stock might have fixed.
But now it won't charge or boot might suggest something worse like failed hardware or hard brick.
But perhaps, as windows is seeing it (I forget now if Windows will detect usb on bricked phone, as luckily I've never had this), it may just be that you have run the battery down too low so now it won't recharge.
Click to expand...
Click to collapse
i hv tried a [plug n charge] charger to charge my battery,after all this my phone wont boot or nothing happens but just to b very sure, for now i need to arrange fully charged battery, then i ll update the same...
thank u very much 4 replying...
Related
Hey,
since two days i experience some serious problems with my Galaxy W, dont know if its bricked or not.
I have flashed CM 10.1 and the newest Clockworkmod recovery, after that i was able to charge my device and connect the device as mass storage with my laptop. But this was just possible for ONE time.
Since then, i havent been able to charge it nor to connect it with my laptop. Funny thing is that my brother wasnt able to charge the battery in his Galaxy W, but i was able to charge and connect with his battery, but again just for ONE time (too bad that i disconnected before flashing the stock rom). When i try to connect my device with the charger, it just starts CM but wont show the charging symbol nor would charge once loaded CM.
Do you guys have any idea what has happened to my device?
So is there any chance to get the stock recovery and Rom back on my phone if i cant use odin or adb? I dont think that i can send it in for warranty under these conditions.
A solution might be buying a new battery so that i can connect it for one time to odin to flash the stock recovery...
sdfee said:
Hey,
since two days i experience some serious problems with my Galaxy W, dont know if its bricked or not.
I have flashed CM 10.1 and the newest Clockworkmod recovery, after that i was able to charge my device and connect the device as mass storage with my laptop. But this was just possible for ONE time.
Since then, i havent been able to charge it nor to connect it with my laptop. Funny thing is that my brother wasnt able to charge the battery in his Galaxy W, but i was able to charge and connect with his battery, but again just for ONE time (too bad that i disconnected before flashing the stock rom). When i try to connect my device with the charger, it just starts CM but wont show the charging symbol nor would charge once loaded CM.
Do you guys have any idea what has happened to my device?
So is there any chance to get the stock recovery and Rom back on my phone if i cant use odin or adb? I dont think that i can send it in for warranty under these conditions.
A solution might be buying a new battery so that i can connect it for one time to odin to flash the stock recovery...
Click to expand...
Click to collapse
Your usb driver migh got corrupted.
This happened to a friend with his S2 after ubgrading his rom via OTA. He also coudn´t connect via USB nor charge his phone. Funny thing was I could charge his phone at my usb connection, but not with my charger. Lucky him it was Samsung stock rom, so Samsungs Service Center reflashed his rom and so fixed this issue. They also told him his usb drivers got corrupted during the ubdate via OTA.
What you can try is for example to download CM9, put in on your SDCard and flash it from there. If that doesn´t help try reflashing CWM.
Hi guys.
One of my friends recently gave me his bricked galaxy s4 mini. The phone doesn't turn on and when I plug it in to my laptop it comes up as Qualcomm, Inc. Gobi Wireless Modem (QDL mode) . I've tried to fix it using qdload.pl and QPST but none of them worked.
Is there any way to restore the device without jtaging it ?? I have another working gs4 mini if that helps.
Download odin and a firmware from sammobile. Then do the steps showing on the website and done.
Han5ixix1 said:
Download odin and a firmware from sammobile. Then do the steps showing on the website and done.
Click to expand...
Click to collapse
it doesn't go in to download mode, it's a hard brick
http://forum.xda-developers.com/showthread.php?t=2625628
http://forum.xda-developers.com/galaxy-s4-mini/help/debrick-image-galasxy-s4-mini-t3014728
Try this
Btw: How did he manage to brick his device?
s4 mini flashed wrong twrp
I flashed wrong twrp and phone got bricked . I connect it to pc and it recognise then disconnects
I can't flash my S4 mini, Odin blocks on this screen http€://i64.tinypic.com/m7b76f.jpg (remove the "€")
ab de said:
I flashed wrong twrp and phone got bricked . I connect it to pc and it recognise then disconnects
Click to expand...
Click to collapse
have you been able to fix your phone. got a similar case over here.. help
Eskay_Sedem said:
have you been able to fix your phone. got a similar case over here.. help
Click to expand...
Click to collapse
The same thing just happened to my working S4 mini. I put it on charge yesterday and it switched off after 5 minutes and never switched back on. I don't think there's any way to fix it as the EMMC is most likely dead :crying:
Patrick4 said:
The same thing just happened to my working S4 mini. I put it on charge yesterday and it switched off after 5 minutes and never switched back on. I don't think there's any way to fix it as the EMMC is most likely dead :crying:
Click to expand...
Click to collapse
Brickbug much?
=/
Same thing happenned to me. I installed TWRP and the phone just died. Now it turns on and everything but is stuck in bootloop. Main issue is, my recovery just shows TWRP symbol and no options to be able to flash a new rom or a new recovery.
Odin flashes stuff such as cwm, stock rom, but none of these seem to actually have any impact in my phone behaviour.
I think it's just dead yet I just don't want to accept it, I'm trying everything I can to make it work again.
PS: I hate myself the day I decided to install a trwp
Guys I need your help
I don't know what happened to my Note II phone.
Only thing I've done was to root it. I'm still using the same O.S. I haven't tried flashing something on it before
Here's what happened.
I was just chillin, chatting on Messenger when all of a sudden, the phone LED indicator flashes but it doesn't unlock. then the phone died and when i was trying to charge it, there was only a charge icon on the screen but it wasn't moving.
The next day i bought a new battery and now what happened was that it wasn't going through the Galaxy Note II screen (bootloop perhaps?) i tried going through recovery mode -- dead android icon then it shuts down. and i was still able to access download mode
before i was able to follow the soft brick recovery mode, all of a sudden it doesn't even go to recovery/download mode anymore
LED indicator does not turn on for charging even if i plug it into the charger.
What do i need to do? i don't have JTAG as an option
I read somewhere that I you can boot hardbricked phones using an SD card by doing something about partition stuff there will that work? :laugh::laugh::laugh: hope to get some replies from you guys :good::good:
Have you tried using a 2.0 amp charger and letting the phone charge for a few hours?
audit13 said:
Have you tried using a 2.0 amp charger and letting the phone charge for a few hours?
Click to expand...
Click to collapse
no i haven't tho the battery has a charge (i tested it on a different note 2 i booted)
phone doesn't go into recovery mode anymore. anything i can do to revive it? btw sorry for the late reply
Not much you can do if the phone can't get into recovery mode.
When connected to a computer, do any devices appear in the device manager?
I am also facing the same problem,,,,..not entering to recovery mode .......when trying to install stock firmware through odin (using windows 10)it says nand write and next step fail....i didn't even root my phone.....please friends help me....Thanks in advance....and yes it enters to download mode
Are you using the original Samsung USB cable? Tried other USB cables and all USB ports on the computer? What is the specific Odin error?
audit13 said:
Are you using the original Samsung USB cable? Tried other USB cables and all USB ports on the computer? What is the specific Odin error?
Click to expand...
Click to collapse
i don't have the samsung cable,,,,I was using the sony data cable with cylinder shapes at the ends
yes,i tried all the ports
odin says FAIL! after the Nand write start
What is the error message in Odin? You could also post the log from the log window.
my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
LumberjackZac said:
my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
Click to expand...
Click to collapse
Can you still boot into TWRP?
dhplap said:
Can you still boot into TWRP?
Click to expand...
Click to collapse
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
LumberjackZac said:
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
Click to expand...
Click to collapse
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
That is awesome. Been looking at Note 4's on ebay because.... not looking good
ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
Hey buddy. I've been reading that qhsusb_bulk is a hard brick, possible fried bootloader. But I guess if you can make this unbrick.img on to a sdcard it may work. I'm scratching my head on what files go into this unbrick.img and if I can make it myself. Any ideas
I have samsung s4 mini that suddenly won't turn on. The phone was not rooted, neither had custom recovery installed or custom rom. It was working fine and one day suddenly won't turn on. If i connect it with usb cable to pc in device manager, under 'other devices' it's shown as QHSUSB_DLOAD.
Any idea what happened to the phone and can it be fixed?
Peter770 said:
I have samsung s4 mini that suddenly won't turn on. The phone was not rooted, neither had custom recovery installed or custom rom. It was working fine and one day suddenly won't turn on. If i connect it with usb cable to pc in device manager, under 'other devices' it's shown as QHSUSB_DLOAD.
Any idea what happened to the phone and can it be fixed?
Click to expand...
Click to collapse
sadly, welcome to the club, the emmc memory chip is probably dead, but if you are lucky it's just corrupted (thought it might just be your battery). If corrupted you can try botching it with a debrick file put onto a 16Gig or 32Gig & boat from that, refer to the hard debrick thread. You need one that matches your bootloader (BL) rev so either a debrick image from an android 4.4.2 or 4.4.3 ( BL v1 & BL v2 respectively).
You might have to try the whole procedure multiple times, some report, but it never worked for me.
A repair shop may also be able to flash new system if memory chip is OK.
Else you can order a new motherboard, but you may decide a new phone is better to spend your money on
Yes, i think new phone will be better solution.
Hi, i can say for sure that the mobile's eMMC memory is dead. I already had that problem with another S4 Mini, and that was the reason. There is no fix for that (unless you want to send it to replace that memory, and would be more expensive than buying a new motherboard for that device)