This is my first post, though I've been pouring over the forums everyday for a few weeks to try to get up to speed. You may notice that my join date is quite recent, but I only recently signed up! I finally replaced the broken usb port last night and then flashed wm6 from htc onto my hermes. This morning I've been trying to install Hard-SPL-V7, which failed, then I successfully ran the SIM/CID unlocker, and finally tried to run HERM-SSPL which failed. What seems to be happening is that after syncing and running RUUWrapper.exe the device goes to the bootloader screen:
Code:
HERM100
IPL-1.04
HERM100
SPL-2.03
But doesn't do anything else, and then the PC reports a disconnect error. I think that the device is supposed to reboot after going to the bootloader, but it doesn't. I have noticed that shortly after going to the bootloader, it flashes a white screen with red text, and then returns. It's so fast I can't read the text. After the error prompt on the pc (vista), I soft-restart the device and it returns to the today screen where everything appears to be normal.
What am I doing wrong? I read the guide for installing the hard-spl. RUU_signed.nbh is in the same directory on the pac as RUUWrapper.exe. The device isn't bricked. I'm stumped.
I appreciate any and all help. I know it's painful to keep answering the same questions over and over again, so I promise that I've been searching for an answer in the wiki and on the forums.
Also, thank you for these utilities, roms, forums, etc. It's amazing that so much is being accomplished by apparently so few.
***UPDATE***
More information is always better...
After wmdc is connected I run RUUWrapper.exe
I check Force using SSPL and go through the prompts...
Code:
From:
Image Version : 3.62.502.3
To:
Hard-SPL-2.10
The device goes to the SSPL as opposed to the SPL, I think, and displays this:
Code:
HERM100
IPL-SSPL
HERM100
SPL-1.09.ds
Then the pc prompts 'Verifying ...'
The device stays one the bootloader screen, and then the pc prompts:
Code:
ERROR[260] UPDATE ERROR
When I soft reset the device, it comes up to the today screen, and going to the bootloader displays this:
Code:
HERM100
IPL-1.04
HERM100
SPL-2.03
OK, I think I know what's going on.
I thought that I had gone through installing the vista x64 drivers from the guide but I hadn't. It doesn't matter much though as vista x64 really doesn't like unsigned drivers. I've not been able to get past that. So the issue was that vista x64 can't sync with hermes in bootloader mode. OK, fine, I guess that I'll be working with XP. Why oh why did I decide to try vista x64...
Has anyone else found a solution to this?
mangiaculo said:
OK, I think I know what's going on.
I thought that I had gone through installing the vista x64 drivers from the guide but I hadn't. It doesn't matter much though as vista x64 really doesn't like unsigned drivers. I've not been able to get past that. So the issue was that vista x64 can't sync with hermes in bootloader mode. OK, fine, I guess that I'll be working with XP. Why oh why did I decide to try vista x64...
Has anyone else found a solution to this?
Click to expand...
Click to collapse
Id stay clear of vista when trying to do flashing stuff....it REALLY just messes with all aspects of the process, regardless of if the WMDC is up to date.
Best thing to do is to get 32bit XP fired up and use that its just so much easier and everything else you use wont have to be patched/tweaked to behave on XP. LOL my vista config guide should really be a sly 'Uninstall vista, format and install XP SP2......guide'.
when you ran the SIM/CID unlocker, did you run it from your Storage card or did you use your usb to install? i think i had a similar issue. it would always give me the error 260. First, i sim/cid unlock my phone via storage card and it said unlocked and everything, but it still gave me the error 260. then i decided to just try to SIM/CID unlock via USB and when i did that, i didn't get the error 260 but instead it updated to Hardspl v7. hope that makes sense.
mrvanx said:
Id stay clear of vista when trying to do flashing stuff....it REALLY just messes with all aspects of the process, regardless of if the WMDC is up to date.
Best thing to do is to get 32bit XP fired up and use that its just so much easier and everything else you use wont have to be patched/tweaked to behave on XP. LOL my vista config guide should really be a sly 'Uninstall vista, format and install XP SP2......guide'.
Click to expand...
Click to collapse
Thank you both for the responses. I ended up going home and flashing on my xp machine. Our new work machines are 64bit and I had several options for os, and silly me, I thought vista x64 sounded like a good idea. It's been a challenge.
Anywho, hardspl is installed! I also flashed the black 3.0 wm6 rom, though my keymapping is strange for the additional key functions. I'm off to research an answer on that. Thanks!
Would it be possible to install virutal PC on vista 64-bit and just run a virtual instance of 32-bit xp? I guess my real question is whether it is possible to flash the phone from a virtual pc.
-thanks.
hi,
Yes, it is possivel , i do it, i recomend you using VMware soft, because virtual pc doen't have USB support.
If anyone could spare a moment that would be most appreciated. I have searched for hours and my laptop is crying under the "weight of a thousand tabs" at the moment and have finally decided that my problem is not going to be solved by more forum browsing. Luckily I have all the links to tutorials I was following so I can pinpoint exactly where things went wrong.
The carrier: Virgin Mobile
The problem: Stuck in bootloader, no options working. Recovery and factory reset both yield nothing. RUU fails with error 170.
The History: I decided I was going to try and root my phone today. That actually worked via stock. Followed a guide that showed me how to unlock the phone (using HTCDEV) and pushed TWRP as my recovery.img. I flashed the stock ROM and had root access. Then I was following another guide to obtain S-OFF. It said that I should flash SetMainVersionLow via my recovery and the next step was to run "fastboot oem lock" which worked. Then it told me to run the RUU.exe which simply gives me error 170 "USB Connection Error". I was running adb and fastboot commands early from this same machine, and nothing changed from the point of "fastboot oem lock" and running the RUU, though now my device won't even show up in fastboot or adb.
Any help would be most appreciated. I'm 12 hours in surfing on the web for solutions and have got nothing. I have learned that this site rocks (just looking through posts and the general responses people get) and you can bet and help some stranger will give me on the internet will be paid forward five times over. I'm a computer major in school so I am well versed with technology but as you can tell my rooting experience is non-existent. Thanks all.
More info:
Windows 8 64-Bit
Bootloader displays the following:
*** RELOCKED ***
*** Security Warning ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
RADIO-1.09.00.0108
OpenADSP-v2.6.0.226.00.0217
eMMC-boot
May 17 2012,15:06:44
EDIT: I have, through restarting both laptop and phone a few times, obtained fastboot. My RUU now proceeds past where I would encounter error 170, but still fails. When I unplug the USB it says HBoot older. Anyone have a "newer" RUU?
fastboot getvar cid = SPCS_002
fastboot getvar mainver = 1.00.000.0
I was trying to use:
RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radio_1.06.00.0426_NV_1.53_144_release_262287_signed.exe
I also tried:
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
'
which gave me the error "CID incorrect"
I have a sprint htc evo 3d and have tried everything possible to unlock this damn thing. I'm on windows 8.1 which i think can be part of the issue but have tried it in ubuntu 14.10 on a vmware image.(detects the phone as a device).Have htc sync installed with the drivers etc etc.The main issue seems to be it can't find the driver when i put it into the 'bootloader mode' and set it to fastboot. Unknown driver says 'My HTC' with these hardware id's:
USB\VID_0BB4&PID_0FF0&REV_0100
USB\VID_0BB4&PID_0FF0
I have tried every driver possible i could find, including disabling whatever the driver verification in windows 8.1 and adding those id's to a .inf file that was supposed to work.Nothing happens.The phone has ICS and the bootloader comes up with this:
shooter xc ship s-on RL
hboot-1.58.0000
Have tried the htc dev site to unlock it but end up with the same issue. Tried 2 different cables,but nothing.
I have no clue what to try at this point. Is it me or does windows 8.1 really hate the HTC evo 3d? Idk what else to try but maybe someone here has an idea what to do next.thanks
jake20fc said:
I have a sprint htc evo 3d and have tried everything possible to unlock this damn thing. I'm on windows 8.1 which i think can be part of the issue but have tried it in ubuntu 14.10 on a vmware image.(detects the phone as a device).Have htc sync installed with the drivers etc etc.The main issue seems to be it can't find the driver when i put it into the 'bootloader mode' and set it to fastboot. Unknown driver says 'My HTC' with these hardware id's:
USB\VID_0BB4&PID_0FF0&REV_0100
USB\VID_0BB4&PID_0FF0
I have tried every driver possible i could find, including disabling whatever the driver verification in windows 8.1 and adding those id's to a .inf file that was supposed to work.Nothing happens.The phone has ICS and the bootloader comes up with this:
shooter xc ship s-on RL
hboot-1.58.0000
Have tried the htc dev site to unlock it but end up with the same issue. Tried 2 different cables,but nothing.
I have no clue what to try at this point. Is it me or does windows 8.1 really hate the HTC evo 3d? Idk what else to try but maybe someone here has an idea what to do next.thanks
Click to expand...
Click to collapse
To unlock your device you must have fastboot running.
To check this boot into bootloader and type "fastboot devices".
With that you should be reportet your device number, otherwise fastboot is not running/installed properly.
If you have problems to get fastboot running, download a linux live CD.
Maybe look here.
thanks!
Using the linux live cd seemed to have done it with no issues It pulled up the code from fastboot and put it in the htc dev website, and got the unlock key. Having some issues with trying to update the old 'superuser' app which i think is now through chainfire? idk. I installed it but wouldn't update the binarys for some reason. Flashed the root with this: su-2.3.6.3-efgh-signed.zip. Maybe i'll find a better version through searching through the forums. Thanks anyways for the help!
jake20fc said:
Maybe i'll find a better version through searching through the forums. Thanks anyways for the help!
Click to expand...
Click to collapse
SuperSU v.1_93
https://db.tt/z2oDb1ox
Okay so I have the SDK, JRE and all other tools available. Fastboot and adb commands work when the device is on and unlocked, but when I tell it to reboot to the bootloader, Windows 10 claims that it cannot identify the device and as such the "fastboot oem get_identifier_token" command from HTCDev (EMEA Version) does not do anything except hang at "waiting for device to respond"
I strongly suspect it's a driver fault however the 3.xx versions of the driver are not compatible with Windows 10 and the 4.xx versions simply do nothing when I try to run the exe.
Does anyone have any ideas? The device is new, stock and carrier unlocked (Thanks eBay!) but the stock OS is a bit yuck and I plan to use this ROM: http://forum.xda-developers.com/show....php?t=2526391
Any help appreciated!
Try to find a friend / family member with a Win 7 PC. I mod phones as a side job and keep a Win 7 PC just for stuff like this. I could never get fastboot to work on 2010-2012 HTC phones on Win 8+. Some people say it works for them, but Win 7 will work WAY better for this type of thing, trust me.
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,