Related
I was trying to do the radio s off with visionary and something went wrong.
I downloaded visionary+ onto my Telus HTC Desire HD no problem, I had rooted it earlier and beleived that to be done correctly. I was getting ready to flash my radio and was going through the steps to do so when my problems began.
Now, all that happens is VISIONary+ keeps on rebooting. I have tried pulling the battery, I have tried to change my settings (re: usb debugging) but nothing seems to help.....all it does is continously shut back off and try to reboot.
Any help would be greatly appreciated.
Update: This issue has been resolved. I am now trying to figure out if my phone is properly rooted...go to page 2 in thread please
What is your build number in settings>about>software information? Anything higher (and including) than 1.7 will cause Visionary to fail. Then you have to downgrade first.
OK, that is my first mistake, my Build # is 1.84.61.2.
I will attempt the downgrade and report back here
I am at the downgrade prompt. When I put in the command "adb push psneuter /data/local/tmp" I get a message saying "'adb' is not recognized as an internal or external command, operable program or batch file"
What did I do wrong?
bleagues said:
I am at the downgrade prompt. When I put in the command "adb push psneuter /data/local/tmp" I get a message saying "'adb' is not recognized as an internal or external command, operable program or batch file"
What did I do wrong?
Click to expand...
Click to collapse
download android sdk first
http://developer.android.com/sdk/index.html
put your command to the folder .. for example if u extract to desktop with folder android, then go to command prompt, point to the folder first
e.g: "cd desktop" "cd android"
p/s: put the file inside the folder too
Thanks Hayday, this dosen't seem to help though.
I have the Android SDK in my C: drive and I have placed the "downgrade" folder inside of it. And I still get the same error of "adb' is not recognized as an internal or external command, operable program or batch file" when I type the "adb push psneuter /data/local/tmp"
Any other suggestions?
I believe it still may be a driver problem. I keep getting a message from HTC Sync that says "HTC sync port of ### is not responding. Please disconnect cable and reconnect after 10 seconds"
Can I use the program terminal emulator to do this directly on the phone?
does the folder have adb.exe in it ?
if you place the android sdk folder in c for example the folder name is "android" , you just go to cmd .. then type "cd c:/android/"
and then type "adb" ..
you must use the command inside c:/android .. not c:/android/Downgrade
to be safe, just copy everything in "Downgrade" folder and paste to android sdk folder too ..
btw, here is the full thread by jkoljo himself on how to downgrade.
http://forum.xda-developers.com/showthread.php?t=905003&highlight=downgrade
I have done exactly as you say, I have the "downgrade" folder inside of the "AndroidSDK" folder....and still get the exact same message of "'adb' is not recognized....."
I cannot post a question in that other thread because I have fewer than 10 posts. I will as soon as I get up to 10.
Download & install htc sync, this should include all the drivers you need.
I think you need net framework 3.xx installed as well.
Then in cmd, go to where you put the downgrade file (cd blah blah) - http://forum.xda-developers.com/attachment.php?attachmentid=483902&d=1294492245 - & then the command lines should work.
arlrb said:
Download & install htc sync, this should include all the drivers you need.
I think you need net framework 3.xx installed as well.
Then in cmd, go to where you put the downgrade file (cd blah blah) - http://forum.xda-developers.com/attachment.php?attachmentid=483902&d=1294492245 - & then the command lines should work.
Click to expand...
Click to collapse
oh forgot to mention. download and install htc sync for the driver.
http://www.htc.com/www/supportdownloadlist.aspx?p_id=324&act=sd&cat=all
bleagues said:
I have done exactly as you say, I have the "downgrade" folder inside of the "AndroidSDK" folder....and still get the exact same message of "'adb' is not recognized....."
Click to expand...
Click to collapse
adb.exe is found in platform-tools folder in the android-sdk folder.
Add it to your path. Eg: PATH=c:\android-sdk\platform-tools;%PATH%
Thanks arjunr, after a little bit of tinkering with some files and folders I got it!
Thanks!
Now that I have the proper build #, I want to make sure my phone is properly rooted......or do I have to re-root it?
Is there any way to check and see if my phone is properly rooted?
I had rooted it before I did the build downgrade, does this make a difference?
My phone out of the box was a HTC Desire HD by Telus. The rooting that I followed was the http://forum.xda-developers.com/showthread.php?t=954997"which is the "[GUIDE] Telus Desire HD - Rooting and Flashing" found here on this website
I am good to go, I am rooted and downgraded!
bleagues said:
I am good to go, I am rooted and downgraded!
Click to expand...
Click to collapse
yeah now you can proceed with s-off, and flash new roms if you like.
Heydayat, I seem to be having some issues with anything internet related. I have started another post at http://forum.xda-developers.com/showthread.php?t=1012754 can you take a look at this and see if you can help me?
Thanks
Update: I have fixed the issue at the other thread, it was my APN settings.
Thanks to all for the help
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.
There are several threads on XDA and elsewhere purporting to explain/help people fastboot while using a Mac as their "host." There is even a utility, Androtility:
http://forum.xda-developers.com/showthread.php?t=914826
that claims to facilitate fastboot, as well as most other platform-tools-like tools. Unfortunately, I have not been able to get this to work for me...has anyone out there got another idea?
I can see my device with "adb devices" but "fastboot devices" just returns me to the command line. The version of the stock utility I have is one downloaded from the CyanogenMod wiki, and with which I (without fastboot) succesfully downgraded and rooted my phone...so most of the stuff there works...just not fastboot.
One thought I had was that of the name collision...the CM utility is called fastboot, as is the one in Androtility. Since I adjusted my PATH in .bash_profile to allow access to the CM fastboot version from anywhere, will it be called _even_ if I invoke fastboot while in the Androtility folder, instead of the version that is right there?
Also, need I change permission on Androtility to make it run...? When I call what seems to be the main Androtility app...my shell says there is no such command.
I tried changing the name of the Androtility version to "fastboot-mac" and "fastboot mac" and each time I also got the "no such command" respond from my shell,maybe chmod to 777 is needed...I admit I haven't looked...
I want fastboot so I can flash my hboot to 0.84...has any DZ/G2 plus Mac user done that?
many thanks and regards,
p-d
You have to boot your phone to fastboot, you haven't said if you actually did so I'm assuming no. Otherwise you probably don't have the driver so the easiest option is install the android sdk and platform tools
If you're getting "no such command" it's because the location of it isn't in path, if you're in the folder it's located in you need to do "./fastboot" to run it
Sent from my HTC Vision using Tapatalk 2
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.
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