Database Info

[APK,IMG,DAT,BR] One click decompile/compile - Windows Shell Integration

This tool is a part of ADK software, thread can be found here (For summary read Introduction part below). Read Instructions at the end on how to install this.
Click to expand...
Click to collapse
{
"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"
}
Snapshot
Click to expand...
Click to collapse
Introduction
This Utility adds option to right click decompile, compile options for some extensions (like apk, img, dat, br, file_context.bin, payload.bin) so that you don't have to open any kind of kitchen again and again move files there and select options to unpack. See screenshots above you will get an idea about what is it..
Also it's not a separate tool it is a part of ADK. Read Installation and download instructions from below and check 2nd post for usage instructions.
And yes the main part since ADK kitchen is not completely free it works for only 7 days as a trial after that you will have to use demo version which has certain feature disabled. Not to worry this utility will work fine but there will be a pop-up notifying to buy license.
What is ADK?
Well if I've to say, ADK (Android Development Kit) is a complete Windows based GUI application which allows you to edit Android apk files, ROM zips, boot or recovery images, Android Firmware and also to create TWRP/CWM flashable recovery zips easily. It's like a complete Android Kitchen with lots of mods, patches, scripts, templates, rich text editor, etc. like an IDE. For more info visit official thread here.
Click to expand...
Click to collapse
Features
Well here you go,,,
Unpack/Repack APK (including smali), IMG, DAT, BR files.
Generate Java Source for APK.
View APK Info like App name, Package, permissions, icon, etc.
Import App as dependency for system apk.
Support Android 9.0 ROM.
Supported lists are: System, Vendor img, dat, br and Recovery or Boot images)
Suggest me what to add more.. :laugh:
Click to expand...
Click to collapse
Changelog and Known Issues
Changelog as per release 1.1.0.0 (17th January 2019)
*Added: Option to unpack Payload.bin
*Added: Option to convert file_contexts.bin to file_context
*Added: Support for Android 9.0 images.
*Updated: APK decompiling so as to create project for ADK.
Known Bugs
* Unpack option is not showing for .IMG file (on Win8.1 and lower).
Current Fix:- Open CMD and type "contexts d path-to-img" (without quotes).
Click to expand...
Click to collapse
Downloads & Instructions
To use these feature you must have ADK to be installed. So read steps below (noob friendly) in order to get it. If you want to know what is ADK read Introduction Part above.
Step 1: Install ADK
Grab a latest release of the software from above link.
Step 2: Extract the ZIP and install setup.exe as we normally do.
Do not install the software in C:\Program Files or Program Files (x86) folder.
Step 3: Launch ADK from desktop shortcut and go to Help > Plugins & Patches.
Keep your internet connection ON to do this steps.
Step 4: Search for ADK Context [Script] and install it.
First click on Download option then after click on Install it. Installation will be like normal setup file.
Step 5: Once installed you can close ADK and use the plugin.
Click to expand...
Click to collapse

Reserved

Nice tool keep up the good work!
Sent from my Redmi 4X using Tapatalk

can we then recompile say a vendor img after using this tool to unpack?

Xdevillived666 said:
can we then recompile say a vendor img after using this tool to unpack?
Click to expand...
Click to collapse
Yes why not! Just right click on the unpack folder created by the tool and select Encode APK,IMG,DAT,BR option from there

Tool has been updated. To download it open ADK it will notify you which plug-in needs to be updated!

[email protected] said:
Yes why not! Just right click on the unpack folder created by the tool and select Encode APK,IMG,DAT,BR option from there
Click to expand...
Click to collapse
Can't repack vendor either with ADK or shell.
ADK says cant find context for system/apps probabby its cant find selinux perms in file_contexts as its vendors its should not need that
And with Shell method can't say log are not getting create
Please looks and thanks for your work

Luffy.d said:
Can't repack vendor either with ADK or shell.
ADK says cant find context for system/apps probabby its cant find selinux perms in file_contexts as its vendors its should not need that
And with Shell method can't say log are not getting create
Please looks and thanks for your work
Click to expand...
Click to collapse
Vendor needs file_context especially plat_file_context it maybe missing something. I will look into it soon as currently I'm working on new project. So this might take a little while, but for sure I'll fix this.

[email protected] said:
Vendor needs file_context especially plat_file_context it maybe missing something. I will look into it soon as currently I'm working on new project. So this might take a little while, but for sure I'll fix this.
Click to expand...
Click to collapse
Thank you and no hurry
and here the exact error
error: build_directory_structure: cannot lookup security context for /system/app

Wow nice.
This can decompile framework-res.apk ans systemui.apk without errors anf uknown folders? Means java problem?
Good work, thank you.
Wysłane z mojego SM-G930F przy użyciu Tapatalka

Luffy.d said:
Thank you and no hurry
and here the exact error
error: build_directory_structure: cannot lookup security context for /system/app
Click to expand...
Click to collapse
I'll contact you once I will look up in this issue and fix it.

nalas said:
Wow nice.
This can decompile framework-res.apk ans systemui.apk without errors anf uknown folders? Means java problem?
Good work, thank you.
Wysłane z mojego SM-G930F przy użyciu Tapatalka
Click to expand...
Click to collapse
Yes it will unpack framework-res.apk and system ui. Just make sure when you want to decompile these system apps make sure to check the option 'import as dependencies' to not get any decompiling and compiling error further.
For Java problem I still get no response to issue with the latest Java problem. I think we still have to use lower Java version.

Android pie repacked system_ext.img can't boot.

Werewolf 99 said:
Android pie repacked system_ext.img can't boot.
Click to expand...
Click to collapse
Well I need some more info on this issue a logcat or something else. From your info I deduct following things like!
1. Your ROM might but using sparse image not ext if that's the case convert the image and then flash.(since sparse image omits some empty blocks)
2. I need to know the original image size and new compiled image size (if you have not made any changes then how much difference is present in their size).
Also let me know if you are flashing the new image using sp tool (for mtk devices).

futuretricks
thanks for this

Thanks for Your Share
EnerJon said:
Nice tool keep up the good work!
Sent from my Redmi 4X using Tapatalk
Click to expand...
Click to collapse
Thanks

cant use without a license, script download function is locked.. This must be under "paid software"not here.

guap said:
cant use without a license, script download function is locked.. This must be under "paid software"not here.
Click to expand...
Click to collapse
As discussed with the moderator this is part of ADK which is free to use even after trail period https://www.google.com/amp/s/forum....adk-android-reverse-engineering-t3803044/amp/
So if this is not working try original ADK which works after expiry date

I keep trying to download the script but the file is 0 kb and wont install. Any help?

Arden said:
I keep trying to download the script but the file is 0 kb and wont install. Any help?
Click to expand...
Click to collapse
Check your PM

[GUIDE] : HOW TO - Remove Stock Launcher on v.195 and above >

Hi guys, well, finally, after i spend so many nights trying to find a solution to remove the stock Launcher on v.195, i have manage to find a working solution. Please keep in mind this solution will Uninstall/Disable the Stock Launcher on your User 0, it will not be remove from your phone. Is the same as we use to uninstall it just before the v.195 but this way is different, well, at least it works 100%. ( I tested on both my devices AL00 and it works ). We can also remove the Default PhoneManager App by this method, as Huawei block this PhoneManager to be removed by ABD with the v.915 Update.
This method i test it on my Windows 7 Home Premium X64 with the lastest drivers
Devices Used : 2 Devices AL00 China Version , both of them running v.195 Update
Please READ CAREFULLY, i do not take any responsability if you will brick your phone :
IMPORTANT : Before starting with this method, make sure you have another 3rd Party Launcher already installed, otherwise, when you will remove the Stock Launcher, your phone will freeze as you do not have another Launcher.
Things we need :
Direct Download links provided
1 - Latest Version of JAVA installed into your PC
2 - Minimal ADB and FastBoot Portable Version 1.4.1
3 - Package Disabler (All Android).apk
4 - Remove Any Accounts you already have on your Mate 20 X, otherwise, this method it will Fail. ( You can add them back on after you remove the Stock Launcher ) without any kind of problem. Keep in mind if you have any account on your phone, this method will not work.
{
"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"
}
STEP 1 :
- Install JAVA into your computer if you do not have it already.
STEP 2 :
-Install Minimal ADB and Fastboot ( it is already exectuable file just unzip it and you're good to go )
- Install ADB Composite Driver
STEP 3 :
- Install Package Disabler (All Android).apk into your Mate 20 X and Make sure you give Storage Permission, otherwise this method will not work.
STEP 4 :
- Connect your phone through ADB and input this command into your ADB Console : Adb Devices
If everything will be ok and you have all your drivers properly installed, you will see this message into your ADB Console :
Now, open Package Disabler App in your phone and access the first link, for NON Root Users :
- Input the following command into your ADB Console :
adb shell dpm set-device-owner com.kunkunsoft.rootpackagedisablerfree/.receiver.DPMReceiver
Click to expand...
Click to collapse
- If everything was ok ( JAVA Installed, No accounts on your device ) you will see the following message, which means you properly set device owner authorizathion for kunkunsoft Package Disabler.apk :
- Press OK on both screens in Package Disabler App
STEP 5 :
- Move to System Apps and find Stock Launcher > Tick The BOX to Disable it
Optional : You can disable the PhoneManager.apk as well if you wish, as Huawei block PhoneManager apk to be removed since the update v.195
Congratulations, you have now Remove the Stock Launcher from your Huawei Mate 20 X.
Additional Info: You may see a strange message on your Lock Screen
This device is managed by your company
To get rid of this message, simply Uninstall the Package Disabler.apk from your phone :
- Press the 3 dots on the right corner and Select Uninstall this app
That's it, enjoy your New Huawei with your favorite Launcher.
You are welcome.

Nice one thx.
With this guide even i could figure it out i think.
Never did this kind of things with my phone before.
But i dont have the needs for doing it, but still a nice guide for a amateur like me... If [emoji3]

I've been using Package Disabler for a few weeks and it seems to work well on the Mate 20 X. The best part is you can just uncheck an app when you want to enable it again.

ajsmsg78 said:
I've been using Package Disabler for a few weeks and it seems to work well on the Mate 20 X. The best part is you can just uncheck an app when you want to enable it again.
Click to expand...
Click to collapse
Agree with that, but only if we can remove the Lock Screen Message : This device is managed by your company, that would be awesome... i still did not find this option in the settings...

I lost the home gesture

Get Nova Launcher Prime and activate the gestures... Me , i don't use gestures at all... I'm a classic guy, i use app drawer button...

I've disabled the Huawei Stock Launcher with a simpler way.
Install your favorite Launcher.
Enable USB Debuggung and connect the Phone.
Open your ADB Console and type: adb shell.
and type:
pm uninstall -k --user 0 com.huawei.android.launcher
With this Guide can many Systemapps uninstall
https://forum.xda-developers.com/note-10/how-to/guide-to-remove-apps-root-t3828324
It will work on the most Huawei/Honor Phones.
My is Honor Note 10 and View 20

letschky said:
I've disabled the Huawei Stock Launcher with a simpler way.
Install your favorite Launcher.
Enable USB Debuggung and connect the Phone.
Open your ADB Console and type: adb shell.
and type:
pm uninstall -k --user 0 com.huawei.android.launcher
Click to expand...
Click to collapse
Please read description very carefully. Since the Update v. 195, Huawei block the option to Delete the Stock Launcher on Huawei Mate 20 X via ADB Console.
ADB Method is no longer supported ( INTERNAL FAIL ERROR ).

filip_pine said:
Please read description very carefully. Since the Update v. 195, Huawei block the option to Delete the Stock Launcher on Huawei Mate 20 X via ADB Console.
ADB Method is no longer supported ( INTERNAL FAIL ERROR ).
Click to expand...
Click to collapse
Ok,sorry,but with root is no Problem to change the Launcher

letschky said:
Ok,sorry,but with root is no Problem to change the Launcher
Click to expand...
Click to collapse
For those of us ( like 80% ) who have a Locked Bootloader, there is no Root Option....
Not to mention Huawei stop providing Unlock Codes...

filip_pine said:
For those of us ( like 80% ) who have a Locked Bootloader, there is no Root Option....
Not to mention Huawei stop providing Unlock Codes...
Click to expand...
Click to collapse
my Bootloader is open on Note 10 and View 20,there is a buy Option.

I'm one of those if not the only who was able to disable stock launcher via ADB command after the 195 update. I got the 198 update just a moment ago and it did not restore the stock launcher...

flatronics said:
I'm one of those if not the only who was able to disable stock launcher via ADB command after the 195 update. I got the 198 update just a moment ago and it did not restore the stock launcher...
Click to expand...
Click to collapse
Hi. Are you rooted and/or have unlocked bootloader? To be clear, what are exact commands you used? Thanks!

All stock, no unlocked BL, no root.
I don't remember the exact command but it's the standard ADB command of uninstalling apps.
mscion said:
Hi. Are you rooted and/or have unlocked bootloader? To be clear, what are exact commands you used? Thanks!
Click to expand...
Click to collapse

flatronics said:
All stock, no unlocked BL, no root.
I don't remember the exact command but it's the standard ADB command of uninstalling apps.
Click to expand...
Click to collapse
Interesting.
Which version phone do you have? Chinese (AL00)? Thanks!

I have the Chinese model AL00
mscion said:
Interesting.
Which version phone do you have? Chinese (AL00)? Thanks!
Click to expand...
Click to collapse

mscion said:
Interesting.
Which version phone do you have? Chinese (AL00)? Thanks!
Click to expand...
Click to collapse
Don't get to excited mscion, i know exactly what he says... Trust me... You are able to Remove it first time only... Reset your phone to Factory Conditions again and the second time INTERNAL FAIL ERROR
I have 2 units AL00, first time after the 195 Update, when i was trying to Uninstall Stock Launcher, i was able to do so, after i reset the devices to Factory Settings while on v.195 Update, second time when i try to uninstall, Error....
I think there is something that trigger itself after the first Remove attempt and then the Uninstall command become unavailable and it get back with INTERNAL FAIL ERROR

@mscion so you too did a factory reset after or while at update 195 that's why can no longer disable stock launcher?

flatronics said:
@mscion so you too did a factory reset after or while at update 195 that's why can no longer disable stock launcher?
Click to expand...
Click to collapse
Actually, I haven't tried anything yet. Just reading about things and trying to understand whats up and how to do mods. Regardless, right now I'm really disappointed with Huawei's policy with bootloader code. Just waiting a bit longer to see if it is possible to obtain. But soon I will give up and sell phone....

Hey guys for me its not working. Look at the pic! Can someone help me i am so desperate!
I have app freezer but it wont freeze the homelaucher anymore after the update!
What can i do

A Temp root solution for Nokia 5.1 Plus

{
"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"
}
This method is based on Amazing Temp Root for MediaTek ARMv8 by diplomatic
Clever work that give MTK-soc devices a bootless root ( Root remains until reboot ). And lucky enough it works on our Nokia 5.1 Plus
So to begin :
-Grab diplomatic lastest mtk-su.zip in Amazing Temp Root for MediaTek ARMv8
- Follow instructions from Bootless root with Magisk and MTK-SU
#You can install Magisk Manager from the magisk 18.1 package, or any version below 7.1.2. Lastest version of MM doesn't work.
And your device should have root permission.

Hi stizzir,
Great post I've tried it and it works.
The only problem I had is that you can't use the latest version of Magisk Manager you
need to use the 7.0.0 version if not Magisk manager won't open after running the suboot.sh script.
I was wondering if with this we may be able to get full root and also turn the notch on and
off on devices that don't have the Full Bezel option in Display Settings or Developer Options.
Best regards,
voidRunner

I tried it as well and it works. Thanks for letting us know I've been checking these forums every week waiting for something like this. I also used Magisk 7.0.0 inside the 18.1 Magisk zip. Latest version didn't work.

@vddrnnr
The only problem I had is that you can't use the latest version of Magisk Manager you
need to use the 7.0.0 version if not Magisk manager won't open after running the suboot.sh script.
Click to expand...
Click to collapse
Wow good to know, i encountered that problem too, and you figure it out !
I was wondering if with this we may be able to get full root and also turn the notch on and
off on devices that don't have the Full Bezel option in Display Settings or Developer Options.
Click to expand...
Click to collapse
I don't think full root can be acquired since there are still no Bootloader unlock solution yet, really looking for that. N-tool devs are working on it and they said X5 unlock is coming soon. But the bootless root work fine ! couldn't complain anything, it's basically a rooted device.

I tried Adaway it didn't work first time but worked second time, After that it would not work again no matter what I tried, says not enough space on partition. I checked host file when it worked and it had changed. Titanium backup worked, SD maid worked. Looks like I was wrong you can't edit or delete anything in system folder.

@rustdroid
I tried it as well and it works. Thanks for letting us know I've been checking these forums every week waiting for something like this. I also used Magisk 7.0.0 inside the 18.1 Magisk zip. Latest version didn't work.
Click to expand...
Click to collapse
No problems, but again, all the credits go to diplomatic for his work, I'm just lucky enough to come across his thread.
Yes latest Magisk doesn't work, diplomatic had already mentioned it the original thread.

rustdroid said:
I tried Adaway it didn't work first time but worked second time, After that it would not work again no matter what I tried, says not enough space on partition. I checked host file when it worked and it had changed. Titanium backup worked, SD maid worked. Mixplore root worked I deleted Google drive app from system/apps but took a few tries and reboots for it to be uninstalled, the folder always restores after reboot.
Click to expand...
Click to collapse
This is just a temporary solution so don't expect much out of it.
The doors will be open once the Bootloader can be unlock

Yes I know and I'm happy with it until we can unlock bootloader. Hopefully they can find a way soon but this will do until then.

Can someone else with this phone try Adaway to see if it can edit host file or delete a system app like Google drive (move the app file in system/apps replace it after tested) ? Just want to see if I'm only one that can't edit system folder.
Edit: It's okay I just read that you can't modify System/Vendor partition unless boot image modified. Will have to wait until bootloader unlocked.

vddrnnr said:
Hi stizzir,
Great post I've tried it and it works.
The only problem I had is that you can't use the latest version of Magisk Manager you
need to use the 7.0.0 version if not Magisk manager won't open after running the suboot.sh script.
I was wondering if with this we may be able to get full root and also turn the notch on and
off on devices that don't have the Full Bezel option in Display Settings or Developer Options.
Best regards,
voidRunner
Click to expand...
Click to collapse
rustdroid said:
Can someone else with this phone try Adaway to see if it can edit host file or delete a system app like Google drive (move the app file in system/apps replace it after tested) ? Just want to see if I'm only one that can't edit system folder.
Edit: It's okay I just read that you can't modify System/Vendor partition unless boot image modified. Will have to wait until bootloader unlocked.
Click to expand...
Click to collapse
Man i just can't wait for the Bootloader unlock. Nokia obviously doesn't want to offer a official unlock service ( at least for now ) since the android one line-up is meant to be as stock as possible. The company also promised to support new Android One devices in the next 3 years, so allowing Bootloader unlock will work agains their product course i think.
I have seen many attempts from the community however, and i have trust in them, many devices get unlocked by a unofficial method so.... Wait for the good news.

@stizzie I can't wait, hate having a device that I don't have full control. I've asked Nokia on there forums and signed a partition that is closed now, That's all I can do and just wait. I read somewhere that Nokia will allow it soon but who knows how long. Hopefully someone finds another way soon.

Doing this won't kill OTA, right?

Rajeel911 said:
Doing this won't kill OTA, right?
Click to expand...
Click to collapse
Absolutely not

stizzie said:
This method is based on Amazing Temp Root for MediaTek ARMv8 by diplomatic
Clever work that give MTK-soc devices a bootless root ( Root remains until reboot ). And lucky enough it works on our Nokia 5.1 Plus
So to begin :
-Grab diplomatic lastest mtk-su.zip in Amazing Temp Root for MediaTek ARMv8
- Follow instructions from Bootless root with Magisk and MTK-SU
#You can install Magisk Manager from the magisk 18.1 package, or any version below 7.1.2. Lastest version of MM doesn't work.
And your device should have root permission.
Click to expand...
Click to collapse
Can I give permission to es file file explorer if yes than how??
And can I modify this partition Device/data/nvram/APCFG/APRDEB

Ranjhag said:
Can I give permission to es file file explorer if yes than how??
And can I modify this partition Device/data/nvram/APCFG/APRDEB
Click to expand...
Click to collapse
Just follow instructions in the provided links, you should have root permission. Applications working or not really depends on your device so it won't hurt if you try it yourself.

Device is Nokia 5.1 plus?
And sir can u tell me where I have to paste mku-su file? In the pc

I got OTA update today while this thing was running so no OTA issues.
Just 2 warnings:
1) Don't write even a single byte to system partition or boot partition.
2) Don't expect Netflix etc to work since it breaks CTS profile and basic integrity. Banking apps etc will whine for rightful reasons too.

Ilgazc said:
I got OTA update today while this thing was running so no OTA issues.
Just 2 warnings:
1) Don't write even a single byte to system partition or boot partition.
2) Don't expect Netflix etc to work since it breaks CTS profile and basic integrity. Banking apps etc will whine for rightful reasons too.
Click to expand...
Click to collapse
It doesn't let you do anything to system or boot partition. I tried editing and deleting and doesn't work. Have to wait until bootloader unlocked.

Rajeel911 said:
Doing this won't kill OTA, right?
Click to expand...
Click to collapse
rustdroid said:
It doesn't let you do anything to system or boot partition. I tried editing and deleting and doesn't work. Have to wait until bootloader unlocked.
Click to expand...
Click to collapse
If you (by chance) are able to write a single byte to system or boot partition on this dm-Verity enabled device, it won't boot and will need service center.
That changes if bootloader can be unlocked of course.

Ilgazc said:
If you (by chance) are able to write a single byte to system or boot partition on this dm-Verity enabled device, it won't boot and will need service center.
That changes if bootloader can be unlocked of course.
Click to expand...
Click to collapse
Okay thanks for the info. Guess I was lucky that you can't do anything. I tired to delete a few pre installed apps and edit the host file. Looks like this is as good as it gets until we can unlock bootloader.

[GUIDE] Rooting the Moann inkPalm 5

Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
EDIT: You can find an extended guide at https://github.com/qwerty12/inkPalm-5-EPD105-root with steps for installing microG.

qwerty12 said:
Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
Click to expand...
Click to collapse
As far as I could gather, with both USB connection and developper mode on, ADB conncection is explicitely rejected. Besides, there is, on InkPalm, below the usuals USB checks, one that reads "...ADB/ADT..." which cannot be checked. The connetion request by wireless ADB, supplying the correct address, is also rejected.... As though the device needed be rooted first !

I haven't tested using ADB over Wi-Fi, but I can honestly say I have had no issues using ADB over USB on the inkPalm. ADB was enabled by default on mine, and not to mention the security of it has been weakened - you don't even need to approve ADB connections for the first time...

So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ? I cannot find any reference to the manufacturer that would eventually grant me permissions-- step ?
So long,
Sixto Quesada

Bis -- I forget to mention that my primary goal is merely to be able to change the language to English, as I think that there are already many possibilities in-built as to the configuration, including the shell !

squsqu6 said:
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ?
Click to expand...
Click to collapse
Is debugging mode actually on? Open the settings, go to the highlighted page and
{
"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"
}
turn the highlighted setting on (make sure the setting above it is on too - it will let you install external APKs)
You can follow these steps to show the Developer Settings, that's up to you: https://github.com/epodegrid/epd106-ADB#step-1-install-adb
squsqu6 said:
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English
Click to expand...
Click to collapse
If you really can't get ADB to work, then there might be another way. Install the APK of my launcher fork (how you do that is up to you - you can try using the built-in browser or transferring the APK over MTP and using the file manager [which I've never opened] to install it).
In the new launcher, tap-and-hold the Settings icon (the one with a dark background),
choose Additional Settings and tap Locale. Then follow the instructions here: https://github.com/philips/inkpalm-5-adb-english#change-the-language

ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.

This worked great for me thanks a lot. I have a quick question if you know it. Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)? The stuff you can do with the home button/logo button in settings is pretty limited.

Thanks.
reaverclan said:
Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)?
Click to expand...
Click to collapse
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button

qwerty12 said:
Thanks.
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
Click to expand...
Click to collapse
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible. So I guess it's for another xiaomi device or base android version. I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.

reaverclan said:
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible.
Click to expand...
Click to collapse
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
Click to expand...
Click to collapse
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).

qwerty12 said:
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
Click to expand...
Click to collapse
Ah I see that's clever. It's not the end of the world and yeah I think it's cause root explorer does what you said about invoking the thing directly. I just use the stock app to only install and that's it. My journey so far is shown here and regardless of the jank it has been a great device. https://www.mobileread.com/forums/showpost.php?p=4140508&postcount=155
Thanks again for the time to make it even greater. Only thing that sucks is no stock img to un brick if something goes to far. Hopefully someone leaks that at some point. This device seems pretty new to the market still.

squsqu6 said:
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
Click to expand...
Click to collapse
I now have a new, but old !, trouble : battery life. I have enforced all saving possibilities available --from standard menu, from E-Ink Launcher, and, from RomToolBox, processors speed slowing--, and, yet, after 8 hours of use, InkPalm battery is totally empty, even though being totally user-idle --not a single user application being active according to linux 'top' request. Conversely, Kobo reader battery lasts for days in reading mode.
My question : would it be thinkable any possible trick of triggering the sleeping function without pushing the red button, so as to keep the screen as it is --allowing the reading of actual page until next (not a book, a musical partion, which takes longer !)--. Bypassing by script the red button action, or other ? --Note : the screensaver option allows for user-image, like a screenshot, but it requires to move it to the proper place and to renew it at every page...
Sorry for being so long, I am far from being familiar wich Linux (Android).
Greetings,
S. Quesada

[Tool] APK Toolkit v1.2 [Windows]

APK Toolkit is a native Windows GUI app for Reverse Engineering Android apps. It provides multiple tools & options for decompiling, compiling, extracting and zipping various Android file formats as well as displaying app permissions, metadata and much more
It was written from scratch when APK Easy Tool was discontinued. It has similar features to APK Easy Tool as well as a lot more updated features
Light Skin
{
"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"
}
Dark Skin
Features
Decompile / Compile / Extract / Zip xapk, apk, jar
ZipAlign / Check align xapk, apk
Check Align xapk, apk
Sign / Verify signature apk
Assemble / Disassemble dex, odex, oat (Baksmali / Smali)
Convert xapk / split xapk to single apk
Drag & drop support for single or multiple files
Pin window so it's always on top
JumpList and toolbar shortcuts
View / Remove app permissions
View app info including if app includes native 32bit / 64bit libs and/or global-metadata.dat and libil2cpp.so
il2cppdumper & dnspy built in, also supporting single / multiple file drag & drop (Dump directly without decompiling from xapk & apk and then view instantly in dnspy)
Install compiled Apk via Adb (Android Debug Bridge) or drag & drop Apk to install
Automate adding mod-menu to xapk or apk with single mouse click
Automate adding patched libs to xapk or apk
Automate adding toast message to app on startup
Decode / Rebuild to API level
Regex Search & Replace decompiled smali code
Remove Ads from Apps / Games via Regex Search & Replace
Requirements
Windows (APK Toolkit is a native windows app)
Java for additional tools
.net framework for additional tools
Updated to v1.2
Regex Search & Replace decompiled smali code
Remove Ads from Apps / Games via Regex Search & Replace
Added Light or Dark Skin setting
Bug fixes
Download
https://www.mediafire.com/file/uv86qhvwm7q5wg8/APK_Toolkit_v1.2_by_0xd00d.zip/file
Mirror
http://e.pc.cd/qj9otalK

ooh, useful idea, but what a sloppy init release -

VolBob said:
ooh, useful idea, but what a sloppy init release -
Click to expand...
Click to collapse
You realise that this app is a GUI for ApkTool and other command line apps right?
Are you using Aapt2 in the settings?
The error in your screenshot shows it is an error with ApkTool and not ApkToolkit and there are plenty of topics relating to this ApkTool error, maybe search next time before insulting someone who is providing a free app
but what a sloppy init release
Click to expand...
Click to collapse
If you wanted help then this is the wrong way to go about it. I suggest you delete ApkToolkit and use something else

0xd00d said:
View attachment 5881817
View attachment 5881821
ApkToolkit is a native windows GUI app for multiple tools for Reverse Engineering Android apps
It was written from scratch when APK Easy Tool was discontinued. It has similar features to APK Easy Tool as well as a lot more updated features
Features
Decompile / Compile / Extract / Zip xapk, apk, jar
ZipAlign / Check align xapk, apk
Check Align xapk, apk
Sign / Verify signature apk
Assemble / Disassemble dex, odex, oat (Baksmali / Smali)
Convert xapk / split xapk to single apk
Drag & drop support for single or multiple files
Pin window so it's always on top
JumpList and toolbar shortcuts
View / Remove app permissions
View app info including if app includes native 32bit / 64bit libs and/or global-metadata.dat and libil2cpp.so
il2cppdumper & dnspy built in, also supporting single / multiple file drag & drop (Dump directly without decompiling from xapk & apk and then view instantly in dnspy)
Automate adding mod-menu to xapk or apk with single mouse click
Automate adding patched libs to xapk or apk
Automate adding toast message to app on startup
Requirements
Windows (ApkToolkit is a native windows app)
Java for additional tools
.net framework for additional tools
Download
https://www.mediafire.com/file/eryd3c7jd2w591t/ApkToolkit+v1.0+by+0xd00d.rar/file
Mirror
https://mega.nz/file/wXoiEZCb#lK2ylis3EcK0n8UPUc5gmdfMoPKrVn34hNq0LvDFtvc
Click to expand...
Click to collapse
I'm enjoying Apk Tool Kit, but it would be great if you could add a feature to install APKs using ADB. Currently, the only way to install APKs while using scrcpy is to use Apk Easy Tool. However, Apk Easy Tool kills the ADB server scrcpy spawns, which closes the mirrored window on the computer. If you could add a way to install APKs using ADB directly in Apk Tool Kit, that would be a great improvement. Thanks for your consideration!

Ives Gunther said:
If you could add a way to install APKs using ADB directly in Apk Tool Kit, that would be a great improvement.
Click to expand...
Click to collapse
I'll add that into the next release, thanks for the suggestion

@0xd00d Sir when i made clone,its not launch on android 12
Its launch perfectly with android 11
Help please

Leftrand said:
@0xd00d Sir when i made clone,its not launch on android 12
Its launch perfectly with android 11
Help please
Click to expand...
Click to collapse
It's hard to say for sure because a lot has changed in Android 12, especially access permissions
For example if app uses data folder then android 12 will not access it due to new access permissions
Does it install ok?
Do you get any error messages?
There are a few things you can try...
Disable google play protect
To disable Google Play Protect. Open "Play Store" application -> tap on Menu button -> select "Play Protect" option -> Disable the options "Scan device for security threats"
Some permissions like overlay permissions cause problems with android 12, you can try removing permissions in the AndroidManifest.xml and then trying again
Check your manifest for the mainactivity and check if you have
android:exported="false"> and if you have then set to true not false
make sure you have no duplicates in your manifest such as a duplicate mainactivity
you can also try signing with different signing versions in APK Toolkit settings
you can check your android logs via adb logcat
I don't use android 12 so have no way of testing sorry, please try the above and try and narrow down the problem

0xd00d said:
It's hard to say for sure because a lot has changed in Android 12, especially access permissions
For example if app uses data folder then android 12 will not access it due to new access permissions
Does it install ok?
Do you get any error messages?
There are a few things you can try...
Disable google play protect
To disable Google Play Protect. Open "Play Store" application -> tap on Menu button -> select "Play Protect" option -> Disable the options "Scan device for security threats"
Some permissions like overlay permissions cause problems with android 12, you can try removing permissions in the AndroidManifest.xml and then trying again
Check your manifest for the mainactivity and check if you have
android:exported="false"> and if you have then set to true not false
make sure you have no duplicates in your manifest such as a duplicate mainactivity
you can also try signing with different signing versions in APK Toolkit settings
you can check your android logs via adb logcat
I don't use android 12 so have no way of testing sorry, please try the above and try and narrow down the problem
Click to expand...
Click to collapse
Thank you for your reply sir
Install oke sir without error.
I did disable play protect all the time,my manifest also true
Recently i use np manager to remove signature verification using Modex3.0 to sign apk before i modified using apktool or apk editor,it will launch on a11 below but not a12 up
If no remove signature verification,it will not launch for both a11 and a12 after installed.
I also try sign v1 v2 v3 v4 yet no luck,only black screen and closed
Viet guy did also modified same apk but their apk lauch for a11 a12 and a13 perfectly,don't know they did
Wish i could find solution for this because your tool very handy and simple to use

Leftrand said:
Thank you for your reply sir
Install oke sir without error.
I did disable play protect all the time,my manifest also true
Recently i use np manager to remove signature verification using Modex3.0 to sign apk before i modified using apktool or apk editor,it will launch on a11 below but not a12 up
If no remove signature verification,it will not launch for both a11 and a12 after installed.
I also try sign v1 v2 v3 v4 yet no luck,only black screen and closed
Viet guy did also modified same apk but their apk lauch for a11 a12 and a13 perfectly,don't know they did
Wish i could find solution for this because your tool very handy and simple to use
Click to expand...
Click to collapse
Can you message me with a link to your APK and a link to the other modded APK which works for a11,a12 amd a13
I can't promise anything but I can try to see whats wrong using a12 emulator as soon as I get time

0xd00d said:
Can you message me with a link to your APK and a link to the other modded APK which works for a11,a12 amd a13
I can't promise anything but I can try to see whats wrong using a12 emulator as soon as I get time
Click to expand...
Click to collapse
Yess i send you both link in pm,thank you

Updated to v1.1 with some small bug fixes and additions...

0xd00d said:
Updated to v1.1 with some small bug fixes and additions...
Click to expand...
Click to collapse
Pushing Thanks button for you...

Amazing tool i like it it's so useful thanks for your great work could you please add support for dark mode in next relesae.

Updated to v1.2 with some small bug fixes and additions...

Hi guys, I'm trying to modify a system apk on my head Unit (PX5). Specifically HCT4Music.apk. I just want to modify the colours of the screen, so that it fits the inside lighting of my car. I have no problem with the modifications. But I can't get it installed by the signature. How can I keep the same signature of the original apk.
I have also tried to copy the modified apk to /system/app and the result is that it works but it does not allow me to access the music files because it denies me access to the file system.
Do you have any solution?. Thanks
Translated with www.DeepL.com/Translator (free version)

ivexsa said:
How can I keep the same signature of the original apk
Click to expand...
Click to collapse
Only if you have a rooted device, you can use original sig in apk with disable signature with magisk / xposed framework
If no rooted device then you can try one of the signature killers which hook / replace new sig with original sig

0xd00d said:
Only if you have a rooted device, you can use original sig in apk with disable signature with magisk / xposed framework
If no rooted device then you can try one of the signature killers which hook / replace new sig with original sig
Click to expand...
Click to collapse
Thank you very much 0xd00d. I have installed the magisk module and installed the system apk (music apk). But android 10 denies me access to storage devices.
Any more help?
thank you
By the way. excellent application

Looks like a great piece of kit , just wish I knew how to use it to to moddify a app, and re-sign it well done.

Nice tool, tried to decompile the apk and make change on smali file. Hit the compile button and generate the APK. But it looks like no changes which I had made with the new APK in `2 - Compiled` directory

If it compiled without error then your new changes should be in there
Are you editing the right smali file?
If you are editing libs then make sure you are editing the correct one for the architecture you are installing / testing the APK ( armeabi-v7a or arm64-v8a )