[Q] Xperia L Bootloop after mounting SD card using Link2SD - Sony Xperia L

I am facing trouble in mounting 2nd partition (ext4) of the SD card using Link2SD in Rooted Xperia L. Like many people have faced. I experienced a Boot-Loop. After taking out the partitioned SD card, fortunately the phone boots fine. Even it boots without any problem with non-partitioned SD card, too.
There is unofficial solution of enabling support for init.d using apps like Init.d Toggler.
But, I find that there already an /etc/init.d directory exists. Inside, there are two scripts, viz. 00stop_ric and 11link2sd.
00stop_ric
---------------
#!/system/bin/sh
/system/xbin/busybox pkill /sbin/ric
mount -o remount,rw /
rm /sbin/ric
mount -o remount,ro /
/system/xbin/busybox pkill /sbin/ric
Click to expand...
Click to collapse
11link2sd
--------------
#!/system/bin/sh
#added by link2sd
LOG=/data/link2sd-11link2sd.log
echo "$(date) mounting..." > $LOG
sleep 2
mount -t ext4-o rw /dev/block/
vold/179:34/data/sdext2 1>>$LOG
2>>$LOG
mount -t ext4-o rw /dev/block/
mmcblk1 p2 /data/sdext2 1>>$LOG
2>>$LOG
mount >> $LOG
echo "$(date) mount finished" >> $LOG
Click to expand...
Click to collapse
I failed to find any reference to this problem in the FAQ section of official website.
Should I go for Init.d Toggler solution?
What is causing this problem?
Is 00stop_ric the original mount script of Xperia L?
I solved the problem using Init.d Toggler.
But, I find it surprising why it boot-loop-ed initially, i.e. when init.d was disabled. It could fail to mount the partition, that is acceptable. But, how come just the presence of /etc/init.d/11link2sd script make it boot-loop?
Even before trying Link2SD, I had both /etc/init.d and /etc/init.d/00stop_ric script present. There are the leftover from the Getroot method I applied to root my Xperia. So, neither the phone not having init.d support nor the creation of init.d folder can be the cause of boot-loop.
Definitely, either the presence of /etc/init.d/11link2sd script or something else which we are missing (Developer of Link2SD, Akpinar should be able to correctly answer) is/are the cause of boot-loop.
@Akpinar
Please let us know what Link2SD exactly does while creating Mount script.

@Any Moderator,
Please move this thread to Troubleshooting section. I realized that I have posted in wrong section.

Related

HOW TO MOUNT an SD card

I want to know what clockworkmod did after refermatting
What device do I use
mkdir mnt/c
mkdir mnt/d
mou mount -o rw,remount -t ?????????????? /mntc
I'm hardly a command line unix user but without knowledge of the exact device
I'm never ever going to succeeed
PLEASE ANSWER I'm hoping for an echo of the mounted file system
ext 3 /ext 4
PLease Help

Journal Disabler For Pico! :D

----------------------- Journaling Disabler For Pico ----------------------
This is just a simple Zip to Disable Journaling on pico! as we use 2 or 3 extra ext4 partitions for OC!
It even clear's /sd-data,/sd-cache - for aosp
and /sd-ext,/sd-data,/sd-cache - for sense 4
Which means you need not always format your sd-card to switch between roms! .. But if you are switching from aosp rom to sense 4 you need to partition the sd-card appropriately!
Steps to USE:
******* Use this Zip Only when installing a Rom from scratch!... cause it wipes everything! ******
-- clear almost everything you can from recovery e.g factory-reset,/system,/boot,/cache etc
-- install this Zip! as like you do with any other zip (Prefered Recovery TWRP 2.4.X)
-- Flash Your Favourite Rom Now!!
I can use this even if i am not oc'ing?? Just like superwipe?
Disabling journal wont harm anything! Right?
Parth_14 said:
I can use this even if i am not oc'ing?? Just like superwipe?
Disabling journal wont harm anything! Right?
Click to expand...
Click to collapse
From the wikipedia's article:
A journaling file system is a file system that keeps track of the changes that will be made in a journal (usually a circular log in a dedicated area of the file system) before committing them to the main file system. In the event of a system crash or power failure, such file systems are quicker to bring back online and less likely to become corrupted.[1]
Click to expand...
Click to collapse
For overclocking, the SD Card is used for the /data and /cache partition. In that case, the SD Card would be read more frequently as the /data and /cache partitions are the most frequently accessed and modified partitions while running the Android system. In that case, using a Journal would slow down the memory access times if the SD Card is not fast enough. Also, as many modifications are made to the /data and /cache partition, the SD Card would be going through the read/write cycle twice the number of times, once for the journaling and once for the "commiting them to the main file system". So, it is likely that the SD Card might get corrupted faster than it normally should. That is the reason why Class 4 and below SD Cards are likely to "go dead" soon when overclocking with cute_prince's new PLL2 overclocking method. And, this is why ateeq72 has made this flashable zip to disable journaling. It would reduce the possibility/risk of losing your SD Card and at the same time allow you to OC your phone.
Using this when you are not OC'ing your phone? I wouldn't recommend that you flash this zip, but you would need a slightly modified zip. Also, journaling, I presume you want to disable in your phone's sd-ext memory. It would increase your phone's performance in case you are using any memory increasing scripts like int2ext which mount the sd-ext partition in the /data folder.
vineethraj49 said:
Using this when you are not OC'ing your phone? I wouldn't recommend that you flash this zip, but you would need a slightly modified zip. Also, journaling, I presume you want to disable in your phone's sd-ext memory. It would increase your phone's performance in case you are using any memory increasing scripts like int2ext which mount the sd-ext partition in the /data folder.
Click to expand...
Click to collapse
Thanks man!
Can you tell what is to be modified in the zip so that i can use it when i am not oc'ing?
Parth_14 said:
Thanks man!
Can you tell what is to be modified in the zip so that i can use it when i am not oc'ing?
Click to expand...
Click to collapse
No need to mod dude, u can use it if u dont OC.
Helped? Thanks maybe!
Parth_14 said:
Thanks man!
Can you tell what is to be modified in the zip so that i can use it when i am not oc'ing?
Click to expand...
Click to collapse
Edit the file named "ateeqscript" using Notepad++.
Make sure the file looks like the one below.
Code:
#!/bin/sh
echo ***************Begin Disable Journaling Partition***************
/sbin/busybox mount -t auto /dev/block/mmcblk0p2 /sd-ext
rm -rf /sd-ext/*
/sbin/busybox umount -l /sd-ext
/tmp/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p2
fsck.ext4 -Dfy /dev/block/mmcblk0p2
sync
echo ***************Data Partion Done***************
echo ***************Finished No Journaling Partions***************
What I have done? Simple. Removed all code related to /sd-data and sd-cache, and kept only commands necessary for the sd-ext partition.
---------------------------------------------------
@OP, I suggest a few changes in your script. First, the mounting commands are run, so, if the sd-ext is already mounted by the recovery (just in case, accidentally it happened), then, you wouldn't (or rather shouldn't) be able to mount it in another folder, namely /sd-data. I would suggest the following change in your flashable zip. Try to make it look something like the one below.
Code:
#!/bin/sh
echo "\"Disabling Journaling\" Script"
echo "Initializing script..."
/sbin/busybox umount -l /sd-ext
/sbin/busybox mkdir /sd-data
/sbin/busybox mount /dev/block/mmcblk0p2 /sd-data
/sbin/busybox mkdir /sd-cache
/sbin/busybox mount /dev/block/mmcblk0p3 /sd-cache
/sbin/busybox mkdir /sd-ext2
/sbin/busybox mount /dev/block/mmcblk0p4 /sd-ext
rm -rf /sd-cache/*
rm -rf /sd-data/*
rm -rf /sd-ext/*
/sbin/busybox umount -l /sd-data
/sbin/busybox umount -l /sd-cache
/sbin/busybox umount -l /sd-ext
echo "Disabling Journal in sd-data"
/tmp/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p2
fsck.ext4 -Dfy /dev/block/mmcblk0p2
echo "Disabling Journal in sd-cache"
/tmp/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p3
fsck.ext4 -Dfy /dev/block/mmcblk0p3
echo "Disabling Journal in sd-ext"
/tmp/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p4
fsck.ext4 -Dfy /dev/block/mmcblk0p4
sync
echo "Partitions Journaling Disabled..."
echo "Finished no journaling partitions"
Do we need to flash this zip for every new rom or just once is enough?
Sent from my HTC Explorer A310e using xda app-developers app
faiPICO said:
Do we need to flash this zip for every new rom or just once is enough?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
i guess one time is enough no need to flash again and again
@ateeq72
Can you edit this script with just the wiping part? As it is not necessary to disable journal for aosp roms!
Parth_14 said:
@ateeq72
Can you edit this script with just the wiping part? As it is not necessary to disable journal for aosp roms!
Click to expand...
Click to collapse
Its already there I guess
vineethraj49 said:
Its already there I guess
Click to expand...
Click to collapse
I've read that it formats through ext2/4 ! What i want is the parition to be remain untouched..
Parth_14 said:
@ateeq72
Can you edit this script with just the wiping part? As it is not necessary to disable journal for aosp roms!
Click to expand...
Click to collapse
vineethraj49 said:
Its already there I guess
Click to expand...
Click to collapse
journal disabling is required for only ext4 partition for max performace
if u dont use ext4 use any wiping script
the script keval gave format partitions to ext2 only not ext4
sakshamx said:
journal disabling is required for only ext4 partition for max performace
if u dont use ext4 use any wiping script
the script keval gave format partitions to ext2 only not ext4
Click to expand...
Click to collapse
NOTE:------------>Do remember the script of sense will format partitions as EXT2 and script for aosp roms will format partitions as EXT4 and sense 4.1 sctript will also format as EXT4
Click to expand...
Click to collapse
vineethraj49 said:
Click to expand...
Click to collapse
u can check the script it formats as ext2 i had also checked from sd card its ext2
i also had thought that as it was given in thread but its not
is it updated script which u posted in facebook
bloodhound42 said:
is it updated script which u posted in facebook
Click to expand...
Click to collapse
yup! it is!
vineethraj49 said:
@OP, I suggest a few changes in your script. First, the mounting commands are run, so, if the sd-ext is already mounted by the recovery (just in case, accidentally it happened), then, you wouldn't (or rather shouldn't) be able to mount it in another folder, namely /sd-data. I would suggest the following change in your flashable zip. Try to make it look something like the one below.
Code:
#!/bin/sh
echo "\"Disabling Journaling\" Script"
echo "Initializing script..."
/sbin/busybox umount -l /sd-ext
/sbin/busybox mkdir /sd-data
/sbin/busybox mount /dev/block/mmcblk0p2 /sd-data
/sbin/busybox mkdir /sd-cache
/sbin/busybox mount /dev/block/mmcblk0p3 /sd-cache
/sbin/busybox mkdir /sd-ext2
/sbin/busybox mount /dev/block/mmcblk0p4 /sd-ext
rm -rf /sd-cache/*
rm -rf /sd-data/*
rm -rf /sd-ext/*
Click to expand...
Click to collapse
Bro thats why i have mounted sd-ext as "sd-ext2" ! to make sure every recovery doesnt have any issue mounting it!
what is journal?
in many posts i found this about this journal what is this actually..

[Completed] Cyanogenmod 12 and 2nd partition in Sdcard

Any one can tell me what I make round. I have cyanogenmod with one sdcard with 2 partitions the first is mount with ext4 and the second I try fat32 ext4 ext3 ...
I no found fuse.ko in the system but internal partition and storage is mount with fuse in /storage/....
I try to mount the second partition by many difference ways . Always is mount and show up
I copy files from internal memory or sdcard first partition to the second partition
But if I try to open the files I got permission errors . Very possible is a Selinux problem but I have in permissive mode
I look with rootexplorer and files a copy in the 2nd partition in the sdcard for the owner only can read or write
Any ideas how to make the correct mounts for the 2nd Partition on SD card
I make a simple script for make test that is the last configuration I make but still only the owner can read or write that means any app can't open the files if is not root
that is the configuration I use
#!/system/bin/sh
# Mount SD Card Ext4 Script
mkdir /storage/sdcard2
mount -r -w -o exec,dev,suid,rw -t ext4 /dev/block/vold/179:66 /storage/sdcard2
mount -r -w -o exec,dev,suid,rw -t ext4 /dev/block/mmcblk1p2 /storage/sdcard2
chown media_rw:media_rw /storage/sdcard2
chmod g+w /storage/sdcard2
ln -s /storage/sdcard2 /mnt/media_rw/sdcard2
ln -s /storage/sdcard2 /mnt/sdcard2
chown media_rw:media_rw /mnt/sdcard2
chmod g+w /mnt/sdcard2
Hi there,
I'm sorry but I can't find anything related to your question.
Please post that in the forum bellow for more answers from the experts:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck

[Completed] error in link2sd, 2nd partition not mounted. (android lollipop)

hi,
i've partitioned my sdcard to fat32(6gb) and ext2(2gb) using aparted. after installing, link2sd, error says, "mount script can not be created. mount: no such device". i repartition my sdcard using mini partition wizard and set both partition to primary using the same file system as stated earlier, but still the error occur. i tried to manually create mount file /etc/init.d/11link2sd, then change then chmod to 777 using terminal emulator(busy box is installed).
11link2sd contains:
mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2 (i also tried to execute it this command in terminal emulator, but it says, device does not exist). /data/sdext2 folder exist.
other 11link2sd scripts that i have tried also doesn't work.
-------------------------------------------------
#!/system/bin/sh
#added by link2sd
LOG=/data/link2sd-11link2sd.log
echo "$(date) mounting..." > $LOG
# Leave out "/external_sd" if you are using your internal SD card.
# And check the path, it may be different for your ROM.
mount -o bind /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG
mount >> $LOG
echo "$(date) mount finished" >> $LOG
int.d folder is not present so i created it manually(as stated in some post).
i also installed Smanager to run the script at boot.
when i do cat /proc/partitions, it shows that mmcblk1p2(2nd partition of sdcard).
a youtube video says that converting link2sd to system app will fix the problem, however i can not convert link2sd to system app. (i removed some system apps to free up space).
device: rooted myphone uno (android 5.1 lollipop).
thanks.
Hi, thank you for using XDA Assist. Could you let us know what device you're using? It'll help us try to to get your problem solved.
Sent from my Nexus 9 using XDA Free mobile app
Sorry, my bad, I didn't see you're on the myphone uno. Unfortunately there is not much information on xda for your device. I'd try here and see if someone can help you. http://forum.xda-developers.com/showthread.php?p=40872426
Sent from my Nexus 9 using XDA Free mobile app

Mount external partition using rooted Z3 with locked bootloader

Hello.
I just started messing around with my Z3 and so far followed the tutorial here https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714 to install root and recovery without unlocking the bootloader. Also took the chance to make a backup of the ta partition.
My objective was being able to mount an external ext4 partition so I could move game data and free some internal space. I believe the official kernel doesn't support init.d so I searched and found a script that worked and added it to the bottom of init.qcom.post_boot.sh.
Code:
### Init.d support ###
busybox run-parts /system/etc/init.d/
It's a very simple script that creates /sd-ext folder if it's missing and mounts /dev/block/mmcblk1p2 there
Code:
#!/system/bin/sh
#
# mounts ext partition from sd card
if [ ! -d /sd-ext ];
then
mount -o rw,remount /
install -m 774 -o 1000 -g 1000 -d /sd-ext
mount -o ro,remount /
fi
if [ ! -d /sd-ext ];
then
echo sd-ext not created >> /data/Test.log
else
mount -o rw -t ext4 /dev/block/mmcblk1p2 /sd-ext
fi
It was something that I got on some forum plus some trial and error and some Linux knowledge I have.
It seemed to work. The directory was created and mounted and I was able to move the games there using Titanium Backup.
But after I rebooted, the folder was there and all the data, but the apps don't show up on the apps list. I have to reinstall them...
Am I missing something? How can I fix this?

Categories

Resources