[Q] Phone won't boot - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Greetings all
I recently tried the root process that was developed by geohot (http://towelroot.com/) on my s4. It worked to get root and unlock the bootloader (I thought). When i tried to flash a custom recovery to it, it failed and now the phone won't even boot normally at all. Can still get to Odin but can't get to Recovery. When I tried to Odin the stock ROM to it, it fails immediately.
Got any ideas on things that I can try to do to fix it, or you think that it's hardbricked now?

You will be able to Odin flash the full NB1 firmware. The link is available in the all things at&t thread
Sent from my SGH-I337 running GPE using Tapatalk

Also, towelroot only roots. There still is no custom recovery, the bootloader is still locked
Sent from my Nexus 5 using XDA Free mobile app

Related

[Q] Strange problems after full restore

I tried flashing to the latest version of stock rom and found it had the new Samsung policy updates in place preventing me from rooting and using superuser things properly, so I went to do a full restore back (using clockworkmod).
Now my phone takes about 3 minutes to pass the logo screen before booting up to the home screen and my wifi won't switch on either... Anyone have any ideas why this may be?
I'm currently downloading an older stock firmware to flash using odin and then using titanium to restore all my apps and settings.
Is there a way I can have the latest stock firmware without the new policy updates?
Hi, you need to reinstall the stock up to date version via Odin. It may take two attempts. Your boot loader is locked. Once you have done this, flash a recovery via odin then you can root and flash a recovery. It happened to me. Any questions let me know.
Sent from my GT-I9505 using xda app-developers app
Watenaccio said:
Hi, you need to reinstall the stock up to date version via Odin. It may take two attempts. Your boot loader is locked. Once you have done this, flash a recovery via odin then you can root and flash a recovery. It happened to me. Any questions let me know.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
So I need to install the latest stock rom (even though it's got the new Samsung policy updates thing on?), to lock the boot loader, then root and flash CWM via Odin and then use CWM to restore a full backup?
I tried that and it doesn't work... and now when I flash the latest stock rom, the wifi doesn't even turn on... arggghhhhhhhhh!!!!

[Q] Flashed new TWRP now no recovery.

I installed the KOT49H GE ROM on my AT&T SGH-I337 and it runs great. I then decided to see if there was an update to TWRP and I found an updated one and flashed it via goo.im. I later read that this is not the way to do it. Anyway, when I boot into recovery a big yella triangle appears and at&t scolds me for running in authorized firmware. I can boot into download, cancel it and the ROM boots and runs fine.
Under the "about device" page on settings it says the baseband is MK2 (because I flashed that modem). If I look at the boot loader version via android terminal emulator it shows I'm still on MDL.
Any ideas how to get recovery working again?
I am trying to understand the reason why you flashed a recovery.
From your post, it looks like you are using safestrap and deadly venom tool to run GE.
You can flash the MLD files from the tool to get the recovery back.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
insaneretard said:
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
Click to expand...
Click to collapse
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
jmjoyas said:
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
Click to expand...
Click to collapse
Thanks for helping me out. I tried this yesterday and today with the link you provided. When I try to flash it via odin, it comes up as failed. On my phone, it says "SECURE CHECK FAIL: recovery" in red letters on the download page. Any other ideas?
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Do i need root to do this? I don't think I even have root any more. I'm running a custom ROM without root access. I tried to use CASUAL to root and install the recovery but it couldn't root it.
You will only need to root again if you go all the way back to stock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Problem installing custom recovery using Odin

Hey guys, I'm pretty new here and new to rooting devices. I recently just rooted my Samsung Galaxy S 4 SGH-1337 (At&t) with the new "TowelRoot" and then using Super SU to finish the root. I has a question when it came to installing the custom recovery Philz Touch. I have the 4 most recent versions of PT and using Odin v3.09 and v3.07 I am still unable to correctly install the recovery. When I try starting the process I get a "Leave CS" in the bottom left of the Odin window, and when I start the process fails? I've noticed when I go into download mode on my S 4 the phone tells me on the the official binary and official operating system. If I am rooted should that say something else? I have checked the Root Checker app and it says I am in fact rooted.
Other solutions I've already got advice and still unable:
- I'm using my out of box charging cable.
- I am pressing start after I ad the AP in Odin.
- The phone is in Download mode.
Can anyone help me out and assist me? This is super annoying and I would love to figure it out soon. Thank you in advance!
kelvin00 said:
Hey guys, I'm pretty new here and new to rooting devices. I recently just rooted my Samsung Galaxy S 4 SGH-1337 (At&t) with the new "TowelRoot" and then using Super SU to finish the root. I has a question when it came to installing the custom recovery Philz Touch. I have the 4 most recent versions of PT and using Odin v3.09 and v3.07 I am still unable to correctly install the recovery. When I try starting the process I get a "Leave CS" in the bottom left of the Odin window, and when I start the process fails? I've noticed when I go into download mode on my S 4 the phone tells me on the the official binary and official operating system. If I am rooted should that say something else? I have checked the Root Checker app and it says I am in fact rooted.
Other solutions I've already got advice and still unable:
- I'm using my out of box charging cable.
- I am pressing start after I ad the AP in Odin.
- The phone is in Download mode.
Can anyone help me out and assist me? This is super annoying and I would love to figure it out soon. Thank you in advance!
Click to expand...
Click to collapse
Since towel root worked in your phone I'm assuming you're on firmware nc1. This can not have a custom recovery installed. In fact you probably erased your stock recovery trying these other ones. I suggest using odin to flash nb1 then update back to nc1 and if you want a recovery yo install another rom (only touchwiz based roms) you'll to use safestrap. That is the only option at this time.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
Since towel root worked in your phone I'm assuming you're on firmware nc1. This can not have a custom recovery installed. In fact you probably erased your stock recovery trying these other ones. I suggest using odin to flash nb1 then update back to nc1 and if you want a recovery yo install another rom (only touchwiz based roms) you'll to use safestrap. That is the only option at this time.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the response. I am on firmware NC1. After posting I have read that there is a new bootlocker (?) that was pushed on the 4.4.2 update preventing people from actually installing custom recovery and other things. There is a workaround going to an older version to then root and get a custom recovery, but I definitely don't have the knowledge of what to do.
I'm not sure what you mean by me probably erasing my stock recovery? Are you saying if I try and restore my device it will not work?
kelvin00 said:
Thanks for the response. I am on firmware NC1. After posting I have read that there is a new bootlocker (?) that was pushed on the 4.4.2 update preventing people from actually installing custom recovery and other things. There is a workaround going to an older version to then root and get a custom recovery, but I definitely don't have the knowledge of what to do.
I'm not sure what you mean by me probably erasing my stock recovery? Are you saying if I try and restore my device it will not work?
Click to expand...
Click to collapse
When you tried to install the custom recovery it more than likely erased your stock recovery and the only way to get it back is to flash nb1. And going to an older version is no longer possible. Once you update and the bootloader is updated you're no longer able to revert to an older bootloader. Trying to do so could brick your phone
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
When you tried to install the custom recovery it more than likely erased your stock recovery and the only way to get it back is to flash nb1. And going to an older version is no longer possible. Once you update and the bootloader is updated you're no longer able to revert to an older bootloader. Trying to do so could brick your phone
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Again, thank you for responding to me. I understand what you are saying now about me possibly deleting my stock recovery. I didn't go very far i the process and I'm fairly sure I didn't for the simple reason that it did not work. I can definitely be wrong and you are probably more right on this situation than I am.
Thank you for the heads up with the older version not possibly anymore.
Do you know any confirmed ways of rooting and flashing a custom recovery since 4.4.2? If not I guess I'm just going to wait a bit for a confirmed method.
kelvin00 said:
Again, thank you for responding to me. I understand what you are saying now about me possibly deleting my stock recovery. I didn't go very far i the process and I'm fairly sure I didn't for the simple reason that it did not work. I can definitely be wrong and you are probably more right on this situation than I am.
Thank you for the heads up with the older version not possibly anymore.
Do you know any confirmed ways of rooting and flashing a custom recovery since 4.4.2? If not I guess I'm just going to wait a bit for a confirmed method.
Click to expand...
Click to collapse
Before proceeding check to make sure your stock recovery is still intact (power phone off, wait 10 seconds, power on while holding volume up/home button/power if you boot into recovery you're fine and can proceed with towel root (just Google it it'll come up right away) download and install the apk on your phone and it'll root your phone for you. Next go here
http://forum.xda-developers.com/showthread.php?t=2680868
Closest thing to custom recovery that will let you only flash touchwiz based roms.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

[Q] Bricked my Galaxy S4, stuck on boot screen

I apologize in advance for my lack of knowledge and understanding. I recently flashed a custom rom on my Galaxy S4, and it worked but I noticed the Wifi wasn't working, so I attempted to get it to work by trying again. It ended up badly, and it's now been stuck on the boot screen for a while. I tried doing a factory reset and wiping the cache partition, but it was still stuck on the screen. I can also still get onto download mode, so I'm hoping that means I can still save my phone.. I'm also not worried if I lose my internal storage, considering I'm just desperate to get my phone working again. I have an SGH-I337 AT&T phone.
What rom did you try to flash and what firmware version are you on. You're phone is not bricked and is recoverable.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What rom did you try to flash and what firmware version are you on. You're phone is not bricked and is recoverable.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for the fast response. I tried flashing Goldeneye rom and used Safestrap recovery. I'm on firmware version NC1. It's relieving to hear my phone is still fixable. Thank you again!
Daze_ said:
Thank you for the fast response. I tried flashing Goldeneye rom and used Safestrap recovery. I'm on firmware version NC1. It's relieving to hear my phone is still fixable. Thank you again!
Click to expand...
Click to collapse
I would flash the nb1 tar file in Odin. Then do the nb1 to nc1 update and start over again. You'll need to root again and install safestrap. Have you successfully flashed roms in safestrap before?
Start here for the nb1 tar http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would flash the nb1 tar file in Odin. Then do the nb1 to nc1 update and start over again. You'll need to root again and install safestrap. Have you successfully flashed roms in safestrap before?
Start here for the nb1 tar http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I'll try that. Also, this was the first time I've ever flashed a rom, and I'm unsure if you would consider it successful, since the wifi wasn't working, but besides that, I saw no issues.
I had to go this same route when I was messing around and soft bricked like you. It's not hard to recover following the instructions . Odin the NB1 stock tar, let phone boot to ensure it is alive again. Then use the built in recovery to install the NC1 update. Reboot and you are ready to towelroot/supersu/safestrap.
Don't worry. It will be ok!
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Root but can't get recovery

I was able to do the Odin downgrade to to NC1L and towelroot the bring it back to NJ4 with root. Used the TWRP recovery and says the recovery was installed but I am still getting download mode.
I have a SGH-I337 4.4.4, I don't want Safestrap so I can install GPE 5.0. I am new to Samsung only HTC and Motorola usually. This is my work phone.
Thanks in advance.
You can't use twrp recovery on your phone. Safestrap is the only option because of the locked bootloader
Sent from my Nexus 5 using XDA Free mobile app
Sad face commence........I seem to only get phones that have Locked BL UGH!

Categories

Resources