Related
lost root after updating the SU binary, flash the following in recovery:
http://downloads.androidsu.com/super...fgh-signed.zip
Then update to binary 3.0.3 from SU. Goto all apps, start superuser, under superuser information tap SU binary. Follow instructions.
Or download binary at: http://downloads.androidsu.com/superuser/su-bin-3.0.3-efgh-signed.zip and flash in recovery.
---------------------------------------------------------------------------
Update Superuser
1) update to binary 3.0.3 from SU. Goto all apps, start superuser, under superuser information tap SU binary. Follow instructions.
Or download binary at: http://downloads.androidsu.com/superuser/su-bin-3.0.3-efgh-signed.zip and flash in recovery.
2) Update SU to 3.0.6 via market. or download
http://downloads.androidsu.com/super...fgh-signed.zip and flash
3) clear the data from SU.
Credits go to HomerSP for the binary fix
Or you can do it manually...as posted by the OP (@theraver) in a different thread :
binary: http://dl.dropbox.com/u/11494687/superuser/su
to install do this:
Update to superuser 3.0.5 in the market (if you didn't do this)
adb remount
adb push su /system/bin/
adb shell chmod 06755 /system/bin/su
adb shell rm /data/data/com.noshufou.android.su/databases/permissions.*
bloodhawk said:
Or you can do it manually...as posted by the OP in a different thread :
binary: http://dl.dropbox.com/u/11494687/superuser/su
to install do this:
Update to superuser 3.0.5 in the market (if you didn't do this)
adb remount
adb push su /system/bin/
adb shell chmod 06755 /system/bin/su
adb shell rm /data/data/com.noshufou.android.su/databases/permissions.*
Click to expand...
Click to collapse
That;s correct . thats what i posted earlier today, lol
theraver said:
That;s correct . thats the fix i posted earlier today, lol
In which thread was it placed in the OP?
Click to expand...
Click to collapse
Didnt, find it any OP per se. It was there in Faux's HTC Stock kernel thread...
Have tested it across 4 ROM's by now. (Though shouldn't really make a difference)
- by OP i meant YOU. OP for this thread
bloodhawk said:
Didnt, find it any OP per se. It was there in Faux's HTC Stock kernel thread...
Have tested it across 4 ROM's by now. (Though shouldn't really make a difference)
- by OP i meant YOU. OP for this thread
Click to expand...
Click to collapse
edit post #1 because of new 3.0.6 SU!
It works for me! yay
Awesome, it worked for me too. They should put a thanks botton on the mobile app too.
Sent from my HTC Sensation 4G using XDA App
Thanks!No FCs so far
Sent from my greatest Sensation 4G with Beats Audio
Failed to push su as it says the directory is not empty...
paultcook said:
Failed to push su as it says the directory is not empty...
Click to expand...
Click to collapse
Fix for Superuser
1) Update to binary 3.0.2. Go to all apps, start superuser, under superuser information tap SU binary. Follow instructions. Or download binary at:
downloads.androidsu.com/superuser/su-3.0.2-bin-efgh-signed.zip and flash in recovery.
2) Update SU to 3.0.6 via market. or download update at:
http://downloads.androidsu.com/superuser/Superuser-3.0.6-efgh-signed.zip
and flash in recovery.
3) clear the data from SU if your still getting FC's
Credits go to HomerSP for coming up with the fix!!
broncogr said:
SU Binary 3.02 is out.
Update it through the superuser app settings
Click to expand...
Click to collapse
thanx. .
There are problems with 3.02!!!!
Dont update to it!!!!!
broncogr said:
There are problems with 3.02!!!!
Dont update to it!!!!!
Click to expand...
Click to collapse
problems are only on arm6 , sensation is arm7 so i have no problems
http://androidsu.com/2011/10/i-updated-to-3-0-1-binary-and-lost-root-help/
It removes root
http://androidsu.com/2011/10/i-updated-to-3-0-1-binary-and-lost-root-help/
justice26 said:
It removes root
Click to expand...
Click to collapse
only on arm6 chipset
http://androidsu.com/2011/10/i-updated-to-3-0-1-binary-and-lost-root-help/
lost root on HTC sensation?
I updated to 3.06 and also updated the binary...but then it seems I've lost root after I did that. I am not sure how to clear the data if I can't get into titanium backup?? I am using a HTC sensation.
Any ideas how I can fix it? Do I just flash the su file again in recovery?
Thx
newr said:
I updated to 3.06 and also updated the binary...but then it seems I've lost root after I did that. I am not sure how to clear the data if I can't get into titanium backup?? I am using a HTC sensation.
Any ideas how I can fix it? Do I just flash the su file again in recovery?
Thx
Click to expand...
Click to collapse
did you update to 3.0.1 binary? then you can try to flash 3.0.2 binary in recovery
http://downloads.androidsu.com/superuser/su-3.0.2-bin-efgh-signed.zip
I updated to SU3.06..and also updated the binary in there to 3.02...then I lost root. I just flashed the 3.06 file...still don't have root...so I need to flash 3.02 binary as well? It says I already have 3.02 binary when I open SU. I have clear data in the manage application on my phone....still the same problem
I loose ROOT with 3.0.2 bin update over market ad trought app.
Just flashed 3.0.1 binaries from recovery
downloads.androidsu.com/superuser/su-3.0.1-bin-efgh-signed.zip
Rooted again
Im having problems with the app "script manager" on se x10i running on custom ROM (feralabs v4). Is there an alternative for this app? Im trying to install v6 supercharger. Any help would be highly appreciated.
Sent from my X10 using XDA App
before running the script manager, you must install busybox first
a simply tutorial video
http://www.youtube.com/watch?v=75yH02rxUxI
I used to have problem too in installing v6 supercharger using script manager. I tried different busybox version but still had problems. Finally, I only installed it using terminal emulator. If you want to try it, here's how I did it:
- copy the downloaded v6 script to the root folder of the sdcard and rename it to v6.sh
- open terminal emulator
- type this command:
$ su [enter]
# sh /sdcard/v6.sh [enter]
- that will open v6 interface like usual and you can install it from there.
Only one drawback though, there's no widget that script manager provide to quick check v6 status. If I want to check it, then I have to run the command in the terminal again.
Sent from my SK17i using XDA App
Sent from my SK17i using XDA App
greenAlgae said:
I used to have problem too in installing v6 supercharger using script manager. I tried different busybox version but still had problems. Finally, I only installed it using terminal emulator. If you want to try it, here's how I did it:
- copy the downloaded v6 script to the root folder of the sdcard and rename it to v6.sh
- open terminal emulator
- type this command:
$ su [enter]
# sh /sdcard/v6.sh [enter]
- that will open v6 interface like usual and you can install it from there.
Only one drawback though, there's no widget that script manager provide to quick check v6 status. If I want to check it, then I have to run the command in the terminal again.
Sent from my SK17i using XDA App
Sent from my SK17i using XDA App
Click to expand...
Click to collapse
Thank you so much. This worked. Im now blazing on my x10i
Cheers.
Sent from my X10 using XDA App
glad I could help
Sent from my SK17i using XDA App
Installed v6 using the terminal method (smanager keeps fc) and it worked. Thanks. I know it's an old thread but it helped. Just a Q; how do i check if v6 is up? Do i enter sh /sdcard/v6.sh again?
keypad not working
hey i followed all steps. but when it come to choose a number my keypad dont work. what to do??
[Q] Re: "Busybox Uninstaller v1.0 - Removes busybox and its +600 symlink files"
I'm trying to use the script provided in the thread Busybox Uninstaller v1.0 - Remove busybox & its +600 symlink files [26 Aug 2012]. Would've asked this question there, but not allowed, being new to the forum. (Hello. First post.)
New to android in general, actually, but familiar with linux.
Anyhow, I tried using the script both using Flash from recovery method and running the script from terminal, but both fail.
Flash from recovery method fails with an error regarding package verification.
Not running CWM but the stock-thingy. Hardware is Samsung n8010 tablet. Factory-ROM (4.1.2) loaded through ODIN. Rooted.
Run script in terminal fails with a long row of "readling: applet not found".
Script was run in terminal, having su:ed and permitting root-rights. Also remounted system as RW.
Looking at bb-uninstall.log, I see a lot of
/system/bin/COMMAND is not linked to busybox but to ---> file not deleted
Click to expand...
Click to collapse
I have successfully built ClockworkMod for our HP Slate 7. I have been successful in backup and restore to and from internal SD and external SD. This is confirmed working on 2800 series and 4600 series tablets.
Prerequisites
You must have root to install this.
- Download ROOT install tool http://www.sjroot.com
- After tablet is rooted, install SuperSU from the market and update the su binary
- Verify root access with Root Checker or equivilent
Updates
-Confirmed working on 2800 series by user Joshua11007! Thanks!
-Confirmed working on 4600 series by goodguy25. Thanks!
-Added download link to stock recovery
Install at your own risk. I or anyone else am not responsible for the damage caused to your tablet or breaking warranty.
Issues
If you go into key test the only way out is to reboot is to hold the power button until tablet resets, but i think this normal.
Install from Windows *** Updated installer
If your tablet isn't rooted, please root it first. You must also have ADB working in Windows. This installer will not work from Linux, but I will provide steps below to flash from linux too.
Download attached zip file and extract on Windows PC.
Follow back-up procedure below if you want to backup your factory recovery first. (This can be skipped but you won't have your factory recovery image anymore if you skip it).
Run the Batch file labeled "Install-CWM.bat"
Done! The script will automatically reboot the tablet into recovery when complete.
Install from Linux
Ensure tablet is rooted
Download attached file and unzip it
Code:
adb push recovery.img /sdcard/
Code:
adb shell dd if=/sdcard/recovery.img of=/dev/block/mtd/by-name/recovery
Code:
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
Done! You have copied the recovery image to the internal SD, copied it to the recovery partition, and moved the factory recovery image so it doesn't over-write CWM the next time you reboot.
Backup Procedure
From your computer with ADB working
Code:
adb shell dd if=/dev/block/mtd/by-name/recovery of=/sdcard/factory-recovery.img
Code:
adb pull /sdcard/factory-recovery.img
You have copied the recovery partition to your internal SD and copied it to your computer.
Download Link
CWM 6.0.3.3
http://goo.gl/GDbDyc - Mega (Link Fixed 11/13/2014)
Stock Recovery
http://goo.gl/cGtlt1 - Mega
Reserved
Please can you upload a stock recovery backup? Thanks!!
rjwil1086 said:
I have successfully built ClockworkMod for our HP Slate 7. I have only tested this on my Slate, which is a 2800. I have been successful in backup and restore to and from internal SD and external SD. I don't have a ROM to test with yet but once I do, I will verify ROM installation works as well.
I hope this goes without saying, but I am the only person that has tested this, so install at your own risk. I or anyone else am not responsible for the damage caused to your tablet or breaking warranty.
Issues
None that I am aware of. Please let me know otherwise.
Install from Windows
If your tablet isn't rooted, please root it first. You must also have ADB working in Windows. This installer will not work from Linux, but I will provide steps below to flash from linux too.
Download attached zip file and extract on Windows PC.
Follow back-up procedure below if you want to backup your factory recovery first. (This can be skipped but you won't have your factory recovery image anymore if you skip it).
Run the Batch file labeled "Install-CWM.bat"
Done! The script will automatically reboot the tablet into recovery when complete.
Install from Linux
Ensure tablet is rooted
Download attached file and unzip it
Code:
adb push recovery.img /sdcard/
Code:
adb shell dd if=/sdcard/recovery.img of=/dev/block/mtd/by-name/recovery
Code:
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
Done! You have copied the recovery image to the internal SD, copied it to the recovery partition, and moved the factory recovery image so it doesn't over-write CWM the next time you reboot.
Backup Procedure
From your computer with ADB working
Code:
adb shell dd if=/dev/block/mtd/by-name/recovery of=/sdcard/factory-recovery.img
Code:
adb pull /sdcard/factory-recovery.img
You have copied the recovery partition to your internal SD and copied it to your computer.
Download Link
http://goo.gl/aGjiij - Mega
Click to expand...
Click to collapse
Please can you upload a stock recovery.img backup? Thanks!! :good:
J001E said:
Please can you upload a stock recovery.img backup? Thanks!! :good:
Click to expand...
Click to collapse
I have added a link to the op. Thanks.
Just tested, I can confirm it works.
Most easy way to install on linux :
Use this rkflashkit
Also works across 4600 models. Just don't use key test as you'll trap yourself inside and have to power off manually.
Sent from my HP Slate 7 using Tapatalk
how to flash stock recovery?
preferably from CWM
Just so you guys know I got a request to port my custom ROM for the Slate 7 Plus to the Slate 7 and worst case scenario I can get a build out Monday.
Sent from my Sero 7 Pro using Tapatalk
gless said:
how to flash stock recovery?
preferably from CWM
Click to expand...
Click to collapse
You can flash the stock recovery via Flashify if you're rooted.
Sent from my Sero 7 Pro using Tapatalk
I tried to install this by it comes up with an error:
/dev/block/mtd/by-name/recovery: cannot open for write: Permission denied
Click to expand...
Click to collapse
Any advice? Thanks!
Python. said:
I tried to install this by it comes up with an error:
Any advice? Thanks!
Click to expand...
Click to collapse
Are you rooted?
Sent from my HP Slate 7 using Tapatalk
goodguy25 said:
Are you rooted?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
Yep. That was the first thing I checked. Confirmed it with Root Checker...
Edit: For extra information, I have the HP Slate 7 2801 (Same as the 2800 version)
Python. said:
Yep. That was the first thing I checked. Confirmed it with Root Checker...
Click to expand...
Click to collapse
If I were you, I would get the Cwm recovery on to the tablet, then using terminal emulator to backup the stock recovery and install the Cwm one.
Sent from my HP Slate 7 using Tapatalk
goodguy25 said:
If I were you, I would get the Cwm recovery on to the tablet, then using terminal emulator to backup the stock recovery and install the Cwm one.
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
Could you clarify that? How would I get CWM recovery on to the tablet? I'm getting the error message when running the Batch file 'Install-CWM.bat'. The cmd console has that message about permission being denied and then it says installation complete and press to reboot. When rebooting, it goes to the stock recovery...
Python. said:
Could you clarify that? How would I get CWM recovery on to the tablet? I'm getting the error message when running the Batch file 'Install-CWM.bat'. The cmd console has that message about permission being denied and then it says installation complete and press to reboot. When rebooting, it goes to the stock recovery...
Click to expand...
Click to collapse
Try taking the CWM .IMG file and flashing it via Flashify.
Sent from my Sero 7 Pro using Tapatalk
I looked through my batch script. I think I need to modify it because it's not executing as root. Use the steps I created for Linux except from Windows command prompt. That's all the batch file is doing.
Sent from my LG-E970 using XDA Premium 4 mobile app
jerbear294 said:
Try taking the CWM .IMG file and flashing it via Flashify.
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
I tried this but when I open Flashify, it says 'You don't have root/superuser access'. But, Root Checker says that I have root and SuperSU is working...
rjwil1086 said:
I looked through my batch script. I think I need to modify it because it's not executing as root. Use the steps I created for Linux except from Windows command prompt. That's all the batch file is doing.
Sent from my LG-E970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried doing that but there's an error on Step 2:
rjwil1086 said:
adb shell dd if=/sdcard/recovery.img of=/dev/block/mtd/by-name/recovery
Click to expand...
Click to collapse
It states that:
Code:
/dev/block/mtd/by-name/recovery: cannot open for write: Permission denied
Python. said:
I tried this but when I open Flashify, it says 'You don't have root/superuser access'. But, Root Checker says that I have root and SuperSU is working...
I tried doing that but there's an error on Step 2:
It states that:
Code:
/dev/block/mtd/by-name/recovery: cannot open for write: Permission denied
Click to expand...
Click to collapse
Strange. Try rerooting, both issues are connected to root. It could be the SU binary as well, does SuperSU want you to update?
Sent from my Sero 7 Pro using Tapatalk
jerbear294 said:
Strange. Try rerooting, both issues are connected to root. It could be the SU binary as well, does SuperSU want you to update?
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
I've tried rebooting several times, SuperSU doesn't need an update but it's still not working...
I'll need a bit more time to make the ROM. Sorry guys, I've been trying to tackle an issue with porting CWM to the Slate 7 Plus. I will definitely have a ROM for you guys by the time Saturday rolls around.
Sent from my Sero 7 Pro using Tapatalk
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.