Related
Hi,
With the help from (maju) both me and my brother in-law has successful upgrade our SX66 to WM5 with the lazy version and would like to know if someone knows how to change the splash screen after the upgrade?
I don't mind the three color bands but something more attractive will be nice because before the upgrade I have installed the BA splash screen from the Standardized project and it didn't mention if that's going to work on the WM5.
If anyone know or if you have a custom splash screen wouldn't mind sharing please post.
Thanks
noyu said:
WM5 ... how to change the splash screen after the upgrade?
I don't mind the three color bands but something more attractive will be nice ...
Click to expand...
Click to collapse
Unfortunately if you want to use WM5, you'll need to live with the colour bars as your first 'splash screen' on the BA. This is because in the WM5 Kernel boot process (in the 'beta' leaked ROM build we're using), there is no support present for a splash screen.
I don't 'boot' my BA often during the week, and when I do, the reboot time is so fast now, I really couldn't care at all.
Thanks for your post!
I have a small issue:
After removal of the battery (change sim / replace battery etc) on first start up there is no radio rom in the bottom of the three color bar and I have to do a soft reset after the boot up then it will show radio rom etc and the phone will be working, otherwise without the soft set the phone will show an indicator "no network"
Is this normal or is there a way to fix it?
Thanks
noyu said:
Thanks for your post!
Click to expand...
Click to collapse
You're welcome ... (from one Canuck to another )
noyu said:
I have a small issue:
After removal of the battery (change sim / replace battery etc) on first start up there is no radio rom in the bottom of the three color bar and I have to do a soft reset after the boot up then it will show radio rom etc and the phone will be working, otherwise without the soft set the phone will show an indicator "no network"
Is this normal or is there a way to fix it?
Click to expand...
Click to collapse
My BA exhibits this exact same issue ... but only sometimes on a "full moon night", when Pluto isn't aligning with Venus nicely.
Basically, this is some kind of a startup issue in the beta ROM boot code we have to use in the BA ROM, by which the Radio ROM is sometimes not ready, and/or not initialized 100% by the time the OS is ready to start. I think that the hardware timeout is too short, but we have no ready way to fix this issue either. This will only happen from a COLD BOOT (i.e. battery dead, device completely off), and not from a reset or warm boot.
The answer as you figured out (and is on the forums here - just search!) is to simply 'reset' if you see "R.None" come up on the display, and on the second boot, everything will always work fine.
"The future is in beta, and we have to live with the bugs."
Hi everyone! Basically the whole problem is, as indicated in the heading, I have to soft-reset my T-Mobile Vario 3 if it's been charging for a long time. The same problem may sometimes occur when the handset is used as a modem for my laptop. A typical sign is when some icons on the taskbar (clock,start menu,etc) turn into strange green rectangles.
It let me down a few times with the alarm plus they couldn't get in touch with me from work I've searched through the forum and didn't find anything relevant. Will be grateful for any input.
Are you using the Batti battery indicator bar? I had a similar thing happen to my Tilt when using that program, had to uninstall it to make the freeze and glitched icons stop.
You're right! I've got Batti installed. I'll try uninstalling it. Thanks mate!
Okay, I've searched and can't find this problem but hopefully somebody may have some ideas.
Quite frequently, I lose the top line of my display (the one with the start button and the system status icons). Everything else works but that line just disappears.
If I then lock the device it comes back. When I unlock it, it sometimes stays but sometimes disappears again once it's unlocked and I then have to turn my phone off and back on again.
I have a standard Orange UK phone, standard ROM and I've used some of the performance tweaks listed here. I've also disabled Touchflo and am using spb diary as my home page.
Anybody any ideas because this is driving me mad?
I had the same, but only when TF3D was deactivated. Since I use it again, it doesn't happen anymore...
It happens on my Orange diamond as well - stock 1.37 rom with TF3D enabled.
It seems to happen once every 4-5 days, and doesn't really have a pattern. Sometimes it's switching between Today and Second Today, sometimes it's rotating, sometimes it's unlocking etc..
flash a new ROM
Hello there.
Well i just recommend you to flash a new cooked ROM. I havent seen this behavior with a cooked ROM.
Best regards.
Well, at least it isn't just me but does anybody have any idea what causes the problem and how it can be solved.
Could it be something to do with glyph memory?
I used to see this sometimes on the orange rom. Since flashing a cooked rom makes the device twice as fast - and removes that problem - I would just flash it.
unwired4 said:
I used to see this sometimes on the orange rom. Since flashing a cooked rom makes the device twice as fast - and removes that problem - I would just flash it.
Click to expand...
Click to collapse
I know it's the wrong forum to say this but I'm just a bit scared to flash it because I've never done it before.
I'm worried about either a) bricking it or b) losing some setting that Orange put in to connect to their network (voice, data, voice mail etc).
Hi
I've had a similar Problem!
It seems to happen when I take the phone out of sleep cos I've got a text and its locked (I've set it for 30min).
I press the power button but the screen only half lights and the top line doesn't display. It sometimes says 'password' in the top left but does nothing if I press it.
I can slide along the bottom line but it doesn't work properly.
Interestingly I also have a Orange Diamond 1.37 ROM (which I've unlocked).
I'm gonna flash with HTC's ROM from there site and I'll let everyone know if the problem persists.
Wish me luck
TheFlash007 said:
Hi
I've had a similar Problem!
It seems to happen when I take the phone out of sleep cos I've got a text and its locked (I've set it for 30min).
I press the power button but the screen only half lights and the top line doesn't display. It sometimes says 'password' in the top left but does nothing if I press it.
I can slide along the bottom line but it doesn't work properly.
Interestingly I also have a Orange Diamond 1.37 ROM (which I've unlocked).
I'm gonna flash with HTC's ROM from there site and I'll let everyone know if the problem persists.
Wish me luck
Click to expand...
Click to collapse
And what happened?
Hi
Sorry for the delay. I tried the HTC site ROM but it just gave me a message saying 'Sorry, this software download is not suitable for your device'.
So it looks like i'm stuck cos its still doing it about once a day just have to switch of and on again.
TheFlash007 said:
Hi
Sorry for the delay. I tried the HTC site ROM but it just gave me a message saying 'Sorry, this software download is not suitable for your device'.
So it looks like i'm stuck cos its still doing it about once a day just have to switch of and on again.
Click to expand...
Click to collapse
Okay. I still have the problem and am very, very tempted to try flashing a new ROM (and Radio). But I just can't quite work up the courage to do it since I've never done it before and it's the fear of the unknown.
dastewart said:
Well, at least it isn't just me but does anybody have any idea what causes the problem and how it can be solved.
Could it be something to do with glyph memory?
Click to expand...
Click to collapse
This happens to me too. I have a T-Mobile Compact IV.
I've found that using FreeUP RAM (part of SKTools) not only releases memory, but also fixes this problem (until the next time it happens, which admittedly is not often).
Just wanted to say that I've upgraded my Orange ROM to the new 1.93 and I haven't had this problem....yet.
2 days without problems so I thought it may be safe to post.
IVe also had this on 1.37.x.x on my mda cmpct IV. Like everyone on here Im considering flashing but Im waiting for t-mobile to release an update (they keep telling me the will, presummably the 1.93.x.x) so that if I then brick the puppy - I can blame it on there rom upgrade.
I want this phone to be better, I know it can be with a ROM change...but I dont want to brick it and for once in my life will have some patience to wait.
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Edit: confirmed solution method described in post# 10 http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10 . Thank you agent 47 big time for the tool you provided!
Ibster said:
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Click to expand...
Click to collapse
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
MCbrian said:
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
Click to expand...
Click to collapse
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also experience it on my Tilt 2 AT&T unlocked, so i reverted back to Sense 2.1 Euro 1.86.401.0. any solution there, i bought mine from Negrielectronics USA.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also exprence it on my Tilt 2. is there any help out there
It's because chiefs have updated their XIP. Ask them to cook a rom for you with the old XIP from stock HTC WM6.5 Sense 2.1 rom.
Ach, that's just my theory based on my experience. I might be wrong, so keep that in mind.
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Same here on the SMS black screen
ctbear said:
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Click to expand...
Click to collapse
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
Yes....interesting that I've never had this issue on Energy's...my guess is he doesn't cook in the latest HTC SMS client which can be unstable at times
Are you talking about Elcondor's GTX theme? Yes that is a very awesome theme
I couldn't wait until 201x version comes out so I made my own Not as good as GTX but I'm half satisfied now
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
like i mentioned in the the post#1 I had these problems with almost all recent (last two weeks) custom ROM releases, ROMs of different chefs. Because others or the majority of people don't have any problems with that I thought the reason must be hardware issues. yesterday I saw this thread http://forum.xda-developers.com/showthread.php?t=649191 opened by agent_47 where he provides a modified tool:
agent_47 said:
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
Well I used it and have flashed to Sergio's Leo Cell Evo 6 and I can confirm that I haven't had any "sleep of death" issues, well still haven't and hope I won't have this "SOD" issue anymore. And when I tried this same ROM before I wasn't even able to make a proper configuration and set up the phone because the phone always froze or as soon the screen went off I wasn't able to activate it back without soft reset.
So maybe this is a solution and could help others who also are having this issue of "sleep of death".
Please if you try the tool from the mentioned agent_47's thread, let know us here because it will be very useful for the rest of the users to finally figure out "the dark side" of their phone and fix it.
Cheers, Ibster
Solution
I had this just recently. Funny side was that I installed an official new ROM from HTC which I just updated. Somehow the phone just didn't want to turn on and show the screen. So just like you guys said, hard-reset did the thing but just when the screen went off, same thing happened.
So what I did was wipe/clean or any other name. Practically did the installation of the rom again. Now, the device works normally and without any problems.
Maybe this happens because some old files of older ROMS sayed on the device itself and started making problems. Anyways, check this thread too, maybe it will explain something more: http://forum.xda-developers.com/showthread.php?t=649191
Or, final explanation. Our Rhodiums have soul inside their little chips and they just simply fu.k with us They tell us they're too tired of so many ROM changes.
I have also had this problem with my two latest official swedish roms (manilla 2.1 and 2.5) cant remember if I had it when I used 6.1. Now I use a cooked rom and still have the issue several times a week. The only thing I had done with my Rhodium before using cooked Rom was flashing hard spl for future use. If its not an inbuilt hardware/software problem from the beginning the only thing I can point at in my case is hard spl?
Originally Posted by agent_47
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
back with my kaiser you always had to flash back to stock before going to a new ROM no matter what, for just this very reason...
could flashing back to stock be a 'best practice' that we as users should start doing to help with this issue?
I - have had some xperience with the issue in a few ROMS. Im a loyal flasher of Agent 47s masterpieces. And a month or so ago he had like 2 or 3 builds that had this issue. From what I remember he said that he thought it had to do with some sys evrybody was using to cook roms. and after her came out with this diagnosis and "fixed"(i dont know the technical part of what was fixed) this problem it has never happened since. But a good thing I would say to try is in Agents thread about 4 or so pages from the last page(maybe more or less) but close to the last page he posted a .zip file for this mitty fix. and you essentially flash this zip just like a rom then reflash which ever rom you had or a new one and ta da. Ive also heard of people reflashing a stock rom with results from doing so but from what Agent said is flashing a stock rom then back technicaly "shouldnt" do anything and to definately use mitty. But one of the other frequent valkyrie users that I chat with all the time Mcbrian who posted here on the first page has used the stock rom and did have whatever issue he had cured dont remember what that was tho.
UPDATE- Oh I guess that Agent has a thread for Tool29 so you dont have to search through his thread to find it.
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
Great! I'm glad to hear your confirmation. I now on my side haven't had a sleep of death for three days on the ROM (Cell Leo V6) that previously, before I used the agent_47's tool, couldn't even start normally at all or had extremely many "sleeps of death". But I also noticed overall improvements even though the speed slows down but there are barely any freezes and stability is much better.
Cheers, Ibster
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
kienkham said:
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
Click to expand...
Click to collapse
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Ibster said:
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Click to expand...
Click to collapse
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
kienkham said:
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
Click to expand...
Click to collapse
Your steps should be
1. Shutdown tp2..
2. Remove memory card( I also removed sim card).
3. Turn on tp2, connect through the computer through active sync.
4. Run task 29. Let it load flash, whatever it is doing until it actually reboots.
5. At this point, everything should be cleaned, you don't have a rom or radio anymore, so its blank, so you "pull battery out."
6. Put memory card/sim card back in. Flash radio through boot whatever menu. Soft reset it yourself. Pull battery out again.
7. Flash rom this time, and soft reset it again. Now rom should start setting up.
This shouldn't be rocket science.
Everybody knows: the battery in the diamond is little bit to small for the device. sometimes i lost the power faster then i can use the device. yesterday i have filled the battery up to 100% at 10pm. in the morning at 5 am i had only 73% battery. i dont have used the device other night. i think this is not normal. i use HomeScreen++ UI, there i can measure the battery consumption. when the device is in standby, i have seen vor very short time a value for 20ma, but when the device is powered on i see values from 150 - 212ma.
What with your device? can we say, that this is normal or is this a error? whats the normal power consumption in stand by and at running time (no applications in foreground)? Can anyone give some normal value's?
dude that's very weird... are you using a standard ROM? which radio version are you using? how is the cell reception in your area or near your home? do you use GSM or 3G? there are many factors that can accelerate battery consumption...
try another ROM & make sure you have the latest RADIO I have a DAIM100 & use the 1.17.25.09 & after two years of owning it I still use the same battery & get a whole day at least, I also don't really play on my phone during the day but I sync & use GPS when travelling & also have my email on it & make & receive a fair amount of calls & txts so it depends on your particular situation...
i Have now changed my ROM to a earlir version. It uses now a COM5 Build. Before that i use a Com3 Build. As the Radio ROM is use every time the same as you (but with rilphone from 1.09). The Battery consumption is returned to normal. it uses now near 3% in 10 hours, without using the device (over night).
i dont know whats the problem with the newer ROM. The first days with the COM3 Build, the battery consumption was normal. i fear that the problem is comming with some service or program i have installes later, but i dont know what for software. BatLog couldnt help me at this point.
i'm also having the same problem, i need to charge my phone twice a day and when its fully charged from midnight it gets to about 70% by 10am how do i make it last longer and how do i update the ROM or whatever it is that you guys are talking about?
I suggest you to buy a new battery.
I had a 1800mAh from China on eBay at 10€ and i solved the problem.
Before buying it, i just had two batteries, but i had to carry in my poket another battery :\
I think BP E270 is a resolution.
It increase battery juice a little bit (1350mah) and keep your diamond in a sexy shape.
I'm using Don Salari rom (WM 6.5, TF3d 2.1) and have a fully 2 days without charging. Not so good but pretty pleased anyway.
Shaks said:
i'm also having the same problem, i need to charge my phone twice a day and when its fully charged from midnight it gets to about 70% by 10am how do i make it last longer and how do i update the ROM or whatever it is that you guys are talking about?
Click to expand...
Click to collapse
There can be different reasons for abnormal battery consumption. actual i lost around 3-5% in 10 hours, without using the device. if i use it often its more, if i use wifi, hdspa or bluetooth or do i make a game, hear music or such thing, it consumes more. thats in my opinion a normal state for the diamond device.
the most important thing is the radion rom. the radio rom responsibly for the radio things in the device: Phone, hdspa, bluetooth, wifi, gps (not the fm radio). the problem is: not every radio is good for every device. on some devices the version 1.09 is good, on some other the latest 1.17.x
than there is the ROM for the device. you can see it as the operating system. at the moment im using am COM5 build (Windows Mobile 6.5.5, Version 7.00). I have had problem with 7.30, this is a COM3 build. On the Main Site of the ROM you can find intructions to flash this ROM to your device, because its not a official one.
bilbo_b said:
There can be different reasons for abnormal battery consumption. actual i lost around 3-5% in 10 hours, without using the device. if i use it often its more, if i use wifi, hdspa or bluetooth or do i make a game, hear music or such thing, it consumes more. thats in my opinion a normal state for the diamond device.
the most important thing is the radion rom. the radio rom responsibly for the radio things in the device: Phone, hdspa, bluetooth, wifi, gps (not the fm radio). the problem is: not every radio is good for every device. on some devices the version 1.09 is good, on some other the latest 1.17.x
than there is the ROM for the device. you can see it as the operating system. at the moment im using am COM5 build (Windows Mobile 6.5.5, Version 7.00). I have had problem with 7.30, this is a COM3 build. On the Main Site of the ROM you can find intructions to flash this ROM to your device, because its not a official one.
Click to expand...
Click to collapse
erm... my phone is not used at all for 10 hours whilst i am sleeping and i switch my wi-fi and bluetooth off also. sometimes i even put the phone into airplane mode to see if it makes a difference but not much.
about the radio and roms, im still a bit unsure as to how that works i have a htc touch diamond which is wm 6.1 not 6.5... would it be possible to upgrade it to a 6.5 by flashing the rom?
sorry for the million questions lol im just confused as to how it all works
Shaks said:
erm... my phone is not used at all for 10 hours whilst i am sleeping and i switch my wi-fi and bluetooth off also. sometimes i even put the phone into airplane mode to see if it makes a difference but not much.
Click to expand...
Click to collapse
then there is something wrong with your device. if take phone to airplane mode, it uses around 1% in 10h!!! When you have the original rom on your device. i think you have some software installed that consumes such a amount of battery or your batters is broken.
Shaks said:
about the radio and roms, im still a bit unsure as to how that works i have a htc touch diamond which is wm 6.1 not 6.5... would it be possible to upgrade it to a 6.5 by flashing the rom?
Click to expand...
Click to collapse
Sure, you can upgrade, but its not a official way and you loose your guarantee. you do this al on your risk. a good German guide you can find here: http://www.pocketpc.ch/td-rom-upgrade/42092-htc-touch-diamond-rom-upgrade-anleitung.html or of English here: http://forum.xda-developers.com/showthread.php?t=416211. Most important: You should make a complete backup of all your data. there are a lot of apps, that can do this. i recommend SPB Backup. After this: Install the latest official ROM from HTC, make a Hardreset and install directly after this the unofficial ROM of your choice. after flashing, make Hardreset again, before you continue. Remember to flash first the official ROM, than Hardreset, then unofficial ROM, then Hardreset for every ROM you test. you can find many ROM's here http://forum.xda-developers.com/forumdisplay.php?f=430 or here http://www.htc-developers.de/viewforum.php?f=85
bilbo_b said:
then there is something wrong with your device. if take phone to airplane mode, it uses around 1% in 10h!!! When you have the original rom on your device. i think you have some software installed that consumes such a amount of battery or your batters is broken.
Sure, you can upgrade, but its not a official way and you loose your guarantee. you do this al on your risk. a good German guide you can find here: http://www.pocketpc.ch/td-rom-upgrade/42092-htc-touch-diamond-rom-upgrade-anleitung.html or of English here: http://forum.xda-developers.com/showthread.php?t=416211. Most important: You should make a complete backup of all your data. there are a lot of apps, that can do this. i recommend SPB Backup. After this: Install the latest official ROM from HTC, make a Hardreset and install directly after this the unofficial ROM of your choice. after flashing, make Hardreset again, before you continue. Remember to flash first the official ROM, than Hardreset, then unofficial ROM, then Hardreset for every ROM you test. you can find many ROM's here http://forum.xda-developers.com/forumdisplay.php?f=430 or here http://www.htc-developers.de/viewforum.php?f=85
Click to expand...
Click to collapse
thank you very much for your help, i will definitely try to do this over the next few hours after your wonderful explanation... cheers mate!!
Shaks said:
thank you very much for your help, i will definitely try to do this over the next few hours after your wonderful explanation... cheers mate!!
Click to expand...
Click to collapse
i got stuck and confused half way through reading what to do wish i could get someone to do this for me
For the first time, it seems to be very complicated, but it is not. Trust me.
first: Backup you whole device or only the needed data.
in the first step you need to install HardSPL. I use 1.93 from Olinex. Do a softreset after this. After the softreset i have installed the HTC Stock ROM. the easyest way is it, to put the image in the root of your internal storage. name the file DIAMIMG.nbh. Now boot in to USB Mode with holding Volume Down and Right Softkey Button pressed (the <- Key), with this pressed, to a reset with your stylus. it apears a 3 colored screen, followed by a gray screen with instructions in blue letters. follow the instructions. DO NOT destroy the internal storage, there are your backup and the image file!
With the Stock Rom installed, make a HardReset (same as Boot to USB mode, but now hold VolumeDown and the middle round button). After this put your custom ROM to the internal memory, otherwrite the Stock ROM. Boot to USB Mode and follow the instructions. When your done, make again a HardReset. The Hardresets are very important, after this last hardreset you have the device with a custom ROM.
bilbo_b said:
For the first time, it seems to be very complicated, but it is not. Trust me.
first: Backup you whole device or only the needed data.
in the first step you need to install HardSPL. I use 1.93 from Olinex. Do a softreset after this. After the softreset i have installed the HTC Stock ROM. the easyest way is it, to put the image in the root of your internal storage. name the file DIAMIMG.nbh. Now boot in to USB Mode with holding Volume Down and Right Softkey Button pressed (the <- Key), with this pressed, to a reset with your stylus. it apears a 3 colored screen, followed by a gray screen with instructions in blue letters. follow the instructions. DO NOT destroy the internal storage, there are your backup and the image file!
Click to expand...
Click to collapse
thanks once again, let me start with just backing up my data to begin with... i am on the thread for hardspl 1.93 from olinex which i am currently reading through with a confused face lol
also when i press and hold the volume down button and softkey button (<-) it does not do anything (soft reset) instead i have had to download a softreset app in the past just to do a soft reset... (im using a touch diamond) ?
you must press both buttons, dont release them, do a reset (press the red dot with you stylus in the stylus slot). dont release the both buttons, hold dem pressed until the colored screen appears.
you must press both buttons, dont release them, do a reset (press the red dot with you stylus in the stylus slot). dont release the both buttons, hold dem pressed until the colored screen appears.
Click to expand...
Click to collapse
To flash rom via Internal card
1. Hold Volume down and Back buttons .
2. Press the reset button.
3. Keep holding Volume down and Back buttons then release reset button.
To reset to boot-loader mode ( for upgrade Hard-SPL or flash ROM via computer )
1. Hold Volume down button.
2. Press the reset button.
3. Keep holding Volume down then release reset button, you will see tri-color screen - that is called boot-loader mode.
For Battery consumption issue - maybe your battery is too old - you should change to another one.
I'm using Galilio battery with 1400mAh - which has same size with original battery and I can use my phone 2 days ( with sense 2.5 ) or 3 days ( with sense 2.1 ) without charging.
do you have a link to the battery?