Database Develop

Need help with rooting

Hello.
I am having trouble rooting my LG P990.
Android 2.2.2
Kernel 2.6.32.9
Build FRG83G
LGE Version LGP990-V10b
I have tried SuperOneClick 1.7 and the latest version (1.9.1).
Failed after trying to install Busybox.
I have also tried Z4root 1.3
I have also tried the method explained on Cyanogenmod Wiki
http://wiki.cyanogenmod.com/index.php?title=LG_Optimus_2X:_Rooting
and have gotten stuck at the command
/data/local/busybox cp /data/local/su /system/xbin/su
I am returned this error:
can't stat '/system/xbin/su': Not a directory
So yes. I have checked other threads. Does anyone have any good ideas on what I should do next to get this phone "permanently" rooted?

vitaminxero said:
Hello.
I am having trouble rooting my LG P990.
Android 2.2.2
Kernel 2.6.32.9
Build FRG83G
LGE Version LGP990-V10b
I have tried SuperOneClick 1.7 and the latest version (1.9.1).
Failed after trying to install Busybox.
I have also tried Z4root 1.3
I have also tried the method explained on Cyanogenmod Wiki
http://wiki.cyanogenmod.com/index.php?title=LG_Optimus_2X:_Rooting
and have gotten stuck at the command
/data/local/busybox cp /data/local/su /system/xbin/su
I am returned this error:
can't stat '/system/xbin/su': Not a directory
So yes. I have checked other threads. Does anyone have any good ideas on what I should do next to get this phone "permanently" rooted?
Click to expand...
Click to collapse
Try installing Pauls clockwork. No preroot required, it uses psneuter to create root. After that push busybox and superuser.
Sent from my LG-P990 using XDA Premium App

SuperOneClick also uses the psneuter exploit, so if one works, they all should.
I use SOC v1.9.1 yesterday on my phone (as I briefly reverted to stock for some testing), and it worked first time.

Rusty! said:
SuperOneClick also uses the psneuter exploit, so if one works, they all should.
I use SOC v1.9.1 yesterday on my phone (as I briefly reverted to stock for some testing), and it worked first time.
Click to expand...
Click to collapse
Well, he does not state that the exploit dont work..
I have never had problems with soc either..
Sent from my LG-P990 using XDA Premium App

reidar.ostrem said:
Well, he does not state that the exploit dont work..
I have never had problems with soc either..
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
PSneuter roots successfully but the entire thing fails when i cannot seem to install busybox
Checking for busybox
Copying busybox (/system/xbin/)...
cp: can't stat '/system/xbin/busybox': Not a directory
OK
chmod busybox (/system/xbin/)...
Unable to chmod /system/xbin/busybox: Not a directory
OK
Installing busybox (/system/xbin/)...
/system/xbin/busybox: not found
FAILED

vitaminxero said:
PSneuter roots successfully but the entire thing fails when i cannot seem to install busybox
Checking for busybox
Copying busybox (/system/xbin/)...
cp: can't stat '/system/xbin/busybox': Not a directory
OK
chmod busybox (/system/xbin/)...
Unable to chmod /system/xbin/busybox: Not a directory
OK
Installing busybox (/system/xbin/)...
/system/xbin/busybox: not found
FAILED
Click to expand...
Click to collapse
Well, have you tried installing busybox any other way? If you are not comfortable with adb, i think you can install busybox from titanium and see if titanium gets root at the same time ...

Skipped the whole thing and used CWM. =P
Used Paul's CWM. Replaced the .img with one for cyanogen.
Followed the rest of the steps here: http://wiki.cyanogenmod.com/index.php?title=LG_Optimus_2X:_Recovery_and_CyanogenMod
Now running CM7.1Nightly10

vitaminxero said:
Skipped the whole thing and used CWM. =P
Used Paul's CWM. Replaced the .img with one for cyanogen.
Followed the rest of the steps here: http://wiki.cyanogenmod.com/index.php?title=LG_Optimus_2X:_Recovery_and_CyanogenMod
Now running CM7.1Nightly10
Click to expand...
Click to collapse
Good to hear ! Glad it worked out for you.

[Q] Rooting TELUS Optimus Black

Anyone figured out how to do it? I've tried following the guides with no success (gingerbreak). Model is P970g and software is 10a. Country code is TLS.
Anyone have a Telus OB and been able to root it? How did you do it?

I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck

alexredford said:
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
Click to expand...
Click to collapse
I tried both z4 and the superoneclick you suggested to no avail.
Do you think it's safe to try flashing another vulnerable rom? 10b or 10c? I'm worried the basebands may be different and the phone will have no voice/data connection.
Running out of ideas.

Attempted to root another one, same model, same version and none of the previous methods worked, was able to root this one as well using a combination of SOC 2.1.1 and the attached ADB Shell.
1. Download and run SuperOneClick 2.1.1, choose psneuter and click Shell Root
2. It should get stuck on step #4, run task manager, end superoneclick and terminate any adb.exe processes. (You should have Shell Root now)
3. Extract ADB.zip and open a command prompt to where you extracted it.
4. Enter the following commands
Code:
adb push su /tmp/
adb push Superuser.apk /tmp/
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
The permissions on /system/bin/su didn't stick the first time for me, and the phone rebooted a couple times, but eventually it all went through. To verify permissions on su, type "adb shell", then "ls -l /system/bin/su". The permission should read -rwsr-sr-x, if it doesn't repeat the shell root process and type
Code:
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
chmod 06755 /system/bin/su
ls -l /system/bin/su

Ok, i've figured out what the problem is. As soon as the adb process from SOC is shut down, the phone soft reboots and I lose temporary root. I've tried the psneuter exploit in the same adb command shell, but it hangs just like SOC. I've tried to be "quick" and get the commands in before the reboot, but it isn't possible.
Suggestions on how I may bypass that? Otherwise i'll wait for the official 2.3 update in september and try again then.

One of the phones I tried it on, did the same thing, ended the adb process and phone would reboot, pushed a file, phone would reboot, set permissions, phone would reboot. Occasionally the phone would appear to hang, buttons flash at the bottom for awhile, phone becomes unresponsive. Just wait a minute or 2 and it should return to normal. I also tried creating a script to do all of the above before the device had time to reboot and it didn't help.
Persistence was the key.

Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium

Hey i am having the same problem and am fearing bricking my phone from making a mistake. is there an easier method than those above mentioned?
Android 2.2.2
software: v10a

Sobralobo said:
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
This method worked when rooting my wife's P970g.

KDZ file
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)

s0dhi said:
This method worked when rooting my wife's P970g.
Click to expand...
Click to collapse
...which ROM did you use, the v10a EEU from the thread?
I'm worried cause on Telus 970g as well.

The_non_rootable said:
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=1

[Outdated, New Tool Created] Disable & Remove CIQ After Bootloader Unlock

!!!!UPDATE!!!
I have created a tool that makes this process 100% easier!
http://forum.xda-developers.com/showpost.php?p=21566003&postcount=1
Proceed to use the following manual guide as reference but I suggest using the tool I created for an easier experience.
=======================================================================
First if you havent already, Unlock the Vivid Bootloader on HTCdev.com!
>>>>>Follow These directions step by step dont rush or skip any steps. Take your time with this removal. It involves deleting certain files from the system folder!<<<<<
***You need root, Look for ZERGRUSH's root method on the forums***
Update the root SU binary! ( can be done in the superuser settings menu )
Go to the marketplace and look for NoBloat Free
***Look for two entries***
HtcIQAgent (com.htc.android.iqagent)
IQRD (com.htc.android.iqrd)
Click to expand...
Click to collapse
Remove them or Backup and Remove them
Go to your terminal
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd system/bin
rm iqd
rm iqfd
cd system/lib
rm libhtciqagent.so
rm libciq_client.so
rm libciq_htc.so
cd system/etc
rm iqprofile.pro
Click to expand...
Click to collapse
close your terminal session
reboot
Enjoy!
Update : This seems to be complete for now, all CIQ libraries and apps removed. Supercurios CIQ app detects that only the log remains, its useless but you can delete this too. thanks khhawkins for opening up my eyes to something i blinked over.
Update #2: You will detect two linux kernel drivers t__param_str_ciq_info & t__param_ciq_info, these two load up from the stock kernel and cant do anything after CIQ has been removed. This is normal and you will not see CIQ resurface on your device
Update #3: If youre score is 150 on Supercurios CIQ detector app you are clear!
Update #4: Dont skip any steps!
RIP CIQ on the Vivid....

What about /system/bin/iqfd? Is that related too?
Thanks for this
Sent from my HTC PH39100 using xda premium

kxhawkins said:
What about /system/bin/iqfd? Is that related too?
Thanks for this
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
According to supercurios app for detecting CIQ, the IQD file in /system/bin remains after deletion of the main CIQ files. Youll see in the logcat regarding CIQ "Unable to start service Intent", after you killed the two main running apps. There are two linux drivers that stop running after you ill iqd. But even if they are on, they are basically stranded, youre CIQ free either way.
Thanks for pointing this out KHhawkins, Im updating the post to instruct how to remove the iqd file and the iqfd file

Mission Accomplished

I have searched for Zergrushs root but haven't had any luck. Can some one post the link?

capman231 said:
I have searched for Zergrushs root but haven't had any luck. Can some one post the link?
Click to expand...
Click to collapse
Search for the HTC supertool

there also happens to be an entry in /system/build.prop
ro.ril.ciq=1
dont know if changing it to 0 would have any effect.

Pirateghost said:
there also happens to be an entry in /system/build.prop
ro.ril.ciq=1
dont know if changing it to 0 would have any effect.
Click to expand...
Click to collapse
No effect, I see no more ciq activity on logcat. I wanted to tinker with the build.prop file and initially remove it, but its an unnecessary step. Similar to the orphaned kernel drivers
Sent from my HTC PH39100 using xda premium

My device has no system\pro directory at all.
Otherwise the only discrepancy I found was the file htciqagent.so was also libhtciqagent.so.
---------- Post added at 03:07 PM ---------- Previous post was at 02:44 PM ----------
FYI - My Voodoo CarrierIQ score is 150 after following your directions. The applicaiton labeled my device as "Carrier IQ elements found - however it seems inactive".

ifiweresolucky said:
My device has no system\pro directory at all...
Click to expand...
Click to collapse
Before
Code:
cd system\pro
rm iqprofile.pro
Issue:
Code:
find / -name iqprofile.pro
to locate the iqprofile.pro file.
Then, "cd" to that location, and issue
Code:
rm iqprofile.pro

Thanks, was in system\etc\

Fixed all entries

Any performance increase after removing CIQ?

ifiweresolucky said:
My device has no system\pro directory at all.
Otherwise the only discrepancy I found was the file htciqagent.so was also libhtciqagent.so.
---------- Post added at 03:07 PM ---------- Previous post was at 02:44 PM ----------
FYI - My Voodoo CarrierIQ score is 150 after following your directions. The applicaiton labeled my device as "Carrier IQ elements found - however it seems inactive".
Click to expand...
Click to collapse
Youre in the clear, the last "150" come from the linux kernel drivers which are actually part of the kernel.

Okay. Noob question here. When you say go to terminal. What does that mean? Terminal emulator on the phone? Or a terminal on the PC? And if on the PC what do I use?
I have unlocked the bootloader

He means a DOS prompt (Windows) or terminal window (Linux). Then navigate to where you have ADB (assuming you dont have environmental variables set up) and execute the commands.

backtothemac said:
Okay. Noob question here. When you say go to terminal. What does that mean? Terminal emulator on the phone? Or a terminal on the PC? And if on the PC what do I use?
I have unlocked the bootloader
Click to expand...
Click to collapse
On your Mac use the terminal app with adb. On a PC use command prompt with adb.
Sent from my HTC PH39100 using xda premium

I am missing something. I can open the shell. Enter SU and then then next step in the process fails. I am close. lol

backtothemac said:
I am missing something. I can open the shell. Enter SU and then then next step in the process fails. I am close. lol
Click to expand...
Click to collapse
Root first!

I did. I am missing something small I am sure. But I am definitely missing it.

finally got rooted on jb only took me 11 days

guys I finally have been able to root mu atrix hd on jb . this is what worked for me http://forum.xda-developers.com/showthread.php?p=35905543#post35905543

Did you have partial root previously? If you didn't, a new thread was warranted. If you had partial root, why create a new thread?

After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app. i was only able to invoke a root prompt. i looked all over the internet not just the xda forums. i tried mattigriffs root restore. i typed into a command prompt for several hours each day.. all i ever got was a root prompt in adb shell. no prompt on the phone emulator. this is the only page that has worked for me. i noticed right away that the code was written differently than any other that i tried. also the su used is different(it is described as wide open) any way because of this i felt that others who were /are in the same boat. no root. may be able to get root back. I hope that answers your question. have a great day! .

Simple yes or no would have worked. I was hoping that by chance someone was stating that they didn't have root previously and were able to obtain root using this method.

Someone tested if it works on 4.1.1 official without prior recovery Boodoo ota?
Sent from my MB886 using xda premium

ashraf sharif said:
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app.
Click to expand...
Click to collapse
Thats what happened to me as well

Would this work if i havent rooted my device prior tho official jb update
Sent from my MB886 using xda premium

My question too any idea
Sent from my MB886 using xda premium

sickkside13 said:
Would this work if i havent rooted my device prior tho official jb update
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
If I wasn't at work I would try it.

Lol me 2. I bought the phone online but it already came with jb i didnt knew the bootloader was locked .
Sent from my MB886 using xda premium

I think what that is fake
Sent from my MB886 using xda premium

i am no expert. and from my reading the forums. the consensus is that if you lost root after the upgrade then you have a chance of regaining it. this method was not meant as a root for atrix hd. but it worked for me. one thing that helps is the abilithy to invoke a root prompt in adb shell. i had a su-backup in /system/usr/we-need-root. ,/su-backup; su i was able to achieve shell root only until today. the the commands used are not identical to the ones i have tried for the past 11 days and the su used is described as 'wide open' whatever that means. Another thing i noticed was that the instructions said to download the su from the play store and update the binary while still in adb shell. , instead of rebooting. when i did this the binary finally gained root.I tried alot of methods none worked except for this one.i was not expecting this to work but it did. I dont know why. all i know is it worked for me. if you choose to try this . best of luck and i sincerely hope it works for you too.

This is gonna sound dumb but, how do I "log in to ADB" (Step 2)? I got the same problem u had and am trying to figure this method out.
Sent from my MB886 using xda premium

i got the shell prompt working with these commands found on this page http://forum.xda-developers.com/showthread.php?t=1911261
Code:
adb shell:
$ cd /system/usr/we-need-root
$./su-backup; su (that is a semicolon immediately after the ./su-backup)
# mount -o remount,rw /system
(do what needs to be done)
#exit
... su-backup must have permissions as such: (get permissions by typing this into adb shell: ls -l /system/usr/we-need-root ) If you get an error, than this specifically won't work for you.
Code:
Required su-backup permissions for manual root restore
$ ls -l /system/usr/we-need-root/su-backup
-rwsr-sr-x root ... basically, if you can find a su-backup with proper permissions (and cannot restore root with voodoo or supersu), you can manually use that to repair your root access configuration. Maybe this is well known... but to those who don't this could be useful.
Thanks

Man, I cannot figure this out for some reason.
Sent from my MB886 using xda premium

logging in to adb
cmdru1980 said:
This is gonna sound dumb but, how do I "log in to ADB" (Step 2)? I got the same problem u had and am trying to figure this method out.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
download java developement kit and android sdk
the sdk has a section called tools where you will find fastboot and adb unzip the files and install the drivers.your first cmd will be cd or'change directory" to wherever the adb folder is. then type adb shell. this should restart the daemon. good luck

This is what I get.
Sent from my MB886 using xda premium

Thank you, Ashraf! I think I got it. I really appreciate it!
Sent from my MB886 using xda premium

I am confused
Sent from my MB886 using xda app-developers app

adolfo778 said:
I am confused
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'm confused now as well. If the people here did not have partial root to begin with and were running stock Jelly Bean firmware and then went through these steps to get root access, this needs to be made more clear. If these are users that already had root access from a previous attempt but temporarily lost it during the upgrade process, that should be clarified and merged over into another thread and perhaps edited into the first post.

[Q] adb with root rights

Hello
Is there a solution to have adb with root access with a stock kernel ?
Or the only way is to unlock the bootloader and flash an alternative kernel ?
Thanks.

Adb can access stock ROM with root rights on stock kernel.
Just type "adb su" and you'll get prompt to allow superuser access to your device. But you should be rooted in order to do this.
And having unlocked Bootloader is very necessary to flash custom kernel
Sent from my C5302 using XDA Free mobile app

My bad, I forgot that.
I was trying using "adb root" and it answers something like impossible.
Thanks !

No problem
Always there to help
Sent from my C5302 using XDA Free mobile app

To fully use the adb root function on your device it has to be rooted;
So when rooted just enter the following commands:
Adb shell >enter<
Su >enter<
- A SuperUser prompt will appear on your device press approve or ok or whatever
And you can now use adb with your phone and root rights
~~ Regards

mrjraider said:
To fully use the adb root function on your device it has to be rooted;
So when rooted just enter the following commands:
Adb shell >enter<
Su >enter<
- A SuperUser prompt will appear on your device press approve or ok or whatever
And you can now use adb with your phone and root rights
~~ Regards
Click to expand...
Click to collapse
No. Even running a shell as root I continue with:
- adb root : "adbd cannot run as root in production builds"
- adb push xxxx /system/xxxx : failed to copy 'xxxx' to '/system/xxxxx': Permission denied
I think the only way to do that is to have a rooted kernel.

Last one is because /system is Read-Only
~~ Regards

mrjraider said:
Last one is because /system is Read-Only
~~ Regards
Click to expand...
Click to collapse
Nope ...
it's rw, verified ...

oh it is RW protected ofcourse
~~ Regards

mrjraider said:
oh it is RW protected ofcourse
~~ Regards
Click to expand...
Click to collapse
? rw protected ?

Without proper root you cannot push files to /system.
I even had issues with adb pull /system
To be honest I have no idea.
~~ Regards