It might seem a bit stupid, but maybe others will encounter one of this issues and it will help them. your more than welcome at add to this.
P: computer wont recognize device in debug mode. instead it recognizes "android 1.0" or something else.
S: download HTC sync. it contains the proper drivers.
P: while activating the *.bat file you get the erroe "adb out of date...killing". the script will run all the way, but root access wont be given.
s: you need to close all adb processes from task manager, and the htcsync process as well (on PC)! also, you need to reflash the img file, and try rooting again.
HTC SYNC
after 10 attempts at ROOT, I found this tread. It is CRITICAL that you stop the HTCSync process on you PC or root will not work!
HTC Sync on the tab or on the pc? I killed it on the tab through the running applications. To kill adb processes just close the command window on the pc.
you need to kill it on the PC.
Ok so noob question of the day!
Where are you supposed to input the commands (such as adb reboot bootloader) to start the kernel flash process? I tried in cmd as well as terminal emulator on the tablet with no luck, what am I missing here?
NJFM said:
Ok so noob question of the day!
Where are you supposed to input the commands (such as adb reboot bootloader) to start the kernel flash process? I tried in cmd as well as terminal emulator on the tablet with no luck, what am I missing here?
Click to expand...
Click to collapse
you should have ADB in your c:\android folder, or wherever your sdk is installed.
Do a search for adb with your pc to find out where you installed it.
then using the command prompt under start> programs> accessories> command prompt, go to the corrected directory that ADB is in.
to go to C:\android, for example, type " cd c:\android "
Then you would execute the adb commands, (example: adb reboot bootloader)
Go to youtube and search for a 'how to use ADB' tutorial.
I'm having difficulty hotbooting the insecure kernel.
I've uninstalled HTC Sync on my PC, and I've downloaded the insecure kernel to my SD card's root directory.
I have no problem rebooting the bootloader via adb, and my device is detected. However, when I try to hotboot the kernel, I routinely get a "cannot load" response. I'm typing in "fastboot boot [filename].img."
Suggestions?
Many thanks.
the insecure kernel shouldn't go to the SD card. only the wifi module should.
the *.img file should go to the adb\tools directory,
(maybe you can put it anywhere else and just write the full path while flashing, i'm not sure. i just copy this files to the tools directory and flash them from there. easiest way)
the flash command flashes the file from the directory on the computer to the device.
Thanks very much!
I'm sitting here laughing to myself because I'd tried changing the path in the command to a couple of places I'd placed the insecure kernel in my PC; the c: root directory and a directory I'd created to house downloaded Jetstream files. Obviously, neither worked.
Placing it in the adb\tools directory makes complete sense.
By the way, your mention of the "wifi module" sent me back to DooMLoRD's kernel thread. I see that you flashed the kernel and related wifi module on 1/4. Like others who posted, are you pleased with the kernel?
Thanks, again!
The kernel seems very nice and almost no one complaind.
Sent from my GT-I9000 using XDA App
Related
THIS IS STRICTLY A GUIDE TO PRE-PARE YOU ON HOW TO SET-UP ANDROID SDK AND ADB DEVICES(DRIVERS), IF YOU ALREADY HAVE THAT SET-UP YOU CAN SKIP TO EUGENE'S POST ON HOW TO ROOT MYTOUCH SLIDE.
Last Updated:6/29/2010 at 11:36PM
Any other issues to deal with the actual process to root your mytouch slide should be directed toward his thread. Thank you for reading.
Okay so after about 4 hours of reading and asking questions I finally got my device rooted. My biggest problem doing this was that the guide in this forum was basically showing you how to root the phone if you had previous experience with androids and android SDK which I did not.
Note: If you have SDK installed already on your pc please delete your SDK folder and start from scratch for best results with my guide.
1. download Android SDK.(You will not have to use Android SDK physically but you will need it installed on your pc to root your phone) Save it to your PC where you can find it.
2.Extact the .zip file, do not rename just yet for the sake of my guide you also may delete the .zip file of it to keep clean.
3a. Move android-sdk-windows* out of the android-sdk_r06-windows folder onto the root of your C:/ drive.
*=the name of the folder may be different if you use a different operating system but since I do not own the other systems I cannot really tell you what the folders name.
3b.Now that you have the folder in the correct place you can rename the folder from "SDK-Anroid-Windows" to something easier such as "SDK" "Android" or something else which you will remember has to do with SDK.
This next part is not required, if you do not feel comfortable doing this, then don't, there is other ways around this.
3c.You also have the option to change your the path of your directory on your system. To do this, follow the instrustion here on step 2.( I would like to thank fermunky for his input)
My directory was pointed to the C:/Program files so I switched it to C:/android/tools , for those who do not know what this does it simply makes it so you do not have to change directory in step 7 (CD), you will only have to open your command prompt and then your ready to enter "ADB devices" .
4.Install the correct ADB drivers from pdanet . Select the proper download based on your OS if you do not know what bit you are using click start, right click computer, click properties, the system type will show you the proper file to download. and save it to your computer where you can find it.
5.Start the installation process for the ABD drivers, Follow the on-screen directions to install the drivers ( make sure your phone is not plugged into the pc at this time)
6.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools**
**=your file directory might be different than this, it depends what you renamed your folder
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.***
***=If it is correctly connected you will see a device listed and under attached it should say device.
After you have this all set up you are ready to root your phone via the guide from Eugene.****Remember you need to add the contents from his root.zip file into the tools of your SDK folder in order to root your phone.
****=Eugene's guide has changed since I wrote this but you still are ready to follow his steps. I plan on rooting someones slide soon based off his steps and will edit here if I need to add anything)
Thanks for reading.
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
the other guide mentions to create a new variable such as:
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Click to expand...
Click to collapse
so would i follow this? or list that directory under the already-enabled PATH variable?
Yeah just use the existing PATH variable, and only need the path, no need to include variable names.
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
For the uninitiated, and yes it's common sense
When I was using Windows (as I'm using Ubuntu now), and reading all the adb guides, for ease of use and to prevent people from getting confused, they name the sdk as "android-sdk-windows", which is fine for a newcomer (it's the same for Ubuntu except the "windows" part and the slash direction \ vs. /). However, you can name it whatever you want. You just need to make sure to have the same name in your path. For example, I'm lazy and my typing skills aren't that great. I don't want to type 19 characters (yes, I counted). So I just named it simply "android". 7 characters from 19. Its way more efficient for me. I've contemplated naming it "andy" or something to shorten it further. But, again, you don't even need to name it anything android related. You can choose to name it r2d2 (see what I did there?) if you want! Just my 2 cents. Thanks!
Yeah I could of renamed it something different but I didn't think about that til after it was written, I will fix it as soon as I am on an actual pc. I will also include how to do it via mac and ubuanta(sorry if I miss spelled)
kingofyo1 said:
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
Click to expand...
Click to collapse
Thanks kingofyo. Glad I could give back to this forum after all it has done for me. And if I find any other helpful tips to help make rooting easier I'll be sure to include it.
Sent from my T-Mobile myTouch 3G Slide using XDA App
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
I will leave that as an option for others to pick if they want to do that, as some might not want to change their directory to follow that path.
oo, this cleared up a few things for me! thanks!
eff0rtless said:
oo, this cleared up a few things for me! thanks!
Click to expand...
Click to collapse
ah what pat of seattle do you live in? I live up in mukilteo.
rlacsamana1989 said:
7.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools (your file directory might be different than this, it depends what you renamed your folder)
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.
Click to expand...
Click to collapse
when typing in 'adb devices', i get this message:
Code:
adb server is out of date. killing...
* daemon started successfully *
however, it does continue to list my device as attached.
the full message is:
Code:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HTxxxxxxxx device
*the x's do represent a valid serial number
-------------------------------------------------------
is this a problem? and will i run into any problems trying to successfully root?
note: i have done a search on this and the results returned as the program DroidExplorer being the culprit, however, i do not have that program installed.
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
rlacsamana1989 said:
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
poetik517 said:
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
Click to expand...
Click to collapse
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
cdt82002 said:
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay my guide is to set you up to root, you need to download slideroot.zip from eugene's how to guide. It will download a folder so you need to save it somewhere you will find it. Once you have it saved extract the files and the files within that folder you need to put in the tools of the sdk directory. Do not just drop the folder as that would change the directory even more to another folder. A file in that folder is what actually makes the loop feature work and there are other things you will need from that folder to root.
And to this. %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
you just need to delete "Program Files (x86)\QuickTime\QTSystem\"
and then replace it with your directory to your C:/
rlacsamana1989 said:
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Click to expand...
Click to collapse
a successful uninstall & reinstall of the sdk worked for me. i no longer get the 'adb server is out of date' message when trying to list devices.
when reinstalling all of the packages in sdk, i did note this message:
Code:
'Downloading Usb Driver package, revision 3
Installing Usb Driver package, revision 3
Installed Usb Driver package, revision 3
Updated ADB to support the USB devices declared in the SDK add-ons.
'adb kill-server' succeeded.
ADB: * daemon not running. starting it now *
ADB: * daemon started successfully *
'adb start-server' succeeded.
but its a good thing =]
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
poetik517 said:
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
Click to expand...
Click to collapse
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
usbdeview
rlacsamana1989 said:
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I think the program you're trying to remember may be "usbdeview"? This program allows you to disconnect or uninstall drivers.
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
I would take the time to learn ADB or wait until a one click is out. Learning ADB while rooting your phone could easily break it.
what os are you using?
svalle713 said:
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
Click to expand...
Click to collapse
Honestly just take the time to read the procedure, other help topics on these forums, and take your time when actually going through the procedure.
I had never used ADB either or rooted an android phone for that matter, and I gotta say, rooting the TBolt was cake.
I just took my time with it ensuring I typed in the commands properly.
But if you need a video, here you go: http://www.droid-life.com/2011/03/22/video-rooting-the-htc-thunderbolt/
what drivers do we need for the process, are they only the htc sync drivers? where can these be found?
Android SDK should be extracted/installed straight onto the C:\ directory to make it easy. Open the android-sdk folder and in it is a program sdkmanager.exe, open that and you can reject all of the downloads but scroll down and install one called the "google usb driver package" which may be necessary, I'm not sure (you should also have the htc sync drivers installed)
The contents from the "exploit.zip" should be extracted into the folder "platform-tools" within the android-sdk folder. Plug in your phone to the usb and open the command prompt. To get started open the command prompt (like a dos prompt) and get the prompt into the folder 'platform-tools' and type "adb devices" then hit enter. If your phone is connected and you have "usb debugging" enabled on your phone from the settings, your phone should appear and you can begin the instructions from jcase
Installed latest version of CWM..made backup of original rom...Rebooted System...No problem...Flashed CM9 per instructions...Full Wipe...Played with it for awhile...Backed it up...tried to restore Stock Rom ...went into CWM loop...Read a lot of threads and I still have drivers and Asus is seen in Device Manager with ADB Interface...So I tried Command prompts for 1a...and what I get is 'adb' is not recognized as an internal or external command,operable program or batch file...
Am I typin the command right ???...I never used ADB before...Came over from Epic Touch 4g Forum here...and I only used Odin...Could someone give me a clue if on on the right path of Unbrickin this thing...
Thanx...
BTW its Unlocked and of course rooted...
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Hobbesian said:
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Click to expand...
Click to collapse
Yep it was a Nandroid Backup...Im not at all familiar with ADB ...Just Odin which I use Rooting Phones...Ill give it a try...This is drivin me nuts...Just cant get ADB to work for me thru commands...Ill definitely do what you suggest...Thanx a lot Ill let ya know what happens...
Still gettin this when I run a command prompt
adb is not recognized as an internal or external command,operable program or batch file..Says the same for fastboot...Am I typin the commands right...
Installed driver and extracted the files from the download to my c part of the drive...Do I have to open anything in the download folder inorder for it to work or just extract everything like I did...
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Help
ronny71 said:
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Click to expand...
Click to collapse
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
chrsbrrss said:
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
Click to expand...
Click to collapse
Extract it if you haven't already.... put your prime into recovery .... plug it into the pc... in device manager find the prime and update the driver manually... point windows to the driver and your there...
For adb... you need to download that too I use the one in the nvfashpack... so... you extract the file.. with the window open... press and hold shift then right click in the window (nvflashpack folder, where the adb.exe file is) and select open command prompt here. Now you can use the adb commands... if your trying to push a file...it is best to put it in the same folder (nvflashpack)
Hi guys,
EDIT: See the last posts - I have figured this out, and tried to include helpful information, if you are having this problem too.
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
urbainmenace said:
Hi guys,
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
Click to expand...
Click to collapse
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
goodayoo said:
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
Click to expand...
Click to collapse
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
urbainmenace said:
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
Click to expand...
Click to collapse
OK，I think I'm gonna get one and give it a try. the only way to fix this brick is in the ADB Interface I'm sure. though I also don't know How to do.
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
urbainmenace said:
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
Click to expand...
Click to collapse
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
goodayoo said:
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
Click to expand...
Click to collapse
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
bootlooped, adb runs some commands
urbainmenace said:
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
Click to expand...
Click to collapse
Working with the HDX 8.9.
I think I have deleted some of the system files also. I was reloading a safestrap backup and rebooted but the backup had failed to complete. I don't know what may be missing from the system files and would like to push the system files onto the device.
Right now I get a gray kindlefire screen for about 90 seconds, during which I have adb access, then it goes to the color kindlefire screen and asks if I want to Restore to Factory Defaults or reboot. I finally subjected it to the Restore to Factory Defaults, but that just wiped the cache and data partitions, I don't see where it did anything to the system files. It did not change my adb access.
In adb I can push files to some locations but others say: failed to copy ....: Read-only file system.
I cannot run shell commands
# adb shell
soinfo_link_image(linker.cpp:1617): could not load library "/vendor/lib/libNimsWrap.so" needed by "/system/bin/sh"; caused by load_library(linker.cpp:745): library "/vendor/lib/libNimsWrap.so" not foundCANNOT LINK EXECUTABLE
I was working in Windows 8.1 but have switched to Suse Linux but the results are the same so far.
I have the stock system files but I am not sure how to push them to the device, if it can be done, while the device is trying to reboot.
fastboot
I can put the HDX in Fastboot mode with the adb command. But when I try to pass commands to the HDX I get:
< waiting for device >
and I have to Ctrl-c to stop the process.
Do the fastboot commands only work if you have a fastboot cable???
Since you guys are using adb checkout these threads:
http://forum.xda-developers.com/showthread.php?t=2530623 Factory Reset
http://forum.xda-developers.com/showthread.php?t=2636817 [Video Tutorial] GAPPS + Amazon from Cpasjuste
http://forum.xda-developers.com/showthread.php?t=2638241 How to un-boot-loop (another way)
http://forum.xda-developers.com/showthread.php?t=2598577 [TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"
This guy may also be able to help, forum member: GSLEON3 Post #16
http://forum.xda-developers.com/showthread.php?t=2580989&page=2
Hello all
So here I am in my first topic :laugh:
For Mac users can be tough to work with commands, which most of it has to be done in order to perform stuff in our Moto X.
Instead of having to mount virtual machines in order to have access to Windows' stuff. Or the Android SDK has to be installed, browse to specific folders to run commands from them, etc.
We can work directly in our precious Terminal! :victory:
So, I made a little script that will allow Mac users to work directly on Terminal, no matter which folder we are working on. I've included the following files:
adb
fastboot
mfastboot (Motorola's modified version of fastboot)
To Install
Run Terminal (/Applications/Utilities/Terminal.app)
Browse to the folder in which the script resides, i.e., if it’s in Desktop, then type in Terminal “cd Desktop/ADBInstall” (without quotes).
To run the script type “./install.sh” (without quotes).
You will see input on the screen.
That’s it
To Uninstall
You can safely remove the 3 files in one command, just run the uninstall.sh script by following step 1 and 2 from the Install section. Instead of following step 3, type the following in Terminal: “./unistall.sh” (without quotes).
Hope you like it
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
HeroOfTime said:
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
Click to expand...
Click to collapse
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
MoisesPerez said:
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
Click to expand...
Click to collapse
Thanks for looking into this for me. Yes, it did ask for my password. Here is what I get after running the installer:
Jareds-MBP:ADBinstall Jared$ ./install.sh
This will install ADB, Fastboot and mFastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/Jared/Desktop/ADBinstall
Copying ADB...
ADB copied to /usr/bin/adb
Copying Fastboot...
Fastboot copied to /usr/bin/fastboot
Copying mFastboot...
mFastboot copied to /usr/bin/mfastboot
You may now run Android Debug Bridge, Fastboot and mFastboot commands
Have a nice day
I'm attaching a screenshot of the output as well, but that is the output I get, which seems correct.
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
MoisesPerez said:
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
Click to expand...
Click to collapse
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
HeroOfTime said:
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
Click to expand...
Click to collapse
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
MoisesPerez said:
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
Click to expand...
Click to collapse
Well thanks a lot for your help. Still a great resource. I will keep playing around with things and maybe get it to work.
Thanks again!
Not a problem my friend. Good luck!
worked great for me on 10.9!
worked for me as well on Yosemite 10.10.1. thanks!
Glad it did! Regards.