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.
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
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app
Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk
Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.
i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot
re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app
Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.
cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2
So I am on nc4 Ota and used towelroot to get root then downloaded SuperSU and it keeps failing to update the binary... what am I doing wrong?
....okay good, I am not the only one. I reported the same issue:
http://forum.xda-developers.com/ver...supersu-fails-to-update-t2845426/post54772550
No one has responded to me yet. I highly doubt we are the only two people who have experienced this. From what I can tell, we have to install BusyBox, SafeStrap, and BajaROM in order to get this to work properly but I am not sure exactly how to do this. Take a look at my thread and see if the steps I laid out make sense.
Same issue here. It even said the initial install failed, but I can grant root permissions to apps. Who knows. I was able to get SafeStrap installed and flash another rom, anyway.
I found a solution and updated my thread for everyone's reference...
http://forum.xda-developers.com/ver...ote-3-rooted-supersu-fails-to-update-t2845426
sigh..
HyperTension said:
Lord, I had given up hope re: rooting the S7 Edge.. and holy crap has a lot changed from my Galaxy Nexus.. that was the last phone I rooted... (gave up on the Note 4). A lot has changed, and have a lot to re-learn...
Anywho.. utilized the process by jrkruse (massive thanks BTW) and once she finally rebooted, noticed that I'm unable to update SuperSU, get the error of "SU binary cannot be updated with this kind of root".... Uninstalled it, and I get the same issue when I installed it via his thread directly...
I am able to install and use Root Explore and Titanium Backup so I'm inclined to think I did.... but any insight is more than appreciated and thanks for tolerating me through this.
Click to expand...
Click to collapse
Updating the binaries causes issues so I purposely made the app so it won't update the binaries so I don't understand why you would start a whole thread about updating the binaries even when the app tells you not too. This is mentioned in the root thread