asadullah
Android Enthusiast
Gimme till tomorrow. I'll update to 2.2.1 and try this then I see about getting you what you requested. Will the custom recovery work with 2.2.1 also?
That seems like a stupid question. lol
99.99% sure it will.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Gimme till tomorrow. I'll update to 2.2.1 and try this then I see about getting you what you requested. Will the custom recovery work with 2.2.1 also?
That seems like a stupid question. lol
now you may have to wait several minutes here. Once you get back to command prompt and rage is done go to next step. IF it hangs after a few minutes (more than 3-5 minutes) then do adb kill-server from another (second) command prompt windowCode:adb push rageagainstthecage-arm5.bin /data/local/tmp/ adb shell chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin cd /data/local/tmp ./rageagainstthecage-arm5.bin
Code:adb shell Now you should have a # prompt and you have root.[/QUOTE] I get to this part and when I type adb shell it returns "error: device not found" so I cannot continue. I get no # prompt and adb fails to see my phone. What seem to be happening here is that after rage runs and gets back to the $ prompt, the phone pops up a notification that usb degging is enabled again, but i'm thinking something stops it from connecting, like it's falsely reporting that it's connected when it really isn't. This is why I get device not found. adb will only recognize the phone after it's been rebooted which of course overwites anything that rage has done. Other programs such as LGNPST and CDMAworkshop both see my device after running rage but then again they don't rely on usb debugging to be enabled. I really think LG added something to the Optimus-M 2.2.1 update to block any attempts at all to root the device.
I get to this part and when I type adb shell it returns "error: device not found" so I cannot continue. I get no # prompt and adb fails to see my phone.
What seem to be happening here is that after rage runs and gets back to the $ prompt, the phone pops up a notification that usb degging is enabled again, but i'm thinking something stops it from connecting, like it's falsely reporting that it's connected when it really isn't. This is why I get device not found. adb will only recognize the phone after it's been rebooted which of course overwites anything that rage has done.
Other programs such as LGNPST and CDMAworkshop both see my device after running rage but then again they don't rely on usb debugging to be enabled. I really think LG added something to the Optimus-M 2.2.1 update to block any attempts at all to root the device.
It'd be the same as when I downgraded back to 2.2 the last time I was on 2.2.1. It overwrite everything from the previous version.
Going back to 2.2 now. Everything works on that and I just want my phone to work.
As far as I can see there is no possible way to root this phone once it's on 2.2.1, so making a nandroid backup for this is not going to happen.
In one day we got a custom recovery, OC kernel and a stragefright enabler for 2.2, so why don't we just try to build off that? How about HW accel? That sounds like a good thing to add.
With me being the only one that's even seemed to bother with testing any of this stuff it's becoming an obsession and interfering with my personal life.
Unless someone can come up with a definitive way of rooting The Optimus M while it's on 2.2.1 FRG83, I gotta say the nay no my brothas.
Yes I know it's possible on phones X,Y and Z....I've been through every forum I could find on google dealing with rooting 2.2.1 and this isn't one of those phones.
While I've built computers from scratch, I've never messed with Linux and this is my first smartphone. So, I don't want to brick it. I sincerely thank you for your fearlessness.