When i check Root with Root Checker, in Stage 2 is Superuser Binary files : Not Installed. How repair this problem ?
Marek89 said:
When i check Root with Root Checker, in Stage 2 is Superuser Binary files : Not Installed. How repair this problem ?
Click to expand...
Click to collapse
Use magisk
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
i use magisk, but root checker not see binnary files.
any solution to my problem ?
Superuser Binary Files : Not Installed
black_file said:
Use magisk
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Click to expand...
Click to collapse
Rooted my phone by flashing Magisk 19.3. Root Checker verifies- the device is rooted but it also states :
Stage 2 - Superuser Binary
Files: Not Installed
Standard System Location
Command: Is -I /system/bin/su
Result: Is: /system/bin/su. No
such file or directory
Analysis: File /system/bin/su
does not exist.
Standard System Location
Command: Is -I /system/xbin/su
Result: Is: /system/xbin/su: No
such file or directory
Analysis. File /system/xbin/su
does not exist.
Standard System-less Location
Command: Is -I /su/bin/su
Result: Is: /su/bin/su: No such file
or directory
Analysis: File /su/bin/su does not
exist.
Alternative Location
Command; Is -I /sbin/su
Result: Irwxrwxrwx 1 root root
12 1970-03-26 00:23 /sbin/su -> /
sbin/magisk
Analysis:
Alternative Location
Command: Is -I /system/sbin/su
Result: Is; /system/sbin/su: No
such file or directory
Analysis: File/system/sbin/su
does not exist.
Alternative Location
Command: Is -I /system/xbin/
sudo
Result: Is: /system/xbin/sudo: No
such file or directory
Analysis: File/system/xbin/sudo
does not exist.
Should I be worried about this ? Should I install Supersu and update the binaries OR should the message be ignored.
I read on the forum that Magisk is an alternative to Supersu so am confused.Please enlighten :angel: a newbie.
Root Checker screenshot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@GOD-TheSupreme
The root checker used doesn't recognise Magisk. It finds it:
Code:
Alternative Location
Command; Is -I /sbin/su
Result: Irwxrwxrwx 1 root root
12 1970-03-26 00:23 /sbin/su -> /
sbin/magisk
But, it doesn't know what it's looking at. It's probably not been updated in a long time and still think that SuperSU is the way to go...
Root checkers feel like quite an outdated thing though. If you have root, you'll see it in the Magisk Manager.
And by the way, superuser is not the same thing as SuperSU...
Binary files not installed
Have root on kindle fire with kingroot but su binary files not installed
Hi, im noob in rooting And i install magisk new version And root with SuperSU root Is compleate but "stage 2 supersu binary files not found" And my 128gb Samsung Galaxy S10 convert to 32gb when i put original firmware all Its ok but i want root And 32gb Its low And moduls in magisk noting do can't change my ui design or any in system anyone help please
Fresz
Related
Hi,
i have rooted my phone and applied newest recovery following every instruction on this site to the letter.
also installed and using fyodor's excellent rom since it's first release.
when i use adb i always obtain root # and have done so since flashing and entering commands
but when i try to access root on my phone (root explorer for example) i am now unable to mount rw/ro?? and cannot browse files. i also use cachemate which appears to gain root access and do its job
any help much appreciated as to how to solve this issue and allow my phone to recognise root
thank you for any help
Hi huetson2:
Try to execute the command below(on PC):
Code:
adb shell ls -l /system/sbin/su
If you get this output, I think rootExplorer and others(e.g.: Autostarts, setCPU) will work properly.
Code:
-rwsr-sr-x root root 76232 2008-08-01 20:00 su
cn.fyodor said:
Hi huetson2:
Try to execute the command below(on PC):
Code:
adb shell ls -l /system/sbin/su
If you get this output, I think rootExplorer and others(e.g.: Autostarts, setCPU) will work properly.
Code:
-rwsr-sr-x root root 76232 2008-08-01 20:00 su
Click to expand...
Click to collapse
-rwsr-sr-x root root 76232 2008-08-01 13:00 su
but still no root on phone!, got an error message on handset telling me su cannot be found?
setcpu not working either,
I have a similar problem. I'll post a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: adding some info... If I type "su" from terminal emulator, it says something like "access granted, courtesy of magicandroidapps.com.
Root explorer works ok...
Chackemate and SetCPU work...
I'm running one-click root, unleash the beast, circle battery and ext2 lag fix. Unleash the beast updated my hosts file to block ads but unfortunately also blocks the Audiogalaxy servers which I'd like to use for their new streaming app.
Trying to edit the hosts file I did an adp pull to my PC, edited the file and saved. But I can't push it back to /system/etc/hosts as I get a "permission denied" error.
After some reading it seems this means my root directory doesn't mounted with write permissions. I tried "adb root" but it gives me error "cannot run as root in production builds" and tried "adb remount" but that gives me error "remount failed: No such file or directory". I'm stuck at this point.
Any ideas? Could this be because I'm running the ext2 lag fix?
phishie said:
I'm running one-click root, unleash the beast, circle battery and ext2 lag fix. Unleash the beast updated my hosts file to block ads but unfortunately also blocks the Audiogalaxy servers which I'd like to use for their new streaming app.
Trying to edit the hosts file I did an adp pull to my PC, edited the file and saved. But I can't push it back to /system/etc/hosts as I get a "permission denied" error.
After some reading it seems this means my root directory doesn't mounted with write permissions. I tried "adb root" but it gives me error "cannot run as root in production builds" and tried "adb remount" but that gives me error "remount failed: No such file or directory". I'm stuck at this point.
Any ideas? Could this be because I'm running the ext2 lag fix?
Click to expand...
Click to collapse
did you type in su before using pushing the file?
Edit: it would be like this
su (press enter)
adb push blah*
tytdfn said:
did you type in su before using pushing the file?
Edit: it would be like this
su (press enter)
adb push blah*
Click to expand...
Click to collapse
Yea I had tried that. "su" by itself is not a recognized command. "adb su" just prints the adb help text (lists commands).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok maybe I need to simplify my question:
Does anyone know how to get the root directory to mount to USB with write permissions?
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/media/<filename>
busybox mv /sdcard/<filename> /system/media
Hope that helps.
Click to expand...
Click to collapse
Cool I'll try that, are you running any lag fixes by chance?
phishie said:
Cool I'll try that, are you running any lag fixes by chance?
Click to expand...
Click to collapse
Yeah, the one that come in the old SuperRooter.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
Click to expand...
Click to collapse
Permission denied when trying to push to /sdcard.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
Click to expand...
Click to collapse
By the way this worked perfectly once I realized I needed to physically approve the "su" request on the phone. Thanks again.
After a little looking around, I found a great boot animation by another guy from the xda forums, and I modded it a bit for the G Tablet.
Here's a preview:
(All credit goes to ASimmons for making this AWESOME animation.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To install it,
adb push bootanimation.zip /logodata
Click to expand...
Click to collapse
Use 7zip to extract the zip file.
I love this! Can I install it without adb? I haven't gotten it working properly on my XP x64 machine.
Mine boots up so quickly, I never get to see the entire automation. Thanks!
I used RootExplorer to copy this over, since I don't have the SDK stuff loaded.
Thanks for the animation but it does not seem to work with VEGAn Beta 4 ROM image I recently loaded. I see it is the same size but cant get it to show - it just shows the normal VEGAn Android animation. Is there something I am doing wrong. Here is output of my what is in my logodata directory:
# ls -l
-rw-rw-rw- root root 16610683 2010-12-29 09:33 bootanimation.zip
-rwxr--r-- adb compass 2359350 2010-09-28 02:43 boot2.bmp
drw-rw-rw- root root 2010-12-30 12:38 lost+found
-rwxr--r-- adb compass 620888 2009-07-14 04:52 Tulips.jpg
Is it a permissions thing - I even set it to executable with chmod and still no different animation.
Anagin thanks for the animation - is there something I am doing wrong?
powerx86 said:
Thanks for the animation but it does not seem to work with VEGAn Beta 4 ROM image I recently loaded. I see it is the same size but cant get it to show - it just shows the normal VEGAn Android animation. Is there something I am doing wrong. Here is output of my what is in my logodata directory:
# ls -l
-rw-rw-rw- root root 16610683 2010-12-29 09:33 bootanimation.zip
-rwxr--r-- adb compass 2359350 2010-09-28 02:43 boot2.bmp
drw-rw-rw- root root 2010-12-30 12:38 lost+found
-rwxr--r-- adb compass 620888 2009-07-14 04:52 Tulips.jpg
Is it a permissions thing - I even set it to executable with chmod and still no different animation.
Anagin thanks for the animation - is there something I am doing wrong?
Click to expand...
Click to collapse
I have heard of some people saying that they find the bootanimation under a media directory instead of the logodata, is it possible that for the Vegan ROM that this zip must be put somewhere else?
Take a look at this post, perhaps it will help?
http://forum.xda-developers.com/showthread.php?t=878143&highlight=bootanimation
It didn't work the first time I install because androzip extracted damage zip file. I had to unzip it from my computer then transfer it over to the tablet. Use root explorer to copy it over to system/media.
If you get time can you post a step By step for us total newbs. I assume I just unzip and transfer via a USB cable but that's about it. (wouldnt insoluble exactly where to abstract it and if any other steps are involved)
I logged back on to the shell and did not see any other bootanimation other an executable bootanimation in the following folder:
/system/bin/
So I looked in the /system/media folder and no bootanimation.zip just the following:
# pwd
/system/media
# ls -l
drwxr-xr-x root root 2010-12-29 21:26 audio
I copied the bootanimation.zip file to that directory after reading multiple posts about the file being located in /system/media.
Here is the link that directs you to do the same.
http://forum.xda-developers.com/show...=bootanimation
I finally got this to work and at least for the VEGAn 4, the bootanimation.zip must reside in the /system/media folder.
Basic instructions are as follows and done in Linux:
Requirement: a way to copy data to /system folder (like adb tool). Here are the steps I used.
a) Enter the Android Shell using: ./adb shell
b) At the # prompt enter: mount
c) You should see the following as a READ-Only
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
d) Now you need to make this Read/Write to do this use the following commands:
mount -o rw,remount -t ext2 /dev/block/mtdblock3 /system
e) validate the mount is now read/write by re-executing the mount command - enter the following:
mount
f) You should see the following if everything worked to make this folder read/write:
/dev/block/mtdblock3 /system yaffs2 rw,relatime 0 0
g) Now lets exit the shell type the following:
exit
h) Now push the bootanimation.zip to the android device using the following command:
./adb push bootanimation.zip /system/media
i) Now lets reboot the Android device - execute the following:
./adb reboot
This worked and I have tried a few others. Thanks to all the tips to help me figure this out!
>>>>>>>>>>>>>>>>>>>>>>>>: (
>>>>>>>>>>>>>>>>:V
i wanted to use a gif that is around 40 mb 35 seconds long is that something that is possible to do or will i have to shorten it
is it possible to even use a gif
Is there anyway to have sound go along with the bootanimation?
Some phone bootani's have sound -- but I've never been able to get it to work properly after changing the stock...
Thank you for this boot animation. I have been presented with so many choices for customization, that it is hard to choose. I love this little tablet.
CM App Installer will pull the latest versions of the apps available that CyanogenMod exclusively develop, and give you the option to install them to your system either rooted or non-rooted. I cannot guarantee success with this, I don't develop the application, my job is simply to make it easier for you guys to get your favourite CyanogenMod apps on your own ROMs!
Use carefully! As ever, I do not take responsibilty for any damage done to your device as a result of this! The root features use the code specified in "code" in the options menu, or it's listed below. If you're paranoid, please give it a read
I have to emphasise, please try the non-root method first!. The root method is designed as a last ditch attempt to get it working, it does backup and restore your old versions but errors do happen, expect this as a possibility if you're rooted!
The list of apps available in the application are:
Apollo
Calculator
CM File Manager
Torch
Messaging
DSP Manager
Voice+
News and Weather Widget
Trebuchet Launcher
cLock Widget
Movie Studio
CM Wallpapers
Let me know if you have any more suggestions to add!
Code
This information is also available from within the application.
There are a number of commands that this application uses, it executes certain processes through the code to copy apps to the system directory.
These commands are ran as if they were ran inside the terminal emulator, and always consist of
process, remount to read-write, transfer/copy/rename, remount to read-only, close. (In this order).
I use a Process to get a SU Runtime instance
Code:
Process p = Runtime.getRuntime().exec("su");
And then I use a PrintStream to issue the commands listed below to it.
Remount the system partition as read-write
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Rename an app (use move command to move with a different extension - Creating backups)
Code:
mv /system/app/AppOfChoice.apk /system/app/AppOfChoice.bak
Copy an app from SD card to System directory
Code:
cat /sdcard/CMApps/AppOfChoice.apk > /system/app/AppOfChoice.apk
Remove an app from system partition
Code:
rm -r /system/app/AppOfChoice.apk
For permissions, I use chmod
Code:
chmod 644 /system/app/AppOfChoice.apk
Remount the system partition as read-only
Code:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
And that is it. The process commands get pushed over the course of about two seconds, and should work. Again, I can't promise everything.
Credit also goes to the Reddit member /u/wchill, his code helped with the system code (shown in the Code section above)
Similarly, I do not take any responsibility if this app causes your phone to be bricked, corrupted, broken, or to encounter an unfortunate case of spontaneous combustion. Use at your own risk.
In the mean time, enjoy!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source:
See this xda thread
Today i got an issue for my N960F after flashing a custom ROM. I'm not sure till now what've gone wrong, but after rebooting my device i faced an issue that my SIM card can not register on network.
Cellular network signal is full, but can not make any calls and can not connect to data.
Tried to restore through TWRP with a nand backup, but always fails as EFS partition can not be mounted. Eventually I managed to restore my EFS partition after following the hereunder steps.
I'll just leave it here if anyone faced the same in the future.
Disclaimer: You are doing this at your own risk. I shall not be held liable for any losses or bricked devices ( They already are )
Pre requisites:
- ADB on your PC, latest SDK is preferred.
- Custom recovery ( with ADB enabled )
- Better to have a previous EFS backup
Steps:
- Reboot into recovery and enable ADB ( in TWRP, ADB is enabled by default )
- Attach your device to your PC. and open your terminal or command prompt as an admin.
- Type the following commands:
- Navigate to your ADB folder ( in my case it is C:/ADB )
cd C:/ADB
- Ensure that your phone is readable in ADB mode
c:\ADB>adb devices[ATTACH type="full"]5610649[/ATTACH]
c:\ADB>adb shell
Your terminal handle should change into root ~ #
~ # cd /dev/block
/dev/block # ls
you should get an output like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/dev/block # cd by-name
/dev/block/by-name # ls -la
you should see device partitions listed as this .. EFS partition is highlighted in yellow and is on sda3 as below
/dev/block/by-name # mke2fs /dev/block/sda3
and you should be prompted by a message to proceed or not. Press y then enter
Finally,
/dev/block/by-name # mount -w -t ext4 /dev/block/sda3
We successfully formatted and mounted EFS partition and now either to restore your old EFS backup or flash stock firmware through ODIN.
Resources: