The "#" sign means you have root.what, i updated it and it went back to stock rom and its not rooted anymore
cd /
ls -l
cd system
ls -l
cd bin
ls -l
Your /system is not mounted which is why you are having trouble with the instructions. You are running a custom rom when the instructions expect you to be running the stock rom.
mount -o rw -t yaffs2 /dev/block/mtdblock5 /system
cd /system
ls -l
cd bin
ls -l
My phone came with ZVC installed on it. Will this method work? With the repeated warnings of "if you didn't use the LGMobile update tool to get to ZVC, this will not work" make me nervous to try it...
My point was, I did not accept the OTA update, do I still need to revert to v9? The big red letters do not describe what to do when the phone comes with VC installed already.
Thanks for the assistance.
You need to revert to V9 first per the RED section of the original post.At step 10 when i try to Fire up the shell (again) it says
C:\Program Files\Android\android-sdk\platform-tools>adb shell
error: device not found
Don't know what is up with getting stuck, but to become root in adb shell, turn on the phone, make sure you aren't in the lock screen, type "su" in adb shell, look on the phone for a prompt asking for root privileges, and accept the prompt.I followed the VC rooting process successfully a few weeks ago, and have been enjoying the root privileges. I wanted to adb shell into my phone today, and I got the $ prompt, and running 'su' came back with permission denied. Then an adb reboot got me stuck at the LG screen, but was fixed by popping the battery.
My question is, how do I get the # prompt when running adb shell? And it seems that I can repeat getting stuck at the LG screen. Any ideas as to what is wrong?
rageagainstthecage depends on a race condition. It doesn't always hit gold. You may have to try many attempts before it works. Sometimes sprinkling in an "adb kill-server", rebooting the phone, and rebooting the PC help alter the timings to be more favorable, but again, it is a race condition. You aren't racing Usain Bolt, but more likely the best athlete in your cafeteria. Sometimes you might win, but many times you'll lose.I'm on a MacBook here having some problems with this procedure:
![]()
Things go according to plan, step 8 doesn't work, then in step 9 I only notice the phone disconnecting and reconnecting once. I gave it a couple minutes to make sure, but it still only reconnected once so far as I could tell. It kicks me out of shell. I get back in and I'm still stuck in $$$$$. :-\
Any ideas?