Please answer exactly that question. Is it possible? If so, how is it possible, or should there be no real difference between activated and not activated.
IF the answer is unequivocally "Yes, you can root and mod the Optimus V before activation." then here are some details about my sitch:
BACKGROUND:
I have already rooted and modded 2 LG Optimus V phones. I used the method described by RevolutionRed at this link.
The first time took awhile. The second time, just last week, was very quick. Both were activated first. I modded them both to CyanogenMod. aospCMod-VM670-20110601-signed.zip among others all worked as advertised.
CURRENT SITUATION:
Cannot boot to recovery by any method. ( To finish the Rom installation process)
I get the LG screen, then black "glowing" screen.
Brand new LG Optimus V NOT activated. (and I have no intention of activating it (I already have service on another phone. I am going to use it for development purposes.)
SuperOneClick tried like 100 times never got me root access.
Tried GingerBreak, which appeared to get me half way there, BUT
I still cannot boot into recovery.
I've tried booting into recovery both through Rom Manager and manually (home/down vol/power buttons simultaneously then release at LG splash screen). No difference at all.
If I don't try to boot to recovery the phone boots up fine to 2.2 stock Froyo.
"Root Check" app says that I have root access, however it also reads:
Those "No such file or directory" statements look like a problem.
I can get adb access, but only "$" not "#" root access.
So... is it in need of activation? Could it be some new firmware that resists rooting (since this one is brand new) Did I royally screw something up? Any ideas?
Thanks in advance. Apologies for the long post, but you're supposed to give lots of information, right?
IF the answer is unequivocally "Yes, you can root and mod the Optimus V before activation." then here are some details about my sitch:
BACKGROUND:
I have already rooted and modded 2 LG Optimus V phones. I used the method described by RevolutionRed at this link.
The first time took awhile. The second time, just last week, was very quick. Both were activated first. I modded them both to CyanogenMod. aospCMod-VM670-20110601-signed.zip among others all worked as advertised.
CURRENT SITUATION:
Cannot boot to recovery by any method. ( To finish the Rom installation process)
I get the LG screen, then black "glowing" screen.
Brand new LG Optimus V NOT activated. (and I have no intention of activating it (I already have service on another phone. I am going to use it for development purposes.)
SuperOneClick tried like 100 times never got me root access.
Tried GingerBreak, which appeared to get me half way there, BUT
I still cannot boot into recovery.
I've tried booting into recovery both through Rom Manager and manually (home/down vol/power buttons simultaneously then release at LG splash screen). No difference at all.
If I don't try to boot to recovery the phone boots up fine to 2.2 stock Froyo.
"Root Check" app says that I have root access, however it also reads:
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/
su:
-rwsr-sr-x root root 26264 2011-09-29
23:21 su
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /
system/xbin/sudo:
/system/xbin/sudo: No such file or directory
Root user id:
uid=0(root)
Root group id:
gid=0(root)
Standard su binary location: ls -l /system/bin/
su:
-rwsr-sr-x root root 26264 2011-09-29
23:21 su
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /
system/xbin/sudo:
/system/xbin/sudo: No such file or directory
Root user id:
uid=0(root)
Root group id:
gid=0(root)
Those "No such file or directory" statements look like a problem.
I can get adb access, but only "$" not "#" root access.
So... is it in need of activation? Could it be some new firmware that resists rooting (since this one is brand new) Did I royally screw something up? Any ideas?
Thanks in advance. Apologies for the long post, but you're supposed to give lots of information, right?