Related
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.
FRIENDS help , I think I have the brick of all bricks I followed the wiki step by step including creating and copying the nbh file. I got as far as 70% of image loading and it hung and dropped into recovery mode but could not get passed there. I have tried all forms of reset and do not get passed bootloader screen with Herm100 IPL-1.04 and SPL-2.03. This was a imate jasjam running windows mobile 5.0 to which I tried flashing to the new HTC WWE 6.0 upgrade. I have tried running usb monitor from the link but it just gives me a series of paramters in a notice window and then dops off. I have tried another verison but it is not capturing anything.
I have tried mtty and cant even get the usb> prompt after disabling the usb connect in activesync. Please help as this was a works new unit last month and I have some major explaining to do if I cant get it sorted!
Model: Imate Jasjam
ROM Before Flash: TMO_UK_3.60.110.1_6275_1.50.00.00_108_Test
Radio Before Flash: 1.50
Bootloader Before Flash: Not sure
Flash failed at: 70%
Flashing ROM: Image Vers 3.54.255.3
CID Corrupt: Assume Yes
Radio Corrupt: Assume Yes
No GSM Error: Not got that far
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: Not got that far
Can boot into OS: No
Tried mtty command set 14 0: Yes but not getting usb>
Tried wiki problem number 4: Yes dont get passed point 3 as as soon as powers up goes to tri colour screen. Switched from serial to usb with connect of usb cable
mtty info 2 output: cannot run
Current Device Status: unusable
Tried re running install and get error 260 and 294(AFTER 1%)and - Not getting a response from PDA!
I TRIED PB + KITL method .BUT IT FAILED AS I COULD NOT ACTIVATE KITL MODE.I BELIEVE ITS NOT ACTIVATED IN MY PDA.
I SPOKE TO TO IMATE INDIA PEOPLE , THEY REPLIED THAT THE MOTHERBOARD IS TO BE CHANGED , WHICH COSTS 60% OF THE COST OF THE PDA.
CAN ANYONE HELP WITH A BOOTLOADER V2.03 ?
WAKE UP DEVELOPERS .DO SOMETHING.
tHANKS IN ADVANCE.
the output is for :
HTC_Hermes_SIM_CID_Unlock_v3a
And
RUU_Hermes_TMO_UK_3.60.110.1_6275_1.50.00.00_108_Test repectively.
So no HardSPL before you flashed?
You should still be able to get a USB monitor from it.. regardless if the thing has been thrown off the empire state building.
What USB monitor program are you using?
MTTY Set 14 0 I beleive is for a corrupt radio stack, all that does is restore your radio stack to factory form, sounds to me like you have a hybrid brick, which is corrupet or invalid CID coupled along with a corrupt radio stack..
Madcap180 said:
MTTY Set 14 0 I beleive is for a corrupt radio stack, all that does is restore your radio stack to factory form, sounds to me like you have a hybrid brick, which is corrupet or invalid CID coupled along with a corrupt radio stack..
Click to expand...
Click to collapse
set 14 0 tells the device to skip to OS boot rather than go to bootloader (opposite of set 14 1)
what we need to ascertain is exactly what bootloader version this guy is running, and then to find out what CID he has from the bootloader.
until we get these both, I think we'll have to "assume" it's ****ed.
oh and in future, don't PM me twice, it pisses me off. so consider yourself lucky I've bothered to comment.
Cmd>
Cmd>info 2
HTCSCDL__001ÄÊìHTCE
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: HERM100, Bootloader Version : 2.03
Built at: Jun 16 2007 01:57:22
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x6
Cmd>info 6
HTCST ÚÈÒHTCE
Cmd>info 5
Cmd>info 4
HTCSCDL__001ÄÊìHTCE
Cmd>info 3
HTCSH
Cmd>set 14 1
Write Nand Success
HTCST ÚÈÒHTCE
Cmd>rtask 32
Command error !!!
Cmd>rtask 28
Command error !!!
Cmd>rtask 8
Command error !!!
lastly it's not KITL enable.
This is becoming a common issue and there are a lot of people with a bricked Hermes devices, usually because of a WinXP crash, bad USB port, USB hub or pulled USB cable while flashing.
This thread is in the aim of finding a solution to all these common problems: if you are the owner of a bricked hermes, please post your comments here instead of opening a new thread.
There seems to be 3 types of bricked (or dead) hermes devices:
Type 1 bricks: Corrupted radio area: No GSM, No CID, no IMEI
Usual reason for that is flashing whent wrong when RUU was flashing the radio stack (GSM.nb). Other reason can be that you flashed radio from another device (universal unlocker run on hermes, for example).
Within the type 1 bricks, there seem to be two variants:
Type 1a:devices which can boot windows mobile but can't use the phone functions.
Type 1b: devices which can't boot windows mobile and are stuck while booting, see also type 2 bricks below.
Type 2 bricks: Stuck in boot process
Usual reason for that is that flashing went wrong when the RUU was flashing any rom part different than IPL and SPL. Symptoms can vary depending on which is the ROM part affected. The most common is OS because it is the bigger part. Radio is the second most common.
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
Type 2b: When the phone boots, it stays in subslpash screen (htc or operator logo)
Type 2c: When the phone boots, it doesn't pass the windows mobile logo
Hybrid Bricks: combinations of both type 1 and type 2 bricks
These usually have a corrupted radio and are stuck in bootloader, unfortunately these are very common too, and the most dificult to repair.
We made a wiki page long time ago whith the solutions that have worked for some people to fix bricks, unfotunately these solutions do not work for everyone, some devices are more bricked than others
First thing you have to do is visit this wiki page and follow the process explained: Common upgrade problems
If you can't repair your brick after following the process, please provide a USB monitor capture in ANSI text format (this is explained on the wiki page too) as this is the only thing that can give us a real idea on what your exact problem is. Please don't come crying and say "help me" because we can't help you if you don't provide useful information, you are in front of a big problem and you will have to loose some hours reading and experimenting before repairing your brick. If you are not willing to loose some hours reading, go and send the device to the service centre for a repair as it is the only valid solution most of the times.
Hopefully after research of everyone in this thread we can find new solutions for some of the bricks
EDIT: Please use axiom's comment below as a template for your comment and attach USB monitor capture: If your bootloader is 1.04 attach capture when trying to flash an extracted radio ROM and when trying to flash a shipped rom update. If your bootloader is 1.06 or 1.09 only attach the usb monitor capture of the shipped update.
EDIT (2007-03-22):
After more than 3 months since this thread started and more than 660 comments, we have now solutions for some bricks, so I compiled the most common on this unbricking guide:
How to unbrick your bricked hermes
Please spend some time reading through the wiki and thread comments before posting desesperately, otherwise you'll get no answer.
The following info may help in isolating the problem and keeping the clutter down.:
I'm including my info.
Model: O2 XDA Trion
ROM Before Flash: Dopod 1.23.707.4
Radio Before Flash: 1.16
Bootloader Before Flash: 1.04
Flash failed at: 6%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>
Current Device Status: unusable
Hi, I've managed to brick my Hermes as well.. First time on any of my HTC Devices....
Model: Vodafone v1605
ROM Before Flash: Voda Launch ROM
Radio Before Flash: Not sure
Bootloader Before Flash: 1.04
Flash failed at: 8%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Assume Yes
No GSM Error: Not got that far
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: Not got that far
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>
Current Device Status: unusable
You may already know this, as I posted it in all over the other threads of people with bricked hermes, but I'm posting again to make sure every piece of information is concentrated on this thread, and see if finally this can get us somewhere
HTC bootloader returns data encapsulated in a block between HTCS (start) and HTCE (end), before the HTCE there's always a 4-byte checksum of the data. You're getting a timeout when you query the bootloader for the device's CID, so the output you see is "F" which means failure (T means success) encapsulated in this HTCS/HTCE block, plus the checksum. The CID is read from the security area of the device, found on radio, but the wrong flash corrupted the radio area.
As the CID is not returned, the error you get when flashing the ROM is "CID Not allow (255)". The security level depends on CID, as the device has CID corrupted, the security level returned is FF (255), which means you can't bypass CID check in bootloader.
You both have bootloader 1.09 which does enforce CID checking (as opposite to bootloader 1.04 which has a known bug to circumvent this). This bootloader also only allows updates with bootloader version > 1.09 (and no such bootloader exists yet).
Bootloader 1.04 allows to flash unsigned code in radio with radio bootloader command 'rwdata', but radio bootloader is accessed through command 'rtask' and this command has been removed in following bootloader versions.
All the commands to flash code in bootloader 1.06 and above require the code to be signed (the commands are 'wdatah' and 'lnbs'), and bootloader checks the signature before the code is actually flashed on the device. So modifying a 1.04 bootloader to show itself as 1.10 is not possible because it will return a certificate error and will not be possible to flash.
Command 'lnbs' doesn't check CID, but it is only enabled if device has security level=0, and as your radio is corrupted and your seclevel=FF it will not be possible to use this command to fix it even if you had a signed bootloader, so 'wdatah' is the only command that would allow you flashing code, but 'wdatah' requires a NBH header to be sent, which contains the CID of the update and is checked against the missing CID on your device and will never match (even if you could modify the NBH header and have a valid signature after).
In conclusion, my recommendation to you is that you send the device to service centre to get it repaired and don't try to fix this by yourselves, as you will go nowhere.
Many thanks for explaining it so succinctly Pof, much appreciated. With this error I've learnt a heck of a lot more about the ROM flashing process... I guess it may be time to send the unit for repair!
This is the full report after I soft rest my phone while the USB is still connected. Would any one know what the rest of the data means? I did it in the morning then just left it for the day to see what would happen, I just got back from work.
onj: can you use axiom comment as a template to provide information?
radioerror.txt: I see you're using the Himalaya upgrade utility there... rbmc reads data from memory, but I don't know what is at 0x70010000. It would be better if you can provide a log of hermes RUU.
Model: x01ht
ROM Before Flash: i-mate
Radio Before Flash: 1.07.03.10
Bootloader Before Flash: 1.04
Flash failed at: 0%
Flashing ROM: JASJAR_WWE_19096_19505_11300_AKU_3_2_ship
Flashing Radio: 1.13.00
Bootloader After Failure: 1.04
CID Before Failure Super CID: success
CID Corrupt: don't know
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: stalls
Current Device Status: unusable
I will upload the usbmonitor with using
RUU_HERMES_HTC_WWE_1[1].35.255.2_1.35.255.102_1.08.00.10_SHIP
the upgrading dies after info 3
computer says ERROR [222] Device not responding
that's with all the RUU's that I use and even the full upgrade ROM
Hi, I have a herm 200 an i have a Type 2a bricks (it goes directly to bootloader mode tri-color screen).
But i upgrade with the rom (ME_DT_WWE_1182553_106_10303_Ship) and all run good. but 3 moths later i have the type 2a bricks.
I try with that solution (http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems) and others and NOthing.
In screnn say herm200 ILP-1.00 and Her200 SPL-1.04.
ps: sorry my english is very bad.
@onj: Oh ****! You where trying to flash an HTC Universal ROM in your HTC Hermes!! These are different devices, most probably that's what screwed it.
From your attached file I see bootloader does not answer to any command.
@landtd5: please use axiom comment as a template, and attach USB monitor capture when tryng to flash a shipped rom and a radio rom.
Yup, I upgraded with the wrong Rom. After going through the forum for the past 2 weeks I realized what I did. I guess it's time for me to send it to the shop
thanks for you help pof
jash431 Dead Tytn
I had tytn with this rom
"TYTN_me_dt_wwe_1182553_106_10303_ship" which has bootloader 1.04
And I upgraded with
"RUU_HERMES_HTC_WWE_1.35.255.2_1.35.255.102_1.08.00.10_SHIP"
during upgrade stopped and after that I cannot do anything with it
It never answer to any solutions .
Please help me .
USB monitore is attached here .
jash431 said:
USB monitore is attached here .
Click to expand...
Click to collapse
This is not useful: You saved LGS file, please follow instructions in wiki, you need to EXPORT as ANSI TEXT file. Also please use the 1st comment as a template to provide useful information.
Jash431
I exported in ansi text
@jash431: doesn't return anything... when you connect to bootloader on mtty, do you see the USB prompt? does it answer any commands?
Jash431
I'm sorry . this is complete one .
yes I can work with mtty.exe and my info 2 is "HTCSF kEØ(HTCEUSB>"
jash431: hybrid brick with corrupted radio and bootloader 1.09. Send it to repair centre.
jash431
is it theorically possible to fix my tytn . I mean maybe in future someone make a downgrade or SuperCID rom !! .
Because in my country doesn't exist repair center (Iran) . So what can I do ???
then keep it until something is found to fix this, creative solutions to the problem will come to your mind after looking everyday at a $500 brick.
Jash431
Thanks pof for your answer . I'll check my private message every day , for your solution and I remember you whenever I see a 500$ . ( Of course 500$ doesn't exist but you do ).
hello! im not so god at English. so it can be hard to understand what im trying to explanie.
my htc stoped to work as phone a few mouht back. so i bought i new phone,
but now i want my htc back. and i have looked everywhere on this forum for a answer, and ever time i find something it dosent work for me.
in the device info it says that my radio version is None. so thats bad i think?
i tried to flash and put in a new SPL and all of that, but when the phone go to bootloader the connection between the computer and phone disperse. my OS on the computer is win7, and i have tried it on a computer whit xp whit the same results.
so what can i do to make the phone work again?
/Dreamcore
pleas, can somebody help me? i tried everting now, usb monitors and changed spl like a milion times now, what do you need to see my problem?
Model:HTC TYTN
ROM Before Flash:shiped wm6?
Radio Before Flash:??
Bootloader Before Flash: 1.04
Flash failed at:no
Flashing ROM:??
Flashing Radio: ??
Bootloader After Failure:??
CID Before Failure Super CID: ??
CID Corrupt: ??
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash:no
Can boot into OS: yes
Tried mtty command set 14 0:no, cant connect to it
Tried wiki problem number 5: Yes
mtty info 2 output: CID:??
Current Device Status: phone dead, but the rest works fine
if somebody wants a usbmonitor screener from my, so pleas help me understand how to do it..
been reading treads for 6 ours now. so pleas, help me
Phone needs...
The Phone needs a new system board! Radio hardware failed!
These phones are getting to be about 5 years old?? or more??
They need new boards!
$90 + shipping online. Or whatever method you can come up with to get one.
Good Luck.
Hi xda-community,
I am new to the Smartphone- and the Windows Phone world. My main cause is to get rid of the swisscom branding of my HTC Radar. But I also would really like to test some custom ROMs - especially the Dynamics HD2O looks promising in my mind. That's why I bought all the equipment necessary for Goldcard method for 2nd Gen WP7 phones as in this manual.
My Info:
HTC Radar C110e
Model ID: PI06100
SPL – 1.8. 160015.3 (131745)
Radio-16.23.06.10
Radio Software version: 16.23.06.10_ 16.32.00.23U
FW-Rev: 1600.2200.10801.166
What I did so far:
downloaded IMG_Omega_HTC_Europe_2.05.401.01_Radio_Signed_16.23.06.10_16.32.00.23_OMEGA_RELEASE.nbh
renamed it to OMEGIMG.nbh
put it on microSD-Card
used goldcard-tool and made Goldcard of microSD card
put goldcard on one end of Y-Cable, Radar on thick end, and red end in USB port of PC, which put Radar to light
entered USB Host Mode by pressing vol down + camera (now it shows "Update in Progress" and reboots about 10 times every 10 (?) seconds...then this appears:
OMEGIMG.nbh - FAIL
RADIO - Fail
BOOTLOADER -
RCUST -
OS -
>*>*>*>*>*
Update Terminate
UPDATE FAIL
Error code: 33
I tried it a dozen of times and only once it showed me "Update Complete - Update Success". The next time I rebooted the device it showed an "SPL 2.5 MFG" but only once. After another reboot it was back to 1.8 again
But I think the Radio version was upgraded by this "success", since it was 16.23.02.09_2_ 16.24.00.23U when I bought this smartphone.
However, I am lost at this point. In the DFT-manual linked above the basic stuff to know doesn't contain "RUU". I downloaded the ROMUpdateUtility from the manual but when I try, there's always this Error 294- invalid vender ID.
I tried several times to upgrade spl_2.6.160015.3_WWE.exe, but it'S stuck at 0% and then I get the connection Error 262.
Also I might add, that the Radar isn't anymore in the Control Panel but only the HTC USB Sync-Driver (?)
I am afraid to update via Zune, because I read, if the SPL is too high, I couldn't downgrade again to HSPL. However, I never installed Zune. Is this still available? What should I do?
Edit: it worked
after GOldcard, the device restartet b itself and I missed that to enter SPL mode (instead it rebooted to USB HOst Mode by itself and startet the goldcard-method from beginning). By entering SPL mode I stopped the loop of goldcarding and after my SPL was 2.5 after first goldcarding, I was able to HSPL'ing the device
SGE2010 said:
Hi xda-community,
I am new to the Smartphone- and the Windows Phone world. My main cause is to get rid of the swisscom branding of my HTC Radar. But I also would really like to test some custom ROMs - especially the Dynamics HD2O looks promising in my mind. That's why I bought all the equipment necessary for Goldcard method for 2nd Gen WP7 phones as in this manual.
My Info:
HTC Radar C110e
Model ID: PI06100
SPL – 1.8. 160015.3 (131745)
Radio-16.23.06.10
Radio Software version: 16.23.06.10_ 16.32.00.23U
FW-Rev: 1600.2200.10801.166
Edit: it worked
after GOldcard, the device restartet b itself and I missed that to enter SPL mode (instead it rebooted to USB HOst Mode by itself and startet the goldcard-method from beginning). By entering SPL mode I stopped the loop of goldcarding and after my SPL was 2.5 after first goldcarding, I was able to HSPL'ing the device
Click to expand...
Click to collapse
Hi,
I use this ROM and it is very good one. But if you put HSPL already now you should put new radio RUU_Radar_Radio_17.5006.08.27 otherwise it will not work. Read the instructions in the tread. http://forum.xda-developers.com/showthread.php?t=1685271 in the tread there is link for downloading this radio. For me it was easy to HSPL the phone because I am not receive Country error and I don't need to use gold card just RUU.