Related
Hello,
I try to unlock my bootloader with htcdev but i get this error :
C:\Users\Administrator>cd C:\Android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
How to fix this ? :$
I'm looking too, but for the [Doubleshot].
Trying the same thing myself on the HTC Doubleshot (MyTouch 4G Slide) and no joy, same exact error.
ericosman, did you by chance follow all the advice on HTC's site -- including specifically installing HTC Sync? I didn't install Sync because it looks like stuff I won't use and don't need, except that Sync has some dependencies (like a USB BMP Driver, whatever that is) that might make the difference. I haven't tried yet but I plan to.
I've tried two different versions of Fastboot, one I downloaded from masterjason.com and another I downloaded from Google's Android SDK manager. Both behave identically, despite one being nearly a megabyte where the other was 70 kilobytes.
I've tried reinstalling USB drivers, no joy.
I can get fastboot devices to work, as well as adb anything when the phone is booted, so I don't think drivers are really the issue.
I think it's HTC making a blanket promise that all the phones in that list can do this and indeed not all can.
[EDIT 2012-01-07: Add more info I found]
Gotta love it. Edited the post, and when saving, was told to refresh and log in. Then I wasn't given a chance to copy-paste what I typed. Annoying.
Anyway, see if I can remember what all I typed...
uhm...
I found through Google, and directed to Yet Another Android Forum somewhere on the 'net, that fastboot oem h will provide you a list of commands that are supported, and get_identifier_token was not among them. I suspect it's the phone's bootloader which contains supported commands, not Fastboot executable itself, so it may require downgrading/upgrading to a different HBOOT that has the necessary command support.
I did find readsecureflag which returns the integer "3" on my S-ON device. I assume then that the command I found called writesecureflag similarly takes an integer value, but what value to feed it, I don't know, and I don't want to risk my phone. Seems benign enough, but I know from computer programming that anything looking benign is not always.
Anyway, if you run fastboot oem h and get_identifier_token isn't there, I'd recommend giving up on this particular method of rooting.
Hope this helps.
[Edit 2012-04-15: Strikeout above no longer applicable info]
Turns out, see Aisho's post below, which sums up what eventually worked for me.
I actually had to wait for an OTA to be available long enough for a dev to package it up to a bootloader-flashable package, which included the get_identifier_token. Once I had that version on my phone, I was able to get the token to HTCDEV and get my bootloader unlocked. Not full access, but not bad: The only downside is if I need to flash a kernel I have to do it separately from the ROM through fastboot, and I don't think I can update my radio (not that I should need to). But hey, I can flash a custom ROM and get rid of this nasty crap T-Mobile thinks everyone should have (I will never play bejeweled, so I don't even want that adware/nagware on my phone).
[/edit]
I actually had this same problem with my HTC Wildfire S, and found this thread in searching for answers -- since I figured it out, I figured I'd put the solution out there.
My HBOOT was precisely the version HTC was advertising on their site as necessary for the unlock, which made it all the more perplexing when I repeatedly got this error. But then it occurred to me that while my version might be the same, HTC had stuck a neat little asterisk* next to the Wildfire S initially, saying that it required a new HBOOT anyway. I'd thought I was smarter than they were, but really what's different in the new download is the incorporation of just the command you're missing here. Since the ability to unlock is fairly new (through HTC officially, I mean) they're providing new HBOOTs with that command line included. I flashed the new HBOOT (even though it was exactly the same version) and lo and behold when I tried it again, it accepted the fastboot oem get_indentifier_token command.
I'd check to make sure that the HTC Legend doesn't have an asterisk as well, and maybe redownload the HBOOT anyway just in case. It can't hurt.
Aisho said:
I flashed the new HBOOT (even though it was exactly the same version)
Click to expand...
Click to collapse
I'm having the same problem on htc salsa, I have the version it says i should have, but have no get_indentifier_token, how is HBOOT updated?
My phone is S-ON and Hboot is 1.07.0000
HBOOT is updated via bootloader mode (on my phone, assumably the same for most HTC phones). You will need the correct HBOOT for your phone, and it will probably have to be contained within a full update package (for my phone, it's PG59IMG.ZIP, for the Dream it was DREAIMG.ZIP, your phone model will have its own filename). That file goes on the SD card, you boot into bootloader (usually, remove battery to ensure phone is full off, replace battery, and power up while holding the "VOLUME DOWN" button in). It then checks the file and asks you if you want to update.
However, if your phone is the same or newer version as the file you are trying to use, there's a good chance it will not work (the phone will not downgrade (usually (I think (I could be wrong) ) ) ).
You might also be amongst the lucky few who have a phone with what's called an RUU available. That's an .EXE file you run in Windows, connect your phone, and it writes what's in the file directly to the phone regardless of version.
HIH.
I have the upgraded HBOOT version as Im following a thread for how to do it, which incidentally isnt working, when I go to the bootloader menu it finds the file but does not up date it. It has been updated to the current version stated on htcdev with a FOTA update which may be why the HBOOT upgrade doesnt work.
I have the HTC salsa and it does reference RUU a few times. I dont use windows but HTC sync doesnt seem to find the phone, I have tried many things to get it working
Am I meant to run the EXE provided by htcdev and dont run HTC SYNC? Should I be in the bootloader menu/recovery first before running it?
@ericosman
did you follow every single steps ?
I just did it on my Legend (24 hours ago), in the end I followed the post of BlaY0 (http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62) and it worked great.
And yes, the RUU file is the one of a few MiB that you find at the very beginning at HTCdev.
The only trick is that I had to restore my data backup but also my boot backup, otherwise I was stuck in the hboot.
I did it by flashing the recovery image, as I deleted my old update.zip of ClockWorkMod, following the steps of http://forum.xda-developers.com/showthread.php?t=1290841 (see the end of the post: 'New recovery'). Then I went to 'Advanced restore' and restored both my boot image and my data back.
Always backup your system before playing around !
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
chris... said:
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
Click to expand...
Click to collapse
Alright, let's try again.
Before the step 1 of HTCdev, it asks you to upgrade your phone to the latest RUU. You don't have to. (see BlaY0's post [1])
Just download the RUU file, thus you will be able to retrieve the very hboot's zip (just run the EXE, don't go through the installer but instead locate its temporary extraction folder with the task manager and get that rom.zip).
They only want you to install HTC Sync so that your phone is recognized by Windows and the RUU can located it.
[1] BlaY0 explains that you don't have to upgrade to the latest HTC ROM or even RUU.
got it, and dump that zip file with the correct file name onto the root of the sdcard and start the bootloader
YAY it works, time to proceed to unlock
The version I got from a different post must not have been the correct one
im sure im bumping an old thread, but im trying to unlock an old espresso, but its having the same issue as the OP, i cant find the RUU with the new hboot, it currently has the 1.02 hboot, any clues?
Have you tried following the steps I referred to ?
Look at my two posts.
In fastboot, What is displayed besides the hboot version ? Something like "unlocked" ?
If note you have to re-flash your hboot with HTC dev method, once again read the post I linked to.
Sent from my Legend using XDA
just to add that on my MyTouch 4G slide I had hboot-1.44.0007 and gave me the same error as the first post when trying to unlock through htcdev.com. I did an OTA update to HBOOT-1.45.0013 (Software version 1.63.531.2 710RD) then went back to htcdev.com and it worked without problems
Getting this while trying to re-unlock evo 3d ics. hboot 1.58.
It's an old thread but maybe it's helping someone...
If you receive the error described in the topic title/first post you need to simply register to htcdev dot com and follow each step(including the 1st step because that's actually what you need to do )
i got same problem w my Z3 plus hbot will work on my z3 plus????????
Hi,
My original Sensation started dieing (backlight issues I think). I successfully returned it to standard with S-ON prior to returning it to Vodafone.
Today the replacement turned up, so S-OFF is the first step ) So a few checks first and......
Anyway, "adb devices" seems not to be able to see the new phone.
i) USB Debugging enabled on the phone;
ii) PC sees it perfectly as a storage device;
iii) "adb devices" sees my Desire perfectly;
iv) Yesterday on the same PC I installed RUU on the old Sensation, then reset CID then finally changed it back to S-ON, the final two rely on adb/fastboot connectivity.
So with the above in mind I believe ADB is installed correctly on the PC.
Anyone have any thoughts what I've missed (screwed up) or why the replacement Sensation is invisible to the PC via ADB ?
gol_n_dal said:
Hi,
My original Sensation started dieing (backlight issues I think). I successfully returned it to standard with S-ON prior to returning it to Vodafone.
Today the replacement turned up, so S-OFF is the first step ) So a few checks first and......
Anyway, "adb devices" seems not to be able to see the new phone.
i) USB Debugging enabled on the phone;
ii) PC sees it perfectly as a storage device;
iii) "adb devices" sees my Desire perfectly;
iv) Yesterday on the same PC I installed RUU on the old Sensation, then reset CID then finally changed it back to S-ON, the final two rely on adb/fastboot connectivity.
So with the above in mind I believe ADB is installed correctly on the PC.
Anyone have any thoughts what I've missed (screwed up) or why the replacement Sensation is invisible to the PC via ADB ?
Click to expand...
Click to collapse
Hi,
Might be worth trying to re-install the HTC DRIVERS
Thanks,
I'd already started downloading the latest version of HTC Sync for its drivers.
Weird though how the old one worked fine and this is invisible.
I'll update if it works.
EDIT: Meant to add that I noticed the Desire was recognised in Hardware/Devices, however, the Sensation wasn't.
How about fastboot?
Did you try fastboot devices
With phone connected to pc from bootloader? (phone should read fastboot usb after this)
Sent from my pyramid.. Through blazing fast sonic waves
Turns out the replacement phone was goosed before I had a chance to screw it up myself
Never appeared in Hardware/Devices properly, HTC Sync didn't work, Vodafone asked me to install latest OTA. Then I discovered WiFi was also screwed, the WiFi icon never turned up in the notification bar...
So, Replacement for the Replacement is on its way.
Thanks folks.
Replacement , replacement phone turned up today and it worked perfectly first time with both ADB and WiFi.
The only slight down side is that it's running 3.32.161.11 so HBOOT 1.27.0000. The first replacement was 1.17.0006 (so easy revolutionary S-OFF). 1.27.0000 seems a little more hassle and looks like I need to go via http://htcdev.com/bootloader to start with, I'd hoped to avoid that. At least this phone is working properly.
Thanks for the suggestions folks, all my issues came down to a broken replacement phone
Colin
P.S.
Talk about consistency, the first replacement turned up with no back and an 8GB uSD card. The latest one came with a back and no uSD card
gol_n_dal said:
1.27.0000 seems a little more hassle and looks like I need to go via http://htcdev.com/bootloader to start with, I'd hoped to avoid that. QUOTE]
Before you go doing that, the HTC unlock method can create other roadblocks for you down the road. Make sure to read up on it first.
I never had to root the 1.27 version so I'm not intimately familiar with the problems the HTC method causes, but I'm constantly seeing issues about things that work quirky later because of it, or other workarounds you need to do to to overcome the HTC unlock.
The short circuit thing is goofy, but it supposedly works well and gives you a truely unlocked bootloader.
Click to expand...
Click to collapse
gol_n_dal said:
Replacement , replacement phone turned up today and it worked perfectly first time with both ADB and WiFi.
The only slight down side is that it's running 3.32.161.11 so HBOOT 1.27.0000. The first replacement was 1.17.0006 (so easy revolutionary S-OFF). 1.27.0000 seems a little more hassle and looks like I need to go via http://htcdev.com/bootloader to start with, I'd hoped to avoid that. At least this phone is working properly.
Thanks for the suggestions folks, all my issues came down to a broken replacement phone
Colin
P.S.
Talk about consistency, the first replacement turned up with no back and an 8GB uSD card. The latest one came with a back and no uSD card
Click to expand...
Click to collapse
you can use my soff guide ( link in my signature ) and avoid htc-dev unlock ..but remember wire trick my way is bit difficult
Thanks,
I found a coltrolbear/JuopunutBear guide, so all sorted now: S-OFF, rooted, custom recovery and SuperCID. The only issue was the timing with the paper clip, it took a few attempts. Still a lot more hassle than just using revolutionary.io....
Just need to have a look around now at the latest ROMs. I see there is a Jelly Bean one floating around.
I rooted my HTC One X 3 days ago and installed ClockworkMod recovery.
I then used CWM to backup the stock ROM which I moved (not copied, damn it!) onto my desktop via USB. I also made an online backup with "Backup Pro".
Then I downloaded and installed Cyanogenmod 10.1 ROM using ADB.EXE and flashed the associated boot.img. It worked ok but crashed and rebooted the phone every hour or so, constantly. After half a day I gave up on that and looked around for something else. I made a ROM backup with CWM and then downloaded Viper Venom on the PC and copied the zip file and boot.img onto the phone. I loaded the ROM and boot.img, using adb.exe - same as before.
After rebooting into Viper Venom the HTC splash-screen appeared and a groovy animated robotic snake moved across the screen for 3 seconds before locking up the phone and rebooting. Now it was in an endless loop rebooting every 20 seconds or so.
So I restored the Cyanogenmod rom but forgot to restore the boot.img file, and rebooted. This time once the OS loaded and I unlocked the screen this error popup appeared: "Unfortunately, the process com.android.phone has stopped". Once I dismiss the popup it re-appears 0.5 second later, and repeats endlessly.
Then I remembered I didn't flash the boot.img so I rebooted into Recovery again but then suddenly I lost computer connection via the USB cable. Now, no matter what I try "adb devices" just won't find the phone. In Windows Device Manager the phone appears as "My HTC" under "Android USB Devices". An unknown icon also appears under "Other Devices" called "Android Phone".
Many months ago I installed the HTC windows drivers and have been connecting to the phone on countless occasions so I don't believe it's a PC driver issue but something in the last boot.img or ROM on the phone that has corrupted the phone.
I have googled non-stop for the past 2 days throughout XDA and other sites and the solutions offered to anybody having issues with rooted ROMs is to use ADB via USB or TCP/IP and do this and that. My problem is that nothing will talk to the phone over cable or wifi, so my hands are tied to make any changes.
Does anyone have any ideas what I can try to re-enable the USB connection? I've tried 2 newish micro-USB cables in all of my Windows7 64-bit USB ports (I heard USB 3.0 ports can cause problems so tried the 2.0 ports), and I've repeated everything on a new Windows7 build 32-bit desktop but everything displays the same in the Device Manager and ADB never connects.
I have a dual-boot Ubuntu desktop I haven't tried yet. Is it possible that would have more luck?
Any ideas anyone.............?
Try installing twrp recovery. Cwm does not have official support for our phone and causes issues
Sent from my VENOMized HoxL
Try reinstalling your HTC drivers.
Fixed!
area51avenger said:
Try installing twrp recovery. Cwm does not have official support for our phone and causes issues
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
iElvis said:
Try re-installing your HTC drivers.
Click to expand...
Click to collapse
Thanks for both of your suggestions. I have uninstalled and reinstalled the HTC drivers countless times but the device can never be seen. Re. trying TWRP, well without USB access and a phone I can't use, loading anything else is impossible.
HOWEVER! I stumbled on some software called PDANet last night and installed that on my laptop. Immediately ADB was able to see my phone again (MAJOR YAY!!!). I rebooted into Fastboot USB and low and behold, fastboot could now see the phone too! I was back in business and ran fastboot flash boot boot.img to install the Cyanogen boot image. Within 5 seconds it was done and after a reboot the relentless error message was gone for good!
I have since copied the stock rom files back onto the phone via usb (it now appears again in My Computer so I just drag and dropped them) and then ran a CWM Restore. Then flashed the boot.img and rebooted. My old stock rom appeared and everything is 100% as I left it.
I have learned so much about root/rom/recovery over these last 4 nights trying to recover the phone so it's not wasted, although I'm sure I cut a few days off my life worrying whether the "brick" would ever go again
This morning I installed CleanROM from ScottsRoms as I like many of the HTC apps, but I just want better battery life. For some reason it seems I have got a completely stock rom now which is weird but I've asked for advice on the Scotts Rom forum.
Does anybody have advice regarding another suitable rom that has better battery life but still runs some of the HTC stuff like these apps: Email, Car Dock, Messages? I also love the HTC One X keyboard - nothing else I've tried comes close to it, so ideally a rom that retains that would be a major plus.
I tried Viper/Venom 3 nights ago which is when all this went crazy. It was stuck in an endless loop which no amount of clearing cache/data/resets/fix permissions could fix so I'm reluctant to try that again.
Many thanks for any advice!
Make sure your dev settings are turned on and make sure usb debugging is turned on
And for the Rom recommendation you just have to try yourself per the rules we cannot say due to equal competition
Buut if your looking for battery life cough* bulletproof kernel *cough
Sent from my HTC One X using Tapatalk 2
Kole_Ackerson said:
Make sure your dev settings are turned on and make sure usb debugging is turned on
And for the Rom recommendation you just have to try yourself per the rules we cannot say due to equal competition
Buut if your looking for battery life cough* bulletproof kernel *cough
Click to expand...
Click to collapse
Thanks for the tips Kole. It's all good now. As for the ROM question, I didn't realise recommendations weren't allowed, whoops
I did coincidentally stumble upon a kernel called bulletproof after reading your post , and chose the fastboot flash boot method since my phone is S=OFF - as per their recommendation, but sadly the phone wouldn't boot after that. Not sure if I should have performed any other actions (cache deleting etc?) but I returned it back to the original boot.img and all is well again.
I've since restored a CyanogenMod 10.1 image and is working ok now. Days ago when I installed it, the phone would crash when it was locked. I think I have identified the culprit to be the "2X" battery saver app I installed on it. When that's not active it doesn't crash so I've uninstalled it now.
Would it be fair to assume I should get better battery life day to day with CyanogenMod than the stock HTC rom? Hope so.
thanks
gpfnz said:
Thanks for the tips Kole. It's all good now. As for the ROM question, I didn't realise recommendations weren't allowed, whoops
I did coincidentally stumble upon a kernel called bulletproof after reading your post , and chose the fastboot flash boot method since my phone is S=OFF - as per their recommendation, but sadly the phone wouldn't boot after that. Not sure if I should have performed any other actions (cache deleting etc?) but I returned it back to the original boot.img and all is well again.
I've since restored a CyanogenMod 10.1 image and is working ok now. Days ago when I installed it, the phone would crash when it was locked. I think I have identified the culprit to be the "2X" battery saver app I installed on it. When that's not active it doesn't crash so I've uninstalled it now.
Would it be fair to assume I should get better battery life day to day with CyanogenMod than the stock HTC rom? Hope so.
thanks
Click to expand...
Click to collapse
you don't need to fastboot kernel after s-off. bulletproof kernel doesn't work with aosp roms only sense roms.
bulletproof question
DvineLord said:
you don't need to fastboot kernel after s-off. bulletproof kernel doesn't work with aosp roms only sense roms.
Click to expand...
Click to collapse
Whoops, I got it wrong. The phone is S-ON and I wrote S-OFF in above post. I followed the instruction in this thread on xda:
http://forum.xda-developers.com/showthread.php?p=38727496
INSTALLATION
1. Install zip from TWRP Recovery
2. Reboot!
S-OFF recommended for easy installation
hboot 1.14+ and S-ON:
The installer includes a method to flash the boot.img for S-ON devices using hboot 1.14 or higher;
however, some people still have difficulties. If it doesn't work:
1. extract boot.img from the zip, reboot to bootloader and do:
fastboot flash boot boot.img
2. If you had previously installed ElementalX or Beastmode, be sure to run the installer to get the correct wifi module.
First boot will take a while. Let it load all the way, then let it settle in for a few minutes, then reboot again.
Click to expand...
Click to collapse
I followed what's mentioned under this heading: hboot 1.14+ and S-ON since my phone spec. meets both criteria:
Endeavoru PVT SHIP S-ON RL (what's RL stand for???)
HBOOT-1.36.0000
CPLD-None
MICROP-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: disabled
MODEM PATH: OFF
Nov 16 2012, 18:32:39
I think I applied it when I still had ScottsRoms CleanROM onboard. When you say it only works on sense roms, do you mean the stock HTC ROM or should it also work on a cleanROM which contains lots of sense stuff? Sorry for the newbie questions, I find it difficult to get answers online to the most basic of android/rom/root questions.
Thanks for your time guys!
this is the evita forum not the endeavoru forum.
what phone do you have? this is probably not your forum.
DvineLord said:
this is the evita forum not the endeavoru forum.
what phone do you have? this is probably not your forum.
Click to expand...
Click to collapse
As it says in the first line of my post: HTC One X. I thought endeavoru=OneX and evita=OneXL?
According to the thread path, this forum is for both phones:
> AT&T, Rogers HTC One X, Telstra One XL > One X Q&A, Help & Troubleshooting > [Q] Lost USB/ADB connection after ROM change > Reply to Thread
Thanks for calling me an idiot too, nice sign-off, not.
gpfnz said:
As it says in the first line of my post: HTC One X. I thought endeavoru=OneX and evita=OneXL?
According to the thread path, this forum is for both phones:
> AT&T, Rogers HTC One X, Telstra One XL > One X Q&A, Help & Troubleshooting > [Q] Lost USB/ADB connection after ROM change > Reply to Thread
Thanks for calling me an idiot too, nice sign-off, not.
Click to expand...
Click to collapse
AT&T and Rogers both sell a model that they call the "One X" but is really a One XL (evita) just like Telstra and other carriers sell. Any One X not from AT&T or Rogers is an endeavoru
You need this forum instead
Oh I see. On this side of the world we don't have AT&T and I've never heard of Rogers. It must be a US thing only.
Oh well, discussion is over anyway, problem solved, thanks to all for your input.
Sent from my HTC One X using Tapatalk 2
Hey XDA-People!
I'm having trouble with my HTC One S S3.
So here's what I already did :
I unlocked bootloader with htc-dev.
I flashed custom recovery (twrp).
I tried to install cm10 but here is where the problems started.
I didnt do the wipe before I flashed the rom because i had done multiple wipes before while trying to install other roms and thought it wouldn't matter (I was wrong).
When I tried to boot I got stuck in the cm animation.
So i tried to reinstall with a wipe but my internal sd card didn't mount anymore.
I looked up how to fix that and kinda did. I have access to my sd card in the recovery again.
But now theres another problem:
Since i dont have any working rom to boot into i tried to push a rom via adb but now my device doesnt show up anymore.
I followed this guide : how-to-solve-adb-device-not-found-error on dominantwire dot com (cant post link)
I have HTC Sync installed and adb worked before so i should have the drivers installed correctly right?!
In my Bootloader it says :
*** UNLOCKED ***
VILLEC2 PVT SHIP S-ON RL
HBOOT-3.01.0000
RADIO-16.15.20.29_M
OpenDSP-v11.6.0.2235.00.0304
eMMC-boot
Apr 21 2014,21:30:53:-1
FASTBOOT USB
Can anybody help me to get my device to work again?
EDIT 1 : OK my adb is working again
but im getting permission denied if i try to push a file
also the command "su" is not being found
EDIT 2: I managed to get past the permission error and adb push seems to work
but the file i have pushed does not show up if I want to install in in recovery
Don't know if for Ville C2 is the same but for the S4 you should not have HTC Sync instaled, it messes up with ADB. You should have only the drivers not the application installed.
Sent from nowhere over the air...
ok i have uninstalled htc sync
are the drivers that come via windows update fine?
harlequinnn said:
ok i have uninstalled htc sync
are the drivers that come via windows update fine?
Click to expand...
Click to collapse
They should be fine for connecting as MTP device but for ADB you should either install generic ADB drivers (they're in Android SDK) or you can use the drivers installed by HTC Sync. The program also install drivers. There is also a thread that contain the drivers, look for a thread in dev section and it's title should say something like "latest ADB drivers" or something like that. I'm on mobile right now so I can't search easily
NOTE: The thread I was taking about is in the Ville S4 section, I am not 100% sure that it'll work for you (but it could). Otherwise look in the Ville C2 section for a similar thread
Sent from nowhere over the air...
Rapier said:
They should be fine for connecting as MTP device but for ADB you should either install generic ADB drivers (they're in Android SDK) or you can use the drivers installed by HTC Sync. The program also install drivers. There is also a thread that contain the drivers, look for a thread in dev section and it's title should say something like "latest ADB drivers" or something like that. I'm on mobile right now so I can't search easily
NOTE: The thread I was taking about is in the Ville S4 section, I am not 100% sure that it'll work for you (but it could). Otherwise look in the Ville C2 section for a similar thread
Sent from nowhere over the air...
Click to expand...
Click to collapse
OK thx a lot everybody
I installed the correct drivers and got cm 10 to work.
But with one problem solved another one came up
Everything seems to work except i cant connect to a mobile network.
If I search for networks i just get an error.
I read something in other threads about "borked radios" or something like that, yet I have no idea how to fix it.
I'm seriously starting to get desperate about this whole thing.
Hi there all, I've got both an old HTC Desire HD and Incredible S which I thought I might try to root, install custom ROM etc to try make them a bit more useable and enjoyable as they are very slow and quite unusable. My mother was also using the DHD until it became too slow and laggy for her to use, also battery life deteriorated even after I bought a new battery. There are a couple of dilemmas I am facing however not being able to use fastboot is the biggest and most important one so far. If I can solve this then I may be able to solve the others myself so I thought I'd see if there was anyone who could help me. I've been on this for hours, days, I don't know what happened but I'll tell you my story.
First of all, my DHD has been rooted previously and I installed CM11 onto it, however that ROM keeps giving me processes that stop continuously after installing the associated Gapps file. The incredible S is NOT rooted yet, I haven't been able to unlock bootloader because that also won't connect via fastboot. I ALSO have an HTC M7 which I recently unlocked, rooted and installed Venom 9.0.0 ROM without any problems. I'm not sure what is wrong with these two. I know there are a lot of posts on this topic online but not one of them has helped me in the slightest.
I am not too sure exactly what details you might need, but I'll start with these:
- I am running Windows 10 on my desktop, with USB 2.0 and 3.0 ports available.
- I have a myriad of HTC cables and other micro USB cables as well to use.
- I have a couple of microSD Cards available.
- I have installed HTC Sync Manager for HTC drivers and uninstalled it as requested by many threads online.
- I've downloaded a lot of other drivers, ie HTC driver installer, universal drivers from Koush, and Google drivers.
- I have SDK tools from the AndroidSDKSlim.rar archive.
I've currently deleted and uninstalled everything because I want to start again hopefully with some assistance. I've downloaded Devmanview to delete and uninstall anything that said HTC, Phone or Android to start fresh.
My HTC Desire HD bootloader details are as follows:
*** UNLOCKED ***
ACE PVT ENG S-OFF RL
HBOOT-2.00.2728
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011, 19:06:24
I am aware there is an hboot update, I have the hboot update by behtash.bat file from the HBOOTUpdate_kit.rar archive but I also can't update that without fastboot)
Currently it has PD98IMG (Philz Touch 6.25.0 For HTC Desire HD) recovery, prior to that I had TWRP.
I was able to install that via my SD card
Now when I plug the phones into the computer while they're on, it picks them up on Device manager, and using ADB DEVICES turns up with their serial numbers. I can command them to ADB REBOOT BOOTLOADER to fastboot, I hear the windows sounds for connecting and disconnecting USB's then I get the windows does not recognize this device message. Please try plugging in again etc. When I look at my device manager it comes up in Other devices as Android 1.0 in device status it says:
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver.
If I try to search automatically it fails. If I go to Update driver>Browse my computer>Let me pick from a list of device drivers on my computer it comes up in the box both Android Device and Android USB Devices. If I click the Android USB Devices there are no supported drivers. If i click Android Device it gives me 3 SAMSUNG Android ADB Interface versions :S:S
I should probably state that I'm trying to reflash a TWRP recovery for aceopt so I can install the CM12.1 or CM13 ROMs on my DHD.
My brain really hurts from all this... If anyone has any ideas or suggestions for me to try, please... Any help would be greatly appreciated. Also If you need any more information let me know I'll be happy to provide. Thanks in advance!!