Hello,
I have uploaded the dlpkgfile and fota_script for the D850 Lollipop OTA. I have attempted to extract the contents several ways and have been unsuccessful. I am uploading these with the hopes that someone either a) knows how to extract the contents or b) can figure out how to extract the contents. So, keeping things short and simple, here is the zip file containing the two aforementioned files.
Mega - Android File Host
TekGadgt said:
Hello,
I have uploaded the dlpkgfile and fota_script for the D850 Lollipop OTA. I have attempted to extract the contents several ways and have been unsuccessful. I am uploading these with the hopes that someone either a) knows how to extract the contents or b) can figure out how to extract the contents. So, keeping things short and simple, here is the zip file containing the two aforementioned files.
Mega - Android File Host
Click to expand...
Click to collapse
From what I heard they can do nothing with those files they need the full firmware files to be able to work on but thanks for your efforts.
The discussion on this has been ongoing in the lounge. Found in this general section:good:
TonyStark said:
The discussion on this has been ongoing in the lounge. Found in this general section:good:
Click to expand...
Click to collapse
Sorry about that. Should have checked prior to posting. My bad!
TekGadgt said:
Sorry about that. Should have checked prior to posting. My bad!
Click to expand...
Click to collapse
No worries, it was just an FYI.
Related
I just can't find a way to extract what is in the .img files.
It's such a small file so shouldn't be hard to find.
Downloading it from the Play store does not resolve the issue
How can I re-acquire the needed .odex file and/or extract what I may need from the .img files?
Delirious17 said:
I just can't find a way to extract what is in the .img files.
It's such a small file so shouldn't be hard to find.
Downloading it from the Play store does not resolve the issue
How can I re-acquire the needed .odex file and/or extract what I may need from the .img files?
Click to expand...
Click to collapse
Do you have a Backup of your system - if so restore your backup. If not google extract .img files and look for software.
No backup...I just need to find a way to extract the files from the .img files of which I did google but nothing useful came up
Delirious17 said:
No backup...I just need to find a way to extract the files from the .img files of which I did google but nothing useful came up
Click to expand...
Click to collapse
Try magic iso -
http://www.free-news-release.com/Extract--IMG-files---MagicISO-Detail_14991.html
No luck
I have ISOBuster...extracted some files but it was unable to extract them all. It did find a number of android files but no .odex files
Delirious17 said:
No luck
I have ISOBuster...extracted some files but it was unable to extract them all. It did find a number of android files but no .odex files
Click to expand...
Click to collapse
Sorry Bro. Do full wipe and start over from scratch, reinstall. I Hope all works out for ya. Peace-
Why the hell is it impossible for someone to find a way to get such a small measly file to get this stupid update to go through!!
Which update are you trying to apply? You will need the pre-updated file. 4g updates were 3.2.4 and 3.2.6.
Sent from my Xoom
I'm on 3.2.4 and trying to update to whatever it's asking me to update it to.
Delirious17 said:
Why the hell is it impossible for someone to find a way to get such a small measly file to get this stupid update to go through!!
Click to expand...
Click to collapse
Well first, getting angry because others may not be interested in your issue is not the way to get help LOL. If you tried everything else, Why don't
you try flash the Stock 4G XOOM Firmware Download [4G|MZ602-HLK75D]
##PLEASE NOTE##
This file are from Motorola's Development site, I will not take liability with anything that happens with your device if something goes wrong.
DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z602 (4G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
dungeondefenders.odex anyone?
Such a small file to find yet only option seems to flash...
Make a nandroid backup of your current setup...restore stock, pull file, restore backup. Or try just opening the img file with winrar.
Sent from my Galaxy Nexus
bwcorvus said:
Make a nandroid backup of your current setup...restore stock, pull file, restore backup. Or try just opening the img file with winrar.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
What good would making a backup of something I don't even have in the current setup??
Delirious17 said:
What good would making a backup of something I don't even have in the current setup??
Click to expand...
Click to collapse
Because that's the first thing you do when you are going to flash stuff. If you had done this the first time you wouldn't be in this situation.
Sent from my Xoom using Tapatalk 2
testingchip said:
because that's the first thing you do when you are going to flash stuff. If you had done this the first time you wouldn't be in this situation.
Sent from my xoom using tapatalk 2
Click to expand...
Click to collapse
you are no help why even reply
Delirious17 said:
I just can't find a way to extract what is in the .img files.
It's such a small file so shouldn't be hard to find.
Downloading it from the Play store does not resolve the issue
How can I re-acquire the needed .odex file and/or extract what I may need from the .img files?
Click to expand...
Click to collapse
did u ever find the file? if so can you send it to me. i have a similar issue
:crying:
So i just downgraded to ICS again since JB is waaaay too slow and seemed not working well with me.
My current version is 4.03 with US .30, rooted of course. Here's the thing.
My freakn stupid TF700 keeps alerting me with this message.
"New firmware update is available"
I DON'T WANT UR DAM JELLYBEAN UPDATE! I REALLY HATE THAT and do not even wanna see the word ''update" any more
it seriously freaks me out and I wanna kill myself every time I see anything related to 'UPDATE' or 'JELLY BEAN'..
EVERY SINGLE TIME I turn it on, they show me the message. Even if i ignore it once, it is still stuck in the corner of my tf 700 as u can see
from the pictures I attached. In those pictures, things in blue box are able to erase or delete by just sliding it to the right or left.
But those in red box are undeletable. There's nothing i can do to get rid of those stupid update icons and notifications.
What can I do to NOT see this notification again? I will do anything...
PS. While i was reading HTC forum, I found a thread with the same problem and one of em suggested solution
by adding something like this to the build.prop
(ro.config.htc.nocheckin=1)
Of course this one is for HTC EVO 4G LTE so theres no way it's gonna work on my TF 700
but could there be something like this that I could use for my infinity?
If your device is rooted, rename /system/app/CMClient.apk and /system/app/DMClient.apk to e.g. CMClient.disabled and DMClient.disabled - that should prevent starting them at the next reboot.
And, just to contribute something to the community's collective knowledge, please upload your file /cache/dlpkgfile somewhere - I want to know if that is a direct upgrade from 9.4.5.30 to 10.4.4.20.
Problem solved
_that said:
If your device is rooted, rename /system/app/CMClient.apk and /system/app/DMClient.apk to e.g. CMClient.disabled and DMClient.disabled - that should prevent starting them at the next reboot.
And, just to contribute something to the community's collective knowledge, please upload your file /cache/dlpkgfile somewhere - I want to know if that is a direct upgrade from 9.4.5.30 to 10.4.4.20.
Click to expand...
Click to collapse
Well, right after posting this article, I started deleting things using root explorer to see if anything can solve the problem.
Since I am not an expert, I deleted pretty much everything that seemed useless for me, including DMC and CMC whatever they are.
If i knew what I know now, I could have just renamed them, but anyway those files are completely gone now.
and Hallelujah! The notification's gone too. Thanks for your support tho.
I don't know if you still want my dlpkg file since the problem's solved already.
If you still want it, just let me know where to find that file (exact location/directory of the file) and where to upload it.:good:
almightytaek said:
I don't know if you still want my dlpkg file since the problem's solved already.
If you still want it, just let me know where to find that file (exact location/directory of the file) and where to upload it.:good:
Click to expand...
Click to collapse
Yes, please. The exact location of the file is "/cache" and the name is "dlpkgfile". I just noticed that the file will be rather big (~185 MB) and only a small detail will reveal if it is interesting in its entirety, so if you have such a file on your device, please do the following:
- download the dlpkgfile file to your PC and rename it to dlpkgfile.zip
- extract \META-INF\com\google\android\updater-script from the zip
- attach the extracted file (~291 kB) to your reply post
If the first lines of updater-script indicate that it's an update from 9.4.5.30 to 10.4.4.20, the whole file can help users who downgrade to root and want to re-upgrade to the latest JB.
Alright
_that said:
Yes, please. The exact location of the file is "/cache" and the name is "dlpkgfile". I just noticed that the file will be rather big (~185 MB) and only a small detail will reveal if it is interesting in its entirety, so if you have such a file on your device, please do the following:
- download the dlpkgfile file to your PC and rename it to dlpkgfile.zip
- extract \META-INF\com\google\android\updater-script from the zip
- attach the extracted file (~291 kB) to your reply post
If the first lines of updater-script indicate that it's an update from 9.4.5.30 to 10.4.4.20, the whole file can help users who downgrade to root and want to re-upgrade to the latest JB.
Click to expand...
Click to collapse
Here it is.
I don't know why, but I couldn't upload it here with its original form (which is just a file named 'updater-script')
so I added .zip at the end. I bet you know what you have to do now, just delete '.zip' part and use it for the community.
almightytaek said:
Here it is.
Click to expand...
Click to collapse
Thanks!
Code:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.30-20120907:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.4.20-20121026:user/release-keys");
Nice, that's a direct upgrade from 9.4.5.30 to 10.4.4.20. That confirms my theory that there are dlpkgfiles that bundle multiple incremental updates into one.
If you could upload the complete dlpkgfile to some file upload service, US users who want to root their tablet without unlocking would be grateful for a one-step upgrade to the latest JB, having to mess with OTA RootKeeper and the manual upgrading process only once. (I personally don't need it, since I'm unlocked and on WW firmware)
Hello I am trying to flash the factory image on to my Nexus 5 with the flash all option in the zip file and it keep going missing boot.img as seen in the picture and I am unsure what to do at this point cause I disconnect my phone and it does boot up in to android 4.4.4 but I need help here
hell I would let some one remote connect if that helps any lol
Buckii said:
Hello I am trying to flash the factory image on to my Nexus 5 with the flash all option in the zip file and it keep going missing boot.img as seen in the picture and I am unsure what to do at this point cause I disconnect my phone and it does boot up in to android 4.4.4 but I need help here
hell I would let some one remote connect if that helps any lol
Click to expand...
Click to collapse
1) "Stuck" is NOT a question. Please use descriptive thread titles
2) You haven't unzipped the image-hammerheadxxx.zip that contains the images :/
but I have I followed the instructions to a T and put all file in the folder under platform tools
Buckii said:
but I have I followed the instructions to a T and put all file in the folder under platform tools
Click to expand...
Click to collapse
Not sure what instructions you've followed. Either they're incomplete or you made a mistake. Like I said, your screenshot shows a zip file. You need to unzip that in the location that it is in now
picture
rootSU said:
Not sure what instructions you've followed. Either they're incomplete or you made a mistake. Like I said, your screenshot shows a zip file. You need to unzip that in the location that it is in now
Click to expand...
Click to collapse
This is now what I have done you were right but still missing boot.img
Buckii said:
This is now what I have done you were right but still missing boot.img
Click to expand...
Click to collapse
Just fastboot flash it then.
Link to guides in my signature.
I have similar issues. Mine complains that the archive doesn't contain boot.sig and recovery.sig, and then it fails to allocate space and the update package missing system.img.
Going to do it manually now to see if it works
Desca said:
I have similar issues. Mine complains that the archive doesn't contain boot.sig and recovery.sig, and then it fails to allocate space and the update package missing system.img.
Going to do it manually now to see if it works
Click to expand...
Click to collapse
Mine shows same as you, but just reboot and it is working
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
Try the tools in this thread . I used them last week to extract a build prop.
Just load up the system.IMG and drag the file from the system folder to your desktop.
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
daniel4653 said:
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
Click to expand...
Click to collapse
I already downloaded that file.... I just need to extract the build.prop from the system.img which I already have. The thing is I am having trouble getting the build.prop
Sent from my SAMSUNG-SM-G920AZ
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
tiboric said:
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
Click to expand...
Click to collapse
When I try to open the file the program just closes and i go to the log and this is what it says.
Error Opening \\.\PhysicalDrive1. Error Code 2
No of disks 1
Scanning \\.\PhysicalDrive0
index 0 ID 7 size 976769024
Partition Table Error on C:/Users/giovany/Desktop/New folder (2)/system.img
Invalid End of sector markerBad Super Block. The drive is not ext2 formatted.
Drive is not right formatted.
solution for img extraction/fix here
https://xiaomifirmware.com/roms/download-official-roms-for-xiaomi-mi-a2-lite/
or this one seems to be even more up to date (credits to a1291762 for finding it)
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
Apparently nobody in this forum has ever posted a link to this blog.
This blog seems to be made by a xda member using automated scripts to scrap download links for ROMs.
It seems to be quite up to date and also includes the fastboot zip for the most current security patch v10.0.15.0.PDLMIXM , which I haven't seen in this forum yet.
Not sure how trustworthy these sites are but they actually just link to the official Xiaomi OTA download site(https://bigota.d.miui.com), thus the downloaded zips are the official one.
p-walker said:
https://xiaomifirmware.com/roms/download-official-roms-for-xiaomi-mi-a2-lite/
Apparently nobody in this forum has ever posted a link to this blog.
Apparently this blog is made by a xda member using automated scripts to scrap download links for ROMs.
It seems to be quite up to date and also includes the fastboot zip for the most current security patch v10.0.15.0.PDLMIXM , which I haven't seen in this forum yet.
Not sure how trustworthy the site is though. Seems to exist for quite a while though and it's been mentioned in other threads on xda.
Click to expand...
Click to collapse
It could be useful for some OTA files specially for the latest v10.0.14.0 and v10.0.15.0 (wrongly placed in fastboot section) but about the fastboot roms the thread opened here is more updated and complete https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871 it contains the latest fastboot rom for our device, v10.0.13.0.
I recently found this site.
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
That looks like every fastboot and full OTA (site calls them "recovery") to me.
a1291762 said:
I recently found this site.
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
That looks like every fastboot and full OTA (site calls them "recovery") to me.
Click to expand...
Click to collapse
Thx that site seems to be even more up to date, I will include it in the top post if you don't mind. However it is very "minimalistic" I mean there is no information at all about this site available and at least on xiaomifirware you get some extra information blog posts on top and they actually have a disclaimer that they are not affiliated with Xiaomi.
However it seems both sites are actually linking to the official https://bigota.d.miui.com site when downloading the files, thus they should be kinda trustworthy as long as they actually linkt to the official xiami site.
The files from these sites aren't made to be used on Mi Flasher. How I can use these files? TWRP?
romulocarlos said:
The files from these sites aren't made to be used on Mi Flasher. How I can use these files? TWRP?
Click to expand...
Click to collapse
The .tgz files are designed to be used with fastboot/MiFlash. Not every version has one of these.
The .zip (Recovery) files are OTAs that get flashed by the system. I don't know how people usually unpack and flash those but it is possible.
a1291762 said:
The .tgz files are designed to be used with fastboot/MiFlash. Not every version has one of these.
The .zip (Recovery) files are OTAs that get flashed by the system. I don't know how people usually unpack and flash those but it is possible.
Click to expand...
Click to collapse
I know about .tgz files. Just unpack and use with Mi Flasher. But these big zip files aren't. Inside have a big "payload.bin" file. Maybe is for use with stock recovery or TWRP, but I'm unsure.
romulocarlos said:
I know about .tgz files. Just unpack and use with Mi Flasher. But these big zip files aren't. Inside have a big "payload.bin" file. Maybe is for use with stock recovery or TWRP, but I'm unsure.
Click to expand...
Click to collapse
Files with extension tgz are full global rom to be used with MiFlash tool, fastboot or EDL and first you have to unpack it.
Files with extension zip are OTA updates to be flashed through system when it does use the scripts of the stock recovery (when you receive that you have an update) or totally through a custom recovery like TWRP and you don´t need to unpack it (inside within other files you will see payload.bin file)
All the rest that can be founded out there is unnoficial, adapted roms at the like of the user.
Hi guys. Do you know which firmware version is the last android 9 version?