![android img file android img file](https://www.mygb.eu/files/htc1.jpg)
(14-04-2019, 10:53 PM)X3non Wrote: (14-04-2019, 01:26 AM)shankar1790 Wrote: 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). Well, so that's how you unsign these files using IMG unsign tool 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 So lets now try and extract the unsigned image which is this So that means it can't extract a signed system image So you can see it says it's done but checking the extracted folder, it's empty. So first, i'm going to try and extract system signed image to confirm that the image is actually signed You can use any of your favourite system extracting tool Now lets try extracting these files to confirm that it has actually been unsigned Now lets try unsigning vendor image remember we've already copied vendor-sign into the signed folder We can now check the unsigned folder this is our unsigned system.img So once that's done, you'll get the message system image has been unsigned successfully Ok, so we'll click the unsigned tab then click system So, we're trying to unsign system and vendor but we also need to copy boot signed image So this lenovo A1000 the system.img is not signed so there's no need Ok, so the instruction says copy boot-sign.img into the signed folder then copy system image or vendor image into the signed folder Now lets try unsigning a system signed image So lets go back and try boot image instead So here it gives us an error message it can't extract boot-sign We'll try unsigning boot-sign first sorry, extracting boot-sign first 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 To confirm, we'll need to extract using carliv image kitchen
![android img file android img file](https://i.postimg.cc/wvX2Qb3k/Untitled.png)
Now lets confirm that this boot has actually been unsigned Once it's done, you'll get boot image has been unsigned successfully, check the unsigned folder So since we copied a boot image file we'll click boot Launch the tool, click the unsign tab then click boot or recovery Now to unsign a boot image you copy the boot image file into the signed folder then launch the tool
![android img file android img file](https://1.bp.blogspot.com/-qIZ7JMY-Z-4/X-oFHNVJ4XI/AAAAAAAAKS4/uVI6iZbS7PA7qIT7yO7slMHJ0O4yqPqrQCLcBGAsYHQ/s888/Superimg%2BExtractor.jpg)
So that means FBwintools can't unsign this image file So here you go, it says file boot-sign is not FB. Now we're actually trying to see if FBwintools can unsign this image So this image here can be unsigned using FBwintools.
#Android img file how to#
We have a guide on how to use FBwintools but there's a new signature type that FBwintools can't unsign Now the difference between this two images is that the two of them can not be unsigned using FBwintools. So i have here with me two different firmwares that have been signed. Quote:In this video tutorial, i'm going to be showing how to unsign image files using IMG unsign tool.
![android img file android img file](https://3.bp.blogspot.com/-4iYc7JnUFWU/XHn2GUGk_yI/AAAAAAAAEhI/Frmpk_YLidQOdVSVf-_xg63NSmT51OvRACLcBGAs/s1600/unpack-boot-img.jpg)
#Android img file android#
Extract the android IMG unsign tool zip.