Has anybody got a Sony Tablet S being recognised by adb?
It seems to be blocked :-(
And yes, I have done all the usual enable USB debugging etc...
I can not use it for development :-(
---------- Post added at 12:56 PM ---------- Previous post was at 12:06 PM ----------
Managed to sort it myself
you need to cd to your .android folder (on a mac, this is ~/.android) and then type
echo 0x054c > adb_usb.ini
Where 0x054c is the vendor id for Sony (I got that by looking at the attached evices in the 'About this mac' preferences)
Now adb sees the device - woohoo
would this apply if i just wanted to use it to transfer music and such? I am not incredibly savy with coding but i tried to enable debugging and all that. I am justnot sure whats the problem.
No, the Android File Transfer program still works without this
Good to know it can be used to dev on. Anyone have any information on how to send data out using the IR blaster, I dont think there is support for it in the native android libraries from what I can see?
The following procedure has confirmed that ubuntu 11.04.
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Kaz Taguchi said:
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Click to expand...
Click to collapse
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Found a way on Windows!
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Bojanglez said:
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Click to expand...
Click to collapse
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file.
Works lime a charm now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
CaptainJack87 said:
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Click to expand...
Click to collapse
Done loading packages.
Preparing to install archives
Downloading Google USB Driver package, revision 4
File not found: C:\Program Files (x86)\Android\android-sdk\temp\usb_driver_r04-windows.zip (Access is denied)
Done. Nothing was installed.
I tried downloading and installing
(Can't post links)Download: Android USB Drivers - Original (Firmware 1.0)
But when I try to install the drivers for the tablet through device manager it says:
The folder you specified doesn't contain compatible software... ...Windows for x64-based systems.
Apparently this driver is only for x86. But after googling "download Google USB Driver Package" that's all I can find.
Got it...
At least I was able to "enable it" through the USB port,
thanks to this exercise in frustration.
Alas no root screen cap still didn't work.
It flashes wildly and does nothing.
Anyone happen to know the proper command line in system variables for win 7 for adb should be?
I haven't used adb in forever, and I think alot of peoples issues with adb is in the fact they cannot use it outside of the android/android-sdk/platform-tools directory. As in you can just type adb shell, adb start-server, adb kill-server from the root dir. I had it set up before, but with a new comp now, and I forgot what it was before.
whats going wrong
i cant seem to get the device driver on my adb at all. no matter what i do i cant get the usb driver sorted. this is where i get stuck"
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
home directory???? every time i try this from home directory i get nothing.
this is my problem.... i dont have this file or entry. what is the entry?????? o notpad doc??,
adb_usb.ini file was missing the 0x54c entry! <<< what is this. a screen shot goes a loooong way.
Adb was simple with my x10 and sgs2 but man this is giving me the ****s.
can someone please post a few simple screenshots of what directory is supposed to be where please?
---------- Post added at 08:39 AM ---------- Previous post was at 08:21 AM ----------
what does this mean?
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file
?????????
I've created an automated ADB driver installer for the Sony tablets.
No more messy, time-consuming SDK install.
http://forum.xda-developers.com/showthread.php?t=1488822
Official Sony instructions
Looks like Sony has posted official instructions for setting up ADB with the Tablet S:
esupport.sony.com/US/perl/support-info.pl?info_id=878
After following their instructions I still had to go to Device Manager, choose to Update the driver for my tablet, and point it to the SDK/usb_driver folder. After that it works great.
debug
Hey guys i have installed the android sdk and the sony s drivers from the official site as dreadengineer posted. but after run the adb devices command i was unable to saw my device.
After that i tried the automated installations that BluechipJ posted, but the result was the same i cannot see the devices neither on eclipse or adb devices command.
i want to debug my application on this device but i could not access it. Can someone help me.
I have a windows 7 x64 OS. i'm able to debug on htc phone and also on the super slower emulator
Obligatory reading before you begin: So You Want to Root and Mod Your HTC Phone
Introduction
Credit goes to Bin4ry for developing the loop-restore trick that applies to many phones, and of course CaptainRewind and jose51197 for being the first to demonstrate its applicability to the HTC Droid Incredible 4G LTE. Since that time, I have put quite a bit of work into writing these automated scripts. I am splitting them out of the original thread so that I can give them a proper home and continue to maintain them. With the start of this thread, I'm also introducing a Linux variant of the script.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usage - typical procedures
All of the below procedures assume you're still using a phone with a locked bootloader and S-ON.
Prerequisites:
Windows users: uninstall any HTC software you currently have installed (e.g. HTC Sync) and install the HTC drivers from this post. Only unlimited.io's S-OFF requires a certain driver version. Other procedures can use the latest version.
All users: Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
HTCDev Unlock: unlock the bootloader, install a custom recovery, and install superuser (for root access):
Flash RUU 2.17.605.2 or run factory reset if you are already on this software version.
... then set these options:
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 1 of the script to unlock the bootloader
... then set these options (yes, again):
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 5 of the script to install either TWRP or CWM recovery
Occasionally, this step needs to be run twice in order for the recovery to boot. It's a quirk of the phone.
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
If you opt for Superuser, you want Superuser-3.1.3-arm-signed.zip
Use task 3 of the script to revert the CID to stock (this will not affect unlock)
Unlimited.io S-OFF (DirtyRacun):
Follow the instructions for DirtyRacun: Fireball at unlimited.io very carefully
When you get to Temproot your phone via any method available, use task 6 of the script to put your phone in temp-root mode.
Continue the instructions for DirtyRacun
Facepalm S-OFF:
Flash RUU 2.17.605.2 or run factory reset if you are already on this software version.
... then set these options:
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 1 of the script to unlock the bootloader
... then set these options (yes, again):
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 5 of the script to install either TWRP or CWM recovery
Occasionally, this step needs to be run twice in order for the recovery to boot. It's a quirk of the phone.
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
If you opt for Superuser, you want Superuser-3.1.3-arm-signed.zip
Follow the directions for Facepalm S-OFF
Use task 3 of the script to revert the CID to stock (this will not affect unlock or S-OFF)
Flash the DirtyRacun HBOOT from unlimited.io - follow the instructions on the right sidebar
Notice: Windows users can run these commands by removing sudo ./ from each line.
Cautionary Notes about OTAs
When (if) fireball gets an official jellybean release from HTC/Verizon:
It is crucial that users have their CID as VZW__001 (and not SuperCID). It seems OTAs (over-the-air updates) for other HTC devices have caused bricks for users who are S-ON and SuperCID. I strongly recommend users revert their CID after unlocking or doing facepalm S-OFF.
New touch firmware may cause compatibility issues when switching between ROMs. If possible, delay updating while devs work on testing ROMs with the new firmware.
With this said, I really have NO clue whether we will ever get an official jellybean release.
Linux script notes
The linux script will only execute properly in a bash terminal!
After extracting, make runme.sh executable:
Code:
chmod +x runme.sh
Then, run the script:
Code:
./runme.sh
Manual procedures for reference
Windows
Before you begin
Uninstall HTC Sync and any other applications/drivers that come up with a search for "htc" in the uninstall programs list in Windows. Download and install the latest HTC Drivers from this post.
Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
Verify your phone is on the correct software version: Settings > About > Software information: Software number = 2.17.605.2 710RD
If you need to update your phone (from 4.0.3) the RUU is here.
Factory reset your phone: Settings > Storage > Factory data reset
Turn off Fast boot: Settings > Power > Fast boot = Off
Turn on USB debugging: Settings > Developer options > USB debugging = On
Part 1: Obtain temp-root
Open a command prompt in the directory where you extracted Inc4GUnlockV6-Windows.zip. Ensure USB debugging is enabled on your device and verify the connection with:
Code:
adb devices
You should see something like:
List of devices attached
HTXXXXXXXXXX device
Click to expand...
Click to collapse
Start the restore process with
Code:
adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
The command prompt will appear to be hung. At this point you can accept the restore prompt on your phone. When the command prompt returns, type:
Code:
adb reboot
Wait at least 60 seconds (seriously, time it) and you phone should be in temp-root mode. There will be only a status bar on the phone, but no unlock-ring.
Part 2: Apply SuperCID
Apply the SuperCID modification:
Code:
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
copy cid mmcblk0p4.original
hexalter cid 0x214=0x31,0x31,0x31,0x31,0x31,0x31,0x31,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
adb shell "rm /data/local.prop /sdcard/cid"
del cid
If all went well, reboot your phone to the bootloader and check your cid:
Code:
adb reboot-bootloader
fastboot oem readcid
Verify that your cid is 11111111.
Part 3: Unlock the bootloader
You can now proceed to unlock your bootloader. Start by retrieving your unlock token:
Code:
fastboot oem get_identifier_token
Sign up for an account using a valid e-mail address at htcdev.com. After you have logged in, jump to page 3. Submit your device token. When you receive Unlock_code.bin in your e-mail (check your junk mail folder!), copy it to the directory where you extracted Inc4GUnlockV6-Windows.zip, then type:
Code:
fastboot flash unlocktoken Unlock_code.bin
Follow the on-screen instructions to unlock your bootloader.
Part 4: Flash a custom recovery
Download your preferred recovery, TWRP or CWM, and flash it through fastboot (phone is at the bootloader) using:
Code:
fastboot flash recovery recovery_file_name.img
fastboot reboot-bootloader
If this is the first time flashing a custom recovery, you may have to perform this step twice. It's a quirk of the phone.
Part 5: Root the phone
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
Part 6: Revert your CID to stock
You may want to revert your cid to stock after installing a new ROM. Keeping SuperCID can cause issues with making/receiving phone calls in stock-based ROMs. Make sure you have Superuser installed. Then, with the phone fully booted up, type:
Code:
adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/sdcard/cid'"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "su -c 'dd if=/sdcard/cid of=/dev/block/mmcblk0p4'"
adb shell "rm /sdcard/cid"
del cid
Linux
Before you begin
Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
Verify your phone is on the correct software version: Settings > About > Software information: Software number = 2.17.605.2 710RD
If you need to update your phone (from 4.0.3) the RUU is here.
Factory reset your phone: Settings > Storage > Factory data reset
Turn off Fast boot: Settings > Power > Fast boot = Off
Turn on USB debugging: Settings > Developer options > USB debugging = On
Part 1: Obtain temp-root
Open a terminal in the directory where you extracted Inc4GUnlockV6-Linux.zip. Ensure USB debugging is enabled on your device and verify the connection with:
Code:
./adb devices
You should see something like:
List of devices attached
HTXXXXXXXXXX device
Click to expand...
Click to collapse
Start the restore process with
Code:
./adb restore fakebackup.ab
./adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
The terminal will appear to be hung. At this point you can accept the restore prompt on your phone. When the terminal prompt returns, type:
Code:
./adb reboot
Wait at least 60 seconds (seriously, time it) and you phone should be in temp-root mode. There will be only a status bar on the phone, but no unlock-ring.
Part 2: Apply SuperCID
Apply the SuperCID modification:
Code:
./adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
./adb pull /sdcard/cid
cp cid mmcblk0p4.original
printf '\x31\x31\x31\x31\x31\x31\x31\x31' | dd of=cid bs=1 seek=532 conv=notrunc
./adb push cid /sdcard/
./adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
./adb shell "rm /data/local.prop /sdcard/cid"
rm cid
If all went well, reboot your phone to the bootloader and check your cid:
Code:
./adb reboot-bootloader
./fastboot oem readcid
Verify that your cid is 11111111.
Part 3: Unlock the bootloader
You can now proceed to unlock your bootloader. Start by retrieving your unlock token:
Code:
./fastboot oem get_identifier_token
Sign up for an account using a valid e-mail address at htcdev.com. After you have logged in, jump to page 3. Submit your device token. When you receive Unlock_code.bin in your e-mail (check your junk mail folder!), copy it to the directory where you extracted Inc4GUnlockV6-Linux.zip, then type:
Code:
./fastboot flash unlocktoken Unlock_code.bin
Follow the on-screen instructions to unlock your bootloader.
Part 4: Flash a custom recovery
Download your preferred recovery, TWRP or CWM, and flash it through fastboot (phone is at the bootloader) using:
Code:
./fastboot flash recovery recovery_file_name.img
./fastboot reboot-bootloader
If this is the first time flashing a custom recovery, you may have to perform this step twice. It's a quirk of the phone.
Part 5: Root the phone
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
Part 6: Revert your CID to stock
You may want to revert your cid to stock after installing a new ROM. Keeping SuperCID can cause issues with making/receiving phone calls in stock-based ROMs. Make sure you have Superuser installed. Then, with the phone fully booted up, type:
Code:
./adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/sdcard/cid'"
./adb pull /sdcard/cid
printf '\x56\x5A\x57\x5F\x5F\x30\x30\x31' | dd of=cid bs=1 seek=532 conv=notrunc
./adb push cid /sdcard/
./adb shell "su -c 'dd if=/sdcard/cid of=/dev/block/mmcblk0p4'"
./adb shell "rm /sdcard/cid"
rm cid
Changelog
Version 6.2
Linux: Fix incorrect use of grep when busybox is not available; update adb and fastboot executables
Version 6.1
Windows: (Hopefully) fixed hanging procedures due to std redirects
Linux: Allow more diverse device codes returned by adb devices
Version 6.0 - Initial Release (in this thread)
Great tool, wish I had this when I was did mine I wasted valuable angry birds time
Sent from my ADR6300 using xda app-developers app
I assume that is only available in linux not a windows version. Anything automated with this process for s-off would be so great. old laptops, new phones and dumbass users like me isn't really a great mix lol
kramer56 said:
I assume that is only available in linux not a windows version. Anything automated with this process for s-off would be so great. old laptops, new phones and dumbass users like me isn't really a great mix lol
Click to expand...
Click to collapse
I literally just put my palm to my face. You need to re-consider whether leaving your stock ROM is a good idea.
This post is relevant.
deserved. the original inc was just so easy i guess. this seems so much more involved with the windows os
I always flash roms with the og
mdmower said:
I literally just put my palm to my face.
Click to expand...
Click to collapse
I see why the new method is called Facepalm S-OFF now.
Well when i get to here adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; it asks on the phone for a encryption password and the cmd.exe says link not found and just keeps running that for 3 minutes then I exited out
maybe I am not extracting to the proper place, that is unclear to me, sorry
When i run the script it doesn't find my device, asks if i see it listed above as "HTXXXXXXX" but all i can see is
emulator-5554 device
FA29TS301243 device
i have the phone connected as charge only, debugging enabled and fast boot dissabled. running latest android 4.0.4, sense 4.1 official update and yes i have latest htc drivers installed and when i plugged the phone it gets recognized just fine.
what could i be doing wrong? win 7 64 bits by the way.
sidgallup said:
When i run the script it doesn't find my device, asks if i see it listed above as "HTXXXXXXX" but all i can see is
emulator-5554 device
FA29TS301243 device
i have the phone connected as charge only, debugging enabled and fast boot dissabled. running latest android 4.0.4, sense 4.1 official update and yes i have latest htc drivers installed and when i plugged the phone it gets recognized just fine.
what could i be doing wrong? win 7 64 bits by the way.
Click to expand...
Click to collapse
I have not seen a fireball with an FAXXXXXXXXX device code. Are you positive you have the Incredible 4G LTE (and not the Desire 4G LTE or Incredible 2, or Incredible S, or something else)?
It looks like you have two devices plugged in. If so, unplug the other device.
If you have HTC Sync or any other HTC software installed, remove it all and re-install just the driver.
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
sidgallup said:
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
Click to expand...
Click to collapse
that driver is for windows 8 i think you need 3.0.007 something like that.
Aldo101t said:
that driver is for windows 8 i think you need 3.0.007 something like that.
Click to expand...
Click to collapse
The 4.x drivers also work with Win7.
sidgallup said:
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
Click to expand...
Click to collapse
Well, if you're sure, you can give the manual instructions a try. If the emulated device isn't something you can unplug, then you'll have to specify the target device for adb with: adb -s FA29TS301243 ...
well... thing is i'm not familiar at all with command line, that's the reason i wanted to use this automatic method, coming from a rooted+m9 Droid 2 with locked bootloader, Incredible 4g looks to intimidating for someone like me, as much as i want to flash Cm10 i don't wanna take the risk of ending with a brick.
Do i need to use this same tool to get it unlocked using the HTCDev method?
sidgallup said:
well... thing is i'm not familiar at all with command line, that's the reason i wanted to use this automatic method, coming from a rooted+m9 Droid 2 with locked bootloader, Incredible 4g looks to intimidating for someone like me, as much as i want to flash Cm10 i don't wanna take the risk of ending with a brick.
Click to expand...
Click to collapse
If you are not comfortable with the command line and the thrill of potentially bricking your phone, please stick with your stock ROM.
This post is relevant.
mdmower said:
If you are not comfortable with the command line and the thrill of potentially bricking your phone, please stick with your stock ROM.
This post is relevant.
Click to expand...
Click to collapse
Yeah, that's what i'm gonna do for now, i thought rooting this phone will be just as relatively easy as with my old Droid 2 Global but it's a completely different animal.
At least last week HTC announced they are updating stock to 4.2.2, with some luck our 4g LTE is getting the update too
mdmower said:
The 4.x drivers also work with Win7.
Well, if you're sure, you can give the manual instructions a try. If the emulated device isn't something you can unplug, then you'll have to specify the target device for adb with: adb -s FA29TS301243 ...
Click to expand...
Click to collapse
I stand corrected, thanks
Ok one last question just to be completely shure i'm not missing something... can i run the script witile the phone is ON or should i be running it with the phone in bootloader mode?
EDIT: ok i got it to work, that other "emulator" device was related to Blue Stacks App Player, as soon as i uninstalled it the script worked perfectly even when my phone wasn't listed as HTXXXX, just installed CM10 and everything is fine.
c:\Android>fastboot oem get_identifier_token
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
I am stuck on this, how do i get pass this the fastboot is there I see it but it won't run
I use windows vista home premium 32 bit
ok yesterday I got as far as the fast boot token on windows and now today the adb is out of date or something to that effect. every time I click sdk manager it has all the revision updates for platform and tools. yesterday it did none of stuff. My device is not found and when i run task 1 it say daemon not working switch to port 5037 and it does not list any devices. Should I do a factory reset on hboot screen? I just installed htc drivers ending in ....23 and still nothing. UBUNTU was a fail because nothing would auto run at all and I had to keep extracting to folders in which nothing found later not to mention no wireless on ubuntu either.
adb is up to date now but no device found, everything powers up just fine
wrong thread