Related
ok so I'm trying to root my G2 phone from T-mobile, I have followed the steps in this forum:
http://forum.xda-developers.com/wik..._Root_.2F_.22Permaroot.22.29_using_gfree_v0.7
all of the steps, I downgraded my firmware, I got permroot but when I get to step 2: copy files to phone it does not let me push the Superuser files onto my phone, it says permission denied. I have USB debuggin on and i have the screen on stay awake, I have superuser app on my phone but I don't know what i am doing wrong.
adb push su /sdcard/
adb push Superuser.apk /sdcard/ <---these 2 are the ones it doesn't let me push. i have them installed on my platform-tools directory and everything too.
Look here
Http://forum.xda-developers.com/showthread.php?t=879701
Sent from my T-Mobile_G2 using xda premium
What is this??
this is for ADB I already have adb
Instead of pushing to /sdcard, try pushing to /mnt/sdcard (/sdcard is just a symlink and I am not sure every system has it by default).
Example:
adb push Superuser.apk /mnt/sdcard/
Also, are you sure your sdcard is working properly? You could also just copy those files manually to your sdcard from your OS as well as you would any other file like music or videos. It would make no difference.
That totally worked!!!
Thanks man, I was stuck on that thing for like a week, ohh man thanks again.
Hi,
I was having trouble with my app YouTubeTablet.apk, it stopped working while I was using it. thinking I was starting to get the hang of this OS, I found the apk in system/app/ and, thinking I could just reinstall it, I deleted it. It wont let me reinstall it. it trys to install, then just gives an error saying "app did not install"
I have been reading and searching all night, I have tried the chmod 644 and a few other things but nothing I have done has seemed to work to get this reinstalled.
Does anyone know a way to get this app back?
thanks,
John
Hello I'm not 100% certain as I'm also pretty new to this scene, but couldn't you just copy the apk back to /system/app ?
Sent from my ADR6300 using XDA App
Use a root explorer and copy the new app to /system/app. Restart and it should work.
I use ES File Explorer, but you have to check mount as read/write in the settings before you copy to system/
Install in /system/app and make sure your permissions are correct. Read: User, Group and Others checked and Write: User checked. Reboot
BTW Youtube crashed last night for everyone. Was a thread about it.
Thanks for the reply's,
I have tried most of this stuff, I tried the rest (changing the permissions) and it still doesn't show up in apps or install
not sure what else to try??
John
Try pushing it via adb then fixing permissions.
Beamed from my TF101 using Tapatalk HD
Xerravon said:
Thanks for the reply's,
I have tried most of this stuff, I tried the rest (changing the permissions) and it still doesn't show up in apps or install
not sure what else to try??
John
Click to expand...
Click to collapse
What ROM are you running? Just flash that ROM again without wiping.
infazzdar said:
Try pushing it via adb then fixing permissions.
Beamed from my TF101 using Tapatalk HD
Click to expand...
Click to collapse
Hi,
I have been trying to do this, I cant seem to do it
after installing sdk I am
1. booting into apx vol up + power while plugged into the pc (plus I tried pluging nto the pc after going into apx mode)
2. adb devices (none show) If I boot normally the devices do show
3. in apx mode, apx shows under devices and printers in my pc
so I tried to do adb remount with the TF booted normally it says not permitted, if I try in apx mode it says no device
I dont know, I am lost, I hope this is all my fault, it has to be, I am reading and reading, nothing I find, or stuff people tell me to try works. I am really starting to wonder about this OS
John
Xerravon said:
Hi,
I have been trying to do this, I cant seem to do it
after installing sdk I am
1. booting into apx vol up + power while plugged into the pc (plus I tried pluging nto the pc after going into apx mode)
2. adb devices (none show) If I boot normally the devices do show
3. in apx mode, apx shows under devices and printers in my pc
so I tried to do adb remount with the TF booted normally it says not permitted, if I try in apx mode it says no device
I dont know, I am lost, I hope this is all my fault, it has to be, I am reading and reading, nothing I find, or stuff people tell me to try works. I am really starting to wonder about this OS
John
Click to expand...
Click to collapse
It's ADB, you do NOT put it in APX mode. Just turn USB Debugging on.
Open the command window and type in ADB devices to see if your device come up.
This thread help with driver's and such for ADB
http://forum.xda-developers.com/showthread.php?t=1071584
baseballfanz said:
What ROM are you running? Just flash that ROM again without wiping.
Click to expand...
Click to collapse
I think I am running the stock rom, rooted. I dont have anyidea how to flash
Is there a way for me to reflash the same stock rom? If you can point me to same directions or info where I can try to learn this?
thanks
baseballfanz said:
It's ADB, you do NOT put it in APX mode. Just turn USB Debugging on.
Open the command window and type in ADB devices to see if your device come up.
This thread help with driver's and such for ADB
http://forum.xda-developers.com/showthread.php?t=1071584
Click to expand...
Click to collapse
thank you, I just read somewhere it had to be in apx for adb
Ok the devices do show in the list
I read to type
adb remount
adb push youtubetablet.apk /system/app/
adb push youtubetablet.odex /system/app/
to push these into system/app
when I type adb remount I get the error
"remount failed operation not permitted"
any idea what I am doing wrong
thanks
John
try
Code:
adb shell remount rw
baseballfanz said:
try
Code:
adb shell remount rw
Click to expand...
Click to collapse
It gives me
remount: permission denied
I just read I will quote below
"If it shows a $ sign when u type adb shell then u got no root son"
Ok, when I type adb shell I do get the $ does this mean I am not rooted? I do have su and can get su permissions in root explorer. heck that is what got me in this trouble, I was able to delete the youtubetablet apk from system/app/
adb
Xerravon said:
It gives me
remount: permission denied
I just read I will quote below
"If it shows a $ sign when u type adb shell then u got no root son"
Ok, when I type adb shell I do get the $ does this mean I am not rooted? I do have su and can get su permissions in root explorer. heck that is what got me in this trouble, I was able to delete the youtubetablet apk from system/app/
adb
Click to expand...
Click to collapse
What method did you use to root?
baseballfanz said:
What method did you use to root?
Click to expand...
Click to collapse
I used this one to root back on (8.6.5.9)
ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22 (brk's)
http://forum.xda-developers.com/showthread.php?t=1185104
and I updated with these
[UPDATE] CWM - Stock + Root - 8.6.5.21 US 8.6.5.21-WW 8.6.6.23-WW Updated 12/29/2011 (daoist )
http://forum.xda-developers.com/showthread.php?t=1334673
I was able to do this in terminal emulator
mount -o rw,remount /system
cp sdcard/download/youtubetablet.apk /system/app/
cp sdcard/download/youtubetablet.apk /system/app/
mount -o ro,remount /system
this did seem to work, i mean It did copy the files into the system/app dir however I still dont see the app in my apps and still cannot install
One difference this time, if I copied the files into the system/app dir using root explorer then changed the permissions with root explorer I could, I mean it would allow me to check the box's and save the change
this time In root explorer I cannot keep or save the changes to the permissions, it gives some error about "not being able to change permissions on some file formats such as sdcard etc..." something like that
thanks
John
I was able to push the files over using this method found here (pushing it via adb with my TF in recovery (CWM)
http://androidforums.com/optimus-m-...anyone-who-has-rooted-deleted-lghome-apk.html
it did push the files but still doesnt show up as an app
The may seems simple and don't get mad at me for saying this, but did you reboot after you pushed it to /system /app? It should show up then. At least that is the way I push them and usually when it doesn't work, it is because I forgot that part.
Xerravon said:
[UPDATE] CWM - Stock + Root - 8.6.5.21 US 8.6.5.21-WW 8.6.6.23-WW Updated 12/29/2011 (daoist )
http://forum.xda-developers.com/showthread.php?t=1334673
John
Click to expand...
Click to collapse
Have you tried flashing that ROM again?
baseballfanz said:
Have you tried flashing that ROM again?
Click to expand...
Click to collapse
No I havent, is it ok to just reflash like that? I ask cause it says (in the thread) it wont work unless you have the update before that one installed.
Hi, Yes, I did reboot, actually tried the whole thing a few times/
thanks guys
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
You should be able to just run the root.bat if you have the folder with all contents extracted to desktop.
Sent from my MB865 using xda premium
Aimless Rambler said:
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
Click to expand...
Click to collapse
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Re-Rooted!
jimbridgman said:
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Click to expand...
Click to collapse
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Hmm
Aimless Rambler said:
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Click to expand...
Click to collapse
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
update on strange problem
Aimless Rambler said:
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
Click to expand...
Click to collapse
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Aimless Rambler said:
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Click to expand...
Click to collapse
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Rooted again??
jimbridgman said:
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Click to expand...
Click to collapse
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin it alone did not fix the problem. I still could not access root. So I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Aimless Rambler said:
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Click to expand...
Click to collapse
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
jimbridgman said:
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
Click to expand...
Click to collapse
Thanks! I'm sure I did something to cause the troubles but can't recall exactly what it was I did wrong! My brain is getting old. Ha! But to answer your question ... other than my original root (using Motofail) I've hesitated to do anything until after the ICS update. I recently bought the phone 2nd hand to replace my Samsung Captivate so I could experiment with a Lapdock (in my line of work portability and multi-role is a plus). The phone was stock when I got it. Also, I had moved the root.sh file and superuser.apk into my Android/Platform_Tools folder which is in my system path (android rules,etc), so there was some forethought prior to dragging the script into terminal. Next time I'll 'cd it like ya recommend!
Could it be there was an issue with how I did the original GB motofail root?
In any case all seems to be good now.
Thanks again!
Well let me first off say i'm feeling really dumb atm.
Just bought my wife the new m8 , I've already s-offd and perm rooted mine but for some reason im having trouble getting the commands to work for hers .
im using a mac btw but like ive said i did successfully do this on this exact setup
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp <<<<<<<<
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
do i actually put the data local tmp part in or am i supposed to be putting in my local directory where i have the file on my computer
when i adb devices , i can see my device, so it is connected
in adb when i " adb reboot" it does reboot my phone
but when i try to push the firewater file it does not push , i get this
cannot stat 'firewater': No such file or directory
firewater file is in my adb folder on my desktop and its the right size etc etc .
thanks in advance if anyone can tell me what im doing wrong!!!!
commandocon said:
Well let me first off say i'm feeling really dumb atm.
Just bought my wife the new m8 , I've already s-offd and perm rooted mine but for some reason im having trouble getting the commands to work for hers .
im using a mac btw but like ive said i did successfully do this on this exact setup
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp <<<<<<<<
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
do i actually put the data local tmp part in or am i supposed to be putting in my local directory where i have the file on my computer
when i adb devices , i can see my device, so it is connected
in adb when i " adb reboot" it does reboot my phone
but when i try to push the firewater file it does not push , i get this
cannot stat 'firewater': No such file or directory
firewater file is in my adb folder on my desktop and its the right size etc etc .
thanks in advance if anyone can tell me what im doing wrong!!!!
Click to expand...
Click to collapse
Have you already temp rooted her phone with weak sauce?
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
Have you already temp rooted her phone with weak sauce?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
yes i have temp root and su installed
commandocon said:
yes i have temp root and su installed
Click to expand...
Click to collapse
Hmm. Are you copy pasting the messages? Make sure you don't have any spaces in wrong places. Maybe try a factory reset on said device. Just confirming firewater and adb are in the same directory?
Sent from my HTC6525LVW using Tapatalk
yeah theyre in the same folder
commandocon said:
yeah theyre in the same folder
Click to expand...
Click to collapse
Click on weaksauce to make sure it is still working and you may have to click on a prompt and then try ADB again after that.
Figured out what it was at about 12 midnight, I had to add in the directory then put the data/local/ tmp/ etc after that.
So problem is all solved thank god was justa long night of trying commands
where you add the directory?
So I have setup adb by following a video another user posted to an earlier question of mine that being said adb is setup correctly my phone is recognized it is online I can reboot the phone along with other adb actions. the problem Im having is where do i put the pie.jar and root.sh files i have put them in platform tools and it says cannot stat no such file or directory i moved them to sdk folder and still getting the same message please help i have been trying to root for over a week now im not stupid im just doing something wrong im close to just giving up any feedback is greatly appreciated
I posted a vid in other thread that may help not sure exacly what you are doing.
mrwinkle said:
I posted a vid in other thread that may help not sure exactly what you are doing.
Click to expand...
Click to collapse
Yeah I followed that video got adb setup got all the expected output except for the last two I get
C:\Android-SDK\sdk>adb shell /data/local/atvc/root.sh
rm failed for /data/local/atvc/blop.asec, No such file or directory
rm failed for /data/local/atvc/blop, No such file or directory
pie by jcase
want to buy me pie? paypal-> [email protected]
And my device does not reboot but it acts like it reboots on my pc it discovers it again like I unplugged it then plugged it back in and when I install super su it says no binaries are installed what should I do This process is the bane of my exscitence but I will get it
ojodetigre said:
Yeah I followed that video got adb setup got all the expected output except for the last two I get
C:\Android-SDK\sdk>adb shell /data/local/atvc/root.sh
rm failed for /data/local/atvc/blop.asec, No such file or directory
rm failed for /data/local/atvc/blop, No such file or directory
pie by jcase
want to buy me pie? paypal-> [email protected]
And my device does not reboot but it acts like it reboots on my pc it discovers it again like I unplugged it then plugged it back in and when I install super su it says no binaries are installed what should I do This process is the bane of my exscitence but I will get it
Click to expand...
Click to collapse
those are okay just ignore your phone should be rooted now but will unroot if you reboot b/c write protection is still on. to be completely rooted (non-tethered) follow steps HERE.
mrwinkle said:
those are okay just ignore your phone should be rooted now but will unroot if you reboot b/c write protection is still on. to be completely rooted (non-tethered) follow steps HERE.
Click to expand...
Click to collapse
but its not as soon as that happens i try to install super su and it says no binaries are installed i installed root checker and it says my device is not rooted i read whhere it says to ignore those messages i guess i should just keep trying until i get root but do i have to start back with the push commands or just the shell commands and i have evrything else ready for perma root just need to get root first