Database Info

{Howto}Downgrrade form rooted 1.47.651.1

Ok... If your wimax isn't working and you want to downgrade to try to get it working this is how to do it...
1st get all of the files like you want to do Toast's Part-2. link: http://forum.xda-developers.com/showthread.php?t=701835
Then do this part:
STEP 2~FLASHING MTD PARTITION TO ENABLE DOWNGRADE:
- download all files posted above
- unzip the flash_image.zip and the mtd-eng.zip
- put the flash_image and mtd-eng.img on the root of your sdcard
- go into shell on ur pc and do:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
- this should only take a second or two
- now put the PC36IMG.zip on the root of your sdcard
- power off the phone
STEP 3~FLASHING ENG BUILD:
- hold volume down + power to boot into hboot
- it should now find and verify the PC36IMG.zip on the root of your sdcard. itll show a blue status bar on the top right of the screen.
- after a minute or so it will ask u if u wanna flash SAY YES
- affter it flashes the PC36IMG.zip it will ask if you wanna reboot. SAY YES
After if finally boots you should see HTC quietly brilliant which hangs forever but it should eventually get past it. Once it does you will have the oldest everything. This is a beta build and has a bunch of tools but just do an upgrade to root like you normally would. I would suggest going to .6 then upgrading to the latest 47 from there.
Hope that this helps someone.
P.S. is anyone willing to dump all of the tools that are included in this rom. It might be helpful for the other devs.

Thats the hard way... but yeah it'l work.
Why is everyone so hype on adb everything...?

Tell me the easy way. I would love to do it instead.

kthejoker20 said:
Thats the hard way... but yeah it'l work.
Why is everyone so hype on adb everything...?
Click to expand...
Click to collapse
It's just easier to copy and paste stuff, even typing on a real keyboard. It's a pain in the ass doing it via terminal emulator with the lack of a physical keyboard on our Evo's.

Can anyone confirm if this helps fix the 4g issue?

krosemm said:
Can anyone confirm if this helps fix the 4g issue?
Click to expand...
Click to collapse
If you used the unrevoked, no it wont.
There is no fix for 4g from unrevoked yet.

Neotelos_com said:
If you used the unrevoked, no it wont.
There is no fix for 4g from unrevoked yet.
Click to expand...
Click to collapse
I used the toast method. And if i'm not mistaken I should flash roms w/o the 1.47.651.1 OTA update after downgrading right?

Nope, I try this method and it is not working. Some how the new OTA encrypted a code that any lower version will not over write it.

You don't have root access to even copy/paste or push the files to /data. I tried this and got a permission denied error message.

How do you input adb shell into Vista, I clicked "start", "run" and type "cmd" it bring up C:\users\XXXXX\ cd c:\android hit "enter"
then I type
c:\android>adb remount
Access is denied
Please advise what I did wrong. thanks

It worked for me... you have to make sure that when you enter the su command in adb to look at your phone. There should be a super user permission box that pops up. Accept it and youll be able to adb. It went fine for me after that.

urcboss07 said:
How do you input adb shell into Vista, I clicked "start", "run" and type "cmd" it bring up C:\users\XXXXX\ cd c:\android hit "enter"
then I type
c:\android>adb remount
Access is denied
Please advise what I did wrong. thanks
Click to expand...
Click to collapse
1) Put your phone on USB Debug
2) On your Phone make sure the Ninja(SuperUserPermission) is set to prompt you when you have a request.
3) go to your PC and type in adb shell
4) type in SU
5) Once do you that you will see a prompt from the Ninja asking for a request. Allow for it. And it will remember from that point forward.
6) Look at your cmd prompt screen for a # - if you have it you have full access.
Then so what commands you have been given to do.
It can also be done from the Android Terminal Emulator but some might not like working with a smaller screen I like it myself. Makes me feel geeky

mrmomoman said:
1) Put your phone on USB Debug
2) On your Phone make sure the Ninja(SuperUserPermission) is set to prompt you when you have a request.
3) go to your PC and type in adb shell
4) type in SU
5) Once do you that you will see a prompt from the Ninja asking for a request. Allow for it. And it will remember from that point forward.
6) Look at your cmd prompt screen for a # - if you have it you have full access.
Then so what commands you have been given to do.
It can also be done from the Android Terminal Emulator but some might not like working with a smaller screen I like it myself. Makes me feel geeky
Click to expand...
Click to collapse
This would only work if after the messup your still has root access. Some people have root and the "SU" will work but for the people w/o root will get access denied.

also
From above (I hate quoting) have you tried going to your tools folder inside your android folder and from there try your adb commands?

If you applied the OTA sent from Sprint, you lost root access. There will be no Ninja in the programs folder, because it was a new rom that the was flashed with the OTA. Root access has been closed for those that downloaded the update. If you try and type su, you will get permission denied.
Those of you that still have the root and superuser rights, DON'T DOWNLOAD THE OTA!! You are in a better position then the rest of us. I wanted the good battery life, so that's why I did it.

[Q] Any suggestions on how to regain root after the OTA ICS update using Linux?

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!

[ROOT] $99 Walmart Nextbook 8 (NX008HD8G)

The Nextbook 8 (NX008HD8G) is a $99 tablet available from Walmart. It sports a AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU), 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage. Its a nice little budget tablet for those who don't need a Nexus 7 or greater performance rated tablet. Not too long ago I discovered how to root it and apparently I'm the first to do it as far as I can tell. Now here's how.
What you will need is Bin4ary's One Touch Root App. This app will get you only partial root via the ADB Shell. My guess is the ADB exploit he uses does work to get basic root access for ADB, but some incompatibility prevents proper installation of su & SuperUser.apk. What we're going to do is finish the job manually.
First run Bin4ary's app and use the Normal Method. Be sure to ignore all errors. After your tablet reboots move su and Superuser.apk from Bin4ry's app folder to the root of the Internal SDCard. Next you will need ADB. If you don't have it you can get it either from Bin4ary's app folder you found su & superuser.apk in or you can install the Android SDK. At the command prompt enter the following:
Code:
adb shell
su
At this point you should see a # sign indicating root privileges. If you do enter the following commands.
Code:
mv /system/xbin/su /system/xbin/osu
cp /sdcard/su /system/xbin
chmod 6755 /system/xbin/su
The use Astro or your favorite file manager to navigate to /sdcard and install SuperUser.apk then reboot your tablet. From here on you should have full root on your tablet. Credit should definitely goto Bin4ry for his work on his One Touch Root App for getting us half way there.

Confirmed Working
Confirmed. Works as described.
Nice work!

Thank you for this information, works excellent.

Ron Overdrive said:
The Nextbook 8 (NX008HD8G) is a $99 tablet available from Walmart. It sports a AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU), 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage. Its a nice little budget tablet for those who don't need a Nexus 7 or greater performance rated tablet. Not too long ago I discovered how to root it and apparently I'm the first to do it as far as I can tell. Now here's how.
What you will need is Bin4ary's One Touch Root App. This app will get you only partial root via the ADB Shell. My guess is the ADB exploit he uses does work to get basic root access for ADB, but some incompatibility prevents proper installation of su & SuperUser.apk. What we're going to do is finish the job manually.
First run Bin4ary's app and use the Normal Method. Be sure to ignore all errors. After your tablet reboots move su and Superuser.apk from Bin4ry's app folder to the root of the Internal SDCard. Next you will need ADB. If you don't have it you can get it either from Bin4ary's app folder you found su & superuser.apk in or you can install the Android SDK. At the command prompt enter the following:
Code:
adb shell
su
At this point you should see a # sign indicating root privileges. If you do enter the following commands.
Code:
mv /system/xbin/su /system/xbin/osu
cp /sdcard/su /system/xbin
chmod 6755 /system/xbin/su
The use Astro or your favorite file manager to navigate to /sdcard and install SuperUser.apk then reboot your tablet. From here on you should have full root on your tablet. Credit should definitely goto Bin4ry for his work on his One Touch Root App for getting us half way there.
Click to expand...
Click to collapse
Did NOT work for me.
1-On first attempt, got pound sign....tried to push code resulting in cant find SD
2-On second attempts, would not let me be superuser su
3-Did a factory reset....same results as (2)
Im stomped!....please help

Amlogic Next8HD8G (NX008HD8G) Modified Recovery - Stock Rom - Root & Gapps
Modified recovery, stock rom, flashable root and flashable Gapps here: http://www.freaktab.com/showthread.php?7010-Amlogic-Next8HD8G-%28NX008HD8G%29-Modified-Recovery-Stock-Rom-amp-Flashable-Root
ShaunMT

Confirmed as well..
Ty... no fusses at all..

zenkillizen said:
Ty... no fusses at all..
Click to expand...
Click to collapse
I need someone to be more clear on rooting this device because I already bricked one using the method from tab freaks instructions aren't that clear and I don't want to brick another one ! Please thanks

andrew09 said:
I need someone to be more clear on rooting this device because I already bricked one using the method from tab freaks instructions aren't that clear and I don't want to brick another one ! Please thanks
Click to expand...
Click to collapse
this guide is like the clearest root guide I've seen Just sit down and read it, take your time Rooting my seem hard at first, but you catch on

Aiko0923 said:
this guide is like the clearest root guide I've seen Just sit down and read it, take your time Rooting my seem hard at first, but you catch on
Click to expand...
Click to collapse
Parts are missing from the guide like how to install the adb drivers the computer needs to recognise the tablet first before u try and root it I have read through it and I've already bricked one also I noticed if you go to recovery on this tablet it erases the system and factory reset doesn't fix anything there's no factory ROMs or anything to fix it if it messes up. If someone can't a sure me that the method is correct I'll do it I'll try it.

Does this method work on the newer models say model number starting with YFG12 and up?

I bought this today.
I am having problems here:
I did what you said to do:
Normal Mode enabled!
Pushing busybox....
4806 KB/s (1165484 bytes in 0.236s)
Pushing su binary ....
7134 KB/s (104576 bytes in 0.014s)
Pushing Superuser app
6792 KB/s (2139595 bytes in 0.307s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
RunMe.sh: line 222: wait: pid 10 is not a child of this shell
Waiting for device to show up again....
RunMe.sh: line 225: wait: pid 10 is not a child of this shell
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
---
And then I copied the files su and the .apk to /sdcard
Then I try to run su, and it says:
su
/system/bin/sh: su: not found
so I do
[email protected]:/sdcard $ ./su
/system/bin/sh: ./su: can't execute: Permission denied
---
Other times, it just does this:
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
and it runs forever
what do I do?

http://www.cydiaimpactor.com/
Worked for me.

YES! use cydia impactor
H0wdy said:
http://www.cydiaimpactor.com/
Worked for me.
Click to expand...
Click to collapse
Yes, I used it also. worked for me too (my serial for the tablet is YF07... in case there is a problem with the newer versions)
Thanks, H0wdy
Steps to do it:
Download Cydia Impactor
Turn on USB debug in settings-> Developer options
Plug in tablet into PC (I used a 32 bit Windows 8.1)
Wait a while... a long while for me... for windows to download drivers, disconnect tablet, wait a few seconds, then reconnect.
you should see in the device manager (on the top) android phone and underneath Android Composite ADB interface
Unzip Cydia, run impactor.exe and just choose start for # drop SuperSU su to /system/xbin/su
Wait a bit, then you're done. (no reboot or anything else necessary).
Install supersu (or I guess any other superuser app) from the android market. It will tell you that you can update the su binary... your choice, I updated without a problem.
I had supersu installed beforehand, but I guess it has nothing to do with it, it wasn't working anyway)
Ranting, but maybe someone has this issue also:
One ( -- BIG --) problem I had was getting the connection between the tablet and my computer, and Not because I can't plug-in a cable
the tablet said it was connected, but on the computer, nothing showed up in device manager and the list of devices kept refreshing.
The PC was beep-ing just like it found a device. the device list would refresh once or twice, then again beep, all this till the end of my patience.
At first I thought it was the USB 3.0 port, then the cable, then the ESXi USB redirection (my desktop is actually a VM), then the windows version, then the architecture,
Then I switched to a laptop, nothing.. same story.
I can BET it's Sony's F***ed up drivers
So, I used a clean system (no other adb or phone drivers installed) and worked as a charm
I think I hat this much trouble because I had a lot of other drivers (for sony, samsung, universal adb, etc etc.)
So on the computer I had all this stuff installed, it looked like the tablet was connected, then disconnected in the space of 10-15 seconds, then repeat forever.
If this happens to you, use a clean windows.

[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