Hi everybody
I own an Xperia Pro MK16i. The phone is still on stock ROM (4.0.2.A.0.58 GB 2.3.4) and the bootloader is still locked. The only thing I did recently is root the phone successfully with eRoot.
Now, the phone still gets the OTA updates, right now it does notify me that the "new" update 4.0.2.A.0.62 (the latest GB release available for my phone) is ready to download. I would like to install this update in order to try it and only after eventually switch for ICS 4.0.4 (4.1.B.0.587 is the latest).
I was wondering myself:
1) Is there any way to backup the OTA update in order to save and store it for the future? I red that OTA update files end up in the /cache folder and thank to root access I managed to open that folder and see that as soon as I download the OTA update a download_package.bin is created inside the folder; the problem is that the file is less than 8MB and it's a BIN file. What this file is for and is there any way to make use of it? The only thing I know is that it's too small to be the real firmware/rom...right?
2) Is there any chance for me to get somewhere the 4.0.2.A.0.62 stock rom with the proper customization number? My phone is unbranded and purchased in Italy where I live, customization version is: 1249-7782_R12D
3) What does this customization mean? Is it about language? About preinstalled apps? Or what? Someone could clear me the whole thing please?
Many thanks
goriath said:
1) Is there any way to backup the OTA update in order to save and store it for the future? I red that OTA update files end up in the /cache folder and thank to root access I managed to open that folder and see that as soon as I download the OTA update a download_package.bin is created inside the folder; the problem is that the file is less than 8MB and it's a BIN file. What this file is for and is there any way to make use of it? The only thing I know is that it's too small to be the real firmware/rom...right?
Click to expand...
Click to collapse
OK, I digged around about this point and just for reference I share what I found.
The main problem with OTA updates is these packages are binary DELTA packages; they are not the full ROM/FW release, but they contain only the differences between the source ROM (the firmware installed in the phone) and the target ROM (the updated firmware you want to install in the phone).
I took a look inside the BIN file with an HEX editor and what I found confirm the dependance between the update and the stock ROM:
<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata version="3.2">
<product>
<manufacturer>SonyEricsson</manufacturer>
<model>MK16i</model>
<hwplatform>MSM7x30/8x55</hwplatform>
</product>
<update>
<generation>
<version>2.0.0.24</version>
<date>2012-02-01T11:01:38+01:00</date>
<rb_version>6.2.29.19</rb_version>
<rb_ua_version>6.2.29.19</rb_ua_version>
</generation>
<source>
<software>
<revision>4.0.2.A.0.58</revision>
</software>
<customization>
<variant>1249-7782</variant>
<revision>R12D</revision>
</customization>
</source>
<target>
<software>
<revision>4.0.2.A.0.62</revision>
</software>
<customization>
<variant>1249-7782</variant>
<revision>R12D</revision>
</customization>
</target>
</update>
</metadata>
This explains why my download_package.bin is large only 7.55MB; it does update (add/replace files to) the actual ROM. And this is the reason why updates through OTA are sequentials; I cannot install latest GB OTA update w/o go through every previous update first.
So this binary package alone is not useful to create a full ROM of any sort, cannot be flashed as is and cannot be extracted/unpacked/decrypted unless to be a developer and doing reverse engineering.
I plan to give LG G3 I have to an elderly person, so I want this updated to the latest stock rom.
I currently have rooted ZVC with 3.0.1 TWRP recovery.
I could not find a file to perform the upgrade in TWRP.
Is the only way to go restore stock recovery, ZVG, root, TWRP?
In this case is there an easy way to restore stock recovery on a working phone?
Any help?
Thank you.
OM
ObviousMan said:
I plan to give LG G3 I have to an elderly person, so I want this updated to the latest stock rom.
I currently have rooted ZVC with 3.0.1 TWRP recovery.
I could not find a file to perform the upgrade in TWRP.
Is the only way to go restore stock recovery, ZVG, root, TWRP?
In this case is there an easy way to restore stock recovery on a working phone?
Any help?
Thank you.
OM
Click to expand...
Click to collapse
Similar problem, I have ZV8 and want to go to ZVG. The OTA update doesn't work. I tried Flashfire which sees that downloaded file in the /cache folder but when it runs the update, it gives and error "file not found". So I used adb and several root file explorer programs and discovered that the /cache folder is locked despite being rooted. I can not read or copy any files that are in that folder. I can explore the folder and see that update.zip is there, but I can't do anything with it. It does allow me to copy and paste as long as I am only moving it around within the /cache folder. If I could just get that stinking update.zip file out of that folder, then flashfire should be able to do the update.
To the OP. This claims to put your phone back to fresh out of the box status. From there, you can take the OTA updates and get ZVG.
lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
please put the htt . . . stuff in front of the above link, it won't let me post a link since I haven't been active enough.
But I have no interest in going back to stock, I would just like to go from ZV8 to ZVG without losing root and without having to completely reconfig my phone.
Anyone? Someone must know how to get that stinkin update.zip file to be readable by fireflash
I have uploaded the OTApkg from my Verizon 10 downloaded 7/6/17. I have not been able to run it on my 10 because of customization issues.
I have also changed the suffix of the filename to "zip" so it could be uploaded. You may want to rename it before manipulating it. The default name is "OTApkg"
You can download it here and I welcome someone else's better ability to parse the file contents.
MD5 is: e684728237328c1a59c8c53ab2308467
I've now extracted the firmware.zip and created two update.zips, one without boot (but stock recovery) and one without both boot and recovery images. Someone reported to me that flashing the boot.img could be problematic -- I do not know the particulars, just reporting what I heard. I have not flashed these files, so you're on your own. If there are reports of problems, I'll pull the files.
2.41.605.20 firmware update (no boot) md5: 13b3461cbe2e1f9a8098d83115f501c8
2.41 605.20 firmware update (no boot; no recovery) md5: 97c1df3e7cbc9583b9916b4e1768f245
hgoldner said:
I have uploaded the OTApkg from my Verizon 10 downloaded 7/6/17. I have not been able to run it on my 10 because of customization issues.
I have also changed the suffix of the filename to "zip" so it could be uploaded. With past OTA's I've been able to extract the contents, but not so with this one. You may want to rename it before manipulating it. The default name is "OTApkg"
You can download it here and I welcome someone else's better ability to parse the file contents.
(Last OTA I actually ended up flashing with htc_fastboot partition-by-partition in download mode.)
Click to expand...
Click to collapse
I renamed mine also and was able to extract the contents. I have rezipped the files (Files only, not flashable) here is anyone wants them. Strange, 2gb ota but contents are 103mb. I did not install tho, just ran the update to pull the updated system img.
kc6wke said:
I renamed mine also and was able to extract the contents. I have rezipped the files (Files only, not flashable) here is anyone wants them. Strange, 2gb ota but contents are 103mb. I did not install tho, just ran the update to pull the updated system img.
Click to expand...
Click to collapse
NVM. Reread your post. Do you think the firmware would be flashable if renamed 2PS6IMG.zip?
hgoldner said:
NVM. Reread your post. Do you think the firmware would be flashable if renamed 2PS6IMG.zip?
Click to expand...
Click to collapse
I just tried it and it flashed. But remove the boot.img first. The. 20 boot.img won't work on. 18.
kc6wke said:
I just tried it and it flashed. But remove the boot.img first. The. 20 boot.img won't work on. 18.
Click to expand...
Click to collapse
Thanks, , my file may have been corrupted. Going to upload a file I could open on my workstation instead and re-link.
Original upload was corrupted; I've uploaded corrected file and added md5.
Added two firmware only update files, one without boot and one without boot or recovery.
Verizon getting Oreo ota
mattie_49 said:
Verizon getting Oreo ota
Click to expand...
Click to collapse
Yup.
hgoldner said:
Yup.
Click to expand...
Click to collapse
Can I now flash Maximum or Lee-Droid Oreo roms without having to do anything other than installing twrp first? That is correct isn't it?
mattie_49 said:
Can I now flash Maximum or Lee-Droid Oreo roms without having to do anything other than installing twrp first? That is correct isn't it?
Click to expand...
Click to collapse
I would go by the OP's in each of those ROM threads, but presumably you are now on Oreo firmware, so I don't see why not.
Maximus doesn't do vzw..
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
We need someone then to unroot the phone and update to b170 or at least check how to update to b170
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
ensol52 said:
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
Click to expand...
Click to collapse
Paisley Pirate said:
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
Click to expand...
Click to collapse
divineBliss said:
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
Click to expand...
Click to collapse
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
clsA said:
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Click to expand...
Click to collapse
divineBliss said:
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
Click to expand...
Click to collapse
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
HwOUC/****** (numbers)
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
MT2-User said:
HwOUC/****** (numbers)
Click to expand...
Click to collapse
Thanks seems AT&T likes to put them in the path I described though
I'm pretty sure we can edit the updater script to install this from TWRP if someone captures it
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Paisley Pirate said:
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Click to expand...
Click to collapse
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
When I get it I'll get all that as well.
The ATT update note calls it B160_B170_SMR_100 , I hit continue when I tried to hit "remind me later" - but it redownloaded.
Ghost Commander shows nothing in the /cache - odd - so I don't know where it's actually sticking it. I'm searching for it both under that name above and also as update.zip and anything else I can think of (by date, since it just re-downloaded)
I'll grab and document all the info on what I got where.
File is in /cache/fotapkg/ but is named package_temp.zip
I have it out, xda won't accept the file that large, trying to figure out how to link that file only to my onedrive so you can get it without access to all my other junk (sorry)
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Paisley Pirate said:
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Click to expand...
Click to collapse
ok my phone doesn't see the file as an update ..where was it located ?
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
cust.new
cust.patch
cust.transfer
system.new
system.patch
system.transfer
UPDATE.APP
(drawer) META-INF
(drawer) com
(drawer) android
otacert
(drawer) google
(drawer) android
update-binary
update-script
blacklist.conf
CERT.RSA
CERT.SF
MANIFEST.MF
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Paisley Pirate said:
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Click to expand...
Click to collapse
file opens fine ..where was it located on the phone
clsA said:
file opens fine ..where was it located on the phone
Click to expand...
Click to collapse
as I said earlier - /cache/fotapkg/
Paisley Pirate said:
as I said earlier - /cache/fotapkg/
Click to expand...
Click to collapse
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Any idea how the phone installs this OTA zip file?
Is the updater-script failing because of assert statements for cust and system?
Have you had success patching cust and system using the OTA updater-script/OTA zips for the Huawei Ascend XT before? How did you end up getting the cust and system for your B160 Update zip? Probably from a TWRP of someone's updated B160, which is what we need to do for B170 now, I'm guessing?
Thanks for your efforts on this and answering my questions.
clsA said:
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Click to expand...
Click to collapse
As the title says, after latest Miui update Today (23/01/19) and losing root privileges, Installed TWRP but can't see the Zip files i uploaded to the phone needed for rooting.
Where did I go wrong?
isratom said:
As the title says, after latest Miui update Today (23/01/19) and losing root privileges, Installed TWRP but can't see the Zip files i uploaded to the phone needed for rooting.
Where did I go wrong?
Click to expand...
Click to collapse
Perhaps you are on the Install IMG screen instead of Install ZIP screen.