I'm sure a lot of you must have thought about this. Since the NoDo update would supposedly start rolling out anytime this week, I'm wondering if it would be possible to extract the ROM from the update?
Assuming that the update process is similar to iOS (since we have to update through Zune) and all the files are downloaded to the PC first, it is possible that the ROM is also downloaded to the PC from where it can be extracted.
If this works, will it be possible to use that ROM/Firmware and flash it on other devices? Say a NoDo update ROM from an AT&T Focus could be used to revive (mine and a lot of other) Samsung Focus devices.
Someone might have to play with the Microsoft Windows Update Service Protocol a bit to get this idea to work, but I'm sure it would be worth the effort.
I would have given it a shot myself but I recently had to return the HD7 review unit I had and my personal Samsung Focus is laying dead.
actualy update could have OEM SOFTWARE PARTS .. like new kernel or driver update .. also - RRUU counts as FFU ( full flash update ) and could not flash partial update .... since ms distribute updates in packages for corresponding os parts . not full image
I think WP7 update process is more complicated than iOS. WP and its build system support differential update, not only full flash update. So the update file could be just part of system files.
There is a com dll you can look into ZuneWmdu.dll, but i was not able to create a com instance in c#. (Maybe i was quiet stupid yesterday or there is really a problem). You should be able with the api to make your own update tool, but since the phone does the request for the firmware/update/rom this could be a little bit complicated.
Flow WP7 said:
There is a com dll you can look into ZuneWmdu.dll, but i was not able to create a com instance in c#. (Maybe i was quiet stupid yesterday or there is really a problem). You should be able with the api to make your own update tool, but since the phone does the request for the firmware/update/rom this could be a little bit complicated.
Click to expand...
Click to collapse
Hmm from what I've heard, the Zune client uses the Zune pass through connection to the phone which checks for updates on its own.
The problem is that if it is a delta update then it would be impossible to build a complete system image from the update.
I wonder if it still would be possible to use ROMs from another similar device but replace driver and device specific files from the original device. That would be sort of a custom ROM.
Related
With all these unofficial ROM's, is it actually safe to use windows update for windows mobile?
it will actually never works since
1. There are no working wa/ota servers
2. There is no IU flag in imgfs
3. Most roms have IU loader removed
i always get an code0x000000000 (No update available). I have a LG KS20. Is this update Device specific or how does it work?
because of what sp3dev said and lazyness on ms's part
it is not Device specific because it dont work on any devices i know of
Um.....?
so u can't update ur device?
seems so, a feature with no function....
Hi guy
into setting - system menu there is the windows update icon.
i can't use it because everytimes i have an error with the server connection.
are there any configuration or anythings to do for use it?
thank you
it doesn't work with our phone.
doesnt work with any phone. ms has never released an ota update.
it only existed in 6.1 anyways. what would they update that you wouldnt need a new rom for?
The Jack of Clubs said:
it only existed in 6.1 anyways. what would they update that you wouldnt need a new rom for?
Click to expand...
Click to collapse
Only once, AT&T released two hotfixes for their Tilt2 in the form of .cab.pku files, which are CAB installers capable of overwriting files in ROM, permanently patching the problem files. Of course, Windows Update mobile failed to deliver them, automatically or otherwise, so you still had to download them from AT&T regardless...
@OP: Windows Update mobile is absolutely useless, don't waste your time actually checking for updates.
att didnt use windows mobiles windows update. the tilt 2 only had 6.5 for one, and the hotfixes used a rom updater like thingy. itll actually try to update from microsoft but fails. im running htcs stock 2.07 rom anyways.
I used Nokia Care Suite to get the AT&T Tango update for my cyan Lumia 900. Since then, I've seen a couple of older posts (pre-Tango) that talk about not being able to update your phone through Zune if you used Nokia Care Suite to update a device, but the thing I can't lock down is if that is only if the ROM used was not an official one. Does anyone have any feedback on this issue? Have I hosed myself a little and now I can ONLY update using NCS or since I used the official ROM, am I still good to update through Zune whenever another update is available? Thanks, and sorry if I'm asking a questions that's been answered before .
Relax. If you flashed the official ROM designated for your phone then you're good to go. The Zune update installs the latest ROM in steps (3 in the latest update) file by file and leaving data/settings in place. Flashing wipes the device and replaces everythng with a factory fresh ROM image that already includes both the latest OS and Nokia firmware tweaks.
Cheers
dougthug said:
I used Nokia Care Suite to get the AT&T Tango update for my cyan Lumia 900. Since then, I've seen a couple of older posts (pre-Tango) that talk about not being able to update your phone through Zune if you used Nokia Care Suite to update a device, but the thing I can't lock down is if that is only if the ROM used was not an official one. Does anyone have any feedback on this issue? Have I hosed myself a little and now I can ONLY update using NCS or since I used the official ROM, am I still good to update through Zune whenever another update is available? Thanks, and sorry if I'm asking a questions that's been answered before .
Click to expand...
Click to collapse
One of the great things about xda, things do go untried. Maybe there has been no success in breaking the OS, but the people around here push everything else.
I didn't know for sure if using Nokia Care suite would allow me access to the future updates. So, I used the Suite to downgrade from tango. Plugging into Zune immediately triggered the Tango update packages, all 3 of them.
I figure if it works going backwards, it will work going forwards. So, as the last responder said...Relax, you're good dog.
alodar1 said:
One of the great things about xda, things do go untried. Maybe there has been no success in breaking the OS, but the people around here push everything else.
I didn't know for sure if using Nokia Care suite would allow me access to the future updates. So, I used the Suite to downgrade from tango. Plugging into Zune immediately triggered the Tango update packages, all 3 of them.
I figure if it works going backwards, it will work going forwards. So, as the last responder said...Relax, you're good dog.
Click to expand...
Click to collapse
Excellent news. Thanks for the reply's
dougthug said:
Excellent news. Thanks for the reply's
Click to expand...
Click to collapse
In Nokia Care Suite, if you want to experiment and flash your phone with an update not yet available for your product code, you can rename another ROM with your own code and it will work, but then your phone is "walshed" - ie; won't update through Zune but you can always reflash.
As mentioned before, as long as you use the ROM with name matched to your own product code, Zune will work fine.
I just read this article from Android Police....I copied and pasted this. The link is below..... PSA: New Lollipop OTA Procedure On Devices With Verified Boot Means Your Update Will Fail If Your System Is Modified In Any Way At All
Published on November 13th, 2014
Written by: Shawn De Cesari
Next
Skip to Responses
Prev
Ever since the beginning, Android OTA updates have worked by patching each file on your system partition individually. With Lollipop, that is all changing, and it has some important implications for those who like to root and mod their devices.
Here's what a pre-Lollipop update script looked like:
image
As shown, the recovery looks at this, finds each file, checks its signature, then applies a patch to it if it matches. This is the slow way of doing things, but it had a big benefit for rooters and those who like to mod their devices. As long as none of those files were touched, you could have anything you wanted on your system partition (the "su" binary for instance, maybe an INI file for a root app, etc.) and you could still apply OTA updates successfully.
With Lollipop, this has all been turned on its head because now, the OTA script no longer patches individual files. Instead, it patches the system block directly and treats it as one enormous blob. Here's a look at the update script in a recent Nexus 9 OTA:
image
From a technical standpoint, the reason behind the change was the addition of verified boot functionality in Lollipop. Though verified boot was introduced in KitKat, it appears that Google has only started using it with the Nexus 9 and (presumably) Nexus 6.
As for whether or not older devices like the Nexus 5 or 7 (that were updated to Lollipop from older versions) will have this same issue, that remains to be seen. We'll have to see what happens when those devices get their first Lollipop -> Lollipop OTA update.
Even outside of verified boot, though, it makes all the sense in the world to do OTAs this way. Patching the system block directly is far faster than trying to patch a lot of individual files. That said, if you're one of those who like to tinker with your devices, you'll have to flash a completely stock system image before applying an update because changing anything by so much as one byte will throw off the signature and make it so the OTA will fail.
Android Source Documentation
Original Article here:http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
So, I just went through hell trying to go back to stock for the 4.4.4 update. after about 4 hours of complete brain screwing I finally managed to do it, and don't know how I did it, through different flashable ZIPs, nandroid backups, FUUs, RUUs, etc...
My question is, "Would it be better for me to leave my phone on the stock image until the Android L update or go ahead and root it again and wait & look for a rooted version of the Android L to appear on XDA after it comes out?"
Hey everyone, this is a carryover post from the LG G7 Reddit. As of now, there are a number of people out there with US model firmware flashed phones that don't allow updating via normal methods (most commonly PM/Sprint phone flashed with ULM/Unlocked firmware). The only way for these users to update their phone is to flash an updated kdz with LGUP's refurbish option, which causes the phone to be wiped (while it's possible to backup most elements of the phone, it'd be ideal if a normal FOTA update could be obtained and executed on these devices). I used to own one of these phones, before obtaining a factory ULM version. The phone I bought was running the October (10g) update so I was hoping I could just capture the 10i update and share that to users that needed an alternative way to upgrade with the FOTA update.
However, LG apparently has their phone updates in a cumulative/rolled up package (in this case, my phone downloaded this 522MB file when updating, even though I'm sure only a small portion was ultimately needed). When opened with a program like 7-Zip, only one, much smaller file is shown (I don't know if this is actually a kdz file or something similar since 7-Zip is unable to correctly read the header/contents). This could very well be the same file one would download if using LG Bridge (although the PM/Sprint model => ULM/Unlocked converted phones are not detected by that program). I've only worked with HTC/Samsung/Nexus+Pixel-branded phones in the past, so I know little to nothing about LG's packaging and update methodology. Any assistance in creating (or explaining how one might go about creating) a FOTA file that could be sideloaded or flashed with LGUP would be amazing. Cheers!
Hello, updating with lgup doesn't need to be with the refurbish option. There is an update option witch keeps data.
Usually other kdz models can't be flashed on other models (but certainly possible). That also goes for update files.
FOTA updates can't be extracted with simply opening it with a 7zip. Btw how did you get the link to that update?
LameMonster82 said:
Hello, updating with lgup doesn't need to be with the refurbish option. There is an update option witch keeps data.
Usually other kdz models can't be flashed on other models (but certainly possible). That also goes for update files.
FOTA updates can't be extracted with simply opening it with a 7zip. Btw how did you get the link to that update?
Click to expand...
Click to collapse
Thanks for confirming the information about using the update option. Another XDA user, tycrek, was able to do the same with the aid of a modified dll file (which seems to be a requirement for getting official apps to recognize modified phones; LGUP Dualmode is nice too, even if you don't need to touch the dev side). I'm unsure what type of modifications their phone had from stock though (if any).
The used market is flooded with a lot of G7 phones that were originally Sprint models that have had the unlocked/Google Fi firmware flashed to them (there is an active thread here about the subject; one of the most prolific sellers of these phones is even actively posting replies). If anyone is unsure, go to the phone's Hardware Info in the Settings. If the model is LM-G710ULM but the S/N is blank, then it's likely one of these phones. OTA Updates as well as using Google Pay are both unavailable to these phones as well (flashing the Verizon firmware to the phone can supposedly fix both of these issues, however, I didn't know about this at the time and so I couldn't test it before getting a replacement).
As far as my use of 7-Zip, I was hoping that the file was, in reality, a zip file that just had its extension removed, but obviously, that's not the case =). I still want to figure out the format of this file and extract the contents from it (I'm just waiting for some free time to appear!) As far as obtaining the link, I was fortunate, in that my phone was due for an update that had already been released. Using the 1st method in this tutorial, I was able to capture the URL that my phone was updating from (LG seems to be making use of Limelight Network's CDN to give users faster downloads... I'm sure other files are being hosted as well, but I'm not sure how they could be located aside from trying to find a pattern in the naming scheme).