Database Users

Install non-market apps without File Manager: Possible?

Simply put is there a way to get an app onto my phone without the market or file manager?
I ask because I want to use Haykuro's G build but I cant download any apps. I do however have all the ones I use regularly backed up onto my SD card but I cant access them without a File Manager (which I cant download to use). Is there a way?
|Spike|

There's always the option of using AppsInstaller/APKInstaller and putting APK's onto your SD Card. Though, to install AppsInstaller, you have to install it through ADB.

Unicornasaurus said:
There's always the option of using AppsInstaller/APKInstaller and putting APK's onto your SD Card. Though, to install AppsInstaller, you have to install it through ADB.
Click to expand...
Click to collapse
How do I install thru ADB?
|Spike|

Get the android usb drivers, adb.exe and adbwinapi.dll from an Android SDK. Plug the Dream in via USB and point to the location of the drivers when it is installed. Then open your command line, navigate to whatever folder adb.exe is in and type adb install <full path to the apk>. If you run Linux hopefully you can figure it out on your own based on the steps above.
Alternately, upload all the apks you want to the internet somewhere. Check the box to enable installation from Non-market sources in the system settings, then type the full URL of the apk into the browser. The package installer will take over from there.

Here's how you do it. Assuming your G1 is rooted
1. Download the attched files, and copy them into your \system32 folder (Start > Run > %systemroot%\system32)
2. Sure your G1 is enabled for USB Debugging (Settings > Applications > Development > USB debugging) and that your G1 has the appropriate drivers installed. If not, download the USB drivers from HERE
3. Plug your G1 into your computer (Make sure you have USB 2.0 - Click here to find out how to check). When your G1 says "USB Connected" DO NOT click "Mount"..don't do anything
4a. Vista users - Follow these steps. For XP Users, skip to step 5
4b. On your computer, browse to the directory where the APK for your file is located
4c. Once located, hold SHIFT and right click on a blank area of the folder
4d. Click on "Open Command Window Here"
4e. Type "adb install nameofyourapkhere.apk" - without the quotes.
4f. It might say something like "daemon service not started" or something, but it will start it and continue. It'll then say something like 626k/1293k bla bla bla
4g. If it was successful, it will just say "Success". You can close the command window and SHAZAM! Your program will now be installed on your G1, and you can access it like any other program on your phone
5. XP Users - Follow these directions:
a) You can either go Start > Run > type CMD and press enter
OR
Windows Key + R > type CMD and press enter
Navigate to your APK file via the command prompt. For easy usage, put your APK file on your desktop. That way all you have to do is type "CD Desktop" into the command prompt
b)Type "adb install nameofyourapkhere.apk"
c)You may get a couple of messages like in the steps for Vista users
d)If all goes well, you too will get the success message
e)Enjoy your application!
Any confusions, let me know. Hope it helps, and Good Luck!

I've been using a local web server and the android browser.

untermensch:
Thats a possibility, but oddly enough, that requires a http-server
AGx-07_162:
With unicornasaurus's method above, you can install all the apk's you want... you can install apkinstaller and use that through that method, but you can just aswell install your apk's directly through it

I ran into the same problem. Here is the easiest ways to get the appinstaller on your G1. Download this file from your g1 browser or Gmail yourself this file, and download.
http://www.mediafire.com/?egy0mop2qqx

Droid starts in recovery mode all the time

When I turn it on in the morning it goes into recovery mode I then select the reboot and it boots up and I'm good. I turn it off at night and charge it then when I turn it on again its in recovery mode. I was rooted and had bootstrapper but I do not have bootstrapper any more but still rooted. I deleted every file and everything that was related with bootstrapper. Please help me and I'm a noob at some of this stuff.
Sent from my DROIDX using XDA App

Most will tell u this is a blessing z better to always boot into recovery than to ppotentially not boot at all one day. If you TRULY want to remove bootstrap completely, google "completely remove droid X bootstrap"
The process involves renaming a logwrapper file that bootstrap had renamed, and deleting the one created by bootstrap
Sent from my DROIDX using XDA App

I agree that its not a problem but still don't want it. Can you please tell me how to do what you said. I have no clue in how to do that. As simlp as possible please and thank you
Sent from my DROIDX using XDA App

Ok... Here goes:
1) connect your phone to ur pc in charge only mode. Makr sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no reaponsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following thesr directions, you do so at your own risk.
Sent from my DROIDX using XDA App

One question about adb you said it will recognize it. Is it on my phone or is it something that I need to installed. That's the only thing I'm a little confused on everything else I'm good on.
Sent from my DROIDX using XDA App

Adb is the driver interface between your computer and your phone. You will need the latest motorola drivers installed on ur computer. Adb is on your computer
Sent from my DROIDX using XDA App

Sorry for the stupid questions but is adb going to pop up on my computer when I plug my phone in or is it something im going to need to find. Again thank you.
Sent from my DROIDX using XDA App

spacecasespiff said:
Sorry for the stupid questions but is adb going to pop up on my computer when I plug my phone in or is it something im going to need to find. Again thank you.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Here is a way to tell if you have adb drivers installed.
1) plug in your phone via usb to your computer.
2) open a command prompt. Type "adb devices" and press enter. (you don't need the quotes)
If it returns text that looks like " device 05842688788" adb is working correctly. The random numbers will be unique to your phone.
Sent from my DROIDX using XDA App

actually if this continues and you have koush's droid x bootstrapper open it and click the first option and give it superuser permission and it should stop

ok i pluged in my phone and put it on charge mode now I clicked on the start botton on my computer brought up the search bar and typed in command prompt. Is that correct. I then entered adb devices and i said it was not reconized as and external device. now im not sure if that is what i was sopposed to do. I think i was expecting something to just pop up. This is the only thing that i dont know how to find. You say its on my computer but where do i find it.

some people who dont know what theyre doing in the first place shouldn't start....smh just saying

Funnyface19 said:
some people who dont know what theyre doing in the first place shouldn't start....smh just saying
Click to expand...
Click to collapse
Eh... Yes and no. he wants to learb, and we all had to start somewhere.
Spacecase:
You need to download and install the android sdk. Google this and post back when you have it installed =)
Sent from my DROIDX using XDA App

So how am I going to learn how to do something if I don't start some where I just don't wake up and go " I know how to do it" no one told me about the sdk and now I know thank you. It will be tomorrow before I do any more.
Sent from my DROIDX using XDA App

I downloaded the ask and have no clue inn how to use it. I click on the ask within the file it then brings up a black menu then wants me to download all sorts of stuff. The black box is where I type in the stuff but it wont let me type anything. Is this the only way to fix my problem
Sent from my DROIDX using XDA App

spacecasespiff said:
I downloaded the ask and have no clue inn how to use it. I click on the ask within the file it then brings up a black menu then wants me to download all sorts of stuff. The black box is where I type in the stuff but it wont let me type anything. Is this the only way to fix my problem
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Space,
I will need some time to try and put together some steps for you.
My suggestion would be to be careful with modding your phone. I feel like you may be in a little over your head. I do not say this to belittle you, but merely out of concern. I don't want to see ur phone break on you, and you not have the means to fix it yourself, that is all.
I am glad you have a desire to learn what you want to, but be careful, as these tools can also cause more harm than good. I will try and get you some info to set you straight!
Sent from my DROIDX using XDA App

Can't you just use root explorer to delete the hijack file and modified logwrapper, then rename logwrapper.bin to logwrapper? Instead of using all the sdk stuff?
Sent from my DROID2 using XDA App

spaceman4 said:
Can't you just use root explorer to delete the hijack file and modified logwrapper, then rename logwrapper.bin to logwrapper? Instead of using all the sdk stuff?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yes! If you've purchased root explorer.... So kinda has a caveat there! But definitely a recommended program if you know what you are doing with root privileges...

Just posting a few files for a tutorial I am typing up to come later...

GUIDE PART I:
Ok, here are the steps for setting up the sdk, getting rooted, and all that good stuff... have a feeling I will be making this into a new thread...perhaps....
SDK:
First off... you will want to go to the following site to download the sdk:
http://developer.android.com/sdk/index.html
Grab the following download: android-sdk_r08-windows.zip
I saved it to C:\sdk (i created a folder called SDK right at the root of C: drive). When it finishes, unzip this using 7zip (or any other unzip program you like) to the sdk folder. When it is finished unzipping, you should have a folder called "android-sdk_r08-windows". If you open up that folder, you will find a folder called "android-sdk-windows". Open this folder up and double click on the "SDK Manager.exe". This will open up a window, and bring up additional windows, one of which will ask you to "choose packages to install". You can download any or all of them. I recommend downloading the following:
• Android SDK Platform-tools, revision 1 (the top-most download)
• SDK Platform Android 2.3, API 9, revision 1
• SDK Platform Android 2.2, API 8, revision 2
• USB drivers (I don't think this shows up in the latest version of the sdk's first download window. I believe it is found if you go to the available packages section the "Android SDK and AVD Manager and expand the 3rd party section....but if you happen to see it in there...grab it)
This should be sufficient for now. All packages are accepted by default. If you do not wish to download all of them, simply highlight each one (one at a time) and then click the reject button towards the bottom middle of the window. When you have selected the packages you wish to download, click the install button.
After this has installed, you now have the Android SDK installed on your machine. You can close all windows related to the SDK, as we don't actually need to do anything with it, it simply has tools within it that we will need later. (This is where the adb command originates from. There is an adb.exe tool in the "tools" folder of the sdk install, but we will get to this later).
Now you will want to go to your desktop (or anywhere you have a shortcut or icon for My Computer), right click on My Computer, and select properties. Under the "advanced" tab of the window that opens, you should see a button at the bottom that says "environment variables". Click on this, and then find the "Path" variable under System Variables NOT user variables. Click Edit and go to the end of the "Variable Value" field. You will want to make sure there is a semicolon ; at the end of this before typing any additional info. You will want to add the full path of your android SDK install. For example, if you followed my example for download/saving/extracting/installing above, you would type the following information into the end of the "Variable Value" section:
C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools
If you installed to another location, be sure to type the correct path to the "tools" folder within your installation of the Android SDK. Then click the OK button, and close any windows that were opened from adding to the "path variable".
Droid X Drivers
This section is a little more difficult to explain, as there are so many variables depending on what operating system you are running (windows XP, Windows Vista, Windows 7, etc). and whether or not you are running a 32-bit or 64-bit instance of your chosen Operating system.
Here is one link for Droid X drivers:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
I simply googled Droid X drivers, I'm sure this isn't the best link, but just for example I'm throwing it out there. If you google Droid X USB drivers <your operating system> you should be able to find the drivers you need, as well as help and instructions on how to get everything working.
Once you get the usb drivers installed, you will want to connect your Droid X to your computer. If it is recognized, you will get a notification in your drop down bar on your phone. On your phone, press on the USB connection in the drop down menu, and select "charge only". Next, open up a command prompt on your computer. Type the following in and hit enter:
adb devices
You should see something simiilar to the following come up if everything is configured correctly:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A882315005010 device
If you see something similar to what I have above... then ADB is working correctly, and we can continue! Now we will move on to getting your device rooted! You will want to grab the z4root.apk that I have attached earlier in this thread and download it onto your computer. We will now test out if adb is indeed working! Save the z4root.1.3.0.apk and put it in the "tools" folder of the sdk we downloaded earlier. Now open up a new command prompt (or use the one we opened earlier if you haven't already closed it!) Change directories to the "tools" folder of the sdk:
If you installed the SDK where I used in my example.... type the following:
cd C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools (press enter)
type the following: adb install z4root.1.3.0.apk (press enter)
You should now see the following:
C:\android-sdk-windows\tools>adb install z4root.1.3.0.apk
1833 KB/s (978414 bytes in 0.521s)
pkg: /data/local/tmp/z4root.1.3.0.apk
Success
z4root and ROOTING
If you get all of this, you have now installed a package using adb and we know the interface works. If you don't want to have to mess with this method of installing, you could also download "Astro File Manager" from the android market. You would then need to save z4root.apk to your sdcard of your Droid X. Then open the Astro program and browse to your SDcard and file the z4root.1.3.0.apk. Press on the .apk file and it should come up with a box that says something similar to "open with app installer" or "app manager"... don't recall exactly what it says, but should be something similar to package management or install of some sort. After pressing on that, you should see an install button. Press on that to install z4root.
Now that z4root is installed, you will want to go to your application list on your phone and press on the z4root to open the application. Press on the permanent root button and wait! This process may take a while, and your phone will reboot, but when it does, you are now rooted.
Removing BOOTSTRAP COMPLETELY
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
Installing Droid X Bootstrap
You can grab this .apk file from this thread as well, as I have it posted in one of my previous posts. You will then install this .apk file the same way that you installed z4root. Obviously if you are using the adb command prompt method, you will want to replace z4root.apk with the full name of the droid X bootstrap apk; if you are using a file manager or installer, just follow the same instructions as before as well.
With the bootstrap installed, you are now able to take backups and restore them as well in the event your phone has problems.
There will be more to come...but it's late, and I have already type 4 pages worth of text into Word already... Add 8 hours of server management to this... equals one fried brain...gonna get some sleep.

I know I was over my head a little and did my home work about how to fix any problems that I may encountered but didn't think that I would need to use adb. I know how far I can go and be ok now. I greatly appreciate what you are doing for me. I will get back on my computer when im done at work. I seem to have the right file downloaded so im good there. I will let you know how it goes. Again thank you. Im done messing with my phone and I find out that it runs great and is quick even with no roms or tweeks. Best phone I've owned.
Sent from my DROIDX using XDA App

DX noob here. Anybody wanna help me out?

I ordered my DX earlier today and should have it tomorrow afternoon. (yay!)
I'm coming from the LG Ally, which I played around with quite a bit as far as root/roms go. I ended up bricking it when the Froyo update came out trying to get from 2.1 to one of the new 2.2.1 roms.
I've seen a lot of stuff about the DX and it looks like a lot of progress has been made (yay, again!). I love the look of Gingerbread, so I'd probably look into flashing one of the roms that supports a GB theme (Liberty looks cool!), but I don't want to run into trouble when the official GB release comes out.
So, how hard is this on the DX? What are the general steps? What in the world is a SBF?
Any sort of basic noob-friendly introduction would be greatly appreciated!
Thanks!

Here is a bunch of stuff I have put together for various people that should get you started:
Ok, here are the steps for setting up the sdk, getting rooted, and all that good stuff... have a feeling I will be making this into a new thread...perhaps....
SDK:
First off... you will want to go to the following site to download the sdk:
http://developer.android.com/sdk/index.html
Grab the following download: android-sdk_r08-windows.zip
I saved it to C:\sdk (i created a folder called SDK right at the root of C: drive). When it finishes, unzip this using 7zip (or any other unzip program you like) to the sdk folder. When it is finished unzipping, you should have a folder called "android-sdk_r08-windows". If you open up that folder, you will find a folder called "android-sdk-windows". Open this folder up and double click on the "SDK Manager.exe". This will open up a window, and bring up additional windows, one of which will ask you to "choose packages to install". You can download any or all of them. I recommend downloading the following:
• Android SDK Platform-tools, revision 1 (the top-most download)
• SDK Platform Android 2.3, API 9, revision 1
• SDK Platform Android 2.2, API 8, revision 2
• USB drivers (I don't think this shows up in the latest version of the sdk's first download window. I believe it is found if you go to the available packages section the "Android SDK and AVD Manager and expand the 3rd party section....but if you happen to see it in there...grab it)
This should be sufficient for now. All packages are accepted by default. If you do not wish to download all of them, simply highlight each one (one at a time) and then click the reject button towards the bottom middle of the window. When you have selected the packages you wish to download, click the install button.
After this has installed, you now have the Android SDK installed on your machine. You can close all windows related to the SDK, as we don't actually need to do anything with it, it simply has tools within it that we will need later. (This is where the adb command originates from. There is an adb.exe tool in the "tools" folder of the sdk install, but we will get to this later).
Now you will want to go to your desktop (or anywhere you have a shortcut or icon for My Computer), right click on My Computer, and select properties. Under the "advanced" tab of the window that opens, you should see a button at the bottom that says "environment variables". Click on this, and then find the "Path" variable under System Variables NOT user variables. Click Edit and go to the end of the "Variable Value" field. You will want to make sure there is a semicolon ( at the end of this before typing any additional info. You will want to add the full path of your android SDK install. For example, if you followed my example for download/saving/extracting/installing above, you would type the following information into the end of the "Variable Value" section:
C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools
If you installed to another location, be sure to type the correct path to the "tools" folder within your installation of the Android SDK. Then click the OK button, and close any windows that were opened from adding to the "path variable".
Droid X Drivers
This section is a little more difficult to explain, as there are so many variables depending on what operating system you are running (windows XP, Windows Vista, Windows 7, etc). and whether or not you are running a 32-bit or 64-bit instance of your chosen Operating system.
Here is one link for Droid X drivers:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
I simply googled Droid X drivers, I'm sure this isn't the best link, but just for example I'm throwing it out there. If you google Droid X USB drivers <your operating system> you should be able to find the drivers you need, as well as help and instructions on how to get everything working.
Once you get the usb drivers installed, you will want to connect your Droid X to your computer. If it is recognized, you will get a notification in your drop down bar on your phone. On your phone, press on the USB connection in the drop down menu, and select "charge only". Next, open up a command prompt on your computer. Type the following in and hit enter:
adb devices
You should see something simiilar to the following come up if everything is configured correctly:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A882315005010 device
If you see something similar to what I have above... then ADB is working correctly, and we can continue! Now we will move on to getting your device rooted! You will want to grab the z4root.apk that I have attached earlier in this thread and download it onto your computer. We will now test out if adb is indeed working! Save the z4root.1.3.0.apk and put it in the "tools" folder of the sdk we downloaded earlier. Now open up a new command prompt (or use the one we opened earlier if you haven't already closed it!) Change directories to the "tools" folder of the sdk:
If you installed the SDK where I used in my example.... type the following:
cd C:\sdk\android-sdk_r08-windows\android-sdk-windows\tools (press enter)
type the following: adb install z4root.1.3.0.apk (press enter)
You should now see the following:
C:\android-sdk-windows\tools>adb install z4root.1.3.0.apk
1833 KB/s (978414 bytes in 0.521s)
pkg: /data/local/tmp/z4root.1.3.0.apk
Success
z4root and ROOTING
If you get all of this, you have now installed a package using adb and we know the interface works. If you don't want to have to mess with this method of installing, you could also download "Astro File Manager" from the android market. You would then need to save z4root.apk to your sdcard of your Droid X. Then open the Astro program and browse to your SDcard and file the z4root.1.3.0.apk. Press on the .apk file and it should come up with a box that says something similar to "open with app installer" or "app manager"... don't recall exactly what it says, but should be something similar to package management or install of some sort. After pressing on that, you should see an install button. Press on that to install z4root.
Now that z4root is installed, you will want to go to your application list on your phone and press on the z4root to open the application. Press on the permanent root button and wait! This process may take a while, and your phone will reboot, but when it does, you are now rooted.
Removing BOOTSTRAP COMPLETELY
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
Installing Droid X Bootstrap
You can grab this .apk file from this thread as well, as I have it posted in one of my previous posts. You will then install this .apk file the same way that you installed z4root. Obviously if you are using the adb command prompt method, you will want to replace z4root.apk with the full name of the droid X bootstrap apk; if you are using a file manager or installer, just follow the same instructions as before as well.
With the bootstrap installed, you are now able to take backups and restore them as well in the event your phone has problems.

Thanks for the reply, but it's actually pretty confusing...
To install z4root, do I NEED to do any of those adb steps or can I just sideload it? I'm not sure if you're telling me to do both of those steps or just either/or. Sideloading is much easier, if it's an option.
And as far as the bootstrap goes - am I removing the original bootstrap and then installing the apk you attached to replace it with a custom bootstrap? Is this different than a custom recovery?
Also, what are SBFs and how do they fit into all of this?
Thanks!

lextex said:
Thanks for the reply, but it's actually pretty confusing...
To install z4root, do I NEED to do any of those adb steps or can I just sideload it? I'm not sure if you're telling me to do both of those steps or just either/or. Sideloading is much easier, if it's an option.
And as far as the bootstrap goes - am I removing the original bootstrap and then installing the apk you attached to replace it with a custom bootstrap? Is this different than a custom recovery?
Also, what are SBFs and how do they fit into all of this?
Thanks!
Click to expand...
Click to collapse
No, you do not have to do it this way. I just used this as an example for something I was doing for someone else, especially since they needed the sdk anyways... Just was practice.
(PS, not sure what you mean by sideloading... sorry just not familiar with the term...) Nonetheless...
You can just download the file, and then use file manager to install the file or any app installer you may normally use. Just make sure that under Settings-->Applications-->Unknown sources, that the check box is marked. Then you should be good to go.
As for bootstrap... You are basically replacing a logwrapper file that tells the phone to boot to Motorola's built in recovery. Koush's bootstrap hijacks this and writes its own logwrapper and allows for the recovery process to be interrupted so backing up/restorying, etc. You can load that apk the same way you do Z4root.
As for SBF files, I'm can't recall what it actually stands for, but it is basically a file from Motorola that allowed their employees to flash a phone back to "out of the box" state in the event that a customer ruined their phone or had issues with it... this goes way back to even the Motorola Razor days I believe... In any event, it is used alongside a program called RSDlite. This program allows you to connect your phone to your computer and flash the sbf files that have been released, and as a result allows you to restore your phone back to a "clean" state in the event that you mess up the /system partition and for other uses as well.
I will be adding more to a basic guide for all things Droid X later this weekend. If you have more questions, feel free to post back. And check out my other post here:
http://forum.xda-developers.com/showthread.php?t=940986
This includes the same info as I posted here already, but should have some more updates this weekend.
Good luck!

new here also.
i thought droid x could not be rooted.
i bought mine in october 2010; it's running 2.2.1
thanks in advance

Simplifying ADB installation

There's a lot of angst around getting ADB to work, particularly over USB, and it leaves a lot of folks frustrated. Some of the stuff I have seen is outdated for one and USB itself is problematic.
But, if you use Manual Nooter (for 1.2), GabrialDestruir baked in ADB Wireless, so it should be super easy to go from zero to ADB connected in nothing flat now. Here's some quick instructions that won't change.
1. Make sure you have Java installed (I'm sure you do). You *do not* need the JDK to do this!
2. Go to the android site and grab the Android SDK zip file (the windows executable *requires* the JDK so grab the zip file)
3. Unzip it to the root of your drive (it has the 'android-sdk-windows' folder in it)
4. Now go in the android-sdk-windows folder and launch sdk manager
5. Cancel out of the window that pops up with a list of a bunch of stuff
6. Click on available packages
7. Now expand 'Android Repository' and check 'Android SDK Platform-tools'
8. Now click 'install selected' and then 'install' on the next screen
9. After it finishes it will ask if you want to restart ADB, go ahead and select yes
10. Now do the standard path edit and add these two paths to your environment path: c:\android-sdk-windows\platform-tools and c:\android-sdk-windows\tools
11. On your nook, start up adb wireless and note the command it tells you
12. open a command window on your pc and type the command adb wireless gave you
Voila! You are using ADB to access your Nook Color! No special drivers or ini files, etc. I know there is an easy ADB USB thread, but I actually eventually had issues with that and went back to grab the original "official" kit to get things working. I just did the above on a fresh machine with nothing else and it worked flawlessly.
Anyway, I figured this might help a few people out there.

[ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version

This is a simple Step-by-Step guide on How To: How To: Root the Kindle Fire 7" HD, Kindle Fire HD 8.9" and Kindle Fire 2 with Windows - Noob (Simple) Version. The main group steps are outlined with A, B, C while the sub-group steps are outlined with 1, 2, 3. We attempt to keep this tutorial updated regularly - adding information from the end users experience. We have recently upgraded the storage servers to increase uptime, you now have two options for the downloads both are ad free. Option one is a Dropbox Storage Server and Option two is a Ubuntu One Storage Server, if one is under maintenance you may use the other download link. When you are done with the tutorial, please take the time to post feedback, this is very important to us - without your feedback, we have no way of knowing if we are doing our job. Finally, if you feel we did a decent job, please think about donating to us using the "Donate to Me" button - this is how we make a living, without your kind donations we would no longer be able to do this for a living.
Prerequisites:
1. Software: Windows XP, 7 or 8 Workstation 32bit or 64bit
2. Hardware: Free USB 2.0 or Greater Port
3. Kindle Fire HD 7", Kindle Fire HD 8.9" or Kindle Fire 2 7"
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/showthread.php?p=36373627
It is important that you use our Utilities since we have modified the ADB daemons plus we did little tweaks in some of the batch files. PLEASE USE OUR UTILITIES, WE ARE RECEIVING A NUMBER OF FAILURES CAUSED BY USING ANOTHER PARTIES UTILITIES. IF YOU FOLLOW THE STEPS BELOW, EXACTLY, YOU HAVE A 99% CHANCE OF SUCCESS.
Unplug the Kindle from USB.
A) Although the processes do not use Java directly, the software does call to some Java API's so we need to make sure Java is updated to the latest version. Please go to Oracle's site here: Java SE Development Kit 7u13 download and install Java SDK 32-bit or 64-bit. Reboot your computer after installing the Java update.
B) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle, move on to Main Step C
Note: Please remove any old or outdated drivers by following the instructions in Post #361 here: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers(Dropbox) or Kindle Fire ADB Drivers(Ubuntu One)
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
Please open an Administrative CMD Prompt and enter:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot the Computer to apply the above command.
Extract the Kindle Fire ADB drivers.zip to your desktop.
1. Unzip Kindle Fire ADB drivers.zip to Kindle Fire ADB drivers on your desktop.
2. Click windows start button.
3. Next choose Search, in the "Search programs and files" box type "cmd" (don't hit enter or search).
4. The program "cmd.exe" should be listed at the top. Right click that and select "Run As Administrator".
5. Navigate to the Kindle Fire ADB drivers.exe or KindleDrivers.exe using the DOS Command cd.
6. Next, the install will begin, allow the install to complete.
7. While the driver is installing. Go to the Kindle unlock if locked.
8. Pull down the upper bar. Select "More".
9. Now Select the "Security" Tab.
10. In Security is an option to: Enable ADB
11. Select "On" to Enable ADB on the Kindle
If not, We have an alternative driver here: usb_driver(Dropbox) or usb_driver(Ubuntu One)
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
2. Select Install from a list or specific location and click Next.
3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
5. Click Next to install the driver.
Or, to upgrade an existing Android USB driver on Windows XP with the new driver:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Android Phone in the right pane.
5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9.Click Next to upgrade the driver.
C-1) The next steps are used to Root the Kindle - Preferred Method (Automated Version)
The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Plug the Kindle back into USB if it is not already plugged into USB.
Root Step 1: Download Kindle Fire First Aide: Windows 32-bit Version Or Windows 64-bit Version
Root Step 2: Using either 7-Zip or Microsoft Zip, unzip the KFFirstAide.zip to your C:\ Drive as C:\KFFirstAide
Root Step 3: With your mouse, open the C:\KFFirstAide contents by double mouse clicking the C:\KFFirstAide folder
Root Step 4: Find the RunMe.bat file. Right Hand Mouse click on RunMe.bat, select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Root Step 5: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Root Step 6: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Root Step 7: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Root Step 8: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Code:
;C:\KFFirstAide
Note: Do Not forget the semi-colen before the C:\KFFirstAide
Root Step 9: That is it! The software is ready. Next we get the Kindle ready to Root.
Root Step 10: Please check the Kindle under More + > Security - make sure ADB is ON. Leave it disconnected from USB.
Root Step 11: Launch Kindle Fire First Aide, if the ADB Driver is not installed, use Option 12 to Install the ADB Driver
Root Step 12: Make sure the Kindle is turned ON, plugged into the Computer USB and ready. Select Option 15 to Root the Kindle. If Option 15 fails to Root the Kindle, use Option 16.
Root Step 13: That is it! The Kindle now has Root, you may close the software.
You may view the Kindle Fire First Aide Forum Notes here: http://forum.xda-developers.com/show....php?t=2096888
C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version):
The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID 32-bit!(Dropbox) or Root MANY ANDROID! 64-bit(Dropbox) to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Win32 or Win64 folder.
Next Single Left Mouse Click on the Win32 or Win64 folder tool-bar.
This highlights the Win32 or Win64 folder.
Note: Make sure none of the files within the Win32 or Win64 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it may react VERY slow, this is normal - leave it alone. Immediately proceed to Step 1 again. If the Kindle reboot normally and appears normal, then proceed to Step 3 you are almost done.
Root Step 3: Download suchecker.apk from here: Root Checker Basic(Dropbox)
Root Step 4: Using Windows Explorer, move suchecker from the desktop to /Kindle/Internal Drive/Download
Root Step 5: Now go to the Kindle. Using ES File Explorer or Root Explorer, go to /sdcard/Download/suchecker.apk choose Install
Root Step 6: When the install has finished, go to your Apps. Launch Root Checker. When you check Root you will be presented with a "Allow" dialog box, be sure to Allow Root Checker. You should now see that Superuser.apk is working.
You should now have root AND if this is true your ADB communication is also functional.
D) Finally, let's disable the Amazon OTA (Over The Air) Updates so your hard work is not destroyed.
OTA Step 1: Open Kindle Fire First Aide - Select Option 14 to Disable OTA.
Note: You may still install the updates manually after you have read the install notes and know what to expect. The updates and manual install instructions can be found on Amazon Support here: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_sib?ie=UTF8&nodeId=201016350
E) Finally drop to an Administrative CMD and enter:
Code:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
Reboot the computer to apply the above command.
When you run Root Checker, the output should be similar to:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, move onto our How to: Install Google Play Step-by-Step Thread

:good::good::good::good::good:

how long is it suppose to stay at *daemon started successfully* ?

ADB Communication Issues
urbannerdmaeio said:
how long is it suppose to stay at *daemon started successfully* ?
Click to expand...
Click to collapse
Once you plug in the Kindle, it takes up to 2 minutes for Windows to detect it. So having said this *daemon started successfully*
Should not be displayed for longer than 2 minutes.
Where did you download the Utilities? From us or the developers? Our utilities use new updated adb.exe daemons
dated 11/05/2012 11:06AM
If the adb.exe has the correct date stamp, then make sure you are following our instructions on how to open a command
prompt. If you are following the instructions exactly then....
You must have Windows 7 which requires you to open an Administrative Prompt by choosing Run as: Administrator when
opening the CMD Shortcut.

Still nothing...
I downloaded the files from this thread, minus the ADB drivers because my computer already reads it under the device manager.
I go to the start menu, search for "cmd", run it as administrator and launch RunMe.bat from it
and it reads this to me
http[semi-colon]//s9.postimage.org/bpzs9w8u7/Untitled_1[dot]jpg
and nothing happens to the kindle, no message to restore and if i press any key on the command prompt it doesnt do anything either.

ADB Communication Issues
urbannerdmaeio said:
I downloaded the files from this thread, minus the ADB drivers because my computer already reads it under the device manager.
I go to the start menu, search for "cmd", run it as administrator and launch RunMe.bat from it
and it reads this to me
http[semi-colon]//s9.postimage.org/bpzs9w8u7/Untitled_1[dot]jpg
and nothing happens to the kindle, no message to restore and if i press any key on the command prompt it doesnt do anything either.
Click to expand...
Click to collapse
Please verify the date of the adb.exe daemons. Reply back with the date if the daemon in Root_with_Restore_by_Bin4ry_v17Root_with_Restore_by_Bin4ry_v17 Stuff folder.
Next download this mini-test utility: https://dl.dropbox.com/u/54456659/ADB%20Update.zip to your desktop
Unzip ADB Update.zip to your desktop
Open the ADB Update folder on your desktop
Make sure the Kindle is still plugged into USB.
Double Mouse Click and Open the ADB Update folder.
Next Single Left Mouse Click on the ADB Update folder toolbar.
This highlights the ADB Update folder.
Note: Make sure none of the files within the ADB Update are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
adb kill-server
adb start-server
adb devices
Respond with the results.

Never mind

results...
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be

urbannerdmaeio said:
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be
Click to expand...
Click to collapse
I was getting the same results as you earlier. The mistake i made was that i believed my drivers were good too because my PC was reading the device under device manager. This ended up being a bad assumption. I deleted the drivers and installed the drivers that are found in the Qemu Zip folder. The drivers there worked perfectly.
I am rooted w/Play & thats what made the difference.

fiddystorms said:
I was getting the same results as you earlier. The mistake i made was that i believed my drivers were good too because my PC was reading the device under device manager. This ended up being a bad assumption. I deleted the drivers and installed the drivers that are found in the Qemu Zip folder. The drivers there worked perfectly.
I am rooted w/Play & thats what made the difference.
Click to expand...
Click to collapse
I've tried this several times, I keep getting the exact same problem regardless of where I get the drivers from, or what computer I use. I'm ready to pull out my hair...

ADB Communication Issues
urbannerdmaeio said:
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be
Click to expand...
Click to collapse
There is a problem with ADB Communicating to the Kindle.
What platform are you using? Windows 7?
Are you sure ADB is enabled on the Kindle itself?
When you go into Windows device manager, do you see any Yellow Triangles over the devices?
In the device manager, do you see "Android Composite ADB Interface" or ?

ive already uninstalled and deleted the drivers, then installed the ones from the Quem folder and it gives me the same "drivers were not installed blah blah" message everyone else gets, and so i unplug then plug back in the kindle and my pc reinstalls the adb drivers....
try to root again, and nope, nothing.
heres a screen shot of my device manager (WINDOWS 7 x64)
http[semi-colon]//s14.postimage.org/6t9oytl5d/Untitled_3[dot]jpg
& yes im 100% positive ADB is on

Woop, finally got it rooted! Thanks for the noob guide and your patience.
One more question tho, I can't find where this path is: /system/ect/security/otacerts.zip
I'd rather not have amazon get rid of my rooting and wipe all my google play apps once I get that up and running.

ADB Communication Issues
urbannerdmaeio said:
ive already uninstalled and deleted the drivers, then installed the ones from the Quem folder and it gives me the same "drivers were not installed blah blah" message everyone else gets, and so i unplug then plug back in the kindle and my pc reinstalls the adb drivers....
try to root again, and nope, nothing.
heres a screen shot of my device manager (WINDOWS 7 x64)
http[semi-colon]//s14.postimage.org/6t9oytl5d/Untitled_3[dot]jpg
& yes im 100% positive ADB is on
Click to expand...
Click to collapse
OK, everything looks good with ADB. Looks like we have a pesky Windows 7 issue. Windows 7 Command prompt is only User level by default and will cause these utilities to fail.
If you go into Programs > Accessories or Programs > Accessories > System Tools do you see the Command Prompt? Now Right Hand Mouse click over the prompt and choose Run As Administrator
Once the Command Prompt is opened navigate to each utility using the "cd" "cd.." "cd c:\" etc command.
Once you navigate to the Root_with_Restore_by_Bin4ry_v17 folder, you will be able to successfully run the batch file through the Administrative prompt.

Thank you
Wow thank you for taking all of this time to put together a easy to follow guide in rooting the Kindle Fire HD. I plan to do this soon, just waiting on my scorpi0n cord, just incase I make a mistake. I am a total noob to android so I am looking forward to seeing some of the options with root. Again thank you

Follow Up
Jayj0ka said:
Wow thank you for taking all of this time to put together a easy to follow guide in rooting the Kindle Fire HD. I plan to do this soon, just waiting on my scorpi0n cord, just incase I make a mistake. I am a total noob to android so I am looking forward to seeing some of the options with root. Again thank you
Click to expand...
Click to collapse
Thank you for the feedback. We are here to support you.
We monitor the Threads closely from about 10AM PST to 10PM PST USA GMT -8 so if you get stuck we'll be here for you.

prokennexusa said:
This is a simple Step-by-Step guide on How To: Root the Kindle Fire 7" HD. The main group steps are outlined with A, B, C while the sub-group steps are outlined with 1, 2, 3.
Click to expand...
Click to collapse
Your guides are amazing can I request a how to backup and restore possibly, you offer so much information and support that really helps to break down and simplify the process for me.
Again thank you

Backup and Restore
Jayj0ka said:
Your guides are amazing can I request a how to backup and restore possibly, you offer so much information and support that really helps to break down and simplify the process for me.
Again thank you
Click to expand...
Click to collapse
Thank you for the feedback.
We are in the process of creating a How to: Backup and Restore the Kindle System Image
Give me 48 hours for this series. We are working on How to: How to: Install ICS Google Applications and Google Voice Noob (Easy) Version at the moment.

Hi, Excellent guide!
Will this work on Kindle Fire 2nd Gen (10.2.4)

Big thanks, all these How-To guides are great, bookmarked them all