I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
is busy box installed?
is SU working?
feefeeboomboom said:
is busy box installed?
is SU working?
Click to expand...
Click to collapse
I haven't done anything since flashing the 2.1 RUU. What steps do I need to do to get busybox and su working?
if you installed the RUU that was just 'leaked' (from what i understood our 2.1 builds are based off this ruu already). The build does not include busy box or anything for that matter that is required for wireless tether-
damageless said:
Here is a link to the latest RUU from Sprint.
You cannot simply extract it. This still has root since it is a test release. I recommend just doing an adb pull of your system directory after you flash it. Don't do this when the final one comes out or else you might be stuck without root.
You will need to add busybox, patch sh and su, and make sure that you do another recovery image and such. I also recommend adding Superuser.apk and stuff. If you use the Desire build.prop, you can get most of the protected apps working.
Enjoy.
http://dl.damagedroms.com/2.0/RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe
Leak, I know who you are.
Click to expand...
Click to collapse
http://benno.id.au/blog/2007/11/14/android-busybox
Busy Box link for you, I'm not really sure how to get it working but it's a start, alot of results come up if you google "busybox for android", so I hope that helps ya out bud
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
dwertz said:
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
Click to expand...
Click to collapse
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root
Click to expand...
Click to collapse
Who told you that the RUU was rooted already? It's not. Why would it be? Sprint has no interest in you being root.
As for why do you have to install busybox? Because the application requires it.
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
mobilehavoc said:
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
Click to expand...
Click to collapse
Here is the superuser.apk You have to have root.
Put superuser.apk in your C:\AndroidSDK\Tools\
adb remount
adb push superuser.apk /system/app/
mobilehavoc said:
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
Click to expand...
Click to collapse
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
Not sure what you mean but I was able to push a new build prop onto the phone using adb with no issues.
posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
The leak actually is rooted. It's an engineering leak, so root can work his magic- but only from the adb shell.
why do you need superuser?
superuser requires root, if you had root, you wouldnt need it.
you can just dl the wifi tether for root from the market
program and it would work right?
10 chars and a poke
Related
This is the latest Sprint Rom based on the latest RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
I have verified that A2SD is working as I downloaded and installed a couple of programs from the market. The programs are being stored in /system/sd/app.
Here's the link: http://www.darktremor.info/files/2.1/2.1-ruu-a2sd-signed.ziphttp://www.darktremor.info/files/2.1/sprintstock-21-a2sd-b-signed.zip
This one now has adb rooted (thanks to nfinitefx45 for his assistance) and does flash (heard complaints on the symlink issue...never sure what causes that, but ended up starting over and porting the files from the previous build).
This is for those people who want to keep with the stock installation but want the addition of A2SD. If you want a customized look, faster performance and A2SD support, I suggest a custom rom. Fresh 2.1.2 or FreshToast is a good one to use.
Note: It will not affect recovery.
Enjoy and I'll answer any questions you may have (if I can answer them).
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
tkirton said:
This is the latest Sprint RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
This is definitely an RUU as when I go into adb shell, I get the dollar sign as a prompt rather than the pound sign...I'm pretty certain it is not rooted.
.
Click to expand...
Click to collapse
<<<snip>>>
This makes no sense at all.
Good point about the Rom vs RUU. Edited to correct.
As for the init.rc. Mainly it was init.rc edit.
regaw_leinad said:
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
Click to expand...
Click to collapse
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
wctom said:
<<<snip>>>
This makes no sense at all.
Click to expand...
Click to collapse
tkirton said:
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
Click to expand...
Click to collapse
Thanks, I'll just use your boot image for RegawMOD 2.5. saves me a few minutes
working perfectly all apps installed and 132 megs still open internal
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
sandboxlove said:
is it a general consensus that if you want to run a2sd successfully you should use a class6? i currently have a class4
Click to expand...
Click to collapse
right now, I switched back to my class 4 and its working great
nvmchars....
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
sandboxlove said:
i just want to be clear...this is the latest sprint leak? you seriously deodexed the whole thing?
i thought vince was crazy for trying, your completely BANANNAS
Click to expand...
Click to collapse
yeah, i thought I'd post it in here. Didn't think since it's the same thing as he posted but deodexed that I should make another thread.
and yes, the latest sprint leak. you should test this. I can't right now.
Oooh...cool. Enhancements. I like enhancements.
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
tkirton said:
Oooh...cool. Enhancements. I like enhancements.
Click to expand...
Click to collapse
Well, I like your work, so that's for you
did anyone test it out to make sure it boots?
Sorry to be such a noob, but what is "deodexed" a ROM mean?
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
Well I flashed it and stuck on the HTC screen. Flashed the non deodexed version and loads fine.
So apparently i f***ed up deodexing lol. I guess that ROM that I did wont work..
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Now that the A2SD stuff is behind me, I'll take a look at that. Flipzmode or Toastcfh may be able to shed some light on how you get this image rooted correctly, especially Flipz since he's using the latest leak for Fresh 2.1.1.
The original goal was to get A2SD working on a stock rom, which I did....but it is rather annoying that it isn't rooted (or fully rooted).
Damage said in his point that it was rooted, but I got the same thing you did...no root when doing adb.
I'll talk to Flipz or Toast and see if they can point me in a direction to go.
nfinitefx45 said:
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Click to expand...
Click to collapse
well this is a piece from some of the reading I've been doing I beleice this needs to be done with in the boot image. I dont know if this will help in your research,
-------------------------
You also need to modify the ROM update script to change the default permissions for /system/bin/su so it can be used to elevate privileges to root. The script is in $WKD/dst/META-INF/com/google/android/update-script. Open it in your favorite editor and find the line starting with set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh and after it add the following set_perm 0 0 04755 SYSTEM:bin/su
=======================
Hi tkirton,
Nice job on this and thanks for all your hard work on everything! I am also wondering what dedoxed means? Is it like where application data is also stored on the SD card instead of on the phone itself?
Thanks!
One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector!
Here's a new one click root. 2.4.0 now flashes clockworkmod recovery for you. It's also a little less likely to fail, and is tested to work on Froyo.
It will also work correctly if you are on a pre-rooted kernel. It will install superuser, busybox, and clockworkmod.
http://firon.net/xda/one.click.root.exploitv2.5.5.zip
Here's 2.5.0 of the one click root, now with the clockwork redirector integrated.
I cleaned up noobnl's script a little bit and ensured that adbd would run as root when booted into recovery. Also made sure we symlinked every single applet that recovery's busybox provides.
Now the one click also avoids pushing playlogo unless it detects that you have the old joeykrim root installed, to avoid any potential issues with future froyo releases.
Linux and Mac users users chmod +x run.sh and run it
THANKS FIRON
Here's 2.2.7, that simplifies the root process thanks to the discoveries here: http://forum.xda-developers.com/showthread.php?t=800483
I also increased the timeout after running the root (fails less), moved more things to /system/xbin to reduce the risk of breaking things, and removes all the old files leftover from joeykrim's root (including his modified playlogo that runs at boot every time).
It also means your system will no longer be mounted as read-only every time you reboot and there's no more problems with jk-su overwriting your existing su binary.
1. you need samsung galaxy s drivers
32-bit drivers: http://firon.net/xda/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
64-bit drivers: http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
2. push MENU, select Applications > Development, then enable USB debugging.
3. extract and run run.bat
4. enjoy!
v2.2.4 added busybox and the remount script and fixes sprint animation not showing
2.2.5 superuser.apk & su added!
v2.2.6 installs busybox to xbin
uninstaller http://firon.net/xda/one.click.stock.flasher.&.root.uninstaller-di18.zip
Any word on whether the OTA update (Hotspot/4G/AmazonMP3) breaks or makes this method not work?
lordcyrus said:
Any word on whether the OTA update (Hotspot/4G/AmazonMP3) breaks or makes this method not work?
Click to expand...
Click to collapse
no it doesn't break it
Gonna test this right now!
Sweet!!! Thanks!!! Going to do this after i get my epic after work.
Longest day ever!!!
OP. There is a really big step missing here. Guess what it is?
Hint: You need to have set the path in the command prompt for adb in order to work.
Fixter said:
Gonna test this right now!
Click to expand...
Click to collapse
You first Boriqua.
Fixter said:
OP. There is a really big step missing here. Guess what it is?
Hint: You need to have set the path in the command prompt for adb in order to work.
Click to expand...
Click to collapse
updated the post and dl link!
NOOB question, how do you know if your 32-bit, or 64-bit? Running Windows 7 basic on a net book.
Will this nand unlock?
vazquezcmp said:
NOOB question, how do you know if your 32-bit, or 64-bit? Running Windows 7 basic on a net book.
Click to expand...
Click to collapse
Odds are its 32 but heres how to check:
Click Start
Right Click Computer
Click Properties
Then look where it says System Type
32. Thanks man. I'm next.
Hmm.. Still not working.
Bring on the custom ROM's
Alright, well you needed to copy the folder to the Tools folder of the SDK.
I'm typically not brain dead but I'm lost
Working on Windows XP....
A) Installed the 32 bit drivers (strange that when I plug the phone into the USB cord the computer doesn't ever seem to acknowledge that I did so as it did with my BB?)
B) Tried to run the RUN and RUN 2 but I keep getting messages that no device is detected.
Obviously I'm missing something somewhere???????
jfenton57 said:
I'm typically not brain dead but I'm lost
Working on Windows XP....
A) Installed the 32 bit drivers (strange that when I plug the phone into the USB cord the computer doesn't ever seem to acknowledge that I did so as it did with my BB?)
B) Tried to run the RUN and RUN 2 but I keep getting messages that no device is detected.
Obviously I'm missing something somewhere???????
Click to expand...
Click to collapse
I'm not even seeing RUN2.
My phone went completely black. Not responding to anything.
I can see the device with adb devices and ran run.bat and then run2.bat and it rebooted the phone but I don't think I have root. How can I test it? I downloaded wireless tether and it doesn't broadcast.
GrandMstrBud said:
I can see the device with adb devices and ran run.bat and then run2.bat and it rebooted the phone but I don't think I have root. How can I test it? I downloaded wireless tether and it doesn't broadcast.
Click to expand...
Click to collapse
Download Titanium Backup.
Hello to all the kernels Devs,
I just want to share with you all the initramfs I use in my kernels.This initram has scripts that run on boot to give root and installs the Superuser.apk and Busybox along with a script that will allow people to easily remount the /system filesystem read write if changes need to be made I think this is the best way to run root on the Epic that way there is no need for rom devs to have to setup a rom to be rooted.The scripts in it are run from init.rc and sets up the phone for root and installs Busybox with a full compliment of applets.It is in working order and will work with Rom Manager.If you have any questions about it let me know.
Link to my initramfs.
http://www.mediafire.com/?aynk2gd05xuv6c0
Another link in case mediafire doesn't feel like working.
http://www.sdx-downloads.com/devs/skeeterslint/Epic-4G-initramfs.tar.gz
Updated to latest stable busybox version 1.17.3
does root explorer and metamorph work with this?
Root explorer will work when he updates it on the merket is is bugged right now, metamorph I can't say I never used it, Titanium Backup will work without having to install busybox through the app all root programs will work without issues. It sets su in /system/bin and /system/xbin so as to not break any root apps. The root script is in /sbin it is run from init.rc during startup, the busybox install is also run from init.rc and gets setup in /bin.
Sent from my SPH-D700 using Tapatalk
Metamorph works fine for me.
[email protected] said:
Metamorph works fine for me.
Click to expand...
Click to collapse
I thought it only worked with Cyanogen - what ROM/kernel are you using?
If root explorer has a bug and needs an update, is the same true for connectbot?
ragnarokx said:
I thought it only worked with Cyanogen - what ROM/kernel are you using?
Click to expand...
Click to collapse
Works with twiz also(worked on my behold 2) but not all themes work.
skeeterslint said:
Hello to all the kernels Devs,
I just want to share with you all the initramfs I use in my kernels.This initram has scripts that run on boot to give root and installs the Superuser.apk and Busybox along with a script that will allow people to easily remount the /system filesystem read write if changes need to be made I think this is the best way to run root on the Epic that way there is no need for rom devs to have to setup a rom to be rooted.The scripts in it are run from init.rc and sets up the phone for root and installs Busybox with a full compliment of applets.It is in working order and will work with Rom Manager.If you have any questions about it let me know.
Link to my initramfs.
http://www.mediafire.com/?q4n2mgb4d2l6ucv
Click to expand...
Click to collapse
Wont flash in clockwork,is this for odin?
Ummm no this is for kernel devs to build kernels with. It is the ramdisk that is inside the kernel.
Sent from my SPH-D700 using Tapatalk
Bump,
Joeys root exploit was never ment to be permanant was just a hold out till the source code was released and we could root with the kernel.its worth trying it out at least once
skeeterslint said:
Bump,
Joeys root exploit was never ment to be permanant was just a hold out till the source code was released and we could root with the kernel.its worth trying it out at least once
Click to expand...
Click to collapse
Hey bro I tried integrating your ramdisk into my kernel, but theres a few issues.
For one, ADB can still run as root, and I can get into it thru a shell, but I lose all root access in usermode. SetCPU fails. My Search2Play app fails. Nothing can get root. I believe its because of the SU binary you're using.
Any ideas?
Geniusdog254 said:
Hey bro I tried integrating your ramdisk into my kernel, but theres a few issues.
For one, ADB can still run as root, and I can get into it thru a shell, but I lose all root access in usermode. SetCPU fails. My Search2Play app fails. Nothing can get root. I believe its because of the SU binary you're using.
Any ideas?
Click to expand...
Click to collapse
Go into the default.prop and remove this ro.secure=0 thats a setting that koush had in it it gives a root shell in adb and that is probably what is breaking it.TThe su binary I am using is the the one that comes with Superuser.apk that you can download through Rom Manager.I don't seem to have any issues losing root on my phone.
skeeterslint said:
Go into the default.prop and remove this ro.secure=0 thats a setting that koush had in it it gives a root shell in adb and that is probably what is breaking it.TThe su binary I am using is the the one that comes with Superuser.apk that you can download through Rom Manager.
Click to expand...
Click to collapse
I didn't even know Koush had added that lol I'd had it in mine since day one. That would make since. But I'm not sure its the best idea. Then you can't adb remount or adb push to /system since it'll be in secure mode.
What path does your search2play use to find cp?Thats what fails on my phone I guess its not checking the whole path that is setup in init.rc which is export PATH /sbin:/bin:/system/sbin:/system/bin:/system/xbin.
Geniusdog254 said:
I didn't even know Koush had added that lol I'd had it in mine since day one. That would make since. But I'm not sure its the best idea. Then you can't adb remount or adb push to /system since it'll be in secure mode.
Click to expand...
Click to collapse
To be honest I thought i had changed that before I packed it up.Oh and whats up with setcpu it works fine for me other then being a bit unstable on any other setting except conservative which isn't the initram that cuases that its the phone its always been a bit unstable on the galaxy s from reading the other forums?
Initramfs is updated for DI18.
Updated again to fix issues with bluetooth.
skeeterslint said:
Updated again to fix issues with bluetooth.
Click to expand...
Click to collapse
How'd you fix Bluetooth? Was it just a change in the modules?
Geniusdog254 said:
How'd you fix Bluetooth? Was it just a change in the modules?
Click to expand...
Click to collapse
No was either sonething in init.rc or the init binary itself becuase the release i just replaced had the modules in it already.
skeeterslint said:
No was either sonething in init.rc or the init binary itself becuase the release i just replaced had the modules in it already.
Click to expand...
Click to collapse
I new to the whole kernel development, just starting out but how would I install this? Would I use menuconfig?
Right now I have me my kernel development environment all setup, and compiled my first working kernel for the epic. Thanks in advance.
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.
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.