[FIXED] Hyperdrive RLS17.1 for I337 (AT&T) showing I545 (Verizon) - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Last night I’ve replaced my spare GS4 i337 AT&T (US) stock ROM with Hyperdrive RLS17.1 KitKat (http://forum.xda-developers.com/showthread.php?t=2520418).
Evidently the device was rooted and Safestrap installed. The Hyperdrive install went smooth and the phone booted properly, with poorer signal reception than usual, but with wi-fi. I also installed the AT&T Module (http://forum.xda-developers.com/showthread.php?t=2616221). I’ve used my SIM card and was able to make at least one phone calls without changing any settings.
However, when I look at the About Device, I see that “Model Number” is SCH-I545 (while it should have been I337), but the “Baseband Version” correctly reads I337UCUFNB1.
Now I’m planning to do the upgrade to my main (also S4) phone, but should I be concerned about the Model Number being wrong? Or is this a developer oversight? Did I missed a step (like replace Kernel)?
Did anyone else had this problem?
Thanks in advance

tsaxman said:
Last night I’ve replaced my spare GS4 i337 AT&T (US) stock ROM with Hyperdrive RLS17.1 KitKat (http://forum.xda-developers.com/showthread.php?t=2520418).
Evidently the device was rooted and Safestrap installed. The Hyperdrive install went smooth and the phone booted properly, with poorer signal reception than usual, but with wi-fi. I also installed the AT&T Module (http://forum.xda-developers.com/showthread.php?t=2616221). I’ve used my SIM card and was able to make at least one phone calls without changing any settings.
However, when I look at the About Device, I see that “Model Number” is SCH-I545 (while it should have been I337), but the “Baseband Version” correctly reads I337UCUFNB1.
Now I’m planning to do the upgrade to my main (also S4) phone, but should I be concerned about the Model Number being wrong? Or is this a developer oversight? Did I missed a step (like replace Kernel)?
Did anyone else had this problem?
Thanks in advance
Click to expand...
Click to collapse
That ROM usually has multiple device / carrier options in Aroma. You probably chose Verizon instead of AT&T, or as you suggested, the dev made an error on the build.prop.
Either way, nothing to worry about as long as the device is working properly.

upndwn4par said:
That ROM usually has multiple device / carrier options in Aroma. You probably chose Verizon instead of AT&T, or as you suggested, the dev made an error on the build.prop.
Either way, nothing to worry about as long as the device is working properly.
Click to expand...
Click to collapse
Thanks upndwn4par!!!
Yes, I made the correct AT&T carrier choice, in Aroma. I also made sure the Module file matched the NBI file.
Will keep on going and will report if anything is not working as expected.
Once again, thanks for the replay.
Cheers :good:

tsaxman said:
Thanks upndwn4par!!!
Yes, I made the correct AT&T carrier choice, in Aroma. I also made sure the Module file matched the NBI file.
Will keep on going and will report if anything is not working as expected.
Once again, thanks for the replay.
Cheers :good:
Click to expand...
Click to collapse
My experience is that without the proper I337 configuration, certain apps wouldn't install from Google Play. This included some expected issues, such as ATT apps (like ATT Messaging app) that would be expected to be specific to ATT supported phone models, but also lots of other apps just wouldn't show up in the store when I browsed on the phone that identified itself wrongly as a Verizon phone. Sort of random hit or miss.
You can restore the identification of the phone by flashing the ATT build.prop/APN file, but that somehow interferes with hyperdrive tweaks app.
The dev has said build 18 should work better for ATT phones... if so, it would be awesome. He put an incredible amount of effort into this ROM. I had to leave it due to the "+" addition messing up incoming/outgoing calls, plus the phone model ID issue. Prefixer app apparently can fix for some the + issue, but I never found enough details to properly edit the build.prop to identify the phone for google play. However, I was in a hurry and didn't have a lot of time to mess with it.
I look forward to investigating version 18 when it comes out.
Marc

upndwn4par said:
That ROM usually has multiple device / carrier options in Aroma. You probably chose Verizon instead of AT&T, or as you suggested, the dev made an error on the build.prop.
Either way, nothing to worry about as long as the device is working properly.
Click to expand...
Click to collapse
Frankenscript said:
My experience is that without the proper I337 configuration, certain apps wouldn't install from Google Play. This included some expected issues, such as ATT apps (like ATT Messaging app) that would be expected to be specific to ATT supported phone models, but also lots of other apps just wouldn't show up in the store when I browsed on the phone that identified itself wrongly as a Verizon phone. Sort of random hit or miss.
You can restore the identification of the phone by flashing the ATT build.prop/APN file, but that somehow interferes with hyperdrive tweaks app.
The dev has said build 18 should work better for ATT phones... if so, it would be awesome. He put an incredible amount of effort into this ROM. I had to leave it due to the "+" addition messing up incoming/outgoing calls, plus the phone model ID issue. Prefixer app apparently can fix for some the + issue, but I never found enough details to properly edit the build.prop to identify the phone for google play. However, I was in a hurry and didn't have a lot of time to mess with it.
I look forward to investigating version 18 when it comes out.
Marc
Click to expand...
Click to collapse
Thanks for the information, Marc. But the link is dead!!!:crying:
After reading some more about this problem, I've decided to try a few more things. The first one was the most basic: Restart the phone! And guess what? It got stuck on the Samsung logo screen for a long time. After 30 minutes starring at the swirling logo I got dizzy and decided to restart it again. Same thing happen, over and over again
After some [yet] more reading, I've decided to reflash (see steps below) the Hyperdrive ROM again, but got stuck on the Samsung logo screen for over 30 min. Back to reading some more, and at this time I've reflash the GE (GoldenEye) ROM. Same result: got stuck on the Samsung logo screen!!
Any advices?
These are the steps I'm doing:
(Root steps were done only once, when the phone was stock)
1 - ROOT:
Note: Good video (just skip the step to set Permissive - see easier approach on #1.4) -http://youtu.be/2bDe_-mB7Rw
1.1 - Root with towel root (https://towelroot.com/)
1.2 - Install SuperSU (PlayStore) and let it disable Knox.
1.3 - Install BusyBox (PlayStore) and let it cook
1.4 - Install SELinux Mode Changer (PlayStore). Run and set it to Permissive.
1.5 - Install Safestrap (http://forum.xda-developers.com/showthread.php?p=45693712)
2 - Replace/Install Hyperdrive ROM
2.1 - Flash Hyperdrive (http://forum.xda-developers.com/showthread.php?t=2520418)
2.2 - Flash SuperSU.zip file. (http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip)
2.3 - Flash NB1 modem zip file (http://forum.xda-developers.com/showpost.php?p=46762296&postcount=1).
2.4 - Flash I337 Build.prop/APN (http://forum.xda-developers.com/showpost.php?p=51112381&postcount=9)
3 - Replace/Install GoldenEye ROM
3.1 - Flash Goldeneye (http://forum.xda-developers.com/showthread.php?t=2313469)
3.2 - Flash SuperSU.zip file. (http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip)
3.3 - Flash NB1 modem zip file (http://forum.xda-developers.com/showpost.php?p=46762296&postcount=1).
3.4 - Flash I337 Build.prop/APN (http://forum.xda-developers.com/showpost.php?p=51112381&postcount=9)
I've also followed these steps http://forum.xda-developers.com/showthread.php?t=2313469&highlight=stuck+on+boot&page=151), but still the same issue:
if ur device gets stuck after flash at att boot animations for a long time .. dont freak out .. do this
1. hold power till device is off or remove battery then put in back in after 30 secs
2. hold power and vol up til u see blue text top left of screen, now let go of buttons
3. choose wipe factory reset
4. wipe cache for the hell of it
5. choose reboot system
Click to expand...
Click to collapse

Which link was dead?
I've seen in the past month several posts of problems of people with NB1, so I recommend starting over via ODIN to Stock NB1, flash to NC1, then re root / safestrap and try the rom again. Also, when you flash the ROMs in safestrap, were you wiping system/cache/dalvik etc.. first?
Marc

Frankenscript said:
Which link was dead?
I've seen in the past month several posts of problems of people with NB1, so I recommend starting over via ODIN to Stock NB1, flash to NC1, then re root / safestrap and try the rom again. Also, when you flash the ROMs in safestrap, were you wiping system/cache/dalvik etc.. first?
Marc
Click to expand...
Click to collapse
Mark,
The link you posted initially
You can restore the identification of the phone by flashing the ATT build.prop/APN file, but that somehow interferes with hyperdrive tweaks app.c
Click to expand...
Click to collapse
Yikes, I was fearing not go the ODIN route (or root? :silly. Does anyone know where I can get ODIN and the NB1 and NC1 stock? (I'm not being lazy and will search for it. I just want to make sure I'm getting the right files)
I still don't understand why did the phone booted, setup, and I was able to make a call and then simply failed to reboot? Do you believe that maybe the Build.prop/APN was broken? what happened if it was not installed?
Thanks.
T.

Mark,
I've realized the 'broken link' problem. I've copy/paste the text Build.prop/APN and noticed that it has a URL property "Link added by VigLink', which points to nowhere.

tsaxman said:
Mark,
I've realized the 'broken link' problem. I've copy/paste the text Build.prop/APN and noticed that it has a URL property "Link added by VigLink', which points to nowhere.
Click to expand...
Click to collapse
Oops. Not sure where the viglink thing came from. Here's the download page for the build.prop file:
http://d-h.st/6tN
Links to ODIN stuff including NB1 ODIN-flashable file and NC1 update (flashed from stock recovery after NB1 return to stock is done) are found in the all things ATT thread:
http://forum.xda-developers.com/showthread.php?t=2616221
See post 1, the Returning to Stock / ODIN section.
FWIW, I always use the stock NB1 (not the rootable NB1 variant) then flash the NC1 update. I had one bad experience with the rootable NB1 (couldn't get wifi to work after ROM flash), and never quite figured out why. Doing NB1-NC1 only takes a few extra minutes, so I stick with that.
Marc

Frankenscript said:
Oops. Not sure where the viglink thing came from. Here's the download page for the build.prop file:
http://d-h.st/6tN
Links to ODIN stuff including NB1 ODIN-flashable file and NC1 update (flashed from stock recovery after NB1 return to stock is done) are found in the all things ATT thread:
http://forum.xda-developers.com/showthread.php?t=2616221
See post 1, the Returning to Stock / ODIN section.
FWIW, I always use the stock NB1 (not the rootable NB1 variant) then flash the NC1 update. I had one bad experience with the rootable NB1 (couldn't get wifi to work after ROM flash), and never quite figured out why. Doing NB1-NC1 only takes a few extra minutes, so I stick with that.
Marc
Click to expand...
Click to collapse
Thanks a million, man. Downloading and trying that now.
BTW, other than I should have done NB1 to NC1 prior to install the ROM and since you've already done all this (on GE 36, right?), are the steps I've outline correct?

By now with some luck you are on GoldenEye, but yeah, the steps you outlined are correct.
1. Get to NC1 stock.
2. Root / SuperSU / SeLinuxModeChanger (sometimes needed sometimes not) / SafeStrap
3. In safestrap: advance wipe everything but SD card then: Golden Eye / SuperSU / NC1 module / ATT APNw/Build.Prop
Should be golden. Let us know how it went!

Frankenscript said:
By now with some luck you are on GoldenEye, but yeah, the steps you outlined are correct.
1. Get to NC1 stock.
2. Root / SuperSU / SeLinuxModeChanger (sometimes needed sometimes not) / SafeStrap
3. In safestrap: advance wipe everything but SD card then: Golden Eye / SuperSU / NC1 module / ATT APNw/Build.Prop
Should be golden. Let us know how it went!
Click to expand...
Click to collapse
Marc,
I am up and running. Lot's of work, but everything seems to be working in order now. Loving the debloated GoldenEye.
Just one more thing: The Build Number now reads: Venomous-Droid v1
Is that right? Shouldn't it say something like GoldenEye?
Maybe I should stop looking at the Build Number from now on, but I can't resist :cyclops:
Again, thanks for the help man. Forever grateful :good:

tsaxman said:
Marc,
I am up and running. Lot's of work, but everything seems to be working in order now. Loving the debloated GoldenEye.
Just one more thing: The Build Number now reads: Venomous-Droid v1
Is that right? Shouldn't it say something like GoldenEye?
Maybe I should stop looking at the Build Number from now on, but I can't resist :cyclops:
Again, thanks for the help man. Forever grateful :good:
Click to expand...
Click to collapse
Glad it's working out. Hit thanks if I helped. (EDIT: Just noticed you did! :good: )My build also shows venomous. My guess has been that our GoldenEye dev used some pieces of Deadly Venom, and acknowledges it via this method, but I don't know for sure. The important thing is that as far as Google Play is concerned, our device is an I337.
I presume Wifi is working for you? I was chatting with another user similar to us earlier this week, and going through the steps he had trouble getting wifi working, even after flashing the modules and everything. Not sure what caused it but glad you seem to be up and running.
In other news, I've just bought a phone on Swappa, a T-Mobile version of the S4, sim unlocked (so should work fine with ATT), and the T-Mobile phones come with unlocked boot loader. So, as long as I don't care about knox, I can install full recoveries and play with different kernels and such. I'll get the phone in-hand next week. After checking it out, it's bye-bye locked boot loader.
HAve fun with Golden Eye. It's been rock steady for me.

Frankenscript said:
Glad it's working out. Hit thanks if I helped. (EDIT: Just noticed you did! :good: )My build also shows venomous. My guess has been that our GoldenEye dev used some pieces of Deadly Venom, and acknowledges it via this method, but I don't know for sure. The important thing is that as far as Google Play is concerned, our device is an I337.
I presume Wifi is working for you? I was chatting with another user similar to us earlier this week, and going through the steps he had trouble getting wifi working, even after flashing the modules and everything. Not sure what caused it but glad you seem to be up and running.
In other news, I've just bought a phone on Swappa, a T-Mobile version of the S4, sim unlocked (so should work fine with ATT), and the T-Mobile phones come with unlocked boot loader. So, as long as I don't care about knox, I can install full recoveries and play with different kernels and such. I'll get the phone in-hand next week. After checking it out, it's bye-bye locked boot loader.
HAve fun with Golden Eye. It's been rock steady for me.
Click to expand...
Click to collapse
Yes, Wifi is working fine. I'll continue testing over this weekend and will report back Monday.
Seems like you're reading my mind. I'm just looking into the Unlock Sim threads and found this... http://forum.xda-developers.com/showpost.php?p=54772758&postcount=286, which points to the Saferoot thread/download http://forum.xda-developers.com/showthread.php?t=2565758.
The important part (at least to me) was the comments..
2. Resetting the "Custom" and open padlock indication during boot can be worked around using the Xposed Framwork and Wanam Xposed. Get those two from the Play Store. In Wanam, tick "Security Hacks", "Fake System Status".
Click to expand...
Click to collapse
I don't know much about Wanam or Xposed, but do you think these can unlock the SIM on just trick the system at a higher lever (as indicated) for some other reasons?
Oh, the last link on the page points to file to NC1 users
Method 3 (For those on NC1 or higher) @NewToGalaxy
Link for the files needed:
https://www.dropbox.com/s/16fu4havwvbt59c/NC1unlock.zip
Click to expand...
Click to collapse

tsaxman said:
Yes, Wifi is working fine. I'll continue testing over this weekend and will report back Monday.
Seems like you're reading my mind. I'm just looking into the Unlock Sim threads and found this... http://forum.xda-developers.com/showpost.php?p=54772758&postcount=286, which points to the Saferoot thread/download http://forum.xda-developers.com/showthread.php?t=2565758.
The important part (at least to me) was the comments..
I don't know much about Wanam or Xposed, but do you think these can unlock the SIM on just trick the system at a higher lever (as indicated) for some other reasons?
Oh, the last link on the page points to file to NC1 users
Click to expand...
Click to collapse
I bought a factory-unlocked one from Swappa. No need to fuss with SIM unlocking :laugh: :good:

Related

[Q] Need help recovering i337 S4

Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
revolut10n said:
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
Click to expand...
Click to collapse
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Safestrap only works with other TW ROMS, so your first issue was trying to use CM. Second, it's not official TWRP and is not even installed to the recovery partition so using ROM Manager was your second issue. Trying to boot into recovery normally will take you to stock recovery since it isn't installed in the recovery partition, there should be a splash screen that comes up after the Samsung Galaxy S4 screen asking to either press for recovery or continue. If that works, you can use the backup from there. If it's gone, you have to use ODIN. The reason you get that SW REV. CHECK FAIL is because you're trying to flash an older firmware than you have. Depending on if you were on 4.2.2 or 4.3 you will either need the MF3 or MK2 .tar.md5 respectively.
jd1639 said:
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
Click to expand...
Click to collapse
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
revolut10n said:
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
Click to expand...
Click to collapse
Deadly sin said it all. Cm and rom manager. Here are the files you need http://forum.xda-developers.com/showthread.php?p=49687770
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
revolut10n said:
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
Click to expand...
Click to collapse
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Now you tell me - after I've been trying to do this for 12+ hours. Many thanks though - it looks like the MK2 AiO files are working.
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
revolut10n said:
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
Click to expand...
Click to collapse
Check my last Post #50 it should get u an idea and where to find related link. Also check that MK2 INDEX & ROM LIST ....:good:

[Q] Very confused about what options are available to someone with nc4,

Hello all, I posted a similar topic a few days back, and cannot seem to find it. I fear it was deleted, but could be wrong. I only looked back a few pages in the history.
My problems have multiplied since that posting. I have nc4, when I bought my phone it was on there. Used towelroot and was able to root, download safestrap 3.75 and was able to add/delete slots, attempted to use hyperdrive, experienced a lot of weird things like my SMS would randomly not send, battery life was not spectacular,and just other misc things. IT seemed like I might have used a rom that could not be used properly for nc4. I then tried bajarom, which completely does not work for my phone, probably because it's nc2 and I didn't realize that?? Tried jellybeanz or whatever the exact name was, my phone won't even boot, says it successfully installed but sticks on the black screen.
Somehow over the past few days I managed to wipe my stock so I do not have the stock, thus I cannot go back.
I am sure I can find or maybe be directed to the stock firmware and reflash it.
I am not sure if it's possible but I'd really love to be able to get nc2, or if someone more knowledgable than myself could point out a solution for me, I would like to have a custom rom if theres one that would work properly on my phone.
Another confusion I have, with the nc4, am I able to use odin to flash a different radio, should I even bother? I would sincerely appreciate someone who would help clear some of this up for me, I'm pretty novice as you can see. Thanks in advance.
update
I guess my question is unclear. I really can use some help if anyone would be so obliged.
I am trying to use ADB to push the file over, it says access denied, I was previously rooted and verified as much. My issue is I need a way to send the roms over to my SD or my regular phone internal mem so I can at least load a rom. Currently my phone is bricked and I am just getting very upset, I really could use someone to give me a bit of guidance.
I opened the cmd with admin and it's still saying access denied. IS there a way to force the phone to open as a media device via cmd? That way I can edit sd card info and push on there what needs to go?
I am currently trying to find a way to get hyperdrive, or another rom over.
I have beanstowns rom on there, it appears as .zip yet when I try to install from safestrap I end up exploring the directory, as opposed to just being an option I can choose.
Baja is the same way, both are still on my sd, yet for whatever reason I cannot select them to install them.
Hope is not lost.
I think your initial problem was that you tried using rom slots. It specifies in the Safestrap OP that rom slots are only supported on NC2 bootloader. Since you are on the NC4 bootloader you cannot go backwards, however you can flash the NC2 kernel if you want to run a custom rom, you simply need to use the stock slot alone.
Since I know very little about ADB & Terminal CMD, I will try to give you directions to get up and running the way I know how.
First you'll need to reflash the stock NC4 tar via odin and reroot. Files can be found here.
Since you've flashed a couple different roms that have probably messed with the system settings I would do a factory reset before rerooting.
After you are up, running and rooted, follow the instructions here to get on the NC2 kernel.
Once you've completed these steps you will be on the NC4 bootloader with the NC2 kernel and be able to flash a custom rom in the stock rom slot. Only a NC2+ rom will function so make sure it is based on NC2/NC4 (i.e. jelly 'beans' will not run on NC2+ firmware as it is based on MJE).
kinstre11 said:
Hope is not lost.
I think your initial problem was that you tried using rom slots. It specifies in the Safestrap OP that rom slots are only supported on NC2 bootloader. Since you are on the NC4 bootloader you cannot go backwards, however you can flash the NC2 kernel if you want to run a custom rom, you simply need to use the stock slot alone.
Since I know very little about ADB & Terminal CMD, I will try to give you directions to get up and running the way I know how.
First you'll need to reflash the stock NC4 tar via odin and reroot. Files can be found here.
Since you've flashed a couple different roms that have probably messed with the system settings I would do a factory reset before rerooting.
After you are up, running and rooted, follow the instructions here to get on the NC2 kernel.
Once you've completed these steps you will be on the NC4 bootloader with the NC2 kernel and be able to flash a custom rom in the stock rom slot. Only a NC2+ rom will function so make sure it is based on NC2/NC4 (i.e. jelly 'beans' will not run on NC2+ firmware as it is based on MJE).
Click to expand...
Click to collapse
firstly, thank you so much for the reply.
I did flash nc2 kernal, but was confused when I still saw nc4 in the about section. I flashed with odin NC2_modem_kk.tar and nc2kernel.tar.
The issue I was having is with hyperdrive, and baja I had some serious issues, so I assumed it was because I was using them incorrectly, ie didn't install one of the above files correctly, or did something else wrong in the process. Just for example, with hyperdrive, my sms would just stop sending/receiving/ double sending. My sim card was not being recognized. And a whole lot of other issues.. So I kept messing around and now im at a point where nothing boots up, I cannot reflash, and I'm just stuck.
I will follow your link and attempt to do as you said, will wipe, and then will try again.
deindichter said:
firstly, thank you so much for the reply.
I did flash nc2 kernal, but was confused when I still saw nc4 in the about section. I flashed with odin NC2_modem_kk.tar and nc2kernel.tar.
The issue I was having is with hyperdrive, and baja I had some serious issues, so I assumed it was because I was using them incorrectly, ie didn't install one of the above files correctly, or did something else wrong in the process. Just for example, with hyperdrive, my sms would just stop sending/receiving/ double sending. My sim card was not being recognized. And a whole lot of other issues.. So I kept messing around and now im at a point where nothing boots up, I cannot reflash, and I'm just stuck.
I will follow your link and attempt to do as you said, will wipe, and then will try again.
Click to expand...
Click to collapse
Alright, I applied to nc4 and did a factory reset, made sure all my slots were deleted (had 2). Then factory reset and rebooted, saw safestrap, pressed continue, and i'm looking at a blank screen now as though there is nothing to boot to. I was under the impression factory reset would undo all and it has not.
Did I do something wrong, or am I missing something?
deindichter said:
Alright, I applied to nc4 and did a factory reset, made sure all my slots were deleted (had 2). Then factory reset and rebooted, saw safestrap, pressed continue, and i'm looking at a blank screen now as though there is nothing to boot to. I was under the impression factory reset would undo all and it has not.
Did I do something wrong, or am I missing something?
Click to expand...
Click to collapse
Did you already boot into download mode and flash the correct files through Odin? If so that should set your phone back to stock. Then you would have to re root.
fsolares said:
Did you already boot into download mode and flash the correct files through Odin? If so that should set your phone back to stock. Then you would have to re root.
Click to expand...
Click to collapse
I did and it did not boot me back into stock. I then found http://forum.xda-developers.com/showthread.php?t=1922461which led me to download the files directly from samsung.
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
deindichter said:
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
Click to expand...
Click to collapse
can u post the link from where u got the official partition table/modem/kernel on verizon website...
deindichter said:
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
Click to expand...
Click to collapse
So are you good to go now?
moin786 said:
can u post the link from where u got the official partition table/modem/kernel on verizon website...
Click to expand...
Click to collapse
could you post where you found all this since im trying to get my phone back to stock.
Paulrybicki83 said:
could you post where you found all this since im trying to get my phone back to stock.
Click to expand...
Click to collapse
Seriously, just Google for the Samsung official firmware. It's on their site. Not Verizon.

[Q] AT&T SG4 SGH-I337 Slow

Hello. Sorry for the noobie question. I tried to search the forums, and I did find the noob beginner guide, but I still wasn't sure, so I prefer to ask before I screw up my phone lol.
I have the AT&T SG4 SGH-I337 Phone. It was fine before it was upgraded to 4.4.2 (I didn't want to upgrade, but it did it on its own one day). Once it went to 4.4.2, everything is just DOG SLOW. I mean everything. In Car Audio takes forever to connect, phone calls takes like 5 secs to answer, even after I press the answer button. To unlock the phone I have to press the code 2-3 times, as I can see the keys I press is lagging behind.
What I wanted to ask is this: How can I bring this phone back to the previous OS? Or How can I modify this phone to a stock OS, where all this bloatware crap is not installed?
All I care for is my Bluetooth, in car audio and calls and have a phone that's fast enough as it was originally.
can someone point me to the right thread where it gives me step by step instructions? Ive never modified a Samsung Phone before.
I found this thread, but wasn't sure if its the right one for my phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Thank you VERY MUCH. Thanks....
Don't use those links, some are redirecting me to questionable sites. Not sure if it does to you also.
I don't have time atm but someone will get you the correct info. :good:
It may have been a bad download that updated you--
Also, those files are too old for you if you look at thread date--
---------- Post added at 07:01 PM ---------- Previous post was at 06:25 PM ----------
This would be a starting point
http://forum.xda-developers.com/showthread.php?t=2616221
Assume you are now on NC1
Believe you will need to Odin back to NB1 then update to NC1
If you want to root other steps involved--This thread covers it pretty well
Some one else more familiar can be exact, as I am on old bootloader and no handson exp--
Read the OP on the link very well and generally not a good idea to use links outside xda unless you are 120% sure of what you are doing--good luck--
Cornelp said:
Hello. Sorry for the noobie question. I tried to search the forums, and I did find the noob beginner guide, but I still wasn't sure, so I prefer to ask before I screw up my phone lol.
I have the AT&T SG4 SGH-I337 Phone. It was fine before it was upgraded to 4.4.2 (I didn't want to upgrade, but it did it on its own one day). Once it went to 4.4.2, everything is just DOG SLOW. I mean everything. In Car Audio takes forever to connect, phone calls takes like 5 secs to answer, even after I press the answer button. To unlock the phone I have to press the code 2-3 times, as I can see the keys I press is lagging behind.
What I wanted to ask is this: How can I bring this phone back to the previous OS? Or How can I modify this phone to a stock OS, where all this bloatware crap is not installed?
All I care for is my Bluetooth, in car audio and calls and have a phone that's fast enough as it was originally.
can someone point me to the right thread where it gives me step by step instructions? Ive never modified a Samsung Phone before.
I found this thread, but wasn't sure if its the right one for my phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Thank you VERY MUCH. Thanks....
Click to expand...
Click to collapse
I would suggest getting the Google Play Edition rom as stock android is much better optimized. Tutorials are available on the all things NC1 post. This will require root and installing a custom rom. Your warranty (if still applicable) will be void if you choose to do this. Regardless, the software on the device is not well optimized and the touchwiz UI is unnecessary imo. The GPE rom also does not have the samsung or at&t bloatware.
cxzzcx said:
I would suggest getting the Google Play Edition rom as stock android is much better optimized. Tutorials are available on the all things NC1 post. This will require root and installing a custom rom. Your warranty (if still applicable) will be void if you choose to do this. Regardless, the software on the device is not well optimized and the touchwiz UI is unnecessary imo. The GPE rom also does not have the samsung or at&t bloatware.
Click to expand...
Click to collapse
The google play ROM I would not mind, but I cant seem to find a way to root my SG4 NC1 firmware.
Do you happen to have a link or directions, please?
Thanks...
Cornelp said:
The google play ROM I would not mind, but I cant seem to find a way to root my SG4 NC1 firmware.
Do you happen to have a link or directions, please?
Thanks...
Click to expand...
Click to collapse
you can root using geohot's towelroot.
Cornelp said:
The google play ROM I would not mind, but I cant seem to find a way to root my SG4 NC1 firmware.
Do you happen to have a link or directions, please?
Thanks...
Click to expand...
Click to collapse
Use the "All things ATT" link rugmankc gave you. In the first posts in that thread you will get links to the root method, safestrap, and a list of compatible ROMs. A few thoughtsL
1. Before making any changes to you phone, charge it to 100 %, unplug the charger, and let it sit idle for some number of hours. Then check to see what services are using most of the power. For a while my own 4.4.2 GS4 was slow, and it turned out to be google play framework services bogging things down, and this showed up as an excessive battery drain during idle. If you phone uses more than say 0.5% battery per hour when completely idle / screen off (but with cell and wifi on), something's up. Fix it and maybe your problems will resolve.
2. Next step: back up any data / photos etc. and do a factory data reset from the settings menu. After it has been reset, perhaps whatever problem is going on will be cleared up.
3. You don't need to root the phone to ODIN a stock firmware (NB1 then flash update to NC1). Links are on the ALL Things ATT thread. This should take it all the way back to proper NC1, bypassing any mess that might have happened if you got a corrupt flash during your OTA update.
If the phone still performs so poorly as you describe after a flash back to stock, there's a problem that's more than the OS/ROM. Sure, the stock build is a bit laggy and bloated, but it's not so bad as what you are seeing.
If you find a restored stock ROM to be better but still laggier than you like, I have had good results with the GoldenEye ROM, flashed according to the instructions in the ATT thread. To flash, you must first root and install safestrap (selinux mode changer set to permissive may be required). You then boot to the safestrap recovery, wipe everything but the SD card, then flash the rom, SuperSU, ATT Module, and ATT BuildProp/APN. That should get you up and running on a new ROM.
I'm a died in the wool geek but I read through this forum and others for two weeks before attempting... but I'm very happy with the phone as it works on GoldenEye. I'm on V36, but V38 is current.
Good luck
Frankenscript said:
Use the "All things ATT" link rugmankc gave you. In the first posts in that thread you will get links to the root method, safestrap, and a list of compatible ROMs. A few thoughtsL
1. Before making any changes to you phone, charge it to 100 %, unplug the charger, and let it sit idle for some number of hours. Then check to see what services are using most of the power. For a while my own 4.4.2 GS4 was slow, and it turned out to be google play framework services bogging things down, and this showed up as an excessive battery drain during idle. If you phone uses more than say 0.5% battery per hour when completely idle / screen off (but with cell and wifi on), something's up. Fix it and maybe your problems will resolve.
2. Next step: back up any data / photos etc. and do a factory data reset from the settings menu. After it has been reset, perhaps whatever problem is going on will be cleared up.
3. You don't need to root the phone to ODIN a stock firmware (NB1 then flash update to NC1). Links are on the ALL Things ATT thread. This should take it all the way back to proper NC1, bypassing any mess that might have happened if you got a corrupt flash during your OTA update.
If the phone still performs so poorly as you describe after a flash back to stock, there's a problem that's more than the OS/ROM. Sure, the stock build is a bit laggy and bloated, but it's not so bad as what you are seeing.
If you find a restored stock ROM to be better but still laggier than you like, I have had good results with the GoldenEye ROM, flashed according to the instructions in the ATT thread. To flash, you must first root and install safestrap (selinux mode changer set to permissive may be required). You then boot to the safestrap recovery, wipe everything but the SD card, then flash the rom, SuperSU, ATT Module, and ATT BuildProp/APN. That should get you up and running on a new ROM.
I'm a died in the wool geek but I read through this forum and others for two weeks before attempting... but I'm very happy with the phone as it works on GoldenEye. I'm on V36, but V38 is current.
Good luck
Click to expand...
Click to collapse
Thank you very much for your help. Yeah everytime I redo my phone, from scratch, it works OK for about an hour. Then bam, it goes back to being a low pain in the rear. This is ONLY after the phone upgraded to 4.4.2. I didn't choose that upgrade, actually I didn't want to upgrade, but OTA upgrade took over and BAM, I got screwed.
OK I just installed the Safestrap and rooted the phone. Now I gotta figure out the rom part.
Im still going thru that link that rugmankc gave me above. Now im trying to figure out how to change the OS, since I just rooted the phone. I have to do this. Ive gotten really really tired of the phone being so slow, I basically give up on many tasks that I need to do, just cause its too slow.
Ill update once I get it figured out, hopefully I wont brick it, that's the only thing that im afraid of.
Don't remember, did you consider Odin back to stock and start over. If not, whatever was causing the slow downs may still be there. Could have been a bad update.
Read the SafeStrap thread by HashCode carefully. I read the OP 100% and last 30 pages or so of thread and don't even use it. It is complicated to me. IE which slot to flash to stock or rom. I think stock, Flash Modules. Install Selinux and set to permissive. And using correct SafeStrap. Gives me a headache and I am not even needing to use it--
Good Luck--as mentioned just backup whenever you can before moving to next major step. :good::good:
rugmankc said:
Don't remember, did you consider Odin back to stock and start over. If not, whatever was causing the slow downs may still be there. Could have been a bad update.
Read the SafeStrap thread by HashCode carefully. I read the OP 100% and last 30 pages or so of thread and don't even use it. It is complicated to me. IE which slot to flash to stock or rom. I think stock, Flash Modules. Install Selinux and set to permissive. And using correct SafeStrap. Gives me a headache and I am not even needing to use it--
Good Luck--as mentioned just backup whenever you can before moving to next major step. :good::good:
Click to expand...
Click to collapse
Thank you. Actually I backed up my phone already, as I reformatted it last night again. I don't know how to Odin back to stock. What is that? Is that a stock Android? Sorry I don't know.
Thanks...
It's in the same All Things ATT, MK2 thread under Returning to Stock Odin. An option if you still have issues. Takes you back to stock NB1, firmware and all. Kinda like your update, but think you may have got a bad update. Other options are to wipe internal in case bad stuff still there. Frankenscript was pretty thorough--:good:
SafeStrap is how you are going to flash a new OS/Rom. You can't flash custom kernels and aosp roms unless TW based like a couple GPE mentioned.
Read/Scan the two mentioned threads, as in OP and first and last couple dozen pages. Probably the last are more important. You will see folks asking the same questions you will eventually ask. I have read thousands of pages over the years and it has kept me out of trouble--most of the time--
rugmankc said:
It's in the same All Things ATT, MK2 thread under Returning to Stock Odin. An option if you still have issues. Takes you back to stock NB1, firmware and all. Kinda like your update, but think you may have got a bad update. Other options are to wipe internal in case bad stuff still there. Frankenscript was pretty thorough--:good:
SafeStrap is how you are going to flash a new OS/Rom. You can't flash custom kernels and aosp roms unless TW based like a couple GPE mentioned.
Read/Scan the two mentioned threads, as in OP and first and last couple dozen pages. Probably the last are more important. You will see folks asking the same questions you will eventually ask. I have read thousands of pages over the years and it has kept me out of trouble--most of the time--
Click to expand...
Click to collapse
Man, that link really got me confused as heck lol. Ive been reading that link the entire weekend and still im a bit confused.
I rooted the phone with towelroot. Ive installed SafeStrap, but it worked the first time I ran it. Now if I want to run it again it crashes my phone. Not sure what that is about.
Either way, now my understanding is that I should be able to download a rom for my phone and flash it. From that link that I was given, its very confusing.
Could someone PLEASE PLEASE help me here with this?
My phone is an AT&T US SG4. Here are the details:
SAMSUNG-SGH-I337
Android 4.4.2
BaseBand I337UCUFNC1
Kernel Ver 3.4.0-1125940
Build # KOT49H.I337UCUFNC1
Which ROM can I use for my phone? As long as its stock, I don't care which version, Google Play ROM or CY or Golden, whichever, as long as I get rid of this crappy Samsung and AT&T stuff off my phone.
Could someone please help me out here? I know that link says everything, but jeez, im trying to make sense of it, and so far, I got the phone rooted, but just cant figure out the ROM part.
Thanks...
I can't help with specifics as I don't need SS.
Make sure you have correct SS--3.72, afaik
Flash, I believe, to stock slot not rom slot but confirm that
Install Selinux app from Play and set Permissive--afaik
The above items are things people get into trouble with, so reconfirm them
Just keep reviewing the thread and the SafeStrap thread in Dev section by HashCode. Maybe go back more pages from end of threads as you have time. You can post in All things thread now for help and at 10 posts in Dev section. It will come together in time--:good:
Flash roms only for you build, think there is a list within that thread or another one in General or Q&A.
iB's Goldeneye 38 is good and you can use the Aroma to select SafeStrap and the Slimmed down version.
Read his SS flashing instructions first.
Make sure you use SafeStrap recovery to wipe ALL--System/Data/Caches before flashing--:good:
Cornelp: Having recently been through all this, I wrote up a short summary with some links for another user, and it might help you to look through it. It's an overview written from my end-user perspective, not a replacement for the detailed posts the devs have done.
However, based on your description, I would say the best thing to do is ODIN back to stock because I have a sneaking suspicious you got a bad OTA flash. It happens. Going back to stock will be the best way to eliminate that as a source of problems. Learn how in the All things ATT thread OP.
Best of luck to you!
Marc
Frankenscript said:
Cornelp: Having recently been through all this, I wrote up a short summary with some links for another user, and it might help you to look through it. It's an overview written from my end-user perspective, not a replacement for the detailed posts the devs have done.
However, based on your description, I would say the best thing to do is ODIN back to stock because I have a sneaking suspicious you got a bad OTA flash. It happens. Going back to stock will be the best way to eliminate that as a source of problems. Learn how in the All things ATT thread OP.
Best of luck to you!
Marc
Click to expand...
Click to collapse
Frankenscript,
Thank you very much, I will read up on that link you gave me. How would I ODIN back to stock? Do you have specific details on that? I did read something about that on the All things ATT, but wasn't clear.
Thanks...
Cornelp said:
Frankenscript,
Thank you very much, I will read up on that link you gave me. How would I ODIN back to stock? Do you have specific details on that? I did read something about that on the All things ATT, but wasn't clear.
Thanks...
Click to expand...
Click to collapse
Complete instructions here:
http://forum.xda-developers.com/showpost.php?p=51130818&postcount=5
Basically, download ODIN to your PC, run it, get phone into download mode, connect phone to PC via USB, in ODIN select the NB1 file, tell it to start. When done, reboot phone. Then flash the NC1 update from an SD card using stock recovery.
A good pictorial description of how to flash can be found in this S3 thread here:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
Though for a different phone (the S3, not our S4), the process is still the same.
Good luck. I'm headed off to a work trip and won't be on the forum much this week!
Frankenscript said:
Complete instructions here:
http://forum.xda-developers.com/showpost.php?p=51130818&postcount=5
Basically, download ODIN to your PC, run it, get phone into download mode, connect phone to PC via USB, in ODIN select the NB1 file, tell it to start. When done, reboot phone. Then flash the NC1 update from an SD card using stock recovery.
A good pictorial description of how to flash can be found in this S3 thread here:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
Though for a different phone (the S3, not our S4), the process is still the same.
Good luck. I'm headed off to a work trip and won't be on the forum much this week!
Click to expand...
Click to collapse
Thank you all. I was able to revert back to the NB1 stock, but it failed the first time. I had to download and install the NB1 Rootable Odin. For some reason, the NB1 Odin didn't work, but the Rootable one worked.
So im glad I was able to go back. Now I just gotta test it and see if it does slow down as it did before. I will post update, in case anyone else has the same problem, maybe this would be a good solution.
Thanks again to all of you guys, really appreciate it. I really hope it worked.

New OTA update today

Hey guys, thought I would make a discussion thread about the new update today for the Sprint S5's. Looks like todays update was just over 200 MB. I don't know if it affects the latest chainfire root yet or not.
But yeah, make your stock S5 search for a update and you should find one waiting.
I've noticed:
The Android Security Patch Level is now December 1, 2016
Software version is now G900PVPU3CPL2
Do we know how long Samsung will continue to update our phone OTA? I appreciate that we still have support. It's not so bad being 1 month behind in security updates since even with security updates we are still vulnerable to 0-day exploits anyway.
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
KIES
The~Skater~187 said:
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
Click to expand...
Click to collapse
The best way to actually try and get this is through Kies or SmartSwitch apps. Sam Mobile does not have this, and it would be, about another month from now, till they even have it... Been there too many times looking for this so call update.
I know that is does state 01dec2016 security update. I also know, that Knox is added to (at least, all Knox is added data (Kbs, not Mbs) I also believe, they (Samsung, tech side phone updates) have added more apps for Knox. However, we don't have anything that is related to these new updates. heck 2 of them, state they have DATA. Through the stock app manager, you have an option, to erase this, because it is not installed....
not sure if this helps you find what you are looking for. ...
( me 2cents on this),... Why extra apps and data../. Why do we have to download a complete new Stock Rom, when we already were stock anyway ???) (Me dog did a real number on the phone. had to be a good eBay and Amazon shopper... Completely rebuild my S5.
Wondering if the S5 will be having A real update, such as 7.1... ??? !!!) we S5, was not on or in the press release early this month, regard the Samsung, Android updates... 7.0, 7.1 NOUGAT !!!
I certainly believe that they will in time update the S5 to 71 Nougat
This may just be a hunch but I have a feeling that if the Note 8's don't blow peoples faces off that the S5 probably won't be seeing Nougat officially (from Sammy).
Well there's a new update today for me anyways. This one is just over 27 MB's. 2 new updates in one month!
The new software version is called G900PVPS3CQA2
New antutu score updated.
It's very unlikely that S5 will receive an official N OTA from any carrier(or any msm8974, for that matter) as Qualcomm had planned 'no official support' for msm8974 past M. It was already very late in the cycle for M, and may not have made it onto the list for M had the msm8994 sucked less.
Does anybody know if we are still able to root our phone model with this new update?
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
I don't know for sure myself, as I have not gotten the update bring on aftermarket firmware. But I would imagine if you flash twrp and apply the latest supersu, it should work. I know that's how I did it with the cpk1 update.
Someone please correct me if I am wrong. I don't want anyone bricking their device based on what I've said.
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Cmicasa the Great XvX said:
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Click to expand...
Click to collapse
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
You can always see the latest official stuff for our phones here: https://www.sammobile.com/firmwares/database/SM-G900P/SPR/
The only way we'll ever see Nougat on the S5 is via rom ports, or CM14/CM14.1 Official, which is supporting the S5.
LEN671 said:
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
Click to expand...
Click to collapse
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Cmicasa the Great XvX said:
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Click to expand...
Click to collapse
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
LEN671 said:
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
Click to expand...
Click to collapse
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Cmicasa the Great XvX said:
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Click to expand...
Click to collapse
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
LEN671 said:
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
Click to expand...
Click to collapse
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Cmicasa the Great XvX said:
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Click to expand...
Click to collapse
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
LEN671 said:
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
Click to expand...
Click to collapse
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Cmicasa the Great XvX said:
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Click to expand...
Click to collapse
Okay, I am just making sure as I am not sure if that was one of reasons why Odin came back saying "FAIL". Thank you again.

ATT I-337 running GoldenEye and having major issues.

My Prior thread: https://forum.xda-developers.com/galaxy-s4-att/help/n00b-sgh-i337-running-original-kernel-4-t3850783
I obtained a stock MDL i337 S4 running 4.2.2 and following the instructions in the prior thread I rooted with TowelRoot and updated to Lollipop 5.0.1/ GoldenEye and I've had nothing but problems ever since, so much so that the phone has almost gotten me lost in Oakland and has made me late for work twice!
The phone freezes, sometimes randomly reboots, shuts down applications without reason or warning (LIKE MY ALARM CLOCK!!!), apps can freeze while in use (like Google Maps at a critical time!), it eats power like me at a Chinese buffet and runs hot sometimes, apps are slow to load or won't load (sucks when a call comes in. By the time I am able to answer it, the caller has hung up!), app updates hang, and more. I suspect that part of the issue is that the instructions I got for rooting it and installing a custom ROM were a bit different than those of the GoldenEYe dev (who abandoned his project years ago and no longer answers questions) but I'm not sure.
The first time I did the upgrade, it froze at the Samsung screen for almost 30 min and I had to start over. Then when it was complete the phone was almost unusable. I read that there were issues with SuperSU so I started uninstalling some of the dev apps (I really don't know what the hell I'm doing but was desperate) and when I disabled SuperSU and did clean up to switch to another superuser app" then thought I uninstalled it and all the problems seemed to go away. A few days later while doing something else in the play store, I find that SuperSU is running even though it no longer shows in my apps! So thinking something nefarious was going on, I uninstalled it via the play store and my phone was back to being hosed again. Ok, yes I'm an idiot and deserved that.
I go back to the beginning and started all over AGAIN, reinstall/upgrade but with a different kernel (thinking maybe that?, I tried leaving my apps and settings but that didn't take. Any clue how many times I've now configured my email and office tools? lol) and ended up with what I have now, ie the issues above. I thought about trying to just somehow go back to stock 4.2.2 then just finding the stock ATT Lollipop firmware and saying to hell with root but those instructions are not clear and most post links to the firmware are now dead (I REALLY don't want to brick my phone. I have no money for another and I need my phone for my job). I'd really like to go above Lollipop if at all possible but would be happy just to have GoldenEye work!
Does anyone have any idea what the heck is going on with my phone and how I fix it? This is a serious problem for me.
SGi337
Android 5.0.1
Baseband I337UCUAMDL
Kernel Ver: 3.4.0-S4-AELKerel-v4.3-LP [email protected] #36 Wed Apr 8 19:56:06 EEST 2015
Build number LRX22C.I9505XXUHOD7
Rom Ver: GOLDENEYE 53 XXUHOD7
Dev iB4STid
SuperSU PseudoPro (had Pro, didn't reinstall it the last time) is installed but disabled
ES Task Manager and ES File Manager
Titanium Backup Pro
And so we meet again! Okay so forget golden eye. What you should do is get ODIN for your PC. Then get the MDL firmware and flash it with ODIN by connect your phone to your PC. You might also need Samsung Kies for your PC for this as it has the drivers for your phone.
Once you're back on Android jelly bean, use towel root to root, install Loki, install clockwork mod or TWRP recovery (for TWRP go here https://forum.xda-developers.com/showthread.php?t=2262996 and for clockwork mod just use my guide again).
Then flash this:
https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
This will give you the latest stock Rom for your phone. It's from AT&T but has been modified to work with the MDL bootloader so it doesn't patch the Loki exploit.
Also remember that you need superSU installed or else you won't have any root management for your root apps.
Hi! lol
Any idea why this is happening? I'd really like to go to something like Marshmallow or the like but if stock is it, that will have to do.
I tried finding the MDL firmware but so far all the links are old dead ones. Have you seen anything more current?
StoneyJSG said:
And so we meet again! Okay so forget golden eye. What you should do is get ODIN for your PC. Then get the MDL firmware and flash it with ODIN by connect your phone to your PC. You might also need Samsung Kies for your PC for this as it has the drivers for your phone.
Once you're back on Android jelly bean, use towel root to root, install Loki, install clockwork mod or TWRP recovery (for TWRP go here https://forum.xda-developers.com/showthread.php?t=2262996 and for clockwork mod just use my guide again).
Then flash this:
https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
This will give you the latest stock Rom for your phone. It's from AT&T but has been modified to work with the MDL bootloader so it doesn't patch the Loki exploit.
Also remember that you need superSU installed or else you won't have any root management for your root apps.
Click to expand...
Click to collapse
I have no idea why golden eye is giving you issues. It works fine for me and you followed my guide just like I did. Anyway, you can goto marshmallow but it'll be AOSP based rather than touchwiz based so the look and feel will be way different than that of golden eye or any other stock Samsung ROM.
You can also just try going into clockwork mod and do a wipe (I forgot the sequence, it's wipe system, data, cache I THINK but it's in my guide on the order of how to do it) for a clean install of a ROM from there. This will eliminate the need for ODIN. You should however, keep ODIN on standby in case anything goes south you can go back to how the phone was when you first got it. I have the ODIN MDL firmware on a USB drive, let me find it over the weekend and upload it to my Google drive and will link you to it.
SilkRoadDog said:
I tried finding the MDL firmware but so far all the links are old dead ones. Have you seen anything more current?
Click to expand...
Click to collapse
Hey dude, here's the link to the MDL firmware for ODIN off my Google drive: https://drive.google.com/file/d/1ZXv9FAcDbfkbFZzh078SSMZ85jbMVPSx/view?usp=drivesdk
StoneyJSG said:
Hey dude, here's the link to the MDL firmware for ODIN off my Google drive: https://drive.google.com/file/d/1ZXv9FAcDbfkbFZzh078SSMZ85jbMVPSx/view?usp=drivesdk
Click to expand...
Click to collapse
Well after putting up with the phone issues for 2 months, I reset everything following your instructions to the best of my abilities (except couldn't get towelroot to load so went with another). Let's see how this works! lol
Your instructions say "SuperSU will kill the evil KNOX for you." What is that and how do I do this?
SilkRoadDog said:
Your instructions say "SuperSU will kill the evil KNOX for you." What is that and how do I do this?
Click to expand...
Click to collapse
Once rooted, goto the Google play store and download the SuperSU app, open it and it will ask you some stuff then do the rest. Towel root needs internet access to work. I was starting to have issues with golden eye rom off and on until I flashed the OC3 modem, you may wanna try that after you get back to golden eye.
There's also another ROM on here called i337_OC3_stock_rooted_rom(MDL) , you may want to try it out as it's 100% stock and hasn't been modified like golden eye rom has. I am not sure it works with clock work mod recovery so you might need TWRP recovery for it.

Categories

Resources