Hi all,
I installed SS and installed CM from a zip, but after the reboot, it's stuck on the Samsung Galaxy S4 Splash screen, does anyone have any ideas of why this would happen?
durron said:
Hi all,
I installed SS and installed CM from a zip, but after the reboot, it's stuck on the Samsung Galaxy S4 Splash screen, does anyone have any ideas of why this would happen?
Click to expand...
Click to collapse
Seriously? do some reading before you do anything to your phone. If you would have read you would have seen that SS only allows TWroms because you cannot change the kernel therefore since you didn't listn you are gonna have to odin back and try to flash back to stock so that you can then find another TW rom to replace stock with. There are a million different forums on here explaining all of this. If you do not know what you are doing either stop or read read read read.
Related
Ok so today I have installed safestrap on my galaxy S4 that has the MF3 update with the locked boot loader. Safestrap is working fine I am useing Slot 1. I have wiped it and installed Google Play Edition 4.3 Virgin ROM for the galaxy s4 from galaxys4root.com. and the mf3 module files. It says successful but then when I hit reboot It shows the samsung galaxy s4 logo then the screen just goes black and the notification light is blue but then it just starts rebooting. I searched for a solution but no results. I have seen some people on these forums that are useing the rom I am and they are working fine. I just dont understand what I am doing wrong please help. If you need a video I can record and show whats wrong but only if you need it.
rajwii64 said:
Ok so today I have installed safestrap on my galaxy S4 that has the MF3 update with the locked boot loader. Safestrap is working fine I am useing Slot 1. I have wiped it and installed Google Play Edition 4.3 Virgin ROM for the galaxy s4 from galaxys4root.com. and the mf3 module files. It says successful but then when I hit reboot It shows the samsung galaxy s4 logo then the screen just goes black and the notification light is blue but then it just starts rebooting. I searched for a solution but no results. I have seen some people on these forums that are useing the rom I am and they are working fine. I just dont understand what I am doing wrong please help. If you need a video I can record and show whats wrong but only if you need it.
Click to expand...
Click to collapse
4.3 roms don't work on safestrap. get the 4.2.2 version of the rom
reply
deadenz said:
4.3 roms don't work on safestrap. get the 4.2.2 version of the rom
Click to expand...
Click to collapse
I thought it could. I swear I saw people with it.
rajwii64 said:
I thought it could. I swear I saw people with it.
Click to expand...
Click to collapse
maybe they have mdl. I think 4.3 roms will work as long as you aren't on mf3
I'm currently running on 4.3 on my S4 and i'm having trouble finding a way to install CWM on my phone. I Downloaded ROM Manager and tried installing it through the app but when I boot into recovery mode, it just shows the regular recovery mode not CWM. So then I went to the official CWM website and downloaded the latest CWM but it comes as a .img and I don't know how to install that. Can somebody show me how to install it?
Dude.
Search. Read. Repeat.
joeybear23 said:
Dude.
Search. Read. Repeat.
Click to expand...
Click to collapse
I'm not that dumb, I've tried that. I guess I should be more specific. every method I find i get an error or it doesn't work. So if you know how to that would be great
You really do need to search, its not that hard. CWM isn't available for your Galaxy S4, and probably never will be. They are working on bringing safestrap which allows some custom roms to be installed on your device.
Samsung and AT&T have really cracked down on rooting and custom recoveries. Those who got the S4 early on who didn't update are still able to flash roms through CWM.
alexs1993 said:
I'm not that dumb, I've tried that...
Click to expand...
Click to collapse
Obviously you haven't. There is no custom recovery available for an AT&T S4 with a release later than MDL.
It's all over the forums. A simple search would have gotten you that, and in the process you may have learned the answer to your next question as well.
Hello,
i m having problems with getting a custom rom to work.
its a AT&T Galaxy S4
I337
Baseband MK2
i rooted the phone....then installed safestrap....
went into safestrap and created a backup. and then installed one of the following files (after each other) on the phone.
aokp_4.3_jflteatt_task650_10.22.2013.zip
CARBON-JB-NIGHTLY-20130906-0328-jflteatt (1).zip
pa_jflteatt-BETA-3.99-RC2-20130922.zip
The Task 650 showed the horse head for a second but went into a thousand blinking lights afterwards.
the Carbot didnt do anything.
and paranoid android showed the shark head loading screen but didnt move on from there.
so none of these 3 worked and i always had to restore the backup.
am i using the wrong roms? am i missing a step? if you could help me out that would be greatly appreciated.
thank you
Ben
You need to use touchwiz based roms
jd1639 said:
You need to use touchwiz based roms
Click to expand...
Click to collapse
alright...now comes the stupid question....
what is a touchwiz rom? and where do i find it?
ben9000 said:
alright...now comes the stupid question....
what is a touchwiz rom? and where do i find it?
Click to expand...
Click to collapse
Start here and use stock based.
Sorry, forgot the link http://forum.xda-developers.com/showthread.php?p=42266401
Why are you trying to flash roms if you don't know what they are? Or what base they are to begin with? What are your long term goals of having a custom rom?
Sent from my SGH-I337 using Tapatalk
First of all sorry if this is the wrong sub forum, I'm new to this site and wasn't sure which section to post it in.
Basically the entire purpose of this is installing XPOSED on my Galaxy S4 SGH-1337M. Now you might be like look up threads on how to but I'm having troubles.
Basically I rooted my phone and have flashed the stock 5.0.1 Bell.
Here my problems begin:
I got the XPOSED framework that was exclusive for Samsung devices and got the version I need. However it said I needed a deodexed version.
I don't know what a deodexed version is and how I get one.
I saw a thread on how you can do it, but is their any file for the bell SGH-1337M that already have a deodexed firmware.
Search XDA for instructions to deodex the ROM yourself. I have never seen a pre-deodexed stock ROM for the i337m.
audit13 said:
Search XDA for instructions to deodex the ROM yourself. I have never seen a pre-deodexed stock ROM for the i337m.
Click to expand...
Click to collapse
How can I tell the difference between a bootloop and a softbrick?
Is bootloop when it stays on the Samsung Galaxy S4?
In don't think there is an "official" definition for bootloop and softbrick but some people define being stuck at the Samsung start up screen as a bootloop and being stuck in download screen as soft brick.
audit13 said:
In don't think there is an "official" definition for bootloop and softbrick but some people define being stuck at the Samsung start up screen as a bootloop and being stuck in download screen as soft brick.
Click to expand...
Click to collapse
So basically if I start it up and it just says Galaxy S4 with particles coming off of it and it stays on that screen forever that is a boot loop?
Yes, that would be a bootloop to some people.
Hi guys, I'm pretty new to custom roms and this forum so feel free to delete/move thread if i've posted in the wrong area.
Phone: Samsung J5 SM-J500FN
I am having trouble flashing custom roms. I have rooted my device, installed TWRP and got to the point where I can install the rom. After installing the rom through TWRP when I reboot the phone I get the classic boot screen then it freezes, I get a yellow line across the screen and the screen goes bright green and full of what look to be dead pixels. I have attempted to install Lineage, Aosp extended and Ressurection Reloaded and have had the same result with all 3. I have been able to reinstall back to stock each time. Is it possible to maybe get some tips on where I may be going wrong here? Thank you in advance.
Garz92 said:
Hi guys, I'm pretty new to custom roms and this forum so feel free to delete/move thread if i've posted in the wrong area.
Phone: Samsung J5 SM-J500FN
I am having trouble flashing custom roms. I have rooted my device, installed TWRP and got to the point where I can install the rom. After installing the rom through TWRP when I reboot the phone I get the classic boot screen then it freezes, I get a yellow line across the screen and the screen goes bright green and full of what look to be dead pixels. I have attempted to install Lineage, Aosp extended and Ressurection Reloaded and have had the same result with all 3. I have been able to reinstall back to stock each time. Is it possible to maybe get some tips on where I may be going wrong here? Thank you in advance.
Click to expand...
Click to collapse
Are you sure you're using the stock firmware required?
Some custom roms, like the 7.1.2s almost all of the threads tells you you need LL 5.1.1 before flashing the custom rom.
Or some need 6.0.1. Are you sure you're reading all the instructions correctly?
JohnTryingToRoot said:
Are you sure you're using the stock firmware required?
Some custom roms, like the 7.1.2s almost all of the threads tells you you need LL 5.1.1 before flashing the custom rom.
Or some need 6.0.1. Are you sure you're reading all the instructions correctly?
Click to expand...
Click to collapse
Thanks for the response mate, I did a bit more reading after posting this and found that out My own fault. I am currently downgrading to Lollipop 5.1.1 using odin but now it's stuck on the samsung logo on boot up after odin has done its bit. Maybe it just takes ages to install but I wouldn't be surprised if I've done something else wrong
Garz92 said:
Thanks for the response mate, I did a bit more reading after posting this and found that out My own fault. I am currently downgrading to Lollipop 5.1.1 using odin but now it's stuck on the samsung logo on boot up after odin has done its bit. Maybe it just takes ages to install but I wouldn't be surprised if I've done something else wrong
Click to expand...
Click to collapse
Got Lollipop installed now, just got to cross my fingers while I try and do this the proper way this time