Related
ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
dbc00per said:
ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
Click to expand...
Click to collapse
This would be better suited for Q&A that being said post the commands you are issuing and the errors you are getting. This would help someone trying to help you. Good luck
Try posting in clear concise sentences and it will help as well. Your post is like reading a teenagers tantrum and it's hard to follow.
From what I gathered, you can't get ADB to work, even though you're attempting to run it from a command prompt but the command prompt immediately closes from some unknown commands. That makes no sense.
From your computer, in windows, browse to the Android SDK folder.
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
With your phone connected via USB and debugging mode enabled type:
adb remount
and press enter.
What do you get?
First off...wrong section, this belongs in Q&A
Anyways...
1) Go to Settings -> Applications -> Development -> Enable USB debugging
2) Make sure HTC Sync is installed. Link
3) Right-click My Computer and go into Device Manager (while your phone is plugged in), if you see any yellow flags or unknown devices, remove them.
Now unplug your phone and plug it back in.
4) Place the sdk folder on your C:\ and run command prompt in Administrator mode.
Type "cd " (don't forget the trailing space), do not hit enter yet.
Now try to physically drag the tools folder into the prompt window, it will type text for you.
Hit enter.
5) Type adb and it should work.
If it doesn't work, well, you're going to need to give us more details...especially since if you follow what I wrote above correctly there is no reason it shouldn't work.
Sirchuk said:
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
Click to expand...
Click to collapse
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Neotelos_com said:
Does that work in XP?
Click to expand...
Click to collapse
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Neotelos_com said:
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Click to expand...
Click to collapse
Only works in vista and win 7
gx1400 said:
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Click to expand...
Click to collapse
Yeah like I said "workstation", I don't call any of my personal machines "workstations".
Also, I'd hope I know command line well considering I just gave advice on how to run adb through it.
thank you I've just gathered more information here than searching for days
Anywhere else.
Okay, I am getting ready to root my phone tonight...
As far as all that - I think I got all that covered.
As far as flashing a recovery - I want to use amon-ra's - RA-evo-v1.8.0 found here - http://forum.xda-developers.com/showthread.php?t=705026
In that post it gives two differant ways to flash the recovery:
via fastboot
Code:
Copy recovery-RA-evo-v1.8.0.img to a location where fastboot can find it.
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
via terminal app or adb => Make sure your rom contains flash_image!!
Code:
Copy recovery-RA-evo-v1.8.0.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
My questions are:
first of all - what is "Fastboot"?? I mean is it an application that I can download and install it this way?
second of all - what is a "terminal app"
&
third - what is "adb"?
I keep hearing the term "shell", is a "shell" the same as windows command prompt? Or is that "adb"?
I know these are probably stupid questions for most, but I like to have every thing ready to go before I tackle projects...
Any guidance would be greatly appriciated!!
J
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
terrel_b said:
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
Click to expand...
Click to collapse
Great, thanks for the response! That helps alot - I searched around a little while waiting for a reply and still didnt clear any thing up. I have already DL'd ROM Manager and I will just use that... I just like to have as much info as I can...
Thank you!
J
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
ifly4vamerica said:
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
Click to expand...
Click to collapse
Im using unrevoked... I am still running hboot 0.97.0000... thanks for the input, I appriciate it!!
J
roscoenr said:
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
Click to expand...
Click to collapse
Very helpful info - thanks!! I have already DL'd ROM Manger Pro...
Okay - another question, can i place the amon-ra recovery on the SD card BEFORE i root the phone or should I do that AFTER I root the phone? Just curious, I dont even know if it matters one way or the other... Just want to be sure before I do it...
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
JayStation3 said:
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
Click to expand...
Click to collapse
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
alekosy said:
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
Click to expand...
Click to collapse
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
JayStation3 said:
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
Click to expand...
Click to collapse
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
Everything is there, pretty much solid on the information. I hope it works out for you, if not don't RUSH and take your sweet old time browsing the forums for help. GL
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
cool, I will read them and figure it all out... thanks for the info... i flashed amon ra last night, did a back up w/ TB... did a NAND back up through the recovery of the phone... Im just a little confused on the differant recoveries...
Jbcarrera said:
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I thought I did reboot at least once, when I was preforming the NAND back up - but Im rebooting now and I will test it out again...
I do not have great 4G signal here at my house, so that may be it as well... I will mess with it and see whats up through out the day and let you know tonight...
I have noticed that my touch screen doesnt seem as responsive as it was and the phone in general is kind of glichy...
Ok, my 4G is still working... I must not have had a strong enuf signal at my house for it to kick in... No I'm having problems getting tether to work... I started a new thread on that one though...
Sent from the MATRIX... while plugged into my EVO... using the XDA app... from a galaxy far-far away.......
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Did you do "adb shell" and then you tried more adb commands and got "permission denied" ?
If so, then that's because "adb shell" starts a command prompt session on your phone, and the adb commands need to be run on your PC, not your phone. So don't do the "adb shell" first.
So wait a second, you're saying that the wonderful wiki, either is in the wrong order, or requires me to follow the pc, and phone steps simultaneously? Because im running them from my pc. Which would be implied by my saying im following the wiki. Fyi, i meant the one on the g2, involving rooting the g2, on the xda-dev site. I've done this before, i know how to use adb. this is the first time i have rooted a g2. Don't mean to sound like a ****, but you basically didnt read anything i wrote.
The Wiki isn't in the wrong order. But IMHO it's very confusing that it shows a $ prompt when it shows "adb push" etc, because that makes it looks like it is run on the phone. But it's assuming you're running from Linux/Mac. On a PC the prompt for your adb commands would be C:\ or similar.
The Wiki doesn't tell you to run "adb shell"
So the answer to my question was yes, it works, but i had to wait 5 minutes to post this. I dont understand why there cant be a note that, unless you put adb into your path, cmd isnt going to recognize it unless its in the folder you're using. I feel no need to put a tool that i will use maybe once a year at most into path. also, when i just checked the wiki now, i noticed how the dollar signs had changed to c:/ ha ha. and sorry about the rudeness, at first it just seemed like you were making fun of me.
jenlow said:
Okay, so before i opened the adb shell from cmd, when i would type adb push, i would get adb is not recognized as an internal or external command. so, my solution of putting the adb tools into gfree, should work now once i cd to the gfree folder?
Click to expand...
Click to collapse
That's an issue with your path not being setup properly on your PC. You can adb adb's folder to the path to mean you can run it from anywhere. Otherwise you need to put the gfree tools etc in the same folder as adb, then cd to there and run the commands.
Or if the path is setup properly, cd to where the gfree tools are and start doing your "adb push" etc from there.
I have just edited the Wiki to show a "C:\" prompt for the stuff that's run on the PC, to try and avoid this confusion.
Did it work ?
jenlow said:
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Click to expand...
Click to collapse
the "permission denied" thing... from the phone? Or from the computer? You know you need to be root in order to access the hardware, or at least set the permissions on the hardware to be accessible to your user account....???
And... you DID enable adb on the phone side, didn't you?
I used the Wiki and am now perm rooted. A few tips that may help you since they helped me to get it done. I opened a command prompt and noted the default path that opened. For me it was C:\Users\Ed . I used windows explorer to navigate there and open up the Ed folder and created a new folder in Ed that I named pr. This is where I unzipped both of the gfree zip files...into that same folder. When temp rooting and perm rooting, I simply opened up the command prompt, it opened to C:\Users\Ed and then I typed cd pr then I hit enter. That set me up to input the commands in the right place both times and it worked out just fine.
Another thing that I noticed. After temp rooting, I had to ctrl alt del to open up task manager and close down adb.exe (as noted in the instructions that appeared in terminal emulator). I couldn't load adb again until I closed it down and let it restart itself. When I entered the first command in the perm root process adb started up again by itself and all went well.
Good Luck! It is well worth it. I now have Cyanogen's latest stable build loaded along with the Google apps package that I found online.
Ed
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Root my phone!!! HELP
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
mannær said:
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
Click to expand...
Click to collapse
None of those apps work with the G2 to perm root without extra steps. And in that case only Visionary. You need to check out the vision wiki page.
Ed thoroughly described how to make it work. I did the exact same thing he did and got it last night.
jenlow said:
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Click to expand...
Click to collapse
What method did you use to root your cliq, and did you still have 3G? I have stock motoblur 2.1 on it now, I have it for a backup phone (got a G2), but I would like to root it.
Desperately needs help here, and I've looked through a lot of different threads & forums...most bootloop problems are caused by custom roms...
Got my phone online from UK, I live in Canada, been using it since June 2012...everything was fine...until last week or so...
My phone all of a sudden start rebooting itself non-stop. It makes it to the home screen, but after 5-10 seconds, it starts re-booting until battery dies...I did not unlock my phone, nor tamper it in any way....
tried to perform a recovery, failed
tried to perform a factory reset, failed
the only way to turn the phone off and charge it is to go into fastboot and select "power down"
is there any way to solve this problem?? I just want my phone back and function properly.
I've attached some pictures showing software information...don't know if that helps.....:crying:
even just taking pics of software info already restarted twice on me....
please help...
I say warranty, the bootloader has never been unlocked. If you unlock it now and flash roms your warranty will be voided !
Even that you bought it second hand, there is a 2 year factory warranty.....
since warranty was mentioned...i decided to call HTC....
and the tech support guy told me to download this android.process.acore fix on their support website, and follow the instructions...
but since my phone keeps rebooting every 10 seconds after it reaches to the home screen...
How can I install that apk file manually? I would greatly appreciate anyone's help...
It could be pushed with adb commands, but i don't know how that works.....i am a noob with adb
Or tell them to give proper service and not ditch you with a non working solution for you :banghead:
Mr Hofs said:
It could be pushed with adb commands, but i don't know how that works.....i am a noob with adb
Or tell them to give proper service and not ditch you with a non working solution for you :banghead:
Click to expand...
Click to collapse
Maybe this thread will help with your idea.
(just helping you to write final post - - CASE CLOSED-- hahahaa.. It look nice though)
:thumbup::thumbup::thumbup::thumbup::thumbup:
Edit: opps, forgot to include the link. http://forum.xda-developers.com/showthread.php?t=1605720
Sent from Viperized HTC One X using XDA Premium.
DevilRedJack said:
Maybe this thread will help with your idea.
(just helping you to write final post - - CASE CLOSED-- hahahaa.. It look nice though)
:thumbup::thumbup::thumbup::thumbup::thumbup:
Edit: opps, forgot to include the link. http://forum.xda-developers.com/showthread.php?t=1605720
Sent from Viperized HTC One X using XDA Premium.
Click to expand...
Click to collapse
LOL ! You can write that too .......
Mr Hofs said:
LOL ! You can write that too .......
Click to expand...
Click to collapse
DevilRedJack said:
Maybe this thread will help with your idea.
(just helping you to write final post - - CASE CLOSED-- hahahaa.. It look nice though)
:thumbup::thumbup::thumbup::thumbup::thumbup:
Edit: opps, forgot to include the link. http://forum.xda-developers.com/showthread.php?t=1605720
Sent from Viperized HTC One X using XDA Premium.
Click to expand...
Click to collapse
Oh man...i just took a glance at that thread...looks complicated to this first time android user here!! lol
I'll read that more in-depth later when i get a chance...and hopefully I can somehow install that fix onto the phone....
Thanks so much for replying guys...:laugh:
Mr Hofs said:
LOL ! You can write that too .......
Click to expand...
Click to collapse
Of course I can, but seeing you helping people around until they satisfied then you put the last post. Hahhaaha.. Don't know why, but I like it..
Sent from Viperized HTC One X using XDA Premium.
---------- Post added at 01:17 AM ---------- Previous post was at 01:13 AM ----------
Ahhh, btw back on topic. Maybe you can help this guy with your idea using adb to push rom and install apk without being in recovery using that thread. I'm away from my laptop for now so couldn't try it.
Sent from Viperized HTC One X using XDA Premium.
i think it can be done
your phone boots to the locksrcreen, and from that point it does not reboot ? you can leave it there and connect the cable to the laptop. then open a command prompt inside the fastboot/adb folder on the pc
then type
adb install *name of the file.apk
the .apk file has to be in the fastboot/adb folder, otherwise you have to type out the whole location of where the .apk is !
Mr Hofs said:
i think it can be done
your phone boots to the locksrcreen, and from that point it does not reboot ? you can leave it there and connect the cable to the laptop. then open a command prompt inside the fastboot/adb folder on the pc
then type
adb install *name of the file.apk
the .apk file has to be in the fastboot/adb folder, otherwise you have to type out the whole location of where the .apk is !
Click to expand...
Click to collapse
help a girl out...help a girl out... i'm a girl lol
the phone still reboots in the lockscreen....it will stay for like 10-15 seconds and then it reboots....:crying:
How do you know she has USB Debugging enabled for the ADB Commands?
Sent from my Desire HD using Tapatalk 2
Usb debugging is required for adb.
Do you have time to quickly go to settings -> developer options -> usb debugging and enable it. Then adb should work and the setting persist through reboots.
EDIT: ninja'd
Sent from my One X
Its the only option im afraid ! Otherwise its back to warranty
Mr Hofs said:
i think it can be done
your phone boots to the locksrcreen, and from that point it does not reboot ? you can leave it there and connect the cable to the laptop. then open a command prompt inside the fastboot/adb folder on the pc
then type
adb install *name of the file.apk
the .apk file has to be in the fastboot/adb folder, otherwise you have to type out the whole location of where the .apk is !
Click to expand...
Click to collapse
Once i plugged in the usb cable, USB debugging enabled automatically.
so I did exactly what you told me....but not quite sure if it's correct....
i got an error message
adb server is out of date. killing...
* daemon started successfully *
error: device not found
i attached a picture of it...when i type fastboot devices...it did find my phone though....
I couldn't remember if I could ever use adb commands while in the bootloader. I tried recently to push an APK file using adb and absolutely could not do it while in fastboot or in the bootloader.
Here's how I eventually got around it:
ADB has a nifty command script that allows it to wait for the first instance your phone is ready to accept the commands
adb wait-for-device install "android.process.acore or something like that".apk
So, with the phone plugged into my laptop, I opened the folder with the apk and fastboot/adb files in it, opened a command prompt, ran the script and then rebooted my phone.
The adb script said waiting for device until the HTC logo screen started, then BAM! apk installed (even though my phone continued bootlooping).
Give it a shot and see what happens.
As far as i know adb works in recovery (at least a custom one,never tested on stock) and a working OS and fastboot only in the bootloader
requiem11 said:
I couldn't remember if I could ever use adb commands while in the bootloader. I tried recently to push an APK file using adb and absolutely could not do it while in fastboot or in the bootloader.
Here's how I eventually got around it:
ADB has a nifty command script that allows it to wait for the first instance your phone is ready to accept the commands
adb wait-for-device install "android.process.acore or something like that".apk
So, with the phone plugged into my laptop, I opened the folder with the apk and fastboot/adb files in it, opened a command prompt, ran the script and then rebooted my phone.
The adb script said waiting for device until the HTC logo screen started, then BAM! apk installed (even though my phone continued bootlooping).
Give it a shot and see what happens.
Click to expand...
Click to collapse
I tried...and it gave me a similar error message....device not found.
I even tried it when it's at the lock screen...but same thing happened :crying:
Warranty ....... again
Mr Hofs said:
Warranty ....... again
Click to expand...
Click to collapse
Yup. I called last night, and they have escalated the issue...
So now i have to wait for HTC to call me back and teach me how to install the file with some other method using the computer.....
we shall see....otherwise, i have to ship the phone to Texas.....
Okay so I'm having problems trying to get my Kindle Fire fixed. I first need the drivers installed properly. I've installed them a million times from the install_drivers.bat in one of the KFU's I just don't remember which one. I've uninstalled everything and I'm starting fresh as I thought this would be easy and it's turning into a very large headache. Step by step would be beneficial as I'm very clueless. I've tried http://forum.xda-developers.com/showthread.php?t=2166668 but that doesn't give much help just tells me what to and not how to do it. I know exactly what I need and to do and I've googled for days and still can't find nothing. I have tried plugging my Kindle in with both a USB and factory cable and everytime I look in device manager it says unknown device (code 43). So let's start from here and hopefully I can resolve this headache! I also (if this will help) have tried opening up the command prompt from the KFU tools and typed in fastboot -i 0x1949 oem idme bootmode 4000 and all it said was waiting for device and I tried this with the USB NOT the factory cable. I figured I just have to get my computer to configure it. I am pretty noobish when it comes to the Kindle, so any help would greatly be appreciated!
buckeyestilidie said:
Okay so I'm having problems trying to get my Kindle Fire fixed. I first need the drivers installed properly. I've installed them a million times from the install_drivers.bat in one of the KFU's I just don't remember which one. I've uninstalled everything and I'm starting fresh as I thought this would be easy and it's turning into a very large headache. Step by step would be beneficial as I'm very clueless. I've tried http://forum.xda-developers.com/showthread.php?t=2166668 but that doesn't give much help just tells me what to and not how to do it. I know exactly what I need and to do and I've googled for days and still can't find nothing. I have tried plugging my Kindle in with both a USB and factory cable and everytime I look in device manager it says unknown device (code 43). So let's start from here and hopefully I can resolve this headache!
Click to expand...
Click to collapse
Your aversion to use the information available to you is a little disappointing.
Ignoring the fact that you have another thread where this problem is already being discussed, the "Kindle Fire for Beginners" guide, linked to in the FAQ thread that you mentioned, has information on how to properly install your device drivers. The FAQ thread also points to another resource that can help you figure out your device driver problem. If that isn't enough, there is information on where to go when you have exhausted all of your options and still cannot get your drivers working. You ask for a step-by-step guide...well...there they are. Somebody has already gone through all the trouble of doing that for you ahead of time.
Writing a step-by-step guide (again) to tell you how get your drivers working properly, takes a little more effort than just saying..."Do this, do that, then do this, blah blah blah. There is no "one, two" fix to get your device working again. You actually need to educate yourself a little to understand what's going on. It'd be one thing if you had at least some experience, and you tried to resolve the problem yourself and failed, then asked for help. But you're starting from nothing, with nothing. Asking for a step-by-step tutorial from someone at this point is like asking someone to teach you how to read when you don't even know your alphabet yet....that person would have to FIRST go through the trouble of teaching you the alphabet, and THEN teach you how to read.
If you used the information available to you, and you had a specific question about something that wasn't necessarily covered in that information, or if there was something in that information that you didn't understand, I'm sure you would find that there are lots of people around here that are willing to help you figure it out. Otherwise (and I'm speaking from experience), it is very unlikely that you would find anyone of appropriate knowledge to even put forth the effort.
That being said...
...as many people around here can attest, I am always willing to help those in need (even you), assuming those in need (you), are at least willing to meet me halfway first....but I'm not going to hold anyone's hand, and I doubt anyone else will either.
soupmagnet said:
Your aversion to use the information available to you is a little disappointing.
Ignoring the fact that you have another thread where this problem is already being discussed, the "Kindle Fire for Beginners" guide, linked to in the FAQ thread that you mentioned, has information on how to properly install your device drivers. The FAQ thread also points to another resource that can help you figure out your device driver problem. If that isn't enough, there is information on where to go when you have exhausted all of your options and still cannot get your drivers working. You ask for a step-by-step guide...well...there they are. Somebody has already gone through all the trouble of doing that for you ahead of time.
Writing a step-by-step guide (again) to tell you how get your drivers working properly, takes a little more effort than just saying..."Do this, do that, then do this, blah blah blah. There is no "one, two" fix to get your device working again. You actually need to educate yourself a little to understand what's going on. It'd be one thing if you had at least some experience, and you tried to resolve the problem yourself and failed, then asked for help. But you're starting from nothing, with nothing. Asking for a step-by-step tutorial from someone at this point is like asking someone to teach you how to read when you don't even know your alphabet yet....that person would have to FIRST go through the trouble of teaching you the alphabet, and THEN teach you how to read.
If you used the information available to you, and you had a specific question about something that wasn't necessarily covered in that information, or if there was something in that information that you didn't understand, I'm sure you would find that there are lots of people around here that are willing to help you figure it out. Otherwise (and I'm speaking from experience), it is very unlikely that you would find anyone of appropriate knowledge to even put forth the effort.
That being said...
...as many people around here can attest, I am always willing to help those in need (even you), assuming those in need (you), are at least willing to meet me halfway first....but I'm not going to hold anyone's hand, and I doubt anyone else will either.
Click to expand...
Click to collapse
You're acting like I haven't tried everything. Obviously if I'm asking for help I have tried everything and studied into it and failed. You can check out Droidrzr.com, I am very knowledgeable and insightful over there. I'm not just coming over here demanding answers, I've tried everything except the liveusb as my labtop doesn't support it. I am patient but I just want help as obviously I'm not doing something right. I have no problem to supply answers to any questions as I need to fix my dads kindle quick. So please I want to start fresh and figure out what it is I'm doing wrong.
buckeyestilidie said:
You're acting like I haven't tried everything. Obviously if I'm asking for help I have tried everything and studied into it and failed. You can check out Droidrzr.com, I am very knowledgeable and insightful over there. I'm not just coming over here demanding answers, I've tried everything except the liveusb as my labtop doesn't support it. I am patient but I just want help as obviously I'm not doing something right. I have no problem to supply answers to any questions as I need to fix my dads kindle quick. So please I want to start fresh and figure out what it is I'm doing wrong.
Click to expand...
Click to collapse
Believe me, I am sympathetic to your situation, but without any specific insight as to what's happening on your end, other than the fact that you can't get it to work, I have no choice but to assume you haven't done the necessary groundwork to educate yourself in what you need to resolve your problem.
Did you read the Kindle Fire for Beginners guide? Did you understand all of it? If not, what didn't you understand? Have you checked the hardware ID of your device in the device manager and made sure it is in your 'android_winusb.inf'? What have you tried? What haven't you tried? The same goes for any other guide, tutorial or tool that you have been directed to.
No one can see anything you're doing or not doing, so without the appropriate amount of information to give us a clue to the specifics to your situation (other than drivers aren't working), you're just wasting your time. Are we literally supposed to assume you've actually tried "10 million different ways" to get your drivers working? Or do you think it would be more beneficial for everyone to know exactly what you have tried so an appropriate solution can be suggested? You haven't even told anyone what operating system you're using.
Put yourself on the other side for a moment, and imagine someone came to the Driodrzr.com forums...and despite a wealth of information available to them, the only information you can glean from their situation after six different responses across two different threads, is that they have tried "10 million different ways" to get their drivers working, yet they are still unsuccessful. Would you automatically assume they read and understood all of the information available to them and actually put that information to use...all while paying close attention to detail and following all instructions to a 'T'? Call me skeptical...but I think you wouldn't.
[Edit:] In case you're wondering, this is a more appropriate way to present your problem...
http://forum.xda-developers.com/showpost.php?p=40447680&postcount=149
...it isn't perfect, but it at least paints a good picture for anyone who reads it to get a decent idea of what's going on.
soupmagnet said:
Believe me, I am sympathetic to your situation, but without any specific insight as to what's happening on your end, other than the fact that you can't get it to work, I have no choice but to assume you haven't done the necessary groundwork to educate yourself in what you need to resolve your problem.
Did you read the Kindle Fire for Beginners guide? Did you understand all of it? If not, what didn't you understand? Have you checked the hardware ID of your device in the device manager and made sure it is in your 'android_winusb.inf'? What have you tried? What haven't you tried? The same goes for any other guide, tutorial or tool that you have been directed to.
No one can see anything you're doing or not doing, so without the appropriate amount of information to give us a clue to the specifics to your situation (other than drivers aren't working), you're just wasting your time. Are we literally supposed to assume you've actually tried "10 million different ways" to get your drivers working? Or do you think it would be more beneficial for everyone to know exactly what you have tried so an appropriate solution can be suggested? You haven't even told anyone what operating system you're using.
Put yourself on the other side for a moment, and imagine someone came to the Driodrzr.com forums...and despite a wealth of information available to them, the only information you can glean from their situation after six different responses across two different threads, is that they have tried "10 million different ways" to get their drivers working, yet they are still unsuccessful. Would you automatically assume they read and understood all of the information available to them and actually put that information to use...all while paying close attention to detail and following all instructions to a 'T'? Call me skeptical...but I think you wouldn't.
[Edit:] In case you're wondering, this is a more appropriate way to present your problem...
http://forum.xda-developers.com/showpost.php?p=40447680&postcount=149
...it isn't perfect, but it at least paints a good picture for anyone who reads it to get a decent idea of what's going on.
Click to expand...
Click to collapse
Trust me I understand, I think I'm just frustrated from not being able to figure this out and yet it sounds so simple. I am running windows and I can't check my hardware ID's because every time I go into device manager it says unknown (for the Kindle device). I'm gonna try on another computer but if you can tell me why it says unknown and how to solve it I believe I'd be good from there.
There could be a number of reasons why your device manager shows "unknown device". Your bootloader could be malfunctioning or you could just have the wrong information listed in your 'android_winusb.inf' file. It would be helpful to know what hardware IDs are listed in it.
It would also be helpful to know if there is any change in how your device shows up in the device manager when the factory cable is plugged in. On that note, where did you get your factory cable? Did you purchase it from Skorpn, or did you make it yourself? What happens to your device when you plug it in with the factory cable? We've already established that it sits at the Kindle Fire logo, but which one? Does it stay at one brightness, or does it go dim after a few seconds?
And I can tell you are running Windows by the fact that you have a device manager, but what version is it? What prevents you from being able to boot from a liveUSB on your computer? (BTW, this is required if your booloader is malfunctioning)
The more information like this that you can provide, the better chance you will have at getting your problem fixed. Paint a picture. Imagine you're explaining to a blind person next to you what's going on on your end.
soupmagnet said:
There could be a number of reasons why your device manager shows "unknown device". Your bootloader could be malfunctioning or you could just have the wrong information listed in your 'android_winusb.inf' file. It would be helpful to know what hardware IDs are listed in it.
It would also be helpful to know if there is any change in how your device shows up in the device manager when the factory cable is plugged in. On that note, where did you get your factory cable? Did you purchase it from Skorpn, or did you make it yourself? What happens to your device when you plug it in with the factory cable? We've already established that it sits at the Kindle Fire logo, but which one? Does it stay at one brightness, or does it go dim after a few seconds?
And I can tell you are running Windows by the fact that you have a device manager, but what version is it? What prevents you from being able to boot from a liveUSB on your computer? (BTW, this is required if your booloader is malfunctioning)
The more information like this that you can provide, the better chance you will have at getting your problem fixed. Paint a picture. Imagine you're explaining to a blind person next to you what's going on on your end.
Click to expand...
Click to collapse
Okay so I went onto another computer and it shows Andriod phone then the ADB interface. I immediately became exuberated with joy! Now do I do fastboot? Can I use KFU to just hit the option to put TWRP on? I don't wanna mess nothing up as this is all the computers in my house lol. If I do fastboot how do I open up the commands for it? I know I must shift and right click on something I just can't remember what. Thanks for the patience with one man who's finally got something to look forward to when it comes to his Kindle! I also just used a simple USB cord not the factory cable.
buckeyestilidie said:
Okay so I went onto another computer and it shows Andriod phone then the ADB interface. I immediately became exuberated with joy! Now do I do fastboot? Can I use KFU to just hit the option to put TWRP on? I don't wanna mess nothing up as this is all the computers in my house lol. If I do fastboot how do I open up the commands for it? I know I must shift and right click on something I just can't remember what. Thanks for the patience with one man who's finally got something to look forward to when it comes to his Kindle! I also just used a simple USB cord not the factory cable.
Click to expand...
Click to collapse
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
soupmagnet said:
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
Click to expand...
Click to collapse
I used a USB and it said offline in the KFU but it went to the menu to where I could hit options. I never tried the factory cable but I will when I get home. Also since I'm close to fixing this do you have an idea of what is the most stable ROM to put on this? I'm doing it for my dad so he's not into speed or processing anything. Just looking for a stable ROM that has good battery life.
soupmagnet said:
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
Click to expand...
Click to collapse
The FAQ just says I change the bootmode. I know I must shift right click on something to send those commands but I just can't remember what, do you know what I shift right click to send those commands to fix this Kindle? Also can I just send TWRP to the Kindle through those same commands? Also I read the FB guide and the codes USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
popped up in the hardware ID's so I know it's in FB. I just need to know where I shift right click to enter these codes: fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
buckeyestilidie said:
The FAQ just says I change the bootmode. I know I must shift right click on something to send those commands but I just can't remember what, do you know what I shift right click to send those commands to fix this Kindle? Also can I just send TWRP to the Kindle through those same commands? Also I read the FB guide and the codes USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
popped up in the hardware ID's so I know it's in FB. I just need to know where I shift right click to enter these codes: fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
If KFU can detect your device in fastboot , you can use it to install custom recovery, FFF, and/or change the bootmode respectively. It uses fastboot commands to do this when your device is in fastboot mode. When your device is booted normally or in recovery, it uses ADB commands instead.
But...
...if you were to enter the commands manually, the fastboot.exe(adb.exe) must be in the same directory from which you are entering the commands. You can either change to that directory using the 'cd' command at your command prompt, or you can open a new prompt in that directory by pressing shift + right-clicking on that directory, then selecting "Open command window here". Some versions of Windows don't support opening a command prompt in this fashion, BTW.
As for your question of what ROM is the most stable, it would be safe to say that all JB/CM10 based ROMs are quite stable, but CM10. If you want a ROM that has good battery life, you might want to go with a GB/CM7 based ROM, but they're not as nice to look at and kind of awkward to navigate....simple things like changing the volume can be a chore.
soupmagnet said:
If KFU can detect your device in fastboot , you can use it to install custom recovery, FFF, and/or change the bootmode respectively. It uses fastboot commands to do this when your device is in fastboot mode. When your device is booted normally or in recovery, it uses ADB commands instead.
But...
...if you were to enter the commands manually, the fastboot.exe(adb.exe) must be in the same directory from which you are entering the commands. You can either change to that directory using the 'cd' command at your command prompt, or you can open a new prompt in that directory by pressing shift + right-clicking on that directory, then selecting "Open command window here". Some versions of Windows don't support opening a command prompt in this fashion, BTW.
As for your question of what ROM is the most stable, it would be safe to say that all JB/CM10 based ROMs are quite stable, but CM10. If you want a ROM that has good battery life, you might want to go with a GB/CM7 based ROM, but they're not as nice to look at and kind of awkward to navigate....simple things like changing the volume can be a chore.
Click to expand...
Click to collapse
My other computer I'm using doesn't support this :/ what can I do to get the KFU to recognize this? Also how do I change the bootmode?
buckeyestilidie said:
My other computer I'm using doesn't support this :/ what can I do to get the KFU to recognize this? Also how do I change the bootmode?
Click to expand...
Click to collapse
If KFU doesn't recognize your device, it's unlikely that fastboot will work anyway. You can confirm this by entering the following in the command prompt...
Code:
fastboot -i 0x1949 getvar product
...if it returns "kindle", you are good to install custom recovery, then change the bootmode.
Commands for installing custom recovery and changing bootmodes can both can be found in the "Kindle Fire for Beginners" guide.
If the previous command doesn't return a result, you need to fix your drivers.
soupmagnet said:
If KFU doesn't recognize your device, it's unlikely that fastboot will work anyway. You can confirm this by entering the following in the command prompt...
Code:
fastboot -i 0x1949 getvar product
...if it returns "kindle", you are good to install custom recovery, then change the bootmode.
Commands for installing custom recovery and changing bootmodes can both can be found in the "Kindle Fire for Beginners" guide.
If the previous command doesn't return a result, you need to fix your drivers.
Click to expand...
Click to collapse
I entered in a command prompt and It says 'fastboot' is not recognized as an internal or external command, operable program or batch file. I take it this means my freaking drivers aren't working :/ so since the kindle registers as Android ADB Interface what do I need to fix? I thought this was what I was aiming for?
buckeyestilidie said:
It says 'fastboot' is not recognized as an internal or external command, operable program or batch file. I take it this means my freaking drivers aren't working :/ so since the kindle registers as Android ADB Interface what do I need to fix? I thought this was what I was aiming for?
Click to expand...
Click to collapse
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
soupmagnet said:
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
Click to expand...
Click to collapse
Then I can run the kfu?
soupmagnet said:
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
Click to expand...
Click to collapse
My computer won't allow me to open a command prompt from the FB.exe though
buckeyestilidie said:
My computer won't allow me to open a command prompt from the FB.exe though
Click to expand...
Click to collapse
THIS RIGHT HERE is why I am so adamant that you read the information available to you and pay attention to what's being said.
The 'cd' command stands for "change directory". You use it to change the current directory of the command prompt (default is your User directory) to another directory. The correct usage of that command is...
Code:
cd
If you don't know the path of the directory you want to change to, right click on it and select "Properties".
If you still can't figure it out, type 'cd' (without quotes), enter a SPACE, then drag that folder into your command window. The rest should be self explanatory.
[Edit:] CASE IN POINT...Quoted directly from the Kindle Fire for Beginners thread
kinfauns said:
OK, so what are these commands?
To get started, click on the Start Menu to begin. Then, depending on the version of Windows, either use "Run…" or "Search" and type "cmd" to open up a command line window that will look a lot like...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The last line in this example is called a prompt and it's followed by a blinking cursor.
The prompt tells you where you are in the directory structure. When the "cmd" program first starts up, that location is your Windows user's home directory by default. In the above example, my username is "kinfauns" and my home directory by the same name is in the "Users" directory located on the "C:" drive. The "C:\Users\kinfauns" part of the prompt is the directory path and it uniquely describes the location of the home directory owned by the "kinfauns" user.
The blinking cursor indicates the program's readiness to accept a new command. Each time you execute a command, a new prompt/cursor will appear at the bottom, telling you that it's ready for you to type another.
Now type "dir" (without the quotes) and press Enter, and you'll see the names of all the folders in your home directory. The "dir" command just prints out a content listing of the directory indicated by the prompt. If you open up your home folder in Windows Explorer and look inside, you'll see everything in that folder shown in the list you got from the "dir" command. The "dir" command implicitly operated on the current directory shown in the prompt, but you can also provide an explicit argument to tell it what directory to list. For example, "dir C:\Users" lists all the users directories. Providing an argument after the command name will be important for the next command...
The "cd" command is used to change the current working directory. We need to get to the KFU directory, so we can use "C:\kfu" as an argument to the "cd" command. Type "cd C:\kfu" and press Enter to change to that directory. No output was provided, but the new prompt has a different directory path to confirm the "cd" command has executed successfully. You can try "dir" here to list the contents of the "C:\kfu" directory, but it's not necessary to first list it if you know what's in there already. In this case, we'll "cd" into the "C:\kfu\tools" directory, but you won't have to provide the full path. Since "C:\kfu" is already the current working directory, "cd tools" is equivalent to the "cd C:\kfu\tools" command. The one other key component to navigating the directory structure is the ".." directory. The ".." directory refers to the parent of the current directory, so "cd .." will take you back up to "C:\kfu" and another "cd .." will take you up to the "C:\" directory.
Now you'll be able to navigate through the directories and you should have a fair idea about how to construct a directory path (this will come in handy later). The fastboot and adb executables are in the "C:\kfu\tools" directory, so you'll have to get there using what you learned to be able to use them in the next section. There are just a few more tips that might come in handy...
Shift-right-click on/within a folder and select "Open command window here" to open a command line window with that directory path as the current working directory.
File/folder names or directory paths containing spaces must be enclosed in double quotes.
Drag and drop a file or folder from the Windows Explorer windows into the Command Prompt window. The complete, absolute path of the object will be pasted into the Command Prompt window automatically.
Utilize the "Tab" key to complete a file/folder name without typing it in its entirety (e.g. Try typing "cd C:\kfu\to" and then hit the "Tab" key).
For more information on Windows cmd commands, bleepingcomputer.com has a nice introductory tutorial and ss64.com has a full reference page of commands.
Click to expand...
Click to collapse
I seriously hope you'll learn from this and actually pay attention next time you read something.
soupmagnet said:
THIS RIGHT HERE is why I am so adamant that you read the information available to you and pay attention to what's being said.
The 'cd' command stands for "change directory". You use it to change the current directory of the command prompt (default is your User directory) to another directory. The correct usage of that command is...
Code:
cd
If you don't know the path of the directory you want to change to, right click on it and select "Properties".
If you still can't figure it out, type 'cd' (without quotes), enter a SPACE, then drag that folder into your command window. The rest should be self explanatory.
[Edit:] CASE IN POINT...Quoted directly from the Kindle Fire for Beginners thread
[/LIST][/B]
I seriously hope you'll learn from this and actually pay attention next time you read something.
Click to expand...
Click to collapse
I changed the directory to the tools subfolder in the KFU folder. I tried typing the commands I told you 2 or 3 posts ago. It gave me 3 dots and I waited 10 minutes and nothing. Now what am I doing wrong?
buckeyestilidie said:
I changed the directory to the tools subfolder in the KFU folder. I tried typing the commands I told you 2 or 3 posts ago. It gave me 3 dots and I waited 10 minutes and nothing. Now what am I doing wrong?
Click to expand...
Click to collapse
Nothing. That's normal when changing bootmodes in fastboot. Rebooting will boot your device into that particular bootmode.
But simply changing the bootmode to normal (4000) isn't going to fix your device unless there wasn't anything wrong with it in the first place. You'll likely need to access recovery to fix the original problem.
soupmagnet said:
Q16: What does it mean when my device is stuck at the Kindle Fire logo?It depends on which Kindle Fire logo you're talking about. If you're talking about the Kindle Fire logo that stays brightly lit without any change in brightness, it means the device is in fastboot mode. Just change the bootmode to normal or recovery and reboot. If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.
Click to expand...
Click to collapse