(L5 II) CWM for Locked Bootloader(Beta 2) - LG Optimus L3 II, L5 II, L7 II, L9 II

Hey guys
I finished building CWM Recovery for locked bootloaders.
its still in the beta phases.... actually there was no alpha tests because no one on my team has a l5 II.
Due to forum rules I cannot choose who I want to give this recovery or exclude anyone from using it. so if you are a noob I cannot stop you from using it but please dont blame me if you brick your device!!!!!
The recovery as far as I know has no errors.
I have tested flashing Mother of all ad blocking and it worked perfectly.
How Does It Work?
the recovery uses 2nd int.
when your phone boots It is hacked to load scripts from init.d folder.
inside the init.d folder there is a script called 1.unsecure
this stops the system an kills process and launches the recovery.
How Do I Install?
Busybox must be installed
Extract the zip(attached)
Run the init.bat
Enjoy
How Do I Enter Recovery?
Reboot
after the lg logo before your boot animation starts repetitively hit the Vol + key
or run the reboot recovery app
Who do I thank?
ME for all the hard work testing and retesting
@IGGYVIP for giving me hope that its possible and all the support he has given me so far.
Optima Team for being such a great team
Can I port this to my device?
Yes!!
Port this to as many devices as possible. If you need advice or need to know how to port feel free to PM me.
It doesnt work for me?
some user experience problems when the script applies permissions
to fix this
Change permissions to all files in /system/bootstrap/* to 775
Download
DOWNLOAD

---

Great work man! Optima Team is proud of you!!!
Sent from my GT-I9300 using Tapatalk

---

slipsystem said:
Hey guys
I finished building CWM Recovery for locked bootloaders.
its still in the beta phases.... actually there was no alpha tests because no one on my team has a l5 II.
Due to forum rules I cannot choose who I want to give this recovery or exclude anyone from using it. so if you are a noob I cannot stop you from using it but please dont blame me if you brick your device!!!!!
The recovery as far as I know has no errors.
I have tested flashing Mother of all ad blocking and it worked perfectly.
How Does It Work?
the recovery uses 2nd int.
when your phone boots It is hacked to load scripts from init.d folder.
inside the init.d folder there is a script called 1.unsecure
this stops the system an kills process and launches the recovery.
How Do I Install?
Busybox must be installed
Extract the zip(attached)
Run the init.bat
Enjoy
How Do I Enter Recovery?
Reboot
after the lg logo before your boot animation starts repetitively hit the Vol + key
Who do I thank?
ME for all the hard work testing and retesting
@IGGYVIP for giving me hope that its possible and all the support he has given me so far.
Optima Team for being such a great team
Can I port this to my device?
Yes!!
Port this to as many devices as possible. If you need advice or need to know how to port feel free to PM me.
Download
https://dl.dropboxusercontent.com/u/51036208/Android/Stock/cwm.zip
Click to expand...
Click to collapse
why not mod one of the 2nd-init recovery apks with this?? Make much simpler for n00bs as well as give the reboot to recovery option.
Modding the apk I have exp with, I just never had any success building a working 2nd-init binary.

---

PlayfulGod said:
why not mod one of the 2nd-init recovery apks with this?? Make much simpler for n00bs as well as give the reboot to recovery option.
Modding the apk I have exp with, I just never had any success building a working 2nd-init binary.
Click to expand...
Click to collapse
The apk pushes the script to a different location and only executes on the l3 ii. So the app doesn't work on the l5 ii. I would have to do allot of editting. Enable init.d and change where the files get pushed to.
But it's pretty simple for noobs.
And this is not ment for noobs as I said on my thread its still on beta testing.

---

slipsystem said:
The apk pushes the script to a different location and only executes on the l3 ii. So the app doesn't work on the l5 ii. I would have to do allot of editting. Enable init.d and change where the files get pushed to.
But it's pretty simple for noobs.
And this is not ment for noobs as I said on my thread its still on beta testing.
Click to expand...
Click to collapse
ahh, I've just messed with 2nd-init on the LG Motion & Spirit and the same apk works on the F3, F6, & F7 (I think). The Spirit no longer needs 2nd-init tho.

---

PlayfulGod said:
ahh, I've just messed with 2nd-init on the LG Motion & Spirit and the same apk works on the F3, F6, & F7 (I think). The Spirit no longer needs 2nd-init tho.
Click to expand...
Click to collapse
Ya I think the apology works on most devices. If not then mine should work pr you will just have to change the key. It's pretty simple to port. I will try make. A guide tommorow

---

Awesome Work Mate !!!
@slipsystem
Great Job
You have made so much more out of that apk then i ever would
I can see Newsworthy thread when porting to other devices works

---

I can't reboon in recovery mode
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!

---

jamonazo3000 said:
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!
Click to expand...
Click to collapse
Check
/data/local/tmp
There is a file called init.d_log_test
Check if you have that file
Open it check if the date and time matches your last reboot.

---

Great! Now we only need custom roms and android updates.

---

jamonazo3000 said:
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!
Click to expand...
Click to collapse
Sorry its dues to permissions
Change permissions to all files in /system/bootstrap/* to 775

---

slipsystem said:
Sorry its dues to permissions
Change permissions to all files in /system/bootstrap/* to 775
Click to expand...
Click to collapse
the init.sh has chmod rules to 755
the attached one has 775

---

Updated Version in first post!
Now Includes Reboot Recovery app
and hopefully fixed permission problem.

---

slipsystem said:
Check
/data/local/tmp
There is a file called init.d_log_test
Check if you have that file
Open it check if the date and time matches your last reboot.
Click to expand...
Click to collapse
Hello, I was open /data/local/temp/ and only can see a file recoverylog.txt
I will check your new update.
Thanks for all

---

IGGYVIP said:
the init.sh has chmod rules to 755
the attached one has 775
Click to expand...
Click to collapse
sorry my math is bad. the permission are meant to be 755. for some reason when shell is changing permissions it gets permission denied.

---

I think that the script 001unsecureboot doesn't kill the bootanimation, in fact when I reboot to recovery there is the bootanimation (deformed and with strange colors) on the screen, and only when I press a key the recovery appears for one second.
After adding the line "$BB killall bootanimation" after "$BB mount -o remount,rw /system /system", the issue is solved.

---

ownership ?
slipsystem said:
sorry my math is bad. the permission are meant to be 755. for some reason when shell is changing permissions it gets permission denied.
Click to expand...
Click to collapse
May be try changing owner to root before changing permissions ?
in the .sh add this code before chmod but after the remount,rw
Code:
chown -R root /system/bootstrap
in theory as its owner it must allow change of permission
Let me know

---

IGGYVIP said:
May be try changing owner to root before changing permissions ?
in the .sh add this code before chmod but after the remount,rw
Code:
chown -R root /system/bootstrap
in theory as its owner it must allow change of permission
Let me know
Click to expand...
Click to collapse
I actually had the script setting permission for
/System/etc/bootstrap
And not
/System/bootstrap

---

@HandyMenny
Thanks For that. I added that in a update.

---

slipsystem said:
I actually had the script setting permission for
/System/etc/bootstrap
And not
/System/bootstrap
Click to expand...
Click to collapse
with system as System? never had em capped b4.