Problems with G-Sensor - Touch Diamond, MDA Compact IV General

Hey folks,
i got a htc touch diamond about a week now, and my g sensor doesnt work anymore.
Whenever i start teeter, the ball speeds over to the upper lefthand corner of the screen, and even the Hologram tool doesnt work.
When i try and install the calibration tool from the official htc site it sais that my htc g sensor is out of balance, even when i lay it on the table.
Whats wrong?
Can i fix it somehow?
Thanks in advance!!
/cry

BryanMarley said:
Hey folks,
i got a htc touch diamond about a week now, and my g sensor doesnt work anymore.
Whenever i start teeter, the ball speeds over to the upper lefthand corner of the screen, and even the Hologram tool doesnt work.
When i try and install the calibration tool from the official htc site it sais that my htc g sensor is out of balance, even when i lay it on the table.
Whats wrong?
Can i fix it somehow?
Thanks in advance!!
/cry
Click to expand...
Click to collapse
Have you tried calibrating g-sensor with g-sensor tool?
http://msmobiles.com/news.php/7666.html

Jura_ZG said:
Have you tried calibrating g-sensor with g-sensor tool?
http://msmobiles.com/news.php/7666.html
Click to expand...
Click to collapse
like i said in my first post:
When i try and install the calibration tool from the official htc site it sais that my htc g sensor is out of balance, even when i lay it on the table.
Click to expand...
Click to collapse
i did, and it still doesnt work..
when i let it calibrate, it does that standard animation thingy, and it jumps right back to '****ed up' state.
Which is not good is it now?

BryanMarley said:
like i said in my first post:
Click to expand...
Click to collapse
Sorry missed that one
BryanMarley said:
i did, and it still doesnt work..
when i let it calibrate, it does that standard animation thingy, and it jumps right back to '****ed up' state.
Which is not good is it now?
Click to expand...
Click to collapse
I guess its a hardware error then.

Jura_ZG said:
Sorry missed that one
I guess its a hardware error then.
Click to expand...
Click to collapse
what should i do then? cus i cant really fix hw do i ? haha

send it back for repair....

Hey, tryed Hard-Reset?
Have the same problem now (till some days without realizing it really...) and backup current system now.
Hope a hard reset helps.. me and you ;-)

BryanMarley said:
what should i do then? cus i cant really fix hw do i ? haha
Click to expand...
Click to collapse
Try HR and if that don't help i suppose sending it for repair is the only option you've got left.

hard reset doesnt work, already tried it, gonna send it to htc then. Do they mind i installed HardSPL?

DO NOT SEND IT BACK WITH A HARD SPL OR FLASHED ROM!!!
your warranty is voided when u flash a Hard SPL, so you have to flash back a official ROM and original SPL.
I have a Offical HTC Touch Diamond, and i wrote down the original details incase i needed to flash it back.
ROM: _HTC Touch Diamond_QMR_RUU_Diamond_HTC_WWE_1.93.405.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe
SPL: Stock-Original_Diamond_SPL_1.37_Multi_Regional.zip
You can find both of these on this site.

mugglesquop said:
DO NOT SEND IT BACK WITH A HARD SPL OR FLASHED ROM!!!
your warranty is voided when u flash a Hard SPL, so you have to flash back a official ROM and original SPL.
I have a Offical HTC Touch Diamond, and i wrote down the original details incase i needed to flash it back.
ROM: _HTC Touch Diamond_QMR_RUU_Diamond_HTC_WWE_1.93.405.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe
SPL: Stock-Original_Diamond_SPL_1.37_Multi_Regional.zip
You can find both of these on this site.
Click to expand...
Click to collapse
thanks for the heads up, but erh, i bought it at vodafone, and they have their own branded rom, is there anyway to get that one back?

Before sending it back I would try flashing a different ROM....I suspect the issue is ROM related (S/W) and not h/w....

PJ6363 said:
Before sending it back I would try flashing a different ROM....I suspect the issue is ROM related (S/W) and not h/w....
Click to expand...
Click to collapse
No, its no sw problem, tried different roms. Is it maybe an idea to flash back to original SPL and then reflashing it to HardSPL? maybe hardspl is causing this?
And where do i find the original vodafone rom? (NL) cus i cant seem to find it on the site.
Thanks.

Related

[Walkthrough] How to fix your bricked phone

So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Here's tmobile's ROM.
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
ivanmmj said:
So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Click to expand...
Click to collapse
papamopps said:
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
Click to expand...
Click to collapse
I know it has been stated a million times. I'm just tired of the same question being asked over and over again and so here we are...
Too bad it'll be stated a million more times afterwards too.
falconeyez said:
Too bad it'll be stated a million more times afterwards too.
Click to expand...
Click to collapse
If we sticky it and threatened their lives if they don't read it... lol
ivanmmj said:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
Click to expand...
Click to collapse
It will not help!
ASerg said:
It will not help!
Click to expand...
Click to collapse
And we hold their pet's hostage?
ivanmmj said:
And we hold their pet's hostage?
Click to expand...
Click to collapse
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
falconeyez said:
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
Click to expand...
Click to collapse
Might work out, I get 10% of the over all sold
Ghostrider
Ghostrider said:
Might work out, I get 10% of the over all sold
Ghostrider
Click to expand...
Click to collapse
Fine, but I get 15% because it's my thread.
The instructions to do this are actually in my newbie thread. Which is a sticky.
TylerC161 said:
The instructions to do this are actually in my newbie thread. Which is a sticky.
Click to expand...
Click to collapse
I know, but most people don't search. I figured, maybe if it says "How to fix your bricked phone" on the title, they might get the idea.
It was actually done mostly as a joke...
help
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
gumbico said:
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
Click to expand...
Click to collapse
SPL 4.70.yang!!! your device is HARD-SPL!!
So going back to stockrom--> delete the SPL.nbh from EVERY RUU you are running.
Then it shouldn´t stop......
Big Thanks papa! That did the trick. My Wing is happy once again and running Open Touch. But I still want to give TouchIt another try.
And what if i cant find stock RUU mine came with some arabic keyboard and spl was 1.08 , thanks to Oli he didnt mention that SPL should be 4 or higher , so device is bricked since first Olis release and no way to find this arabic stock RUU.
Any Help ?????
Hitec
If the device had an spl of 1.08 prior to HardSPLing it, then you'll have to bring the device to your nearest repair center. There isn't a way around that. Oli doesn't know everything and that's the risk we take when we try new and experimental things that people create but have no way of testing. But, we live and learn. If it wasn't for that issue, you could always cook your own ROM and if the HardSPL was working, you could've easily flashed any ROM. But the keyboard wouldn't been wrong until you could find someone who had the correct keyboard and you extracted the ROM from it and cooked that keyboard driver into your ROM.
Oh noooo!!
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
foo_bar_baz said:
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
Click to expand...
Click to collapse
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
ivanmmj said:
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
Click to expand...
Click to collapse
Oh deary me! I am so dead now - I live in Tanzania, East-Africa. My "local" repair center is several hundred thousand miles away across The Big Blue. What exactly do the repair center folks do to fix the device? Perhaps I can soldier out myself with some guidance...
Thank you,
foo_bar_baz.

Problem with screen turns black (see this video)!

Don't know if others are having this problem with the screen fading black, but have seen it a couple of times on my Diamond, latest last night, I took the camera and filmed it.
Am troubled if something is wrong with my Diamond, or this could be the case of incompatible HardSPL
if someone's diamond came with 1.93 SPL originally, maybe this HardSPL based on 1.93 will work better than the olders. I have a report that someone has black screen with older SPL's.
Click to expand...
Click to collapse
This could be the case, was just wondering if others has had this issue, and if so how did you resolve it?
Here is the video: http://www.youtube.com/watch?v=5y5CW05sSVc
Did you try flashing your SPL and then Hard Resetting ?
That doesn't look right to me. I will upgrade to latest rom, if that doesn't help, I will send it back for repair.
Scotchy49 said:
Did you try flashing your SPL and then Hard Resetting ?
Click to expand...
Click to collapse
Am trying an other HardSPL now, dont know what SPL my phone came with stock.
mmp7 said:
That doesn't look right to me. I will upgrade to latest rom, if that doesn't help, I will send it back for repair.
Click to expand...
Click to collapse
Am currently running Duttys 2.2 though the problem also on latest stock rom, but only noticed it when going from HardSPL and back to stock SPL just dont know what SPL the phone came with, so maybe I have only treid the wrong ones.
Hmmm. I think that when you install a stock rom it will also reinstall stock SPL.
Scotchy49 said:
Hmmm. I think that when you install a stock rom it will also reinstall stock SPL.
Click to expand...
Click to collapse
No that is not the case I an afraid, you have to install the SPL manually as a seperate installation from the ROM.

Hellp... my G-sensor not function...

After I get new rom and a unsigned Hard SPL my G-sensor just show the programs in vertical position... in Teeter, the ball just stay at the up side of display... Why???
What ROM did you flash to?
From the first momment I tried the Energy rom, after, dutch, ahen, macadam, and others... but in all of them my display shows some programs in up-side-down position... where I mistake?
I have the same problem
I have tried different ROMs but i am still not able to use teeter
Helllpppppp... If some one knows...
i have the same problem after i crashed my diamond...may be you guys crashed it and didnt notice that you just broke the g-sensor hardware....
Are you sure about this ??
I dont think we can break the g-sensor hardware so easily without even having a scratch on diamond. :|
I don´t think its possible... ´cause I just change rom... in the same moment it wasn´t function...
Maybe it change to the original Hard SPL 1.93 get back to the normal form... but I don´t know how can I make it turn back to 1.93... ´cause the file isn´t executable...
I have HardSpl 1.93 and it doesnt function for me
is there a newer HardSpl that i can try maybe ??
Guys can any1 of you help us out here ??
abhishek.vij said:
Are you sure about this ??
I dont think we can break the g-sensor hardware so easily without even having a scratch on diamond. :|
Click to expand...
Click to collapse
sure 99%
anyway,what it is the connection between gsensor and hardspl???
I don´t know what´s connection... but my friend had the same problem and he get his diamond to support and there the support just put another rom (Official) with a 1.93 hard spl and the g sensor turn on perfectly without hardware damage...
So...
the same problem in more then 3 diamonds (If I correct)... it isn´t a hardware damage...
@ Foxlou : any updates from your side ?
I have been trying very hard to make this work but it just doesnt work . I am thinking of going to a service center and giving them the device..
abhishek.vij said:
@ Foxlou : any updates from your side ?
I have been trying very hard to make this work but it just doesnt work . I am thinking of going to a service center and giving them the device..
Click to expand...
Click to collapse
let us know it its a hardware issue
Guys try to flash with a stock ROM (2.03). If it doesn't work, try another SPL like Olinex 1.40.
If you want to know what kind of problem is it (hardware or software) just flash with stock rom and stock spl.
very easy to identify whether is ur g-sensor hardware spoil or not function
go www.htc.com flash ur latest diamond ROM .. check whether the g-sensor working anot .
For me i still would recommend use offical ROM
I flashed with the Stock rom but the problem is that i am not able to put the stock SPL.. i have HSPL 1.40.
Whenever i flash with stock SPL it will show as 100% but still i wont get the Stock SPL. Btw guys any links for stock spl 2.03
g sensor solution
download gyrator
idada10 said:
download gyrator
Click to expand...
Click to collapse
this is funny
anyway i have original ROM and SPL..and still doesnt work

My Touch HD just died

Hi,
I just flashed Pdavietv 65.
After 10 minutes of using it, I locked the phone using the WM lock.
When i wanted to unlock it, the screen doesn't respond anymore.
I did a hard reset, I can't type anything on the screen, screen doesn't feel my fingers....
Anyone has an Idea?
I try to flash stock rom right now...
Sorry for my bad english
darkblue68 said:
Hi,
I just flashed Pdavietv 65.
After 10 minutes of using it, I locked the phone using the WM lock.
When i wanted to unlock it, the screen doesn't respond anymore.
I did a hard reset, I can't type anything on the screen, screen doesn't feel my fingers....
Anyone has an Idea?
I try to flash stock rom right now...
Sorry for my bad english
Click to expand...
Click to collapse
Flash another rom from the tri-color screen.
I just flashed the frenck Stock Rom From HTC.
I can't access.
When i 've the screen 'tap the screen to align screen', Nothing happens when i Touch the screen.
Only vol UP and down and power off are working....
Any solution?
Thanks
I think your digitizer unit died..get one one ebay and replace it
try fresh a stock rom which includes SPL as well.
mcdull said:
try fresh a stock rom which includes SPL as well.
Click to expand...
Click to collapse
You have a link please?
darkblue68 said:
You have a link please?
Click to expand...
Click to collapse
Try Putting your Phone in BootLoader mode.
Flash it with HARD SPL1.56
Then Try Installin a Fresh firmware again, a Hard Reset n it will be fixed.
I did all of this...
Nothing, I think I must send it to HTC...
I think your HD died touchscreen . You need to bring the HTC Service Center for repairs. If you is bought on ebay then there will pay for about 200 USD
My Touch HD just died
R.I.P. !
Damn all was working nice.
I did nothing.... Only flashed all days another rom
And when i wanted to call a friend yesterday,the screen didn(t respond anymore....
Grrr, I will send it to HTC this week, and i will by a Topaz One...
Leo is too big for my pocket....
ancola66 said:
I think your HD died touchscreen . You need to bring the HTC Service Center for repairs. If you is bought on ebay then there will pay for about 200 USD
Click to expand...
Click to collapse
DIY for 30 USD..ebay the spare part.
Had one same condition and fixed flashing with an original rom. Radio+Rom and Align screen on startup/\
I was in same condition as yours ,When in typped align scren nothing but after flash and a hard reset everything getback
Me, nothing after flshing original Stock ROM and originalHSPL.
But solething is very strange.
When the backlight power off (the dimmer), it comes back when i hit the screen... But i can't align the screen, the screen doesn't recognise my touch.
Why the dim is working when i hit the screen ans my gesture are not recognised?
Thanks a lot
Greats from France
It looks like only the alignment of the screen is wrong. Why it does not get fixed when flashing original ROM is strange. But the fact that the screen response to touch (returning from dim) should mean that the digitizer is OK.
Yes I think the digitizer is OK.
But I don't know what the problem is.
I will try to reflash tomorrow a custom Rom without align to screen at first boot....
Thanks
try mtty to completely erase ur internal memory..
then flash stock rom..
Ok, a few simple queries to help solve your issue. I'm assuming you used USPL or HSPL before flashing rom? and correct version of HSPL? Can you still access bootloader? What is your SPL?
If you can access bootloader, all is not lost and your device is not bricked.
I'd recommend flashing original stock rom onto your device and starting from fresh. Stock roms can be found in the wiki here. Once you have restored stock rom and if you still want a cooked rom, follow thisguide.
Let me know the answer to the above queries and how you get on.
Hi,
I used the SPL by Olinex.
Now i revert back to the original SPL.
When i enter in booloader mode, I can see: SPL-1.54.0000
Is this ok?
Before flashing the origal SPL i flashed the original French Stock ROM.
What is MMTY ?
Thanks
darkblue68 said:
Hi,
I used the SPL by Olinex.
Now i revert back to the original SPL.
When i enter in booloader mode, I can see: SPL-1.54.0000
Is this ok?
Before flashing the origal SPL i flashed the original French Stock ROM.
What is MMTY ?
Thanks
Click to expand...
Click to collapse
Solution should be found here including MTTY info & instructions. Same method for HD

Please help, I think I bricked my phone :(

Sorry if I shouldn't be writing a new thread about this, but I couldn't find a thread about bad flashes...
I'm a newbie with this, and I think I just bricked my phone after only my second flash I have a Touch Pro 2 (T-Mobile), and I was able to successfully install HardSPL. I even flashed the EnergyROM LEO with no problems. After a few days of playing around, I tried to flash the AthineOS v2.0 ROM, and now my phone won't boot up... it gets stuck in the Touch Pro 2 black screen with the red lettered version numbers at the bottom. I tried rebooting and pulling the battery out, but I have had no success in being able to boot it back up.
Any ideas on how I can fix this? This sucks I've only had the thing for less than a month...
localcall001 said:
Sorry if I shouldn't be writing a new thread about this, but I couldn't find a thread about bad flashes...
I'm a newbie with this, and I think I just bricked my phone after only my second flash I have a Touch Pro 2 (T-Mobile), and I was able to successfully install HardSPL. I even flashed the EnergyROM LEO with no problems. After a few days of playing around, I tried to flash the AthineOS v2.0 ROM, and now my phone won't boot up... it gets stuck in the Touch Pro 2 black screen with the red lettered version numbers at the bottom. I tried rebooting and pulling the battery out, but I have had no success in being able to boot it back up.
Any ideas on how I can fix this? This sucks I've only had the thing for less than a month...
Click to expand...
Click to collapse
hi if you have done the hardspl then try this
to enter Bootloader
Remove the back cover from the phone.
Hold the Volume Down button.
Use the stylus to press the reset hole.
Or if the device was powered off, press the power button whilst holding down the Volume Down button.
you should see serial at the bottom of the three color screen then plug in the usb cable the serial should change to USB then just flash another rom.
i hope this helps you.
Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...
localcall001 said:
Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...
Click to expand...
Click to collapse
only to pleased to help I am glad you got your phone back working
localcall001 said:
Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...
Click to expand...
Click to collapse
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
idd, this is not ROM related, its just unlucky like hell. See the phone as a PC, where blocks need be written. If a block fails or is corrupt, you get these jokes. Its like a BSOD on a Windows PC.
I gotta admit it is great knowing that once you've done a hardspl you are safe as houses as even if you flashed the most currupted ROM, the bootloader will always allow a reflash.
This is way more stable and safe than any other experience I've had of phone flashing.
b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
Funny that, your latest ROM was the only one I had problems with - the same problems as the original poster, in fact. I flashed a different ROM fine, re-downloaded your 2.0 and flashed it again, same problem. Hanging on the boot screen.
b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
Probably I think I was just unlucky. My fear (while I was panicking) was that your ROM is European based, and since mine came from T-Mobile, it didn't mesh well. I also didn't unlock my phone so that could be also be a problem...
awesome community
localcall001 said:
That's a really cool recovery feature from HardSPL...
Click to expand...
Click to collapse
well..this is a normal recovery feature for stock spl also
Same Issue
I had the same issue with AthineOS v2.0 ROM it gets stuck on Touch Pro 2 logo
wahida76 said:
I had the same issue with AthineOS v2.0 ROM it gets stuck on Touch Pro 2 logo
Click to expand...
Click to collapse
no one have told me that on my thread... only here i found this issue.. and finally how pass the problem?
I had to re-flash a different ROM.
I'm wondering if it's related to the radio version...
what is your version of radio
can't you flash the latest 23060?
i use radio 3.36
I've used 4.49.25.05 and have just got the same result on 4.49.25.17
I'll try flashing 3.44.25.27 (the oldest in the radio thread) and re-flashing your ROM.
Alas, no luck with that one either.
I have no idea why it doesn't seem to work on my Rhodium :/
I'm sorry if I'm hijacking this thread but it's the only one I've found that's even close to having the same issue I have, though I'm still using the stock rom/os.
I was installing winmo msn messenger. It installed fine and reset my tp2 fine. It goes thru the tp2 splash screen, the verizon splash screen and the winmo splash screen. Then it shows owner information and this is where it gets screwed up. Owner info will stay up forever if I dont touch the screen. After touching the screen the only thing left will be the top bar and the rest of the screen stays black. The only things on the top bar are the signal icon (which always has an x), the wifi icon (which seems to be connected fine lol) and either owner info will still be in the upper left or the start menu will be there. Hitting the screen only causes my tp2 to beep.
Nothing I know how to do (which is basically just hard and soft resetting it) works. Verizon can't fix it (didnt think they would be able to) and I can find no drivers (possibly cause I'm still a noob with winmo) to resolve my issue. I'm not even sure how I'd get them on as it wont even sync up to my computer and my computer cannot find its hd. If I could get a rom for the verizon one I think I can figure it out from there with no issues...but htc website sends me to verizon website for support and vice versa. The htc wiki is the closest I've gotten to an answer...but no rom to download. The only OEM roms I can find anywhere aren't for this phone, unless one of those will work? You guys are the experts.
Does anyone know what I can try? Verizon wants me to return it but cannot tell me when I'll get my new one as they are out of stock...again. Please help lol! Thanks for any and all help.
Mr.Clark said:
I've used 4.49.25.05 and have just got the same result on 4.49.25.17
I'll try flashing 3.44.25.27 (the oldest in the radio thread) and re-flashing your ROM.
Click to expand...
Click to collapse
i using this..
*Change the radio to 3.46.25.30 (Hot Fix For GPS Lock)
and also try the latest release of my rom.. (maybe you have bad file bad download)
b16b said:
i using this..
*Change the radio to 3.46.25.30 (Hot Fix For GPS Lock)
and also try the latest release of my rom.. (maybe you have bad file bad download)
Click to expand...
Click to collapse
Sorry, I tried that one as well yesterday. And I've downloaded your ROM a few times too...
Are you still working on the 6.1 ROM? Maybe a new version will just magically start working for me...
EDIT: Tried a fresh 3.46.25.30 and a fresh download of your ROM. Still nothing

Categories

Resources