Database Users

HELP!: a possible XDA paper weight, how to recover

A history of what has been done:
at first a perfectly working factory default XDA with a rom that dated back to fall 2002.
Connected to a Compar laptop running WinXp, ActiveSync 3.5 (build 12007)
Tried to flash Radio_Stack_Upgrade_v421.exe to the XDA, the flash went all-ok as far as 45% or 53% and froze after that. After being frozen for more than 5 minutes gave a message "flash failed" and booted the XDA, and started flashing all over again with the same result (this cycle repeated about 10 times)
After which I deleted the flash-related files from the XDA:sta startup directory, during while it was flashing.
Booted the XDA
Worked seemingly fine, except that none of the GSM functions vere operational. At first nothing else seemed to be wrong, but then the XDA completely failed to recognize the AC power connection. It insisted that it ran on battery even thou the power cord was connected. Even tried a different powerplug on the wall. Also the power utility from the settings meny gave "uknown" as batterylife.
Tried to flash the XDA with Radio_Unit_Upgrade_v31703.exe, but could not even start the procedure, as it insists on an early phase that the AC powercord must be connected, and since it doesn't recognize the connetion it simply aborts.
Desperate after this tried a hard reset.
After that the XDA doesn't boot properly: it gets past the inital "plash screen" into making a beep sound and displaying a white screen with blue thick bar (empty) on top. I'v booted the machine about 20 times like this by now, always with the same result. Some times it doesn't get as far as the blue-white empty window. If I leave it at that the XDA simply reboots itself after being frozen in the white-blue screen for over 2 minutes.
I left the machine at the table and went to the gym after coming back it had gotten past the white-blue screen, to the initial phase after hard reset where it says "tap screen to setup your XDA" I tapped the screen and it went to clicking through the crosses on the screen to initialize. I managed to click 1 cross, after which the XDA froze completely and did not react for 15 minutes.
After that single incident getting past the white-blue screen, I haven't been able to repeat it. I have tried to boot with SIM and SD, with SIM only, with SD only, and without both: the same results with each.
I have another XDA at my disposal, and a SD card. Could the device still be rocoverable somehow through using that other XDA to copy something into the SD card and booting.
Please tell me do I have a paper weight on my hands, or can I somehow recover from this. Thank you!

Yea that’s a good place to start use the other XDA to copy it ROM+Boot to the SD card and use that to reflash your ROM. You do that by entering bootloader mode and select CE+Boot. Hopefully you won't get the dreaded Check Sum after the reload!
Do you have access to a PC SD card reader, because you're go to need
one!
Updating your Qtek ROM using the 'SD Card' or 'Bootloader' Method
http://xda-developers.com/forum/viewtopic.php?t=1717
HTH

Qman said:
Yea that’s a good place to start use the other XDA to copy it ROM+Boot to the SD card and use that to reflash your ROM. You do that by entering bootloader mode and select CE+Boot. Hopefully you won't get the dreaded Check Sum after the reload!
Do you have access to a PC SD card reader, because you're go to need
one!
Updating your Qtek ROM using the 'SD Card' or 'Bootloader' Method
http://xda-developers.com/forum/viewtopic.php?t=1717
HTH
Click to expand...
Click to collapse
It appears my XDA O2 has the 5.17 version of the bootloader. When I boot into the bootloader it says "GSM error" at first, when I press the action button, it says "GSM turn on" and after a while "GSM turn on failed!!" and freezes there. Is this the kind of an error that prevents me from flashing a ROM from a SD card even if I had one? Since it gets stuck with that GSM error thing, and never even actually goes to the bootloader menu... why do I need a PC SD card reader? wouldn't just using the other XDA to copy the ROM and then flash it to the broken one do the trick?
Thanks, for the reply btw, for a while I was thinking that nobody would help me - and my situation is hopeless. Not atleast there is some light at the end of the tunnel..

Try pressing the Calendar button instead of the Action.
BTW You would need a PC SD card reader to load the needed radio stack upgrade files on to your device if all else failed plus if the CE+Boot backup to SD failed with that other XDA you could use XDArit to write another ROM to SD.
HTH

Qman said:
Try pressing the Calendar button instead of the Action.
BTW You would need a PC SD card reader to load the needed radio stack upgrade files on to your device if all else failed plus if the CE+Boot backup to SD failed with that other XDA you could use XDArit to write another ROM to SD.
HTH
Click to expand...
Click to collapse
Thanks, that appears to work: the button on the left brings up the ROM+BOOT etc menu, and the button on the right (calendar) brings up the menu for setting the GSM (different options, like on, off, 900, 1800, etc). Since the local time is 00:36, I'll try the tricks with the other XDA O2 tomorrow..

You're right I'm sorry, its the Contacts button for CE+Boot!
WOW 00:36 its 14:47 here in LV, NV US anyhow good night and check you tomorrow.

xda1 GSM ERROR- not able to reload from SD

I WAS PERFORMING AN UPGRADE ON XDA1 and got and error and the suggeation was to reboot and that the pgm would recover. Whoever wote these programs must have been in LA LA land when he/she wote them. Now my XDA1 shows only an OS version when it boots and no radio stack. When I now want to reflash with the help of the SD card I do a soft reset power button ritual and get a GSM error and no option to load from the SD. Does anyone know how to get out of this mess? Please give me detailed instructions if yo do

I have a similar problem. i flashed, but it must have failed or been bad versions. i write to the sd but it doesn't boot. i tried the wallaby bootloader but either i scrod the pooch, or it isn't working. if i let it boot, it halts at white screen with top blue strip. if i leave itr go, it reboots after a while and the cycle starts again. i have v5.17 bootloader onboard.
Help!

Since my post I have given up trying to fix the device myself and have sent it to Siemens here in Canada. For a fee of 35$ can they will reflash my phone if that is all that I have screwed up. I have also found out that for the SD card to be recoconized with a new ROM it must be loaded on the card with OSItools. Otherwise it won't. I am using bootloader 5.15

P4350 quite dead after USPL'ing

Hi,
I tried to USPL my P4350 (SPL & IPL 4.xx.xxxx) in order to update to WM6.1, using Herald-USPL-Beta3. Everything went OK until ROMUpdateUtility kicked in, and gave me an error: FILE IN USE.
So I started the ROMUpdateUtility again, with the screen still blank, and suddenly the P4350 turned off. I'm 100% sure the battery was at least 90% full during USPL'ing, so why it turned off; I have no idea.
Problem is: I can't power up the device anymore. No LED's, even when attaching it to the power adapter.
Any tips on how to fix this, or is it fair to say my device is now really DEAD?
Thanks!

Some suggestions of a Junior Member.
1st. Try a soft reset. Didn't work? Go to Step 2
2nd. Try a hard reset. Didn't work? Go to Step 3
3rd. Pull the battery off. Put it again. Try to turn it on. Didn't work? Go to Step 4
4rd. Wait replies from advanced user. End.

Thank you for replying
However none of the options you mentioned worked out.
I'm stuck waiting for some expert guidance here

Hi, it's been a while, but today I finally made -sure hope so- some progress..
I purchased a HTC Touch HD two weeks ago, from which I plugged in the power adaptor to see what my P4350 would do. (specs are the same btw as the P4350 power adaptor; output 5V, 1A) On this attempt however, the left LED on the front of the device turned RED for about 5 seconds before turning off again. I plugged in the adaptor again, and it lit up RED again. However, the device did not respond to an attempt to power it up.
What does this mean? Is it not dead after all?
Any tips on what to do?
Thanks again.

Wow man, I'm getting somewhere now!
I got the device powered on holding the RESET+POWER+CAMERA and it now hangs on the IPL + SPL screen.
What is very strange is the following:
IPL 1.08.0001
SPL 1.08.0001
as to where these were above 4.xx.xxxx before I did the USPL'ing. I am a 100% sure.. (not so sure anymore now to be honest.. )
The screen displays USB in the left bottom corner, because it is connected to the USB power supply.
I'm afraid to turn it off because it might not turn on again...
Where do I go from here?

Well, I finally got my P4350 to work again
I noticed I was able to start into bootloader mode using CAMERA+RESET, unlike previous attempts to do so. I don't know what caused the device to boot after 6 weeks, but I guess attaching the Touch HD power adapter did the trick.
At first I followed the instructions at topic "Goldcard for Herald", but somehow I wasn't able to make the MicroSD card bootable using my HTC Touch HD for the formatting.
Instead I went to page 5 of the topic and discovered this comment by leptir79, who stated the creation of the Goldcard could easily be done from a DOS-prompt in Windows, with the MicroSD card in the SD-cardreader on a PC or notebook. And this is what did the trick for me:
- I put the SD-card in my notebook cardreader (drive W: ), opened a DOS-prompt, and ran the following command to format the SD-card with the correct priviliges: FORMAT w: /FS:FAT32 /A:4096
- After that I copied heradiag.nbh to the blank MicroSD card to see if my P4350 would boot from the MicroSD card. And it did. From this tool I ran some diagnostics tools to see whether my device was fully functioning, and I got no errors. I noticed that among the diagnostics tools there was a tool to Flash the device with a new ROM
- So I downloaded HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe, extracted RUU_signed.nbh to the root of my MicroSD card (along with heradiag.nbh), and renamed RUU_signed.nbh to heraimg.nbh.
- I started the P4350 into bootloader mode, booting from the MicroSD card. Heradiag.nbh booted up, and I chose to use the Flash ROM utility that came with heradiag. The device automatically found heraimg.nbh, and started the flashing procedure for my device. After confirming, the flashing started.
After a few minutes my P4350 rebooted, and my device is now running Windows Mobile 6.0. Everything seems to work just fine now.
So, if you don't have a second (working) WM device, but do have an cardreader on your PC or notebook, this really is the best option to create the Goldcard imho.. (even if you do have another WM-phone, really, try this procedure first before installing ActivePerl and all the perl-scripts)
Thanks everyone for all the procedures and help. You all did a great job, but most credits in this case go out to leptir79 who gave me the breakthrough in getting my -left for dead- device to work again.

This is a gold trick thats what i'm waiting for...
I have my heralds bricked since 2 months ago... Yup....really bricked...means cant do bootloader mode or hard reseting on device...
And already sent it to the HTC care center, and they ask for mainboard replacing...which is too expensive for me...400US...later cancelling it...
Searching out this forum, and didn't find a solution to reprogramming OMAP via JTAG...then my research suspended...
Untill I found this...
All I need...just to enter to the bootloader...powering up the brick
Can't wait to try this method @home...ASAP...
For now...just looking for 5V, 1A Charger first....
TIA frummel...

hera100
hie i have a hera100 does not detect on active sync when i try to update rom stops at 2% try diffrernt roms some stop at 7% my IPL 4.14.0002 SPL 4.10.000 i tried formating my 2gig and put heraimg on it nothing happens. pliz help how do i do it now phone shows three colors i cant hard spl coz of active sync. ithanx in advance

Attach phone to a computer with a mini-USB cable and install a RUU ROM.

Help me (lost my ROM) :(

I was trying to upgrade my ROM to windows 6.1, and something wrong happened.
the update software hangs up on 0% also in my phone, form more than hour.
then I unplug the USB cable, and connect it again, the wizard told me that process will be resumed, but the same for more than hour and nothing happened when i reconnect it again it gives me error connecting
now my device is no longer working, it just give me a colored screen and nothing happened.
is there is anyway to fix my phone.

Is there anybody ? any idea ??

This might help.
http://wiki.xda-developers.com/index.php?pagename=Elf_SD_Card_Flashing

thank you jeremy,
I tried this method but it didn't work.
first i get the SD card and format it using windows (i tried both FAT, FAT32)
then extract the .nbh file from this package RUU_Elf_DOPOD_AU_1.14.710.2_4.1.13.46_02.97.90_BLUE_Ship.exe,
then i renamed it to ELF0IMG.nbh copied it to the root of SD card, then put the SD card in my device,
push and hold camera button and push the power button then the colored screen appeared but nothing happened. i tried also press and hold camera button then soft reset using stylus but it didn't work.
am i doing something wrong
Sorry i tired you

It should work.
It should say like ' do you want to flash your phone ' , press the power key to continue..
mmm, have you CID unlocked your phone?
have you tried flashing your phone?

how can i do that "CID unlock" ?

Go to the elf-upgrading forums and flash your ipl and spl to 3.10.
Cheers.
Can you start your phone in the first place?

no I cannot start my phone. it just freeze on the colored screen

Serious problems with (semi?) bricked HD2

Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?

SS and HX in the bootloader screen just means Samsung or Hynix, , two chip providers HTC uses. They do the same thing, and you can forget about that for now, you have much bigger issues than one chipset being slightly better than the other.
The pink on black screen is a splashscreen, anyone recognise it? winmo? android?
The HTC website started dropping support pages for the HD2 a month or two ago, , looks like its ancient history as far as HTC are concerned.
Qualcomm MSM,,, this is a bad sign, , it is what the bare chipset presents itself to the usb connection as when there is no controlling bootloader. (This is what tmous users get when they radio brick their phones). Quite an odd symptom to see in a phone that powers on.
From the various power / boot symptoms, it sounds likely that one or more of the following are true
1 - the battery may be low on charge, and if magldr is installed the battery wont charge until android is running (which of course it cant) so you NEED to get magldr off ASAP (if in fact it flashed)
2 - the radio may be corrupted, which usually manifests itself as flashes failing at 8 - 10%, or radio flashes never completing.
3 - The phone may be one of the unlucky ones that has/is cooked/cooking itself. have a read on the 'freezer trick' where you cool the phone down for a while in a bag in the freezer, then quickly flash from sd as soon as you take it out, so the chips don't overheat before its done. If this turns out to work, then the phone has hardware issues.
4 - The bootloader itself may be corrupt, but only slightly (just theorising now) or the NAND memory where the bootloader is stored could be starting to degrade.
Recommended way forward.
Assuming you have access to a card reader,,,
send me your IMEI and an email address, and ill generate you a Goldcard.img,
follow THIS to make teh goldcard and place on that goldcard the RUU_Signed.nbh (renamed to leoimg.nbh) extracted from, , lets go for the WWE 3.14 rom from HERE (Lotta junk in that folder, scroll way down towards the bottom, look for filename as below)
id go for
RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.zip
down towards the bottom.
(Thats assuming you want english? theres probably a DE one if you prefer)
SO, id try flash that from the goldcard, and report back.
(Note i'll be on and off all day, so don't expect an immediate response to your IMEI, cheers, oh and the .img when i send it will most likely get spam foldered, so dont miss it!)

I created a goldcard myself and tried the image inside "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship.zip".
While flashing it showed me "RSA Fail" on "Radio_v2".
Any ideas? I'll try other ROMs till someone answers
Thanks,
iCEQB
EDIT1:
Trying "GER" Roms:
1 test) HTC_HD2_RUU_Leo_HTC_GER_1.66.407.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe - "RSA-Fail" on "Radio_v2"

Ahh radio fail, bad news. I've seen it cured once or twice, by flashing the phones original rom, but I suspect those were exceptions.
I've also seen failed flashes take when you well chill in the freezer (card sim and battery out while it chills) and quickly flash on removal.
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.

samsamuel said:
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
Click to expand...
Click to collapse
Yeah I used the wp7 config. Is it bad? I mean, the goldcard works right?

test 2) RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe - "RSA-Fail" on "Radio_v2"
I'm out of ideas guys ... will wait for you to create me a winmo goldcard image and try them again.
Last resort is the freezer trick. Or any other ideas on how to progress from here?
Regards,
iCEQB
EDIT: BTW, does HSPL need to be deinstalled for these goldcard actions?

Ohhh hang on, that img i sent wont work, silly me, its not the imei I need, its the Cid (unique serial, uid, goes by a few names) of the SD card. See the howto I linked ya for how to find it.(really easy if you have access to any other winmo phone, not so easy otherwise.)
Just shows how long its been since I thought about goldcards.
Sorry.

Which branded phone is this?
Brother even I have same type of logo when phone starts (pink colour circle)
Even my phone is bricked but I can install wp7 or android (only no network problem)
Can u guide me how did u solve this issue pls
Thanks & Regards
SE_iCEQB said:
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
Click to expand...
Click to collapse

Do a jtag on it it will fix everything i think
Sent from my Nexus 7 using xda premium