Database Develop

Flashing WM6.1 to a new Herald

Hey there,
since I'm new to the community I hope I'm not doing it wrong
I will receive my new Herald within the next days and now I'm seeking for all the stuff I will need then.
1. Hard-Spl. I don't get it. What is it? Is it some kind of firmware update or whatever? The ROM's thread says that I would need SPL 4 or later to successfully finish the Update but I can't find that SPL application in version 4+ :/
2. http://forum.xda-developers.com/showthread.php?t=437385 - http://www.evolvers.net/Herald_Roms/Version 7.7/ => I'd like to use that ROM. But I'm not too sure whether to use Manilla2D or Omnia.
3. What if I needed to send my device back for warranty reasons. Is there some way to flash back the standard Win Mobile 5.0?
I hope I will get your attention!
Regards,
Chris

Hey there,
A friend of mine just told me about flashing ROMs literally a few days ago. I did my first successful flash just yesterday and I am very happy that I did. FYI, yes I am using a stock TMobile Wing from 2007.
Rom's are not interchangeable across different phone models as far as I know. So you need to get ROMs made for the wing a.k.a. the Herald. Any Rom for the Herald should work.
Just remember one thing that I forgot to do, make sure that you back up your data. I forgot to do this and lost all of my data. Luckily, I did not have any pictures or music that I was too sad to lose. However, I did lose my contacts. Again luckily, I had an old Sim card from last year that had my contacts on it, so I was able to get back 90% of my phonebook, except for a few people that changed numbers or new contacts. So be sure to save anything you want to keep somewhere else.
I am pretty technically savvy, but I must say that flashing the Rom did take me several hours. The process itself only takes about 10 minutes, but it took hours to figure out what type of Rom I needed and how to exactly flash it. You will see many people trying to tell you that you need to know your IPL and SPL version, and there is no way to know this until you start flashing! It wasn't until I did my first accidental flash that it showed me this information, and this ended up being my first successful flash. After trying for several hours the night before and not succeeding, I guess that's why it slipped my mind that flashing successfully would erase all my data.
The one that actually worked for me was the Canonyang Rom. In the link below please look at post number 216, and you will see a link to download the ROM that worked for me. The file is "HardSpl_WM6".
http://forum.xda-developers.com/showthread.php?t=332413&page=22
I tried to flash directly to open touch, and no matter what I tried it was not successful. When I accidentally tried this Canonyang flash it worked successfully the first time, and after that now I was able to flash to any other Rom.
I am currently running open touch light version 6.5 because I read in another thread that it's supposed to be the fastest. I don't need a lot of features so I'm happy with what it has, and it is much, much faster than the stock T-Mobile Rom.
Since you are now getting it, yes, warranty is an issue for you. I am very new to all this, but from what I gather, once you flash, it does void the warranty. Perhaps someone else can answer if there is a stock TMobile rom, that you can flash back to. However, since the roms are digitally signed, I'm not sure that by even doing that, if TMobile can tell you modded it, and therefore elect not to honor your warranty. I guess that's a risk you have to decide if it's worth it or not. IMHO, I found out about rom flashing this week, and my warranty was up last month. However, if I had found out about this during my warranty period, I would have still done it. The Tmobile stock rom is sooo slow, compared to these roms. If you've never used these roms, you'd think like hey, it's got some bugs, but it's not that bad. But if you've used them, you're never going back to stock rom again.
I apologize if there are any typos, as I am using voice to text recognition software that I am testing. I thought I'd help you out by writing this as well as I test it. Good luck and let us know if you have any questions, we're all here to help.

Hey,
thanks for all the information. Was very helpful. I decided to you the ROM from that link. Should work, shouldn't it?
The only thing I don't get is how to get to SPL4+ :/ I heared of different methods of SPLing. Like Hard SPL and USPL. Can you bring light into that cave?
Cheers.

Hey there,
Your link goes to the Open Touch thread. The link I'm referring to, is this one:
http://rapidshare.de/files/38148213/HardSpl_WM6.rar.html
As I said, I was NOT able to flash directly from stock to OTP. I tried many methods, and Canonyang was the only one that worked for me. After I successfully flashed to CY, then I was able to flash to OTP without issue. But in theory yes, any Herald rom's should work fine.
In regards to IPL/SPL, my wing is from September 2007, and I had IPL/SPL both above 4. I had NO WAY to verify this before flashing. When I initiated the flash for CY, and the wing rebooted, it was THEN I saw my IPL/SPL versions. I'm sure yours will be at least v4.
Actually as I write this to you, I remember a critical step I forgot to tell you. You need to Application Unlock your device as well. This is probably what I was missing in my failed attempts. After I did that, then the CY flash worked. I got that information, from this link:
http://forum.xda-developers.com/showthread.php?t=356295
So I would suggest following the steps there first, then trying the link earlier to flash to CY, then flash to anything else. This is the procedure that worked for me. Good luck!

Hey there and thanks again for that bunch of information
itbmd said:
I'm sure yours will be at least v4.
Click to expand...
Click to collapse
What does that mean then? I do not have to HardSPL my phone? But still, would you mind telling my step by step (And I really mean step by step^^) how to HardSPL a device? I really do not want to brick my phone directly at the beginning.
Oh and what should I rather be using, SoftSPL or HardSPL?
Cheers.

Hey there,
Sorry but I just flashed my device less than a week ago as I mentioned. I don't have many of the answers you ask, because I'm asking them myself. I don't know the diff between Hard vs. Soft SPL.
The file I linked you to earlier, is a hardspl, as denoted by its filename "HardSpl_WM6". It hardspl flashes to the canonyang rom. It was then I saw the IPL/SPL versions, and then was able to flash to other roms.
FYI, I was concerned about bricking my device as well. But during the roughly 5 hours I was trying to flash it correctly, every time the flash failed, it did NOT brick. It just errored on the pc, and the Wing itself just restarted and went back to the stock TMobile rom. It never actually bricked. Make sure you do the application unlock though; I think that's a step that people may not do and could cause it to brick. Good luck.

Restore device to OEM without touchscreen

Hello out there.....
First of all i have to say THX to all these people which are really willing to help every1 with their great tutorials. Ive used alot of them already. Thanks.
And i have to say sorry for my english language, due Im german and i left school behind long time ago. I'm really taken pains to write this comment.
Now, in my case ive tried to restore my device (Xperia X1i) to OEM status step by step as its shown in this thread.
My worst issue is that my touchscreen aint work anymore after i flashed a custom ROM and that i got stock at the point where the ROM wants to configure the OS like "Tap the screen to continue with configuration".
Ive tried to flash way too much ROMs using HardSPL but the touchscreen wont let me do anything - no reaction.
So how can I restore the bootloader (SPL) on my device, when my touchscreen aint work? How can I take the following step without any working ROM ?
sirsycho said:
12. Run SSPL.KAIS.exe from your phone (make sure you do this on your actual device and not your PC)
Click to expand...
Click to collapse
I do not know what I did wrong, that the screen wont react anymore, but im sure that the SPL is the cause for this disaster.
I'm really desperate couz i already have sent the device to the SE Support, where they told me that there is an "extraneous" on my device although ive flashed the Stock ROM firstly... there was still something that bothered them...
After i got the device back the touchscreen worked again as funny, allthough the support did nothing on the device as they said in the delivery.
A bit skeptical but with alot of happiness i kept on flashing some ROMs after that.
Now, after i found a good ROM and kept this one on my device for some days the screen doesnt work again.....
This is what my bootloader says right now
Code:
KOVS110
SPL-0.72.OliNex
MicroP1-787
MicroP2-707
....seems like the HardSPL is still there......
Honistly i had to apollogize (maybe too late) that this part of using a cellphone (flashing a ROM using HardSPL etc.) is a big fish and that ive underrated it. Now i have a 400$-Device which aint work anymore
Ive read like all Tutorials here at xda-devs containing something about flashing a ROM or informations about SPLs; tried everything
I feel like im lost and fu**ed right now....
Is there any1 can help me with my problem?
Hopefully there is.....i pray for him

first flash a stock rom
then just run the hard-spl exe, and replace the ruu_signed.nbh file
why are you trying to use kaiser spl?
use the things found in the hardspl sticky in the xperia section

Wrong Tutorial
You're using tutorial for wrong device (HTC Kaiser)
The correct tutorial is in first post (extra how to: how to restore Stock SPL for warranty reasons.)
http://forum.xda-developers.com/showthread.php?t=431218
But before restoring original hardspl you should flash with original rom found in this thread http://forum.xda-developers.com/showthread.php?t=475482

wow thanks for your answers !!
i never thought ill get response.
Its really weird that i havnt found that tut before bcuz i was looking through whole board.
I will try do that tomorrow.
I hope that it will work then. Don't wanna pay 300$ for a new device

Else there is mtty to restore the bootloader

Aight i have done the steps showing in the tutorial.
1. I have flashed teh Stock ROM (R2A german - Vodafone)
2. I've used the RUU with the stockSPL given in that post.
Now my tricolour screen shows the following
Code:
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-707
This is what it shall looks like OliNex said.
I hope this is all i had to do, to make use of my device's guarantee, cuz the touchscreen still doesnt work
Seems like i really have to send my Xperia to the Support again (now hopefully with a ROM + SPL they wont reject)
But if i send my device with "extraneous" again i have to pay another 15€ just for let them do a costs estimate -.-
I would like to get a reply before i make use of the support again.
Thanks for all your help

Glad to hear recovering to stock rom + spl worked out.
Your touchscreen doesn't work when you have booted up windows?
If that's correct then I suggest to send in the device for service. Although
it might not help I suggest updating your device with SE updating service (SEUS) first.
After the flash remove the battery for 10 seconds, then turn it on.
Hope it helps and otherwise servicing the device is free of charges

Haha!
That's what im doing right now, using SEUS
Thanks for the tip with the battery but i already tried that way too often
Edit:
Ok, touchscreen still aint work....
Time to contact the support...at 11:45 PM **WOOT
nvm....Ill wait till tomorrow
gn8 and thanks for helping me with my issue ^^

a few days ago I returned my silver X1 for the same issue, my touch screen (digitizer) doesn't work. Then right in front of SE support person, he justed took out the battery and rebooted. Then it worked. The thing is, I did the same thing several times earlier that day and it did NOT worked. I am worrying of getting the same problem again and I only have until november 30th until my 1 year warranty expires. I haven't tried any cooked roms and it is because of warranty purpose. Altough I'm not new to custom roms since I own an Alpine and a Prophet. I've been here for some time now.
The thing that holds me back testing cooked roms on my Xperia is the aftermath if in case my device goes half-dead. I almost always read the restoring on to official roms everytime I get here, but still the thousand dollar spent on my phone's tag price comes with a fear of who's gonna rescue if my phone won't work. And to add that spare parts aren't available here as of the moment. And yes I'm eager and very curious about almost everyone saying cooked 6.5 is faster than stock roms but though I haven't tested it I have to disagree for now on my case basis.
First, my Xperia doesn't come with a carrier lock. It's locally called "open line" in my country I guess technically called debranding. Then my phone has the generic r3a rom via seus I think it's generic uk. Lastly, for some reasons, the touchflo 3d doesn't work with my device I've tried it since r1 firmware time. Some response told me to unlock-debrand my phone first but I dont have to since it isn't locked. Still installing tf3d makes my phone hang, doesn't uninstall, doesn't show in the themes list if installed as a theme, and doesn't let me have another panel since it always stay as tf3d whenever I choose another one. And it is very unstable in my device. These happened even if I install it as a panel.
I feel handsets here are faster than handsets that are locked by a carrier so I'm thinking again since for now, my Xperia works for me as stock as it is.

X1 hard resets all by itself... all the time

It's done it 3 times now and it's very annoying. Obviously, everything is deleted. Anyone know why this might be and/or how to prevent it? Generally the phone crashes, I have to remove the battery and then it re-installs Windows.
Thanks

at45 said:
It's done it 3 times now and it's very annoying. Obviously, everything is deleted. Anyone know why this might be and/or how to prevent it? Generally the phone crashes, I have to remove the battery and then it re-installs Windows.
Thanks
Click to expand...
Click to collapse
That sounds like a hardware problem!
When my X1 ever crashed, I've never lost anything!

Which rom do you use, how do you do your backups?

I'm using a WinMo 6.5 ROM. Can't find the link at the mo, but it's a ROM designed to replicate an official SEX1 release - no junk or anything included.
I've only had this problem since using this ROM, but my handset was always notorious for screwing up factory resets. A few weeks ago my files slowly became corrupted until such time as the device became unusable.

You're probably using gtrab's R5.07.
I've noticed the reset bug as well. Out of interest, are you using the WinMo alarm feature?

Leddy said:
You're probably using gtrab's R5.07.
I've noticed the reset bug as well. Out of interest, are you using the WinMo alarm feature?
Click to expand...
Click to collapse
Hi Leddy. Yes to both. I re-flashed with a 6.5.3 ROM and am hoping all will be well now.

had the same problem with one of the touch-it ROMs. flashed to a new ROM and it never happened again.

Solution to this problem is to flash a stock rom and after that flash the custom rom back. It fixed my phone one time when I had this and also another diamond was fixed this way with the same problem

Same problem with the SXGU 1.5 Plus ROM. Massive shame. Just lost a load of stuff too!

this problem and any problem cannot be rom related unless everyone using the same rom experiences the same thing... in other words, if you experienced a problem after flashing any rom and others haven't with the same rom, then i suggest to check elsewhere like how u flashed, what u flashed before and so on....
problems after flashing are mostly solved by flashing a stock rom, task29 and flash via RUU and not SD method

not true.
this can and can not happen on the same rom.
there are two possibilities:
- it's rom related and many, but not all are getting it - change rom-version.
- something's messed up which task29 will NOT fix - flash stockrom
i had the second one and it took me some time to figure out that task29 didn't fix it. stockrom performs task28, if i'm not mistaken.
it's definitely NOT hardware related!

dude, if the problem lies within the rom, which means everyone using the same rom should experience the same very problem... if not then its either hardware related or files remained on the device from previous flashes that caused conflicts with the current rom
check this
Intratech said:
Never had this problem and I've been running Xperia X1.5 Home Plus since it's release. I suggest flash back to generic R3A ROM, task29 and then flash to whichever ROM you chose to run.
Click to expand...
Click to collapse
i can either be hardware or conflicts with previous files, but definitely not a rom issue since others have no problems...
and this goes for any rom its common sense to understand that
i remembered i had a perfect device few weeks ago, i flashed a rom and tested some stuff, didnt like it so i went back to the rom that was perfect, unfortunately, my device had tons of SOD and resets, i was pissed and had to use a rom i hated, but then i remembered someone sayign something about flashing stock rom again, so said so done, i task29 then reflashed that perfect rom, right now im still using it with no issues whatsoever

dude, you're not talking to a total n00b here... so maybe you could change your tone a bit?!
if your logic was to be true, everyone on the same rom would get SoD if the rom has it - but... and the same goes for this hardreset-thingy - it's not "either everyone gets it or noone", it's an individual bug. but some roms seem to be more prone to have it than others.
sometime this year (about february?) you'd see reports of this in almost every rom-thread. it's rather rare now... (assisted, but not only caused by task29)
and again: it's nothing to do with faulty hardware - or it would be uncurable.
dude.
edit:
and that "someone saying to flash stockrom..."? that could (!) have been me, as i left a note on that some time ago in task29-thread. (i said "could"!!!)

caliban2 said:
dude, you're not talking to a total n00b here... so maybe you could change your tone a bit?!
if your logic was to be true, everyone on the same rom would get SoD if the rom has it - but... and the same goes for this hardreset-thingy - it's not "either everyone gets it or noone", it's an individual bug. but some roms seem to be more prone to have it than others.
sometime this year (about february?) you'd see reports of this in almost every rom-thread. it's rather rare now... (assisted, but not only caused by task29)
and again: it's nothing to do with faulty hardware - or it would be uncurable.
dude.
edit:
and that "someone saying to flash stockrom..."? that could (!) have been me, as i left a note on that some time ago in task29-thread. (i said "could"!!!)
Click to expand...
Click to collapse
lol i dont think u understood me, as i said, it is not rom related...
if a problem was caused because of a fault in the rom, everyone using the rom would experience the same problem, its not logic, its common sense...
why do we task29? to remove files from previous roms right? which means that it has nothing to do with the rom... chances are it could be hardware related too, note i said chances... for who dont know, windows 7 isthe first OS from M$ that can actually wipe a partition clean, leaving no trace of anything behind that no forensic kit can detect... however we task29 our devices to remove these files that remain and cause conflicts with newely installed roms
if i delete solitaire.exe from the sys, cook a rom, no one would get solitaire to play by default, why? because its a default rom issue caused on my part so no one will get it to work just like that
sometimes before we think about criticizing something we use, we first should ask if anyone is having the same problem, if all does who used the same product, then the problem is the product itself, you dont have to be a noobie/senior to figure that out... its plain common sense
btw, sometimes i personally have 2 xperias here with me flashing, wanna know the weird thing? my own device causes problems when flashing roms at times, my friend's xperia flashes with no problems, no SODS nothing...
as i keep saying, its only rom related if everyone using the same rom gets the issue

rofl, stubborn he is...
okay, it's not rom-related as in "the rom is faulty". but just because noone else gets it with a certain rom doesn't mean it's not related to the rom at all. as i said, there was a time when many roms were affected (but never all users!), it was probably build-related (234xx - something around that).
it's not hardware. that's for sure.
but there are individual circumstances (something messed up in bootloader - well no, not bootloader, but in that area, you get me) which can cause this. most of the time these are cured with task29, but not always - then you need (!) stockrom.
so let's settle on this, shall we?
whoever experiences this, try task29. if it doesn't help, flash stockrom and try custom-rom again.
about your solitair.exe:
if it was always that simple, bugfixing would be very easy because everyone would expirience the same bugs. (if caused by rom) well, it isn't that way, we all know that.
read this, i've been the only one with this bug on that particular rom-version. and i've tried a lot of things. i even got itje to make a test-rom with his old kitchen because of this... (guess his reaction when i told him what cured it, hehe... )

lol dude, i know what u are trying to say, but to say because not everyone using the roms gets the problem doesnt mean its not rom related just doesnt make any sense, if its rom related then everyone using the rom should experience it, how can a product have a defect with only some people and not others when everyone is using the same exact product??? ever thought of the fact that it might be something else causing the problem outside the rom by forcing such issues to occur?
dont think my device never had issues, i did, but never once i re-developed a rom because of an issue... reflashing stock and task29 after fixed all my issues of instability... that rom i told you about that was perfect, you think i re-cooked it because my device was unstable? no, because i know that my device was perfect before so it was not the rom, but it was my hardware not functioning as it should when flashing, meaning the system was never clean of previous files, so conflicts occur... remember that poster who flashed a rom and the bootscreen from the previous was still on the device after flashing a new rom???? thats what im talking about
... but i do agree that it has something to do with the bootloader...
do you know that some of us have never seen the headphone icon on any stock rom via SEUS, some people seen it some havent, the only time i see the icon is when i flash a custom rom, but i have never seen it on any stock rom since i bought my x1 brand new from sony...
its either

My experience would lead me to disagree with both of you. If I flash back to my previous ROM, everything's fine; if I install Gtrab's or Spike's I get this damn bug, but it's different on each. With Gtrab's the phone formats itself; with Spikes' the phone boots into a black illuminated screen after a crash and requires re-flashing, or all data wiping.
It would be great if I could get back today's data though before flashing a stock ROM. Anyone know how I might?
Edit: It booted once when I connected the USB and took out the microSD, (I got my data!) but now it hangs on the SE boot logo. IE, ROM erased. I'll give the ROM one more shot since it really is brilliant other than this bug and an issue with the keyboard.

at45 said:
My experience would lead me to disagree with both of you. If I flash back to my previous ROM, everything's fine; if I install Gtrab's or Spike's I get this damn bug, but it's different on each. With Gtrab's the phone formats itself; with Spikes' the phone boots into a black illuminated screen after a crash and requires re-flashing, or all data wiping.
I'll try the stock ROM idea, but I haven't been able to find one. It would be great if I could get back today's data though before doing that. Anyone know how I might?
Edit: Oh, it boots if I 1) connect the USB and 2) take out the microSD card. Yay!
Click to expand...
Click to collapse
dude, if you havent tried to flash the stock rom you cannot say u disagree with us, try it first and see...
so many people are currently using x1.5 home plus, check the rom thread and see for yourself, no one else is having your issue... flash the stock rom, there is a thread with the stock rom on the rom forum... then report back to us.... btw, i too am using x1.5 home plus as from today and i reinstalled all my apps

Auto-hard resetting...

Alright people, I consider myself pretty smart when it comes to the world of WinMo, but this is a problem that I just cannot nail down. I have been using the OLD STAXXXSTYLE WM6.5.1 ROM for as long as I've had my Kaiser, and decided to upgrade to his last stable version, well I did and everything seemed fine. After 3-4 hours of using my phone, it went all unresponsive on me...no big deal so I soft-reset it.
Well, it took FOREVER at the initial bootscreen, then eventually continued on and went back to being all-"Oh hai, set me up plox!", like I had hard-reset it. So I chalked it up to weirdness and continued through and re-set it up and such.
Well, long story short, this has happened 2 or 3 more times since then. I just cannot figure out why it keeps doing this. I thought it was my HardSPL since I have read that this can happen with older versions, so I flashed upto 3.34DAVESHAW, and it still continues. I am running radio 1.71.09.01 and have never had any problems with this Kaiser up until now. ANY help is GREATLY appreciated. Thanks.

seems like bad rom. hard reset usually comes if there are unrepairable memory problems. I had this while using certain kitchen, after I changed to different kitchen and did the same mix of rom, all was good.
Before, when I extracted 20MB zip, some of the files always went wrong and hard reset followed.

in the FIRST post of staxxtanium ROM thread, the fourth line reads:
Unless you have Issues, Stock wont be necessary, Well I personally don't have issues but to be on safe side, flash stock first. Those previously on Ultimate X2.V11 its a MUST that you flash Stock first-
Click to expand...
Click to collapse
the chefs of nearly all WM6.5(.x) ROMs advise flashing stock ROM before flashing a WM6.5(.x) ROM (even if you already have a 6.5(.x) ROM). some chefs are more clear about the reason, i.e. most chefs will clearly state that this step will avoid unexpected hard resets later on. it seems staxxthedan did not feel it necessary to state the exact reason for his quote above. still, you are having an issue and this is the first suggestion staxxthedan gives for any "issues".
also, further searching would have revealed this solution.

um, what happens with another rom?

Wow, way to be an asshole ASCIIker. I have ALWAYS reflashed to stock before flashing to something else. And yes, it happens with ANY ROM from ANY cook that I have tried in the past few days.

well then you should clarify in your opening post with all pertinent information especially your flash procedure so that the obvious (to you and me) can be ruled out first hand.
not trying to be an asshole, i did try to help, given the limited information you provided. but the information was just that..."limited"!

hello mate
i have the same problem you posted here
my mobile is HTC TyTn II
i've tried many radio versions hardSPLs roms
and i cannot find any solution
my question is : did u found any solution since it's an old post? i hope yes

Auto Hard reset
hello mate
i have the same problem you posted here and my mobile is HTC TyTn II
i've tried many radio versions hardSPLs roms and i also cannot find any solution
Do u found any solution since it's an old post? i hope yes. I used Shifu and Gangster wm6.5
I tried with different Radios and Harspls but no lukc.
Your prompt action is highly apprecaited.

[Q] How to "virginize" HTC Touch HD?

Hi People
I am not sure whether this is the correct section, but it is still ROM related.
Recently, my phone does not want to wake up sometimes...I press the button and the screen remains black..after few minutes it goes back on but is unresponsive..I have to reset my phone...this is very annoying as for example my alarm also did not sound becuase of this - I was almost late for work...
In conclusion, my 560 EUR phone is not reliable anymore and is still under warranty - I want to have it replaced.
That is where my question comes - How can I completely virginize my phone?
I always used USPL while flashing...
I will perform Task29 and should I flash some stock ROM before I go to give it to service?
If so, what is the appropriate stock ROM for my phone?
What else should I be aware of when virginizing?
Please help me guys, I really want my phone fixed or replaced - it could be the motherboard causing this and I dont want my phone to die...
THANK YOU!!

Sopis said:
Hi People
I am not sure whether this is the correct section, but it is still ROM related.
Recently, my phone does not want to wake up sometimes...I press the button and the screen remains black..after few minutes it goes back on but is unresponsive..I have to reset my phone...this is very annoying as for example my alarm also did not sound becuase of this - I was almost late for work...
In conclusion, my 560 EUR phone is not reliable anymore and is still under warranty - I want to have it replaced.
That is where my question comes - How can I completely virginize my phone?
I always used USPL while flashing...
I will perform Task29 and should I flash some stock ROM before I go to give it to service?
If so, what is the appropriate stock ROM for my phone?
What else should I be aware of when virginizing?
Please help me guys, I really want my phone fixed or replaced - it could be the motherboard causing this and I dont want my phone to die...
THANK YOU!!
Click to expand...
Click to collapse
Dear friend,
first let's know what ROM have you installed on your device? I'm sure the problems that you've mentioned are not hardware problems, and in fact they are related to the ROM, since I have the same problem sometimes with some ROMs and some application. I had problem with alarm clock several times, just after flashing Energy ROMs! I reported this matter, but nobody paid attention, so I downgrade my device to kwbr WM6.1+sense2.1, now I have no problem with alarm clock.
about the another problem, I still have this problem, but I think it is related to WKTask! sometimes when I turn my device off by WKTask shortcut, I encounter the problem that you pointed, but it's not the case if I turn it off by hardware key.

Same question
I have used HSPL
and have tried several roms
Few days back my touchscreen stops responding.
flashed differnet roms but no difference. so i think its a hardware problem
(kinda works sometimes so may be just a loose link)
I want to send it for repair under warranty.. so can someone tell me how to get back to factory settings of Touch HD (German)
Prajwal

Ah, now we have 2 different cases.
1. Flash with USPL
2. Flash with HSPL
I'm almost sure that "virginizing" is described on HD Wiki, but nevermind...
Case 1. is nice and easy...
Go to HTC site and try to find update for your device. Before that, write serial and IMEI (not sure which one is needed, both are under the battery).
If there is "No suitable update", then you are in big trouble... try to find what was original ROM which was on device when it was delivered.
Case 2. is bit difficult... you HAVE TO remove HSPL and restore original SPL, then proceed as described in case 1. I think for german ROM was SPL 1.54
However, I have bought my device recently (with German ROM), but maybe earlier devices had some other SPL...
Check HD Wiki anyway...

prajbio said:
I have used HSPL
Click to expand...
Click to collapse
Ah... [TUT] Dummies guide: flashing 1.56+ roms [v 2.0] - [HSPL][USPL] has at least one important thing for you: stock SPL...

Thanks Guys...
I didnt think of checking the wiki...
Ill go there, and also do what you suggest...
I guess the issue is not related..I flashed a new ROM from different cook and it happened.
Nevermind...I will virginize and then have it fixed or replaced...
THANKS!!

Bodisson said:
Ah, now we have 2 different cases.
1. Flash with USPL
2. Flash with HSPL
I'm almost sure that "virginizing" is described on HD Wiki, but nevermind...
Case 1. is nice and easy...
Go to HTC site and try to find update for your device. Before that, write serial and IMEI (not sure which one is needed, both are under the battery).
If there is "No suitable update", then you are in big trouble... try to find what was original ROM which was on device when it was delivered.
Case 2. is bit difficult... you HAVE TO remove HSPL and restore original SPL, then proceed as described in case 1. I think for german ROM was SPL 1.54
However, I have bought my device recently (with German ROM), but maybe earlier devices had some other SPL...
Check HD Wiki anyway...
Click to expand...
Click to collapse
From my experience, HTC is usually ok as long as the SPL is an official one. No matter the one came with your phone or other older/newer version.

Sopis said:
Hi People
I am not sure whether this is the correct section, but it is still ROM related.
Recently, my phone does not want to wake up sometimes...I press the button and the screen remains black..after few minutes it goes back on but is unresponsive..I have to reset my phone...this is very annoying as for example my alarm also did not sound becuase of this - I was almost late for work...
In conclusion, my 560 EUR phone is not reliable anymore and is still under warranty - I want to have it replaced.
That is where my question comes - How can I completely virginize my phone?
I always used USPL while flashing...
I will perform Task29 and should I flash some stock ROM before I go to give it to service?
If so, what is the appropriate stock ROM for my phone?
What else should I be aware of when virginizing?
Please help me guys, I really want my phone fixed or replaced - it could be the motherboard causing this and I dont want my phone to die...
THANK YOU!!
Click to expand...
Click to collapse
since you just use USPL, you just need download the official ROM from HTC page by inserting your HD serial number under ROM download. then flashed it. it think this step will solve your warranty issue.