Can anyone help me figure this problem out? I have tried everything now and the CID is still corrupt.
I don't think IMEI Check can help since the CID is corrupt, there has to be another solution.
My CID reads:
HTCSF kEØ(HTCE
Nobody has any insights into this. There has to be some way to reset the cid from BL using mtty.
I had the exact same problem. Believe it or not the cause was a flaky USB port on my computer. I lost a lot of hair during the three days without a solution..
After switching ports, I ran a full general/shipped ROM update. I received the "Invalid Vender ID" error message, but (as per Wiki instructions), I reran the update utility without resetting the device... (see http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems).
After getting back to a baseline ROM, I was then able to run the SIM/CID unlocker successfully, and install any ROM I want
I hope this helps you...
Related
I've seen a few posts now with people having issues with the 1.09 SPL and info 2 returning CID timeout followed eventually by HTCSF kEØ>HTCEUSB.
My M3100 sits at the Windows mobile screen, and doesnt progress. Also get the NO GSM message in the bootloader.
Trying to upgrade (any version) using an activesync connection always fails with device not found errors.
Trying to upgrade (any version) using a bootloader connection usually fails with an invalid country id (244 error?).
Using the japanese downgrade method also gives a country id error.
Using POFs radio only upgrade has no effect (as expected as ipl >1.04).
Using imea-check's tools always gets an invalid device message - apparently due to the required commands not being available.
Incidently - I'm sure that I've only had this problem since running imea-check unlock, however they insist that their software could not do this and are blaming a harware fault... hmm, doubtful to say the least.
Has anyone had any success with reviving the device from this state - I'd be interested if POF's (forthcomming?!) unlock tool will work.......
Any suggestions... it sounds like there's enough "bricks" out there to build a wall.......
Oh, and also tried troubleshooting stuck at Windows Mobile screen as in Wiki, no effect.
I have the same problems....
I take a hard decision. i take it to assistance support, because I was loosing too much time in following all the instructions.
i just hope they can solve my problems in 15/20 days (as they told me) in the cheaper way possible.
ibanyard said:
Has anyone had any success with reviving the device from this state - I'd be interested if POF's (forthcomming?!) unlock tool will work.......
Click to expand...
Click to collapse
It will only work if you are able to boot into WinCE, if you are stuck on wince splash screen it will not
Thought as much.....
Going to send back to htc or orange for "repair".....
I was flashing my tytn with the new rom with bootloader 1.09 after 8% the usb cord came out and now my tytn is dead its stuck in bootloader mode..spl 1.09...please help
I am also in this boat, except my usb cord didn't fall off, it just stopped updating at 6%.
Connect to the device using mtty and type info 2. If you're CID is corrupt, then you're out of luck just like me.
It seems that the only way to fix this problem is to send the unit back to a service center and get the main board replaced. Unless anyone else has any other ideas. In BL 1.04 you could bypass the CID check but in 1.06 and 1.09 that bug has been fixed.
Great job HTC, you really messed everyone up now, I hope you're ready to start replacing some board on account of your ignorance to create a sufficient backup routine. I guess this means less money of new development and less devices from HTC in the near future.
Because you're in bootloader mode, you might be able to flash the 1.04 bootloader downgrader in; which would then allow you to re-flash any firmware.
Nope, even in boot loader mode I can't go back to 1.04. It doesn't recognize the CID and keeps saying invalid vendor id.
The only possible fix I can see is if someone hacks the hermes and finds a way to cook a rom and not check the CID. Otherwise, it's a full board replacement.
Somehow there has got to be a way to "Bypass" the CID check.
What I was trying to say, if you use the IMEI-CHECK downgrader it will bypass the CID checking enough to get you back down to 1.04?
Yes. Imei-check downgrades your bootloader to 1.04
sn00x said:
Yes. Imei-check downgrades your bootloader to 1.04
Click to expand...
Click to collapse
But to run imei-check unlocker you need a running OS (it needs to transfer files via activesync to the device) and your IMEI should be not screewed while checking it from bootloader. Otherwise it will not work.
I've tried everything possible to get out of bootloader mtty says my cid is corrupt.does anyone know a number for the service center
depends on your country, go into htc website and look at it:
http://www.htc.com
Pof you are correct. The CID is completely corrupt, the radio sectors have a bad record, and the phone can't boot past the windows mobile splash screen. So the only way we can fix this problem, is to hack the flashing of the rom to not check the CID at all. If this can be done, then we're in business.
On another note, I've been seen 1 of these problems arise every day now. Someone either pulls the usb cord or the flashing just crashes.
I think there is a serious enough priority to hack the hermes rom flashing now aside from crossbow. We really need some resources on this so that we don't ever have to go through these problems again.
In the words of Russel Peters (a famous Canadian comedian)... Pof, be a man, do the right thing. Hehehe.
pof said:
But to run imei-check unlocker you need a running OS (it needs to transfer files via activesync to the device) and your IMEI should be not screewed while checking it from bootloader. Otherwise it will not work.
Click to expand...
Click to collapse
But does that "other solution" which can't be posted here anymore bypass that requirement, as it runs through the bootloader and not activesync?
no it doesn't. The update still checks the CID before updating.
And it also needs activesync to transfer the fake bootloader to the device... remember it starts with M3100v3cUnlock.exe too....
Ooh, forgot about that bit .
I have tried many times to upgrade the Rom Image on my HTC Tytn (Cingular 8525) with no success. I am getting a 260 error with the program located at this link...
http://forum.xda-developers.com/showthread.php?t=293665
I did first run the unlocking application to unlock both SIM and CID before running the upgrade.
I followed all the steps exactly and have had no success...
The following might be effecting my attempt:
I am running my pc on Vista
I am syncing with Windows Mobile Device Center
I have tried to solve this problem for about two weeks. Can anyone help me?
Mrvanx has a guide on how to prepare Vista for flashing, you can find it here.
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Same problem
compwiz2008 said:
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Click to expand...
Click to collapse
Same problem here trying to change the radio version after changing the bootloader........
Connection alwayse lost just as said above.
Any help will be appreciuated
justx24
Use the RUU wrapper with the NBH file you want to upgrade.
I still have the same issue, even when using the RUU Wrapper and any nhb.
don't use vista
Ok, got one step furthur
I reached the point where the ROM Begins to update, which is VERY good...
The ROM update Reaches 1%, then waits for 20 minutes...
Then I get a 262 error and have to go through recovery, try again, with the same result.
i have same problem plz help thnx in advance
compwiz2008 said:
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Click to expand...
Click to collapse
Have you tried removing or adding a checkmark to the USB to PC in CONNECTIONS on your device? I remember having a similar problem when I installed Radio Rom 1.38 that my USB connection was lost with the pc . I am using XP when flashing so if you have no luck then do this on a XP machine.
Forgot to ask! What ROM are you trying to flash??
@compwiz2008 and ahmerpar
I read somewhere that running windows update will update WMDC........maybe give that a shot?
Maybe you can try to upgrade your ROM from your SD card.
Nope
Let me try that...
Still did not work
I'm probably going to just take my phone to a computer repair shop and pay them to deal with it, since I'm evedently doing something wrong.
Hey,
So, I've got a strange problem. I've bought my HTC TyTn a few weeks ago and I've allready used the HTC_Hermes_SIM_CID_Unlock_v3 to SIM unlock my phone. Everything went fine and I was very happy until the day of releasing WM06 for my device. I've downloaded again the HTC_Hermes_SIM_CID_Unlock_v3 and tried to remove CID to make my device superCID. But now it seems it just doesn't work properly or maybe I'm doing something wrong. Each time the RUU starts ( after softreset, because of confirming 'yes' for sspl, it starts in bootloader ) it can't connect to the device... I don't know what to do, it seems that I do something wrong, but I don't have any idea what
I thougt that maybe just don't need to change the radio, and everything I need to do is to copy the Herm_Unlock_v3, run it and select to remove CID lock. Tried that way but don't have any idea how to check if it's superCID already. Anyway I tried to upgrade to WM6 after that, and It has same problem. RUU just can't connect to my device when it's in bootloader.
Am I doing something wrong ? Somehow it just can't connect to the device now, but at the first time it was perfect. If anyone knows the answer, please report me
sry for my english
I would be happy if someone could help me
Which RUU are you using? Which SPL is on your phone. You may not need to connect in bootloader. If you are using the custom RUU and a "Hard" SPL - then try connecting with the phone up in regular mode.
Found the solution. I think that my USB port in PC is corrupted. Changed the port and everything went fine
Hello all,
I got a friend of mine who came to me with a device-password locked Hermes, which password he cannot recall (actually his girlfriend...). I said I would be willing to give him a hand to unbrick the device. The problem is that I cannot install any ROM on the device, coz I got an error connection right after the screen goes white and the percentage count should normally start.
So I put the Herm in Bootloader (spl-1.06) and try to flash the OliPro Bootloader. The procedure goes correctly until the step where the upgrade itself should begin, counting from 0%... here, I got:
ERROR [262]: Update error: communication error.
I also tried to flash a ROM directly, but since my Bootloader is 1.06, I didn't find a CID match ROM, so it also failed. The Herm is now not bricked, but it stays at the password input screen, so cannot enter windows properly.
Any help on this?
Thanks,
Ionutz
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
agovinoveritas said:
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
Click to expand...
Click to collapse
yes, i grih you,and normally i wouldnt even try to do such thing, if it hadnt been for a friend of mine which i know.
besides i would like to learn more stuff about my Herm and this is one thing I havent seen discussed here, although i keep reading xda forums for such info.
just found the solution: i flashed another ROM with same CID since my BL was 1.06, but with BL 1.04. After that, I managed to flash any other ROM and automatically upgrade the SPL to 1.10 or 2.10 Oli accordingly.
If any of you interested and dont get the short explanation, PM me.
cheers,
Io, owner of 2 kicking TyTn's
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
mrvanx said:
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
Click to expand...
Click to collapse
I know the details about BL 1.04 vs 1.06, thats why I flashed a BL 1.04 ROM, but with the same CID QTEK_001, or smth.
I have to admit though that I never ever thought about doing a simple hard-reset. I guess it would have been to easy, I jumped to more complicate scenarios. Thanks for the help anyway, i gotta learn that.
Thanks mrvanx, glad I read down the whole thread to the part about a simple hard reset working. I lent my 8525 to a friend, thinking he might be interested in buying it, then he didn't have the money, and after I listed it on ebay today, I charged it up to flash to ATT stock, found it password locked, called my friend a few times just getting his voicemail, so tried flashing, and it said the Hermes wasn't connected to the PC...
I figured there would be a solution here at XDA..and POOF, like magic here it is!
So yes, all I had to do was a hard reset, tested and it works, and it was simple, so thanks again mrvanx, although this thread is very old, glad I found it LOL!