Database Users

Rooting through a noob's eyes

I'm not sure how this will be taken by the people here. Everyone seems really helpful when other people ask questions or need help so I may be surprised, but after rooting my Incredible last night and then trying to look into boot animations, removing bloatware and other things I was left with some feelings that took the joy out of being rooted and I wanted to share them.
Laugh if you will, insult if you feel it's necessary. I'm old enough to be able to handle it but beyond all of that I just wanted to say that the "rooting community" are a brilliant bunch of people. The things that you guys do boggles my mind. Since I only just registered I'm forbidden to post links, but if you're so inclined to go read it here it is.
ishootpixels.tumblr.com/
EDIT: I'd also like to add that my wife's netbook is running XP and not Vista. I forgot that we downgraded it (or upgraded however you want to look at it). I've gone back and changed my blog post.

If you would like some help getting where you want to be, PM me and I would be glad to help. I am far from an expert, but after scouring these forums endlessly, I am quite familiar with the process.

@mtag1029 Thanks. I guess my first problem is that whenever I type in "adb" anything, I get that "adb is not recognized as an internal or external command, operable program or batch file."
I've used this method to connect the phone to the netbook...
1. Boot into Clockworkmod recovery by powering off the phone and pressing and holding the volume down and power button until the screen lights up.
2. At the menu press volume down to select Recovery, then press power.
3. At the Clockworkmod main menu select partitions menu, then select mount /system
4. On the computer click Start > Run, and type CMD to open a command prompt.
5. In the command prompt type cd\sdk\tools
6. At the command prompt type adb shell. Now you’re in the phone’s OS.
and I get as far as step 6 before I can't go any further which is where I get that message. Right now I'm trying to install a boot animation and sound but I'll also need to be able to get beyond this in order to remove the bloatware. What am I doing wrong?
And THANK YOU again for the help. I'm almost to the point of returning it to stock so I'll at least be able to get Froyo whenever it's released OTA, but I've come so far at this point I'd hate to throw it all away and go back to stock.

IShootPixels said:
5. In the command prompt type cd\sdk\tools
6. At the command prompt type adb shell. Now you’re in the phone’s OS.
Click to expand...
Click to collapse
Assuming your sdk folder is in the root of the C drive (i.e. C:\sdk\), the command in step 5 is wrong -- it's supposed to be:
Code:
cd \sdk\tools
with a space. That should get you into the C:\sdk\tools directory, where adb is.
Not sure if the lack of spacing was just a typo, but if not, there ya go Let me know how it works
edit: Just tried cd\sdk\tools, actually works, I thought there had to be a space, but maybe not. I guess the next step would be to make sure there's an adb.exe in your tools folder?

I created a file folder under Local Disk C called "sdk" and inside that I created another folder "tools". I couldn't find folders that were already named this so I created them myself. That may be wrong so it wouldn't surprise me if that's my first mistake.
Beyond that, when I get into running command lines I have gotten to where it looks like this...
C:\sdk\tools>
No spaces. I'm taking a pic and trying to attach it if my noob status on the forums will allow me.

I don't have the exe file. I didn't need it to root the phone. I don't know where to even get it.

IShootPixels said:
I created a file folder under Local Disk C called "sdk" and inside that I created another folder "tools". I couldn't find folders that were already named this so I created them myself. That may be wrong so it wouldn't surprise me if that's my first mistake.
Click to expand...
Click to collapse
If you just made the folders, there's nothing in them -- if you go to the tools directory and type "dir", there probably won't be any files unless you extracted some in there.
From the how 2 adb thread by dreamersipaq:
1) Setting up ADB
ADB stands for Android Development Bridge. It is used by Android developers for programming. For us, it is used to hack into our phones . For our purposes, just know that it is like the cmd (command prompt) that allows us to send commands to our phone. This is extremely useful when we're in the custom recovery
Download the Android SDK from Google: http://developer.android.com/sdk/index.html
Unzip to your desktop
Take the "android-sdk-_**-windows" folder and move it to the root of your hard drive (C:\)
** will change, it is revision of SDK, like "r6"
****The below is not necessary, but is useful sometimes if you just want to run "adb shell" from anywhere without going into the sdk directory****
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-_**-windows\tools
****End of the "This is not necessary thing****
Click to expand...
Click to collapse
edit: the rest of that thread is located http://forum.xda-developers.com/showthread.php?t=709220 there, if you're interested

gmonox is absolutely correct. You cannot just create the folders. They have to come from the sdk.
Another thing. You mentioned in your blog post that you would like to have froyo. Froyo should be flashed before removing any apps becauseeverything that you have removed will be put back in with froyo.

Wow, that was a pretty necessary step that I never knew about. Okay, so I DL'd, unzipped, and copied the folder to the root of C. Question, do I have to rename the "android-sdk-windows" folder to simply "sdk" when following the directions I listed earlier or do I leave it and at the command line type...
cd\android-sdk-windows\tools
I also didn't do the "advanced" part of the post simply because it's my wife's PC and I'm really not in the mood to screw up anything else today.
EDIT: And about Froyo, right now I just want to see if I can get a little boot animation working before I even THINK about tackling ROMs, Kernals or anything else. Although I know that most ROMs have the kernals that are optimized for that particular ROM if I've read things right. I realize Froyo is not a mod so it won't have an overclocked kernal but I read that others might. I've read that Froyo packs in VZ Nav (like I didn't have enough of that crap with my old Blackberry) amongst other things. If nothing else, I'm really good at reading about all of the things that I wish I could do.

IShootPixels said:
Wow, that was a pretty necessary step that I never knew about. Okay, so I DL'd, unzipped, and copied the folder to the root of C. Question, do I have to rename the "android-sdk-windows" folder to simply "sdk" when following the directions I listed earlier or do I leave it and at the command line type...
cd\android-sdk-windows\tools
I also didn't do the "advanced" part of the post simply because it's my wife's PC and I'm really not in the mood to screw up anything else today.
EDIT: And about Froyo, right now I just want to see if I can get a little boot animation working before I even THINK about tackling ROMs, Kernals or anything else. Although I know that most ROMs have the kernals that are optimized for that particular ROM if I've read things right. I realize Froyo is not a mod so it won't have an overclocked kernal but I read that others might. I've read that Froyo packs in VZ Nav (like I didn't have enough of that crap with my old Blackberry) amongst other things. If nothing else, I'm really good at reading about all of the things that I wish I could do.
Click to expand...
Click to collapse
Either way works. I renamed mine sdk because I'm too lazy to type android-sdk-windows every time I want to go into adb shell. But it's up to you

Ok, I'm guessing that my question will be answered after I run the setup. I didn't see the link at first to the thread. Apparently my wife's netbook doesn't even have the right java ver. to run the setup.
This is making my brain hurt.

I should have asked this earlier, have you made a nandroid backup?

LOL. Actually as soon as I finished rooting the phone I DL'd Titanium from Marketplace and installed it and BusyBox and made a backup that way. Then I remembered Nandroid and went in and backed up that way too. Probably overkill but the whole process has scared the crap outta me. I wouldn't know how to apply these backups, but at least I have them.
At the moment I'm installing the Documentation for Android SDK, API 8, revision 1
EDIT: This is going to take awhile I'm guessing. Installing SDK Platform Android 2.2, API 8, revision 2

Okay. The nandroid is the most important. It will save your butt if something goes wrong.

IShootPixels said:
LOL. Actually as soon as I finished rooting the phone I DL'd Titanium from Marketplace and installed it and BusyBox and made a backup that way. Then I remembered Nandroid and went in and backed up that way too. Probably overkill but the whole process has scared the crap outta me. I wouldn't know how to apply these backups, but at least I have them.
At the moment I'm installing the Documentation for Android SDK, API 8, revision 1
Click to expand...
Click to collapse
Both types of backups are easy to restore, for nandroid you just go into recovery, same place as you backed it up but click Restore and just wait for it. For titanium, go into backup/restore, batch, and there's an option to restore apps, apps+data, and apps+system data I think. If you have the paid version, the apps will all install on their own, but if not I don't think they will.
Are you still on a netbook or can you use a pc? Might be easier if your java's out of date and whatnot to just use a pc, I'm no expert on netbooks but I'd imagine they're stripped down a lot

gmonox said:
Both types of backups are easy to restore
Click to expand...
Click to collapse
Just keep in mind that you need a functioning phone in order to use Titanium. If you mess something up while in adb and the phone will not boot, Titanium is useless. A nandroid however will restore you back exactly how you were before messing around in adb even if the os will not boot.

Well then I'm glad I did the Nandroid BU! Bsically then I guess that because I backed up with Ti first and then with Nandroid, the Nandroid created a back up of my Ti backup. If so I think I just set a record for redundancy.
As for using a netbook, I don't have a choice. I run everything off of my Macbook, or did until now. The only Windows based item in the house aside from my Xboxes is my wife's netbook. I've updated the Java and begun the setup process. I had to do as the thread said and force the http and then go into the available packages and I'm DLing and installing them all because I was afriad that if I didn't I'd find that I needed one I hadn't installed. I'm guessing that since I'm already rooted (and I'm hoping) that once I'm done installing all of these packages that that should be it except for step #4 and #5.
1. Run SDK Setup.exe
2. If it gives you any error go to settings and click on "Force http//....."
3. Select usb driver package, let it download and install
4. Some say the below step is not needed, but I did this so I'm posting it
Go to tools folder, and edit "android_winusb.inf" (you can do this by opening it via wordpad). Add the following at the end of the [Google.NTx86] and [Google.NTamd64] blocks:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Save the file and exit.
5). Plug your phone into PC, when windows asks to install drivers for new found hardware, point the New Hardware Found wizaed to android_winusb.inf that you just edited.

I'd also like to add that this is the YouTube video that started this mess. I followed his tutorial on rooting the phone and although the sound was low it was pretty spot on minus one or two things he failed to mention.
However, after watching this video I thought it would be just as easy to install the boot animation as it was to root the phone. Seems the bigger task would be rooting rather than a boot animation. In the hours that you guys have helped me I've learn that this boot video lacks a TRUCK LOAD of information and assumes that the person watching it isn't a noob. Dont' most people that watch tutorial videos watch them because they have no idea what they're doing? I realize now that there's a ton o' stuff missing from it. I still want the animation and sound though.
http://www.youtube.com/watch?v=-Ju9lpH7_4g&feature=channel

Titanium stores backups on your SD card. Nandroid does not backup your SD card, but you are in good shape. Keep us posted.

I'm not sure if step 4 is required, I'm on win7 64bit and I don't recall doing it, but I guess it couldn't hurt. Also, I don't think nandroid backs up your titanium backup -- Ti backup is stored on your SD card

Android Commander.

I just want to give props to a program for windows called Android Commander. I am not sure if its been mentioned on the Vibrant forum yet, but it got me out of a major jam today.
Android Commander is basically ADB with an easy to use interface. It lets you pull and push files to and from your pc to your Android device.
Story:
I tried to MM the Androdena theme but it seems the framework was corrupted and caused me to keep me in a forceclose loop not letting mount or boot or really do anything. I did make a nandroid backup but some how deleted the CW update zip from my sd at an earlier date and could only boot up into the stock recovery. I was ok with having to reflash the stock rom using Odin, but needed some important pictures that I took for work. Needless to say I starting freaking out. I have ADB set up but only know a few basic commands and I'm sure what I needed to be done could have been done from there. I started searching for solutions on Google and found this awesome program.
I was first able to move the picture folder from my sd card to my pc, then move and rename the CW update.zip to root of the sd card in turn letting me boot into CW recovery and restoring my nandroid.
The only thing I needed to do was to make sure my device was online through ADB and Android Commander was able to find the device and show me all my files and such. Its a great program, and I highly recommend it if you are not familiar with ADB.

I will need to check this out when I get home. I want an easy way to remove the bloatware on my phone.

it seems like an interesting program, and would be good, but for me it doesn't show that i have root. it tells me "root no" and when i use the console in it and use the su command it tells me no. but still a good program over all, i did some looking around and i believe it will only show you have root access if you have an APP2SD installed. i might be wrong with that, but atleast if anyone else has the same trouble with it please let me know if you figure a work around.
ps, you can view root files and folders just not push or pull anything from them.

Yep, I am seeing the same thing.
I did some research on Google and this is what I came up with:
"adb remount and adb root are protected commands and need either a rooted kernel or a flashed recovery model to run" - Source: Rastaman-FB

ah I see. That's good to know. I guess ill be sticking with just the normal ADB. But I think the program will still be very useful for other stuff considering we don't have to mount the USB so no rescan media after the unmount. That alone is a keeper for me. Thanks again for the information pal.
Sent from my SGH-T959 using XDA App

I must say
I have been using android commander since his 1st beta on all my android rooted phone..
It is the best android tool Out there.
Im usually private about the tools I use but
Android Commander (By PanPiotr) is the best and easiest adb GUI tools out there.
Features
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- update
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more…
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off phone
- screenshots (beta)

Stupid question. I accidently deleted my update.zip file and I attempted to reflash another rom. Of course now I'm stuck at the Vibrant Logo and tried to use this app. It says its trying to connect, but never does. I have SDK installed, but I think its the version from when I was tinkering with the G1.
I got into Download mode with the BIG yellow triangle, but my PC never seems to show anything connected via USB unless I try connecting via Recovery.
This app sounded like something would help me since I'm not very good at ADB, but I guess I'm having issues getting over the first hurtle is seems. LOL

Qverse said:
I have been using android commander since his 1st beta on all my android rooted phone..
It is the best android tool Out there.
Im usually private about the tools I use but
Android Commander (By PanPiotr) is the best and easiest adb GUI tools out there.
Features
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- update
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more…
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off phone
- screenshots (beta)
Click to expand...
Click to collapse
I'd say it's ok at best. I don't know of any other ADB GUI tools but this one doesn't work well with my Vibrant.

StrayPanda said:
I'd say it's ok at best. I don't know of any other ADB GUI tools but this one doesn't work well with my Vibrant.
Click to expand...
Click to collapse
I'm going to have to agree with this. Is nice to have but doesn't play nice with the vibrant.
Sent from my SGH-T959 using XDA App

It sometimes is very slow in reading internal sd memory on samsung vibrant and it loads up as a blank screen. Disconnecting usb cable and refreshing does the trick for me.
Sent from my SGH-T959 using XDA App

[GUIDE]Install Android SDK and upgrade Marketplace to 2.2.6

FIRST OF ALL, I CAN NOT BE HELD RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR DEVICE! PROCEED AT YOUR OWN RISK!!!​
Now that we got that out of the way...
I have noticed that some people`s Marketplaces simply refuse to update by themselves (exactly what happened in my case) and as most of the people visiting this forums are not tech-savvy and simply want a step-by-step guide to get things working, I decided no harm can be done by me posting this info.
Installing Android SDK revision 8
First of all, you will need to have Android SDK (and ADB of course) installed with the drivers ready to go. In order to get the SDK installed go to the official Android website and download the latest revision (r08 at the time I posted this). You can download any of those files, but I prefer using the executable installer so I can make sure everything is at its place. Now, there are two major flaws with this whole process which have almost made me quit the whole process several times, but I got them sorted out and will help you solve them aswell.
FLAW #1: After beginning the installation process, the installer will prompt you to download a JDK (Java Developer Kit) in order to continue installation. Hit the "Visit sun.java.com" button and download the latest Java SE (currently this one). But before proceeding be sure to download the 32 bit one, as the Android SDK only recognises this version. I know it`s not a big deal, but I spent about two hours trying to figure out what the heck went wrong and it became quite frustrating.
Install the JDK, then the SDK. Once Android SDK is done, simply go ahead and launch SDK Manager (you can find it in Program Files\Android\android-sdk-windows\) and when you get to choose the packages to install, simply check "Accept All" and click "Install". Once it`s done, it`s time to download the drivers. Click "Available packages", tick "Third party Add-ons" and under "Google Inc. add-ons" you should find "Google Usb Driver package". Tick it and click "Install". IF YOU GET AN ERROR SAYING THAT PERMISSION WAS DENIED AND YOU ARE UNDER WINDOWS 7, COPY THE WHOLE "Android" FOLDER CONTAINING THE SDK TO YOUR DESKTOP (OR ANY OTHER PLACE) AND REPEAT THE STEPS ABOVE. I know it`s quite rudimentary, but it does its job. Once it`s done, a folder named "google-usb_driver" will be created under Android. Be sure to correctly copy it to the original location in case you had permission issues.
FLAW #2: Ever since Android SDK r08, Google decided to remove the ADB files so now they have to be manually placed in the folder. I have uploaded them for you, so click here to download them. Once downloaded, extract the archive to the "Android\android-sdk-windows\tools" folder.
OPTIONAL: Go to Start Menu, right click on Computer, click Properties. The System window will appear, where you need to go to "Advanced system settings". Once there, click on "Environment variables" and where it says "System variables", look for PATH. Once found, highlight it and click "Edit..." then add the line "C:\Program Files\Android\android-sdk-windows\tools;" at the end. Click "Ok", "Ok" and "Ok", then restart your computer.
Right now everything should be working as expected. Connect your HD2 to the PC via USB and hope for the best. If the drivers are working and it is recognized as a HTC device, open a command prompt and type "adb devices". If you get anything such as "List of devices attached" followed by some code such as "0123456789ABCDEF device", everything is working well. Good job, you just correctly and completely installed Android SDK on your PC!
If not...
Check your device manager and if you see any devices related to your HD2 having problems, simply right click on them and update the drivers with the ones downloaded earlier in the "google-usb_driver" folder then reboot your computer.
We`re all set! ...What now?
The whole process is actually quite simple. First of all, download the new 2.2.6 Marketplace and put it somewhere accessible, such as your desktop. Open a command prompt and enter the following:
Code:
adb remount
adb shell
rm /system/app/Vending.apk
This will basically delete the old Marketplace from your device.
Now go to the folder where you placed the new Marketplace, hold down Shift, right-click and select "Open command window here". A command prompt should pop up at the exact location. Now execute the following command:
Code:
adb push Vending.apk /system/app
And that is it! Now restart your device and try to run your Marketplace, it will load for half a minute or so then it will start normally. Enjoy!
I know this is rather a tutorial for installing the SDK, but I figured it would be useful to let everyone know how I managed to solve my problem. In case I skipped any steps or you notice anything wrong/wish to add anything, please feel free to do so!
If you feel my post has helped you in any way, do not hesitate to hit the "Thank" button!

Reserved post for further mini-tutorials.

At least on my r08 install if you install the platform tools component then adb will be available under the platform-tools directory (moved from the tools directory).

@OP
Did you test this on a non sense build?

This procedure will most likely not work with Cyanogenmod ROMs. That and I'd suggest you give the newest market version (2.2.7) instead. I'm not willing to destroy my ROM again by trying it on CM.

Could anyone Help?

Hi,
I am currently trying to get into Android Developing and I am following a tutorial book called "Practical Android Projects" however, I have only got so far and I am coming across a problem.
I have installed the Android SDK and required files, and installed ant as per instructions here: http://ant.apache.org/manual/install.html (Under Windows and OS/2 section)
I am getting an error about my /res folder not existing, when it infact does exist, in the directory it specifies?
Please see screenshot at the following link: http://server3.uploadit.org/files/StuMcBill-cmdprompt.jpg
Thanks for any help you can give?
I am running Windows 7 Home Premium x64!
Stewart

I would suggest using eclipse. Especially for beginners it is alot easier than building everything on console.
It has nice plugins and the android emulator from the sdk is integrated.

100% agree with Dark3n.
Ant is a programming language in and of itself. (Well sort of a scripting language but whatever).
No need to try and learn two things at once. I'd suggest wait until your 2nd or 3rd app at least to learn Ant. You really don't need it unless you want to use something like ProGuard. (Which is yet another thing to learn and another thing I'd suggest waiting on).

Oh an for a possible quick fix type
>ant clean
And see if that helps.
EDIT:
Err nevermind -- looked at your screenshot... why are you running ant from the System32 directory? Is your Android project really in that folder?
Usually you set the path environment variable in your system properties in windows to add ant to the list of paths, so you can run ant from any folder.
Then you can open that folder, type cmd in the address bar and open a command prompt in your project directory. You then run ant from there which reads the build.xml file an default.properties and local.properties files in your android project folder.

OK, I will give eclipse a try.
RE system32 and ant: Well the book I am following said to use ant, and I just followed the instructions and it installed the project in System32.
Could I just substitute Eclipse for ant while following the guide?
I do have Ubuntu installed on this computer, would that be better / easier?

Eclipse is available for any OS.
Use the one you are most comftable with.
I think eclipse might even use ANT internally but you don't have to hassle with it.
Working in system32 is not adviseable, you should generally keep out of there .

KFU help requested, first try at rooting anything

Previous "first try" threads are pretty old, I'm concerned that information is outdated.
First, I wouldn't have done it, but the Fire just cries out to be uncrippled. It is 6.3. I am pretty new to this. I stopped tearing into stuff about 11 years ago, I was OK with it then but I stopped caring about it and haven't paid attention since. But I know one thing, and that is how to ask for help.
I downloaded the SDK Manager and ran the installer, installing SDK Tools and SDK Platform-Tools, then tried to install the drivers from the Kindle Fire Utility; it is the most recent version, 9.5 I believe (from yesterday).
I got:
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
twrp.img is missing.
So we will download it for you!
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Download successful.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
The system cannot find the path specified.
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Recovery Bootmode.
Please wait...
...And that's it, about half an hour ago. I know one thing, that when "NOT" is capitalized, you "don't touch the big, beautiful, shiny red button."
How long do I wait? What is going on, and if something is wrong, what do I do next?
Thanks for looking.
edited to add: I tried running install_drivers.bat; "UNC paths are not supported... Defaulting to Windows directory. The system cannot find the path specified."

Did you extract the contents of the Kindle Fire Utility zip archive before running anything?
Did you install the drivers?
Did you read this guide?
http://forum.xda-developers.com/showthread.php?t=1552547

kinfauns said:
Did you extract the contents of the Kindle Fire Utility zip archive before running anything?
Did you install the drivers?
Did you read this guide?
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thank you, yes I did. I read the guide several times. I did extract the contents first, before running anything.
I did manage to install the drivers manually, in between writing the first post and your response, by going through Device Manager and pointing it toward the Kindle Fire Utility folder.
I am confident that I won't permanently destroy anything, but at the same time I feel blind.

M0sca said:
Thank you, yes I did. I read the guide several times. I did extract the contents first, before running anything.
I did manage to install the drivers manually, in between writing the first post and your response, by going through Device Manager and pointing it toward the Kindle Fire Utility folder.
I am confident that I won't permanently destroy anything, but at the same time I feel blind.
Click to expand...
Click to collapse
All of those "The system cannot find the path specified." errors are because it can't find the directories within the KFU folder. Did you move the run.bat file or something? Within the KFU directory, you should have...
drivers
files
tools
install_drivers.bat
run.bat
Like the first 5 errors after "Activating Fastboot (4002)" it's looking for the tools directory. Most of the time this is caused by users who try to run the batch file from within the zip archive.
EDIT: I'm not a Windows guru by any means, but I was just looking at some docs about UNC paths. Do you have the KFU directory on some shared directory or mapped network drive or something? Try moving it to some place local like your user directory and run it from there.

kinfauns, I thank you for your patience.
Is it possible that the fact that I am running Windows in a vm on a Mac is part of the problem, that I downloaded Kindle Fire Utility (for Windows) in the Mac environment, then tried running it in the Windows environment?
I finally said screw it, and unplugged the Kindle. It is fine. I have to go to bed now, I will try doing it all from Windows (including the download) tomorrow.
Thank you again for your patience. I'm sorry that I ran out of time in the middle of requesting your assistance, that is rude and implies that I don't value the help. On the contrary, I value it very much. But the hours in between now and tomorrow morning mean nothing to the machines, and everything to my biological recharging. I apologize.

M0sca said:
kinfauns, I thank you for your patience.
Is it possible that the fact that I am running Windows in a vm on a Mac is part of the problem, that I downloaded Kindle Fire Utility (for Windows) in the Mac environment, then tried running it in the Windows environment?
I finally said screw it, and unplugged the Kindle. It is fine. I have to go to bed now, I will try doing it all from Windows (including the download) tomorrow.
Thank you again for your patience. I'm sorry that I ran out of time in the middle of requesting your assistance, that is rude and implies that I don't value the help. On the contrary, I value it very much. But the hours in between now and tomorrow morning mean nothing to the machines, and everything to my biological recharging. I apologize.
Click to expand...
Click to collapse
No, that's fine... no apologies necessary. It's good to step away from the situation for a while and regroup when things don't seem to go right. In the interest of full disclosure, Mac OS X Lion is my primary OS. All of this Windows stuff I do through Parallels Desktop VM and I don't have any problems with it. I don't know what you are using, but I'll warn you now that if you are trying to use Oracle's VirtualBox, it's not going to do the job for you. There seems to be some bug in their USB implementation that breaks adb and fastboot.
My guess right now is that you are trying to run KFU from a shared directory that resides on your Mac. If you look at post #2 of the guide I mentioned previously, I suggest putting everything in C:\kfu before running things. It doesn't necessarily have to be that directory, but you should trying putting it somewhere on the boot drive. The 2 minutes I spent looking at UNC paths seems to indicate cmd.exe doesn't like them and that might be the cause of your troubles. Good luck.

kinfauns, I followed the instructions better this time, downloading KFU in the Windows environment and extracting directly to C:, and everything proceeded perfectly. Thank you!