Database Users

Bell phones and the lack of 3 button combo

I'm starting a new thread because it doesn't necessarily fall in to unlocking of the phone (as I've been asked).
I'm guessing any new purchases of this phone will have the recovery/download 3 button combo feature completely disabled.
The reason why I say this is that I've been to 5 different stores between yesterday and today (with the most recent one having a stock amount of 9 phones) and here are my findings:
Every single boxed up phone has the feature disabled. (All I did was have them install the battery (no sim or anything) and pass the phone to me).
However, every one of those 5 stores that I went to, I did it flawlessly on their demo phones.
So my guess is, as the demo phones would have been the first batch Bell provided (and some being on display before any actual product released to the public), all subsequent batches of these phones will have this feature disabled.
I went to 2 different best buys that have ample stock of the phones because it is onsale this week, and none of them worked... nor did they work at the future shop I attended or the 2 bell stores (including the one I purchased and returned initially).
But every single demo did.
So if anyone got their hands on the very first batch of phones and it works then you're a lucky one. For the rest of us, I think we are S.O.L.
There's got to be a way to do it... Anyone know a Bell Representative or better yet a person inside samsung that will leak that info to you?
Heck I don't even want to unlock the phone. I'll stay on Bell's network, I just want to be able to load new versions of Android without any risk of bricking my phone.

Thank you! It was annoying reading all those posts abt this in that thread.
And I'm not too sure that the new phones don't have it. There have been a few people on the thread that have said that they got the phone at launch, and it didn't have the feature, but when they went to return it and get a new one (from the new shipment) it was fine...
So really I dont think its very easy to tell if its gonna work or not...

I think I'll wait til september to buy the phone.
I don't care too much about custom roms and the like, the stock one is fine, but Bell has a history (See the i7500L) of not updating their firmwares in a timely fashion. The i7500L is still on 1.5. Terrible if you ask me, considering the "open-source" feel of android.
So there are rumours, I don't know if its true or not, that bell is going to have an official 2.2 update in september. Maybe then I'll buy it and by then all phones will have the 3 button combo on them.
I just went to a local future shop here, and the phone representative contacted their Bell Rep, who was at another store, he couldn't do it on the phones they had there, but promised to call Samsung on Monday to find out if their is an alternate way.
Maybe you have to hit a reset button along with it. I remember doing something similar on my old HTC diamond phone, maybe this is the same thing (sort of).
Too bad, I loved this phone all the 4 days I had it (up until reading about the 3 button combo). I sort of miss it.

I just put a call in to Samsung to find out why some work and some don't, they said because the phone was so new that I had to call a number specifically set up for support on the Galaxy S but they are only open Monday to friday..
So hopefully with all this calling around I'm doing something will be figured out.

I got my Vibrant on launch day, 3 button combo didn't work. Swapped it out for a new one, from a new shipment last Thursday (august 12th) 3 button combo works.

arr0ww,
Can you confirm what i've been reading on wiki then?
It states:
"Note: There are many Bell I9000M floating around with this feature disabled, without the Download Mode enable you wont be able to restore from a failed firmware flash. We highly recommend you to take it back and exchange it for a model that can work properly with the 3 button combination. The first batch from around Aug 5 or Serial # ending with 6000000 have the 3 buttons combo disabled, the new batch after Aug 11 with Serial # ending with 6500000 have the working 3 buttons.
example of full Serial # 89302610202006500000"
Do your last 7 digits end with 65 and not 60?
Also, where did you get yours exactly? I think if its close to me, I'll just pop by that store and get it (assuming your somewhere in the GTA).

I got mine first thing Launch morning. My serial is 59XXXXX. 3 button combo IS working.

it shouldn't be hard to fix the issue. from what i've read, and people have said, the 3-button combo is written into the SPL part (256kb) part of the Nand. all we would theoretically have to do is flash our SPL with some else's 3-button enabled SPL. now two of my friends bought their phones same day as me, and have theirs enabled, and both are rooted, so it's not hard to get our hands on a copy.
i have posted another thread in the software technical section about this and haven't gotten any replies (maybe it's the wrong section). the g1 users flash their spl, but they don't talk about how to make an image of the current spl. so i'm stuck here. i know it can be done, just don't know how yet.
apparently nandroid backup doesn't backup the spl, so that's useless to us. from the SPL backup kit for the g1 users, i read the batch file, and it reads specific hex addresses in the nand and writes them to a file, but i would assume these addresses are different for our nand. so once again, useless.

For all those that have their 3 button disabled... can you confirm if your serial ends with 60XXXXX? Maybe its limited to just that batch of s/n's.
As for wang1chung.. hopefully its a simple fix.. but i'll refuse to buy one again unless I get one that is confirmed working or easily fixable to get it working without a cable.
Thanks

Electroz said:
I got mine first thing Launch morning. My serial is 59XXXXX. 3 button combo IS working.
Click to expand...
Click to collapse
it is possible the bug was only in the batch with numbers ending in 60xxxxxxxx
since the ones on 59xxxxxxxx works, and 65xxxxxxxx works
that seems to be the logical sense

this would be nice
problem is, no one has been able to get a way to extract, and flash back the good SPL to the bad phones
wang1chung said:
it shouldn't be hard to fix the issue. from what i've read, and people have said, the 3-button combo is written into the SPL part (256kb) part of the Nand. all we would theoretically have to do is flash our SPL with some else's 3-button enabled SPL. now two of my friends bought their phones same day as me, and have theirs enabled, and both are rooted, so it's not hard to get our hands on a copy.
i have posted another thread in the software technical section about this and haven't gotten any replies (maybe it's the wrong section). the g1 users flash their spl, but they don't talk about how to make an image of the current spl. so i'm stuck here. i know it can be done, just don't know how yet.
apparently nandroid backup doesn't backup the spl, so that's useless to us. from the SPL backup kit for the g1 users, i read the batch file, and it reads specific hex addresses in the nand and writes them to a file, but i would assume these addresses are different for our nand. so once again, useless.
Click to expand...
Click to collapse

Hey guys, are you still able to start in recovery mode with a cable and ADB. I would like to know cause my G-sensor is dead and I went to Best Buy to exchange it and the phones were all lacking this mode.
I didn't swap ysterday because of this but I have to do something before aug. 20. After that I will have to see with bell what they want to do and it will surely go for a repair. I would prefer to have a new one working right away but the lack of recovery mode is discouraging me.

my s/n is 52xxxxx and 3button is disabled
sp991, recovery mode is still accessible via adb to those with the 3button disabled.
allgamer, i only suggested that as no one else had suggested anything else? i assumed it would be possible since the g1 users can read their spl via the command " pmemdump -a 0x8c000000 0x40000 " and save it to a .nb file to update later. maybe this would be better accomplished in the hands of talented coders/developers.

Mine is 64xxxxx and it is disabled.
adb works.

I exchanged my first i9000m coz the download mode wasn't working.
The second one I got two days ago goes into download/recovery mode without problem!! This one has IMEI ending with 65xxxxxx and manufactured in Aug.
I also tested new one at Bell store today which had IMEI # 65xxxx as well, but it didnt go into download mode. The guy at the store said it was the newest batch as they received it yesterday, and now i'm totally confused....coz I thought all newer batchs are download mode enalbed..

sp991 said:
Hey guys, are you still able to start in recovery mode with a cable and ADB. I would like to know cause my G-sensor is dead and I went to Best Buy to exchange it and the phones were all lacking this mode.
I didn't swap ysterday because of this but I have to do something before aug. 20. After that I will have to see with bell what they want to do and it will surely go for a repair. I would prefer to have a new one working right away but the lack of recovery mode is discouraging me.
Click to expand...
Click to collapse
do you have any other best buy store that you can go to?
try testing with the Download mode, it's easier than testing with the Repair mode
the Download mode kicks in right away, after you put in the battery, and do the 3 button test
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
check the wiki for some visuals
you can do it even with the plastic back and screen protector on top

trueimage said:
Mine is 64xxxxx and it is disabled.
adb works.
Click to expand...
Click to collapse
ADB will always work, but it's useless if it gets bricked
good to know 64xxxxxxxx is not good
so i guess batches between 60xxxxxxxx to 64xxxxxxx are bad?
since the 59xxxxxxxx were good, and 65xxxxxxxxxx are also good

karakake said:
I exchanged my first i9000m coz the download mode wasn't working.
The second one I got two days ago goes into download/recovery mode without problem!! This one has IMEI ending with 65xxxxxx and manufactured in Aug.
I also tested new one at Bell store today which had IMEI # 65xxxx as well, but it didnt go into download mode. The guy at the store said it was the newest batch as they received it yesterday, and now i'm totally confused....coz I thought all newer batchs are download mode enalbed..
Click to expand...
Click to collapse
that's exactly what we are trying to find out, to see if there is any pattern
but if the one you tested with 65xxxxxxxxxxx didn't work, then i guess we can't really identify it via the serials numbers, and only can be tested manually.

Try downloading the new firmware for bell the JH2 that you can download via Kies this might fix the 3 button combo for people have issues. as the recovery screen is a bit different. give your a warning now that you have entered the system menu. the old recovery screen did not have this.
Someone that can't get into recovery should try this update..

no dice, just updated
EDIT: what's worse is i thought it would've at least helped with the gps lag, and now i can't find my location at all. under the gps performance testing option, i can't pickup any satellites whatsoever.
i'm pissed now, as i needed it to go on a roadtrip tomorrow

Codes Secret Codes

The samsung galaxy s have a bunch of secret codes that you can dial in and it gives you access to hidden options and hidden menues, does HTC have any secret codes like this?
If so can someone make a list of all the codes and what functions they have.
thank you

*#*#4636#*#*

All I know is *#06# but that's no secret. Codes went dead a long time ago. Only people I knew that messed with them was motorola and nokia. Now moto has its bootloader mode and nokia....well idk about them
lettin the hussy role on my MT3G Slide

Some of these may or may not work, but they're said to be universal in Android. Haven't tried them all on the Slide.
FYI These codes have been obtained by decoding various .apk files present in the phone firmware.
*#*#4636#*#*
This code can be used to get some interesting information about your phone and battery. It shows following 4 menus on screen:
Phone information
Battery information
Battery history
Usage statistics
*#*#7780#*#*
This code can be used for a factory data reset. It'll remove following things:
Google account settings stored in your phone
System and application data and settings
Downloaded applications
It'll NOT remove:
Current system software and bundled applications
SD card files e.g. photos, music files, etc.
PS: Once you give this code, you get a prompt screen asking you to click on "Reset phone" button. So you get a chance to cancel your operation.
*2767*3855#
Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
PS: Once you give this code, there is no way to cancel the operation unless you remove the battery from the phone. So think twice before giving this code.
*#*#34971539#*#*
This code is used to get information about phone camera. It shows following 4 menus:
Update camera firmware in image (Don't try this option)
Update camera firmware in SD card
Get camera firmware version
Get firmware update count
WARNING: Never use the first option otherwise your phone camera will stop working and you'll need to take your phone to service center to reinstall camera firmware.
*#*#7594#*#*
This one is my favorite one. This code can be used to change the "End Call / Power" button action in your phone. Be default, if you long press the button, it shows a screen asking you to select any option from Silent mode, Airplane mode and Power off.
You can change this action using this code. You can enable direct power off on this button so you don't need to waste your time in selecting the option.
*#*#273283*255*663282*#*#*
This code opens a File copy screen where you can backup your media files e.g. Images, Sound, Video and Voice memo.
*#*#197328640#*#*
This code can be used to enter into Service mode. You can run various tests and change settings in the service mode.
WLAN, GPS and Bluetooth Test Codes:
*#*#232339#*#* OR *#*#526#*#* OR *#*#528#*#* - WLAN test (Use "Menu" button to start various tests)
*#*#232338#*#* - Shows WiFi MAC address
*#*#1472365#*#* - GPS test
*#*#1575#*#* - Another GPS test
*#*#232331#*#* - Bluetooth test
*#*#232337#*# - Shows Bluetooth device address
*#*#8255#*#*
This code can be used to launch GTalk Service Monitor.
Codes to get Firmware version information:
*#*#4986*2650468#*#* - PDA, Phone, H/W, RFCallDate
*#*#1234#*#* - PDA and Phone
*#*#1111#*#* - FTA SW Version
*#*#2222#*#* - FTA HW Version
*#*#44336#*#* - PDA, Phone, CSC, Build Time, Changelist number
Codes to launch various Factory Tests:
*#*#0283#*#* - Packet Loopback
*#*#0*#*#* - LCD test
*#*#0673#*#* OR *#*#0289#*#* - Melody test
*#*#0842#*#* - Device test (Vibration test and BackLight test)
*#*#2663#*#* - Touch screen version
*#*#2664#*#* - Touch screen test
*#*#0588#*#* - Proximity sensor test
*#*#3264#*#* - RAM version
Click to expand...
Click to collapse

I pray you have not given a loaded gun to a child with those codes. People, if you do something wrong, your phone will be dead. I have seen it a million times. Use these at your own risk.

donepate said:
I pray you have not given a loaded gun to a child with those codes. People, if you do something wrong, your phone will be dead. I have seen it a million times. Use these at your own risk.
Click to expand...
Click to collapse
Exactly. I cannot tell you all how many phones I have ruined playing with codes. It is just better to leave them alone all together.
Best possible thing that can happen is it requires the subsity (sp?) Lock code which can only be gotten from tmo with a crap load of questions
lettin the hussy role on my MT3G Slide

Hussyfan said:
Exactly. I cannot tell you all how many phones I have ruined playing with codes. It is just better to leave them alone all together.
Best possible thing that can happen is it requires the subsity (sp?) Lock code which can only be gotten from tmo with a crap load of questions
lettin the hussy role on my MT3G Slide
Click to expand...
Click to collapse
What are you talking about? The subsidy unlock is a SIM unlock. In other words, if you want to use an AT&T SIM in a Tmo phone, you need to get a subsidy unlock code. Also, subsidy unlock is easy to get. All you have to do is ask for it, have an account must be active for at least 45 days (might be 40 actually, I don't remember the exact number), and give them your email address. You will then get an email with the code and instructions within 24 hours. Wow, real crap load of questions to go through, sure...

Hussyfan said:
If you were alive or smart enough to remember the 90s tmo would not give you the subsity lock without asking you a bunch of questions because the only way you would need it was because you were probing around secret menues and got locked out of you phone (getting the master password wrong 3 times would result in a subsity lock and you could not access the phone at all). Sim unlocks back then were not subsity locks you twat so do some research.
Haha another dork I made piss and moan. You gonna go call mommy now? Oh wait that may require getting off your fat ass and breathing some fresh air outside the basement. Get a life loser. Haha
Click to expand...
Click to collapse
LMFAO! I think you are the one who needs to do some research. Go look for the definition of subsidy first of all, you tard. And I ain't pissin and moaning about anything. I just don't appreciate people spreading misinformation.
BTW, I did do some research:
http://en.wikipedia.org/wiki/Subsidy_Password
http://www.phonescoop.com/glossary/term.php?gid=100
http://en.wikipedia.org/wiki/SIM_lock
P.S. It's subsiDy, twat.

Hahaha, yeah if you think actually knowing wtf you're talking about means having no life, then yes I have no life whatsoever. I'm done with this thread and your ignorance. Good luck on XDA, your dumbass attitude isn't gonna get you anywhere here!
Sent from my T-Mobile myTouch 3G Slide using XDA App

Hussyfan said:
Awww I made you upset. Its ok to cry. Pissing and moaning is not the way. Smoke a blunt and chill, like me...
lettin the hussy role on my MT3G Slide
Click to expand...
Click to collapse
I'm glad I came back haha. I smoke blunts on the regular, check my name even lol. stay high...

stoneyjonez said:
I'm glad I came back haha. I smoke blunts on the regular, check my name even lol. stay high...
Click to expand...
Click to collapse
Haha well at least we found some common ground. See how cannabis unites people everyone? Well I'm gonna pack the pipe and call it a night
lettin the hussy role on my MT3G Slide

I've deleted a couple of flaming/trolling posts.
Please keep it friendly in here.

Hello there, have anyone tried these codes? I am going to buy a used Touch Pro, and I think those hardware test codes will really come in handy. Do they work at all?

warhamer2 said:
Hello there, have anyone tried these codes? I am going to buy a used Touch Pro, and I think those hardware test codes will really come in handy. Do they work at all?
Click to expand...
Click to collapse
touch pro is not android and this thread clearly states that these are android codes so please find the proper forum

Possible Kin 2 update being pushed!

So I was in Verizon today because of software issues. I still have the same phone but all they could say is pull the battery every night. So the lady tells me, my software is behind. I'm like "what, how?" She says "Its a known issue and an update has been pushed for the phone. Depending on when you got the phone, the new software will be pushed through." Apparently, thousands of people have gotten this "Update" I will call this week and see what the deal is.

Update like version 1.02?

not to sure..it was some lady which means she probably has no clue what the hell she's talking about so just sit and wait for a text from verizon wireless or the "Uploading Logs" screen. She said it will either be pushed OTA (over the air) or you will get a notice saying to bring your phone in which I think wont happen. 0lus the software has been released since April 1st so I'm guessing this is a load of bull.

Well, I had my phone turned off all day while i was out. I got back home, turned it on, and got a text from 475-6. It says BREW://----- idk what it said. Im guessing the update? not to sure. Phone info says..
Software Version: 1.0.1 (4704.0)
Radio firmware: v0.4.727
Model 119

Kinuser1 said:
Well, I had my phone turned off all day while i was out. I got back home, turned it on, and got a text from 475-6. It says BREW://----- idk what it said. Im guessing the update? not to sure. Phone info says..
Software Version: 1.0.1 (4704.0)
Radio firmware: v0.4.727
Model 119
Click to expand...
Click to collapse
Hmm I did abit of research about BREW. It's actually,Binary Runtime Environment for Wireless.
Brew (Brew MP) is an application development platform created by Qualcomm, originally for CDMA mobile phones.
As a software platform that can download and run small programs for playing games, sending messages, and sharing photos, the main advantage of Brew MP is that the application developers can easily port their applications among all Brew MP devices. Brew MP acts between the application and the wireless device on-chip operating system in order to allow programmers to develop applications without needing to code for system interface or understand wireless applications.
Click to expand...
Click to collapse
Sauce: http://en.wikipedia.org/wiki/Binary_Runtime_Environment_for_Wireless
Hmm... Hack via brew?

My phone software is the same as yours (1.0.1, etc...). I haven't received a text like that though. Did you follow the link in the text? I would be nervous clicking it unless I knew it was really from Verizon.

It's not a link at all. It usually says
"BREW:06:07---YADA YADA YADA."
(Just making up numbers but you get the point.)
Actually you cannot "hack" using brew. The brew message is sent over a wireless network. Unless you want to hack the network, go right on ahead
I think these messages are for the "Developmental" process of the phone since it originally had the "KIN" software. Not this "M" Bullsh*t
I'll do some research. I have time freeing up on me now since I'm getting school work done quicker. I will try to develop some sort of application to "Pull out" the information we need. If this is to techy for you, just put it this way. "I'll try to hack the phone" I've had a lot of success in hacking phone WITHOUT turning to the source of the internet/Bitpim. Technology is one of the things I know most about. I'm 15 and all I do is look for ways to hack. So far successful. As for this KIN 2m, not so much. So I turned to this forum so I could get some tips for stuff that i might not have done yet. Well, for today, I have nothing.

Kinuser1 said:
I will try to develop some sort of application to "Pull out" the information we need. If this is to techy for you, just put it this way. "I'll try to hack the phone"
Click to expand...
Click to collapse
As a matter of fact, i found it opposite to techy, better said "abstract". Can you explain in detail the Pull out attempt process?
I just wanna know, can handle tech terms.

Okay..well heres how it goes. We have to somehow get the kin into a "hidden" software writing screen(you should know what i mean) EVERY phone has one of these...AKA...enV touch..you hold clear..power..vol up and down and that brings the phone to a downloading screen and waits to be plugged into the drivers on the computer. But the kin is different...there arent any drivers as of right now.

Kin has that mode, indeed. It was labeled as "Download mode" both in QPST, Bitpim and several other tools.
Unfortunately, being switched ON by software (i guess that's the only way, or the only one available atm) made my phone reboot after a little while (maybe 1-2 mins), so it could be protected by the phone manufacturer. Also, no special effect was shown on screen, like you can see on other phones examples (with SERIAL and USB labels with a colours background).
On the other hand, QPST and other tools could get a backup of the NVitems on memory, and not the memory itself (they fail to). Messing with this made my last attempt a brick, so... not happy about them.

Hmm... MY Kin Came with 1.01

1.01 is the latest version.

[Q] Omnia 7 turns off immediately after switching on

I got my phone from Expansys a few months ago.
I've been trying to install Mango 7720 using the instructions in this thread. Having seen so many people say they did it no problem on their Omnia 7, I decided to give it a go.
I had NoDo on my phone, and during the update to 7712 the update failed, claiming I had removed the USB cable. I didn't and I still have no idea why it failed. Anyway, after thinking my phone was bricked, I managed to get it back to life by installing a stock ROM ("XXJL3 RETAIL UNITED KINGDOM") and I've now updated it through Zune 4.7 back to NoDo.
Now about 8 or 9 times out of 10, my phone fails to start up. If I have it running only on its battery, the phone switches itself off a second or two after I turn it on (while the "Samsung Omnia 7" screen is showing). If I have it connected to the PC while I turn it on, it gets stuck in an infinite loop where the white "Samsung Omnia 7" logo is displayed, the screen goes black (presumably phone reboots itself) and then the logo is displayed again.
Any help anyone can give would be greatly appreciated. I really don't want to have to buy another phone.
Details from "about" below:
OS version: 7.0.7392.0
Firmware revision number: 2424.11.2.3
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.2.2
Radio hardware version: 0.0.0.800
Bootloader version 5.2.1.4
Chip SOC version: 0.36.2.0

I have the same problem
but it was nodo 3 months ago and now it is the same problem looping and stuck in omnia 7 logo
I post too many thread in a different forum Unfortunately no body give a good answer
if you have any news please post because I need the solution

did you guys install that KC3 update from samsung?
When i had that installed it would cause my phone to get stuck in the reboot loop (boot > logo > boot > logo) when attempting the mango update. I had to re flash my phone for the mango update trick to work.

You are NOT alone!
This is a very similar issue to what it won't boot but stays looping on "Samsung Omnia 7" when tried to restart the phone.
To pull the battery out for about 10 minutes then it will start once but issue still remains.
This issue looks like happens on all versions of ROM and Mango.
As far as now, I don't see any solution yet.

I sent my phone to Samsung for repair. I got it back yesterday and it looks like they have installed the Orange France software on it despite my phone being a completely unbranded version.
Not only that, but the issue is persisting. All I need to do is browse to any sort of resource intensive website and the phone will crash.

From my experiences, Samsung has the worst service in the world. Not only the cell phones, but also other electronics.
I feel sorry for myself that I bought the Samsung Omnia 7.

motherboard failure?
i have the exact same problem as you, my phone will restart by itself for no apparent reasons... even simple task like browsing also will restart...
at first i use as it is...but when i try to update to Mango Beta, the phone goes into infinite loop, cant even hard reset
so i took it to the service center and they told me is motherboard failure. Changed a new one for me and now my phone didnt even restart once... i use it for few months without even switching off....

jyusa said:
From my experiences, Samsung has the worst service in the world. Not only the cell phones, but also other electronics.
I feel sorry for myself that I bought the Samsung Omnia 7.
Click to expand...
Click to collapse
Confirmed.
My first Omnia7 turned on once, then rebooted and went in the loop since then. Being the first week it was available there were no threads in forum, local support personnel didn't even know what phone it was and obviously had no battery to try to replace. So I had to send it in for warrany repairs, at my shipping expenses. Came back after 3 weeks.
But I'm still thinking it has to do with the battery, sometimes it's still acting up and the battery shows it's empty even if it's not

Try Windows Phone Support Tool. It won't make any harm.
Sent from my OMNIA7 using Board Express

andycted said:
Confirmed.
My first Omnia7 turned on once, then rebooted and went in the loop since then. Being the first week it was available there were no threads in forum, local support personnel didn't even know what phone it was and obviously had no battery to try to replace. So I had to send it in for warrany repairs, at my shipping expenses. Came back after 3 weeks.
But I'm still thinking it has to do with the battery, sometimes it's still acting up and the battery shows it's empty even if it's not
Click to expand...
Click to collapse
How and where did you send for Omnia 7 warranty repair?
Thanks in Advance.

My Omnia 7 picked up the Samsung update in August and I'm absolutely convinced that this is the cause of my device's crashing/booting issues, but I'm open to persuasion from anyone who has experience otherwise. I'd not had any instability until this update got applied but ever since it's been an absolute nightmare.
Whenever it crashes and reboots itself I'm also covinced that it's got something to do with attempting to retrieve data or access one of the radios, because it always seems to be when an app starts an attempt to retrieve data (e.g. IE or Twitter, etc.)
Since getting Mango yesterday (despite it refusing to boot on nuerous occassions during the update process!!) my about screen shows the following;
OS version: 7.10.7720.68
Firmware revision number: 2424.11.8.5
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.7.2
Radio hardware version: 0.0.0.800
Bootloader version: 5.8.1.9
Chip SOC version: 0.36.2.0
I'd be interested to know if anyone's tried replacing the battery or even the storage card to try and fix this.
I should be getting a HTC Titan when our corporate contract is up for renewal next month, and I'm planning on rolling back the Omnia 7 to a pre-NoDo image to see whether the issue continues or not, anyone else tried anything similar?

dbooth2 said:
My Omnia 7 picked up the Samsung update in August and I'm absolutely convinced that this is the cause of my device's crashing/booting issues, but I'm open to persuasion from anyone who has experience otherwise. I'd not had any instability until this update got applied but ever since it's been an absolute nightmare.
Whenever it crashes and reboots itself I'm also covinced that it's got something to do with attempting to retrieve data or access one of the radios, because it always seems to be when an app starts an attempt to retrieve data (e.g. IE or Twitter, etc.)
Since getting Mango yesterday (despite it refusing to boot on nuerous occassions during the update process!!) my about screen shows the following;
OS version: 7.10.7720.68
Firmware revision number: 2424.11.8.5
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.7.2
Radio hardware version: 0.0.0.800
Bootloader version: 5.8.1.9
Chip SOC version: 0.36.2.0
I'd be interested to know if anyone's tried replacing the battery or even the storage card to try and fix this.
I should be getting a HTC Titan when our corporate contract is up for renewal next month, and I'm planning on rolling back the Omnia 7 to a pre-NoDo image to see whether the issue continues or not, anyone else tried anything similar?
Click to expand...
Click to collapse
I have the same issue.
I have tried everything including battery change, rolling back versions... could not resolve it. My research found that I'm not alone. I'm waiting for Samsung UK to reply my service request now. Unfortunately, I'm in U.S.

fishfingers said:
I sent my phone to Samsung for repair. I got it back yesterday and it looks like they have installed the Orange France software on it despite my phone being a completely unbranded version.
Not only that, but the issue is persisting. All I need to do is browse to any sort of resource intensive website and the phone will crash.
Click to expand...
Click to collapse
I sent it for repair again and got it back today. This time, they have installed the T-Mobile UK software on it. I don't understand why they can't just put the unbranded software on my phone....

I've had this problem a lot in the past month, at first it started happening after trying to update from nodo to mango beta (via legit developer method) I got stuck in the boot loop and it was a real pain to get it updated. Throughout my use of Mango beta it would crash quite a lot, but it seemed to be getting more frequent.
I was hoping it was more of a bug with the OS than the firmware/phone. However, after updating to Mango 7720 the problem seems to have got even worse.
It crashed a lot during the update process. And now it's a real struggle to get it to turn on. I have the exact same firmware and bootloader as Dbooth and the same problem
I've submitted a repair with samsung.
*EDIT*
I've just done some testing and it seems that my phone barely crashes without a sim card in it. So I'm going to reflash to an old Orange UK Rom and see if it fixes it. I know I updated to a generic rom, hopefully this is what is causing the problems for me.
Fishfingers, how long did it take for samsung to repair your phone?
Also, I'm guessing they just repaired the faulty part, and not a new phone. I've heard that it is something to do with a motherboard issue.

[Q] What Focus is this

Hi all
I have a few questions to ask first I must though give the history of the device:
1. Phone was given to a bunch of us at Teched 2011 Atlanta by AT&T - they second hand rep and employee phones.
2. The phone worked well used AT&T and othe USA SIM cards - so this isn't a "Demo" phone.
3. I had to network unlock the phone with wwwfastgsmcom as I needed to use the phone outside USA. This worked and I have been able to use the phone in different countries.
4. I did the Cheveron NoDo update on the phone and subsequently upgraded to Mango Beta with NO problems what so ever.
Thank you guys for the help!!!
5. I upgraded to "Mango RTM".
6. Recently through Zune I received the "Pre release Mango cleanup" update. This ran on my phone. I haven't received anything ever since.
7. I have an ORIGINAL PAID FOR developer account so the phone is fully dev unlocked.
Phone details
Current versions (Settings: About"
Software Windows Phone 7.5
OS Version: 7.10.7720.68
Firmware revision number: 2102.10.9.5
Hardware revision number: 3.1.0.3
Radio software version: 2103.10.9.5
Bootloader version: 4.9.2.4
Chip SOC version: 0.36.2.0
Now through the diag mode I checked hardware version. INTERESTING part its says:
HW REV:1.0
No 1.3 or 1.4 just 1.0.....
So some questions and hopefully help:
1. My back button is a nightmare. All the way up to the Mango release that enabled multi tasking the back button works PERFECTLY. After the Mango update with multi tasking the phone has become irritating. Depending on which application and or menu I am in if I press the BACK button it either goes to multi tasking (no holding back just simply pressing it) or it goes back as its suppose to.
Sometimes even if I press softly or to the left or right of the back button it never goes back just keeps throwing me back INTO the multi tasking menu.
With APPS its a nightmare it always goes into multi tasking and not back. This throws the app into "resuming" if it is not a multi task written app. i.e. WhatsApp is almost impossible to use.
In certain menus it works well goes back as I need it to, in other menus like say contacts... it goes into multi task mode when I press back.
I do have a Zagg protector on the phone.
Question 2:
2. I see that my Firmware, Radio, Bootloader basically all those are completely out of date! This could be why the wierd behaviour?
2.1 I can't find a MANGO rom out there with the updated Firmware, Radio, Bootloader - is there one that I can use please? Provide some sort of link or point me in the right direction.
2.2 Do the ROM's relock the phone, just so I know to go back and unlock the phone