Related
I have an xda exec running fine with the rom it first came with. Should I upgrade to the new rom and if i do how will it improve the performance of the exec.As it seems to be working fine with tom tom etc. would i be best to leave to leave it as it is. Not being very technical i would really appreciate some advice.
If you are not very technical and your device is working fine then you should probably leave well alone. As the saying goes, If it ain't broke, don't fix it.
Melty said:
If you are not very technical and your device is working fine then you should probably leave well alone. As the saying goes, If it ain't broke, don't fix it.
Click to expand...
Click to collapse
Sound advice, but I think the attitude of most of us here on this forum is more like "if it ain't broke, fix it anyway"!! On a more serious note, there doesn't seem to be much of a difference between the launch rom and the update, but it really is a very simple operation to update the rom, it's nothing to be afraid of.
Fin
I will stick with the first rom and wait a few weeks to see if itis upgraded again. Seriously i have already hadsome real disasters with rom upgrades particularywith theearly pocket pc's.Today i invested in the xda mini s whichi will run as mymain phone.we really got the exec for tom tom and its use in a motorhome.I have managed to upgrade an imate jam in the past but it was very hit and miss.If i need to upgrade the new device i will certainly ask for advice on this forum-its members are so helpful.
best wishes
patricia
Upgraded ROM last night.
Took about 20 mins as suggested onscreen.
Seems quicker now but have yet to reinstall all apps which will consume some memory even if forced to SD.
Gift 1 month ago. 'Evaluated' it just for testing purposes for a week you understand. But I have had to wrap it up for xmas again.
John
upgrade
Thanks for the information. I decided to upgrade tonight after you let me know how simple it was. It all went fine. I even managed to install tom tom and planmaker afterwards and all seemsto work fine. anyway it was really helpful to know you had managedthe upgrade so successfully.
best wishes
patricia
I'm glad it all went well!
Anyway happy christmas-thanks for all the support.xda exec is working fine.i certainly wouldn't have upgraded without the advice.the exec is an amazing bit of kit.
best wishes patricia
When I try to get the download file from the O2 website, I get as far as inputting my IMEI and phone number but then clicking 'proceed' gives a page not found error.
This happens even if I try a different XDA (I have an XDA IIi).
Any ideas please? I assume it's a problem at my end rather than the O2 site down?
mdrandall said:
When I try to get the download file from the O2 website, I get as far as inputting my IMEI and phone number but then clicking 'proceed' gives a page not found error.
This happens even if I try a different XDA (I have an XDA IIi).
Any ideas please? I assume it's a problem at my end rather than the O2 site down?
Click to expand...
Click to collapse
Try this software update link from O2 site: http://www.my-xda.com/xdaexec_soft3.html
Upgrade Problems
Merry Christmas everyone
I tried to upgrade my dopod 900 original rom 113.63 to rom113.82(XDA exec upgrade v113.118)and had failed. I tried using the MaUpgradeUt noID without success
The messages errors are ERROR 101, 150 and 201
My dopod900 is now FROZEN for christmas
Please kindly advise...Thanks in advance
Re: Upgrade Problems
leslie lee said:
Merry Christmas everyone
I tried to upgrade my dopod 900 original rom 113.63 to rom113.82(XDA exec upgrade v113.118)and had failed. I tried using the MaUpgradeUt noID without success
The messages errors are ERROR 101, 150 and 201
My dopod900 is now FROZEN for christmas
Please kindly advise...Thanks in advance
Click to expand...
Click to collapse
Don't panic yet. I had trouble myself considering I even have an O2 EXEC who actually released the update. You are not the only one. It takes about 2-3 tries before the computer and the Universal becomes connected. Just follow the suggestions on this thread: http://forum.xda-developers.com/viewtopic.php?t=36115
Upgraded finally but still screwed
My dopod900 finally upgraded by using MaUpgradeUt no ID on the xda exec .rom133.188 with the final screen CONGRATULATIONS....BUT as instructed to boot....on soft resets many times it is still remain in the bootloader screen
I tried many hard resets it is still likewise ie.stuck in the bootloader screen.
Please guide????What should I do for christmas to get my universal working again?????
Re: Upgraded finally but still screwed
leslie lee said:
My dopod900 finally upgraded by using MaUpgradeUt no ID on the xda exec .rom133.188 with the final screen CONGRATULATIONS....BUT as instructed to boot....on soft resets many times it is still remain in the bootloader screen
I tried many hard resets it is still likewise ie.stuck in the bootloader screen.
Please guide????What should I do for christmas to get my universal working again?????
Click to expand...
Click to collapse
see your pm
I must convey my sincere thanks to all the wonderful people for trying to help.
It is definitely befitting in the spirit of xmas .
I reflash a 2nd time..and when I reset after finishing the flashing the screen reverts to the bootloader screen with top...serial and bottom...v1.00
I tried the hard reset after failing in the soft resets over 6 to 7 times. the screen also reverts to the same bootloader.
I had flash 4 times n the soft resets,cold resets n finally hard resets revert the screen to bootloader ie top-serial...bottom-v1.00.thanks once again
maybe on boxing day luck may be better....meanwhile xmas still remains very cold on my universal dopod
leslie lee said:
I must convey my sincere thanks to all the wonderful people for trying to help.
It is definitely befitting in the spirit of xmas .
I reflash a 2nd time..and when I reset after finishing the flashing the screen reverts to the bootloader screen with top...serial and bottom...v1.00
I tried the hard reset after failing in the soft resets over 6 to 7 times. the screen also reverts to the same bootloader.
I had flash 4 times n the soft resets,cold resets n finally hard resets revert the screen to bootloader ie top-serial...bottom-v1.00.thanks once again
maybe on boxing day luck may be better....meanwhile xmas still remains very cold on my universal dopod
Click to expand...
Click to collapse
Normaly no problem: have you removed your SD and SIM-Card? And also use the original usb-cable!
It'll work => at least at the second try!
Teja
Hi guys. I know I know, wrong place, but maybe some one here could help too! Just maybe.. You guys are very smart peps here. You've helped me with many XDA's I own. And I'm just hoping you wouldn't let me down this time too. Any way I’ve killed my eten (typhoon my guide m500 German) and hoping some one could help me to bring it back to life. Please understand that I have exhausted all my resources in order to find the solution my self but came up empty handed. I have read every single post in this forum as well as few others in order to find the solution. And now I am hoping that some one could help. I may have overlooked some little but important piece of info. Please except my apologies if this request may be annoying.
This is what happened and what I’ve done about it.
I’ve got Typhoon MyGuide m500 (E-Ten m500) Original rom was German.
The reason I say “was” is since I had german OS that I can’t read it I wanted to flash the device with WWE Rom. But the device would not accept any other rom and at the time of reflashing through RUU, I get message “the os image is not compatible with your device”. I understand a lot of people have this problem, but still, some succeed. I have tried all the possible roms that are available there. I’m sure you’ve heard that before too Finally I’ve succeeded in flashing CHT WM2003 rom that came with WM 5 Rom update for downgrade purposes. But, I can’t read chinese either so I tried to flash wwe at this time. Hoping that chinese rom would allow upgrades in different language. But the upgrade went bad I’ve ended up with formatted e-ten with no OS installed. It was only showing white screen when turned on or it would boot into boot loader when soft reset and power was pressed.
At that time, since the device would not boot and I couldn’t active sync it, I’ve tried SD flashing with RescueDLX.bin. As well USB download utility. It flashed the device, but I was stuck at the green m500 screen when tried booting. So that didn’t work either. I’ve tried SD flashing with temp.dat saved as .bin from all possible roms, including the first chineese that worked once for me. But again, I got “the os image is not compatible with your device”
Well, here is where I’ve screwed up big time. Since the rescueDLX.bin was actually flashing into my device, and I was not getting “the os image is not compatible with your device” message, I’ve opened the rescueDLX.bin with Hex Editor, copied first 400 bytes of the header, then using Hex Editor opened the temp.dat from WWE rom update that I wanted to use and pasted this 400 bytes from rescuedlx.bin over the first 400 bytes of temp.dat file and saved it as a bin. Then copied on SD card, put it in the device, entered into the boot loader and started flashing process. Amazingly, I didn’t get the “the os image is not compatible with your device” message! But worst thing happened The boot loader was going through all the check lists and everything was ok but device froze at the last one, “looking for FPTP” or something like that.. Apperantly I copied to much stuff or it just plain incompatible. Well, now my device would not even load into the boot loader! I think I’ve erased it too So no more updating for me, that is for a sure not through RUU, not through USB Update Utility that I found on etens forum, and not even through SD with devices internal boot loader. There isn’t one anymore
So here we go, I’ve got really nice looking paper weight Oh, and I can use it as a flash light too When turned on, the screen lights up with bright white light
So any way, can any body help?! Is there any way to revive this thing? Or the road is straight to manufacturer? I don’t think I even have a warranty on this device; it’s in brand new condition, but its second hand. So I have only one hope that some smart gurus of this forum would show mercy and would help! Like I said, I’ve researched all over the internet, all forums, even xda developers and spv developers forums, but this is different device. Deferent rules… But I know it’s doable, I’ve seen posts that others did it! So please, share how you guys did it!
Thank you in advance. And sorry for such a long post!
this is the .cab that Ace Hellas gave to us before 10 minutes from HTC to solve the sd corruption
i do not have the problem but i hope to help all with this...
And I run and install all vague .cabs on my device!!
What is this supposed to be and where did you get it. Are you implying this is the fabled HTC fix, yet for some reason HTC have chosen not to release it themselves, but you have leaked it??????
Having just gone thru the SD card failure routine (followed by neccessary total rebuild!!), I'm keen to try anything to fix this "fault" on my O2 Orbit.....However, I'd love to know what this does before implementing the "solution".....
....I think what I'm trying to say is: if this is the solution then what was the definative problem? and what does this solution do?
Hope you can help and I really hope this fixes it...many thanks!
this file is a patch as i said is in the official web page of htc in Greece and it is on the site since 30 minutes
more info i will tell when i have something new
here it is but you must put first the imei of the ppc to have access
http://www.qtek.gr/forum/showthread.php?t=4081
mastelos said:
this file is a patch as i said is in the official web page of htc in Greece and it is on the site since 30 minutes
Click to expand...
Click to collapse
Thanks mastelos,
This file is only on Greece Qtek/HTC forum but there is no information about it on P3300 updates page. Maybe you could find out why? Is this an unofficial or made by Greek programmers patch - not send to HTC headquarter yet?
Cheers,
ace hellas doesnt put unofficial updates!its from HTC...they didnt say how it works..i just install it at my P3300,i hope it works!
Ok has anyone tried this yet??
Downloaded but not installing until I've seen some release details from HTC. I also am not sure if I should remove SDsentry before I install it....
LargePig said:
Downloaded but not installing until I've seen some release details from HTC. I also am not sure if I should remove SDsentry before I install it....
Click to expand...
Click to collapse
I too have downloaded it but like you, I don't want to run it until either (1) HTC release some details or (2) somebody who has been brave enough to try it confirms that it doesn't do anything malicious.
I can't think of any reason why you would need to remove SDsentry first, though. All this does is put a file called sdsentry.txt in various important directories and then warns as soon as it has any problems reading any of these files (which suggests that the microSD card is corrupted).
guys i have it install for 3 hours now..
its nothing malicious..
for the corrupt problem until now its ok but its very soon to say that is really solved!
Ace Hellas is the official HTC provider in greece,i dont know why HTC didnt put at their site the patch yet but its real...
Yeh, I just loaded it up. Normally most cab files I install I get some message about unknown publishers etc. Not with this, It looks legitimate to me. I think htc watch this space so we can do an evaluation for them.
One more thing that has really been bugging my orbit has been the soft reset loop, after installing this cab my orbit went through only one cycle, maybe coincidence but that is the first time in months that that has happened.
I just installed it on a german p3300 - seems to work fine after install - i will see if there is any sd corrupption in the next weeks
Update:
Got bit late last night, But this morning orbit is 100% ok, again almost every morning I normally have a slight corruption in program files. Today all is good.
Not sure but I also think that maybe the thing is even reading the card a bit faster than it was.
Just a thought obvious to everyone, but Artemis was a Greek goddess, HTC must like Greece for some reason.
uniqueboy said:
Update:
but Artemis was a Greek goddess, HTC must like Greece for some reason.
Click to expand...
Click to collapse
maybe this is the answer.....
well isend yesterday an e-mail to htc Greece to explain me if this an official or custom i'm waiting for answer
from my experience i believe this is an official patch because htc Greece never
gave to us a non official rom or anything one year now i use their products
i do not install the file because i do not have the corruption problem and i have 3300 from 27/9/2006 us you can see on my previews posts
i believe that they (htc Greece) recieve the file on friday afternoon and put it immediately on their site and from monday all the htc sites will have the patch
*sorry for bad english
Maybe not the UK, bank holiday monday.
I installed the patch last night. Now, almost 24 hours later, and after using my Orbit a lot, I have not had a single warning from SDsentry!
Installing the patch required a reboot. It shows up in the "Remove Programs" menu if you decide you want to get rid of it. So far, I can't see any reason why you would want to remove it.
Looks like Well Done, HTC!
Well after months of never having card corruption, it hit me last night, and as good to form, my backup on the PC was out of date. Thankfully the damage wasn't too bad.
So I've installed this patch, which goes on smoothly, as said above, it is signed so you don't have to agree to install it, and it is listed in remove programs as "HTC Patch DrvUpdate".
Theres no instant way of testing it I guess, as I had to wait months for my first corruption anyway.
Installed on 2 Orbits - no ill effects, I got "the bug" about once a week previously, will post back here if it happens again, fingers crossed...
Installed the Patch wich consists of the following file :
\windows\omap850_sdhc.dll
so that the original Rom files being superseded ....
Will see .....
Please can some one help me.
I have tried alsorts of stuff to get my UNI back to the O2 operating system.
I used the MTTY thingy and cleared it out I have done so much but I keep ending up with a multi coloured screen and thats it.
I can load WM6 operating systems OK and the seem to work.
I have tried the Original O2 shipped ROM and the upgraded ROM but no luck.
I don't want to upset people by being lazy because I promise I have looked but I cant find the solution.
Please Help Me
I am not sure but it seams you have the same issue like the guy here
http://forum.xda-developers.com/showthread.php?p=1432943#post1432943
Are you guys sure that the ROM that you have downloaded "good"
Hello All,
I have been upgrading mine and a few friend's dash's to the Kavana 6.1. My Dash however has a hardware issue (the ear piece speaker is distorted) and is being replaced through warranty service. My new dash arrived today, and I know I need how to re flash my software back before I send it to T mobile. I downloaded TMO_1.22.531.6 from the official rom sticky. However when I open the zip file it is a RUU_signed.nbh file contained inside.
I am not sure how to flash with this file. I assume it requires some other software in order to flash it. I have tried numerous searches and can't really seem to find what I am looking for. I really got spoiled by the simple EXE launchers included with Kavana rom's.
Any help would be VERY appreciated.
Thanks!
You need to go to this thread .
On the bottom of that thread download the files needed zip file, add (copy or move) the .nbh file in that folder after you unzip it of course.
Run the romutilityupgrade.exe file and follow the directions as you did before.
Why not go to Tmobile support site and download the official Rom and install that ?
Thank you for your help -- I actually tried it both ways.
First I tried to use the t-mobile website and when I attempted to run the exe it always failed out on error 202 which of course is usb (even though it was connected). So then I tried it the way by grabbing the software recommended. When I ran the AUTO batch script (similar to the way I installed Kavana), it installed just fine. So that being said, I got it downgraded. If you can't tell I don't have a real great understanding of the actual upgrade/downgrade process.
Issue is tho, when I first got the phone, the initial splash screen was t mobile if I remember correct, but when I upgraded to Kavana it changed it to the HTC logo. Well after the downgrade, it still boots with the HTC logo instead of Tmobile. Will that be a dead give away that I flashed the phone when warranty center receives it? If so how could i change it?
That's definitely gonna raise some eyebrows.. but I kinda doubt they'll notice it. Just look at the idiot phone techs you get when you call their tech support line... I don't know how you would change that...
chris300zx said:
Thank you for your help -- I actually tried it both ways.
First I tried to use the t-mobile website and when I attempted to run the exe it always failed out on error 202 which of course is usb (even though it was connected). So then I tried it the way by grabbing the software recommended. When I ran the AUTO batch script (similar to the way I installed Kavana), it installed just fine. So that being said, I got it downgraded. If you can't tell I don't have a real great understanding of the actual upgrade/downgrade process.
Issue is tho, when I first got the phone, the initial splash screen was t mobile if I remember correct, but when I upgraded to Kavana it changed it to the HTC logo. Well after the downgrade, it still boots with the HTC logo instead of Tmobile. Will that be a dead give away that I flashed the phone when warranty center receives it? If so how could i change it?
Click to expand...
Click to collapse
you can go here--> http://forum.xda-developers.com/showthread.php?t=341753 and follow instructions on post #1 to reflash the tmobile boot spash screen. i've tried it and i have the t-mo splash screen now.
Thanks for the help! I actually was able to get it to successfully go away by stepping back another version to .4 from .6 -- this replaced the screen and returned it back to the way it came. Coincidentally, after looking at the replacement units software version and confirming it was .4 I feel fairly confident everything will be fine, oh and now everyone doesn't sound like a robot!
Thanks again,
Chris