Related
Hi all and thanks for viewing this post before you start asking questions that have been answered several times before.
For Sim(Un)Lock tool GO
Many questions can be found on the WIKI.
WIKI main page.
WIKI page for the Blue Angel
The WIKI is a website connected to this forum, and all information on the WIKI is posted by users of this Forum.
SO CHECK OUT THE WIKI, and read it.
GENERAL FAQ GO
Index of WIKI
How to upgrade to the latest rom GO
Bluetooth upgrades GO
CAB files GO
Extended Rom GO
Radio ROM GO
Upgrading the Blue Angel GO
****
More will be added later[/url]
Nice post, Bosjo....great idea....now let's hope people read this, so I can stop referring to the links in my signature...!
bosjo, add the new 1.40 Tutorial I added to wiki, it makes the seperate Bluetooth and Radio ones obsolete (largely) as 1.40 include 1.12.00 and 1.0.0.3900
The noob finally did it
I want to thank Brazillian Joefor helping me out with my ineptness to READ THE WHOLE WIKI first- I finally upgraded to WM2k5 flawlessly after nearly 6 hours and despite sctatching a bald spot into my head everything is great.
I also want to thank Helmi and everyone else that made this all possible this site is a real asset keep up the great work.
Siemens Sx66 Model ph20b1
Used the unlock on 12/07/2006 on referenced Cingular phone purchased somewhere around April 2005. Worked like a charm, phone now works great on T-Mobile.
I failed to download MaUpgradeUt_noID file from the ftp site for resolving the country code error problem. For tha I am requesting you please upload the file in rapidshare.com (or arrange to upload).
It will be a great help for me.
Thanks
I installed WM6 with a simple PIN last night. This morning I switched SIMs and when switching on I entered the normal PIN and it says "incorrect password".
I haven't changing the PIN and it worked last night. Of course now it goes into longer and longer gaps before you can do anything! and now i must wait for 34minutes before i can try my "lucky" PIN..
No problem I thought, I'll just do a hard reset... but BIG problem. It appears that WM6 won't let you do a hard reset from the unlock screen.
Does anyone know if they have changed the hard reset procedure in WM6?
From the device being powered on I am pressing an holding the power button, pressing the reset and then letting both go simultaneously - is this correct?
It is nice to know if someone steals your 'phone that they can't use it - not at all good when a bug in WM6 makes it happen to the owner!
I have a completely useless brick at the moment...
need your help guys..
Links for wiki don't work, any idea where to get these info from?
in the top bar there is also a link to the wiki, or take this one: http://wiki.xda-developers.com/
EDIT: sorry, apparently i misunderstood, the wiki is apparently experiencing problems and is currently down.
turning off alone.
I upgraded my BA to d-two's WM6.5.5 Build 23529, and now when the battery is on 30%, he turn of or reset and keep doing aftera a while when i turn on again. Chief tony, you know this error?
you should always make sure that your battery is completely full when upgrading. there's been people before, reporting that their battery meter is screwed up after upgrading. so, i guess the 30% are just not an accurate value and the battery is in fact empty. you should load up the battery up to 100% and re-flash the rom. the values will be more accurate
then.
another reason could be that your battery is really starting to go bad and maybe should be replaced.
Hi Chief
Hey chief tony, i reflashed my BA with full charge, and instaled the Wm 6.1 manilla 2d final from D-two, and i've got what realy happens, everytime i used the wifi conection, is doesnt take long and Ba turn of, and when i turn on where it must have the radio version, it appears 'none', so i soft reset and gets ok. you know whats happening?
ps: sorry for the bad english
the fact, that it turns off quickly again, points to the battery having lost most of its capacity. maybe you should have a look at ebay for a replacement.
it shows R NONE G NONE, because unplanned switch-offs or soft resets, that are not triggered by the reset pin cause the phone to boot without radio, some roms start without the radio then, some don't boot at all. it happens with all custom roms and soft resetting is the only way to avoid it.
Chef_Tony said:
the fact, that it turns off quickly again, points to the battery having lost most of its capacity. maybe you should have a look at ebay for a replacement.
it shows R NONE G NONE, because unplanned switch-offs or soft resets, that are not triggered by the reset pin cause the phone to boot without radio, some roms start without the radio then, some don't boot at all. it happens with all custom roms and soft resetting is the only way to avoid it.
Click to expand...
Click to collapse
I wouldn't blame the battery so fast on this one (although entirely possible). There are a few roms (not sure about d-two's 6.1 since I have not tried it) that will become unresponsive once you activate Wifi (not sure why), and eventually resets the device... He could try a different rom and see if that helps.
Hi,
I am trying to get the "For Sim(Un)Lock tool GO" but when I click on GO it returns "No input file specified."
Any other links that I can get this tool to unlock my Blue Angel...
Jay
this tutorial is quite outdated, the one linked in my signature is new and all links are working there. in the 2nd post, you will find the tool needed for the sim unlock and many more
Re-detecting my 1gb sd card!
Hi, Chef.
I initially had some issues with my 1gb sd card after upgrading to m 6.1 & then 6.5.3. But, after a vista laptop detected an removed a virus (autorun file), I was able to access again.
Now, after upgrading using sun dream's latest rom (6.5.5), my sd-card issue has re-appeared. I have just formatted the card (tried either fat or fat32) and still no progress.
Other Issues: Activisync's complaint about my having to increase the size of my mailbox & delete one or two other files is becoming too frequent.
my ba now trips up (or shuts down completely) when d battery is around 50%.
What next?
MDi
Idiake MD said:
Hi, Chef.
I initially had some issues with my 1gb sd card after upgrading to m 6.1 & then 6.5.3. But, after a vista laptop detected an removed a virus (autorun file), I was able to access again.
Now, after upgrading using sun dream's latest rom (6.5.5), my sd-card issue has re-appeared. I have just formatted the card (tried either fat or fat32) and still no progress.
Other Issues: Activisync's complaint about my having to increase the size of my mailbox & delete one or two other files is becoming too frequent.
my ba now trips up (or shuts down completely) when d battery is around 50%.
What next?
MDi
Click to expand...
Click to collapse
What Rom do you have?
ROM: sun_dream's WM6.5.5 Build 23569 CHS WWE
Radio: 1.15
hi everyone. im new to the site. i'm amazed how much i never knew about my xda2i before i found this site. there are sooo many cool tools and stuff i'd never heard about. indeed, i wish i had found this site before i made a huge mistake!
i found an update for windows mobile 2005 and tried to use it to update my xda2i (which i now know is really called alpine). of course it didnt work out how i hoped. it ran through the whole process correctly. it erased the curent rom and - so it said - it wrote the new rtom to my device.
unfortunately my xda2i no longer works. the screen is blank and nothing seems to help. soft and hard reset dont work. i tried taking out the battery, and putting it in the cradle. the red light on the top right corner flashes when i do this. but still no joy. i tried re-loading the 2003 se rom but active sync wont detect my xda2i!!!
i cant get any other tools to work because they all seem to use active sync...
i was hoping there was a way to manually put my device into bootloader mode but i cant find anything on how to do this. if anyone can help it would be much appreciated!!!!
all sorted
well it looks like i was a bit premature in posting my problem. i've just been told how to manually put my alpine into bootloader mode. it worked a treat and i have no problems anymore. many thanks and once again im grateful to the have such a great resource as this site! i'll definitly donate next time i have some money in my paypal!
for anyone else having similar problems i'll just say how to put your device into bootloader mode as i had the hardest time finding it out. too many people assume this to be common sense and dont explain for all of us newbies! lol
simply hold down the power button, the select button (thats the directional pad pressed down centrally) and the reset button for a couple of seconds. this puts the alpine into bootloader mode.
athomas81 said:
hi everyone. im new to the site. i'm amazed how much i never knew about my xda2i before i found this site. there are sooo many cool tools and stuff i'd never heard about. indeed, i wish i had found this site before i made a huge mistake!
i found an update for windows mobile 2005 and tried to use it to update my xda2i (which i now know is really called alpine). of course it didnt work out how i hoped. it ran through the whole process correctly. it erased the curent rom and - so it said - it wrote the new rtom to my device.
unfortunately my xda2i no longer works. the screen is blank and nothing seems to help. soft and hard reset dont work. i tried taking out the battery, and putting it in the cradle. the red light on the top right corner flashes when i do this. but still no joy. i tried re-loading the 2003 se rom but active sync wont detect my xda2i!!!
i cant get any other tools to work because they all seem to use active sync...
i was hoping there was a way to manually put my device into bootloader mode but i cant find anything on how to do this. if anyone can help it would be much appreciated!!!!
Click to expand...
Click to collapse
there is no window2005 rom for 02i at the moment. note that before upgrade ROM you have to find out the suitable rom for you PPC. 02i rom is always Alpile ROM. the newest is 1.11.171 radio is 1.04
Ever since returning from repairs, my Kaiser is giving me more problems than before.
First, I apparently lost the ability to hard reset my phone using the 2 softkeys & soft reset button method.
For more: http://forum.xda-developers.com/showthread.php?t=384581
First thing I did when I got my phone back, was flashing the latest ROM from Dutty (Dutty's Official WM6.1 5.2.19209 Release). After performing numerous installations and soft resets, my device went crazy after yet another installation and soft reset.
Just before my Kaiser takes me to the Today screen after (re)booting, the phonepad pops up and seems to be 'pushing numbers out of itself'. Confused by the explanation? Just take a quick look at the short vid I made.
http://www.youtube.com/watch?v=YGkot2-mbbI
(Fast forward to 01:00 to see it going crazy. Long after the vid ends this continues)
Anyone got a clue as to why this is happening? Or has my incompetence reached new heights and is that to blame for my problems?
Thanks in advance
P.S.: In the meantime I have hard resetted my device, but I'm still curious...
call at&t and get a replacement. Easiest thing to do.
Try load the factory default ROM.
FAx
The kaiser has been known to act haunted, thats why it comes in black.
Fix: When applying this fix avoid looking at the screen to avoid the image inside the device that you want to exorcise. Unplug fully and remove battery to prevent an escape through the wires; also ensure that you disconnect any usb devices to avoid an escape to your computer.
Once you have isolated the device. Find the packaging and insert carefully, ensuring that it is packed safely to avoid any breakage resulting in an escape to your home. Then ship to the place you purchased it from and ask them to send you back one that is not possessed.
Good luck.
alexn2 said:
The kaiser has been known to act haunted, thats why it comes in black.
Fix: When applying this fix avoid looking at the screen to avoid the image inside the device that you want to exorcise. Unplug fully and remove battery to prevent an escape through the wires; also ensure that you disconnect any usb devices to avoid an escape to your computer.
Once you have isolated the device. Find the packaging and insert carefully, ensuring that it is packed safely to avoid any breakage resulting in an escape to your home. Then ship to the place you purchased it from and ask them to send you back one that is not possessed.
Good luck.
Click to expand...
Click to collapse
Very dramatic - you don't work in Hollywood do you?
gqstatus0685 said:
call at&t and get a replacement. Easiest thing to do.
Click to expand...
Click to collapse
He's in Belgium
ach2 said:
Very dramatic - you don't work in Hollywood do you?
Click to expand...
Click to collapse
Is that a hint for a career change...... the loss of one's tilt is quite a dramatic event.
@alexn2
I already called in help from the Vatican, but it will take some days before the first batch of exorcists arrives (haunted was a sarcastic expression). Any explanation in the meantime?
@gqstatus0685
This device is a replacement which I got back last week. But it seems to me that I will need to send it back again. Another week without my Kaiser...
alexn2 said:
Is that a hint for a career change...... the loss of one's tilt is quite a dramatic event.
Click to expand...
Click to collapse
care to sign up for ma 4th installement of the exorcist?
Damn this is scary. Call the Ghost Busters!!
WTF?
I just don't get it...
I now have my 3rd Kaiser, since I had issues with the first two. One of the problems my second phone had was the 'haunted' problem as described above.
My Kaiser has been working like a charm for several weeks. I first used the stock ROM, then switched to Dutty's ROMs. I used 3 ROMs: Apr16, Apr29 and Jun07 release.
I installed the Jun07 release today. After installing and configuring the same software I had before upgrading the ROM, guess what?
HAUNTED AGAIN... WTF?
I loaded the ROM, did multiple hard-resets, soft-resetted after customization, loaded CABs, configured them, rebooted several times and when I had finally configured every app => TOTAL Clusterf*ck... (again)
Sometimes it does boot normally BUT when I press the 'Send'-button and the dialer opens => Kaiser goes LOCO again...
Anyone got any idea as to why this happens?
NOTE: I have the latest SPL + Radio NEON 1.58.25.17 (included in the ROM)
I did some additional testing. I had SPB Pocket Plus installed an had the Safe Boot option enabled. So I did some testing in safe mode.
The phone boots 'normally' to safe mode. No apps or services are loaded, and I can open the dialer and even enter numbers to dial. But when I try to delete a number using the backspace in the dialer => again haunted
I just discovered the problem. I always try to install most of my apps to my Storage Card.
Some of those apps is the Microsoft RDP (remote desktop) client.
Installing it to the Storage Card caused the phone to go crazy. It has to be installed to the Main Memory.
NOTE: After discovering the problem, I did find other posts across the forum reporting problems if the app isn't installed to the main memory. Since I found the cab on someone's 4Shared account, I wasn't aware of the installation requirements.
Thanks anyway for the support given
As posted before, I very recently flashed Dutty's Diamond V1 Build 19588 ROM (Jun07).
Today I tried playing WMV files with Windows Media Player for some performance testing. I loaded my first file and whenever I tried something, like fast-forward, switch to fullscreen mode,... my phone crashed and soft-resetted itself.
Guess what I got when the phone booted => The crazy dialer (haunted edition)... It kept doing this after every soft-reset until I removed the MicroSD card. The video I was trying to play was located on the Storage Card, so there might be a relation.
While I have done additional testing under the same circumstances, I haven't been able to simulate the problem.
I'm still clueless, so as always are ideas welcome...
i know alot of you all dont want me to start a new thread but my phone is acting crazy and i need help ASAP its giving me plenty of problems but only going to ask to help a couple....
1.) i installed psShutXP Power key on my phone and it worked great and actually still does but after it has been on my phone my phone will soft reset at any given moment(mainly when im on a phone call)...i have uninstalled and installed to see if that was the problem and unistalled again and still no fix please help on this problem first
2.) sometimes when i hit my power key to wake up the phone from sleep mode it gives me either an all black screen or an all white screen so i will have to put it back to sleep and try 2 or 3 times
P.S. i own the htc fuze from at&t in the US and same ROM as it came with...PLEASE help and dont flame and i will not add another thread of this kind again
No worries friend. This site is here to help.
Your best bet is to try a hard reset. This will wipe the device and set it back to factory fresh state. Just like you took it our of the box.
The downside to this is all of your data and programs in memory will be wiped out. The SD card will be fine, but to be safe, remove it befre you hard reset.
To hard reset, do the following:
1. turn the device off.
2. press and hold the volume down and Enter Button (round one on front)
3. Soft reset and keep holding down volume.
4. follow instructions on the screen.
Since you are faced with this, you may want to try flashing a new ROM or deleting some of the ATT "bloat" that comes pre installed. Check here for new ROM advice. Check here for a lighter set-up of the factory ROM.
Good luck.
Doug M.
is it any other way i might be able to fix without hard reset...just want that to be a last resort
P.S. my phone have seen some water it fell in outside during a rain storm so didnt know if that would have something to do with it also but this also happen a couple of months ago
It sounds like you have already tried the normal procedures. Your best bet for future stability is to start over. If you follow one of the 2 guides in my earlier post, you will have a much more stable device going forward. It takes a bit of time, but is worth it. Once you get the hang of it, it gets easier.
Doug M.
just try to hard reset it. you always can go back to factory ROM.
now im using wm 6.5, and my device performance is spectacular. XDA is the best.
thx guys.....i will try the energy rom 3 wm 6.5 that i have heard alot about
energy rom is a good choice and my current rom .
don't worry , once you figure out the rom scene you will hard reset all the time and will learn how to backup your contacts and texts .
a good thing is that nrg's rom even has a good restoring program built in . Pim restore . i use it religiously .
If you run into problems flashing another ROM or the phone still "acts" up, the drop or the water may have damaged some circuitry in the device.
You may need to restore to a factory state and send it in for service.
thx guys i was out of town.........but yea i got a replacement coming in so back to the drawing board with adding all the software i had on the old one to the new one but once again thx
my phone would turn off randomly and when slid it shut. bent the battery pins out a bit and all good now. just thought I'd add that as a possible problem/solution
lol wish you told me a few days sooner i just filed insurance claim and got a new but thx anyway because i might just have to do that with phone....im not hard on phones just bad luck if you know what i mean
Other things to do in the future if you come across similar problems:
1. Uninstall the last app you installed prior to having the problems.
2. See if problem is still there...
3. Repeat 1&2.
Always back up your data... There are some very nice backup programs available.
If above doesn't work.
Hard Reset and load programs one at a time after hard reset until problem reappears...or hopefully does not reappear.
If you load a bunch of apps on your phone, it can be more difficult to narrow down because of the amount of changes made by each app it may not return to the same state after uninstalling a program. That is why Hard Reset can be your friend...
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.