Hello again folks
I'm really struggling with this program,
I am following the tutorial and I'm not sure if my path is correct, (I don't really understand it TBH) Below is my actual path.
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Calibre2\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\KFFirstAide;
I have followed the guide and added in the ;C:\KFFirstAide; to the end of my path, the KFFirstAide directory is C:\KFFirstAide
in a cmd prompt when i type
CD C:\Windows\
then adb kill-server
then adb wait-for-device at this point the cmd prompt doesn't seem to do anything other than display "daemon not running. starting it now on port 5037" then "daemon started successfully" after this line i get a blinking curser however i cannot type anything?
doing my head in now, i truely am out of my depth lol
fordy0508 said:
Hello again folks
I'm really struggling with this program,
I am following the tutorial and I'm not sure if my path is correct, (I don't really understand it TBH) Below is my actual path.
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Calibre2\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\KFFirstAide;
I have followed the guide and added in the ;C:\KFFirstAide; to the end of my path, the KFFirstAide directory is C:\KFFirstAide
in a cmd prompt when i type
CD C:\Windows\
then adb kill-server
then adb wait-for-device at this point the cmd prompt doesn't seem to do anything other than display "daemon not running. starting it now on port 5037" then "daemon started successfully" after this line i get a blinking curser however i cannot type anything?
doing my head in now, i truely am out of my depth lol
Click to expand...
Click to collapse
it is supposed to do that more or less, it does that until a adb device is plugged in and detected, if yours is plugged in and usb debugging is enabled and it still is doing that then go into the device manager, look for a device with a yellow triangle,once you find it download the drivers in my signature, extract them somewhere. Now right click the device with a yellow triangle and hit update drivers, point it to where you extracted mine. Once it is done installing them try running the command again, if it completes successfully it should be back at a command prompt.
I checked that and there was 1 think with a yellow triangle but it wasn't the kindle ?
Sent from my HTC One using Tapatalk
What is it called?
Sent from my Amazon Kindle Fire HD using Tapatalk
Sorry about the late reply, the yellow triangle is on avast! Firewall NDIS filter mini port
Sent from my HTC One using Tapatalk
fordy0508 said:
Sorry about the late reply, the yellow triangle is on avast! Firewall NDIS filter mini port
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yea thats not it... Weird, also sorry for late reply myself, i viewed your reply on my pc and went off to do somethign and came back and did something else, then when i checked for new posts on forum your thread wasnt highlighted anymore. Ok so does the device show up as a portable/mtp device that you can view the sdcards contents?
Not sure I'll check tonight
Sent from my HTC One using Tapatalk
Related
Somebody please help me out of my misery. I followed the rooting directions to the letter, but when I type "adb devices" I get the following error:
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I'm in the right directory ( AndroidSDK\tools\ ), I have the android driver installed, I have USB debugging checked, I don't understand why this is not working.
Please help me out here.
I had no problem rooting my palm pre, which was infinately more complicated than this.
Thank you in advance.
flaav8r said:
Somebody please help me out of my misery. I followed the rooting directions to the letter, but when I type "adb devices" I get the following error:
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I'm in the right directory ( AndroidSDK\tools\ ), I have the android driver installed, I have USB debugging checked, I don't understand why this is not working.
Please help me out here.
I had no problem rooting my palm pre, which was infinately more complicated than this.
Thank you in advance.
Click to expand...
Click to collapse
had a pre and "rooted" it as well..... using putty is more complicated that this but this is a little more like hacking... whereas on the pre you are just accessing root rather than breaking into it.
anyway... try these
nstall htc sync from htc's website, can you sync?
run cmd as administrator
cd untill you are in the same directory as your adb
type "adb devices"
does it display your hero?
type "adb shell"
does is display "$" ?
johnsongrantr said:
had a pre and "rooted" it as well..... using putty is more complicated that this but this is a little more like hacking... whereas on the pre you are just accessing root rather than breaking into it.
anyway... try these
nstall htc sync from htc's website, can you sync?
run cmd as administrator
cd untill you are in the same directory as your adb
type "adb devices"
does it display your hero?
type "adb shell"
does is display "$" ?
Click to expand...
Click to collapse
Yes, I can sync with HTC Sync. When I do the adb devices I get the error I described above and I cannot do adb shell because I cannot communicate via android sdk.
flaav8r said:
Yes, I can sync with HTC Sync. When I do the adb devices I get the error I described above and I cannot do adb shell because I cannot communicate via android sdk.
Click to expand...
Click to collapse
windows 7? VISTA? XP?
restart phone/computer
unplug/plugin usb
also find another copy of adb.exe i heard there's a old copy floating out there that doesn't reccognize the hero for some reason but if you got it from a guide you shouldn't have a problem.
download sprint RUU and wipe your phone (if it will connect) also if you want to dig down the ruu has a working adb.exe twisted into their install they dump in your %TEMP% folder
johnsongrantr said:
windows 7? VISTA? XP?
restart phone/computer
unplug/plugin usb
also find another copy of adb.exe i heard there's a old copy floating out there that doesn't reccognize the hero for some reason but if you got it from a guide you shouldn't have a problem.
download sprint RUU and wipe your phone (if it will connect) also if you want to dig down the ruu has a working adb.exe twisted into their install they dump in your %TEMP% folder
Click to expand...
Click to collapse
Windows XP, and I got the files from this site and androidsdk from the google site linked from theunlockr.com.
flaav8r said:
Windows XP, and I got the files from this site and androidsdk from the google site linked from theunlockr.com.
Click to expand...
Click to collapse
try this known good version
http://forum.xda-developers.com/attachment.php?attachmentid=244916&stc=1&d=1257827184
johnsongrantr said:
try this known good version
http://forum.xda-developers.com/attachment.php?attachmentid=244916&stc=1&d=1257827184
Click to expand...
Click to collapse
I tried the new files, and still got the exact same error.
well i'm out of ideas.... and i'm tired.... anyone else throw a little help this guy's way?
if by tomorrow you/they haven't figured it out I'll see if I can't think of something else for ya
johnsongrantr said:
well i'm out of ideas.... and i'm tired.... anyone else throw a little help this guy's way?
if by tomorrow you/they haven't figured it out I'll see if I can't think of something else for ya
Click to expand...
Click to collapse
Thank you for your help. Greatly appreciated.
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
I'm gonna give it a shot right now.
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
Haha, success. I'm gonna try and root it now.
Thank you so much.
flaav8r said:
Haha, success. I'm gonna try and root it now.
Thank you so much.
Click to expand...
Click to collapse
Np glad to help
simplyphp said:
Np glad to help
Click to expand...
Click to collapse
Sucussfully rooted, thanks again.
Sorry for reviving an ancient post, but I just wanted to say that I ran into the same issue and opening up "taskmgr" and killing the active instance of "adb.exe" resolved the issue.
Just for help :
I had the same issue and it was my Firewall which blocked the starting of deamon.
Turn off your Firewall can fix the problem
cheers guys, followed the instructions and flashed rec. radio
This solved it for me: edit adb_usb.ini
This solved it for me:
Edit ~/.android/adb_usb.ini file to make sure that there is no extra empty line after the 0x0006 line entry
For other users: I also found this:
After killing ADB.exe run netstat (just "netstat", no parameters) and
see if port 5037 is opened. It probably will be. Wait a while. Run
netstat again, now there are less connections on the port. After a
port 5037 is no longer opened. Only then it's OK to run ADB again.
Please note that this worked for when I killed the ADB.exe process &
process tree from Sysintenal's Process Explorer.
Also, I still don't know why running ADB again before all connection
are closed led to the port never being freed (albeit netstat didn't
show any open connections anymore). Moreover, the problem that forced
me to kill ADB in the first place needs to be solved and there's
enough on that in the forum.
AsafR.
Click to expand...
Click to collapse
Problem is HTC Sync
lucbloom said:
This solved it for me:
Edit ~/.android/adb_usb.ini file to make sure that there is no extra empty line after the 0x0006 line entry
For other users: I also found this:
Click to expand...
Click to collapse
HTC Sync Manager has adb.exe at location C:\Program Files\htc\htc sync manager\htc sync\adb.exe
You have 2 options now:-
1) Delete this adb.exe
2) Copy latest adb.exe from android sdk to this path.
Note: You need to make the 2 copies of adb.exe in sync always(when android sdk is updated) else this problem will come up again.
On windows 7, you can make a link of adb.exe from android sdk to this folder, which will avoid copying manually.
C:\> cd "C:\Program Files\htc\htc sync manager\htc sync"
C:\Program Files\htc\htc sync manager\htc sync\> mklink adb.exe C:\<path to your sdk>\platform-tools\adb.exe
kill htc sync
nevermind someone already posted
I Followed all the instructions to the T on how to install adb.
When I get to the point where I plug in my phone,....and DONT MOUNT...
it shows up on my computer like its gonna install the adb but then asks me to locate the driver.
I am very confused on what to do from here. Can someone help me please?
I'm assuming you're on a Windows machine. As such, you need to install the windows drivers.
http://stuff.foamcoffee.com/misc/adb/win/android_usb_windows.zip
Those are XP only.
oK i AM ASSUMING I GOT THE DRIVERS INSTALLED, BUT WHEN I TYPE ADB DEVICES INTO MY COMMPAND PROMT. IT SHOWS THIS...
Code:
C:\Documents and Settings\HP_Administrator>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
C:\android-sdk-windows\tools>
There is no deviec being read?
Now what.
spazoid said:
oK i AM ASSUMING I GOT THE DRIVERS INSTALLED, BUT WHEN I TYPE ADB DEVICES INTO MY COMMPAND PROMT. IT SHOWS THIS...
Code:
C:\Documents and Settings\HP_Administrator>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
C:\android-sdk-windows\tools>
There is no deviec being read?
Now what.
Click to expand...
Click to collapse
because you don't have your drivers installed
Um...yes I do...I made sure three times.. I may be a noob at this, but im def not a noob when it comes to a pc
HAHA if you don't have the HTC driver installed it will not read the device. Uninstall the default usb driver in device manager under adb interface, then make sure windows doesn't reintall it and use the one in the file posted above.
I can only assume it is the correct driver that he linked. What OS do you have running x86 or x64?
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
oceanisbleu said:
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
Click to expand...
Click to collapse
Double check your path...
"Now type cd\AndroidSDK\tools\"
My path is c:\android-sdk-windows\tools\
I've renamed the file to AndroidSDK & placed it directly in C:/ so for me it's C:/ AndroidSDK/tools/
doesn't work...
-I plug the phone in and it's recognized as "Android ADB Interface" in device manager
-I open easy tether on the phone then right click on the pc & click connect then it says connection established via Android ADB.....
-I open CMD
-I type cd\
-then cd\AndroidSDK\tools\
-then adb devices & this is where I want to break everything because I can never get past this part and all I see is 'adb' is not recognized as an internal or external command.......
I hate this phone lol & wish I had the money to get the evo so I can put this thing in the trash, I just want to setup firerat's and that's the main reason why I want to establish ADB, is there any way it can be done without ADB????
thanks for trying to help, I hope someone can still figure this out for me
If you downloaded the newest SDK, then the problem might be that you are looking for adb in the wrong directory. It is no longer located in \tools. It was moved to the \platform-tools directory
Sent from my HERO CDMA using xda premium
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
dastin1015 said:
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
I have just added this exact directory to the end of my PATH
;C:\AndroidSDK\platform-tools\
rebooted, opened cmd, typed adb devices and still I get ADB is not a recognized command.
I went to HTC's site & downloaded the latest hero sync software (new version just came out 2 days ago) when I plugged my phone in it re-installed the drivers, tried it again and nothing!!
I did notice that after the HTC Sync installation in device manager the phone is no longer Android ADB Device, now it says MY HTC, did Sync ruin my ADB drivers?
Ok. So were you at with this???
Shoot me a pm if you still need assistance.
Edit: From reading your post I think your not changing the directory first.
So open up the cmd window. And type cd\ "then hit enter"
Thenn type.
cd\AndroidSDK\platform-tools\
And hit enter.
Then type. "adb devices" without the quotes. And see if that will show your serial number.
If that yeilds no results then try
cd\android\SDK\tools\
And hit enter.
Then type "adb devices" without the quotes. And hit enter and see if that will return your serial number.
Locked & Loaded
" Shooter on Deck"
Thanks guys for all the help you have provided, I have finally figured it out using this guide;
http://forum.xda-developers.com/showthread.php?t=532719
slightly different than the first guide I followed, instead of editing the PATH a new Environment Variable was created also a slightly different CMD code to get to ADB;
cd C:\android-sdk-windows\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
I hope this helps anyone else who might have the same issue.
When i open ADB all it does is it has a lot of white writing that scrolls along and then closes, does anyone know if i set it up wrong, or if they could post step by step instructions? it would be much appreciated, Thanks.
what operating system are you using
smoshism said:
what operating system are you using
Click to expand...
Click to collapse
I am using windows 7
um, is there a way to remount adb? im on ubuntu so i cant help out a whole lot. but maybe i can bounce some ideas that could work
smoshism said:
um, is there a way to remount adb? im on ubuntu so i cant help out a whole lot. but maybe i can bounce some ideas that could work
Click to expand...
Click to collapse
im not sure, im not very familiar with ADB
I'm pretty new to this, but seems to me you are trying to open the adb that psouza includes with his tools. (If not, then just ignore me)
that's not gonna work for what you are trying to do. i think you need to download the android sdk to get adb working.
SrulDog said:
I'm pretty new to this, but seems to me you are trying to open the adb that psouza includes with his tools. (If not, then just ignore me)
that's not gonna work for what you are trying to do. i think you need to download the android sdk to get adb working.
Click to expand...
Click to collapse
i am using the one in the SDK, i have it on my c drive in the correct spot but it still closes itslef
Are you clicking it like an icon or running it from a DOS prompt? It is to be run from the command line as it is a dos/command line program..
Ie.. at the c:\android-sdk-x86\platform_tools\ prompt you type adb and what you want to do.
Adb push or adb pull or adb shell, etc. Just adb will give some command options
Sent from my Xoom
d7benjamin said:
When i open ADB all it does is it has a lot of white writing that scrolls along and then closes, does anyone know if i set it up wrong, or if they could post step by step instructions? it would be much appreciated, Thanks.
Click to expand...
Click to collapse
First you have to open an elevated command prompt. Do this by clicking the start icon, then typing in "cmd" (without the quotes of course) and then right clicking the only thing that pops up and choosing Run As Administrator. After doing this, you need to know where you folder that contains ADB is at. To find this easily, click Start and then click Computer and in the explorer window that just popped up, type in "adb.exe". That will show you where your adb files are at.
Continuing on, for an example, my adb stuff is in C:\root stuffz. So in the command prompt I would type in "cd c:\root stuffz" and then hit enter. After that, I can then do my adb commands, such as "adb shell", "adb push", "adb pull", etc...
Edit: Make sure you have your drivers installed for the phone. Also, make sure the phone is in debug mode and charge only. This should just about cover most of the absolute basics of getting your phone recognized by adb. I'm not too sure if I missed anything, and one of the other more experienced peeps on here can prob give you more detailed information lol.
Hello all.
Was tinkering around with my KF- And accidentally wiped everything from my internal storage and system. When it boots up I get the blue KF logo and it stays stuck there- Can't boot into recovery.
ADB doesnt recognize it.
Have a fastboot cable.
How do I atleast push files to it /boot into recovery??
Many thanks.
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
SilverRoxas said:
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
Click to expand...
Click to collapse
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
LinearEquation said:
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
Click to expand...
Click to collapse
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
SilverRoxas said:
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
Click to expand...
Click to collapse
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
LinearEquation said:
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
Click to expand...
Click to collapse
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
SilverRoxas said:
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
Click to expand...
Click to collapse
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
LinearEquation said:
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
Click to expand...
Click to collapse
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
SilverRoxas said:
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
Click to expand...
Click to collapse
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
SilverRoxas said:
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
Click to expand...
Click to collapse
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, my Kindle is still recognized.
i dont os on my kindle fire hd 7
I am having a mare with my kindle fire hd 7
It all starrted when anything google related kept crashing.
I tried to find solutions to the problem but no joy.
I then tried to install a different update to cyanogenmod nightly software but i then had a major problem with not being able to turn on my wifi.
I went into Twrp and tried to restore to my previous software but when my kindle re-booted i got stuck with a flashing teamwin logo
After trawling for days i managed to get out of that but im now in a situation where i dont have any OS on my kindle.
I have followed instructions on how to push files onto my kindle but despiote finding some files on my sdcard i am unable to reboot past the blue and white Kindlefire logo.
I have tried using the kindle un-brick java option but no joy either
I would really appreciate some help solving this proble as it is really driving me crazy.
I can still access twrp and i can access bootloader to get the orange and white fastboot logo.
If someone can help guide me through how i can get my kindle working again id really appreciate it
cheers
JJ
Might be able to help.
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Hey Danny101
Danny101 said:
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Click to expand...
Click to collapse
Thanx for your response.
Sorry its taken me a while to reply but have had loads going one recently.
Shortly after making my post i did find that exact same youtube vid tutorial and was able to solve my problem.
I just wanted to say thanx for taking time to respond even so.
All the best.
JJ