Database Info

[Q] ATT Samsung Galaxy S2 Skyrocket will not root!

I have been trying to root my phone for about a week now and i am getting no where. I have been trying to use superoneclick and it keeps on saying failed. Installed the drivers for the phone also and still nothing. PLEASE HELP!!

xgame4u said:
I have been trying to use superoneclick and it keeps on saying failed.
Click to expand...
Click to collapse
I used this method to root my phone. I actually found this method to be a lot easier than superoneclick. As long as you follow the instructions in the first post of the thread you should be okay.
BUT, if you have permissions problems (or if you're not sure what they mean by "run the batch file"):
Right-click on cmd.exe in the start menu, select run as administrator then navigate to the folder extracted. For instance if you saved the file in your users downloads folder then navigate to: x:\users\[user name]\downloads\Skyrocket-Easy-Root and then type root.bat and press enter.
If you need help with that method, let me know. I didn't bother with superoneclick.

Try this from Copperhead! Worked beautifully!
http://forum.xda-developers.com/showthread.php?p=19223405
Don't forget to thank copperhead :thumbup:
Sent from my SGH-I727R using xda premium

Thanks!
thanks guys finally got it done!!

OneClick 4.0.4 - Can't root!
This is the first time I've rooted or flashed on my Skyrocket. I got tired of AT&T sitting on their asses with ICS and found OneClick's 4.0.4 UCLE2.
I was able to root with Odin and CWS on AT&T's stock 2.3.6 and backup my data with Titanium, and need my WiFi keys back... but I can't root again!
Odin and superuser.zip has failed after 13 attempts, SuperOneClick freezes on my Windows box (I use Ubuntu 12.04 on my Main box), and Skyrocket Easy Root fails because of permission issues. No method here works.
Am I doing something wrong, or is 4.0.4 un-rootable at the moment? I need the WiFi key for work and the only person with the password will be in Greece for two weeks!
I also can't force /system into r/w mode, with any tools (won't show up in bash, Total Commander can't mod it).

Frost58 said:
This is the first time I've rooted or flashed on my Skyrocket. I got tired of AT&T sitting on their asses with ICS and found OneClick's 4.0.4 UCLE2.
I was able to root with Odin and CWS on AT&T's stock 2.3.6 and backup my data with Titanium, and need my WiFi keys back... but I can't root again!
Odin and superuser.zip has failed after 13 attempts, SuperOneClick freezes on my Windows box (I use Ubuntu 12.04 on my Main box), and Skyrocket Easy Root fails because of permission issues. No method here works.
Am I doing something wrong, or is 4.0.4 un-rootable at the moment? I need the WiFi key for work and the only person with the password will be in Greece for two weeks!
I also can't force /system into r/w mode, with any tools (won't show up in bash, Total Commander can't mod it).
Click to expand...
Click to collapse
with superoneclick are you using zergrush?

zergRush = fail
I need to find the setting to get emailed when someone posts to a thread I'm involved in.
I tried zerg and it didn't work, but updating CWM to 5.8x and the 3.x version of superuser.zip did the trick.
I read in other threads that the screen flickers and the keys don't work with the touch interface, but I got it.
Now I just need to figure out how to do a batch restore with Titanium and get my Uverse, WiFi settings, and Opera bookmarks back.
Thanks for asking Decepticaons: So far I'm happy with 4.0.4, but was expecting individual contact SMS tones to be available... perhaps there's a ROM for that?

[ROOT][TOOL][2012-07-24] GS3DebugFSRoot: Root the Verizon GSIII without flashing

THIS WILL NOT WORK WITH JELLY BEAN.
---
Here's a easy-to-use tool based on the method in this thread.
If you like this tool, please click the Thanks button!
Even better, see my signature.
DISCLAIMER: As with any rooting tool, there is some chance that something will go wrong. Use of this tool is at your own risk, and I will not be responsible if you brick your phone in the process. Although there have been zero reports of this tool breaking anyone's phone, don't run it if you aren't comfortable with the possibility of having something go wrong and having to re-Odin back to stock or worse.
Instructions:
Install the USB drivers if you don't have them already: Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Download the package and extract it somewhere (you'll need 7-Zip or some other modern compression tool) Make sure you extract all the files to a folder somewhere! Running it straight from your compression program probably won't work.
On your phone, enable installation of third-party apps (Settings --> Security --> Unknown sources, near the bottom in the "Device administration" section)
On your phone, enable USB debugging (Settings --> Developer options --> USB debugging)
On your PC, make sure you don't have any other Android devices connected, any Android emulators running, or any Android tools like PdaNet running.
Plug your phone into a USB port on your computer. For best results, use a port directly on the machine, and not a USB hub.
Double-click RootDebugfs.bat and follow the directions on the screen. Your phone will reboot 3 or 4 times during the process; just leave it plugged in. To be safe, don't switch to any other applications while the root process is running.
DOWNLOAD GS3DebugFSRoot R2 FOR US GALAXY S III VARIANTS ONLY!!!
(Released July 24, 2012)
If anything goes wrong, post here and I'll see what I can do.
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser

Version History:
The most recent version is always at the top.
r2 2012-07-24
+ Changed font color to white for readability
+ Cleaned up output
+ Fixed typo in title (GSII instead of GSIII)
+ Fixed Unknown Sources/USB Debugging directions
+ Included latest version of adb from platform-tools 13, might make things more reliable
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Known to work with LF2 and LG1.
r1 2012-07-23
* Initial beta
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Works with LF2. Probably works with LG1.
Possible future features:
* APK version of the tool! I'm still not sure if this is possible - currently researching.
Sadly, I don't think this is going to happen.
* Unroot tool.
* Choice of Superuser or SuperSU.

FAQs:
Q: What versions of the stock ROM does this work with?
A: It's known to work with anything from LF2 up to LHE. It seems likely that DebugFSRoot will be able to work with any ICS ROMs. We'll have to wait and see if it works on JB or not.
Q: I'm getting an error like "adb is not recognized as an internal or external command", or "cannot stat 'su': No such file or directory". What do I do?
A: Don't run the tool straight from your compression program. Make sure to extract all the files somewhere first.
Q: Will this wipe my data?
A: Nope.
Q: How can I unroot? Will flashing a stock ROM unroot?
A: Flashing a stock ROM will unroot and also remove any modifications you made to /system.
Q: Everything seems to have worked fine, and the Superuser app shows the binary as present and working. However, none of my root apps work. What do I do?
A: This seems to happen to a very small number of people, and the cause is unknown. If this happens to you, try installing Chainfire SuperSU.
Q: Is this any better than flashing the root66 ROM?
A: The end result should be pretty much the same, but this tool is much smaller to download than the root66 ROM.
A: If you are on a phone with the stock LG1 ROM update, root66 will downgrade you to LF2, while this tool will leave your ROM alone.
Q: Is this any better than using the VRALEC boot chain method?
A: The boot chain is a little more complicated. It requires flashing two bootloaders, flashing recovery, and using Triangle Away to reset the Custom Binary Download counter. If you intend to install a custom recovery/custom ROMs anyway, it's fine and probably quicker. However, if all you want is root to run Titanium Backup or other root apps, GS3DebugFSRoot is easier.
Q: Will this increment the flash counter?
A: Not on its own. If you flash anything else after rooting, however, you might, so read up on what you're doing.
Q: Will this cause the "custom unlock" boot screen to appear?
A: In general, no. However, the spyware Samsung/Verizon included (SysScope/libcordon) is paranoid, and a lot of tweaks you can do after rooting will trigger it. If you don't want to risk getting the custom unlock screen, don't freeze any apps using Titanium Backup and generally limit your tweaking to things you could do without root.
Q: Can Samsung/Verizon block this method in the future?
Yes. It's very possible that a future OTA will patch the exploit that this tool uses. If you want to root, it's always best to do it now!

I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.

DFieldFL said:
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
Also title says Galaxy S II not III.

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
The boot screen looks the same to me.

Worked for me, thanks

Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"

phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
Same thing happening to me.
EDIT: Just switched usb ports and unplugged and replugged my phone in and it worked!

If my gs3 came updated with the newest version, will this still work?

Next release will be out tonight after I test it.
DFieldFL said:
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Fixed in the next version. Also, I added those steps to the main post.
open1your1eyes0 said:
Also title says Galaxy S II not III.
Click to expand...
Click to collapse
Typo on my part. Will be fixed in the next release.
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
I'm not sure about this one. However, I had packaged a slightly older version of adb, which could cause a difference. The next release will have the latest adb.
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
I think so, but I don't know if it's been tested. Worst case should be that it would fail when trying to copy su into /system/xbin/, and you might have to manually clean up a few things:
Code:
adb shell
[COLOR="Red"]$[/COLOR] rm /data/local/tmp
[COLOR="Red"]$[/COLOR] mv /data/local/tmp.bak /data/local/tmp
[COLOR="Red"]$[/COLOR] rm /data/local/su
[COLOR="Red"]$[/COLOR] rm /data/local/debugfs
[COLOR="Red"]$[/COLOR] rm /data/local/debugfsinput
[COLOR="Red"]$[/COLOR] exit
Really worst case is that your /system is screwed up and you have to re-flash a stock ROM with Odin, but that is highly, highly unlikely with this method.

Thanks for this awesome tool!!! Will there be a reversal to what this script does, aka, non-root to reverse changes if necessary or will that require odin flash?

It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.

Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
edit: sorry I typed and posted this as others were doing the same... I couldn't delete or edit the post for a few minutes because of my newby status.

edthesped said:
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
Click to expand...
Click to collapse
You should be able to do it via adb shell.
Code:
adb remount rw
adb shell
$ su
# rm /system/xbin/su
# exit
And then uninstall the Superuser app.
I'll try and add it to the script.

Thank You ! so much ... The tool works perfectly on my stock VZ ... Finally can get rid of all the crap that VZ puts in.

Noxious Ninja said:
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Click to expand...
Click to collapse
That would be awesome. It would be cool if you could make it unroot as well. Keep up the good work!
Tap'd via SGSIII(!)

CooL Very Very CooL
Thanks Noxious Ninja

eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
Mine came with the update and I was able to root successfully with this tool. Very nice.

My Atrix 2 ME865 wont root!

okay so i stumbled across the idea of getting my atrix 2 rooted,
so i finally get all the drivers installed that i needed for adb to recognize the phone and then this happens, saying permission denied, not quite sure what is happening
also i have a picture of what it says exactly which i can send to you if that would further help,
any help at all would be much appreciated!

kiwibro92 said:
okay so i stumbled across the idea of getting my atrix 2 rooted,
so i finally get all the drivers installed that i needed for adb to recognize the phone and then this happens, saying permission denied, not quite sure what is happening
also i have a picture of what it says exactly which i can send to you if that would further help,
any help at all would be much appreciated!
Click to expand...
Click to collapse
Which method to root are you using, and which firmware/software version is you device currently running, and lastly do you have USB Debugging enabled on your device?

Apex_Strider said:
Which method to root are you using, and which firmware/software version is you device currently running, and lastly do you have USB Debugging enabled on your device?
Click to expand...
Click to collapse
the method i tried is MOTO_4.0.4_ROOT_V5 and it's currently running 4.0.4 and yes indeed i do.

kiwibro92 said:
the method i tried is MOTO_4.0.4_ROOT_V5 and it's currently running 4.0.4 and yes indeed i do.
Click to expand...
Click to collapse
don't know if this is of any help but it might,
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
The Superuser application, available in the Android Market, is recommended for managing root access.
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
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.
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.
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

I have got the same problem as you but someone answered my question.he said:
For my best understanding, 67.220.3.en05 is only available from the HKTW OTA update up to now (SBF is not available), which is known that it's not able to be rooted at this moment (except replacing the boot.img with the ASIA RETAIL version)
Sent from my ME865 using xda premium

thanks, guess i wont be rooting my phone then
sunnytse1 said:
I have got the same problem as you but someone answered my question.he said:
For my best understanding, 67.220.3.en05 is only available from the HKTW OTA update up to now (SBF is not available), which is known that it's not able to be rooted at this moment (except replacing the boot.img with the ASIA RETAIL version)
Sent from my ME865 using xda premium
Click to expand...
Click to collapse

Yeah,it's too bad
Sent from my ME865 using xda premium

a new phone it is then, haha.
sunnytse1 said:
Yeah,it's too bad
Sent from my ME865 using xda premium
Click to expand...
Click to collapse

sunnytse1 said:
For my best understanding, 67.220.3.en05 is only available from the HKTW OTA update up to now (SBF is not available), which is known that it's not able to be rooted at this moment (except replacing the boot.img with the ASIA RETAIL version)
Click to expand...
Click to collapse
Can you please check if /data/local/12m exists (and writable)? All these moto ICS root scripts depends on this vulnerability: http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ Would like to know if HKTW does things differently.

i tried accessing it via the computer and also through my phone using root explorer, but to access that folder says my phone needs to be rooted, so no luck, how do i go about flash the asia retail .img will that make any difference ?
kousik said:
Can you please check if /data/local/12m exists (and writable)? All these moto ICS root scripts depends on this vulnerability: http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ Would like to know if HKTW does things differently.
Click to expand...
Click to collapse

kiwibro92 said:
i tried accessing it via the computer and also through my phone using root explorer, but to access that folder says my phone needs to be rooted, so no luck, how do i go about flash the asia retail .img will that make any difference ?
Click to expand...
Click to collapse
You can flash the ME 865 China Retail using rsdlite..its rootable

thanks! sorry, but where abouts do i get the latest version from ? if not are there any other version that will work on this phone or will all version work ?
another question, sorry! am i able to use a custom rom to flash it then root ?
devilhunter47 said:
You can flash the ME 865 China Retail using rsdlite..its rootable
Click to expand...
Click to collapse
UPDATE: attempted to download the china retail but it's not allowing me to register to be able to download it, so any other options ?

kiwibro92 said:
thanks! sorry, but where abouts do i get the latest version from ? if not are there any other version that will work on this phone or will all version work ?
another question, sorry! am i able to use a custom rom to flash it then root ?
UPDATE: attempted to download the china retail but it's not allowing me to register to be able to download it, so any other options ?
Click to expand...
Click to collapse
Download from here
http://pan.baidu.com/share/link?shareid=5145&uk=3473189901

so i finally get around to flashing it and now the phone keeps crashing, awesome!
help please!
UPDATE:
managed to flash to the asia retail version, anyone point me in the right direction as to what's best to root the phone, please!
update 2: tried rooting the asia retail no luck, still saying permission denied, going to try downloading the china retail again even though it was crashing, maybe i had a faulty download, not sure!

kiwibro92 said:
so i finally get around to flashing it and now the phone keeps crashing, awesome!
help please!
UPDATE:
managed to flash to the asia retail version, anyone point me in the right direction as to what's best to root the phone, please!
update 2: tried rooting the asia retail no luck, still saying permission denied, going to try downloading the china retail again even though it was crashing, maybe i had a faulty download, not sure!
Click to expand...
Click to collapse
update 3: okay so i managed to flash china retail again, it keeps crashing and sometimes it even just hangs on the motorola logo, can anyone please point me in the direction of a rom or something that will work, the asia retail flashes and works properly but has the same problem as the hktw folder access is restricted. :/

kiwibro92 said:
update 3: okay so i managed to flash china retail again, it keeps crashing and sometimes it even just hangs on the motorola logo, can anyone please point me in the direction of a rom or something that will work, the asia retail flashes and works properly but has the same problem as the hktw folder access is restricted. :/
Click to expand...
Click to collapse
Were you able to resolve the issues? I also have 67.220.3.en05 and I'm uncertain about flashing the china retail...

http://bbs.angeeks.com/forum.php?mo...lter=author&orderby=dateline&orderby=dateline
Try this.if you can understand chinese
Sent from my ME865 using xda premium

I found using the china retail I ran into a multitude of crashes, I can provide the right one I found worked perfectly when I get on the computer,
Sent using xda app-developers app

hunpgod said:
Were you able to resolve the issues? I also have 67.220.3.en05 and I'm uncertain about flashing the china retail...
Click to expand...
Click to collapse
flash it with this, it's asia retail, it roots perfectly fine. - http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
then enable usb debugging through developer options in settings and connect usb.
and use this root by jim, http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip

kiwibro92 said:
flash it with this, it's asia retail, it roots perfectly fine. - http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
then enable usb debugging through developer options in settings and connect usb.
and use this root by jim, http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Click to expand...
Click to collapse
Thanks
I flashed it. Everything seems to be ok, root worked as well.

New Root Method for AT&T Samsung Galaxy S 4 (OTA MF3 + Safe update to MK2)

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?

[Q] Pie is killing me please help

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.