Database Develop

[Q] how to create cm7.2 odin flash fw

hi guys i am running cm7.2 nightly on my captivate and i want to create an odin flashable firmware of cm7.2 rom on windows xp for backup purpose please give me a full tutorial on doing this

I believe it isn't possible. I was asking around for ICS and from what i gathered it isn't.

Two things you could do.
1.download the newest nightly that you want to base it on.
2. Use Root Explorer and EXTRACT ALL.
3. Then go to the extracted folder for the nightly, and delete out the SYSTEM folder.
4.Now MAKE SURE you have your phone set up EXACTLY how you want it to look like. Reboot the phone once that is done.
5. Now with root explorer navigate to /system and long press on the system folder. Choose COPY
6. Navigate to the extracted folder (which should be like sdcard/speedsoftware/extracted OR something like that) and go into the folder where you deleted out SYSTEM folder earlier. Now long press and choose PASTE.
7. Back out until your back at the extracted folder name, long press on it and choose RENAME. Pick the name you want it to be. (I usually use something like: CM7.2RockRattRedRemixThemed02-10-2012).
8.Long press on the name again and choose ZIP THIS FOLDER.
9. GO TO ZIPPED FOLDER.
10. Move the zipped folder to your sdcard, reboot to recovery and flash it to make sure it works.
11. If it worked just copy or or move that .zip file to your computer for backup.
Or I can upload the one I have created so you can see it and test it out. I have made some other changes so it is partially already themed, has the theme chooser. apk File I use instead of the stock theme chooser .apks that come with the original cm7. I use zip themer to set up certain things so they are automatically themed when just flashing the build i created. Hope this helps you get an idea of a pretty bazsic way of making your own cwm flashable cm7 rom already personalized. Oh I also delete of some of the apps that come in cm7 and just put my own personal apps into the system folder so I already have them built in.
Sent From My KickAss ATT SGS2 SPORTING CM7

RockRatt said:
Two things you could do.
1.download the newest nightly that you want to base it on.
2. Use Root Explorer and EXTRACT ALL.
3. Then go to the extracted folder for the nightly, and delete out the SYSTEM folder.
4.Now MAKE SURE you have your phone set up EXACTLY how you want it to look like. Reboot the phone once that is done.
5. Now with root explorer navigate to /system and long press on the system folder. Choose COPY
6. Navigate to the extracted folder (which should be like sdcard/speedsoftware/extracted OR something like that) and go into the folder where you deleted out SYSTEM folder earlier. Now long press and choose PASTE.
7. Back out until your back at the extracted folder name, long press on it and choose RENAME. Pick the name you want it to be. (I usually use something like: CM7.2RockRattRedRemixThemed02-10-2012).
8.Long press on the name again and choose ZIP THIS FOLDER.
9. GO TO ZIPPED FOLDER.
10. Move the zipped folder to your sdcard, reboot to recovery and flash it to make sure it works.
11. If it worked just copy or or move that .zip file to your computer for backup
Click to expand...
Click to collapse
thanks for your effort and reply but i want to create odin flashable fw not cwm, i know how to create cwm flashable rom, but anyway thanks for your reply

You could DD'ing a back up of all partitions and then tar'ing it, then flashing it in ODIN

Aren't the partition blocks different on AOSP?

Yess, but you can look them up then dd them, and DL the pit with heimdall, and create an ODIN FW flasher

Boot.img vs zImage. Way around?

decompile the boot.img and grab the zImage from the decompiled boot.img

b-eock said:
You could DD'ing a back up of all partitions and then tar'ing it, then flashing it in ODIN
Click to expand...
Click to collapse
can you please tell me step by step tutorial, i also dont know about dd'ing and do not use heimdal so cannot create pit file

Modify SGS3 Photowall Livewall paper to add own pictures

Hi Devs,
I was wondering if there is a way to modify the photowall live wallpaper and add your own pictures, I tried to look for a guide & modified app, however no luck.
Found 1 modified apk with batman pics but that didnt work.
Please let me know if anyone has been able to modify or is working on this.
Regards,
[email protected]

If at beginning of your title you put " (REQUEST) "then you might get better and faster answer.
Sent from my SGH-I897 using xda premium

Steps To Modify SGS3 Photowall Live Wallpaper
Hi All,
I had tried multiple roms and when used the Photowall Live Wallpaper, I could not point it to the photo gallery to use my own pics. The gallery would never open and I had to do with the default pics which came with the SGS3. (Not sure if anyone has faced this issue).
After playing around with the apk files I did find a way to use my own pics in the PhotoWall Live Wallpaper. I hope you would like this.
A: Uploading your pictures in the Photowall.apk file.
1. Select a maximum of 8 pictures that you wish to use in the Photowall and move them to a folder on your desktop.
2. Rename the 8 pictures as follows: g1p1.jpg / g1p2.jpg / g1p3.jpg / g1p4.jpg / g1p5.jpg / g1p6.jpg / g2p1.jpg / g2p2.jpg
3. Extract the Photowall.apk from ICS ROM onto a folder on your desktop. (I used RemICS v1.3, haven’t tried this is on any other ROM).
4. Open the apk file using winrar. (Do not extract, just open)…. Navigate to the PhotoWall.apk\res\raw folder.
5. You should be able to see the files as shown in the screenshot 1.jpg
6. Click on “Add” and navigate to the folder where you have stored the pictures (remember to rename them as mentioned in step 2).
7. Select the files and click “OK”. This will replace the original files in the Photowall.apk.
8. Once this is done, exit/close the apk file opened in winrar.
You can try installing this file directly by copying it to your phone, however that didn’t work on my phone.
B: Uploading your customized Photowall.apk file in your ROM. (Tested on RemICS v1.3).
1.Open the Rom that you wish to flash (I used RemICS UX v1.3) using winrar (do not extract)
2.Navigate to \data\app folder.
3.Click on “Add” and navigate to the folder where you have saved your customized Photowall.apk. (Make sure that the name is “Photowall.apk”).
4.This will replace the original Photowall.apk with your customized file.
5.Exit and save the zip file.
6.Use the new edited Rom and copy it to the root of your “Internal SD” card.
7.Reboot the phone to “Recovery” and flash the new Rom. (I did not lose my data & settings as I did not wipe cache partition or Data/Factory, however this may or may not work for you. To be on a safer side please backup your data and applications. I will not be responsible for any data loss or bricked devices while trying this procedure. Try at your own risk.).
You can watch the video on the link below (sorry for the poor quality)
http://www.youtube.com/watch?v=Yd2VCzvphu8&feature=youtu.be
Special thanks toTeam RemICS for the beautiful Rom.
If you liked my work, please use the thanks meter.
- Disclaimer -
This product/steps is/are free to use at your own risk. I take no
responsibility for any conflict, fault, data loss or damage caused by this procedure.
No warranties, implied or otherwise, are given if you agree to use this product.
No problems were found while testing this on my Samsung Captivate device. your experience may vary.

maqbulsayed said:
B: Uploading your customized Photowall.apk file in your ROM. (Tested on RemICS v1.3).
1.Open the Rom that you wish to flash (I used RemICS UX v1.3) using winrar (do not extract)
2.Navigate to \data\app folder.
3.Click on “Add” and navigate to the folder where you have saved your customized Photowall.apk. (Make sure that the name is “Photowall.apk”).
4.This will replace the original Photowall.apk with your customized file.
5.Exit and save the zip file.
6.Use the new edited Rom and copy it to the root of your “Internal SD” card.
7.Reboot the phone to “Recovery” and flash the new Rom.
Click to expand...
Click to collapse
I think you over complicated the install process by a bit...
Why not just use a file explorer with root permissions and place the new Photowall.apk back to /system/app where it actually belongs, reboot the phone and be done with it? (/system/app is where live wallpapers that come with the phone are located by default, not /data/app)
As you can see here on my GS3, two of the several live wallpapers (phase beam and photo wall) are in /system/app
And these are the proper permissions for the apk

I tried that, but that wont work..... that the reason i mentioned
" You can try installing this file directly by copying it to your phone, however that didn’t work on my phone. "
Unfortunately wht u menitioned didnt work for me...
correct me if I am wrong... did u mention SG3... for SG3, you dont need to modify the photowall.apk, if you go to the wallpaper settings you can select pics from your gallery..

maqbulsayed said:
I tried that, but that wont work..... that the reason i mentioned
" You can try installing this file directly by copying it to your phone, however that didn’t work on my phone. "
Unfortunately wht u menitioned didnt work for me...
correct me if I am wrong... did u mention SG3... for SG3, you dont need to modify the photowall.apk, if you go to the wallpaper settings you can select pics from your gallery..
Click to expand...
Click to collapse
Yes, I understand that on the SG3 you don't need to do this, but on a Captivate, I don't see why you wouldn't be able to place it in /system/app and still have it work.

[SOLVED]How to convert system.sin to system.img?

Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.

Rycon33 said:
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Click to expand...
Click to collapse
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones

gregbradley said:
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
Click to expand...
Click to collapse
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?

Rycon33 said:
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Click to expand...
Click to collapse
wait, let me boot into linux and I will check

gregbradley said:
wait, let me boot into linux and I will check
Click to expand...
Click to collapse
mate, btw I'm only using cygwin in win7 if that matters on my issue

Rycon33 said:
mate, btw I'm only using cygwin in win7 if that matters on my issue
Click to expand...
Click to collapse
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,

gregbradley said:
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
Click to expand...
Click to collapse
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16

Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?

gregbradley said:
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
Click to expand...
Click to collapse
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework

Rycon33 said:
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Click to expand...
Click to collapse
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.

gregbradley said:
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
Click to expand...
Click to collapse
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained

Rycon33 said:
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Click to expand...
Click to collapse
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.

Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app

gregbradley said:
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Click to expand...
Click to collapse
asterix005 said:
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
ok mates, thank you very much, I managed to de-odexed my stock ROM:good:

This is what I did. Using flashtool, I dumped my system.sin file to get a ext4 file. Then I open it with ext4 reader and extracted the contents. I then placed it in a folder called 'system' and proceed with the android kitchen.
Humans have evolved to be smarter, but there's one thing we can't get rid off. It's human stupidity.

If you still want to deodex playstationcertified.odex rename it to com.playstation.playstationcertified.odex.
That did the trick for me in earlier firmware versions.
Sent from my phone using XDA Premium

i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67

lucky92 said:
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
Click to expand...
Click to collapse
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?

gregbradley said:
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
Click to expand...
Click to collapse
i tried extract thee system.sin into ext4 and rename it to sysmtem.img but no luck
update: after re-dump system.sin and press countinue, it's seem ok, maybe my fault.
Thank you anyway :laugh:

Sorry but I have another question, after i make a flashable zip and flash through CWM, it always stuck at Sony logo, any idea ?

[GUIDE][TUTORIAL] Create small flashable zips to restore before applying MODs/Fonts

I originally posted this on the G2 forum, now I am on OnePlus and I realized of course this is the same procedure with a few small differences in file locations, etc, so posting here too.
GUIDE: CREATING SMALL FLASHABLE ZIPs TO RESTORE FILES OR SETTINGS WITHOUT HAVING TO DO FULL NANDROID RESTORE
This will enable you to apply MODs without having to do a FULL NANDROID restore to recover if the MOD fails or if you don't like it
This brief guide will teach you how to create a flashable ZIP file that you can use to restore your phone to pre-MOD settings if you want to revert back or if the MOD simply does not work
WITHOUT having to do a full restore of your phone.​
It is a very good idea to create these backup flashable ZIPs and keep them safe to recover from mishaps or when creating/testing MODs/themes.​
*************************************************************************************************************************************************
As usual: Disclaimer: I am not responsible for any loss of data or functionality on your phone. To be 100% sure, always make a NANDROID backup if you are not 100% certain you can recover.
*************************************************************************************************************************************************​
There are many reasons you might want to do this, for example when testing a MOD for another ROM that is similar to yours but not exactly the same, or when upgrading your ROM to a new version and wanting to re-apply old MODs to test if they work.
There are many ways to get into boot loops or fail to boot, the biggest culprit being fonts installations, but include also bootanimations and others.
INSTRUCTIONS:
Part 1: general
1. Install ZIPme app from playstore
2. Find out which files are being modified by the MOD you are trying to apply, this is usually framework-res.apk, SystemUI.apk, but be aware that some MODs affect a lot of files. See part 2 for more details on how to do this.
3. If you are applying a font, don't worry, the FONTs section (see part 2) should cover all Fonts.
4. If you are applying a bootanimation, don't worry, the bootanimation section (see part 4) should cover all Bootanimations.
5. For every flashable ZIP you create you can test it straight away by booting into recovery and applying the zip file. There is no reason why it should not work.
Part 2: FONTS
1. In ZIPme select the following:
- ADD FOLDER: /system/fonts
- ADD FILE: /system/etc/system_fonts.xml
2. Create the flashable zip in an /sdcard location you can access from recovery
Part 3: MODs that affect framework-res.apk, LGSystemUI.apk or any other app
1. Find out which apks are being modified:
- You should of course read the OP (instructions for the MOD)
- The easiest way to find out modified apks is to download the MOD and open it: the zip file will contain either the apk files themselves or have directories with the names of the apks being modified.
- You can always ask the developer to make sure
2. Once you have a full list of files being affected you can create the flashable zip:
- in ZIPme, simply select "ADD -> File" for every file being affected
- If you have an ODEX ROM (.odex files are present) make sure you pick those too!
- save the flashable zip in an /sdcard location you can access from recovery
Part 4: Bootanimations
1. In ZIPme select the following:
- ADD FILE: /system/bin/bootnimation
- ADD FILE: /system/media/bootanimation.zip
2. Create the flashable zip in an /sdcard location you can access from recovery
Part 5: Other flashable files you should always keep handy
1. Always keep with you the following files for good measure: they don't take much space but can help recover from problems without having to fully restore from NANDROID backup
- original kernel from your ROM
- flashable bootloader (if you do not know what I am talking about then DON'T do it)
- flashable baseband (if you do not know what I am talking about then DON'T do it)
- flashable recovery image (TWRP, etc)
- "Xposed-Disabler-Recovery.zip": this is created by Xposed when you install it. It is located in the root folder of your sdcard. Copy it and put it somewhere safe.
- SuperSU: keep a flashable latest SuperSU with you to recover root
Any comments, suggestions, feedback are welcome

android 11 root problem miui 12.5

hi.I rooted the phone using magisk, it was installed and apparently rooted, but I have a problem with root file programs like root explorer or es file manager. The problem is that the rw mount does not work or I even have trouble installing busybox.
my phone : redmi note 10 pro
miui version : 12.5.8 and 12.5.9
android version : 11
magiak version : 23

I don't know deeply this case, but it was told that mounting r/w is not possible in recent Androids for system partitions.
However this is Magisk benefit that you put your files to it's tree and Magisk overmounts original files, I guess it does it using option "mount --bind".
You put file into /data/adb/modules/<module_name>/system/etc/<exemplary file> and after reboot you see it under /system/etc/.
At least the above path was checked personally by me by changing /system/etc/gps_psds.conf file to my own.

F308 said:
I don't know deeply this case, but it was told that mounting r/w is not possible in recent Androids for system partitions.
However this is Magisk benefit that you put your files to it's tree and Magisk overmounts original files, I guess it does it using option "mount --bind".
You put file into /data/adb/modules/<module_name>/system/etc/<exemplary file> and after reboot you see it under /system/etc/.
At least the above path was checked personally by me by changing /system/etc/gps_psds.conf file to my own.
Click to expand...
Click to collapse
I want to install a program as a system, but it is not possible without rw mount, do you know the solution?

I presume you have at least one Magisk module installed.
Put it into /data/adb/modules/<any_Magisk_module_name>/PATH_WHERE_YOU_WANT_TO_HAVE_IT/.
If wanted directories don't exist - create them.
Reboot.
Check.
Maybe tune permissions to make file executable.
Report result here.

F308 said:
I presume you have at least one Magisk module installed.
Put it into /data/adb/modules/<any_Magisk_module_name>/PATH_WHERE_YOU_WANT_TO_HAVE_IT/.
If wanted directories don't exist - create them.
Reboot.
Check.
Maybe tune permissions to make file executable.
Report result here.
Click to expand...
Click to collapse
I have no problem installing the module. My problem is accessing the system / app folder and making changes.

What changes do you want to perform?
Change one or more of files there, right?
If so - I repeat.
Put your modified file(s) under /data/adb/modules/<any_installed_Magisk_module_name>/system/app/ and reboot.

F308 said:
What changes do you want to perform?
Change one or more of files there, right?
If so - I repeat.
Put your modified file(s) under /data/adb/modules/<any_installed_Magisk_module_name>/system/app/ and reboot.
Click to expand...
Click to collapse
I do not want to install the module, I want to move an apk file to the system/app folder that is installed as a system and can not be deleted

I wasted my time.
Good luck.

I devoted a while to check that I was right suggesting what I suggested.