Database Users

[Q] Stuck on Downloading Screen...

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.

[Q] Stuck in boot loop with no recovery Please Help

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.

Problem after using goomanager

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

Hard bricked GS4 i337, PLEASE HELP.

Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...

dotkong said:
Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...
Click to expand...
Click to collapse
In these situations its best to provide as much information as possible. What was your Baseband? MDL? MF3? if you have no idea what any of this means....then you shouldn't be trying to flash anything on your phone, atleast not until after doing a ton of research. Your best bet is to try and get it into download mode and ODIN back to a stock image. If you can't get into download mode then unfortunately there isn't much you can do. You can try going to a best buy and see if they can flash it for you. You should know that if you're on MF3 you CANNOT flash a custom recovery other than SafeStrap. Hope some if this helps.

This phone is super special with special needs.if you can get it into DL mode than SEARCH for the Odin files that are floating around here.this phone will teach you how to read again
Sent from my ATT S4 MF3 using Tapatalk

If the phone is new like you said, its a good chance the model is MF3. The custom recovery you installed doesnt work for that model which more than likely cased or helped cause your issue. If you dont know the model and your phone won't turn on...the model number is listed on the box (assuming you still have it).
The TC mentioned he can't obtain DL mode so I'm not sure how the using odin will help him since it won't recognize his phone. I'd try best buy and go from there. If you try to have it warrentied while pleading the "I dont know what happened" card to your carrier...just be warned, if they replace it and find out it was rooted or messed with than they will charge your account the full retail cost. I've had many phones replace via manufacturers warranty and that is the first thing they tell me. It can even be an issue if the screen has a tiny scratch. Hope it works out.
brought to you by my not so sexy GS4 MF3

nash2000 said:
If the phone is new like you said, its a good chance the model is MF3. The custom recovery you installed doesnt work for that model which more than likely cased or helped cause your issue. If you dont know the model and your phone won't turn on...the model number is listed on the box (assuming you still have it).
The TC mentioned he can't obtain DL mode so I'm not sure how the using odin will help him since it won't recognize his phone. I'd try best buy and go from there. If you try to have it warrentied while pleading the "I dont know what happened" card to your carrier...just be warned, if they replace it and find out it was rooted or messed with than they will charge your account the full retail cost. I've had many phones replace via manufacturers warranty and that is the first thing they tell me. It can even be an issue if the screen has a tiny scratch. Hope it works out.
brought to you by my not so sexy GS4 MF3
Click to expand...
Click to collapse
He he can't turn it on best buy isn't going to help either. No one will be able to tell it's rooted either. Just take it back to where you got it and tell them it won't turn on. If it does turn on then you can Odin it.

dotkong said:
Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...
Click to expand...
Click to collapse
Pull the battery and wait a minute. Then replace it and see if you can use the correct key combo to get into recovery. If you fix it or get it replaced I suggest you do a lot of reading and learning before doing anything else. Good luck.

Bricked Galaxy S4
I've been there my self. The best and fastest thing to do now is go on the Wed and look up mobiletechvideo .
The guys are great. The turn around is fast.

Thread cleaned and closed.
XDA does not condone fraud in any form.

[Q] Rewarded for my stupidity

Greetings, I'm having a cascade failure and I'm not sure what to do next.
I signed with AT&T on Saturday, and took home a new S4 for free. About 30 minutes later it was rooted, and the upgrade from MF3 to MK2 was installing I removed some obvious bloatware, patched the mail client to bypass an Exchange server's mobile device management, and began to use TB to restore my apps.
I encountered some odd behavior with a couple of restored apps, and did a factory reset. Then, I decided that I wanted to get the patched mail client off the system, so I reflashed the MK2 update through ADB.
The reflash of MK2 failed because I'd removed chrome.apk . D'oh.
Then I thought I'd flash a stock firmware. I quickly found the MF3 tars in another topic. And because I'm stupid and didn't read the whole topic, my nice new phone is showing an ugly yellow triangle and says, "Firmware upgrade encountered an issue." D'oh, d'oh, d'oh.
I'm stopping before I waste any more time or do any more damage (not that I think I can eff things up any more).
Can I fix this at home?
Or should I just take it to the Samsung Experience Shop at the nearby Best Buy store? Will they believe me if I tell them that the MK2 upgrade trashed my phone? The loader says, "Samsung Official," but, also, "custom." Both Knox lines read 0x0. Does any of that matter if they're reflashing as a courtesy?
If they flash MK2, can I get root ..... I'm guessing, no, but probably someone else knows for sure.
THANKS
.

Deleted

xpanmanx said:
Greetings, I'm having a cascade failure and I'm not sure what to do next.
I signed with AT&T on Saturday, and took home a new S4 for free. About 30 minutes later it was rooted, and the upgrade from MF3 to MK2 was installing I removed some obvious bloatware, patched the mail client to bypass an Exchange server's mobile device management, and began to use TB to restore my apps.
I encountered some odd behavior with a couple of restored apps, and did a factory reset. Then, I decided that I wanted to get the patched mail client off the system, so I reflashed the MK2 update through ADB.
The reflash of MK2 failed because I'd removed chrome.apk . D'oh.
Then I thought I'd flash a stock firmware. I quickly found the MF3 tars in another topic. And because I'm stupid and didn't read the whole topic, my nice new phone is showing an ugly yellow triangle and says, "Firmware upgrade encountered an issue." D'oh, d'oh, d'oh.
I'm stopping before I waste any more time or do any more damage (not that I think I can eff things up any more).
Can I fix this at home?
Or should I just take it to the Samsung Experience Shop at the nearby Best Buy store? Will they believe me if I tell them that the MK2 upgrade trashed my phone? The loader says, "Samsung Official," but, also, "custom." Both Knox lines read 0x0. Does any of that matter if they're reflashing as a courtesy?
If they flash MK2, can I get root ..... I'm guessing, no, but probably someone else knows for sure.
THANKS
.
Click to expand...
Click to collapse
I think Best Buy has the update now, but I'm not sure. If you have the unlocked padlock boot screen, they won't take it probably and not if system status is custom in download mode either. There is a chance they'll glance over it, but otherwise you have to follow these instructions: http://forum.xda-developers.com/showpost.php?p=47586777&postcount=135
You can get root, look in the general section for the safe root thread.

joshzdad2013 said:
Deleted
Click to expand...
Click to collapse
Deleted, why?
This post in your quoted topic makes it look like a viable option....
ETA: Ok, I get it. DeadlySin9 post has a link that drops you right onto the procedure.

Nutty. Following DeadlySin9's advice, I used Odin to flash recovery-mj6.tar.md5 into the bootloader slot, it was successful, the phone rebooted through the Samsung / open padlock screen and came right up into my old MK2 load. I immediately used TA to remove the open padlock and it now shows official/official. In the end I guess I didn't eff things up as badly as I'd thought.
How may I reflash MK2 from here? Being as there's only have an upgrade ROM out there, and we're waiting patiently for the whole ROM, I bet it will choke on the missing chrome.apk and other victims of my bloatware-removal party.

xpanmanx said:
Nutty. Following DeadlySin9's advice, I used Odin to flash recovery-mj6.tar.md5 into the bootloader slot, it was successful, the phone rebooted through the Samsung / open padlock screen and came right up into my old MK2 load. I immediately used TA to remove the open padlock and it now shows official/official. In the end I guess I didn't eff things up as badly as I'd thought.
How may I reflash MK2 from here? Being as there's only have an upgrade ROM out there, and we're waiting patiently for the whole ROM, I bet it will choke on the missing chrome.apk and other victims of my bloatware-removal party.
Click to expand...
Click to collapse
Follow deadly sins guide exactly...except replace the mj9 side load zip with the mk2...
The two emergency files will get everything you need for the phone to pass security checks (adds in missing files and apps) after you Odin the two emergency files Odin the recovery again. Reboot to recovery and it will perform a mini update. When the mini update completes reboot to recovery once more and side load mk2...so:
-Boot to download mode
-Odin emergency tar1 (it will fail that's ok)
-Reboot to download mode
-Odin emergency tar2 (it will fail that's ok)
-Reboot to download mode
-Odin recovery
-Reboot to recovery
-Let it auto update
-Reboot to recovery
-Sideload mk2
After I rooted mk2 I messed up with a mod and was left with a phone missing a system file which resulted in it not booting, I did the above and was able to successfully side load mk2 and was back to stock... :
All credit goes do Deadlysin9
Edit here is the link for the mk2 side load: http://www.mediafire.com/?ktkoogwz562p64k
Found like from this post: http://forum.xda-developers.com/showthread.php?p=48363444
Sent from my SAMSUNG-SGH-I337 using Tapatalk

mg2195 said:
Follow deadly sins guide exactly
Click to expand...
Click to collapse
Thanks so much, man.
Things went a little differently, but I let the phone walk me through it. All's well.
For me it went like this ....
-Odin recovery, reboot
-Odin emergency tar1, failed as expected, had to manually reboot
-Odin emergency tar2, failed as expected, had to manually reboot
-Let it boot to the pulsating blue LED, manually reboot
-Odin recovery, it automatically rebooted and applied updates and rebooted to pulsating blue LED
-Manual reboot to recovery, sideload mk2, reboot
-Blow through the initial setup
-Regain root with this procedure
-Drink beer
.