Related
Been following this site for weeks and it is getting more popular eacha nd every time someone buys a Diamond phone, so keep up the good work.
I have finally decided to see what I can do with mine by upgrading the ROM and I would appriciate any advice you guys can give me as i am a totally newbie.
Here are the details:
It is on T-Mobile (UK)
Version -
1.37.110.3 WWE
06/20/08
1.00.25.03
Thanks
Hello there!
Not sure what you mean by upgrading the rom? Guess you mean applying a cooked rom?
A cooked rom is one thats been customised and is flashed over the top of your current rom, in your case probably a "stock" or out of the box/factory rom.
First thing to do in your case would be to upgrade the Radio. You may well need to run the HardSPL (I needed developer edition) and then apply the radio upgrade.
From then on, its up to you which cooked rom you run as they all have advantages and disadvantages. For example, im running the Diamond TLR rom as I don't like touchflo (i think its a gimmick that slows things down - drasticaly). Using this rom i'm able to uninstall touchflo and free up significant memory. This suits me down to the ground but not those who want to use touchflo!
Take a look at the wiki (mostly) and the Rom development sub-section of this Diamond section of the forums. As long as you follow the Wiki instructions on HardSPL and then use a rom specifically for a touch diamond, you should be fine.
Be very carefull though and DOUBLE check everything, one wrong flash program and you can destroy your phone.
Have fun!
p.s. Many people think that the factory 1.37.xx roms are the most stable, even more than the later versions. I'm running a TLR based 1.37something and I am very happy with it and never have to reboot my phone.
Got it....Its all here
Hi Lats... I've tried a variety of roms on my Compact IV and I have to say, me and my colleagues at work find that Swiftblades roms are pretty much as good as they come. He's now released version 5.0 and if you're still on the original T-mobile rom, then you'll notice one hell of a difference and improvement in speed and usability.
Go for it and don't worry if your concerned about warranty, there is a stock T-mobile rom floating around on the forum and instructions on how to return your Compact IV back to it's original state.
If you find the whole rom thing confusing, then take a look at this site:- www.modmydiamond.info It'll pretty much tell you everything.
Basically though, you'll find there are 3 phases to upgrading
1) HardSPL - In laymans terms, this pretty much opens the phone up for flashing roms. Most people seem to go for and recommend using Hard-SPL 1.40 Olinex Developers Edition-Unsigned. There are consequences to using an unsigned version, it means you could in theory download and install a dodgy untested Rom, but it's up to you to go for roms on the thread from reputable guys where you can see lots of other people have installed their tried and tested roms.
Once you've done this, you'll not need to do this again.
2) The Radio - This deals with the comms side of the phone, ie phone signal strength etc etc. It's pretty much been agreed by most people that v1.00.25.05 appears to be the best of the bunch.
3) Lastly choose a rom, there are half a dozen really good roms out there and many of them are down to personal choice. Many of them are customised too much for my liking. I chose Swifts as he pretty much keeps his clean and looking like a stock rom.
You'll only have to do the Hard-SPL once and probably the radio once, unless a better radio arrives. So once you've done all this, you can keep trying different roms without the need to do the Hard-SPL and radio all over again.
Hope this clarifies things a bit for you.
Good luck and have fun!
Thanks ever so much guys. I already feel alot more confident about this. Just one question... guide suggests the following:-
Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time
Where is the camera button and it sounds as I need 3 hands to do this!
They're refering to the main round button below your screen in the middle of the 4 buttons, and yes you need 3 hands, but you can just about do it with 2
Let us know which ROM you upgrade to - I'm on the same ROM and radio as you are. Bit nervous about flashing the rom as my last phone (Vario II/Hermes) had to go back a month after I had it due to the screen alignment issues. After the warranty expired, I was flashing daily (lol) and yes, they do make a big difference.
I've got a copy of the UK Tmobile rom from this site, but cant remember the page now or what i typed in to get it... will try again later. It's called "RUU_Victor_TMO_UK_1.37.110.3_Radio_Signed_Diamond_52.26a.25.09_1.00.25.03_Ship"
Lats said:
Thanks ever so much guys. I already feel alot more confident about this. Just one question... guide suggests the following:-
Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time
Where is the camera button and it sounds as I need 3 hands to do this!
Click to expand...
Click to collapse
That is for last resort methods only...
Ensure you are connnected via activesync when doing any flashing, remembering to hard reset again after every flash,
Yeah, most definetly I will let you know but I think it will be over the weekend now. I had a quick attempt to get bootloader going, but it don't look easy. Phone just resets everytime and just reboots back to normal.
If anyone has any tips on which buttons I need to press first or if there is any easier way of doing this, I'm listening.
Lats said:
Yeah, most definetly I will let you know but I think it will be over the weekend now. I had a quick attempt to get bootloader going, but it don't look easy. Phone just resets everytime and just reboots back to normal.
If anyone has any tips on which buttons I need to press first or if there is any easier way of doing this, I'm listening.
Click to expand...
Click to collapse
If you want to flash any ROM - you dont need to manually enter boot loader to do so...
As I mentioned before.
just make sure you have active-sync running and working and the battery id over %50 charged.
I'll be doing this tonight
The Tmobile stock rom can be found here
http://forum.xda-developers.com/showthread.php?t=406327
OK, I've upgraded my Diamond from 1.37 to 1.93. I then used SKTools backup to restore everything from a backup before the upgrade. And now I have a few strange things. This is just what I've noted immediately, I haven't even tried anything else yet....
On the Home screen, after a soft reset or moving from any other TF3D screen to home, the clock runs from the current time to 12:59AM, the Home screen also shows my connection to T-Mobile, which is strange as I'm with O2, which is what it shows in the Phone screen.
The date is also wrong, showing Jan 1 2008. If you go into the date/time screen the date & time are correct.
Oh, and the Soft menus are a bit screwed as well...
I will try a hard reset without a restore and see what happens...
I think you should re-do your upgrade to 1.93.
I had similar problems with HTC's back-up software... after upgrade to 1.93 and running the back-up program... it showed that i still had 1.37 ROM!
I don't back-up my data anymore, I just use Outlook for my contacts.
glumetu said:
I think you should re-do your upgrade to 1.93.
I had similar problems with HTC's back-up software... after upgrade to 1.93 and running the back-up program... it showed that i still had 1.37 ROM!
I don't back-up my data anymore, I just use Outlook for my contacts.
Click to expand...
Click to collapse
always hard reset when flashing a new rom
and restoring backup between two different roms is nto recommended at all. at that might be the cause of your problem
use pim backup to restore contacts, calendar, and inbox. backing up settings not recommended.
regards
karim099 said:
always hard reset when flashing a new rom
and restoring backup between two different roms is nto recommended at all. at that might be the cause of your problem
use pim backup to restore contacts, calendar, and inbox. backing up settings not recommended.
regards
Click to expand...
Click to collapse
i tried using SPB back up and Sprite and in the end it was easier to do fresh CAB installs on the new flashed ROM. Less hassles trying to troubleshoot the problems.
Definitely, dont back up the systems data with a different ROM, you will run into trouble!
Anyone out there carried out a fully successful restore after a ROM upgrade?
If so, could you please give details, i.e. what ROM versions were involved, and which backup software was used.
Really itching to go to from .37 to .93, but really can't face all the re-prog. I did one full restore on the phone with Sprite, when I screwed up some settings beyond what I could be bothered to fix, and it worked flawlessly, so I suppose I could suck it and see with a .93, and if it's rubbish, revert to .37, but I'd still be interested in any feedback first.
karim099 said:
always hard reset when flashing a new rom
and restoring backup between two different roms is nto recommended at all. at that might be the cause of your problem
use pim backup to restore contacts, calendar, and inbox. backing up settings not recommended.
regards
Click to expand...
Click to collapse
you are soooo right! by restoring the backup from a previous ROM you brought in system setting and registries that no longer apply to the new ROM.
if restoring from the old system and register why bother flushing a new ROM?
i think that in order to correct the present situation all you have to do is a hard reset.
and yes, you can restore PIM.
KukurikU said:
you are soooo right! by restoring the backup from a previous ROM you brought in system setting and registries that no longer apply to the new ROM.
if restoring from the old system and register why bother flushing a new ROM?
i think that in order to correct the present situation all you have to do is a hard reset.
and yes, you can restore PIM.
Click to expand...
Click to collapse
i cant beleive u agreed on every idea i said neighbor
So the consensus of opinion is to clean install everything....
To avoid the hassle of continually updating ROMs, and the subsequent 'F' factor of re-progging every time, I'll probably wait a few months for the run of updates to fizzle out and we'll hopefully have something of a 'definitive' ROM.
Do any of the old hands have any thoughts or feelings as to how long it usually takes before ROMs for new devices become close to 'definitive'?
studz said:
So the consensus of opinion is to clean install everything....
To avoid the hassle of continually updating ROMs, and the subsequent 'F' factor of re-progging every time, I'll probably wait a few months for the run of updates to fizzle out and we'll hopefully have something of a 'definitive' ROM.
Do any of the old hands have any thoughts or feelings as to how long it usually takes before ROMs for new devices become close to 'definitive'?
Click to expand...
Click to collapse
i think that rom developement will never stop.. it will slow down when the next gen device arrives... which was the case for the touch, its been few months only when the rom developement slowed down ( but still roms are being released)
However, htc barely releases official roms only if there is a big improvement.
an average of 2 to 3 updates for a device.
what will you say for chefs and rom enthusiasts which have their devices flashed for over 50 times till now?
i sometimes encounter that weird soft menus during start up, but they'd go away after the phone had fully booted up...
mcvpjd3 said:
Oh, and the Soft menus are a bit screwed as well...
Click to expand...
Click to collapse
karim099 said:
what will you say for chefs and rom enthusiasts which have their devices flashed for over 50 times till now?
Click to expand...
Click to collapse
I know, perhaps I'm just lazy, but here's me cringing at the thought of doing just one
I think I'll wait a few months for HTC's next official release, and if there isn't one by about November I'll flash the .93
studz said:
I know, perhaps I'm just lazy, but here's me cringing at the thought of doing just one
I think I'll wait a few months for HTC's next official release, and if there isn't one by about November I'll flash the .93
Click to expand...
Click to collapse
.93 is a must. it has a big performance increase.. and battery life improvement
you may want to try one of the coocked roms also u will fall in love with your device
karim099 said:
.93 is a must. it has a big performance increase.. and battery life improvement
you may want to try one of the cooked roms also u will fall in love with your device
Click to expand...
Click to collapse
Fairly enamoured with it now to be honest, but I might be tempted to bite the bullet sooner rather than later. Too busy to go through the hassle right now though... how do you boys find the time??! Thanks for the insight into the advantages of .93
problem is from backup program
back up is for 1.37 rom. and now u want apply it in 1.93 !
If you are going to frequently flash your device you can use SASHIMI, from the development and hacking forum. It is basically an autoinstaller so you can set it up with all your cabs, registry entries, files, start menu etc and after a hard reset you run it and it copies it all across. Works better than restoring a backup from a different rom, and faster and more convenient than doing it all manually. It did take me about 10 hours to set it up with all my registry changes though, but it was a fun rainy day projects. Please post in the main SASHIMI thread if you have questions.
bigruss said:
Please post in the main SASHIMI thread if you have questions.
Click to expand...
Click to collapse
Sounds like that could be the way forward bigruss... I'll look in on the tread and give you all a shout if I need help when the time comes. Thanks for the tip.
karim099 said:
i cant beleive u agreed on every idea i said neighbor
Click to expand...
Click to collapse
believe it! isn't this wonderful? you are right and i agree. flags don't matter here.
studz said:
I know, perhaps I'm just lazy, but here's me cringing at the thought of doing just one
I think I'll wait a few months for HTC's next official release, and if there isn't one by about November I'll flash the .93
Click to expand...
Click to collapse
i think this is going to make yr life a lot easier:
http://forum.xda-developers.com/showthread.php?t=392983
very strange indeed
KukurikU said:
believe it! isn't this wonderful? you are right and i agree. flags don't matter here.
Click to expand...
Click to collapse
hope one day flags wont matter anywhere
SASHIMI seems to be interesting... good find
i will be recieving my new at&t tilt on tues. i have been reading alot about it over the last few days and i have noticed alot of chatter about having a bunch of un-necessary software pre loaded onto the device. i was wondering if anyone had any good ideas on how to optimize mine in the easiest way possible.. this will be my first smartphone running windows mobile so plz forgive me if i dont understand some stuff. thanks in advance for any ideas..
The first thing you should do is read all the wiki's that you can on this site. I came to this site many months ago and through using the wiki's I managed to learn how to flash a new rom (think of it as an altered version of windows mobile), how to change spl's (the equivalent of a computer's BIOS), flashing new radio's (The phone's parameters for call quality, signal acquiring, and gps capability), and now I'm cooking my own rom and hope to have it ready by the end of the month. Search for answers to your questions first so you don't get flamed, but if you need to post, know that these are probably the most knowledgable people around for this and they will go out of their way to help you. HOWEVER, know this, after you become accustomed to flashing your phone, it's a nonstop never ending addiction to reach perfection.
thanks so much, i found the wiki's now and am reading thru them..
Don't get overwhelmed when you try this stuff. Follow the directions and and don't try to do too much at once. Have fun, Welcome to the forum
One quick way to get rid of a lot of the bloat is to do a hard reset of the software ( hold down both soft keys and hit reset button by USB port with stylus, when prompted hit green button. If no prompt to"hit send button" then you did it wrong) then as soon as the customization screen comes on do a soft reset (same as hard reset without holding soft keys.)
This won't do much but keep a lot of ATT specific software from being installed. IT is a start until you are comfortable with flashing.
Also you might need to reset ATT settings for internet if you do this. I am not sure though.
** 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)
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