Database Info

HowTo re-flash the recovery image after old 2.1 RUU

This guide was taken from AndroidCentral and I thought I would share it here because it's taken me 4 hours this morning to figure out why I was having so many problems trying to flash a recovery image when I know my phone was rooted and flashed in order to get 2.1 a month or so ago. I have been searching these forums and google and hope anyone else who has my issue finds this post.
1. Make sure you have the Android SDK installed.
2. Download flash_image.zip
3. Download recovery-RA-heroc-v1.5.2.img
4. Unzip the first file, and place both in your Android SDK/tools folder.
5. Make sure USB debugging is ON
6. Connect your phone to the PC
7. Open the command window and navigate to the Android-sdk/tools folder on your computer.
8. At the prompt enter the following, one line at a time followed by enter
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
adb push flash_image /system/bin
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb shell
chmod 0755 /system/bin/flash_image
reboot
9. Your phone will reboot. When it is finished, back at your command window, once again enter
Code:
adb shell
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.5.2.img
reboot recovery
10. With any luck, you'll have the recovery image back and can load custom 2.1 based ROMS again.
Hope this helps. All credit goes to gbhil at Android Central.

You might want to change the title of the post. People might get confused thinking you found a way to downgrade the hboot and not how to flash the recovery image.

Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.

bubbacs1 said:
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
Click to expand...
Click to collapse
This won't work for the leak that was put out today. You lost root. This process requires root.

bubbacs1 said:
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
Click to expand...
Click to collapse
If you used the new RUU that was leaked today you're screwed. The older 2.1 leaks were test ROMs that were already rooted so you could use the instructions above to flash the RECOVERY. Notice recovery in bold, not bootloader. Once hboot is updated there is no known way to downgrade so you could use an older RUU file.

This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.

HeroMeng said:
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
Click to expand...
Click to collapse
So they can't run an older ruu with 1.5?

HeroMeng said:
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
Click to expand...
Click to collapse
To clear that up, if you run the RUU you have no root. If you extract the ROM, set it up, and flash it, you will preserve root, just like damageless made for all of us. But, yeah, you are not gonna be able to get back from this one. at least until someone figures it out.

I changed the thread title to hopefully alleviate some confusion. I didn't realize there was a newer RUU released.
I flashed the Damageless Rom and it's running smoothly so far, but I'm still trying to figure out why wifi tethering isn't working out for me. :-(

celemew2 said:
I changed the thread title to hopefully alleviate some confusion. I didn't realize there was a newer RUU released.
I flashed the Damageless Rom and it's running smoothly so far, but I'm still trying to figure out why wifi tethering isn't working out for me. :-(
Click to expand...
Click to collapse
Did you get wifi tether version 1_60? That's the only version that ever worked for me.

Yeah, I have 1.60 installed on my phone right now, but when I try to start tethering, a SU Request black screen comes up and nothing happens until I get an error, "Activity SU Request (in application Superuser Permissions) is not responding."
I'm sure there's an answer somewhere, but lately I haven't been having luck searching for it.
Edit:
Thank you 98classic! All I had to do was enable USB Debugging. (I had it turned off cause I didn't like the warning up top when my phone was plugged into the computer)

"flash_image not found" what the f**k

need the binary? physically check its there with a root explorer
Sent from my broken Typewriter!!!

or do this download and set up the android SDK it itself includes the flash_image binary. after that u will need to open a command prompt on your computer u will have to change directory to platform tools
cd /path/to/platform-tools
after that u will get the chance to do
flash_image recovery /path/to/recovery.img
that will flash the recovery
now reboot into recovery
Typed from my broken Typewriter!!!

[Q] Is there any way to reinstall a system app?

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

[Q] [OUYA] SuperUser Access Help

Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-adb shell
-su
-mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
-exit
-exit
-adb push su /sdcard/su<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?

cronikman84 said:
Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-adb shell
-su
-mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
-exit
-exit
-adb push su /sdcard/su<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?
Click to expand...
Click to collapse
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?

cronikman84 said:
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?
Click to expand...
Click to collapse
Never mind LMAO...i got it :victory:

cronikman84 said:
Never mind LMAO...i got it :victory:
Click to expand...
Click to collapse
How'd you get it?! I'm stuck here too, thanks!

thanamesjames said:
How'd you get it?! I'm stuck here too, thanks!
Click to expand...
Click to collapse
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute

cronikman84 said:
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute
Click to expand...
Click to collapse
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?

diazamet said:
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?
Click to expand...
Click to collapse
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...

cronikman84 said:
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...
Click to expand...
Click to collapse
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?

diazamet said:
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?
Click to expand...
Click to collapse
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.

cronikman84 said:
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.
Click to expand...
Click to collapse
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.

diazamet said:
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.
Click to expand...
Click to collapse
Sweet!!...glad you got it fixed... I knew that the native SU was crippled the first time i tried it...that's why i tried the OUYA toolbox cause i knew people had success with SU on that toolbox, so i gave it a try and SU was workin...tha's how i knew something was wrong with the native SU...

[Q] SuperSu Installation fails, cannot root

Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks

Backup important pics, videos, and docs that are located in your phone storage. You will need to Odin flash the VRUCML1 tar then run Saferoot. You can download the 1+ GB file from my link below. Unzip it then use Odin to flash the entire tar or tar.md5. Doing this will format your phone's storage.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 4

shark_dude said:
Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks
Click to expand...
Click to collapse
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.

buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?

shark_dude said:
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?
Click to expand...
Click to collapse
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.

buhohitr said:
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
Click to expand...
Click to collapse
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?

shark_dude said:
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?
Click to expand...
Click to collapse
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.

buhohitr said:
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.
Click to expand...
Click to collapse
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?

shark_dude said:
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?
Click to expand...
Click to collapse
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.

buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Nice work! Thanks for finding that fix.
Sent from my SCH-I535 using Tapatalk 2

buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Gotcha, thanks again! I appreciate the prompt responses :good:

i cnt see $ prom
buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.

DrunkenZombie said:
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.
Click to expand...
Click to collapse
Just continue with the following command:
/system/xbin/su hit enter, you should see the # prompt. Then do the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.

[Q] Im missing a crucial step in PIE Help

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