Hi
After a hard reset, I've lose my G-sensor. Even the icon to 'Use' or 'Don't use' G-sensor is not there.
Using Omnia ll with WM6.5 original rom.
Grateful if anyone can held and advise how to recover G-sensor.
Thank you very much.
Regards
woodrow
Hi,
i would try another hard reset.
If this doesn´t work, dump your original Rom, try flashing again your original Rom(downloaded somwhere) or upgrade a newer one.
If this doesn´t help, restore original Rom and send Omnia to the Servicecenter...
Regards
Related
Hello there.
I am in urging need of help. I am new to this HTC part and my phone just started freezing when i started the phone after i installed TouchPal and HTCHome 2.1.
I was wondering if you can reinstall the phone somehow cause i dont care if i lose all information on my phone.
Greets, Felix
Hard reset.
Google "hard reset for HTC diamond" and find the instructions on how to do it.
...or look through the WIKI. It has a wealth of basic information about the phone.
Thanks for the help. Works now
I seem to be having a problem with all of the WM6.5 Polaris ROMs. Hoping someone can help!
I first noticed the issue with Gullum's Rom, though it is still present with Belial's and Pcarvalho's
Basically soft-reset doesn't work. It will result in a hard-reset almost always. It doesn't matter if i use the soft reset pinhole or whether i use a program on the Polaris to soft-reset the device; the result is always the same - a hard reset.
In all circumstances I flashed the rom, waited until the screen alignment, hard reset (on purpose), then configured the phone.
Originally I thought the issue was because of pimbackup getting stuck sometimes and me resetting during that but it seems that even if I do not use PIM backup the phone will still hard reset it self.
The only thing that I can see being common is that the roms are all WM6.5 and all build 23016. When I downgrade to 3LIT3III (WM6.1 rom) the problem seems to go away - though I would prefer the 6.5 roms.
My phone has been flashed lots of times over the past 18 months and maybe something weird has happened. My next steps are to reflash the latest official HTC ROM in the hopes that fixes any weird things my phone might have before I try again.
If anyone has any suggestions I'd really appreciate them!
Thanks,
Dom
dlotters said:
I seem to be having a problem with all of the WM6.5 Polaris ROMs. Hoping someone can help!
I first noticed the issue with Gullum's Rom, though it is still present with Belial's and Pcarvalho's
Basically soft-reset doesn't work. It will result in a hard-reset almost always. It doesn't matter if i use the soft reset pinhole or whether i use a program on the Polaris to soft-reset the device; the result is always the same - a hard reset.
In all circumstances I flashed the rom, waited until the screen alignment, hard reset (on purpose), then configured the phone.
Originally I thought the issue was because of pimbackup getting stuck sometimes and me resetting during that but it seems that even if I do not use PIM backup the phone will still hard reset it self.
The only thing that I can see being common is that the roms are all WM6.5 and all build 23016. When I downgrade to 3LIT3III (WM6.1 rom) the problem seems to go away - though I would prefer the 6.5 roms.
My phone has been flashed lots of times over the past 18 months and maybe something weird has happened. My next steps are to reflash the latest official HTC ROM in the hopes that fixes any weird things my phone might have before I try again.
If anyone has any suggestions I'd really appreciate them!
Thanks,
Dom
Click to expand...
Click to collapse
flash original htc rom and then wm65...should fix this issue...cheers
pcarvalho said:
flash original htc rom and then wm65...should fix this issue...cheers
Click to expand...
Click to collapse
Hi, I've done that and so far it all appears stable... but I'm worried that by saying this I've now jinxed myself
Thank you for your suggestion! If only 'Microsoft My Phone' could restore text messages faster than 1 every 3 seconds... 3500 to go!
dlotters said:
The only thing that I can see being common is that the roms are all WM6.5 and all build 23016. When I downgrade to 3LIT3III (WM6.1 rom) the problem seems to go away - though I would prefer the 6.5 roms.
Click to expand...
Click to collapse
Exactly the same for me. Have tested the "[10 Aug] WM23016_MEGAPACK_ByBelial_BETA, "[Aug 14] PDAVIET ROM WM6.5 Manila 2D (Core 21840) by TranMinhMan" and"pcarvalho eXtreme ROM 3.19 WM6.5 OS 5.2.23009" and all of them was very unstable with 3 to 5 HR pr day.
Then flash to 3LIT3III (WM6.1 rom) and it vent solid as a rock.
I'l test flashing back to original before installing 6.5 again. Thanks for the tip.
I've noticed the same problem too and this tip fixed it (so far). My sequence of flashing is slightly different but the usual suspects were all there. My question is, is it always better to flash original HTC ROM first before flashing a new cooked ROM? Or will it make no difference?
lz8028 said:
I've noticed the same problem too and this tip fixed it (so far). My sequence of flashing is slightly different but the usual suspects were all there. My question is, is it always better to flash original HTC ROM first before flashing a new cooked ROM? Or will it make no difference?
Click to expand...
Click to collapse
its always better as you will flash a rom to a standard rom...every device has/had an original rom to start with...so all settings are...reset
For sure
After a couple of days usage now the phone has not hard reset itself at all - which is awesome - as is your ROM (I'm using the non-3D 23106 build of yours and haven't noticed any issues that a 'soft' reset doesn't resolve )
dlotters said:
I seem to be having a problem with all of the WM6.5 Polaris ROMs. Hoping someone can help!
I first noticed the issue with Gullum's Rom, though it is still present with Belial's and Pcarvalho's
Basically soft-reset doesn't work. It will result in a hard-reset almost always. It doesn't matter if i use the soft reset pinhole or whether i use a program on the Polaris to soft-reset the device; the result is always the same - a hard reset.
In all circumstances I flashed the rom, waited until the screen alignment, hard reset (on purpose), then configured the phone.
Originally I thought the issue was because of pimbackup getting stuck sometimes and me resetting during that but it seems that even if I do not use PIM backup the phone will still hard reset it self.
The only thing that I can see being common is that the roms are all WM6.5 and all build 23016. When I downgrade to 3LIT3III (WM6.1 rom) the problem seems to go away - though I would prefer the 6.5 roms.
My phone has been flashed lots of times over the past 18 months and maybe something weird has happened. My next steps are to reflash the latest official HTC ROM in the hopes that fixes any weird things my phone might have before I try again.
If anyone has any suggestions I'd really appreciate them!
Thanks,
Dom
Click to expand...
Click to collapse
You just said what I wanted.. same thing.. 23016 build Pcarvalho's rom. Sad..
tcfanboy said:
You just said what I wanted.. same thing.. 23016 build Pcarvalho's rom. Sad..
Click to expand...
Click to collapse
Pcarvalho's suggestion of flashing an original HTC rom is perfect - works well.
Hi gays,
How can I flashing ROM in HTC Diamon 2? My Diamond is dead.
My latest upgrade ROM did not proceed well. Proces was ending during loading. Upgrade from memory card is not funkcional and synchronization with PC is not funkcional too.
Try removing the battery, hard resetting it, etc. If that doesn't work, try jtag, although I don't know if anyone has done it successfully on the topaz yet
I try Hard reset and removig batery. That was first thing what I tried. Servisman try to flashing wholle day, bat not succesful.
Did you Hard SPL?
Hello,
my friend's /he dodn't speak english/ Leo have problem. The notifications of WM automatically pops up. It start slowly and as time goes on it pops up more frequently and faster. It is impossible to work on it. He tried to flash custom ROM again, but any change.
He tried to remove the screen protector but no luck.
He wearing his Leo in his pocket , but there are any physical changes on the Leo
ANY IDEA?
try going back to the stock (provider) rom.using custom roms can leave old files after flashing which can cause problems.
if that doesn't help try using mtty to format the phone and then flash a new rom.
okey, i tell him, but i can't believe to this because i use the same rom. this problem started after 2 weeks of using the rom.
but thank you very much and i will translate this to him.
hope it will help
okey. he tried to reflash the shipped rom but no luck. tried few hard reset and no luck. today he gonna try myty.
Hey,
a while ago I flashed from 1.48 to 1.66. After that, the soft reset bootup screen, bootloader, and after a hard reset it will report my device as running 1.66.
But as soon as I use SPB backup, it changes the "device information" entry to 1.48. Soft reset bootup screen still reports 1.66.
I didn't think too much of it really -- mostly because I figure this would be a good way for me to know what my original ROM version is anyways.
Until I installed a new radio ROM with CustomRUU. The program detected my device as a 1.48 device, not 1.66.
My concern is that this may mean some restrictions with regards to flashing in the future.
So...is there any way to change this? Do I need to change it at all?
when you change rom you shouldn't restore registry in the same way as you do after a normal hard reset.
I don't use them myself so I can't advise further but that's the reason.
its unlikely to cause many serious problems, being a standard official upgrade.
samsamuel said:
when you change rom you shouldn't restore registry in the same way as you do after a normal hard reset.
I don't use them myself so I can't advise further but that's the reason.
its unlikely to cause many serious problems, being a standard official upgrade.
Click to expand...
Click to collapse
Yeah. SPB Backup has a restore mode called "force ROM upgrade mode" and I would've thought that that would be sufficient.
It's been stable otherwise though so I'm not too concerned. Just find it interesting that the ROM version is being reported by data stored in the volatile RAM rather than the ROM itself.