Hi guys long time lurker, first time poster.
Here's the story:
Was running CM 10.2 on my Galaxy S4 AT&T. Everything ran great etc. I decided to flash a new kernel. Upon flashing the kernel I received an error (I must have not done such great research before I did this) but figured nothing had changed since the flash did not go successfully. I proceeded to reboot my phone and lo and behold I'm stuck with a black screen and a constant vibration as if the phone is going to boot up but it doesn't. I immediately went to Odin as I have done when things go awry. After flashing stock firmware Odin says that everything went successful and my phone reboots. However it does not reboot to any screen (no splash screen, no Samsung logo absolutely nothing) just constant vibration and I'm back to square one I cannot boot into recovery I have tried the button combo many, many times but the phone just keeps on fake vibrate booting. The only screen I can get to is the download menu. The things I have tried so far:
1. Flashing back to stock firmware with Odin.
2. Flashing stock kernel by itself with Odin.
3. Tried to flash a custom recovery but since my phone is no longer rooted Odin was giving me a failed message.
4. Tried flashing stock recovery by itself with Odin.
5. Tried Kies but no success either.
I assume no files from a custom ROM will flash successfully as my phone is not rooted. So I guess my question here is am I bricked forever? Odin recognizes my phone and I have read that there is some hope if this happens but I have come to many dead ends searching for a solution to this problem. Have I exhausted my resources on this one or are there a few more things to try? If I left out any information I'll be more than happy to provide what I missed. Thank you in advance.
You flashed a kernel not for your device and have hard bricked your phone. Look up jtag and mobiletechvideos.com
jd1639 said:
You flashed a kernel not for your device and have hard bricked your phone. Look up jtag and mobiletechvideos.com
Click to expand...
Click to collapse
Yep. That is exactly correct.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Thanks guys. I actually went to AT&T and played dumb. Since the phone was still under warranty they just replaced it on site.
dmesserr said:
Thanks guys. I actually went to AT&T and played dumb. Since the phone was still under warranty they just replaced it on site.
Click to expand...
Click to collapse
Replaced it with MDL or MF3? If MDL, you better block the OTA quickly, If MF3, you better do some reading.
Related
Before I get jumped, YES, I did do countless readings to the point of going blind with information overload! Rooting phone was a confirmed success after the OTA update, and I did not do any bootloader roms, but now I can't get pass the download screen while booting up the phone. When I was trying to boot into recovery mode after I did a few quick restarts in a row after rooting phone, to install a debloater .zip, it came to this screen only (see screenshot), quickly (Samsung logo comes up before with the blue corner text) before this, and it's all that it does now. I think I might have pulled the battery a couple times when I saw the first image, my dumbass fault, as a quick power button push wasn't doing anything to reboot. Thinking it's a soft brick as this screen is the only thing that keeps coming up after Samsung Logo with no unlock/lock symbol, when I try to reboot the phone in various ways. I know I can't use Odin to reflash back to stock MDL after the June OTA update, as I tried with no luck came up failed like I knew it would. Plug in via usb to computer, PC doesn't recognize it, so I can't check / access anything on the phone. Pulling straws here. Just looking to get her back to normal
UPDATE
Plugged stock USB cable/Phone in another USB slot, Odin picked it up (See pics), of course I can't downgrade to MDL from MF3.... failure.
US ATT SGH-1337 Jelly Bean 4.2.2
(Last night) Stock Firm: I337UCUAMDL
(This morning) OTA Firm: I337UCUAMF3
You tried to install a custom recovery from what you are describing, yet not really saying.
You wanted to flash a debloat zip... How would one go about doing that? A custom recovery. Unfortunately, there is none for the MF3 update. The only way you would be in this situation is by trying to flash one. So... You're screwed.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
You tried to install a custom recovery from what you are describing, yet not really saying.
You wanted to flash a debloat zip... How would one go about doing that? A custom recovery. Unfortunately, there is none for the MF3 update. The only way you would be in this situation is by trying to flash one. So... You're screwed.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured I was, was hanging on by chance for a bypass, that I might have a chance on getting the phone to boot normally again, by trying a method I hadn't tried / known yet... :crying:
l33t_killa said:
I figured I was, was hanging on by chance for a bypass, that I might have a chance on getting the phone to boot normally again, by trying a method I hadn't tried / known yet... :crying:
Click to expand...
Click to collapse
You can try what this guy did and see if it helps...
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
If it doesn't work i would say you screwed yourself.
Maybe when you "read yourself blind" you missed the Numerous warnings throughout the MF3 root thread and the rest of the forum about MF3 not being able to use custom recoveries or flashing anything?
Good luck.
scott14719 said:
You can try what this guy did and see if it helps...
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
If it doesn't work i would say you screwed yourself.
Maybe when you "read yourself blind" you missed the Numerous warnings throughout the MF3 root thread and the rest of the forum about MF3 not being able to use custom recoveries or flashing anything?
Good luck.
Click to expand...
Click to collapse
,
Yep, I missed that tidbit of info, I did try your suggestion from another member via this thread http://forum.xda-developers.com/showthread.php?t=2407443 as I'm getting closer as per my updates there. Going to try out ou812bkewl's method here http://forum.xda-developers.com/showthread.php?t=2360859
MF3 Nandroid Backup
I was able to get a full Nandroid Backup for AT&T S4 with the MF# firmware using an app called OBackup. Im not real sure if any of the files would be helpful to those stuck after trying to install a custom recovery. I think if you could get into download mode and in Odin, these .tar files might be helpful.
I have the att s4 with the mf3 build which I received via an ota update. I recently did the root for this build which worked perfectly, afterwards I read through 47 pages of forums and was trying to do the work around djrbliss put out, around page 40 someone says if your phone is rooted just download goomanager and installscriptrecovery. then reboot recovery. I downloaded goomanager then installed script, after this I hit the reboot recovery and the phone went into download mode. and it will stay there. If i restart it returns to download mode. Any Ideas?
Im not 100% but u may hve read wrong. This has happened to everyone who has tryed to flash a recovery on mf3. You can only have root there is no custom recovery for this build. Ok now this is wat you do take your phone to bestbuy tell them kies f'd ur phone up nd they can reflash mf3.at this moment mf3 isnt available to general public
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Yeah, read the forums. I mean seriously, almost every other post, including the one you read, tells you that drjbliss's exploit was patched in mf3, and can brick your device if you attempt to install a custom recovery. It is, quite literally, the biggest topic in the S4 forums. Also, there is no odin flashable image for mf3, so you cannot return to stock without taking it to bestbuy. Read more in the q&a section, as this same mistake has been made and asked about at least a hundred times. Literally.
In conclusion, you have a paperweight till you take it to get it flashed back to normal.
ok thanks for the help
cooljg said:
ok thanks for the help
Click to expand...
Click to collapse
Read this thread. Best buy can flash the stock mf3 firmware and get your recovery back. http://forum.xda-developers.com/showthread.php?p=45457012
Either that or J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hey guys thanks for chiming in. I want to give a thank you to those who have gave me a serious answer. I will go back to best buy and try again, but I sent my wife up there and she said the cell phone department told her they do not flash firmware there. She said she asked them if the service section did and the lady told her no again. I am fairly familiar with flashing the firmware on an s3 I just haven't messed with the s4 that much,and obviously I didn't read as well as I thought I did or it wouldn't be bricked. I do have one other question tho if Best Buy can flash it back to stock firmware, is it safe to assume at some point I should be able to flash it back via odin when the mf3 build is released by sammobile? Either way if best buy doesn't flash it back i'm screwed on this one and i'll just have to pick up another s4 tomorrow. I just want to know if this one can be fixed i'd really hate to waste a perfectly good phone.
If and when mf3 firmware is available you should be able to flash with odin. Best buy seems to be using a new software package other than Odin so who knows if an odin package will be available.
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
~wolverine~ said:
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
Click to expand...
Click to collapse
Correct
Question on brick fix
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
cooljg said:
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
Click to expand...
Click to collapse
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Sounds like a simple factory reset...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
haremmon said:
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Click to expand...
Click to collapse
He originally plugged my phone up when I gave it to him but it wouldn't come on so he unplugged it and replaced the battery. The battery I had was completely dead. After he replaced the battery he turned it on and it went to the download screen with the little green alien. After that he held some buttons and kept looking at the back and then the front of the phone. I couldn't really see what he hit but shortly afterwards it came up with my lock screen picture. After that he said it doesn't need flashing but he would flash the firmware if I wanted so I said ok and he did. I have the phone now working great but it doesn't show rooted anymore.
Omg how do people not know this already. I have had my S4 for 2 days even i know better and I cant believe people dont read
Hello, I don't post much as I read and find my answers but this one is sort of a doozy and don't want to waste time if it is unfixable.
So I tried to update my CynogenMod on my phone. I wanted to start off fresh install. I backed everything I wanted with Titanium. Anyways I seem to have rebooted my phone after being formated. It gave the warning that the root has been removed so I pressed the back button but I guess that means go ahead.
Now the phone won't boot into recovery mode. I see the Blue text show up but it just reboots again and then it just sits at the Samsung logo.
I found forum.xda-developers.com/showthread.php?t=2621279 but not sure if this just works with AT&T or every carrier. I am currently downloading my stock firmware but taking forever as it is huge. I do have a backup of my phone before I installed CynogenMod but not sure if I can use those with odin or even which file goes where.
Model is SGH-I337m
Any help will be greatly appreciated.
Thank You!
So after working on this late into the night I got it back up and running. forum.xda-developers.com/showthread.php?t=2621279 worked like a charm. All I had to do was download a stock rom for my carrier I found online. Rstored it to stock form then just started over again. Glad I made backups of all the apps still got Flappy Bird :good:
Finally got CM 11 with PGAPPS working.
Sallad said:
So after working on this late into the night I got it back up and running. forum.xda-developers.com/showthread.php?t=2621279 worked like a charm. All I had to do was download a stock rom for my carrier I found online. Rstored it to stock form then just started over again. Glad I made backups of all the apps still got Flappy Bird :good:
Finally got CM 11 with PGAPPS working.
Click to expand...
Click to collapse
Yeah, just be careful. The guide you followed is for the i337, our canadian variants are i377m. Completely different, glad it worked out for you though. And yes, flashing stock fw with odin will fix any boot issue/soft brick provided the device turns on, any lights at all and can always recover. There is also an unbrick creator script for fixing hard bricks on our devices as well.
azuziel said:
Yeah, just be careful. The guide you followed is for the i337, our canadian variants are i377m. Completely different, glad it worked out for you though. And yes, flashing stock fw with odin will fix any boot issue/soft brick provided the device turns on, any lights at all and can always recover. There is also an unbrick creator script for fixing hard bricks on our devices as well.
Click to expand...
Click to collapse
Thanks for the information. I was pretty desperate last night I even tried adb sideband.
So I'm no stranger to rooting and flashing roms but I messed up big this time. I have a sch-r970 with stock rom and twrp recovery. I attempted to flash a rom. Can't remember the name but the end goal was to get xposed on it. I made a back up then did what I thought was a factory reset. It went downhill from there. I ended up completely wiping the phone. I didn't realize until I couldn't find the rom and rebooted thinking I'll be fine. Well I got the warning that "no OS is installed continue?". I did and now it won't even load twrp. Only download and emergency mode. How screwed am I?
Not very. As long as you can get into download mode you can restore your phone to operating condition. Download the stock ROM for your device from Sammobile and install it using Odin.
Sorry. I should've elaborated more. I downloaded a stock rom and attempted the odin method. It recognized the device but when I started the process it failed. I attempted it via kies as well and it wouldn't connect to my phone. The only thing I haven't tried it an adb push. Unless I'm using the software wrong... Toss me a life jacket plz
Nvm. Just tried a couple different roms. Apparently odin didn't want to flash a couple and it got me worried. Thx for the help.
Glad you were able to resolve things.
I am wanting to flash my phone back to absolute stock 4.4.4 NK7 but am having trouble locating the files needed to do so. I have looked everywhere (that I'm aware of) and have come up empty handed. Thank you for any help you can give in this matter. It is greatly appreciated.
Let me be more specific. I was attempting to install Optimalrom via Safestrap and now I only receive the "Samsung Galaxy S5", (unlock symbol) "custom" "Powered by Android" screen. I can still boot into recovery which is now LRX21T.G900VVRU2BOG5. I can also boot into Odin/download mode.
P.S. : If you'll take the time to assist me, I'll buy you a cup of coffee.
I bought some time with Sammobile. Downloaded the NK2 FW and now have my phone back in order.
Salval said:
Let me be more specific. I was attempting to install Optimalrom via Safestrap and now I only receive the "Samsung Galaxy S5", (unlock symbol) "custom" "Powered by Android" screen. I can still boot into recovery which is now LRX21T.G900VVRU2BOG5. I can also boot into Odin/download mode.
P.S. : If you'll take the time to assist me, I'll buy you a cup of coffee.
Click to expand...
Click to collapse
I flashed mine to Optimal last week and ran in to the same problem. If I recall, the instructions in the Optimal thread said to flash ROM then firmware then OD5 bootloader. I used that sequence and froze on the same screen as you. Decided to try something so I wiped again and flashed ROM then bootloader second and then firmware and it came right up as it should and has been running fine since. I think I might try something else though, not real impressed with the battery life versus stock un-rooted.
I just got back in to being able to root again last week with a warranty replacement stroke of luck that came in as BOC4