One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector! - Epic 4G Android Development

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.

Related

For extreme noobs like myself info reg rooting & clockwork recovery

About a day ago I didn't know anything about rooting and what it was but now I know to a degree from many hours of reading.
These are the steps I did.
You have to make sure that you choose the correct one click root method for the DI07 patch. Obviously you need to put the epic in debugging mode and click on the appropriate run.bat command and let the batch run. That part wasn't to hard for me, pretty much self explanatory.
Also to check for "root", to make sure your epic is rooted, download titanium backup from the android market and if it launches your epic is rooted and plus it will say root status "ok"..
The part I had issues with was with the one click clockwork recovery. Especially when people started talking about typing in commands in the dos prompt. I'm ok with doing that but it wasn't explained in full detail regarding what to do.
So first thing that I had to figure out was what they meant by c:/android-sdk-windows/tools and where was this located. I didn't have this file on my cpu on the c: drive and i was lost at this point being that I didn't know where to get it. I later found out and if im wrong please tell me you had to create your own folder on your c: drive so you can point to it from the c: prompt in dos. So I went ahead and did that.
In the tools folder from android-sdk-windows folder you would go ahead and place the contents of the clockwork recovery files in the tools folder. So wahla I now have a folder I can point to in the dos prompt. At this point I still didn't know if this is going to work or not but I felt like I was close.
Next step was to follow "open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code."
adb devices
adb shell
su
remount rw
exit
exit
first you need to type cd C:/android-sdk-windows/tools and press enter to point to that folder. And run subsequent commands from there.
If when you type in adb devices and a device does not pull up that means that the usb drivers are not installed properly for the epic phone and you need to look into that first.
After you run those commands now you can go ahead and run the run.bat file for the clock works recovery. But also make sure your still in debugging mode.
This might take a few tries but it will eventually work and if it does not work after trying to flash the recovery and the epic reboots pull the battery (reinstall battery) and then try to go into recovery by pressing the vol down--camera--and power button at the same time and you should see a green recovery screen.
I wish someone had typed something like this sooner so I wouldn't of had issues.
I hope this helps at-least one person.
Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305
Whosdaman said:
Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305
Click to expand...
Click to collapse
I know I was trying to follow that but there was parts missing that I didn't understand for ex. the part where I had to create the actual folder it never stated to create a folder but it wanted you to point to it in the dos prompt. And yes that tutorial did help out tremendously but i was still a little lost. My explanation fills in the missing gaps or parts. But thank you for pointing that out.
Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?
jimmyz said:
Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?
Click to expand...
Click to collapse
That is correct. Version 32 is truly one-click.
mattallica76 said:
That is correct. Version 32 is truly one-click.
Click to expand...
Click to collapse
Thats true
I'm not quite as noobish as the OP but I'm a complete noob to Android and -nix os's in general (besides a tiny bit of unix experience and a non-fear of command-line interfaces). Still, I have enough fear of the process to wait until Epic ROMs are a little further along and more refined to the degree that that's possible. If I weren't quite so noobish I'd dive right in.

Samsung Transform

The Samsung Transform has the same vulnerability as the Epic (joeykrim-root.sh works to get root).
So how would I go about rooting? Would I use the same process as the EPIC 4g?
if you're good with linux, you can follow the directions in this link forum.sdx-developers.com/epic-development/adb-root-exploit-test
(The mount command is slightly different in step 4.)
I'm running a mac. I tried several guides on the sph-m910 rooting for mac osx but it won't let me push any files to the phone with adb.
Sent from my SPH-M920 using XDA App
Have any of you successfully rooted it using this method?
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
aliendude5300 said:
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
Click to expand...
Click to collapse
Here's a link to the zip file containing the exploit that worked: http://www.filedropper.com/ocr
drivers?
What drivers are you guys using? i cant get any drivers to install...
mark920 said:
What drivers are you guys using? i cant get any drivers to install...
Click to expand...
Click to collapse
From what I am told and understand it must be mounted and run in linux. I will find out as soon as my local store gets one in, I'm first in line.
aliendude5300 said:
I have successfully rooted my brother's Transform using the same method I used to root my Epic 4G... same files and everything.
Click to expand...
Click to collapse
Any link to the method you used?
aliendude5300 said:
Here's a link to the zip file containing the exploit that worked:
I've tried 8 times, cannot get it rooted. Suppose I'll wait just like the rest of us
Click to expand...
Click to collapse
berger1980 said:
aliendude5300 said:
Here's a link to the zip file containing the exploit that worked:
I've tried 8 times, cannot get it rooted. Suppose I'll wait just like the rest of us
Click to expand...
Click to collapse
I tried it as well. I couldn't get it to work either.
Click to expand...
Click to collapse
I got it to work. I tried it under my computer with Windows 7. I had to right click the run.bat and click properties, Click compatibility, Run this program in compatibility mode for Windows XP Service Pack 3. Thanks.
cachorropedorro said:
I got it to work. I tried it under my computer with Windows 7. I had to right click the run.bat and click properties, Click compatibility, Run this program in compatibility mode for Windows XP Service Pack 3. Thanks.
Click to expand...
Click to collapse
I don't mean to be a ****, but what app have you installed that requires root access? I have a specific one, roam manager, that will not run. I believe you may have seen visually that it was rooting it, but it does not do squat.
berger1980 said:
I don't mean to be a ****, but what app have you installed that requires root access? I have a specific one, roam manager, that will not run. I believe you may have seen visually that it was rooting it, but it does not do squat.
Click to expand...
Click to collapse
apps2sd, I need a new kernel for wifi tethering which is the main thing that I want
Rooting Help
Can someone give some detailed instructions on rooting the Samsung Transform???
I agree with cachorropedorro, I'm looking to root for wifi teathering also..... Tried a few methods also.... No luck.
Guys, I've never rooted a phone before and this is my first android. I looked a the Joeyconway version of root.... I'm having a hard time following the command prompts??? Any suggestions?
Is there going to be a transform category? Are there other pages about rooting this new phone??
I was able to root my transform using the ocr joey krimm root method, the drivers for the epic finally worked after restarting the phone, one thing i noticed about the transform was that the ratc script takes longer to work and does not always work. I modified the bat file to have a longer wait after running the ratc file, however that doesnt even work all the time, if you manually run the ratc script and then run the bat it should work thats what i had to do. I also updated the su bin and the busybox version from the current version of the one click root because the files in the ocr.zip have an older su bin that doesnt use superuser.apk and the busybox is not compatible with ti backup.
Mark920,
Can you give some more detailed directions for all of us that are newbees? Like I said in a earlier post, I've never rooted a phone so some of the things you were talking about like ratc script confuses me. Any detailed steps would be awsome.

Epic 4G All in One Root and Recovery 2.04 for Win Mac Linux *ClockworkMod Redirector*

Epic 4G All in One Root and Recovery 2.04 for Windows, Intel Mac, and Linux
***SORRY, AIO v2.04 IS CURRENTLY BROKEN FOR EB13, FIX IS COMING ASAP, USE ONE CLICK ROOT FOR NOW***
***WARNING NOT TO BE USED WITH ANY SUPPOSED LAGFIX, IT WILL SCREW UP YOUR SYSTEM AND YOU WILL NEED ODIN TO RESTORE***
OK, what started as scripts for my Mac turned out to be a big scripting project for Windows, Mac, and Linux.
This gives root and clockworkmod for all of the major operating systems.
This is like an Epic 4G swiss army knife, providing all of the basic tools in one convenient download.
These scripts give you a menu that allows you to choose between the following:
1) Simple One Click Root and ClockworkMod 2.04 - based on one click root 2.5.4 by noobnl and firon, compatible with Eclair and Froyo, ClockworkMod redirector for Froyo included
2) Andromeda Kernel 1.4.1 by noobnl - custom kernel with root, busybox and superuser, for 2.1 Eclair
3) SDX Stock App Remover 1.5 apk - back up and remove Stock Apps for rooted users
4) Wireless Tether 2.0.5-pre13 - Open source wireless tether for rooted users
5) Simple Root Uninstaller 2.04 - removes one clicks / z4root, Eclair and Froyo compatible
6) Reinstate Stock DI18 kernel for 2.1 Eclair
7) Reinstate Stock Samsung Recovery for Eclair or Froyo, uninstalls ClockworkMod and redirector
You could call this a noobnl festival for all operating systems...
PLEASE READ ALL MY NOTES BEFORE INSTALLING, I'VE FOUND LOTS OF PEOPLE HAVEN'T READ OR FOLLOW THE INSTRUCTIONS... FOR WINDOWS USERS, DRIVERS NEED TO BE INSTALLED CORRECTLY FOR THIS TO WORK.
http://dl.dropbox.com/u/500010/epic.aio.v2.04.zip
New! Now compatible with Android 2.2 Froyo, with ClockworkMod redirector included in script. Won't allow Eclair kernels or recovery to be installed on Froyo. ClockworkMod install now in Simple Root script. Wireless Tether added. Stock Samsung Recovery for Eclair and Froyo added.
NOTES: - Sorry so many in this page, but they really need to be listed Please at least read through until the end of the instructions before running this.
This is an all-in-one installer for the Epic 4G. When running this, the menu presented allows you to choose what you want to do, and does not install everything in one run. It is intended to only perform one menu item at a time.
If you just want to remove bloatware and run rooted apps, and don't intend to flash ROMs or rooted kernels, then just the Simple One Click Root will suffice by itself. This script now has a menu option to install SDX Stock App Remover, which is great at backing up and removing the Sprint bloatware. That will make it easy to bring back to stock and just remove root if it's necessary. Know what you're removing with the Stock App Remover, as removing the wrong system apps will get you into trouble!
Installing the Andromeda Kernel from this script does not require ClockworkMod Recovery. It can be uninstalled by flashing the stock kernel. The Andromeda kernel is already rooted, and does not require the one click root.
Clockwork Mod Recovery is used to flash other kernels, ROMs, and Mods. Instructions for booting into ClockworkMod are listed below. This is now installed with the Simple One Click Root, and a backup should be performed right away after installing it from the menu in ClockworkMod.
The past couple of generations of one click roots are safe with rooted kernels and ROMs, and are installed in /system/xbin, which is the last location in the path. Rooted kernels will just take precedence when installed.
Both the Simple One Click Root and the Root Uninstaller will remove the older joeykrim roots that use the hacked playlogo.
Because Superuser.apk is installed, superuser will ask permission before any program is granted root access. This is to ensure that no rogue program takes root privilege without your knowledge.
Booting into Clockwork Mod: Power down phone. Press and hold the camera button, then the volume down button, and then the power button, continuing pressure on all 3 keys until the Clockwork Mod menu appears, which will be seconds after the Samsung logo appears on the screen. The menu for Clockwork Mod Recovery has green text, instead of the blue text used by the stock Samsung recovery. Navigate up and down using the volume up and down keys, the power button goes back, and the camera button acts as enter key.
INSTRUCTIONS:
Before running, do the following on the phone from the home screen :
Press Menu > Settings > Applications > Development, and make sure USB Debugging is checked on your phone.
WINDOWS:
Samsung drivers are required:
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
Note: Driver installation under Windows 7 has been a pain for some, and has been the number one reason why people haven't been able to run the script successfully.
Also: DO NOT RUN run.bat as Administrator (by right clicking on the file and running as admin), the script will fail! Thanks to shepscrook for pointing this out.
Extract the zip file, and go inside the folder that was created with the same name.
Open run.bat (or just run) type in a number option, and press enter. Really easy (Hopefully ).
INTEL MAC & LINUX:
Note: Mac and Linux users may be prompted to enter administrative password, as adb server requires sudo permissions to start.
No drivers required.
Extract the zip file.
Open Terminal. Use the cd command to get to the directory. If you extracted inside the Downloads folder, it would be easy in Terminal as so:
Code:
cd ~/Downloads/epic.aio.v2.04
Now give permissions and run it:
Code:
chmod +x run.sh
./run.sh
THANKS TO FIRON FOR CODE MAKING THE SAME SCRIPT BOTH INTEL MAC AND LINUX COMPATIBLE.
After choosing the menu selection, just follow the instructions. I did try to make this very easy for you
THANKS TO NOOBNL FOR PERMISSION TO USE HIS STUFF, AND FIRON FOR HELP WITH SCRIPTING.
Other Credits:
joeykrim - original exploit
skeeterslint - busybox
koush - Clockwork Mod
These are just modifications of work already done by the aforementioned. I just had the vision to unify all of it into one master tool that can be used across all computers.
LINKS TO ORIGINAL RELEASES:
Handy if you're having trouble with this release, or just want to learn more about the originals:
One Click Root 2.5.4 by noobnl
ClockworkMod Recovery 2.5.1.0 by noobnl
Andromeda Kernel 1.4.1 by noobnl and Kernel Sources
SDX Stock App Remover 1.5 apk
VERSION HISTORY:
1.01 Added chmod to adb.lin and adb.osx to ensure that scripts work right first time, especially in linux.
1.10 Major rewrite for Mac and Linux unifying into one master script, with very generous script contribution by Firon. Scripts are now more organized and efficient. Remount now in /system/xbin. Uninstaller has rclean file that lists all files to be removed from phone, and now runs from phone to reduce visible rm failed errors. adb server now restarts after exploit, which greatly reduces chances of phone losing connection. Command line input options. Has busybox by skeeterslint. Added menu option to reboot phone.
1.11 Changed adb alias to include sudo, to prevent permission errors. Will prompt for password on first run if necessary.
1.12 Checks to make sure phone connection is seen before and after exploit, and after reboot. Thanks to Firon for the timer code. Checks to make sure Clockwork mod install reboot takes place, therefore knowing if it was properly installed. Added both methods for installing clockwork mod, and menu option to install SDX Stock App Remover 1.5 apk.
1.13 Smarter script, detecting if kernel is rooted, should eliminate problems with Clockwork Mod installs. Added Andromeda Kernel 1.4.0.
2.00 Rewritten based on One Click Root 2.4.0 by noobnl and Firon. Made compatible with 2.2 Froyo. Stock Samsung Recovery added. Added Wifi Tether. Will detect if Froyo is installed on phone and abort if trying to flash Eclair kernels or recovery.
2.01 ClockworkMod redirector by noobnl included, only installs if Froyo is detected.
2.02 Incorporated improvements from One Click Root & ClockworkMod 2.5.0 by noobnl and Firon. Includes Firon edits to ClockworkMod redirector files. Reinstating Stock Samsumg recovery will install appropriate bin for Eclair or Froyo automatically.
2.03 Fixes a couple of script errors, minor edits.
2.04 Updated to latest adb binaries, which affected linux users. Wifi tether updated to pre15. Playlogo replace fixed in batch script. Clockworkmod redirector files fixed to fit inside dk28 /system folder. More script fixes.
Bonus: Command line tools built into script:
e --runs the exploit, to get su from adb shell, if kernel isn't rooted
k --shuts down adb with adb kill-server
r --reboots the phone by starting adb server then calling adb reboot
s --restarts adb server, by first killing it, then starting it again
This can be evoked from the command line as so, saving some typing:
Windows:
Code:
run e
run k
run r
run s
Mac / Linux:
Code:
./run.sh e
./run.sh k
./run.sh r
./run.sh s
Enjoy!
Sorry no link here, it's in the sdx epic 4g developers forum, the file is about 13mb hosted on my dropbox account. I couldn't find a way to split it into just 2 files, all my archive programs only handle diskette and cd sizes.
I've been working on this for a while now, and figured I'd share it on xda now, especially since the post by mkasick here on the simpler root method inspired me to name the root and removal methods "simple".
I'm new at xda, I'm just a scripter, but any developer can take a look at the script and see it's legit.
If a moderator could unlock me to put the link directly in the post, I'd be much obliged... I do realize the need to prevent spammers.
OK, signing off, hope you all enjoy it!
DRockstar
OK, this has been updated for those interested. I know some of you have checked this out at the SDX forums. I'm still waiting for permissions to post outside links so that you can download it directly from here. Sorry for the inconvenience.
Used your root and worked flawlessly. Awesome job!!
phantomevo77 said:
Used your root and worked flawlessly. Awesome job!!
Click to expand...
Click to collapse
Thanks for letting me know that it's been useful! I spent a lot of time perfecting it.
Download link is finally up...
Thanks to the moderator for letting me know what I needed to do.
Have people used this? See, this is why there's not a huge dev pool on here...this would've came in handy if I saw this post a couple days ago :/ you should put this on the wiki for other people
Sent from my SPH-D700 using XDA App
My last post sounded mean...I meant it as people just don't appreciate some of the hard work on here
Sent from my SPH-D700 using XDA App
Very nice, works easy for me on Mac OS X.
Quick question, is it ok/safe to flash the Andromeda Kernel 1.4.0 by noobnl over the stock kernel just to compare it's battery life/performance over the stock kernel?
I'm NOT interested in flashing custom ROMS yet (and when i do i'll be sure to follow your caveats regarding removing one-clicks and such).
LordLugard said:
Very nice, works easy for me on Mac OS X.
Quick question, is it ok/safe to flash the Andromeda Kernel 1.4.0 by noobnl over the stock kernel just to compare it's battery life/performance over the stock kernel?
I'm NOT interested in flashing custom ROMS yet (and when i do i'll be sure to follow your caveats regarding removing one-clicks and such).
Click to expand...
Click to collapse
Yes, you'll be fine if you want to test out the Andromeda kernel in this release. The Root Uninstaller will remove it without problems. That is one reason I included it in this release, so you can at least try one good rooted kernel safely.
For Mac and Linux users, it is imperative to create a backup in clockwork mod before testing out any other kernels and ROMs. Windows has Odin3 for flashing a full stock system to the phone as a backup, while no alternative exists for Mac or Linux. There is a stock ROM posted by noobnl in the Epic 4G wiki, which I think is the best alternative we have right now.
Sent from my SPH-D700 using Tapatalk
I ran it all in one and it worked it seemed, however, it did not install clockwork. Worked great tho once I ran the file again and picked clockwork only.
Dulanic said:
I ran it all in one and it worked it seemed, however, it did not install clockwork. Worked great tho once I ran the file again and picked clockwork only.
Click to expand...
Click to collapse
This expects you to perform only one action at a time, and it should automatically reboot the phone.
The exception is installing the SDX Stock App Remover, which simply installs the apk to the phone. That can be removed easily like any other app.
Sent from my SPH-D700 using Tapatalk
Oh I see, I didnt quite read it right
A_Flying_Fox said:
Have people used this? See, this is why there's not a huge dev pool on here...this would've came in handy if I saw this post a couple days ago :/ you should put this on the wiki for other people
Click to expand...
Click to collapse
Yeah, I was just new to this particular forum and didn't realize what I needed to do... it is now in the wiki, so others can see it... I expect this to be very popular once people realize just what it is and how useful it can be.
Based on One Click 2.3.0?? I thought we were only at 2.2.9?
spitefulrain said:
Based on One Click 2.3.0?? I thought we were only at 2.2.9?
Click to expand...
Click to collapse
Well, firon and I worked together on script making the bash script Mac and linux compatible, and other things. Firon has been a valuable help in contributing code, he's gifted with scripting. He uploaded his changes to a 2.3.0 version in the SDX forums, but I guess that was never reflected in the official posts, or he just uploaded the changes without changing the version...
You can see here:
http://forum.sdx-developers.com/epi...ck-root-for-the-epic-4g!/msg102968/#msg102968
Edit: if you click the download link for the 2.2.9 one click root, you'll actually download 2.3.0 the original posts needs to be updated to reflect the update.
Sent from my SPH-D700 using Tapatalk
I am getting a message that says phone is offline. Its sees it but its offline. How do I make the phone online?
leebo73 said:
I am getting a message that says phone is offline. Its sees it but its offline. How do I make the phone online?
Click to expand...
Click to collapse
What OS version are you using? If Windows, have you loaded the drivers? If you're getting a message that the phone is offline, then your phone connection is not being recognized.
You do have debugging checked in the phone's application preferences?
If you're running Windows 7, drivers are a notorious pain, and they need to be installed correctly for any scripts like this to work.
Rockstar, this is a very underrated app, swiss army tool for the Epics for sure. Worked flawlessly on my sister's phone installing root, CWM, and SDK app remover. Appreciate your work ... if I get time, I might develop a simple frontend for this. You, Firon, noobnl, and mkaslick are awesome
Very nice package, downloading now. This should make it much easier to restore things back to how I like them after all the re-flashing to stock I do.

[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.

[Q] FileMate Clear 7" T720 tablet

Does anyone know if Z4Root will work on this tablet? Thanks!
I've been looking for one for 3 days now, I tryed onclickroot and z4root or something like that,, cant find anything Anyone please help!!
I'm still waiting for my tablet to be delivered...I'm gonna try SuperOneClick (crosses fingers)
I got one of these for my daughter for xmas. I spent a few days trying to root it with no luck. I'm not intimately familiar with android (some unix experience), but I tried all the options I could find for rooting Allwinner a10 devices. At first I ran into problems with adb unable to recognize the device for most one-click methods. I downloaded the android tools and was able to connect with the included adb. After studying the scripts, they all use the "adb root" command to gain root access on the device and copy the necessary files. Unfortunately, this command fails using adb from the tools. At first I thought this was due to my adb version, but after doing some research I think it is actually due to the device kernel. I believe it requires reflashing or some exploit to be able to gain root. I was able to install root explorer and I can browse all the necessary directories but I can't modify or copy the necessary files into them. Busybox told me there was an older version installed, but wouldn't let me install a newer version (again I think due to the permissions). Also, superuser would say it installed but the su binary did not show up on the bin directory. As the necessary directories are all owned by root, I couldn't figure out a way to modify the permissions...
I wound up returning the FileMate and got a Lenovo IdeaTab. Got that rooted in no time.
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
ferny_dx said:
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
Click to expand...
Click to collapse
Screw it, here it is for future reference.
How'd you do it!?!?
ferny_dx said:
Screw it, here it is for future reference.
Click to expand...
Click to collapse
FileMate Clear T720
Thank you very much for being the only person ever to have posted in regards to this tablet. I just got mine for christmas and have been trying to get it rooted. I've tried a lot of those one-click methods, and I've even tried this Bin4ary method. but it just hangs up on "daemon started sucessfully*"
Can you please direct me to the filemate drivers (if needed)
also, I have usb debugging endable, allowing 3rd party (not secure) files enabled. and pulling my hair out (enabled).
Thanks again.
Also, I'm running windows 7 and 8, (((maybe i should try win7))) hmm. i'll get back to you on that. Anyhow, any advice would be greatly appreciated, since returning it doesn't sound very fun.
jiberish05 said:
FileMate Clear T720
pulling my hair out (enabled)..
Click to expand...
Click to collapse
I laughed so hard. ok your going to have to install drivers by force,
first off do you happen to have android sdk installed? if you don't there is another way but its going to sound weird,
if you do have the android SDK installed:
1. go to your computer manager (by opening explorer, right click on the "computer" group on the left column and select manager)
2. look for any unrecognized item that appears, ( it will most likely be labeled "Clear" with a faded icon and a "?" sign on top
3. right click and choose "Update drivers", it will give you options, choose "Browse my computer for driver software", another option screen will show,
4. at the bottom of the window there will be an option that says "let me pick from a list of device drivers on my computer"
5. on the screen that appears there should be an option that says "ADB Interface", choose this
6. choose "Google, Inc.">"ADB Testing Interface version x.x.x.x" (I chose version 2.1.0.0)
that should do it next time you plug in the tablet try running ddms or open the cmd and type in "adb devices" (assuming you have adb installed) and it should show.
if this helps just hit the thanks button
[edit] I am running windows 8 btw [/edit]
ADB interface doesn't show up
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
jiberish05 said:
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
Click to expand...
Click to collapse
open up SDK manager and go to Extras>"Google USB Drivers"
also install everything in the "Android 4.0 (API 14)" section, I have other options installed if this still doesn't work.
its worth it just for the extra stuff that root comes with like titanium backup, but you cant over clock, if you go any higher than 1200 MHz it will lock up and you have to force it to reset.
cyberkeeper1 said:
HERE is the link to root as provided earlier
Click Here to download ADB universal drivers. they should work better than the google USB drivers.
---------- Post added at 12:20 AM ---------- Previous post was at 12:11 AM ----------
this seems kind of spammy. What backs up my claim is that you dont have more than 5 posts...
Click to expand...
Click to collapse
Thanks for the link to my post on android central, the link in that post just comes back the xda thread
Root MANY ANDROID! [Upd: 20.11.2013] - Added Z1 Root
Sent from my XT862 using Tapatalk
Rooted Filemate Clear
I just wanted to confirm I have also rooted the Clear with the Bin4ry v33 exploit using option 1. Although I received the following error:
remote object '/system/bin/ric' does not exist
.
Going to copy files to it's place
Rebooting again, please wait!
Could Not Find C:\Documents and Settings\Graham School\My Documents\Downloads\Ro
ot_with_Restore_by_Bin4ry_v33\ric
Restoring previous Backup! Please select the RESTORE MY DATA option now on your
device!
SuperSu installed and root apps working.
Rooted With Kingo
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, no problem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Jfender1005 said:
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, lem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Click to expand...
Click to collapse
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Kingoroot
cyberkeeper1 said:
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Click to expand...
Click to collapse
http://www.kingoapp.com/android-root.htm
That is the link for the Kingo site. The first time I saw it on here there was some question about whether it was safe becase it is not open source and used a Chinese SuperSu app. I felt safe using it on a tablet because I do no banking on it or anything, but the newest posts I have seen are that Kingo is safe. Hope that helps. And if you know where to find a custom recovery that will work with this app please let me know.

Categories

Resources