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,
I have been using the 1.440 rom upgrade for the iMate PDA2k for the last 2 months and apart fromt he normal shortcomings associated with the rom, such as the phone hanging on pressing the red "hang up" button and the sound associated bug with WM10, i have been pretty content with this present version. I have recently installed FLASHDASH and macromedia flash player on my PDA2k to enjoy animated themes however the software refuses to display the selected themes for some odd reason.
I have also hard reset my machine but still it just doesnt want to work.
I REALLY want this thing to work so please can someone advise me what to do.
Regards
Ahmed
There is something wrong with the today screen part of the 1.40 ROM; i cannot minimize pocketbreeze and uptime meter not works properly.
Help needed,
First time I "bricked" my device is about half a year ago.
I installed a ROM (ThaiHugo's age of reason) and after a BSOD in
Windows my Shift Windows Vista Side was broken. Windows Mobile did boot once in a while. Sent it in for free repair, they changed my motherboard and keyboard, and happy I was after.
Today I installed RomeOS Rom, the ROM istelf wasn't really performing well after installation (memory issues, see other post) but after
a few hard resets to see where the problem was (it seems activesync/pushmail) the device stopped booting WinMo alltogether.
So, I dunnit, I bricked my Shift a second time !
I tried hard reset from Vista using Shift Control Center
Tried soft reset from the control center.
Tried Removing the battery completely.
Tried some other things.
Havent tried ECSHift.exe as the link to cmonex site is dead.
Hope you guys want to post that file again ecshift.exe
It seems to be my last resort
------
UPDATE !! UPDATE !!
I download ECShift.exe. performed a mode0, a -reset and a -w (wakeup) and my screen is still black.
I can't seem to perform a task 28, what is the exact syntaxis ?
This is getting worse every minute, I expected with ECshift to restore it.
----------------------------------
UPDATE UPDATE
Ok...so I'm not jumping of the bridge.
It's working again, I managed to flash good ol' ThaiHugo's Age of Reason again.
What I had to do is do a ecshift.exe /bl (entered the bootloader)
Checked if the bootloader was really active with ecshift.exe /gm
Then , switched to WIndows 7 and customRUU thaihugo,
So', I''m back, after some really scary 3 hours. I''ll wait and see
if anyone else has problems with ROMEOS ROM.
So the conclusion is its not bricked
Actually this happened to me many times when i'm testing ROMeO_S
but i dont get worried because I believe cmonex 200% with her HardSPL.
v1_01 has been running with my machine almost 3 days with push enabled both live & exchange server w/o any lock/hang/resets.
Could it be that I clicked on the Pagepool changer once ? I clicked on it, then closed it.
Did that change my ROM ? I just tested again and I don't think I did. One has to really go in and change a value in order to be able to save.
I wonder what the difference is. Another user has posted my exact issues wth this ROM too. I hope you want to keep developing, as it's one of the best looking ROM's today.
Hi! For a while I've been searching for a reason why my phone seems to freeze almost daily while charging or before / after I snooze a morning alarm. And sometimes during the night, maybe it's random. By freeze I mean the phone is sleeping and when I push the power button nothing happens. The only way to restart it is to take off the cover and either remove the battery or press the little reset button.
I use itje's ROM with standard WM6.5 and Manila 2.1. I tried diferent builds and newer Leo ROMs, but I always get the same problem. It didn't happen some time ago when I was using WM6.1 + Manila 2.0.
While searching in the forums for solutions, I noticed there are some users with the same random freezes using various ROMs from different chefs. But most of the users don't seem to have this problem, which is weird. I guess the hardware should be the same, so does anyone have any idea why this freezing happens only to some of us?
I tried different methods and ROMs, countless hard resets and re-flashes, even additonal Stock-SPL and Hard-SPL, but nothing seems to work. It even happens if I install no other programs and don't have the SD inserted into the phone, only my SIM card. So it's not from external programs (like G-Alarm) either.
Well, any helpful information or advice? Thanks!
I am experiencing the same problem. If anyone got a solution for this, please share.
Regards, Eduardo.
i have the same problem to but only with the cooked wm 6.5 roms and higher not with the rom that came with my x1
i get the same problem. i'm using itje's Touch I-T Xperience 15 6.5
Now I flashed a WM6.1 ROM with Manila 2.1 to see if I still get the problem. Do you think our phones have a problem with the Windows 6.5 builds or maybe the problem is with Manila?
Did anyone try to live with one of these ROMS for a few days with Manila disabled to see if you still get the freeze? Maybe I'll try this also after I finish my 6.1 test. It's very annoying that we don't even know the cause for this freeze yet...
have the same problem when using 6.5 but when on 6.1 nothing of the kind...
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Well, I can confirm that on various itje 6.5 ROMs I get the standby of death without installing any alarm program. I didn't install ANY programs, for what it's worth. And others can use G-Alarm 2.3 and don't get this freeze.
Didn't use Valkyrie ROMs yet. I'm testing now Touch X 10.8.2 and I have G-Alarm 2.3 installed. Let's see if it dies in the next 48 hours while on a 6.1 build...
Here is my experience...
I never got standby freeze issue(never used G-alarm/Klaxon), but i do get black screen or garbled screen issue randomly while receiving call irrespective of the ROMS(wm 6.5/6.5.1).
Only one time almost a week i didnt face this issue, then later problem repeated. So i realized that week i've used COM4 build. So for testing it i tried again same one for a week and problem didnt exists. Since the ROM which i used has default X1 dialer which i didnt like at all.. so got updated to other ROM and started face the same issue
Maybe some of us have a slightly different harware in our X1 that triggers this freeze, but only in WM 6.5?
So far the WM6.1 + Manila 2.1 is working fine, lots of customizations made by me after flashing too. G-Alarm managed to wake me up OK.
Darkchaser said:
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Click to expand...
Click to collapse
Well you can count Valkyrie 4.5.502 out because i installed it yesterday and this morning after my alarm went off about 20mins later the phone frooze. I have been experiencing this for the past months and i REALLY hate this phone now. I have tried all sorts of tricks from reseting the phone around 9pm to just not running ANY program and it still freezes. I have tried all sorts of roms with the exception of Touch X 10.8.2. I guess i might as well give that one a try. I will keep an eye on this thread for a solution.
On an older Valkyrie TR build I was getting the problem and I fixed it by doing a soft reset with the SD card out, waiting for everything to load up and run nicely, then inserting the card again. Went to the music tab and waited for it to load all my tunes and the same with photos. Didn't have the problem after that, but I was only on that ROM for about a week.
I thought it may be related to usb port driver issues in WM6.5, but it could also be the audiomanager in manila or some conflict between a WM6.5 process and a manila process.
Anyway, will be trying 4.4.81TR Valkyrie and see...
But the biggest question is why some (most) people never have this problem...
Never seen this problem on WCX 22001 Pure wm6.5 rom and I'm using it for about one month. I've installed many apps and my X1 works great with battery about 2-3 days using WIFI, BT, and all other stuff. No Manila - no problem in this case. It's an older build of WM6.5 but with newer builds WCX Rom users didn't complain about freezing problem or alarm issues.
So maybe it's Manila?
Today I wanted to flash Itjes newest ROM but I'll wait for solution couse my phone should wake me up today
Can program your phone Lockscreen has frozen the rechargeable device. Best before charging you restart your phone and not run any programs.
yes i get this problem too.. every morning my phone is off.... so it really needs to be looked into.. it seems to occur from more recent builds of 6.5..
i was previously using a wild child pure rom from about 3-4 months ago (6.5 early build)... this issue never happened...
then recently i upgraded to the V11 Unoff series and now it occurs.. and is obviously occuring for a lot of people with other recent builds of 6.5...
if the solution is ever found please let us know....
I might be completely off here... but I used to have this problem often, in addition to having slide to unlock malfunction on me, even with the newer rom builds.
When I unchecked the boxes that said display owner information/notes when device is turned on, both problems were gone - it might just be a coincidence though and I've only been testing it for 2 days.
Hey guys,
I've been having the same problem, only that this are the situations in which I faced the issue with my X1i (and managed to replicate the freeze):
-Receiving SMS while charging (no pc conection)
-Charging while alarm goes off (again no pc)
-When task or appointment announcement sets itself to sleep (i.e: you ignore it) while charging. (go figure, no PC)
-When after ignoring (not hitting dismissed button) task or appointment screen shuts off (Running on battery)
I've also gotten the problem in other situations, but i couldn't replicate them. The only Thing I did notice was that there is a growth in the rate this happens over a span of 3 days after flashing/hard reseting. In my case, it was one increment per day (ie: 1st day, happened once; 2nd day, twice; 3times the 3rd day.. then, i reseted or replicated, so my statistics went down the pipe )
Other thoughs: what radio are you guys using? maybe we can narrow it down to a radio as well. Thus far I've seen it narrowed it down to Manila 2.5, but then others do not have this (and then there me, with Manila 2.1, that has it ). I changed my radio y-day and hasn't happened yet (xing fingers though...) wil try to replicate tomorrow after my alarm wakes me up
My info:
X1i Black (came with R3 generic UK ROM, Radio. 1.14...)
Issues happened with: Radio 1.10.25.18 (Installed with NRG's ROM vOCT 28)
ROM info: (see signature..)
Manila: v2.1.191...
Current radio: 1.14...
Carrier: AT&T US
I tried to contribute as much info I could get about this issue... hope we can get it solved.
I'll try to flash again a WM6.5 version to see what radio will be installed. This week I needed my phone WORKING , so I used a 6.1 ROM.
I didn't find a pattern for my freezes, but I think it mostly happened while charging from the outlet, or in the morning before the alarm went off (very bad thing to happen), or after I snoozed the alarm (again, very bad).
I read somewhere that it's useful to format your SD card before flashing. I don't see how this could help, but I'll try to flash via USB or from another newly-formated SD card. I always flashed with kovsimg.nbh on the SD root and I only formatted it when I got the phone, 9 months ago...
Also, some say it's good to flash first an original ROM, hard reset, then install the custom ROM again. I tried that, even stock-SPL and hard-SPL again, but didn't seem to work. Maybe I had 48 hours without freeze, but then it started again.
@8SE8 - I never had those options checked, so we can rule that out I guess.
I have been reading about this issue here and in another forum - mainly
because I had seen it only one single time. It actually occured when I was
loading the device during the night. I do not remember which ROM it was
exactly, except that it was an itje ROM with Manila 2.5.
Then, I went back to Manila 2.1 and WinMo 6.1, Touch_X 10.X.X. Must say,
that is still my fallback ROM, it feels extremely fast, it is stable, memory
usage is low - what else to wish?
Next, I went to the multilanguage Rhodium based Manila 2.1 and WinMo 6.5
from itje in my own language. After installing FM Tuner, a correct dialer and
some tweaks, it is also very fast and stable, memory usage at 50%. No more
soft resets since almost a week now, no "stand-by of death".
The difference to others is maybe: I do not flash using the SD card, always
with the USB connection. Is this provoking the difference? I cannot imagine,
but this is what I can contribute here.
Hi Guys,
I suppose one good thing to come out of me constantly finding my HD dead after it being on standby for a few hours (it seems intermittent) is that it seems many others are having similar issues.
Can people post their findings to the following question so we can help the community at large narrow down the issue:
When your device hangs/freezes, is it in standby or in use?
If the unit is in Standby, are you using Manila 2.5 or an earlier version?
Which WM version are you using? (6.1 of 6.5)
Have you unticked the "Today timeout" on the Today Settings screen?
My experiences are as follows:
I have only seen this since I have been using a 6.5 ROM
I have only seen this since I have been using Manila 2.5 (i think)
I install only a small number of applications
I have used both MyPhone and PIM Backup to restore info
oh and finally, it's bloody annoying!!!
If anyone has any information as to what could be causing this please post. I'm sure we'd all give our left nut to get this fixed?
This does seem to be an issue that effects some and not others, I had it happen a few times but after flashing back to an official ROM then back to custom (including SPL) I have using custom ROMs for a while now without this occuring again.
Flashmore, thanks for your input. Can you state what steps you followed for others?
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
xboxhalo said:
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
Click to expand...
Click to collapse
I'm attempting to systematically find out what the problem is by installing the same programs each flash with the exception of one. The first attempt was to move back to Manila 2.1 - so far so good but I'm expecting the same to happen at some point.
I want a good ROM, but I'm more bothered about not missing an emergency phone call because my phone is dead!
Hi all.
I'm not sure if this is actually related since when I experienced these so called "lock ups" my phone hard reset and corrupted the SD card as well. This happened two times with HD and once with Diamond2. Both phones with WM6.5.
I'm using corporate exchange and get enforced a device lock policy. I noticed that each time the device froze it was displaying the "classic" device lock number keyboard although the "default" (the new wm6.5) lock was selected.
Anyway, both phones have been working perfectly with WM6.5 and manilla 2.5 after I have started to use the ugly "classic" lock screen.
E
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
gallegus said:
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
Click to expand...
Click to collapse
That's interesting. I might try that.
I have been on Manila 2.1 for a few days and so far so good though.
I'm on WM 6.5 w/ Manila 2.1 for a couple of days and it has happened to me too.
I just tried disabling the options for turning off backlight and turning off phone. Hopefully this "fixes" the problem.
Check this thread, same subject, more details !
K
As said by Kostas66 above me. I guess this thread will soon get a lock...
As per post#10 & 11, please use this thread for future posts
Thread closed