Develop Bugs

[Q] Create flashable .zip?

Hi im working on creating some boot animations. Ive got the files ready, but i cant figure out how to put them into a flashable .zip.
I flashed this file thunderbolt boot animation and it worked so i figured if i just replaced my animation and audio it would work but i get an error saying "e:update script not found" or something along those lines.
Id like to know if there is an easy way to create a "template" were i just copy my animation into a folder and zip it, or if there is a program that will package it for me including the script/etc.
Any input or guide on how to make these boot animations flashable .zip's would be great, thanks.

Eat it iPhone said:
Hi im working on creating some boot animations. Ive got the files ready, but i cant figure out how to put them into a flashable .zip.
I flashed this file thunderbolt boot animation and it worked so i figured if i just replaced my animation and audio it would work but i get an error saying "e:update script not found" or something along those lines.
Id like to know if there is an easy way to create a "template" were i just copy my animation into a folder and zip it, or if there is a program that will package it for me including the script/etc.
Any input or guide on how to make these boot animations flashable .zip's would be great, thanks.
Click to expand...
Click to collapse
Thats weird it didn't work. Should. Maybe it wasn't re-packaged correctly.
Try the one attached.

CCallahan said:
Thats weird it didn't work. Should. Maybe it wasn't re-packaged correctly.
Try the one attached.
Click to expand...
Click to collapse
Thanks ill try it out, just dont have the time right now.

If you cant figure it out i'll give you a guide tomorrow when i'm off my iPad .

did you rezip it correctly?
I ran into this trouble, I forget what it is, but you have to zip the files a certain way or they will not work. I don't remember the settings anymore, but just creating a regular zip file won't work.

There is a good guide to making your own update script on xda somewhere. Just search the entire site. If i'm just flashing something simple like a theme or boot animation sometimes I just use someone else's flashable zip and replace the necessary files. I can't remember off the top of my head, but iirc there are two folders you want to keep from someone else's zip. Meta-inf which is basically the signature files and something else which contains the script. If you dissect someone's zip it should be obvious what the other folder you want to keep is. You will find the update script in one of the sub folders, and if you want you can open it with a text editor and get an idea of how the script works.
If you need more info I can help you more when I get to my computer.
Sent from my PC36100 using XDA App

dkdude36 said:
If you cant figure it out i'll give you a guide tomorrow when i'm off my iPad .
Click to expand...
Click to collapse
Id appreciate a guide either way, id rather learn to do it myself than use someone else's. No rush as i cant really approach this til the weekend.

Eat it iPhone said:
Id appreciate a guide either way, id rather learn to do it myself than use someone else's. No rush as i cant really approach this til the weekend.
Click to expand...
Click to collapse
ok, here it goes.
first, figure out where you want to push your file. i'd reccomend pushing manually in recovery to make sure the file itself works. then, using a tool like 7zip (pc) or betterzip (mac) create a file structure that matches the one on the phone. for example, if you wanted a boot animation to be put in system/customize/resource, make a folder system, customize in that, resource in that, and the bootanimation.zip inside that. now you have the main part. next, make a folder in the root of the zip called META-INF (caps counts) inside that, com, inside that, google, and inside that, android. thats /META-INF/com/google/android/. inside android, you need to place in an update-script. i'd reccomend taking one from another zip and just editing it becasue i still have not figured out a way to make that type of file (unix exec) from scratch. open it up in a .txt editor like notepad++ (pc) or coda (mac) and write your script. here is the baisic script for copying the directory system on the zip to system on the phone (like flashing a boot animation).
copy_dir PACKAGE:system SYSTEM:
CAPS COUNT AND MAKE SURE YOU HAVE AN ENTER AT THE END. IF YOU DO NOT HAVE AN ENTER AT THE END (TO MAKE IT TWO LINES INSTEAD OF ONE, LIKE ISSUEING A COMMAND) THEN IT WILL NOT WORK AT ALL ( E:SYNTAX ERROR IN UPDATE-SCRIPT IS THE ERROR YOU WILL GET)
so put this file into the folder android, and zip it. make sure it is in store only, compatibility mode, if you have such options. then, use an auto signer (or just say zip is not signed and make sure to put sig verification off) to sign the zip. flash, and watch your work magically appear.
the update-script i showed is written in amend. i have no idea how to write in edify bcuz it is much more complicated with the binary and stuff. so dont flash with cwm 3.0+.
good luck. ask if you have any questions.

hello will this methed work on like adding some personal apps you want to be on your rom?

how i remove startup verizon logo ? urgent

hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4

remember i have not .zip file in media folder

Mr Hassan said:
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
Click to expand...
Click to collapse
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.

-spektor- said:
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
Click to expand...
Click to collapse
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?

Mr Hassan said:
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Click to expand...
Click to collapse
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.

-spektor- said:
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
Click to expand...
Click to collapse
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again

Mr Hassan said:
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Click to expand...
Click to collapse
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms

-spektor- said:
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
Click to expand...
Click to collapse
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc

Mr Hassan said:
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Click to expand...
Click to collapse
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could help it deals with modifying samsung rom and flashing it. If you want to read more on it here's the link: http://android.stackexchange.com/questions/85703/modifying-samsung-rom-and-flashing-it-on-a-device if you wanted to remove apps or add custom apps to your phone you would modify system file.
But what I thought was important was this;
(I did not write this thread)
< "You should be able to use an archive program on PC and recompress to .tar, .gz, and others. Dont forget to re-sign the archive. Keep a copy of your untouched ROM until you have the modified ROM tested and running.
The ROMs are signed with a signature. When repacking if they don't get signed they will fail in flashing. This link will help explain it.
So basically after downloading the firmware you have to rename it so you can extract the files, change them as you need, recompress them again and re-sign them, so you can flash them using Odin." >
This thread was dealing with modifying CM rom;
< "There are multiple solutions available:
Re-Zip the Image
Advantage: You do it once, and can use the resulting image for multiple devices. That's what I did with CM7.2 for my Milestone 2. Easy enough to do:
create a temporary (empty) folder
unzip the zip file to it
remove unwanted *.apk files from /system/apps (be careful of what you remove, of course)
zip up the directory contents again
Using a graphical ZIP manager (like WinZip or the like), steps would be even easier:
open the zip file with the archive manager
remove the unwanted .apk files
if the ZIP manager requires it, save the manipulated zip
Manually cleanup after flashing, using the shell
This is what ce4 recommended in the comments. It requires you using a terminal emulator on your device:
Flash the image as-is
remove superfluous stuff from the system partition by hand (like rm /system/big/junk/example.mp4)
Manually cleanup after flashing, using other tools
Almost the same as the previous method, but a bit more user-friendly. Disadvantage: this won't do for superflous ringtones and the like:
Flash the image as-is
Use a tool like Titanium Backup or Root Uninstaller to remove unwanted system apps" >
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/

-spektor- said:
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
Click to expand...
Click to collapse
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom

Mr Hassan said:
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Click to expand...
Click to collapse
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.

-spektor- said:
.
Click to expand...
Click to collapse
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible

Mr Hassan said:
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Click to expand...
Click to collapse
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.

-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
Ok apps done
Bulid done
Now final thing need . repack in ext4 format
I'll check these things tomorrow

-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
brother did you found anything for repack ext4 img?

Mr Hassan said:
brother did you found anything for repack ext4 img?
Click to expand...
Click to collapse
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461

-spektor- said:
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
yes but its for linux , and for window 99% unsuccessfully rates , have you try in window ? this ?
now i,m in next step if you have the time so kindly share your experience
https://forum.xda-developers.com/android/help/repack-img-giving-error-odin-invalid-t3577719

Hmmmmm ? I think you want to change the boot animation (white Verizon logo red background? ) if so your gonna need to either need to flash a pre-made zip with Flashfire (can't seem to get it to apply from twrp) or your gonna need to manually copy into the appropriate directory (mount system directory r/w copy then change permissions of the file you copied to 644 and reboot) presumably with a root explorer though doable from terminal
---------- Post added at 07:47 PM ---------- Previous post was at 07:29 PM ----------
-spektor- said:
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
Click to expand...
Click to collapse
Try flashing with flasfire enabling the option mount system r/w and use common paths (probably not necessary but won't hurt) I have had difficulty getting anything other than ROM and gapps to apply from twrp but flashfire seems to work . I'm thinking its due to the fact that flashfire flashes after boot loader and then resets prior to os load.

GUIDE - Replace "N/A" boot image? [QUALCOMM] Moto E4

The credit for this guide goes to @1chrome, who made the guide for the Moto G4/G4+. Everything is basically the same, aside from the position of the N/A.
The problem - When we unlock our bootloaders and install TWRP, the Moto boot logo is replaced with a black screen that says N/A. Now, thanks to @mikaleee, we have a template to create custom bootlogo images. Unfortunately, even though we can replace the plain black bootlogo, whatever image we replace it with will still have the N/A overlay show up. However, depending on the image used, or your creativity, you can use white/light images to hide the N/A.
On the attached template, there is a black block to illustrate where the N/A will show up on an image. Again, depending on the background of the image used, or your creativity, you will be able to hide the N/A with lighter colors.
I have attached pictures to illustrate.
What you’ll need to create your own bootlogo:
1. Windows PC
2. Moto Bootlogo Maker from here (all credits to @caitsith2) and @xpmule (12/18/17 UPDATED LINK TO CORRECT VERSION OF MOTOBOOTLOGOMAKER)
3. Your desired image (in 720 x 1280 px resolution, PNG/JPG)
4. MotoE4-BootLogo.bin I've created for reference (Attached below. Unzip before using)
Procedure:
1. Open Moto Bootlogo Maker
2. Go to File > Open > Select MotoE4-BootLogo.bin
3. Once loaded, ensure that the Motorola device is listed as Custom and the resolution is set to 720 x 1280.
4. Replace the following entries with your custom image. You can either double click or select replace.
* logo_boot
* logo_unlocked
* yellow
* red
* orange
5. When done, select File>Save As. This will create a flashable zip that you can install with TWRP.
I’ve also attached a custom bootlogo, but it will display the N/A as I’ve not had time to find other images to play with. However, it may be a nice replacement until you create your own.
Original Post
I am rooted and have TWRP installed. Naturally, when i boot the phone I get the black screen with "N/A".
I have tried flashing a new logo.bin image through TWRP, Terminal Emulator, and even ADB. Nothing works. All guides pretty much say the same thing, and the actual procedure isn't that difficult, so why is replacing the logo.bin on the E4 so dang difficult? I have my images formatted to 720x1280. I've looked at the stock logo.bin. I can't figure this one out. It would be nice to boot up and not see "N/A", although it isn't the end of the world. But now this is a freakin' quest!
Any advice?

I've been trying to figure it out myself

@mn1968 disable *boot_logo_updater* within the ramdisk.

@Francesco Franz
Well, that settles it. We need someone smarter than me. I couldn't find any useful directions/guides on the subject.

mn1968 said:
@Francesco Franz
Well, that settles it. We need someone smarter than me. I couldn't find any useful directions/guides on the subject.
Click to expand...
Click to collapse
search for this
service boot_logo_updater /vendor/bin/bootlogoupdater
comment "#" out this service.

Thanks. But it's still over my head.

There's not even a file with that name on my phone

KyleBryant said:
There's not even a file with that name on my phone
Click to expand...
Click to collapse
Yeah, I've been looking like hell but I can't find it either. That looks like something that would be in the ramdisk but I don't see anything like it yet. I have an idea though. I'm going to try something.

try this boot.img
download > https://www.androidfilehost.com/?fid=889964283620757558
also boot_logo_updater is found on line 793 in file named init.mt6735.rc

iykeDROID™ said:
try this boot.img
download > https://www.androidfilehost.com/?fid=889964283620757558
also boot_logo_updateris found online 793in file namedinit.mt6735.rc
Click to expand...
Click to collapse
Unfortunately that file doesn't exist in qcom variants. Don't flash that unless you have a mediatek variant guys!
Sent from my Moto E (4) using XDA Labs

amarc78 said:
Unfortunately that file doesn't exist in qcom variants. Don't flash that unless you have a mediatek variant guys!
Click to expand...
Click to collapse
Okay,
I think you have to state your Variant next time

(redacted)

All there

Update: as y'all probably already surmised.... Nope I guess it doesn't work.. I tried XD :/
It works but not in a way to be visible I guess

Got the default logo back instead of the ugly black screen. (15 mins of messing around in the MotoBootLogoMaker tool.) IT STILL DISPLAYS THE N/A but it's hardly visible with the blue bg

mikaleee said:
Got the default logo back instead of the ugly black screen. (15 mins of messing around in the MotoBootLogoMaker tool.) IT STILL DISPLAYS THE N/A but it's hardly visible with the blue bg
Click to expand...
Click to collapse
Dude, you're AWESOME! I had been replacing images in the logo.bin I extracted from the retail firmware. I notice in your logo.bin, there are entries for red, yellow, & orange (just like the Moto G4 I have). However, in the retail firmware logo.bin, they are labeled as yellow warning, red warning, orange warning, and those did not work for me on the E4. I had considered using the template from the G4 but didn't think it would work. Regardless, you have now provided a template to create custom bootlogos.
To hide the "N/A", one would need to either use a white background for the logo, or creatively use white/light images to hide the "N/A".
When I have time later, I'll update the OP with a guide/template to create custom boot logos.
THANKS FOR FIGURING THIS OUT!

Yeah I actually started with a logo.bin from a G5 (provided by somebody in the forums) and then opened another window with the "official" logo.bin from the E4 stock, extracted every icon and replaced the G5 larger ones with the E4 ones. And changed the resolution. This was the only way I could get it to show up. When I tried replacing boot logo in the default E4 one just got a black screen. So finally a working template

OP updated with guide and template.

Twrp ends with error 6
---------- Post added at 05:24 PM ---------- Previous post was at 05:24 PM ----------
I followed the op instructions

Ljseegar said:
Twrp ends with error 6
---------- Post added at 05:24 PM ---------- Previous post was at 05:24 PM ----------
I followed the op instructions
Click to expand...
Click to collapse
Try flashing one of these. If they work, then you didn't do something right when you made yours.
https://forum.xda-developers.com/moto-e4/themes/custom-boot-logos-e4-qualcomm-maybe-t3699202

any solution to fix the fingerprint on GSI?

Does anyone know if they already have a solution to fix the fingerprint on any GSI on the moto g7 play?

I don't think there will be a fix for it. GSIs are basically developed for testing purposes and are not functionally ROMs.
---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------
https://source.android.com/setup/build/gsi

Guhl0rd64 said:
Does anyone know if they already have a solution to fix the fingerprint on any GSI on the moto g7 play?
Click to expand...
Click to collapse
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.

Spaceminer said:
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.
Click to expand...
Click to collapse
man, you are the g7 play hero ngl, can you post an explanation of what needed to be done when youve done it, you know like the technical side, so people like me can learn?

00p513 said:
man, you are the g7 play hero ngl, can you post an explanation of what needed to be done when youve done it, you know like the technical side, so people like me can learn?
Click to expand...
Click to collapse
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.

Spaceminer said:
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.
Click to expand...
Click to collapse
Wow, thank you very much my friend, I will test now

Spaceminer said:
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.
Click to expand...
Click to collapse
Thank you.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Guhl0rd64 said:
Wow, thank you very much my friend, I will test now
Click to expand...
Click to collapse
So...?

Marcondes BR said:
Thank you.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
So...?
Click to expand...
Click to collapse
I installed by TWRP, I have Lineage OS 17.1, still with the same problem

Descendent Modified GSI, doesnt work. It sees the reader, but doesnt recognise me touching it

Spaceminer said:
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.
Click to expand...
Click to collapse
I have tested on several GSI, and I have had no success

Guhl0rd64 said:
I have tested on several GSI, and I have had no success
Click to expand...
Click to collapse
You might need to add ro.fpsensor.position=1 & persist.qfp=false to the build prop.

Spaceminer said:
You might need to add ro.fpsensor.position=1 & persist.qfp=false to the build prop.
Click to expand...
Click to collapse
it still didn't work

Guhl0rd64 said:
it still didn't work
Click to expand...
Click to collapse
I'm unfortunately out ideas at this point.

Spaceminer said:
I'm unfortunately out ideas at this point.
Click to expand...
Click to collapse
I guess this means no fingerprint on Ubuntu Touch when i get it to work

Question [?] Is is possible to remove the unlocked bootloader warning?

So I stumbled upon this thread: https://forum.xda-developers.com/t/guide-remove-unlocked-bootloader-warning.4069207/
The flash script reads:
package_extract_file("files/abl.elf", "/dev/block/bootdevice/by-name/abl_a");
package_extract_file("files/abl.elf", "/dev/block/bootdevice/by-name/abl_b");
On my root explorer, I am able to see both these files by navigating to /dev/block/bootdevice/by-name/
So my question is, how do we edit abl_a and abl_b for our phones, to remove the warning screen?

Interesting. If these files/partitions serve the same purpose on the Pixel as they do on Xiaomi, then there's hope. I'd find it amazing if this was possible on the Pixel that no one would have found this yet - unless the solution just wouldn't work on the Pixel. I have no idea if you can safely replace those files on the Pixel with the same example that is included in the flashable zip with ADB either with the system booted or in recovery mode.
I found the files to be actually inside:
Code:
/dev/block/platform/14700000.ufs/by-name/
through X-Plore File Manager, but the "/dev/block/bootdevice/" does exist and redirects to "/dev/block/platform/14700000.ufs/".

roirraW edor ehT said:
Interesting. If these files/partitions serve the same purpose on the Pixel as they do on Xiaomi, then there's hope. I'd find it amazing if this was possible on the Pixel that no one would have found this yet - unless the solution just wouldn't work on the Pixel. I have no idea if you can safely replace those files on the Pixel with the same example that is included in the flashable zip with ADB either with the system booted or in recovery mode.
I found the files to be actually inside:
Code:
/dev/block/platform/14700000.ufs/by-name/
through X-Plore File Manager, but the "/dev/block/bootdevice/" does exist and redirects to "/dev/block/platform/14700000.ufs/".
Click to expand...
Click to collapse
/Tad off topic: I am using Material Files (found on F-Droid - free and open source). Material Files has true root file explorer, unlike many file explorers and comes ad-free and fully functional!

I would strongly recommend against this unless you know EXACTLY what you are doing. You can render your device permanently hard bricked if you effort the bootloader even slightly wrong.

I agree with @dragynbane222. Unless you're prepared to RMA your device, I wouldn't attempt it.

dragynbane222 said:
I would strongly recommend against this unless you know EXACTLY what you are doing. You can render your device permanently hard bricked if you effort the bootloader even slightly wrong.
Click to expand...
Click to collapse
This is exactly why I have not even attempted to research this any further. I was simply asking the dev community for their input.

mkhcb said:
So I stumbled upon this thread: https://forum.xda-developers.com/t/guide-remove-unlocked-bootloader-warning.4069207/
The flash script reads:
package_extract_file("files/abl.elf", "/dev/block/bootdevice/by-name/abl_a");
package_extract_file("files/abl.elf", "/dev/block/bootdevice/by-name/abl_b");
On my root explorer, I am able to see both these files by navigating to /dev/block/bootdevice/by-name/
So my question is, how do we edit abl_a and abl_b for our phones, to remove the warning screen?
Click to expand...
Click to collapse
As other people have mentioned, it is theoretically possible, but you can easily hardbrick your device.
On many Android versions, it was possible to adjust this warning via setting certain permissions manually (I haven't seen an attempt with A12 yet). Oddly enough, some people have reported (over the years) that such a module/mod worked without problem, whilst other had "random" hardbricks, even though they - as far as I recall - claimed that they did not deviate from instructions, and had the same devices with stock firmware. Meaning even if someone would provide you with such a file that you could add via terminal (su) or other means, and even if a dozen people here would claim it works on their end, it could still easily brick your device for reasons we do not understand. So I'd just step away from that thought and even if someone would provide a solution, to not use it. I've never seen any explanation as to why some devices bricked, and some did not, so that's danger-danger.