Database Info

[ROM] Stock Donut (Android-1.6_r1) w/o Google Apps

I got bored so I decided to compile the latest Donut source.
Please make a Nandroid backup before you flash any of this! Just in case.
To add Google apps, check out the Google Stuffer, or similar scripts.
Features:
- Latest Donut source compiled for the HTC-Dream
- Stock (No Google apps whatsoever)
- Otherwise fully working (report bugs if you find any though)
Bugs
- Home key and Phone key not working (I'll try to get them to work)
Instructions
Code:
Unzip "Android-1.6_r1.zip"
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Only the system.img and boot.img is needed for the flashing procedure, but I included the other images just in case someone wants to take a look at them.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download
http://www.mediafire.com/?ntdmo0ulxdr
Enjoy~

Is this a root rom?

Great job now we proved to Google that we don't need them

This does not affect the recovery.img. So if you have Cyanogen's 1.4 recovery.img you will still have root.
Although you won't have apps like SuperUser, since it's Stock.

Good Job!
I want to try this, but I dont ADB (yet) can this be flashed thru recovery??
I used Tmobile contacts backup, so I can see if it will restore my contacts.
Chevy

chevycowboyusa said:
I want to try this, but I dont ADB (yet) can this be flashed thru recovery??
I used Tmobile contacts backup, so I can see if it will restore my contacts.
Chevy
Click to expand...
Click to collapse
Yes you can use the recovery console.
Move the files to the root of your sdcard first though.
Code:
mount sdcard [enter]
mount system [enter]
flash_image system /sdcard/system.img [enter]
flash_image boot /sdcard/boot.img [enter]
reboot

any way you could make this a update.zip. so we can just use cyan recovery to flash the zip?

Only things that I noticed to be not working are the home key and phone key.
I'll investigate further.

is this experimental

i feel i shouldnt be looking at this. its so naked

Yes this is experimental since it's compiled from a non-finalized source.
I know this ROM is naked. But since Google is taking action against the distribution of their closed-source apps, everyone has to release Stock ROMs now.

Bavilo said:
Yes this is experimental since it's compiled from a non-finalized source.
I know this ROM is naked. But since Google is taking action against the distribution of their closed-source apps, everyone has to release Stock ROMs now.
Click to expand...
Click to collapse
i know i know its just so different from what were used to seeing.. but this is the new standard now(unless google changes! ..) so might as well get used to it =/

this looks very interesting. i will probably wait to use this until i see that it works with a few of the scripts that are being developed.

DavidChill said:
this looks very interesting. i will probably wait to use this until i see that it works with a few of the scripts that are being developed.
Click to expand...
Click to collapse
I'm sure someone will create a script that's compatible with Donut. Since we have all of the proprietary files necessary.
Script makers, do your magic please ;D

Weird
I keep getting an invalid argument when trying to mount the system in recovery terminal.
i typed
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mmcblk0p2 /system
I seem to b having a brain fart.
Can i flash thru terminal emulator? edit: [I figured this one out.... NOPE!]
Chevy

It was VERY hard on my eyes to see an actual "bare bones" ROM already. Use to all the bells and whistles. I guess this is what we will have to work with right now till something is figured out. I really like this idea. Has ANYONE tested this yet with any google apps script. I really dont wanna try this until I know that we can get everything. I'll keep my eye on this though. Thanks for coming up with something so quickly

chevycowboyusa said:
I keep getting an invalid argument when trying to mount the system in recovery terminal.
i typed
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mmcblk0p2 /system
I seem to b having a brain fart.
Can i flash thru terminal emulator? edit: [I figured this one out.... NOPE!]
Chevy
Click to expand...
Click to collapse
To mount anything in the recovery console you just need to type "mount system" for instance...or mount sdcard.

wow.. this is the start of more freedom... Rebenga!!!!

Weird things
Wow.... Something must have been messed up....
I wiped and reflashed cm 4.1.11.1... then I went to recovery terminal (after booting)
was able to [mount system] [mount sdcard] flashed system and boot imgs.
Rebooted and went thru g1 screen, then black, and then another g1 screen, then automatically went back to recovery.... {Weird!!!}
any advice?

chevycowboyusa said:
Wow.... Something must have been messed up....
I wiped and reflashed cm 4.1.11.1... then I went to recovery terminal (after booting)
was able to [mount system] [mount sdcard] flashed system and boot imgs.
Rebooted and went thru g1 screen, then black, and then another g1 screen, then automatically went back to recovery.... {Weird!!!}
any advice?
Click to expand...
Click to collapse
Yea that is weird. I only tried flashing the images with fastboot, and erasing the userdata.
I'm working on fixing the home and phone key atm.

[Tool] Yaffs Explorer, made for Defy

Its a free Root Explorer without Ads and without network use.
When busybox and root modes are enabled, you can make dumps of your nand partitions and export Kernel and initramfs (Menu/Tools)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://market.android.com/details?id=fr.wdscript.yaffsexplorer
You can report here bug and feature requests...
Example : Dump and Rename The /cdrom partition (p17)
change dump file ext from .raw to .iso and you get your Windows drivers (MotoHelper 2.0.44 Driver 4.9.0 - 27 Jan 2011)
Version 1.9.9.8 attached

Awesome thanks, will def check this out.

useful tool

How can i dump the roofs?
can i restore it after backup?
Thank you.

This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)

Update v1.1 : You can create yaffs images now

Epsylon3 said:
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Click to expand...
Click to collapse
Do you know, how to dump and remount the rootfs?
Thank you.

in fact, i dont know... rootfs is mounted before android (initrd on some devices)

Epsylon3 said:
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Click to expand...
Click to collapse
Ok, thank you.

Ok, been using this for a while now; couple suggestions.
1. Copy feature needs to work more like Root Explorer.
---- So when you long-press and copy a file, two buttons popup, Paste and Cancel - Maybe you could even add a third to paste quickly to a favourites folder without leaving working directory ?
2. Be able to change text size of file browser. I have big fingers heh.
3. Have a Mount/Unmount button similar to the Mount R/W in Root Explorer.
--- I find I cant copy anything to anywhere, am I just missing something ?
4. Select multiple files, and copy, delete, zip, move . . . . . to favourites ?
5. Compress files or folders and save zip to a saved favourites without leaving working directory.
6. Load apk icons maybe; easier to find things sometimes.
7. Show favourites picker on program startup. I'm always working in the same directories.
A built in text editor with line numbers would be awesome. Maybe an sqlite editor addon too ?
I like what this looks like so far; I really like that you can see symlinks, the dropdown with recent paths, nandroid dumps of any partitions (nice), and the favorites are cool. Just hoping it can take over for root explorer.
Keep up the great work so far. Will be keeping on eye on this for sure.

Thanks for your report
First, i dont want to copy Root Explorer or all these slow and "3 lines" explorers... So no image/movies preview... This tool is focused on system files exploration
Apk icons maybe but not in my prority (filter by name is nice), line size : not for the moment (maybe a zoom or something later)
The multiselect on click is almost ready (for files), to keep folder navigation
the Mount/Unmount will be in tools menu later (in mounted devices menu) i need to make a new window for that... but that need work (and could make lot of reports from unknown devices, like chinese ones)
Compression.... yea hmm v2.0

Hm. I tried this, but it is a lot slower than Root Explorer. Perhaps this is because it shows a lot more objects, or due to it having a lot of features I do not directly associate with a program to manage files. Still, I can not say that having more competition is a bad thing, so keep up the good work

its because the tool use a terminal process to list folders, and a new one on each refresh... I think i can optimize that if i keep the shell process opened.
but Root enabled, its 5x slower (220ms instead of 40ms)... i think there could be a problem with superuser tool, will try to uninstall it to check...

johnw.xda said:
Do you know, how to dump and remount the rootfs?
Thank you.
Click to expand...
Click to collapse
to remount In fact like others :
Code:
mount -o rw,remount,relatime -t rootfs rootfs /
This feature will be available in some minutes (v1.3.0)
But to dump... you need to skip /proc /tmp and /sys

Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance

Its the next step yaffs extraction...
sorry, not for the moment (but soon)
just made an update v1.3.2 which really enhance exploration speed...

I hope you release it soon
Thanks

I can't Dump Partition. A circular thing shows up then it disapear and no text saying records in+out and that it finished (like in the screenshot). And there is no file on my SD card and yes I have plenty of space.
Tried several of the small 512k partitions and the Boot and Recovery partitions.
I'm running rooted froyo 3.4.2-155, few bloat APK's removed.

this feature uses busybox "dd" applet, try to set another busybox in setting window
you can search for them in other apps, do a search in /data/data/

Namiga said:
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Click to expand...
Click to collapse
Done... in v1.5.0 Single file or Folder for the moment... (file/folder context menu)
full extraction will be possible in next version... not linked

[HACK]LCD Density Changer That Doesn't Mess With Market

Hello All. Its me again. This time I bring you a long awaited solution. I'm sure you can remember changing your LCD density and then going to install an app which has always worked only to find that the market says its incompatible with your device. Well wait no more, This little hack will make you able to set any density and not be limited in the market.
EDIT: NOW A FLASHABLE ZIP
Process:
Download the zip and flash in recovery. (MOUNT SYSTEM FIRST)
Code:
/system/bin/density (YOUR DESIRED DENSITY)
reboot
Thats it. With every boot, the init.d script spawns the marketdensity script and it waits 45 seconds for boot to complete... Then it swaps the build.props so the market sees the correct one.
Have fun changing your density and not being limited.
Wanna help pay my bills???? Consider Donating
http://goo.gl/qQVRs
atc3030

Edited OP with new zip. Now flashable.

It didn't take when I flashed it. I'm using twrp recovery. does this support edify?
I could just put those files in there place with root explorer, right? What permissions do they need?
EDIT: I just realized I forgot to mount system. Will try again

Yes you can do root explorer. Idk the perms they need through that but if you use chmod in terminal, the perms are 775
Sent from my DROID2 GLOBAL using Tapatalk

It worked this time mounting system like I should have, lol.
But where do I enter the density? In place of the $1?

No. You run the script in terminal
Sent from my DROID2 GLOBAL using Tapatalk

I'm surprised more people aren't taking an interest in this. I understood this was a problem
Sent from my DROID2 GLOBAL using Tapatalk

atc3030 said:
I'm surprised more people aren't taking an interest in this. I understood this was a problem
Sent from my DROID2 GLOBAL using Tapatalk
Click to expand...
Click to collapse
I'm interested This has been a thorn in my side for a while now...
Gonna try this out
m.

No Joy.
Out of the box, the density script wasn't running, failing on the mount command.
I made a few changes to get it to run:
Code:
#!/system/bin/sh
echo "Setting Density to $1"
# mount only runs as root, so execute 'su' before 'mount'
su
# mount was failing without specifying the device
mount -o remount,rw /dev/block/mmcblk0p24 /system
sed "s/^ro\.sf\.lcd_density=.*/ro.sf.lcd_density=$1/" /system/build.prop > /system/.build.prop.hack
# not sure if this next mount is needed, but it makes sense to me to remount as ro once we've made the changes
mount -o remount,ro /dev/block/mmcblk0p24 /system
exit
After those changes, I was finally able to run density, and it does everything its supposed to, ie it creates /system/.build.prop.hack and the density is set to what I want there.
However, when I reboot, the changes are not applied. I'm guessing that the 98density init.d script is not being called.
I'm running a Telus SGH-T989 with Juggernaut 4.1 ROM.
Any thoughts on how to get this last piece to fall into place?
Clever idea btw, we really need something like this
m.

It works for me. I will work on it when I get home
Sent from my DROID2 GLOBAL using Tapatalk

I wanna try this out when I get home. awesome awesome awesome
Question: the 98density file in init.d is it suppose to be 755? cause all the other files in init.d are like so
I'm getting an sed:command not found. To fix it I had to write:
Busybox sed etc ....
this also needs needs SU
--EDIT-- just noticed a user above me had similar tweaks I wrote below (now striked out).
BTW for the mounting.. I think it will have to depend on your device..I got mine to mount by
mount -o rw,remount /dev/block/mmcblk0p24 /system
which I believe is different per device. I'll try the script again by changing that part of the code
After all the changes and no error. after reboot nothing changed.
very excited though

I am going to work on the scripts when I get home. They are on that computer.
Sent from my DROID2 GLOBAL using Tapatalk

emmdub said:
No Joy.
Out of the box, the density script wasn't running, failing on the mount command.
I made a few changes to get it to run:
Code:
#!/system/bin/sh
echo "Setting Density to $1"
# mount only runs as root, so execute 'su' before 'mount'
su
# mount was failing without specifying the device
mount -o remount,rw /dev/block/mmcblk0p24 /system
sed "s/^ro\.sf\.lcd_density=.*/ro.sf.lcd_density=$1/" /system/build.prop > /system/.build.prop.hack
# not sure if this next mount is needed, but it makes sense to me to remount as ro once we've made the changes
mount -o remount,ro /dev/block/mmcblk0p24 /system
exit
After those changes, I was finally able to run density, and it does everything its supposed to, ie it creates /system/.build.prop.hack and the density is set to what I want there.
However, when I reboot, the changes are not applied. I'm guessing that the 98density init.d script is not being called.
I'm running a Telus SGH-T989 with Juggernaut 4.1 ROM.
Any thoughts on how to get this last piece to fall into place?
Clever idea btw, we really need something like this
m.
Click to expand...
Click to collapse
Not all devices use the same memory block as your devices. therefore, the way you are mounting system will not work. I am working on fixing this now

Great idea but the hacked market works great.
Sent from my Incredible 2 using Tapatalk

Yeah, my setting wasn't applied after I ran it either but im not sure if it's the same problem as emmdub. I do see that it creates the .buildprop hack file. But i'm not sure why the setting isn't sticking.

I noticed that even with the hacked market sometimes I have to clear data/ cache because sometimes it kind of reverts itself.
Sent from my Incredible 2 using Tapatalk

I would like this to work, but I don't think this solution is permanent for a few reasons:
1. The market does not read the build.prop file directly. It uses the prop values that are stored in memory, and retrieved by the DisplayMetrics class. That is why after changing your density you have to reboot to get the market to recognize your new density.
2. The market does not use your device density to check compatibility. The check is server side. The market sends your density to their servers along with other info about your device when you accept their terms and services (and sometimes periodically, but not every time you use it). It registers your device info with your deviceID, and determines compatibility that way. Its how the website market knows which devices you have and if they are compatible.
Note that I am not an expert, but I have written an app to change lcd density, as well as decompiled the market and studied it a bit, so i am pretty knowledgeable in the subject.

disconnecktie said:
I noticed that even with the hacked market sometimes I have to clear data/ cache because sometimes it kind of reverts itself.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
got a link for the hacked market?
edit: i got it, thanks
http://forum.xda-developers.com/showpost.php?p=20623581&postcount=10

http://forum.xda-developers.com/showthread.php?t=1434037
Here ya go. Just copy the original vending apk from data app to somewhere safe take the new market put in the data/app folder and rename it to vending and change the permissions to
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did not think of that. I'm going too look into the memory thing right now.
Sent from my DROID2 GLOBAL using Tapatalk

[Guide][Win-Linux-Script] The Easiest Ways For Getting All Device's Mounting Points

For Non-Rooted Devices and Rooted Devices​
Here is a summary on how to get mounting points without rooting or extracting recovery.img.
The different procedures only needs to have adb shell or terminal emulator.. I will explain using adb shell through pc.
After establishing adb connection to your device, you can choose any of the following procedures to get your mounting points:
#1
Code:
adb shell
cat /proc/mounts
This will give you info about device, the mount point, the file system type, and how it is mounted.
Limitation: This method, however, will not give you all mounting points.!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#2
Code:
adb shell
cat /proc/partitions
This is more neat, it will give you info about ALL dev blocks and their names (not the familiar name!), and block size
Limitation: Needs from you to figure out which block belong to which partition name.!!
#3
Code:
adb shell
ls -al /dev/block/platform/[B][COLOR="Blue"]dw_mmc[/COLOR][/B]/by-name
This one is the command that I like on non-rooted device..! It will give you info about the dev block names WITH their familiar names (i.e, boot, recovery, system... etc) :laugh:
This command is not universal between devices, and you will need to gather its pieces (/dev/block/platform/dw_mmc/by-name).
How?
- In your device, use any explorer that can get you to the device root (personally I use ES Explorer, by pressing on "/" on navigation bar).
- Go to "/dev/block/platform/" folder
- Here you will see some files and folders, we need to open folders and search for the folder called "by-name" inside one of them; in my situation it was "dw_mmc" folder which has the folder "by-name" inside it.
- At the end, my targeted piece info will be (/dev/block/platform/dw_mmc/by-name)
- Now open adb shell and put the command..
***​
For Rooted Devices Only​
There are different ways to get mounting points in rooted device (including the non-rooted devices way), but the easiest way to get all device mounting points is to push parted binary to /system/bin folder and run it.
Code:
adb remount
adb shell "su" "" "mount -o remount,rw /system"
adb push parted /system/bin/parted
adb shell
chmod 755 /system/bin/parted
parted /dev/block/[B][COLOR="Blue"]mmcblk0[/COLOR][/B]
print
Here, your mounting points will start with /dev/block/mmcblk0p* where (*) is the number shown in the table above for each partition.
example:
The preload partition mounting point will be mmcblk0p12
The modem partition mounting point will be mmcblk0p8
The system partition mounting point will be mmcblk0p9
The Kernel partition mounting point will be mmcblk0p5
and so on
Don't forget to "quit" the parted action after grasping your device mounting points.
N.B:
- You may need to run first:
Code:
adb shell
cat /proc/partitions
to know what is the initial name for your device partition.. In the example above, it was mmcblk0.
- Also to be able to do adb push to /system partition, you will need adbd insecure installed in your device (Check this thread for that app), or to push it manually by any root explorer and then fix permissions to 755.
***​
Pre-made Scripts​Windows users
Here is a script I wrote for both non-rooted (way #3) and rooted devices for windows users.
Just extract the content in any folder and run the script that you want ("Non-Rooted and Rooted.cmd" or "Rooted Only.cmd")
Don't forget to install adbd insecure in rooted device in order to use Rooted Only.cmd script.
Linux users
As same, here is a script I wrote for both non-rooted (way #3) and rooted devices for linux users.
Just extract the content in any folder and run the script that you want ("non-rooted" or "rooted")
Don't forget to install adbd insecure in rooted device in order to use rooted script.
N.B: The linux scripts are tested with cygwin emulator on windows machine.. So needs feedback on actual machine.!!
Cheers

reserved

Thank you, I go to try.

Linux script added to OP

Thanks
Thank you You are the best one

Mount system as rw on Android 10 with Magisk 20.4

I am using Magisk 20.4 and trying to mount /system on a Google Pixel running Android 10.
I have tried using:
Code:
adb shell su -c mount -o rw,remount /system
that gives: me
mount: '/system' not in /proc/mounts
Click to expand...
Click to collapse
The following also do not work:
Code:
adb shell su -c mount -o rw,remount /
'/dev/root' is read-only
Click to expand...
Click to collapse
Code:
adb shell su -c mount -o rw,remount /sbin/.magisk/mirror/system_root
'/sbin/.magisk/block/system_root' is read-only
Click to expand...
Click to collapse
I was also curious whether stuff in /sbin/.magisk/rootdir/system/ can actually override stuff in /system/ but that doesn't seem to be the case..
Has anyone managed to mount /system on Android 10? Is this issue specific to Google Pixel?
Cheers,
Paschalis

Its due to EXT4 dedup filesystem (it's not writable).
This was pointed out by magisk developer john wu, more info: https://mobile.twitter.com/topjohnwu/status/1170404631865778177

So it's impossible? Even with TWRP?

Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.

The only way to make changes to the /system partition is to make a Magisk module that mounts the files you modified instead of the original ones.

Paschalis said:
Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.
Click to expand...
Click to collapse
Well I need to mount because of Link2sd. Is there any way to do it?

jcruzcruz35 said:
Well I need to mount because of Link2sd. Is there any way to do it?
Click to expand...
Click to collapse
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.

JJcoder said:
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.
Click to expand...
Click to collapse
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?

jcruzcruz35 said:
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?
Click to expand...
Click to collapse
I'm sure eventually there will either be a universal Module, Or a way to resize the partition and change the file system to make it writable.

JJcoder said:
...Or a way to resize the partition and change the file system to make it writable.
Click to expand...
Click to collapse
Resized works, but how to change the file system to make it writable?

vagyula said:
Resized works, but how to change the file system to make it writable?
Click to expand...
Click to collapse
How did you resize it?

Code:
$ su
# mount --remount / -w
ONLY makes effert to terminal, which means other apps like Solid Explorer, Root Explorer etc are still r/o. Some roms(Pixel Experience tested, including stock) are not working.

hardplastic said:
Code:
$ su
# mount --remount / -w
Only works in terminal
Click to expand...
Click to collapse
It doesn't work on Android 10, you will just get the error:
Code:
'/dev/root' is read only

JJcoder said:
It doesn't work on Android 10, you will just get the error:
Code:
mount: '/dev/root' not user user mountable in fstab
Click to expand...
Click to collapse
Reboot your device and try again, it works both two of my devices in Android 10

hardplastic said:
Reboot your device and try again, it works both two of my devices in Android 10
Click to expand...
Click to collapse
Nope, Same error bcuz it is locked at read only.

JJcoder said:
Nope, Same error bcuz it is locked at read only.
Click to expand...
Click to collapse
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .

hardplastic said:
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .
Click to expand...
Click to collapse
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
I have no idea how u got it to work, I would like to see proof..

JJcoder said:
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you would have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
Click to expand...
Click to collapse
Then how do you explain that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hardplastic said:
Then how do you explain that?
Click to expand...
Click to collapse
Let me see that u are on stock Android 10

JJcoder said:
Let me see that u are on stock Android 10
Click to expand...
Click to collapse