How to change the official samsung splash/boot screen/logo samsung - Android Software/Hacking General [Developers Only]

OK first thing first IM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE OR DECIDE TO BE CARELESS OR CREATE A CYCLONE... you know the drill.
Well i stumbled on this by mistake and hey it works!!!!
Some of us do get bored with seeing the same thing over and over again specailly if u keep switching on and off your phone for whatever reason...
we can change boot animations thats popular but now we can the splash screen and by splash screen i mean boot logo and by bootlogo i mean that image that show "Samsung Galaxy **** powered by android"
Samsung stores its boot files in Param Partition but extracting those images is a hustle well now you dont have to... Here's How and its easy...
I dont know if it will work for any other device with a param partition but i am using Samsungs
YOU WILL NEED:
- A rooted device (Samsung)
- Terminal emulator or ADB (I used ADB but still i was at adb shell)
- Being able to check your partition (But ill explain how anyway)
HOW TO
CHECKING PARTITION BLOCK
1.a First check which block is your Param partition
use and root browsing app and goto /dev/platform/****/by-name
where i used *** is where things differ... there are usually two folder and one will have a folder named "by-name"...
take note of the full path to by-name
E.g in my j7 its: /dev/block/platform/13540000.dwmmc0/by-name
1.b In ADB type "adb shell"
now in Terminal or Continue in ADB
- run "ls -l /dev/block/platform/****/by-name"
- It will output all your block partition with their names
- Take the name of your mmcblk*** and mine is mmcblk0p9
NOTE : BACKUP YOUR ORIGINAL PARAM PARTITION
In Terminal or adb shell:
$ su
# dd if=/dev/block/mmcblk*** of=/data/media/0/param.fls
or dd if=/dev/block/mmcblk*** of=/storage/extSdCard/param.fls
-------- on of="Location to your sdcard (ext or int)" Dont use linked storages
Getting another device's Param file (The Boot logo you want)
Backup its PARAM partition by doing The steps above (Get block partition name and extract)
CHANGING YOUR BOOTLOGO[/COLOR]
-Copy the param.fls file you backed up to your device and note the location you put it (Dont overwrite your original)
In Terminal or adb shell
$ su
# dd if=location_param_file_you_copied/param.fls of=your_dev_block_partition
e.g
# dd if=/data/media/0/copied/param.fls of=/dev/block/mmcblk***
to restore your original change your bootlogo by your original Param.fls
image
{
"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"
}
vide:
https://youtu.be/st-VIeW4u2M
CHECKOUT POST 2 BEFORE ....
Downloads on Post 3

NOTICE's
PRO's
- You can change bootscreen to any other samsung you wish
-it will also change recovery and download mode images ... i think
CON's
- Dont know what else the param partition is for.... e.g dont know the side effects
---------- have you had any on your phone????
******** NO, i havent
- PARAM is a partition, it has a size... your stock param size is your partition size...
E.G Param from j7 is 8MB and that from Tab3 is 2MB... meaning Tab 3 param can fit and work in j7 but j7 param cannot work in Tab3
- Screen Size matters... if a bootlogo is too big for your screen itll will be small etc in order to fit
What if i wanna modify the image???
i managed to do this...
1. Create an empty archieve and put in in your phone
In Terminal or adb shell:
$ su
# dd if=/data/media/0/param.fls of=/data/media/0/archieve.zip
after this, all the images will be on the zip... N.B not in... On the zip
you can view them in the zip and extract them but you cannot add files to the archieve thats the problem...
7z says ... There are files at end of archieve (Not quite sure but something like that):
so thats where you guys and devs come in... making that zip addable...
if you extract the zip and compress it again... its size drops and if you flash it... it removes the boot image.

reserved
Downloads: PARAM by Other people
PARAM upload and download thread here
If you have question and/or answers... feel free :good:

can't modify image on j5 2016. I create archieve.zip but it say corrupted archive on any archive manager. I want old boot logo.jpg, any other way? decrypt, extract, convert param.lfs...??

How to modify param file in tab S6 ??

Related

[solved] resized data img for incubus26jc's froyo 2.2

Can anybody share a 1G data.img? I am not familiar with linux but I want more space on my polaris.
regards
EDIT: the solution here http://forum.xda-developers.com/showthread.php?t=741383
Code:
This can be done with any data.img... even existing one one.
Boot phone in windows mobile. attach to linux box(linux computer or live cd) in disk mode(when u attach hd2 to computer it will ask mode,select disk mode).
go to terminal.
go to the /media
then go to the directory which represents your hd2 phone, then to [B]andboot [/B]directory.
then enter following commands
e2fsck -f data.img
(if it asks to fix say y)
resize2fs -p data.img 512000
(this is for half gb, change it as per requirement)
e2fsck -f data.img
Then reboot the phone.
You may see green screen. if so, simply reboot again.
works like a charm.
no need to download huge file. can be done with a used data.img at any time and any number of times.
Last edited by bhaveshdj; 1st August 2010 at 03:43 PM. Reason: to give more info
You need to install ubuntu first / You do not need any partitions
Install normally first, system to NAND and data to data.img
Remove the card from the phone
Move the card to the phone and reboot
You are done.
Storage shows 2,36 G for me now (2,13 G free after installing 60 programs), and I still have 11,55G for music, maps and so on !
kk last kernel + incubus26jc's RLS14
{
"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"
}
Note: do not ask me to share it because it constains all personal configuration and I do not know yet how to clean it.
Now the question is: when I want to update to next release, what do I have to do? install data to data.img and resize it again? or I can overwrite with my old&big data.img file?
you can create it using boot script generator (select the size)
ok I thought your tool required the nbh posted in your thread.
I have created the sh file but before I flash may be you can help me:
1. What I want to do is to install all apps to my 16g sd. Typically in windows mobile I keep 6g in music, 4g in onroad and offroad navigators and maps 1g on installed apps and 2g on non installed apps.
2. After quite a lot of reading, I do not understand which options do I have with incubus26jc's froyo 2.2. for pola100: apps2sd? dataimg? ext2 partition? linux swap on a third partition?
3. Your tool can help creating partitions? does it exist an easy way to create partitions from windows with no linux and no money?
4. Which set-up would you recommend to me data.img or ext2? I like it fast boot and fast performance so I am trying nand install.
5. I can not flash from the sdcard so I flash the nbh from windows and leave the rar file in andboot. If I leave your sh in andboot will it work?
6. If I do not use the script generated by your app and resize data.img manually will I have to do it everytime I try a new ROM?
thanks so much for your help so far.
new nbh has all you need to make it works inside.
i'm writing a new tool to partition sd card but is in alpha version and i need dzo release my file...
Well it seems not easy to me:
I stick to Kakt_Kaffe kernel + incubus rls 14 since i have wifi and camera with no probs. I have installed ubuntu and formated the sd card with fat32,ext and lynux-swap but I can not install data to the partition. sigh
I have also tried with the same kernel your script and I does not boot.
I will try to resize my data.img in ubunto (reinstalling now because I rebooted ubuntu without noticing it was downloading a system uptade)
If you need beta testers for the sd partitioner I can do some testing.
Solution in first post.
Now the question is: when I want to update to next release, what do I have to do? install data to data.img and resize it again? or I can overwrite with my old&big data.img file?

[Tool] Yaffs Explorer, made for Defy

Its a free Root Explorer without Ads and without network use.
When busybox and root modes are enabled, you can make dumps of your nand partitions and export Kernel and initramfs (Menu/Tools)
{
"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"
}
https://market.android.com/details?id=fr.wdscript.yaffsexplorer
You can report here bug and feature requests...
Example : Dump and Rename The /cdrom partition (p17)
change dump file ext from .raw to .iso and you get your Windows drivers (MotoHelper 2.0.44 Driver 4.9.0 - 27 Jan 2011)
Version 1.9.9.8 attached
Awesome thanks, will def check this out.
useful tool
How can i dump the roofs?
can i restore it after backup?
Thank you.
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Update v1.1 : You can create yaffs images now
Epsylon3 said:
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Click to expand...
Click to collapse
Do you know, how to dump and remount the rootfs?
Thank you.
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Epsylon3 said:
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Click to expand...
Click to collapse
Ok, thank you.
Ok, been using this for a while now; couple suggestions.
1. Copy feature needs to work more like Root Explorer.
---- So when you long-press and copy a file, two buttons popup, Paste and Cancel - Maybe you could even add a third to paste quickly to a favourites folder without leaving working directory ?
2. Be able to change text size of file browser. I have big fingers heh.
3. Have a Mount/Unmount button similar to the Mount R/W in Root Explorer.
--- I find I cant copy anything to anywhere, am I just missing something ?
4. Select multiple files, and copy, delete, zip, move . . . . . to favourites ?
5. Compress files or folders and save zip to a saved favourites without leaving working directory.
6. Load apk icons maybe; easier to find things sometimes.
7. Show favourites picker on program startup. I'm always working in the same directories.
A built in text editor with line numbers would be awesome. Maybe an sqlite editor addon too ?
I like what this looks like so far; I really like that you can see symlinks, the dropdown with recent paths, nandroid dumps of any partitions (nice), and the favorites are cool. Just hoping it can take over for root explorer.
Keep up the great work so far. Will be keeping on eye on this for sure.
Thanks for your report
First, i dont want to copy Root Explorer or all these slow and "3 lines" explorers... So no image/movies preview... This tool is focused on system files exploration
Apk icons maybe but not in my prority (filter by name is nice), line size : not for the moment (maybe a zoom or something later)
The multiselect on click is almost ready (for files), to keep folder navigation
the Mount/Unmount will be in tools menu later (in mounted devices menu) i need to make a new window for that... but that need work (and could make lot of reports from unknown devices, like chinese ones)
Compression.... yea hmm v2.0
Hm. I tried this, but it is a lot slower than Root Explorer. Perhaps this is because it shows a lot more objects, or due to it having a lot of features I do not directly associate with a program to manage files. Still, I can not say that having more competition is a bad thing, so keep up the good work
its because the tool use a terminal process to list folders, and a new one on each refresh... I think i can optimize that if i keep the shell process opened.
but Root enabled, its 5x slower (220ms instead of 40ms)... i think there could be a problem with superuser tool, will try to uninstall it to check...
johnw.xda said:
Do you know, how to dump and remount the rootfs?
Thank you.
Click to expand...
Click to collapse
to remount In fact like others :
Code:
mount -o rw,remount,relatime -t rootfs rootfs /
This feature will be available in some minutes (v1.3.0)
But to dump... you need to skip /proc /tmp and /sys
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Its the next step yaffs extraction...
sorry, not for the moment (but soon)
just made an update v1.3.2 which really enhance exploration speed...
I hope you release it soon
Thanks
I can't Dump Partition. A circular thing shows up then it disapear and no text saying records in+out and that it finished (like in the screenshot). And there is no file on my SD card and yes I have plenty of space.
Tried several of the small 512k partitions and the Boot and Recovery partitions.
I'm running rooted froyo 3.4.2-155, few bloat APK's removed.
this feature uses busybox "dd" applet, try to set another busybox in setting window
you can search for them in other apps, do a search in /data/data/
Namiga said:
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Click to expand...
Click to collapse
Done... in v1.5.0 Single file or Folder for the moment... (file/folder context menu)
full extraction will be possible in next version... not linked

[Dump] Tab 4 7.0

Galaxy Tab 4 7.0 (3G) system dump
~~~~~~~
Apps:
HERE
~~~~~~~
priv-app - folder:
HERE
~~~~~~~
media - folder:
HERE
~~~~~~~
Framework:
HERE
~~~~~~~
lib - folder:
HERE
~~~~~~~
bin - folder:
HERE
~~~~~~~
vendor - folder:
HERE
~~~~~~~
etc - folder:
HERE
~~~~~~~
recovery.img:
(I´m not sure if this image is working please give feedback)
HERE
~~~~~~~
boot.img:
(I´m not sure if this image is working please give feedback)
HERE
~~~~~~~
build.prop:
HERE
~~~~~~~
Note: I´m not responsible for any damage to your device
~~~~~~~
Wrong device ?
Galaxy Tab 4 10.1 dump here
Galaxy Tab 4 8.0 dump Coming soon
Make your own dumps Coming soon
​
Thank you so much bro
Waiting for this \m/
Sent from an expensive Toaster (SM-T211)
Boot
Hey I'm trying to make a boot.img dump myself. Did you find out if you dumped the right mount point? I downloaded Partition Table from the play store and it shows all the mount points but I'm not sure which one is the boot. It doesn't actually specify a boot partition and if i go into the /dev/block/platform/soc,2/by-name folder it doesn't have a boot file in there or an aboot file. So I'm confused.
ubuntu is the solution
TheOriginalist said:
Hey I'm trying to make a boot.img dump myself. Did you find out if you dumped the right mount point? I downloaded Partition Table from the play store and it shows all the mount points but I'm not sure which one is the boot. It doesn't actually specify a boot partition and if i go into the /dev/block/platform/soc,2/by-name folder it doesn't have a boot file in there or an aboot file. So I'm confused.
Click to expand...
Click to collapse
Hey,
I can't help you with that using a phone.
I have done this multiple times using Ubuntu.
PHP:
sudo apt-get install abootimg
sudo abootimg -x boot.img
mkdir workspace
cd workspace
gzip -cd initrd.img | cpio -i
I could upload the dump, too !?
UAdeveloper said:
Hey,
I can't help you with that using a phone.
I have done this multiple times using Ubuntu.
PHP:
sudo apt-get install abootimg
sudo abootimg -x boot.img
mkdir workspace
cd workspace
gzip -cd initrd.img | cpio -i
I could upload the dump, too !?
Click to expand...
Click to collapse
Wait I don't quite understand did you successfully dump the boot img from the tablet? Cause it looks like your just making a boot img there (not too linux friendly I mainly use windows)
TheOriginalist said:
did you successfully dump the boot img from the tablet?
Click to expand...
Click to collapse
Yes (using the linux method) ...
Do you need it? I could upload it tomorrow
Hi, all I really need is the keyboard files but, I cannot see the files. I can ony see so many and the list cuts off. Also, I cannot download the .zips. Is there any way you could just link me to the keyboard files, please?
{
"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"
}
UAdeveloper said:
Wrong device ?
Galaxy Tab 4 10.1 dump here
Galaxy Tab 4 8.0 dump Coming soon
Make your own dumps Coming soon
​
Click to expand...
Click to collapse
still waiting for 'make your own dumbs'
bubenking said:
still waiting for 'make your own dumbs'
Click to expand...
Click to collapse
I don`t work with Samsung Tab´s anymore, sorry.
If someone wants me to link him to his work, pm me.

[OTA] ADB-Enabler - Flashable UPDATE.ZIP File

{
"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 tool is not meant to be used on Android devices with dm-verify or Android Verify Boot (AVB) enabled
Every Android device has a stock recovery installed. That default recovery typically at least offers you the 4 options
reboot system now
apply update from sd card
wipe data factory reset
wipe cache partition
thus you can place any valid update.zip in device's SD-card slot and update your Android from external SD-card.
Because being in recovery mode Android isn’t loaded, the Android system files are not placed in memory, which means they can be accessed, edited and replaced.
That fact allows Android users to enable ADB on their devices what natively support ADB, if they haven't done it yet, for whatever reason.
Download the signed ADB.Enabler.OTA.ZIP from here . IMPORTANT: Rename it to UPDATE.ZIP before you make use of it.
If you get error "Signature verification failed" means that OEM/Carrier blocked to flash a 3rd-party OTA. You would need to have a Custom Recovery like CWM/TWRP already installed and use that to flash the ADB.Enabler.OTA.
HTH
link not working
I am looking for zip that can enable usb-debugging and disable RSA keys without touching /data (encrypted/not mountable):
- boot.img
- system.img A-only SAR system-as-root device
I tried modifying build.prop and default.prop manually but it seems adbd is not running at all
got inspired by @ehteshamxa and created some flashable zip which does NOT modify system files. instead own files added
Code:
/system/etc/init/99userinit.rc
/system/xbin/99userinit_daemon
/sdcard/userinit.sh
/sdcard/rsa_copy
Instructions:
- install userinit-rsa_copy-flashable.zip
- install Magisk.zip
- copy adbkey.pub to SD Card
USE AT OWN RISK
aIecxs said:
got inspired by @ehteshamxa and created some flashable zip which does NOT modify system files. instead own files added
Code:
/system/etc/init/99userinit.rc
/system/xbin/99userinit_daemon
/sdcard/userinit.sh
/sdcard/rsa_copy
Instructions:
- install userinit-rsa_copy-flashable.zip
- install Magisk.zip
- copy adbkey.pub to SD Card
USE AT OWN RISK
Click to expand...
Click to collapse
is root required?
No root required. Magisk is recommended for easy avb/dm-verity disable, but of course one can also place the files manually by unpack/repack (simg2img/sdat2img) flash tool method.
optional:
- copy sqlite3 binary to SD Card
(get it from here credits: @DiamondJohn)
- copy Magisk-v23.0.apk to SD Card
(credits: topjohnwu you all know of course)
have added example code in userinit.sh that can authorize su permissions for adb shell. useful on broken screen in case one can't get scrcpy to work on boot-loop
(credits: @mirfatif for magisk.db injection)
rsa_copy works also from emulated storage if one edit the path in first line:
Code:
sdcard=/sdcard
on locked screen external MicroSD Card is only available location as MTP might not work. in that case place files from PC card reader and insert back
remember the whole purpose of that backdoor is inaccessible userdata partition, otherwise one could just add rsa_copy or 99userinit_daemon to /data/adb/service.d systemless-ly instead (or most straightforward inject /data/misc/adb/adb_keys directly).
once got su shell one can backup partitions, for example:
Code:
adb shell su -c "cat /dev/block/dm-0 2> /dev/null" > userdata.img
edit: visit main thread for more discussion
https://forum.xda-developers.com/showthread.php?t=2965462
FIX THE LINK
@AlinTecsan​So let me see f I understand well.T enable adb ub )I have stock A71 with android 11 I download this file (ADB.Enabler.OTA.ZIP file missing can u uplad it please?) the rename it in UPDATE.ZIP ,put it n SD restart handy n recovery mode selecting "Apply update fron SD card" and that will be all?
helen2 said:
@AlinTecsan​So let me see f I understand well.T enable adb ub )I have stock A71 with android 11 I download this file (ADB.Enabler.OTA.ZIP file missing can u uplad it please?) the rename it in UPDATE.ZIP ,put it n SD restart handy n recovery mode selecting "Apply update frn SD card" and taht will be all?
Click to expand...
Click to collapse
i didnt try yet i need this file this is gone as a cloud
AlinTecsan said:
i didnt try yet i need this file this is gone as a cloud
Click to expand...
Click to collapse
me to maybe I will sort ut all my troubles let we wait post is quite old :/
This won't work on stock recovery anyway, it's for custom recovery only

Android 10+ system file r/w access

Hi what is secret to using file manager on phone Android 10+ with su access to read and write in system - remove bloat apps? I have su access, but I read in 10+ file system not allow from file manager, only need use adb. How to use file manager with su to remove manually on Android 10+? I get error when deleting app from any file manager with su access "cannot delete". Danke.
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect(,avb_keys=/product/etc/security/avb/oem.avbpubkey)code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
{
"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"
}
SirisRui said:
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect(,avb_keys=/product/etc/security/avb/oem.avbpubkey)code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
View attachment 5577955
Click to expand...
Click to collapse
Wow very complex but thank you for explain!

Categories

Resources