Related
So i rooted my desire using the modaco r6 root.
I'm using defrost 1.0 atm and when I'm entering recovery i cant use any adb command, except for devices which show my desire in recovery mode.
all other commands return an error like:
su:
/sbin/sh: su: not found
logcat:
/sbin/sh: exec: line 1: logcat: not found
install
/sbin/sh: pm: not found
just to name a few.
i just got it so i don't know if they worked before.
however i did get one boot loop due to flashing the circle battery mode.
after which i recovered the nandroid backup.
If you need more info tell me what to do im clueless, im prolly just doing something very stupid.
Thanks in advance.
Go into partitions menu and mount /system then try.
No go doesn't even change the error.
so no ideas? i got no wifi or 3g connectivity atm so you guys are my last resort.
just some updates i flashed mcr 3.1 and it change in addition htc sync doesn't recognize my desire now.
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Can you not boot into fastboot. Volume down and power. Then go to recovery. Then hold volume up and power. Select wipe data and wipe cache. Wouldn't that solve your wifi issues etc?
Wait...if you're using root r6 then your using fake flash aren't you? Try looking for r5 and use pauls recovery or look for amskghs recovery and use that. Pretty sure adb stuff doesn't work easily with fake-flash.
cgrec92 said:
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Click to expand...
Click to collapse
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Hash = #
What exact commands are you doing and what are you trying to achieve?
I really want to help
LByte said:
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Click to expand...
Click to collapse
I had your same problems and felt retarded too, but it might be something funky with the dos command prompt in windows. Follow these instructions to make adb commands universal so it doesn't matter what directory the dos command prompt thinks you're in (because obviously it didn't actually move you to the tools folder somehow even though you instructed it too):
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools
This was found here: sorry can't post link to give proper credit, but do a google search for adb for dummies or adb commands, it's an xda forum post...
The thread looks dead, but im going to post the possible solution anyway.
PM commands like install and uninstall doesnt work in recovery mode, so if you want to use them, run the commands when the phone had booted normally.
i have same problem? anyone help me
adb error /sbin/sh: exec: line 1: logcat: not found
Well I want to command my htc desire from cmd but I am not beeing successful.
I type/get (phone in Fastboot mode):
c:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
c:\Program Files\Android\android-sdk\platform-tools>adb shell
error: device not found
This what I have in Windows "Device Manager" ADB Interface (Installed correctly did not have any "Yellow exlamation icon"):
"Android Bootloader Interface"
any ideas?
Yes, ignore that as mine too said the same. Here's my instructions that I recorded so that I can remember (old age) :-
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Click to expand...
Click to collapse
Note that mine is not located in the 'Program Files' directory so you will need to change that to suit. From there you should be able to run fastboot commands. The 'path' command I had to set due to ADB being in a different directory to Fastboot so running any fastboot commands failed as it was looking to use ADB which doesn't reside in the same directory.
If you are using fastboot, you want to type
Code:
fastboot devices
rather than adb devices. ADB is for use when the phone is normally booted rather than in bootloader/fastboot.
parva, i tried that but nothing changed
C:\sdk\tools>fastboot reboot-bootloader
< waiting for device >
C:\sdk\tools>fastboot devices
and nothing... happens ... My device is there! (Android Bootloader Interface)
more ideas?
Try a different USB cable?
Or another usb port. And make sure you installed all necessary drivers correctly.
Sent from my HTC Desire using XDA App
Why should i try another cable if with this cable I transfer files, windows check all drivers etc... already tried in another pc -.-
what should i see on device manager for the htcdesire device when it is on fastboot?
maybe try using safe mode (if using windows) it could be a firewall or a program blocking the connection
but tell me what should I see on device manager when my htc is on fastboot
portelaux said:
parva, i tried that but nothing changed
C:\sdk\tools>fastboot reboot-bootloader
< waiting for device >
C:\sdk\tools>fastboot devices
and nothing... happens ... My device is there! (Android Bootloader Interface)
more ideas?
Click to expand...
Click to collapse
Are you sure that everything is in that directory? Only by default it installs to 'C:\Program Files\Android', I simply removed the 'Program Files' directory but you haven't even got an 'Android' directory now. Reinstall it and start again maybe, using defaults. You're directory structure may or may not be the issue here but we could be here until this time next year fixing something that is unrelated.
Reinstall the SDK and only remove the 'Progam Files' part of the directory then follow my instructions again.
portelaux said:
but tell me what should I see on device manager when my htc is on fastboot
Click to expand...
Click to collapse
If all is well, when you type "fastboot devices" in your terminal window , you should see something of this format, meaning your connection is good.
"fastboot H3567FYH5577"
Copy the content of Platform-tools to tools. And try ADB that way - if the drivers are correctly installed it should work.
And you must have the USB Debugging option enabled (settings> applications> developement).
Well thanks you all anyway...
My sdk device control started working ^^ ... i dont know why but if already find devices etc
thanks you all
portelaux said:
Well thanks you all anyway...
My sdk device control started working ^^ ... i dont know why but if already find devices etc
thanks you all
Click to expand...
Click to collapse
Please add "[SOLVED]" to topic's title, to help other users.
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.
hi guys,,
love your forum....
simple NOOB question plzzzzzzzzzzzzz...
how do i get into fastboot,,,,
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1668159
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
My Kindle is never recognized by KFU . Here's what you need:
Android SDK
Working adb and fastboot
KFU
On windows 7 shift+right click in your KFU tools directory and click "open command window here"
Here are the commands:
adb devices (your device should be listed)
adb shell (make sure it shows up as root, there will be a #, if not su)
idme bootmode 0x4002
reboot
Then your device should be booted into fastboot mode
He could be having the same problem I had, no /system/bin/sh so the adb technique will not work. I had to make a factory cable, which got me into fastboot mode (but ROMS still are not applying right, that question is in another thread).
gdjy said:
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
Click to expand...
Click to collapse
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
SLOmtb said:
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
Click to expand...
Click to collapse
Thanks for the KFFB plug. Just as an FYI, fastboot doesn't look at the adb_usb.ini file... adb is the only thing that looks at it.
gdjy said:
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
Click to expand...
Click to collapse
I just updated my fastboot guide (the second link I gave you) with details on how to get the hardware IDs and identify whether or not you are in fastboot mode. Take a look again and see what your hardware IDs are. If that doesn't help you, post a more detailed description of what you are doing, what the device is doing, what errors you get, etc. The more details you can provide, the easier it will be for your helpers to determine what's happening. Look at the sticky post at the top of this section.
i know this is also a stupid question, but how do i issue the "fastboot oem format" command? i tried partitioning my kf but it failed....
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.