My phone is i9505 from At&T. It is not rooted, and I have upgraded to 5.0.1. How do I root my phone now? o.o Thanks.
liu8651 said:
My phone is i9505 from At&T. It is not rooted, and I have upgraded to 5.0.1. How do I root my phone now? o.o Thanks.
Click to expand...
Click to collapse
If it's a real i9505, use CF Auto Root. Otherwise, if it's one of the many devices showing up with an i9505 ROM but i337 bootloader, you'll have to downgrade to 4.4 and use the keeproot method. Go in to download mode and it should tell you the real model.
Sent from my SGH-I337
Related
Hey fellow XDA members, I have been searching for a way to
root and install a custom recovery on my I337M, but am slightly
confused about this phone, and I don't wanna screw it up.
First off I am on 4.3 - MVLUEMK6. I also have the Knox app.
Am I able to Root using a certain method? I tried Saferoot, but that was a
no go. I have also heard through my searches of "Kingo", which
I'm hoping to try, given it won't turn this S4 into a brick.
Also in the CF-Auto Root Thread, it states near the Downloads,
that AT&T users shouldn't use it, and go figure I'm on Telus. So also a no go..
Can this darn thing be rooted?!?
C.f.will work on the m Version http://forum.xda-developers.com/showthread.php?t=2293800
Sent from my Nexus 5
jd1639 said:
C.f.will work on the m Version http://forum.xda-developers.com/showthread.php?t=2293800
Sent from my Nexus 5
Click to expand...
Click to collapse
Even though it states ATT has locked Bootloader?
Adizzzle said:
Even though it states ATT has locked Bootloader?
Click to expand...
Click to collapse
The i337 at&t has a locked bootloader. The i337m does not.
Sent from my Nexus 5
jd1639 said:
The i337 at&t has a locked bootloader. The i337m does not.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks very much my good sir, I appreciate your insight on this!
the I337M (jfltecan) is NOT the same as the I337 (jflteatt)
i use a I337M (originally bell), cf auto root works perfect
your phone is the same as mine, use cf auto root and flash via odin on pc, it'll work
So I used motochopper when I first bought my S4 and it rooted my phone just fine. After updating to 4.4 kit kat I lost my root status and now I am getting this message about updating my binary code for super user. If anybody has any tips I would much appreciate it.
SGH i337
4.4.2
I337UCUFNB1
you can't direct root anymore
see the general section on the root workaround and downgrade threads by muniz and ted
Root
bigadam2089 said:
So I used motochopper when I first bought my S4 and it rooted my phone just fine. After updating to 4.4 kit kat I lost my root status and now I am getting this message about updating my binary code for super user. If anybody has any tips I would much appreciate it.
SGH i337
4.4.2
I337UCUFNB1
Click to expand...
Click to collapse
Have same trouble with mine also after update to 4.4.2. Yet can run Root Checker and it says its rooted, but it is not. But at least phone works OK, just No Root.
tailgunner9 said:
Have same trouble with mine also after update to 4.4.2. Yet can run Root Checker and it says its rooted, but it is not. But at least phone works OK, just No Root.
Click to expand...
Click to collapse
there currently is no direct root method
Sent from my Deadly Venom SS 3.0 S4 ~ 20GB free cloud https://copy.com?r=vtiraF
S5 Root
tailgunner9 said:
Have same trouble with mine also after update to 4.4.2. Yet can run Root Checker and it says its rooted, but it is not. But at least phone works OK, just No Root.
Click to expand...
Click to collapse
Strange there is root method for new S5 and it is not even released yet, but No Root for phones that has been out for Months with 4.4.2????
tailgunner9 said:
Strange there is root method for new S5 and it is not even released yet, but No Root for phones that has been out for Months with 4.4.2????
Click to expand...
Click to collapse
Not strange, the S5 release is international not the i337 att
tailgunner9 said:
Strange there is root method for new S5 and it is not even released yet, but No Root for phones that has been out for Months with 4.4.2????
Click to expand...
Click to collapse
rugmankc said:
Not strange, the S5 release is international not the i337 att
Click to expand...
Click to collapse
Definitely not strange, specifically because our bootloader is locked and that one isn't. If our bootloader was unlocked we would have had root as soon as our update was released because Chainfire puts out his autoroot for unlocked S4's but we can't flash it since it isn't signed.
DeadlySin9 said:
Definitely not strange, specifically because our bootloader is locked and that one isn't. If our bootloader was unlocked we would have had root as soon as our update was released because Chainfire puts out his autoroot for unlocked S4's but we can't flash it since it isn't signed.
Click to expand...
Click to collapse
Exactly ☺
Sent From My i337 S4 using Tapatalk
Hello, I just got a brand new at&t Samsung Galaxy S4. It is running android 4.4.2 kitkat, I am trying to get into service mode to unlock it. I have tried the *#0011# code and pressed back and entered 1 and nothing happened, I also tried the other code but option number 6 (UTMS) was missing. Any advice on how to unlock my att galaxy s4? Thanks
ntrambitas12 said:
Hello, I just got a brand new at&t Samsung Galaxy S4. It is running android 4.4.2 kitkat, I am trying to get into service mode to unlock it. I have tried the *#0011# code and pressed back and entered 1 and nothing happened, I also tried the other code but option number 6 (UTMS) was missing. Any advice on how to unlock my att galaxy s4? Thanks
Click to expand...
Click to collapse
Did you ever find an answer for this? Does RegionLockAway work?
I can't use regionlockaway because it requires root and my phone is not rooted because there is no root for 4.4.2 kit kat on the att variant
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Hey. I have the same question about sim unlock for ATT Galaxy S4. My phone is running stock NB1. I did downgrade to MK2 and flashed MDL radio (I got hidden menu *#0011#, but unlock didn't work anyways)...finally I did root and installed RegionLockAway and it didn't work too...so I flashed it back to NB1 and stuck with this question
denver_man said:
Hey. I have the same question about sim unlock for ATT Galaxy S4. My phone is running stock NB1. I did downgrade to MK2 and flashed MDL radio (I got hidden menu *#0011#, but unlock didn't work anyways)...finally I did root and installed RegionLockAway and it didn't work too...so I flashed it back to NB1 and stuck with this question
Click to expand...
Click to collapse
You flashed back to MDL and still didn't get the unlock to work? Dman..
Indian9990 said:
You flashed back to MDL and still didn't get the unlock to work? Dman..
Click to expand...
Click to collapse
I tried to downgrade from NB1 to MK2 by this post http://forum.xda-developers.com/showthread.php?t=2663545 and I think MK2 that I got is not exactly same as the original att S4 MK2 (cuz it has multi languages and att version I belive has only 5...idk maybe it's wrong opinion) but I'm sure if you have a stock android 4.3 MK2 you can flash MDL radio, then root it and use RegionLockAway, unlock will work. I did it with Mom's att S4 on stock android 4.3 MK2 before KitKat update.
@denverman, when I downgrade, would this void my Knox warranty and set it to 0x1?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
ntrambitas12 said:
I can't use regionlockaway because it requires root and my phone is not rooted because there is no root for 4.4.2 kit kat on the att variant
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
There is root for att 4.42. You have to root mk2 .. Then flash 100% stocknb1_rooted .. To get root in 4.4.2
Hi all, I have a galaxy S4 that is still on android 4.4.2, Build number JDQ39.I337UCUAMDB. What is the proper way to get this updated to KitKat so that I can use towelroot?
Izviral said:
Hi all, I have a galaxy S4 that is still on android 4.4.2, Build number JDQ39.I337UCUAMDB. What is the proper way to get this updated to KitKat so that I can use towelroot?
Click to expand...
Click to collapse
If you're on MDB, you can use motochopper to root and have a true custom recovery to run ROMs like Cyanogenmod, Paranoid Android, Slim Bean, and other AOSP ROMs. If you update you're limited to touchwiz ROMs of only the same system version you have.
Sent from my SGH-I337 running GPE
Izviral said:
Hi all, I have a galaxy S4 that is still on android 4.4.2, Build number JDQ39.I337UCUAMDB. What is the proper way to get this updated to KitKat so that I can use towelroot?
Click to expand...
Click to collapse
I assume you meant Android 4.2.2...
But yeah, your on MDB so this what I could recommend...
(Optional) First, use Odin and update your phone to MDL using these files. I can't recall if MDB works the same way as MDL (via Loki), it doesn't hurt to update to MDL though.
Secondly, after you have successfully flashed MDL follow this guide to obtain root, install a custom recovery, and learn how to use the Loki exploit.
Whatever you do, DO NOT let your device update to MF3, MK2, NB1,etc as you will lose the ability to run non-TouchWiz based roms.
Personally, I'd recommend just going with pure CyanogenMod after you get your device ready to go. You may want to do a little more research however, my experience with pre-MF3 devices is limited.
Hi Guy's,
Need help how do I update my rooted s4 4.3 to Kitkat 4.4
jegome said:
Hi Guy's,
Need help how do I update my rooted s4 4.3 to Kitkat 4.4
Click to expand...
Click to collapse
Download the official firmware from sammobile.com for your model no.
Flash it via odin
Youre done
But you will loose root access. For that, use towelroot. ^_^
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
DeepankarS said:
Download the official firmware from sammobile.com for your model no.
Flash it via odin
Youre done
But you will loose root access. For that, use towelroot. ^_^
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
Click to expand...
Click to collapse
Does towelroot set the device software flash to custom preventing future otas?