Database Develop

Temp root for apps required root access (for s-on IS)

Psneuter exploit is working on IS, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Unzip the attached .zip into a directory (like c:\adb)
2. Open a command prompt and cd to the directory where you extracted the .zip (like cd \adb)
3. run pushroot.bat (simply type pushroot)
4. adb shell /data/local/tmp/getroot
5. adb shell
6. you are now in # prompt. Type /data/local/tmp/pushroot
You have to redo steps 4,5,6 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.

Nice but old news mate...
Sent from my HTC Incredible S using XDA Premium App

Good job...thanks

Thanks for writing this up, might quell the thirst for S-OFF a little longer

/system/ is writeable btw, if you remount it, but after reboot everything u done will be changed to the way it were before.
so a temp root in xbin is possible also, only it will be gone afterwards (atleast i never tried this, but should work also...)

Yes. /system could be remount in rw with root. However, the files you wrote will be gone after you remount ro, and then you won't be able to copy the same filename into the same location again before next reboot ( I don't know why, actually!!). This is why I put su in sbin instead of /system/xbin.

thanks to your files 非常感谢你的工作。

Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?

faf said:
Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?
Click to expand...
Click to collapse
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk

pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....

itandy said:
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Definitely, this is the way to go.
Unfortunately, the root exploit I know could run on device itself, including
rageagainstthecage (ratc) and local root exploit (hotplug) both failed on IS.
The solution will be nearly perfect if we can get temp root on IS without a computer link.
Any input will be welcome.

sky1212 said:
pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....
Click to expand...
Click to collapse
Please then type adb shell.
If you see # but not $, do
cd /data/local/tmp
rm ./cp
ln busybox cp
./pushroot
Then you finished the install.
If you see $, please do all over again.

You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work

l0st.prophet said:
You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work
Click to expand...
Click to collapse
Adfree is working for me. Are you getting some type of error message?
MetaMorph, screenshot and MyBackup Root are also working.
I had to mount system, then push su to /system/xbin. Then install BusyBox Installer from Market.

No erro, still got the ads. I've tried rebooting & rerooting, still no luck

l0st.prophet said:
No erro, still got the ads. I've tried rebooting & rerooting, still no luck
Click to expand...
Click to collapse
What site/app are you going to so I can see if I get the ads.

the anti-ads actually tries to modify the current host file... which is not allowed in your state as far as i know
what you can do is replace it by pushin it to the right spot
but after reboot gone,but sure u know

Adfee is working for me, you can also add Droidwall.

@eddycyf, did you test adfree with apps? Since it aint working for prophet...
Sent from my HTC Incredible S using XDA Premium App

Mhm AdFree isnt working for me. The App states that everything is okay, and that my hosts file is up to date, but I see ads everywhere.
But I am kinda happy now, because i can use Titanium Backup

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.

[HOWTO] Root HKTW 2.3.4 - The easier way

I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
Click to expand...
Click to collapse
3. Then, type and press enter:
su
Click to expand...
Click to collapse
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
Click to expand...
Click to collapse
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!

Will try and report if it works or not
Sent from my MB860 using XDA App

Well I know I shouldn't say it here...
But is the HKTW rom blurred or blurless?

Different kind of blur but its still blur
Sent from my MB860 using XDA App

Do you mean Blur 4.5?

I don't know what its called lol
Sent from my MB860 using XDA App

Trying it out now. Will report back.
And this has Blur on it. It's not a custom ROM.

Anyone else experiencing issues getting their phone recognize by adb
Sent from my Atrix 4g Ubl 2.3.4

su is throwing me a permission denied
http://pastebin.com/brXVEYDb

i guess i didn't phrase the instruction clearly. sorry. just edited first post.. reread everything and try again.

had to run it a few times.. but it worked! thx!

Works! 10char

reserved *10chars

su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.

jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
having the same issue with SU

Are there any other alternatives to root currently?

jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
Can you be more specifically on those files? Where to download and how exactly did you go about running those files?

Do I need the SDK for rooting it?

THIS WORKS ON WINDOWS, OSX, AND LINUX
once you type in adb shell then type dosu instead of su and see if that helps

I get an error at the last part when I put it in cmd
Whenever I type in 'su', I get permission denied - and dosu doesn't work either.

[TOOL] Perma-Temp-Root Solution [Mac/Linux/Windows]

Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
Its stable & works 100%
I personally have not lost root with this method in over 48 hours.
Zero com.noshufou.android.su crashes.
Before Using!!
HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
Restart your phone!
Lastly, if you're getting com.noshufou.android.su force close errors
Uninstall superuser prior to running scripts.​
If you Lose Root, all you have to do is open Terminal Emulator & type fixsu
No More Rebooting & running the exploit again for R/W on system to get Root back in place!​
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal and type fixsu to get root back.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot.
Q. Can I push & remove items to system and will it work?
A. Yes, but all changes are reset on a reboot.
~~~~~~~~~
For Mac/Linux users
Once downloaded, extract vividtemproot.zip to your home/root folder.
(Typically named after your login, has a house icon in Finder's sidebar of places)
Open folder vividtemproot, double-click run_me_mac (or run_me_linux)
and thats is all!
Click here to download for Mac/Linux
(Updated 11/14 - 23:50)
~~~~~~~~~
For Windows Users
Once downloaded, extract where ever you please.
Double click _RUN_ME
and enjoy!
Click here to download for Windows
(Updated 11/14 - 23:50)​

Link for Windows is the Mac file...

CharlieMurphyIVXX said:
Link for Windows is the Mac file...
Click to expand...
Click to collapse
Thank you :]
Fixed

Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!

thecubed said:
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
Click to expand...
Click to collapse
I haven't lost root in going on ~60 hours, as as a newbie here, you definitely know far more than I do!
As you'll see in the fixsu, I redundantly copy su from /vendor/bin
to /system/xbin/ from which I hardlink (as you'd know is virtually the same as bind mounting in this case) to /system/bin
I added the fixsu, as a last resort, in case the something would dissolve, but unless someone really fudges something up, the fixsu shouldn't be needed
As my programming teacher once told me: the code doesn't need to be pretty as long as it works.
And through that philosophy I've used a lot of redundancies, that may or may not need to be there,
but they'll definitely keep anyone from having any sort of issues using the scripts!
P.S. Thank you :]

Thanks, I'll try this out and report back.
Sent from my HTC PH39100 using xda premium

It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!

http://pastebin.com/MkGHWadW
appears to have failed for me
Drew

The device rebooted itself -- the "root" is lost

guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .

rinnycoop121 said:
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
Click to expand...
Click to collapse
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!

drewdatrip said:
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
Click to expand...
Click to collapse
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.

3f62011 said:
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
Click to expand...
Click to collapse
I don't own a Windows box, an had to write the Windows bat file
without giving it a test run for errors.
I'm sure I did mess up the syntax, an probably left some command that isn't windows relavent at the end of the script.
No worries, you've got root, and shouldn't loose it.

bjg222 said:
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
Click to expand...
Click to collapse
I tried to pipe all errors out to null, as I took a mash up of your code, my code, and and another guys code, and left a lot of "in case it exists" type of lines in the code, to make sure no one would have any issues.
Apparently I didn't pipe it all to null well enough
The mac/linux version you only see 'starting' and 'finished' haha

rpendrick said:
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
Click to expand...
Click to collapse
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium

drewdatrip said:
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.

rpendrick said:
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
Click to expand...
Click to collapse
Yes, works much better with something in the folder.

Scrog said:
Yes, works much better with something in the folder.
Click to expand...
Click to collapse
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium

drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I was able to update superuser, but titanium back up doesn't see either SD card.

drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Superuser crashes when it is the lastest versions.
Do a google search for superuser.apk 3.0
I thought I included it in the package, but perhaps, once again in a rush
fudged that up too...

AIO ZV 8 rooter/CVM NOT WORKING.

I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"

On the "Regain Root after update" post there is talk of using a terminal emulator to make the root stick on V8. The only thing that worked for me is the post at the top of page 7 (or 8?) that has about 8 steps. If you haven't already tried it.
Sent from my BROKEN OUT VS910

antiwesley said:
I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"
Click to expand...
Click to collapse
Try booting into CWM the old-fashioned way (hold down button and power). When I went through all the steps, everything looked liked it failed and all I had was an unrooted ZV8. Even Root Checker said I was unrooted. But then I tried to manually boot into CWM, and it worked! I flashed the new rom, and superuser came with it! Might as well give it a try. There's the possibility that you end up wiping data if you don't actually have CWM, but it sounds like you don't really care at this point...

I went through 2 days of hell to get root. There are so many things to try but I think the one thing that worked for me was that after you root the stock V7 is to run titanium backup. When I ran it it said it had to change su access or something and then I rebooted and did this in a terminal program
su<enter>
echo 'ro.kernel.qemu=1' > /data/local.prop<enter>
but also made sure by then doing this:
cat /data/local.prop
if you don't see exactly the ro.kernel.qemu=1 redo it. I was surprised that I had it wrong but for some reason the terminal app missed characters sometimes.
-Keith

What a maroon.
Sent from my VS910 4G using Tapatalk

$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$

If you are able to have cwm breakout is rooted.
Sent from my Galaxy Nexus using xda premium

Thanks!
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.

stinkyjak said:
$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$
Click to expand...
Click to collapse
koda1789 said:
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.
Click to expand...
Click to collapse
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?

Plumbert said:
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?
Click to expand...
Click to collapse
Are you already on stock ZV7 and rooted? Use Root Explorer and go to /data and create new file, name it local.prop. Open in text editor, enter ro.kernel.qemu=1 then save it. If you can't do that in Root Explorer then you aren't rooted.