Database Info

Flash custom files or use adb?

Hi, this is my first time posting on this site and I apologizes if this is in the wrong place. I just recently rooted my evo and was wondering when I want to apply a customization such as a new notification bar how do I know to use either flashing the file from the sd card or to run a command in adb? Is there an important difference, or can either be used? Thanks in advance for the help.

rafroehlich2 said:
Hi, this is my first time posting on this site and I apologizes if this is in the wrong place. I just recently rooted my evo and was wondering when I want to apply a customization such as a new notification bar how do I know to use either flashing the file from the sd card or to run a command in adb? Is there an important difference, or can either be used? Thanks in advance for the help.
Click to expand...
Click to collapse
Most files can be flashed, if they are in a .zip form, you should be okay. However for things like the bootscreens, the recommended method is to use ADB and push the bootanimation.zip file to the specified folder on the phone. However, this has been extremely simplified by user-made tools here on the EVO forums, not many people like using ADB (don't know why)... so there are tools to make it easier for people.
Usually the person that is distributing the file should say whether you need to flash or use ADB commands, just read the OP's post.

Thanks so much for your help.

rafroehlich2 said:
Thanks so much for your help.
Click to expand...
Click to collapse
Sure, no problem!

pseudoremora said:
Most files can be flashed, if they are in a .zip form, you should be okay. However for things like the bootscreens, the recommended method is to use ADB and push the bootanimation.zip file to the specified folder on the phone. However, this has been extremely simplified by user-made tools here on the EVO forums, not many people like using ADB (don't know why)... so there are tools to make it easier for people.
Usually the person that is distributing the file should say whether you need to flash or use ADB commands, just read the OP's post.
Click to expand...
Click to collapse
If I use the flashing method will the files be moved to the correct system folder or will it just deposit it in the ROM? When you use adb you specify the target, if I'm not mistaken. I just don't want my system to get cluttered with random files. Sorry if this isn't worded well.

rafroehlich2 said:
If I use the flashing method will the files be moved to the correct system folder or will it just deposit it in the ROM? When you use adb you specify the target, if I'm not mistaken. I just don't want my system to get cluttered with random files. Sorry if this isn't worded well.
Click to expand...
Click to collapse
When using ADB, the system won't get "cluttered"... mainly because when you're are using the adb push (copy) command, you will be overwriting the file that is currently residing on your phone.
For example, if I wanted to replace my bootanimation -- I would type:
Code:
adb push bootanimation.zip /system/customize/resource
This would copy the new bootanimation.zip over to the directory being specified (/system/customize/resource -- where the bootanimation resides), upon copying, it explicitly overwrites any file/folder with the name "bootanimation" -- unless you set a parameter when typing the command to ask you if it should overwrite. You don't need to worry about this though, almost always you'll overwrite the files.
As long as you push (copy) any and all files to its correct directory, nothing should ever get cluttered and if it does, then you can always remove it just as easily.

pseudoremora said:
When using ADB, the system won't get "cluttered"... mainly because when you're are using the adb push (copy) command, you will be overwriting the file that is currently residing on your phone.
For example, if I wanted to replace my bootanimation -- I would type:
Code:
adb push bootanimation.zip /system/customize/resource
This would copy the new bootanimation.zip over to the directory being specified (/system/customize/resource -- where the bootanimation resides), upon copying, it explicitly overwrites any file/folder with the name "bootanimation" -- unless you set a parameter when typing the command to ask you if it should overwrite. You don't need to worry about this though, almost always you'll overwrite the files.
As long as you push (copy) any and all files to its correct directory, nothing should ever get cluttered and if it does, then you can always remove it just as easily.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm new to this and any time I see command line I get hesitant. Thanks again for the thorough answer.

rafroehlich2 said:
Thanks for taking the time to answer. I'm new to this and any time I see command line I get hesitant. Thanks again for the thorough answer.
Click to expand...
Click to collapse
Yup, no problem. I try to usually give a detailed answer, as I'm sure not everyone will understand vague answers.

pseudoremora said:
Yup, no problem. I try to usually give a detailed answer, as I'm sure not everyone will understand vague answers.
Click to expand...
Click to collapse
Since you seem to be knowledgeable what is the difference between flashing a rom by its name.zip as opposed to renaming it update.zip? Does the former start new and the latter maintain all apps/settings?
Sent from my PC36100

rafroehlich2 said:
Since you seem to be knowledgeable what is the difference between flashing a rom by its name.zip as opposed to renaming it update.zip? Does the former start new and the latter maintain all apps/settings?
Sent from my PC36100
Click to expand...
Click to collapse
No difference.
The naming conventions don't mean anything really. There used to be a time when all packages had to be called "update.zip", but the Devs that built the recoveries made it so you could name the .zip files whatever you wanted.
You'll see ROM's/theme's/etc with fancy names -- that's just so its easier for the end user to identify what he/she is actually going to flash.
When I say "update.zip", I just mean that the file can be flashed via recovery and won't require command line/terminal/ADB.
However, there are certain files that will always have a static name (bootanimation.zip) -- that can't change because the phone is programmed to look for that specified file. So whenever someone uploads a bootanimation and calls it: "Nexus-bootanimation.zip" --- this should be renamed to bootanimation before adb pushing or flashing to its specified directory.

Now I understand the idea behind flashing a radio, however I don't understand flashing a kernel. How do I know when to do this and do the risks of radio apply to the kernel? Also, are there any other major components that I'll eventually have to flash? Thanks for answering my many questions.
Sent from my PC36100

rafroehlich2 said:
Now I understand the idea behind flashing a radio, however I don't understand flashing a kernel. How do I know when to do this and do the risks of radio apply to the kernel? Also, are there any other major components that I'll eventually have to flash? Thanks for answering my many questions.
Sent from my PC36100
Click to expand...
Click to collapse
There are risks with both.
Flashing a kernel or radio has the potential to brick your phone. The radio is used for controlling all the "wireless" functions (3G, 4G, x1 connections (texting/calling)) -- pretty much anytime the phone connects to the Sprint towers, the radio is playing its part. So if you flash it incorrectly; the consequences are obvious.
The kernel is the heart of the Android. The kernel itself is actually Linux. Android is built upon Linux, so pretty much Google took the already existing Linux kernel and built Android on top of it (the UI, the apps, etc) and made Android into a Mobile OS, which can run on virtually any platform or device.
How do you know? You don't -- it's a matter of wanting to be curious enough to test. Some devs will put out kernels that overclock your device, others will add different features (screen fixes, loopback interface, underclocking, etc). The kernel controls all the hardware on the phone and how everything functions -- so when devs mess with source code, they are essentially making the hardware function differently for your device.
Some of the major components? -- The biggest ones so far are the wireless driver and 4G driver. When the EVO came out -- the battery life wasn't great; but after the new update (1.47 and the accompanying radio's); battery life on the device have improved significantly and people have experience better WiFi reception and such.
Hope that helps.

pseudoremora said:
There are risks with both.
Flashing a kernel or radio has the potential to brick your phone. The radio is used for controlling all the "wireless" functions (3G, 4G, x1 connections (texting/calling)) -- pretty much anytime the phone connects to the Sprint towers, the radio is playing its part. So if you flash it incorrectly; the consequences are obvious.
The kernel is the heart of the Android. The kernel itself is actually Linux. Android is built upon Linux, so pretty much Google took the already existing Linux kernel and built Android on top of it (the UI, the apps, etc) and made Android into a Mobile OS, which can run on virtually any platform or device.
How do you know? You don't -- it's a matter of wanting to be curious enough to test. Some devs will put out kernels that overclock your device, others will add different features (screen fixes, loopback interface, underclocking, etc). The kernel controls all the hardware on the phone and how everything functions -- so when devs mess with source code, they are essentially making the hardware function differently for your device.
Some of the major components? -- The biggest ones so far are the wireless driver and 4G driver. When the EVO came out -- the battery life wasn't great; but after the new update (1.47 and the accompanying radio's); battery life on the device have improved significantly and people have experience better WiFi reception and such.
Hope that helps.
Click to expand...
Click to collapse
That does help. This is my first time with android and my first time attempting to actually mess with it.

rafroehlich2 said:
That does help. This is my first time with android and my first time attempting to actually mess with it.
Click to expand...
Click to collapse
There will be a lot more "firsts", believe me. Some things will be harder than others; but if you stick with it and actually take the time to learn, you'll realize that working Android can be a helluva lot of fun and unbelievably addictive!

pseudoremora said:
There will be a lot more "firsts", believe me. Some things will be harder than others; but if you stick with it and actually take the time to learn, you'll realize that working Android can be a helluva lot of fun and unbelievably addictive!
Click to expand...
Click to collapse
The bug has already bit me. I appreciate the help. It's nice to know there is a community to get good answers from when needed.
Sent from my PC36100

pseudoremora said:
There will be a lot more "firsts", believe me. Some things will be harder than others; but if you stick with it and actually take the time to learn, you'll realize that working Android can be a helluva lot of fun and unbelievably addictive!
Click to expand...
Click to collapse
Instead of posting a new thread perhaps you can help me on this. When I attempt to use adb to remove a bundled app.
adb shell
cd /system/app
ls
rm app.apk
I get Disk space read only. I have full root and NAND I assume. I used the OTA method and am able to flash custom ROMs. I am using the rooted stock 1.47.651.1

rafroehlich2 said:
Instead of posting a new thread perhaps you can help me on this. When I attempt to use adb to remove a bundled app.
adb shell
cd /system/app
ls
rm app.apk
I get Disk space read only. I have full root and NAND I assume. I used the OTA method and am able to flash custom ROMs. I am using the rooted stock 1.47.651.1
Click to expand...
Click to collapse
When a "read-only" message is returned, it usually means that you don't have RW (read-write access), to circumvent this, run this command:
Code:
adb remount -- Should always be run if you plan on changing something that requires RW access
Then:
adb shell
cd /system/app
ls
rm app.apk
If for some reason you get a error message with adb remount (most likely due to permissions), then you'll need to use the full "remount" command, for that, run:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Hope that helps.

pseudoremora said:
When a "read-only" message is returned, it usually means that you don't have RW (read-write access), to circumvent this, run this command:
Code:
adb remount -- Should always be run if you plan on changing something that requires RW access
Then:
adb shell
cd /system/app
ls
rm app.apk
If for some reason you get a error message with adb remount (most likely due to permissions), then you'll need to use the full "remount" command, for that, run:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Hope that helps.
Click to expand...
Click to collapse
I tried your method, but I get another error. It looks like:
Code:
mac-mini:~ rafroehlich2$ adb remount
remount failed: Operation not permitted
mac-mini:~ rafroehlich2$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: exec /usr/sbin/mount_yaffs2 for /System: No such file or directory
Is there a preventable reason
Code:
adb remount
fails? Thanks for the help.

rafroehlich2 said:
I tried your method, but I get another error. It looks like:
Code:
mac-mini:~ rafroehlich2$ adb remount
remount failed: Operation not permitted
mac-mini:~ rafroehlich2$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: exec /usr/sbin/mount_yaffs2 for /System: No such file or directory
Is there a preventable reason
Code:
adb remount
fails? Thanks for the help.
Click to expand...
Click to collapse
I figured you might have trouble with the ADB remount -- again, this is usually due to permissions. For testing purposes, try booting into recovery and then issuing the adb remount command.
In regards to the full remount command -- I'm wondering if you have busybox (it contains all the Linux command line tools) so that you can run the above commands.
Can you issue and then paste the output back here?:
Code:
cat /proc/mounts
Also, run this:
Code:
adb shell
cd /system/xbin
ls
If you can see a huge list of files -- then that means you do in fact have Busybox installed.
Also, what ROM are you running?

pseudoremora said:
I figured you might have trouble with the ADB remount -- again, this is usually due to permissions. For testing purposes, try booting into recovery and then issuing the adb remount command.
In regards to the full remount command -- I'm wondering if you have busybox (it contains all the Linux command line tools) so that you can run the above commands.
Can you issue and then paste the output back here?:
Code:
cat /proc/mounts
Also, run this:
Code:
adb shell
cd /system/xbin
ls
If you can see a huge list of files -- then that means you do in fact have Busybox installed.
Also, what ROM are you running?
Click to expand...
Click to collapse
After
Code:
cat /proc/mounts
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Code:
mac-mini:~ rafroehlich2$ adb shell
$ cd /system/xbin
$ ls
wireless_modem
dnsmasq
su
I download the BusyBox app to keep it up to date and also installed it through the "problems" section on titanium backup. However, that's all I got.
The ROM I am using is the fully rooted stock RUU. I'd post a link, but am not sure if I'm allowed to yet. It is the one posted by whitslack.

Experiments with GB Kernel

I'm opening this thread to share information about experiments with the new GB kernel with other devs/contributors of M2 community.
Based on the idea of dual-booting I managed today to get my phone running using system directly from an image on /data.
The base system installed is boot/devtree/recovery from signed GB Leak with Mostly Blurless ROM. I created an image from this same system with dd if=/dev/block/system of=/data/blurless.img.
I then edited bootmenu 2nd-int init.rc to:
- comment lines that mount /data and /system
- added the following lines:
Code:
mount ext3 [email protected] /data nosuid nodev noatime nodiratime barrier=0
mount ext3 [email protected]/data/blurless.img /system noatime nodiratime barrier=1
In init.mapphone_umts.rc:
- commented lines that remounts /system
- added following line:
Code:
mount ext3 [email protected]/data/blurless-system.img /system ro noatime nodiratime remount
In /system/bootmenu/scripts/2nd-init.sh:
Code:
#!/sbin/sh
######## BootMenu Script v0.8.6
######## Execute [2nd-init] Menu
export PATH=/sbin:/system/xbin:/system/bin
######## Main Script
rm /*.rc
cp -r -f /system/bootmenu/2nd-init/* /
cp -fp /system/bootmenu/binary/2nd-init /sbin/
chmod 755 /*.rc
#chmod 755 /system/bootmenu/binary/2nd-init
chmod 755 /sbin/2nd-init
umount /acct
umount /mnt/asec
umount /dev/cpuctl
umount /dev/pts
umount /mnt/obb
## sbin cleanup
## move post_bootmenu.sh
#/system/bootmenu/binary/2nd-init
umount -l /system
/sbin/2nd-init
exit
Works fine and system is really mounted on loopback device after boot. Now I want to mount on init.rc /data as a bind fs. Does anyone know how to do that as a init.rc script command?
As a test I tried
mount ext3 [email protected]/data/system /mnt/data
but it didn't work

Ok. I found a way to do that mounting data first as /mnt/data then mounting loopback system. with system ready I can mount bind /data with the following command:
exec /system/xbin/busybox mount -obind /mnt/data/rom/blurless-data /data
I'd like better to mount this with a native init command if anybody knows how to, but for the moment this will do.

It doesn't work because bind is not supported by the original mount command ?
Anyway, may be you can do symlink with the data directory .
But good job allowing us to test img system without breaking existing one !

Trying now to boot MIUI on a second system image I get the following error:
08-26 21:06:40.773 2971 2979 E FramebufferNativeWindow: couldn't open framebuffer HAL (No such device)
I'm not sure if this error was caused by kernel incompatibility or by some special file libsurfaceflinger could not find. Doing strings | grep on libsurfaceflinger.so from miui I could find this references:
/dev/tty0
/sys/android_power/wait_for_fb_sleep
/sys/android_power/wait_for_fb_wake
/sys/class/graphics/fbcon
/sys/power/wait_for_fb_sleep
/sys/power/wait_for_fb_wake
Maybe we can map old devices to new devices (ln -s) at run time and make it work but I don't know exactly how to map them.
Edit: I am unable to create anything in /sys, even mounting it as RW. Does n1 know what I should do?

Yeah! You rule!

r2beta0 said:
Trying now to boot MIUI on a second system image I get the following error:
08-26 21:06:40.773 2971 2979 E FramebufferNativeWindow: couldn't open framebuffer HAL (No such device)
I'm not sure if this error was caused by kernel incompatibility or by some special file libsurfaceflinger could not find. Doing strings | grep on libsurfaceflinger.so from miui I could find this references:
/dev/tty0
/sys/android_power/wait_for_fb_sleep
/sys/android_power/wait_for_fb_wake
/sys/class/graphics/fbcon
/sys/power/wait_for_fb_sleep
/sys/power/wait_for_fb_wake
Maybe we can map old devices to new devices (ln -s) at run time and make it work but I don't know exactly how to map them.
Edit: I am unable to create anything in /sys, even mounting it as RW. Does n1 know what I should do?
Click to expand...
Click to collapse
Ok. for your system find all it needs, you have to "bind" (by anyway i think) /proc and /sys . Like a normal linux when you do a chroot. I don't know the exact order of execution of your script, but before anything else, you must have proper /proc , /sys ,/dev . For example, here it what we need in to do in linux,
#!/bin/bash
mount --bind /dev /répertoire-vers-votre-chroot/dev
mount --bind /dev/pts /répertoire-vers-votre-chroot/dev/pts
mount --bind /dev/shm /répertoire-vers-votre-chroot/dev/shm
mount -t proc none /répertoire-vers-votre-chroot/proc
mount -t sysfs none /répertoire-vers-votre-chroot/sys
As you can't bind them with mount, try the symlink , it might work (i dont see why not) . These directories are created by the kernel , maybe there are other in android , i don't know.
Try that and let me know , it should do the trick !
Edit: i read too fast! It couldnt be that, as you dont change / .

r2beta0 said:
Trying now to boot MIUI on a second system image I get the following error:
08-26 21:06:40.773 2971 2979 E FramebufferNativeWindow: couldn't open framebuffer HAL (No such device)
I'm not sure if this error was caused by kernel incompatibility or by some special file libsurfaceflinger could not find. Doing strings | grep on libsurfaceflinger.so from miui I could find this references:
/dev/tty0
/sys/android_power/wait_for_fb_sleep
/sys/android_power/wait_for_fb_wake
/sys/class/graphics/fbcon
/sys/power/wait_for_fb_sleep
/sys/power/wait_for_fb_wake
Maybe we can map old devices to new devices (ln -s) at run time and make it work but I don't know exactly how to map them.
Edit: I am unable to create anything in /sys, even mounting it as RW. Does n1 know what I should do?
Click to expand...
Click to collapse
Isn't MIUI and CM7 running on top of froyo kernel/dev tree?
I remember I got the same HAL issue when I tried to run unsigned GB on froyo kernel. I assume trying to run froyo based rom's on 2.3.4 kernel will show the same issues.

n3ptun3 said:
Isn't MIUI and CM7 running on top of froyo kernel/dev tree?
I remember I got the same HAL issue when I tried to run unsigned GB on froyo kernel. I assume trying to run froyo based rom's on 2.3.4 kernel will show the same issues.
Click to expand...
Click to collapse
Hm... maybe you're right. The new nightly CM from Defy should work with GB kernel I think.
Sent from my Milestone 2 XDA App

dangpzanco said:
Hm... maybe you're right. The new nightly CM from Defy should work with GB kernel I think.
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
I wouldn't bet on it. 2nd-init might be GB ready, but Defy's CM7 is still built over a froyo base. If I have time this weekend I'll experiment on D2G CM7 with GB base.

Just let GB kernel boot CM7. ch-2.2 kernel suck in touch screen.

n3ptun3 said:
I wouldn't bet on it. 2nd-init might be GB ready, but Defy's CM7 is still built over a froyo base. If I have time this weekend I'll experiment on D2G CM7 with GB base.
Click to expand...
Click to collapse
I can't boot CM7 0826 nightly bulid with both ch-2.2.2/GB kernels. Anyone know why? The author has changed the 2nd-init?
Edit: I think I know why. The author delete 2nd-init in /binary. So we need to change the boot method to 2nd-boot. GB kernel isn't suported yet.

Endless7 said:
Edit: I think I know why. The author delete 2nd-init in /binary. So we need to change the boot method to 2nd-boot. GB kernel isn't suported yet.
Click to expand...
Click to collapse
That seems to be a mistake and was fixed in 3e3c820adecf812e3dfea872a184f5f428fd4fbc (Allow 2nd-init support with bootmenu, which is stored in system image). It was caused by heavy restructuring of the motorola common boot-code in the CM7 repository. Just copy my 2nd-init into the binary directory, and you should be fine.

pat972 said:
Ok. for your system find all it needs, you have to "bind" (by anyway i think) /proc and /sys . Like a normal linux when you do a chroot. I don't know the exact order of execution of your script, but before anything else, you must have proper /proc , /sys ,/dev . For example, here it what we need in to do in linux,
#!/bin/bash
mount --bind /dev /répertoire-vers-votre-chroot/dev
mount --bind /dev/pts /répertoire-vers-votre-chroot/dev/pts
mount --bind /dev/shm /répertoire-vers-votre-chroot/dev/shm
mount -t proc none /répertoire-vers-votre-chroot/proc
mount -t sysfs none /répertoire-vers-votre-chroot/sys
As you can't bind them with mount, try the symlink , it might work (i dont see why not) . These directories are created by the kernel , maybe there are other in android , i don't know.
Try that and let me know , it should do the trick !
Edit: i read too fast! It couldnt be that, as you dont change / .
Click to expand...
Click to collapse
It's a good idea, as I can bind filesystems using busybox mount. It needs just some engineering into 2nd-init script like copying busybox to /sbin and forcing umount of /dev /proc and /sys, but it can be done.
How do I clone /sys to some other folder like /data/sys? I tried with 'cp -a' but it doesn't work fine. As I see I have to clone /sys and make some symlinks on this clone. Then I bind it with original /sys on init.rc. Is that right?

r2beta0 said:
It's a good idea, as I can bind filesystems using busybox mount. It needs just some engineering into 2nd-init script like copying busybox to /sbin and forcing umount of /dev /proc and /sys, but it can be done.
How do I clone /sys to some other folder like /data/sys? I tried with 'cp -a' but it doesn't work fine. As I see I have to clone /sys and make some symlinks on this clone. Then I bind it with original /sys on init.rc. Is that right?
Click to expand...
Click to collapse
I would not unmount /dev /proc and /sys, they are closely related to kernel init, in linux desktop it the first thing rc.sysinit does.
I was thinking more to something like "ln -s /sys/ /data/sys" , and one other solution i've just tested, is to do a "mount -n -t sysfs sys /data/sys -o nosuid,noexec,nodev" ! The difference for me is that with the mount command you'll not be able to umount /data/sys until reboot ! With the symlink you can just rm it when you finish.
The bind option is usefull cause when you do a chroot, you don't have access the other part of the system , so i'm not sure the symlink method work in that case. i'll ask and tell you.
Edit : I confirm It's that well about bind and chroot. and it seems to me , you can't create file in /sys , the kernel create them and you can read/change values. If you create one, it will not be taken in account by the kernel.
Also can you light up my lantern, which script in /system is called after the 2nd-init to launch the MIUI ?

pat972 said:
I would not unmount /dev /proc and /sys, they are closely related to kernel init, in linux desktop it the first thing rc.sysinit does.
I was thinking more to something like "ln -s /sys/ /data/sys" , and one other solution i've just tested, is to do a "mount -n -t sysfs sys /data/sys -o nosuid,noexec,nodev" ! The difference for me is that with the mount command you'll not be able to umount /data/sys until reboot ! With the symlink you can just rm it when you finish.
The bind option is usefull cause when you do a chroot, you don't have access the other part of the system , so i'm not sure the symlink method work in that case. i'll ask and tell you.
Edit : I confirm It's that well about bind and chroot. and it seems to me , you can't create file in /sys , the kernel create them and you can read/change values. If you create one, it will not be taken in account by the kernel.
Also can you light up my lantern, which script in /system is called after the 2nd-init to launch the MIUI ?
Click to expand...
Click to collapse
When you use bootmenu to start 2nd-init it will run a script called /system/bootmenu/script/2nd-init.sh. The last line of this script is 2nd-init binary itself. When you call 2nd-init binary it forks init on top of itself causing something like a hot restart. So, what 2nd-init script does is remount / as RW and copy new init.rc, init.mpaphone_umts.rc and init binary to /. Then it calls 2nd-init binary in order to use your custom files instead of stock ones. You can do anything you like on init.rc, as I did to boot MIUI from a loopback device. Unfortunately MIUI was compiled for froyo kernel and can't find some devices it needs to work. Thats why I need to create symlinks inside /sys and I think I already found a way to do that. Will test and explain that later.

Ok thanks !

Even with the new symlinks the system is unable to boot. As I suspected it is far more complicated then just adding links to /sys, too bad. I think the only way we have to boot multi-systems with multi-kernels (like miui on froyo and stock on gb) will be using kexec hack. n1 know if some group already found a way to run kexec on milestone or milestone2?

You can't rebuilt miui over a generic 2.6.32 kernel ? Well i'm a total newb in rom dev, i assume the officiel ginger from google won't work, you must have some specific hardware stuff ! For kexec it seems they have some driver problem, but since you want to boot the moto kernel may be it'll be easier !

pat972 said:
You can't rebuilt miui over a generic 2.6.32 kernel ? Well i'm a total newb in rom dev, i assume the officiel ginger from google won't work, you must have some specific hardware stuff ! For kexec it seems they have some driver problem, but since you want to boot the moto kernel may be it'll be easier !
Click to expand...
Click to collapse
MIUI is closed source, so only team members are able to rebuilt it
Do you know how can I use kexec to boot moto kernel?

r2beta0 said:
MIUI is closed source, so only team members are able to rebuilt it
Click to expand...
Click to collapse
This is illegal - violation of GPL license. If they modified Linux kernel they should give users source code to those modifications.

Help mounting with R/W access

Hi, I cannot figure out what I need to write in terminal emulator to gain root access to install cwm. I was hoping someone could post the exact command needed, I would appreciate it alot. I have tried searching but the generic commands i found on a different site didnt work. Thanks!

Can you gain root from terminal emulator? First I have heard this. Why not just Odin one of the modded kernels?
Sent from my HTC Sensation Z710e using xda premium

andale927 said:
Hi, I cannot figure out what I need to write in terminal emulator to gain root access to install cwm. I was hoping someone could post the exact command needed, I would appreciate it alot. I have tried searching but the generic commands i found on a different site didnt work. Thanks!
Click to expand...
Click to collapse
If you're just looking for the command to mount /system as read/write, you'll have to figure out what "device" is used for the mount. From the terminal, type:
mount
That will show you a list of things that are currently mounted. You'll see something like (not exactly):
/dev/block/stl9 /system rfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime, uid=1000,gid=1015,fmask=0002,dm
ask=0002,allow_utime=0020,codepage=cp437,iocharset =iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
The part you're interested in is the part before "/system" and that is the block device used to mount your system partition. To mount it read/write, you type (based on this example's block device & based on the rfs vs. ext4 file system):
mount -o rw,remount -t rfs /dev/block/stl9 /system
The -o part tells mount "here come the options" which are read/write & remount. The -t tells it the filesystem type (rfs or ext4, depends on if you have voodoo enabled). The next argument tells it the block device, then what mount point to use.
As for root, what Exodian said. You'll either have to flash a root enabled kernel or use SuperOneClick v2.2.

[Q] OTA Update for Pantech Discover

I have the Pantech Discover
My phone is rooted because of WiFi issues
It only remembered the first 2 WiFi networks I came across after I bought the phone.
So I did all kinds of stuff to it to fix it. But I apparently screwed something up while fixing it, kind of. lol
Every time my phone restarts I have to go to the WiFi files and change the permissions in order for WiFi to turn on.
Other than that it works like a champ. This however isn't the problem.
I want to start fresh. Factory Rom would be great, but nobody has one.
There is an update to 4.1 jellybean for my phone OTA but It gets an error every time I try to update it.
Is there anything I can do?
ANY suggestions or help would be greatly appreciated
Thanks

TheAtreus said:
I have the Pantech Discover
My phone is rooted because of WiFi issues
It only remembered the first 2 WiFi networks I came across after I bought the phone.
So I did all kinds of stuff to it to fix it. But I apparently screwed something up while fixing it, kind of. lol
Every time my phone restarts I have to go to the WiFi files and change the permissions in order for WiFi to turn on.
Other than that it works like a champ. This however isn't the problem.
I want to start fresh. Factory Rom would be great, but nobody has one.
There is an update to 4.1 jellybean for my phone OTA but It gets an error every time I try to update it.
Is there anything I can do?
ANY suggestions or help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
The update validates that dozens of files in /system including everthing in /system/app is there and unmodified. The user gj23 was kind enough to provide the original ICS /system files here: http://www.mediafire.com/folder/r3n3loxxlrv08/systemext4. I was able to help another user with the same problem get updated and suggest the following procedure.
Do this at your own risk. I do not recommend that you try to replace a file unless you are sure you removed or modified it or it shows up as invalid in the log. This can be tedious but far less tedious and risky than reconstructing the entire /system partition (voice of experience).
NOTE: Download and use the VooDoo OTA Rootkeeper application to temporarily unroot. You can use the app to restore root after the update. If you lose root several users have reported Framaroot 1.6 works with Jellbean, download here: http://forum.xda-developers.com/showthread.php?t=2130276.
Dowload the JB update on the phone and choose to delay the update.
Install an sd card in the phone and using a root explorer copy the update to the external sd card. The update is called gota_package.bin and is in /cache/recovery.
Rename the file you copied to the external sd card to gota_package.zip.
Open the last_log file in the /cache/recovery folder with a text editor, scroll to the bottom, and look for a message indicating which file failed the checksum validation.
Download the valid version of the file that failed from the site I posted above. If there is a file with the same name in the same folder but with a different extension (e.g. myfile.apk & myfile.odex) dowload both.
Using a root explorer copy the file(s) you downloaded to the appropriate directory on your device.
Access recovery mode. To do this shutdown the phone, hold the volume up key and the power key down, when you see "pantech" flash on then off let go of the power button. You should be at the green robot screen, if not try again. From here, hold down power, press up volume, then let go of both. You should see a menu of options if not try again.
Use the volume keys to navigate to the option that allows you to install an update from the external sd card, press power, select gota_package.zip, press power again to run the update.
If the update fails go back to step 4 and repeat the process.
If you know which /system/app files you removed you can download and copy all of them (both apk & odex) at once.
Ask if you have questions.

sandnap said:
The update validates that dozens of files in /system including everthing in /system/app is there and unmodified. The user gj23 was kind enough to provide the original ICS /system files here: http://www.mediafire.com/folder/r3n3loxxlrv08/systemext4. I was able to help another user with the same problem get updated and suggest the following procedure.
Do this at your own risk. I do not recommend that you try to replace a file unless you are sure you removed or modified it or it shows up as invalid in the log. This can be tedious but far less tedious and risky than reconstructing the entire /system partition (voice of experience).
Dowload the JB update on the phone and choose to delay the update.
Install an sd card in the phone and using a root explorer copy the update to the external sd card. The update is called gota_package.bin and is in /cache/recovery.
Rename the file you copied to the external sd card to gota_package.zip.
Open the last_log file in the /cache/recovery folder with a text editor, scroll to the bottom, and look for a message indicating which file failed the checksum validation.
Download the valid version of the file that failed from the site I posted above. If there is a file with the same name in the same folder but with a different extension (e.g. myfile.apk & myfile.odex) dowload both.
Using a root explorer copy the file(s) you downloaded to the appropriate directory on your device.
Access recovery mode. To do this shutdown the phone, hold the volume up key and the power key down, when you see "pantech" flash on then off let go of the power button. You should be at the green robot screen, if not try again. From here, hold down power, press up volume, then let go of both. You should see a menu of options if not try again.
Use the volume keys to navigate to the option that allows you to install an update from the external sd card, press power, select gota_package.zip, press power again to run the update.
If the update fails go back to step 4 and repeat the process.
If you know which /system/app files you removed you can download and copy all of them (both apk & odex) at once.
Ask if you have questions.
Click to expand...
Click to collapse
Can someone provide the gota_package.bin file?

jose makalolot said:
Can someone provide the gota_package.bin file?
Click to expand...
Click to collapse
Uploading gota_package.zip (renamed already), I'll PM you a link in a while.

sandnap said:
Uploading gota_package.zip (renamed already), I'll PM you a link in a while.
Click to expand...
Click to collapse
thank you sir
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4

Wow... Totally lost hope in finding a solution.. I'm not sure which files have been modified due to me allowing apps to try and fix issues with my phone and getting the permissions to "stick" I'll take a look at what you've presented here and try to figure out which files I need to change
Sent from my PantechP9090 using xda app-developers app

attnav.apk first delinquent lol... I removed that soon after rooting.. so no surprise there. Ill let you know how it all goes
Update 1:
currently downloading (slowly) the update file.
While I wait I am checking my phones files with the list of files in the link above.
Ive created a mirror image of the folder structure on my computer where i download all the missing files in the appropriate folders. So far in the apps folder in the "A"s ive deleted 4 files family map.. the stupid driving app attnav and some other att bull..
I knew it would come down to this but wasn't anything I could do without the original files... THANK YOU GUYS sooo much
Update 2:
Final Count in the app folder was 16 missing files... Question. Should I remove the superuser.apk file?

Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.

TheAtreus said:
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
Click to expand...
Click to collapse
Well anyone who has this phone and does this... It works GREAT. BTW my root was still in place but superuser temporarily unrooted my phone and had rootkeeper enabled... I just unchecked temp unroot and its back in business...
Still does anyone know how to make the permissions stick... OR could Greg Jennings upload just the wifi files.
I know there are multiple files but all known associated files to the operation of wifi would be great. I was hoping this update would fix the issue but it didnt.

TheAtreus said:
Well anyone who has this phone and does this... It works GREAT. BTW my root was still in place but superuser temporarily unrooted my phone and had rootkeeper enabled... I just unchecked temp unroot and its back in business...
Still does anyone know how to make the permissions stick... OR could Greg Jennings upload just the wifi files.
I know there are multiple files but all known associated files to the operation of wifi would be great. I was hoping this update would fix the issue but it didnt.
Click to expand...
Click to collapse
What exactly do you do to get it working after a reboot? Can you access it with adb? More than likely you just need to mount the partition as read/write before making the changes
---------- Post added at 07:02 AM ---------- Previous post was at 06:50 AM ----------
TheAtreus said:
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
Click to expand...
Click to collapse
I updated the tutorial above to address maintaining root or rerooting after the update.

sandnap said:
What exactly do you do to get it working after a reboot? Can you access it with adb? More than likely you just need to mount the partition as read/write before making the changes
---------- Post added at 07:02 AM ---------- Previous post was at 06:50 AM ----------
I updated the tutorial above to address maintaining root or rerooting after the update.
Click to expand...
Click to collapse
I got root back... luckily the superuser app is smarter than me.
When I turn the phone on, it wont even let the wifi turn on for a second... So I go to /data/misc/wifi and change the permission of wpa_supplicant.conf from rw-rw---- to rwxrwxrwx ... but it always reverts back if my phone ever turns off.
There are some other files I do the same way. I am doing this using ES File Explorer. Also that wpa file along with some others have root for the owner and for the group.
Im just tired of having to do that and remembering all the passkeys to all my friends networks because my phone cant.

TheAtreus said:
I got root back... luckily the superuser app is smarter than me.
When I turn the phone on, it wont even let the wifi turn on for a second... So I go to /data/misc/wifi and change the permission of wpa_supplicant.conf from rw-rw---- to rwxrwxrwx ... but it always reverts back if my phone ever turns off.
There are some other files I do the same way. I am doing this using ES File Explorer. Also that wpa file along with some others have root for the owner and for the group.
Im just tired of having to do that and remembering all the passkeys to all my friends networks because my phone cant.
Click to expand...
Click to collapse
If you have adb access to the phone type (hit enter after each line):
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
If you don't have access to adb download the "Android Terminal Emulator" app from the Play Store, open it and type:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
Now, make your permission changes, reboot, and report back. If that doesn't work give me the full path of all files causing the issue and I will write a script that will take care of it.

Alright will do
Sent from my PantechP9090 using xda app-developers app

sandnap said:
If you have adb access to the phone type (hit enter after each line):
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
If you don't have access to adb download the "Android Terminal Emulator" app from the Play Store, open it and type:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
Now, make your permission changes, reboot, and report back. If that doesn't work give me the full path of all files causing the issue and I will write a script that will take care of it.
Click to expand...
Click to collapse
Okay i followed the directions.
I rebooted my phone first
Connected it to my computer after it finished booting
Opened my command prompt
made sure my phone was detected
Ran adb shell (said it was out of date)
Here is a copy of what I did
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p14 /system
[email protected]:/ # mount -o rw,remount /dev/block/mmcblk0p25 /data
mount -o rw,remount /dev/block/mmcblk0p25 /data
[email protected]:/ #
Also here is a list of my mounts after reboot
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,relatime,data=orde
red 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,rel
atime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,relatime,noauto_da
_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatim
e,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000
,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=low
er,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ #
None of what i did before stuck
Here is a list of the files, the status of the files, and what I change on each file.
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O root G root CHANGED TO rwxrwxrwx (i didnt change the owner or group on any of them)
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi CHANGED TO rwxrwxrwx
/data/misc/wifi/wpa_suplicant/wlan0 STAYED AFTER TRYING YOUR FIX it is rwxrwxrwx O wifi G wifi
/dev/network_latency rw-rw---- O root G root CHANGED TO rwxrwxrwx
/dev/network_throughput rw-rw---- O root G root CHANGED TO rwxrwxrwx
/dev/wcnss_wlan rw-rw---- O root G root CHANGED TO rwxrwxrwx
After reboot they all except the one I told you about changed back.
I honestly dont know what files do what for wifi... so I just changed these try and make the networks STICK... All I need to do to get wifi to actually turn on and act right is change that first file and it will turn on and take a network passkey and continue working until phone reboots. then i have to change the permissions again and re-enter the passkey for the networks.

Just read that wifi is controlled by the kernel.. When I rooted my phone (using the guide found here at xda ultimate... ) I believe it had the original ics kernel. Would that help?
Sent from my PantechP9090 using xda app-developers app

If you need any more information just let me know
Sent from my PantechP9090 using xda app-developers app

The permissions and ownership for the same files on my JB discover are:
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O system G wifi
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi
/data/misc/wifi/wpa_suplicant/wlan0 rwxrwx--- O wifi G wifi
/dev/network_latency rw------- O root G root
/dev/network_throughput rw------- O root G root
/dev/wcnss_wlan rw------- O root G root
It looks like the ownership is different for the first file but you have the same ownership and equal or looser permissions on the rest of the files. Try changing the ownership of wpa_supplicant.conf:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /data
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
exit
exit
adb reboot

sandnap said:
The permissions and ownership for the same files on my JB discover are:
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O system G wifi
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi
/data/misc/wifi/wpa_suplicant/wlan0 rwxrwx--- O wifi G wifi
/dev/network_latency rw------- O root G root
/dev/network_throughput rw------- O root G root
/dev/wcnss_wlan rw------- O root G root
It looks like the ownership is different for the first file but you have the same ownership and equal or looser permissions on the rest of the files. Try changing the ownership of wpa_supplicant.conf:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /data
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
exit
exit
adb reboot
Click to expand...
Click to collapse
That worked half way. Now I dont have to change any permissions in order to get wifi to turn on but now I have to enter in the passkey for the network every 3 minutes or so because it wipes it or something
UPDATE
Im the type to just fiddle with stuff till it works.. While this hasn't really fixed my issue it might explain whats going on more to you that know the inner workings of Android linux OS better than i do. After I type the passkey in for my wifi network I wait for it to connect and before it shuts off on me I restart my phone... I tried it with the regular connection I have and after that I was think OH maybe it just needed to restart to fix it so i tested with my 5G connection. I put the passkey in and turned my wifi off and then back on it lost the info for 5G and still had the regular... So I typed it in again and restarted my phone and now both are stored permanently (i assume)

TheAtreus said:
That worked half way. Now I dont have to change any permissions in order to get wifi to turn on but now I have to enter in the passkey for the network every 3 minutes or so because it wipes it or something
UPDATE
Im the type to just fiddle with stuff till it works.. While this hasn't really fixed my issue it might explain whats going on more to you that know the inner workings of Android linux OS better than i do. After I type the passkey in for my wifi network I wait for it to connect and before it shuts off on me I restart my phone... I tried it with the regular connection I have and after that I was think OH maybe it just needed to restart to fix it so i tested with my 5G connection. I put the passkey in and turned my wifi off and then back on it lost the info for 5G and still had the regular... So I typed it in again and restarted my phone and now both are stored permanently (i assume)
Click to expand...
Click to collapse
So it seems to be okay for now? It's strange that it wipes after a few minutes. In Settings > Backup & Reset do you have the "Back up my data" checkbox checked? It's a long shot but I wonder if it's synchronizing with the google server and your settings are being overwritten. If you have this selected you can try unchecking it. Have you tried doing a factory data reset?
On a different topic, have you tried booting to the recovery-evita.img since you updated to Jellybean? I am pretty sure they locked the bootloader with the JB update but wanted to confirm with others.

sandnap said:
So it seems to be okay for now? It's strange that it wipes after a few minutes. In Settings > Backup & Reset do you have the "Back up my data" checkbox checked? It's a long shot but I wonder if it's synchronizing with the google server and your settings are being overwritten. If you have this selected you can try unchecking it. Have you tried doing a factory data reset?
On a different topic, have you tried booting to the recovery-evita.img since you updated to Jellybean? I am pretty sure they locked the bootloader with the JB update but wanted to confirm with others.
Click to expand...
Click to collapse
This is what I got when I tried
C:\Users\Atreus\Downloads>fastboot devices
6603452b fastboot
C:\Users\Atreus\Downloads>fastboot boot recovery-evita.img
downloading 'boot.img'...
OKAY [ 0.640s]
booting...
FAILED (remote: Not Support !!)
finished. total time: 0.656s
C:\Users\Atreus\Downloads>
So it looks like they patched that... If somebody wanted root their phone like our. they would need to revert back to ICS do you know how to do that?

how to make an everybody accessible tmpfs

on PCs, i like having tmpfs/ramdisks, and trying to force everything to use it for burnable trash, i mean cache ;P. the reason why im trying to enforce it is because of my old elementary school teacher back in Y2K said, 'a byte saved is a byte earned', a spin of a proverb that i truly believe in. id say its successful on older OSs, but some difficulties with newer droids. ive seen the horrors of changing the internal a few times...
my only phone ATM is a redmi 8
- firmware A9
- crdroid A11
- magisk set to global, and 'su -mm' just for the double tap
root dir /tmp
mount -t tmpfs tmpfs /tmp
chmod 0777 /tmp
chown everybody:everybody /tmp
works just fine, except everything is restricted to root access (pretty sure chmod and chown arent required for this).
so the next step was to mount '/sdcard/tmp' (shortened from /storage/emulated/0/tmp, thankfully it works). doesnt work as i expected (nor the full name). a reboot shouldve cleared everything inside a tmpfs, after a reboot /tmp was empty whereas /sdcard/tmp still had the random test files. 'df -h' correctly reports /tmp is used whereas /sdcadr/tmp was not used. reading the 'mount' points only work under root as well. as i know linux in general dont play well with symlinks on different filesystem types, i did a bit of searching a long time ago for my old dead phone running A6. these tricks no longer work.
How can I make a symlink (or equivalent) inside /storage/emulated/0?
So, I have rooted my phone (GT-i9505 with android 5.0.1) and I would like to move my WhatsApp folder to my external SD card to save 3GB on internal storage. This is what I tried so far. EDIT: solu...
android.stackexchange.com
What is a bind mount?
What is a “bind mount”? How do I make one? What is it good for? I've been told to use a bind mount for something, but I don't understand what it is or how to use it.
unix.stackexchange.com
using the mount -o bind method was what i wanted, symlink that worked both ways. on this phone they both dont seem to connect, each acting as their own folder.
what i wanted to achieve was setting a global /tmp (done), but accessible to everybody under /sdcard/tmp (confused), then later symlink /sdcard/android/data/*/cache to /sdcard/tmp. this is obviously way above my pay grade and im honestly stummped. a quick search shows no ones interested with tmpfs on droids. would be awesome if one were to come along and make a simple everybody usable tmpfs as a shellscript/magiskmodule.
is any of this achievable under modern OSs?