Hi all,
Have been mucking about with my Vodafone v1605 and the new HTC ROM. Had a play with the 'green' theme and decided to try and go back to Vodafon colours etc (basically the Vodafone extended ROM).
So, unlocked the Extended ROM, deleted the HTC stuff and replaced with Voda's. No problem.
When I hard reset the device it appeared to be loading HTC's stuff again???? I hard reset again and this time soft reset before the extended ROM could load. I now had a very vanilla WM5 setup
I now unlocked the ext rom again and went to re-import the Vodafone stuff...but it was allready there.
So - I ran the autoupdate and it stared to run. However, after a few secs it complained it could not find \Windows\vodafone.bmp. I ok'd and it carried on.
After all this I have a semi-vodafoned TyTN.
Anyone know what I need to do?? Does anyone have the vodafone.bmp so I may try again??? Is there an easier way to do this that I am missing???
Thanks - Rich
Some more digging found the following:
By simply taking any of the PNG splashscreens available on this site and calling it vodafone.bmp and placing it in the WINDOWS directory I can get the Vodafone extended ROM to run.
However, with teh ROM run I do not get the Vodafone theme or the phone skin or today plugins (guess they belong to the actual ROM not the extended). I do however get a 3 symbol....
In the end I gave up playnig and went back to the HTC extended ROM. Sure, green might not be 100% me but it's a nice change
R
Questions
Which ROm are you using instead the Vodafone one ?? Did you had screen calibration problems with the old ROM ? Changing the old ROM for the new one fixed this stuff ??
Ok this problem is related to the pre autorun issue that is availavail in the hermas verient....that means not only that the file willbe installed from the extrom bit also a part of extrom is kept in mail ce rom which will install before the installaton of ext rom...you can see it easily as the wait for 3 sec message after a hard reset will came twice the first time for pre autorum and second one from autorun...
now as u using the tytn rom s the pre auorun cnfig is still there which will install the green htc theme and default ie homepage and some other things like hsdpa anaval and some customised operator setting....so it doesnt matter what ext rom you use if u use the tytn main ce rom then u cant ignore them if not u reset just before first 3 sec wait massage and as a result u will not get the complete vodaphone ext rom addons as for vodaphone cd imate too there has some setting which relies on main image not on ext rom...
i think this explainaiton should clear it a bit..
thanks
Related
Having found the excellent walk-through post on how to amend the nbf files so that the correct country code is set, allowing you to change ROMs to a none country ROM, I set about to try it.
And in fact, changing the files, and re-packing them, was not too bad.
Then I ran the upgrade program for the M1000 Orange Dutch (but WWE version) ROM, on my UK O2 XDA2.
And lo and behold, it no longer failed the country check, and proceeded to upgrade!
It managed to erase the current ROM no problem...
Then it started to install the new ROM...
And it got right up to a lovely 99%, and then hung for a while, before the installer program coming back with an Upgrade Failed error, and telling me to soft re-boot and try again.
Soft re-booting brought up the O2 'water' boot image, but with the ROM details etc re-written for the new verison 1.66 instead of 1.60 - but no backlight would come on, and it wouldn't get any further than this.
I had to go into Bootloader mode, to get it to try again.
And after three attempts, it ALWAYS fails at 99% of the ROM install.
So, does anyone have any ideas?
In the meantime, I am back to my O2 ROM, but I was led to beleive, from the tutorial, that ANY ROM could be used, as long as they were meant for a Himalaya device.
So, why does the Orange M1000 Dutch WWE 1.66 ROM, always fail at 99% when run on a UK O2 XDA2 1.60 WWE?
Anyone?
i think that other have don it without failure
could it be the file you downloaded which is a bit corrupt ?
try downloading it again
Sorry for the offtopic question but where did ya get the Orange Dutch rom?
I really would like to get that one...
Cheers
Panja
maybe dutch == danish
both starts with d and ends with h could be a mistake
from what i know the danish orange rom is the only one out yet but of cause i could be wrong
That would be the answer yes...
I am Dutch and check Orange once and a while and for as far as I know the m1000 isn't even released in Holland...
I just rang Orange because I can't get GPRS to work and I told them I have a XDA II, same as the m1000. But they couldn't help me because they don't have any settings for the m1000 yet...
Pretty g*y they couldn't help me
well what you need is really only access point
and depending on orange login and pass
Oops.
I meant Danish.
Second time I have done that this week.
Copenhaagen and Eindhoven - it's becuase they are so close together maybe *lol* ;-)
Rudegar, any ideas who the users were that got it to work, so I can ask them for the patched ROM files and try that?
m8
I got it to work!
Just download the update from the Danish Orange site.
Click here!
Panja said:
m8
I got it to work!
Just download the update from the Danish Orange site.
Click here!
Click to expand...
Click to collapse
I do what exactly?
If left as is, it won't work, as it fails the country check (er remember, it's a UK O2 XDA2 I'm trying to install it on here).
On the other hand, if I use xdatools to alter the nbf file, it allows me to run the install, but constantly fails the process at 99% of the first ROM install...
So, any ideas?
What device did you install it on?
i think he followed this guide
http://forum.xda-developers.com/viewtopic.php?t=8205
That's the very one I refer to earlier, that taught me how to change the country info.
The install fails on 99% though.
So Panja, have you got your extracted files to share if you put it on an XDA2 O2 as well?
Well I've downloaded the ROM upgrade again, and worked through the tutorial steps to change the device settings.
Can I just check something...
I currently have an O2 XDA2, and I am upgrading it with an Orange ROM.
When I enter the device settings, it IS "PH10 O2" I enter as the settings, NOT PH10 Orange, as I want the device to end up as it were. I do enter the device's EXISTING settings Panja, yes?
That's what I have done anyway - entered PH10 O2, so as I speak, it is busy wiping the ROM from the device, connected to my other PC.
I'll be sure to post back here if I manage to get past the 99% new ROM install this time, with a new ROM download, and a new attempt at altering the nbf files...
Wish me luck folks.
NEVER one to tempt the hand of fate, so I will start by saying it's not finished YET...
But it passed the ROM update ok, and now is onto the Extended ROM.
Keep wishing me luck folks...
Weh hey!
Nice new Orange XDA2, if I say so myself.
It looks a bit better, the proper Windows Mobile Boot Screen, than an O2 one, especially with an Orange SIM in...
So now I've saved the amended .nbf files on my PC, so that if needs be and a re-upgrade is needed, I can just run the installer, then delete the real nbf files and replace with my altered ones.
It's just busy doing a Sprite backup restore now - quality. Thanks everyone!
I'll repost back with my experiences of reliability and speed soon if I notice anything untoward...
Oh blast...
I've noticed something straight away...
The new implementation of Cleartype is TERRIBLE.
I can see blue edging to letters all over the place as it attempts to anti-aliase the font.
Previously with the O2 ROM and Cleartype, the letters were smooth, but black throughout...
I seriously think I will either have to forego using Cleartype, or do a ROM re-upgrade back to O2 at this rate.
Thanks for nothing Orange...
After all that, going back to O2 ROM.
Cleartype as per Orange's idea of it, is terrible. Blue all over black text, yellow on the white menu text, and sore eyes all round.
DOH
So now I have to go through it all over again to change the Country Code, to get the O2 ROM back on...
Great...
Sorry I couldn't help ya in time.
I'm sick @ home and didn't check the board till now...
Nice you got it finally to work.
Cheers
Panja,
Did you find the Cleartype as per the Orange ROM, to be unreadable, and full of colour cast?
Also, now that I have gone back to the O2 ROM becuase of the terrible Cleartype with the Orange ROM, do you know if you can just do an Upgrade whereby you only install the Orange EXTENDED ROM onto the O2 current ROM?
I have both ICQ and Messenger, if this is better for you...
I didnt use the cleartype on the Orange rom.
I swapped the Orange rom for the QTek rom.
Happy with the Qtek to be honist...
...Details are best left private, but the unit was one of the first Atoms to be released. it has been upgraded to the Jan rom, and then left alone because its owner was, uh, more chicken than I am. The Mini I used to own will be going to someone else. >_>
I will miss Bigstorage, a small price to pay for (somewhat) limited Wifi and no longer having to fear losing all my data to a power out.
Few questions here:
1. Is it safe to use the Xda-Atom-Exec-ENG-20060721-MOT0822.exe from the FTP yet?
2. Should I use that or the Xda-Atom-ENG-20060426-MOT0822.exe ?
3. Is there a way to disable the message that refuses to run unsigned exes, or is there an exe signer anywhere? I remember it having problems with programs that don't need installation.
Thanks in advance.
...Just got it today.
Apparently it's been through the service centre once, so it's ROM turned out to be the 20060426 one - radio still at RS*49. Still wondering if I should flash for the new radio driver.
I've read through the forums and I think I won't be messing around with the Exec rom for now.
Thanks, all.
i currently using the Atom with Atom Exec ROM version Xda-Atom-Exec-ENG-20060721-MOT0822
and so far until now, no prob at all..
anyone know how to cook WM5 ROM in atom,
cause, i see to other forum, they have the ROM WM5 AKU3.5 into their device,,
why can we (atom) have that to??
Ehehehehehe. Finally took the risk, nearly lost my phone - tho it was easily fixed by flashing over with the same Exec rom again. The ROM I grabbed from the FTP right here on xdadev. <_<
See, a funny thing happened.
I installed the Extrom revealer hack for extra space.
Then I installed SKTools Trial 3.0.75 - and thereafter the Extrom revealer hack stopped working.
So my device asked me this question - "Do you want to format your Storage Card so it's easily readable?"
not wanting to get my 2gig eaten, I removed it, and tried to click NO... only I accidentially touched "Yes".
Whoops.
Everything just stopped working - well, except the phone and basic winDOS mobile 5 apps.
Soft reset - device took ages to boot. Nothing that isn't WM5 native runs.
Hard reset - device went wonky, still booted, but screen got out of alignment. Still usable, but autoconfig not working (detected Sim as jumble of numbers, but phone still works).
Went into device settings -> system info.
Guess what I saw:
CMOS: NULL (WTF)
ExtROM: NULL (WTF)
...correct
...correct
...correct
And upon looking at the Flash Size, I saw 192MB (?!). Fake number?
(No screenshots will be made avaliable. I will NOT do this again.)
Anyways, a reflash put the unit back in full working condition, problem, but I'm still seeing it report that I have 192MB of Flash RAM avaliable. Oy.
Still workink for now, but I hope this won't mess up the system any. -.-
Hi I just bought a Niki locked to T-Mobile. I got it unlocked thanks to Olipro and £5 . I would like to debrand the phone, I hate the "Web'n'Walk" stuff and the T-Mobile splash screen. I just wondered what my options are for doing this and peoples opinions on difficulty and results.
1. Manualy remove apps, and flash new splash screens
2. Load completely new ROM, if so which one, can I get an original HTC one?
3. Any other suggestions?
Thanks in advance.
Grab the HTC WWE rom and flash that or you could try Tom's rom
I have "debranded" my italian TIM Niki without even reflashing any ROMs:
1) Hard reset your device
2) Go through screen alignment and startup settings
3) Soft-Reset before the extended rom is installed (you will be informed by a dialog box with a 3 seconds timeout, so be quick!)
Please let us know whether it ever worked at all.
Ciao!
It doesnt remove the bootscreen though or the ugly pink icons and when you hard reset again you have to pull out the battery lol
Hi dtm203
Grab the HTC WWE rom and flash that or you could try Tom's rom
Click to expand...
Click to collapse
Where can I find the HTC WWE ROM?
Thanks
go to this:
http://www.4shared.com/dir/5678614/f5139b2c/HTC_Nike.html
its a guy on the forums hes doing great work on the Nike.
Kurt
I looked through as many posts as I could but maybe I'm not doing it right.
I flashed the android 2.2 ROM on my HTC HD2 from O2 but now I need to go back to windows 6.5 which was originally there. I dont have the official ROM and I would be very thankful if someone could send me the correct link to how to do it or how to get the official ROM.
Just a reminder I have an O2 HTC HD 2
Thanks to anyone and everyone who helps !
you didnt say which country, so i will assume UK.
first, run hspl.exe (the one you used when you installed hspl) but this time choose 2.08.0000
then
get 1.72 from htc website
http://www.htc.com/uk/SupportDownload.aspx?p_id=297&cat=2&dl_id=960
phone into bootloader, connect usb, run the 1.72 rom.exe
If you didnt mean UK, go to teh htc website, choose your country, choose your phone, click support, downloads, change the dropdown from 'all' to 'rom updates', find teh one that says o2 and use that.
thanku
thanks bruv ... ill look into it !
i still have an issue that the phone keeps restarting or gets stuck in a while !
There's a 3.14 rom, you could try that, but it could also be faulty....
Dear XDA Developers community,
my father recently gave me his old HTC HD2. It had its factory default stuff. I wanted to download some apps and play around with it, so I downloaded some apps from the marketplace. As soon as I downloaded a free Sudoku game, and ran it, the phone stopped responding. I tried to do a soft reset, but the phone did not respond either (it was stuck at the menu).
Now, I may have done an error: I removed the battery, instead of performing a Hard Reset. When I turned it on, it started rebooting in a loop, being stuck always at the HTC white welcome screen.
I decided for a Hard Reset. Well, it always gets stuck at the bootloader screen (the screen with the 4 colors).
So, I researched a bit, and found out, you can return to its stock ROM, eve with a stuck bootloader.
Well, I downloaded many old ROMS (the Rom before the problems was a 1.66 one), and ran the RUU through USB. But it always gave me a Incorrect vendor ID error (I think it was 194), so the update would always stop at 1%.
I even tried a 1.43 ROM.
I tried many WWE version Roms, but they don't seem to work. My father bought the phone on Amazon US, with no special contract or phone lock, so I guess it has to be a WWE, so I don't know why the RUU says it's incorrect.
I have seen other threads that have some similarities, but my exact same problem has not been addressed.
I would be very happy if you could help me, since I do not want to spend any money on repairs which I could probably perform with help of the community
I would be most glad to give more information if needed.
Many thanks in advance.
Edit:
The issue was resolved by installing HSPL4 on it, and then using a WWE 1.66 ROM on it! Silly me for not trying that earlier!
glad you sorted it, , to explain why it wouldnt work, you were not using the correct rom for that phone.
Your first clue would be the 'invalid vendor id'. An 02 phone (for example) will only take o2 roms, a tmo phone tmo roms, a voda phone, voda roms. Only unbranded phones take pure wwe roms, so for example
ruu leo htc wwe 1.66.405.2
see it says HTC in the filename? its for unbranded (not sold by a network) hd2s only.
I guess you have a branded one. (even if its been unlocked, the rom lock always remains, which is why we have hspl)
Incidentally, you only had trouble because you initially flashed from sd card, and step 1 in teh sd card flash is hspl gets removed, the phone restarts to continue flashing but because hspl is now gone, it fails. Had you flashed from usb teh first time, it would have worked.
samsamuel said:
glad you sorted it, , to explain why it wouldnt work, you were not using the correct rom for that phone.
Your first clue would be the 'invalid vendor id'. An 02 phone (for example) will only take o2 roms, a tmo phone tmo roms, a voda phone, voda roms. Only unbranded phones take pure wwe roms, so for example
ruu leo htc wwe 1.66.405.2
see it says HTC in the filename? its for unbranded (not sold by a network) hd2s only.
I guess you have a branded one. (even if its been unlocked, the rom lock always remains, which is why we have hspl)
Incidentally, you only had trouble because you initially flashed from sd card, and step 1 in teh sd card flash is hspl gets removed, the phone restarts to continue flashing but because hspl is now gone, it fails. Had you flashed from usb teh first time, it would have worked.
Click to expand...
Click to collapse
Thanks for the answer Samuel. I got the phone to work again, and I even loaded NAND Android from the DFTeam.
Although the ROM runs just perfect and I love it, now my Volume Up key has stopped working.
I could not post on the Development section, so I guess I won't bother anyone, and will just post it in this thread.
It is a minor issue, but it's still is annoying. I found on the forums problems with the key with other models, but not with the HTC Leo.
Maybe someone has heard of this. Again, thanks in advance!