2)Run ADB for Dummies.exe and install android SDK for Windows:
3)Right click on My Computer and go to Properties/Advanced settings (for Windows 7 & Vista) or Poperties/Advanced Tab (for Windows XP). Open Environment Variables , click New and fill in following values:
in field Variable: adb
in field Value: C:\android-sdk-windows\platform-tools
4)Extract zip file from first page of this tread sgs3-root-install.zip in directory:
C:\android-sdk-windows\platform-tools
5)Check USB Debugging in Settings/Development mode of your S3 phone.
6)Connect USB cable
7)Go to directory: C:\android-sdk-windows\platform-tools
and double click on install.bat
Telephone should reboot and update android which proves that work done. You can see SuperSU installed in your programs.
+1 with this error and unfortunately, this guide didn't help. Getting error: device not found when trying to use ADB, therefore can't push SU onto the S3 so no real root :(
Looking at recovery now. I think there's a logic breakdown in the recovery sources which will mess with internal/external sdcard selection at the moment.
I had the same problem, i need someone with a GS3 to pick up some commands output to fix internal sdcard, because external already works fine
I had the same problem, i need someone with a GS3 to pick up some commands output to fix internal sdcard, because external already works fine
I know what you're thinking, but that's not going to work. Internal sdcard is "fuse"d. I know that's supported, you just have to setup the recovery fstab right - I've done it for other models. The thing is, the current CWM source supports that, or it supports internal sdcard normally, or it supports external sdcard, or it supports internal sdcard + external sdcard, but it does *not* support internal sdcard *fused* + external sdcard. You can make it work by switching the sdcards around, but that will mess up usage and "android secure" will not be properly backed up or restore.
At least, that's how I read the source. I haven't bothered compiling or testing. But if I read it right, the source needs some overhauling for this to work *properly*. That's not a big problem by itself, however it's probably best if that is played directly in cooperation with Koush, so the CWM sources are fixed - instead of us hero-ing around on our own.
(On the other hand, if this is all actually true, it's a pretty big fail in the last batch of CWM adjustments ... because this setup should have been expected when "fuse"d sdcards were introduced)
(And still, aside from this specific problem, yes, you could have just taken SGS2 recovery binaries, adjusted recovery.fstab, and injected it into stock SGS3 recovery to get a proper CWM)
I AM ON VACATION
I know, I still had lots of PMs and emails to answer, problems to debug, features to implement, updates to release, people to help, etc, but it'll just have to wait. But do not despair, I will return soon to procrastinate some more.
I know what you're thinking, but that's not going to work. Internal sdcard is "fuse"d. I know that's supported, you just have to setup the recovery fstab right - I've done it for other models. The thing is, the current CWM source supports that, or it supports internal sdcard normally, or it supports external sdcard, or it supports internal sdcard + external sdcard, but it does *not* support internal sdcard *fused* + external sdcard. You can make it work by switching the sdcards around, but that will mess up usage and "android secure" will not be properly backed up or restore.
At least, that's how I read the source. I haven't bothered compiling or testing. But if I read it right, the source needs some overhauling for this to work *properly*. That's not a big problem by itself, however it's probably best if that is played directly in cooperation with Koush, so the CWM sources are fixed - instead of us hero-ing around on our own.
(On the other hand, if this is all actually true, it's a pretty big fail in the last batch of CWM adjustments ... because this setup should have been expected when "fuse"d sdcards were introduced)
(And still, aside from this specific problem, yes, you could have just taken SGS2 recovery binaries, adjusted recovery.fstab, and injected it into stock SGS3 recovery to get a proper CWM)
That's what i thought too, and also kinda "hacking" the fstab is an easy way to fix it...we just need to know the proper partition position in the block device afaik, as there SHOULD be a partition for it (or a device address...)
And yes, i already knew that only needs changing the fstab to be usable
What i am trying now is to port the touch features
+1 with this error and unfortunately, this guide didn't help. Getting error: device not found when trying to use ADB, therefore can't push SU onto the S3 so no real root :(
1) Install latest version of KIES from Samsung site.
2) Turn ON the phone, connect to the computer and wait until all drivers installed. This takes time.
Thanks guys. After hours of fiddling, got it to work.
My main problem was drivers. When I ran the Kies setup, it just unpacked and quit. It worked before, just not now!
I eventually managed to solve this by, and I don't know why it worked, redownloading the exact same Kies package. Installed the Samsung USB Drivers first, then Kies, and then ADB found my device.
I'm running a rooted S3 now yay! Oh Titanium Backup how I missed you so!!
Do you find yourself obsessively jumping from ROM to ROM? And do you hate having to restore a full … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon – A Conference For Developers By Developers
>
[PRERLS-REF] Root, BL, Kernel, Recovery
Print
Email
View Profile
View Forum Posts
Follow on Twitter
Visit Homepage
.gif "Netherlands - T-Mobile (Ben)")
Follow on Google+
Linear Mode
