Need help with samsung skyrocket root!! - AT&T Samsung Galaxy S II Skyrocket SGH-I727

So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.

is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.

shansmi said:
is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.
Click to expand...
Click to collapse
I have not changed anything since the first success of my Skyrocket root. It's weird that it would root the first Skyrocket but not the second one.

I used this one.
http://androidadvices.com/root-samsung-galaxy-s2-sky-rocket-4g-sgh-i727-tutorial/

Solution for "Files not found" and "permission" when trying to run ZergRush
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!

trying to root
ashque01 said:
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!
Click to expand...
Click to collapse
I still get errors "system cannot find the path specified" and it doesn't work.
ashque01 you put "D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat"
I didn't get that to work until I switch the > to a \ the arrow instead of a backslash makes a difference, beg pardon but I don't know dos very well and I did use the arrow with no success, lol...
Once in the command prompt (you get there by typing exactly that "command prompt" in search bar, after clicking the start button in windows 7) Right click on command prompt to run as administrator.
I put D:\DooMLoRD_v3_ROOT-zergRush-busybox-su\runme.bat because that's where I used 7zip to extract it to, in the root of hard drive partition. It ran but with errors and announced done! press any key to continue.
I tried it again by creating a subfolder on the D: partition named android like you did, tried it again, same thing,
Still hoping to get a superuser icon so I can download my root explorer app from the market.

YAY!
I got root.
I told all of about it in that thread I started titled s#%rocket. I did admire what Entrophy remarked about it's hardware being disagreeable, but that was in the i777 thread. I had no business there (mod moved my thread, thank you) as my handset is i727.
I coulda swore that's what about phone said before I started but sure enough when you pull the battery it says i727 right there, can't argue with that, I was just being "elevator up, but door not open"
Beg pardon

androiduser1 said:
So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.
Click to expand...
Click to collapse
use 2.3 not 2.2
Sent from my SAMSUNG-SGH-I727 using xda premium

Related

Froyo Root Instructions using Superoneclick And Unrooting

ROOTING:
Since z4root, one of the easiest ways to root, is not working on Froyo in Galaxy 3, I decided to make this separate thread for instructions on how to root Froyo using Superoneclick.
First and foremost: Enable USB Debugging by going to Settings>Applications>Development. Make sure it is ticked.
Download the attached Superoneclickv1.5.zip file. Extract its contents. Make sure your phone drivers are installed on the computer (Samsung Kies). Then follow the steps:
1. From the extracted contents, run the file named Superoneclick.
2. Turn off your phone, then connect it to the computer using the USB Cable. Don't turn on the phone. Keep it off but connected to the computer.
3. In Superoneclick, click on the 'Root' button. After a few seconds, it'll say 'Waiting for device'.
4. Now turn on your phone (while it is still connected to the computer). Superoneclick will detect the phone.
5. Now the phone will be rooted, while it is starting up. When it is started, it'll be rooted.
6. After rooting, download and install busybox on your phone. It should take care of any slowing down of your phone after rooting.
That's it. The phone is now rooted, although it would be so much better if z4root worked on Froyo..
For those getting stuck at the 'pushing raceagainstthecage' step, try this method. Credits go to haree:
1. login as admin and then open the application. Or right click on Superoneclick.exe and click on 'Run as administrator'.
2. turn off ur Virus protection
3. remove all the additional external USB devices(this seems to confuse the SW)
i removed all the above mentioned
and then follow the instructions u will be successful
it worked for me now i have 2.2 and rooted
Click to expand...
Click to collapse
UNROOTING INSTRUCTIONS:
Unfortunately, the method to unroot by clicking on the Unroot button in Superoneclick does not work. So follow the following steps to unroot.
1. Download rootexplorer.apk (attached) and install Root Explorer on phone.
2. Run Root Explorer. A 'Superuser Request' prompt will come up. Press Allow.
3. Now, on the top, there will be a button saying 'Mount R/W'. Press it. It should change to 'Mount R/O'. The button should say 'Mount R/O' in order for you to be able to do anything in the following steps.
4. Now scroll to the bottom, click on system. Then click on bin.
5. In the bin folder, look for a file named 'su'. Long press on this file, and select Delete to delete it.
6. Now go back to the system folder by pressing the Back button once.
7. Now enter the app folder. Scroll down and look for the file named 'superuser.apk'. Long press on this file and delete it.
8. Exit Root Explorer after this. Uninstall it if you don't want to use it.
9. That's it. Your phone will be un-rooted.
Another method to unroot:
1. Download and install Terminal Emulator (attached).
2. Run Terminal Emulator on the phone. If you don't see a keyboard to type, press Menu and press Toggle Soft Keyboard.
3. Type su and press enter. Press Allow on the 'Superuser Request' prompt. The $ sign will change to a #.
4. Now type the following line exactly as it is and press enter: mount -o rw,remount /dev/block/mtdblock3 /system
5. Nothing will happen visually. The pointer will shift to a new line.
6. Now type the following line and press enter: rm /system/bin/su
7. Again, type following line and press enter: rm /system/app/superuser.apk.
8. Now exit Terminal Emulator. Your phone is un-rooted.
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
FadeFx said:
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
Click to expand...
Click to collapse
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
addicted2088 said:
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
Click to expand...
Click to collapse
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
haree said:
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
Click to expand...
Click to collapse
Can't unroot using the same procedure, but have added another procedure to do it.
This method does work for everyone. The only new step in my procedure is to do it while the phone is booting.
help! !
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
coolzarjun said:
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
Click to expand...
Click to collapse
Are your phone drivers properly installed? Does your computer make a 'Hardware connected' ding sound when you turn on the phone? If not, then you'll have to install Samsung Kies and then connect the phone to the computer to install the drivers. Try rooting after that.
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
coolzarjun said:
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
Click to expand...
Click to collapse
Connect your phone to your computer. Then open the Device Manager. Then look for the entry 'SAMSUNG Android Composite ADB Interface' in the list. It might be under the ADB Interface tab. Right click on the 'SAMSUNG Android Composite ADB Interface' and uninstall it.
Then reconnect your phone to the computer and see if the ADB drivers get installed properly this time.
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
coolzarjun said:
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
Click to expand...
Click to collapse
Sorry, I'm using Windows 7, so I've no idea what to do about the drivers in Windows XP. Try updating Kies..
i also have win 7 and it doesnt work...help??
reist said:
i also have win 7 and it doesnt work...help??
Click to expand...
Click to collapse
I can't help if the drivers on your computer are not installed properly. After connecting the phone while it is ON, open the Device Manager and see if the ADB driver is properly installed.
If the drivers are properly installed, this method will work..
Edit: As mentioned by mhndk14 below, enable USB Debugging in Settings>Applications>Development.
I also had the same problem with windows 7. Just make sure that the USB Debugging is enabled and then try again. It worked for me.
how to bring the phone back to factory settings
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
nageshkaja said:
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
Click to expand...
Click to collapse
To remove the Live Wallpapers, you'll have to root your phone, and then use Root Explorer to remove the files Livewallpaperspicker.apk from system/app, and libRS.so and librs_jni.so from system/bin. Then un-root your phone. Be sure to press the 'Mount R/W' button in Root Explorer to be able to delete the files.
As for restoring your boot menu, that procedure is there somewhere in the Development section. The boot menu changes because of upgrading, not rooting.
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
stubborn_d0nkey said:
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
Click to expand...
Click to collapse
Yeah, haptic feedback stops working sometimes on JPA and JPB after rooting. But restarting the phone corrects it. (Although your method of restarting the phone was too brutal!! )
Thanks addicted2088...worked perfectly...
successfully rooted..........
now i need to know how to install live wallpapers......
thanks

[Q] Android 2.3.1 Tablet - Gingerbreak not working

Hi, I have a 8" Tablet with Android 2.3.1 and Samsung S5PV210 processor.
I'm trying to gain root access, but I'm having particularry hard times doing it. Basically, I found I don't have the su command neither inside system/bin nor system/xbin directories.
All the root methods (I found till now) are based on a .bat file, but fail because su: command not found.
Gingerbreak fails too, it stays forever spinning trying to root, it crashes when I rotate the tablet; sometime, once every 5 attemps, it reboot the tablet, but fails to root it :\
What can I do, where can I find mor info on the rooting process?
Tnx.
exact same problem.... no one with a solution ?
Cant beleive no one answered this one yet
Sent from my Nexus One using Tapatalk
Same problem as well
Little help here ? ;-)
Sent from my Nexus One using Tapatalk
Might want to try reading through this thread http://forum.xda-developers.com/showthread.php?t=1044765
If you can't find the answer there, then ask in that thread, those people know best how that method works.
I had the same problem... i tried them all, z4root, androot, gingerbreak, and super one click to no avail... I then stumbled on SUPER ONE CLICK 2.2 and it rooted first try no problem..
the S5PV210 CAN be rooted
I looked for three days trying to find a way to root this Chinese Samsung tablet knock off. Finally I used Super Click 2.3.3.0 You can find it at download.cnet.com
Download and unzip the file. I unzipped it to a USB stick -- just to make it portable.
You only have to connect the tablet to an XP computer with a USB cable. Then you must load the driver for the tablet when prompted by Windows. The driver has been provided for you. Just browse to the drivers folder in the unzipped software. Then run SuperOneClick.exe Click the Root button. Done.
Trust me. Skip all other advice. Nothing else could be easier than this.

[Q] rooting inspire questions

Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Linch89 said:
Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Click to expand...
Click to collapse
Ace Hack Kit
That will walk you through the root/s-off/unlock process. It's been VERY much simplified over time, now it's just a 1 step process. Read the effen manual a few times before you start - but like I said, at this point it's very straight-forward.
Once installed hit up the MIUI thread. Basically you'll download the ROM to your SD, boot to recovery, perform a wipe, and flash the ROM
And thank you for your service and dedication to this wonderful country of ours!
He said the adb drivers won't connect
Any specific error messages? At what point is this happening? Is he trying to run the hack kit or just trying to access an ADB shell?
The hack kit contains all necessary adb files/drivers
Make sure he's done all of this:
Make sure HTC USB Drivers for Android are installed (included in the Hack Kit @ tools/windrivers)
Disable all malware detection, including Windows Defender
Uninstall HTC Sync
Uninstall Droid Explorer
Uninstall iTunes or stop service
Uninstall Other phone pda or tablet software
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
trouble rooting my phone
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
did u ever find out y adb wont connect im having d same problem
Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Did you install the drivers that came with the kit just to be safe?? I just did this like 2 days ago and it worked perfect..
Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Has he by any chance tried a different USB port? And is the phone in charge only mode, it's not mounting itself as a disk drive automatically? I don't know how feasible it might be, but if he has another computer available try running it there and see if you get any different results. At least then we might be able to narrow down better whether it's the software, the computer, or the phone.
jonathanj942 said:
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
Click to expand...
Click to collapse
Another simple thing that I have to ask about...you guys did extract all the contents of the hack kit somewhere on your computer, correct? You're not trying to run it from the .zip?
If it is extracted,
go to the tools\win\ directory.
Hold Shift and Right-Click in an empty spot, select "open command window here"
type "adb devices" and hit Enter
You should see 12 alpha-numerics listed under "List of devices attached"
If you don't see anything under this, then for some reason adb isn't recognizing your phone is plugged in. In which case I'd try a different USB port or computer

[Q] Having Trouble Rooting LG Optimus 3D (P925G). Please help!

So I have a brand new LG Optimus 3D, locked to Rogers and running Froyo. I have tried every method I can think of to root this phone, but nothing seems to work.
To date, here is what I have tried:
SuperOneClick: This method fails miserably and SuperOneClick just freezes up every time I try to run it.
psneuter: this actually DOES work...however it does NOT permanently root the phone. Once I reboot, the phone is back to being unrooted.
I'm still new to the whole android mod thing, having only done this once before with my old HTC Dream. Is there a step I'm missing somewhere to permanently root my Optimus 3D? Is it even possible as of yet to root this phone?? Is there some kind of NAND lock on the phone that I don't know about and/or just haven't found yet?
Again, I AM new at this, so any answers or information you can give would be helpful.
check if you have .net framework for super one click and run it as administrator
don't forget tu set the usb debugging mode
heve rooted several optimus 3d like that never had any problems
Tylwith said:
check if you have .net framework for super one click and run it as administrator
don't forget tu set the usb debugging mode
heve rooted several optimus 3d like that never had any problems
Click to expand...
Click to collapse
Try to kill all adb servers..including Droid explorer if you have.....open task mng in your PC,and kill it all...after that try to root your phone....
I should also note I've done all of the above both in Linux AND in Windows (in this case it's a Windows VM in Virtualbox, however...not sure if that makes any difference)
Also, does it matter that this is the Canadian version of the LG Optimus 3D and not the one that was released in the EU?
Try this.. http://forum.xda-developers.com/showthread.php?t=1358257
It should work...
Let me know if you were successful.
smohanv said:
Try this.. http://forum.xda-developers.com/showthread.php?t=1358257
It should work...
Let me know if you were successful.
Click to expand...
Click to collapse
Maybe I'm wrong (entirely probable), but isn't ZergRush only for GingerBread?? My phone runs Froyo (probably should have mentioned this before...oops. )
TuxOtaku said:
Maybe I'm wrong (entirely probable), but isn't ZergRush only for GingerBread?? My phone runs Froyo (probably should have mentioned this before...oops. )
Click to expand...
Click to collapse
Okay so here's the thing: ZergRush SEEMS to work. That is to say, if I run it manually via ADB, the exploit works and I get a root prompt when I log back into the adb shell. However any apps that need root on the phone still don't work. (example: superuser tried to download and install a new version of the su binary. It downloads fine, but then fails when it says "gaining root access")
I reckon using windows in virtual box is your problem. Try direct on a xp machine.
Pete
Sent from my LG-P920 using xda premium
ROOTED! I ended up having to follow a guide on another forum which employed a batch script that deploys ZergRush PROPERLY. (I'd include a link to said guide...but since I'm new here, vBulletin is going all anti-spam on me saying I haven't posted enough.)
Basically all I did was manually execute each command in the batch one at a time.
Incidentally, for all you fellow Linux geeks out there, I'll be adapting the batch file into a bash script as soon as I have time.
SuperOneClick working fine too.
http://forum.xda-developers.com/showthread.php?t=1358257
[QUOTE
Incidentally, for all you fellow Linux geeks out there, I'll be adapting the batch file into a bash script as soon as I have time.[/QUOTE]
Did you manage to do this? I REALLY hate having to resort to using windows, especially as the phone is running Linux anyway! Lol
Pete
Sent from my LG-P920 using xda premium

[Q] root issues...

Hey guys, I've frequenting this site for some time now and as you can see I don't ever post.. I usually don't have an issues figuring stuff out.. I have experience rooting GSII, GSIII, EVO 4G LTE and DROID RAZR... But for some reason I can't seem to root my TF700T. I've followed the directions in the "ALL IN ONE" guide exactly (or as it would seem I didn't....)
Yes debugging is on, yes unknown sources, yes I ran the .bat file as admin... I even uninstalled the TF700 drivers and reinstalled them to see if that would work... but.. I run the .bat file, press 1/enter.. it reminds me to have debugging on, unknown sources and drivers for ADB... then the command prompt just disappears without any notion or confirmation I've successfully rooted ( is that normal?).
Anyways, I'm not sure what I'm missing (obviously) but does anyone know where I may be ****ing up? Thanks.
... weird... I didn't do anything differently I just kept running the .bat over and over again and eventually it moved on to the next steps.....
Open a command prompt and get into the directory you saved it in and run it from there. Worked for me that way after having the same issue as you.
MooreHeat said:
Hey guys, I've frequenting this site for some time now and as you can see I don't ever post.. I usually don't have an issues figuring stuff out.. I have experience rooting GSII, GSIII, EVO 4G LTE and DROID RAZR... But for some reason I can't seem to root my TF700T. I've followed the directions in the "ALL IN ONE" guide exactly (or as it would seem I didn't....)
Yes debugging is on, yes unknown sources, yes I ran the .bat file as admin... I even uninstalled the TF700 drivers and reinstalled them to see if that would work... but.. I run the .bat file, press 1/enter.. it reminds me to have debugging on, unknown sources and drivers for ADB... then the command prompt just disappears without any notion or confirmation I've successfully rooted ( is that normal?).
Anyways, I'm not sure what I'm missing (obviously) but does anyone know where I may be ****ing up? Thanks.
Click to expand...
Click to collapse
I had the exact same problem with the window closing and all you have to do is run it through a command prompt and It will work fine
sent from My Own Galaxy
if you're using debugfs method, I've read it doesn't play nice if you have Android SDK and ADB installed on your PC. It contains everything needed. Somehow, haveing ADB A-SDK causes some weird conflict/error. I'm not aware if this has been resolved.
Ya I figured it out... I actually didn't need to run it through cmd prompt... it just finally worked... lol
Sent from my SGH-I747 using xda app-developers app

Categories

Resources