Bricked Phone! - Dead - HELP!! - T-Mobile Samsung Galaxy S 4

Hi guys, I'm gonna tell you what happened with my S4 to see if you can help me.
I got a MetroPCS Galaxy S4 (SGH-M919N) then I went to a tech and unlocked it. After 2 days the screen started blinking in pink color and I decided to flash it with a stock ROM from T-Mobile (SGH-M919-TMB-M919UVUAMDL-1366964131) using ODIN. Everything was great, in a couple of days the screen went kinda black (No brightness at all) I could barely see it. In this state with the phone turned off and tried to plug in to the PC or charge it and started blinking in green color. I decided once again to flash it with the stock ROM mentioned above but the phone won't enter in recovery or download mode after that I tried to flash it with the CyanogenMOD Installer......everything was OK but it stuck in about 75%, left the phone connected for 20min aprox and nothing happened. I unplugged it and tried to turn it on (It vibrates but I get no startup sound, logo, boot, anything!) ODIN doesn't recognized anymore, can't enter in recovery or download.
I tried to reboot download with ADB to flash it with ODIN but usb debugging is not enabled and ADB commands doesn't work.
I don't know what to do with my S4, I hope you guys can help me. I'm not in the US so I can't return it for replacement.
I hope to hear from you soon. THANKS IN ADVANCE.

Related

[Q] Can't boot to recovery or download mode

It is a long story, started with wanting Photoshare App. After rooting using Odin got into all sort of process stopped error. Desperate, downloaded and tried to flash CM10 using CWM. All I got was CM logo circling endlessly for 30 minutes. Pulled the plug and now, I seem to have a brick, can't even boot to recovery or download mode. When I try to boot to downlad mode, the warning screen appears for just a second and goes away. When I try recovery mode Samsumg log appears and then blank.
Is there anything I can do at this point? I appreciate any help I can get.
dileepan said:
It is a long story, started with wanting Photoshare App. After rooting using Odin got into all sort of process stopped error. Desperate, downloaded and tried to flash CM10 using CWM. All I got was CM logo circling endlessly for 30 minutes. Pulled the plug and now, I seem to have a brick, can't even boot to recovery or download mode. When I try to boot to downlad mode, the warning screen appears for just a second and goes away. When I try recovery mode Samsumg log appears and then blank.
Is there anything I can do at this point? I appreciate any help I can get.
Click to expand...
Click to collapse
Hm. if you boot up your phone are you stuck at the cm bootup? If you are im sorry bro you cant fix it for free by sending it to samsung. JTAG for 60 bucks or samsung for 60 bucks. Reason being that it shows that you have rooted and modded your device. If you were hardbricked and nothing would turn on at all you would be able to send it to samsung and get it fixed for free!
Well if it shows Download mode then it might be working, just not showing, if you see a blue ID:COM number in Odin its working. Try to flash a stock ROM in Odin while in Download mode and make sure its in PDA or you will brick. Check only Auto-Reboot and F. Reset time.
If it works congrats if not search this forum for a service called JTAG which repairs bricks.
\(._.\) To the window, to the wall.
(/._.)/
A little update ...
I was able to get to download mode after many trys and got back to stock -- unrooted. I should have stopped when I was ahead, but I was feeling invincible after this feat of reviving the phone and that was really stupid.
I wanted to root and flash CM10 nightly. I followed the instructions from http://rootzwiki.com/topic/32486-gu...m10-nightlies-without-k-exec-updated-8-18-12/. After unlocking the bootloader step, I wanted to backup the stock ROM I had on the phone -- I don't know why I wanted to do that as I had just flashed the stock and didn't have anything customized. Anyway, when I clicked backup from CWM everything died, kaput, nothing. I have been desperately holding the power button, reovery combination of buttons, download mode combination, anything I can think of, the phone is giving me the total silent treatment, which BTW I am used from a more human source.
Let me know if there is anything I can do, perhaps stand on one leg and try switching it on perhaps. http://forum.xda-developers.com/images/smilies/redface.gif
Sorry for the dumb jokes, I am a little frustrated, but I am sure I will get over it.
Thanks for those who took interest to read my question and those who cared to respond, I appreciate it....
Cheers!
are you getting any signs of life with the phone plugged in with or without the battery in?
jeeper11 said:
are you getting any signs of life with the phone plugged in with or without the battery in?
Click to expand...
Click to collapse
Absolutely nothing, not even the light that comes on when plugged in for charging.
best ...
dileepan said:
Absolutely nothing, not even the light that comes on when plugged in for charging.
best ...
Click to expand...
Click to collapse
Best advice...take out the battery, leave for 1-2 hours, insert battery, try to access download, flash stock in odin, reboot, don't flash any more Jelly Bean roms. lol

[S/SL/AS/Ion]General bricked device thread

So, I've been seeing A LOT of threads regarding bricked devices (be it soft or hard bricks). So, I decided to create this thread, so everyone with bricked devices post here for help, instead of filling our forums and XDA servers with a load of topics with the same stuff.
If someone knows of a general unbricking thread, please PM me or tag me with a link so I can post on this post.
I will PM a mod to pin this thread to top.
To all brickers,
Before posting, try this thread:{RECOVER SOFT-brick}[2012 XPERIA's]Recover ALL 2012 XPERIAs from SOFT-brick
Remember to give the author thanks
Xperia S Return Back To Stock!
Pre-Requisites
For All The New Users..
If You Did Something Wrong
If nothing is working out
Not Able to Fix
Need to Return Back To Original Firmware?
Here is the Guide For You
Click to expand...
Click to collapse
Return Back To Stock
GUIDE for Better Understanding With Pictures And Images For New Users
Explained Step By Step
Click -- [HERE]​
Just a tip: Try downloading Sony Update Service and following the instructions if you get a green LED blink on your phone, which is way simpler to recover without any problems.
Guys My ION LT28h got bricked during a recovery using CWM.
First It was a soft brick, i did something , random pressing of buttons made it worse. its on HARD BRICKED STATE now. Its been more than 5 weeks.
So after some research i found out that my Kernel is ****ed up. My phone is Boot loader Locked, so i cant flash the Kernel separately.
Now few of our fellow xda members told me to unplug the battery cable from the motherboard.
I have successfully disconnected the battery cable from motherboard, i kept it disconnected for one whole night.
Whats the next step ?
Will i be able to flash it with flash tool after connecting the battery to motherboard back ?
Will i be able flash the busted Kernel to a working stock kernel ?
Accidentally messed up and soft bricked Ion- LT28h.
xperia Ion LT28h
ROM: JB 4.1 Pure CyanogenMod Based on CM 10 FXP 218
kernel: GI Kernel v3 or v5
Recovery: TWRP and CWM
Rooted and Unlocked Bootloader
Hi guys, above mentioned were my previous settings. Had occassional reboots and sometimes it was kinda laggy that's why i decided to flash it to another ROM - supposedly to ParanoidAndroid. After following steps to install PA, my phone was on bootloops, was in a hurry then freaked out, i tried soft and hardreset, and tried booting on recovery both on twrp and cwm to flash properly as what was instructed however i may have flashed the wrong zips interchangeably with other roms and kernels resulting to a total messed up ion. i could have restored immediately to a saved CWM or TWRP backup right away however, i only stopped resetting when my phone suddenly stopped responding, no Sony logo, no Xperia logo, no boot, just backlight on, does not turn off, soft and hard reset no nothing. i guess until the battery went dead, then i charged it the whole night.
after reading most threads on recovering softbricked phone, mainly this {RECOVER SOFT-brick}[2012 XPERIA's]Recover ALL 2012 XPERIAs from SOFT-brick thread, and after a couple of days of red led, i constantly charged, i patiently waited(2days) still no green led, however i found out that i can access fastboot. (blue led).. i managed to get to this fastboot mode(blue led) ONLY after i soft reset or power+vol.up/1 vibrate the phone once the backlight lits up- on&off - for about less than a minute then it goes back to red led. (i'll be calling that stage as backlit-on&off-then-back-to-solid-red-led cycle) but then again if i go to fastboot, it will stay in fastboot mode during flashes and it stays there until the battery runs out and goes back to red led. then i charge my phone again, but
during fastboot mode, i have tried flashing the kernel, system and boot image. all via Fastboot command prompt.
and all were successful. there were combinations like, flashing only the kernel, tried flashing kernel and system, tried boot image only, tried all the same time, tried system only, tried different kernels, system and boot img, BUT STILL my phone wont even give me the sony logo screen.
then i thought i may need to wipe cache and userdata so i also erased cache and userdate a couple of times via fastboot mode command prompt. and yes fastboot does detects my phone. it can reboot to bootloader or just the normal fastboot reboot. so i have no issues regarding phone and pc via using fastboot command prompt. and Same thing - all flashes were successful,
i have flashed i think more or less than a total of 50 times, flashing different combinations. Still it goes back to brick mode.. backlit-on&off-then-back-to-solid-red-led cycle.
i'd like to add that i have also tried flashing via fastboot mode using Flashtool. (thunder icon+selecting 'fastboot mode'). i have flashed the kernel and system, tried kernel only, tried both same time, tried system with boot.img tried flashing kernel with boot.img too, tried different combinations. again, all were successful, but still same result.
it only goes back to backlit-on&off-then-back-to-solid-red-led cycle.
a couple of days after it went to green. flashmode finally! thinking everything will now be alright, i decided to flash it using flashtool via flashmode. I connected phone to pc, after the solid red led and after backlit-on&off-then-back-to-solid-red-led cycle. and the it goes back to red led then the backlit on&off cycle, after observing my phone for hours i then knew that after, i guess about a hundred cycle of backlit on&offs it really does go to green led by itself and if i'm connected to the pc and flashtool it stays on green led or flashmode, however if im connected only on a wallcharger it goes to green led but will only stay there for like 1-2 seconds then goes back to red led and then the backlit on&off cycle.
then i thought just maybe my battery really needs to die as mentioned, since upon plugging my phone on to a wall charger it goes immediately to red led and there's really no response on the phone except only if you gonna wait for the backlit on&off cycle the n press power + vol up then it will respond and go to fastboot mode or power+vol down which goes to flashmode. then i decided to reset the battery by carefully unplugging the ribbon cable and i did. well, initially it did (led was off for a moment then changed to blinking red then solid red) but i have to go to work that time and had to continue only after coming home from work, and that did not resolved it.
i may have flashed my ion a hundred times or so to this date, still no luck. i have finally decided to re-locked my bootloader- and yes it is successfully locked now. - thinking PCC/SEUS/SUS would get it back to life but i'm wrong - it just cant detect my phone. PC companion detects it as Phone/Tablet only then after selecting Ion on the phone list it always says my device is upto date and no available software. (sad)
I also noticed that flashtool does not detect my phone as LT28h. It only says that it is connected to flashmode. Is that an issue too. I have tried diff versions of flashtool from 9.6 to 9.11 all same. i have also installed fastboot and adb as well as flashtool drivers, it sayas all were successfully installed however if im connected via flashtool flashmode, none seems to be detected on device manager, tried reinstalling and manually installing the sony sa0103 adb interface driver however after installing i get an error unable to start device. even if my phone is connected still the device on devicemanager still has an excalamation point. i'm using windows 8. i have flashed successfully before when my phone was in good state, however now that im on brick mode it seems that all flashes i've done did not push thru. also those times that i have flashed my ion via flashtool it says something like:
phone should be connected with usb debugging on and enabled install on unknown sources. i have tried flashing it using win7 pc phone was not detected still, however flashtool stated and detected my device was connected on usb debugging mode, but have has errors during flashing though.
since my bootloader is now locked im unable to flash now via fastboot. before bootloader status says- rooted now bootloader status is- ROOTABLE.
i previously owned xperia neo and have managed to flash it successfully without any issues, also this is the 3rd time i had bricked my ion and managed to fix it before..
i also want to ask regarding flashing back to stock - does that mean any stock firmware can be selected? can be .233 / .68 /.20 or the latest ICS 6.1.E.3.7? coz i have basically tried to all of those mentioned. also is the reason that my flashes were not successful is it because i was currently on 4.1 JB ROM and im flashing 4.0 ICS stock? I also have TWRP and CWM backups on my PC and on internal SD card, is there a way for me to flash or restore those backups via flashtool?
I'm running out of options, i'm desperate and on the verge of giving up.
i dont want to believe that i have totally messed up and hard bricked my phone. I do believe that there is a solution to this, and my phone can be recovered without sending it over to repairshop.. Today is the 3rd week and still struggling to get my phone back to life (even just the sony logo) . any suggestions before i unlock again my bootloader? please help. Any help will be gladly appreciated, and many thanks to everyone for spending time on reading my messed up and soft/hardbrick ion experience.
If you brick your device while flashing kernel and device do not respond any way then follow this little difficult but 100% sure method.
- Dissemble your phone.
- Disconnect battery ribbon from motherboard.
- Reconnect battery ribbon.
- Fastly connect USB cable while holding vol +/-
- Flash Kernel or FTF FW.
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Droiiiiiiiiid said:
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Click to expand...
Click to collapse
Did you try SUS ? Official update service ?
Droiiiiiiiiid said:
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Click to expand...
Click to collapse
I think that you should charge it more to be able to go into flashmode. Maybe until the red light will go off or it'll turn into green. Then try to go into flashmode. Good luck
MozzieZ said:
Did you try SUS ? Official update service ?
Click to expand...
Click to collapse
I was going to but that requires my device be in Flashmode.
Droiiiiiiiiid said:
I was going to but that requires my device be in Flashmode.
Click to expand...
Click to collapse
Read this, maybe it will help you.
http://forum.xda-developers.com/showthread.php?t=2344896
This is my first time got hard brick on my phone. I'm flash wrong ROM (it made for S but I flash it on SL) now my phone totally dead. When I put on wall charger it show constant red led and off several minutes later, try disassemble phone and disconnect and connect ribbon doesn't help to get flashmode and fastboot mode. Any help would be very appreciated.
EDIT: After disconnect ribbon battery I got notification on flashtool "device connected with usb debugging off" but led remains on constant red. Should I try rubber band tricks?
ahlulnugraha said:
This is my first time got hard brick on my phone. I'm flash wrong ROM (it made for S but I flash it on SL) now my phone totally dead. When I put on wall charger it show constant red led and off several minutes later, try disassemble phone and disconnect and connect ribbon doesn't help to get flashmode and fastboot mode. Any help would be very appreciated.
EDIT: After disconnect ribbon battery I got notification on flashtool "device connected with usb debugging off" but led remains on constant red. Should I try rubber band tricks?
Click to expand...
Click to collapse
After disconnecting and connecting back the battery cable , you wont get access to flashboot/flashmode instantly. disconnecting the cable will reset the phone.
If you are getting red led means , its charging on low power. You should keep on wall charging for some hours , say 12 + hours.
After that try flashing the kernel alone , first . you will have to hold the flash mode button for sometime. say 5-10 minutes. then if u have enough charge in your phone it will flash the kernel alone. if u are successful in flashing the kernel, then charge again for some hours , 2-4 hours then try to flash the entire ROM.
Read the Thread Recovering Bricked Phones. This will help. I recovered my phone following the method shown in that thread.
Be patient bro, you can recover your phone, just that it will take some time
Captain Droid said:
After disconnecting and connecting back the battery cable , you wont get access to flashboot/flashmode instantly. disconnecting the cable will reset the phone.
If you are getting red led means , its charging on low power. You should keep on wall charging for some hours , say 12 + hours.
After that try flashing the kernel alone , first . you will have to hold the flash mode button for sometime. say 5-10 minutes. then if u have enough charge in your phone it will flash the kernel alone. if u are successful in flashing the kernel, then charge again for some hours , 2-4 hours then try to flash the entire ROM.
Read the Thread Recovering Bricked Phones. This will help. I recovered my phone following the method shown in that thread.
Be patient bro, you can recover your phone, just that it will take some time
Click to expand...
Click to collapse
Thanks for your fast reply, but I'm already put on wall charger 1 day, and the red led got turn off (no led at all). I think I'll try rubber band trick tonight and leave it till morning.
Hey guys I'm having a problem with my Acro S... It's bootloader is unlocked.
It was soft bricked due to a command I ran on Terminal Emulator (dd if=/dev/zero of=/dev/block/mmcblk0). After inputting that command I safely turned off the phone (Long press Power button, Choose Power off). After turning off, phone was completely dead, no response. It was on 80% battery for sure. It happened last week Saturday (July 20). I then charged my phone for 2days+. On the first day (July 21), no red LED appeared, on the 2nd day (July 22), constant red LED appeared, 3rd day (July 23), red LED disappeared. I then prepared my flashtool for flashing the JB firmware .211 KERNEL ONLY. So I plugged in my phone with volume down pressed, I pressed it for 15mins! My finger was f*cked, after 15mins... nothing happened, RED LED just disappeared and I just heard the Windows USB sound. Flash process didn't start, phone didn't give me a GREEN LED. I tried it again and again and miserably same thing happens, can't go to flash mode. Tried the same with volume up button for fastboot mode but still nothing happens, the RED LED just disappears!
Should I just leave my phone charging on the wall socket even if the RED LED disappeared? To get green LED?
SOMEBODY PLEASE HELP ME! I NEED MY PHONE SO BAD! :crying:
i was installing the prerooted/deodexed stock lt28h rom through cwm in the middle of instalation my phone rebooted and came into a sony bootloop i forced it shutdown by pressing power and volume up now its not starting not even charginig what to do please help :crying::crying:
Flash Tool
Be calm and sit back now put your phone to charger for whole night and then next day download flashtool and a firmware for you device and fladh it your device will breath again.......
tejasvi1 said:
i was installing the prerooted/deodexed stock lt28h rom through cwm in the middle of instalation my phone rebooted and came into a sony bootloop i forced it shutdown by pressing power and volume up now its not starting not even charginig what to do please help :crying::crying:
Click to expand...
Click to collapse
we have desame problem my phone is not charging no ligths/led and cant power on after pressing power and up because im stuck in boothllop after afgrading via OTA.
theprint said:
we have desame problem my phone is not charging no ligths/led and cant power on after pressing power and up because im stuck in boothllop after afgrading via OTA.
Click to expand...
Click to collapse
thks for sharing but i have alraedy solved my hard brick problem my phone is back and running normally

VZW Galaxy Nexus goes black after the Google logo

Hi,
I have a really tough problem with my Verizon Galaxy Nexus. After I boot it up it shows the Google logo and then the screen goes black. It is still on because I have left it there hoping it would pass this screen but the battery died eventually. If I put the phone into a computer I get the charging screen and it will charge. I can get into fastboot mode. I have tried unlocking the device so I could flash a new ROM but as soon as I use the Gnex toolkit to unlock it, the fastboot mode reboots and it is locked again. When the device is plugged into the computer in fastboot mode Windows is constantly giving the noise that something is plugged in than unplugged then plugged in, on and on and on. I have put it in Odin mode and flashing the 4.04 image ROM looked like it worked but still after the phone reboots it just shows the Google Logo and then goes black. I have gotten into the stock recovery and wiped data and cache and that did not help either. Any help would be appreciated!
Nick
PS
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
I followed that and afterwards my screen still comes up black after the Google logo.
I just tried to install TWRP recovery to see if that would help. I went through all of the fastboot commands and they said they completed successfully. When the phone rebooted the stock android recovery was still on the device... so for some reason this phone is taking the commands and they are getting returned as successful but they are not successful... super strange.
Sorry I can't help you but I've read several reports (forum posts) about Galaxy Nexus devices becoming "read only". I think the eMMC got bricked and can't be fixed.
My Gnexi said:
Sorry I can't help you but I've read several reports (forum posts) about Galaxy Nexus devices becoming "read only". I think the eMMC got bricked and can't be fixed.
Click to expand...
Click to collapse
Correct, seems highly likely his eMMC deep fried. If unlocking bootloader doesn't even work, I would try nothing else and get its mainboard replaced.
Thanks. Now that I know, I can stop wasting my time trying to fix this.

Lg g2 wont turn on

Im having trouble turning on my lg g2. My phone died last night and is unresponsive if I dont have it plugged in (like a normal dead phone) however, when it is plugged in the LG boot logo appears but then disappears after about 4 seconds followed by the red light blinking a couple of times and then the cycle repeats. I had my phone charging all night and i woke up to it still being in this cycle.
A couple of side notes:
I can enter download mode, although i am unsure if my computer is able to recognize the device
I am rooted
I cant enter recovery mode. the closest i have gotten is the "recovery mode screen.." then the phone powers off.
my device is an ls980 on sprint
Any help is appreciated and I am willing to factory reset as a last resort
did u find aby solution? as I am having same problem wont tun on or charge at all
If you can enter download mode, do it and see if the computer recognizes it. If it does then go ahead and flash the stock firmware using LG Flash Tool. If it doesn't install the LG drivers found on XDA.

Nexus not booting up. Only fastboot and download mode while charging

Hello there everyone! Let me explain my problem:
Backstory
I have a Samsung Galaxy Nexus GT-i9250 maguro since 7-6 years or so. I've been flashing some roms into it and everything went well since a week ago.
I had installed from a very long time this version of CM "cm-13.0-20160921-NIGHTLY-maguro" and I have not updated it, so I basically was running that from a very long time.
Three weeks ago the phone started behaving strangely, it was closing automatically, and I thought that it was a temperature problem (being a very hot summer) so I did not worry too much.
Everything was working fine, charging and connecting via USB .
Problem
Last week the phone once again died and I tried to boot it up normally as I would normally do, but nothing happened, not even the Google logo popped up.
So I removed the battery and put it back in, the phone booted up to the Google logo, then after two or three seconds the Google logo flashed like brightness went up to 100% and black screen.
Went into fastboot, booted TWRP to see if that was working, and the recovery was working fine.
Things got worse.
At the moment
I cannot get the phone to do anything if it's not connected to a power source.
If the phone is connected via USB, or charger, I can get it to go ONLY on fastboot, and download mode. If I unplug the phone while on fastboot or download mode, the screen brightness goes up to 100% for half a second then it glitches out and goes into black screen immediatelly. I can not access bootloader nor recovery mode from fastboot, because the phone reboots, shows the Google logo and then it dies.
What I tried
Thinking that maybe the ROM went crazy, I followed this guide to flash the phone with all the original ROM and recovery (I downloaded "yakju-jwr66y-factory-4cadea65" and followed the instructions of the guide).
Nothing changed, if the phone is not connected to a power source, it is basically dead, if I put it to a power source it shows the charging logo for a second, then black screen, and I can only boot up fastboot and download mode.
I don't know if this might help but I've also tested the battery voltage and it seems to be fine.
Last thing, if I connect the phone to the PC (with the battery or without) every 2 seconds it shows up that an unidentified device is being detected.
I currently am using a laptop running windows 8.
On my desktop computer the same thing happens (the device detection) but from device manager I see a OMAP4400 (something like that) popping up but at the moment I cannot use my desktop PC since I'm traveling.
I would really like to know what happened to my phone, any answer will be appreciated.
Thanks in advance!
Update [solved]
After doing some research and trying different methods I gave up. But then I realized that maybe trying the stupidest thing could be the solution, so I went to a phone shop and asked them if they had some sort of test battery that I could plug in my phone temporarily to see if it was booting up.
Turns out, it was the battery.
I bought a new battery and now the phone runs smoothly like it's new.
I feel so dumb and I'm so sorry if I've made some of you people waste your time by reading the poem of the first post.
Hopefully this will someday help someone that will have the same problem of my GT-I9250!
(This thread can be closed now)

Categories

Resources