Related
I, have Siemens SX66 GSM ( PH20B) Upgraded to wron version and now it boot with colored horizontel straps (red,green,blue,white) and goes to WM 5, with slow to none functions and also lost radio.
Now I, tried with several WM5 versions and it display error message ( Model ID error 100) Can some one help how to remove / clean it and recomend working WM5.
See some post at the bottom of this topic
If you you have lost the Radio, ie, no version number is displayed on cold booting/hard re-set, then all is lost.
As i had the same problem with a phone I was given to fix.
As most/all of the Upgrade programs Check to see what Radio version the phone already has, and if it cant see one it fails
My only course of action was to get the Phone fixed under warenty
Read all about it here
Hope.......
Mine did the same thing, it was sooooo slow that I was thinking about buying a new unit but at the last breath I did the following and it worked:
- Go to the BootLoader screen (Press: Power Switch+Media Player+Recorder+Rest) all at the same time, your PDA should say “Serial” at the top of the screen.
- Plug you PDA to the cradle and it should read “USB” at the top of the screen.
- Use At least TuMa 1.3 with Radio 1.13.
Note:
The upgrade EXE should load up with a picture of the PD at the left side of the screen that DOES NOT look like your SX66…it looks like an HP PDA…!!!
Mine came back to life but sometimes you might have to SOFT reboot your PDA to get the Radio to work (Hard boot then use a third party software to softreboot).
Good luck.
so using the MaUpgradeUt_noID.ZIP and radio rom only you were unsuccessful at flashing?
Black6spdZ said:
so using the MaUpgradeUt_noID.ZIP and radio rom only you were unsuccessful at flashing?
Click to expand...
Click to collapse
I, went through all upgrades without issue but now PDA is so slow it takes ages to change selections..
have you downgraded back to 03se and still have this issue?
You will have to follow the steps very accurately...if you leave any step out you might end up like me at the beginning when my device was sooooo slow it was useless.
I took these steps from this forum...try it
Best Luck…
Thanks for all help did every thing but still some of menu are so slow that take several minutes to open , still looking for some tips and suggestions or if some one one knows how to turn it back to W2003
I, remoed some of programs from my SX66 that seems to be causing problems and were npt compatible with and got my PDA back...its now working awsome...Thanks for all who helped
there's a radio v2.61.21 for prophet, is there any 1 for wizard?
i am always ready to test a new radio for the wizard(as long as it doesnt screw anything up ofcourse)
i installed the prophet rom and i think my mda is done
Done as in working
or done as in "My, what a nice shinny brick you have there"
Jules
I would guess the "nice shiny brick" part, but maybe we'll get lucky...not a big fan of my 2.47 radio ROM...
I like to hear more about this new rom, but indeed, i guess he means that he dorked his device.....
paypalbid said:
i installed the prophet rom and i think my mda is done
Click to expand...
Click to collapse
It works, but the battery-status doesn't work anymore. It doesn't brick your device, bull....t.
lol hmm interesting, extract the radio for us!
jacob-mda said:
lol hmm interesting, extract the radio for us!
Click to expand...
Click to collapse
Just go to ftp://xda:[email protected]/Uploads/Prophet/Prophet-roms/Radio_ROMs
What I don't understand is why always people come up to this forum claiming the "bricked" their device. I don't know how many times I flashed mine, it's still working.
Also I must say my Wizard is the best, because no matter how hard I try it never acts in the way people write here sometimes, why's that....
WM6 installed with 47.11
* no switching of and/or on
* MMS works
* Camera Works
* No battery drain, it's even better now.
* Wifi works
* No carshes in the last weeks....
* GPRS working
* Phone's not constantly "searching"
* etc.
I'm going to look for a uncontrolled and/or beta release AKU 3.8 and a half HTC Blue angel ROM to flash on my Wizard, maybe that will do the trick.
"edit" there's is one thing though: No matter how often I flash my Wizard, I still have the Molski splash, how to remove this ?
anybody ?
Vilem said:
"edit" there's is one thing though: No matter how often I flash my Wizard, I still have the Molski splash, how to remove this ?
anybody ?
Click to expand...
Click to collapse
This is the splash screen I use atm:
http://forum.xda-developers.com/showthread.php?t=290454&highlight=wm6+splash
vippie said:
This is the splash screen I use atm:
http://forum.xda-developers.com/showthread.php?t=290454&highlight=wm6+splash
Click to expand...
Click to collapse
Heeeeeeeeeeelp I used this file, but was unsure so I stopped at 50% now I'm stuck with this coloured screen, did I brick my device.............
Kiddin, thanks Vippie, I know I could have looked for it, but while writing the post I came up with one thing which was bothering me.
It worked, it's gone...
Just flashed this on a CID unlocked G4 wizard with Orwell's Crossbow on. So far so good, full signal strength where I normally get it. Bundled utility works fine with the upgrade. About to test the power up thing by disabling batterystatus.
Vilem said:
Heeeeeeeeeeelp I used this file, but was unsure so I stopped at 50% now I'm stuck with this coloured screen, did I brick my device.............
Kiddin, thanks Vippie, I know I could have looked for it, but while writing the post I came up with one thing which was bothering me.
It worked, it's gone...
Click to expand...
Click to collapse
You have to commit to the flash! If you start it, let it finish or don't start at all!
Take out your battery, put back in your battery, turn on your device, connect to your pc and reflash the SAME radio rom!!
This will atleast get you out of the bootloader cycle.
dwny said:
You have to commit to the flash! If you start it, let it finish or don't start at all!
Take out your battery, put back in your battery, turn on your device, connect to your pc and reflash the SAME radio rom!!
This will atleast get you out of the bootloader cycle.
Click to expand...
Click to collapse
I think he was just joking...
installed the radio. works but no battery indicator anymore. battery status won't overclock either.
The strange thing that i encounter with this rom is also no battery indicator and no battery status, but most important, when i call to a voiceresponse system and i have to make a choice in a menu, let's say the voice says choose 1 to bla bla bla, then i press one but nothing happens. So i went back to radio 2.47.11 but the problem remains. How could this be? Could this have something to to with sending dtmf signals? Anyone knows how to make this work again?
Also with that new radio the battery isn't charged anymore.....
Downgrade to radio 2.19
the reason i thought my device was done because I was unable to charge the phone, I was unable to communicate the phone to active sync. But anyway worked things through and out and went back to 2.47. At least i took the plunge and installed it.
Anyone got from MyQtek new 2.61 radio ?
do the prophet radio roms work on the wizard?
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.
Recently upgraded to 6.1 on my ATT Tilt. Now after i lock the device it will go to a grey lit up screen and suck the battery. The screen will go from grey to black and back and forth a few times then remain grey.
If i hit the power button on and then hit the power button again the screen will go away.
The problem is when i do not notice this, my battery dies FAST!
Anyone else have this? Any idea why?
Bump. Please this is draining my battery like crazy.
Not sure if this is the exact same issue or not, but I've noticed that occasionally, after I hit the power button or it goes into stanby on its own, that my screen will "turn grey" as you put it..... I think it is the backlight comming on without the rest of the screen. I've noticed it a couple times where it flashes on, then goes off again a couple times... once or twice staying on longer. Also, if I hit the power button to turn it on, the regular screen comes on and then it seems to stop. I've got the lock set to activate after 1 hour of stanby and rarely lock the phone otherwise.
I only noticed this after upgrading to AT&T's official WM6.1 ROM.
Anyone have any ideas?
That is the exact situation. And when you hit the power button on again then off again it seems to go away.
Glad I am not alone. Someone out there that is smart should know what is going on with the 6.1 and backlight.
I just noticed this happen on my Tilt last night when I plugged in the charger. The screen was already locked and in standby when I plugged it in. I placed in down on the desk and started to walk away when I saw the screen light up... just blank gray. I pressed the button to take it out of standby and then again to put it back in standby and then it was fine. Didn't think too much about it until I saw this thread.
I'm running totally stock WM6.1.
great im posting this months after the last poster but yes i just updated my phone to the 6.1 rom and i have the same issue happening.....and what is sad is that no one has answered with any help!
to EVERYONE in this thread...this forum would love to help others facing problems but we are not mind readers! please post more information...
for example, quite a few of you have noticed that the problem started happening after the ROM update to 6.1...don't you then think that it is important for you to look into what changes occur in your device when you upgrade a ROM?
if you read around, you will notice that SPL version and Radio ROM versions are just as important as your ROM version and that certain combinations of these three key ingredients will cause unexpected problems.
for those in this thread that already know the importance of SPL and Radio ROM versions, don't you think it is important to let the rest of us know these details in your posts about issues if you want help?
my suggestion to you is to post information about your device in your signatures (see mine for an example) so that you can post short messages about your issues and not have to worry whether or not you've provided the basic amount of information...you don't go to your doctor and tell him it hurts and then expect the doctor to guess where it hurts and to guess your medical history? you bring this information along in the form of medical history documents when you FIRST visit the doctor.
i'll try to help (and so will countless others) once you provide the basic information.
read the wiki for more details.
good luck!
thank you for help and advice. I have added information into my signature about my phone. And the grey screen has gotten worse. and yes it started when i dl the ROM from the HTC site for the ATT Tilt phone. Ive searched around and no one really has an answer from what i have found...please help!! Its is really annoying!
you still need to mention your SPL version so we can proceed from there. read the wiki for more information on how to find out what SPL version is present on your device.
update your signature with that information and then i feel your signature will be complete. remember, if the filename of the ROM contains some strings defining the versions of the various parts of the ROM, it does NOT mean that those parts of the ROM will be updated exactly as expected. for example, your signature says your ROM is "3.57.502.2 WWE"...did you get that information from the filename containing the ROM update? or did you actually go into Settings->System->Device Information to see the versions?
bottom line, don't rely on the version strings in the file that you download. instead, after the ROM has been updated, check on your device to make sure that the ROM, Radio, and SPL versions are as expected.
after you find and report your SPL here (read the wiki to find out how to check your SPL version), then we will probably advise you play around with the SPL version or maybe even try some other 6.1 ROM for the Kaiser. you should know that there are SEVERAL "official" ROMs available to upgrade to an "official" WinMo 6.1 and there are even more unofficial "cooked" ROMs to get you to WinMo 6.1.
hey thanks...i totally understand what your saying but i really dont even know how to check for my SPL or what SPL im using. I dont even know what SPL stands. I looked at the wiki but its talking about restoring your ROM and SPL back to what it was and stuff. I also found my ROM name in the phone info tab.
in the wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser) the second question in the "ROM Upgrading" section should have an answer (http://wiki.xda-developers.com/index.php?pagename=SPL Questions?) that will explain what SPL stands for, what it does, and other terms that can refer to the SPL.
once you have read all of that, you will understand that the term "bootloader" is also used to refer to the SPL...then you can look at this page (http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets) detailing the various methods of accessing low level device functionalities such as hard resets, soft reset, and entering the bootloader screen (at the bottom of this page). once you enter the bootloader screen (its called the tri-color screen), all the information displayed indicates what SPL version you have installed.
i agree that the information on how to check your SPL version is a bit difficult to find in the wiki but ALL of the above information is there...just have to read quite a lot of it and carefully too! but believe me, once you've done some solid reading and searching, you won't regret it!
please find out your SPL version and let us know! good luck
Thanks again...and i didnt see that SPL question before...i might have missed it...but it was helpful. Thank you...i hope i finally got what is needed and i added it to my signature! So i hope that is all the info needed to help me out because that grey screen is annoying...never happened before until i went to the WM 6.1 rom!
let take a step back......why dont you flash the at&t 6.0 rom back onto your device, if it still does that grey screen thing, we could then rule out the rom upgrade as being the cause.
well i really dont know how to go back to the other ROM since it is one o the ATT Tilt ROMs from HTC. And i like how the WM 6.1 is...they got really some nice new upgrades but thats about the only annoying glitch that comes with it other then the backlight resetting to dim at 10 sec's all the time. I know it is the ROM cause a lot of other people on here had the same issue after the upgrade...and some people tried to go back to the original ROM before the upgrade and it messed their phone up for a few people so i dont want that to happen with me!
Download the 6.0 ROM and and flash it just like how you upgraded it to 6.1, exactly the same process. You dont need to install HardSPL but it advisable that you do so.
Ton of ppl flash their device many many times, and they dont mess up their device. If you are too afraid that flashing ur device will mess it up, and you are very sure that the grey screen is cause by the 6.1 rom, good luck figuring out, cause i dont have any suggestions that doesnt involve flashing. ok maybe a hard reset.....but after that i'm out of suggestions.
Aight thanks for your help but flashing back isnt really what i want to do....like i said i like the new ROM but the grey screen is the only issue i have...and i know its only cause of the new ROM but im hoping someone else has an answer to the issue!!!
same here
Not looking for a solution, but just adding mine to the list,, I had a 6.0 version that did this. got a replacement after complaining of the backlight problem, and it did it (6.1 version), took it to the ATT device store and they swapped it for a third, 6.1 version also and it does it,, called the help line and they pretended not to know anything about it. just did a hard reset and said "its not doing it now,, I cant help you" I'll live with it if its the worst thing it has.
Scott
I just upgraded to the ATT 6.1 Rom last night and I'm facing the same issue. I have been trying to research as much as possible today and can only find people describing the issue. I did do some experiments today and here is what I noticed...
I have the Device Lock on my today screen. Before the ROM upgrade, when I would lock the device the screen used to dim immediately, and then of course I would press the power button to shut off the screen. Now, with 6.1 ROM, I noticed that when I lock the phone, the dim does not take place until 10 seconds. What seemed to be happening with my "experiments" today, is that if I press lock and wait for the 10 seconds for the screen to dim, and then press the power button to turn off the screen, no grey screen. If I press lock and hit the power button before the screen dims I get the grey.
Looking further into this, I hit lock and waited 2 seconds before turning off the screen. Sure enough after 8 more seconds I get grey. I repeated the experiment again. This time I hit the lock icon and waited 8 seconds before turning off the screen. Sure enough after only two seconds, the grey screen returned.
I feel pretty confident that if that dim took place immediately after lock, like the original ATT ROM, this might not be an issue (at least for someone like me that is used to the 2-step, lock and power button process).
As another experiment...
I also noticed that if I get the grey screen, I could slide out the keyboard and slide it back (which of course turns the screen back on), hit the power button to turn the screen back off, and the grey screen would go away.
Grey Screen on Tilt Problem
Same issue on mine. Anyone find a solution (for any version ROM, etc.) on the ATT Tilt? Thanks.
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.