Related
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
So, I used to run WinMo way back when, and I'm familiar with flashing, HardSPL, blah blah blah, whatevs. I haven't done the rooting process yet on my phone because I'm finding it hard to find a few key things that I need.
-What is the effect on my phone when I root, in regards to data? Do I need to backup? If so, can I backup on my SD card or is everything wiped? What program could I use to backup?
-Are there any crazy little tweaks or tips that anyone has to help guard against a brick?
-I've read the pros and cons list, but can I get more details from someone? Can this help with battery life, allow me to flash my radio, increase general connectivity, etc.
All help would be greatly appreciated, and I'll plan on doing a donation today. I've just been out of the loop (running WinMo 6.5 style out of the loop:/) so some advice to a rook would be great. My goal is to get out of school and come home and root and fiddle with things with little to no problems. Thanks a ton everyone.
Dig Life!
D
The process of actually rooting doesn't mess with any of your stuff.
I use Titanium Backup to restore apps after flashing roms.
In general, most of this stuff COULD help your battery life, here there are Devs that will help - with sprint you get their tech support.
Well, I DL'ed TB and it says that I have to root first? Am I missing something here? Is it ok to root or will it delete all of my apps and what not? I mean, if it does, it isn't really that big of a deal, considering I can just download them again, I'm just looking for input.
copsgottanks said:
Well, I DL'ed TB and it says that I have to root first? Am I missing something here? Is it ok to root or will it delete all of my apps and what not? I mean, if it does, it isn't really that big of a deal, considering I can just download them again, I'm just looking for input.
Click to expand...
Click to collapse
I'm pretty new, too, but I think I can answer your questions. Rooting (at least with the One Click Method I used on my Epic) doesn't destroy any data/apps on your phone. It simply gives your user root access to the underlying OS. Once that is achieved, you can modify things and tweak things. Titanium Backup will let you backup all system files and data, but only AFTER rooting.
This is not a ROM flash or anything like that from the WinMo days. I haven't gotten that far on Android, so I'm not sure what the flashing options are yet, but rooting is harmless on its own. It will let you royally screw things up though, so once it is done, be careful what you do.
Well, I tried to do a few things like listed in the One-Click root thread, but I guess I'm just not getting it. Now that I know the effects of the root, I'd like to be able to actually do it, but I don't have enough details. I haven't ever rooted before, and I'm finding it confusing. What was listed in the one-click thread wasn't specific enough for me, I don't know if I need to run from SD card, what the ADB thing is, nothing. I was a WinMo master and I'm finally coming to Android which is literally worlds away from my comfortable norm.
what os are you running? the one click comes with everything you need. theres an osx version the windows version that noobnl updates and the linux version i maintain
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
copsgottanks said:
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
Click to expand...
Click to collapse
I wouldn't exactly call root harmless..in itself it is ok..but if you give root access to a program that program has FULL access to your system..aka anything inputed on your phone or stored on your phone can be accessed by the program with root access. Though generally its not a problem..just careful which programs you allow to use root access.
Also, at what point are you getting stuck? did you install the drivers? are you getting any sort of errors or etc?
There is also some good reading over at SDX Developers.
I have hacked and rooted before, WinMo, Palm, HTC Hero, but this one was tough. It basically took me two days off and on, but it worked - finally.
Downloading drivers is a b--h, they are finicky and I needed all of them, kept
hanging on 2. They are slow, and kept looking for sources.
Search here, there is good info, then look there (above) I used OneClickExploit 2.2.4 which finally worked. It had some of the same files
in other methods, but this one worked.
I'm not changing roms, did on Hero to 2.2 because they weren't getting upgrade but I'm just going to hang and wait for Froyo.
Good luck
copsgottanks said:
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
Click to expand...
Click to collapse
Download and unzip the one-click archive in to a folder. Double-click the run.bat. I had some problems where it would start and then hang. I often had to kill it and rerun the batch file. Sometimes I had to end task on the adb.exe process. Eventually after rebooting the phone, etc, I was able to get it to work. Not sure what the exact problem was. I think part of it was connectivity to the phone via usb. Connect through a port on your computer, not a hub.
Also, the batch file is just a bunch of commands. You can open a command line in the folder where the batch file is and run each line in the batch file individually from the command line. That will give you some idea of what is happening and where it might be failing.
Like I said, I had to stop and restart a bunch of time before it finally got through to the end of the batch file correctly. When it did, it was fast. Not sure what was happening.
gTen said:
I wouldn't exactly call root harmless..in itself it is ok..but if you give root access to a program that program has FULL access to your system..aka anything inputed on your phone or stored on your phone can be accessed by the program with root access. Though generally its not a problem..just careful which programs you allow to use root access.
Also, at what point are you getting stuck? did you install the drivers? are you getting any sort of errors or etc?
Click to expand...
Click to collapse
When I try to install the drivers I get this message:
"The MSS InstallWizard was not Completed for SAMSUNG USB Driver for Mobile Phones V1.3.450.0
The MSS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones V1.3.450.0. Click Finish to exit the wizard.
And I'm basically stuck there. I've searched around and can't find any drivers that will work. Like I said, I'm on 64-bit Windows 7 with a clean OS and no previous negative install history. Not sure what the issue could be?
Found the drivers and everything that I needed and I'm rooted, but now I have one more question. I don't plan on flashing any roms, I'm alright with the stock rom, at least for now. I wanted to know what rooting will do in regards to over the air updates on my phone. Will I be able to OTA to FroYo when released? Any info would be great guys, thanks.
where did you find the drivers? I am having the exact same problem that you had where the installwizard cannot download finish installing the drivers for whatever reason
So I've poured over the potentially relevant threads and I haven't found anything about how to go about rooting the Tab on a Mac. I've rooted a Xoom on a Mac before, which was no problem using adb, but does adb recognize the Tab as a device (given the lack of Mac file reading compatibility otherwise) or is there another trick I'll need to know? Obviously at some point I'd need the new Kies for Mac, but is this all I'll need in order for adb to work? The only guides I've seen pertain to rooting through a PC, which is no help to me unfortunately. I don't have my Tab yet, but I was hoping to get a feel for what lies ahead once it arrives.
Please do not Post Questions in the Development forum thanks
lufc said:
Please do not Post Questions in the Development forum thanks
Click to expand...
Click to collapse
IT WAS A DEVELOPMENT (ROOTING) QUESTION, not a general question, so now its in a less appropriate place, but whatever
Anybody?
Regardless if it was a rooting question. Development forums are for development releases like kernels, roms, mod instructions. Questions are asked in the General forum.
As for your question:
In order to get a reliable root you must install CWM. In order to flash CWM you must use nvflash which is a windows command line tool. So there is currently no way to do this from a mac. TBH there may never be a way to do this from mac. I would suggest getting a copy of windows and use bootcamp as I have.
X10D3 said:
Regardless if it was a rooting question. Development forums are for development releases like kernels, roms, mod instructions. Questions are asked in the General forum.
As for your question:
In order to get a reliable root you must install CWM. In order to flash CWM you must use nvflash which is a windows command line tool. So there is currently no way to do this from a mac. TBH there may never be a way to do this from mac. I would suggest getting a copy of windows and use bootcamp as I have.
Click to expand...
Click to collapse
Well at this point I do have Parallels, so I'm guessing I should be able to use that as my means of installing CWM, as per the instructions found in the thread in the development section, yes?
Correct. But! I've tried this stuff before from parallels with limited to no success. You need to boot from windows(bootcamp). So that windows has full control of your hardware. I've never been able to get paralleled windows to see things right for this kind of stuff.
http://forum.xda-developers.com/showpost.php?p=14866263&postcount=2
That is the guide that you want to follow. Once your are done flashing CWM you can then just drop the busybox and root zips on your SD card like you normally would with your mac and flash with CWM.
X10D3 said:
Correct. But! I've tried this stuff before from parallels with limited to no success. You need to boot from windows(bootcamp). So that windows has full control of your hardware. I've never been able to get paralleled windows to see things right for this kind of stuff.
http://forum.xda-developers.com/showpost.php?p=14866263&postcount=2
That is the guide that you want to follow. Once your are done flashing CWM you can then just drop the busybox and root zips on your SD card like you normally would with your mac and flash with CWM.
Click to expand...
Click to collapse
Yeah but in order to do this wouldn't I have to have a copy of a Windows CD (which I have no access to)? And obviously I'm not about to drop $$$ on a damn Winblows CD just to be able to root. This seriously sucks.
Now I do have access to my work PC, which runs XP. Might you have a rough estimate on how long the steps in that guide would take, should I decide to try doing it here at the office?? I could of course get the files, drivers, etc all set up in advance, so take that part out of the equation. Just wondering on how long in terms of installing CWM; once I have that I can root at home later that night.
...and actually, once I get CWM installed on the 10.1 I should really have no need to connect to it for adb (or at least very very rarely) in the future, correct? I mean it seems like the main hump to get over for a Mac owner is to just get a custom recovery on the 10.1, and after that everything else is just all about flashing (from recovery that is). Would that be a fair statement??
It seriously took me like 10-15 min to run through the steps from none root to CMW, Busybox, and root. I did it at my desk at work eating lunch on my bootcamp Win7 x64.
Hi everyone, i am trying to root my kindle fire device , but the process is not working.
Here is what i've done:
1. Installed Drivers from "install_drivers.bat" file from KFU
2. Manually Installed Drivers
Still cannot make ADB Status to go "ONLINE".
The way i can make it "ONLINE" is by executing the "run.bat" file as administrator, but, doing this, leads me to error "cannot find tools/wget.exe". Ofc, because running with administrator privileges forces it to run from system32 folder.
I've already tried to run from the Command Prompt, even running the command prompt as administrator aswell.
Any idea of how to solve it ?
My Kindle is 6.3 Version. I bought it in February.
I used the KFU 0.9.5 version.
I also tried to install drivers manually, from a difference source ( a youtube video tutorial of how to root 6.2 version ), but, the device manager says the drivers are already up to date.
My device manager shows a "Android device" at the top of the list, but no "Kindle" or "Amazon Kindle" device in the whole list.
What am i doing wrong ?
Please, if you can't solve it, at least, bump this thread.
Thanks !
Try this... delete your drivers and configure and reinstall your own from the AndroidSDK
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Then use command prompt to issue the appropriate adb and fastboot commands to manually root your device using the method posted here:
http://forum.xda-developers.com/showthread.php?p=24124828
If, after you reinstalled your drivers, you can't get adb to connect through command prompt, you may need to make sure that your user account has the appropriate permissions to perform such tasks (although I can't imagine why you wouldn't anyway).
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Try this... delete your drivers and configure and reinstall your own from the AndroidSDK
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Then use command prompt to issue the appropriate adb and fastboot commands to manually root your device using the method posted here:
http://forum.xda-developers.com/showthread.php?p=24124828
If, after you reinstalled your drivers, you can't get adb to connect through command prompt, you may need to make sure that your user account has the appropriate permissions to perform such tasks (although I can't imagine why you wouldn't anyway).
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I've seen you mention the Android SDK a number of times as it relates to driver installation. This is not meant as an argumentative post, but the SDK is entirely unnecessary if the user won't be "developing" software and just wants to install the drivers.
The SDK method is a lot of unneeded bulk to install the Java JDK, so you can install the Android SDK installer to get at the USB driver extras. Then the user has to go manually edit the .INF file with the necessary KF details before installing. Then create the .android folder in the right place and add a correctly named .INI file with more information. All these hoops create problems because most people who come here looking for help are flustered enough as it is and missing any one of these things or doing it wrong will just cause more issues that will have to be ironed out. It's just a bad idea all around.
And just in case you believe that the SDK drivers are somehow "better" than the KFU ones... they're not. All of the relavant files are identical. When I was writing my drivers guide, I checked them all to see if it could be a potential source for differences on why one install would work and not another. All of the md5 checksums for each and every .DLL and .CAT file match each other.
The only difference I found was in the source.properties files and that was just in the order of the name=value pairs at the bottom and the SDK distribution has an "Extra.NameDisplay=Google USB Driver" pair while the KFU one does not. I tried to find out how this file gets used in the driver installation, but the fact that I came up empty leads me to believe that it's a a non-player in the whole scheme of things.
Of course, the android_winusb.inf file is different between the two because some Kindle Fire specific information has already been added to it in KFU, but this is a good thing because you won't have to go do it manually and therefore skip an error prone task.
Please do not complicate matters by having people do this unnecessarily. If people want to install the drivers manually, they can point the driver update wizard to the KFU folder containing the android_winusb.inf file and it will do the same thing. If they use KFU's install_drivers batch file to install, they'll even get the .android folder created in the right place and the adb_usb.ini tossed in there with the correct values.
If you believe my reasoning is flawed, please let me know how installing from the SDK makes a difference. If you have a sound argument, I'm perfectly willing to admit my wrong, change my position and my guide as well.
I am inclined to agree with you with so many different instructions with different levels of experience how the new user can achieve root and proper driver installation has become muddled to the point where people are getting stuck in modes rendering thier devices unseen by thier computers. Stuck in fastboot or recovery or soft and hard bricked with batteries draining and time running out to achieve a fix. There is a serious need for a clear easy exploit for very low experience level OS dedicated. KFU worked perfect for me and so did adb but with others it has created a problem if I had the knowledge base to build a one click wonder I would but its way out of my experience level even though I have successfully rooted every device I have 2 kindles a galaxy tab 10.1 and my droidx after the .621 ota for droidx. So where do we go from here?
kinfauns said:
I've seen you mention the Android SDK a number of times as it relates to driver installation. This is not meant as an argumentative post, but the SDK is entirely unnecessary if the user won't be "developing" software and just wants to install the drivers.
The SDK method is a lot of unneeded bulk to install the Java JDK, so you can install the Android SDK installer to get at the USB driver extras. Then the user has to go manually edit the .INF file with the necessary KF details before installing. Then create the .android folder in the right place and add a correctly named .INI file with more information. All these hoops create problems because most people who come here looking for help are flustered enough as it is and missing any one of these things or doing it wrong will just cause more issues that will have to be ironed out. It's just a bad idea all around.
And just in case you believe that the SDK drivers are somehow "better" than the KFU ones... they're not. All of the relavant files are identical. When I was writing my drivers guide, I checked them all to see if it could be a potential source for differences on why one install would work and not another. All of the md5 checksums for each and every .DLL and .CAT file match each other.
The only difference I found was in the source.properties files and that was just in the order of the name=value pairs at the bottom and the SDK distribution has an "Extra.NameDisplay=Google USB Driver" pair while the KFU one does not. I tried to find out how this file gets used in the driver installation, but the fact that I came up empty leads me to believe that it's a a non-player in the whole scheme of things.
Of course, the android_winusb.inf file is different between the two because some Kindle Fire specific information has already been added to it in KFU, but this is a good thing because you won't have to go do it manually and therefore skip an error prone task.
Please do not complicate matters by having people do this unnecessarily. If people want to install the drivers manually, they can point the driver update wizard to the KFU folder containing the android_winusb.inf file and it will do the same thing. If they use KFU's install_drivers batch file to install, they'll even get the .android folder created in the right place and the adb_usb.ini tossed in there with the correct values.
If you believe my reasoning is flawed, please let me know how installing from the SDK makes a difference. If you have a sound argument, I'm perfectly willing to admit my wrong, change my position and my guide as well.
Click to expand...
Click to collapse
Yes, I know.
The point is to get people to forget about KFU for a minute and learn to do it the right way first (so as not to get distracted) so when they ARE ready to use a utility like the KFU they will know what to do when problems arise. You learn to do it the hard way first (one that will be around LONG after the KFU is gone) and THEN you can take shortcuts. That's pretty much standard procedure for learning anything.
I think it's safe to say that the KFU has caused more problems for newbies than has helped. And the ones it has helped usually have to learn the old way anyway. I'm just trying to get rid of the middleman.
Just think of how great this place would be if everyone knew how to how to do this on their own.
Sent from my Amazon Kindle Fire using xda premium
That being said, the people that I told to do it the "hard" way haven't needed any further help.
And if it does come back to bite me in the ass, you can rest assured, I'll eat my words.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Yes, I know.
The point is to get people to forget about KFU for a minute and learn to do it the right way first (so as not to get distracted) so when they ARE ready to use a utility like the KFU they will know what to do when problems arise. You learn to do it the hard way first (one that will be around LONG after the KFU is gone) and THEN you can take shortcuts. That's pretty much standard procedure for learning anything.
I think it's safe to say that the KFU has caused more problems for newbies than has helped. And the ones it has helped usually have to learn the old way anyway. I'm just trying to get rid of the middleman.
Just think of how great this place would be if everyone knew how to how to do this on their own.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I get your point about KFU and I think my guide is evidence of that. However, I'm in complete disagreement about your suggestion for the driver installation process. I don't believe fixing one's Kindle Fire should first involve learning the roundabout way of installing the drivers. In my mind, the KFU utility is entirely separate from the driver installation batch file. I see no good reason make that part of it any more difficult than it has to be. I also think your middleman analogy is a bit flawed. It's more like having the guy go chop down a tree in the dead of night when you've already got a stack of firewood for him.
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
marcelloLins said:
Hi everyone, i am trying to root my kindle fire device , but the process is not working.
Here is what i've done:
1. Installed Drivers from "install_drivers.bat" file from KFU
2. Manually Installed Drivers
Still cannot make ADB Status to go "ONLINE".
The way i can make it "ONLINE" is by executing the "run.bat" file as administrator, but, doing this, leads me to error "cannot find tools/wget.exe". Ofc, because running with administrator privileges forces it to run from system32 folder.
I've already tried to run from the Command Prompt, even running the command prompt as administrator aswell.
Any idea of how to solve it ?
My Kindle is 6.3 Version. I bought it in February.
I used the KFU 0.9.5 version.
I also tried to install drivers manually, from a difference source ( a youtube video tutorial of how to root 6.2 version ), but, the device manager says the drivers are already up to date.
My device manager shows a "Android device" at the top of the list, but no "Kindle" or "Amazon Kindle" device in the whole list.
What am i doing wrong ?
Please, if you can't solve it, at least, bump this thread.
Thanks !
Click to expand...
Click to collapse
So, instead of totally hijacking this thread for the sake of an argument...
I think you need to confirm that your drivers are installed properly. Regardless of what path you take to get them installed, pay attention to the middle part of this post...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
and make sure that you are seeing the right things in the device manager. You'll have to verify that part of it is working right, so Windows and the Kindle Fire are able to communicate with each other before moving ahead in your troubleshooting.
kinfauns said:
I get your point about KFU and I think my guide is evidence of that. However, I'm in complete disagreement about your suggestion for the driver installation process. I don't believe fixing one's Kindle Fire should first involve learning the roundabout way of installing the drivers. In my mind, the KFU utility is entirely separate from the driver installation batch file. I see no good reason make that part of it any more difficult than it has to be. I also think your middleman analogy is a bit flawed. It's more like having the guy go chop down a tree in the dead of night when you've already got a stack of firewood for him
Click to expand...
Click to collapse
Let me say just this and I'll let it be. Ask yourself, "What's more likely to stand the test of time? Android SDK or KFU?" What happens when KFU becomes obsolete/unmaintained and is no longer hosted for people to download? What happens when KF owners move on to other Android devices not supported in such a way? Configuring and installing device drivers is a basic skill that every Android device owner should have anyway, and it causes no harm pushing people to learn it. I'm not breaking any rules by doing so and until now you are the only one to have had a problem with it.
That being said, don't let my disagreement fool you into thinking I have anything anything less than the utmost respect for you. - Quite the contrary in fact. I personally have learned a lot from you and many others here and I feel it is my duty to pay it forward. I apologize if the method I use offends you, and if others here feel the same way I will definitely take it into consideration.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Let me say just this and I'll let it be. Ask yourself, "What's more likely to stand the test of time? Android SDK or KFU?" What happens when KFU becomes obsolete/unmaintained and is no longer hosted for people to download? What happens when KF owners move on to other Android devices not supported in such a way? Configuring and installing device drivers is a basic skill that every Android device owner should have anyway, and it causes no harm pushing people to learn it. I'm not breaking any rules by doing so and until now you are the only one to have had a problem with it.
That being said, don't let my disagreement fool you into thinking I have anything anything less than the utmost respect for you. - Quite the contrary in fact. I personally have learned a lot from you and many others here and I feel it is my duty to pay it forward. I apologize if the method I use offends you, and if others here feel the same way I will definitely take it into consideration.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Believe me, I'm not offended by this discussion. We are just having a respectful disagreement over a mutually shared desire to help people who want to mod their KF. I understand that you aren't doing anything wrong. I'm not wagging my finger at you or yelling, "my way or the highway!" It's just my belief that going the SDK route is error prone and the cost/benefit of doing it that way may be too high for most users to bear.
Let me share an experience I had with someone who PM'd me for help after deciding to install the drivers from the SDK. After days of back and forth, he figured out that he had created the adb_usb.ini file as a text file and Windows was hiding the file suffix. So, he actually had an adb_usb.ini.txt file and with Windows Explorer only showing the adb_usb.ini part, he hadn't really considered the possibility that the file could have been named incorrectly. It's the silly things that will trip up even a knowledgeable user.
I'm not saying never to the SDK... I'm just saying it shouldn't be the first choice. I certainly won't be upset if you decide to instruct users to install the SDK just for the drivers, but they might be if they figure out they could have gotten to the same place with KFU's driver installer in 1/20th of the time.
Hello, I have a stock XOOM WiFi (Wingray) and have been looking at installing a custom ROM. I am doing it for fun, knowledge, and to hopefully get a little better performance out of my XOOM.
I currently use my xoom for Web Browsing, XBMC, and Sling Player...
I have been searching the Web and this Forum for information on how i can do this, step by step but i am lost. I know that i have to do the following:
1.Unlock Boot loader (Lord AIO Tool, was unsuccessful which is why i started the thread to post useful links after i succeed.)
2.Modify the Recovery Partition.
3.BigPart
4.Install Custom ROM (Based on whatever Android Ver / Kernel)
I am running Mac OSX 10.8, have a windows VM, and access to a windows laptop if needed.
*EDIT*
Results: I used my Windows Laptop and started to have some success with the Lord AIO Tool. i dont see why the VM wouldn't work, but i had given up on the VM thinking it may have cause a problem.
Steps Needed:
1. Download Motorola Fastboot Drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
2. Download ADP Tool (or Install Android SDK and add appropriate locations to your System Path)
ADP Tool: (Awesome)
http://forum.xda-developers.com/showthread.php?t=2588979
Android SDK:
http://developer.android.com/sdk/index.html
3. Download Lord AIO Tools: (also, Awesome)
http://forum.xda-developers.com/showthread.php?t=1468298
4. Download the ROM you need. I used OMNI 4.4.2 (Also needed Big Part, and this too is Awesome)
http://forum.xda-developers.com/showthread.php?t=2593757
Big Part:
http://forum.xda-developers.com/showthread.php?t=2506997
5. Download Super User Root zip file.
6. Format an microSD Card FAT32 and copy over the following files:
TeamWin Recover Partition
TeamWin Recovery Partition Big Part (only needed for ROMs that need larger partition.
Super User
OMNI ROM (or whatever ROM you want)
GApps (one of the Google Apps. I used the gapps-wingray-kk-20131223.zip)
7. Follow Instructions for Lord AIO Tool installation and then do the following:
Run the tool and unlock the boot loader (enter option 03, not 3, but 03)
When done you need to install The recovery partition, i used TeamWin RP. (This is option 09 in the Lord AIO Tool)
Then i rebooted into recovery mode and was in the TeamWin RP menu. From there i Flashed the BigPart, then ROM, then Gapps, and then the Super User to Root.
I think there is an option to Root from the Lord AIO Tool, but i dont think i used it at all.
I was trying stuff all day and when it's all said and done I think that's basically what i did, things didnt always work on the first try and i had some trouble mounting the microSD in the Recovery Partition.
I put this here to hopefully give people new to the game a run down of what to do. i did a lot of searching yesterday and was spinning my wheels. and some of the old threads i found were quite technical and had dead links. (not necessarily from XDA) It's not a Step by Step for the XOOM but will hopefully get people who are late to the game a good start.
tonycajjo said:
Hello, I have a stock XOOM WiFi (Wingray) and have been looking at installing a custom ROM. I am doing it for fun, knowledge, and to hopefully get a little better performance out of my XOOM.
I currently use my xoom for Web Browsing, XBMC, and Sling Player...
I have been searching the Web and this Forum for information on how i can do this, step by step but i am lost. I know that i have to do the following:
1.Unlock Boot loader (Lord AIO Tool, was unsuccessful which is why i started the thread to post useful links after i succeed.)
2.Modify the Recovery Partition.
3.BigPart
4.Install Custom ROM (Based on whatever Android Ver / Kernel)
I am running Mac OSX 10.8, have a windows VM, and access to a windows laptop if needed.
*EDIT*
Results: I used my Windows Laptop and started to have some success with the Lord AIO Tool. i dont see why the VM wouldn't work, but i had given up on the VM thinking it may have cause a problem.
Click to expand...
Click to collapse
I use the Lord AIO Tool on desktop Windows 8.1 and when I ran the Set_Up.bat as Admin, it say file is missing. Not sure what i did wrong.
cat2115 said:
I use the Lord AIO Tool on desktop Windows 8.1 and when I ran the Set_Up.bat as Admin, it say file is missing. Not sure what i did wrong.
Click to expand...
Click to collapse
i did not need to run as Admin, possibly cause the user was already admin. i had issues when i ran as admin... that's one thing i forgot to add above. (I ran it on Win7 32-Bit)
2. Download ADP Tool (or Install Android SDK and add appropriate locations to your System Path)
ADP Tool: (Awesome)
http://forum.xda-developers.com/show....php?t=2588979
Android SDK:
http://developer.android.com/sdk/index.html
also, try moving LAIOT to C:\ if not already there.
after you install ADP tool you may have to reinstall LAIOT, delete the files and just start over using the setup.bat
Stuck on step seven
I will be very grateful of any help stuck on step seven it says too many parameters
floydme said:
I will be very grateful of any help stuck on step seven it says too many parameters
Click to expand...
Click to collapse
what part of step 7? my step 7 is pretty broad.
tonycajjo said:
what part of step 7? my step 7 is pretty broad.
Click to expand...
Click to collapse
After running setup bat on the second return key hit I I get too many parameters message
Perfect (step by step)
Followed this step by step, utilizing this process as well as the individual threads regarding each part (Big Part Partitioning, LORD AIO Tool-with file folder placed on "C" drive, etc.) and worked like a charm.
This thread should become sticky and placed at the very top for Xoom Rooting guide.
Stingray Xoom
kamikazebeats said:
Followed this step by step, utilizing this process as well as the individual threads regarding each part (Big Part Partitioning, LORD AIO Tool-with file folder placed on "C" drive, etc.) and worked like a charm.
This thread should become sticky and placed at the very top for Xoom Rooting guide.
Stingray Xoom
Click to expand...
Click to collapse
good stuff, glad it helped.
floydme said:
After running setup bat on the second return key hit I I get too many parameters message
Click to expand...
Click to collapse
can you write explicitly what the error says, and when you hit "enter" the second time what are you exactly hitting enter to?
also include a bit of info on what OS you are using, where you have stuff installed, and so on.