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.
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 have owned samsung phones since the original s1 and it's always been easy to flash a stock rom using odin.whenever I had a problem with my current rom or soft bricked I just downloaded the tar odin file flashed pda in odin and went back to 100% stock. But I cannot for the love of God seem to find this easy on at&t s4. A buddy gave me his s4 to update it to latest 4.3 but cannot find any odin tars for any of the 4.3 updates..and when I find it why is it split up by recovery/bootloader etc? So my question is how do i go from 4.2.2 to 4.3 using odin, because he cannot do it via kies or ota
euklid said:
I have owned samsung phones since the original s1 and it's always been easy to flash a stock rom using odin.whenever I had a problem with my current rom or soft bricked I just downloaded the tar odin file flashed pda in odin and went back to 100% stock. But I cannot for the love of God seem to find this easy on at&t s4. A buddy gave me his s4 to update it to latest 4.3 but cannot find any odin tars for any of the 4.3 updates..and when I find it why is it split up by recovery/bootloader etc? So my question is how do i go from 4.2.2 to 4.3 using odin, because he cannot do it via kies or ota
Click to expand...
Click to collapse
There is no 4.3. First off, if he's on MDL then you should root and get recovery and use the StockUp ROM, because that way he'll get 4.3 MK2 but also be able to change ROMs to something like Cyanogemnod. If he already has MF3 then there's a nice clear thread with "UPDATE.ZIP" in the title you can find in the general section with all the information you should need.
DeadlySin9 said:
There is no 4.3. First off, if he's on MDL then you should root and get recovery and use the StockUp ROM, because that way he'll get 4.3 MK2 but also be able to change ROMs to something like Cyanogemnod. If he already has MF3 then there's a nice clear thread with "UPDATE.ZIP" in the title you can find in the general section with all the information you should need.
Click to expand...
Click to collapse
what do you mean there's no 4.3, you mean an odin image of 4.3?? thats what I meant why is it that on my t-mobile s4 they have the complete image of the stock rom, is it because att version has a locked bootloader?? I never had to mess with update.zip files ever on a samsung phone, excuse my ignorance.
euklid said:
what do you mean there's no 4.3, you mean an odin image of 4.3?? thats what I meant why is it that on my t-mobile s4 they have the complete image of the stock rom, is it because att version has a locked bootloader?? I never had to mess with update.zip files ever on a samsung phone, excuse my ignorance.
Click to expand...
Click to collapse
He told you where to look.
scott14719 said:
He told you where to look.
Click to expand...
Click to collapse
I know where to look now thanks, my originally question is why we even have to bother with update.zip instead of just flashing 1 odin file that has complete stock rom like in all other samsung phones.
euklid said:
I know where to look now thanks, my originally question is why we even have to bother with update.zip instead of just flashing 1 odin file that has complete stock rom like in all other samsung phones.
Click to expand...
Click to collapse
Locked bootloader. There is tons of informative threads about it in the general, q&a, development, original development. and developer's only sub-forums.
euklid said:
what do you mean there's no 4.3, you mean an odin image of 4.3?? thats what I meant why is it that on my t-mobile s4 they have the complete image of the stock rom, is it because att version has a locked bootloader?? I never had to mess with update.zip files ever on a samsung phone, excuse my ignorance.
Click to expand...
Click to collapse
Yes, i meant no ODIN image. There's a locked bootloader and they're trying so hard to keep us from modifying it they make it so you can only get repairs through the Samsung centers and such where they check if you tried to mod it and are supposed to not do anything to help you if you did. As scott said, you can find plenty more information around and probably better explanations than my theories.
I think the last full stock rom was I337UCUAMDL or just MDL. Since then though, each update has been just merely that, an update or patch. So there isnt a full rom of 4.3 MK2. Your best bet, which i just did yesterday, is to use Ted77USA's thread on the bricked MK2, third post in his thread. Follow this link. http://forum.xda-developers.com/showthread.php?t=2573080&nocache=1 Again pay attention to it all. Worked out very well for me and my issue. Sure it should be as easy for you.
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.
Hey all,
So I'm sure I'm just doing something stupid and need someone to slap me, but here's what's going on...
I've tried installing every Android 5.0 Rom I can find for the kltevzw in here, it will install (after a factory reset of course) and when I go to reboot, I get a black screen for about 5 seconds after the S5 logo then it reboots into recovery.
I have a Verizon S5 currently with Beans' 4.4.4 (v19) and safestrap 3.75. I've got the NI2 bootloader. Can't think of anything as useful.
Any help would be greatly appreciated. Thanks!
Dude....You are in the wrong section...XDA made a "Q&A, Help & Troubleshooting" for a reason!....You can probably get an answer threre
DonsTechnology said:
Hey all,
So I'm sure I'm just doing something stupid and need someone to slap me, but here's what's going on...
I've tried installing every Android 5.0 Rom I can find for the kltevzw in here, it will install (after a factory reset of course) and when I go to reboot, I get a black screen for about 5 seconds after the S5 logo then it reboots into recovery.
I have a Verizon S5 currently with Beans' 4.4.4 (v19) and safestrap 3.75. I've got the NI2 bootloader. Can't think of anything as useful.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Isn't Verizon's bootloader locked? That would explain the black screen you are getting.
Shawn5162 said:
Dude....You are in the wrong XDA made a "Q&A, Help & Troubleshooting" for a reason!....You can probably get an answer threre
Click to expand...
Click to collapse
Woops, my bad Shawn, I thought that's the section I had open to post to... (on my phone posting) can someone move this to that group?
+1 bootloader locked
eloko said:
+1 bootloader locked
Click to expand...
Click to collapse
Why would the bootloader all of a sudden be an issue with 5.0,when it's not an issue with 4.4.4?
DonsTechnology said:
Why would the bootloader all of a sudden be an issue with 5.0,when it's not an issue with 4.4.4?
Click to expand...
Click to collapse
Because you can only flash touchwiz Roms not any aosp based
DLUX24 said:
Because you can only flash touchwiz Roms not any aosp based
Click to expand...
Click to collapse
DonsTechnology said:
Why would the bootloader all of a sudden be an issue with 5.0,when it's not an issue with 4.4.4?
Click to expand...
Click to collapse
not just that you can only instal TW roms but you cant install ANY 5.0 rom TW or otherwise without the 5.0 kernel which you can't flash due to the locked bootloader, this is the same situation as with AT&T S5 devices. until ATT and VZW come out with 5.0 and we can gain root and update safestrap for 5.0 we are stuck with 4.4.x
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