Preface: I am trying to attain root, on a un-rooted device, Samsung xCover3, (Note: Root is able to be achieved on kit-kat, and marshmallow, not on Lollipop, which is the current device I'm working on. My][url]http://forum.xda-developers.com/android/development/4-4-4-5-1-1-6-0-1-samsung-xcover3-t3465132 XDA thread[/URL] incease someone say's "follow this", Becuse I created that thread) implementing chainfires systemless root by hand (No working TWRP for lollipop, plus we have an uncommon boot.img which chainfires SuperSu.zip probably couldn't handle).
Prep-work:
- Created a su.img with relevant files inside (Needed for Systemless root to work). Note: This is the file that needs to be pushed to /data.
- Modified the Ramdisk to launch daemonsu (needed to mount su.img for systemless root) as well as changed the defult.prop to
Code:
ro.secure=0
ro.debuggable=1
ro.adb.secure=0
to allow for ADB to be able to be run as root.
- I then also patched the sepolicy file with the default patches as done by chainfires SuperSu.zip
- I then recompiled the kernel so Samsung's Anti-root features and TIMA aren't enabled.
Problem: When typing `adb root` my id does not change to root (0) instead it stays the same, as before hand.
Note: In the below image, daemonsu service should also be running, but I believe what ever is stopping ADB root, working is also probably what stops that service.
{
"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"
}
Reason/Questions, why??
- Maybe the sepolicy doesn't allow it? If so how would I patch to allow adb root to work
- Am I missing something Obvious?
So what is needed to be done to allow for "ADB root" to work?
My question is also on Android Stackexchange
Related
ZERG INITZERG INIT - Universal init.d Patcher.
{
"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"
}
Basically init.d is folder contains some scripts those can automatically executed at boot time.
This system is a Linux Kernel’s feature.
But there are many stock ROMs are comes without init.d feature. These ROM's kernel hasn't init.d support. I also face this problem.
We could found many tweaks, Mods in XDA or outside that requires init.d.
So I was decided to write a program that could patch init.d. with some alternative methods.
Features due to version 0.1:
1. You can execute scripts with any name.
2. You do not need to keep “00” like numbers before scripts name.
3. You can keep extension like “.sh” after scripts name.
4. Faster execution.
5. More powerful patch.
6. init.d related scripts file/folders auto permission fixing.
7. Full compatible with SuperSU flashable zip update (after or before).
How to:
1. Download all the files in attachments
2. Install Terminal Emulator
3. Install BusyBox
4. Unpack "zerginit_v0.1_ansaryx.zip"
5. Keep the binary file to your sdcard
6. Open Terminal Emulator
7. Type
8. See the on screen statuses
9. Now Reboot your device
10. Check log file in "/data/AlienoidMod/logs/init.d_status.log" if init.d working or not.
Comment and let me know how you feel about this... Please give me a thanks
Hi. I have Xouch A2 LTE . I just rooted this device somedays ago with kingroot. But some apps don't work with it. Like Titanium Backup says, "your su version is valid but this might not work reliably." And some apps like LiveBoot. don't work at all.
It's maybe because the su version is too low. The apps recommends to use SuperSu.
So, I googled and found a way to remove KingUser and install SuperSu. From this page http://techstarnayem.blogspot.com/2015/07/how-to-replace-kinguser-kingroot-with.html?m=1 and saw their video tutorial. I did exactly what they did and Terminal Emulator did the same.
When I run the command below.
Code:
su
sh /sdcard/mrw/root.sh
And the KingUser was removed I could realize by a message from Es File Explorer and at the end of it SuperSu was installed and it launched. It told to update su binary and I hit continue and then chose normal way. In the tutorial the guy chose normal way too and it was installed successfully but it didn't work for me. Supersu told to reboot and try again. When I reboot Supersu was installed into the system and when I run SuperSu it says, "There's no su binary installed and SuperSu can't install it. This is a problem. If you just updgaded to Android 4.3, you need to re-root manually-consult the relevant forums for your device!
{
"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"
}
What should I do to gain the root back (Withou flashing the firmware)?
Hello,
There is no forum for your device. Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help. Good luck.
Preface: I am trying to attain root, on a un-rooted device, Samsung xCover3, (Note: Root is able to be achieved on kit-kat, and marshmallow, not on Lollipop, which is the current device I'm working on. My XDA thread incease someone say's "follow this", Becuse I created that thread) implementing chainfires systemless root by hand (No working TWRP for lollipop, plus we have an uncommon boot.img which chainfires SuperSu.zip probably couldn't handle).
Prep-work:
- Created a su.img with relevant files inside (Needed for Systemless root to work). Note: This is the file that needs to be pushed to /data.
- Modified the Ramdisk to launch daemonsu (needed to mount su.img for systemless root) as well as changed the defult.prop to
Code:
ro.secure=0
ro.debuggable=1
ro.adb.secure=0
to allow for ADB to be able to be run as root.
- I then also patched the sepolicy file with the default patches as done by chainfires SuperSu.zip
- I then recompiled the kernel so Samsung's Anti-root features and TIMA aren't enabled.
Problem: When typing `adb root` my id does not change to root (0) instead it stays the same, as before hand.
Note: In the below image, daemonsu service should also be running, but I believe what ever is stopping ADB root, working is also probably what stops that service.
{
"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"
}
Reason/Questions, why??
- Maybe the sepolicy doesn't allow it? If so how would I patch to allow adb root to work
- Am I missing something Obvious?
So what is needed to be done to allow for "ADB root" to work?
My question is also on Android Stackexchange
I've been having some increasingly problematic issues with my S7 (which was rooted and had Xposed working for a long time) so I decided to do a factory reset/wipe and essentially start from scratch.
I got the device rooted okay, but any attempts to install/flash the Xposed framework results in a failure to boot.
Here are the steps I'm taking to root setup/root the device (I have had to do this several times now):
1. Used "Odin PrinceComsy.exe" to flash the following stock firmware to the device (contents of VZW-G930VVRU4API3-20161121101036.zip):
• AP_G930VVRU4API3_CL8875708_QB11198919_REV02_user_low_ship_MULTI_CERT.tar.md5
• BL_G930VVRU4API3_CL8875708_QB11198919_REV02_user_low_ship_MULTI_CERT.tar.md5
• CP_G930VVRU4API3_CL8875708_QB11198919_REV02_user_low_ship_MULTI_CERT.tar.md5
• CSC_VZW_G930VVZW4API3_CL8875708_QB11198919_REV02_user_low_ship_MULTI_CERT.tar.md5
2. Used Odin again to flash this "pre-rooted" file:
• Samsung_G930x_QC_Rooted_BOOT.TAR
3. Used this version of SuperSU and pushed it to the device with adb:
• http://downloadmirror.co/1JU9/SuperSU-v2.74-2-S7QC.zip
At this point, successful root is achieved. Unfortunately I still can't get Xposed to install successfully.
I've tried flashing each the following with Flashfire (each one failed, requiring a repeat of the steps above):
• xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211.zip
• xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530.zip
• a few of the ones here https://dl-xda.xposed.info/framework/sdk23/arm64/
I think I've tried some others too but I didn't keep track, sadly.
So basically, if I provide as much information as needed, I'm hoping someone can help me find the right Xposed version/files and maybe provide a few step by step instructions for installing Xposed on my device successfully. I really wish I had all the files I used when I originally did all this but I can't find them.
Here are some more specific details about my device:
{
"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"
}
I really hope someone is able to help. Thanks a ton!
{
"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"
}
I tried to flash update su v2.4.v2.51.v2.7.....view. 2.82 help
What Android version are you running?
@Yabu2020
SuperSU you installed is a superuser access management tool, what requires that SU binary is already present in Android OS. Hence you have to install the Android OS version matching SU binary, too.
dedq said:
What Android version are you running?
Click to expand...
Click to collapse
dedq said:
What Android version are you running?
Click to expand...
Click to collapse
5.0.2 lollipop
jwoegerbauer said:
@Yabu2020
SuperSU you installed is a superuser access management tool, what requires that SU binary is already present in Android OS. Hence you have to install the Android OS version matching SU binary, too.
Click to expand...
Click to collapse
How can I do that?
IMO easiest method is to replace the restricted version of Toybox multicommand applet that comes with Lollipop ( means what hasn't SU embedded ) by an unrestrichted one like Toybox version 0.8.5 ( means what has SU incorporated ).
Toybox 0.8.5 is downloadable from here:
Index of /toybox/bin
landley.net
What should i do with the file i download(toybox)should i flash it by twrp or what please be more specific about it