Hello everyone, I'm a returning (or more so new) user who's been here since the tytn2 days but gone rogue for awhile. Recently I've picked up an s4 through my contract renewal and stepped into a few hickups on rooting. beforehand, i've been on the iphone for a long time and only recently gotten somewhat recognized into the android platform with the note 10.1 before getting the s4 so i'm not completely new to it, but still a noob when it comes to fixing recurring problems when it comes to rooting. Anyways... For the past week i've tried the motochopper method to root my galaxy s4 with unsuccessful results as each time i've tried it the string: "[-] Failure." would occur every time i got it to run.
Methods of rooting:
- Particularly, motochopper was the only method of rooting that i've tried and it did install the superuser apk, however when i'm prompted to install the superuser binary update within the app the following error, "There was an error installing superuser. Please send a log of the error to the developer" always occurs. installing SuperSU and attempting to use it also didn't work as it will prompt me, "There is no binary installed, and SuperSU cannot install it. This is a problem!"
Notable things:
- I've updated my phone to the most recent firmware from att as of 4 days ago. I'm aware that this is most likely the cause of my difficulties and i was foolish to not read beforehand about the update blocking root :/.
- My phone is the galaxy s4 version sgh-i337 from AT&T US
- Baseband number is i337UCUAMF3. I'm also aware that this is the version that everyone's having trouble with for those trying to root.
- After the root attempt, i've read up on a few things regarding my issue as well as a couple of posts within the motochopper thread where some people had trouble rooting. After which i figured out that the update blocked root.
- I strongly do not want to factory reset my phone and have to back up everything but, if necessary, then i will.
- So far with the information I've read I couldn't find many clear answers which is why I ended up making this thread.
- Even with the experience that I had with the note 10.1 i'm still fairly new to android, so my apologies if all of this sounds ignorant or.. "newbish".
Problems I've come across:
- Using root checker pro i've compiled the detailed results on the bottom. It should also be noted that i was prompted, "root access not properly configured or was not granted." It will say that superuser was not installed but I can assure that it's on my app drawer.
Code:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed.
SuperSU application - version 1.41 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
- For reference, i've also tried an app that required root (GMusicFS) but it tells me "Device is not rooted"
- I read up on the site how to use odin to remove the root but my current baseband doesn't match the baseband of the md5 files supplied as the end letters like MDL do not match with my own which are MF3. My fears are that i'll brick it, especially if it isn't necessary to do so given that my root went unsuccessful.
- Tried using the Updater to see if it tells me that my phone is up to date after attempting the root, but after being stuck on "contacting DM server" for a good 10 minutes and force closing it, it prompted me that the process was interrupted and that the phone was up to date. What worries me is that the updater may or may not be broken after the root attempt
General Questions:
- Is it necessary to unroot my phone given that there is no root present to begin with? or will there be any recurring problems if i don't do so?
- Is the updater to my phone broken because of the root attempt or is it something else?
- Will Odin brick my phone if i use it with the current files and should i wait until an mf3 file shows up if i need to unroot? (my common sense tells me that if i do it will brick it, but i want to get someone else's opinion on it if it's possible)
- Can i remove the superuser app manually and will it be safe if i do it?
- Did the root attempt on motochopper work to a certain point or did it not go through at all?
- When is it expected that we'll see a fix for the mf3 baseband and see a root program for it? I'm aware that it locks the bootloader too and some deeming it impossible at the moment but i'm just curious.
Any help to these questions is very much appreciated and if there's anything that i've missed to which you need more info on i'd be glad to respond.
You cant downgrade...once on mf3 your stuck, odin will instantly fail when trying ti flash if your on mf3. Lastly there is no current root methid for mf3...so you will just have to wait for a new exploit..
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mg2195 said:
You cant downgrade...once on mf3 your stuck, odin will instantly fail when trying ti flash if your on mf3. Lastly there is no current root methid for mf3...so you will just have to wait for a new exploit..
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for replying, i didn't know that about odin. So because of this it also means that nothing got changed except just adding the superuser apk on my phone then, right? Seeing that i can't even use odin and the root doesn't go through on mf3 anyway, i don't need to unroot for any reason or factory reset except if the root went through successfully and i wanted to remove it correct?
Is there still not a way to unroot when youre on mf3?
Zamdam1 said:
Is there still not a way to unroot when youre on mf3?
Click to expand...
Click to collapse
You should have super su on your phone. There is an unroot feature in it. Many have reported success unrooting with it.
http://forum.xda-developers.com/showthread.php?p=45301834
jd1639 said:
You should have super su on your phone. There is an unroot feature in it. Many have reported success unrooting with it.
Click to expand...
Click to collapse
Well, i removed supersu somehow.. i guess i should try this again and then try and use supersu to unroot it.
Why don'y you just read the information already available in this forum. Especially the "pinned" threads in 'General" and "Q & A" sections. Also read the threads with MF3 in the title. ALL of the questions you asked are answered in detail in those threads, plus you will learn a lot more about the phone while reading the threads. Good luck.
Read through this thread:
http://forum.xda-developers.com/showthread.php?t=2432876&page=2
scott14719 said:
Why don'y you just read the information already available in this forum. Especially the "pinned" threads in 'General" and "Q & A" sections. Also read the threads with MF3 in the title. ALL of the questions you asked are answered in detail in those threads, plus you will learn a lot more about the phone while reading the threads. Good luck.
Click to expand...
Click to collapse
I've read quite a lot actually, that's why i made this thread at the time mostly to clear some glaring concerns I had being new to this. Since then though the MF3 update was able to be rooted and most of my questions and concerns were answered. I appreciate the help.
skullstrider said:
I've read quite a lot actually, that's why i made this thread at the time mostly to clear some glaring concerns I had being new to this. Since then though the MF3 update was able to be rooted and most of my questions and concerns were answered. I appreciate the help.
Click to expand...
Click to collapse
Also notice SuperSU upgraded to 1.60. I noticed you posted an older version which may be incompatible with latest MF3 update. :S
In short motochopper rooting method DOES NOT work with MF3. I know a lot of people are tired of saying that but I'll be the one this time to remind you haha. But it looks like you figured that out and moved on to jortex's rooting method.
Just know there is no way to ODIN it back like on the old MDL update.
haremmon said:
Also notice SuperSU upgraded to 1.60. I noticed you posted an older version which may be incompatible with latest MF3 update. :S
In short motochopper rooting method DOES NOT work with MF3. I know a lot of people are tired of saying that but I'll be the one this time to remind you haha. But it looks like you figured that out and moved on to jortex's rooting method.
Just know there is no way to ODIN it back like on the old MDL update.
Click to expand...
Click to collapse
well.. for some reason the jortex method did reinstall supersu.. i used motochopper to install the superuser app. im guessing there is no unroot option in that app.. oh well. i will just keep it rooted until they release the fw for mf3..
Zamdam1 said:
well.. for some reason the jortex method did reinstall supersu.. i used motochopper to install the superuser app. im guessing there is no unroot option in that app.. oh well. i will just keep it rooted until they release the fw for mf3..
Click to expand...
Click to collapse
Are you trying to unroot? Try following this post I made on the other thread: http://forum.xda-developers.com/showpost.php?p=45340743&postcount=12
Related
I recently rooted my atrix with superoneclick then i accidently updated then i belive i still had my root until i went to install a 3d theme then my phone crashed and wouldnt get past the at&t screen so i had to erase everything now on my phone i still have "super user" in my app draw but i cannot side load apps did i lose my root? what do i have to do to sideload apps again ? and i guess re root my phone
Yes i am a newb i am comming from IOS and an iPhone 4 please dont flame
If you updated, you mean 4.1.57, this is what I did to re-root when I lost mine after updating and SuperOneClick wouldn't work.
http://forum.xda-developers.com/showthread.php?t=1013931
Ok so i read that so basically i have to flash my phone back to default then root again?
Yeap, that's exactly what I did, but in that same thread, I think someone else outlined using aRoot to go over SuperOneClick.
Originally Posted by donbar85
I'm pretty new to Android (two weeks now), and want to ensure I don't end up with a bricked device, so I apologize for the 'noob' question here. I rooted with SuperOneClick. Has anyone else used this script successfully with that root method, or will it only be successful with aRoot?
Also, if I need aRoot, can I run it over top SuperOneClick, or would it be best to unroot, run aRoot (or let the script root) and then run the script?
I appreciate all the hard work I've seen done in these forums and appreciate any help anyone can offer.
---
Yes you may safely run aroot over superoneclick. Aroot is the recommended method because it cleans up a lot of things Superroneclick does.
----
Originally Posted by DJQ1212
Yes you may safely run aroot over superoneclick. Aroot is the recommended method because it cleans up a lot of things Superroneclick does.
Thank you both. I believe I will try running aRoot over my SuperOneClick root and then try out the script. Thanks again!
Click to expand...
Click to collapse
Yup the aRoot script is used in the GladiAtrix and possibly the GingerBlur rom as well. Either way. SOC is crap, not meant for atrix anyway. aRoot was written specifically for the Atrix. If you want to update to 4.1.57 read through the retain root thread over in atrix development.
after update, i can still see "su" installed in /system/bin/
I am unable to use it, getting permissioned denied message, any solutions ?
sam_t610 said:
after update, i can still see "su" installed in /system/bin/
I am unable to use it, getting permissioned denied message, any solutions ?
Click to expand...
Click to collapse
This has been explained many times. updating kills root, even though you still have superuser installed. to retain root you need to use the script in the development section when updating from 1.26 to 1.57. flash back to 1.26 and try again.
Hey Guys,
I recently bought a Nexus 7 from ebay. The guy I bought it from had put Paranoid Android 3 on it. I am cimplete noob and do not know how to root or flash.
I just did something which I dont know how to correct.
GooManager kept telling me there was an update which when tapped on, would bring me to the .zip file i was supposed to dl.
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh
Josh5321 said:
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh
Click to expand...
Click to collapse
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.
Pirateghost said:
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.
Click to expand...
Click to collapse
but in the past when I would click on the update notification it brought me straight to the download file. now it just brings me to the goomanager main screen.
reboot the device and try again. or you can go in and clear out all data and cache for goomanager in your settings/apps/goomanager page
I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.
Josh5321 said:
I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.
Click to expand...
Click to collapse
open the NEXUS 7 ORIGINAL DEVELOPMENT FORUMS and download yourself, or open GOOMANAGER and BROWSE COMPATIBLE ROMS...
I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.
TyneBridges said:
I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.
Click to expand...
Click to collapse
Hi, TyneBridges...
Well, I've never used GooManager myself... but the apps description on PlayStore certainly suggests you do need to be rooted to be use it.
You're a long way from the Motorola Xoom forums (wherever they may be)... but try, from PlayStore, running some app that requires root... like Titanium backup, or perhaps better, Android Terminal emulator (by Jack Palevich)... run it, and type...
Code:
su
If you're NOT rooted, you should see something like this...
Code:
$su
su: not found
$
-------------------------------------------------------
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
If you have some root SU binary installed, then Chainfire's SuperSU app should detect it... and either replace it, or update it.
Anyway... just some thoughts.
I really have no idea what other technical issues/problems there might be rooting a Motorola Xoom. And so you should hunt out the XDA forum for your specific device for more information... I'd be very surprised if there wasn't one.
Good luck.
Rgrds,
Ged.
GedBlake said:
Hi, TyneBridges...
...
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
...
Click to expand...
Click to collapse
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John
TyneBridges said:
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John
Click to expand...
Click to collapse
Hi, again John...
I'm afraid I'm a bit out of my depth with the Motorola Xoom... I know absolutely nothing about it. Sorry.
Here's where you should really be asking...
http://forum.xda-developers.com/motorola-xoom
...if anybody can solve your problem, then that's where you're likely to find them.
----------------------------------------------
If you can install a Custom Recovery like TWRP or CWM on your device, then it **SHOULD** (theoretically) just be a case of flashing Chainfire's UPDATE-SuperSU-v1.94, via that Custom Recovery.
On Nexus devices, you use FASTBOOT to flash a Custom Recovery.... on Samsung Devices, you need something called Odin to do likewise.
Once you have a Custom Recovery installed, rooting should be a piece of cake.
Problem is, I have absolutely no idea how to get such a Custom Recovery installed on a Xoom.
Do a bit of research... XDA is a vast repository of considerably more knowledgeable people than myself... and somebody is likely to know something.
Good luck.
Rgrds,
Ged.
I have searched everywhere and I think this phone is unable to be rooted. I have discovered the UK version of this phone has a locked down bootloader that will not allow me to gain access any way I try. The phone is running Gingerbread 2.3.6, Build No. GRK39F, Kernel Version 2.6.38.6-perf+ and does not have a su.bin on the phone, nor will it allow me access to put one on it. I get permission denied when i try to remount the partition as r/w. When I try to unlock the bootloader, the phone does reboot but not into bootloader mode. This phone only has a hard reset. No other boot modes (just the factory reset). Chmod/chown will not allow me to change permissions. No matter which application I have tried, I am unable to flash anything to the device, since I can not gain root access. The adb root command gives me an error message as well "adbd cannot run as root in production builds." I know I may be a noob, but I have done a ton of research and have not found anything that will help me. Does anyone has any sort of information that will help me root this device? It would be greatly appreciated!
What programs did you use ?
wmt9905 said:
I have searched everywhere and I think this phone is unable to be rooted. I have discovered the UK version of this phone has a locked down bootloader that will not allow me to gain access any way I try. The phone is running Gingerbread 2.3.6, Build No. GRK39F, Kernel Version 2.6.38.6-perf+ and does not have a su.bin on the phone, nor will it allow me access to put one on it. I get permission denied when i try to remount the partition as r/w. When I try to unlock the bootloader, the phone does reboot but not into bootloader mode. This phone only has a hard reset. No other boot modes (just the factory reset). Chmod/chown will not allow me to change permissions. No matter which application I have tried, I am unable to flash anything to the device, since I can not gain root access. The adb root command gives me an error message as well "adbd cannot run as root in production builds." I know I may be a noob, but I have done a ton of research and have not found anything that will help me. Does anyone has any sort of information that will help me root this device? It would be greatly appreciated!
Click to expand...
Click to collapse
are you trying to just root or flash custom rom too ?
did you try SuperOneClickv2.3.3-ShortFuse.zip ?
did you try vroot ? in my signature (guide too)
if you install root browser it will install basic commands on your phone busybox sqlite etc
also check this out it might be your firmware does not support root and you might need to install v10b or v10c kdz
wmt9905 said:
I have searched everywhere and I think this phone is unable to be rooted. I have discovered the UK version of this phone has a locked down bootloader that will not allow me to gain access any way I try. The phone is running Gingerbread 2.3.6, Build No. GRK39F, Kernel Version 2.6.38.6-perf+ and does not have a su.bin on the phone, nor will it allow me access to put one on it. I get permission denied when i try to remount the partition as r/w. When I try to unlock the bootloader, the phone does reboot but not into bootloader mode. This phone only has a hard reset. No other boot modes (just the factory reset). Chmod/chown will not allow me to change permissions. No matter which application I have tried, I am unable to flash anything to the device, since I can not gain root access. The adb root command gives me an error message as well "adbd cannot run as root in production builds." I know I may be a noob, but I have done a ton of research and have not found anything that will help me. Does anyone has any sort of information that will help me root this device? It would be greatly appreciated!
Click to expand...
Click to collapse
havr u tried apectrum root window...that rooted my and my friends l3
Sent from my LG-E400 using Tapatalk
aroop mishra said:
havr u tried apectrum root window...that rooted my and my friends l3
Sent from my LG-E400 using Tapatalk
Click to expand...
Click to collapse
Yes, I have tried every app. The apps I use are pretty much irrelevant though, since there isn't a su binary to request permission from. without the su binary, no app can gain root access.
IGGYVIP said:
are you trying to just root or flash custom rom too ?
did you try SuperOneClickv2.3.3-ShortFuse.zip ?
did you try vroot ? in my signature (guide too)
if you install root browser it will install basic commands on your phone busybox sqlite etc
also check this out it might be your firmware does not support root and you might need to install v10b or v10c kdz
Click to expand...
Click to collapse
superoneclick does not work as it requests permission from the su binary, which does not exist. root browser does not work either, as it does not allow me to change permissions or ownership either. chmod and chown in linux don't work either. I get "permission denied" when attempting those commands. I an currently running on v10c, but I can not flash anything, including firmware, to this device either. There's no way to downgrade or upgrade. I get a parameter error when attempting to and then the kdz updater crashes and forces itself closed every time I have tried.
My phone model is LG Optimus L3 E400. I could fix this by change the default.prop file ro.secure=1 to ro.secure=0, but I can't write to that file. It's read-only and I can't figure out a way to change that.
I'm really about to just throw this phone out. I had no clue that some phones can not be rooted and would have no further research before buying this one.
try this
wmt9905 said:
superoneclick does not work as it requests permission from the su binary, which does not exist. root browser does not work either, as it does not allow me to change permissions or ownership either. chmod and chown in linux don't work either. I get "permission denied" when attempting those commands. I an currently running on v10c, but I can not flash anything, including firmware, to this device either. There's no way to downgrade or upgrade. I get a parameter error when attempting to and then the kdz updater crashes and forces itself closed every time I have tried.
My phone model is LG Optimus L3 E400. I could fix this by change the default.prop file ro.secure=1 to ro.secure=0, but I can't write to that file. It's read-only and I can't figure out a way to change that.
I'm really about to just throw this phone out. I had no clue that some phones can not be rooted and would have no further research before buying this one.
Click to expand...
Click to collapse
you didnt mention vroot was there any error message ?
when you installed root browser on first launch it asks to download little utilities did they install or come with any error ?
also try this super one click 1.7 and select exploit RAGEAGAINSTCAGE in right top corner (it has proven to root problematic e400's)
please update us on your progress
and worst case scenario we will get you to another version of stock and root then
IGGYVIP said:
you didnt mention vroot was there any error message ?
when you installed root browser on first launch it asks to download little utilities did they install or come with any error ?
also try this super one click 1.7 and select exploit RAGEAGAINSTCAGE in right top corner (it has proven to root problematic e400's)
please update us on your progress
and worst case scenario we will get you to another version of stock and root then
Click to expand...
Click to collapse
I don't know what vroot did, but it actually worked. you don't know how long I have spent trying to get this done. so many other programs told me that rooting was complete and didn't actually do anything, that when vroot did, I didn't believe it. I thought i was just stuck with a p.o.s. that I couldn't customize. I really appreciate your hep. Thank you so much!
i did but glad i could help
IGGYVIP said:
are you trying to just root or flash custom rom too ?
did you try SuperOneClickv2.3.3-ShortFuse.zip ?
did you try vroot ? in my signature (guide too) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
if you install root browser it will install basic commands on your phone busybox sqlite etc
also check this out it might be your firmware does not support root and you might need to install v10b or v10c kdz
Click to expand...
Click to collapse
i did
wmt9905 said:
Yes, I have tried every app. The apps I use are pretty much irrelevant though, since there isn't a su binary to request permission from. without the su binary, no app can gain root access.
Click to expand...
Click to collapse
you are right and my problem it too.
try vroot. it's the only i tried that worked.
Can anyone help me how to fix this problem " adbd cannot run as root in product builds".
lcsmatos said:
Can anyone help me how to fix this problem " adbd cannot run as root in product builds".
Click to expand...
Click to collapse
unlock bootloader
Greetings,
My wife's S4 is on 4.2.2 (MF3) and it drives me nuts. I've been looking around the forums, but haven't found anything conclusive as to if there is a way to go from 4.2.2 to 4.4.2 and keep or reroot.
Normally I'd throw caution to the wind, close my eyes, and hit start... but, being that this is the wife's phone and that she is perfectly content with 4.2.2, the last thing I want to do is screw up her phone.
So I guess the question is: Does anyone know of a guide they can point me to that upgrades a rooted 4.2.2 to 4.4.2?
Thank you!
PS
I found this guide (http://forum.xda-developers.com/showthread.php?t=2728462), but it just seems strange that the thread was all but ignored, so there is no feedback from users/testers.
You can upgrade to 4.4.2, but you don't keep root. You'll have to re-root it. And you have to use Odin which means you'll wipe the phone. If it was my wife's phone I wouldn't want to put up with the complaining of having to setup everything again.
Sent from my Nexus 5 using XDA Free mobile app
tarikakleh said:
Greetings,
My wife's S4 is on 4.2.2 (MF3) and it drives me nuts. I've been looking around the forums, but haven't found anything conclusive as to if there is a way to go from 4.2.2 to 4.4.2 and keep or reroot.
Normally I'd throw caution to the wind, close my eyes, and hit start... but, being that this is the wife's phone and that she is perfectly content with 4.2.2, the last thing I want to do is screw up her phone.
So I guess the question is: Does anyone know of a guide they can point me to that upgrades a rooted 4.2.2 to 4.4.2?
Thank you!
PS
I found this guide (http://forum.xda-developers.com/showthread.php?t=2728462), but it just seems strange that the thread was all but ignored, so there is no feedback from users/testers.
Click to expand...
Click to collapse
You can first unroot then go to settings---->more----->about device----> software update and take the OTA to MK2. Once on MK2 take the OTA to NB1, then to NC1, then re-root using towelroot: http://forum.xda-developers.com/showthread.php?t=2783157
The above process will leave your current set-up intact and rooted.
muniz_ri said:
You can first unroot then go to settings---->more----->about device----> software update and take the OTA to MK2. Once on MK2 take the OTA to NB1, then to NC1, then re-root using towelroot: http://forum.xda-developers.com/showthread.php?t=2783157
The above process will leave your current set-up intact and rooted.
Click to expand...
Click to collapse
Would this method be the best way to unroot, starting with step 2 in my case since I still have root...or is there a different route I can take?
Originally Posted by ou812bkewl
So, here is what I did and what you must do:
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
When you reboot, wait a full minute and check on device status. It should still say "Official" and you will be fully un-rooted.
Why does it stay "Official" with Busybox present ONLY when SuperSU's most recently updated apk and binary are present? I have no clue... But I hope this helps you out.
Click to expand...
Click to collapse
but none of them seem to work quite right...
-i tried one from the thread that was titled something like "Everything You Need To Know About the SCL22"...
---... but when i finished my root-checker app told me that i did not have root, and busybox/terminal weren't installed correctly.
-i then tried one from different thread that required manual terminal input "using su, etc."...
---... but when i got to the point of inputting the terminal code, it told me that it could find root, and rather than having a #-symbol, i got the $-symbol...
i also tried the first two methods again , two more times, each; to make sure i wasn't fowling up someplace. meticulously followed each of the steps, with same result.
-and then, finally, i tried CF-autoroot but could not find my model number, and was getting impatient, so i tried just the standard N900 one and got a soft-brick, which i am currently trying to restore...
-i only wish to remove bloat, install a custom rom (don't care about NFC, don't care about Knox, etc.), and install custom apk's. but meh :/
does anyone actually have a real, working root that i can follow clearly? lollipop or otherwise? in my reading of these forums, it seems the SCL22/SM-N900J (au Model) has been neglected.
i read through every thread i could find on the matter, so i feel like i really tried to root it myself and fix it myself, before asking for assistance :/ any help?
DK
Old post... but I have been looking for some SCL22 solutions myself, so I thought I'd help here.
I have root on my SCL22. Busybox works. I may have done more, but as I remember it, all it needed was:
Install:
twrp-3.3.1-0-hltekdi.img.tar (Installed via Odin3 v3.12)
Booted into recovery mode with TWRP. Installed (via zip, not image)
SR3-SuperSU-v2.79-SR3-20170114223742
That SuperSU copy, I've had for a while. Dunno if it can be found again, so I'll leave a copy here.
Yeah... that's it! There may be better software than SuperSU, but this works 90% for me. I wish SuperSU had the option for me to select software to give root permissions to; instead the app has to request root access, and then SuperSu will pop-op a notification to grant/deny root permissions. Sounds fine until the software you want to give root, doesn't ask for root (so then it never gets it )
But yeah... root. Enjoy.