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.

Weird Problems & Diamond almost dead (software/ROM)

Some days ago, i've flashed my phone to get an "up-to-date" ROM. I chose "PDACornerIllusion 21139" of 2009.03.06. All went fine excepting the keyboard of my GPS wont work anymore (dunno why of course), so i re-flashed with another ROM.
I was surprised that my phone kept the CornerIllusion BootScreen, but i didnt care.
All of a sudden, after having soft reset the ROM i chose (the 2nd one), for an installation of some proggie. The ROM restart as brand new asking me to reset the screen, the clock, date etc... losing all my content and customizations. Then i couldnt sync with Outlook after the first sync i've done minutes ago (error code 800004005). I've decided to soft-reset the phone, and now, TF3D wont even start, (it selft tries to start several times, then gives up), AND the programs lists is all broken, no shortcuts left and the games folder is named *h1/4Eg+ç^, nothing works anymore.
I flashed with about 4 roms (including Aztor one), resulting in the same mess.
Does it have something to do with the first one "PDACornerIllusion 21139" and its still remaining BootScreen?
Can i flash my phone from its roots, to get rid of this ?
As it's maybe not the "fault" of PDACornerIllusion, i write this in this section of the Diamond general thread and made a double post at PDACornerIllusion development thread

I suggest you perform a hard reset before flashing any new rom and that you use the traditional "flash-from-PC-using-ActiveSync-connection" method to flash.
And above all I wish you luck!

What was the other ROM you flashed? I am curious.
rondol1 suggests you hard reset prior to flashing a new rom. I suggest you hard reset after flashing a new rom. Net result is probaby much the same. You could even just do a hard reset now with whatever is loaded and things will probably improve. Main thing is...whenever you flash a rom do a hard reset straight after loading it. I always do this religiously and with the exception of one recent rom I tried I have never had a problem.

First of all, thank you both for trying to suggest hints, i really appreciate it.
I've never hard reset the ROM before or after having installed a new one. I never have a problem before.
For the last 2 months, i was on NEON 1.28, then i've decided it was time to update seeing the new features of the more up-to-date ROMs
I've just reflashed it (an hour ago) with PDACornerIllusion 21139, i've hard reseted before and after. let's see how it turns out ....
I've tried NATALY, CLOUDY, MORNA & AZTOR, no luck with any of them, all died after a soft reset or after the 1st sync (reconnecting for a 2nd sync).
Maybe the problem comes from the very root of the phone (like BIOS in a PC, dunno), maybe something in there got corrupted. How to repair it if my guess exists and is it repairable?

dunnno said:
I've never hard reset the ROM before or after having installed a new one.
Click to expand...
Click to collapse
There in lies the problem.
I bet you will be fine from now on. Don't ask why you need to do the hard reset - as no one has been able to give a definitive answer - But it is a well known step that many chefs recommend post flash - just do it from now on and you wont regret it.

logger said:
There in lies the problem.
I bet you will be fine from now on. Don't ask why you need to do the hard reset - as no one has been able to give a definitive answer - But it is a well known step that many chefs recommend post flash - just do it from now on and you wont regret it.
Click to expand...
Click to collapse
completely agree with logger - hard reset after you flash any ROM. I haven't used PDACorner - so can't say for sure... but do the flash via CustomRUU once... when the new ROM is flashed... do a hard reset as soon as it's complete..
good luck!

let's see then, >>>>crossing fingers<<<<

I've had this happen a lot lately as well. Might have something to do with the newer SYS? Anyway, hard reseting hasn't always fixed it for me. However, flashing back to the Sprint stock ROM (or HTC stock for you GSM guys) then flashing a new custom ROM has always done the trick. Maybe because the stock ROMs are bigger and "clean" out the memory somehow? At any rate, flash stock and then you're good to go. No permanent damage.

no luck, after a 2nd soft-reset, the phone is asking "touch the screen to configure for the 1sy use blablabla", all data's lost again & again...
what do you mean by stock Rom ? the rom that came with my phone when i've bought it ?

I've got the same problem with the Diamond rebooting like a hard-reset. But I always did a hard-reset after a fresh install. I blamed it on the rom and tried several others, including donsalari's "Clean Basic Rom", the Gen.Y Sense 2.1 and 2.5 versions and an older Aztor rom. Same problem every time, the first reboot after changing the device locale works fine, then I set the whole phone up properly and on the next reboot it will come up as if had performed a hard reset.
Additionally, the file system on my internal storage got corrupted somehow, had to reformat. At some point, I also had the impression that data on the phone memory got lost gradually. First the Contact's numbers got replaced by some nonsense characters, then there were numbers and contacts missing, and finally I had no contacts at all. ActiveSync stopped working so I was in the middle of a trip without my phonebook...
I've got two hypotheses:
1) The Gen.Y bootloader messed with the phone (Had tried the Sense 2.5 Gen.Y rom before donsalari's)
2) Flash controller or Flash itself is broken
@dunnno: I suggest you rename the thread to something like "diamond hard-resets on 2nd reboot after rom install"
edit: oops, just realised I resurrected a very old thread... Maybe there's a fix already?

My diamond still suffers from this problem. I tried it again and again with different roms but everytime, at some point all my configuration is lost and the diamond reboots like after a fresh install. Can anyone please help?

I'm having this problem as well :|
Grr, I have to rely on my phone for so much, but it just doesn't want to work correctly.
Help is immensely appreciated.

Well, I got mine to work, I just flashed the stock HTC ROM and everything has gone back to normal. H3PO, I suggest you give that a shot if you are still having problems.

I had these problems when I first started flashing my Diamond with custom roms.
Now I always flash my carrier stock rom first, then hard reset, then flash custom rom, then hard reset and I never have any problems. I have no idea why flashing the stock rom first stops the problems but I haven't had any problems with the dozens of roms I've flashed using this method.
Also I always flash from internal storage, but others prefer using MTTY

I still have some problems with the Contact Database, but flashing some stock O2 Rom solved the "reboot as new" problem.

TyTN II problem restarting

When i restart it activates the first time installation thingie... it does it even with shutdown and soft reset and hardreset.
i used 3 roms and they all did the same thing
enter the first time installation thingie
can any1 help me?

I got caught in a loop one time when i was trying to do a hard reset. When it came back from clearing the memory and I did the calibrate screen thing, I would soft reset prior to the bloatware installation. When it restarted it would go right back into the clearing data screen of the hard reset.
Eventually I let the bloatware install, then did a hard reset and that seemed to clear it out.
Not sure if that will help.

I have no idea what you just said .. :$ sry
but is there a way to TOTALLY clean my Pocket pc?

chimera_nl said:
I have no idea what you just said .. :$ sry
but is there a way to TOTALLY clean my Pocket pc?
Click to expand...
Click to collapse
A Hard reset will wipe out everything that you have installed on the phone, and you will be back with the operating system, whether it is a custom rom or an ATT Rom or HTC Rom.
Are you talking about wiping the "hard drive" clean with no operation system? I do not know how to do that, but why would you want to do that anyway.

phooey, i'm having similar problems... hard reset (holding soft keys and pressing reset with stylus) doesn't stop the issue from happening again. -- back to factory reset when rebooting either soft or hard. not sure if this is the same issue...if so i double posted sorry.

hey jklarich, you have posted a new thread:
http://forum.xda-developers.com/showthread.php?t=564537
...so consider this post of mine a reply to this thread as well as the one created by you (referenced above).
NEITHER of you have mentioned WHICH ROMs you tried when the problem started.
NEITHER of you have mentioned the HardSPL version(s) you have on your devices.
NEITHER of you have categorically clarified that you have gone through the steps in the FAQs of the ROMs you've tried.
BOTTOM LINE: always provide more information!
now with lack of information, using my "mind reading skills" (well actually they're just logical, deductive, and analytic approaches with a touch of human psychology and n00b-behavior-predicting voodoo magic), i will reason as follows:
seeing as how BOTH of you are junior members and how BOTH of you mention experiencing the issue with THREE ROMs, i suspect you must have coincidently tried the top three most popular WM6.5 ROMs, which would be TPC's, abusalsa's PDA Corner, and one other.
THIS IS A KNOWN ISSUE WITH NEARLY EVERY WM6.5 ROM! it is mentioned in the FAQs on the first page pertaining to each of the popular WM6.5 ROMs for the kaiser. the workaround/solution is mentioned in the FAQ!
the above "flame" is based solely on the assumption that you both tried WM6.5 ROMs without reading/following the suggestions in the FAQs. if you have indeed tried the magical step in the FAQ that should fix this problem but yet the problem remains, then i'm sorry about the unnecessary flame and i hope you find the solution to your problem.

Even though the TPC ROM says it's worked out, install the factory ROM first. That fixed the problem for me. Sorry, but I think this is valid only because TPC states quite clearly that they think they sorted out this problem on their thread.

[GUIDE] What to do when your Blackstone Starts Hanging?

Hi,
My experience today is the motive of me writing this guide to help most of you out of this problem and eliminate the Fear that you will have of you blackstone might gone bad (hardware fault).
ok,
here is what happend to me today.
I had XannyTech Rom flashed on my phone and i really felt i found something interesting about another ROM so i decided to flash that one.
after a smooth flashing, the phone booted and i started syncing using myphone.
left the phone on the desk for a while, came back and found that the device is not responding to the power button, poked that red button and the phone get's stuck at the "smart mobility" screen!!
Hard resetted the phone and started over, again the phone hanged.
i thought that it's maybe a bad flash! so i downloaded the file again and flashed again.
still the same!!!!
decided to go to the old ROM ,
still after a while i get the same result!
notice that i hard resetted after each and every flash!
so what did i do?
[Guide]
Hard Reset the phone, check if it's a software you installed or if it happens even on a pure ROM.
If the problem still exist, Confirm it's not a bad flash! flash again the same ROM.
If you still have the same symtoms, go to HTC website and download the latest OFFICIAL ROM from there.
Run the RUU from your pc (Don't worry about HSPL, it's protected so you will NOT have to HSPL your device again, Thanks olinex)
Test your phone with the new official ROM (in my case -blackstone- it's a 6.1 rom ). Mostly everything will be back to normal.
flash the rom of your choice.
I don't have a real explaination about this (maybe someone with more experience can do) but it works! and even the ROM works faster .
Hope you find this usefull.
Regards,
Adel

I will remember this if it happens to me!
Thank you!

For me, with the HSPL, when I went back to original rom, I had a big problem with color. I flashed to old SPL too, and so, color where good after

Wiki
Not a huge problem, it's well documented
Understanding 1.56 Roms (Greenscreen issue & Flashing)
edit : oops, the link is accessable from the wiki

re the topic:
Looks like Viagra cant fix this issue then

anaadoul said:
Not a huge problem, it's well documented
Understanding 1.56 Roms (Greenscreen issue & Flashing)
Click to expand...
Click to collapse
Hi
You should fix your link and put wiki instead if forum

Jal84 said:
Hi
You should fix your link and put wiki instead if forum
Click to expand...
Click to collapse
it is good to see that you have followed the link

anaadoul said:
I don't have a real explaination about this (maybe someone with more experience can do) but it works! and even the ROM works faster .
Click to expand...
Click to collapse
Well, I am not sure, but it seems that Official ROMs not only flash your phone, but also "format" it.
You may want to have a look at this post (http://forum.xda-developers.com/showthread.php?t=540290) for more references, but the fact is that "flashing" means issuing some commands to the phone. These commands are all about uploading the ROM data in the appropriate section of the NVRAM/EEPROM (I am not an expert, but I think I am more or less near to reality with such a description).
In the Official ROM's case, more commands are issued and some of these commands "clean" completely your phone, making route for a clean installation and a good one.
I don't know (I am not a cooker, nor an expert) why cookers can't or won't issue those commands in their ROMs, but soon after flashing an official one, you have a "clean" phone that is not affected by random behaviour, due properly to the commands that only official one's issues during the flash.
Hope this may help
Regards
Ehol

Ehol said:
Well, I am not sure, but it seems that Official ROMs not only flash your phone, but also "format" it.
You may want to have a look at this post (http://forum.xda-developers.com/showthread.php?t=540290) for more references, but the fact is that "flashing" means issuing some commands to the phone. These commands are all about uploading the ROM data in the appropriate section of the NVRAM/EEPROM (I am not an expert, but I think I am more or less near to reality with such a description).
In the Official ROM's case, more commands are issued and some of these commands "clean" completely your phone, making route for a clean installation and a good one.
I don't know (I am not a cooker, nor an expert) why cookers can't or won't issue those commands in their ROMs, but soon after flashing an official one, you have a "clean" phone that is not affected by random behaviour, due properly to the commands that only official one's issues during the flash.
Hope this may help
Regards
Ehol
Click to expand...
Click to collapse
Good explaination!
also while i was extracting a shiped ROM i got an unknown nb file which might be responsible for this?
what you have said means that as long as you are flashing a larger sized ROM you should have no problem, but once the new ROM have a smaller size then you will face some issues?!
oh, one more thing.
after formating the phone with the stock ROM, i noticed that it runs much faster (around 15% performance increase) can anyone try flashing shipped ROM then the same one he was using and confirm this?

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