Database Info

[Q4DEV] Desire HD - where is the hidden partition??

When you take a look at the original ROM file for the ACE device you will see this files below:
- hboot... bla, bla, bla (which is self spelling)
- boot.img (...no comment...)
- recovery.img (...no comment again...)
- system.img (...we all know what's inside)
...a few more files and...
- lib.img (...uhhh??? what's this???)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you open the lib.img there you can find all the files which belongs to the /system/lib folder.
So far - everything seems to be O.k. BUT now my problem and question.
When I use the PD98IMG.zip to install my device and do a backup with the RECOVERY tool and create .tar files - the /system/lib folder within the backup is empty.
When I do a wipe of my device and erase EVERYTHING on it and I try to restore my backup file this fails. This was driving me nearly crazy until I have found that the /lib folder has his own partition.
First I need to restore the original PD98IMG.zip and after this I'm able to successfully restore my backup.
On the one hand this is a great thing because this will offer more space within the /system partition and this will give the DEV's more options for porting ROM's from and to other devices.
On the other hand - where the hell is the /lib folder or partition or whatever located on the DHD device???
Regards!

I think these files are from the Sense 3.0 leaked ROM for ace rite?
For some reason they've made a separate lib.img & if you want to know how exact & where it is extracted during the installation, unpack boot.img & check init.rc / init.spade.rc..
You'll see few lines in either of the files related to extraction of lib.img..
hope this helps

fshami said:
I think these files are from the Sense 3.0 leaked ROM for ace rite?
For some reason they've made a separate lib.img & if you want to know how exact & where it is extracted during the installation, unpack boot.img & check init.rc / init.spade.rc..
You'll see few lines in either of the files related to extraction of lib.img..
hope this helps
Click to expand...
Click to collapse
Yep m8, this is related to the leaked 3.06 ROM for the ACE.
I guess this might be interesting for some DEV's and this is also a thing which needs to be covered by the guy's who are developing the kernels and ramdisk for the ACE.
Also the 4EXT Recovery should be adjust for the ACE device.
From my point of view this is a good solution to get more space on the /system partition.
The next thing is /data/at folder within the original dzdata.img and the sub folders. This folders will be mounted automatically to the /system partition. Don't know how...
Let me give an example for WhatsApp.apk
The original dzdata.img contains this folder structure:
/data/app
/data/at/app
/data/at/lib
/data/at/plugin
If I store this file within /data/at/app I can use WhatsApp without creating an hard link to the /system/apps folder.
All this things might be interesting for the DEV's.

Just a quick (related) question. How do you unpack dzdata.img?

It might not be a hidden/new partition. Quite the contrary. Notice that with the 3.06, there's a new hboot shipped. I'm theorizing, that it changes the partition layout, chopping up /system into smaller partitions. Now, as we all probably use the eng hboot and a custom update-script for unsigned roms, this doesn't concern us.
Or at least that's my theory. I remember in the sapphire/magic days, the new radio would allot more flash space to /system to fit in SenseUI, while old radio would allot more space to /data.

[TOOL] Droid-IMG

Droid-IMG v1.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm new to the Android platform, only getting an Android Phone less than a week ago. I am however a developer and from reading up on Android and ROM's I noticed that there was little to nothing on the .IMG format, especially tools for windows.
With that in mind I started to develop a command line based tool to extract and compress .IMG files. It does rely on other tools to do this (hence the Tools folder included). My utility searches for the GZip Signature in the .IMG file and dumps the data. It then extracts it into a folder and from here you can modify the files and then re-compress them back into an .IMG file using my tool.
What I have found is some .IMG files that contain links/shortcuts will become corrupt upon extraction since they are only supported by the linux operating system.
Anyway, my program should be self explanatory when you run it. The screenshot above also shows the commands and parameters that should be used.
NOTE : [Base IMG] is your original unmodified .IMG File and [New IMG] is the file name of the .IMG file that will be created. Also, ignore the function not implemented errors.

Reserved.
P.S : Guess nobody knows what .IMG files are then...

Nice man! Thank you.

TheUnkn0wn said:
Droid-IMG v1.0
I'm new to the Android platform, only getting an Android Phone less than a week ago. I am however a developer and from reading up on Android and ROM's I noticed that there was little to nothing on the .IMG format, especially tools for windows.
With that in mind I started to develop a command line based tool to extract and compress .IMG files. It does rely on other tools to do this (hence the Tools folder included). My utility searches for the GZip Signature in the .IMG file and dumps the data. It then extracts it into a folder and from here you can modify the files and then re-compress them back into an .IMG file using my tool.
What I have found is some .IMG files that contain links/shortcuts will become corrupt upon extraction since they are only supported by the linux operating system.
Anyway, my program should be self explanatory when you run it. The screenshot above also shows the commands and parameters that should be used.
NOTE : [Base IMG] is your original unmodified .IMG File and [New IMG] is the file name of the .IMG file that will be created. Also, ignore the function not implemented errors.
Click to expand...
Click to collapse
These are some useful little tools, Considering lack of them for Windows users. Maybe nice one day to Polish it up with a nice GUI to make it easy for less experienced people.
But Good job I'll be using these.

Delete

Delete

Thank you very much for sharing

Thanks for sharing. But I can not see any system img files via 7zip without previously repaired. May I use repaired system img files?

You must be doing something wrong. I've tried WWE and Orange PL and both extract without repairing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks for sharing.

thank u!

Thanx mate later that day ill extraxt System dump an share it with you guys.

Thanks for the DiskInternals thingy
Since i never needed to extract a System.img I never looked for a method but I will remember this. Seems fairly straightforward.
And thanks for the creds.

I will try this one.
Btw, i made a backup with twrp. Ia there any way to get the backed up system.emmc.win file extracted? Renaming it to .tar doesn't work.
What I try to achive is an extracted ROM so I can deodex the apks

DroidShift79 said:
I will try this one.
Btw, i made a backup with twrp. Ia there any way to get the backed up system.emmc.win file extracted? Renaming it to .tar doesn't work.
What I try to achive is an extracted ROM so I can deodex the apks
Click to expand...
Click to collapse
add .tar to the end of each image and under Linux or cygwin use tar -xvf xxxx.tar

Hmm... Hoped there's anything for win 8.1
...setting up cygwin
Edit: @LeeDroid
Nothing happens when doing the command in the cygwin window...

Worked like a charm
I did have to edit the ConvertHima.bat and remove the line set wf=%cd%\ for it to work
but everything else was spot on .. thanks!!
Anyone need the 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426167_signed.zip
System.img or Dump

Worked great I think. I did get an error, and I received this error 4 times for sparse.img, 2,4,6,8. Here is the error: - "1 [main] sparse2img 7912 find_fast_cwd:". It also says "WARNING Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list [email protected]". I wrote cygwin, and got a reply from a Marco stating, "Dear Hal, Same answer as given last month to another guy". Then gave me this link https://cygwin.com/ml/cygwin/2015-05/msg00318.html. Followed by, "Please report the solution to whom provided the ConvertHima.bat". The answer in the link basically says a utility called rsync is being used, and the person who provided it is bundling it with an old version of the cygwin kernel. I did however get a new system_hima.img, and I started ConvertHima.bat. After completion I have what appears to be a complete system image. It's 3.53Gb in size, and has the folders - app, bin customize, etc, fonts, framework, lib, lib64, lost+found, media, priv-app, tts, usr, vendor, xbin, and has the file build.prop. It appears to have all the Deodexed APK's in app and priv-app. This is from the T-Mobile RUU. I'm using Window 8.1.

I'm trying to create a system dump (1.40.708.9)but was stuck at step 2. Where can I download my ROM.zip?

xunus said:
I'm trying to create a system dump (1.40.708.9)but was stuck at step 2. Where can I download my ROM.zip?
Click to expand...
Click to collapse
i think you misunderstand what this is for

flex360 said:
i think you misunderstand what this is for
Click to expand...
Click to collapse
That could be true. Seems like this is to extract M9's rom from an RUU and not from the phone itself.

Mr_Bartek said:
You must be doing something wrong. I've tried WWE and Orange PL and both extract without repairing.
View attachment 3226483
Click to expand...
Click to collapse
Can you send me the file system.img_01 ?

htsang08dqt said:
Can you send me the file system.img_01 ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/one-a9/development/decrypt-ruu-ruu-decryption-script-htc-t3282562

Is there a Linux version of the sparse2img.exe? I am in need of this because I don't have the system.img but I have the system.img_xx chunks from the RUU ZIP.

[Guide | Tutorial] Change Boot Logo of Samsung device without Root access!

This is j7108's
is from 5.1.1 but should can use in 6.0.1 as well:
https://mega.nz/#!nNkliAQb!VvopPnS5Zkk15Mhlikaixmg6zWbhyfS_xXe2unSmRqo
Boot Logo =/= Boot animation
Tool you need:
Windows Pc : 7zip, Odin, maybe a linux OS as well
Please note that I'm not responsible if you brick your device, flash back original BL_{firmware version}.tar.md5 to unbrick it
1. You need to get BL_{firmware version}.tar.md5 from your stock firmware, I get from SmartSwitch/Kies which has 4 .tar.md5 files
If your stock firmware consist of only 1, you might can extract it, not entirely sure how. Do share in the comment if you know.
2. You should open BL_{firmware version}.tar.md5 inside linux environment and modify param.bin because the tar contain permission information
Inside param.bin contain Logo.jpg which you can replace it
(rename the param.bin to param.tar so you can open it, after replace the picture, check the permission, tar it, rename it back to param.bin)
Note: The order(cm, sboot then param) and the permission inside the tar is extremely important. Once messed you will brick your phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please share your method how to pack tar on Windows as well. I don't know how to set the permission in windows.
3. Once done repack the 3 files to anynameBL.tar note the .md5 is not needed. If you want to use .tar.md5, Odin need to verify it and it need extra steps
I apologies for lack of linux knowledge, I can't provide comprehensive method. All these steps are simplest possible approach.
We are almost done, now before you flash the Bootloader that you just repack, you need to make sure Frp Lock(if your phone has this feature) is OFF else you will brick your device.
To close Frp Lock, enable Developer Options(google it for step), enable OEM Unlock
Put your device to Odin mode, and you can start flashing
enjoy your new favorite stylish boot logo and turn off OEM Unlock to secure your device back

you write "The order(cm, sboot then param) inside the tar is extremely important" but in the screenshot there is another order.
And in some BL-images which i examined, it is always sboot, param and then cm!

hi
how to edit permission logo after edit file?
windows 32bit

Help with extracting boot.img from dmz file

Hi all.
I followed this guide
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
have been rooted for few months now. Received the OTA notification and did my research on how to apply it. Unfortunately I can't restore factory images in magisk as there is no stock backup found. I read somewhere that You can find the missing file and put it in manually. To do this I need to find and download official firmware file that the phone is running and extract it from there.
mine is here:
LG V500EM | LG V50 ThinQ 5G | Version: V500EM20g_00_0120 | Firmware for Region: EEE from UNITED KINGDOM - Lg-firmwares.com
LG V500EM Download the latest version of firmware | OS Version: Android 10 Q | Firmware version: V500EM20g_00_0120 | EEE - Fan club LG-firmwares
lg-firmwares.com
Now this is where I start facing issues. I got the right kdz file. Extracted the dz file. But by no means I cant get boot.img out of it.
Any help would be great and much appreciated.

What prevents you from extracting the image

It just won't work.
I found a guide and used
LG Firmware Extract Tool v1.2.6.1​The file is there but cant be extracted
this the output of the program:
Progress extractDZFlle Done !!
Complete on extract DZ partition files
Exception on extract partition file Ionic.Zlib.ZlibException: Bad state (incorrect header check)
at Ionic.Zlib.InflateManager.Inflate(FlushType flush)
at Ionic.Zlib.ZlibCodec.Inflate(FlushType flush)
at Ionic.Zlib.ZlibBaseStream.finish()
at Ionic.Zlib.ZlibBaseStream.Close()
at Ionic.Zlib.ZlibStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at WindowsLGFramwareExtract.Form1.DZExtractBackprocess.extractDZFlle(ArrayList contents) in L:\Working_PROJECT\WindowsLGFramwareExtract\WindowsLGFirmwareExtract\Form1.cs:line 464
boot.img_118538
byte read position 4
header 32-96-18-74
byte read position 0
DZ file C:\Users\dirt\Desktop\LG_Firmware_Extract_v1.2.6.1\LG_Firmware_Extract_v1.2.6.1\V50020m00EEOGBOP0120.dz
Could the program be outdated and LG have changed their way of packing their firmware? Is there any other way to get it out?

The same thing happens to me when I try to do this. All I get are some vendor .img files and the same 'exception error'. The kdz I used is like 4.2gb, the dz file output is 155mb.
I think the firmware extract program is too dated for these phones, it was used for the G2. This sucks

Hmm maybe the file is corrupt, try finding a new source or downloading it.

Actually the KDZ file is not corrupt but the software you are using to extract does not work with new LG firmwares files (since they use version 3 compression). You need to use Linux for extraction.
I could help you in getting the boot.img if you tell me which specific firmware you are seeking from.

Royaltiger said:
Actually the KDZ file is not corrupt but the software you are using to extract does not work with new LG firmwares files (since they use version 3 compression). You need to use Linux for extraction.
I could help you in getting the boot.img if you tell me which specific firmware you are seeking from.
Click to expand...
Click to collapse
EDIT: My issue was that i was running .bat and storing file on newtwork HD. I will leave this post up incase someone else runs into the issue.
There are really no windows programs to successfully extract the DZ from KDZ ??
I've been working on this issue for 3 days and can't get a boot image and other necessary files to come out of the DZ. Only way i read about that was successful was using OneKeyExtraction.bat (sourabh7625) but program cannot find the KDZ file like shown below. I'm working with LG G710VM on Win10 can only access EDL at this point.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}