Develop Bugs

Xda Exec Major Problems

PLEASE HELP ME
I tried to upgrade my xda exec rom from the O2 updates website, the process went smoothly until my pc told me to do the cold reboot on the phone. However after doing this reboot my screen looks like it has crashed and just a coloured mess fills the screen. my pc cannot see the phone now. is it possible to put the original software on the rom and if so how do i do it?
PLEASE HELP, ANYONE.... I feel like O2 have given dodgy info on their downloads

I have a same problem like u. I try to upgrade rom to version v1.30.162 on http://www.my-xda.com/xdaExecSoftware.jsp, but afer that my exec stuck on bootloader and can't recognize USB port only serial port. And i try to send back my exec to O2 and ask what happen to my phone, customer service said that i upgrade using uncompatible ROM for Exec, but i think i use an original ROM from O2.

Put the device into bootloader by pressing and holding the backlight key, power key and reset button at the same time for 3 seconds. If you see serial in the display, hook it up to the PC. The display will change to read usb. Windows will whinge and ***** that the usb device is not recognised, ignore this, it is normal. Take this opportunity to flash a decent ROM, not the crap standard ones. If you do want to use a standard ROM, download them from the FTP. I have downloaded corrupt ROMs from O2 in the past.
@Willows, try using a different USB port, sounds daft but happened quite often on the Alpine. You never know......

Just to add to Pug's answer. If your next question is how to upgrade, follow this thread: http://forum.xda-developers.com/showthread.php?t=269118

cktlcmd said:
Just to add to Pug's answer. If your next question is how to upgrade, follow this thread: http://forum.xda-developers.com/showthread.php?t=269118
Click to expand...
Click to collapse
Watching my back when I'm drink surfing now?
There's always something you forget isn't there.
Thank you.

pug said:
Watching my back when I'm drink surfing now?
There's always something you forget isn't there.
Thank you.
Click to expand...
Click to collapse
All the stuff I am learning from WM5 I read from here just lurking around. Just returning them to others. I should be thanking you too. So thank you.

where can i get the upgrade
hi, can anyone supply me with a link to get an O2 xda exec rom upgrade as i downloaded and installed the version from the O2 site and it caused my phone to go into meltdown.
Please help
Thanks in advance.

IT WORKS But....
pug said:
Put the device into bootloader by pressing and holding the backlight key, power key and reset button at the same time for 3 seconds. If you see serial in the display, hook it up to the PC. The display will change to read usb. Windows will whinge and ***** that the usb device is not recognised, ignore this, it is normal. Take this opportunity to flash a decent ROM, not the crap standard ones. If you do want to use a standard ROM, download them from the FTP. I have downloaded corrupt ROMs from O2 in the past.
@Willows, try using a different USB port, sounds daft but happened quite often on the Alpine. You never know......
Click to expand...
Click to collapse
I did what you said and my phone is up and running again, however I have a new problem now.
I have TomTom 5 on my xda exec with an BT GPS Bluetooth sat ariel. Before hand the device worked perfectly but now TomTom cannot see the device, I have re-installed all the software and set up my Com ports and enabled Bluetooth.
Has anyone got any ideas?

scousegitt said:
hi, can anyone supply me with a link to get an O2 xda exec rom upgrade as i downloaded and installed the version from the O2 site and it caused my phone to go into meltdown.
Please help
Thanks in advance.
Click to expand...
Click to collapse
Just re-flash it, it's the only way to be sure:
ftp://xda:[email protected]/Uploads/Universal/Shipped_ROMs/Xda_Exec_Upgrade_v1.30.162.exe
Make a backup of your contacts first though.....
EDIT:
Forgot to mention, when using BT GPS, do not set up the COM ports with secure connections, the UNI doesn't like it.

Still no joy
pug said:
Just re-flash it, it's the only way to be sure:
ftp://xda:[email protected]/Uploads/Universal/Shipped_ROMs/Xda_Exec_Upgrade_v1.30.162.exe
Make a backup of your contacts first though.....
EDIT:
Forgot to mention, when using BT GPS, do not set up the COM ports with secure connections, the UNI doesn't like it.
Click to expand...
Click to collapse
I have re-flashed again and installed tomtom 5 but still can't get the xda to communicate with the BT GPS FGPXBT02 the bluetooth is connected and the com ports set up with no security but tomtom still reports no GPS device found. Could anythin else be wrong?

Tom Tom 5 will not work under WM5. Go to ToTom site, and there is a 5.2 upgrade, which works fine

When installing WM6, ActiveSync auto disconects. What to do?

Hello everyone.
I have just bought my Hermes (AT&T 8525) after one year of planing so. It came with WM5. I downloaded some of the ROMSs, radio and bootloaders commented here. I tried reading all the vast infromation in this forum and the wiki, but still having a problem.
THE PROBLEM IS AS FOLLOW:
When I start the flashing process, using HTC_TyTN_WWE_3[1].54.255.3_6275_1.48.00.10_108.exe or RUU_Hermes_CINGULAR_WWE_3.1.57.502.1_6275_1.48.00.00_108
... everything goes well, until the progress bar appears in my PC. When it appears, ActiveSync in my PC closes and my Hermes goes to stand by (the lcd goes off) so I cannot complete the installation process.
The phone works pretty well and I'm really amazed for all its capabilities. But still, I'm stucked with wm5.
Why do you think this happened?
PS: I flashed the radio (1.51.00.10) and bootloader (HARD SPL v7). My ROM version is 2.15.502.3. I use "ActiveStink" to sync my files without problems.
Any advice will be more than welcome!!

I'm no expert but that appears to be normal behaviour!
ActiveSync is only used at the start of the process. After a few files have been transfered, Activesync is closed and a different link is established. If you just leave it for a short while longer, a progress bar should appear on the Hermes too.

Yes, ActiveSync will disconnect. The RUU takes over the connection. Have you let it sit - sometimes it takes a minute for the progress bar to move.
Have you consulted www.mrvanx.org for help on the flashing?

todd_jg said:
Yes, ActiveSync will disconnect. The RUU takes over the connection. Have you let it sit - sometimes it takes a minute for the progress bar to move.
Have you consulted www.mrvanx.org for help on the flashing?
Click to expand...
Click to collapse
I'm having the same problem - always have. The message tells me that I'm disconnected and that I should check my USB connect etc. I left that box up there for about 15 minutes. Now I've closed the box and have waited several minutes with no activity. This is pretty aggravating. Thanks for any help.

try turning off your antivirus aplication. thats work for me flashing my tytn to wm6.

I've done everything.... I guess
Hi...
Yes, I consulted the www.mrvanx.org, excellent tutorials.
I flashed without problem the radio and bootloader. The progress bar started to "progress" and everything was fine. The only problem I have is flashing the WM6.
I don't remember where, but I readed that flashing the bootloader "Hard SLP v7" causes my HTC not to accept any Oficial WM6 ROM. The article said that I only had the chance to flash a coocked or modified ROMs. Is this true?
If not... what else can it be? I also closed all my applicacations including the antivirus, goback, disabled the internet connection, the logictec mouse center, etc. and nothing, the same as Chicoh happens to me.
"Error 260: Connection... check the USB cable bla bla bla."
Should I restart in safe mode to do the flashing?
Should I try to install a modified ROM?
Have in mind I've tried three different official ROMs: WWE, Cingular and spanish.
Thanks to all the comunity!!!
Saludos desde México!!

Greetings -
I had a similar problem and couldn't get the thing get going. My solution was to load it from the SD card. This worked flawlessly.

liquidsilver said:
Greetings -
I had a similar problem and couldn't get the thing get going. My solution was to load it from the SD card. This worked flawlessly.
Click to expand...
Click to collapse
I'm trying that as we speak. I have a good feeling about this. I'm a little concerned that I didn't think of it though. Makes perfect sense - Skip the middle man.
UPDATE: Crap. No luck. Thanks all the same though. I'm not giving up.

What OS are you using, xp or vista? My vista 'top had the same problem wouldnt flash for the longest time and i had to use my xp.
However, it does work now. Not entirely sure why.

Now I had success!!!
Hello my friends.
It seems that the article I readed days ago detailing that after flashing the Hard SPL v7, I could only install a modified ROM, not an official one from HTC or Cingular.
I downloaded Black Satin and installed it without any troubles. The entire process lasted only 3 minutes!!!
I wanted to have an official ROM, don't ask me why, and never tried the "other" ROMs that are actually excellent!!! some apps that were on WM5 are not in WM6, which is kind of sad, but if there's something that I love of WM Smartphones is that I can download and install whatever I want or develop it if it doesn't exist!!!
By the way, I use Windows XP Pro.
Thanks for all the support!!!
PS: Before flashing the Hard SPL v7, I tried installing the cingular WM6, but didn't make it. That's why I readed almost all the pages and threads here in xda-developers and found that flashing a new bootloader was a very good idea. The rest of the story is known by you.

Help! have i been cursed with a bad dash?

i dont know what's wrong, ive owned this dash since march. updated to wm6 when it came out, then stopped giving a hoot after finding out that SNappunlock wont work on my dash.
i noticed people here found a very nice dash rom that i want to flash to so badly, but i learned that this requires appunlock in order to get the CID bypass to work
after searching around for wm5 (took about an hour) so i can flash back just so i can appunlock, then flash to the better rom. i found it! all thanks to BGNiko
you think i'm done with my problems, right? well i go to flash to wm5, and during the flashing session, the screen brings me to that RGB before the rom change happens, but no go! it tells me my usb cable isnt hooked up even though it is. ive had no problems re-flashing to the wm6, so the cable isnt the problem.
anyone ever have problems reverting to wm5? is there a solution?
thanks in advance
ps: i have us tmobile

uhh... did you try again?
i had the same thing happen to me. tried again, same thing (same message that you got). restarted the computer, tried again... presto. worked fine.
so long as the flash process doesn't start, your phone should be fine. it's just a matter of getting the computer to talk to the phone. it might be as simple as a computer restart... or trying a differnt usb port or something.

well, took your advise.. didnt work, but thats because i have vista (go figure). did it on my other comp and it worked
though i'm still faced with the appunlock problem
appunlock didnt work, and every time i go to execute sda unlock it tells me that its "not a certified windows CE edition"? or something to that matter
any help would be greatly appreciated
edit: wow, so i am an idiot. i thought the apps had to be excecuted from the phone.
anyway, did the uspl cid unlock. turned my screen white instead of black, but i'll take it

Very Strange Brick Problem

Hi guys, I've read and used the forum for years and upgraded my Cingular 8525 a ton without troubles (followed Vanx's method for vista and for upgrading), but this is the first time I'm really stuck without a clue.
I had Schaps latest OS on my phone working fine for about three days. It was charging with the USB hook up to my Computer. I pulled the USB out and the phone entered bootloader. I couldn't get it out. I tried using mtty to no avail, hard reset ect., but finally used the SD loading method to put TNT's latest on it (don't know why this worked). Here's the thing though, the phone will load fine on first load after I flash, but if I soft reset or turn the phone off and on it goes right into bootloader mode. The only way I can get it to load up again is to connect it to the computer's USB, take out the battery and then put it back in. the OS then boots up without fail.
I have read a ton and searched on the forum, and if any of you can help me understand what the hell I can do to fix my phone I would really appreciate it. I will post anymore info you guys would like, I really need your help on this one.
Thank you so much!

Hi,
I posted exactly the same problem today ! here:
http://forum.xda-developers.com/showthread.php?t=381284
It's really strange !
Dave

I've been reading everything and it appears that Schaps's new version seems to have this problem sometimes....I have the exact same problem as everyone else (mtty gives me the same results), and flashing a new rom doesn't get rid of it....I hope there is some way to fix this!
maybe I'll try flashing a new radio and see if that helps things....

I did notice that flashing Schaps 4.31 seems to include radio 1.50 and I had changed my anyway to 1.43 as I thought that was better for my area.
Not sure a radio will help. Maybe a different ROM version will ? Maybe 3.54 ?

I have flashed TNT's rom as well and it still has the problem now....I'm flashing a new radio as I type, I'm going to have to reflash the OS too, it just got stuck again as it was restarting.

Just a quick thing, I think I have solved my problem (not sure if it is permanent) by powering the phone off and on. Not resetting, just a simple power off. I spoke to a colleague who said the way it shuts down is different to soft reset (makes sense) and I haven't powered my phone off properly for a long time.
I have tried soft reset a couple of times since doing this and it hasn't gone to the bootloader screen once.
Maybe this is the simple fix.
I will keep you posted.

try to flash OFFICIAL ROM first , maybe there are few bug / missing file when error appear while flashing other ROM.
I hope it will help you both.
rgds,
ermen

Use mtty to see if yo have any bad blocks... I've had a few problems the same as yours and found I had 1 or 2 extra bad blocks, after the 2 "factory standard" bad blocks I got on my jasjam of course. hope this helps...

My fix didn't work.
Not sure what I am suppossed to see when I run "task 2a".
Has anyone had any luck fixing this ?

[Q] Touch Diamond :: permanent reboot :: bootloader update back to Stock SPL imposs.

Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers

same problemm
Same problem. Any help?

tekata said:
Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers
Click to expand...
Click to collapse
Any chance to MTTY? Might help, just guessing...
Or try to flash a new radio ROM as the wifi hardware might be stuck in a state that is unknown to the drivers. Flashing a radio is supposed to reset hardware but I may be wrong.
Really guessing here but symptoms shows relation to radio hardware.
Cheers,
Cina.

sspl
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.

Hello, my solution to this was conductive interconnect of metalic parts as you can see here
://i.ytimg.com/vi/UUnH8O-1jII/0.jpg
(of course with http on the beginning, i'm not allowed to post links)
on the left with aluminium tape (sorry for image quality, found it on web).
It also seems that the sim card reader has to be conductively connected with the above em shielding.
Hope it will help

it´s a battery problem ... get a different one and your phone should be fine

Dreamtheater2003 said:
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.
Click to expand...
Click to collapse
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
@edefux
Do you already had such a case? I am not sure, if buying a new battery is economical enough only in order to try, if it works. I admit, it could be the battery. But running the phone with the charger switched on, should show if its the battery or not. I tried with charger on, but obviously this didn't solve the problem. Or do you mean, that in the battery there is some sort of "short circuit", that's confusing the Diamond no matter if the charger is on or not?
@DiamondFlower
Thanks for the suggestion. I'll give it a try, when I tried everything else
This will be the final try before burrying the precious Diamond.
Cheerz

MTTY.
tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
...
Cheerz
Click to expand...
Click to collapse
See this post for MTTY. This is the second post on Diamond ROM thread pinned for easy access anyway. Please search before you post!
If you can enter bootloader mode with VolDown pressed while reboot you're off to go. You can plug in USB cable and you can flash SPL, Radio or any new ROM. I assumed this based on your first post:
tekata said:
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
Click to expand...
Click to collapse
Cheers,
Cina.

it is a battery problem i´m 99,9% sure of it - i had the same case ... it was driving me crazy ... different roms, radios, but the problem persisted - luckily at that time i was working at a cell phone provider and could try different hardware, which finally brought me to the solution to switch the battery.

edefux said:
it is a battery problem i´m 99,9% sure of it...
Click to expand...
Click to collapse
Maybe I'm a bit unlucky, but I've got the 0,1%. Took a new battery, this didn't solve the problem though.

i´m sorry it didn´t work for you ... !

it's ok! it didn't work - actually I could have thought about it wont work: beforehand I sent the item to the mobile operator guarantee team and they returned it back - no warranty of course (due to olinex bootloader which I wasn't able to remove) and stating: Fremdeinwirkung/ Totalschaden (total loss). And because I sent it without battery and they obviously checked it ... suppose with a fresh or "good" battery. And it still didn't work for them, so...
I'll try to open it and see if there is some short circuit around the metal shielding. Maybe I'm lucky then.
Anyway thanks guys about the hints and suggestions!

tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
Click to expand...
Click to collapse
I'm not sure if its called sspl but you can run it from boot loader and it will black out your phone. after that you need flash the new bootloader.
I'm thinking its not a bootloader problem though...