Database Users

STOCK and ROOTED SGH-I257M

Thanks to @spyke555 for his backup copy of the Rogers version of the SGH-I257M firmware. I managed to root it with vroot, so there is a chinese version of SU on there but it works. I also stuck busy box on it and tried to get rid of most of Rogers apps.
Now to use this, you must stick it into your backup folder (i.e: clockworkmod/backup) it is NOT a flashable rom, it is a backup. If anyone wants to turn it into a flash rom, or create custom roms out of it, please do. Need to see some I257M roms popping up.
Dropbox
Box.com
G Drive
We also have @dsavard copy of the stock firmware from Koodo, which you can flash with Odin
Dropbox
Mirror 1
And here we have all of the STOCK and UNROOTED firmware for the Canadian I257M over at Sammobile
All vroot does is give root access without changing the rom. It uses the chinese program Superuser 1.0.4. You can get rid of this by following these steps:
Go to play store and install SuperSU.
Start SuperSU and you will be asked for permission by Superuser 1.0.4, choose 允许(means allow). (Should be the right side option.)
SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
Now, freeze Superuser 1.0.4 in titanium backup, just in case you need it again.
Note: If you uninstall straight away from app manager, you need to make sure SuperSU updated the binary.
Re-run SuperSU to make sure everything is alright. You will be prompt again to install SU binary, just do what it asked.
After that, you are rooted with SuperSU and Superuser 1.0.4 will not be there anymore.
Once you do that, SuperSU will be the default and will be in english.

Good to see this here. I just picked up my S4 Mini today. I'm from Canada so I'm assuming it's a slightly different version than the other models? Cause mine in an SGH-1257M. Is it a different process to root it?
I'm not too familiar with vroot. My last phone was an HTC Evo 3D.

Skyty said:
Good to see this here. I just picked up my S4 Mini today. I'm from Canada so I'm assuming it's a slightly different version than the other models? Cause mine in an SGH-1257M. Is it a different process to root it?
I'm not too familiar with vroot. My last phone was an HTC Evo 3D.
Click to expand...
Click to collapse
vroot is like SRS or any other one touch root program, but it's in chinese. Easy to use and has a high success rate for most phones. the I257M is slightly different from what we can tell from the other models; different features. As far as I can tell there isn't a different way to root this but I'm not to sure how the others were rooted. I also don't know if there is anything different between the Bell, Rogers, Fido, etc. versions besides their own bloatware. I hope I can get all the different versions uploaded.

Omega2513 said:
vroot is like SRS or any other one touch root program, but it's in chinese. Easy to use and has a high success rate for most phones. the I257M is slightly different from what we can tell from the other models; different features. As far as I can tell there isn't a different way to root this but I'm not to sure how the others were rooted. I also don't know if there is anything different between the Bell, Rogers, Fido, etc. versions besides their own bloatware. I hope I can get all the different versions uploaded.
Click to expand...
Click to collapse
Yeah, I have a Rogers phone. Just got it yesterday.
Is there a guide on here how to root with vroot? I'm not too good at rooting and whatnot. I've only done it once on my Evo 3D and that was more than a year a go haha!

Just google it. The vroot forum has step by step with pictures
Sent from my SGH-I257M disguised as a GT-I9195

hey can someone help me?
i have a telus version and i would like to back mine up and post an image for you guys. we can then update the first post with the different carrier versions if we ever need to go back to stock for warranty purposes. i'd also like to see if there are different files from the carriers.

Omega2513 said:
Just google it. The vroot forum has step by step with pictures
Sent from my SGH-I257M disguised as a GT-I9195
Click to expand...
Click to collapse
Will do!
Edit: So I found this post:
http://forum.xda-developers.com/showthread.php?t=2455822
It mentions select the drivers for your phone? Is the S4 Mini supported?

infamouskid said:
hey can someone help me?
i have a telus version and i would like to back mine up and post an image for you guys. we can then update the first post with the different carrier versions if we ever need to go back to stock for warranty purposes. i'd also like to see if there are different files from the carriers.
Click to expand...
Click to collapse
There are forums here on how to temporarily give root and install CMW to make a backup.

Well, I just rooted my phone using VROOT. It is still recognized as an SGH-I257M. However, when any of my apps update it's all in Mandarin (I think?). Would I simply use the backup you posted? Would that solve that issue?
Will the I9195 roms work with phone even though I didn't root it as a I9195?

Skyty said:
Well, I just rooted my phone using VROOT. It is still recognized as an SGH-I257M. However, when any of my apps update it's all in Mandarin (I think?). Would I simply use the backup you posted? Would that solve that issue?
Will the I9195 roms work with phone even though I didn't root it as a I9195?
Click to expand...
Click to collapse
All vroot does is give root access without changing the rom. It uses the chinese program Superuser 1.0.4. You can get rid of this by following these steps:
Go to play store and install SuperSU.
Start SuperSU and you will be asked for permission by Superuser 1.0.4, choose 允许(means allow). (Should be the right side option.)
SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
Now, freeze Superuser 1.0.4 in titanium backup, just in case you need it again.
Note: If you uninstall straight away from app manager, you need to make sure SuperSU updated the binary.
Re-run SuperSU to make sure everything is alright. You will be prompt again to install SU binary, just do what it asked.
After that, you are rooted with SuperSU and Superuser 1.0.4 will not be there anymore.
Once you do that, SuperSU will be the default and will be in english.
You can use the backup that I posted but it would be the same as your stock rom. The backup is just for those who don't want to root their own rom, doesn't trust the program, etc. The I9195 roms will still work, but when you flash them, your phone will recognize itself as a GT-I9195 instead of SGH-I257M

Sorry for bumping this, but I wanted to ask, did you have any trouble installing CWM after you rooted with VROOT?
It keeps telling me that SGH-I257M is unsupported.

What I did was use the I9195 rooting method to get CWM installed then switch back with I257M backup. It turns your phone back to I257M but CWM stays installed. You could also try installing twrp
Sent from my SGH-I257M disguised as a GT-I9195

Omega2513 said:
What I did was use the I9195 rooting method to get CWM installed then switch back with I257M backup. It turns your phone back to I257M but CWM stays installed. You could also try installing twrp
Sent from my SGH-I257M disguised as a GT-I9195
Click to expand...
Click to collapse
Ah... that's why I'm having issues. I'll look into TWRP.
Edit: Just tried TWRP. No luck.
It wouldn't backup my ROM. Just booted me into recovery with no option of backing up.
Edit #2:
Slowly figuring this out. I unrooted my phone and re-rooted with the I9195 method. I now have CWM.

What I think it is, the I9195 method unlocks the bootloader where just rooting the I257M doesn't do that
Sent from my SGH-I257M disguised as a GT-I9195

Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942

dsavard said:
Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942
Click to expand...
Click to collapse
Hmm... good to know... thanks!
I unrooted my phone and re-rooted via the I9195 so I could get CWM. Hopefully it removed anything that VROOT left.

dsavard said:
Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942
Click to expand...
Click to collapse
Thanks for the info. I didn't realize that was possible

@Omega2513 As a safer alternative, why not install the S4Mini_RootKit_v1.zip from arco68 (http://forum.xda-developers.com/showthread.php?t=2364980) from CWM Recovery ? It is the same for all s4 mini (I9190, I9192 and I9195), so I suppose it will work for the SGH-I257M too.

It's possible it could work. Never tried it, but since it does the other models, I don't see why not.
Sent from my SGH-I257M disguised as a GT-I9195

I've got a backup of the latest Koodo SGH-I257M stock firmware [MK5 (KDO)]) by following this recipe:
​http://forum.xda-developers.com/showthread.php?p=23188887
I've uploaded it online for anyone who could need it :
​[EDIT: Download not available anymore. Anyway the firmware is now available on Sammobile.]
It seems to be in the same format than firmwares found on the sammobile web site. So, it could be useful for those who wish to revert to stock with Odin... and know how to do it.

[Q] Rooting w/Kingo App Question

Please forgive me if this has been discussed elsewhere. I could not locate it. Anyways, I have the Verizon Samsung Galaxy Note 3 with the latest software...Android 4.3, build MJE. My goal is to hopefully root the device and then install SS to add a ROM. Previously I have the Galaxy S3, which was running a custom ROM. I had no problems with my S3. Since the boot loader of the Note 3 is locked, it's not as easy to do. I keep reading about using Kingo but I'm not sure if it will actually will work with this phone. Has anybody out there successfully rooted their phone with Kingo? Please respond if you have. I have a free day and would love to spend it customizing my phone.
Thanks!

tss01 said:
Has anybody out there successfully rooted their phone with Kingo? Please respond if you have. I have a free day and would love to spend it customizing my phone.
Click to expand...
Click to collapse
Yes. It was really not difficult although it took me a few tries to successfully get SS working. Although Kingo kept saying I was rooted, SS said I was not rooted and it did not have SU access. I just removed SS and SU and un-rooted and tried again. The 3rd time it just worked. In hindsight I think I was having a problem with the cable, that came with the phone, maintaining a USB connection.

Rooting w/Kingo
Hi,
I went ahead to gave it a shot. First I made sure my anti-virus was disabled then I started Kingo and following the onscreen prompts. I automatically downloaded needed drivers. It then told me to re-connect my phone. I did and within a couple of minutes I get "ROOT Failed Not Support". I tried it two more times with the same result.
Any suggestions on my next step cuz I'm out of ideas.
Thanks!

I used it successfully last night, but on MJ7, not MJE.
I didn't read very carefully and had my phone in download/Odin mode.
Kingo recognizes that and attempted exploits against the bootloader - which failed.
So I booted the phone (with ADB / USB debugging on), and Kingo automatically recognized that and succeeded.
Just mentioning in case that's what is going on.

I've used it twice now, most recently about 12 hours ago. Haven't had a problem doing it. Worked first try both times. Normally booted with USB debugging enabled, connected and ran the program. Windows 8.1 laptop. Verizon GN3 fresh odin of MJE and am now rooted with SS installed and running Beans B6 on the stock slot.
Did you get this situated OP? We would love to help get you up and running so you can customize away.

Rooting w/Kingo
There must be some special trick to get Kingo to work properly. I did disable my anti-virus on my computer. I forgot that I have an anti-virus program on my phone as well. Should I disable that also? Is there some special way that I need to install my drivers? I'm really lost right now.
Thanks, for any help.

tss01 said:
There must be some special trick to get Kingo to work properly. I did disable my anti-virus on my computer. I forgot that I have an anti-virus program on my phone as well. Should I disable that also? Is there some special way that I need to install my drivers? I'm really lost right now.
Thanks, for any help.
Click to expand...
Click to collapse
Kingo should install the drivers for you. As far as the anti virus on your phone that could be a problem. I've never tried when I wasn't bare bones stock before I installed anything. Are you adverse to doing a factory reset and trying from scratch, I mean thats what you are doing after you root anyways right?, or are you wanting root to use titanium or whatever to backup everything before you use SafeStrap?
I would reboot everything, disable both Anti-Virus, make sure USB debugging is enabled and run Kingo again. You may have to run as administrator. Keep watching during the process and your phone will prompt you to allow USB debugging for your computer and then it will prompt you again to allow unknown source installs and then after the reboot the phone will prompt one more time for root right to finalize the process.

I was able to root with Kingo on the latest built MJE. It worked for me on the first try. Try another computer if you can.
Does anyone know if there is a way to remove the Custom text with the padlock from the splash screen?
Sent from my SM-N900V using Tapatalk

mexiking713 said:
I was able to root with Kingo on the latest built MJE. It worked for me on the first try. Try another computer if you can.
Does anyone know if there is a way to remove the Custom text with the padlock from the splash screen?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Use Wanam and check "fake system status" reboot a couple times and it will be gone.

GrandMasterB said:
Use Wanam and check "fake system status" reboot a couple times and it will be gone.
Click to expand...
Click to collapse
I tried that but it didn't work. I rooted while on the official MJE with Kingo. I installed SafeStrap recovery and I'm running CleanRom. It's no big deal but it would be nice to be able to get rid of it.
Sent from my SM-N900V using Tapatalk

Just as a note for people using this method. I tried it it told me it failed but it actually worked. I don't understand the reasoning behind it but all I know is that it worked. Way easier than de LA Vega. Which used to be easy. Lol. I still prefer Odin and CF auto root. But kingo works
Sent from my SM-N900P using xda app-developers app

mexiking713 said:
I tried that but it didn't work. I rooted while on the official MJE with Kingo. I installed SafeStrap recovery and I'm running CleanRom. It's no big deal but it would be nice to be able to get rid of it.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
You made sure to install/activate Xposed framework, then reboot, then activate the Wanam Module and reboot again? Just asking because I've never had it not work for me and I've done it a dozen times or more between the AT&T Galaxy Note 3 and now the Verizon Galaxy Note 3.

GrandMasterB said:
You made sure to install/activate Xposed framework, then reboot, then activate the Wanam Module and reboot again? Just asking because I've never had it not work for me and I've done it a dozen times or more between the AT&T Galaxy Note 3 and now the Verizon Galaxy Note 3.
Click to expand...
Click to collapse
I have other mods running from Wanam right now but that particular one doesn't work. Bummer
Sent from my SM-N900V using Tapatalk

tss01 said:
Hi,
I went ahead to gave it a shot. First I made sure my anti-virus was disabled then I started Kingo and following the onscreen prompts. I automatically downloaded needed drivers. It then told me to re-connect my phone. I did and within a couple of minutes I get "ROOT Failed Not Support". I tried it two more times with the same result.
Any suggestions on my next step cuz I'm out of ideas.
Thanks!
Click to expand...
Click to collapse
If you're still having issues, check the link in my sig. Step by step instructions to get you up and running. Basically fool-proof

MJE TAR File - Question
Hello again:
I'm alittle confused about the need to Oden the MJE Tar file. I am already at MJE (from Verizon) and wonder why I would need to install this? I am Jelly Beans Build 6 installed and it appears to be working just fine. I also have HyperDrive installed and it appears to be working "ok" so far but time will tell. I did have a problem getting my phone to connect to my car via bluetooth but will try this again when I go out this morning.
Thanks!

tss01 said:
Hello again:
I'm alittle confused about the need to Oden the MJE Tar file. I am already at MJE (from Verizon) and wonder why I would need to install this? I am Jelly Beans Build 6 installed and it appears to be working just fine. I also have HyperDrive installed and it appears to be working "ok" so far but time will tell. I did have a problem getting my phone to connect to my car via bluetooth but will try this again when I go out this morning.
Thanks!
Click to expand...
Click to collapse
If you're already running MJE no need to reflash it in Odin. The Odin step isvfor those still on Mi9 or Mj7.
Notorious 3

Error while trying to update to 4.4 (D800)

Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?

This is my problem too. Hopefully there is a way.
Sent from my LG-D800 using xda app-developers app

Maybe doing a factory reset from stock recovery?
Sent from my LG-D805 using xda app-developers app

rohan611 said:
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
Click to expand...
Click to collapse
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help

antawnm26 said:
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
Click to expand...
Click to collapse
nope. as i said in the OP< i have a stock recovery.

rohan611 said:
nope. as i said in the OP< i have a stock recovery.
Click to expand...
Click to collapse
then try root keeper it will disable root but back up root path and reinstate it once the update is done

antawnm26 said:
then try root keeper it will disable root but back up root path and reinstate it once the update is done
Click to expand...
Click to collapse
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.

rohan611 said:
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
Click to expand...
Click to collapse
lol..yeah i read each statement in your OP just wanted to get to that last part of you saying your going back to stock and going from there, because thats your next option....

Let us know if you went back to stock then did the update and it worked.

I've read that some people kept root through their OTA. Why are some people able to update and others aren't. I've been reading up on this for the VZW update whenever that happens. I hope I haven't kept all this bloatware on my phone for no reason!!
Sent from my VS980 4G using Tapatalk

hinduboy74 said:
Let us know if you went back to stock then did the update and it worked.
Click to expand...
Click to collapse
I reverted back to stock using the instructions in the Stickied post. I was then able to update to D80010o. I had to call to request a rep to push out the D80010q update again though. They're calling it a "security update" so you should use that phrase when talking to the rep so that they don't get confused and think that you're just requesting that they push out the KitKat update.
Once I got the D80010q update, the KitKat update was available and I was able to update. Unfortunately, I didn't try to root it prior to updating - though to be honest, I don't really feel the need to root anymore. Only reason I had it rooted before was to get the multitasking button, but I'm okay with using an S3 layout (Menu, Home, Back) since that's the phone I'm coming from.

I have posted this in Other thread too.. may be this helps (Or save some time)
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.

streetsmart999 said:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o

rohan611 said:
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
Click to expand...
Click to collapse
That is correct. I was on D80010o all four times I updated to Kit-kat and kept root everytime.

streetsmart999 said:
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
Same thing happened to me. I followed your advice in the other thread and did a reset using the LG flash tool, following rootjunky's guide on youtube and using the files from his website. Everything went smoothly except for at the end I got the same check flag error thing, but it completed the reset perfectly.
I then chatted with ATT and had him push the update to my phone which brought me up to d80010o. It finally went through the update and didn't get me the root error. So I think I'm in the green now. He said that he didn't have an option to push the kit kat update to my phone but it told him to have me do it through the software update in the settings. Which I tried and it said it was up to date. But he said that since they roll out in batches my phone might just not be ready for it yet. I will keep trying though and I'm one step further than I was before. At least it let me update. Shout out to ATT though, chat service is on point.

[Q] no wifi rooted at&t S4 4.4.2 NB1

greetings!
I've been searching for hours and bashing my brains trying to get wifi working. It originally broke after an OTA update
tried all the tips and still nothing works permanently. The things I have tried are too numerous to remember or list.
It's not a hardware issue as wifi can work for periods of time but it always breaks - I assume because of an update that downloads and breaks it.
i see talk of reflashing "modules" with safestrap but safestrap has never worked properly and now does not work at all ("unfortunately safestrap has stopped") Can modules be flashed from Odin?
TIA !

Sorry to hear about your troubles man. Been there, done that...
IMHO, if you don't have hardware issues, this what you should do:
ODIN to stock http://forum.xda-developers.com/show....php?t=2616221 (post 1, the Returning to Stock / ODIN section)
After that root
Root with towel root (https://towelroot.com/)
Install SuperSU (PlayStore) and let it disable Knox.
Install BusyBox (PlayStore) and let it cook
Install SELinux Mode Changer (PlayStore). Run and set it to Permissive.
Install Safestrap (http://forum.xda-developers.com/show...php?p=45693712)
Now it's time to flash you favorite rom (Safestrap has the list). Copy the following to your SD card:
Your favority ROM
SuperSU.zip file. (http://download.chainfire.eu/451/Sup...erSU-v2.01.zip)
Your modem zip file (http://forum.xda-developers.com/show...96&postcount=1).
I337 Build.prop/APN (http://forum.xda-developers.com/show...81&postcount=9)

Same boat as well I believe, need help please.
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.

Few screens to help out
Here are a few screen shots that I hope help someone out. Please let me know what I can do if anything.

ONLY DRAGONMIKE said:
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.
Click to expand...
Click to collapse
You won't be able to put cwm on it or cm. See index, all things at&t......in the general forum
Sent from my Nexus 5 using XDA Free mobile app

Ummmm a tiny bit more help please lol
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.

ONLY DRAGONMIKE said:
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.
Click to expand...
Click to collapse
Just click on the spoiler for nb1 need users. The step by step is there. It's in the first post
Sent from my Nexus 5 using XDA Free mobile app

So this one
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.

ONLY DRAGONMIKE said:
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.
Click to expand...
Click to collapse
You're on nb1 and rooted. The next step is to install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app

So Safestrap 3 it is
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.

ONLY DRAGONMIKE said:
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.
Click to expand...
Click to collapse
What's mdf?
Sent from my Nexus 5 using XDA Free mobile app

MDF Reply
Security software Version
MDF v1.0 Release 2

MDF Reply
Here is a screenshot of where I'm talking about. Oh and Safe strap 3.72 is installed perfectly thank you so very much for that. Your awesome. And a lot of people are saying when you reboot and it shows the "Safestrap is disabled" screen you can't get back into it. I did just fine.

ONLY DRAGONMIKE said:
Here is a screenshot of where I'm talking about.
Click to expand...
Click to collapse
You're on nb1 firmware, safestrap is ok
Sent from my Nexus 5 using XDA Free mobile app

NB1 discussion
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.

ONLY DRAGONMIKE said:
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.
Click to expand...
Click to collapse
You can not install any roms. The i337 on any firmware higher than mdl can only flash touch wiz based roms. See the index, all things at&t.... for roms that are compatible.
Sent from my Nexus 5 using XDA Free mobile app

This mini-guide should work!
The problem is, in order to get WiFi working, you need to install the NB1 modules, but to do that, you need to install Safestrap. However, you can not install Safestrap because the app keeps closing on you. There is a simple fix to this, which I will explain later. For now, just read this WHOLE post BEFORE you do anything, and keep in mind that I am NOT held liable if you mess up your phone. Use this at your own risk.
1.) Root your phone
If you're already rooted with something like SuperSU or Superuser, skip this. If not, read ahead. Download and install the Towelroot APK file attached to this post, open it, and click 'make it ra1n'. If your phone didn't reboot, now you have root (they need to trademark that). Now, down below, I also included the APK for SuperSU. Download and install it. Now open it. When you open it, let it install the 'Normal' way, not via the 'TWRP/CWM' way. Also, when it asks you to disable KNOX, say yes, wait a couple of minutes (it will still be loading) and reboot your phone. Open up SuperSU again, click 'Yes' to disable KNOX again, and now you have a good base to start from.
2.) Install Safestrap AFTER fixing the error
The error your are getting is easily fixed. Go to the Play Store and install 'SELinux Mode Changer'. Open it, grant it root access, and change the mode to 'Permissive'. Now, open up Safestrap again (you mentioned you already installed it), and it shouldn't force close. Click 'Install', and if the 'Reboot to Recovery' option below is not grayed out after that then it worked.
3.) Download and install the NB1 modules
On your phone, download the included NB1 modules ZIP file I attached for you, and once that is done you need to reboot. After the Galaxy S4 logo, you'll see a screen that says 'SAFESTRAP: DISABLED' and there will be a little robot. TIP: To enter Safestrap, press the menu button (physical, hardware key) under 'Recovery' at that screen. To continue to Android, press the back key (again, physical) under the 'System' tab. For now, press the menu button under 'Recovery'. Now, click 'Install' which should be in red, click 'Add zips', and navigate to your Downloads folder. Now click on the NB1 modules ZIP you just downloaded. Swipe to install, and reboot. This time, hit the back key under 'System'.
All done!
Now, Android should (and will) boot up, and you'll have working WiFi! If, for some odd reason, you don't have WiFi- do NOT panic! Just search around for the MF3 modules and flash those! All is good, all is good. A lot of this guide was taken from my post about my personal method of SIM unlocking the AT&T Galaxy S4 without the dialer codes or an AT&T SIM. It was just modified a little to work for you.
Remember, hit thanks! :good:

Rogers 4.4.4 roll out has begun!

Just got the notice. Updating now!
About damn time.
Sent from my XT1058 using XDA Free mobile app

Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.

Yay, now do I unroot and try the OTA or do I wait for the full image.

ChrisAG said:
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Click to expand...
Click to collapse
You can? How? I didn't save the link to the release notes, and can't find them now.

thedosbox said:
You can? How? I didn't save the link to the release notes, and can't find them now.
Click to expand...
Click to collapse
Removing provider name from the Status bar:
Settings > Wireless & Networks > More > Mobile Networks > Show Mobile Network (check on or off)

I completely forgot about the carrier being removed. Really cool.
Sent from my XT1058 using XDA Free mobile app

Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.

Steve-x said:
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Click to expand...
Click to collapse
Ugh... I have TWRP on mine. Can I just unroot, or I need to remove TWRP? (read: flash stock 4.4.2...)

OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?

R3dbeaver said:
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
Click to expand...
Click to collapse
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.

Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.

R3dbeaver said:
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
Click to expand...
Click to collapse
If your bootloader is unlocked then it is very simple. Just go to fastboot and flash the TWRP recovery, once flashed you can access it from fastboot. TWRP will load, then you can just select to restart the phone from it and it will ask if you want to root the phone, swipe to confirm and it will do it and restart the phone for you. Once the phone is booted you will need to finish the process - it should prompt you to update SuperSU, I selected the play store option, it downloaded and installed and was done. From there do yourself a favor and install AdAway

waiting for the firmware image..... anybody knows where to get it?

It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.

Steve-x said:
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Click to expand...
Click to collapse
Would you please send the download link when you are convinient? I searched and find this http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25, but looks something wrong with the system.img.

Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Thanks, works a charm, went from rooted 4.4.2 to 4.4.4.
PS- I grew up in Langley.

I don't know if it's dumb luck or not, but I didn't even unroot and was able to accept OTA to 4.4.4.
This is what I did to prepare the phone:
- Uninstall Xposed Framework from within the Xposed installer itself. Left the installer app in place.
- Changed recovery from TWRP back to factory.
- Enabled all apps previously disabled.
At this point my phone was still rooted. I accepted the OTA and everything worked fine.
Afterwards, I re-installed Xposed from the installer app, and re-disabled the apps I don't use. But left the factory recovery in place since I don't have a need to go into TWRP for now.
Everything is working fine.

No Rogers Update?
I just picked up a Moto X (Brand New) It came with 4.2.2 Im with Rogers, It is a Rogers phone , its been 2 hours now still no software update notification. When I try to check manually in about phone, system update. Keeps telling me my device is up to date??
Any one experienced this before? Or am I being to impatient

Now, a dummy question: what is Rogers?

Rogers is the Canadian phone company that's selling the original Moto X