Dones anyone has step by step tutorial how to update omnia 7 from nodo to beta2 mango ? thx in advance
I'm intersted as well what to do exactly.
This is what i did,
1. Flash you phone with Samsung Omnia 7 Firmware XXJL3 RETAIL UNITED KINGDOM. you should have v7004 installed.
2. Plug phone in to PC and check for updates with Zune, it should say that the Feb update is available, install this update. (if you have problems installing this, make sure your USB cable is connected to a USB port that is physically on the motherboard and try again)
3. Check for updates again, this should say that the NODO update is available, install this update.
4. Follow the instruction on THIS site to get the mango updates.
NOTE: When i tried this with the KC1 firmware, my phone would get stuck in a reboot loop when going through the instructions in step 4, i had no problems with JL3 firmware.
Anyone had any problems with Mango yet? Crashing, laggy, etc?
I'm curious, do most apps work with Mango? Or will they all disappear/fail to open once I update. Also, does this process/"restore.bat" delete data ie. game saves?
I'm interested in updating to Mango, but not at the cost of lost apps/saves either during the update or restore.
I have no crashes at all with mango, the OS is a a lot more responsive overall.
I have only brought one app on my Omnia, all i needed to do was go in to the marketplace and redownload and install it again.
Thanks for the instructions Duck!
I followed them to a 'T' (minus the firmware updates, my phone was bought unlocked and unbranded) and it worked great! All my game saves, apps, etc. were there and Mango runs smooth as silk!
The only downside (and the link mentioned this) was that Zune does not sync with my phone anymore. It requires and 'update' and once you try and get that update Zune errors ('Cannot find update file: blah blah'). So it looks like this currently Mango build prevents Zune syncing (although wifi might still work, I'll have to test it).
Download the Beta version of Zune HERE.
Awesome, that worked great! Where do you find this stuff?! Hah, thanks again.
I always get the timeout when it is restarting for the first time.
OS: 7.10.7712.60
Firmware:2424.11.3.1
Hardware Revision Number: 3.15.0.4
Radio software version: 2424.11.2.2
Radio hardware version: 0.0.0.800
Bootloader version: 5.3.0.4
Chip SOC versopm: 0.36.2.0
Available space: 2.49 GB of 7.39 - I deleted the music as someone in another thread suggested but no help.
Edit: Suspending the process and deleting the unneeded files worked for me.
does anyone know if you lose the Live Services activation key after the a Mango Update? thanks in advance
singularity0821 said:
(...)
Edit: Suspending the process and deleting the unneeded files worked for me.
Click to expand...
Click to collapse
Can you explain wait you did, please?
I'm stuck on "Restarting your phone...".
The phone reboots, waits on backup/download mode (bw image of phone linked to PC) and nothing else happens till .cmd gives a time out.
Applying updates to device
Id: \\?\usb#vid_045e&pid_04ec&mi_00#7&b4f563e&0&0000#{ca3d7387-f67b
-11da-bbec-8000600fe800}
SN: (...)
Name: (...)
KITLName: (...)
Manufacturer: SAMSUNG
ModelId: 4
Model: OMNIA7
MobileOperator: (...)
Version: 07.10.07712.03-00.00.00000.00-00.00.00000.00
Checking your phone's status: Completed in 0.03 seconds
Checking system requirements: Completed in 0.02 seconds
Downloading updates: Completed in 3.02 seconds
Checking system requirements: Completed in 0.02 seconds
Transferring updates: Completed in 1.84 seconds
Preparing to install: Completed in 14.13 seconds
Restarting your phone..
UPDATE: SOLVED! Uninstalled Zune and UpdateTool, rebooted, installed Zone and UpdateTool again, rebooted, updated phone.
Related
Hi all,
I am new to this Kies flash process and have read people having problems when updating their ROM to official releases.
I am currently on JF3 and Kies is offering JM1, I want to upgrade but am wondering if there is a "recommended" way to update?
I have an unrooted phone and have installed software like Launcher Pro, Advanced Task Killer, Alarm Master etc...
I was wondering if I should do a factory reset first on the phone before I upgrade to JM1?
I am running Windows 7 and Kies is on version 1.5.1.10074.2 running in Administrator mode and I have Antivirus turned off.
Any tips for a hassle free update greatly appreciated
Thank you in advance
No just update via Kies... Unless you havent rooted your phone and you dont have a lagfix installed you can update the normal way.
Remember that your data may be corrupted after upgrade and i would advice to do a factory reset after upgrading the firmware to clean up the phone.
So backup your data!
there is a new version of Kies out just today
link is in the wiki
Thank you for the info guys. I did the upgrade and it work flawlessly.
Got a bit scared when Win 7 said that it was installing drivers halfway during the install and the device appeared to get disconnected
But the progress bar kept going and I waited about 5 minutes and it completed and rebooted the phone. Now I am on JM1 and it does run better
I will check out the new Kies too.
Thanks again for the input.
Hello Guys,
I had rooted my SGN before & restored to stock ROM DXKL2. However whenever i tried to update the firware from Software Update, it always says "Failed to update firmware. Try again using PC software (Kies) or Visit Samsung Service Center".
The update download & installation seemed to run well accordingly, but after reboot with "Uploading Media Files" display, the screen simply goes off half way for reboot again, and once SIM PIN gets input, the above display shows up.
May i know how is this happening? Thanks in advance.
Denim Guy said:
Hello Guys,
I had rooted my SGN before & restored to stock ROM DXKL2. However whenever i tried to update the firware from Software Update, it always says "Failed to update firmware. Try again using PC software (Kies) or Visit Samsung Service Center".
The update download & installation seemed to run well accordingly, but after reboot with "Uploading Media Files" display, the screen simply goes off half way for reboot again, and once SIM PIN gets input, the above display shows up.
May i know how is this happening? Thanks in advance.
Click to expand...
Click to collapse
What was the Firmware version when you bought the Phone?? If it is different than KL2, Try restoring firmware which was ter when u bought it. Then Update via Phone or Kies.
Thanks for the tips, Mr Ranjan.Alva. It really worked when i flashed it back to its out of the box stock ROM DXKJ3 Gingerbread 2.3.5.
It could simply download, install & reboot perfectly to latest ROM DXLA1 now
Sorry, but I refuse to give this phone up yet as I love the size, weight, etc.
I unlocked this phone awhile back and through the software upgrades, the GPS stopped working (works maybe 2% of time)
Any idea's if I can reflash the ROM, drivers, firmware, etc. to try to get this GPS alive again?
AT&T
Windows 7.8
OS Version 7.10.8862.144
FW V: 2103.11.10.1
HS V: 25.1.0.8
Radio S Version: 2103.11.10.1
Radio H Version: 0.0.0.0
Bootloader 5.10.2.0
Chip SOC 0.74.2.1
Thanks.
7carisfast said:
Sorry, but I refuse to give this phone up yet as I love the size, weight, etc.
I unlocked this phone awhile back and through the software upgrades, the GPS stopped working (works maybe 2% of time)
Any idea's if I can reflash the ROM, drivers, firmware, etc. to try to get this GPS alive again?
AT&T
Windows 7.8
OS Version 7.10.8862.144
FW V: 2103.11.10.1
HS V: 25.1.0.8
Radio S Version: 2103.11.10.1
Radio H Version: 0.0.0.0
Bootloader 5.10.2.0
Chip SOC 0.74.2.1
Thanks.
Click to expand...
Click to collapse
I have had a couple of GPS issues, ususally when it get hot on my dash board or with dodgy weather normally a reboot fixes it. Its possible that you've accidently buggered up the GPS settings, a hard reset will fix that.
As for a flashable ROM or newer firmware that fixes things? there is 2103.12.5.2 firmware that should get downloaded automagically via zune but other than that (which did bugger all cept fix some audio clicking and keyboard lag issues) it does nothing else, be warned though, that is the firmware that will stop interop from being enabled via the old way, you will need to use heathcliffs newer method after installing it
there is no flashable ROM either.
Thx Dazza
A big thanks Dazza. You've been a tremendous help directly to me. I'd love to do a reset, but the most important part of the process is remembering what to do when as far as backups, unlocking etc. I have the "Internet Sharing" feature unlocked and I don't want to mess that up. Always the question of reward vs. risk.
Hey guys!
It's been a long time since I've stopped by, but I hope you can help me
Last week, I decided to give Windows 10 for Phones a shot on my Lumia 820. It was a complete pain in the ... Basically nothing seemed to work properly, so I decided to go back to WP8 / WP8.1.
The downgrade to WP8.0 with the Recovery Tool worked almost without any difficulties. Getting my Backup to work wasn't a problem either...
After I got the main stuff (Homescreen, App settings, etc) up and running, I installed the Preview for Developers App to upgrade to the latest version of WP8.1 to get Cortana working here in Germany
But after the first two updates, I still don't have Cortana - I'm stuck at WP version 8.10.14192.280.
The Cortana build should at least be 8.10.14219.341.
Every time I try to check for updates, WP comes up with Error Code 80072f8f.
After hours of searching and reading, the only cause for this error I could find was a wrong set date, time or region setting.
Date, time and region are all correct, it doesn't make any difference if i set it automatically or manually. Store apps can be installed and updated without any problems - which shouldn't be the case if any of the above settings were wrong. Updating to the phone`s current OS version worked flawlessly with those settings.
I've manually checked for updates about 30 times over the last few days, to rule out any server-side problems regarding windows update.
when the phone is connected to my pc running Windows phone recovery tool, my pc can't find any newer version of WP either.
Am I doing something monumentally stupid? Or is there any known issue I am encountering? I have no idea what to do anymore... :/
Btw. The about section in settings shows the following:
Model: Nokia Lumia 820
Carrier: o2 DE - v294.02
Software: Windows Phone 8.1 Update
OS version: 8.10.14192.280
Firmware revision number: 3051.40000.1347.1005
Hardware revision number: 2.4.5.0
Radio software version: 1.0.202158.3
Chip-SOC-Version: 8960
Thanks in advance
Try changing your region to US or UK and then search for update
tried 5 different regions so far... didn't make any difference :|
Did you ever get your phone to check for updates? I have a Nokia Lucia 635 and wanted to put windows 10 on it, so i did all the steps, got updated to Lumia denim and now i have the same issue you were having. 80072f8f I have tried everything but a reset.
Sent from my SAMSUNG-SGH-I577 using XDA Premium 4 mobile app
What is the latest official firmware for the Samsung Gear Live?
I've been searching all over these forums for the Samsung gear live, and all over the internet also. I just bought a gear live off of Amazon for $100 and it's supposedly new. It currently has:
Software version: 5.0.1
Build Number: sprat-userdebug 5.0.1 LWX48P 1627902 dev-keys
Android Wear: 1.0.5.1627902
Google Play Services: 6.5.90 (1610726-534)
1) Is this the latest firmware?
2) Is this official firmware? Developer Firmware?
3) Will I get Updates on device? (Says up to date currently on the watch when I try to update on the watch)
Thank you so much for any help you can give me!
If you didn't figure out till now then read below
No this is not the latest firmware
The latest is 5.1.1
Connect the watch to your smartphone and then check for update on your watch(your phone should have internet connection)
You may need to use the gear live restore tool to change to non dev firmware (read the thread, don't use the latest version of tool)
Current:
Wear: 1.3.0.2160025
Play services: 8.3.01 (2385995-534)
Os: 5.1.1
LCA43
Thank you so much guys for all your posts. I used version 2 of the Samsung Gear Live Restore Tool to flash my watch back to stock settings, then used the normal updates via OTA on the watch.
I used the download link and the video from this post:
http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696
The video was step by step and super easy to follow ( Thanks Tom! )
I was in the same exact boat. $100 new from Amazon and had the same exact Software version, Build Number, Android Wear, and Google Play Services as the original poster. Went through the same steps, however I had to fight my computer a bit on the drivers.
In case this helps anyone else: I'm on Win7 64-bit. The first hurdle was getting a microUSB cable that worked (the USB multi-dongle I was trying to use turned out to be crap). Until I got a better cable, the Gear Live was not getting recognized by my computer at all. When it finally did, the drivers weren't getting set up correctly. I went to Device Manager, found the unknown device, right clicked and hit Update Driver Software (see about the 5:30 mark in Tom's video). I had two problems here:
1) My computer initially recognized the device as "Android Composite ADB Interface". That doesn't seem to work, make sure sure it's just "Android ADB Interface", NOT Composite. When I ran the driver check in the Gear Live tool, the device was now finally showing up for the ADB check.
2) But it wasn't showing up for the Fastboot check. To fix that, I had to GO BACK INTO DEVICE MANAGER after the ADB check, while the watch was in bootloader mode, find Android Device (or something like that, I forget what it was called), and again hit Update Driver Software and select the Android ADB Interface again. Once I did that, everything else in the video and Gear Live tool worked flawlessly.
I also wound up restoring the Gear Live watch to stock (option 6 in the tool), and it's downloading the OTA software update now. I'll post here if I hit any other snags.
Thanks again for posting this. Definitely helped me out.
EDIT: Note that if you go the OTA route, you're going to have to do multiple updates to get from the stock version up to the most current version. For example, stock starts out at 4.4W. It won't update from that all the way up to 5.1.1 in one shot. It'll do it in increments and take 3 or 4 updates. A little time-consuming, but otherwise I've had no further issues.
ROM History: http://forum.xda-developers.com/wiki/Samsung_Gear_Live
EDIT: Updating finished, here's the result:
-- Build Number LCA43
-- Android Wear 1.3.0.2160025
-- Google Play services 8.4.89 (2428711-534)
-- Android OS 5.1.1
I've never used my mac to do anything like this. What program do I need to open the gear live tool in, it's a .sh file and just opens in notepad. Thanks
would this lack of OTA updating ability cause the basic programs (Maps, google play music, etc.) not to work? Why is Samsung completely oblivious to this issue?
I have the sprat-userdebug 5.0.1. I'll be using this thread to fix it, I hope. But I cant get most of my apps to work on the watch. Hoping this will resolve it.
Thanks.
OTA now provided to convert from dev-keys to release keys
Today we are rolling out an OTA update to "sprat" Android Wear devices from Samsung that were stuck on a very old LWX48P firmware and old Google Play Services. These devices were sold with a non-standard "dev-keys" firmware, whereas normally devices use "release keys" firmware. dev-keys devices do not receive updates for anything. We have added a special OTA update that converts the LWX48P devices from dev-keys to the proper release keys LWX48P, and that will then allow the OTA update system to bring the watch completely up to date.
For users, it will take a few days for the update to be made available to everyone. After applying the update, you will need to factory reset and pair the watch up again, and then it will apply the latest updates that were previously skipped.
For developers, you will need to wait for users to apply the update and then you should see a drop in the number of old sprat devices showing dev-keys and old versions of Google Play Services. With this update, any user will have an easy to use path to get back to receiving regular updates.
See more discussion about this in my G+ posting ... plus.google.com/+WaynePiekarski/posts/izipAZnd56C