im using the rage method and everything worked up until after i used the command gfree - f.
then i input the command sync followed by /data/local/tmp/root, this is what i get
# /data/local/tmp/root
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
mkdir failed for /system/xbin, File exists
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#
if I were you, you should use gfree method... or unfrogivens way
Sent from my HTC Vision using XDA Premium App
I used rage to get temp root, and using gfree but during the last execution, it doesn't work and that's the message I get back
Sent from my T-Mobile G2 using XDA App
This problem sounds familiar, let me look at previous threads I have participated in and see if I can find anything useful
FYI, /data/local/tmp/root is a script that copies busybox and does other root functions.
I'm guessing that the gfree part did work, you can verify this by rebooting into the bootloader and seeing if you have S-OFF
If you are only looking to flash a custom ROM you don't even need to worry about this issue (as long as you do have S-OFF), all you'd need to do is obtain temp root again (using rage or even visionary) then install ClockWorkMod Recovery (I'd recommend using this method), once you have that you can boot into recovery and flash any pre-rooted ROM you want.
Eidt: I found the post I was thinking of, seems like this guy had a similar problem running /data/local/tmp/root
http://forum.xda-developers.com/showthread.php?p=11215689#post11215689
My advice still stands, if you have S-OFF and can get CWM flashed onto your phone (should be able to with temp root) you can flash a custom ROM (which will be pre-rooted) or flash a pre-rooted stock ROM (see this thread)
Hey there,
today I tried to get perma root and followed the guide from cyanogenmod
everything runs great till step 5 in Gaining Permanent Root Access & More
when I enter:
/data/local/tmp/root
I receive the message like nguyenhoanggg described..
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
mkdir failed for /system/xbin, File exists
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
for sure plan was to install cyanogenmod but I even want permaroot :/
thanks for any help
this was the similar problem when i rooted my desire Z
just ignore it and install clockworks recovery
your phone should actually be rooted by then~
but make sure before you do gfree command, you have already pushed all the other files into the proper location, IE busybox, SU and root
Good Luck~
I seem to be having a simmilar problem using the rage method. I can transfer everything through adb on my pc. But when i run the /data/local/tmp/rage it completes the action but after reseting the terminal and force closing the first time it will not open the second time. Any advice??
Thanks for answer,
when I have temproot and try to install clockworks it says no root-access using google search to find out how to get permaroot...
I was having same issue and realized that busybox's md5 from cyanogenmod wiki wasn't the same as the one it says. I downloaded the busybox file from this guide. Busybox is in gfree_temp-root.zip file.
Fibriso said:
Thanks for answer,
when I have temproot and try to install clockworks it says no root-access using google search to find out how to get permaroot...
Click to expand...
Click to collapse
What method are you using to install CWM? I suspect that ROM Manager will fail if ou only have temp root but I would expect that the flash_image method will work.
Do you have a guide or a good explaination for the flash_image method you talked about?
sacarino2k2 said:
I was having same issue and realized that busybox's md5 from cyanogenmod wiki wasn't the same as the one it says. I downloaded the busybox file from this guide. Busybox is in gfree_temp-root.zip file.
Click to expand...
Click to collapse
just want to bump / confirm that this worked for me. the gfree_temp-root.zip download from that link worked for me. note the underscore vs. dash from the link off the wiki.
as far as i can tell the problem was with the file named 'root' pointing to to some wrong paths but i couldnt see a difference in between the 2 in a text editor.
i'm now happily running cyanogen 6 on my HTC vision / g2 using the directions off http://wiki.cyanogenmod.com with the other root.zip file
Try again
Sent from my HTC Vision using XDA App
okay, i had this problem this morning trying to root my g2 and i got the same problem. i did get it to work after a couple of hours of trying 2 figure out why it wouldnt give me perm root.
the steps posted on the cyanogen wiki are correct. the only thing that you need to do is download the 02 version of gfree instead of the 04 version, and also download a different busybox (i think thats what i did).
i think i got the different busybox file from here.
you can just start off at the steps where it deals with pushing gfree to your phone. also, just push the gfree file (not the .cpp or whatever type it was that has a bunch of code in it. all you need 2 push is that one single file from that zipped file.
if you did it right, it will just print out one line with the failure regarding the 'file already exists' thingas stated in the cm wiki.
hierophanta said:
just want to bump / confirm that this worked for me. the gfree_temp-root.zip download from that link worked for me. note the underscore vs. dash from the link off the wiki.
as far as i can tell the problem was with the file named 'root' pointing to to some wrong paths but i couldnt see a difference in between the 2 in a text editor.
i'm now happily running cyanogen 6 on my HTC vision / g2 using the directions off http://wiki.cyanogenmod.com with the other root.zip file
Click to expand...
Click to collapse
The problem isn't in the root script. It is in busybox file. It doesn't work for some vision systems. Looks like compatibility compilation issues. So if you get errors running the root script use the busybox binary i posted before.
Fibriso said:
Do you have a guide or a good explaination for the flash_image method you talked about?
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?t=902493
Just to touch base on this, it is related to the busybox binary on the CM wiki.
We've gone ahead and replaced the 'bad' one about 3 hours ago from this post.
Thanks for all of you who lets us know about the compatibility issues
Related
This is the 5th g2 tmobile has sent me. Been having build quality issues. Anyways, I was able to root them all without any problems. But this one is a toughie. I got s off. But the latest visionary won't temp root for me after I push wpthisOTA n the hboot.img.
Even removing visionary and resetting the phone n trying gfree n rage hasn't helped. Any advice?
I have the superuser app but no su rights at all. I discovered this cuz rom manager tells me I'm not rooted hence can't flash cwr
try using the rage method instead of visionary
tazz9690 said:
try using the rage method instead of visionary
Click to expand...
Click to collapse
I tried to rage temproot then perm. But no dice
I'm helping someone with their phone that has the same problem.
What we're going to do tomorrow is downgrade the rom using this...
http://forum.xda-developers.com/showthread.php?t=831398
then redo the root with rage.
I think the problem occurs when you use visionary to root then try rage. The person I'm helping keeps having problems after code # /data/local/tmp/root, so I'll report back tomorrow.
Don't use the eng hboot. That's not necessary any more, and is quite risky (e.g. if it goes wrong your phone will be bricked).
To get S-OFF after rooting, use this - http://forum.xda-developers.com/showthread.php?t=855764
With the rage method to get root, I believe that works 100% every time, *if* you follow the instructions very carefully and look out for error messages that indicate something has gone wrong. When rage "doesn't work", it's because the instructions haven't been followed or an error message cropped up and the user didn't notice and just carried on.
I'm going to return the phone to stock hboot and wipe it. Ill try rage next
Thnx for the help... this hexeditor crap makes me nervous lol
When I try to unroot it won't creat the darn misc file....
Any ideas what I can do? My s=off but rage method n visionary aren't woorking...
sheek360 said:
I'm going to return the phone to stock hboot and wipe it. Ill try rage next
Thnx for the help... this hexeditor crap makes me nervous lol
Click to expand...
Click to collapse
Gfree does all the hex editing for you and even backs up your origonal first! Very safe way to do it.
Sent from my HTC Vision using XDA App
ok, as soon as i run
/data/local/tmp/root
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
any ideas guys?
ddgarcia05 said:
I'm helping someone with their phone that has the same problem.
What we're going to do tomorrow is downgrade the rom using this...
http://forum.xda-developers.com/showthread.php?t=831398
then redo the root with rage.
I think the problem occurs when you use visionary to root then try rage. The person I'm helping keeps having problems after code # /data/local/tmp/root, so I'll report back tomorrow.
Click to expand...
Click to collapse
That's not an option for me.
I can't #su @all =(
sheek360 said:
ok, as soon as i run
/data/local/tmp/root
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
?
Click to expand...
Click to collapse
Did you reboot the phone after doing the temp root steps of rage ? Because that's kinda how it looks there.
You are also missing busybox, and an "adb push" for busybox is one of the steps in the temp root part of rage.
Also, when you did the "insmod" command, what error message did it come up with ? This is critical. It must come up with the error message shown in the procedure, if it comes up with a different error message then it hasn't worked.
steviewevie said:
Did you reboot the phone after doing the temp root steps of rage ? Because that's kinda how it looks there.
You are also missing busybox, and an "adb push" for busybox is one of the steps in the temp root part of rage.
Also, when you did the "insmod" command, what error message did it come up with ? This is critical. It must come up with the error message shown in the procedure, if it comes up with a different error message then it hasn't worked.
Click to expand...
Click to collapse
Came up with a diff error message....
Before rage I pushed wpthisOTA n the eng build. Then using visionary I tried to get perm root.
I think by using visionary I f'd up my chances of rooting. I assumed the root procedure didn't change. O well. Doesn't really matter. My camera is now taking pics backwords. Tmobile is swapping my g2 for another lol
Hey, I just got my G2 today and am trying to root it through adb. I get to the last part of the tutorial under getting perm-root, and i put in /data/local/tmp/root in the root terminal, and it gives me a whole bunch of busybox: /system/bin/"": Input/output error's, and at the end says cp: cant creat /system/bin/su Input output error and unable to chmod /system/bin/su no such file or directory.
what method are you using to root?
Hey Andy, I'm having the same problem the original poster is. I'm using the rage/gfree method and everything works like a charm right up to the last step. I'm getting the "unable to chmod /system/bin/su: no such file or directory"
This was also reported here: http://forum.xda-developers.com/showthread.php?t=897499&highlight=chmod+0755+/data/local/tmp/*
(Though, unlike the guy in that thread, I didn't try to use visionary AT ALL (didn't download it or install it or anything) and ONLY followed the wiki's guide, which uses the rage/gfree method.)
All three of us seem to have ended up with the problem though and from reading through that thread I posted the link to above and from what I've done 8 times now tonight, we've followed the steps exactly.
Any ideas? I would love to get this thing perma rooted.
Thanks so much to you and anyone else for any help.
Are you sure there weren't any errors before that one? I would have guessed you had an error in the cp command as well...
Make sure you have the su file on the root of your SD card. It was the first file you pushed in the wiki guide. If that file is not there, just push it to your SD card again and then re-run the root script in terminal.
Finally got it worked out late last night. Turns out that I had put a copy of the su file on the card while it was mounted to my computer, before I mounted it on the phone, prior to following the root steps. I guess this somehow messed with adb pushing it correctly.
So if that is happening to you, clear out the unnecessary files first and only move the necessary files to the card via adb.
After that, it worked like a charm. I am now perma-rooted.
Sent from my T-Mobile G2 using XDA App
And thanks so much ian. What you said got me thinking about removing the su file altogether and starting it fresh.
Sent from my T-Mobile G2 using XDA App
I dont know why it was giving me errors, but all i had to to was flash recovery through adb and flash a rooted rom and everything worked great.
Hey! So I got my G2 from a member on here last night (woohoo!) but I can't seem to root it. I tried every method on here including visionary and gfree. I had some success with gfree since I was able to sim unlock it. When in bootloader I get 's-off' on the first line. But when I go into Rom Manager it tells me I'm not rooted and when I type 'su' into terminal I get 'suermission denied'. Any help here? I really need to flash a new ROM due to ORD.
And just some info from System Info in the boot loader even though I think it's not needed here.
OS ver.-1.22.531.8
eMMC- unknown 2151MB 4407295sectors
Also under IMAGE CRC
hboot: 0x6570c0db
boot: 0x1b87420d
recovery: 0xd4af6ad9
system 0x9f52fea6
Any Update???
OK so you were able to get S-OFF via gfree but not permanent root, when you followed the gfree method, the last step (before the verify) of the gfree rooting guide on the wiki (not sure if that's the one you used) has you run a command to "lock in" root:
You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
Code:
# /data/local/tmp/root
# sync
Click to expand...
Click to collapse
I suspect this is where it went wrong.
You should be able to use the same method again to get perm root, just skip the gfree parts. Summary:
1. Get all the files on your phone (they are probably already there)
2. Get temp root using rage
3. Run the command (script) that I listed above
Link to the full instructions: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#How_To_Get_R.2FW_Access_.28Permanent_Root_.2F_.22Permaroot.22.29
I tried the wiki method three times, making sure I typed everything correctly. After I type the line you put up I get a series on lines that show that some files can't be shown (I dont remember the exact ones off the top of my head, I'll redo it soon so I can tell you which ones). I also tried it with two different SD cards.
SO I found the errors in another thread started today:
Code:
/data/local/tmp/root
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
Strange, /data/local/tmp/root is just a script that does all of the stuff to get you permanent root, not sure why it shouldn't be working for you.
I think once you are temp rooted you should be able to install CWM recovery and use that to install a new (pre-rooted) ROM. If you are not ready to or don't want to jump into a custom ROM you can load the stock pre-rooted ROM and should not even have to wipe (would advise a nandroid backup of course)
http://forum.xda-developers.com/showthread.php?t=836042
raitchison said:
Strange, /data/local/tmp/root is just a script that does all of the stuff to get you permanent root, not sure why it shouldn't be working for you.
I think once you are temp rooted you should be able to install CWM recovery and use that to install a new (pre-rooted) ROM. If you are not ready to or don't want to jump into a custom ROM you can load the stock pre-rooted ROM and should not even have to wipe (would advise a nandroid backup of course)
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
I should try temprooting again and flashing CWM. And The only reason I want to root is to flash custom roms. lol.
EDIT: Well that didn't help. I followed the guide for temproot. I did get the root prompt (#) in terminal, but when testing with 'su' gives me 'su:not found'. And CWM still tells me I'm not rooted and wont let me flash the recovery.
Try using visionary to temp root, that may yield more success.
You may want to use ADB to pull out the remnants from your previous attempts.
If you have # in the terminal you should not need to su.
If you can't flash CWM using ROM manager try this method instead http://forum.xda-developers.com/showthread.php?t=902493
With visionary I push temp root, it makes me wait for like 10 minutes, and does nothing. I was just doing su to see what it does. I'll try removing everything with adb and redownloading all the files. Anyway, what's the command to remove with adb? lol
Open an ADB shell and use the rm command to remove individual files, I would remove everything you ADB pushed originally.
Code:
rm /sdcard/su
rm /sdcard/Superuser.apk
rm /data/local/tmp/rage
rm /data/local/tmp/busybox
rm /data/local/tmp/root
Will only run if you have root access (a # prompt) and you may get errors with some since clearly something isn't as it should be on your system.
Did you try using the flash_image utility to flash CWM?
Also if you can flash the engineering hboot you should be able to load CWM from fastboot.
So I removed the files, redownloaded, and redid the wiki root method.
Still no luck. Same error as posted before. This is getting on my nerves. lol
Did you try to install recovery using this method?
If that didn't work did you try to install the engineering HBOOT?
raitchison said:
Did you try to install recovery using this method?
If that didn't work did you try to install the engineering HBOOT?
Click to expand...
Click to collapse
I will attempt these methods soon and report back.
[Q] Help me root my OTA upgraded G2 Visionary R14 Don't Work "Visionary R7 needed"
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Is temp root working?
Sent from my HTC Vision using XDA App
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
Nonentity018 said:
Is temp root working?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
+1
Like he said, use that, don't waste your time with visionary
sammd301 said:
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Click to expand...
Click to collapse
I'd stay away from visionary if I were you! Its messing up just as many phones as it is rooting them!
part of the problem is that a visionary method is stickied in one of these subforums... that needs to be taken down desperately and replaced with gfree/rage.
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
I am in the process of using this method....I'll let you all know how it turns out. by the thanks for pointing me to it...
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
Yes I am in the process of using ADB / RAGE method....I run in problem and I could use someone help please...
TEMP ROOT
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
===========
All the commands are working except
$ adb push rage /data/local/tmp/rage
the reply I get after input the command is
Cannot open 'rage': No such file or directory
I have search the web for help...but I could find help on that issue
SO please if anyone knows what I am doing wrong could you please help....
thanks
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Cobra281 said:
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Click to expand...
Click to collapse
Yes the "Rage" file is there, all the other command work fine...except the one dealing with the "Rage" file
ratchetrizzo said:
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
Click to expand...
Click to collapse
Thanks so much for your input....when I gfree_temp-root.zip file I can see that the "RAGE" file is present but after 20 to 30 minutes the "RAGE" file disappear from the folder but all the other files remains....Is an alternative gfree_temp-root download link that anyone might know of....thanks again
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
ratchetrizzo said:
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
sammd301 said:
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
Click to expand...
Click to collapse
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
ratchetrizzo said:
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
Click to expand...
Click to collapse
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
sammd301 said:
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
Click to expand...
Click to collapse
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
ratchetrizzo said:
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
Click to expand...
Click to collapse
Yes, I did what you suggested, but now I am getting
"rm failed for -rt, no such file or directory" after inputting ""rm -rf /system/xbin" command...by the way thanks so much for helping me out on this...
Hello everyone,
I've had my LG Nitro HD for about a year and a half. I've recently been disappointed with it's performance and battery live. I read rooting and adding a new rom really helps free up the phone's natural performance. I've unlocked a few phones in the past. This one seems to be giving me a lot of fits.
I downloaded a zip file called 'P930_v20e_ROOT". I do not want to share any external linking as it's usually frowned upon. Nevertheless I unzipped the folder and copied the file "LG_SystemBackupTest" to the root of my sd card. I downloaded a file manager app to execute the file. Once installed I enabled the option for unverified sources, and the option for USB under development mode. I also installed the OEM LG driver off of their website for the P930 model phone. I then ran the LG_SystemBackupTest file that was in my applications. While it ran it simply states "hello world". I powered off/restarted the phone as instructed.
Once the phone booted up I plugged in the usb cable to my Windows 8 PC. I then ran the "root_p880" file. Below is the error I get repeatedly.
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permissio
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: cannot create /data/local.prop: Permission denied
AGAIN REBOOT
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
/system/bin/sh: cannot create /system/xbin/busybox: Read-only file syste
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
/system/bin/sh: busybox: not found
/system/bin/sh: busybox: not found
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
I've tried every possible combination I can think of. I even booted up one of my old Windows XP machines, performed all the steps above, and still the same. Just now I finally reset the phone to it's factory defaults. Only to get the same results. Can anyone provide any guidance?
Kind regards,
Jeremy
Just getting root isn't going to allow you to flash a new or custom rom. You need to install cwm using the P930 unbricking guide.
Re: Rooting problems - Please help!
audit13 said:
Just getting root isn't going to allow you to flash a new or custom rom. You need to install cwm using the P930 unbricking guide.
Click to expand...
Click to collapse
Thank you for the prompt reply. I do have another guide I was following to install a custom rom. However it states I first need to root. It provided no instructions and stated to google how to do it.
LilLowEK said:
Thank you for the prompt reply. I do have another guide I was following to install a custom rom. However it states I first need to root. It provided no instructions and stated to google how to do it.
Click to expand...
Click to collapse
Did you try both guides in this forum? I believe this is the guide I used: http://forum.xda-developers.com/showthread.php?t=1784709
You need to brick the phone, revive it, root, and install cwm.
audit13 said:
Did you try both guides in this forum? I believe this is the guide I used: http://forum.xda-developers.com/showthread.php?t=1784709
You need to brick the phone, revive it, root, and install cwm.
Click to expand...
Click to collapse
Thanks. I didn't use that guide. I'll read through it. It sound kind of odd that I first need to brick the phone just to un-brick it. If anyone else has any experience or used a different guide please feel free to share.
Best,
Jeremy
LilLowEK said:
Thanks. I didn't use that guide. I'll read through it. It sound kind of odd that I first need to brick the phone just to un-brick it. If anyone else has any experience or used a different guide please feel free to share.
Best,
Jeremy
Click to expand...
Click to collapse
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.
audit13 said:
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.
Click to expand...
Click to collapse
Thanks. I sent you a PM with some details on what I was using.
Re: Rooting problems - Please help!
audit13 said:
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.
Click to expand...
Click to collapse
LilLowEK said:
Thanks. I sent you a PM with some details on what I was using.
Click to expand...
Click to collapse
Problem seems to be solved. I rooted the phone with the help of the following thread.
http://forum.xda-developers.com/showthread.php?t=1886460
Thanks everyone! Now off to hopefully get a rom installed.