• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROOT KIT] OPTIMUS M 2.2.2 (Dummy-proof-3-click)

Okay, I've done this twice now and each time it says:
Code: 
Installing persistent root... install-root.sh: cannot create /system/xbin/busybo
x: directory nonexistent
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Done

What's that mean?

I can use J Pal's terminal emulator, get su status, and CD to /system, but there's no xbin directory in /system. And I tried "mkdir xbin" but file system is read only in terminal emulator.
Maybe the script should use "bin" instead of "xbin"? Just wondering as I do have a "bin" directory.


Uninstalling shows:

Code: 
Getting ready to
 
  UNINSTALL persistent root (UNROOT)
 
Please verify ALL of the following:
  SD card is INSERTED
  USB Debugging is ENABLED
  USB Storage Mode is DISABLED
  LG USB/Android drivers are INSTALLED
  Phone is connected to USB port and recognized
Press any key to continue . . .
----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Proceeding with install
----
Asking for root permissions...
  Please turn ON phone and EXIT the lock screen
AFTER you press any key to continue, if you are PROPERLY ROOTED, you
MAY see a PROMPT asking for permissions.  Please ALLOW root access.
Press any key to continue . . .
---- BEGIN LOG ----
...Proceeding to copy necessary files...
push: copy2sd/000root/xionia_cwma_12518.6.img -> /sdcard/000root/xionia_cwma_125
18.6.img
push: copy2sd/000root/Superuser.apk -> /sdcard/000root/Superuser.apk
push: copy2sd/000root/su -> /sdcard/000root/su
push: copy2sd/000root/recovery_vd.img -> /sdcard/000root/recovery_vd.img
push: copy2sd/000root/install-xionia.sh -> /sdcard/000root/install-xionia.sh
push: copy2sd/000root/install-vd.sh -> /sdcard/000root/install-vd.sh
push: copy2sd/000root/install-unroot.sh -> /sdcard/000root/install-unroot.sh
push: copy2sd/000root/install-root.sh -> /sdcard/000root/install-root.sh
push: copy2sd/000root/install-cleanup.sh -> /sdcard/000root/install-cleanup.sh
push: copy2sd/000root/flash_image -> /sdcard/000root/flash_image
push: copy2sd/000root/busybox -> /sdcard/000root/busybox
11 files pushed. 0 files skipped.
1883 KB/s (12815963 bytes in 6.645s)
----
Installing stock VD recovery... error writing recovery: No space left on device
Done
Uninstalling persistent root... Done
Waiting for filesystem to sync... Done
---- END LOG ----
Check for any errors.  Assuming there are none, the UNROOT was successful.
----
Getting ready to reboot...
Press any key to continue . . .

And I'm worried about the "Installing stock VD recovery...: No space left on device" error.
 
abecede said:
Okay, I've done this twice now and each time it says:
Code: 
Installing persistent root... install-root.sh: cannot create /system/xbin/busybo
x: directory nonexistent
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Done

What's that mean?

I can use J Pal's terminal emulator, get su status, and CD to /system, but there's no xbin directory in /system. And I tried "mkdir xbin" but file system is read only in terminal emulator.
Maybe the script should use "bin" instead of "xbin"? Just wondering as I do have a "bin" directory.


Uninstalling shows:

Code: 
Getting ready to
 
  UNINSTALL persistent root (UNROOT)
 
Please verify ALL of the following:
  SD card is INSERTED
  USB Debugging is ENABLED
  USB Storage Mode is DISABLED
  LG USB/Android drivers are INSTALLED
  Phone is connected to USB port and recognized
Press any key to continue . . .
----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Proceeding with install
----
Asking for root permissions...
  Please turn ON phone and EXIT the lock screen
AFTER you press any key to continue, if you are PROPERLY ROOTED, you
MAY see a PROMPT asking for permissions.  Please ALLOW root access.
Press any key to continue . . .
---- BEGIN LOG ----
...Proceeding to copy necessary files...
push: copy2sd/000root/xionia_cwma_12518.6.img -> /sdcard/000root/xionia_cwma_125
18.6.img
push: copy2sd/000root/Superuser.apk -> /sdcard/000root/Superuser.apk
push: copy2sd/000root/su -> /sdcard/000root/su
push: copy2sd/000root/recovery_vd.img -> /sdcard/000root/recovery_vd.img
push: copy2sd/000root/install-xionia.sh -> /sdcard/000root/install-xionia.sh
push: copy2sd/000root/install-vd.sh -> /sdcard/000root/install-vd.sh
push: copy2sd/000root/install-unroot.sh -> /sdcard/000root/install-unroot.sh
push: copy2sd/000root/install-root.sh -> /sdcard/000root/install-root.sh
push: copy2sd/000root/install-cleanup.sh -> /sdcard/000root/install-cleanup.sh
push: copy2sd/000root/flash_image -> /sdcard/000root/flash_image
push: copy2sd/000root/busybox -> /sdcard/000root/busybox
11 files pushed. 0 files skipped.
1883 KB/s (12815963 bytes in 6.645s)
----
Installing stock VD recovery... error writing recovery: No space left on device
Done
Uninstalling persistent root... Done
Waiting for filesystem to sync... Done
---- END LOG ----
Check for any errors.  Assuming there are none, the UNROOT was successful.
----
Getting ready to reboot...
Press any key to continue . . .

And I'm worried about the "Installing stock VD recovery...: No space left on device" error.
Click to expand...


Sounds to me you didn't make sure everything was done on the phone before trying it. When first starting it,it tells u,make sure USB debugging is on,SD card mounted etc. Make sure you did EVERYTHING it said to do and try again.
 
Okay, I started the install again, using "A" as my option, and got the error again, but used terminal emulator, did "SU" in it, then typed in:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mkdir xbin

So now I have the xbin directory, and re-running the "runfirst.bat" - option "A", from the "one-click" root didn't show the error for busybox.

Good? Who knows. ;)
 
mikekelso421 said:
Sounds to me you didn't make sure everything was done on the phone before trying it. When first starting it,it tells u,make sure USB debugging is on,SD card mounted etc. Make sure you did EVERYTHING it said to do and try again.
Click to expand...

Honest, I did. SD card mounted, USB debugging enabled, not on the lock screen- I changed the setting to make sure it didn't go to the lock screen and to "sleep" and verified it wasn't on the lock screen when I started the process.

I made some process, as evident by the post above this.
 
Ok i downloaded but when i open it it says no application can perform this task, ..........now i did try to downgrade this phone in patticular at one point and i kept getting usb dongle not detected
 
followed the video step by step but when I run the root kit (RUNFIRST.bat) and I type in "a" as soon as I enter the root kit screen just disappears and nothing happens...just closes the window. Storage mode not on. Debugging IS enabled. Any suggestions? Guess its not totally dummy proof...LOL

EDIT: OK. I am getting an error message when it closes. It happens so fast I didnt catch it at first so I had to video the process and play it back in order to read it.
(error message)
install-auto.bat is not recognized as an internal or external command operable program or batch file

Hopefully that will be of some help to someone in getting me through this.

PROMBLEM RESOLVED...THANKS
 
followed all the instructions (multiple times) and the program is still stuck on "waiting for device to be connected"

please help
 
make sure device is pluged in and usb debug is enabled also make sure drivers are installed make sure your phone is unlocked on not on the lock screen
 
I found this to be incredibly simple and followed it step by step. After the reboot however, SU did not appear! I then turned on storage mode and saw "000root" was installed on my SD card. I tried to access the recovery menu and completely wiped my phone -.-

Please help!
 
First let me say thank you for coming up with a root method for 2.2.2. It was easy to do, very fast and worked great. You guys did amazing work. I do have a problem though. I used root uninstaller as usual and deleted the bloatware, without a problem, the only thing is, while the apps are deleted or at least the phone tells me they are, the memory hasn't been freed up and I'm still in the same situation I was before. Please help! Thanks in advance!
 
bigdroo said:
when i start up the root kit it says for optimus s. but it should work for the om right?
Click to expand...

Yeah it will work. It was originally for the OS, but I figured it might work on the OM....and it did! :D So I posted my findings. Have a happy rooting.
 
ok i got it to go thru with it but when it rebooted there was no superuser in there

update: nvm. did it again and it showed up this time. so if it doesnt show on first try and it should be there for anybody whose confused.
 
My phone rooted successfully but when i went into recovery it was still at the stock recovery. Did i do something wrong or missed a step???
 
I have a problem .
When I get to the "RunFirst.Bat" whatever, I do the options thing, make sure everything that has to be enabled is enabled & what is not is not. All that good stuff. I plug in my phone, and I guess it doesn't find my phone or anything because it doesn't root. It just stays on 'Waiting for device to be connected. [press Ctrl-C to cancel]... All those codes in the video never show up. And if they do show up later on why did it take so long for me and not for the guy in the video? Anyways the screen still says 'Waiting for device to be connected. [press Ctrl-C to cancel]... Nothing has happened, why? I must be more than a dummy :confused: :(
 
I successfully flashed my Optimus M with Reppards and BOBZ version of CM7. The problem I found with CM7 is the signal strength (or weakness) that comes with it, and MMS doesn't work. Before I flashed - 3/4 bars. After- 0-1/4 if I'm lucky. Does anybody know if baseband file has something to do with this? I'm running K3lsoMod 2.2 ROM (Highly recommended) and my phone couldn't be any happier. BUT, I want Gingerbread!! :(
 
The problem is that LG hasn't released an official gb from for you. So its up to the awesome devs to either port it from another optimus version like the v or s or try to build from source. Its a very rough task to do. And it takes days and days of tweaking to get it right. So froyo it is for now.
 
You must log in or register to reply here.
Back
Top Bottom