Related
ok i had explodes rom on my xda2s and it froze, nothing could be done to make it work. so i reverted back to the 2003 software all was fine ,a week later i thaught i give helmi rom ago the vanilla rom, installed ok same problem boots up into the windows mode an the device locks up any ideas?
You might be running out of space. Are you installing a lot of applications, maybe even perhaps to the RAMDISK?
it was a fresh install no apps. except what was in the rom update unless i need to format the hidden roms first mabe theres to much on them i never altered the size unless xplodes rom does it for you.
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.
Hey guys.
I have a mysterious issue with my HD.
After flashing Dutty's WM 6.5 R8 Turbo ROM the problems appeared.
The freshly flashed and installed ROM works with all programs and changes for approximately 1 week. After this period (without reboot!) suddenly all contacts are gone, all pictures are gone from the album and the SD card is inacessible (like this thread: Thread), today there was just a bug that a notification was repeated 95 times instead of the supposed 1 time, once it just froze.
When you try a reboot, the booting will take a lot of time just to show the WinMo start screen. At this point the boot process gets stuck and you have to hard reset to get back access to your device.
In today's case with the small bug it endep up worse: Instead of trying to boot the system automatically did a hard reset! Fortunately there were no important data on my phone.
First I assumed that this was caused by the SD-TuneUp driver by tyynt. But after hard reseting under Dutty 6.5 R8 T for the third time I didn't install this driver and guess what: 1 week later it froze anyway and made a hard reset necessary.
After this ROM I tried Dutty's 6.5 R12 Revised with the same result. As mentioned, the device performed an automatic hard-reset today. Now I'm back on WM 6.1 HD V4.1 Final to if this is ROM dependent or not.
Do you guys have any idea what's causing this? It's pretty annoying to reconfigure your HD every week
namelessrabbit said:
Hey guys.
I have a mysterious issue with my HD.
After flashing Dutty's WM 6.5 R8 Turbo ROM the problems appeared.
The freshly flashed and installed ROM works with all programs and changes for approximately 1 week. After this period (without reboot!) suddenly all contacts are gone, all pictures are gone from the album and the SD card is inacessible (like this thread: Thread), today there was just a bug that a notification was repeated 95 times instead of the supposed 1 time, once it just froze.
When you try a reboot, the booting will take a lot of time just to show the WinMo start screen. At this point the boot process gets stuck and you have to hard reset to get back access to your device.
In today's case with the small bug it endep up worse: Instead of trying to boot the system automatically did a hard reset! Fortunately there were no important data on my phone.
First I assumed that this was caused by the SD-TuneUp driver by tyynt. But after hard reseting under Dutty 6.5 R8 T for the third time I didn't install this driver and guess what: 1 week later it froze anyway and made a hard reset necessary.
After this ROM I tried Dutty's 6.5 R12 Revised with the same result. As mentioned, the device performed an automatic hard-reset today. Now I'm back on WM 6.1 HD V4.1 Final to if this is ROM dependent or not.
Do you guys have any idea what's causing this? It's pretty annoying to reconfigure your HD every week
Click to expand...
Click to collapse
it might be due to a bad flash.
try flashing the same rom again or flash another rom..
see if the prob still contiues..
most probably it wll not..
I have thesame problem with duty's latest roms (R9,R12)
After a few days it gets very slow. So slow i have to do a soft reset. But then the device loads very slow, it dont shows the htc animation. After a few minutes (1 or 2) it gets stuck at the orange windows mobile 6.5 loading screen.
Somethimes it does automatically a hard reset after the soft reset. All messages, appointments, contacts are gone. Only time and date are restored. Sometimes it does absolutely nothing, it just freezes at the orange screen, even after a few soft resets. In this case I have to do a hard reset. With dutty R9 mostly the freezes occured, sometimes automatically a hard reset. With dutty R12 most of the time (3 times so far) It does automatically a hard reset.
So I have to restore everything 1 or 2 times a week with pim backup. Does someone have an possible explanation?
leeuwtjevanjuda said:
I have thesame problem with duty's latest roms (R9,R12)
After a few days it gets very slow. So slow i have to do a soft reset. But then the device loads very slow, it dont shows the htc animation. After a few minutes (1 or 2) it gets stuck at the orange windows mobile 6.5 loading screen.
Somethimes it does automatically a hard reset after the soft reset. All messages, appointments, contacts are gone. Only time and date are restored. Sometimes it does absolutely nothing, it just freezes at the orange screen, even after a few soft resets. In this case I have to do a hard reset. With dutty R9 mostly the freezes occured, sometimes automatically a hard reset. With dutty R12 most of the time (3 times so far) It does automatically a hard reset.
So I have to restore everything 1 or 2 times a week with pim backup. Does someone have an possible explanation?
Click to expand...
Click to collapse
I had the same Problem after flashing from Dutty's WM6.5 R5 to R6. I tried Flashing back to R5 but the same thing happened.
I resolved it by up flashing the HTC stock ROM, and then R6 again. Now on R12 and haven't seen the problem since. No idea what it could be though.
I've had the same problem. Flash a stock rom like ManiGo says and than you can flash one of Dutty's rom. Worked for me. Good Luck.
The problem doesn't appear to be directly related to the rom as countless others have used Throys roms with no such issues. As Svenvdmeer stated above, the general solution which appears to have worked for all would be to restore stcok rom and then follow guidelines to flash Throys rom again.
Alright, I'm going to try that and one week later we will see if it worked for me, too
Thank you for your help!
Edit: Is there a certain stock rom you would recommend? Otherwise I would just flash one of those provided by Dutty.
Edit²: Could be an indication for a bad flash that all WM6.5 ROMs I tried were noticeably slower and not that smooth in (e.g.) TF3D in comparison to 6.1 ROMs?
Its weird, today i had the problem with dutty's R2 (great rom )
I will try soon to flash a stock rom.
Had the same problems with the first 6.5 roms. Thought that the problem was a CAB I installed (SMS extension from Dutty). Flashed back to 6.1 (not a stock, but a Dutty ROM) and after a while I tried out a other 6.5 ROM and didn't had the problem since then. Still didn't know if it was the CAB or just a 'random' other problem.
This time the WM6.1 is still the most popular choice
try NOT to sync your contact with any of the server after initalizing your machine. (You may restore contact and disconnect all sync service)
Test it for a week and see if it goes right.
I only use PIM Backup, I never updated with a server with Winmob 6.5. Only with 6.1 I updated to my gmail and hotmail server, but that 1.5 months ago.
Similar problem for me with me.
Dutty's WM 6.5 R9 Turbo
Radio 1.14.
It freezes at least 5 -6 times a day.....driving me nuts! It's a shame cause I like the start menu so much more than on Dutty's 6.1 ROM.
I'm flashing Energy's ROM as I type this. Hope it's as good as other peeps say.
I'm sorry for probably being dumb but where do I find a WinMo 6.5 stock ROM?
Searched this forum and got everything about ROM's but one single stock ROM.
The official ROM's by Dutty seem to be based on 6.1 as well.
namelessrabbit said:
I'm sorry for probably being dumb but where do I find a WinMo 6.5 stock ROM?
Searched this forum and got everything about ROM's but one single stock ROM.
The official ROM's by Dutty seem to be based on 6.1 as well.
Click to expand...
Click to collapse
There is no sutch thing as a stock ROM for touch HD.
samlives said:
Similar problem for me with me.
Dutty's WM 6.5 R9 Turbo
Radio 1.14.
It freezes at least 5 -6 times a day.....driving me nuts! It's a shame cause I like the start menu so much more than on Dutty's 6.1 ROM.
I'm flashing Energy's ROM as I type this. Hope it's as good as other peeps say.
Click to expand...
Click to collapse
You can also try his R12. I never had this issue using his ROM´s.
barbapappa_86 said:
There is no sutch thing as a stock ROM for touch HD.
Click to expand...
Click to collapse
So then the already given advices were in vain? Or did I get something wrong about the meaning of a stock rom?
I guess the best solution would be that people who already solved this problem will post which ROM's they exactly used for stock-reflashing.
Thank you
namelessrabbit said:
I'm sorry for probably being dumb but where do I find a WinMo 6.5 stock ROM?
Searched this forum and got everything about ROM's but one single stock ROM.
The official ROM's by Dutty seem to be based on 6.1 as well.
Click to expand...
Click to collapse
Here you can find all the stock ROM's:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Ship_exe
None of them are 6.5 ofcourse.
I think im pretty screwed then. My usb-port doesnt work anymore. I already bought a new cable, used different pc's, different roms, settings but it just don't work. I think its a hardware failure. So i flash my Roms with the micro sd card method (copy blacimg.nbh to card).
But to flash a stock rom, i need a stock spl. And as far as I know you must have a working usb connection.
Well it doesn't have to be a stock rom to fix it but i think that's te safest choice. I (accidentaly) fixed it by trying some of Miri's rom (because i had trouble with dutty) after a couple of roms from miri's i tried a dutty rom again and it worked.
So i have been using Custom ROMs for about a year now with no problems. However, recently i flash to the Valkyrie Firestorm 4.4 (i think) leo and when i attempted to restart my fone it would either hang on the sony erricson logo or it would boot up like it does after a flash. As in it would run the customisation and wipe all my contacts and other information, but strangely enough the clock would remain on the correct time.
This has happened with every firestorm i have tried, which are: 4.4 leo, 4.4 manila and the 4.5 leo. I am going to try a different ROM to see if i still get the problem. has anyone had this problem?
I've re-flashed my hard-spl multiple times to no avail.
Yup I've had the same problem with itje's touch it 14 rom. I have no idea why this is happening, it already occured twice with me.
I had the same problem with the valkyrie 4.4 rom, Itje's Toucht-it Leo v10 and Toucht-It Xperience v2, UnOff 6.5. And also with other versions of itje's Touch-it because i remember seeing the HTCpedia.com customization screen a lot
Every time my phone hung and then when i push the reset button it take's a long time and then it is back to first run. or it does nothing and stays at the touch-it start-up screen.
Could it be a hardware failure like something with the backup batery in the phone? when power goes off it doesn't save data and then when you turn it on it thinks it is first run?
I can always tell when it is going to happen if the favourite programs on the programs tab dont work anymore. When I want to start a program from the tab it says "location not found" or something. After that I will likely have a system freeze and after that I have a hard reset, same sympoms as Aerox912.
So maybe it has something to do with the programs tab?
I am having the same issue with Christians 3.201 build.
Also during the installation it will often hang on the install of Opera or Opera Beta.
But I tried re-downloading and reflashing 6 times before I gave up and went back to an older ROM.
Looking forward to the next version so I can try again. I really like the Firestorm but I also really like the Panels.
Now I just need to find out how to install the SPB Mobile Shell 3 as a panel like on Christians and I would probably stay with my SEX1 build.
Using itje's touch it 15 RC2 and it sometimes, for no reason, phone just reboots. It used to happen with version 14 as well. Never used to have that problem before then.
I tried with rotastrains Blaze rom. the latest edition and i am still getting the same issues. I too, can tell when it is going to happen. When the programs can't be run anymore or if the phone freezes and then i need to turn it off, i can almost guarantee that will happen.
Im glad to see im not the only one with the problem, but isn't there anyone with a solution? I've tried everything and i really cant put up with having to wait 15 minutes until my phone is usable everytime it restarts.
Guys, i had this problem with my Diamond recently & i can say that it's more than frustrating.
try this option, I'm not sure if this is the EXACT same process for the Xperia but it did solve my issues. Perhaps scheduling a daily backup of PPCPIMBackup will help keep info up 2 date when the dreaded lockup happens?
hope this helps
flash a stockrom and then the custom rom and the problem should be gone
Why would that help?
I now tried cristians rom, and had the same problem again within one day. I'm now gonna try the MTTY (format) option, see if that helps...
mobilkungen78 said:
flash a stockrom and then the custom rom and the problem should be gone
Click to expand...
Click to collapse
This simple solution seems to work fine for me. Thanks man!
The MTTY solution for formatting the phones ROM area worked just fine for me
Can you point me the mtty formatting method? Please.
I also had this problem once at my x1 and once at my girlfriends diamond. Seems a reflash with a stockrom and after that flash the custom rom again solves this problem.
Atleast it worked for me.
I put on the R3AA014 ROM and am still seeing the problems.
Is there another Stock ROM that would work better?
And I have tried to look up the mtty method and all I find are people talking about it, but not the actual method.
Any help would be appreciated.
Drokare said:
I put on the R3AA014 ROM and am still seeing the problems.
Is there another Stock ROM that would work better?
And I have tried to look up the mtty method and all I find are people talking about it, but not the actual method.
Any help would be appreciated.
Click to expand...
Click to collapse
Maybe it isn't a software problem but a hardware problem. Incase no rom fix it.
toontoonizer said:
The MTTY solution for formatting the phones ROM area worked just fine for me
Click to expand...
Click to collapse
Could you please describe the process.
I tried the The DEFINITIVE MTTY Thread but the task 29 command did nothing... Though i'm not sure what should happen.
For the Xperia, I heard that the command is Task 28 instead of Task 29 for the MTTY process
someguyyy said:
For the Xperia, I heard that the command is Task 28 instead of Task 29 for the MTTY process
Click to expand...
Click to collapse
Hm... i tried that but that did nothing.
happened to me many times..most frequent is my X1 will restart itself every half an hr...very frustrating
SOLUTION:
Format Your SD card (don't be lazy and just delete the old stuff and put new rom file in there).....put a fresh copy of the .nbh file in root.
Hard reset after flash.
Problem should be gone
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**