Root Test a working lg740 cwm-based recovery v6.0.3.7

[danhalen1]

Wanted to start a new thread for this.
Finally resolved the DTB error, then the malformed fstab error i had in my previous build. This should backup all the partitions to the sdcard. It seems fine on mine so far just waiting for it to generate the md5. Only bootable in fastboot at this point.

This is the first and possibly only version i will be compiling and releasing. If there is a major bug i do not know if i will be able to fix it. If you are interested in picking up where i am or collaborating pm me.

You will most likely need the bootloader unlocked for this to work.

fastboot boot cwma1.img and it will boot into the recovery. Flashing it as the main recovery does not work at this point. Im not sure why. SO DO NOT FLASH IT AS RECOVERY.

dropbox link
https://www.dropbox.com/s/m8verc01kr8gnzq/cwma1.img


Assume anything you do to your phone will brick it.

 

[donjuro]

If you try flashing it with a locked bootloader the worst that can happen is it will be rejected, correct?

 

[danhalen1]

If you try flashing it with a locked bootloader the worst that can happen is it will be rejected, correct?

Im not really sure what the outcome will be, i assume you will get that lg security error screen?

 

[danhalen1]

Just had a tester inform me that flashing it as your recovery does not work, so dont do that. But it boots fine and you can make a backup. Im not sure why it wont work, but it just boots to a blank screen instead of recovery.

 

[donjuro]

I was just about to inform you of that too. So it only works via flash boot? That sucks. BTW when you type in reboot recovery via adb it boots to an error that you don't see when you power off and vol- + power.

 

[danhalen1]

I was just about to inform you of that too. So it only works via flash boot? That sucks. BTW when you type in reboot recovery via adb it boots to an error that you don't see when you power off and vol- + power.

huh what was the error given? Yeah it only works via fastboot Boot. It is somewhat annoying, but you can make a full backup without error to the sdcard. I have a feeling it might be a video setting or a kernel issue.

 

[donjuro]

I don't remember. I'm just getting out of work but when I get time today I'll run the command again and post what I see here.

 

[marcukial]

Any way to make this bootable from sdcard without computer?could a script be ran at boot to somehow make it work using init d or something?thanks for making this.really good to have a fix if ever in trouble.

 

[mjhealy1978]

Any way to make this bootable from sdcard without computer?could a script be ran at boot to somehow make it work using init d or something?thanks for making this.really good to have a fix if ever in trouble.

Yes marcukial, good question! Can this be done without a computer with the init d?

 

[donjuro]

I still haven't run this and have had a really busy day, but I just wanted to congratulate you all and thank everyone who made this possible. Big kudos to danhalen1 for creating the first custom recovery for this phone, this truly is a milestone accomplishment for the volt community, I'd also like to thank all the testers for testing everything and even sacrificing their phones, without the teamwork and everybody's help this wouldn't have been possible.

 

[Gendo420]

you can make a full backup without error to the sdcard.

Can you restore the backup?

 

[danhalen1]

Any way to make this bootable from sdcard without computer?could a script be ran at boot to somehow make it work using init d or something?thanks for making this.really good to have a fix if ever in trouble.

I have no idea if it would work. If somebody wants to work on it by all means!

Can you restore the backup?

Have not had a chance to try it yet, my volt it also my work phone.

 

[marcukial]

Yes marcukial, good question! Can this be done without a computer with the init d?

Boot buddy could possibly work.it would run a recovery script at boot.just havent looked close yet.dont even know if it will work on this phone.lol...just throwin it out here.

 

[mjhealy1978]

I still haven't run this and have had a really busy day, but I just wanted to congratulate you all and thank everyone who made this possible. Big kudos to danhalen1 for creating the first custom recovery for this phone, this truly is a milestone accomplishment for the volt community, I'd also like to thank all the testers for testing everything and even sacrificing their phones, without the teamwork and everybody's help this wouldn't have been possible.

Yes I have no computer presently so I can't try this but I'm very grateful to everyone especially danhalen1 for all your work. It's a team effort & I hope to be able to help in any way! This Volt community has been very good to me! Thank you.

I still haven't run this and have had a really busy day, but I just wanted to congratulate you all and thank everyone who made this possible. Big kudos to danhalen1 for creating the first custom recovery for this phone, this truly is a milestone accomplishment for the volt community, I'd also like to thank all the testers for testing everything and even sacrificing their phones, without the teamwork and everybody's help this wouldn't have been possible.

 

[mjhealy1978]

Boot buddy could possibly work.it would run a recovery script at boot.just havent looked close yet.dont even know if it will work on this phone.lol...just throwin it out here.

Not sure just read up on boot buddy a lil bit so we use the image at boot and it should work, hopefully? I'm new so I'm trying to understand how it works! Bear with me please!

 

[donjuro]

Can you upload a update.zip version?

 

[danhalen1]

Can you upload a update.zip version?

My VM build server crashed and burned, so at this point i dont have one anymore. I might see if i can fix it tomorrow, but if thats not possible i will have to create a new one and sync with cm11 source again. Im not in a big hurry to redo all my past work at this point.

Im not sure if the update.zip would even work. I dont think its possible to fix the DTB error in the zip file the same way i fixed it in the .img.

 

[donjuro]

Oh. So they're two completely different files? I was asking because the error I get is secure booting error, and I read that you can boot into recovery and flash the recovery and it should work.

 

[danhalen1]

the .img file has the ramdisk with the kernel and such inside of it. and the update.zip doesn't. I tried running update.zip from within the stock recovery on a extra ext4 formatted sd card before but the stock recovery didnt play nicely. So maybe you can fastboot boot the .img i made, then try flashing the update.zip, which is what you were talking about im pretty sure.
I found the update.zip which im pretty sure was the most recent from what i had compiled. I updated it with the fixed recovery.fstab. Ill pm you the link to test so nobody gets confused.

 

[donjuro]

I'll test it when I wake up again and get more time. I was doing a bit more testing today and found, to be more specific, the error given is boot certification verify, googling it looks like the bootloader is still not unlocked, but I'm not so sure it is locked. I was also able to successfully flash optimized dalvik, flash superuser (clock work superuser) and back up and restore nandroids.

 

[donjuro]

This is what I get when attempting to install update.zip

-- Installing: /sdcard/Download/update.zip
Finding update package...
I:Update location: /sdcard/Download/update.zip
Opening update package...
Installing update...
Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 args
rm: '/etc' is a directory

about to run program [/sbin/busybox] with 4 args
rm: can't remove '/cache/recovery/command': No such file or directory
rm: can't remove '/cache/update.zip': No such file or directory
sh: invalid number 'root'
sh: can't kill pid 3464: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/adbd'
sh: invalid number 'recovery'
sh: can't kill pid 200: No such process
sh: invalid number 'root'
sh: can't kill pid 1936: No such process
sh: invalid number 'R'
sh: invalid number 'grep'
sh: invalid number '/sbin/adbd'
sh: invalid number 'root'
sh: can't kill pid 16128: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/recovery'
sh: can't kill pid 204: No such process
sh: invalid number 'root'
sh: can't kill pid 1936: No such process
sh: invalid number 'S'
sh: invalid number 'grep'
sh: invalid number '/sbin/recovery'
run_program: child exited with status 1
script result was [256]

 

[danhalen1]

This is what I get when attempting to install update.zip

-- Installing: /sdcard/Download/update.zip
Finding update package...
I:Update location: /sdcard/Download/update.zip
Opening update package...
Installing update...
Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 args
rm: '/etc' is a directory

about to run program [/sbin/busybox] with 4 args
rm: can't remove '/cache/recovery/command': No such file or directory
rm: can't remove '/cache/update.zip': No such file or directory
sh: invalid number 'root'
sh: can't kill pid 3464: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/adbd'
sh: invalid number 'recovery'
sh: can't kill pid 200: No such process
sh: invalid number 'root'
sh: can't kill pid 1936: No such process
sh: invalid number 'R'
sh: invalid number 'grep'
sh: invalid number '/sbin/adbd'
sh: invalid number 'root'
sh: can't kill pid 16128: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/recovery'
sh: can't kill pid 204: No such process
sh: invalid number 'root'
sh: can't kill pid 1936: No such process
sh: invalid number 'S'
sh: invalid number 'grep'
sh: invalid number '/sbin/recovery'
run_program: child exited with status 1
script result was [256]

Huh, thanks for posting your log. I will have to setup a vm again to build cm and will try one last build and see what happens here. If it doesnt work, im out of ideas really.

 

[donjuro]

Read this thread?
http://forum.xda-developers.com/xpe...ics-6-1-1-b-1-54-custom-t1912865/post33013867

 

[donjuro]

I also found out there's a write_recovery command but I'm not sure how to use it. If I type the IMG file it just says "no recovery image. Skip."

 

[donjuro]

Also, just for poops and giggles I tried booting the d620 version of cwm via fastboot boot and it booted successfully, however, the screen was upside down and I didn't dare try anything else.
I also tried flashing and booting it and still get a certification verify error