Related
I rooted my AT&T Galaxy S4 i337 a while back using Motochopper and it worked absolutely fine. After installing Cyanogenmod, I decided to go back to stock. I used triangle away and Odin to return myself back to stock, however, I always had issues. When I would recovery boot, I got an error and I couldn't wipe my cache partition. I tried to re-root my phone today using Motochopper and then Odin, but neither of them worked. I got a fail on both of them. Motochopper installed Supersu on my device, but didn't actually give me root access, and Odin just gave me a fail. Now, my phone is working with stock, but I still get errors in recovery mode and I can't root. Can someone please help!?
What is your baseband and build number on settings, more, about phone?
jd1639 said:
What is your baseband and build number on settings, more, about phone?
Click to expand...
Click to collapse
Baseband - I337UCUAMF3
Build Number - JDQ39.I337UCUAMF3
I
cfoughty7 said:
Baseband - I337UCUAMF3
Build Number - JDQ39.I337UCUAMF3
Click to expand...
Click to collapse
That's what i was afraid of. With mf3 you can't root with motorchopper or flash roms like you could on mdl. You also can't put on a custom recovery. Give me a second and I'll give you some links.
http://forum.xda-developers.com/showthread.php?p=44165374
http://forum.xda-developers.com/showthread.php?p=42478710
http://forum.xda-developers.com/showthread.php?p=45186518
http://forum.xda-developers.com/showthread.php?p=45971194
Read these before you do anything else and get familiar with them.
cfoughty7 said:
Baseband - I337UCUAMF3
Build Number - JDQ39.I337UCUAMF3
Click to expand...
Click to collapse
MF3 has a completely different root and recovery method now. Search the threads and you'll find them. Unfortunately it's pretty risky as you won't be able to flash back to stock using ODIN on MF3.
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
jd1639 said:
I
That's what i was afraid of. With mf3 you can't root with motorchopper or flash roms like you could on mdl. You also can't put on a custom recovery. Give me a second and I'll give you some links.
http://forum.xda-developers.com/showthread.php?p=44165374
http://forum.xda-developers.com/showthread.php?p=42478710
http://forum.xda-developers.com/showthread.php?p=45186518
http://forum.xda-developers.com/showthread.php?p=45971194
Read these before you do anything else and get familiar with them.
Click to expand...
Click to collapse
I'm just confused as to why I was able to do it perfectly before?
cfoughty7 said:
I'm just confused as to why I was able to do it perfectly before?
Click to expand...
Click to collapse
Because you were on mdl firmware. After you Odin'd it had to have taken the ota update to mf3.
shall plyinuf
jd1639 said:
Because you were on mdl firmware. After you Odin'd it had to have taken the ota update to mf3.
Click to expand...
Click to collapse
Ohhh, ok. I understand! There's no way to get it back? Is that what I should read those links for?
cfoughty7 said:
Ohhh, ok. I understand! There's no way to get it back? Is that what I should read those links for?
Click to expand...
Click to collapse
Ok, so I read the links. Now, I'm not so much interested in rooting as I am getting my phone straight. Is there any way to get back to mdl? Will the rumored 4.3 update this month fix that? When I tried to update or recover with Samsung Kies, it said my phone wasn't compatible to recover. Does that mean I won't be able to get the update?
jd1639 said:
Because you were on mdl firmware. After you Odin'd it had to have taken the ota update to mf3.
Click to expand...
Click to collapse
Ok, so I read the links. Now, I'm not so much interested in rooting as I am getting my phone straight. Is there any way to get back to mdl? Will the rumored 4.3 update this month fix that? When I tried to update or recover with Samsung Kies, it said my phone wasn't compatible to recover. Does that mean I won't be able to get the update?
cfoughty7 said:
Ok, so I read the links. Now, I'm not so much interested in rooting as I am getting my phone straight. Is there any way to get back to mdl? Will the rumored 4.3 update this month fix that? When I tried to update or recover with Samsung Kies, it said my phone wasn't compatible to recover. Does that mean I won't be able to get the update?
Click to expand...
Click to collapse
First, there is no way to go back to mdl. Idk if you'll be able to get the 4.3 update but I would assume so since you are on the stick firmware now. But, each new update is going to make it harder to root your phone or run custom roms. So you probably need to choose whether you want to keep your phone stock and take updates if and when they come out. Or have some snooty to run custom roms and root your device and put safestrap on.
jd1639 said:
First, there is no way to go back to mdl. Idk if you'll be able to get the 4.3 update but I would assume so since you are on the stick firmware now. But, each new update is going to make it harder to root your phone or run custom roms. So you probably need to choose whether you want to keep your phone stock and take updates if and when they come out. Or have some snooty to run custom roms and root your device and put safestrap on.
Click to expand...
Click to collapse
I'm going to stay with stock. Will the mdl thing effect anything if I have an issue with warranty sterf?
Shouldn't, your stock mf3 right now.
Hey guys, I've done a lot of searching in this forum and found a lot of conflicting answers, so decided to start a fresh thread. I've been on 4.2.2/MF3 for a while now running Safetrap. I'm looking to take the OTA from AT&T and upgrade to 4.3.
I havent seen any root methods for 4.3 yet, but the question is, can I upgrade to 4.3 and retain root if I am running the latest version of SuperSU Pro with survival mode enabled?
A custom recovery with the option for installing ROMs is not needed, especially since I havent been able to do that since I updated to MF3. All I need is to keep root under 4.3 and I'll be more than happy, thanks!
kevinco1 said:
Hey guys, I've done a lot of searching in this forum and found a lot of conflicting answers, so decided to start a fresh thread. I've been on 4.2.2/MF3 for a while now running Safetrap. I'm looking to take the OTA from AT&T and upgrade to 4.3.
I havent seen any root methods for 4.3 yet, but the question is, can I upgrade to 4.3 and retain root if I am running the latest version of SuperSU Pro with survival mode enabled?
A custom recovery with the option for installing ROMs is not needed, especially since I havent been able to do that since I updated to MF3. All I need is to keep root under 4.3 and I'll be more than happy, thanks!
Click to expand...
Click to collapse
This is my exact question. I just need some concrete answer as to yes or no... but as you said way too many conflicting answers!
YES.
I used "Survival mode" and it worked for me.
ROOTED ATT MK2 using Tapatalk
Hi so there is a way to update stock to 4.3 and continue using safestrap to run 4.2.2 roms????I would doubt that with what Ive read so far.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
jball said:
YES.
I used "Survival mode" and it worked for me.
Click to expand...
Click to collapse
I too can confirm this works using Survival Mode from SuperSU Pro (https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro&hl=en).
Now, that being said, being a very big noob myself (switching over from heavily tweaked jailbroken iPhone 5), I did this, all was well, I thought I had some issues with some apps and thought 'hmm... maybe I'll just downgrade to MF3 and see if the problem is fixed'. Yeah, attempting to do that with Odin has left me soft-bricked, but for all intents and purposes (that I can tell) it's actually hard-bricked 'cause Kies did nothing, Odin does nothing, if I understand things correctly the only thing that could possibly help is if we had the MD5's available to us for MK2, which, my searching is coming up empty. So, point is according to what I can tell, if you go MK2, there is NO going back to 4.2.2, so use caution.
So just an important safety tip there (unless someone wants to correct my noobness).
Yes. I can confirm that enabling "survival mode" in SuperSU and updating will keep your root; i did this on my pphone coming from MF3.
However, with that being said, i quickly unrooted from there because i had issues with MMS/messaging and phone calls not being recieved, and i did not want to reset my phone. If you run into similar issues as i am not the only one reporting those issues you can so a reset on your data (your root will not be affected, you will be rooted after the reset) or an unroot will work.
happy updating
kevinco1 said:
Hey guys, I've done a lot of searching in this forum and found a lot of conflicting answers, so decided to start a fresh thread. I've been on 4.2.2/MF3 for a while now running Safetrap. I'm looking to take the OTA from AT&T and upgrade to 4.3.
I havent seen any root methods for 4.3 yet, but the question is, can I upgrade to 4.3 and retain root if I am running the latest version of SuperSU Pro with survival mode enabled?
A custom recovery with the option for installing ROMs is not needed, especially since I havent been able to do that since I updated to MF3. All I need is to keep root under 4.3 and I'll be more than happy, thanks!
Click to expand...
Click to collapse
First with Safestrap you CAN flash Roms. It is just limited to about 10 or so Roms that will work as they need to be 4.2.2 based.
Now with that said for those that ONLY want root on MK2 then someone in the Verizon thread has a WORKING ROOT available for MK2 4.3 firmware here http://forum.xda-developers.com/showthread.php?t=2565758 and it DOESN'T come with the maliscious code that Kango and VRoot does. This DOES NOT give you recovery but it does give root. So thank the OP in that thread for helping out the community. I did and I HOPE I will never need to use it!!!
Good luck and Happy Rooting...
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Hey this is my first post and Im sorry if some of this is a repeat, I looked around for a little bit and wasnt able to find any answers.
I have a note 3 on verizon and i finally got it rooted on MJE. I have SuperSU installed as well as xposed installer as well as wanam xposed and a couple modules. I was trying to update via OTA and it constantly gives me error 402. I have tried hiding superuser and it says on odin? i believe that im on the offical rom and everything.
i just cant get onto kit kat no matter what i do. it downloads and once it tries updating i get the error.
Is there anything im really missing out on with kit kat? I want to install S view all covers and also want the XLTE. thats the main reasons for me wanting to update.
Is there something wrong with my phone? How can i get the update now? Thanks
Inovazn628 said:
Hey this is my first post and Im sorry if some of this is a repeat, I looked around for a little bit and wasnt able to find any answers.
I have a note 3 on verizon and i finally got it rooted on MJE. I have SuperSU installed as well as xposed installer as well as wanam xposed and a couple modules. I was trying to update via OTA and it constantly gives me error 402. I have tried hiding superuser and it says on odin? i believe that im on the offical rom and everything.
i just cant get onto kit kat no matter what i do. it downloads and once it tries updating i get the error.
Is there anything im really missing out on with kit kat? I want to install S view all covers and also want the XLTE. thats the main reasons for me wanting to update.
Is there something wrong with my phone? How can i get the update now? Thanks
Click to expand...
Click to collapse
You need to be unrooted stock to accept the OTA. Currently no way to root the ota. However there is a kitkat build (nc2) that was rooted. This is the build that everyone is working off of, so you can just flash the firmware / nc2 rom and you will be on kitkat rooted.
Thanks for the reply!
I've heard of people still taking the Ota while keeping root by putting supersu on survival mode though. Should I check that off and then click unroot in Supersu to take the Ota? Thanks
sfld said:
You need to be unrooted stock to accept the OTA. Currently no way to root the ota. However there is a kitkat build (nc2) that was rooted. This is the build that everyone is working off of, so you can just flash the firmware / nc2 rom and you will be on kitkat rooted.
Click to expand...
Click to collapse
You do NOT need to be unrooted, but you do need SuperSU to be in survival mode.
Sent from my Note 3 via Tapatalk
donc113 said:
You do NOT need to be unrooted, but you do need SuperSU to be in survival mode.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
okay so whats seems to be the problem with my note 3 not updating then? Im pretty much lost haha. It reboots into recovery and then goes about 33% on updating before getting a error and restarting.
Inovazn628 said:
okay so whats seems to be the problem with my note 3 not updating then? Im pretty much lost haha. It reboots into recovery and then goes about 33% on updating before getting a error and restarting.
Click to expand...
Click to collapse
Have you ever installed safestrap or anything similar?
Also remove all xposed modules, etc.
Sent from my Note 3 via Tapatalk
Inovazn628 said:
Is there anything im really missing out on with kit kat? I want to install S view all covers and also want the XLTE. thats the main reasons for me wanting to update.
Is there something wrong with my phone? How can i get the update now? Thanks
Click to expand...
Click to collapse
Try installing just the nc4 radio for xlte. Have you tried the leaked NC2 KK? I'd stay rooted personally ... samsung stuff has too much bloat and will run like a pig.
donc113 said:
Have you ever installed safestrap or anything similar?
Also remove all xposed modules, etc.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Nope I just I have supersu. I disabled superuser and then I Uninstaller all the modules. I also uninstalled the framework for xposed. Is there anything else that could be causing it?
Inovazn628 said:
Nope I just I have supersu. I disabled superuser and then I Uninstaller all the modules. I also uninstalled the framework for xposed. Is there anything else that could be causing it?
Click to expand...
Click to collapse
not that I know of.
You may have to reflash MJE and reroot it.
Sent from my Note 3 via Tapatalk
Hi gurus. first off, bought my first note 4 some days ago.. always thought the note series would be too big a phone for me.. what have i been thinking??? this is hands down the best phone i have ever had.. cant remember the last time a phone gave me this feeling..
but I am at a crossroad here.. i really REALLY miss root, but a little hesitant regarding tripping the e-fuse/knox/warranty. havent had a Samsung since the S4 was newly released.
I do not want to flash custom roms, just root stock and debloat and titanium backup, xposed, ad blocking etc..
in this regard, towelroot, stumproot is genius i think, and still able to receive OTA. but does not work on the note 4 of course.
but what happens when Lollipop arrives, seem to remember that the L would be different regarding root? should i wait to root until the Lollipop update arrives, should be here soon for our devices..
do you think there will be a workaround for the e-fuse trippin?
in general, whats your thoughts about this..?
my phone is the Snapdragon, SM-N910F.
Don't hold your breath for a root that doesn't trip Knox, and don't worry about it unless you work for a corporation that requires the use of Knox.
Chainfire had already proven root on devices with LP; I don't see any reason to wait. Being rooted doesn't often seem to be a problem regarding warranty.
Thanks for your reply rcobourn. Would one be able to receive ota with Chain fire auto root? What's the preferred rooting method when only going stock.?
Will root make Private Mode unusable?
I don't care about voiding warranty with knox 1 or 0x1, but I want knox Private mode to work on a Rooted exynos.
Any one knows if rooted knox still works or it must disabled with Titanium Backup?
SJGSM said:
Will root make Private Mode unusable?
I don't care about voiding warranty with knox 1 or 0x1, but I want knox Private mode to work on a Rooted exynos.
Any one knows if rooted knox still works or it must disabled with Titanium Backup?
Click to expand...
Click to collapse
i am rooted and using private mode just try xsecurestorage by wanam and your good to go
just folder mount breaks the private mode
buljo said:
Thanks for your reply rcobourn. Would one be able to receive ota with Chain fire auto root? What's the preferred rooting method when only going stock.?
Click to expand...
Click to collapse
SJGSM said:
Will root make Private Mode unusable?
I don't care about voiding warranty with knox 1 or 0x1, but I want knox Private mode to work on a Rooted exynos.
Any one knows if rooted knox still works or it must disabled with Titanium Backup?
Click to expand...
Click to collapse
CF breaks OTA as I found out the hard way, it tried to auto install and soft bricked itself last night. Easy fix, just flash the latest firmware from sammobile.
As for private mode that is only broken if you use Xposed without Xsecurestorage
Can we use kies for updates? Or do we have to flash roms all the way?
buljo said:
Can we use kies for updates? Or do we have to flash roms all the way?
Click to expand...
Click to collapse
Not if it's rooted. Flash using ODIN, dunno what it's like now but in the S2 days Kies was an awful piece of crap, whereas ODIN always worked perfectly.
buljo said:
Can we use kies for updates? Or do we have to flash roms all the way?
Click to expand...
Click to collapse
I highly doubt Kies will work properly, although it does tell me when there is an update for my phone when rooted so it might but I personally wouldn't try it as it most likely will do the same thing as letting it install the OTA automatically and soft brick it
Fuzzi99 said:
I highly doubt Kies will work properly, although it does tell me when there is an update for my phone when rooted so it might but I personally wouldn't try it as it most likely will do the same thing as letting it install the OTA automatically and soft brick it
Click to expand...
Click to collapse
Worked for me when the last update came out, I just updated via Kies while I was rooted. Everything went good.
Did you keep root while using kies?
buljo said:
Did you keep root while using kies?
Click to expand...
Click to collapse
I was rooted while I used kies to update, after the update the root got removed and I had to root it again with the same method I used to root it before the update.
I have an AT&T Galaxy S4 SGH-I337. I was so excited about the update to lollipop that I un-rooted my phone and downloaded it as soon as I could. I am enjoying it, but I miss root access. Has anyone come up with a way gain root access with this new update? I know with the 4.4.4 update we could flash the old kernel and use towel root, any chance something like that would work for this version?
If this is being dealt with in another thread I apologize, I did look.
Try TowelRoot APK https://towelroot.com/
----------------------------------------------
Please hit the thanks button if it worked
I'm interested in knowing how it turns out for you if you try towelroot. I got the lolipop update on my tab, and I'm liking it. However, I like having root so I haven't plunged in with my S4 yet, been doing some reading first.
dustyhughes said:
I'm interested in knowing how it turns out for you if you try towelroot. I got the lolipop update on my tab, and I'm liking it. However, I like having root so I haven't plunged in with my S4 yet, been doing some reading first.
Click to expand...
Click to collapse
Towle Root hasn't worked for the last few at&t updates. It's awesome but outdated.
Odin back to nb1, then root, then follow the instructions listed here.http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814