Database Develop

Registry erased?

Ok, this has happened to me several times and i have never figured out why this has happened.
today i went to school and since we were having a test i turned my tilt off. after the test i turned my phone on. the tilt went through the normal boot (but i didnt see the att animation). then it went to the phone setup/align screen stuff, this is when i relized im screwed. after that i reset (to avoid the reinstall of the att software).
so the over all damage done is, my registry seems to have been competely erased. all my settings are lost, but as far as i can see all my files are there.
has this happened to anyone else, or does anyone have an idea what caused this? the only thing i could remember that is a cause of worry is that my main phone memory was down to about 2.3mb.
if its possible to get registry back please help, but really the only thing i want to know is how to prevent this after i hard reset and start to rebuild
:-(

are you using a fancy rom or a boring one?

ChumleyEX said:
are you using a fancy rom or a boring one?
Click to expand...
Click to collapse
Boring normal ATT rom, i have just seen to many problems with others....

maybe try the new updated one?

saying this probably doesn't help u much, but i had the same thing happen to me too, except i didn't turn it off or anything special. I just rebooted and lost the registry like you did. I don't think its your free memory though, i had over 40mb free when it happened to mine.

Nothing you can do except backup nightly so you can be prepared for next time.
If you're using the AT&T ROMs, Sprite Backup is installed by default.
Hope this helps!

_Alex_ said:
Nothing you can do except backup nightly so you can be prepared for next time.
If you're using the AT&T ROMs, Sprite Backup is installed by default.
Hope this helps!
Click to expand...
Click to collapse
is there a way to have sprite backup, backup directly to the computer when plugged in? so i dont use up all of the memory?

pizzaguy said:
is there a way to have sprite backup, backup directly to the computer when plugged in? so i dont use up all of the memory?
Click to expand...
Click to collapse
Buy a MicroSD Card, they are relatively cheap, you can tell the backup program to only keep a certian number of back-ups (I keep 5). It also comes in handy if you want to try a new Rom.
You can also auto reset the device after the back-up it helps with stability.

Diamond is running extremely slow - TouchFlo won't start

Suddenly my Sprint HTC Touch Diamond is running extremely slow. TouchFlo 3D will not start. Various things runs extremely slowly like tapping on the start menu takes like 20-30 seconds to come up.
Rebooted several times. Turned off TouchFlo. Phone's still as slow as molasses?
What to do? Flash the ROM? If so, which I'd hate to do, where do I get the original Sprint based ROM?
Update: For some reason \Windows\manilla.exe never gets run. If I run it by hand then Touch Flo comes up. But it's still kinda slow.
Who/What starts manilla.exe?

Simply do a hard reset, this will reset everything back to original rom as in a factory reset.
http://www.hardreset.eu/htc_touch_diamond_hard_reset_soft_reset_en.html

That would be wonderful if I didn't customize things. But I have - heavily. And I'll need to reinstall all my apps. I was hoping not to do that...

defaria said:
That would be wonderful if I didn't customize things. But I have - heavily. And I'll need to reinstall all my apps. I was hoping not to do that...
Click to expand...
Click to collapse
But this is the most likely reason it is running slowly... Needs a hard reset and start again - and be judicious with what you re-install.

Before doing a hard reset, have you tried a soft reset??
A soft reset for heavy users is almost required dally in some cases to release the memory from being attached to programs and the OS which is consider to be called "Memory Leaks." A typical problem for all 6.1 Roms.
This slow and sometimes unresponsive behaviour was what also experience as well. There are programs that help memory find it's home but sometimes a good old fashion soft reset is what's needed.
Last thing: Make sure that when you have flashed a new ROM to ALWAYS do a HARD RESET immediately. Not sure if you followed that procedure in your last flash. IF not, I'm afraid a soft reset might not be sufficient to remedy this issue for you.

Riker88 said:
But this is the most likely reason it is running slowly... Needs a hard reset and start again - and be judicious with what you re-install.
Click to expand...
Click to collapse
This is exactly what I was trying to avoid. A computer doesn't suddenly go from running OK to dog slow when you have not changed anything (I only rebooted/soft reset). The running of manilla.exe doesn't suddenly disappear.
Everything I install I install for a reason.

band27 said:
Before doing a hard reset, have you tried a soft reset??
Click to expand...
Click to collapse
Daily! If not hourly. WinMo is not known for being stable.
A soft reset for heavy users is almost required dally in some cases to release the memory from being attached to programs and the OS which is consider to be called "Memory Leaks." A typical problem for all 6.1 Roms.
Click to expand...
Click to collapse
I'm well versed in what memory leaks are. 'Round here we call them bugs. Being in the business for some 30 years now I can tell you that having to reboot an OS periodically is a sign of an extremely buggy OS. Unfortunately that's what WinMo is.
This slow and sometimes unresponsive behaviour was what also experience as well. There are programs that help memory find it's home but sometimes a good old fashion soft reset is what's needed.
Click to expand...
Click to collapse
There's a big difference between being slow and being suddenly SLOOOOOOOOOWWWWW.
Last thing: Make sure that when you have flashed a new ROM to ALWAYS do a HARD RESET immediately. Not sure if you followed that procedure in your last flash. IF not, I'm afraid a soft reset might not be sufficient to remedy this issue for you.
Click to expand...
Click to collapse
I've yet to flash this phone. I was hoping to avoid it. There are so many ROMs to choose from, some better than others. And I'm not looking forward to having to reapply all my customizations...

i get a problem like this occasionally after a restart. I need to hit the green dial key to get it to ask my PIN. after i enter my pin everything is back to normal.
just an idea

sprite backup
What you should do is when you hard-reset the phone and you have installed all your must-have apps (and the phone still runs smoothly) use Sprite Backup to make an image. This way when things go bad again, just restore the Sprite image to that wonderful time when everything still worked smoothly and you won't have to install all the apps again. Only the apps you installed after the image ofcourse... depends how often you backup
Works like a charm.
Be careful though, when you flash another rom, you CAN'T use the Sprite image anymore!! You have to make a new image then.
Hope this helps.

Newbie question

Getting my D2 delivered to me tomorrow.
Reading the threads, I wonder is it fair to say the D2 quality can vary a lot? I see messages suggesting very different performance on Wifi, vibration mode etc which seem to vary among devices. More fascinating is that it seems many mods (ROM, .cab etc) are suggested to improve the devices.
With all these mods mentioned in the threads, how do I tell if my D2 has some/all these fixes when I receive it (i.e. can I tell from the revision of the ROM code?)?
Does the Touch Diamond registry tweaks / .cab apply to D2?
Finally, being a newbie to HTC and getting a new D2, I may not always do the right thing with the mods. As such, does the hard reset always able to bring me back to the factory setting? What if I messed up the IPL/SPL? Will hard reset still able to recover the device from it?

Connor.McLeod said:
With all these mods mentioned in the threads, how do I tell if my D2 has some/all these fixes when I receive it (i.e. can I tell from the revision of the ROM code?)?
Click to expand...
Click to collapse
It depends on the ROM version you will receive in your device,may be recent or may be old if it was held in stores' stocks for a long time. Anyway applying a fix to an existing one doesn't harm.Furthermore official fixes are so few that you can easily verify if you need them.
Does the Touch Diamond registry tweaks / .cab apply to D2?
Click to expand...
Click to collapse
Not always, but most of the time they work, actually the most used tweak programs (AdvancedConfig and HDTweak) are not Topaz specific but so useful.With time more specific .cab and apps will come out..
does the hard reset always able to bring me back to the factory setting? What if I messed up the IPL/SPL? Will hard reset still able to recover the device from it?
Click to expand...
Click to collapse
No, hard reset would bring you to a brand new configuration of the ROM currently installed, to get back to your factory settings you will need to reflash your device with the original ROM and eventually remove hardspl if you need to send it back for assistance under warranty.
Personal note: I've been flashing hundreds of times different htc devices and I must say that it's almost impossible to mess up with hardspl and topaz, fast&reliable. Just do things calmly as explained in related threads.
Cheers

sualc said:
Personal note: I've been flashing hundreds of times different htc devices and I must say that it's almost impossible to mess up with hardspl and topaz, fast&reliable. Just do things calmly as explained in related threads.
Cheers
Click to expand...
Click to collapse
Thanks for your help.
Surely I won't start modifying my D2 until after a few weeks of using it to see if I really experience any issues with it. As with all beginners I better read up on the FAQs and other threads before posting repeated / obvious question here But really, after seeing a thread on IPL/SPL I will want to be 100% sure before I flash the ROM.

Extremely wise attitude, with this I'm sure you will have full fun and no troubles

Received my D2 today from the courier (amazing he turned up on time as promised!!!)
All was smooth with unboxing and installing SIM/MicroSD/Battery and charging the phone. Tried the basic functions and the phone seems good.
Will test it in real world tomorrow

[REF] "LOCKUP" issue on HD

** Please check post #2 first. It looks like we have found a solution. **​
We don't reprimand anyone for asking questions, so feel free to ask (preferably after reading or searching the thread) if you have doubts.​
I'm starting this thread in the hope that we can determine and find a cure for the lockup issue some of us have been dealing with in the later Manila 2.5 version ROMs.
This is something I've been trying to deal with for some time now and it seems more widespread than people realize from the number of posts by users who have had this issue.
Let me explain my definition of "lockup":
1- It always happens when the device is in sleep mode, never while it's used.
2- Never happens with stock ROM or Manila 2.1, only on Manila 2.5.
3- It's random, could happen any time of the day, in any frequency.
4- It's more likely to happen with some ROMs than others, leading me to believe it is related to the ingredients used in the kitchen (that is: operating system/software ) The "lockups" will start within the first 24 hours and possibly become more frequent over time.
5- It's highly unlikely that any sw installation is responsible for this (NeoS2007_Driverpack_3 excluded, I haven't done sufficient testing with it)
6- When the "lockup" occurs, the screen lights up (you can see it does in the dark) but the device is unresponsive. If you wait for a while, the home screen appears but the device is unresponsive. The only way out is taking the battery out or doing a soft reset.
7- Using MTTY or flashing a stock ROM may help fix other problems but does not help for this specific case, the "lockup" will still occur.
8- It's entirely possible (but hard to determine) that hardware may be an issue here. The fact that some people always have this problem and others don't, may be due to different hardware revisions, if there are any.
9- This problem is very specific and never leads to a hard reset.
10- When the lockup has occurred, people calling may hear the phone ringing but the HD remains unresponsive and there is no call logged, so at least the radio section is working.
Please post you experience with this issue, including the ROM involved, and any action you have taken that leads to a solution.
Please also mention whether you flash using SD card or from the PC. Since none of my SD cards work, I always have to flash using my PC, so that is something I need more info on.

Please read this post to be uptodate on the latest situation with this issue
Quite a number of new sys versions seem to be causing lockups on most HDs. This is a sys problem and is not related to the lockup with the video drivers but is related to the OS version. If you are using a ROM with a new sys version and are having lockups, just switch to another ROM with a different sys version.​
As the number of pages in the thread started to increase, I want to post a summary of our findings here.
As stated numerous times, not everyone suffers from this problem but the number of people who do suffer seems to be much more than I originally thought.
Please remember that we are talking about a very specific kind of lockup here as explained in post #1.
So far, our findings indicate that it is a combination of conditions that cause this issue. If Manila 2.5 and the Neo's Driver pack are used together, this lockup will occur on those HDs that are prone to this issue.
mnet has prepared a cab that effectively deletes the driver pack and restores stock drivers. If you are having this problem on a Manila 2.5 ROM, you should try this. Needless to say, before trying this, you should have already tried the recommended cures, like flashing a stock ROM or using MTTY.
You can't actually delete the files cooked in the ROM, only replace them...Some dlls from Neos drivers remain in the windows folder, however they are no longer used due to registry modifications.
Several users who have been suffering from this lockup have confirmed that after applying mnet's cab to uninstall the Neo's Driver Pack, the lockups have stopped. So, it's a definite cure.
Cab to remove Neo's Driver Pack.
Also, please check this post. It may be worth giving it a try if you have unexplained lockups.
The Topaz D3DM drivers also seem to be causing lockups, confirmed by other users.
Mikenificent BlackStone TestDrivers seem to be safe. I tested for a few days and no lockups occurred.

sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.

homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?

Fallen Spartan said:
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.

I only had this with Dutty and Miri's 21xxx series with Manila 2.5.
Once I went to 28xxx series, from PDAViet, Energy etc, this hasn't happend again.
So I'm guessing its WM6.5 21xxx and 23xxx related rather then manila.
Also, it happens far less when you use a lightweight (short and low bitrate) sound for notification.
It seemed to happen for me whenever the "new mail" or "new sms" notification was supposed to sound.
When putting a very short sound, it stopped freezing. When putting back a long sound, it would freeze up more often.

bobsbbq said:
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.
Click to expand...
Click to collapse
A number of people have stated that they get issues with cooked roms (while others don't) if they are constant flashers, and the common solution would be to flash a shipped rom and then back to cooked. As I stated above I've been fortunate enough not to experience this so haven't had the need to flash a shipped rom. But from reading users issues this isn't a clear cut problem as it doesn't affect everyone

homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
I've ruled that out. I always install the same set of applications, same email etc.
Never have this issue on stock ROM or Manila 2.1 ROM, only on later M2.5 ROMs, so it has to be related to M2.5 somehow.
Xannytech has been very helpful, comparing ROMs where I had this issue with a few ROMs where I don't have it, it seems that the problematic ROMs are larger in size. So perhaps there is a problem with the NAND memory and the bigger size ROMs use it whereas the smaller size ROMs do not use it. This is the reason why I mentioned hw revision as a possible cause.

Fallen Spartan said:
Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
It does happen on a bare ROM, no data sync, no SD card, no applications installed. Just flash a new ROM and wait, it will happen.
I guess it would be OK to mention here that currently the only ROMs where I don't have this issue is with Miri's ROMs (which are smaller in size than others).

wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..
u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..
currently using;
GridLeo 1.7 (1.2.5.30),
OS (5.2.21869)
Manila 2.5.19201130.0,
Radio (1.14.25.24)

termignoni said:
wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..
u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..
Click to expand...
Click to collapse
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.
For your case, I suggest you flash a stock ROM and test with it for a while.

makbil said:
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.
For your case, I suggest you flash a stock ROM and test with it for a while.
Click to expand...
Click to collapse
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..
this is what is going on with my HD.. until one day, even after soft reset, i could not enter my pin or even access the calibration screen as i could only "tap" the top half of the screen..
after many soft resets, i could only "tap" the top half.. hard reset resolved my problem until a couple of days back, where the problem seems to start again.. this has been going on since last month, and out of the blue..

termignoni said:
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..
Click to expand...
Click to collapse
I never got as far as having to do a hard reset but I guess it is possible after extended use.
I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.

makbil said:
I never got as far as having to do a hard reset but I guess it is possible after extended use.
I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.
Click to expand...
Click to collapse
i suspect it's a ROM issue as well, as i never had this issue with any other ROMs with the old Manila.. i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..

termignoni said:
i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..
Click to expand...
Click to collapse
If you do have this problem on a stock ROM, then definitely it's a different problem. Just remember to flash the stock ROM by running the executable and not through running the BlackstoneRUUWrapper + nbh file manually.

I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
http://forum.xda-developers.com/showthread.php?t=540290

bodgeman said:
I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
Click to expand...
Click to collapse
any reference to this "MTTY thing" u did? i might give a try 1st..

bodgeman said:
I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
Click to expand...
Click to collapse
I also did the MTTY thing but had the lockup within 24 hours on Xanny's Evo 1.6. Keep a close eye on this, if you don't have it within a few days your problem may have been cured
Didi you flash from SD card or from the PC?

termignoni said:
any reference to this "MTTY thing" u did? i might give a try 1st..
Click to expand...
Click to collapse
Here . My results are on page 50.

makbil said:
Here . My results are on page 50.
Click to expand...
Click to collapse
thank you..
btw, this time i flashed using PC instead of the SD card..
one more thing to add, the first time i did my hard reset, i restored my device using PIMBackup (restored everything).. within 24hrs, it happened again..
the 2nd hard reset, i restored only my Contacts and till now (after 3weeks), only it's starting to happen again..
i don't know bout u, but this is how it's happening to me..
- at first, u'll notice a slight mis-calibration while typing an sms or selecting something (after screen calibration, everything went fine)
- then, after a few days, same thing happens (can't tap the bottom part, soft reset and screen calibration solved this)
- and today, after my device woke up on sms, i could not unlock (using the default WM6.5 lock screen - had to soft reset twice, then calibrate screen)

another bricking question

My unbranded TyTnII took a dump today, and reset itself to OEM condition, not so bad, except the data base was corrupt, so I would not configure a connection to my carrier (T-mo) .
So, I took it home, hooked it up to activeSynch, and brought up a previous sprite backup file to restore it.
Now it's a paperweight- it will start, display the three three install lines R-G-D with the Smart mobility splash, and that's it. I can't get it into bootloader, or anything else for that matter. Any ideas?

ttruex said:
My unbranded TyTnII took a dump today, and reset itself to OEM condition, not so bad, except the data base was corrupt, so I would not configure a connection to my carrier (T-mo) .
So, I took it home, hooked it up to activeSynch, and brought up a previous sprite backup file to restore it.
Now it's a paperweight- it will start, display the three three install lines R-G-D with the Smart mobility splash, and that's it. I can't get it into bootloader, or anything else for that matter. Any ideas?
Click to expand...
Click to collapse
If you get to the 3 color screen you are in bootloader my friend, do you notice the USB sign display in the screen? If you get that you can flash. I will recommend that you hard spl your device first (Please read the sitcky of how to perfom it, click under my TyTNII link)

Moved as not ROM Development..
Hard-Reset and do not use your backup as may be corrupted...
If that does not work then try and get into bootloader i know you said you can't but try again and flash stock ROM.

thanks for the move, and my apologies for the mispost- I realized only afterward I had put this up in developers.
I can't get to bootlogger mode- the phone hangs at the initial splash where it displays the SW versions of R D G. It will not move past this.
I hold the camera and on buttons, and push and hold the reset pin, but this is as far as it gets. I will sit here, so far for an hour, but will not progress further.
What am I missing? It's been some time since I've had to muck with it at all, so I've become unfamiliar with the tricks.

It's not bricked as long as you can get meaningful info on the screen. It sounds like you need to revisit HardSPL and put on a newer version. Then flash an appropriate rom.

All right,
Many thanks for the help! I flashed and manged to get the bone stock HTC WM 6.0 ROM loaded.
Now, at the risk of asking what could be considered a dangerous question (almost as bad as starting an oil thread on a moto list) what would be considered the latest and greatest ROM of them all? these days? I haven't been on this forum for quite some time, and I'm sure you all have been busy w/updates. I gave up when WM 6.1 came out, screwed up the GPS settings and made the camera even worse, so I've just stuck with my plain 'ol HTC OEM ROM.
Any suggestions?

ttruex said:
All right,
Many thanks for the help! I flashed and manged to get the bone stock HTC WM 6.0 ROM loaded.
Now, at the risk of asking what could be considered a dangerous question (almost as bad as starting an oil thread on a moto list) what would be considered the latest and greatest ROM of them all? these days? I haven't been on this forum for quite some time, and I'm sure you all have been busy w/updates. I gave up when WM 6.1 came out, screwed up the GPS settings and made the camera even worse, so I've just stuck with my plain 'ol HTC OEM ROM.
Any suggestions?
Click to expand...
Click to collapse
Yes, try them all and pick which one can meet your daily needs

having tried quite a few 'light and fast' types, i would say stick to more or less standard 6.1.
i spent a lot of time looking for cabs and then adding back in all the removed stuff i needed.
then get spb mobile shell on there and have a good looking phone.
6.5 never worked properly, esp messages, but a few other obscure probs.
my 2c