mda4 want to go back to t-mobile 1.73 - Touch Diamond, MDA Compact IV ROM Development

mda4 the problem is only getting worse, I'm from the 1.73 t-mobile version went to 1.93 and is now with swifb7.5 however
crashes every day (useful in conversations and your alarm clock to expire)
often with a soft reset after installation problems with startup touchflo3d and often error manila.exe below uberhoubt as he is already so far
hard reset is also often already halfway down.
In short ideal device to send back to my old mda3 again to use
But is it possible to go back to the original 1.73 Tmobile and where is it located?

Use Search
marz01 said:
mda4 the problem is only getting worse, I'm from the 1.73 t-mobile version went to 1.93 and is now with swifb7.5 however
crashes every day (useful in conversations and your alarm clock to expire)
often with a soft reset after installation problems with startup touchflo3d and often error manila.exe below uberhoubt as he is already so far
hard reset is also often already halfway down.
In short ideal device to send back to my old mda3 again to use
But is it possible to go back to the original 1.73 Tmobile and where is it located?
Click to expand...
Click to collapse
Hi there,
A simple search through the few posts below yours would have lead to here
http://forum.xda-developers.com/showthread.php?t=435826
However, instead of just giving up, why not try to find out why your device is behaving as it is..?
With a little reading, I'm beginning to get used to the Diamond and it's litte needs. Mine's running very well on a slightly older ROM from one of the developers on here.
I hope this helps answer your needs..?
Cheers,

thx for the answer,
I have tried my mda4 for a few months now but is getting every day worse and worse.
I have tried serveral roms now.
I don't know what else to do besides then sent the mda4 back.
I will try this rom to sent it back
http://forum.xda-developers.com/showthread.php?p=2600096

have you tried changing to a different Hard SPL. These can cause problems.

tried the HardSPL-1.24 and the Unsigned-Hard-SPL-Diamond-OliNex
I have downloaded the RUU_Victor_TMO_NLD_1.37.114.3_Signed_Diamond_52.26a.25.09_Radio_1.00.25.03.nbh
How do i start this file?

i have put the t-mobile file in the 1.24 map.
But the radio stay on 1002505?
rom is now 1371143.nld and till now no problems

Related

Attempting to update 1 week old 8525 to ATT WM6 - Probs...

Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
Are you following the directions at THIS GUIDE . What ROM are you trying to put on there? Did you CID unlock the device? Are you running Vista? Do you have .NET 2.0 or 3.0 version?
That should be enough questions to get us started.
Did you read my title? This is the stock ATT WM6 that came out yesterday. No need to unlock the phone, it is a 1 week old ATT 8525 with the stock ATT WM5 Rom on it.....
Windows XP SP2+ PC.
If it's the rom RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship maybe it had some problems because if you go to the official release site http://www.htcamerica.net/support/8525/software-downloads.html they are still showing the WM5 rom for download.
There may have been a problem with the release and they pulled it back for some reason. Just a thought and not much help I'm afraid.
Yes thats it. When it ID's my current Rom and what it will upgrade to, it is correct. (it shows it's 3.62 vs my current 2.xx) Many peeps have had no problem upgrading to it. (most find it a very good Rom from the varios sites I read)
And this page at HTC still has it up:
http://www.america.htc.com/support/8525/software-downloads.html
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
@brorex he can wait till christmas next year, if the updater cant communicate with the device , because it has closed AS then it will never update.
@JETninja
try doing what i said to this guy here,
http://forum.xda-developers.com/showthread.php?t=341282
yesterday he upgraded with the same rom and device and it worked
brorex said:
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
Click to expand...
Click to collapse
I thought that too, but after the color bar test when it want to set you up to actually install the ROM, the Upgrader whats you to make sure there is an active connection with AS. Well, there isn't. It shut down and the PPC is still showing the color bars. I can reset it, then re-sync to AS. (after having to re-launch AS from the Program Files - it no longer resides in the Tray when it shuts down during the process) I then get it going again, it attempts to start the ROM upgrade, AS quits again.....about a min later I get the Communication Error message....
I'm downloading a 2nd copy right now, will try it as soon as it completes...
*Edit...think I have an idea what I'm doing wrong, I have it connected and synced too early, the first part of the ROM updater is just a PC test, I'm thinking the PPC should not have been connected at that time. Re-trying it now.....
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Going to give it a shot here at work on this PC. If no go still, will try the above mentioned methods. PC at home kept getting communication errors...
i had the same problem
make the connection at AS then start the update process.... the 8525 will go into 3 bar mode and when the update gets to the upgrading rom screen... the installed rom wont show up.... hit upgrade... and then continue and it will work.... i was stuck there for a while too because if i waited for the istallation to load then made the as connection the right image would show up in the installer but then it would stop working after that.....
I just put this rom on my 8525 and it worked well for me. My 8525 is unlocked with supercid so I had to extract the OS and update using the methods described for working with SPL-140 Olipro with IPL-1.01 or the "How not to Brick thread".
That won't help you much as you don't want to do that mod to your New 8525 and void the warranty, but thought you might like to know the stock OS seems pretty stable at this point and I have had no problems yet.
Thanks everyone! It finally worked here on my Work PC. At home I could get to the Bootloader, but it would lose connection for some reason. Here I lost it the first time, but tried it again and it managed to stay connected and apply the update. Got it up and running, applied owner info, just now re-doing the AS relationship. (a good 500+ contacts! LOL! It'll take a little while as usual!)
Then it's back to all the tweaks I like so far...and some new ones I've held up on since I've been waiting for WM6.
Out of my 3 PDA's (2 ipaqs and this puppy) this one has certainly been the trickiest ROM update, but it seems to be more my device since most don't have this much trouble.
Thanks again!
So far- So good, but just one problem- BATTERY!!!
After I installed upgrade, my battery drains in few hours... I reset phone, I reloded upgrade- nothing helps! Warranty still in affect, but phone worked well and I'm positive- hardware is OK. What else can i do to fix this problem?
I have the same problem
ai6908 said:
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Click to expand...
Click to collapse
I have the same problem exactly. As soon as I start the upgrade the device immediately sleeps and the connection is lost. 1 minute later I get a Connection error message.
I am new to all this. How do i put the machine in 'boot loader' mode?
Thanks
Just did this rom update again on a 8525 the installation went extracting files active sync shut down wait a few minutes nothing happens the the upgrade screen no ACTIVESYNC connection while update is happening as soon as device is in bootloader mode activesync closes out

Hermes WM6.1 Freeze/Lockups and Hard Resets

I'm opening this thread to find out the answer as to why the Hermes freezes or lockups on WM6.1. It gives you no other option but to soft reset. Unfortunately, it stays on your second splash screen after a soft reset; so, you will resort only to hard reset your device.
In some cases, it even causes to hard reset your device without warning after a freeze. It's not how long you use the device... it's what you are using most frequently.
In my observation over the last two weeks, it freezes in the following occasion:
1. restoring messages using dotFred PIM Backup
2. introducing exchange server settings
3. frequent closing and opening of SMS application
4. frequent sliding in/out of keyboard
To single out the problem, I have not introduced any changes to the ROM or even installed CABs. I am merely trying to use the base ROM like I used to with WM6.
I have tried various ROMs todate: Schapps, PDA viet, TNT, No ROM maker, Faria's and they all result to sudden system fault in the two Hermes that I have in my possession. I figured, this must be a 6.1 thing, but I noticed that it has not been given attention.
So, let us hear your freeze and hard reset problems on WM6.1 guys!
the only rom that hasnt froze on me has been CRC's rom. All the others seem to suffer from this weird problem.
After so many testing, one more would not hurt thanks for the feedback. Will give it a try.
tjlabais said:
I'm opening this thread to find out the answer as to why the Hermes freezes or lockups on WM6.1. It gives you no other option but to soft reset. Unfortunately, it stays on your second splash screen after a soft reset; so, you will resort only to hard reset your device.
In some cases, it even causes to hard reset your device without warning after a freeze. It's not how long you use the device... it's what you are using most frequently.
In my observation over the last two weeks, it freezes in the following occasion:
1. restoring messages using dotFred PIM Backup
2. introducing exchange server settings
3. frequent closing and opening of SMS application
4. frequent sliding in/out of keyboard
To single out the problem, I have not introduced any changes to the ROM or even installed CABs. I am merely trying to use the base ROM like I used to with WM6.
I have tried various ROMs todate: Schapps, PDA viet, TNT, No ROM maker, Faria's and they all result to sudden system fault in the two Hermes that I have in my possession. I figured, this must be a 6.1 thing, but I noticed that it has not been given attention.
So, let us hear your freeze and hard reset problems on WM6.1 guys!
Click to expand...
Click to collapse
I have semilar issue and now the problem is solved. please click on my signature below why did I go back to official ROM for the detail threat.
same here
i even got my device changed since i thought it was a hardware problem.
it only happens on wm6.1 though, so as much as i like the added speed and threaded sms, flashing the original wm6 rom fixed it and from there im going to keep to wm6.0 - it worked quite nicely.
I suspect (a lot) of bigstorage or some bug on the write-to-internal-rom cache/buffer (if exists) associated to any app that writes to fast to the ROM.
I notice when I use anything on SD card that nothing bad occurs but if I use the internal mem (SMS, internal apps, etc) it freezes all the time.
I had these issues until I used mtty.exe to clean up some bad blocks and then flashed Faria R32, since then no more issues (though opera 9.405 sometimes will freeze my hermes).
I had the same problem until I flashed the offical AT&T WM6 rom with radio and then flashed back to wm6.1..
No freezes or hard resets since..
I don't think this is a big storage issue... if it were, wm6.1 in other similar devices like the trinity would have suffered the same fate, but it doesn't.
I really don't see the point of going back to an ATT official ROM before flashing 6.1. But a lot has said that they no longer have this issue after doing so, then it must be RUU related.
It might also mean: a full ROM flashing for 6.1 might be necessary.
Either way, I'll continue testing, but it would be nice if other guys with this issue will be willing to help test it...
I just made some digging, and just found out how some wm6.1 users get their freezes/lockups. There issue was due to radio compatibility.
hmmm... if the WM6.1 ROM was built with OEM from the AT&T Official, then the radio that best match for it is from the AT&T as well.
This might explain that flashing the AT&T official prior to flashing the wm6.1 sets the radio to AT&T.
Hope this will solve the freeze/lockup mystery.
Have any of you guys tried changing/switching RADIO ROM while in WM6.1?
I just did, trying to experiment. Prior to WM6.1, I loaded an Official Dopod WM6 ROM. Then I loaded the Faria-R32 Full version.
Although, I did not have freezes on the first day of testing... I decided to switch to Radio 1.54 since most users flashed the AT&T Official prior to flashing WM6.1. Guess what? It flashed successfully and boot successfully for the first time. However, when I make a call, the audio has a very poor quality. So, I reset it using the reset button just to clear it up; however, it hanged on first screen... then I reset one more time, it hanged on 2nd screen, then I reset again, it hanged on WM screen.
Enough of it, so, I loaded back 1.47.0.10, and I'm back in business? No. The switching of the Radio ROM has caused the ROM to be corrupted... Somehow, the RADIO has something to do with the freezing...
WM 6.1 ROMs are very unstable (Faria, TNT, etc. I tested several, including those "naked" or clean)
After I install some (useful) software like HTC Home and some other 2-3 programs and after some hours it froze (it did with Faria, TNT, etc). TNT´s WM6.1 is a little more stable (takes longer to froze) but Faria´s WM6.1 is faster.
The more we use the internal flash memory, the faster it frozes and requests a hard reset. Since Friday I hard rebooted some 20x (Faria + TNT roms).
I´ll go back to WM6.0 for now.
EDIT: I installed my radio rom after the last main rom and works very well (I update all roms from the SD card). I updated before and after the main rom (but it never got corrupted) and they frozed. In my case nothing to do with the froze.
I nearly advised my friend to send for service thinking a big hardware problem. Thanks as now I know it's not the phone itself .
Hello,
I had the same problem when 6.1 came out on all 19199.0.7.0 builds. For me the solution was to update to a ROM using build 19199.1.0.0. Since then I had no hard resets at all (I am running CRCs PHK v12 Release 9 for about 2 weeks now).
Maybe this works for you as well.
Cheers,
Uli
mmick said:
WM 6.1 ROMs are very unstable (Faria, TNT, etc. I tested several, including those "naked" or clean)
After I install some (useful) software like HTC Home and some other 2-3 programs and after some hours it froze (it did with Faria, TNT, etc). TNT´s WM6.1 is a little more stable (takes longer to froze) but Faria´s WM6.1 is faster.
The more we use the internal flash memory, the faster it frozes and requests a hard reset. Since Friday I hard rebooted some 20x (Faria + TNT roms).
I´ll go back to WM6.0 for now.
EDIT: I installed my radio rom after the last main rom and works very well (I update all roms from the SD card). I updated before and after the main rom (but it never got corrupted) and they frozed. In my case nothing to do with the froze.
Click to expand...
Click to collapse
I don't think it's the way it's accessing the memory; otherwise, other devices would have suffered the same fate. So far, only the hermes suffer the freezing syndrome which means that there is something in the hermes that is not fully compatible with the WM6.1 build.
did you try to flash the AT&T build prior to flashing the wm6.1 build?
hukoeth said:
Hello,
I had the same problem when 6.1 came out on all 19199.0.7.0 builds. For me the solution was to update to a ROM using build 19199.1.0.0. Since then I had no hard resets at all (I am running CRCs PHK v12 Release 9 for about 2 weeks now).
Maybe this works for you as well.
Cheers,
Uli
Click to expand...
Click to collapse
I was hoping someone would release the 19202.1.0.0 build since it has the updated GWES...
After 24hours with Faria-R32 Clean version. I did not have any freezing syndrome. This is after I flashed with a Dopod Official ROM. I only got the freezing syndrome by flashing 1.54 Radio ROM.
My next move is to use a different RUU for flashing.
My Faria 6.1 also hard-resets and locks up
I had just recovered from a previous hard reset and read all posts in this thread and the other one currently dealing with this topic (http://forum.xda-developers.com/showthread.php?t=370185), and had gone down to a previous ATT radio rom and switched off SD power management out of desperation, when my Hermes locked up again. This time, however, after two soft resets (stylus induced) I managed to get it running again. Everything seemed to be in the previous state (all my preferences had been preserved), but I found that all contacts, history and calendar items had gone.
I had installed no other software than the network wizard. I had recovered most information from Outlook and the rest from Pimbackup (which by the way keeps crashing when restoring speed dials in 6.1).
As this must be the 6th hard reset in 6 days, I think I'm going back to Schap's good old 6.0 and wait for a solution.
BTW Don't take me wrong: I'm extremely grateful for all the great work done by the various cooks.
Lockups
I thought I was going crazy;my 8525 would lock up an have to be soft reset and when it came back, the contacts would all be gone.
I use Yahoo!Go to sync my contacts. I use Photo Contacts Pro for my contacts manager. I was trying to figure out if it was either of those causing the problem.
I even have a thread going on Microsoft's windows mobile forum about this.
I get NO answers from anyone. I'm running Schaps 4.30 OS and Radio 1.54.07.00. I have a 2gb sd card that I run a few apps from.
You just described the same problem I have. Thank you for confirming my limited sanity!!!
tjlabais said:
I was hoping someone would release the 19202.1.0.0 build since it has the updated GWES...
After 24hours with Faria-R32 Clean version. I did not have any freezing syndrome. This is after I flashed with a Dopod Official ROM. I only got the freezing syndrome by flashing 1.54 Radio ROM.
My next move is to use a different RUU for flashing.
Click to expand...
Click to collapse
If i could get hold of the 19202 source I would probably post a clean naked version for testing....but alas no such luck. Naturally it would help had i got a source for new ROM builds lol!
mrvanx said:
If i could get hold of the 19202 source I would probably post a clean naked version for testing....but alas no such luck. Naturally it would help had i got a source for new ROM builds lol!
Click to expand...
Click to collapse
I totally agree with you... when I cooked ROMs for the XDA Atom, I didn't want to work with none official ROMs because I wouldn't know what has been altered in the adopted device.

Problem with the 1.93.xx release.

I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Sprite?
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
ruffruff said:
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Click to expand...
Click to collapse
Yes i had same problems. imo the 1.93 isnt a stable rom(yet) so im back with 1.37.456.2 this one is just perfect,very stable,less memory leakage.
Well, the problem is still on going. I can't flash my phone anymore for some reason, even though I've tried both, unsigned and signed Hard-SPL, which both of them flash fine. However, the phone gives me error [276] update error. So not sure what exactly is going on here.
Also, no, didn't sprite backup, phone's just being retarded, mobilecityonline will repair it, but it will take almost 4-6weeks, I cannot wait that long. What else should i try?
Okay, nope not fixed... Flashed it with 1.37, connected to the network for a few seconds, dialed somebody and no ring or anything, but when i called my phone i could hear my own voice. So I guess i have to send it in for repair. Damn.
berlinberlin said:
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
Click to expand...
Click to collapse
Could you please detail? I've flashed 1.93.xxx just in the day it appeared on the site and after flashing, I've restored the backup made with Sprite Backup to preserve the settings and so on. I wasn't worried about the contacts/calendar since I have them in Outlook, but I didn't want to start all over with settings, install programs and so. I've made the restore in "upgrade mode", restoring also the databases. The result was that I got a verry strange TF3D, displaying "Home" between the operator name and date, and strange behaviour. I've seen also that the animations were taken out so I've flashed back 1.37.xxx.3. Could be any problems generated by the restore operation? Should I use a different restore type (eventually not selecting "restore databases")?
I have had no problem with the new 1.93xx rom.
Touch FLO 3d is quicker (probably because the animation is disabled)..
and the battery life is about 20% better
Radio ROM Anyone
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
mhbr12742 said:
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
Click to expand...
Click to collapse
I am on 05 and has no problem ( have been using it for a day now)
I don't know, but If i plug the diamond into my adapter, the network suddenly works and I can actually make calls and everything's fine and dandy, but just on the battery, I can't call anyone, and if I pull out the adapter when the phone gets a signal, the signal stays but again, can't call anyone because i can't hear anything.
It's an awkward problem. I'm not sure if it's my battery or something. So I'm getting another battery off ebay since they don't sell HTC Touch Diamonds in the U.S. yet.
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
adwinp said:
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
Click to expand...
Click to collapse
Yes, me I had same problem twice - freezes on PIN input screen, second problem with this release is that sometimes PIN screen doesn't appear. Now I'm back on 1.37 and everything seems to be ok
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
THe Problem you've encountered:
1. Random auto reboot
2. Random freeze
3. etc.
It's sounds familiar to me. Well it's maybe have to do with SPL just like the Kaisers do.Well, I said maybe... So, what we did to our Kaiser before is flashing the HardSPL which has the same version number as the ROM flashed. So, if you're using ROM 1.93 then the HardSPL should be flashed is Olinex HardSPL 1.93 or you can try one by one of the developed HardSPL existed in this forum. My saying is, go with HardSPL 1.93 and see what happen. If it's still no go then it must have to do with the ROM itself.
Just my 2cents.

[Q] Device hangs at random when witching on

Hi all,
My Diamond is acting weird lately; sometimes (so far it seems at random) when I turn on the device (from standby), the display is grey'ish / scrambled, and nothing works. I have to removed the battery to get it working again.
This happens with all ROMS found here (haven't tried stock rom yet).
Anyone know what this might cause?
I'm running dev. edition SPL from olinex...
Any tips would be greatly appreciated!
/edit; Could this be SPL related?
Maybe perform the hardSPL again?
Reform the battery for a minute. After this hard reset your device a few times.
If this doens't fix the problem use your original ROM and send the device back for repair.
Would be my solution
I have the same problem. Diamond swiches to standby mode and does not resume or just the light switches on and the screen is blank. Sometimes, it even switches off while booting. All the time, I have to remove the battery. And after some "battery remove resets", the error seems to occur more and more often. It also suddenly looses the phone signal but immediately finds a new one ofter 1-2 seconds.
I think it is somehow related to the phone chip-whatever. Because when I turn the phone of it seems to run more stable. Errors are not gone but at least I can use it as a mp3 player then.
I tried lots of roms but none of them worked fine. I even restored the original spl to make sure it is not the spl. But error is still there... stronger than ever
I will send it back to htc. This thing is obviously broken. Its one of the typical qualcomm errors. These chips are... what do you say in english... moody? My old polaris had a similar error. the 3g part of the phone went away.
TerianSilva said:
I have the same problem. Diamond swiches to standby mode and does not resume or just the light switches on and the screen is blank. Sometimes, it even switches off while booting. All the time, I have to remove the battery. And after some "battery remove resets", the error seems to occur more and more often. It also suddenly looses the phone signal but immediately finds a new one ofter 1-2 seconds.
I think it is somehow related to the phone chip-whatever. Because when I turn the phone of it seems to run more stable. Errors are not gone but at least I can use it as a mp3 player then.
I tried lots of roms but none of them worked fine. I even restored the original spl to make sure it is not the spl. But error is still there... stronger than ever
I will send it back to htc. This thing is obviously broken. Its one of the typical qualcomm errors. These chips are... what do you say in english... moody? My old polaris had a similar error. the 3g part of the phone went away.
Click to expand...
Click to collapse
Sounds bad
I'm trying an updated radio rom at the moment, we'll see if it hangs today...
mikkelnl said:
Hi all,
My Diamond is acting weird lately; sometimes (so far it seems at random) when I turn on the device (from standby), the display is grey'ish / scrambled, and nothing works. I have to removed the battery to get it working again.
This happens with all ROMS found here (haven't tried stock rom yet).
Anyone know what this might cause?
I'm running dev. edition SPL from olinex...
Any tips would be greatly appreciated!
/edit; Could this be SPL related?
Click to expand...
Click to collapse
Hi mikkelnl... from what you described, it seems to be a typical problems with the SPL you are using. Depending on which SPL that the original ROM that came with your device, you can resolve by installing the respective 1.37 OliNex HardSPL Unsigned or the 1.93 OliNex HardSPL Unsigned by cmonex.
Try to get it from the same thread that you got the 1.40 OliNex HardSPL-Developers Edition. There is also some explanation on the problems that you are experiencing.
One more thing, Radio 1.00.25.08 also appears to have some detrimental effects on some devices after some usage. And it has a lingering effects too. Try use Radio 07 if you are in Europe or Radio 05 if you ar in Asia...
Having said all these, I must state that these are purely my observations and you really need to try it out for yourselves to know whether it works for you. I have given the same advice to about 5 users experiencing these problems and it had worked for them so far.
Swiftblade said:
Hi mikkelnl... from what you described, it seems to be a typical problems with the SPL you are using. Depending on which SPL that the original ROM that came with your device, you can resolve by installing the respective 1.37 OliNex HardSPL Unsigned or the 1.93 OliNex HardSPL Unsigned by cmonex.
Try to get it from the same thread that you got the 1.40 OliNex HardSPL-Developers Edition. There is also some explanation on the problems that you are experiencing.
One more thing, Radio 1.00.25.08 also appears to have some detrimental effects on some devices after some usage. And it has a lingering effects too. Try use Radio 07 if you are in Europe or Radio 05 if you ar in Asia...
Having said all these, I must state that these are purely my observations and you really need to try it out for yourselves to know whether it works for you. I have given the same advice to about 5 users experiencing these problems and it had worked for them so far.
Click to expand...
Click to collapse
Hi Swiftblade!
Thanks for the reply. I've read about those newer SPL versions, but I didn't think it was the reason for my problems, since I have one of the first Diamonds (can't remember the spl version ). And; the thread mentions "fuzziness issues on some newer diamonds", my screen is not 'fuzzy', it simply is scrambled and the device completely hangs. So I didn't figure that would be the problem
Anyways; I am a bit reluctant to install a new SPL, never did that before...
mikkelnl said:
Hi Swiftblade!
Thanks for the reply. I've read about those newer SPL versions, but I didn't think it was the reason for my problems, since I have one of the first Diamonds (can't remember the spl version ). And; the thread mentions "fuzziness issues on some newer diamonds", my screen is not 'fuzzy', it simply is scrambled and the device completely hangs. So I didn't figure that would be the problem
Anyways; I am a bit reluctant to install a new SPL, never did that before...
Click to expand...
Click to collapse
Hi mikkelnl.. It's really worth a try. the description on the thread is of course vague. It is actually to deal with some discrepancy issues between SPL and the device's specification.
Doing a HardSPL will not affect your rom but it will hard reset it so you get a fresh clean rom. Do perform a backup before you do a HardSPL though. My best bet is 1.37 OliNex HardSPL Unsigned.. Cheerz
Edited: If this HardSPLs can't solve your problems then it might be a hardware issue that you are facing...
Well, I just installed 1.37 olinex, let's see if this helps
Thanks for the input Swiftblade! Now I'll just have to re-setup your 7.0 rom
mikkelnl said:
Well, I just installed 1.37 olinex, let's see if this helps
Thanks for the input Swiftblade! Now I'll just have to re-setup your 7.0 rom
Click to expand...
Click to collapse
Hope it works out for you bro... Good Luck!

my diamond is out of control

hi,
i have been experiencing a problem with my diamond for the last couple of weeks. i lose the alignment on my screen and when i start moving the touch flu taps the icons are shaking and not moving as i want!
is it something related to ROM, SPL or radio?
i keep formating, changing cooked Roms, lastely i gone back to the offecial rom but the problem still comes. It is always the case that when the device starts after formating i have to keep alignming the screen up to 10 times or more!
can anyone help please?
join the club....
http://forum.xda-developers.com/showthread.php?p=3892993
People all you tryings are ilusions, this kind of problem nothing can't resolve, with trying of software solutions, cause i tried everythings possible to resolve this problem!
I tried, all versions of SPL, signed-olinex, unisgned - olinex, stock SPL, this means all versions from 1.34 to 1.93, and again, and again same problem...
Phone works 3-4 hours ok, and again same... I think this problem occured when i installed IGO8 app for GPS, and start to use this app, i felt phone start to warm up, and often when i used IGO8, it was very hot, something like overheating of computer's component, MB, CPU, etc..
After 1 month, it started to not respoding touch screen, and i couldn't fast align screen!
Then i tried manny cooked roms, one of the best, Cloudy1.0, Shaks4.2, Duty, etc.. And nothing, i go back to 1.93 , 2.03 STOCK roms, and notging ...
And at the end, i tried with formating rom, with MTTY tool, it passed ok, but nothing, after formating , again, and again same...
I spoke with people from HTC support, but they couldn't tell me nothing new, what i didn't try!
This is i think more hardware problem, touch screen problem when phone start to warm up, touch screen has a problem, same is when i go out, and expose phone directly to the sunny, touch screen start to freeze!
And i decide to send phone in service for repairing, cause phone has 2 years warranty, i hope they will give me new one, like some people wrote here...
I hope they will not discover , that i used HSPL olinex, and my problem is i didn't remember what was stock rom on my phone, when is buyed, stock rom was 1.93, but SPL i forgot, today i added 1.37 STOCK SPL, and today i send my phone to service! And now i have to wait...
Greetings and good luck all you!
I'm sorry for my bad english, cause it's not my native language...
p.s.
You can try with MTTY tool, to resolve that problem ,before sending phone, you can find MTTY tool, in thread "strange problem" just write "strange problem" in search, and follow instructions from that thread, some people succeeded to resolve that problem, with that tool, then you can try... I had not lucky... Before trying that, go back to STOCK rom , and STOCK SPL 1.93...

Categories

Resources