I can not install modul magisk root in this device moto e4 plus, anybody could help ?
Copying zip to temp directory
- Installing [email protected]
- Mounting /system, /vendor
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: config.sh
inflating: module.prop
******************************
Smali Patcher
fOmey @ XDA
******************************
Powered by Magisk (@topjohnwu)
******************************
- Found /data/adb/magisk_merge.img
- Mounting /data/adb/magisk_merge.img to /dev/tmp/magisk_img
! /data/adb/magisk_merge.img mount failed...
Failed!
! Installation failed[/QUOTE]
Flash fuse kernel on medialtek device aosp based rom then magisk module Will work
https://samarv-121.github.io/fuse-nicklaus/
Leo7D said:
Flash fuse kernel on medialtek device aosp based rom then magisk module Will work
https://samarv-121.github.io/fuse-nicklaus/
Click to expand...
Click to collapse
I have done with aex custom rom, i dont have a choice with stock
There is kernel for stock rom too. Take backup of current boot.img and flash fuse kernel for stock rom and try if you want
Leo7D said:
There is kernel for stock rom too. Take backup of current boot.img and flash fuse kernel for stock rom and try if you want
Click to expand...
Click to collapse
Thank you pal
Related
Hi, for those interested I wrote following steps (ubuntu 10.10 32b):
(based on excellent http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images )
I included compiled tools mkbootfs , mkbootimg and perl scripts unpack-bootimg.pl and repack-bootimg.pl.
Repack-bootimg.pl is edited and the needed parameters for our folio are included ([email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:122000:a00:800,linux:a0e00:1000:800,loader:300:400:800,mbr:700:200:800,system:900:20000:800,cache:20900:80000:800,misc:a0900:400:800,userdata:a1f00:80000:800 boardtype=PR)
1) unpack attachement mytools.tgz into your home, in your home the folder ~/mytools is created:
tar -xzf mytools.tgz
2) copy existing boot.img into ~/mytools (from foliomod update.zip)
3) ./unpack-bootimg.pl boot.img
- old kernel from boot.img is extracted: boot.img-kernel.gz
- content of contained ramdisk is extracted in folder: boot-img.ramdisk
4) copy new compiled kernel (zImage) into ~/mytools (from <source>/kernel/arch/arm/boot/zImage , you have to compile yourself with the weeds2000 quide http://forum.xda-developers.com/showthread.php?p=10331797#post10331797)
5) make all desired changes into ramdisk folder
6) repack new boot.img with a new kernel and changed ramdisk
./repack-bootimg.pl zImage boot.img-ramdisk boot-new.img
7) new boot image is created as boot-new.img
8) if you want just to experiment, you can take any full foliomod dexter's update.zip (1.3d), put the new boot image inside instead original one.
It is possible to remove the other 2 images (recovery and system) if you want just to flash kernel. NOTE! But you have to remove the extrating command for recovery and system from update.zip/meta-inf/com/google/android/update-script.
p.s. Feel free to correct me, if something wrong with the steps. It's my first attempt to compile kernel
I am on FolioMod 1.3d and I use the kernel built without patches from http://tegramid.com/wiki/Main_Page(Full GPL source bundle including framework) for a day without problems. I had to do a full wipe. It's meant for testing, I don't say that kernel from source is better or worse.
Many thanks to Dexter because everything is based on his release, weeds2000 because of his kernel compile quide and tsh who placed the sources on the git and to all who try hacking our folio
thx for this, that 'll be usefull
thanks for the guide.
i have managed to do every thing up to the repack
when i type
Code:
perl repack-bootimg.pl boot.img-kernel.gz boot.img-ramdisk.gz boot.img
i get error
Code:
boot.img-ramdisk.gz Not a directory at repack-bootimg.pl line 13.
even though it is definatly in their. any idea how to get it to work?
You don't have to provide the folder instead of the packed Ramdisk-File!
Because this script is made doing changes in Ramdisk and kernel..
So you can change the scripts inside the boot.img-ramdisk folder and the script will repack and add it to the new boot.img!
permission denied
i have done everything as you said, but while using split_bootimg.pl i got "permission denied". please suggest me what to do?
1. Enable read/write permissions for that file.
2. Tobr, you made a mistake in repack-bootimg.pl. You forgot to add " ./ " before mkbootimg.
Jon2555 said:
1. Enable read/write permissions for that file.
2. Tobr, you made a mistake in repack-bootimg.pl. You forgot to add " ./ " before mkbootimg.
Click to expand...
Click to collapse
The script was downloaded from internet not written by me. And it worked for me just fine. I can not verify now that you are right (probably you are). If it works for you with ./ then either I can put fixed version for download for others (if there is anybody) or it can be here just as a notice for other users, if not working.
I have ./ defined in my path variable in my profile so that i don't need it.
eror when repack
tobr said:
Hi, for those interested I wrote following steps (ubuntu 10.10 32b):
(based on excellent http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images )
I included compiled tools mkbootfs , mkbootimg and perl scripts unpack-bootimg.pl and repack-bootimg.pl.
Repack-bootimg.pl is edited and the needed parameters for our folio are included ([email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:122000:a00:800,linux:a0e00:1000:800,loader:300:400:800,mbr:700:200:800,system:900:20000:800,cache:20900:80000:800,misc:a0900:400:800,userdata:a1f00:80000:800 boardtype=PR)
1) unpack attachement mytools.tgz into your home, in your home the folder ~/mytools is created:
tar -xzf mytools.tgz
2) copy existing boot.img into ~/mytools (from foliomod update.zip)
3) ./unpack-bootimg.pl boot.img
- old kernel from boot.img is extracted: boot.img-kernel.gz
- content of contained ramdisk is extracted in folder: boot-img.ramdisk
4) copy new compiled kernel (zImage) into ~/mytools (from <source>/kernel/arch/arm/boot/zImage , you have to compile yourself with the weeds2000 quide http://forum.xda-developers.com/showthread.php?p=10331797#post10331797)
5) make all desired changes into ramdisk folder
6) repack new boot.img with a new kernel and changed ramdisk
./repack-bootimg.pl zImage boot.img-ramdisk boot-new.img
7) new boot image is created as boot-new.img
8) if you want just to experiment, you can take any full foliomod dexter's update.zip (1.3d), put the new boot image inside instead original one.
It is possible to remove the other 2 images (recovery and system) if you want just to flash kernel. NOTE! But you have to remove the extrating command for recovery and system from update.zip/meta-inf/com/google/android/update-script.
p.s. Feel free to correct me, if something wrong with the steps. It's my first attempt to compile kernel
I am on FolioMod 1.3d and I use the kernel built without patches from http://tegramid.com/wiki/Main_Page(Full GPL source bundle including framework) for a day without problems. I had to do a full wipe. It's meant for testing, I don't say that kernel from source is better or worse.
Many thanks to Dexter because everything is based on his release, weeds2000 because of his kernel compile quide and tsh who placed the sources on the git and to all who try hacking our folio
Click to expand...
Click to collapse
hi
when do this in ubuntu 11.4
get eorr below
[email protected]:~/Desktop/untitled folder$ ./unpack-bootimg.pl boot.img
kernel written to boot.img-kernel.gz
ramdisk written to boot.img-ramdisk.cpio.gz
463 blocks
extracted ramdisk contents to directory boot.img-ramdisk/
[email protected]:~/Desktop/untitled folder$ ./repack-bootimg.pl zImage boot.img-ramdisk boot-new.img
gzip: folder/ramdisk-repack.cpio.gz: No such file or directory
sh: mkbootimg: not found
No such file or directory at ./repack-bootimg.pl line 21.
[email protected]:~/Desktop/untitled folder
can any one help me?
any tools for windows ?
nguyenhonganh said:
any tools for windows ?
Click to expand...
Click to collapse
Same request!
repack problem
Can somebody tell me is it possible to repack kernel and ramdisk using just hex editor? Without this scripts and unmkbootimg and mkbootimg. What does not work for me cos im using i9100 Philz root. I know how to unpack it and change init.rc and pack it back again. So can i just put my (kernel+ramdisk) ramdisk.cpio.gz file inside mmcblk0p5 in exac location. Will that work out? I dont know what this is doing:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x20000000
--cmdline 'no_console_suspend=1' -o new_boot.img
this address thing and cmdline but if i replace just ramdisk i dont need to set up addres again cos everything will be in same place. And one more question if something goes wrong can i boot to recovery or download mode?
New kernel copied itself to mmcblk0p5
and i have new CWM now. So it seems to me recovery is inside mmcblk0p5 as well and my phone never use mmcblk0p6
@tobr, I cannot open the archive of boot.img-kernel.gz. When I try to open it with terminal, it says: Not a valid gzip file. What to do?
Hello
I building my first rom and nov have problem
MTK6582
Backup crated with droit tools
After building rom with dsixda, always get cwm update error status 0.
Now i am confused, in working folder is update-script and after build rom is updater-script and updater binary
I try to change format and mount in updater-script but always get status 0
please what iam doin wrong? see attachment mount block, update and updater txt
And can i edit updter script in zip file with 7zip and N++ or i must change it in working folder before buiding rom?
thanks
Extracting:
1. Download this package: https://tusfiles.net/oaiw9ze20tbl
2. Extract to a folder and chmod 777 -r /path/to/the/folder
3. cd (change directory) to that folder
4. Run prereq.sh
5. Place system.transfer.list and system.new.dat into the folder
6. Open extractor.sh using a text edit program
7. Find the line containing chown command, replace yash:yash with yourusername:yourusername
8. Run extractor.sh
9. Modify contents found in output folder
Rebuilding:
1. Do above first and then run compress.sh
2. Find the rebuilt system.new.dat and system.transfer.list in sdat folder
Making it into a ROM:
1. Do above first
2. Find a zip ROM for OnePlus 2 that contains system.transfer.list and system.new.dat
3. Replace it with your rebuilt ones from above mentioned steps
4. Voila! ROM ready!
NOTE:
The package contains OxygenOS SELinux file contexts in progs subfolder...
So, to modify CM ROMs you need to get file_contexts file from the zip of the ROM and replace the one found in progs subfolder
Credits:
@xpirt
Please mention
Two questions; Is this a rom kitchen like tool for OxygenOS? Are there any libs or binaries or other dependencies?
I'm a bit busy, but I'll take it for a spin when I can.
Oh one last thing, is there a repo for this?
Ta,
ALQI
Sent from me mobile.
Nice guide
alquimista said:
Two questions; Is this a rom kitchen like tool for OxygenOS? Are there any libs or binaries or other dependencies?
I'm a bit busy, but I'll take it for a spin when I can.
Oh one last thing, is there a repo for this?
Ta,
ALQI
Sent from me mobile.
Click to expand...
Click to collapse
The dsixda kitchen had much more functions then this but you may cknsidet it as a temporary lollipop kitchen with not much extra functionality..
This was like a automation script for me and was a quick one so repo wasn't needed
I have used this script on Ubuntu 64bit and the only extra dependency apart from those included in package are installed by prereq.sh
Btw this is not just for oxygen os it can also be used for any cm or cm based rom here but.do read the note then
Yash98 said:
Extracting:
1. Download this package: https://tusfiles.net/oaiw9ze20tbl
2. Extract to a folder and chmod 777 -r /path/to/the/folder
3. cd (change directory) to that folder
4. Run prereq.sh
5. Place system.transfer.list and system.new.dat into the folder
6. Open extractor.sh using a text edit program
7. Find the line containing chown command, replace yash:yash with yourusername:yourusername
8. Run extractor.sh
9. Modify contents found in output folder
Rebuilding:
1. Do above first and then run compress.sh
2. Find the rebuilt system.new.dat and system.transfer.list in sdat folder
Making it into a ROM:
1. Do above first
2. Find a zip ROM for OnePlus 2 that contains system.transfer.list and system.new.dat
3. Replace it with your rebuilt ones from above mentioned steps
4. Voila! ROM ready!
Click to expand...
Click to collapse
So does this allow you to make ROM's for the OP2 from ROM's based on other devices, or what? Sorry if I'm sort of a noob, I just don't understand what is being done.
Thanks!
Me1256 said:
So does this allow you to make ROM's for the OP2 from ROM's based on other devices, or what? Sorry if I'm sort of a noob, I just don't understand what is being done.
Thanks!
Click to expand...
Click to collapse
You can make ROMs from prebuilt ROMs like OxygenOS or any other built ROM like Exodus, CM12, etc.
Basically modify ROMs without rebuilding from source (which takes a lot of time!)
Sir I downloaded your tool and followed ur guide....But after I run extract.sh there is no files/folders in output folder.Plz reply thankz in advancw
Thank you. I really wanted to extract .dat file..
Sent from my ONE A2003 using Tapatalk
This is a great tool but I wanted to know how to edit the system folder in ubuntu. Like using chmod and chown to pre-root and uninstall some other apps. Can somebody please direct me in that direction.
I go test...
Hey Guyzzz...... I am Here to provide you the Guide on How to port Lollipop ROMs and MarshMallow ROMs on any Device
New Year Gift For You GuyzFirst Guide on XDA to port ROMs above 5.0.2 (Qualcomm Processor)
Code:
KEEP THESE POINTS IN MIND
This guide wont make you a full fledged dev.
It teaches you the basics of porting ROMS.
If anything happens to your device I AM NOT RESPONSIBLE for IT ! try it on your own risk !
Some Basic things u need to Know before Porting
Code:
The rom which you want to port for your device is named here as [B]PORT[/B]
The rom which is already working for your device is called here as [B]BASE[/B]
Download Some Necessary Files From this Post
1st extract ur base cm,aosp,etc rom on one folder
2nd extract ur Port rom in one folder
Now you can see
boot.img
file_contexts
META-INF
system.new.dat (compressed /system)
system.patch.dat
system.transfer.list
Click to expand...
Click to collapse
Step 1:Ubuntu guide
Now we need to decompress .dat to ext4 img
Open terminal and
Now enter this command
Code:
./sdat2img.py system.transfer.list system.new.dat system.img
By running this command u can see a system.img
Step 2 :decompress ext4 img to output folder
Now we will mount system.img
Enter this command
Code:
sudo mount -t ext4 -o loop system.img output/
Now go to output folder and now u can see all folder and apk like a KitKat rom
Now do the same with port rom
Step 3:Now we will port
Delete some folders from base
Code:
base/system/app
base/system/fonts
base/system/framework
base/system/media
base/system/priv-app
and paste from port
Code:
port/system/priv-app
port/system/app
port/system/fonts
port/system/framework
port/system/media
Now copy some important permissions and init.d files
Code:
port/system/etc/permissions
platform.xml
handheld_core_hardware.xml
handheld_hardware.xml
to base /base/system/etc/permissions
now go to port/system/etc/init.d
and copy
Code:
00banner
to base/system/etc/init.d
Now open the build.prop of both ROMS. Replace the values infront of following
lines in base from port
change frm port to base
Code:
ro.build.id=
ro.build.display.id=
ro.build.version.release=
ro.product.model=
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
base/system/build.prop
port/system/build.prop
Edit meta inf
Now go to metainf/com/google/android
And open updater-script with notepad++
And u can add
Code:
ui_print (" ur text");
and save it
Now we need to again compress rom
Now enter this command
Code:
./make_ext4fs -T 0 -S file_contexts -l 1073741824 -a system system_new.img output/
Now u can see ur system_new.img
Step 4: now we need to compress it back to .dat
Now enter command
Code:
./rimg2sdat my_new_system.img
Now u can see system.new.dat
Now just zip the ROM and flash
Downloads
Click here for sdat2img.py
Click here for make_ext4fs
Click here for rimg2sdat
Now Download all these tools and paste it to ur base and port rom directory then follow instructions to port lollipop roms
Credits
@xpirt
@adityaupreti for guideIf I forgot anyone PM me
A Thanks on our Posts will be Helpful For OUR Efforts ..... Please.....
If u have any queries in Porting.....AdityaUpreti and Me are always here to help you......
Stay Blessed ....... Happy New Year 2K16
Reserved for faq
Reserved
For windows.... Use this Tool http://sourceforge.net/projects/ext2read/files/
Credits: @neonkat for sharing
Cool gonna try it out, thanks man
Bro I want for to port on windows
Finally its here . search lot fr this.. Btw dz guide ll work on snapdragon 810.. E.g. i use 1+2 so . can i port another sp810 roms?
adityaupreti said:
Reserved for faq
Click to expand...
Click to collapse
Bro please tell me how to do this in windows
neelsolanki said:
Finally its here . search lot fr this.. Btw dz guide ll work on snapdragon 810.. E.g. i use 1+2 so . can i port another sp810 roms?
Click to expand...
Click to collapse
If it meet same specs u can port rom
---------- Post added at 09:29 PM ---------- Previous post was at 09:28 PM ----------
salahXDA6805 said:
Bro please tell me how to do this in windows
Click to expand...
Click to collapse
Soon update thread with Windows
adityaupreti said:
If it meet same specs u can port rom
---------- Post added at 09:29 PM ---------- Previous post was at 09:28 PM ----------
Soon update thread with Windows
Click to expand...
Click to collapse
Been looking for this too, thanks for this, will try soon.
[Q]
Is there any most practical way to compare 2 device spec?
NeoLogY said:
Been looking for this too, thanks for this, will try soon.
[Q]
Is there any most practical way to compare 2 device spec?
Click to expand...
Click to collapse
Try 91mobiles.com and compare mobiles there u can see the similarities and differences. ... or gsmarena [emoji6] [emoji571] [emoji571] [emoji571]
........Press Thanks .......
I ported ressurection remix 5.6 for the Moto G 2014 to my LG G3 Beat using an official CM13 base and it bootloops with this guide
Sent from my LG-D722 using Tapatalk
the same here, bootlooping..
Is it almost the same process on windows?
Carlyle_f said:
I ported ressurection remix 5.6 for the Moto G 2014 to my LG G3 Beat using an official CM13 base and it bootloops with this guide
Sent from my LG-D722 using Tapatalk
Click to expand...
Click to collapse
This is where debugging process happen. Log is your best friend now.
yakie47 said:
the same here, bootlooping..
Click to expand...
Click to collapse
I want to port rom for my Spice MI 445 MSM8610 clone of moto e.
I found many custom rom for moto e but didn't know how to port them for my device.
Sent from my Spice Mi-445 using xda Forums PRO
Eklavya Prasad said:
I want to port rom for my Spice MI 445 MSM8610 clone of moto e.
I found many custom rom for moto e but didn't know how to port them for my device.
Sent from my Spice Mi-445 using xda Forums PRO
Click to expand...
Click to collapse
Sry bt u can't port Roms from moto e to ur device
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
yakie47 said:
the same here, bootlooping..
Click to expand...
Click to collapse
kindly give some base ROM info and port ROM info
Also tell base ROM device and port device
Base name port name
i'm porting samsung touchwiz A500fu rom to the chinese version one samsung A5000 base rom, the phone boots up but stuck in samsung boot screen for ever
VigneshS007 said:
Hey Guyzzz...... I am Here to provide you the Guide on How to port Lollipop ROMs and MarshMallow ROMs on any Device
New Year Gift For You GuyzFirst Guide on XDA to port ROMs above 5.0.2 (Qualcomm Processor)
Code:
KEEP THESE POINTS IN MIND
This guide wont make you a full fledged dev.
It teaches you the basics of porting ROMS.
If anything happens to your device I AM NOT RESPONSIBLE for IT ! try it on your own risk !
Some Basic things u need to Know before Porting
Code:
The rom which you want to port for your device is named here as [B]PORT[/B]
The rom which is already working for your device is called here as [B]BASE[/B]
Download Some Necessary Files From this Post
1st extract ur base cm,aosp,etc rom on one folder
2nd extract ur Port rom in one folder
Now you can see
Step 1:Ubuntu guide
Now we need to decompress .dat to ext4 img
Open terminal and
Now enter this command
Code:
./sdat2img.py system.transfer.list system.new.dat system.img
By running this command u can see a system.img
Step 2 :decompress ext4 img to output folder
Now we will mount system.img
Enter this command
Code:
sudo mount -t ext4 -o loop system.img output/
Now go to output folder and now u can see all folder and apk like a KitKat rom
Now do the same with port rom
Step 3:Now we will port
Delete some folders from base
Code:
base/system/app
base/system/fonts
base/system/framework
base/system/media
base/system/priv-app
and paste from port
Code:
port/system/priv-app
port/system/app
port/system/fonts
port/system/framework
port/system/media
Now copy some important permissions and init.d files
Code:
port/system/etc/permissions
platform.xml
handheld_core_hardware.xml
handheld_hardware.xml
to base /base/system/etc/permissions
now go to port/system/etc/init.d
and copy
Code:
00banner
to base/system/etc/init.d
Now open the build.prop of both ROMS. Replace the values infront of following
lines in base from port
change frm port to base
Code:
ro.build.id=
ro.build.display.id=
ro.build.version.release=
ro.product.model=
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
base/system/build.prop
port/system/build.prop
Edit meta inf
Now go to metainf/com/google/android
And open updater-script with notepad++
And u can add
Code:
ui_print (" ur text");
and save it
Now we need to again compress rom
Now enter this command
Code:
./make_ext4fs -T 0 -S file_contexts -l 1073741824 -a system system_new.img output/
Now u can see ur system_new.img
Step 4: now we need to compress it back to .dat
Now enter command
Code:
./rimg2sdat my_new_system.img
Now u can see system.new.dat
Now just zip the ROM and flash
Downloads
Click here for sdat2img.py
Click here for make_ext4fs
Click here for rimg2sdat
Now Download all these tools and paste it to ur base and port rom directory then follow instructions to port lollipop roms
Credits
@xpirt
@adityaupreti for guideIf I forgot anyone PM me
A Thanks on our Posts will be Helpful For OUR Efforts ..... Please.....
If u have any queries in Porting.....AdityaUpreti and Me are always here to help you......
Stay Blessed ....... Happy New Year 2K16
Click to expand...
Click to collapse
When I use command ./sdat2img.py system.transfer.list system.new.dat system.img it shown no such file or directory.
Bro need for windoes
MyAnand13 said:
When I use command ./sdat2img.py system.transfer.list system.new.dat system.img it shown no such file or directory.
Click to expand...
Click to collapse
Try python sdat2img.py system.transfer.list system.new.dat system.img
Sent from my LG-D722 using Tapatalk
---------- Post added at 10:40 AM ---------- Previous post was at 10:40 AM ----------
salahXDA6805 said:
Bro need for windoes
Click to expand...
Click to collapse
Google cgwyn
Sent from my LG-D722 using Tapatalk
physwizz A505 R kernel version 3.1
SM-A505f s9 Android 11
For testing
For OneUI 3.1
( also works for GSIs)
Samsung securities disabled
More CPU governors
Conservative, On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
CPU:
Big 936 MHz - 2314MHz
Little 403MHz - 2054MHz
lz4 default compression added to zram
Bugs:
?
Installation
Post#2
Kernel
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
@physwizz
Installing physwizz custom kernels
INSTALL AT YOUR OWN RISK
I AM NOT RESPONSIBLE FOR ANY BRICKED PHONES
But I will help any well-mannered person to recover.
A. Preparation
1. Root the phone
2. Compress your patched boot.img to make boot.tar
3. Copy boot.tar to PC
B. Installation
Method 1
Install from twrp
Reboot to recovery
Backup boot and dtbo (if available)
Install kernel zip
Wipe both caches
Reboot
Method 2
Install kernel from terminal.
1. Download magisk module (magic-flash.zip) from https://github.com/Magisk-Modules-Alt-Repo/magic-flash
2. Install module and reboot.
3. Open terminal.
4. Navigate to folder containing kernel.zip.
Use
ls to list contents
and
cd to change directories
5. Type su
6. Type flash kernel_name.zip
7. Reboot
Method 3
Using ADB
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload file-name.zip
Method 4
Using boot.img
Install AIK Mobile from magisk modules
Use rootexplorer to access
/data/local/AIK-MOBILE
Add patched boot.img and tap unpackimg.sh
Exit the folder and return to see the files.
Edit the files (eg to add a new Image
rename Image to boot.img-zImage and insert in split-image folder)
Tap repackimg.sh
Rename new_image.img to boot.img
Compress boot.img to boot.tar
Copy boot.tar to PC
Reboot phone to download mode
Install boot.tar from odin
AIKLink
Physwizz Collection
Install from magisk modules Use rootexplorer to access /data/local/AIK-MOBILE Add boot.img or recovery.img and tap unpackimg.sh Exit the folder and return to see the files. Edit the files (eg to add a new Image rename Image to boot.img-zImage and insert in split-image folder) Tap repackimg.sh
t.me
C. Removal
Method 1
Reboot to recovery
Restore boot and dtbo
Reboot
Method 2.
Reboot phone to download mode
Install patched boot.tar from odin
@physwizz
brother you are a genius
Chinito_H18 said:
brother you are a genius
Click to expand...
Click to collapse
Hope it works ok
I don't own this device
friend I was testing the kernel and it goes well in lineageOs, highly recommended
Chinito_H18 said:
friend I was testing the kernel and it goes well in lineageOs, highly recommended
Click to expand...
Click to collapse
Thanks for the feedback
the root did not work, the rest is going very well