[How-to] Guide to Rooting with software version LS670ZVC

Status
Not open for further replies.
ya i edited my post. i'll just hush until i get home tonight and update lol.
 
okay. redid the process...here is how it looks on cmd...

copyofcmd2.jpg
 
OK, I am noticing a few things you're doing that may be causing some issues.

Firstly, "/system/bin/cd" should be simply "cd". Apparently "/system/bin/cd" doesn't exist. O.o

Also, "adb shell" won't work if you are already in a shell. If rageagainstthecage works, it will kick you out of the shell and back to the Windows command prompt.
 
even with just using CD still same issues. and and its looking like rageagainstthecage isnt working...i typed adb shell near the end to show it goes no where.
 
Hmm. OK, I am going to to a nandroid restore to V8, upgrade to V9, upgrade to VC, and root. I will post screenshots of my rooting process.

Could be a little while, so hang in there, OK?

While we're waiting on the updation (yes that is a real word :p), I have one more question for you. Did you upgrade via OTA (regular updates) or with LGMobile update (desktop application)?
 
Last edited:
naw. before updating..i had reverted back to stock. (yeah i know..why...but my answer is why not) lol
 
When you reverted to stock (which is exactly what I did, so I have no idea why this isn't working for you), did you use the nandroid V8 to V9 method?
 
OK. Updating from V9 to VC completed and rooted successfully. Screenshot attached as promised.


Note a few things:

1) When I pushed su and busybox I pushed them to "/sdcard/su" and "/sdcard/busybox" instead of just "/sdcard/"

2) When you "/system/bin/chmod" rageagainstthecage and busybox it says "Unable to chmod /sdcard/whatever: Operation not permitted. It's a bloody liar. The operation completed successfully.

3) When you run "./rageagainstthecage", it will kick you out of the shell and back to the Windows command prompt. This is normal. Let the device sit for a minute or two before continuing.
 
Last edited:
hmm..again nothing happend after ./rageagainsthecage .....okay..think i know whats going on. gonna try this again..
 
I had to do it similarly... but... I had to issue this command:

/system/bin/chmod 777 /sdcard/rage...

(btw, there isn't much point in trying to do a 4777 or 4755 on the first app as you don't have root (the 4xxx is trying to set "setuid" on the file...)

I found that after crashing the update, I had to run all commands with /system/bin/xxx to make them work as the path was no longer right.

(that may have just been me...) this worked pretty straight forward after re-reading those notes a few times...

Now if only I could get the deodexed rom to be happy on my phone... ah well... I'll give it a couple of days...
 
no luck.. have tried everything that i know of..to get passed

rageagainstthecage : permission denied

im not a noob. but damnt lol im missing something. hahaha.
 
no luck.. have tried everything that i know of..to get passed

rageagainstthecage : permission denied

im not a noob. but damnt lol im missing something. hahaha.

I'm going to make a suggestion because just reading over the instruction's theres quite a gap or assumption made right at the beginning which if i had to guess ... you're falling victim to. At no point does it address where to pull the files from in order to get them onto the SD. If i had to guess, are you just mounting, putting them on the SD, then going about the rest of the instructions? Am i close? You can only do this with update.zip

Try this. Put all the files from the optimusroot.zip (attached to post 1) right into the tools folder of the SDK. Remeber MY FOLDER IS CALLED TOOLS, YOURS MAY BE CALLED PLATFORM-TOOLS!!!

Now do the following ...

1) Put update.zip on the root of the SD card
2) Put the files from inside optimusroot.zip inside of the tools folder or platform-tools folder in the sdk
3) cd C:\android\tools (THIS IS GOING TO BE DIFFERENT FOR YOU!!! TYPE YOUR OWN PATH!!! IT MAY BE C:\android-sdk\windows\platform-tools BUT MY POINT IS TYPE YOUR OWN PATH, DONT COPY MINE!!!) :p
4) adb reboot recovery
5) Try to apply the update.zip from the recovery menu option
6) now start right from step 4 of the first post.
 
yeah..ksmith. from the get go. i had the files in platform-tools ..yeah i noticed the gap in the instructions. and the path yeah i got that. and still notta..what im doing right now is using the orig. files from ur orig root thread..lol. trying everything.
 
not sure how i feel to have my method reworded and posted as your own but hey have fun with tech support :)

Edit: I guess i just feel there should be a link back to it or at least 'thanks to zefie for finding this'. But otherwise I am happy you have it in a more user-friendly format. Sorry if I came off as annoyed or mad, because I'm not.

Btw you can safely completely remove step 6.
 
Last edited:
Status
Not open for further replies.