Screen problem after flashing ROM developed by PhamQuang Build 23047.5.3.0 - Touch HD Windows Mobile ROM Development

Hello,
Today I reflash my HTC Touch HD (the first official ROM from December 2008). First I made HardSPL unlock and then changed the ROM (http://forum.xda-developers.com/showthread.php?t=555137).
Since then, the words smart mobility on the first screen changes color after 10 seconds (maybe one color from RGB disappears). But if I press the buttom on the top twice, the color is ok. In this state the text and images are absolutely unreadable. In fact, I would not mind this flaw, but it makes another mistake. When I tap on something, so very often happens that stops working touch layer. I recognised that, because hardware buttom volume up/down works, display indicate loudness, but taping on screen doesn't work. Sometimes after a few tens of seconds it makes better, sometimes helps only software restart.
Before I recognised, that the problem is probably permanent, so I reflash ROM http://forum.xda-developers.com/showthread.php?t=542104 and then http://forum.xda-developers.com/showthread.php?t=547278
Then I tried to save my device by official ROM (_HTC Touch HD_MR_2009_RUU_BlackStone_HTC_Europe_1.56.401.0_Radio_52.62.25.34_1.13.25.24_Ship.exe), from this site: http://www.htc.com/europe/SupportDownload.aspx?p_id=179&cat=2&dl_id=533 and using this code HT849KD07000
Finally, I did SPL Stock.
But the problem is worse and dosn't work gsm module.
Once it shows this message: A problem has occurred with gwes.exe. and if I want to send to microsoft ...
Please hepl me. :-(
Thanks a lot.

I had the same problem
First flash HSPL 1.56 and your colours will still look funny
then flash a new ROM and your colours and everything else will be fine
welcome to the club

USPL the Best flashing tool
Si1m said:
Hello,
Today I reflash my HTC Touch HD (the first official ROM from December 2008). First I made HardSPL unlock and then changed the ROM (http://forum.xda-developers.com/showthread.php?t=555137).
Since then, the words smart mobility on the first screen changes color after 10 seconds (maybe one color from RGB disappears). But if I press the buttom on the top twice, the color is ok. In this state the text and images are absolutely unreadable. In fact, I would not mind this flaw, but it makes another mistake. When I tap on something, so very often happens that stops working touch layer. I recognised that, because hardware buttom volume up/down works, display indicate loudness, but taping on screen doesn't work. Sometimes after a few tens of seconds it makes better, sometimes helps only software restart.
Before I recognised, that the problem is probably permanent, so I reflash ROM http://forum.xda-developers.com/showthread.php?t=542104 and then http://forum.xda-developers.com/showthread.php?t=547278
Then I tried to save my device by official ROM (_HTC Touch HD_MR_2009_RUU_BlackStone_HTC_Europe_1.56.401.0_Radio_52.62.25.34_1.13.25.24_Ship.exe), from this site: http://www.htc.com/europe/SupportDownload.aspx?p_id=179&cat=2&dl_id=533 and using this code HT849KD07000
Finally, I did SPL Stock.
But the problem is worse and dosn't work gsm module.
Once it shows this message: A problem has occurred with gwes.exe. and if I want to send to microsoft ...
Please hepl me. :-(
Thanks a lot.
Click to expand...
Click to collapse
Lyptherion said:
First flash HSPL 1.56 and your colours will still look funny
then flash a new ROM and your colours and everything else will be fine
welcome to the club
Click to expand...
Click to collapse
i highly recommend you use USPL : I still yet have to see someone who had a problem after using USPL. This is even endorsed by Dutty Throy - Moderator ROM Cooker par excellence!
look here
http://forum.xda-developers.com/showthread.php?t=505377
and here
http://forum.xda-developers.com/showthread.php?t=462347
format your sd card using fat32 (full format) (if you are a frequent flasher I suggest you get a small capacity sd card – 1Gb - and devote this only for flashing)
rename the RUU_signed.nbh to BLACIMG.nbh and pair this with ROMUpdateUtility -(application file). copy this two files in you formatted sd card.
then using Digital Outcast's USPL GUI: look here
http://forum.xda-developers.com/showthread.php?t=508361
flash the ROM.
please let me know once you've done this succesfully, i wish you the best of luck!

Lyptherion said:
First flash HSPL 1.56 and your colours will still look funny
then flash a new ROM and your colours and everything else will be fine
welcome to the club
Click to expand...
Click to collapse
Thanks a lot, it works and finaly I din't have to reflash a ROM.

jigners said:
i highly recommend you use USPL : I still yet have to see someone who had a problem after using USPL. This is even endorsed by Dutty Throy - Moderator ROM Cooker par excellence!
look here
http://forum.xda-developers.com/showthread.php?t=505377
and here
http://forum.xda-developers.com/showthread.php?t=462347
format your sd card using fat32 (full format) (if you are a frequent flasher I suggest you get a small capacity sd card – 1Gb - and devote this only for flashing)
rename the RUU_signed.nbh to BLACIMG.nbh and pair this with ROMUpdateUtility -(application file). copy this two files in you formatted sd card.
then using Digital Outcast's USPL GUI: look here
http://forum.xda-developers.com/showthread.php?t=508361
flash the ROM.
please let me know once you've done this succesfully, i wish you the best of luck!
Click to expand...
Click to collapse
Sorry, but I am not sure if I twigged your post. (I dont speak english well) But never mind, the solution of Lyptherion works.

I believe what jigners was suggesting was for you to use USPL instead of HSPL. Both work just as good as each other, though USPL is temporary and would not void warranty should something happen to your device. HSPL is referred to as permanent as it stays on device unless you remove it so would void warranty if something happened to device while it was still on.
But I'm glad you have solved your issue.
Thread closed

Related

[TUT]Flashing the easy way

Hey everyone!
Read lots of threads here on the xda-developers forum, many questions, many answers, lots of "good guys" who are willing and able to help (many have helped me, thank you goes to them and all the others).
The bottom line:
Saw many many questions concerning flashing, bad flashes, error messages and so on.
I really don't know WHY people won't go for the easy way?
Flashing from a PC involves a USB connection through Activesync/WMDC, an application, we all know the procedure thanks to racerx_ (http://trinityguides.info). There are so many things that can go wrong: think about it, from unplugging the device, app error, comm error, power drop, connection drop, system hang and so on.
I don't know about the rest of you but I have done it the hard way but also learned to do it the easy/safe way. There's nothing more to the story than flashing from SD card. Procedure is well described in the Wiki (http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing).
I mean, all you have to do is press three buttons and wait for the flash, no risky connection drops, error messages, driver incompatibilites (see Vista problems), no app hangs.
I have tried many ROMs from over here and except for my first two flashes (first was Des' Crash Proof SPL, second was a cooked ROM) I've made them all using the SD card method and never got an error nor a situation with it.
So here's the question: why won't people flash the easy way?
well, have you actualy tried this procedure before posting this?
banesi said:
well, have you actualy tried this procedure before posting this?
Click to expand...
Click to collapse
Read my post once again, carefully.
hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom
This procedure brings boot loader screen, with three colors, it doesn't bring anything similar to that image posted there.
banesi said:
hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom
This procedure brings boot loader screen, with three colors, it doesn't bring anything similar to that image posted there.
Click to expand...
Click to collapse
Follow the steps carefully.
1. SD card with FAT32 and no label (it can contain other files, no need to wipe it)
2. Renamed nbh file to TRINIMG.nbh placed on SD card root
3. Power+Camera+Reset
4. Follow instructions on screen (Power button to brgin flash and Soft reset when prompted at the end).
It don't get any easier!
It SHOULD work.
Totally agree, I don't understand why ppl persist with the multitude of errors that crop up from flashing via active sync.
Using the SD card you can chuck a few ROMs on board to test and just rename each in turn to TRINIMG.nbh, move it to the SD root and enter boot loader.
Before I test a new ROM I make a static settings image with SPB Backup so I can flash back to the old ROM and restore back to how it was in a jiffy.
Just to point out for some ppl, some of the ROMs here are packaged into EXEs, you will need to extract the contents and only use the file named RUU_signed.nbh.
This process can also be used to flash Radio ROMs in case you flash a ROM that includes a radio that you don't like/use.
Good thread
P3600i saga continues
I wonder if the SD Card method works on the P3600i? According to the Wiki, it doesn't bypass the SuperCID check.
Olipro has modified his SPL-Trin to work with the P3600i. But so far there's still no definite way to flash it. No Hard-SPL, splxploit don't work, same for JumpSPL. So maybe this is the way? Any opinions?
remofo said:
I wonder if the SD Card method works on the P3600i? According to the Wiki, it doesn't bypass the SuperCID check.
Olipro has modified his SPL-Trin to work with the P3600i. But so far there's still no definite way to flash it. No Hard-SPL, splxploit don't work, same for JumpSPL. So maybe this is the way? Any opinions?
Click to expand...
Click to collapse
No, sorry, it's not the way.
Flashing from SD card is not a workaround for bypassing SPL.
You still have to have some kind of a Hard SPL installed.
Please check the Wiki.
evojulz said:
This process can also be used to flash Radio ROMs in case you flash a ROM that includes a radio that you don't like/use.
Click to expand...
Click to collapse
...and also bootscreens.
In other words, this method can flash any nbh file which could be flashed through the update utility method.
Easy and reliable
Fully agree with you tnyynt!
I always flash using the SD method.
Sometimes I even download the new nbh and keep it on the SD and upgrade later on when having time, not connected to a Pc... (I also have all the cab I need on my SD card).
Quick, easy and reliable (done many times).
Would be fine if the nbh would be released on this forum (rather than the .exe package).
Would allow to download them directly from the Trinity. i.e.: no more need for a Pc !!!
I always use this method, it is the only one that works for me and it's the most convenient I think.
I tried this method several times, but I was never able to get it work.
Yes I followed instructions carefully, but no. I only get three colored bootloader screen, that's it. No button to start flashing, nor screen that looks like that photo in wiki.
I really wanted this to work, cause I have an OsX. Since I couldn't get it to work I had to install xp and use it as virtual machine. From there everything works just great. Because of that, I still have to have windows on my laptop :-(
Speed
About this method: is it faster, same or slower than usb? (consider an average SD card, no high-speed)
Sure SD is faster
g77 said:
About this method: is it faster, same or slower than usb? (consider an average SD card, no high-speed)
Click to expand...
Click to collapse
I flashed recently FinixNOver 3.0.2 (BTW - superb ROM) - only OS + splashscreens and it took 2.5 mins in SD (regular 2GB miniSD SANDISK). I think it is fast enough...
Hi!
I want to tell me,if anybody knows, if i make my device superCID i loose the waranty!
I try to flash it with Trinity_SDCard Flashing from wiki (i make 3 step) and after the reset when is in the grey screen and loading i saw in the up side of screen the number 00068002 and after that change to 3 colored screen!
Any help?
jukkus said:
I tried this method several times, but I was never able to get it work.
Yes I followed instructions carefully, but no. I only get three colored bootloader screen, that's it. No button to start flashing, nor screen that looks like that photo in wiki.
I really wanted this to work, cause I have an OsX. Since I couldn't get it to work I had to install xp and use it as virtual machine. From there everything works just great. Because of that, I still have to have windows on my laptop :-(
Click to expand...
Click to collapse
me second, i also have tried many times and still just can go to the tri-color screen.
i am using hardspl 1.20, and a 4GB sd card with fat32, will these matter?
thanks.
manos_23 said:
Hi!
I want to tell me,if anybody knows, if i make my device superCID i loose the waranty!
I try to flash it with Trinity_SDCard Flashing from wiki (i make 3 step) and after the reset when is in the grey screen and loading i saw in the up side of screen the number 00068002 and after that change to 3 colored screen!
Any help?
Click to expand...
Click to collapse
yes, super-cid will void the warranty.. use hard-spl.. there's no reason to super-cid your device if you're flashing cooked roms..
racerx_ said:
yes, super-cid will void the warranty.. use hard-spl.. there's no reason to super-cid your device if you're flashing cooked roms..
Click to expand...
Click to collapse
Ok, and thank's you very much!
ctrlaltdel said:
me second, i also have tried many times and still just can go to the tri-color screen.
i am using hardspl 1.20, and a 4GB sd card with fat32, will these matter?
thanks.
Click to expand...
Click to collapse
Interesting, I'm sure someone will shoot me down but I'm not convinced it works with all SDHC cards... is your 4GB SDHC?
I can't get it to recognise the NBH from my 8GB but I have flashed many times successfully from my 2GB. Not to bothered, as long as it works
Nope, I'm using 2Gb normal sd-card. Also tried 512Mb card.

Unbrick Trinity From SD

Need a favours over here. Recently, i bricked my trinity. P3600 more precisely Dopod D810 (i flashed wrong ROM -> Unpacking cooked rom for trinity but i merge it with -Hermes cmd in NBMerge! houh... so stupid! ). Soo... just not what i expected, Rom flashing stop on half, SR my trin and tada.... 3Color screen bootloader popup! haaarggg, i try flashing another rom using any rom that has same CID *official or cooked rom* (some are 100% thru, but someother not) but like usual it won't start the windows (just blank/black screen with green led[ always on!) Never been like this before! Have been flashing several times using any cooked rom by great chef on trinity but this time! :doh: damn it! my bad.
i found solution on the forum *Unbricking Trinity Stuck on Bootloader* but since my usb port can't be detected on my vista/xp machine, whether i disable AS and changed my usb cable it doesnt work at all, on mtty too! so i can't use that utility. i try run install sspl olipro 1.3 but it never changed my spl at all. now i can't use my trin at all cuz allready dead.
btw this is the info on trin 3color screen bootloader:
IPL 1.00
SPL 3.20 OLIPRO
anysolution for bringing back my trinity from the death? maybe a tools/utility to unbrick trinity from SD or something like that, which not involved any pc connection, without bring this devices to htc center of course.
I hope any expertise on this forum would helped me sort out this probs.
Sorry for my english and thanks for reading my post.
Read this :http://forum.xda-developers.com/showthread.php?t=308691 download splxploit-windows.zip (935.1 KB, 7619 views) put phone in bootloader run splxploit when bootloader change
After this download full rom here is link:http://rapidshare.com/files/21174752/RUU_Trinity_HTC_WWE_1.15.405.5_6275_1.20.00.11_12201_Ship.exe
Then flash full rom bat do not disconnect usb cable in any step.
Before use any step disable active sync.
Usb are dead
Gsmhacks thanks for ure reply. I have tried that one, and lot read ing on wiki. But since i cant use the usb i cant use that splexploit whether on live linuxcd, or .Net version even win version. The usb port cant be opened . I think i broke the usb pin. From the beginning everytime i flashed my trin i never used ruu utility, i always do the sd card method and that is the best and easiest method and it works for me.
I just curious perhaps can anyone or is there any utility to unbrick trin via sd card. I knew a lot a people has bring their trinity life from dead by using htc stackflow splexploit. I hope that was work for me too! Too bad my usb are dead. Damn!
Here what you need bat only work if you have hard spl
If you install hard spl before brick trinity you can use SD CARD to flash trinity. YOu need to formate sd card to FAT32 with Card Reader donwload full rom here is link: http://rapidshare.com/files/21174752/RUU_Trinity_HTC_WWE_1.15.405.5_6275_1.20.00.11_12201_Ship.exe
then extract and file RUU_Signed.nbh rename to TRINIMG.nbh and copy it to the root folder of your miniSD card.
Here is full instruction again also first format sd card to FAT32 !!!! VERY IMORTANT to format sd card to FAT32 or all other step will not work THEN:
1. Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (or you can also use winrar via wine).
2. Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
3. With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
4. You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
5. Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
6. When flashing completes soft-reset your device.
and you will flash and unbrick trinity bat this only work if you install before this hard spl i mean cid unlock trinity. if not you must fix usb port.
That will work? I hope so
Ok then i'll try flashing using that rom. Oo, i have install hardspl btw and so far flashing using sdcard method no probs. But after i bricked my trin flashing doesnt smooth like be4. Always gave me error 0018003 update fail on the halfway, i guess because i have bad nand on trin and probably cuz cooked rom.
Can u give me another link, perhaps on xda ftp. rapids so slow 4 me. Btw i have download dopodasiawwe official rom on xda ftp *twice but still when i tried to run the package it gave me corrupt archive integrity fail w!f.
Thanks gsmhackerns, i downloading the package now!
Perhaps you can find a way to make a goldcard for Trinity?
See http://forum.xda-developers.com/showthread.php?t=437996
That's what i looking for! Thanks.
Humm, superb. Yay, great! Thank you stepw. Even its for elf with a little mod i hope this will work. Once again thank you.
Stepw, i have tried making the gold card, everything went ok. I have temp. cid *supercid* but the probs now is i can't download http://rapidshare.com/files/21174752/RUU_Trinity_HTC_WWE_1.15.405.5_6275_1.20.00.11_12201_Ship.execan someone uploaded to somewhere else. Rapidshare crap! perhaps on xda ftp.
thanks!
goldcard cannot help in such a situation.
I can however make an SSPL that loads off SD card - just like for kaiser you will be able to use it because you are already on hardspl.
then that will allow you to flash stock SPL.
PM me and send your MSN address, so we can test it out. if it works i'll post it in this thread too in case others get stuck also
cmonex said:
goldcard cannot help in such a situation.
I can however make an SSPL that loads off SD card - just like for kaiser you will be able to use it because you are already on hardspl.
then that will allow you to flash stock SPL.
PM me and send your MSN address, so we can test it out. if it works i'll post it in this thread too in case others get stuck also
Click to expand...
Click to collapse
Indeed. Youre right cmonex, it doesnt make any difference at all 4 my trin. After several tried using and making goldcard 4 trin, finally i made working goldcard4trin, but gosh it still stuck when i tried to update the os (update os fail) humm anyone.
Sorry for wasting your time with Goldcard, I have overlooked that you have a hard spl on your Trinity. In this case goldcard doesn't make a lot of difference.
And there's no trindiag.nb to the best of my knowledge that could be used instead of SSPL cmonex is suggesting to run from SD.
Back to the topic, sounds like you have some "bad" blocks in flash and OS can't be flashed. Bad blocks can be reset with "task 2a" command, see this thread for more details:
http://forum.xda-developers.com/showthread.php?t=330496
The question is how to run it without USB and I don't have an answer for you
Some people have previously mentioned they managed to flash smaller OS images when larger images failed, perhaps if you try flashing some minimal vanilla ROM, it will succeed?
Bad NAND, Yup!
Ya... as i mention before yup i do have bad nand block on my devices. Using manila rom with smaller img size the flash went 'OK'. But it doesn't boot at all infact just black screen with green led on.
Okay the only solution probably use mtty and do task 2a if i'm not mistaken. But like you said "The problem is the USB port". I think the port is ok cuz i already tested it connecting my usb to my trin without inserting the battery and the red led *magenta* is on. humm, weird!
But if something can make it working without involving any pc connection it would be a great achievement. hahah! well i supposed i have to put my trin on bunker before someone can make it happens
I asked SEA in my country and they recommend me to changed the machine it self and they charge me around US $160 ho...ho.. too "wideeeeee" for college boy like me
Same problem, i flashed the rom
RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship
and after that i tried to flash a new radio!
power+cam and the cell phone did not show usb, then i used sspl to rum the radio but it locked at 0%
after that it is stucked at bootloader screen
ipl 1.0
spl 3.20 .....
but no usb and no sd card !!
did i lost the cell phone?
there is no jtag ou something like that ?
so now... you still want this SSPL? i'm thinking of patching one up to automatically run task 2a maybe. or just restore stock spl for warranty service if that's what you have in mind. but you didn't really reply to that offer?
Please if you could build a sspl for this condition it would be enough because once sspl i can run a new ruu with hard-spl again ! the problem i believe was caused becaus this original rom's have a spl.nb inside , in the screen we read teh information about the olipro spl but i thing teh original spl.nb messed up the hard spl!
There is another problem, i formated to fat32 my card and put a TRINIMG.nbh of a rom inside and he did nothing!! same card in elf with ELFIMG.nbh of a rom runs great!!
It means that this spl of mine will not flash from card? goldcar would help?
and cant i flash something in serial ? like a jtag or something?
Anyhelp will be more than apreciated!
sorry the bad english
Needed!
Cmonex, sorry for longtime haven't seeing this thread again. okay i really need your help btw if you willing to help me. The spl your talking about perhaps can sort out the probs (i hope) at least we tried. as for task2a cmd to clear the bad nand block is none usefull for me since usb conn. are definitely drop dead.
how about patch the SSPL to do task2a cmd to solve the bad NAND block first.
dinizbruno said:
Please if you could build a sspl for this condition it would be enough because once sspl i can run a new ruu with hard-spl again ! the problem i believe was caused becaus this original rom's have a spl.nb inside , in the screen we read teh information about the olipro spl but i thing teh original spl.nb messed up the hard spl!
There is another problem, i formated to fat32 my card and put a TRINIMG.nbh of a rom inside and he did nothing!! same card in elf with ELFIMG.nbh of a rom runs great!!
It means that this spl of mine will not flash from card? goldcar would help?
and cant i flash something in serial ? like a jtag or something?
Anyhelp will be more than apreciated!
sorry the bad english
Click to expand...
Click to collapse
no usb, no sd, no chance sorry. jtag it or get it serviced or get another phone.
as for jtag, hermes jtag has been worked out by scholbert. trinity is probably the same, but you will have to find the pins. the rest of the process will be the same.
Dear all,
I can't go to bootloader screen ..fff before I had on my trinity faman 4.03 rom and I would change with the NiAX rom... after 3% restart and I think that my phone brick and my phone stay on htc screen fff please help
I have windows vista and even if i follow all steps pfff it changes nothing...after hard reset ...fff please help ...
I think my trinity is out :-(????????????????????????
Please help,
The O.S is more important to these operations than can be stressed - for a 99% safe flash Win XP is your best bet , I have had nothing but error 260,270 halfway flashed roms and usb faults running on vista and since I had my original bricking episode - NOTHING , I repeat NOTHING including genuine roms has flashed without a recovery or at least without doing something strange in the process - SPLXPLOIT has been a saviour here , without it I would've been lost.
Cant the O.P simply use another machine to test out the USB theory ?
ALIVE AGAINnnnnnnnnnnnn!!!!!!!!
My p3600 was stucked att bootloader, and wont give "usb" and do not read TINIMG.NBH (tried on elf with ELFIMG.nbh and the card was great)!
I did a golcard with the post on elf about it and the cell with the gold card inside was the same, no trinimg.nbh and no usb.............
BUT..............
with the goldcard inside, turned OFF, i placed it on the usb cable off the pc and the device booted to the bootloader screen, but this time he got "USB" , before flashing anything i removed the card , and putted switched off in the usb, booted with "serial" with card and pressing power and then placing usb still "serial" message!
I putted the card, did not switched on , placed on the usb and waited for it to boot for it self , and for my surprise "usb".
Flashed stock rom, and it booted nice!!!
Please try!
saved my day!
sidekraouf95 said:
Dear all,
I can't go to bootloader screen ..fff before I had on my trinity faman 4.03 rom and I would change with the NiAX rom... after 3% restart and I think that my phone brick and my phone stay on htc screen fff please help
I have windows vista and even if i follow all steps pfff it changes nothing...after hard reset ...fff please help ...
I think my trinity is out :-(????????????????????????
Please help,
Click to expand...
Click to collapse
I have to know how to repair my phone please... nobody can explain precisely how to put my phone on bootloader using my sd card directly from my computer under vista...???

Why My Screen freezing? Please Help...

Hi all,
I really got angry and I will break my phone...
I tried many Rom's but my screen sometimes freezing(but too much times)? Also softkeys freezing too...
What is the problem?
Please help me...
And any offer for me please, I need a rom very lite. (No manilla or something, just I want Htc Home and stable)???
Thanks...
ccmaniac said:
Hi all,
I really got angry and I will break my phone...
I tried many Rom's but my screen sometimes freezing(but too much times)? Also softkeys freezing too...
What is the problem?
Please help me...
And any offer for me please, I need a rom very lite. (No manilla or something, just I want Htc Home and stable)???
Thanks...
Click to expand...
Click to collapse
You probably have the wrong SPL installed. If you flashed a ROM using Olipof's HardSPL v1 and are using a WM6.1 ROM, you need to upgrade your SPL.
Flash cmonex's latest 3.* Hard SPL's from here: http://forum.xda-developers.com/showthread.php?t=420683
Thanks
Dave
I have installed 3.29
(I have download Kaiser-HardSPL-3.29-force-USB than install with KaiserCustomRUU.exe, isn't it?)
ccmaniac said:
I have installed 3.29
(I have download Kaiser-HardSPL-3.29-force-USB than install with KaiserCustomRUU.exe, isn't it?)
Click to expand...
Click to collapse
Instructions in Post #2 here: http://forum.xda-developers.com/showthread.php?t=396922
There are two sets BTW.
Ta
Dave
Which version do you offer me for WM6.1?
I saw something in cmonex " 3.29 is still very strongly recommended over 3.56, unless you have OS freezing issues with 3.29. "
ccmaniac said:
Which version do you offer me for WM6.1?
I saw something in cmonex " 3.29 is still very strongly recommended over 3.56, unless you have OS freezing issues with 3.29. "
Click to expand...
Click to collapse
If you are using a ROM based on a HTC Rom (which most cooked ones are) then 3.29. For ATT based ROMs then 3.56.
If you don't know, use 3.29, and if your not happy try 3.56
Dave
I think my instalitation is not true, right?
Just get the zip file then run KaiserCustomRUU.exe???
ccmaniac said:
I think my instalitation is not true, right?
Just get the zip file then run KaiserCustomRUU.exe???
Click to expand...
Click to collapse
Read the instructions I posted. I am not copying them out
Dave
3. insert the microSD in the kaiser, then reset kaiser. (I did soft reset???) But not start 4
4. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
5. it should now flash in the KAISIMG.NBH. and will reset.
6. at this point it should boot to the OS, if it doesn't, then flash an OS. (of course delete the previous KAISDIAG.NBH and KAISIMG.NBH from the sd card and remove sd unless you opt to flash the OS from sd too)
I did't do that with http://forum.xda-developers.com/showthread.php?t=420683
But I think I have made it with http://forum.xda-developers.com/showthread.php?t=396922.
Now I will flash Radio and Rom...
Thanks...
Using Dutty's Rom WM6.1 Hybrid v2 5.2.19716/5.2.19700 and works GREAT...
got the same problem, some one say i got a lot of progam runing and the os cant go well, i think i fix it setting X button to really close apps and dont go background
Hi folks!
I had the same problem: change my at&t tilt rom/radio/spl to htc.
result: touch screen does not working!
The only way that i found is undo changes:
1º - installing and using: Remote screen Alignment to skip the first screen calibration. Just power on Tilt and wait until activesync are connected, so, run "remote screen alignment" and click skip, if the phone does not restart, do a soft reset.
2º - In the next power on, use activesync to copy JumpSPL1.56-KAIS.exe to your phone.
3º - use the buttons to navigate and execute JumpSPL1.56-KAIS.exe on the phone. (to execute JumpSPL1.56-KAIS.exe file use the ENTER key of the sliding keyboard).
4º- now just replace RUU_Kaiser_CINGULAR_WWE_.exe (OEM ROM i think)/ bootloader spl1.93.0/1.56 (maybe the screen problem occurs due the wrong spl/rom combination or newer spl like 3.28/3.29 ).
After these steps my AT&T Tilt touch screen is back to work!
Now i'm ready to try others roms again !!
PS: Sorry for poor english, if anybody don't understand anything just ask!

Potentially Broken T.HD - Need help!

Hi All,
I have used the search function - but ended up getting confused.
I have a Touch HD that I bought in January of this year (2009) from Mobiles.co.uk (Carphone Warehouse) and is on the O2 network (UK).
I have been using Dutty's ROMs (both 6.1 and 6.5) for months now - and have always used USPL when flashing, using the SD card method.
Over the past 3 days, my HD has been playing up.
When it started, I was using Dutty's R7. The radio was 1.14.something.something. The device was working perfectly, and I was really happy with the ROM and the way the phone was working. I had installed NO other applications with the exception of a different taskbar and obviously SDKCerts.cab
First of all, HTC Sense stopped working - it would cycle between "Loading HTC Sense" and "Tap here to launch HTC Sense"
Then, when rebooting the device, it just hung on the "Smart Mobility" screen. I left it in case it just needed a while to boot, but nothing.
I had no other option than to hard reset.
It worked OK for a few hours, but then HTC Sense started to crash again. So I flashed a new ROM - Lost in Asia or whatever it is called.
Same symptoms.
I flashed Dutty's R7 back and also the new 1.17 radio.
No joy.
The phone also hangs for ages on the Smart Mobility screen - perhaps a full minute where as before, it used to be no more than 15 seconds or so.
The following is displayed on the "Smart Mobility Screen"
1.17.25.09
52.69.25.37H
1.59.Dutty
The bootloader screen (before running USPL) shows the following:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) V6
So the question I'm asking - is... Is my phone suffering some kind of hardware malfunction, or is this a known and fixable fault that I somehow have caused?
If the phone looks like it is malfunctioning, how would I go about returning it to stock so that the CPWH repair centre do not know it's had an unofficial ROM installed?
I'd like to add that whilst I'm very PC literate, I'm no programmer and a lot of the stuff here is alien to me hence my confusion - I just know how to flash a new ROM etc.
Thanks to anyone that takes the time to help me - I'd be really thankful to anyone that helps me sort this - be it tell me how to fix the device, or tells me to take it back!
Thanks in advance & Regards,
Chris.
Will D/L and flash Dutty's R0 Holy Grail ROM and see if that makes a difference...
If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.
a1gp said:
If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.
Click to expand...
Click to collapse
Thanks for the quick reply.
So is it perhaps better to revert to the original ROM before flashing a cooked ROM? I always Hard Reset twice after flashing as understand this helps.
OK - so the 1.56+ situation - I was under the impression that using the latest USPL (2.5) when flashing was OK? I have never had the colour problem... but perhaps if I'm flashing wrong then these problems could be to do with this?
Thanks again...
Chris
The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.
Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.
mcdull said:
The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.
Click to expand...
Click to collapse
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?
a1gp said:
Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.
Click to expand...
Click to collapse
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris
constablechris said:
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?
Click to expand...
Click to collapse
what do you mean hang for age?
1 minute is nothing if it turns out boot up.
There are chances that the nand flash needs to refresh and wasted some times. But it won't be forever.
constablechris said:
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris
Click to expand...
Click to collapse
there's an original rom on htc.com for blackstone just use that one.
hope it will turn out right for you
I thought I'm the only one who had this problem. Last Sunday my blackstone started to freeze on the smart mobility screen too. I flash 3 different roms because I thought its an rom issue with no luck. On Monday it even managed to hardreset itself after I waited for about 15 min in the smart mobility screen.
After that I flashed a stock rom and it seem to be fine by now.
But now I will flash a custom again, the stock one is so 6.1

[SOD] Any Solutions? Task29 for Topaz Included

There's a lot of beautiful ROMS for our device but most of the new ones face one problem SOD (Sleep of Death) when the device goes to sleep you can't wake it up.
What "causes" SOD?:
* Bad Flashes
* Residual code for flashing you device a lot
* Newer SYS cooked in ROM
I've been searching for a solution and this is what I've found.
qbus00 said:
That's something which I have to do...
I'll downgrade SYS to 21896 soon which does not face SOD problem.
Click to expand...
Click to collapse
wuub said:
MTTY is a software that allows you to format internal storage before you flash a new rom.
By doing this you will make sure that no residual files or past informations are kept in the system. This usually fixes random crashes and weird behaviours on PDAs.
This is the DIAM100 thread but i've been using on D2 without trouble : http://forum.xda-developers.com/showthread.php?t=540290
Click to expand...
Click to collapse
From HD2 ROM Thread
rjd1 said:
I started having issues similar to this and a few other non-normal issues with NRG ROM. I ended up loading carrier ROM again, re-flashing 2.08 radio and then 23544 COokie ROM and all cleared up. It appears alot of risidual code happens with the HD2 ROMS regardless of AS or SD card ROM loading. I added to my flashing every 2 weeks or so - I am a flashaholic...
Click to expand...
Click to collapse
doloop said:
Hi,
(To make it short, follow the red sentence to format your phone to avoid roms problem.)
I hex-edited RomUpdateUtility.exe so it runs task 29 right after flashing ruu_signed.nbh
Task 29 formats your phone memory (=binfs). It prevents weird error appearance when you flash new Roms.
you stile need something to flash, it may be a radio, a splashscreen nbh or a blank nbh file (shadrack repack provide a tiny blank nbh).
Usually you don't need anything more than the file provided in the packs. so:
Just unzip and run task29.exe .
Eventually, you may replace ruu_signed.nbh with the radio/splashscreen of your choice.
When update status reach 99%, press vol down button, and keep it pressed until the phone reboot to the three color bootloader.
After the phone reset itself, your old rom will be gone, so it can't boot to winmo: binfs has been formated, your phone memory is clean.
if you fail to press vol down key and your phone get stuck on the white screen, just remove your battery, then try again: press power, and keep vol down pressed immediatly next, until the phone get to RVB bootloader.
When your phone is back to RVB bootloader screen, use the leocustomruu.exe provided with your favorite rom package to flash a new rom, or flash it from memory card using standard procedure.
Repack by ShaDrac (Recommended):
http://forum.xda-developers.com/showpost.php?p=5848003&postcount=19
No radio needed, smaller, faster.
Video tutorial by [★]
http://forum.xda-developers.com/showthread.php?t=621930 (Video 9: How To Perform A Task 29 Without MTTY)
direct link: http://www.youtube.com/watch?v=DtTDuc4V4cU
To do:
remove the "reset" command from task29.exe, to stay into boot loader screen. Then, one should flash the new rom immediatly using their cook's flash utility.
Original files
http://www.megaupload.com/?d=J3OELQ8I
RS mirror, by Sardelisp
http://www.rapidshare.com/files/361617741/Radio_2.08.50.05___task29.zip
Edit, distribute, repack, comment and spread these files as much as you want.
Click to expand...
Click to collapse
I've tried some of these suggestions, but none work. I tried Task29 flashing a boot screen and everything was erased. I flashed a new ROM and guess what? SOD even with task29
If you want to try any of these procedures do it "At your own risk" task29 for Topaz will flash a custom boot screen and erase your WinMo.
Use it at your own risk
And you, got any solutions that want to share?
PS. I'm sorry for my english, remember I'm El Toro not "The Bull"
I have an ATT Pure and have flashed every ROM on here that is in English and not once has one failed to boot or contiunue running till I get tired of it. You do have to use HARDSPL with all of them. My only ROM issue are the ROMS that have everything in the Start menu instead of separate folders. It seems so disorganized but that is a different topic.
I just wanted to point out it must be your phone or you have not used hardSPL or maybe your phone vendor bugged it so you can't flash a new ROM.
Oh I also noticed you say it's and ATT thats unlocked. That could be the issue. Mine is not unlocked. BTW being unlocked would mean it is not an ATT unit any more right?
Solarenemy68 said:
I have an ATT Pure and have flashed every ROM on here that is in English and not once has one failed to boot or contiunue running till I get tired of it. You do have to use HARDSPL with all of them. My only ROM issue are the ROMS that have everything in the Start menu instead of separate folders. It seems so disorganized but that is a different topic.
I just wanted to point out it must be your phone or you have not used hardSPL or maybe your phone vendor bugged it so you can't flash a new ROM.
Oh I also noticed you say it's and ATT thats unlocked. That could be the issue. Mine is not unlocked. BTW being unlocked would mean it is not an ATT unit any more right?
Click to expand...
Click to collapse
Thanks for replying, my pure is Hardspl'd with the latest 2.51 Olinex. It's unlocked meaning Sim Unlocked that I could use it with any Operator that uses a Sim Card, and yes I could flash every single ROM that it's posted in this Topaz ROM Development thread. I've been using Dutty WWE Official Test ROM since he posted it and no problems have come up at all. The "new ROMS" are the ones that caused the SOD even our chefs have suffered from this bug. So it's not the device.
I never had the SOD happen to me. And i have htc pure too.
Apparently, the great majority of us do not have this problem, and have never heard of it. As long as MTTY is run, I've never heard of anyone having a sleep of death issue.
eltoro said:
There's a lot of beautiful ROMS for our device but most of the new ones face one problem SOD (Standby of Death) when the device goes to sleep you can't wake it up.
What "causes" SOD?:
* Bad Flashes
* Residual code for flashing you device a lot
* Newer SYS cooked in ROM
I've been searching for a solution and this is what I've found.
From HD2 ROM Thread
I've tried some of these suggestions, but none work. I tried Task29 flashing a boot screen and everything was erase. I flashed a new ROM and guess what? SOD even with task29
Qbus13 Com2 ROM with SYS downgraded doesn't face SOD.
If you want to try any of these procedures do it "At your own risk" Keep in mind that HD2 task29 files are intended for that specific device not for the Topaz I put them here just for reference, If you want to try the task29 for Topaz I could post it here, It will flash a custom boot screen and erase your WinMo.
And you, got any solutions that want to share?
PS. I'm sorry for my english, remember I'm El Toro not "The Bull"
Click to expand...
Click to collapse
Standby?
I've ran a few Rom's here from energy 6.5.5 to Dutty R6 - R10
with the latest 6.5.x builds, every once in a while after coming back from standby the device will be unresponsive. The touch screen seems to not do anything, but the hardware keys work fine, typically placing it back to sleep and waking it up again seemed to fix it... I have had to pull the battery once.
This didn't happen on the 6.5 builds, only 6.5.5.
Mostly running Energy Aprl and May releases.
I had SOD. I've solved it by changing my SIM card since previous one was more than 10 years old. With new one I never had this problem.
I'm using NhatHoa TopazRom 23563 WWE so far no SOD after 2 days of using it.
I flashed the Dutty's Topaz Sense 2.5 Holy Grail R10 |WWE| rom last night and get my phone goes into the SOD pretty much every time I leave it alone for more than 10 minutes. I have an HTC Pure as well. From the searches I've done it seems solving this problem is pretty much a turkey shoot. I just wish there was a concrete solution, as I kind of like being able to use my phone.
reptiletim said:
I flashed the Dutty's Topaz Sense 2.5 Holy Grail R10 |WWE| rom last night and get my phone goes into the SOD pretty much every time I leave it alone for more than 10 minutes. I have an HTC Pure as well. From the searches I've done it seems solving this problem is pretty much a turkey shoot. I just wish there was a concrete solution, as I kind of like being able to use my phone.
Click to expand...
Click to collapse
The same thing happened to me with that ROM but if you flash Dutty's Topaz Holy Grail R11 WWE it's fine no SOD
On the Touch Pro 2, Tilt 2 section they have a lot of theories about what causes SOD http://forum.xda-developers.com/showthread.php?t=648134
but still no solutions.......
They said that Task29 is the solution but is not I'm posting the Task29 files if you want to try it yourself
INSTRUCTIONS:
Originally Posted by SacTilt
Some of you are making this too difficult. I've posted this before, as this is all that needs to be done. Task29 does not remove your radio or your splash screen. It only clears the ROM, therefore, all you need to do is run Task29 and then flash your ROM. This is how I do it from the PC.
Connect to PC via Active Sync/WMDC.
Execute Task 29.
When phone boots to "Touch Pro 2" screen (or whatever your splash screen happens to be), I hold down the volume down button while hitting the reset button.
Once I'm on the Bootloader screen, and it shows "USB", I flash the new ROM from the PC as I normally would.
When the phone vibrates, indicating the ROM upgrade is complete, I disconnect the phone from the computer.
Click to expand...
Click to collapse
Of course in this case will be your Topaz, Pure, Touch Diamond 2 boot screen
CREDIT:
all credit goes to doloop
Originally Posted by doloop
Hi,
I hex edited RomUpdateUtility.exe so it runs task 29 right after flashing ruu_signed.nbh
As every one understand this command format the rom,
Just unzip and run task29.exe . You may replace ruu_signed.nbh with the radio of your choice.
After the phone reset itself, your old rom will be gone, so it won't boot: binfs has been formated, your phone memory is clean.
You'll need to power up in bootloader mode (press vol down right after power key), then use the leocustomruu.exe provided with your favorite rom package, or flash it from memory card using standard procedure.
Click to expand...
Click to collapse
This files are for Topaz only it will replace your Boot screen or if you want to replace it with another boot screen or radio is up to you. I like the boot screen because the process is faster. **Use it at your own risk**

Categories

Resources