Help with possible hard brick - Galaxy S 4 Q&A, Help & Troubleshooting

Hi guys i think my galaxy s4 may be hard bricked. i took my phone out of my pocket today to find it completely dead. The phone is rooted and was running jamals 4.3 ge rom. The only explanation i have is that i bumped it in my pocket and it somehow installed the ota update for the google edition phone. very unlucky i know but i cant think of any other explanation apart from hardware failure. When i try to power the phone now i get a flash of green across the screen and the phone vibrates. i then get a solid blue led in the corner. Ive hooked the phone up to the computer and odin recognises it as com5 and blue. ive checked device manager and windows recognises it under portable devices as jussa sam (my phone) i am unable to get the phone into download mode its completely dead apart from a blue led. Any suggestions? ive ordered a usb jig to see if i can force it into download mode. When plugged into the charger the phone is getting very hot.

If the screen goes on, you can repair it.
Put out battery and put it in again.
vol down+home+power button
That must work with odin.
If not try with kies.

My guess is that you have a hardware failure. It's almost impossible to brick it in the way you descriped. You just got unlucky. Nothing you can do that will fix it.

looks like you killed your bootloader. And so the regulation of charching and booting
try kies. if that not works, deinstall the driver from your phone.
restart computer and plug in your phone.
Look what driver will be installed

The OTA would not install on a rooted phone, it would fail during the process and revert back to normal booting.

Convinced its hardware fault nw. Will put it in to Samsung for warranty hoping they won't be able to tell it's rooted. Pic of screen in link http://i105.photobucket.com/albums/m217/justinneumann01/Mobile Uploads/image_zps619f1980.jpg

Related

problem with sgs firmware update

Hey guys I've been watching this forum for a while now and I need some help.
I searched around and found nothing relevant..
I got the latest kies, finally my sgs connected in kies mode, perfect. Popup for update, okay. Now... The first time i did this it showed me some progress bar which was probably something downloading. After that, the phone simply disconnected. Kies didn't show up anything, just that the phone was no longer linked to kies. The phone still showed the mtp application screen. After a few seconds kies shows 'Connecting...' and recognizes the phone again.
The second time it doesn't even get to the progress bar. When I click update, the phone simply vanishes from the kies screen.
I have not applied any lagfixes or anything, haven't rooted my phone.. Actually a few days ago I made a hard reset and everything is smooth. I just want that froyo already, I'm still running eclair.
Please, if you have a solution post it here, or at least point me in the right direction. I'm pretty much a noob when it comes to phones so.. Any help will be appreciated.
I dont know what to say
U already hard reset the phone.
Check with sgs tools what firmware do you have.
In case you have major issues.
Check the three button combo.
Uninstall kies, hard reset and try again.
Maybe is a usb problem .
How is the mount sd working ?
Sent from my GT-I9000 using XDA App
I had a problem just like this and it turned out to be a faulty USB connection. Try a different lead and USB port on the PC first.
Thanks for your replies guys, but unfortunately I still have a problem.
Reinstalled kies, nothing. Hard reset the phone again. Nothing.
Three button combo working perfectly.
In settings, the firmware seems to be 2.1-update1.
Usb problem, I don't think so. The SD card mode works flawlessly. There's one more thing I noticed. When I plug my phone in kies mode, windows also recognizes the phone, showing it up in my computer. The point is that when kies loses link to the phone, windows still finds the phone to be there, e.g. phone disconnects from kies, but not from windows. That's pretty weird..
You guys have any other suggestions..? What is the risk of flashing my phone manually to 2.2? I wanted to avoid that at all cost.
Kies also does not like the phone to be plugged in via any hub. It is best always to plug direct into a system board USB outlet.
Oh forgot to mention. I was indeed plugging the usb cable into a hub, and tried plugging in directly from the motherboard connectors and still no luck.. No idea what to do next.
Might be worth putting the phone into recovery and going to Tools, Emergency firmware recovery.
Well in the 3-button thingy i only have 'reboot system now', 'apply sdcard:update.zip', 'wipe data/factory reset' and 'wipe cache partition'. Halp plox?
Looks like you are left with two routes .
one take phone to service centre
two flash the phone to upgrade .
If flashing i would go the rom kitchen route .
That is only requiring a USB mass storage mode connection to transfer update file to sd card .
jje
I would try it. What are the risks and what happens if something goes wrong? I read somewhere that if I the 3-button combo is working I have nothing to worry about since I can reflash my phone at any given time. Is that true?
To get into recovery it is Home button. DOWN volume and Power on.
You will see a yellow triangle with "DOWNLOADING" Do not turn off the target. When you have this and have opened Kies just plug the USB in and use the recovery option if you can. As with all flashing there is always a risk so do this if you are prepared to accept this.
I've been doing a bit of research and as I saw around the only way you can mess up your flash is simply by disconnecting the cable when you shouldn't. I never actually saw anyone on different forums that have failed flashing so.. That thing pretty much gave me some courage, like hell..
I found a guide which I think would work:
http://samsunggalaxysforums.com/showthread.php/2921-How-to-use-Odin-to-upgrade-to-Froyo-from-Eclair
Do you think this is okay? Also the guy sais we should check *#1234# for PDA, and mine seems to be I9000XWJFB. He said we 'should be on JM1, JM2, JG1, JF1 etc...'. I assume that my phone falls into that category?
If this guide is erroneous please point me in the right direction, if you could.

need help wit sgt-p1010, please!!!!!!!

hey guys is will need some help with this device im not kind of a noobie on this kind of things bcs i been working with several phones, like the veteran xperia10, galaxy ace, motoroi2, etc etc. but never with a tablet
here is what it happens a friend ask me if i can upgrade his sgt-p1010 to a newer version, honeycomb or maybe ics, i´ve read a lot of posts regarding this on how to upgrade it trough odin everything was fine until the reboot of the device, bcs by my mistake i flash a rom of the 7.7" tab and this one is a 7" only now the tab is not turning on, odin is not recognizing it, either samsung kies or the pc. buttons are not responding it wont charge and cant enter to download mode.
I REALLY NEED HELP FROM U GUYS, HOPE U CAN HELP ME
ps. srry for my english :laugh:
This kind of thing can result in the inability to boot which can only be repaired by the use of specific hardware, i.e. this could be a "hard brick". Then again, maybe it can be restored to working order by flashing it again (a "soft brick"). So the very first thing you need to know is, can it get to download mode?
Turn it off, if it's switched on, and charge it for a couple of hours,say four hours. Use the original charger connected to mains. It doesn't matter if it shows anything, or nothing on the screen, let it charge. This is to make sure flashing it won't fail because it doesn't hold a charge.
Now connect it to the PC with the original USB cable. Then after making sure it's switched off, switch it on by pressing the On/Off button, while simultaneously the Volume UP switch. Press them both at the same time, and keep them pressed! If you're lucky you'll get the yellow graphic with the download text. A phone symbol, an !, and a PC symbol is fine too. Even if it doesn't show anything, you may be in download mode, so install the right drivers, and hopefully Odin or Heimdall will recognise is, and will allow you to flash the right ROM.
well i already let it charge for all night long and nothing happens after i perfomed the flashing the screen was totally in black but it doesnt shoes anything i mean the tab was turned on, then apparently batterie dies and after that is not charging. already tried with the heimdall thing but it says that device is not connected.
I think that this is going to be a HARD BRICK
so do u thhink there is another way to solve it?????
or it will be necessary the JTAG stuff???? bcs i dont want to try that it seems that is very difficult to me bcs i dont know nothing about hardware jejejeje
You have installed the Heimdall driver? It's called zadig.exe. Then you have to go to download mode and connect the Tab to the PC with the USB cable. Then Heimdall hopefully will detect the Tab.
If there's no way software will revive the Tab, it's hard bricked and will need hardware to get it working again. There's this guy mobiletechvideos.com who will repair any kind of brick. Basically he uses the JTAG on the board of the Tab and a special box to flash the right ROM to the Tab, even when it's dead. Some here have tried the service, and they say he's quite reliable. Another way is to modify your Tab with Adam Outler's Unbrickable Mod. It's brilliant, you can't soft brick your Tab after that, but it involves soldering very small components on the board of the Tab. The mobiletechvideos guy can do it for you I believe.
Well, I guess you just got a hardbrick .
The only way to fix this problem is go to SAMSUNG SERVICE CENTER.
Sent from my GT-P1000 using xda app-developers app

[Q] Motorola defy black screen with white led

hi all i bought defy about a year ago as a second phone from ebay with cm7 installed.last week i purchase another phone and give my 7 years old daughter. however i reset everything and phone turn old version blur mod then stuck on m logo i download rom and sort the problem.
real problem starts now i try to install cm 9 download all required files wiped the phone and install the rom however it didn't restart stuck on black screen and only white led when connected with usb also didn't connect or recognized by rds lite.I found tread battery wake up from i think was ''mggrager'' or something else finally rds recognized the phone and install another sbf but still stays same as black screen and white.i read so many threats on this side or others and each i installed custom roms without clearing cache
battery replaced with replacement battery also original
all drivers installed
it doesn't respond any buttons or usb connection
rds only with battery jump
please help what to do
I'm having the same problem as you are, i believe... I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport... I take my phone home, not really giving it much importance, and i noticed it would never charge and/or turn on, and that when I connect it to the pc, nothing happened other than the white led coming on.. RSD won't recognized it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
I don't know if i should make a thread of my own.. i think we have the same problem, and i REALLY need my phone back.. so i guess we could just help each other fixing it somehow....
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOLA_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
pasha543 said:
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
Click to expand...
Click to collapse
bump 4 help

S7 Edge is completely Unresponsive after tried Unroot

Last night I tried to unroot my phone as the title says. Everything was going fine, and I installed the stock files on Odin. The video I found on it said to select re.Partition and T.Flash on Odin. I did, and now the phone is unresponsive and my phone doesn't show up on my computer. I can't turn it on or use any button combination to turn it on. If I hold the power button my computer makes a connection sound but doesn't show up. Please help.
Go to device manager and check if it finds it at any name. Sometimes bootloader devices are even found as "bacon sandwich" . Well.. most of the time they will be hidden under like "marshall bootloader" or something totally weird that You would not plug into Your computer (bacon sandwich).
As long as it makes sound it's good. It means that the device isn't 100% dead.
Try holding Odin button combination(5-10 seconds) with the phone being plugged in and see if odin detects it or if Your device manager shows something.
The good thing? Just in case if You really killed Your phone, take it back to Samsung and tell them that You left Your phone to charge over night and in the morning it was dead. They should replace it. (Note 7 battery affair might be helpful)
And future advice. Don't use t.flash nor repartition. Although I think that repartition is safe as long as You use pit file. But t.flash NOPE. Unless I know what certain thing does, I don't touch it.
Just to sum it up.
1. See if Your phone is detected in Device manager
1b. See if You can get it to be detected by using Odin button combination.
2. If not take it to Samsung. They should replace it, because it's completely dead. And there's no way for them to check the knox.
3. Never use t.flash or repartition again.
4. If You need any further help just tell me
Good luck.
What video did you watch? Options only need to be changed when you flash TWRP - you need to untick the Auto Reboot to make TWRP stick, even with auto reboot it flashes ok. So basically OPTIONS of Odin is just when you are in deep... Now your phone is definitely hard bricked and I would recommend just go to your seller and ask for a warranty fix... if they cant boot to dl mode they might not even be able to see if your knox is 0x1.
ProtoDeVNan0 said:
Go to device manager and check if it finds it at any name. Sometimes bootloader devices are even found as "bacon sandwich" . Well.. most of the time they will be hidden under like "marshall bootloader" or something totally weird that You would not plug into Your computer (bacon sandwich).
As long as it makes sound it's good. It means that the device isn't 100% dead.
Try holding Odin button combination(5-10 seconds) with the phone being plugged in and see if odin detects it or if Your device manager shows something.
The good thing? Just in case if You really killed Your phone, take it back to Samsung and tell them that You left Your phone to charge over night and in the morning it was dead. They should replace it. (Note 7 battery affair might be helpful)
And future advice. Don't use t.flash nor repartition. Although I think that repartition is safe as long as You use pit file. But t.flash NOPE. Unless I know what certain thing does, I don't touch it.
Just to sum it up.
1. See if Your phone is detected in Device manager
1b. See if You can get it to be detected by using Odin button combination.
2. If not take it to Samsung. They should replace it, because it's completely dead. And there's no way for them to check the knox.
3. Never use t.flash or repartition again.
4. If You need any further help just tell me
Good luck.
Click to expand...
Click to collapse
I found a UMBus Root Bus Enumerator. I don't know if that's something
Bus enumerators are the USB controllers in Your computer so I don't think it is it. Maybe You could find something like "unknown device" or "unknown descriptor" something like that..
Btw. Did You install Samsung drivers? Sometimes devices aren't visible in device manager until You install proper drivers.
If nothing really works then download Smart Switch and then plug Your phone in. It should find it in like a emergency mode hopefully. And if smart switch doesn't detect anything either then just go to the place where You got the phone and they will replace it.

Bricked phone

Hello, i think my phone is completely dead. Here's what happened : i wanted to go back to a stock ROM so i used MiFlash, but it gave me an error really early after a couple seconds (modem flash error i think) and now it doesn't respond. When i connect it to my PC nothing happens (nothing in device manager). The only sign of "life" is that when the battery is low (i think that's the case), the LED starts flashing RED until the phone runs out of juice. Any ideas? I already tried charging the phone all the way up and then discharging it completely(those are the only things that seem to work as they should) but the phone seems completely dead. I had a similar thing happen to me before on my older Xiaomi phone but that time my PC at least managed to detect it in device manager as qdloader 9008 (EDL mode) but that just doesn't seem to work now. Would shorting the test points work to make it go into EDL mode or is it a lost call? The bootloader was unlocked before flashing and i chose the option in MiFlash that doesn't lock it again. Thanks for anything. EDIT: Phone sent to a repair centre.

Categories

Resources