hello
Today was the first time I joined.
DisasterROM_v8 bugs will tell.
Was a supersu DisasterROM_v7 DisasterROM_v8 do not have su and superuser privileges error appears.
Rom developers solve problems related supersu by Please
8.0 7.0 original rom the xbin su was not xbin busybox and su-related files.Re-upload please.
Xbin 7.0 and 8.0 below screen syaseun comparison photos.
I'm sorry, but I've used Google translate.
Can write well by the developers who made Erom!
Installed su binary and supersu can not be installed.
Problems.!
Reflash any other compatible kernel. Something like Philz kernel : http://forum.xda-developers.com/showthread.php?t=1877270
jl10101 said:
Reflash any other compatible kernel. Something like Philz kernel : http://forum.xda-developers.com/showthread.php?t=1877270
Click to expand...
Click to collapse
I have a solution.
1. Download http://downloadandroidrom.com/file/tools/SuperSU/CWM-SuperSU-v0.99.zip and put on sd card
2. Reboot into recovery
3. flash this zip
4. In recovery go to advanced, and Fix permissions
5. Reboot and enjoy your rom with working superuser
6. Run Google play and let the supersu app to update
i have some problem with the updated busybox.
i flash it in my custom either stock also.
but when i open root explorer it gives permission to root explorer but after closing root explorer and again open it . shows me permission request again and again.
kartik verma said:
i have some problem with the updated busybox.
i flash it in my custom either stock also.
but when i open root explorer it gives permission to root explorer but after closing root explorer and again open it . shows me permission request again and again.
Click to expand...
Click to collapse
Not sure this has anything to do with BusyBox. You don't have to have it installed to run as root and to grant SuperUser access to apps like Root Explorer.
What phone? Custom rom or stock rooted? What update is it running? Do you have issues with other root apps? Are you using SuperSU or SuperUser? What method was used to root? Is the superuser binary updated?
es0tericcha0s said:
Not sure this has anything to do with BusyBox. You don't have to have it installed to run as root and to grant SuperUser access to apps like Root Explorer.
What phone? Custom rom or stock rooted? What update is it running? Do you have issues with other root apps? Are you using SuperSU or SuperUser? What method was used to root? Is the superuser binary updated?
Click to expand...
Click to collapse
really sir this happens. m using super user and my device is galaxy y duos. the busy box size is 1.11 mb . and i also have another problem. some one makes a tool to odex a custom rom tool name is "universal odex script" ir works in galaxy y well. but when i use it in galaxy y duos it gives "busybox permission denied"
kartik verma said:
really sir this happens. m using super user and my device is galaxy y duos. the busy box size is 1.11 mb . and i also have another problem. some one makes a tool to odex a custom rom tool name is "universal odex script" ir works in galaxy y well. but when i use it in galaxy y duos it gives "busybox permission denied"
Click to expand...
Click to collapse
Well since you didn't answer half the questions, I'm just going to suggest to switch to SuperSU by Chainfire. Also, which method of Busybox are you using to install? Did it install correctly? What version of Busybox is it?
How to install the SuperSU from Chainfire, I use the build of CM 20/12/2016, but every time I flash the SuperSU zip I brikea the cell, I deleted the SU from bin and xbin
RubenPCA said:
How to install the SuperSU from Chainfire, I use the build of CM 20/12/2016, but every time I flash the SuperSU zip I brikea the cell, I deleted the SU from bin and xbin
Click to expand...
Click to collapse
You have to install SuperSU V2.79.
Introduction: Since the last days I encountered several problems after updating SuperSU (updating from stable 2.79 to 2.80 then 2.81 then finally 2.82).
Refer to https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Also SuperSU (2.80, 2.81) now requires a lot of new permissions not needed for pure root functions, and since it is now owned by Chinese CCMT company,
I prefer another root solution, and discover Magisk and MagiskSU (Magisk/MagiskSU is open source which is excellent for privacy and security).
Magisk official topic: Magisk v12.0 - Root & Universal Systemless Interface [Android 5.0+]
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
All about Magisk:
https://forum.xda-developers.com/apps/magisk
[UNOFFICIAL] Magisk v13 and MagiskManager v5.0 snapshots
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
I follow the Magisk official topic and try to install Magisk (v12.0 and Magisk manager v4.3.3 from Playstore).
But no root is operational, root is installed but no root persmissions!
After reading some discussion https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382, I decided try the latest Magisk beta (snapshot):
I use:
MagiskManager-v5.0-170612.apk from https://github.com/stangri/MagiskFiles Direct download link: https://github.com/stangri/MagiskFiles/blob/master/MagiskManager-v5.0-170612.apk
Magisk-v13-170612.zip from https://github.com/stangri/MagiskFiles Direct download link: https://github.com/stangri/MagiskFiles/blob/master/Magisk-v13-170612.zip
Magisk-v13-170612-Uninstaller.zip (not needed, just in case) from https://github.com/stangri/MagiskFiles Direct download link: https://github.com/stangri/MagiskFiles/blob/master/Magisk-v13-170612-Uninstaller.zip
UPDATE-unSU-signed.zip from https://forum.xda-developers.com/showpost.php?p=63615067
A2017G-N-B04-boot.img from https://www.androidfilehost.com/?fid=889764386195902948 (original topic: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 )
A2017G-N-B05-boot.img from https://www.androidfilehost.com/?fid=817550096634782427 (original topic: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 )
TWRP 3.1.1-0: https://www.androidfilehost.com/?fid=889764386195900705 (original topic: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
And it works, root is OK, root checker passed, and when enabling Magisk Hide in Magisk manager: Safetynet check passed!
This would mean function like Android Pay should be OK too for interested users.
(Add) To get Google Play Store Settings as Certified: select Magisk hide in Magisk manager, check the box corresponding to Play Store, clear Play Store data => certified. So applications like Netflix would be now available in Play Store (they are hidden for rooted (= not certified) phone.
Procedure I followed:
- Current phone status: unlocked bootloader, stock ROM Nougat B04, TWRP recovery 3.1.1-0, root with SuperSU 2.82 (systemless)
- (optional, but recommended for safety) backup with latest TWRP 3.1.1-0: boot, recovery, system, data, cache
- reboot into TWRP, then in this order during same session: install zip UPDATE-unSU-signed.zip, install image A2017G-N-B04-boot.img, install zip Magisk-v13-170528.zip , reboot system => normal boot OK
- Under Android: click on apk to install magisk manager MagiskManager-v5.0-170528.apk (must first enable Unknown sources in Phone Setting/Security) -
- Run MagiskManager: MagiskManager ok, MagiskSU OK!, enable Magisk hide: Safetynet check passed!
- disable "Unknown sources" in phone settings/Security.
Notes:
- If you have SuperSU 2.79, 2.80 or 2.81 this should work too.
- UPDATE-unSU-signed.zip is used to completely remove/uninstall SuperSU first, which helps Magisk install, although Magisk has actions to uninstall
SuperSU by itself.
- This procedure should work too (not tried) for other model like A2017 or A2017U, just be careful to replace the A2017G-N-B04-boot.img boot image with the one corresponding to your model (you could extract boot.img from your model ROM zip).
Edit (add):
- This procedure works also for Nougat B05. Just use A2017G-N-B05-boot.img instead of A2017G-N-B04-boot.img.
- You can use more updated version of Magisk and Magisk Manager.
- If you do not have SuperSU installed, you can skip all steps related to SuperSU.
Uh. How do I download from GitHub?
senny22 said:
Uh. How do I download from GitHub?
Click to expand...
Click to collapse
Well, links to Github are not direct download link, you open it with a browser, then you see a list of apk/zip files with different dates (build).
You then choose a file (for example file with the latest date) by clicking on its name, it will get you to a new page where there is a Download button.
dnlilas said:
Well, links to Github are not direct download link, you open it with a browser, then you see a list of apk/zip files with different dates (build).
You then choose a file (for example file with the latest date) by clicking on its name, it will get you to a new page where there is a Download button.
Click to expand...
Click to collapse
When I press the chosen file (example magisk apk) it brings me to a new page but where the download link is supposed to be it instead says "the file is to big to show". Do I need to be on a PC?
senny22 said:
When I press the chosen file (example magisk apk) it brings me to a new page but where the download link is supposed to be it instead says "the file is to big to show". Do I need to be on a PC?
Click to expand...
Click to collapse
There is in fact a "download" button to download the file. You probably need a PC for this. I will edit the post to add direct download links.
dnlilas said:
There is in fact a "download" button to download the file. You probably need a PC for this. I will edit the post to add direct download links.
Click to expand...
Click to collapse
Got it. Apparently you need a PC.
I tried to install this on V2.0.0B01 chinese.
All passed green except the ctsProfile which returns false.
SU from magisksu works btw. what does ctsProfile mean?
Also, if I tried to enable su for apps and adb, basic integrity gives false too.
@otaconremo
Did you enable Magisk Hide? Maybe this could help:
https://www.youtube.com/watch?v=Bd3GpYd9V5U
dnlilas said:
@otaconremo
Did you enable Magisk Hide? Maybe this could help:
https://www.youtube.com/watch?v=Bd3GpYd9V5U
Click to expand...
Click to collapse
Yes I did enable magisk hide. It's enabled by default and I even toggled it on and off. Also, magisk app force closes whenever I grant su access to any app. But it still does give me su anyway.
To note, v13 is the only version that works on the chinese variant so far. All other previous versions doesn't allow me to boot my device. Maybe because we don't have a custom kernel/boot to begin with.
Any way to use this in the A2017U running b25?
Can you please update files?
dodo34 said:
Can you please update files?
Click to expand...
Click to collapse
Update to latest Magisk files as of today.
ok. i tried it but system is craching inside android.
Thanks, works perfect.
Only SafetyNet check in magisk isnt succesfull.
What to do to pass the check?
When i go on Storage in Settings i get a system carsh error. Is everything ok with your phone ?
Spillunke said:
Thanks, works perfect.
Only SafetyNet check in magisk isnt succesfull.
Click to expand...
Click to collapse
dodo34 said:
When i go on Storage in Settings i get a system carsh error. Is everything ok with your phone ?
Click to expand...
Click to collapse
Yep.
Installed/flashed Magisk 13.3 and now SafetyNet Check works
Thanks :good:. The method worked for me with B05 and Magisk 13.3.
I used the same method with B06. Magisk Manager 13.3 kept crashing but it seems more stable with Magisk 14.0.
I was new for rooting and choose the easiest way to root(kingoroot not kingroot) my samsung galaxy j1 ace...
and now i want to switch to supersu from kingo superuser...
as kingroot being more famous... i didnt found any tutorials too... some are using supersu me...
i have no idea what to do... i want to clear the remainants of kingo too...
help me...
A procedure is here:
https://forum.xda-developers.com/an...g/replace-kingoroot-supersu-manually-t3573361
My device stores applications in directories in /data/app, ex:
com.kingoapp.apk-1, com.kingouser.com-2, eu.chainfire.supersu-1,
with subdirectories, lib and oat...
Any help to transpose the procedure above into this environment?
pascal.malaise said:
A procedure is here:
https://forum.xda-developers.com/an...g/replace-kingoroot-supersu-manually-t3573361
My device stores applications in directories in /data/app, ex:
com.kingoapp.apk-1, com.kingouser.com-2, eu.chainfire.supersu-1,
with subdirectories, lib and oat...
Any help to transpose the procedure above into this environment?
Click to expand...
Click to collapse
can u suggest me something easy???... like with terminal....
Revert to stock rom and try the manual rooting using SuperSU. You'll need a compatible custom recovery to install supersu.
rolland.arriza said:
Revert to stock rom and try the manual rooting using SuperSU. You'll need a compatible custom recovery to install supersu.
Click to expand...
Click to collapse
terminal or supersu me will work?
http://www.ccnworldtech.com/2017/03/how-to-replace-kinguserkingo-superuser.html?m=1
will it work???
yashasvi.malik said:
can u suggest me something easy???... like with terminal....
Click to expand...
Click to collapse
plss help....
yashasvi.malik said:
terminal or supersu me will work?
Click to expand...
Click to collapse
Have you reverted to stock rom? You can just do a factory reset (root access should be removed too). Install the necessary drivers. Download a custom recovery for your device (TWRP maybe, search it here in the forum). Download the supersu flashable zip (this is an older version, just update after install). Also download the latest ADB drivers (awesome app). Then you root:
(1) Copy the supersu zip to your device storage. Copy/move the custom recovery to the root folder of your ADB.
(2) Open ADB:
Code:
adb reboot bootloader
wait for the device to go into fastboot, then:
Code:
fastboot boot "recovery.img"
(3) Navigate the new custom recovery and select "Install" and select the supersu zip file, then reboot.
(4) Check root access.
Goodluck