Develop Bugs

Need help with my EVO

Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?

xarttyx said:
Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?
Click to expand...
Click to collapse
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot

mongoose8p said:
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
where do i find that folder... im sorry i dont really know much of this

i'm assuming you are using windows. it's the location of your \android-sdk-windows\tools\ folder from when you installed the android sdk in order to root in the first place. it is also the location of adb. if need be, do a search for adb.exe and it should point you directly to the location of everything you need.

It keeps saying "the system cannot find the path specified". I dont even know what to do. This sucks.

it might be under a different path, where did u install ur android sdk?

i don't really remember. i found it though searching for adb and i guess i have 2 folders of it... zipped and unzipped... but i tried putting both path names in there and that went nowhere

When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.

awesomeindeed said:
When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.
Click to expand...
Click to collapse
that option does not pop up.. im running xp if that helps

im still having trouble figuring out what to do.

xarttyx said:
that option does not pop up.. im running xp if that helps
Click to expand...
Click to collapse
copy the path of the folder with adb.exe in it - start - run cmd - command "cd path of adb folder" - then follow the instructions above

[GUIDE] Everything You Need to Setup and Use ADB

Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted Android Device
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now,
1. Run SDK Manager.exe located in the android-sdk-windows folder
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r7+
1. Run SDK Manager.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Still not working?
Try this: Get ADB to recognize your myTouch 4G [Thanks importflip]
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> - Example: adb pull /data/app_s/Stock.apk
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.

Even after unstalling the HTC and myTouch 4G Drivers, when I plug my MT4G back in there's nothing to install. It automatically installs what it has to. I have no idea how to connect it with ADB.

I had to do this:
http://forums.t-mobile.com/t5/Operating-System-Software/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017

This is why after the temp root. I used root explorer to move the files to right folder . And then used the terminal app to do the rest. Really no need to use ADB..
Sent from my HTC Glacier using XDA App

Scoop24 said:
This is why after the temp root. I used root explorer to move the files to right folder . And then used the terminal app to do the rest. Really no need to use ADB..
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I did that too but insmod said can not open wpx.ko every time. No idea why, worked perfect on my G2.
Sent from my HTC Vision using XDA App

Arcadia310 said:
Even after unstalling the HTC and myTouch 4G Drivers, when I plug my MT4G back in there's nothing to install. It automatically installs what it has to. I have no idea how to connect it with ADB.
Click to expand...
Click to collapse
You ran the HTCDriver exe that is on the SDCard? Did you go into Devices on your computer with your phone plugged in and see what it is showing up as?

setzer715 said:
You ran the HTCDriver exe that is on the SDCard? Did you go into Devices on your computer with your phone plugged in and see what it is showing up as?
Click to expand...
Click to collapse
It seemed to work for me when I copied the HTCDriver.exe from the storage card to my PC and install the drivers. My device showed up as some letters and numbers, which is ok I guess I have not named or done anything to the device.

Amazing write up. ABD has always gave me a hard time. I will be following this write up when I get time to root this. Thanks a lot!
Sent from my HTC Glacier using XDA App

Four things:
1. You don't need the generic drivers from the SDK package. I haven't even tried them. You need the HTC Drivers on the SD card.
2. I start adb by SHIFT-right clicking on the tools directory in the SDK folder and selecting 'start command prompt here' in the contextual menu. In order to see if things are working, just type 'adb devices' to see if the HTC device is connected.
3. I don't need to disable mounting of the device. I can adb and have the SD card mounted on the PC at the same time.
4. I don't see the need to add the environmental variable. Perhaps I've done something wrong, but theoretically, by adding this variable, you should just be able to type 'adb' in any command prompt window and have the system recognize adb. I can't seem to get that to work. So, instead I just do #2 above.

setzer715 said:
You ran the HTCDriver exe that is on the SDCard? Did you go into Devices on your computer with your phone plugged in and see what it is showing up as?
Click to expand...
Click to collapse
Yes I have, how exactly do I get into devices on my computer?
Sent from my HTC Glacier using XDA App

Arcadia310 said:
Yes I have, how exactly do I get into devices on my computer?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
type
Code:
adb devices
in the command line

Arcadia310 said:
Yes I have, how exactly do I get into devices on my computer?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
What does the output from typing "adb devices" give you?

grankin01 said:
What does the output from typing "adb devices" give you?
Click to expand...
Click to collapse
It says can not recognize ADB. I have had the SDK and ADB on my PC for months.

Arcadia310 said:
It says can not recognize ADB. I have had the SDK and ADB on my PC for months.
Click to expand...
Click to collapse
Sounds like you aren't in the directory that adb is in when you type it. try going into the tools directory in your sdk and run the command from there.

Arcadia310 said:
Yes I have, how exactly do I get into devices on my computer?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
What version of windows are you running?

setzer715 said:
What version of windows are you running?
Click to expand...
Click to collapse
Windows XP. When i actually go to ADB and click on it it opens and closes within an instant.
Sent from my HTC Vision using XDA App

Arcadia310 said:
Windows XP. When i actually go to ADB and click on it it opens and closes within an instant.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
You don't click on it. It's a utility to use in command line. What it does is makes it easier to enter commands (along with some other useful stuff). Basically, anything you would type in terminal you can type in command line on your pc with "adb shell" pre-face. For example:
In terminal: cd /system/app
In command line: adb shell cd /system/app
Makes sense? You should really read up some guides out there

floepie said:
Four things:
1. You don't need the generic drivers from the SDK package. I haven't even tried them. You need the HTC Drivers on the SD card.
2. I start adb by SHIFT-right clicking on the tools directory in the SDK folder and selecting 'start command prompt here' in the contextual menu. In order to see if things are working, just type 'adb devices' to see if the HTC device is connected.
3. I don't need to disable mounting of the device. I can adb and have the SD card mounted on the PC at the same time.
4. I don't see the need to add the environmental variable. Perhaps I've done something wrong, but theoretically, by adding this variable, you should just be able to type 'adb' in any command prompt window and have the system recognize adb. I can't seem to get that to work. So, instead I just do #2 above.
Click to expand...
Click to collapse
Hey sorry about the driver problems... i wrote this guide based on the Nexus one and T-Mobile G1 and was asked to repost it here. If you let me know exactly what drivers you used i can change it in the OP.
The environmental variables set so that you can run adb and fastboot commands from anywhere in windows without have to be in the tools directory of the sdk. You can press SHIFT or w/e but this is a 1 time solution so u basically never have to be in that directory again...
As for the mounting, it is recommended that you dont mount your SD-Card and use adb for editing system files because that could corrupt your sd card.

Thank you, I got it working. Android is very different from winmo.

nephron said:
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Still not working?
Click to expand...
Click to collapse
This saved me... Constantly had it reverting back to USB storage device, this did the job. Thanks, a little something coming your way...
Bill

KF Failed Root

Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!

Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2

Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.

I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.

AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2

ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567

From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA

I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!

soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!

AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA

For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.

soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA

backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!

I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.

AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA

backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA

AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse

backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.

soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.

AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.

[Q] error: device offline

Hello everyone,
I'm trying to revert back to stock on my one x, and I seem to have run into a snag.
Every time I try to run something from the all in one toolkit I get this lovely error:
error: device offline
My device most certainly is not offline. I'm running CM10.1, and can only access files on my phone from my PC when I turn on the "USB storage" from the app.
I NEED the phone to be recognized, so I can go back to stock.
Thanks in advance

Do you have the debug usb active?
However, when i have my device offline, just take off usb cable from pc and put it in a new usb port.

Guich said:
Do you have the debug usb active?
However, when i have my device offline, just take off usb cable from pc and put it in a new usb port.
Click to expand...
Click to collapse
Yes I do, and I tried that and restarting, but to no avail.

With android 4.2.2, adb changed, do you have the latest?

Guich said:
With android 4.2.2, adb changed, do you have the latest?
Click to expand...
Click to collapse
Define "adb" for a noob :3

R: [Q] error: device offline
adb is the program that you use for "talking" with android.
It have a lot of command and one is: adb devices, and this command give you your error
With android 4.2.2, adb changed and i think adb is present in toolkit that you have is adb for 4.1.x...
However, you can found the new adb on internet or into the sdk
Sent from HOX

Guich said:
adb is the program that you use for "talking" with android.
It have a lot of command and one is: adb devices, and this command give you your error
With android 4.2.2, adb changed and i think adb is present in toolkit that you have is adb for 4.1.x...
However, you can found the new adb on internet or into the sdk
Sent from HOX
Click to expand...
Click to collapse
Been searching for ages, cannot find an adb download.
Might anyone help?

Estract adb from this zip

Guich said:
Estract adb from this zip
Click to expand...
Click to collapse
'Aight, I have downloaded it (many thanks ) and a command prompt flashed open and closed itself, but alas, I cannot get my phone recognized by both the toolkit, and the stock RUU .exe file.
My mission is to get back to the stock rom :/

Download ANDROID SDK BUNDLE (Google) unpack it in a self specified folder. Uninstall HTC sync manager and leave the drivers.
Put the phone in the bootloader and open a command window in the SDK platform tools, point in the folder and hold shift + right click mouse button - open command window
In that window yoh type
Fastboot devices (when a serial pops up its good)
Fastboot getvar version-main

Mr Hofs said:
Download ANDROID SDK BUNDLE (Google) unpack it in a self specified folder. Uninstall HTC sync manager and leave the drivers.
Put the phone in the bootloader and open a command window in the SDK platform tools, point in the folder and hold shift + right click mouse button - open command window
In that window yoh type
Fastboot devices (when a serial pops up its good)
Fastboot getvar version-main
Click to expand...
Click to collapse
Not getting a serial.
C:\Users\userName\Desktop\Blargh\adt-bundle-windows-x86_64-20130219>fastbo
ot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Tamar Al-Tahan\Desktop\Blargh\adt-bundle-windows-x86_64-20130219>

I found new ADB files and replaced them in the toolkit's data folder.
I still, however, get the same error after rebooting both devices, and plugging out/in the USB.

In your line i don't see platform tools ! The fastboot file is inside the platform tools.....so you must get something like this
C:\foldername\android sdk\sdk\platform tools
I don't see you navigated to the platform tools folder

Well the CMD thing worked, but nothing happened with the toolkit :'(
And I'd like to change to a different modded ROM if it makes a difference, but either way I need to be able to flash an .img file, which will be impossible if the device is not recognized while in recovery.
Edit:
C:\Users\Tamar Al-Tahan\Desktop\SDK\adt-bundle-windows-x86_64-20130219\sdk\platf
orm-tools>fastboot devices
C:\Users\Tamar Al-Tahan\Desktop\SDK\adt-bundle-windows-x86_64-20130219\sdk\platf
orm-tools>fastboot getvar version-main
< waiting for device >
version-main: 2.20.502.7
finished. total time: 0.005s
C:\Users\Tamar Al-Tahan\Desktop\SDK\adt-bundle-windows-x86_64-20130219\sdk\platf
orm-tools>
Heres what I get from CMD

Check your bootloader and let me know what's on top !
Does it say ENDEVOURU ?

No it does not, I see the standard
*** Tampered ***
*** unlocked ***
EVITA PUT SHIP S-ON RL
HBOOT-1.14.002
RADIO-.19AS.32.09 11_2
OpenDSP-v29.1.0.45.0622
eMMc-boot
Jun 11 2012, 14:36:28
Fastboot USB

Thought so.....you have the HTC one xl dual-core phone. This forum is actually for the HTC one x quad-core phone !
You need to be official in the AT&T HTC one xl forum
But fastboot is working now. Reflash the custom recovery (and please get it from the AT&t forum)
And then enter recovery and mount the sdcard again as a mass storage device ....
Fastboot flash recovery recovery.img
Is the command. Place the right recovery.img in the fastboot folder and flash it.
You can also perform a ruu
http://androidfiles.org/ruu/securek....11_2_10.105.32.25L_release_271865_signed.exe

:0!
Did not know that, thank you sir.

Cant get fastboot to work!

I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?

Digital signature of the driver or wrong drivers is the problem

joedoctor said:
I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Click to expand...
Click to collapse
u are not saying mutch about how u are trying to enter fastboot
u do know the phone must be turn into fastboot right ?

...
same here, done everything i can...

mockneygeeza said:
same here, done everything i can...
Click to expand...
Click to collapse
to get fastboot to work u need to reboot the phone into fastboot

-fluffy- said:
to get fastboot to work u need to reboot the phone into fastboot
Click to expand...
Click to collapse
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol

moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
I'm going to try the above, it's never too late ?

moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers

-fluffy- said:
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
Click to expand...
Click to collapse
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.

moeq123 said:
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
Click to expand...
Click to collapse
im on windows 10 also an my adb devices also show nothing but i can still flash recovery an all