Related
Hi guys!
Today I tried to get the rooted desire with Android 2.2 with unrevoked 3.21
Previosly I updated to 2.29.405.2 SW
When I run the unrevoked it (desire) freezed on "waiting for root" step. Desire freezed in boot progress (white screen with HTC logo on it)
I removed battery and inserted it again. But I cant boot it, desire freezes on the same white screen with HTC logo.
I can HBOOT, but when I go to recovery menu my device goes to reboot and freez.
So it seems that unrevoked spoiled my recovery and I do not know hot to fix it.
Please guide me, the working solution will be donated $20
--------------
Radio version: 5.11.05.27.
SPL/hboot version: 0.93.0001.
product: bravo.
mid: pb9920000.
security: on.
build-mode: ship.
Device model is not SAPPHIRE - flash old/new disabled.
This device does not have s-off nor eng hboot.
-------------
Thanks!
Flash a stock RUU and try again, you can get 2.29.405.2 from my signature. Remember to use a gold card if you had to in the past
How can I flash the RUU without access to recovery?
You should flash it via fastboot.
Hold the back button and turn on your phone to enter FASTBOOT, then connect your phone to the pc with the usb cable and then run the ruu.
3722 said:
You should flash it via fastboot.
Hold the back button and turn on your phone to enter FASTBOOT, then connect your phone to the pc with the usb cable and then run the ruu.
Click to expand...
Click to collapse
Did it as you said, result is the same
After the successful flash procedure thru RUU device went to reboot and freezed at the same white screen state.
Recovery is still unavailable to get into.
Now I will try to get the logged data thru Android SDK.
This thing is really mess me up =( I'm phoneless.
You, guys, are the one and only hope.
I have installed SDK, but I cant see anything in adb logcat but "waiting for device", thogh my device is conneted via fastboot usb.
Any clue?
I had that same issue, and it turns out it was a problem with the earlier version of clockworkmod (2.5.0.1) that had that issue, where freezing occurred at the HTC splash screen.
Try unrevoked again, with the 2.5.0.7 image here:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Make sure you select the image when you start unrevoked.
It might fail a few times (freezing at splash), but if it does, just pull the battery and keep trying....eventually it'll manage to go through.
Good luck =)
Latty said:
I had that same issue, and it turns out it was a problem with the earlier version of clockworkmod (2.5.0.1) that had that issue, where freezing occurred at the HTC splash screen.
Try unrevoked again, with the 2.5.0.7 image here:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Make sure you select the image when you start unrevoked.
It might fail a few times (freezing at splash), but if it does, just pull the battery and keep trying....eventually it'll manage to go through.
Good luck =)
Click to expand...
Click to collapse
Latty, how can I run unrevoked with a desired image if I cant boot the phone to get it recognized by unrevoked?
you have to start the flasher without the phone being connected, then you should be able to select the image (top left of window).
waebi said:
you have to start the flasher without the phone being connected, then you should be able to select the image (top left of window).
Click to expand...
Click to collapse
yes found it, but when I connect my phone via Hboot usb or fastboot usb - unrevoked does not recognize the connected device.
hellt said:
yes found it, but when I connect my phone via Hboot usb or fastboot usb - unrevoked does not recognize the connected device.
Click to expand...
Click to collapse
Follow the unrevoked guide to install the drivers. Also uninstall HTC drivers before that.
droidzone said:
Follow the unrevoked guide to install the drivers. Also uninstall HTC drivers before that.
Click to expand...
Click to collapse
Already done it. Installed drivers from unrevoked package. But still my phone doesnt get recognized by unrevoked.
hellt said:
Already done it. Installed drivers from unrevoked package. But still my phone doesnt get recognized by unrevoked.
Click to expand...
Click to collapse
It still is a driver issue.
Start from scratch..
Remove all HTC Drivers
Reboot
DC from internet
Connect phone in two modes-Android, Fastboot
It should get recognized but drivers shouldnt be installed and you should be prompted for driver location. If you arent prompted, get Device Manager, uninstall the driver which recognized the device.
Now install Unrevoked drivers as per guide.
Phone should be recognized..
droidzone said:
It still is a driver issue.
Start from scratch..
Remove all HTC Drivers
Reboot
DC from internet
Connect phone in two modes-Android, Fastboot
It should get recognized but drivers shouldnt be installed and you should be prompted for driver location. If you arent prompted, get Device Manager, uninstall the driver which recognized the device.
Now install Unrevoked drivers as per guide.
Phone should be recognized..
Click to expand...
Click to collapse
Ok, thanks will do it now.
But one more question, should it be recognized from hboot usb mode with "Android Bootloader interface" driver, or from fastboot mode?
Cant confirm that without my phone..
But, I believe drivers would recognize it in both..And seperate drivers too..
A small tip..If you have dual boot, try Unrevoked in another OS in which you havent installed HTC. Should work
droidzone said:
Cant confirm that without my phone..
But, I believe drivers would recognize it in both..And seperate drivers too..
A small tip..If you have dual boot, try Unrevoked in another OS in which you havent installed HTC. Should work
Click to expand...
Click to collapse
Faced with problems
1) I uninstalled HTC Drivers.
2) plugged phone and deleted Bootloader interface device then Boot Interface device.
3) rebooted
4) disconnected from internet
5) plugged and powered device and got Bootloader Interface driver installed without a single promt!!! And Boot interface as well.
So I had no chance to manually set the path to the drivers. And unrevoked still doesnt see the device =(
It turns out that I should try another OS???
PS and the key point, should it be recognized in hboot mode or unrevoked only works with booted to OS devices only?
Not really..But that's the easy way out..
Difficult to show you what exactly to delete..
Mostly these are driver clashes..When you uninstall the driver you should tick the option to delete the driver from system.
Try again and you know you've succeeded when it doesnt find any driver installed, and asks you for the location, when you can choose the unrevoked drivers..
Hm, I cant find any options prompting to delete driver from the system... But I will look into more carefully.
ADDED
Found it, trying now.
Tried, was promted to specify the path to the drivers, installed again and with no luck =( Unrevoked doesnt see the device.
I will try it tomorrow on another PC and with another OS.
Thanks for help, I really appreciate this, and I hope we will find a solution.
PS. Is this problem called USB brick?
Hi, today a have tried to root my htc desire using revoked 2 method. I was unable to install usb drivers. And now i cant even mount desire as hard drive. Computer still reports that device is unknown. I tried different usb ports, 2 different cabels, windows xp and seven. Before everything worked fine. Do you thing it is possible, that i damaged phone, when i plug it out just disconnecting cable?
Which version of unrEVOked did you try? I seems like a driver issue as you have to install the modified Hboot drivers for unrEVOked in a certain way before unrEVOked will work. If you attempted root with unrEVOked 3.21, did you follow the steps mentioned in thi thread?:
http://forum.xda-developers.com/showthread.php?t=776696
and
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
MasDroid said:
Which version of unrEVOked did you try? I seems like a driver issue as you have to install the modified Hboot drivers for unrEVOked in a certain way before unrEVOked will work. If you attempted root with unrEVOked 3.21, did you follow the steps mentioned in thi thread?:
http://forum.xda-developers.com/showthread.php?t=776696
and
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
I used this tutorial http://forum.xda-developers.com/showthread.php?t=788044
and I stuck at 3. point... On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
and after that i am unable to connect desire to pc... no way...seems like something happend with usb driver in phone or i dont know...just i ve tried 3 computers for now and every reports same when I connect usb, that device is unknown
What Hboot do you have?
What is your PVT version? (also check the Bootloader for this info)
0.93.0001 and I forgot...I stucked at third point because i got there no option HBOOT USB
benefic said:
0.93.0001 and I forgot...I stucked at third point because i got there no option HBOOT USB
Click to expand...
Click to collapse
And your PVT version?
Bravo pvt1 ship s-on
hboot-0.93.0001
benefic said:
Bravo pvt1 ship s-on
hboot-0.93.0001
Click to expand...
Click to collapse
Ok, thank you for that info.
To tell you the truth, with unrEVOked 3.21, you must install the modified HBOOT drivers for it to work, otherwise it will not work at all.
Please try following this guide as it is definately requied. I asked you above if you had tried going through it, you mentioned that you had only tried using the guide in the first link, but you definately need to have the modified HBOOT drivers installed to proceed.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Try what is suggested and let me know if you can proceed past step three after configuring the HBOOT drivers first, as it is a must.
MasDroid said:
Ok, thank you for that info.
To tell you the truth, with unrEVOked 3.21, you must install the modified HBOOT drivers for it to work, otherwise it will not work at all.
Please try following this guide as it is definately requied. I asked you above if you had tried going through it, you mentioned that you had only tried using the guide in the first link, but you definately need to have the modified HBOOT drivers installed to proceed.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Try what is suggested and let me know if you can proceed past step three after configuring the HBOOT drivers first, as it is a must.
Click to expand...
Click to collapse
Well I tried connecting usb cable in bootloader menu but no HBOOT USB PLUG appeared and in device manager i dont have Android 1.0 device. and this is the problem.
benefic said:
Well I tried connecting usb cable in bootloader menu but no HBOOT USB PLUG appeared and in device manager i dont have Android 1.0 device. and this is the problem.
Click to expand...
Click to collapse
Hmm... yes i see what you mean. Unrevoked is fussy regarding drivers. Try the following:
1) Uninstall HTC Sync completely, the HTC Driver Setup, and HTC BMP Driver if present.
2) Reboot and reinstall the HTC Sync software (latest version).
3) Now uninstall HTC Sync Alone. Keep other two (HTC Driver Setup and HTC BMP Driver) installed.
4) Reboot your PC again.
Note: do not connect phone to PC at all and make sure the phone is switched off.
5) Switch your phone to the Bootloader screen. Connect the phone via USB and it should show Fastboot USB.
6) Windows will show the device detection dialog box - at this point, stop Windows from getting the driver from Windows Update, and manually choose the location of the driver as the folder where Unrevoked driver is present.
7) After this is done, diconnect phone again.
8) Go through the unrEVOked guide and connect the phone when advised to.
If this fails, then try unrEVOked 3.22 (in my sig below) and see how that goes and although you have mentioned that you have tried 3 different PC's, you may have to consider trying it on a different OS platform, such as Linux.
MasDroid said:
Hmm... yes i see what you mean. Unrevoked is fussy regarding drivers. Try the following:
1) Uninstall HTC Sync completely, the HTC Driver Setup, and HTC BMP Driver if present.
2) Reboot and reinstall the HTC Sync software (latest version).
3) Now uninstall HTC Sync Alone. Keep other two (HTC Driver Setup and HTC BMP Driver) installed.
4) Reboot your PC again.
Note: do not connect phone to PC at all and make sure the phone is switched off.
5) Switch your phone to the Bootloader screen. Connect the phone via USB and it should show Fastboot USB.
6) Windows will show the device detection dialog box - at this point, stop Windows from getting the driver from Windows Update, and manually choose the location of the driver as the folder where Unrevoked driver is present.
7) After this is done, diconnect phone again.
8) Go through the unrEVOked guide and connect the phone when advised to.
If this fails, then try unrEVOked 3.22 (in my sig below) and see how that goes and although you have mentioned that you have tried 3 different PC's, you may have to consider trying it on a different OS platform, such as Linux.
Click to expand...
Click to collapse
ok, i tried what you suggest, but desire refused any other driver...and keep installing unknown usb device driver
benefic said:
ok, i tried what you suggest, but desire refused any other driver...and keep installing unknown usb device driver
Click to expand...
Click to collapse
Try downloading the Android SDK: installer_r08-windows.exe
Follow the steps in this video to hopefully get the appropriate USB drivers - http://www.youtube.com/watch?v=N66J6UiN5Pg&feature=player_embedded
EDIT:
With the phone connected, try the following afterwards:
Check to make sure that you have USB Debugging enabled on your phone.
In Device Manager, right-click your Unknown Android device and select 'Update Driver Software'. Browse to the folder (extract the zip to the Desktop) i have attached below and see if it installs them.
MasDroid said:
Try downloading the Android SDK: installer_r08-windows.exe
Follow the steps in this video to hopefully get the appropriate USB drivers - http://www.youtube.com/watch?v=N66J6UiN5Pg&feature=player_embedded
Try the following afterwards:
In Device Manager, right-click your Unknown Android device and select 'Update Driver Software' (Make sure you are connected to the Internet to search for available drivers via Windows Update).
Click to expand...
Click to collapse
OK, i will try the thing with sdk..i am downloading files right now, but that makes no sense to download any other windows drivers. I think the problem is inside of the phone, because it represents itself like unknown device to any computer with any drivers...if there is a way to restore flash memory or something...well looks like i will have to wait one month for reclamation...how this could happen my god
benefic said:
OK, i will try the thing with sdk..i am downloading files right now, but that makes no sense to download any other windows drivers. I think the problem is inside of the phone, because it represents itself like unknown device to any computer with any drivers...if there is a way to restore flash memory or something...well looks like i will have to wait one month for reclamation...how this could happen my god
Click to expand...
Click to collapse
I agree... it is clearly an HBOOT driver issue or the phone... Windows (PC host) drivers are seperate. I was just running out of ideas really
The only definate way of knowing if it is the device that is causing this issue is if you were to try it on a non-Windows related OS, like Linux and maybe it would work for you using an Ubuntu Live CD.
MasDroid said:
I agree... it is clearly an HBOOT driver issue or the phone... Windows (PC host) drivers are seperate. I was just running out of ideas really
The only definate way of knowing if it is the device that is causing this issue is if you were to try it on a non-Windows related OS, like Linux and maybe it would work for you using an Ubuntu Live CD.
Click to expand...
Click to collapse
well this is good idea...do you think it could also fix the usb issue for windows when i will root my phone in linux?
benefic said:
well this is good idea...do you think it could also fix the usb issue for windows when i will root my phone in linux?
Click to expand...
Click to collapse
Yes, because it is not as fussy with drivers as Windows is - with Windows, they have to be properly removed from its cache. With Linux, the phone should be detected ok (unless the phone is at fault).
Here is a simple guide that you can follow:
http://rootmydroid.co.uk/guides/desire/howtolinux-root-your-desire-using-unrevoked-in-linux/
Keep those fingers crossed
MasDroid said:
Yes, because it is not as fussy with drivers as Windows is - with Windows, they have to be properly removed from its cache. With Linux, the phone should be detected ok (unless the phone is at fault).
Here is a simple guide that you can follow:
http://rootmydroid.co.uk/guides/desire/howtolinux-root-your-desire-using-unrevoked-in-linux/
Keep those fingers crossed
Click to expand...
Click to collapse
So, linux didnt work either, system didnt even recognize that anything was plug in. Even crossed fingers dident help Well only last thing I have to ask, if there is any possibility to recover hboot, restore it somehow. Forexample through recovery menu in hboot loader and some kind of .zip file, that i will put to SD card. If not, well I will have to step out to that freezing weather and walk to orange store for reclamation, which I hope would be positive for me, but something telling me it surely will.
I found something about usb unbrick here on xda forum, but is only for root phones
well i found this http://forum.xda-developers.com/showpost.php?p=9056719&postcount=15 i think it could work, just i dont know a way how to discover my CID number..to modify mtd0.img file
ok, i did everything step by step using rageagainstthecage tutorial, but nothing happend at all.
If anyone could help...
Are you able to get into Fastboot?
I suppose running your stock RUU in Hboot won't make a difference then... how about trying the PB99IMG method, which involves renaming the extracted rom.zip file to PB99IMG.zip from your stock RUU, placing this to the root of your SD card and then letting it run from Fastboot mode. This would restore your stock Hboot. You could also try AlphaRev's modified 0.93 HBOOT with S-OFF?
Hi,
A few days ago, I changed my recovery from RA to clockwork, but when i tried to flash zip from sdcard, it showed :
E: can't mount sys/class/mmcblk
My last rom was :
Rcmix s, latest radio, already s-off
Then it could not boot to the phone homescreen, but it still could enter to fastboot, hboot, and recovery. Finally i tried flashing RUU BRAVO WWE RADIO 5110527 SIGNED.exe, and it found that the latest rom was fail/error.
The last step, I had succesfully flashed RUU from hboot. But there is more problem after update :
1. No sdcard detected
2. Adb not detected, but detected as QUALCOMM CDMA MSM on PC, although Usb debugging was already activated. And also No screen notification when usb plugged in the phone
3. Sometimes i could not charge the phone from homescreen, light and battery indicator didn't active, but it still could be charged when phone totally off
Please help me to fix my desire, thank you very much
Sent from my HTC Desire using XDA App
It seems you have a usb brick..follow the usb brick fix link on my sig.
Exiled_SouL said:
It seems you have a usb brick..follow the usb brick fix link on my sig.
Click to expand...
Click to collapse
Wow thank you, i'll try it tonight and will give report to your thread post soon
I'm hoping someone can help me here, and before people say it, yes I have done a search and tried different options but nothing seems to work.
I'm on 0.93 hboot with s-off and fully rooted for years.
The problem?
I was running Nikez Rom on my Desire and it had a few rebooting issues but nothing to be alarmed of. However after one of these reboots the phone did not charge, computer displays a 'power surge on USB' message and disables usb port. Fastboot is not recognised and fastboot USB does not appear when I connect. Using adb does not identify the device either.
What I have tried to do to resolve
Having read several forum posts around USB bricks and fixing fastboot to changing mtd0.IMG files, nothing has seemed to work. Alternatively, it could be me not following things or not doing things in a logical manner. I have also done a factory reset and flashed sandvold Rom but that hasn't helped either.
Help
I am now almost at the end of my tether (no pun intended), so would really appreciate some help in trying to fix this problem.
What I have not done
I have not yet flashed the stock ruu, but not sure how that would work either if my computer disables the USB port anyway.
Skill level
I'm not an expert so please be gentle.
Thanks
Sent from my HTC Sensation Z710e using xda app-developers app
You are SOFF so the easy way to fix usb brick is to flash 4ext recovery since it has got an inbuilt usb brick repairer. However you are saying fastboot is not working. Even with usb brick fastboot should work. That leads me to believe that the problem may be elsewhere. I would check the computer once.
handy5876 said:
You are SOFF so the easy way to fix usb brick is to flash 4ext recovery since it has got an inbuilt usb brick repairer. However you are saying fastboot is not working. Even with usb brick fastboot should work. That leads me to believe that the problem may be elsewhere. I would check the computer once.
Click to expand...
Click to collapse
Thanks, tried 4ext fix usb brick option also, but did not work. I have a Sensation as well and that works fine re computer, so I don't believe it's a computer issue.
Also, the mains charger (plug) light goes off as soon as I put the Desire on charge but comes back on when I remove the phone from the mains charger - which leads me to believe there is something wrong with the phone usb software, but don't know what that could be.
Are there and other options for me to try? Is my phone usb bricked?
You can try the Unbrick option in 4ext recovery.
Also try on a different USB port or even a different PC.
techwiz98 said:
You can try the Unbrick option in 4ext recovery.
Also try on a different USB port or even a different PC.
Click to expand...
Click to collapse
Thanks - already tried these options.
Just responded above to a similar suggestion.
Any other help appreciated.
ac_utd said:
Thanks, tried 4ext fix usb brick option also, but did not work. I have a Sensation as well and that works fine re computer, so I don't believe it's a computer issue.
Also, the mains charger (plug) light goes off as soon as I put the Desire on charge but comes back on when I remove the phone from the mains charger - which leads me to believe there is something wrong with the phone usb software, but don't know what that could be.
Are there and other options for me to try? Is my phone usb bricked?
Click to expand...
Click to collapse
I dont think the problem is software related. I say this bacause the usb port is not working in either fastboot, recovery or rom. Each of these has got its own usb software and they cant all be bad. It seems to be hardware related. I got a feeling your usb port is fried. Most probably it has a short because your mains charger light is fanning out.
handy5876 said:
I dont think the problem is software related. I say this bacause the usb port is not working in either fastboot, recovery or rom. Each of these has got its own usb software and they cant all be bad. It seems to be hardware related. I got a feeling your usb port is fried. Most probably it has a short because your mains charger light is fanning out.
Click to expand...
Click to collapse
But could this happen while it wasn't connect via mains or computer?
How do I confirm this? Is there a solution if this is, in fact, the problem?
ac_utd said:
But could this happen while it wasn't connect via mains or computer?
How do I confirm this? Is there a solution if this is, in fact, the problem?
Click to expand...
Click to collapse
shut down the phone plug it in and see what the charger does.
or even pull the battery and plug it in. if theres ashort it should still be there
colin_404 said:
shut down the phone plug it in and see what the charger does.
or even pull the battery and plug it in. if theres ashort it should still be there
Click to expand...
Click to collapse
Pulled the battery out of the phone, out it on mains charge, but still main charger light goes off.
Tried another battery & it does the same thing. Tried different mains charger and it does the same thing.
How do I prove it's a hardware or a software issue?
Should I try a stock RUU?
Having read other forums regarding USB bricks, people have been able to access fastboot usb, but I can't.
So, I don't really know what the problem is.
I got fixed by this method.
androidforums [dot] com/desire-support-troubleshooting/485991-pls-help-stuck-cant-mount-sd-card-recovery [dot] html
check above link, replace [dot] 's with " . " (period)
boot to fastboot (back+power) and use the following command in command prompt
fastboot oem enableqxdm 0
This will enable the SDcard function in recovery
fastboot oem eraseconfig
This should fix the usb brick
reflash the rom you want from your recovery (you will need to wipe device via recovery 1st)
Click to expand...
Click to collapse
paddyankee said:
I got fixed by this method.
androidforums [dot] com/desire-support-troubleshooting/485991-pls-help-stuck-cant-mount-sd-card-recovery [dot] html
check above link, replace [dot] 's with " . " (period)
Click to expand...
Click to collapse
Thanks for your message, but the issue is every time I connect the phone to my laptop (and I've tried this on two different laptops), I get a message as below:
"One of the USB devices attached to the computer has malfunctioned, and Windows does not recognise it."
It seems the charge on the USB port of the phone has gone corrupt - if that's at all possible.
Once I get fastboot USB working, I'll be good to go.
I'm on BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
RADIO-5.17.05.23
Surely I can't be the only person to have this issue??
Also, I can access my sd card via ES Explorer.
On most of the usb brick issues, I believe the sd card is inaccessible. However, I can access it.
Therefore, I don;t even know whether my phone has a usb brick or whether it's something else?
Anyone?
Sent from my HTC Sensation Z710e using xda app-developers app
Did you try reinstalling usb drivers on your PC?
Sent from my toaster
yea...my username sucks...deal with it...
abaaaabbbb63 said:
Did you try reinstalling usb drivers on your PC?
Sent from my toaster
yea...my username sucks...deal with it...
Click to expand...
Click to collapse
The computer's not the problem The phone is.
Computer usb ports work fine with other devices and my sensation.
Hi,
I'm running Cyanogenmod 10.1 (20130312-Nightly-endeavoru) for some time now.
I'ts time for a new version, but to do that I need to copy de vendor blob to my HOX.
However, for some unknown reason I cannot get a USB connection from my PC to the phone anymore.
Windows doesn't recognize the plugging in of the cord anymore. Both ADB devices and FASTBOOT devices show NO device attached.
USB debuggingmode is on.. so that can't be the problem. I reinstalled the htc-sync software to make sure drivers are installed properly..
I'm out of options of what to check further.
Any bright minds out there who can assist ?
Thanks,
Paul
Try disabling usb debugging, that should solve usb mass storage.
Sent from my IceCold One X
TToivanen said:
Try disabling usb debugging, that should solve usb mass storage.
Click to expand...
Click to collapse
makes no difference. HOX tells me USB storage is in use, with an orange/yellowish android-robot in the screen.
Still no sign from explorer and/or adb and/or fastboot
there is something rotten in the kingdom of denmark
Go to recovery > mounts and storage > mount usb storage.
Alternatively you can use adb when booted to recovery.
Sent from my IceCold One X
TToivanen said:
Go to recovery > mounts and storage > mount usb storage.
Click to expand...
Click to collapse
Hey, Thanks !! That seems to work. :good:
Question: Any idea why I can't have a connection outside of Recovery ?
Don't know what's the cause but it's likely fixed by doing a full wipe before installing the nightly and flashing the boot.img.
Sent from my IceCold One X
TToivanen said:
... and flashing the boot.img.
Click to expand...
Click to collapse
I'm afraid that's not going to happen. To flash boot.img I would need fastboot, and fastboot isn't finding the device..
A nice chicken-egg paradox
I'll try an update from the CM menu...
And it used to work before ?
Are you sure the device is in fastboot mode? (FASTBOOT USB displayed in red)
How about drivers on your PC?
Sent from my IceCold One X
TToivanen said:
And it used to work before ?
Are you sure the device is in fastboot mode? (FASTBOOT USB displayed in red)
How about drivers on your PC?
Click to expand...
Click to collapse
1) Yes, it used to work.
2) I wasn't trying to make the connection from recovery. Just the normal phone-mode, plug in the usb cable, pick USB connection from the menu, and activate USB storage.
3) Nothing really changed on my PC, and reinstalling HTC Sync software didn't do the trick. Drivers must still be good.
I've updated from the CM menu and now run CM 10.1 20130403-NIGHTLY-endeavoru (build date: Tue Apr 23:13:27 PDT 2013)
This hasn't changed my USB problem.
I meant the fastboot, it only works in fastboot mode.
Boot to bootloader by holding vol- and power. Select fastboot from the lil menu.
Now do fastboot devices and it should work.
Sent from my IceCold One X
TToivanen said:
I meant the fastboot, it only works in fastboot mode.
Click to expand...
Click to collapse
Ah - of course.
Yes, in fastbootmode, fastboot devices gives the device name.
ADB still refuses to answer
uninstalled the HTC drivers, and reinstalled from scratch. Still no USB connection in explorer
Gonna try a different computer tomorrow.
Thanks, so far
Huh, you don't need ADB in order to flash boot image. Once you do that, usb issues should be gone
Put the correct boot.img to your fastboot folder and
fastboot flash boot boot.img
Sent from my IceCold One X
The usb issue is definitely a PC related issue
I connected the hox with a laptop, and it worked as normal.
Now to find out why the pc won't recognise the hox anymore.
thanks for thinking along
btw, do I need to flash the boot.img when I update CM from the About >> CM updates menu ?
the kernel is now: 3.1.10-cyanogenmod+
[email protected] #1
Keep an eye on the changelog, if it says "kernel" or "ramdisk", you need to flash the boot image.
Sent from my IceCold One X
MeesterP said:
The usb issue is definitely a PC related issue
I connected the hox with a laptop, and it worked as normal.
Now to find out why the pc won't recognise the hox anymore.
thanks for thinking along
btw, do I need to flash the boot.img when I update CM from the About >> CM updates menu ?
the kernel is now: 3.1.10-cyanogenmod+
[email protected] #1
Click to expand...
Click to collapse
I don't know my friend has this on his hox, running venom and it has this issue across multiple pcs, operating systems and usb cables.
Mounts fine in recovery/fastboot but in sense its nope.
He has just got it back from repair so maybe that was the cause.
Sent from my HTC One X using xda app-developers app
treebill said:
but in sense its nope.
Click to expand...
Click to collapse
I'm running Cyanogenmod, which is non-sense
My laptop at work has the same issue - no connection possible.
So, I have a pc and a laptop that won't work, and one laptop that is working ok...
weird, and hard to pinpoint the underlying problem