Read the first few lines of the OP
Solution is posted
Sent from my C6603 using xda app-developers app
Join the discussion to get it fixed for your phone in my fix thread, I'll be needing people with a XL to test possible solutions. I asked OldDroid to test something by moving the fix script, if you are able to help out that would be great. :thumbup:I used the v17 then used 'the fix'
Now the root works completely with no reboot!
Thank you bro, only method that worked with locked bootloader.
Working perfectly in XPERIA L
---------- Post added at 07:58 PM ---------- Previous post was at 07:51 PM ----------
I spoke too soon ...
Using titanium to delete some crap now just restarted the phone: (
Yes me along with the greatest pleasure. Can I test it until it works perfectly. The root xperia L with locked bootloader still does not work.Join the discussion to get it fixed for your phone in my fix thread, I'll be needing people with a XL to test possible solutions. I asked OldDroid to test something by moving the fix script, if you are able to help out that would be great. :thumbup:
Sent from my C6603 using xda app-developers app
It is actually not the rooting tool causing this. It's the fact you try to remount the system partition which makes /sbin/ric intervene and it will reboot your device to 'save' it from a potentially hazardous situation.Yes me along with the greatest pleasure. Can I test it until it works perfectly. The root xperia L with locked bootloader still does not work.
I even tested starting from scratch, flash stock rom via cwm .31 and .36, used the v17 and then used 'the fix' and was still restarting every time it uses the permissions in titanium backup.
I've tried other versions starting v13 and none worked well.
Ok, I'll be waiting for something permanent for the Xperia L.It is actually not the rooting tool causing this. It's the fact you try to remount the system partition which makes /sbin/ric intervene and it will reboot your device to 'save' it from a potentially hazardous situation.
Head on over to the reboot-remount fix thread: http://forum.xda-developers.com/showpost.php?p=43719890&postcount=131
That's the post you can use to help me fix it, this describes a temporary fix until we find a permanent solution.
Good!Thank you so much DoomLoRD!!!! Awesome...:good:
Can you help us with CWM? I mean to install it manually by using stock kernel. Thanks in advance!!!
OldDroid and me have teamed up for this... (read other comment too)Thank you so much DoomLoRD!!!! Awesome...:good:
Can you help us with CWM? I mean to install it manually by using stock kernel. Thanks in advance!!!
(read above comment)Good!
Install CWM manually without changing kernel would be good .. After only exchange kernel with cwm with unlocked bootloader: (
Thank you bro... I hope u got it!!!! It would be great for users. :good:OldDroid and me have teamed up for this... (read other comment too)
(read above comment)
....he is on holiday now, we will get to work on that as soon as he gets back.
Recovery for locked bootloaders will come, soon
Sent from my C6603 using xda app-developers app
Hello,Head on over to the reboot-remount fix thread: http://forum.xda-developers.com/showpost.php?p=43719890&postcount=131
That's the post you can use to help me fix it, this describes a temporary fix until we find a permanent solution.
su
pkill -f /sbin/ric; mount -o remount,rw /; chmod 644 /sbin/ric

Yes, you can. Because these just need root and this method is for rooting.So just to be sure:
I'll be able to use mods that swaps internal and external SD or apps like Link2SD with this method?
Yes, the install-recovery.sh makes it stick and will apply the temporary fix with every reboot.@Nut
Hi! I do what you write about heross "fix". I write his line of code in terminal and then creat a file in /system/etc exectly that you mentioned. It worked, I uninstall some system app in Titanium BackupThe only question I got is: this "fix" will work after I reboot my phone, or I have to dit again? I think the file that we create: /system/etc/install-recovery.sh is for that, just want to be sure...
THNX!
Anything I'm doing wrong. The trick with the install-recovery.sh does not work for me. :crying:Yes, the install-recovery.sh makes it stick and will apply the temporary fix with every reboot.

Can you attach your install-recovery.sh so I can see if you did anything wrong?Anything I'm doing wrong. The trick with the install-recovery.sh does not work for me. :crying:
But is not a problem, so i use my terminal startcommand. its only one click after reboot.![]()
Change the permissions to 755 and it should start to work.Hello [NUT],
here is my file. (delete .zip at end of file)
I have test with this both lines on start and permission 644
#! /system/bin/sh
#!/system/bin/sh