Link2sd Mount error- "2nd Partition not mounting during boot" (SM-A710F) - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Im getting Link2sd mount error :- "Since the 2nd partition is not mounted during boot time it has been mounted after the system finishes booting. Therefore linked apps are not visible to the system at the moment".
After I follow its advice and do a quick reboot (soft reboot) everything is ok
After researching a lot, I can tell that both init.d & install-recovery.sh is required, which cannot find in /system/etc (using root explorer).
Please suggest if it can be created or not.
Mobile is rooted with Twrp 3.0.2 installed (running 5.1.1).
Busybox is also installed

Related

[Q] Anybody had success with "Linux Installer" app on WajkIUI?

Hi the question is in the title.
I got it working on quarx's cm7 RC 1.0(only with directory method), but on WIUI 2.2.3 i get errors.
On startup i get this error:
Internal tests failed!
-Kernel config is not known becouse /proc/config.gz file is not found. /this was present on cm7 too/
Here i click override.
Directory method:
And when i click "Install in chroot directory" it says "Error: Partition is mounted with nodev: Can't remount with nodev!"
Loop method:
Creating and formating the loop finishes fine.
When i click mount loop it says: "Can't mount BLOCK Part: Did you forget to format? I think this ext version is not supported!"
however i'm using the ext2 file format, which is included in the application. In the log i found this line: "MountLoop > Error:mount mounting /dev/block/loop1 on /data/local/mnt/Linux failed: No such device"
I think this is the source of the error. Beside that i didn't found any strange entries in the log.
I managed to get it working.
All i had to do is remount /data with dev option. After that the directory method is working on internal memory. I've also tried to install linux on sdcard, but that fails, because when i try to change the "Chroot point" in the setup i get "Directory is nodev!, not saved", even after remounting /mnt/sdcard with dev option.
Anybody have an idea to fix this?
for me it worked!
..unfortunetly only for debian squeeze :/ would like to get at least ubuntu 10.4.
i had to manually umount my sdcard.
i'm not shure if this was necessary, but i also remounted all devices that where mounted as nodev.
my mountpoint was /data/local/linux
EDIT: *sigh sorry i forgot to say, i'm on atrix,not on defy.. but the point is, that i also get those errors whenever i try to install any ubuntu while debian squeeze works fine.
I have the same problem
Hi!
I have the same problem,I tried all the 3 roms (Wiui,CM,Miui)+the stock with root,but on these roms,the linux installer sends the same message: "Kernel features is not know because the /proc/config.gz file is not found"
I tried to install Ubuntu too with the ubuntu installer app from market ,it didn't work too.
Is there anybody,who use any linux on his/her Defy?
I' sorry for my English.
On CM10 the application named "Complete Linux Installer" is working fine. Unfortunately i'm still not able to use loop method on CM7. If you really need this on your phone you should try CM10.
By the way i would happy to hear about anybody who have a working loop device setup on CM7.
jumika said:
Directory method:
And when i click "Install in chroot directory" it says "Error: Partition is mounted with nodev: Can't remount with nodev!"
Click to expand...
Click to collapse
I may have partially solved this if you haven't already. Here's what I did to install using BLOCK method:
First, used an old HTC Dream that had an Amon RA recovery on it to format the SD card. The recovery has an automated option to make an ext2, 3, or 4 partition + swap on the sdcard. I first made an ext2, then coverted it into ext3, then into ext4. I then put the sdcard back into my main phone. My main phone did not support the Amon RA recovery and that's why I needed to use another phone.
Then I used another app called "Linux Deploy" to see what the ext4's /dev/block was. The app has a menu option called "sysinfo". I think you can also just use that command in Terminal Emulator. Look at the partition sizes carefully. Remember the filesize you used to create your EXT (the swap partition is right under your EXT as well). Use that block device in the Linux Installer setup menu. You shouldn't see the "nodev" anymore.
What happens is that the sdcard itself is usually formatted as FAT32 (vfat) and will always be "nodev". Partition some or all of the space as EXT + SWAP and it will be fine. I've successfully installed to sdcard using this way. Let me know how this works for you or if I need to clarify some things.

[Q] 0.00b free on /system after rooting

Dear all,
I tried to use link2sd on my S6102, so first I rooted it using this tutorial (which is linked in the link2sd tutorial):
http://forum.xda-developers.com/showthread.php?t=1611830
After applying update.zip, link2sd reports 0.00b on /system, thus the error message when starting link2sd:
"Mount script cannot be created. write: No space left on device.
Before applying update.zip, it was 1.4Mb in /system.
What does it mean? Did I do anything wrong?
BTW in this state, I tried to install the 15toggles package, which resulted in boot loop - had to restore nandroid backup via cwm. Maybe the same reason?
Thanks a lot!
To create a mount script you need a 2nd ext partition on your sd card - nothing to do with /system although you do need space there to place the script which I think is your problem
if you have got /system problems wipe Dalvik cache in cwm
if you still have problems You will have to wipe system & data and install a custom rom that is pre rooted
Yes 2nd partition is there and yes I think it is the script itself which doesn't fit in /system
Wiping dalvik cache did not change anything...
Maybe I can find another root "package" and try with that...

Android 7 writeable /system partition

Hey I can't seem to write to my /system partition on my phone. My phone is rooted and I have tried all the read write commands but it says device busy or "bad option". Its just been a pain for some root apps that write to the system folder. I have to use the systemless AdAway and flash the better battery stat systemless zip... Thanks in advance

Link2SD: mount warning on Samsung galaxy Tab 6 SM-T285

Hi
I was able to install Link2SD Plus version on my rooted tablet but I'm seeing following message after reboot.
Notification: Mount warning
Since thee 2nd partition is not mounted during boot time it has been mounted after the system finishes.
Therefore your linked apps are not visible to the system at the moment.
To make them available again, please try 'Recreate mount scripts' or 'Quick reboot'
1. I tried 'Recreate option' but I have this warning always.
2. When I tried quick reboot I had screen flicker and still got the warning,
I see the ext4 partition mounted already
#df
/data/sdext2 18.2G 4.0K 18.2G 18.2G 2048
What should I do?
I also uploaded the link2sd log files found in /data/ directory
Thank you.
How to rooted my galaxy tab A 6
necro 1/2: in case somebody lands here from google when looking for this "warning" on link2sd. I solved the problem. Try this post:
https://forum.xda-developers.com/showpost.php?p=78074532&postcount=5671

unable to mount system R/W

*Redmi 7a MokeeOS PIE built in root*
Hi, I was able to root the ROM with mokee add-on su, but root apps give me error "unable to mount system R/W"
So I remounted using ADB:
>ADB ROOT
>ADB REMOUNT
It worked successfully as R/W. But it doesn't last as default. It automatically comes back to RO
.
.
*IN SHORT*
I want a way to mount system read/write permanently without worrying if it will automatically be set back READ ONLY
Any help I'd appreciate it
I tried fixing SELinux, didn't work.
I have the same problem, in stock is also like this, you can not move apps to the system partition because it can not mount as writable.
Luelu said:
I have the same problem, in stock is also like this, you can not move apps to the system partition because it can not mount as writable.
Click to expand...
Click to collapse
You can mount it with debugging as mentioned:
>ADB ROOT
>ADB REMOUNT
But the problem is, it's only temporarily

Categories

Resources