I have an XDA IIs from O2 and a Qtek 9090 from Vodafone (fairly litlle tinkering from Vodafone).
I want to unlock the XDA IIs (as does everybody else) but isn't the SimLock part of the Radio Rom, in which case cant I jusr replace this with the Voidafone Rom and hey presto!!
I am sure that this is not as simple as I have suggested, or everybody wouyld be doing it, but can someone explain to me where the SimLock subsystem is and therefore where I should start to poke, to unlock it.
I quite liked the idea of sending millions of AT commands to the wireless modem, but that sounded too easy as well.
I know what the Extended Rom does, and the Rom Rom (presumably OS), and in general I know what the radio Rom does, but if this is all there is then I cant see where the SimLock stuff would be held???
If you could reply I'd be grateful, and if anybody reads this and cracks an unlock, drop me a line as well.
Thanks in advance
During a lot of months I have been wondering this. In my opinion, I think that simlock is in the extended rom because it contains special programs from your provider, but I am not sure. The definite clue would be to change all the operating system (radio rom, OS rom, and extended rom) for other (for example, qtek 9090). If somebody knows how to do this and he tries it, please let us know. Thanks.
The code in the CE ROM (Or possibly the radio rom?) reads information from the phone hardware to detect if it is locked or unlocked and merely displays a message to the user indicating its current status when you try to use an alt network sim. The lock status, network locked to and unlock code is stored in a separate flash area of the phone hardware within the XDA IIs - not in one of the standard 3 roms.
This means that no matter what "standard" rom you put on the XDA it will not suddenly become "unlocked" (As I have had numerous different roms on mine since I purchased it - radio, ce and extended rom).
Unfortunately the area of the phone containing this information cannot easily be accessed and requres a code based on the IMEI number of the phone to access. Without the algorithm used to calc this code (Different for each phone type ie alg. for XDA II is different to one for XDA IIs) we cannot unlock the phone!
That said, I believe that the phone itself may not actually prevent the calls merely the firmware in the radio rom after detecting that the phone is "locked". Therefore, I believe it MAY be possible to hack the rom to allow it to be used on any network. PLEASE NOTE THAT I DO NOT KNOW THIS LAST BIT OF INFO FOR SURE, IT IS SPECULATION ONLY AS A POSSIBLE WAY AROUND THE SIM LOCK....... NOW WHERE IS MY HEX EDITOR!
A summary so far
Ok,
So the simlock code is contained in a fourth ROM somewhere in teh device that we dont know how to get to. The radio ROM then somehow reads to see if it is locked, and if it is prompts for the unlock, and if not then allows you to make a call etc.
This fourth ROM is likely to be pretty fixed, like the deviceID and is presumably unaccessable to anything without opening the device up, removing the chip and hitting it with a lightning bolt.
So where does that leave us. The screen that comes up about SIMlock, enter the number, which interestingly enough says that I have tried a large negative integer times, and then locks up permanently (or so it seams). This bit must be in one of the accessible ROMS, as it is too Windowsy for anything hardware wise.
This screen must call some other function that tries the unlock code into the unaccessable chip. It would probably be easier to attempt to remove the retry timeout and then retry millions of times, either with a simple sendkeys type function or with something cleverer. Or alternatively find the function that SIMLock calls to the hardware.
I am being creative here, hoping that someone can step in and be a little more factual. Anyone....
On the XDA II, if you unlock it, can you lock it again?
Think of this fourth "rom" more as as a type of BIOS with basic hardware call functionality with windows and radio rom sitting on top providing code to access the "BIOS" for radio functions (Bluetooth, GPRS, WiFi, GSM etc) and hardware functionality (LED's, buttons etc). It has a form of NVRAM with IMEI number stored as well as SIM locks etc....
Related
Hi , I'm quite new to this so please be gentle
ROM Version - 3.17.03 ENG
Rom Date - 05/15/03
RADIO Version - 4.21.00
Protocol Version - 32S54
I cannot get the XDA to pick up a signal from my ORANGE Sim card, The SIM works in another phone, what could the problem be. When I click on the antenna I get 'No Signal'
Also the power screen does not display the battery meter, instead saying Battery Power remaining unknown
Can anyone help me please
Thanks in anticipation
The phone is probably locked, it is best to make sure you have a working phone before flashing it, try an o2 sim card, if that works ok then download the special edition rom, flash your phone with it and will unlock itself, you can then upgrade to wm2003 or other flavors of rom.
There's a model number on the back of the XDA, on my particular model it's on the upper left corner (don't know whether the position is universal).
It will either be PW10B1 or PW10A1. Which is yours?
Then go to Start/Settings/System Tab/Device Information/Identity Tab. Does the Hardware Version shown here agree with what's on the back?
---
A North American XDA (PW10B1) will only operate on one of the two European frequency bands.
A locked phone asks for an unlock code when a foreign SIM is inserted. I don't think you ever get to "no signal."
You are right pdhenry, i think i was half asleep when i replied to that, i also have broken ribs so i claim indemnity from any nonsense i may have typed due to malfunction of body and brain.
Hi,
I'm looking for a software to manually lock my Qtek 9090 on a specific GSM cell (or a specific antenna, somehow). It's very easy to do such a thing on my old Nokia using the hidden menus, but I never found a Pocket PC application that can do that. Any idea ?
Hi yannl,
this shouldn't be a big deal for those how know how to program such a thingy. I assume it should be possible to block the phone program from calling (or even simpler and uglier simply to kill it's process) when you are not in the "right" cell.
As dutty's cell profiler is able changes diverse settings or even launch apps, etc. depending on the cell you're in, it shouldn't be too difficult to realize your wish...
HTH,
BGK[/url]
Thanks. I contacted Cell Profiler to ask them about a feature like that. But I'm very surprised that no software around allows to lock on a cell.
why would you like to do so ?
locking phone to a specific cell/BTS/WTS
AlCapone said:
why would you like to do so ?
Click to expand...
Click to collapse
please tell if there is any way to lock the phone to specific Scrambling code or a BTS, needs it for some testing.
hey guyz..
the scene is set, dont want to tell anyone where it happened by whom and ofcourse who got robbed but here's the story.
User had an o2 Xda II, customized rom, with IIWPO Theft Control installed in the rom, so that means hard reset wont wipe IIWPO out of the pda.
Robber comes puts a knife on the user's throat takes away cash and the pda, user gives it happily thinking she will get a msg on the other number with all the info of sim changed.
4 days pass by no info come's and the pda is sold or forwarded to someone else or whatever. END OF STORY.
now how did the user not get a msg of the new sim info.
1. SIM WAS NOT CHANGED.
2.SIM CHANGED BUT NO CREDIT IN NEW SIM.
3.BATTERY TAKEN OUT PDA TOTALLY DEAD TILL NEW CUSTOMER GETS IT. ETC ETC.
WHAT CAN BE DONE.
ok guyz this is the part where i would like allll the geeks & gurus to put in some effort, i know it will be tough but i have a feeling its not impossible.
CAN UR,LL UPDATE IIWPO IN SUCH A WAY THAT WHEN WE ARE FEEDING OUR NAME AND OTHER INFO IT WILL ALSO ASK FOR A SECURITY PASS TO BE PUT IN, SO THAT WHEN ROBBER CHANGES SIM THE IIWPO RECOGNIZES THE SIM CHANGE AND LOCK'S THE PDA AND ASKS FOR THE PASS, AND WONT UNLOCK TILL PASS PROVIDED, REBOOT WONT HELP.
Now ofcourse the robber can be anyone, so the robber plans to hard reset and still the device would recognize the sim change and ask for pass now so annoyed he plans to flash the device and what happens after that all of us know.
To prevent this THE GEEKS & GURUS can just build a small security patch that can wont allow flashing of device till pass given, it would work like this, we flash our device for the first time install IIWPO and the NEW SECURITY PATCH (with passwords) device is robbed, robber changes the sim gets pass error he gets pissed and tries to flash the device and that clever software would not flash the device till pass provided, this would prove that all the efforts the robber made to steal the device are gone to waste.
And ofcourse someday someone might put in a sim with credit and we would get the info.
NOT FORGETTING CHARLES WARNER FOR THE GREAT WORK HE'S PUT IN FOR ALL xda-developers.com USERS and also giving the IIWPO to us for free, REALLY APPRECIATE YOUR WORK SIR !! THANKS ALOT.
no one interested in being secured ?
I think the IIWPO idea can definitely be improved, BUT: It will never protect you from being robbed.
The true advantage of IIWPO in its currect form is to be able to get track of the 'new' owner of a nicked device. In the end: someone will put in his/her sim and then its just bing!
All other enhancements will just make sure noone else gets to use the device. Sure an improvement, but less important to me: I just want my device back and get the thief nailed!
Interesting...
But I think you have misunderstood how IIWPO works.
IIWPO does not detect if someone changes the SIM card. It ONLY acts when the someone changes the Owner Information (Start/Settings/Owner Information), so no matter what SIM card there is, as long as it has credit it will send an SMS to the recipient's phone number. That's the beauty of it, that it silently sends the SMS with the 'new' users data so there is a slight chance of knowing who's the 'new' owner.
But! This is by no means fool proof. It's what they call 'protection by obscurity', so if a savvy robber knows how to reflash the device it will get away with it no matter what features we can integrate to IIWPO.
That's one of the cool new features of WM5.0, that we can at least know for sure that our data is SAFE by wiping the info remotely if necessary.
Just a thought.
Rayan
edsub said:
The true advantage of IIWPO in its currect form is to be able to get track of the 'new' owner of a nicked device.I just want my device back and get the thief nailed!
Click to expand...
Click to collapse
Rayan said:
so if a savvy robber knows how to reflash the device it will get away with it no matter what features we can integrate to IIWPO
Click to expand...
Click to collapse
ofcourse this is why we all love IIWPO cause it sends use a msg, and ofcourse even if someone was to modify IIWPO iam sure that this feature would'nt wipe out.god forbid you get robbed u get a msg frm the cell but you for some reason cant track the person or some other c#@p...and the pda is gone....WHY caz it only sends sms it does not block the screen....if you were to have a feature which would jam or freeze the pda on change of the name then the pda would be useless to the robber nothing much he could do....unless he knows how to flash it...now comes a part where we can do something about not flashin the device with out a pass....this would totally make the pda useless to the robber and would also keep sendin us msgs and secondly the robber maybe maybe next time might think twice before robbing a pda and might go for something else
How about a device that would be installed internally to the xda and if it is stolen and a different sim/different user info is entered and the person makes a call it fires a large captive bolt which nails the phone to the head of the user, it then adjusts itself to full volume with all lights flashing and announcing "This is a stolen phone...call an ambulance...or hearse".,
cruisin-thru said:
How about a device that would be installed internally to the xda and if it is stolen and a different sim/different user info is entered and the person makes a call it fires a large captive bolt which nails the phone to the head of the user, it then adjusts itself to full volume with all lights flashing and announcing "This is a stolen phone...call an ambulance...or hearse".,
Click to expand...
Click to collapse
tht would be great..... are u goood enough to build something like tht ?
Rayan said:
But I think you have misunderstood how IIWPO works.
Click to expand...
Click to collapse
I perfectly understands the IIWPO functionality. It was me who put together IIWPO for other devices than Wallaby.
Let me explain how my earlier post should be interpreted: Sure it is triggered by the change of owner info, but most thieves (or buyer from a stolen device) will put in another SIM (simply because they dont have the pin of the stolen sim or because the stolen sim is blocked by the network). Thus: As soon as the 'new' owner puts in a SIM AND he/she has changed the owner info (and every one does that!) the sms is sent.
Also: Eventually a thief might flash a device, but ost certain a thief (or buyer) starts it up to test whether its working or not.
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve
edsub said:
Rayan said:
But I think you have misunderstood how IIWPO works.
Click to expand...
Click to collapse
I perfectly understands the IIWPO functionality. It was me who put together IIWPO for other devices than Wallaby.
Let me explain how my earlier post should be interpreted: Sure it is triggered by the change of owner info, but most thieves (or buyer from a stolen device) will put in another SIM (simply because they dont have the pin of the stolen sim or because the stolen sim is blocked by the network). Thus: As soon as the 'new' owner puts in a SIM AND he/she has changed the owner info (and every one does that!) the sms is sent.
Also: Eventually a thief might flash a device, but ost certain a thief (or buyer) starts it up to test whether its working or not.
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve
Click to expand...
Click to collapse
Sorry edsub, I should have specified to whom I was refering to (zairyaab) when I wrote that comment.
Best regards,
Rayan
np m8
edsub said:
It was me who put together IIWPO for other devices than Wallaby.
Click to expand...
Click to collapse
Can you explain what should I change in the cab to make it work on other devices (Like ETen M500/Torq P100)?
edsub said:
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve.
Click to expand...
Click to collapse
Yeah, but still I would feel somewhat better if I can at least call the thief/buyer and shout some expletives if he/she refuses to cooperate!!! :twisted: :lol:
Best regards,
Rayan
i have my girlfriend's number as my report number.. what if were together and we got robbed both our phones are taken away.. a multiple report number would be a good addition to IIWPO
The changes I'd like to see done to IIWPO include:
a) not using "IIWPO" or 'xda-developer' in the registry (user customisable registry key)
b) user customisable executable file name (IIWPO_startup is like a dead giveaway)
c) not storing owner name & number 'in the clear' (a simple XOR to hide it would be just as effective)
d) a hash of the entire owner info page (not just the last name) so unit will resend an SMS if any info changes
e) a new sms is resent after a preset time (eg: every 24/48/120 hours for example), regardless if owner info has changed or not.
I also like the idea of multiple number reporting.
a,b,c) Considering the concept of IIWPO is 'security by obscurity'; it will help if one could hide it more effectively. (no one is going to bother too much about bluetooth.exe or msn_update.exe in the startup folder for example...)
d) Most people get their name right; then meddle with the other bits of information as time goes on - it'd be good to get 'updated' info as and when it happens.
e) Consider it a 'keep alive' thing, so we'll know the unit is still in use, and can continue to keep in touch with the new owner =) I've no moral issues burning up the credit of someone who refuses to give me back my property either. =P
If nothing else, we'd be able to know when the unit gets reflashed, and can quiety say goodbye to our unit after not hearing from it for a while... =(
Is IIWPO still being maintained by the author, or anyone on xda-developers? If not, is the source available? I might be interested in following up on it (time permitting...)
Edited to add: A really vicious version of the IIWPO would possibly send out:
a) phone numbers stored in the SIM card
b) phone numbers stored in the addres book
c) recently dialed/received phone numbers
d) recently sent/received SMS phone numbers
Not all in one go; but in bits and pieces (eg: every 20 startups; send phone numbers of last 5 SMSs sent/received + last 5 phone calls dialed/received).
That would allow us get in touch with his friends and would possibly aid in getting the unit returned (use your imagination... probably easier to get them tell you who/where he is, rather than to get them convince him to return it...)
Probably this would add too much bloat to IIWPO; but hey, could be useful... =P
WOW, ok.
First of all - I registered 2 this forum less than a week ago,
and great job for doing these kind of things.
second - where can i d/l the prog?
and last another idea: when some1 steals ur pda he's usually gonna sell it over. meaning he made his money.
HOWEVER - if even after a HR after changing sims (maybe even without) there will be a picture message saying:
"You cannot use this phone"
"This phone can only be used by me - *name*"
"However, Im willing to buy this phone back from you. call +......"
there wont be a place on the screen to enter the code.
however - the phones' user knows he can type his password and unlock the phone. you might even integrate a handwriting recognition programm for signature or somthing but that will be super hard, i know.
another option is that when seeing this message user has to touch 4 corners of the screen with the stylus in a specific order, then he'll have a please enter password screen.
any comment?
is it do-able?
http://wiki.xda-developers.com/index.php?pagename=IIWPO
Recurring 8525 problem since upgrading to WM6 ROM (AT&T version). The phone will freeze completely (clock doesn't advance, screen and buttons and keyboard don't accept input, display freezes at on or off). When restarted by soft reset, the phone will frequently come back up with no GSM. When that happens, sometimes if I remove the battery and leave the phone off for a few hours then GSM will come back and will work for a while and then lock up again.
When it comes back with GSM service all of the network logon info for GPRS, my Wi-Fi networks with their auth info is gone.
Also email accounts are gone from the account picker and can't be re-created with the same names even though they have completely disappeared. I assume the settings are still in the registry but accounts just aren't showing. One account still shows on the Today screen, but isn't in the account picker.
A hard reset "fixes" things for a while. I've experimented with only installing a few of the most necessary 3rd party apps, without finding any "smoking gun" program that's causing problems. I've also re-seated the SIM card multiple times. I'm thinking it might be a hardware problem.
Today I flashed the radio to 1.54 and it has worked for a couple of hours without needing to be reset.
I'd be interested to hear what possible diagnostic paths I should look at before I call AT&T and begin the rigmarole required by tech support. Anyone with a very similar situation?
Thanks in advance.
I'm having the same problem. I was thinking of going to AT&T to get a new SIM, thinking that was the problem. Any solution yet?
-Pete
I started having the same problem with mine last week.
Sometimes it locks up, sometimes it gets stuck at the windows logo durring boot, always displays no gsm rom on boot.
Take a look at the how to unbrick thread. no gsm rom msg is one of the types of brick.
I installed hard spl ( already had it actually ). Flashed os, but it didn't help. Flashed GSM and no gsm msg went away. The phone is still acting strangely.
remember, just because the rom came from your carrier DOESNT mean that it doesnt have problems. Alot of people seem to have problems with upgraded rom versions from their carrier and end up either downgrading to previous rom or flashing cooked roms. try the previous rom or another cooked rom and see if that fixes the problem before blaming the hardware. It will save you a major headache trying to troubleshoot something that is working perfectly....
Please remember to do a bit of reading and hard spl your device before going off and bricking your Hermes. 10 minutes of reading might prevent hours, days or weeks of hair pulling, nail biting insanity to find the answer. Cheers.
hello people,
I have my SVP M3100, original from orange spain - but CID unlock to work with portuguese carrier, now I live and work in Hereford UK, and I use a sim from Three and other from Lebara the three sim is to have net on my pc and the lebara sim is to make low cost international call, and i switch many times the sim's to make calls and to have internet, now i have the same problem that you have, i try to upload the HTC original rom that have IPL. BOOTLOADER, SPLASH SCREENS EXTROM GSM, but lock at 12% I try upload ongly radio rom and the same a think that somekind of hardware problem caused by to many sims switch, if any body have one solution please tell me
Sometimes it locks up, sometimes it gets stuck at the windows logo durring boot, always displays no gsm rom on boot."
Same thing happened to me. Tried to reflash original ATT ROM , Radio Only, OS only. Gonna send it for the repair. Phone is not under warranty anymore hope that the price of repair will be less than price of new phone.
BTW, is there any way to remove Hard SPL from the phone?
how much was the price of repair?
Try changing you radio to a new one. i have had the same problems in the past with different radio roms and rom versions. so i am using radio 1.54.30.10 with pdavet roms and have had no isuue.
Ray_jai said:
how much was the price of repair?
Click to expand...
Click to collapse
Got my phone back fixed. They charged me for shipping only $19
only $19!?
What if I don't have ATT anymore?
do you know?
i had the same issue check for my previous posts i think no GSM is a common error there is method flashing himalaya rom on hermes to erase GSM sector.
if you cant find the link PM me .
i hope it solves your problem.
tracylynnt said:
Recurring 8525 problem since upgrading to WM6 ROM (AT&T version). The phone will freeze completely (clock doesn't advance, screen and buttons and keyboard don't accept input, display freezes at on or off). When restarted by soft reset, the phone will frequently come back up with no GSM. When that happens, sometimes if I remove the battery and leave the phone off for a few hours then GSM will come back and will work for a while and then lock up again.
When it comes back with GSM service all of the network logon info for GPRS, my Wi-Fi networks with their auth info is gone.
Also email accounts are gone from the account picker and can't be re-created with the same names even though they have completely disappeared. I assume the settings are still in the registry but accounts just aren't showing. One account still shows on the Today screen, but isn't in the account picker.
A hard reset "fixes" things for a while. I've experimented with only installing a few of the most necessary 3rd party apps, without finding any "smoking gun" program that's causing problems. I've also re-seated the SIM card multiple times. I'm thinking it might be a hardware problem.
Today I flashed the radio to 1.54 and it has worked for a couple of hours without needing to be reset.
I'd be interested to hear what possible diagnostic paths I should look at before I call AT&T and begin the rigmarole required by tech support. Anyone with a very similar situation?
Thanks in advance.
Click to expand...
Click to collapse
I've got exact the same symtoms. No GSM, network and auth settings gone, opera registration lost etc. It started a few days a go, in the beginning I had a working GSM most of the time, but it became less and less and now it doesn't have service at all anymore.
Currently device information shows:
ROM version: K's Rom v1.21
ROM date: 10/03/07
Radio version: NONE
Protocol version: NONE
Model No.: HERM300
IMEI: <empty>
Does anyone know a permanent solution?
I have the SAME PROBLEM!
I was about to get radio to work 3 days ago, and now the radio says none.
it's like the radio removed itself.
ok this doesn't make sense, I used the hima rom to remove the radio.
and now the radio is back! wtf?
Hm I tried everything but I can't seem to reflash the radio. About every version I try hangs at 0%. Sometimes when I flash from SD card it hangs at arount 10%.
Tried different SPL versions as well
Damn you radio!!!
BTW, I have no idea what they did to my phone there, but after returning from the AT&T Repair center the Call timer was zeroed and Device ID is now different from what it was before in Skyscape software
Any solutions yet? Im having the same issues.
The reason why Active Sync restarts
For many people the Workaround "not a hack or registry at all" does not work is because of a event based notification that runs the program anytime the time changes. Since your phone updates from the cell tower, it updates the time alot even if by mere seconds well this update runs activesync. Get yourself MemMaid
run it in advanced mode then Jump to Databases then select Notification Queue you will see a list of 3 types of Queues; Time Based, Classic Time Based, and Event based. Go to the event based queue, you should see at the end of this list 3 listing for repllog.exe with the active sync icon. Click on them individualy and read what shows up in the window below put a check mark next to the listing that describes the event as "apprunaftertimechange" it is normaly the last one on list
Also make sure there is no repllog.exe listed in any other queue for a time based event. Leave the other instances of repllog.exe since you still want your device to sync when its connected to the computer. Once you select all events that desribe running repllog.exe after a time change or at a certian time and date press the delete button.
This worked for me on my 8125 and the tilt and if i would of figured this out before i had ATT replace my 8525 i probably would of not got the tilt but lol they gave me tilt free cause all the problems i had with 8525.
let me know if this works for you guys that still see activesync running after the fake server WORKAROUND.
This should work
memmaid is not free but i think its free to try and if all you do with it is fix this problem then great or find a way to register it cause it does help has cool tricks and tweaks
Wow, still no real fixes for this problem, bummer
running memmaid work
running memmaid works and fixes the random start of activesync and once the random start of activesync is fixed the device will not lock up because of activesync this not to say if some other program you may have installed locking you up as well
There's a new Zest firmware available for download from http://www.my-xda.com/. The filename is Xda_Zest Firmware Update_V7.7.0S.WWE20.00_M4.6.5.P7_V2.1.4 GBR20, which seems to be updates to most of the roms inside the zest. It's installing at the moment, and the upgrade interface on the phone is displaying "GalaxyMini5 Eboot (3.33.0). Since this appears to be a codename for the P565, I guess this is more evidence that the XDA Zest is simply an underclocked P565 and more evidence that P565 firmware may well work on it.
Warning, this firmware does not appear to contain the O2 menu software, or the free GPS software that comes with the phone (although maybe the latter can be re-installed from the SD card). Shame - I rather liked the O2 menu interface.
what improvements does it have? Is it actually worth upgrading?
Thanks.
The only things I can see that I don't remember seeing before are a couple of new or updated control panel entries. Video calling is probably the really important one.
You seem to lose the RSS reader, the O2 auto settings, the O2 menu and the GPS s/w (although the latter was only a demo). I have no idea if using the SD card that came with the Zest will restore these, as I don't have it. (If the software is all on there somewhere, and someone could bung me a copy, I'd be really grateful.)
It does make me wonder how the P565 firmware compares. I understand it has a nice touch interface on it.
It seems odd that the new firmware would remove all the o2 specific bits. Great if you want to use it on another network I suppose, but I quite like the mobile shell or o2 menu.
The satnav software isn't on the sd card - only the maps.
The instructions say:
Please note that if you already have CoPilot satellite navigation software on your Xda, refer to the Xda Zest user manual before upgrading your device software.
Click to expand...
Click to collapse
I couldn't see anything of significance in the user manual.
Interesting. I actually have Tomtom for GPS on a different SD card, which is related to the reason I don't have the original SD card. Tomtom autoinstalls from the SD card, so I thought it might be that the O2 software installed itself from the SD card provided by O2. I guess that if it's only maps on the SD card then that's not the case, and the new firmware does strip out all the O2 extras, which seems like a peculiar decision to say the least.
Still, it did get me to try the new SPB mobile shell 3, which is what the O2 menu is based on, but nicer. I'm trying to decide whether it's worth the $35 for just a flashy finger driven interface. The weird thing is, it actually might be.
I'm actually going to upgrade my firmware to new one which is currently available in O2 site. What I want to know is if upgrade mine to the latest what would be the changes I may seen... Is it worth upgrading by loosing all the software?
So far I've seen nothing to write home about. The only reason might be if you can't already make video calls and want to do so. (I never make them, so I have no idea whether or not they're supported in the original firmware.)
I just upgraded mine to new firm ware. It worked fine for me. I didn't lose any O2 extras inc O2 menu. It was Oki but haven't tried yet to make video calls.. I will install iGO8 and will uninstall the co-pilot.
SPB Mobile shell 3.0 Rocks working smoothly with my Omnia and Xda Zest
I've just updated, and I didn't lose any O2 extras either (including Copilot). I backed up the Program Files\Copilot folder on the device to my PC before updating, and copied it back over after the update and voila, I've still got my fully activated version of Copilot. It did still prompt for allowing it to connect to the net during the 14-day trial the first time I ran it, but the license screen confirms it's the full version.
aDe
I have a working theory that the autorun on my Tomtom SD card might have run in preference to some autorun that might otherwise have run the first time the OS booted. I could test this by re-installing the firmware, but it's kind of a pain to have to put all the data on again.
Having played around some more and browsed the Extended ROM on my device, this does appear to be what happened, as all the CAB files are present. Fortunately this is a bonus for me, since I'm not on O2, and most of these files are useless to me, and I can therefore just pick and choose the apps I'd like to install.
This might be useful to other Zest users - the hack to make the Extended ROM visible:
Use your favourite Registry Editor to make HKLM\System\StorageManager\Profiles\ONDisk2\FATFS\MountHidden set to 0 (default is 1)
You can then browse to \ASUS_ROM\ in Total Commander to view your Extended ROM partition. The ROM does not appear to be write protected, so you can now put all the packages *you* want re-installed on a hard reset in there. Neat.
I contacted O2 support about this issue, and they replied saying that:
On occasions the O2 menu can drop off after a ROM upgrade, but this would usually be resolve by either hard resetting or running the upgrade again. The o2 menu is still installed on the new ROM.
Click to expand...
Click to collapse
I have now done this upgrade and have retained the 02 menu. The radio reception seems a bit better as I now get HSDPA at home, which I didn't previously, so the radio upgrade seems to be worth it.
ringer
ive got the zest and am happy with it so far apart from the last 2 days i cannot hear it when i get a call everything else works ie.system sounds,core player etc but the actual phone wont ring it just vibrates ive reset it a million times and checked system settings etc but nothing so if anyone has any ideas i would be very grateful, also how do you know if you are getting hdspa or not is there a setting for it or something, cheers guys.
The connectivity icon at the top right of the screen shows what communication protocol is being used by showing a symbol (usually just a single letter) in a solid square. The letters I have seen so far are:
G - GPRS (2G)
E - EDGE
3G - 3G (this is the odd one out with the two letters squashed together)
H - HSDPA
It's worth mentioning that on my train ride home I see all four protocols at different points, and the hand-off between them is very smooth.
thanks for quick reply i will keep an eye on it, still no joy with my ringer though its very strange. never had a problem like it on my orbit. i will keep investigating ,also do you know if anyone will be coming up with a rom for zest as i miss manila 2d although mobile shell v3 is good.
Have you checked:
Start->Settings->Sounds & Notifications
On the Notifications tab you can select the "Ring type", one possible choice of which is "Vibrate", which will make the phone only vibrate on incoming calls. Just guessing.
yes ive tried all that it might be affected by software ive installed recently i will try unistalling them one by one and see if that helps, failing that il do a hard reset i guess, anyone know how to hard reset the zest? thanks for your help.
There is a contortional key sequence for this, but you can also reset it by going to:
Start->Settings->System Tab->Default Settings
cheers managed to sort it , i installed mini lyrics software and ticked all in associating files which for some reason stopped the phone from ringing
thanks for your help.
Failure of firmware upgrade
Ive just had a power failure whilst upgrading the firmware on my new xda Zest and all it it shows when turning on is "OS Update failed! Please update again". Is there anything i can about this or will it need to be returned to O2. Any suggestions. thanx