Hi,
After a mounth of problem caused by my mini-usb connector, I weld it this morning. But, I cannot sync it by usb anymore. I have to sync it by bluetooth. Anyway do you think there is a possibility to upgrade it with an SD card or another solution?
I thank you.
Hi,
My first thoughts would be..
"how am I going to charge the battery",
pointless pursuing an upgrade in the circumstances?!
STI
I don't see charging being an issue, as he may very well have power even if not data running on his connector, and even if that's not the case, there's plenty standalone battery chargers on ebay. Not the perfect scenario, but grab a second battery if you don't already own one and it's suddenly way better than tossing you uni.
About the SD card ROM loading...
I've seen a few posts on it, but I reckon the SD image is always created by dumping the current loaded ROM.
So, I imagine you'll need someone else so make you an SD image of the ROM you need/want.
As for the actual dumping of the OS, I never did it, so I can't really help you there.
It's not about the uni, but here's this: http://forum.xda-developers.com/showpost.php?p=899768&postcount=8
Still, as I told you, I believe you'll need a third party to supply you with the ROM dump, and even then, be damn careful that you both have the some devices (i.e. both G3 or both G4) as it probably matters.
Take this as a hint in (what I believe is) the right direction. By no means I can guarantee that this is the only way to go about it.
Best of luck!
I have the same problem with my HTC prophet device...since i upgraded to wm6 , problem came when I activated Wm5torage
I can still charge it with my usb cable but nothing more...I`m looking to download an SD image backup from somebody
If somebody can help ...
I have the same problem, having replaced the socket it also just now charges and shows in windows as an unknown port. I have checked all the connection on the PDA motherboard and everything appears OK when measured with a meter. As windows recognises that there is a port there, it seems likely that the clock and data are available. If this is the case, it should be recognised. I can only assume that somehow the OS has become corrupt. This seems to be quite a common thing, and it would be nice if someone could throw some light on why this happens.
If the clock and data are available, meaning that the two computers can communicate, you should be able to reflash the device, since Bootloader mode circumvents the OS, and the RUU has it's own drivers for communicating with the device, evidenced by the fact that it shuts down ActiveSync to avoid interference.
Try putting the device into bootloader, then initiating a flash. If there's something, anything, wrong with the dataport, the RUU will be unable to flash. If the ROM Upload starts, the it will probably finish too without a hitch. And you'll have a new working Uni.
Also, it is not possible to flash via SD card, since the SD port can only be used with the appropirate drivers loaded, and that's done by the OS. Flashing is done while in bootloader mode, which circumvents all of the OS, and uses a separately stored on board program to access the main ROM, screen and dataport.
It is possible to flash a new Rom via the SD Card.
It does however require another device to dump the image onto the SD Card first.
Search the forum and you will find specific details on the procedure.
I believe Midget made a post about the process not so long ago.
Also could all peeps please keep these sort of issues in the upgrading section, you are more likely to get better answers there.
This forum is meant to be purely for WM6 on the Universal.
Cheers,
Beasty
Yep, here is:
http://forum.xda-developers.com/showpost.php?p=1822399&postcount=2
Whoops sorry am getting a little off topic here. Anyway boot load will not work so port is probably faulty. Got a version of WM6 on it anyway, so will use as is.
So earlier today I decided I wanted to take my phone off root because it had become really buggy so I followed these instructions from another thread:
"download this http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip unzip it and load it to the root of your sd card and reboot the phone holding down the camera and power key then follow the instructions in screen then reboot and wait for the update. how many more times must i type this? can you people not see the search button."
SOURCE: http://forum.xda-developers.com/showthread.php?t=478856&highlight=original+firmware
After doing this, my phone was working fine. Everything worked. For some reason like 2 hours later, my threaded txt messages started showing up in the wrong order. I called T-Mo and they had no solution so they're going to sen me a new one. I wanna make sure there is no evidence on the phone that it was ever rooted. How do I make sure? Thank you so much!
just make sure you updated to original firmware after you changed your fastboot images... that is... if you changed the fastboot images... then you are good to go.
I never messed with fast boot and all that, after I rooted it, I updated JF1.41 with auto rotate and multi touch. thats it. when I went to original firmware, literally I did exatly what he said with the DREAIMG.nbh file, and rebooted. ( Copied the DREAIMG.nbh file to root of SD, restarted with camera+power, ran the update, rebooted) Was there a step I missed?
The problem now is, I dont wanna change much at this point bc if it fixes the threaded txt issue, then theyll prob charge me for the new phone if the txt problem is fixed.
find the SPL thread(sticky) and make sure that your bootloader screen looks like the stock one and you should be fine as well, RC29 already wipes everything else
my threaded txt messages were going in a crazy order last night. but i assumed it was cuz of daylight savings time lol. my g1 to g1 messages would show up in correct order. but everyone else' messages were in screwy order.
yeah its because of DST. T-mobile changed the clocks to early lol. Either that or the g1 screwed something up.
we will see what happens
I posted this in another thread so ill be brief ...
due to a hardware error I returned a white g1 which I had rooted and tricked out with JF's RC33 a theme and the dev BL... I was feeling lazy so I just wiped it and made sure it was back to the stock theme and sent it off with a flat battery, I dont think they will scrutinize them much, we will see, most of the time you play stoopid say you took it to a store and they did some stuff, whatever, PROVE IT, pry my replacement from my cold dead hand.
ill post if I get some response to my tricked out g1 returned due to a bad bt radio
bhang
Hi,
My girlfriend recently bought an XDA Orbit 2 which has WM 6.5 install on it.
Everything else on the phone works perfectly and without issue but she is unable to make phone calls correctly;
The phone will be able to dial out and establish a connection but no sound can be heard by either party even though both phones say the connection is there.
This can be resolved by a hard reset, however this only last for about 10-20 minutes before we lose all sound once again.
Can anyone shed some light onto this for me?
One thing that always screws up phone calls is the radio on the phone it should be a 1.59.xx.xx to check it go to start => setting => system => Phone Information => Software Information. Will find it there also while you are there what 6.5 rom is she running on it as if its not a stable one it may be worth updating it...
Should the .xx.xx be anything in particular or just stay as .xx.xx?
anything in particular i use the stock one (with the default rom) which is .42.15 any should do the job though...
Ok the radio on it is 1.58.25.14 which im asuming is wrong. How do I change it?
This a custom flash thingy ma bob wont hard reset the phone when you flash it => http://forum.xda-developers.com/showthread.php?t=376119
http://forum.xda-developers.com/showthread.php?t=426203
Is the radio i am using and imo the best for signal/ battery life.
How to do it.
1.Download both
2. Put the nbh file in the same directory as the custom ruu
3. Put the phone into bootloader (Start + OK + Reset whole on bottom, hold the buttons until it show a red green white blue screen)
4. plug it in to computer (let the drivers fully install)
5. Start up the Polaris_Custom_ruu.exe
6. Follow the instructions, shouldnt take too long to go through and flash
7. it will reset and you will have a nice shiny new radio and hopefully no more call problems.
All i will say now is what an idiot for selling the phone in that state... (may actually be the reason it was sold lol)
Im going to sound ike a total idiot now but I have no idea what ruu is or nbh or where to put it or what a bootloader is.
Could you possibly put it in moron speech Chris?
LOL well honestly i thought that i had already done that....
Have a look at the files that you download and then it will be explained.
The RUU is the thing that will do the flashing to the device
The nbh files contains the information of you download the stuff and follow the instructions you will have the result that you want honestly i cant think of a simpler way of doing it
Ive also put 2 screenshots to try to help you (one has a different radio but you get the idea...)
Also give this a read but i feel it may confuse you more..
http://forum.xda-developers.com/showthread.php?t=381600
Its a noobs guide to flashing and has all of the info that you need to have.
It does give one point that it has to have SPL-2.20.Olinex on the screen but i would guess this is there as you already have 6.5 on the phone.
Awesome, thanks chris I will get it done tonight after work and let you know how it goes, if it fails I have no doubt I will be back complaining about my lack of phone savvy.
Hey Chris, just to let you know that it worked perfectly, thank you for your help it was much appricated.
No worries glad that it worked as if it didnt then i would be out of ideas...
I have an Att Fuze running the stock 6.1 firmware from Att.
I tried running XDAndroid 2.2 Final build for my phone, it appeared to crash while loading so I hard-resetted my phone.
Despite the fact that XDAndroid is supposed to run completely off the sdcard and not touch my internal memory, it appears to have corrupted my phone!
TouchFlo no longer launches (it keeps saying touch screen to launch TouchFlo, and if I do it goes crazy trying to launch and failing over and over), the phone is VERY slow and laggy, and the worst of it all, I CANT RUN ANY UNSIGNED SOFTWARE ANYMORE! Any attempt to run any program that isn't signed results in "The file (whatever) cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found"
I can't even run PimBackup to backup my contacts and text message logs!
I tried to install HardSPL since I figured might as well flash a custom rom to it but it failed too! It kept saying "Error 246 Device not responding" even though it identified it correctly when its booted into WM, and when I force it into bootloader mode it starts the process but gets stuck at 0% and eventually HardSPL gives up.
Is there anything I can try? Any way I can backup not just my contacts buy my call logs, text logs, etc before trying to reflash it? Any idea why XDAndroid would do this to my phone?
From what I understand, it isn't specifically Haret that did it, but some weird response to an error in starting Haret. I can't remember exactly what I did but I tried to run Haret incorrectly (my finger slipped on the touch-screen) and after that nothing would run. It triggered some weird thing in the OS.
I've heard of some people needing to get into reset mode before they can flash their phone -- not sure what the process is though.
Might be best to post in THIS thread. Keep in mind, you don't want to keep creating threads. It doesn't help our forum at all...
Also, it helps to read the post in it's entirety then try it out or if you need further assistance, post a reply.
R^7Z said:
Might be best to post in THIS thread. Keep in mind, you don't want to keep creating threads. It doesn't help our forum at all...
Also, it helps to read the post in it's entirety then try it out or if you need further assistance, post a reply.
Click to expand...
Click to collapse
Sorry about that, pretty much every forum I have ever posted in prefers you to make a new topic instead of post in an existing one when you have a problem.
I'll post my question there, although I wasn't sure where to ask a question about disabling that annoying signed programs thing.
So let's start this thread by saying I was stupid.
In my desperation to upgrade my ROM I went and flashed my Focus with the new Omnia engineering rom. Stupid yes but it flashed. The reason I did it was non of the Samsung focus retail Roms would flash with the WP7 flashing tool not even the jK2 ROM. Which is suppose to be the basic 7004 ROM.
Every time I flashed it would say "This Rom does NOT match the device" or "this device is NOt retail."
So let me just state I had the "RTM Mango" flash on my device already flashed and worked. I was trying to upgrade the firmware and radio stacks. The phone aways worked and was NOT a demo device.
I have tried to flash:
1. jK2 stock Rom same error as above
2. Rom for v1.4 won't work same error as above
3. Rogers Rom on my AT&T focus same error as above.
Basically the only rom that flashed was the engineering rom for the Omnia.
Now the phone boots (with a Omnia splash screen ) I can get it to download mode I can even use the phone just none of the buttons work! I really just want to get a Samsung focus rom back on don't care if it's not Mango at the moment.
My questions:
1. Anyone got an engineering rom for the focus seems to be the only Roms that can load on my device
2. Anyone got some advise to get it back to a Samsung focus rom?
I know I shouldn't have but it's done and can't cry over spilt milk.....
I would really appreciate the help.
I'm not sure what you mean by Jk2's rom, but have you tried the 1.3 version, not rogers?
http://forum.xda-developers.com/showthread.php?t=1131022
this thread has rogers, att 1.4 and att 1.3, all for focus. Ive successfully flashed my 1.3 focus several times. Also, in this thread they talk about how flashing 1.4 is always iffy.
Best way to get back to a Focus ROM is probably to restore a backup that was taken when you upgraded the phone. I hope you can still connect the phone to the Zune software? If so, try that.
The Omnia has physical buttons, the Focus uses capacitive buttons only (for the front three). I'm not surprised the drivers are different.
Did you by any chance use a hack to get NoDo on the phone? The "debranding" hack shouldn't prevent flashing, but will result in you receiving a different ROM from the upgrade servers than was quite meant for your phone. Chris Walsh's update hack did not install the full set of update packages it should have, resulting in what has become known as a "Walshed" phone. Walshed phones, because they're kind of partway between updates, can't receive further updates. A tool was later released to fix a Walshed phone.
The fact that the Focus ROMs wouldn't flash but the Omnia onw would is quite odd; I'm not sure what would cause that.
If at all possible, I recommend restoring your phone to a retail configuration using a Zune backup, and them trying the official update path again. Only once you've exhausted your options there should you try anything else.
GoodDayToDie said:
Best way to get back to a Focus ROM is probably to restore a backup that was taken when you upgraded the phone. I hope you can still connect the phone to the Zune software? If so, try that.
The Omnia has physical buttons, the Focus uses capacitive buttons only (for the front three). I'm not surprised the drivers are different.
Did you by any chance use a hack to get NoDo on the phone? The "debranding" hack shouldn't prevent flashing, but will result in you receiving a different ROM from the upgrade servers than was quite meant for your phone. Chris Walsh's update hack did not install the full set of update packages it should have, resulting in what has become known as a "Walshed" phone. Walshed phones, because they're kind of partway between updates, can't receive further updates. A tool was later released to fix a Walshed phone.
The fact that the Focus ROMs wouldn't flash but the Omnia onw would is quite odd; I'm not sure what would cause that.
If at all possible, I recommend restoring your phone to a retail configuration using a Zune backup, and them trying the official update path again. Only once you've exhausted your options there should you try anything else.
Click to expand...
Click to collapse
Firstly thank you for the time you took to reply.
Yes the history of this device is quite a lengthy one. I did do a NODO hack to get it to NODO. I then used the internal MS bits leaked to the net to force it to Mango. I was picking up some funnies like no matter how quick or soft I pressed the back button it would go into multi tasking making the phone impossible to use.
So I looked and researched and found my firmware, bootloaders etc were way out of date. I flashed the Omnia rom onto the Focus in hope that it was the same phone but alas its to late now......
Ok so when I connect it to the PC Zune picks it up all dandy but as a new phone - Omnia not my old focus. Is there a way to trick it into thinking its my Focus?
The phone functions in the sense that it boots, I can use it just don't have any buttons to use it with. All the screen functions work perfectly.
I will download Walsh tool to un Walsh the phone and try again...
I really appreciate the help!
I don't think you can "trick" it into seeing it as your Focus, because from a software perspective, it just isn't. However, the restore points (backups) are tied to the hardware, not the software. To see if you can restore one, first check in Window Explorer at the path %localappdata%\Microsoft\Windows Phone Update\ and see how big the contents of that folder are. There should be hundreds of meg to a few gigs, depending on how big the backup is.
Now, that's only going to be the most recent restore point. If you made backups of your earlier restore points, you can send the phone even further back, hopefully to before quite so many things get messed up. However, each time you do an update with Zune it overwrites the location where the previous restore point was. Note that if you installed any updates through a mecanism other than Zune, for example usign the WPSHIFT tool that was used for the beta, it probably took a backup but might have put it in a different location (often in TEMP, which hopefully you haven't cleaned out).
If you have Volume Shadow Copies enabled on your PC (Vista/Win7/any recent Server), you may be able to use the Previous Versions feature to pull an older restore point than the most recent one, or to recover a restore point if it was deleted for some reason. Be careful, though - old shadow copies are deleted as space is needed for other things, but they aren't deleted atomically; it's possible you'll pull only half of an old restore point or something equally silly (they're made up of hundreds or thousands of small files).
Once you've got your restore point, I strongly recommend making a backup of it by copying the folder! Then, connect your phone and start Zune, and go to Settings -> Device -> Update. It'll probably say there aren't any updates available, that's fine. In the same part of the window where it says that, though, there should be an option to restore a backup (it'll give the date of the backup and a restore button). If that button isn't visible, re-copy the restore point over the location where Zune expected to find it (%localappdata%\Microsoft\Windows Phone Update\), and check for updates again.
As for the un-Walshing tool, it probably won't do anything on your OmniaFocus. It may fix the problem if you successfully use a restore point (and get back to a pure Focus), though. There's a good chance that the last restore point you have will be from right before you began the Mango update process, in which case your phone will be back in its Walshed state, ready for un-Walshing using the tool.
I hope that helps. If you do decide to try flashing again (if you don't have a restore point, this is probably the only option), make sure you're using a ROM for your hardware revision of the Focus. There are two, the 1.3 revision (the first one released), and the 1.4 revision (released later, identical except it uses a different Flash memory chip internally and therefore has different drivers). If you bought your phone any time in 2011, it could be either a 1.3 or a 1.4. There are a few ways to check, but one of the best (since your software is currently messed up) is to look under the battery. There's a sticker that should say soemthing like "rev1.3/rev1.4". You need to match that revision number when selecting a ROM to flash, or (even if it works) you wouldn't be able to access the phone's internal storage.
It seems a little unlikely to me, but it's possible that Walshing your phone made it report itself as an Omnia, thus the reason you could flash that ROM (but not the Focus ones). I'd expect that to be based on lower-level hardware checks, though.
GoodDayToDie said:
I don't think you can "trick" it into seeing it as your Focus, because from a software perspective, it just isn't. However, the restore points (backups) are tied to the hardware, not the software. To see if you can restore one, first check in Window Explorer at the path %localappdata%\Microsoft\Windows Phone Update\ and see how big the contents of that folder are. There should be hundreds of meg to a few gigs, depending on how big the backup is.
Now, that's only going to be the most recent restore point. If you made backups of your earlier restore points, you can send the phone even further back, hopefully to before quite so many things get messed up. However, each time you do an update with Zune it overwrites the location where the previous restore point was. Note that if you installed any updates through a mecanism other than Zune, for example usign the WPSHIFT tool that was used for the beta, it probably took a backup but might have put it in a different location (often in TEMP, which hopefully you haven't cleaned out).
If you have Volume Shadow Copies enabled on your PC (Vista/Win7/any recent Server), you may be able to use the Previous Versions feature to pull an older restore point than the most recent one, or to recover a restore point if it was deleted for some reason. Be careful, though - old shadow copies are deleted as space is needed for other things, but they aren't deleted atomically; it's possible you'll pull only half of an old restore point or something equally silly (they're made up of hundreds or thousands of small files).
Once you've got your restore point, I strongly recommend making a backup of it by copying the folder! Then, connect your phone and start Zune, and go to Settings -> Device -> Update. It'll probably say there aren't any updates available, that's fine. In the same part of the window where it says that, though, there should be an option to restore a backup (it'll give the date of the backup and a restore button). If that button isn't visible, re-copy the restore point over the location where Zune expected to find it (%localappdata%\Microsoft\Windows Phone Update\), and check for updates again.
As for the un-Walshing tool, it probably won't do anything on your OmniaFocus. It may fix the problem if you successfully use a restore point (and get back to a pure Focus), though. There's a good chance that the last restore point you have will be from right before you began the Mango update process, in which case your phone will be back in its Walshed state, ready for un-Walshing using the tool.
I hope that helps. If you do decide to try flashing again (if you don't have a restore point, this is probably the only option), make sure you're using a ROM for your hardware revision of the Focus. There are two, the 1.3 revision (the first one released), and the 1.4 revision (released later, identical except it uses a different Flash memory chip internally and therefore has different drivers). If you bought your phone any time in 2011, it could be either a 1.3 or a 1.4. There are a few ways to check, but one of the best (since your software is currently messed up) is to look under the battery. There's a sticker that should say soemthing like "rev1.3/rev1.4". You need to match that revision number when selecting a ROM to flash, or (even if it works) you wouldn't be able to access the phone's internal storage.
It seems a little unlikely to me, but it's possible that Walshing your phone made it report itself as an Omnia, thus the reason you could flash that ROM (but not the Focus ones). I'd expect that to be based on lower-level hardware checks, though.
Click to expand...
Click to collapse
Thank you for the reply!
So looks like I am screwed. I looked for the backup and nothing on my machine even tried volume shadow copy and nothing in the Windows Phone Update folder.
I might have to try create a USB JIG to force a flash onto the phone. That should work right? That should flash which ever ROM I like regardless of the checks that things like WP7 Downloader do?
I would appreciate the guidance before I go ahead and build the USB JIG.
PS _ Anyone know what files are inside the backup folder maybe I can search windows for those and find the back up folder somewhere
The updates are usually stored here:
"C:\Users\%YOUR_USER%\Local Settings\Microsoft\Windows Phone Update\"
Either search for a "RestorePoint" folder (without quotes) or "Data.0.dat" "Data.1.dat" etc files
EnderPsp said:
The updates are usually stored here:
""
Either search for a "RestorePoint" folder (without quotes) or "Data.0.dat" "Data.1.dat" etc files
Click to expand...
Click to collapse
THANKS so much I FOUND a backup C:\PreMangoState
This is when I did the Mango upgrade using the "MS internal leaked" files.
Going to try this.
I am going to suggest you try the engineering ROM for the Samsung Focus: http://forum.xda-developers.com/showthread.php?t=1045968
day2die said:
I am going to suggest you try the engineering ROM for the Samsung Focus: http://forum.xda-developers.com/showthread.php?t=1045968
Click to expand...
Click to collapse
THAT WORKED YOU ROCK
Now can I ask why only engineering ROM's are working and will I be able to get it to MANGO?
myphonerules said:
THAT WORKED YOU ROCK
Now can I ask why only engineering ROM's are working and will I be able to get it to MANGO?
Click to expand...
Click to collapse
So as soon as I plugged it in Zune found the phone and upgraded all the upgrades all the way to mango
Thank you once again. Do you know what the latest GSM firmware is?
I have similar problem except mine is stuck on the samsung logo screen so cannot connect to zune.
I am trying to flash this engineering ROM that seemed to work for you, but it keeps saying Error!! "This Device does NOT match with selected binary. Downloader will NOT do anything" and thus the flash will nto complete.
Any suggestions?
neibl said:
I have similar problem except mine is stuck on the samsung logo screen so cannot connect to zune.
I am trying to flash this engineering ROM that seemed to work for you, but it keeps saying Error!! "This Device does NOT match with selected binary. Downloader will NOT do anything" and thus the flash will nto complete.
Any suggestions?
Click to expand...
Click to collapse
Have you tried the retail roms (check the general forum there is a sticky with the retail roms) if you getting the error "This device does not match with the selected binary" with the flasher it could be one of two things:
1. Your device is not an engineering device and you need to use the right retail rom.
2. Which version of the WP7 Downloader tool are you using 7.05, 7.21 or 7.41?
For the retail ROM you should use 7.05
For the engineering ROM you should use 7.41.
7.41 comes with the new leaked Samsung OMNIA 7 ROM (Do a search for that rom) DO NOT FLASH (like I did ) the OMNIA ROM onto your focus it will not work.
The other question is if your phone is stuck on the "SAMSUNG" screen can you get it into DOWNLOAD mode (Turn the phone off, then hold CAM + VOL DOWN and POWER) It should then turn on and go into DOWNLOAD MODE. The WP7 tool will only see the phone is in DOWNLOAD MODE. From what you telling us with the error above you are getting into DOWNLOAD MODE but just confirm.
IMO if you can still get into DOWNLOAD MODE not all is lost.
I already have flashed the omnia ROM onto my phone that is why I am in this problem. I have reflashed the focus ROm but it is frozen on the logo screen no matter what I do.
Seems like this engineering ROM fixed it for the lad who created this post, so I might give it a try, what do you think?
Yes I can get the phone into download mode & also the format mode (it doesn't do anything though), I cannot connect the phone to zune because it freezes on the logo screen before launch. Also I have 7.03, 7.05, & 7.21 and have tried all of them thus far, did not know of the 7.41.
So 7.41 and flash the engineering rom? It sounds like you have some ideas, please share it would be greatly apreciated.
neibl said:
I already have flashed the omnia ROM onto my phone that is why I am in this problem. I have reflashed the focus ROm but it is frozen on the logo screen no matter what I do.
Seems like this engineering ROM fixed it for the lad who created this post, so I might give it a try, what do you think?
Yes I can get the phone into download mode & also the format mode (it doesn't do anything though), I cannot connect the phone to zune because it freezes on the logo screen before launch. Also I have 7.03, 7.05, & 7.21 and have tried all of them thus far, did not know of the 7.41.
So 7.41 and flash the engineering rom? It sounds like you have some ideas, please share it would be greatly apreciated.
Click to expand...
Click to collapse
Ok so you need to download the latest Samsung Omnia 7 ROM it will have the WP7 Downloader 4.21. Thats the only one that will flash the engineering ROM onto the device.
Zune will not pick up the phone till it completely boots so Zune wont help you in this case. You have to try and fix it using your WP7 downloader(s).
This is the link I used to get the Downloader: http://www.mobiletechworld.com/2011/10/15/update-your-samsung-omnia-7-to-the-latest-i8700xxki3-firmware-now/
Good luck!
Engineering ROM did not work, still frozen on samsung logo screen, something is definitely broken on the phone that will not let it get past this point and I have no idea. Seems like no one else knows either as no one has been able to solve this for over 7 months.
If anyone thinks they can solve this please suggestions are welcomed. If you need more details please let me know. If someone can fix this I'd be willing to paypal them real cash no joke.
Much thanks to myphonerules for helping!
If I call samsung and complain will they tell me i'm out of luck? I got the phone off ebay so its not covered by anything.
neibl said:
Engineering ROM did not work, still frozen on samsung logo screen, something is definitely broken on the phone that will not let it get past this point and I have no idea. Seems like no one else knows either as no one has been able to solve this for over 7 months.
If anyone thinks they can solve this please suggestions are welcomed. If you need more details please let me know. If someone can fix this I'd be willing to paypal them real cash no joke.
Much thanks to myphonerules for helping!
If I call samsung and complain will they tell me i'm out of luck? I got the phone off ebay so its not covered by anything.
Click to expand...
Click to collapse
You sure you don't have a DEMO phone? Has it ever worked on a GSM network?
No its not a demo phone, i used the phone with my AT&T SIM card for few days. Then i put in a 32mb microsd card and after 24 hours it reset into a gimped mode with only 15 mb where i couldn't do anything and had no at&t apps on it strangly also. I flashed the samsung omnia 7 ROM onto the phone and would not load past the omnia 7 load screen. Then I flashed the focus ROM (it wasn't available originally) back and it would not load past the samsung screen. By this point I really just think the phone is completely done.
Any suggestions? or think its garbage?
I'm debating buying a focus with broken screen off ebay and using the screen from this one to replace it and bam pretty much new phone.
Is there a way to get a convert a non retail focus to retail? Is there a retail ROM available for the focus that can be flashed on the non retail version?