[Q] Unable to install Android 1.0 drivers - HTC EVO 3D

I'm trying to root my Evo 3D with hboot 1.5 and have been following the instructions in the development thread. However, I get stuck at the command "fastboot getvar mainver" in step 1. At this step, windows detects a new device 'Android 1.0' and unsuccessfully tries to install drivers for it. As a result, the only thing I see in my command window is "< waiting for device >."
I don't want to permanently brick my phone so I'd like to ensure that I have properly changed the version to 1.10.651.2 before proceeding.
Does anyone have any ideas on how to resolve this or provide me with a link to the proper drivers?
Thanks!
EDIT: Problem solved. I installed some HTC drivers I found!

Related

[Q] Need help unlocking bootloader in Ubuntu

Hi Guys,
I'm new to the android game and need some help unlocking my Atrix 4g gingerbread bootloader.
I already got it rooted using the one-click root guide floating around. I then installed ROM-manager and installed CWM but I cannot unlock the bootloader for some reason.
Here's basically the steps that I tried so far:
- installed Android SDK
- added udev rules
- installed + restarted adb
- ran "adb devices", no results
- downloaded fastboot, "fastboot devices" had no results
- downloaded moto-fastboot, "moto-fastboot devices" had a motorola item listed
- ran "fastboot oem unlock", pc stuck at "waiting for device", phone stuck at "starting fastboot protocol support"
- tried with sudo, same results
- ran "moto-fastboot oem unlock", had some message about unlocking not supported or something
- tried with sudo, got the "waiting" message on pc and "starting" message on phone
- ran "wine fastboot.exe oem unlock", same result as the fastboot one
any suggestions? thanks
I don't know anything about flashing in linux but you can do:
1. Winehq.org, run rsdlite and flash the sbf. (Most likely won't work because you need the drivers)
2. VMWare Player, install windows, then drivers, rsdlite, you know the drill.
If you can get windows then use this: http://forum.xda-developers.com/showthread.php?t=1154600
Oh I forgot! When you run adb you must have Debugging on for it to work. It's Settings>Applications>Development>Debugging Support (I think).
Alaq said:
I don't know anything about flashing in linux but you can do:
1. Winehq.org, run rsdlite and flash the sbf. (Most likely won't work because you need the drivers)
2. VMWare Player, install windows, then drivers, rsdlite, you know the drill.
If you can get windows then use this: http://forum.xda-developers.com/showthread.php?t=1154600
Oh I forgot! When you run adb you must have Debugging on for it to work. It's Settings>Applications>Development>Debugging Support (I think).
Click to expand...
Click to collapse
thanks for the link, nice info in there
I ended up using my work laptop which has windows in it to flash the sbf and unlock the bootlader
thanks

[Q] Android 1.0 driver error with Fastboot

I been trying for days to get my HTC Flyer with Honeycomb rooted via the GUIDE but I am stuck at step 1.
"If you are not on an appropriate gingerbread version, eg. if you have upgraded to honeycomb then downgrade by using an appropriate RUU; to identify your RUU see: here"
(downgrade to Gingerbread) but I get stuck at the "Fastboot getvar cid" stage to find out which RUU I have. When I have the Flyer in Fastboot mode and connect the cable, I get an error when it trys to install the "Android 1.0" driver.
I have uninstalled, rebooted, reinstalled, repeatedly. I just tried another link that suggested to try installing PDANet for Android to get around this problem. Now when I run Fastboot, rather than just "waiting for connection", I get an error that says "getvar:cid FAILED (status malformed (1 bytes)) finished.
*** Update***
I just tried a different HP Laptop with Windows 7 installed & I had the exact same error regarding the Android 1.0 driver as soon as I plugged in the Flyer when it was in Fastboot mode. Is there some other setting other than Fastboot off I need to do on the Flyer itself? Any other suggestions would be GREATLY appreciated.
Please help!! I am at my wits end here.
thanks,
sPk
still need help
I am still struggling here.
By pointing the Android 1.0 driver installer to the PDANet directory, it found a ADB driver and installed it. But I still get the "malformed error" when I try to use "Fastboot getvar cid" command to find RUU version. Is there another way to get the RUU version??
I think the driver is communicating with the Flyer as I was able to get Flyer to respond to the serialno command.
I have OTA update and want to root/Rom with HBoot 1.11.00011.
If I can't get the RUU version, is there a most likely suspected RUU for a WiFi only Flyer that I just got from Buy.com for US market.
thanks in advance for your help.
sPk
You have the android sdk installed right?
Andriod SDK
Gumby63 said:
You have the android sdk installed right?
Click to expand...
Click to collapse
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
windsurfsail said:
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
Click to expand...
Click to collapse
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
SDK
Gumby63 said:
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
Click to expand...
Click to collapse
I was able to get the Android SDK & Java installed properly. I uninstalled the driver in the Device Manager and then pointed the driver install to Android SDK/Tools and it indicated that the driver was already installed. I tried Fastboot command for the zilllionth time and still got the same malformed error. So I uninstalled driver & deleted it this time and tried to re-install but now it doesn't find the driver files (because I deleted them). I can re-install SDK or just point it to the PDANet directory again.
Is the correct driver for Fastboot the the Android ADB? It is the only one I have been able to get to load when I plug in the Flyer in Fastboot mode.
thanks,
sPk
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
hboot & fastboot confusion
globatron said:
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
Click to expand...
Click to collapse
DOH!
Globatron, thanks for the clarification. In all my reading of threads, I never saw any definition of hboot & fastboot. Since it wasn't working, I installed the other drivers in an effort to fix what was apparently a driver issue.
Is "fastboot mode" just having the "Fast boot" box checked under the Power settings?
thanks again!
sPk
Fastboot mode
After searching in the forums for a while, I found a description on how to get into "fastboot mode". I have added below in case someone else is new enough not to know.
I ran the command & it finally worked. Being in the right mode was key.
sooo, I now have the cidnum= BS_US001 but looking through the list of the RUU's files, I still don't see any reference to this CID. Another stupid question: How do I find which of the list of 25 RUU files is correct for my WiFi Flyer?
UPDATE: Found out how to find RUU file from link.
http://forum.xda-developers.com/showpost.php?p=18508220&postcount=2
modelid: PG4140000 (Wifi Flyer)
RUU_Flyer_BrightstarUS_WWE_X.XX.1540.XX
cidnum: BS_US001
cidnum: HTC__055
sPk
----------------------------------------------------------
You need to be in fastboot mode. Two ways to get there.
Get into boot then select fastboot
Or
While booted in android connect to PC then enter "adb reboot bootloader" (assuming you know adb a little)
Once in fastboot you need to enter the commands in a cmd terminal on your PC just like adb
What I learned, that may help you...
I had a surprisingly difficult time getting my OTA Honeycomb US WiFi Flyer S-Off'ed, Rooted & uploading a new ROM. I did get it done but there were some basic things I should have known or done. Thanks to Globatron & all who post on this board.
1: Before you start, make sure your PC's drivers are 100% working. I had Windows driver problems that caused other problems. Make sure that your tablet is properly recognized by the PC when the tablet is in Fastboot/Hboot modes, and in regular Android mode.
2: I didn't understand the difference between Hboot & Fastboot. This small thing made all the difference and was one of my major issues. Because I had the tablet in Hboot not Fastboot, the Fastboot commands didn't work and I couldn't get my RUU version
3: Pay attention to the phone's settings. Especially USB Debug mode, Fastboot mode.
4: After I had finally downgraded to Gingerbread. I couldn't figure out why Revolutionary wouldn't recognize my tablet. The simple answer was when I had downgraded to Gingerbread, all my phone settings were back to stock also so I had go in and change the USB Debug and Fastboot modes. It would be helpful to add a reminder in the GUIDE to make sure that these settings are changed before running Revolutionary.
5: Not really related but I had a problem when I wanted to backup my newly Rooted/ROM'ed phone. I had previously purchased the Titanium Backup Pro and I installed it on the Flyer but it wasn't listed in the Apps menu but was listed in the Manage Apps. Because Google-Play/Android Marketplace only copied over the paid apps to my newly upgraded Flyer, it didn't copy the free version of Titanium Backup. You must load both the free version & the paid Pro version for it to work.
I hope this helps someone who runs into any of the same issues I had.
thanks,
sPk

[Q] (Q) Troubles unlocking bootloader from xperia U

I'm having troubles with unlocking the bootloader from my xperia U. I am following the steps from this site unlockbootloader.sonymobile.com/instructions , and everything goes very well until step 13. I am not asked to install the driver they mention in that step and I haven't found a solution to install it.
I tried to avoid that step and to go straight into command window and entering the commands ( like fastboot.exe -i 0x0fce getvar version). I don't get a response but an error that states the .exe file couldn't be recognized.
I have flastool installed, and I have installed all the drivers from it. I also tried to use the 'blu' option, but then I get the message "your phone can not be officially unlocked" . I have been searching for 5 days now, and I don't know what to do..
Any kind of help is welcome!

[Q]Lenovo IdeaTab S6000 fastboot unlock issues

Like many of you, my S6000F was easily rooted; but, isn't cooperating with my attempts to unlock it.
I have been following the directions posted at Lenovo Ideatab S6000 Unlock Bootloader Tutorial (not allowed to post a link on xda); but, have hit a brick wall when trying to execute the command line: fastboot-windows oem unlock
I get one of two error messages:
1) If I am at the command line, and the tablet is in normal Android, it will say: Waiting on device
2) If I have the tablet in fastboot mode, it will say: fastboot is not recognized as an external or internal command
I have ensured that
ADT was fully installed and configured
the correct adb windows and adb drivers were installed (I have tried the Google drivers provided with the guide I lined to above; and, also tried the Universal Naked Drivers)
adb can 'see' the tablet, as can Windows (in device manager with the tablet in normal and fastboot modes)
I use an administrative command prompt window
adb, fastboot and sdk are all in the same folder; and, that I open an administrative command prompt in that same folder
I have honestly spent hours trying to find relevent info via Google and Bing; and, then researching in the forums that show up in the searches. All the steps that I bulleted above are the results of what I have found, piecemeal; but, I havn't been able to find one, complete lucid guide to this issue. Any solid direction would be greatly appreciated.
Thanks, in advance!
PJ Arts

Question Issues unlocking

So I just purchased this phone and am trying to follow the instructions on the Sony site. The rooting status in my service menu says my devices should be able to be unlocked.
Device is on android 13 on latest update, OEM unlock and USB debugging are both enabled.
I downloaded the usb drivers and the platform tools from the Sony site.
I opened a command prompt in the platform tools folder and when I run fastboot devices I get a response
When I run the command with my unlock code, I get the error
FAILED (remote: Command not supported in default implementation)
I tried to go to device manager to update the drivers, however when I do that it says the best driver is already installed.
I read in another thread to try to boot into the bootloader rather than fastboot. When I select reboot to bootloader the device seemingly shuts off.
EDIT: OK, I'm dumb and was in fastbootd mode rather than fastboot. I've now entered fastboot correctly (holding volume up while I plug it in, getting a black screen and a blue LED), updated the drivers correctly, and am now getting the error that the device is already unlocked. Now I guess I just need to verify that it is indeed unlocked, anyone have some advice on that?
EDIT 2: OK it seems to be going through the unlock process despite that error rather than the expected confirmation. After a few reboots it is now giving me the setup process again so I hope it worked. Leaving thread up for others who have the same issue to stumble accross.

Categories

Resources