Related
I was able to access the bootloader for 5 times using the softreset and holding the power button.
By the time I figured out how to use the patch to bypass it, it's too late.
It no longer boot to the bootloader.
Now it just by-pass the bootloader screen and goes directly to the T-Mobile screen.
I've tried everything . Hard cold reset. Hold power-on and softreset
numerous time without success.
Anybody knows of any other way to access bootloader?
Bootloader version 5.22.
Maybe the Bootloader has a malfunction.
You can try to fix the bootloader. In the XDA-Tools, there should be a little tool to fix it.....
Stefan
If you are referring to running from the command prompt:
"pnewbootloader bootloader_v5_15.b0"
It didn't work for me.
I cradle it and ran that command and this is what I got:
"
unable to find flash info offset, cannot disable bootloader writeprotect"
message.
Anything else I can try?
TIA
Chip
Yes, this program i´ve meant. WHich version are you using of this tool? There have been an update of it, about half of a year ago. Maybe you download again the XDATools of the ftp and retry it.
Stefan
Thanks, got the updated file and fixed my bootloader.
the version you are referencing to is included here in case anyone
else wants it.
"pnewbootloader_40116.exe"
Thanks to all the people working hard to bring us these features!
And a special thanks to "stefan" for bringing a great kitchen!
The machine by it's default is so "weak!".
Chip
Glad to hear all is working now again....
Stefan
Hello everybody - can anyone help me at this moment. I am right now sitting with my Hermes connected through USB. I was flashing the standard ROM with RUU_HERMES_HTC_WWE_1[1].35.255.2_1.35.255.102_1.08.00.10_SHIP. Unfortunately it stopped at 5% some half an hour ago. I prefer to ask you before disconnecting it. Please help!!!!!!!!!
OK, having no answer I decided to disconnect it and look for an answer. Now I know that I have a 1000 USD brick and no possibility to put it back to work.
I now suspect that the upgrade did not work properly because my device had a CID lock. That is quite strange however, because I bought it on the open market without any commitment to any GSM operator.
I am now stuck on the tricolor bootloader screen with SPL 1,09.
Basing on the post: http://forum.xda-developers.com/showthread.php?t=285157 - especially on the lines:
"1.09
You can't downgrade to bootloader 1.04 by flashing a Shipped ROM. However imei-check.co.uk is able to downgrade the bootloader.
There was a solution posted on this forum, but it was stolen from imei-check and was removed. If you are not willing to pay you have to wait until another solution is developed.
The RadioROM can't be upgraded. You have to downgrade to bootloader 1.04 to unlock your device.", despite seeing info on the website, I paid to imei-check the 20 pounds.
So far I only lost money, time and nerves trying to downgrade or "repair" my hermes. Nothing works. If anybody has any suggestions please share on the forum or PM me.
BTW I started the whole process with SPL 1,04.
Sounds to me like a flaky USB port which is why it stopped at 5%. Try another port in the rear of your PC and re-flash. Be sure to follow the mantra:
Windows XP, screensaver, powersave disabled
No other programs running.
i had a similar problem probably with the flaky usb port as Sleuth255 mentioned. trying with a different pc is another option if you have one and that was what i did with success.
im not sure about the hermes.. but i know on the wizard as long as you could get to the bootloader screen (the RGB screen) that your device isnt bricked yet.. i would follow the other suggestions about usb ports and using different pc's, i bet you can make your $1k work for you again
Try:
Go into bootloader by pressing down both the POWER button and SIDE OK together and using the stylus at the same time to press the RESET button at the bottom.
Make sure you have disabled the USB connection in ActiveSync, before trying to connect to the bootloader:
File --> Connection settings --> uncheck "allow USB connections"
Connect your USB-Cable
Download mtty.exe. Start it and connect to USB
When you see "USB>" Type "info 2". You should get: "HTCS" + CID + (4-byte checksum) + "HTCE". Remeber what CID you have.
Look for a Shipped ROM that matches your CID
Download and flash it using a different USB-Port or PC than the last time
Afterwards you will be able to use the file that you got from imei-check. The imei-check downgrader/unlocker only works if you've got a working operating system on your device.
After typing "info 2" in mtty.exe I get the following line
HTCSF kEŘ(HTCEUSB>
Which of those is the CID? I cannot find any matching one in the Wiki.
corrupted CID by wrong flash.
OK, I have now the confirmation of the diagnosis - as I was suspecting.
Can I now have some help in the solution?
Some people succeded with the method described as "problem 5" here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
but some others don't succeed and have a brick. Try the steps on the wiki, if you are not able to fix it this way, send it to repair centre.
Following the steps from point 5 of the given website, I only get the following lines:
USB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB>
USB>set le 1
USB>erase a0040000 c80000
HTCST ÚČŇHTCEUSB>
USB>erase a0cc0000 c80000
HTCST ÚČŇHTCEUSB>
USB>erase a1940000 640000
HTCST ÚČŇHTCEUSB>
USB>set le 0
USB>
Unfortunatelly nothing changes.
I've the same problem. I was flashing the HTC 1.18.416.1 1.18.416.101 1.14.00.10 but the process has stopped to 89 % and now the phone is in bootloader mode spl- 1.06 and don't enter in windows mode !!! My cid is HTCSORANG001a#USB> I hope that i've not a brick !!!
mtadeuszak said:
Following the steps from point 5 of the given website, I only get the following lines:
[...]
Unfortunatelly nothing changes.
Click to expand...
Click to collapse
Your bootloader is 1.09 and you'll not be able to flash anything because the CID will not match. Send it to service centre.
deika95 said:
I've the same problem. I was flashing the HTC 1.18.416.1 1.18.416.101 1.14.00.10 but the process has stopped to 89 % and now the phone is in bootloader mode spl- 1.06 and don't enter in windows mode !!! My cid is HTCSORANG001a#USB> I hope that i've not a brick !!!
Click to expand...
Click to collapse
Your phone is not trashed, but there is no rom matching your CID yet. You should have cid unlocked it before flashing a rom with BL 1.06.
Try to boot OS again using "set 14 0" (see wiki, "problem 4"), if that doesn't fix it (chances are it will not), then wait until orange releases a rom upgrade with CID "ORANG001".
I've try the procedure "Problem 4" but after "write nand success" and sr it don't start. My cid is always ORANG001 with spl-1.06
pof said:
Your bootloader is 1.09 and you'll not be able to flash anything because the CID will not match. Send it to service centre.
Your phone is not trashed, but there is no rom matching your CID yet. You should have cid unlocked it before flashing a rom with BL 1.06.
Try to boot OS again using "set 14 0" (see wiki, "problem 4"), if that doesn't fix it (chances are it will not), then wait until orange releases a rom upgrade with CID "ORANG001".
Click to expand...
Click to collapse
Please Pof try to help me. Where can i find that rom ? Thanks
You can't find it at the moment. It's not released yet
sn00x said:
You can't find it at the moment. It's not released yet
Click to expand...
Click to collapse
But you think that it will be available ? Thanks
Yes it will surely be released I think. But nobody knows when. Perhaps tomorrow, perhaps next year.
It bet it will be listed here when it's available.
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!
Hi guys
before, my htc tytn had a problem, it not recognize the gsm sim and no IMEI showed on informations of the PDA.
I supposed that it was a problem of radio rom, and I followed the instructions given on (http://forum.xda-developers.com/showthread.php?t=293665) to unlock and update my radio rom, unfortunately, after the operation began the spl1.60 was downgraded to 1.40.Olipro but can't progress in flashing, the htc hermes SIM CID Unlocker 3.12.3.7 has encountered an 262 (update error), a recovery operation was guided but no result, from this error my htc still showing the three colours screen like below:
HERM200
IPL-1.01
HERM200
SPL-1.40.Olipro
please help me to restore my phone, there is indispensable for my job to get e-mails
thanks
If you're using XP then update .net framework to 3.5.
Go to activesync settings on pc and untick "Allow USB connection".
Reconnect Hermes to PC, go to bootloader (you need to reset to bootloader, true bootloader, not bricked bootloader). Run RUU_Wrapper.exe again. Should get you out of tricolour screen.
When you finish unlocking the Hermes install Hard SPL V7, go to post 1160, page 116 of this thread for sd card method - http://forum.xda-developers.com/showthread.php?t=296722
Cheers...
???
Thank you for your response but what do you mean by (you need to reset to bootloader, true bootloader, not bricked bootloader).
At the moment you can read the IPL and SPL on your screen, 3 coloured bands running down the screen. This is NOT true bootloader. You need to hold power, ok button above flywheel and reset with the stylus to go to real bootloader. Looks the same but is real and not a cocked up version.
Cheers...
Yes, but when I am doing this, the same screen become to me, with :
HERM200
IPL-1.01
HERM200
SPL-1.40.Olipro
I suppose that the real bootloader was replaced by the second one from Olipro.
regards.
No, the info you give is right, you upgraded the SPL to 1.40. However, just doing a reset with stylus may bring you to that screen but there may be a fundamental difference in how it flashes the SPL again. You need to do the bootloader reset to make sure that there will be no problems upgrading or you may end up with an unrecoverable brick. It may be fine to use the "bootloader" screen you get with a reset, but its your Hermes you will loose if something goes kaka.... And withot Hard SPL V7, you may not be able to recover it...
Cheers...
Hi, does anyone know how to enter the radio bootloader with mtty? I found some instructions on the net but they dont work, is there any special issue on the nike?
My nike has HardSPL 1.22, radio 1.65.xx and super cid unloked.
You need a MFG SPL which includes the command "rtask"
Do a "rtask a" and you can talk to radio (no echo), to return to SPL type "retuoR".
You can also security unlock your device and enter bootloader directly by pressing send and power on at the same time, or do "rtask a" followed by "setboot 1". Next time device boots up in radio bootloader.
You can then use my FrankenKaiser SPL bootloader for fast loading and booting a ram image. In my opinion a nice way to test Android
jockyw2001 said:
You need a MFG SPL which includes the command "rtask"
Do a "rtask a" and you can talk to radio (no echo), to return to SPL type "retuoR".
You can also security unlock your device and enter bootloader directly by pressing send and power on at the same time, or do "rtask a" followed by "setboot 1". Next time device boots up in radio bootloader.
You can then use my FrankenKaiser SPL bootloader for fast loading and booting a ram image. In my opinion a nice way to test Android
Click to expand...
Click to collapse
Thanks, now i have installed Hard-SPL1.15 MFG, the rtask a is now accepted, and like you said i have no echo... setboot works, but when i type in other commands like help, h, ?, gpio, version i get no outputs... What am i doing wrong? is it still the wrong SPL???
m0rph3us said:
Thanks, now i have installed Hard-SPL1.15 MFG, the rtask a is now accepted, and like you said i have no echo... setboot works, but when i type in other commands like help, h, ?, gpio, version i get no outputs... What am i doing wrong? is it still the wrong SPL???
Click to expand...
Click to collapse
You have a very limted command set if your device is not security unlocked. You find my security unlocker in one of the stickies ..
(then you have echo_on etc, enter a ? for more cmds)
Thank you, finally i get it to work... I have one last question, is there any command to get debugging log or something like that, to see whats going on when wm boots, just like the commands for the diamond?i tried set 1a 0, but it does not work, on the diamond it enables debugging information