hello, i have a orange branded htc elf p3450 (touch) uk gsm. i would like to ask a few questions and any help would be apprieciated.
first off im happy with the way it is execpt a few things
1) the annoying orange splash screens, i know the shutdown screen can be removed in registry, but the startupscreen is in rom, is there any way i can change this back to the default htc one ?
2) iv been looking at the blue elves v5 rom and been thinking about just using that, will it replace that damn annoying startup screen and look standard and also noticed standby is not included in this rom, i use that all the time so if i went this route is there any way i could put it back in.
would prefer option 1, but option 2 would give me more avalible ram, the low memory messages annoy the hell out of me (have already changed pagepool to 4mb)
any help is apprieciated
thanks in advance.
done it, backed up my existing rom just in case, flashed blue elves v5, second bootscreen changed. flashed Hardspl to keep the chances of messing up the rom beyond repair to a minimum, got a random rom from dopodasia, flashed it knowing it would be wrong language but might have bootscreen it did , now the first thing i see is 'smart mobility' than the htc logo than windows mobile splash. flashed back to blue elves v5, boot screens stayed the same, all good. tweaked it around a bit, and now im happy
Related
So I've tried pretty much every rom I can find out here and here is my setup. This is the most stable, most closest to RTM, and best battery life. I've had almost no issues with my setup and would like to share with everyone.
First
Download and flash MDA rom from Tmobiles website. 2.26
Second Download Faria "final" without kitchen. Install that rom. (this gives you HTC logo on startup.
Next Install mUm's, not to smart fixed. It's on the wiki.. This gives you RTM splash boot screens
Next download Windows Mobile Pro 3.0 fron ANTC it's in the main forum.. Flash it
Now you are done, you have RTM spash screens, HTC screen, a GOOD solid base to work off of and this is the least buggy version I have found yet. You need to do the flashing in the exact order to get all RTM flash screens.
Lastly...
I use IPL SPL 3.08 and Tmobile UK radio 2.19.11
I also use MS voice command 1.6
Hope this helps some of you out, I am really happy with this setup and haven't felt the need to re-flash my phone in a couple of days.. "usualy it's hours
Some links are on my "signature" the rest you must fish for!
I started playing with this tonight..
I still use faria first so I can get the factory HTC logo but I completely cut out mUm..
I'm trying from tmobile base, -> faria -> pandora
I noticed a lot of you all have looked at this today, thanks I hope you tried it and feel free to add your idears
sledwrecker said:
I started playing with this tonight..
I still use faria first so I can get the factory HTC logo but I completely cut out mUm..
I'm trying from tmobile base, -> faria -> pandora
I noticed a lot of you all have looked at this today, thanks I hope you tried it and feel free to add your idears
Click to expand...
Click to collapse
If you give Pandora a try, I'd suggest the 02.x0. I'm on it now, and it looks really good. It's using compressed files. 01.x0 had the "wifi" fix, which cost it battery life, and was pre-compression. I won't wonder why you're up at 1:30, cause I am too. Must be a Seattle thing...
Hi,
Have searched and looked and cannt see any real reasons for sticking the HTC cab on.
But have I missed something please and would benefit from changing to the HTC one?
Oh, its a whole lot smaller than my Universal!
Thanks,
Simon.
Do you mean ROM, rather than CAB?
If so, there seems to be very little difference between them in overall performance. I would disable the orange homescreen plug in though.
at this time there is a issue with the kaiser being SIM locked out of the orange network when flashing the HTC shipped rom or any other cooked rom so I wouldnt do it. Search and you will see what I'm talking about
As the title says, this is a WinMo 6.1 hybrid, with Vodafone ROM + Radio (both newest), OEM section from the HTC latest build and .net CF 3.5. The pagepool has been set to 32MB using the PagePool Changer on the .nb during cooking, but the situation around Kaiser PPs seems somewhat unclear.
This ROM is 'in a HTC style' (due to the HTC OEM) but with the good bits from the Vodafone ROM.
NO OTHER CHANGES!
Aside from .net changes, the contents of this ROM are completely stock. It has the modaco man on the splash screen, cos I hang out there and I like the graphics
DOWNLOAD:
ftp://xda:[email protected]/Upload/TLR/TLR-Kaiser-Hybrid-1.08.02.08.zip
Note for moderators: the link above is NOT the XDA Developers FTP site.
NOTE: You will need to flash HardSPL on your device first to flash this ROM!
Balls, can a moderator change the thread title from 1.08.02.04 to 1.08.02.08?
modaco splash removal
Tlr nice rom. i flashed it, but i really have a problem with that modaco splash screen. If you could just give me a hint for the easiest way to get rid of it I would really appreciate. The rest is all good. thanx in advance!
I too like the spash screen.. definitely as good as and OEM screen!
Going to flash the .08 now.. runiing .04 for two days, no probs except keyboard, which I fixed by reading the att tilt specific faq.
How is battery life ?
So far battery life seems good to me. It basically lasts a day with pretty consistent use, and some wifi.
Hi Guys, took the plunge and installed the HTC wm6.1 update on my 3month old UK Orange Branded Tytn.
TBH it was ok before - but i just wanted to see if it would be any quicker and fancied the threaded SMS as i used it on my n95 and it was easier to keep track of conversations. First problem was it would not run HardSPL and i got the white screen problem that i cured by following these instructions..
http://forum.xda-developers.com/showthread.php?t=354061
I have been now able to install the new rom okay, BUT it is as slow as hell (I thought the orange firmware was bad lol) seems to be ok then it just jams - sometimes for a good few seconds. bit of a pain. The keyboard Touch screen and any buttons dont do anything, sometimes for up to 30s, then it all catches up with all the buttons iv pressed during the freeze ect being actioned, a nightmare.
I tried one of Duttys ROMS (Must say im very impressed with his work!!!) BUT Same problem as before the thing just freezes for a few seconds (doesnt crash - just freezes) its a pain trying to browse or send tst messages.
Have I done anything wrong in the upgrade, or is it "Orange care time"?
did u remember to hard reset ur device after flash?
Thanks for the reply,
I just ran the JumpSPL program then ran the rom exe file(S) The thing is fine, just as slow as hell - having to resort to my old n95 now ;-(
I didnt do a hard reset after i updated the rom, just activsync`d it and set it up
do a hard reset it should improve your rom spead. Some times when you flash a new rom and don't do hard reset files of the old rom are still on device and cause conflicts with the new rom that is why a hard reset is almost highly recommended after a rom flash.
Don't forget to back up your contacts,messages,documents on device as a hard reset will erase everything except spl, os, rom, radio.
good luck
ill give that a try, thanks
Can you let us know what ROM's you're running.
I'm on Orange (UK) and mine is much faster than the stock ROM now.
Do you have any other software running on it ? SPB Mobile Shell sometimes slows things down ...
Read my signature for the ROM's I'm using on the Orange Tytn II.
hi,
Where did you download the ROM from? The one from the HTC website only gives me the option to download Norwegian version....any ideas?
Thanks
EDIT I've jst downloaded RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship - Is that the ROM you used?
Just flashed my HTC TyTN II Orange, with the above ROM & everything is O.K at the moment, woo. lol
Iv tried the "Genuine"
RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship
and Duttys
Duttys_Ruu_Signed_5.2.19585_1_65_16_25_test
Tried doing a hard reset as suggested and im not running any other apps. Iv reflashed a couple of times today and both are still causing the same symptoms - touch screen suddenly not as responsive then the tytn freezes completely for a few secs, then its fine for a while.
speedbird said:
Iv tried the "Genuine"
RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship
and Duttys
Duttys_Ruu_Signed_5.2.19585_1_65_16_25_test
.
Click to expand...
Click to collapse
I think the clue is in the title "...test'.
Dutty dropped off the scene for a couple of weeks due to work pressure and came back to play with the new 'official' ROM's.
The test ROM, is just that !! it's for testing. I would never suggest anyone with a posting score of less than 100 attempt to put TEST ROM's on their Tytn II ... There's already been some issues with Radio's that won't allow downgrading etc.
The test ROM has reports showing issues of a similar nature to those you mention.
I would suggest you re-install a more 'mainstream' ROM at this stage and wait for the test ROM to become stable.
I've had no problems with Dutty's Official WM6.1 5.2.19209 Rom or Polaris Radio 1.64.08.21 Radio, although I may upgrade to the 1.65.16.25 Radio in the next couple of days.
As a rule of thumb, problematic radios exhibit poor signal strength, sound issues and problems with GPS. The issues you mention are often associated with the OS rom, in this case the Duttys_Ruu_Signed_5.2.19585_1_65_16_25_test rom.
Even if changing just the OS Rom, it might be worth downloading, and installing them seperately again - Remebering to Hard Reset after each install.
Backup all your contacts etc. to your SD card with PIM Backup 2.8 before you do anything and remember to remove the SD card before you begin.
[*NOTE: I've based my posting number on a direct relatinship with 1. How long they've been active on the forums and 2. That this length of time would equate to having read most of the posts and be able to navigate round the forum - it is not meant to be an insult to new members I'm not a 100 poster and wouldn't try a test rom either *]
I've flashed my Orange Tytn2 and a friends without issue using the 'official' 6.1 rom that was posted on Modaco.
I didn't hard reset afterwards and both units are working fine. Maybe try flashing your device on a different pc?
As far as i was aware the title of this posting was "Orange Kaiser Upgrade of but REALLY Slow Now ;-( "
tbh i dont think you really got the gist of my post, i WAS saying i had problems with the STOCK ROM, and that i had also tried duttys rom (I was very impressed with it), If you read my posting i think you will realise i simply commented it was showing they SAME symptoms on my phone. My problem was NOT with duttys rom (btw i DID notice the word test in its name before i loaded it, but thanks for pointing that out), I was having problems with the flashing process in general.
Thanks anyway.
ajs007 said:
I think the clue is in the title "...test'.
"Dutty dropped off the scene for a couple of weeks due to work pressure and came back to play with the new 'official' ROM's.
The test ROM, is just that !! it's for testing. I would never suggest anyone with a posting score of less than 100 attempt to put TEST ROM's on their Tytn II ... There's already been some issues with Radio's that won't allow downgrading etc.
The test ROM has reports showing issues of a similar nature to those you mention.
I would suggest you re-install a more 'mainstream' ROM at this stage and wait for the test ROM to become stable.
I've had no problems with Dutty's Official WM6.1 5.2.19209 Rom or Polaris Radio 1.64.08.21 Radio, although I may upgrade to the 1.65.16.25 Radio in the next couple of days.
As a rule of thumb, problematic radios exhibit poor signal strength, sound issues and problems with GPS. The issues you mention are often associated with the OS rom, in this case the Duttys_Ruu_Signed_5.2.19585_1_65_16_25_test rom.
Even if changing just the OS Rom, it might be worth downloading, and installing them seperately again - Remebering to Hard Reset after each install.
Backup all your contacts etc. to your SD card with PIM Backup 2.8 before you do anything and remember to remove the SD card before you begin.
[*NOTE: I've based my posting number on a direct relatinship with 1. How long they've been active on the forums and 2. That this length of time would equate to having read most of the posts and be able to navigate round the forum - it is not meant to be an insult to new members I'm not a 100 poster and wouldn't try a test rom either *]
Click to expand...
Click to collapse
speedbird said:
As far as i was aware the title of this posting was "Orange Kaiser Upgrade of but REALLY Slow Now ;-( "
tbh i dont think you really got the gist of my post, i WAS saying i had problems with the STOCK ROM......... I was having problems with the flashing process in general.
Thanks anyway.
Click to expand...
Click to collapse
What are the symptoms ?
Have you added any other Software (i.e. programs or cabs) ?
Has the device got slower over time ?
What challenges are you having with problems with the flashing process ?
Are you using a screen protector as this reduces the touch sensitivity ?
Im not running any other programs or screen protector, the thing is fine for a minute or so then starts to slow down and reaches the point where nothing will happen and it locks up (for what feels like ages) prob about 30-43secs but its enough to cause grief if ur trying to send a txt with it or browse. Then it comes back to life and is fine again for a while, also getting a few error msgs saying that CProg has problems - (on all the 6.1 roms iv tried).
i have tried several roms (inc stock roms) and although i have read postings in modoco about the new 6.1 rom making the machine unresponsive this takes the biscuit, i thought my old n95 was bugridden when i first got it ;-(
There's a thread over at http://forum.xda-developers.com/showthread.php?t=393062 that tells of a similar tale, it might be worth a read.
Some of the issues are with the ROM and poor touch sensitivity making the unit appear to slow down.
If you have nothing to lose, overwrite your ROM's with the ones in my signature, they're on the forum and I know they're quick, and I'm on Orange, so its a good benchmark.
If you are still experiencing similar problems, then I would suggest you update the phone with the original stuff and tell Orange Care that they have a duff handset and you want it replacing.
i will give it a try, thanks ;-)
I'm using Miri's 6.5 V17 ROM for my HDC HD2. This issue started out of the blue. I've tried multiple different Android releases, but nothing is different. After a few hours of the Android being booted within WinMo, I can't get the screen to turn on. I usually get a backlight, but nothing displays. Is this a know issue? Should I use a different ROM? The reason I picked this ROM, is because it fixes the known issue with the robotic call quality.
agentfazexx said:
I'm using Miri's 6.5 V17 ROM for my HDC HD2. This issue started out of the blue. I've tried multiple different Android releases, but nothing is different. After a few hours of the Android being booted within WinMo, I can't get the screen to turn on. I usually get a backlight, but nothing displays. Is this a know issue? Should I use a different ROM? The reason I picked this ROM, is because it fixes the known issue with the robotic call quality.
Click to expand...
Click to collapse
Have you try a hard reset?, don't forget to remove your sd card.
Just did that now. I'll let you know how it went.
You can also try with another ROM
I´m using latest energy and do not have any robot voice and all working ok
Energy ROM? Link? Will this ROM install with any SPL? I think I used HardSPL.
Also, it was fine but just did the same thing again. I'm beginning to think Android was not meant to run on this phone.
Tried Energy. Still does the same thing on a regular basis. Is there a specific Android build to run on the HTC HD2?
Does anybody have a fix for this?
Bump...again.
Tried the newest Froyo release (August 18th) and it does the SAME thing off and on. Why can no one answer this question?
Hard reset seems to be the only fix for this, and even that only works for a day or two. Is this a known issue? I'm not using LauncherPro...
After almost 300 views, no one can help me? What kind of crap is that?
Bump......
Bump.......