Related
so im a previous iphone user and need something new to play with......i follow the instructions to root with visionary but my S is always on and wont be S-off.......what do i do?
Visionary can not perform S-OFF. People tried to come up with 1-click app to do that but it's not possible, at least right now.
Follow this guide to make it happen. It's not as hard as it looks.
borodin1 said:
Visionary can not perform S-OFF. People tried to come up with 1-click app to do that but it's not possible, at least right now.
Follow this guide to make it happen. It's not as hard as it looks.
Click to expand...
Click to collapse
ok yea i did this and from some reason the sdk is not picking up my mt4g......ive been actually trying since i posted this thread lol. things are just not cooperating with me
For me yo get s off o have go put a stock rom on my phone maybe that will help
Sent from my HTC Glacier using XDA App
cdw9800 said:
For me yo get s off o have go put a stock rom on my phone maybe that will help
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I have a stock rom on though
Sent from my HTC Glacier using Tapatalk
Flipnfr3ak said:
so im a previous iphone user and need something new to play with......i follow the instructions to root with visionary but my S is always on and wont be S-off.......what do i do?
Click to expand...
Click to collapse
same as you(*), until last week when i came across this dude, who made it seem so easy. follw these links, and you will gain s-off with sim unlock through gfree 2:
http://www.youtube.com/watch?v=RyELJRy4rhE
http://www.youtube.com/watch?v=dXsORU5_rxI
http://www.youtube.com/watch?v=KvfHC1dQ0D4
http://www.youtube.com/watch?v=sIVMIwMgrWM
pay attention to it though, you don't wanna have a bricked new phone now!
------------------------------------------------------------------------------------------------
*by " same as you" i mean i was heaving a hard time gaining s-off, until these videos
Hi guys, my girlfriend just got a MT4G today and I'm having problems getting s-off too.
I've tried all methods and nothing seems to be working. Any suggestions? If you need more info just ask, but like i said, i've tried like three different ways and none work. I'll edit this post soon and add what common errors im getting
I couldnt get it done with Visionary r14, instead of getting the option screen when I opened it, it went straight to the rooting phone screen and just didnt work
I found r11 and used it instead and that solved my problem, the rest of the process went easy
PhantomRampage said:
Hi guys, my girlfriend just got a MT4G today and I'm having problems getting s-off too.
I've tried all methods and nothing seems to be working. Any suggestions? If you need more info just ask, but like i said, i've tried like three different ways and none work. I'll edit this post soon and add what common errors im getting
Click to expand...
Click to collapse
I had the same problem. I used one way to turn S-off when I had the myTouch 4g with the radio 0.85.xxxx. When I had my phone swapped since I made up an excuse to get the good screen, the radio was 0.86.xxxx. I tried to follow the same steps as I did with 0.85.xxxx, but wouldn't work. So I ended up trying the ULTIMATE GUIDE TO ROOT and it worked. I put everything unlocked even SIM. THen I used VISIONary r14 to have it root then perm root.
mbstang said:
I couldnt get it done with Visionary r14, instead of getting the option screen when I opened it, it went straight to the rooting phone screen and just didnt work
I found r11 and used it instead and that solved my problem, the rest of the process went easy
Click to expand...
Click to collapse
I tried r11 but it didn't work so I went to r14 with the ULTIMATE GUIDE TO ROOT and it works. So I guess each is their own.
Ok so I'm still having trouble with this. Can anyone tell me what I need to download for the sdk kit? I have a acer aspire one laptop either a d150 or a150.i don't know what the difference is. Running windows xp sp2 or 3 lol
Sent from my HTC Glacier using XDA App
Flipnfr3ak said:
Ok so I'm still having trouble with this. Can anyone tell me what I need to download for the sdk kit? I have a acer aspire one laptop either a d150 or a150.i don't know what the difference is. Running windows xp sp2 or 3 lol
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Dont even bother setting up the SDK. It is a pain in the arse!!! Use this method if you need to set up ADB.
Thank you I was looking for something like this
Sent from my HTC Glacier using Tapatalk
Seriously people, don't you read threads? The rooting method is very easy and does not require ADB or the SDK. I've rooted *5 PHONES* on the first try by reading and just following the damn directions.
You temproot, run a couple of commands in terminal, reboot, temproot, permroot, and go on your merry way.
If this doesn't work follow the guide for gfree and that will do it.
Here, I made a SUPER-STEP-BY-STEP guide. If this is still too complicated for you then you really shouldn't be rooting at all, as it requires some basic knowledge of how to use a computer and the phone. And I mean BASIC.
http://forum.xda-developers.com/showthread.php?t=834225
This one is pretty damn easy, takes all of 10 minutes. Use the Terminal Emulator method.
Read the first post all the way through before you start to make sure you understand the entire process. In a nutshell, here's what happens:
*Download root.rar and extract to be a folder called ROOT on your sdcard. The ROOT folder should not be inside any other folders, so it will be sdcard/root.
*Download a file manager from the Market. Linda File Manager is my favorite.
*Download Terminal Emulator from the Market.
*Download the Visionary.apk file from the link in thread.
*from home screen - MENU, SETTINGS, APPLICATIONS, ALLOW INSTALL OF NON-MARKET APPS. Make sure the box is checked. ALSO UNCHECK FAST BOOT.
*Open linda file manager, navigate to visionary and click on it to install.
*Reboot. This will take a minute.
*Open visionary, check the box for SET SYSTEM R/W AFTER ROOT.
*Hit button for TEMP ROOT. Give it a minute.
*Open Terminal Emulator and type THE ITALIC COMMANDS, pressing ENTER after each.
su
*You should get a prompt for SUPERUSER PERMISSIONS. Click ALLOW. Back in Terminal, continue with these commands, typing them EXACTLY as they appear and pressing ENTER after each line.
cd sdcard/root
sh root.sh
*Now just wait a few minutes.
*When it's done, shut down the phone.
*Hold volume down + power until you get to a white screen. If it says S-OFF near the top then you're almost done. If not, repeat the previous steps until you do see S-OFF.
*Reboot.
*Open visionary, make sure SET SYSTEM R/W AFTER ROOT is checked.
*Click TEMP ROOT.
*When done, click ATTEMPT PERM ROOT. This might take a few minutes. Your phone will reboot itself when done. (I think)
When you boot back up you should be permanently rooted and you are ready to install a custom ROM if you like.
*To verify that you are rooted, open Terminal Emulator and type su. If you get the # sign and a notice that superuser permissions were granted, then you have succeeded in rooting your phone. Congrats!
Installing a custom ROM is another procedure so do a search for the guides on those procedures.
Click to expand...
Click to collapse
Phateless said:
Seriously people, don't you read threads? The rooting method is very easy and does not require ADB or the SDK. I've rooted *5 PHONES* on the first try by reading and just following the damn directions.
You temproot, run a couple of commands in terminal, reboot, temproot, permroot, and go on your merry way.
If this doesn't work follow the guide for gfree and that will do it.
Here, I made a SUPER-STEP-BY-STEP guide. If this is still too complicated for you then you really shouldn't be rooting at all, as it requires some basic knowledge of how to use a computer and the phone. And I mean BASIC.
Click to expand...
Click to collapse
see ive done this many many times and my s just wont turn off.....its always on
Flipnfr3ak said:
see ive done this many many times and my s just wont turn off.....its always on
Click to expand...
Click to collapse
Are you making sure that "set system to r/w" and "run visionary.sh" are both checked at the time of temproot.
and are you getting any type of error codes when you type in the command lines.
Flipnfr3ak said:
see ive done this many many times and my s just wont turn off.....its always on
Click to expand...
Click to collapse
Assuming you're doing it correctly, some phones have trouble. Look for the guide titled ULTIMATE S-OFF, CHECK OUT EVEN IF ALREADY ROOTED.
http://forum.xda-developers.com/showthread.php?t=858996
The gfree method should do the trick.
I got it working after 4 hours -__- I'm not sure if it had anything to do with it, but once i removed the sim card it seemed to work. Got s-off and permroot and even flashed cm7 nightlies afterwards with no problems, then put the sim back i n
Phateless said:
Assuming you're doing it correctly, some phones have trouble. Look for the guide titled ULTIMATE S-OFF, CHECK OUT EVEN IF ALREADY ROOTED.
http://forum.xda-developers.com/showthread.php?t=858996
The gfree method should do the trick.
Click to expand...
Click to collapse
See I didnt do the visionary.sh check off part haha I don't remember see that part in the guide
Sent from my HTC Glacier using XDA App
I give up already I just can't get it to work nothing is working
Sent from my HTC Glacier using XDA App
Flipnfr3ak said:
I give up already I just can't get it to work nothing is working
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
SLOW DOWN, read the directions CAREFULLY, and make sure you understand the entire process before starting. I probably read the guides 20 times from start to finish before I rooted.
Here's a super-newbie step-by-step guide I typed up.
http://forum.xda-developers.com/showthread.php?t=834225
This one is pretty damn easy, takes all of 10 minutes. Use the Terminal Emulator method.
Read the first post all the way through before you start to make sure you understand the entire process. In a nutshell, here's what happens:
*Download root.rar and extract to be a folder called ROOT on your sdcard. The ROOT folder should not be inside any other folders, so it will be sdcard/root.
*Download a file manager from the Market. Linda File Manager is my favorite.
*Download Terminal Emulator from the Market.
*Download the Visionary.apk file from the link in thread.
*from home screen - MENU, SETTINGS, APPLICATIONS, ALLOW INSTALL OF NON-MARKET APPS. Make sure the box is checked. ALSO UNCHECK FAST BOOT.
*Open linda file manager, navigate to visionary and click on it to install.
*Reboot. This will take a minute.
*Open visionary, check the box for SET SYSTEM R/W AFTER ROOT.
*Hit button for TEMP ROOT. Give it a minute.
*Open Terminal Emulator and type THE ITALIC COMMANDS, pressing ENTER after each.
su
*You should get a prompt for SUPERUSER PERMISSIONS. Click ALLOW. Back in Terminal, continue with these commands, typing them EXACTLY as they appear and pressing ENTER after each line.
cd sdcard/root
sh root.sh
*Now just wait a few minutes.
*When it's done, shut down the phone.
*Hold volume down + power until you get to a white screen. If it says S-OFF near the top then you're almost done. If not, repeat the previous steps until you do see S-OFF.
*Reboot.
*Open visionary, make sure SET SYSTEM R/W AFTER ROOT is checked.
*Click TEMP ROOT.
*When done, click ATTEMPT PERM ROOT. This might take a few minutes. Your phone will reboot itself when done. (I think)
When you boot back up you should be permanently rooted and you are ready to install a custom ROM if you like.
*To verify that you are rooted, open Terminal Emulator and type su. If you get the # sign and a notice that superuser permissions were granted, then you have succeeded in rooting your phone. Congrats!
Installing a custom ROM is another procedure so do a search for the guides on those procedures.
Click to expand...
Click to collapse
So I rooted my phone using the SuperOneClick method, and got my superuser app and everything but when I try to run Barnacle Wifi Tether, Superuser never prompts, and Barnacle complains that I haven't rooted my phone.
So I go into the preferences of Superuser snooping around to see whats wrong, and I come across (under the general tab) Su binary vnull. I tap it to check for updates and it goes like this:
Working...
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3
Checking installed version = legacy
So it says at the top new version of su binary found.
Update now?
I tap update and this happens:
Working...
Fixing database... okay!
Checking for busybox... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... fail!
I can keep tapping try again over and over but it never really gets past that step sooo, I'm stuck. I was hoping someone could help me out? If you can't, thanks for reading. If you can, I'd appreciate it very much! I live out in the middle of nowhere with no such thing as internet (other than what I can hardwire tether) and all I want to do is connect my Wii to the wifi on my phone.
I have the same problem. A work around is this...
You can download the appropriate su binary here...
androidsu.com/superuser
Then, flash it through recovery. It should update the binary no problem. However, it does not correct the problem. At least you'll have an updated binary.
If someone else knows what the problem is, that would be helpful in easier updates in the future.
Thanks for the quick reply! Though, can you explain what you mean by "flash it through recovery"? That's the only terms I'm not familiar with regarding this. Thanks again!
You need to use Clockwork Mod Recovery.
1) Install Rom Manger from the market.
2) Open up Rom Manger and install Clockwork Mod Recovery. Choose the appropriate phone model.
3) Reboot into recovery from Rom Manager.
4) Flash update using zip.
5) Select appropriate zip.
6) Reboot
How do I install Clockwork Mod Recovery? Where? Sorry if I'm asking to many questions.
taplamp said:
So I rooted my phone using the SuperOneClick method, and got my superuser app and everything but when I try to run Barnacle Wifi Tether, Superuser never prompts, and Barnacle complains that I haven't rooted my phone.
So I go into the preferences of Superuser snooping around to see whats wrong, and I come across (under the general tab) Su binary vnull. I tap it to check for updates and it goes like this:
Working...
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3
Checking installed version = legacy
So it says at the top new version of su binary found.
Update now?
I tap update and this happens:
Working...
Fixing database... okay!
Checking for busybox... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... fail!
I can keep tapping try again over and over but it never really gets past that step sooo, I'm stuck. I was hoping someone could help me out? If you can't, thanks for reading. If you can, I'd appreciate it very much! I live out in the middle of nowhere with no such thing as internet (other than what I can hardwire tether) and all I want to do is connect my Wii to the wifi on my phone.
Click to expand...
Click to collapse
i dunno how u have rooted your phone... but u shud do it this way. i have galaxy y and i did it this way and this might help!!!!
go to this site
http://forum.xda-developers.com/showpost.php?p=18811169&postcount=16
Are you reading?
kingsnakelegend said:
You need to use Clockwork Mod Recovery.
1) Install Rom Manger from the market.
2) Open up Rom Manger and install Clockwork Mod Recovery. Choose the appropriate phone model.
3) Reboot into recovery from Rom Manager.
4) Flash update using zip.
5) Select appropriate zip.
6) Reboot
Click to expand...
Click to collapse
Yes, I'm reading.
I'm no stranger to modding phones. Just android OS'. No need for the big red lettering.
I downloaded ROM Manager. There is no option within this app to download and install this Clockwork Recovery Mod.
There is a button that says, "Flash ClockworkMod Recovery" and underneath it says, "You must have the ClockworkMod Recovery installled to flash and restore ROMS"
But being that I've explained that I'm unfamiliar with the terminology, "Flash ClockworkMod Recovery" Doesn't sound the same as installing. Is that the button I should tap?
has anyone found a easy solution for this? i rooted my X10i on 2.3.3 stock and could update binary fine before now i've flashed DooMLoRD's v06 1113MHz overclocked kernel and flashed the RevolutionHD ROM im having problems updating my binary it says
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3
Checking installed version = 2.3.2-efgh
Fixing database... okay!
Checking for busybox... okay!
Checking current install path... fail!
Failed to find currently installed su binary. update cannot continue
im guessing that means i have not got any su binary atall?
---------- Post added at 02:19 AM ---------- Previous post was at 01:48 AM ----------
also i can't seem to download the latest superuser app from the market, it says your device is not compatible
I'm having the same message as TC. I'm on a SGH-T679 right now which doesn't have a version of CWM available for it yet (at least its not listed in ROM Manager). Any other way to install it? Can I just use ADB to push it to it?
Sorry buddy
taplamp said:
Yes, I'm reading.
I'm no stranger to modding phones. Just android OS'. No need for the big red lettering.
I downloaded ROM Manager. There is no option within this app to download and install this Clockwork Recovery Mod.
There is a button that says, "Flash ClockworkMod Recovery" and underneath it says, "You must have the ClockworkMod Recovery installled to flash and restore ROMS"
But being that I've explained that I'm unfamiliar with the terminology, "Flash ClockworkMod Recovery" Doesn't sound the same as installing. Is that the button I should tap?
Click to expand...
Click to collapse
I am with you buddy. That is one thing I have noticed with people familiar with programming, they seem to be oblivious when providing steps because many of their steps include further steps they simply view as inherent and fail to explain in depth. His steps do not clearly define what needs to be done to those not familiar. Of course they tend to get mad more often and say "If you don't understand you should't be messing with it anyways!" or something, unfortunately. I have been looking for a few hours hoping to find someone who not only knows how to do this, but is also familiar with technical writing, which is hard to do on this site surprisingly haha.
taplamp said:
Yes, I'm reading.
I'm no stranger to modding phones. Just android OS'. No need for the big red lettering.
I downloaded ROM Manager. There is no option within this app to download and install this Clockwork Recovery Mod.
There is a button that says, "Flash ClockworkMod Recovery" and underneath it says, "You must have the ClockworkMod Recovery installled to flash and restore ROMS"
But being that I've explained that I'm unfamiliar with the terminology, "Flash ClockworkMod Recovery" Doesn't sound the same as installing. Is that the button I should tap?
Click to expand...
Click to collapse
Although I imagine you may have figured this out by now -- yes, in this case (and I find it hard to believe that anyone who's familiar with modding phones wouldn't infer this) you're being expected to understand that "Flash ClockworkMod Recovery" would install it to your phone. Press that button and then follow the rest of the directions that several people have already given you in plain english.
Incoherent said:
I am with you buddy. That is one thing I have noticed with people familiar with programming, they seem to be oblivious when providing steps because many of their steps include further steps they simply view as inherent and fail to explain in depth. His steps do not clearly define what needs to be done to those not familiar. Of course they tend to get mad more often and say "If you don't understand you should't be messing with it anyways!" or something, unfortunately. I have been looking for a few hours hoping to find someone who not only knows how to do this, but is also familiar with technical writing, which is hard to do on this site surprisingly haha.
Click to expand...
Click to collapse
This question has nothing to do with "programming" knowledge or talking in obtuse technical terminology -- it's just the basic assumption that if someone has found the XDA-Developers forum and has rooted their phone, they typically don't have to be told that flashing something to their phone installs it.
Same issue
I have the exact same issue as the Taplamp.
Here are the steps I have tried with the same issue -
1. When running SU Bionary update, it fails @ Md5sum.
2. SU Update Fixer Fails @ Root access.
3. Installed Clockworkmod failed to install/run because "An error occurred while attempting to run privileged commands"
4. recovery will boot up fine, however, when trying to load Update.zip, fails and aborts install (without clockworkmod installed) - figures!
5. Resetting catch and wiping memory and reactivating the phone will allow it to work for a few seconds then starts failing.
6. I went to the source and got the updated information on androidsu.com/superuser but when trying to flash it fails.
I may aim to flash my phone via RSD Lite but if anyone has any ideas, I am open to try.
------------------------------------------------------------------------
I do have two rooted droid's, both the same phone. Would it be possible to copy/paste the files on the working one over the one failing?
I would try this, however I am at work.
Does not work with CWM flashing...
I have the same problem: "md5sum...fail".
I tried with "su update fixer" and also with "CWM". No success.
Can anyone help us please?
I figured it out ! WORKS 100%
What you have to do:
1. Download & install BusyBox.
2. Open BusyBox and inside the program make the update (it will show you the update, don't worry)
3. After the update is finished, try to update superuser md5sum.
4. ENJOY !!! This is how simple it worked for me!
Hit a thanks for me...
track13 - That method worked for me, so thankyou!
For the record the steps I completed were:
(1) Install Busybox from Google Play (https://play.google.com/store/apps/details?id=stericson.busybox&feature=search_result)
(2) Re-ran the Superuser (SU) update
That's it!
track13 said:
I have the same problem: "md5sum...fail".
I tried with "su update fixer" and also with "CWM". No success.
Can anyone help us please?
I figured it out ! WORKS 100%
What you have to do:
1. Download & install BusyBox.
2. Open BusyBox and inside the program make the update (it will show you the update, don't worry)
3. After the update is finished, try to update superuser md5sum.
4. ENJOY !!! This is how simple it worked for me!
Hit a thanks for me...
Click to expand...
Click to collapse
I do appreciate the effort that you've put forth in finding a solution and I can see that you've helped a couple of other users as well! Awesome.
Unfortunately though, by the time I came back to the xda-developers forums I've been trying to figure out how to remove all traces of root and removing the Superuser.apk because the only reason I originally wanted to root was to freely use wireless tethering apps, but since FoxFi's release, I've lost the need for it.
So now I'm trying to get rid of Superuser because I've got an upgrade in a few months and I'd like to trade this device in towards credit, anyone got experience with this?
Thanks again, track13.
it worked for me
tnx it worked for me:
[1]:
1) Install Rom Manger from the market.
2) Open up Rom Manger and install Clockwork Mod Recovery. Choose the appropriate phone model.
3) Reboot into recovery from Rom Manager.
4) Flash update using zip.
5) Select appropriate zip.
6) Reboot
[2]:
1) Install Busybox from Google Play (https://play.google.com/store/apps/d...=search_result)
2) Re-ran the Superuser (SU) update
taplamp said:
So I rooted my phone using the SuperOneClick method, and got my superuser app and everything but when I try to run Barnacle Wifi Tether, Superuser never prompts, and Barnacle complains that I haven't rooted my phone.
So I go into the preferences of Superuser snooping around to see whats wrong, and I come across (under the general tab) Su binary vnull. I tap it to check for updates and it goes like this:
Working...
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3
Checking installed version = legacy
So it says at the top new version of su binary found.
Update now?
I tap update and this happens:
Working...
Fixing database... okay!
Checking for busybox... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... fail!
I can keep tapping try again over and over but it never really gets past that step sooo, I'm stuck. I was hoping someone could help me out? If you can't, thanks for reading. If you can, I'd appreciate it very much! I live out in the middle of nowhere with no such thing as internet (other than what I can hardwire tether) and all I want to do is connect my Wii to the wifi on my phone.
Click to expand...
Click to collapse
Ok so I know this thread has been dead for a while but I just wanted you and anyone else out there in the realm of this question and goal to know barnacle or any other tether like it that creates an adhoc network to share it's connection can't be used on a wii, wii is incapable of joining an adhoc wifi network, so you'll need to find another wifi solution anyhow.
Thank boss ama give that a try I got no pc and phone is galaxy j100
I've read the dedicated thread on rooting the TF700t with DebugfsRoot_v1.9 (http://forum.xda-developers.com/showthread.php?t=1706588&page=48).
I did successfully root a TF700t with 9_4_5_22.
Now I tried the same method after upgrading another TF700t from stock to 9_4_5_26.
Everything works fine during rooting (I've tried both manual and automated DebugfsRoot 1.9) with the following exceptions:
1. during the 3rd stage of rooting, I get
/system/bin/sh: /system/xbin/su: not executable: magic 7F45
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
I tried both under XP and 7/32 on the same device, no errors but root does not seem to be active. Between rooting attempts, I restored stock ROM.
Other details:
Asus USB drivers installed (off Asus website)
Asus synch is disabled and prevented from launching.
Security/Unknown sources is checked.
Developer options / USB debugging is ON/checked.
What do you think goes wrong?
Any help is appreciated. Thx
the same..
I have nearly the same problem...
I have updated my rooted .21 to .26, then unlocked it and as it seems have lost root. I dont really know if it happened afted updating or afted unlocking...
None of my R-applications can get root, and so on...
I've tried to use the same method i used to get root on .21 and got this:
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 1469
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
And still no root...
What am i doing wrong? What to do next?
Thanks!
Is it a superuser problem?
EnginesRun said:
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
Any help is appreciated. Thx
Click to expand...
Click to collapse
Can't help yet but I am having a similar problem with SU; its presence suggest I have root but it denies everyone else SU permissions...
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
alienedd said:
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
Click to expand...
Click to collapse
nope. doesnt help in my case..
---------- Post added at 10:17 AM ---------- Previous post was at 09:37 AM ----------
ok, i've solved my problem.
the idea mentioned by alienedd helped me to see that i could have a working root but faulty superuser app.
so i started with installing it from market.
then i ran DebugfsRoot_v1.9.
till it got to this point:
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(m ount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),30 03(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
then i have cleared all the data held by superuser app through settings\apps, stopped it and uninstalled.
after that i continued with the script and it installed me superuser app again.
after installing i've launched it and then ckecked my root-needed apps. they are ok now.
Ahhh, yeah. Read about that in the DebugFS thread that sometimes one needs to uninstall superuser then reinstall for it to run properly. Didn't think about that. Glad that its all working now for yas.
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
henbone11 said:
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
Click to expand...
Click to collapse
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
alienedd said:
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
Click to expand...
Click to collapse
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
henbone11 said:
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
Click to expand...
Click to collapse
Yeah, I understand. Um, I know I've repeated this several other times but I don't see it in your list of things you've done. Were you able to open up the superuser application? It seems that if it opens, you have root, and in some cases might not work until it is opened. It's both fortunate and unfortunate that I did not encounter many problems while rooting so my experience with possible errors isn't that expansive. However, you've run the package(s) completely so it's not a driver issue and you can adb and see su access. It just seems like the tablet isn't recognizing that it does have it.
yeah, I ran superuser immediately after rooting. then rebooted each time. http://forum.xda-developers.com/showpost.php?p=29951628&postcount=494
lol thats everything that I have tried. kinda sucks, but im sure someone will figure it out at some point.
weird thing is, if I run a command prompt from within the package folders I see that its rooted. if I run terminal on the device it says permission denied and prompt is still $. just odd.
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
alienedd said:
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
Click to expand...
Click to collapse
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
henbone11 said:
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
Click to expand...
Click to collapse
Perhaps this then?
d14b0ll0s said:
Perhaps this then?
Click to expand...
Click to collapse
Ok, I followed this http://forum.xda-developers.com/showpost.php?p=28519641&postcount=11 and was successful in rooting mine and my gf's infinity's.
one thing though. after manually rooting, after the final reboot, go into the Superuser app. DO NOT UPDATE IT FROM WITHIN THE APP. for some reason, updating from within Superuser borks the app. at least it did for mine and my gf's.
optional:
close Superuser. go to the play store and download busybox installer (needed to run titanium backup), root checker (there are a ton, just pick one of the top ones), adaway, ota rootkeeper and titanium backup. doesnt matter what order. I would run busybox installer first though once you have everything installed. after busybox installs, you can run root checker, adaway or titanium to check root. I say after you install busybox because some apps do require busybox to be installed before they consider you rooted. if you get the superuser prompt to allow/deny, everything is working fine. once you know that you have root and everything is working ok, run ota rootkeeper.
my only question at this point is regarding OTA updates. to my understanding, simply rooting will allow you to continue to receive OTA updates, but unlocking the bootloader will prevent you from getting OTA updates...is this correct?
HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR or 7-zip).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here.
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Stopping AT&T Auto Software Update
Since AT&T just rolled out the new update (4.3), I add this short guide on how to stop it before it becomes late! Note that these steps require root, so you should follow the rooting steps first.
Download and install "App Quarantine ROOT/FREEZE" from Play Store.
Open the app and go to settings by tapping on the wrench icon at the top right of the screen.
Uncheck the "Hide system services" option.
Go back to the app and select "AT&T Software update".
Tap on the lock icon on the top right of the screen.
It may ask you to enable the USB debugging.
Feel safe from AT&T's new attack
How to get MK2 without losing root
I have tested this approach and it worked for myself. You should consider the risk of losing the root access and follow these steps on your on risk:
Root your MF3 phone using the approach described earlier in this post.
Stop AT&T from pushing the update as described above.
Install Super SU Pro. Note that this is not a free app and it is an add-on for Super SU.
Run Super SU. Go to Settings and check the "Survival Mode". If you don't have this option, probably you don't have the Pro version.
Disable your guard against the AT&T update by enabling "AT&T Software update".
Let the device update itself and hope for the best.
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
MF3
Can't wait to try it...
Sent from my SAMSUNG-SGH-I337 using xda premium
I get permission denied. In terminal emulator I type
CD /mnt/extSdCard
./pwn
Then it says permission denied
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Billsfan99 said:
I get permission denied. In terminal emulator I type
CD /mnt/extSdCard
./pwn
Then it says permission denied
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Same here
Nick James said:
Same here
Click to expand...
Click to collapse
Sorry guys. I missed one step. You should format the external SD card to exFAT. Windows supports it.
Question
Does this mean that we can flash Google Edition rom on the MF3 AT&T S4?
Or do we have to wait until more exploits are discovered?
I was rocking GE rom until I went back to the stock Samsung ROM to SIM unlock my phone.
I got screwed by the OTA MF3 and have been following this forum everyday for a new root method.
ddslee said:
Does this mean that we can flash Google Edition rom on the MF3 AT&T S4?
Or do we have to wait until more exploits are discovered?
I was rocking GE rom until I went back to the stock Samsung ROM to SIM unlock my phone.
I got screwed by the OTA MF3 and have been following this forum everyday for a new root method.
Click to expand...
Click to collapse
This only allows you to root your device. No method to use custom ROM has been found yet.
So my phone WAS rooted, stock ROM.
I installed the OTA update on accident.
Ran the new exploit
Installed SuperSU
It asked me if I wanted to update the binary, I told it "Continue" and it comes back with "failed"
I suspect this is because of my previous root?
Nick James said:
So my phone WAS rooted, stock ROM.
I installed the OTA update on accident.
Ran the new exploit
Installed SuperSU
It asked me if I wanted to update the binary, I told it "Continue" and it comes back with "failed"
I suspect this is because of my previous root?
Click to expand...
Click to collapse
No need to install anything yourself. Uninstall everything and run SuperSU. Let it update itself. If that doesn't work, a reboot may help.
Also try to make sure that you have root.
jortex said:
No need to install anything yourself. Uninstall everything and run SuperSU. Let it update itself. If that doesn't work, a reboot may help.
Also try to make sure that you have root.
Click to expand...
Click to collapse
I never had SuperSU installed though.
You're talking about this, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Right?
Nick James said:
I never had SuperSU installed though.
You're talking about this, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Right?
Click to expand...
Click to collapse
Yes. It is being installed by the script.sh. You just need to update it. That's it.
jortex said:
Yes. It is being installed by the script.sh. You just need to update it. That's it.
Click to expand...
Click to collapse
I'm not following you. What do you mean I just need to update it? The script never installed it. I had t download it from the market and once I did that it asked me, upon opening it for the first time, "The SU binary needs to be updated. Continue?" and when I hit Continue it then says "If you have a custome recovery like TWRP or CWM, that can be used to (try to) install the SU binary. this is recommended for HTC devices. How would you like to install the SU binary? Normal or TWRP/CWM
I've tried both options with no luck.
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Nick James said:
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Click to expand...
Click to collapse
Mine said the same thing. I just kept going and typed the ./script.sh and thats it.
Nick James said:
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Click to expand...
Click to collapse
That's fine. It tries several exploits. The first one does not apply to your device (SG4), but the last one does.
UPDATE: You already "obtained root". Look at the prompt which is changed from $ to #. As wahbob suggested, continue running script.sh. This file installs SuperSU for you. Then you can run it without explicitly getting it from Play Store.
jortex said:
This only allows you to root your device. No method to use custom ROM have been found yet.
Click to expand...
Click to collapse
Ahhh Thanks for the root though!
Thanks! Just tried it and I have Root again
thanks for this
Sorry for the noob question but when I run the cd/mnt/extsdcard command I get a "not found". Does anybody know what I'm doing wrong?
OK I have run the pie exploit about 100 times every time I get the correct output but when I use root checker it says I don't have root I try to install super su and it says there are no binaries installed what am I missing my device shows up I put the update package in my sdk folder advice pushes the files I reverted back to 19.5.3 I get the exact same message that is expected when everyone else runs pie please help I have a Verizon Droid mini do I need to disable fire walls or avg
ojodetigre said:
OK I have run the pie exploit about 100 times every time I get the correct output but when I use root checker it says I don't have root I try to install super su and it says there are no binaries installed what am I missing my device shows up I put the update package in my sdk folder advice pushes the files I reverted back to 19.5.3 I get the exact same message that is expected when everyone else runs pie please help I have a Verizon Droid mini do I need to disable fire walls or avg
Click to expand...
Click to collapse
I got the same error messages. Get Root Check, and ignore the errors, and once it's sent, see if that works. It doesn't allow you to update the binaries though, until you do the full root with the WPnomo described in the Pie thread
Elaborate
livinitwarrior said:
I got the same error messages. Get Root Check, and ignore the errors, and once it's sent, see if that works. It doesn't allow you to update the binaries though, until you do the full root with the WPnomo described in the Pie thread
Click to expand...
Click to collapse
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
ojodetigre said:
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
Click to expand...
Click to collapse
You need to make sure everything like your firewall, avg, security is all turned off or it won't work.
Rooted Droid Ultra
ojodetigre said:
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
Click to expand...
Click to collapse
sorry, I never got a notification from this. No, root checker SHOULD tell you if you have root. Are you running each of the 4 commands separately?
livinitwarrior said:
sorry, I never got a notification from this. No, root checker SHOULD tell you if you have root. Are you running each of the 4 commands separately?
Click to expand...
Click to collapse
I plug my phone in, cd to the path of my sdk, adb devices to make sure it's recognized then run the four commands separately and phone does nothing it doesn't reboot just stays the same run root checker and it says I'm not rooted the guy before you says to turn avg and firewalls off I'm going to try that when I get home
ojodetigre said:
I plug my phone in, cd to the path of my sdk, adb devices to make sure it's recognized then run the four commands separately and phone does nothing it doesn't reboot just stays the same run root checker and it says I'm not rooted the guy before you says to turn avg and firewalls off I'm going to try that when I get home
Click to expand...
Click to collapse
Reboot? It shouldn't reboot. The phone should technically do nothing until you do root checker. The way this root works, it's tethered, and gets wiped once you reboot unless you do the next steps of using wpnomo
Sent from my XT1080 using XDA Premium 4 mobile app
Just asking a little thing. USB debugging enabled?
Rooted Droid Ultra
Pie alone isn't going to give you the root that you are looking for. All Pie does is give you root access to the /system partition.
You need to go here: http://bit.ly/1sxDN9t and disable Write Protection, which will allow you to flash the SU binary that gives full root.
After that is done you need to install Safestrap ((Can be found here: http://bit.ly/1jq4WeO) Our device is the XT1080), reboot into recovery and flash: http://download.chainfire.eu/396/SuperSU/
Now when you boot up you will have permanent root, and root check / SuperSU should show up properly.
Through OTA?
miketoasty said:
Pie alone isn't going to give you the root that you are looking for. All Pie does is give you root access to the /system partition.
Click to expand...
Click to collapse
Will root access survive through an OTA update to 4.4.4?
joshs997 said:
Will root access survive through an OTA update to 4.4.4?
Click to expand...
Click to collapse
Yes after you do all the steps and buy SuperSu pro and enable survival mode to be able to update and keep root
Rooted Droid Ultra
joshs997 said:
Will root access survive through an OTA update to 4.4.4?
Click to expand...
Click to collapse
Root survives but write protection gets disabled. So the root is basically useless.
I've never really had to use adb much before on any of my other devices. It's eating my lunch, and is frustrating because everyone is saying how easy it is. I honestly am having issues simply pushing the pie exploit to my phone. When I do, all correct directories, it gives me the adb info and shortcut stuff, definitions, etc. Any help would be appreciated. Just don't know adb well at all.
Edit: nm. got it.