Related
When i try typing " adb devices" in CMD.
I get
"list of devices attached"
what am i doing wrong?
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
I have the exact same problem. Did you ever figure it out?
What directory are you working out of? If you did the default install of the Android SDK. Try this:
Code:
cd c:\android-sdk-windows\tools
Then:
Code:
adb devices
You have to open the command prompt from within the tools folder from sdk folder.
Also, its never worked for me while my phone is in the bootloader, i run abd commands while my phone is booted normally (with debugging enabled).
I use adb shell stop, adb remount, whatever commands you wanted to do originally, adb shell reboot.
Hope that helps, good luck man.
Sounds like maybe the driver isn't installed correctly. Check your device manager and see if the N1 shows up in there and what it's named.
tamarian said:
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
Click to expand...
Click to collapse
That is fastboot, fastboot for the bootloader, ADB for everywhere else
Are you on windows or linux?
Also try "adb remount" when you are in the /tools folder, then try "adb devices"
Make sure USB Debugging is on..that could be it
Hi,
I have a legend and everything was fine but after I tried to install the legend CM6RC2 BUILD 66 Rom from cynogenmod it would not reboot any more and I only saw the android robot. After that I tried to get into recovery but that's not possible anymore.
I al ready tried modaco's guide but I didn't understand.
Does anyone know how I can unbrick my usb to be able to get into recovery to install another Rom?
Thanks in advance!
you must unbrick your USB by following this step ( nobody can do it for you... ) :
http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/
usb drivers
I tried to understand this guide but I don't understand this part:
"Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)"
and also i cant do step one because device is not found
you must do this after starting your device.
Before starting your device you must mount you sdcard with 'fastboot oem enableqxdm 0' under fastboot mode ( device off : hold power button + volume down )
after your device started, go to market and install Connecbot.
Start connectbot, select ( at the bottom ) Local in place of ssh , and type 'su' 2 times.
If you get permission denied, do what he's done in his PS http://android.modaco.com/index.php?s=&showtopic=309961&view=findpost&p=1335813
i can type su as many times as i want and nothing happens.
YES i typed it in local.I re-installed htc sync and still my pc cant recognize my phone.
what should i do?
you type SU on your device ? ( in connectbot )
if you see a # at the begining of the line , you are logged as root , just follow the unbrink step
ilos said:
you must do this after starting your device.
Before starting your device you must mount you sdcard with 'fastboot oem enableqxdm 0' under fastboot mode ( device off : hold power button + volume down )
after your device started, go to market and install Connecbot.
Start connectbot, select ( at the bottom ) Local in place of ssh , and type 'su' 2 times.
If you get permission denied, do what he's done in his PS http://android.modaco.com/index.php?s=&showtopic=309961&view=findpost&p=1335813
Click to expand...
Click to collapse
could you explain it for me ? how to do fastboot oem enableqxdm 0 in fastboot.....
you must have android sdk installed to use adb
When you have installed android sdk, go to tools directory, open a command prompt ( MSDOS ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
ilos said:
you must have android sdk installed to use adb
When you have installed android sdk, go to tools directory, open a command prompt ( MSDOS ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
Click to expand...
Click to collapse
what should i do after i reboot my device?
Win7 said he cant recognize the usb device.
is this good? dont you have the drivers or something?
zorro12010 said:
what should i do after i reboot my device?
Win7 said he cant recognize the usb device.
is this good? dont you have the drivers or something?
Click to expand...
Click to collapse
see post #6
to be simple :
only the device will see your sdcard.. not your computer... all steps for unbrick must be done on the phone except the fastboot command
i also tried typing SU and sl
and instead of # it says sh-3.2#
so you are logged as root
just to be sure type : ls not sl
you will see same thing like my screenshoot posted early
now follow unbrick command
ilos said:
you must have android sdk installed to use adb
when you have installed android sdk, go to tools directory, open a command prompt ( msdos ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
Click to expand...
Click to collapse
thousand thanks......for you man.....i made it...........
congratulations !!!
Hi ..
I do not speak English well ،But I'm trying to understand
Please have the same problem, and tried to solve, but to no avail
at the above link in comment # 14
Thanks to Google Translate
when typing in;
cd C:\android-sdk-windows\platform-tools
adb reboot bootloader
fastboot oem boot
in cmd all is fine untill i get to "fastboot oem boot" when it says "oem" is not recognised as an internal or external command, operable progam or batch file.
Does anyone have a solution?
Are you sure it's not complaining about 'fastboot' being not recognised?
Check if you have 'fastboot.exe' in your platform-tools folder (it might be in C:\android-sdk-windows\tools) If it is in tools, just drag it into platform-tools and try again.
-Nipqer
i cant thank you enough, ive been trying this for at least 5 hours and it was a simple copy and paste job
I've rooted my kindle fire before but I lost root access so I rooted it again last night via kindlewater (for mac) or some such name like that.
Then I tried to install TWRP via my vmware windows emulator. At some point during the process my kindle fire disconnected from windows and reconnected to my mac and I'm assuming that's where things went tragically wrong.
It looks as if it's stuck in fastboot but windows isn't recognizing it. My drivers are installed and have uninstalled and reinstalled a few times.
I've tried the Kindle Fire Utility 0.9.3 and the Kindle Fire Unbricking Utility. Neither of them have done anything since the only way windows recognizes the KF is as a corrupted USB device.
I've tried boosting it into normal mode but all it gives me is "waiting on device" as it does with any selection in the KF Utility or KF Unbricking Utility.
I've been in web design/computer technology classes for four years (top of my class) but at some point I must have missed the command prompt classes because I can't seem to ever get commands working nor do I have any idea on how to which is why I've been reliant on those two programs which haven't done anything.
I've seen somebody say they forced the correct fastboot with some command line like fastboot oem blablabla and I tried that once or twice or 8 times and it never recognized the command then again though all I typed was the command and hit enter...
I've never seen a yellow triangle when booting I've always been stuck on a static (no animation) kindle fire screen and no matter what I can't get it recognized as anything other than a corrupt usb device.
What makes this all harder is working on a macbook pro with a windows emulator. -_-
I really need some advice here...I'm about ready to say screw it and use my warranty to have the device replaced in a staples store. If I can't figure out how to boot it i'm sure they wouldn't be able to and would just replace it right?
P.S. I'd rather have it replaced then buy a fastboot cord and have to wait a week to have it shipped lol.
Please help a girl out
try this
Symberlei said:
I've rooted my kindle fire before but I lost root access so I rooted it again last night via kindlewater (for mac) or some such name like that.
Then I tried to install TWRP via my vmware windows emulator. At some point during the process my kindle fire disconnected from windows and reconnected to my mac and I'm assuming that's where things went tragically wrong.
It looks as if it's stuck in fastboot but windows isn't recognizing it. My drivers are installed and have uninstalled and reinstalled a few times.
I've tried the Kindle Fire Utility 0.9.3 and the Kindle Fire Unbricking Utility. Neither of them have done anything since the only way windows recognizes the KF is as a corrupted USB device.
I've tried boosting it into normal mode but all it gives me is "waiting on device" as it does with any selection in the KF Utility or KF Unbricking Utility.
I've been in web design/computer technology classes for four years (top of my class) but at some point I must have missed the command prompt classes because I can't seem to ever get commands working nor do I have any idea on how to which is why I've been reliant on those two programs which haven't done anything.
I've seen somebody say they forced the correct fastboot with some command line like fastboot oem blablabla and I tried that once or twice or 8 times and it never recognized the command then again though all I typed was the command and hit enter...
I've never seen a yellow triangle when booting I've always been stuck on a static (no animation) kindle fire screen and no matter what I can't get it recognized as anything other than a corrupt usb device.
What makes this all harder is working on a macbook pro with a windows emulator. -_-
I really need some advice here...I'm about ready to say screw it and use my warranty to have the device replaced in a staples store. If I can't figure out how to boot it i'm sure they wouldn't be able to and would just replace it right?
P.S. I'd rather have it replaced then buy a fastboot cord and have to wait a week to have it shipped lol.
Please help a girl out
Click to expand...
Click to collapse
I had the same thing happen to me (do not use Fastboot in recovery). This worked for me give it a try ; Kindle Fire Unbrick posted on liliputing. You'll need a PC with Windows. Just be sure you have the Kindle Drivers available, otherwise your USB may not see the Kindle.
Good luck
Why were you using Windows emulator to begin with?
Just use terminal and cd to your android sdk tools folder where adb and fast boot are and type: (with device plugged in and turned on)
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
Chances are that it will hang at "rebooting". If so just hold the power button down until it shuts off then turn it back on. It should start normally.
Sent from my Amazon Kindle Fire using xda premium
CD?
How do I CD to something?
I know this sounds stupid and totally noobish but like I said terminal and I don't get together a whole lot XD
Can I just pay somebody to come to my house and do it for me? D=
(Joking of course)
Okay I think I directed myself to fastboot in terminal and I copied and pasted
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
but then it said "-bash: ./fastboot: No such file or directory
mac-users-macbook-pro-1634:~ macuser$ ./fastboot reboot
-bash: ./fastboot: No such file or directory"
Symberlei said:
How do I CD to something?
I know this sounds stupid and totally noobish but like I said terminal and I don't get together a whole lot XD
Can I just pay somebody to come to my house and do it for me? D=
(Joking of course)
Okay I think I directed myself to fastboot in terminal and I copied and pasted
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
but then it said "-bash: ./fastboot: No such file or directory
mac-users-macbook-pro-1634:~ macuser$ ./fastboot reboot
-bash: ./fastboot: No such file or directory"
Click to expand...
Click to collapse
A quick intro:
cd is "change directory"
pwd is "present working directory"
ls is "list directory contents"
What you see in the prompt above is...
mac-users-macbook-pro-1634 - the name of your mac
~ - your pwd
macuser - your username
~ is shorthand for your home directory. i.e. '/Users/macuser'
e.g. If you type 'pwd' you'll get '/Users/macuser'
cd will change your pwd to what you specify
e.g. type 'cd Documents' and you'll change to that directory. This is analogous to opening up your Documents folder in the Finder.
If you then type 'pwd' at the next prompt you'll get '/Users/macuser/Documents'
If you then type 'ls' at the next prompt, you'll get the contents of your Documents folder listed
What the previous poster wants you to do is change directories to wherever you have the fastboot program so you can run it in the terminal. You can do this on the mac by typing "cd " (that's cd followed by a space) and then dragging the folder that contains the fastboot program into the terminal window. The terminal will automatically paste in the complete path (directory location) of the folder for you.
I suggest doing some more reading...
http://osxdaily.com/2007/02/07/basic-command-line-utilities-tips-commands/
Thank you but
Thank you so much that was incredibly helpful =D
it brought up the fastboot program and it says the following
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
mac-users-macbook-pro-1634:~ macuser$
What should I do after this?
*Bump* I still need help D=
I still don't know what to do after that last step or even if I'm in the wrong place. I'd like to have my kindle fire back up and unbricked before the weekends over. Please and thank you
OK so assuming you have terminal open and your current directory is your Android SDK tools folder...
it should read something like iMac-HD~ platform-tools "yourUsername"$
...all you need to do is type:
./fastboot -i 0x1949 oem idme bootmode 4000
Hit enter, then:
./fastboot reboot
It will say "rebooting". If it doesn't reboot right away just hold down the power button until it shuts off, then restart.
If you aren't sure you are in the right directory to start off in, type:
ls
That's "Ls" not "is"...you should see, among other things, adb and fastboot. If you are not in the right directory (edit: type cd in the terminal) find the Android SDK folder and drag it to your terminal window hit enter and type:
cd platform-tools
That should get you going in the right direction
Sent from my Amazon Kindle Fire using xda premium
ERROR:could not get pipe properties
Okay well I finally got all my directories sorted out so those are fine and I entered in your commands which worked fine (THANK YOU SO MUCH) but now I'm getting this error
mac-users-macbook-pro-1634:tools macuser$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000
./fasERROR: could not get pipe properties
< waiting for device >
^R
./ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
_____________
I've tried it again and now I'm just getting "..." and it's not doing anything. :/
mac-users-macbook-pro-1634:~ macuser$ cd /Users/macuser/android-sdk-macosx/tools
mac-users-macbook-pro-1634:tools macuser$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000
...
Success wooooo
OMG THANK YOU SO MUCH! I LOVE YOU! I seriously don't know what in the world I would have done without your help! I'm so happy right now! =D
If you ever need anything digitally designed hit me up at [email protected] I owe you one
Exact same problem resolved, my issue and solution
I've spent the past several hours banging my head against this problem. MBP and an iMac both running OS X 10.7.3 and VM Fusion 4.1. This thread seemed like the best place to share what I learned in case anyone else has a similar issue.
NOTE: I try and run everything inside vms to keep my base OS clean and just revert to snapshots frequently. Also I've rooted/modded a couple android phones with both these vms recently without incident.
Fought with two different XP Pro vms to get the ADB/Fastboot drivers installed. Kept getting an error about unsigned drivers. At some point the SDK drivers did install and I rooted successfully with KFU 0.9.3. Then I tried the TWRP install and had the same issue as the op. Stuck at the static Kindle Fire image. XP refused to recognize my KF and the drivers would not reinstall properly. Fastboot would remain at the "<waiting for device>" prompt when I used the fastboot -i 0x1949... bootmode command. I tried another route and booted a new OS X 10.7.3 vm and installed ADB/Fastboot. The same "<waiting for device>" prompt.
The problem had to do with the vmware usb implementation. I installed ADB/Fastboot to a non-vm install of 10.6.8 and my KF immediately responded to the bootmode command.
So if you're having a problem with the ADB/Fastboot drivers take a hard look at your usb setup.
I was one of those sorry suckers that somehow got my Kindle Fire stuck in TWRP and I couldn't reset the bootmode to normal. ADB wouldn't recognize the Kindle while it was in TWRP no matter what I tried. Here's how I got it booting again.
1. Download Kindle Fire Utility here.
2. Unzip and open a command prompt in the "tools" folder inside of the unzipped kindle fire utility folder. Do this in Windows 7 by double clicking on the KFU folder and then doubleclick on the tools folder. Next find an empty space in the folder and hold down "shift" on your keyboard and then click your right mouse button. Select "Open command window here".
3. Type in this command and hit enter:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
When that properly executes it will say < waiting for device >
4. On the Kindle Fire inside of TWRP select Reboot -> System.
5. During the reboot process the fastboot command will execute and set you back to normal mode. Now type this in your command window on your computer and hit enter:
Code:
fastboot -i 0x1949 reboot
That ought to do it for ya.
*edit* Wish I could change the title somehow. I misspelled "recognize"
Thank you!!! it worked perfectly. I think this happened because once in the ICS rom I select to reboot into recovery using Room Manager and got stuck on it (bootmode 5001). Anyway this solved the problem in a blink!
You rock!!!! took me two days to find this post..... ugh
Kafluke said:
Wish I could change the title somehow. I misspelled "recognize"
Click to expand...
Click to collapse
LoL...just tell everyone you're British