Does anyone know any way of opening the dell provided .pkg files , not ways how to install them on mobile , but to open them and extract the files included in it , in Windows , Linux or MacOSX?
tnx
I think TheManii knows the exact way but it involves flashing the pkg to your streak and pulling the battery out at the proper time. The extracted files will be in your LOST.DIR directory on your sim card. A pkg is encrypted and it takes flashing the file to decrypt it.
At least it goes something like that anyway.
lordmorphous said:
I think TheManii knows the exact way but it involves flashing the pkg to your streak and pulling the battery out at the proper time. The extracted files will be in your LOST.DIR directory on your sim card. A pkg is encrypted and it takes flashing the file to decrypt it.
At least it goes something like that anyway.
Click to expand...
Click to collapse
Thank you, interesting indeed this encryption , do you have more info about this process ?
http://mirror2.streakdroid.com/manii/<rom version>/update.zip are the decrypted pkgs
The pkgs can only be decrypted by the stock recoveries, noone's bothered reversing them to find the encryption algo.
TheManii said:
http://mirror2.streakdroid.com/manii/<rom version>/update.zip are the decrypted pkgs
The pkgs can only be decrypted by the stock recoveries, noone's bothered reversing them to find the encryption algo.
Click to expand...
Click to collapse
Thank you, are those ALL the files included in the corresponding .pkg?
Which is the right procedure to extract them, during installation or post ?
Any info about the process is very much appreciated as i am willing to try to decipher and recreate a working .pkg
tnx
The update.zips are completely unmodified, only thing that's been done is run though the stock rec to decrypt.
The safe way to decrypt them on your own is to load the wrong stock rec so it will fail at the first step in the update script. (It checks to see that your rec is the right region so it doesnt install a different region rom)
Afterwards a file will be dumped into <sdcard>\lost.dir, it's the decrypted pkg + garbage from the end of the last memory block. The zips themselves are the same size as the pkg.
There's no real point to making your own pkgs as the only thing it'd do is allow you to install it on a stock rec, but knowing how the encryption works is still useful.
This is even more true on the s10 as it uses pkgs, but they're encrypted differently and these steps dont work on it. I've yet to get a dump from those. All I can do is make nvflash dumps immediately after installing.
Related
Someone who has done the whole DI01 update, please dump their system for me, or just the framework folder, apparently the one given to me had the stock android lockscreen patch applied to it lol.
Aside from that, the DI01 deodex works perfect, I opt_png'ed and zip_align'ed all the apk's, as well as the framework-res and twframework-res.
I will also need someone who knows how to sign updater-scripts to open the one attached, and just save it again properly and upload it for me. I am trying to get a flashable CW zip but the darn thing always gives me a status 6 error, which means the CW cannot read the updater script.
Sorry for the n00b question, but what benifit does deodexing provide? Also if there is another software update will I have to readd any .apk's to my /system folder?
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Is there anything involved in a dump besides just copying the files in /system?
namebrandon said:
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Click to expand...
Click to collapse
Because I am too lazy to go through all that.
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
s44 said:
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
Click to expand...
Click to collapse
That is all I need. The only things I deodex are the contents of system/app and system/framework.
frostman89 said:
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
Click to expand...
Click to collapse
Try a real editor, like bluefish or something.. Those scripts look like sh#! in notepad.
If no one has done it by tonight, just grab me on IRC and I'll do it under Linux for you.
Make sure you've got the file/directory structure right too.. You can't just throw a script in a zip file, but I'm sure you knew that. Myself and and a few others had the wrong directory structure at first, don't remember what error number that gave us though.. I think it just froze.
OK, how can I get it to you? I can't post links or (I think) files yet.
s44 said:
OK, how can I get it to you? I can't post links or (I think) files yet.
Click to expand...
Click to collapse
You can just zip it up and upload it to mediafire.com
Just splice up the link like WWW. Website. Com and I will just delete the spaces.
Mediafire upload just not working for some reason. Hm.
s44 said:
Mediafire upload just not working for some reason. Hm.
Click to expand...
Click to collapse
http://multiupload.com/
J1HDKEGYAR at multiupload
So, I've used Revolutionary to S-off and root, but now there's a system update (I assume for the security vulnerability that was found a week or two ago). I'd like to install this update, but it just fails when I try... Does anyone know how to turn it into a flashable zip, or will I have to un-s-off/root, update, then re-s-off/root?
A hotfix for the vulnerability is not out yet - you tought HTC is that fast But if you can find it you can remove /system/app/HtcLoggers.apk from your rooted Flyer (with an app like File Expert that can mount partitions like /system).
Since you are still stock you might have been offered an incremental update, but I guess soon you will want to flash a custom ROM that already includes it anyway.
Lucas0511 said:
A hotfix for the vulnerability is not out yet - you tought HTC is that fast But if you can find it you can remove /system/app/HtcLoggers.apk from your rooted Flyer (with an app like File Expert that can mount partitions like /system).
Since you are still stock you might have been offered an incremental update, but I guess soon you will want to flash a custom ROM that already includes it anyway.
Click to expand...
Click to collapse
It appears there's a new update today, and it's only about 4.5 megs - I think HTC may actually be that fast
I really don't want to install a ROM, I just want stock with root (to help with development)... Any suggestions appreciated!
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Cwiiis said:
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Click to expand...
Click to collapse
Removing the recovery.img? I've rezipped everything and it's only 510kb now, surely that cant be it?
Recovery.img's are large files it was just a minor updat to probably fix a couple internal things nothing major. It was a small file at 4mb already.
Hy
Can you please upload the edit-update?
Thanks
ric242 said:
Hy
Can you please upload the edit-update?
Thanks
Click to expand...
Click to collapse
Will do once i'm home!
adaimespechip said:
Will do once i'm home!
Click to expand...
Click to collapse
Thanks! Might be able to make it into a flash able zip.
Cwiiis said:
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Click to expand...
Click to collapse
Thanks for the helpful guidelines...
Just a quick question and pardon me since I am a newcomer to Android universe. What do You mean when You say stock?
Thanks again...
BTY
HTC_Flyer / Revolutionary / CWM
Hi everyone,
I want to eventually create an edited ROM for an Android tablet. (Very simple stuff, really. Removing apks, adding build.prop mods)
I have a working update.zip file, which re-installs the image on the tablet, through stock recovery and the install from sdcard option.
But once I unzip it,
and then zip and even re-sign it (with the tool I found by searching the forum),
the recovery says 'installation aborted', when it is verifying the package.
1. How can I avoid this from happening? I get it that closing the update.zip is done wrong. How can I pass the verification section?
2. It IS possible to push such a .zip through stock recovery, right? I want to avoid CWM and TWRP and make it as simple as possible.
Thanks.
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
dxppxd said:
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
Click to expand...
Click to collapse
I tried this, too.
I only deleted one apk from system/app and later I tried again by deleting the apk and its odex file, too.
In both cases, instead of rejecting the update instanlty, it starts the process and then stops after a few seconds.
IS it possible that there is a filesize checker text inside the image?
(or maybe a propery inside the build.prop or updater-script ?)
Any ideas, anyone?
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
iraklisvel said:
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
Click to expand...
Click to collapse
No
Stock recovery doesn't flash custom roms
Get cwm from builder.recovery.com
Press thanks :good: I'd helped :highfive:
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Just off the subject slightly...but Eliminater74 already has a flashable zip (thought TWRP) for the 20J release. Its a 2 Part System.
Eliminator74's zip is modified. I want to take a 100% pure stock system.img (extracted from stock firmware) and put it into a zip that can be flashed in TWRP. When I say stock, that's what I mean. No root, no Xposed, no BusyBox, nothing. This has already been done for Lollipop on the v10, but I have MM. I have already explained why I want to do this. I'm currently looking into whether Superr's Kitchen can accomplish this.
He has a Fully Stock 20J release..just gotta read the thread..
AnonVendetta said:
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Click to expand...
Click to collapse
What tool did you use to extract the KDZ? I am trying to get a stock boot.img for the H901J build and I cannot seem to find it. I used the WindowsLGFirmwareExtract 1.2.5.0 release and all I see are a ton of .bin files and system.img. Is boot.img inside system.img?
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
AnonVendetta said:
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
Click to expand...
Click to collapse
It's been a while from this post... But I'm looking after the same goal you were and got the same error 6 trying the same things you described in your previous posts. Despite of these long 4 years, let me try: did you finally achieve to make the flashable zip with system.img?
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
AnonVendetta said:
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
Click to expand...
Click to collapse
Thank you for your reply. My device is Lenovo Z6 Pro but I thought this wouldn't make a difference.
Just to be sure, what you get with SuperR's Kitchen is a zip including system.img file and not the /system folder, right? Thank you in advance.
Edit: I had tried with other kitchen softwares with no success but SuperR's Kitchen did the job as you said, like a charm. Tons of thanks.
@descarao81: No, SuperR's Kitchen does not include system.img/boot.img, you must provide them yourself. They are device-specific. And system.img is a very large file, so it cannot reasonably be included in the Kitchen zip.
Yeah, maybe I wasn't clear, I meant if the resultant zip would include those raw image files being the original image files provided by the user. It's clear now. Thank you.
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Upytry2 said:
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Click to expand...
Click to collapse
Trying that exactly when im home! Thank you!
Been trying for days to extract the kernel from Nougat to use it within Marshmallow in order to downgrade with vibration working on nougats bootloader - but for the life of me i can NOT get windows to actually read these files properly. have all kinds of mounting programs, a java based converter that doesnt actually work (sgs2ext4) i end up with this loop of the same lines, and a 0kb converted file. I can mount the regular img file fine, but it will NOT open without some sort of error. the files themselves are just fine as they will properly flash and run when using odin (when compressed into tar.md5)
Tried wthin twrp hoping the file manager might just let me browse through it since the phone is already linux based and can actually see the information... but no dice there either. It doesnt go into further detail than just showing me that theres an img file present, with options to delete, chmod, etc.
what can i do to dig down to this zimage portion of boot.img that everyone insists the kernel is within? (i say insist cuz i havent actually seen it for myself!)
none of the tutorials ive come across address these specific opening errors - other than that the error is happening because windows cant read it
diskinternals wont work, osfmount will mount but i cant read it .... where on earth are these drivers or programs or whatever i need to actually allow me to browse and explore these files properly? and dare i say, recompress them once ive found what im looking for!
i did also try flashify, thinking run nougat, backup kernel, install marshmallow, restore nougat kernel, but it just leads to freezing on boot logo. I need to get within these img files to actually do what i want to successfully, switching out only that one specific zimage part of the file, leaving the rest intact.
very frustrated here, would very much love some help with this...
Try this, helped so much!
https://forum.xda-developers.com/general/xda-university/unpacking-editing-packing-roms-img-dat-t3350261
Also, If you want to try, here is a link for the tools:https://www.androidfilehost.com/?fid=24459283995310951