[Tool] Android IMG Unsign Tool
[Tool] Android IMG Unsign Tool
![[Image: Android-IMG-unsign-tool.png]](https://www.hovatek.com/blog/bpyeki/uploads/2019/03/Android-IMG-unsign-tool.png)
Quote:In this video tutorial, i'm going to be showing how to unsign image files using IMG unsign tool.
So i have here with me two different firmwares that have been signed.
This is for lenovo a1000.
Now the difference between this two images is that the two of them can not be unsigned using FBwintools.
We have a guide on how to use FBwintools but there's a new signature type that FBwintools can't unsign
So this image here can be unsigned using FBwintools. Lenovo A1000 can't
So lets try this now, we'll copy this
Now we're actually trying to see if FBwintools can unsign this image
So here you go, it says file boot-sign is not FB. So that means FBwintools can't unsign this image file
So lets go over to IMG unsign tool
Now to unsign a boot image you copy the boot image file into the signed folder then launch the tool
The first tab shows the instructions
Launch the tool, click the unsign tab then click boot or recovery
So since we copied a boot image file we'll click boot
Once it's done, you'll get boot image has been unsigned successfully, check the unsigned folder
Ok, so this is our unsigned boot image
Now lets confirm that this boot has actually been unsigned
To confirm, we'll need to extract using carliv image kitchen
So this is carliv image kitchen, now we're going to try and extract boot image which is the unsigned file and boot-sign which is the signed file so that we'll confirm that this has actually been unsigned
So we'll click boot, B for boot.
We'll try unsigning boot-sign first sorry, extracting boot-sign first
So here it gives us an error message it can't extract boot-sign
So lets go back and try boot image instead
Ok, so here we go. It has extracted boot.img, we can see it
So clearly unsigning worked
Now lets try unsigning a system signed image
Ok, so the instruction says copy boot-sign.img into the signed folder then copy system image or vendor image into the signed folder
So this lenovo A1000 the system.img is not signed so there's no need
Lets try unsigning from this
So, we're trying to unsign system and vendor but we also need to copy boot signed image
system and vendor
We're copying them into signed folder
Ok, so we'll click the unsigned tab then click system
So once that's done, you'll get the message system image has been unsigned successfully
We can now check the unsigned folder this is our unsigned system.img
Now lets try unsigning vendor image remember we've already copied vendor-sign into the signed folder
So we'll click on vendor. So that's it
Now lets try extracting these files to confirm that it has actually been unsigned
You can use any of your favourite system extracting tool
I'm going to be using MTK extractor
Ok, so let me launch the tool
so first, i'm going to try and extract system signed image to confirm that the image is actually signed
so you can see it says it's done but checking the extracted folder, it's empty. So that means it can't extract a signed system image
So lets now try and extract the unsigned image which is this
So Ok, it says it's done. We can now check the the system folder and here you go it was able to extract the unsigned image so that means unsigning was successful
Well, so that's how you unsign these files using IMG unsign tool
(13-04-2019, 12:06 PM)shankar1790 Well i don't know the process of unsigning method of this tool but it just give same system-sign.img in output unsign folder( system.img is still signed). i had read the instruction carefully and putted both boot and system sign img in Sign folder.
I have to Manually Removed its secure Flag in HXD editor
From OFFSET 400 TO OFFSET 1003F0 (QUITE HUGE)
The system-sign.img is of INFOCUS A2
(13-04-2019, 06:16 PM)X3nonNO i don't think so because its start from 0 to 400(all are 00) the img is still signed because its started from 400 (sprd-secureflag). And multiple line of each secureflag one ended then other started till 1003F0.(13-04-2019, 12:06 PM)shankar1790 Well i don't know the process of unsigning method of this tool but it just give same system-sign.img in output unsign folder( system.img is still signed). i had read the instruction carefully and putted both boot and system sign img in Sign folder.
I have to Manually Removed its secure Flag in HXD editor
From OFFSET 400 TO OFFSET 1003F0 (QUITE HUGE)
The system-sign.img is of INFOCUS A2
like you mentioned 1003F0 is too large, even mtk sign header usually isnt as large as that
i believe the signature should be from 0 to 400
(14-04-2019, 01:26 AM)shankar1790 NO i don't think so because its start from 0 to 400(all are 00) the img is still signed because its started from 400 (sprd-secureflag). And multiple line of each secureflag one ended then other started till 1003F0.
I just searched block ** 80 00 00 80 ** and select and deleted all offsets beginning before 100400 to 400.
(14-04-2019, 10:53 PM)X3non(14-04-2019, 01:26 AM)shankar1790 NO i don't think so because its start from 0 to 400(all are 00) the img is still signed because its started from 400 (sprd-secureflag). And multiple line of each secureflag one ended then other started till 1003F0.
I just searched block ** 80 00 00 80 ** and select and deleted all offsets beginning before 100400 to 400.
can you post link to this rom?
