Related
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
racht said:
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
Click to expand...
Click to collapse
yess, thank you! now i found a mkfs.yaffs2 for arm processors for android. it's verry slow.
so i made my sdcard to ext2, and now i try to "extract" my img.
so ... It's used to ?
trapacska said:
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
Click to expand...
Click to collapse
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
propc said:
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
Click to expand...
Click to collapse
it's cool! thank you. now i try to debrand the oroginal x8 rom.
trapacska said:
it's cool! thank you. now i try to debrand the oroginal x8 rom.
Click to expand...
Click to collapse
you know what. i've found a better method to change permissions
1-mount original system.img
Code:
mkdir tmp/1
sudo mount -o loop /your/system.img/path /tmp/1
2-clone permissions from original system.img to your system folder
Code:
chmod -R --reference /tmp/1 /your/new/system/path
and the permission fix done!
EDIT: tested. and worked. I've finally created my own modified ROM (running on sdcard)
EDIT2: some problem with root permissions, will work on it
thank you i found a way to fix permissions too:
1. unyaffs original system.img
2. in busybox shell mount it to r/w
3. copy xrecovery and su and superuser to fresh rom.
(for me it works well without xrecovery fix permissions)
if there is some error, you can fix it with xrecovery
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
bnight said:
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
Click to expand...
Click to collapse
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
propc said:
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
Click to expand...
Click to collapse
/system/framework (for a skin)((but the all folder))
trapacska said:
/system/framework (for a skin)((but the all folder))
Click to expand...
Click to collapse
thanks. will try porting from htc legend 2.2 rom later.
How can Install the Camera apk on the rooted stock with writable kernel DNA? I replaced this apk with the original stock camera apk, changed the permissions to rw--r--r--. Then, rebooted. But, I don't get the new camera options.
thanks.
Did you mount the /system partition as read/write? This is in addition to the writable kernel, and must be done each time you want to change /system while booted. Most root capable file explorers (i.e. ES explorer) have an option to do this, or you could use this adb command
Code:
adb remount
CastleBravo said:
Did you mount the /system partition as read/write? This is in addition to the writable kernel, and must be done each time you want to change /system while booted. Most root capable file explorers (i.e. ES explorer) have an option to do this, or you could use this adb command
Code:
adb remount
Click to expand...
Click to collapse
It worked. Thanks.:good:
Hello. I installed emui 9.1 on my mate20pro with the dload method. I unlocked the bootloader again and rooted the system with patched recovery. The phone is rooted, but the system partition remains in ro. I have tried various apps to mount the system in rw, but without success. I have also tried some commands found on the net both through adb and emulator, but nothing to do. I have also tried using rootexplorer which has been granted root permissions, but fails to modify anything, nor to insert or delete files within the system folders. What can be done?
ernia66 said:
Hello. I installed emui 9.1 on my mate20pro with the dload method. I unlocked the bootloader again and rooted the system with patched recovery. The phone is rooted, but the system partition remains in ro. I have tried various apps to mount the system in rw, but without success. I have also tried some commands found on the net both through adb and emulator, but nothing to do. I have also tried using rootexplorer which has been granted root permissions, but fails to modify anything, nor to insert or delete files within the system folders. What can be done?
Click to expand...
Click to collapse
it's the new filesystem called erofs (Extendable Read-Only File System)
So there's nothing to do?
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
ernia66 said:
So there's nothing to do?
Click to expand...
Click to collapse
Magisk can already 'replace on the fly' file from /system systemless-y.
It dies already support erofs.
Check Magisk documentations.
There is also a way to mount custom erofs partition....
which is?
ernia66 said:
which is?
Click to expand...
Click to collapse
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
Unfortunately I am not able to do it
:crying:
pvillasuso said:
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
Click to expand...
Click to collapse
use search button pls, you will find the solution already posted
ilos said:
use search button pls, you will find the solution already posted
Click to expand...
Click to collapse
Shhh
Here Rootexplorer paying app does not help writing on erofs partitions...
- Or did you meant something else ?
Magisk Doc. :
https://topjohnwu.github.io/Magisk/
So far, out-of-the-box, Magisk is already ready to replace systemless-ly files and paths on /system easily when used with modules.
-Module just need a a small tweak to add Magisk systemless-ly compatibility to other erofs partitions like /cust
Another way would be to bind or mount...
ilos said:
use search button pls, you will find the solution already posted
Click to expand...
Click to collapse
Wow , what , where ???
I did search but maybe I didnt use the right keywords for such an specific issue
Any extra help , would be very appreciated !
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
I'd like to create my own partition but I don't know how to do it. Is there any online guide for beginners that I can try?
oslo83 said:
Shhh
Here Rootexplorer paying app does not help writing on erofs partitions...
- Or did you meant something else ?
Click to expand...
Click to collapse
my reply was not for you but for the off topic before my reply: contact, ph app and message force close after root.
as I said, there is already a solution about force close.
Anyway I can only write in /system/etc and some over folders
oslo83 said:
Build your own erofs partitions (cf. erofs.mkfs)
Unmount stock ones and mount yours.
I just did some test 48h ago on erofs /cust and it seems to work...
-Mounting other file system type on same folder could even work !
Click to expand...
Click to collapse
Hi, I saw that you managed to get a custom erofs partition mounted using magisk. I was wondering if the same could be done for the/product folder because that would allow me to fix the DPI scaling issues found on EMUI 9.0-9.1. Would it be possible to see the code for your magisk module?
Ok, So.
After having a look at what I did with this WorkInProgress...
So far there is 2 main way I thought about and played with:
Method A
A1/
Using the mkfs.erofs tool to make your custom erofs partition and mount it over the original one. (mayne umount it before)
Thanks @ph03n!x for his work on mkfs.erofs.
Thanks @ante0 for his android arm build.
A2/
I did not yet tryed to flash via fastboot or adb these modded erofs images.
Method B
What I'm actually doing is just mounting systemless-y with a magisk module whole folders over erofs one ;
In post-fs-data.sh, I'm doing:
mount -o bind $MODDIR/cust /cust
mount -o bind $MODDIR/version /version
With a ~150MB custom /cust it is working ; It should be tryed/perfected for bigger folders.
Another way, to not replace/spoof the whole folders could be to mount the whole list of custom files at their respective path (-to be tested)
PS: I'm not sure if update-binary module's file should be modded with some:
mount /cust 2>/dev/null
@ line 42
Sources:
https://forum.xda-developers.com/huawei-p30-pro/how-to/erofs-mounting-accessing-img-t3944193
oslo83 said:
Ok, So.
After having a look at what I did with this WorkInProgress...
So far there is 2 main way I thought about and played with:
Method A
A1/
Using the mkfs.erofs tool to make your custom erofs partition and mount it over the original one. (mayne umount it before)
Thanks @ph03n!x for his work on mkfs.erofs.
Thanks @ante0 for his android arm build.
A2/
I did not yet tryed to flash via fastboot or adb these modded erofs images.
Method B
What I'm actually doing is just mounting systemless-y with a magisk module whole folders over erofs one ;
In post-fs-data.sh, I'm doing:
mount -o bind $MODDIR/cust /cust
mount -o bind $MODDIR/version /version
With a ~150MB custom /cust it is working ; It should be tryed/perfected for bigger folders.
Another way, to not replace/spoof the whole folders could be to mount the whole list of custom files at their respective path (-to be tested)
PS: I'm not sure if update-binary module's file should be modded with some:
mount /cust 2>/dev/null
@ line 42
Sources:
https://forum.xda-developers.com/huawei-p30-pro/how-to/erofs-mounting-accessing-img-t3944193
Click to expand...
Click to collapse
I'm rather new to this trying to do something similar on my EMUI9.1 using Magisk, I'm having a problem that i can replace anything in most other folders without much problem like /etc/ for example, but when i try to substitute /vendor/, whatever i put it the folder does not only fail to get substituted, it even disappears from the $MODDIR/system/vendor folder upon restart!
I.e. let's say I create a new file in $MODDIR/system/etc. Upon restart i'm successfully seeing that same file appear /etc.
However when I create a new file under $MODDIR/system/vendor, Upon restart i'm not seeing that under /vendor. ALSO the file is gone from $MODDIR/system/vendor like it was never there.
Any idea what is happening? I've also tried manually mounting in the post-fs-data.sh, where i put the following:
mount -o bind $MODDIR/system/vendor /vendor
That actually caused my system to freeze on the loading screen. I had to reset magisk to non-modded settings in order to get it to run again.
Any help's appreciated.
pvillasuso said:
Sorry OP if this is off topic , but its about magisk and root in 9.1
I have the "system partition remains in ro" issue too , its annoying yes , but I have a bigger problem
When "rooted" , the phone app ( dialer ), and the contacts app both get broken and crash .. So I have to fastbootflash twrp and lose root to make those apps to work normally again
Anyone with the same problem ?
I need root so I can change and use the font ( I like ) with a magisk module
Click to expand...
Click to collapse
i got the solution of above problem from this https://forum.xda-developers.com/huawei-p30-pro/how-to/guide-magisk-root-p30-pro-bl-code-t3938285
Hi I have almost the same issue after updating to EMUI 9.1 the phone hardbricked. It only shows as fastboot on my PC I tried flashing but not sending the img files please help
Build.prop file accidentally got empty and haven't rebooted yet. Any ways to restore it?
Am i screwed?
You have a customer recovery? Then you can dirty flash your rom
I definitely would have done that if i did.
But TWRP was never released for my phone (poco x3 gt)
Depends the device and android version I guess...
I would do getprop and edit the output to build.prop form.
Notice to chmod the file correctly, 644 or whatever..
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
of course you can download stock ROM from xiaomifirmwareupdater and extract build.prop from super.img, but it's more easy to flash super.img from fastboot.
aIecxs said:
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
of course you can download stock ROM from xiaomifirmwareupdater and extract build.prop from super.img, but it's more easy to flash super.img from fastboot.
Click to expand...
Click to collapse
Nvm my phone just got an OTA update.
I just have to restore the root now
aIecxs said:
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
Click to expand...
Click to collapse
And it's empty like how? Weird crap anyway... ok now, so who cares...
Idk but /system /vendor /product /system_ext /odm are ro dynamic partitions inside super partition, either OP did re-duplicate blocks with e2fsck -E unshare_blocks and disabled avb/dm-verity to allow remount rw / system_root (would break OTA), or it simply wasn't written to build.prop at all (magisk systemless overlay)? "empty" could also mean does not exist/no permissions...
https://github.com/Yuyuko1024/device_xiaomi_chopin/blob/lineage-18.1/rootdir/etc/fstab.mt6891
TWRP is available btw
https://forum.xda-developers.com/t/twrp-unofficial-3-6-0-poco-x3-gt-redmi-note-10-pro-5g.4369207
Can I boot to the root filesystem using fastboot and edit the file from there?
I wanted to edit:
/etc/mkshrc
xracerx123 said:
Can I boot to the root filesystem using fastboot and edit the file from there?
I wanted to edit:
/etc/mkshrc
Click to expand...
Click to collapse
It is generally not possible to perform file changes through fastboot/bootloader. To do so, you need to have a runtime environment such as TWRP. Bootloader/fastboot generally only handles partition images.
V0latyle said:
It is generally not possible to perform file changes through fastboot/bootloader. To do so, you need to have a runtime environment such as TWRP. Bootloader/fastboot generally only handles partition images.
Click to expand...
Click to collapse
Unable to edit /etc/mkshrc
I just tried to add variables on Android /etc/mkshrc file but I get an error: Read-only file system Further, I have tried to use adb remount, but it says inaccessible or not found. I tried to use the following: mount -o remount,rw /...
forum.xda-developers.com
Do refer to the above thread, it is sort of related to this topic.
Is it possible, to edit right on the /etc itself? without going through twrp?
Is there any tools that can help?
xracerx123 said:
Unable to edit /etc/mkshrc
I just tried to add variables on Android /etc/mkshrc file but I get an error: Read-only file system Further, I have tried to use adb remount, but it says inaccessible or not found. I tried to use the following: mount -o remount,rw /...
forum.xda-developers.com
Do refer to the above thread, it is sort of related to this topic.
Click to expand...
Click to collapse
It mentions using ADB, which can only be used either through system or recovery.
xracerx123 said:
Is it possible, to edit right on the /etc itself? without going through twrp?
Click to expand...
Click to collapse
Not through bootloader or fastboot. You can dump an image, edit it, and reflash it, but this would all be much more complicated than using TWRP, which would allow you to mount the partition as r+w so you can effect the edit you want.
xracerx123 said:
Is there any tools that can help?
Click to expand...
Click to collapse
Yes...TWRP.
V0latyle said:
It mentions using ADB, which can only be used either through system or recovery.
Not through bootloader or fastboot. You can dump an image, edit it, and reflash it, but this would all be much more complicated than using TWRP, which would allow you to mount the partition as r+w so you can effect the edit you want.
Yes...TWRP.
Click to expand...
Click to collapse
I am using Pixel 6A, currently there is no TWRP. https://twrp.me/Devices/
xracerx123 said:
I am using Pixel 6A, currently there is no TWRP. https://twrp.me/Devices/
Click to expand...
Click to collapse
Details like this are beneficial when asking questions.
The short answer to your original question is no, what you want to do is not possible.
is your bootloader even unlockable?
https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-6a
xracerx123 said:
I am using Pixel 6A, currently there is no TWRP.
Click to expand...
Click to collapse
but there is Evolution X custom recovery at least
https://forum.xda-developers.com/t/4514881