[solved] Difficulties with unlocking the Bootloader - Legend Q&A, Help & Troubleshooting

Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)

AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app

Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?

Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment

I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)

The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?

Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"

it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?

I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!

AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app

esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.

Related

Can't unlock bootloader

Hello there
My name is Kareem and I'm using a Sony Xperia U 4.0.4 and build number 6.1.1.B.1.10.
So the thing is that I want to update my phone to 4.4 Kitkat and I'm following this thread.
I rooted my device, and I'm now trying to unlock bootloader. My devices says that I'm able to bootload but I still need to unlock it. So I googled around and came across this video which shows me how to unlock bootloader. First I had problems with installing the drivers because I am using windows 8.1 64-bit, but after I disabled “Driver Signature Enforcement” I managed to install the drivers.
And here the problem starts... I have to press the up volume button while plugging in so I can start fastboot. As what I was told, I did and the blue led on the left side turned on. But when I look on my desktop I get a notification that my usb device is not recognized.
Can anyone tell what causes this issue? Otherwise, is there another and maybe an easier way to unlock bootloader?
Kind regards
Kareem
P.s. I'm using that flashtool software to unlock bootloader. It's called "Sony Mobile Flasher by Androxyde".
I prefer to use this.
Is the official method for unlocking the bootloader, includes the drivers and stuff, just follow that tutorial and you're good to go.
Also you have to make sure that your phone can have unlocked bootloader first, if not, then, you have to stick to locked bootloader ROM's.
Now, sorry for saying like this but Windows 8.1 is such a pain in the a**, it always gives error because the drivers isn't signed, if you get problems with that again use this.
USB not recognized, well the solutions for that problem can be:
Use other USB port, if still doesn't work on any of the ports, then can be the slots or bad placement of pins in the motherboard, almost never is a problem of internal dust in the computer but you can try these.
Try other USB cable, may be the cable is failing, try other from another Android phone to complete the process.
Try using other computer with WIndows 7 or Ubuntu.
If you were not able to get working, then tell me.
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with
browse from disk and select "android_winusb.inf" from "...\android-sdk\extras\google\usb_driver" and select "android bootloader interface.
Click to expand...
Click to collapse
There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Kareem_XperiaU said:
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Click to expand...
Click to collapse
Windows key + R, write devmgmt.msc, enter.
Plug your phone and look if some device is recognized in the list, it may appear as Android or something like that, if you got it, then follow me.
Right click to it, Update driver, select from computer, use a list from the PC, and "Use disk", see if there's something that says like that because I got Windows 7 in spanish so it's different.
In that browse for the folder that has the .inf file and open it, it returns a list that you have to select the interface, next and your driver may be installed.
Understand? I can explain more but I have Windows in spanish so I don't know how is in english.
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Kareem_XperiaU said:
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Click to expand...
Click to collapse
Tried to unlock the bootloader with the Sony method?
manudo said:
Tried to unlock the bootloader with the Sony method?
Click to expand...
Click to collapse
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
Sony website said:
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
11. Turn off your device.
12. On your device, push and hold the Fastboot button at the same time as you connect the device to the computer with a USB-cable. The Fastboot button may differ between different device models. See the Fastboot buttons page for more information on what button use on your device.
13. On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
14. Open a command window and go to the tools folder within the Android SDK folder.
15. Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly.
Click to expand...
Click to collapse
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Kareem_XperiaU said:
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Click to expand...
Click to collapse
13. If your phone is recognized in fastboot mode then continue, if not, update the driver.
14. Know the command "cd"? Is for accesing directories, you can use "dir" to see whats in the folder. Example, you downloaded the Android SDK bundle in the Desktop, then "cd" to the "tools" directory, that contains the binary to unlock the bootloader. That's in cmd.
Like:
Code:
cd /SDK/adt-bundle-blah-blah/sdk/tools
And, you're using Windows 8, again, your device is recognized in fastboot mode?
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Kareem_XperiaU said:
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Click to expand...
Click to collapse
Right, if anything goes wrong, feel free to ask!
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Kareem_XperiaU said:
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Click to expand...
Click to collapse
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
manudo said:
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And how can I do that to be honest?
Kareem_XperiaU said:
And how can I do that to be honest?
Click to expand...
Click to collapse
In this post, there are a list with all stock and custom ROM's available in XDA forum, you should download stock and if anything goes wrong then flash the stock ROM with flashtool. You know, flashmode, select kernel, connect to green led, let it boot, and you have stock.
By now, try to unlock the bootloader, if you need help with the flashing then you can ask by here or create another thread.

unable to connect

Dears,
I wonder if you can help
I did the following steps successful.
unlocking bootloader
rooting
flashing cwm recovery
flashing cm10 (updated to CM11 successfully)
flashing gapps
but the phone stays S-on.
Now my computers does not recognize the phone.
In the windows device manager is a one listed under other devices.
But when i am looking for drivers automatically or manually the drivers cannot be found.
When I reboot my phone into bootloader mode then my computer recognize the phone and i have access via ADB or fastboot.exe
fastboot.exe -devices is listening my phone as FA3AAW905529
Maybe I need to S-off my device, but i dont know how.
I would like to have acces to folders on my phone.
Alternatively I installed Airdroide as a workaround.
P.S. Drivers are installed
Sincerely
Alex
No idea?
Sent from my One using xda app-developers app

Help!!! No stock rom, no boot, 218.707.5, cid: Htc_044, can fully charge !

Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
GoRiLaz301 said:
Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
GoRiLaz301 said:
Hi Everyone / Anyone,
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
[email protected] said:
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
Click to expand...
Click to collapse
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
In CUSTOM Recovery the USB debugging is enabled by default...so that step of booting into phone and enabling the USB debugging doesn't matter...
the device won't get recognized if u had not installed the HTC drivers...
try installing the latest drivers from here
Install this and try
Code:
adb devices
And what are u planning on do install a custom ROM or Flash the Stock Nandroid backup from the thread I provided.....????
I can only help u knowing what u are trying to do.....
GoRiLaz301 said:
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
Click to expand...
Click to collapse
GoRiLaz301 said:
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
Click to expand...
Click to collapse
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
GoRiLaz301 said:
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
Click to expand...
Click to collapse
Fine and clear..
have u tried the drivers I have put in the previous post.........????
Try different USB ports to on ur PC too.......that will work sometimes.......:fingers-crossed:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
GoRiLaz301 said:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
Click to expand...
Click to collapse
These are the latest HTC drivers can u try this and report whether ur device is recognized in adb recovery mode......
Please try by uninstalling the previous driver u had.........
BTW is it Windows 8.......????????
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it. it will be recognized as HTC MP DEVICE or something similar but with unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognized as HTC device without USB driver device installation problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Earlier before your help, have found and load TWRP version 2.6.3.0 whereas now the version is 2.4.4.0, will earlier or this 2.4xx version be any difference and affect the connection with adb?
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
GoRiLaz301 said:
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it.
it will be recognised as HTC MP DEVICE or something similar but will unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognised as HTC device without USB driver problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
Click to expand...
Click to collapse
From the control panel OFC
If u had installed HTC drivers u must be able to see it like this uninstall that...
O Haa haa )
Blunder me ! That's right ! Think bit exhaust after a few sleepless nights figuring out why and hows on this phone....
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
GoRiLaz301 said:
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
SDK Manager wont show up on Control panel AFAIK....
it will be a zip file which u have to extract.....
in the extracted folder u will be able to see android-sdk-windows\platform-tools from where u have to open the cmd to execute the abd/fastboot commands
I have the setup of android-sdk-windows and the HTC drivers I pointed to....
It works flawlessly so i recommend to uninstall Universal Adb driver since that isn't helping ur phone recognized anyways.....
Install the Drivers I pointed to and try wether ur phone is getting recognized....:fingers-crossed:
Note : Alternately u can try this installer also which is a small package with the necessary adb and fastboot files......
---------- Post added at 06:43 PM ---------- Previous post was at 06:32 PM ----------
GoRiLaz301 said:
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
these drivers can be there ...they are or the installation of bluetooth drivers for our phones I guess....
Just uninstall the Universal USB driver .....
If you have HTC Sync I beleive u must be having the HTC driver as I showed on the Screen shot.....
Anyways if u dont see that in the control panel install the one I gave.....U must be fine
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
GoRiLaz301 said:
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
Click to expand...
Click to collapse
FIne....
From bootloader boot into recovery.....
try whether u r device is recognized.......
If recognized PROFIT for the hectic work done......
then u can push a rom to ur SDCARD using adb push command......
then install as usual from the recovery........
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
JACK POT !!!!
ADB DEVICES listed my device s/n. in recovery mode.!
GoRiLaz301 said:
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
Click to expand...
Click to collapse
Absolutely Fine........
What I meant in While in TWRP connect ur phone to PC
double click on your Start SDK shortcut and in the CMD type
Code:
adb devices
Ur result must be like this
YES, it did show the device listed with serial no.
Now i into the [Recovery Installation] section and at the BACKUP part (pt. 15), now should i also tick Recovery + Cache to perform full backup of actual ROM? (this seem not applicable to me, is it?)

[Q] Desire X power on only in fastboot

Hi HTC Guru's
i've get a HTC Desire X from a friend, for repair service. his phone starts only in fastboot. no chance to start android.
with fastboot i have unlocked the bootloader with htcdev.
but i cant install any recovery to install stock or custom rom. all what i do fails! i'm stuck at this problem
what can i do now? i cant disable or enable usb debugging, because there's no rom installed.
thanks a lot ...
I assume the startupscreen states S-ON and UNLOCKED.
Did you connect your phone to PC and are you flashing the recovery with the fastboot command (DOS command)? Are you sure the phone is recognized in Windows (if you are using Windows..)?
RuudM said:
I assume the startupscreen states S-ON and UNLOCKED.
Did you connect your phone to PC and are you flashing the recovery with the fastboot command (DOS command)? Are you sure the phone is recognized in Windows (if you are using Windows..)?
Click to expand...
Click to collapse
yes, i have tried installing TWRP via fastbooth. but nothing happens. the phone is recognized in windows. if i plugin the phone, in display i get "Fastboot USB". unlocking the bootloader was able, too.
What happens when you execute 'fastboot devices'? Nothing or a number?
If nothing: which OS do you have? If Windows 8 > try another computer with a lower version.
I'm on way to work. Can't look now. I mean, in display stands '0123456789 device' or something like that.
It's hboot from ICS. And I have the right version of twrp.
And of course I use Windows 8.i don't have windows 7 already.
Just to be sure, maybe I misunderstand your info: fastboot (from Google's Android SDK) is a DOS command, executed from a DOS box (phone connected USB). Are you executing the command that way?
If so, probably for sure that Windows 8 recognizing your phone is your problem if nothings happens. No laptop? Copy the fastboot.exe and your recovery-file and try to flash it on W7 or XP :silly: ("fastboot flash recovery yourtwrp-filename")
Yes, I do it with cmd at admin rights under win 8. I know the usage of cmd. I have successfully customized my HTC sensation and note 4 as well.
Can I run win7 in live mode or in a virtual machine?
So, if there is no respons on 'fastboot devices' it is probably a driverproblem. If that can be solved by a virtual W7? I don't know, don't think so. Anybody else?
"As you all may now, Microsoft pushed the new driver stack in Windows 8.1 so ALL (not only USB 3.0) devices must provide a BOS descriptor. Sony ADB and Fastboot doesn't, so Windows fails to enumerate the device which is reported in Device Manager as error code 43. This also may help if you have a USB drive or mouse and it stopped working after you upgraded from Windows 8 to Windows 8.1."
There is a trick to bypass this by replacing the USB-drivers with the USB.zip files (this link). I had a bit of trouble afterwards
Installing PDAnet seemed to work for me (tried most drivers to no avail on win8/ 8.1)
Is this the same on all USB ports? tried on a different machine yet?
Never tried on VM but I don't think it would work as it still uses the same resources (USB ports, etc.)
Fastboot runs. I have no driver issues. But I get some errors if I try to install twrp or roms. Without twrp, I can't install a rom. That's my problem. Not the drivers. But I understand, if Windows 8 works different in command line as Windows 7 does.
It can be possible.
I try pdanet driver, when I went home from work in round about 8 hours... So on, thanks for you help
Aha, an error. That was not clear to me - it differs from 'nothing happens'.
Did you select the right TWRP? HBoot 1.25=JB or HBoot 1.24=ICS. Look at this page
Oh sorry. I have told you wrong information. Hboot is 1.25. But I have the twrp for jelly bean tried to install. But an error occurred.
I'll take a look at your link later at night. Thanks.
here are the error i get in cmd console:
Code:
c:\Users\my_name\Desktop\htcbootloader>fastboot flash recovery recovery.img
sending 'recovery' (7868 KB)...
OKAY [ 1.268s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.379s
i still have searched google and this forum for this error, but without a solution.
here is a screenshot from bootloader menu.
Sent from my SM-910F with Tapatalk App.
Right mouse click on 'image update error', contextual search, gives me a lot of extra info. Could it be that you picked a wrong version? Is it called 'twrp-2.8.5.0-protou.img'?
Or else: try to install an old TWRP from this page.
I have tried 271 for jb hboot,which should be the right version.. But I can try the ones in your link...
Sent from my SM-910F with Tapatalk App.
Flash stock JB kernel via fastboot.
Sent from my HTC Desire X using XDA Premium 4 mobile app
samarth sathe said:
Flash stock JB kernel via fastboot.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
where do i get the stock kernel? i have no Downloads found only custom kernels -,-
creonx said:
where do i get the stock kernel? i have no Downloads found only custom kernels -,-
Click to expand...
Click to collapse
The one provided here:- http://forum.xda-developers.com/showthread.php?t=2249760
Sent from my HTC Desire X using XDA Premium 4 mobile app

[Q] HTC Rezound Recovery Problem

`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
syedzakiabidi said:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
Click to expand...
Click to collapse
You can't access TWRP because you over-wrote it with the factory RUU firmware image, it isn't there anymore...
Download TWRP image from TWRP official site at https://dl.twrp.me/vigor/ or Flyhalf's build at http://forum.xda-developers.com/showthread.php?t=1902381
Either one is good... then start fastboot, connect usb and flash recovery with the command:
fastboot flash recovery <path/filename of TWRP IMG file>
give it a minute or so, reboot into Hboot and start TWRP.
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
youdoofus said:
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
Click to expand...
Click to collapse
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
acejavelin said:
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
Click to expand...
Click to collapse
fair point, and i do have ubuntu (of differing flavor dates) on 3 of my machines, so i might just do that. Thanks!! Ill also try the goofy htcsynch (which i forgot about, as im a Sammy guy now) Thanks again!!

Categories

Resources