Hi mates, I've a Samsung Neo device (or something similar), I want to use it as a security cam but I need to change file playlpm into /sytem/bin to reboot phone when power plug is connected.
I've rooted the phone with a package, but it contains the SuperSU free, which doesn't let me write into /system/bin, how can I overcome this? I've found SuperSU pro 2.82 but after installing it I can't open the new app, old still there, I've rebboted but didn't help.
Please I need *any* advice which make me able to overwrite playlpm file! Thank you a lot!
It's getting me mad, I've installed and rebooted
I've forced disabled SuperSU and installed the pro after it, nothing. I an only install but no open, no icon.
I've uninstalled SuperSU, nothing too.
I've intslla Kingroot and it gives an error when I run it.
I solved myself, I don't know if SuperSU tricked me only showing on logs "you need the PRO version to do this" when I tried do write somethin on /system, but after some experiments, like installing KingRoot I've figured out I need to mount on write the /system. I used this:
https://forum.xda-developers.com/showpost.php?p=10691125&postcount=7
Related
I f'ed up guys, it seems that after rooting I dont have access to edit data on my phone, it can boot and all, but I cant for example take pictures(says it doesn have space wich is not true), intall apps, etc. I dont know in what extents it affected because I can uninstall apps for example.
When I try to delete a file with a file explorer it says the access was denied. Nor I can copy files from my pc to the phone.
I have a XT1063 with lollipop 5.0.2 that I installed manually before and worked great.
I installed Super SU through TWRP 2.8.5.0 (maybe wasnt compatible with lollipop?) that have Super SU 2.4 built in (according to what i’ve read, maybe this version of Super SU isnt compatible?).
Anyway, after that I proceeded to install busybox with default configuration and later smscript, dont know if all this is relevant. I only was aware of the problem when I tried to download a script for smcript but couldnt save it to my phone.
So next I tried to unroot from super su configuration with no luck, only got to unroot after uninstalling busybox. (also uninstalled smscript if that matters).
I hope I gave enough data if you need more just ask, thanks!
fede011 said:
I f'ed up guys, it seems that after rooting I dont have access to edit data on my phone, it can boot and all, but I cant for example take pictures(says it doesn have space wich is not true), intall apps, etc. I dont know in what extents it affected because I can uninstall apps for example.
When I try to delete a file with a file explorer it says the access was denied. Nor I can copy files from my pc to the phone.
I have a XT1063 with lollipop 5.0.2 that I installed manually before and worked great.
I installed Super SU through TWRP 2.8.5.0 (maybe wasnt compatible with lollipop?) that have Super SU 2.4 built in (according to what i’ve read, maybe this version of Super SU isnt compatible?).
Anyway, after that I proceeded to install busybox with default configuration and later smscript, dont know if all this is relevant. I only was aware of the problem when I tried to download a script for smcript but couldnt save it to my phone.
So next I tried to unroot from super su configuration with no luck, only got to unroot after uninstalling busybox. (also uninstalled smscript if that matters).
I hope I gave enough data if you need more just ask, thanks!
Click to expand...
Click to collapse
I got the same problem here! pls HELP!
I also had the same problem on my XT1068
Just reboot the device and format the internal storage using TWRP 2.8.6.0 (Latest). Problem will be solved
sharkymyn said:
I also had the same problem on my XT1068
Just reboot the device and format the internal storage using TWRP 2.8.6.0 (Latest). Problem will be solved
Click to expand...
Click to collapse
It means that I have to clean install everything again? I dindt want to go to this point, but thanks!
Hello, new user here.
Since I stuggled with root on my Phone and somehow managed to maintain it, I thought, I 'd share you the stuff I did with you.
I put the TL;DR between hide, if you want to read the story behind my struggle anyway, you are welcome.
I am better with explaining stories then explaining things.
Spoiler
I am using a Samsung S4 mini, Stock ROM and just don't want to flash a cROM.
But I wanted more functions to do - a swiss knife like my old GT-S3650, which was able to boot a PC from.
Most of the things I want to use need root, so why not rooting this sleep S4 mini baby?
And I managed to root it using Kingroot. And all of the things I want to use worked.
After a few days, I noticed network traffic, even with the most network apps and Sync disabled.
Weird? Yes. So I installed "Shark" on my Phone and "Wireshark" on my PC, and started logging.
I noticed an increase of Jabber (the protocol) and a lot of request on domains from China.
Some requests even included my IMEI, how I am connected to the Internet, etc... pretty private Stuff.
I found most of the sources, the IMEI sending App was Shark itself.
Used Lucky Patcher to get rid of it and /etc/hosts blocked the DNS with Hosts Editor.
Did the same with some Kingroot DNS.
But then I asked myself: "Can Kingroot still root my phone, even when cut of the web?".
So I UNROOTED my Phone from Kingroot. Bad idea. Really bad one.
After I ran Kingroot again, it told me, it didn't have a network connection.
I have no idea how I was able to edit the hosts file without SU.
Rerooted the Phone, even if it left a bitter taste of having unwanted network traffic.
This is which made me want to switch to SuperSU.
I tried to mount system as RW prior and installing SuperSU over Kingroot SU. And it failed.
I even tried to make my own uninstall script to uninstall KR by unpacking the Kingroot APK and look what it does.
Not working, the script failed (I am not used to Linux), so I stayed at Kingroot.
While I was working on Kingroot, I was thinking about the idea of having 2 SU Apps, which everyone said it won't work.
But I wanted it to make work - and this is actually the focus on this topic.
During tests, it didn't work as intended, so I stopped working on it and forgot it overtime, resting within my /system.
Days passed, Weeks and Months and I lived with Kingroot, forgot all the trouble and access to/from China.
Recently, I started SuperSU - it was still on my phone. This "cannot install su binary" nagged me and thought:
Oh, why not use this instead.
And then there was SuperSuME... which I didn't want to use, since I was able to brick BlueStacks with it.
But I really wanted to get rid of Kingroot and use SuperSU. This was yesterday.
My phone still has warranty and I think I have Odin here (just in case), but not the 100% exact ROM file.
So I did SuperSuME anyway -I always could return the phone and claim it "broken after OTA update", lol.
Well, SuperSuME did it's Job better then expected and no bricks. Nice Job.
While playing around with SuperSU, I did another mistake.
And here we are... at the main topic.
TD;TR for those who didn't want to read the story:
I rooted my phone 2 times with Kingroot and finally wanted to switch to SuperSU.
After I accidentally broke Kingroot the first time, blocked it's Internet access and unrooted afterwards, I got stuck with a unrooted phone and Kingroot failed to root it.
I was lucky to fix that problem and rooted again with Kingroot.
After months, I used SuperSUME to change that. After SuperSU was installed, i made the mistake of unticking "Enable Superuser". Bad idea.
Tapping "Enable" again, it failed to update the su-binary. oh god. I unrooted again.
While traversing through my directories to start Kingroot again to root, I found my "shadow copy" of SU.
Wut? Shadow copy? Let me explain:
After my first unroot, I wanted to have a SU backup anyway at all costs, just in case I accidentally messup root again.
Now after hours I think I know why it doesn't work.. the normal way, of course.
I installed SuperSU, went into /data/data (or where ever SuperSU has its files) and took a look at them.
Unpacked the SuperSU APK on the PC and gathered all "needed" (I think were needed) files.
I hexedited the most SU binaries from SU to ZU and changed all other referenced binaries as well.
I am sorry about that, Chainfire. I was just testing things.
SU => ZU
SUpolicy => ZUpolicy
setup_su => setup_zu
99SuperSUDaemon => 99SuperZUDaemon
daemonsu => daemonzu
zygote => zugote
I had no idea what sukernel was for, so I left that out.
Why call it ZU? "Sun Tzu" thats why. Known as "Sunzi", he wrote Book about "the Art of War".
After I made sure everything is properly renamed and edited, I moved them onto my phone in the right directories required and chmod them.
I don't know much about that, I just copied the chmod numbers from Kingroot SU and some weird script I found on the web.
Tried to run it using JuiceSSH local terminal, and BAM!! the SuperSU box popped up.
But pressing "Allow" accepted it and nothing else happened.
It became stuck after ZU... it did nothing, but the daemon was running as daemonzu and daemonsu at the same time..
JuiceSSH popped up in SuperSU (while it told me the SU bin was outdated), though.
So I was on the right track, but a piece of the puzzle was missing, so I stopped delving deeper into it.
And forgot about it until about yesterday - where I disabled "Superuser" in SuperSU.
Midwhile the su binary changed from Kingroot SU to SuperSU SU.
Note: It should really ask "Do you want to disable Superuser? SuperSU will delete su binary" Yes/NO.
As I found those files, I started JuiceSSH and typed "zu".
This time, ZU somehow worked like it should.
It spawned a root shell. OMG...
I guess it somehow requires something else needed, which wasn't working while Kingroot was active.
I tried "Root Checker" and it failed. I had no "official" root. But still root available in JuiceSSH.
Somehow I managed to restore SuperSU to normal status. Guess this thing can latch onto an active root user or so.. no idea.
I even screenshotted this, cause I couldn't believe it. If you want, I can post those.
I have now a working second su on my phone, which is hidden from most apps.
But I think it is not perfect, it relies on something SuperSU does or installs during installation.
I apologize again to Chainfire for editing his stuff.
So, now my questions:
1. How can I make it perfect to run standalone, only using SuperSU as a GUI for (Allow/Deny)?
1b. Can we make it part of SuperSU? As a special function: "Install Stealth SU"?
2. Can we use that for something else? -> Probably for this? http://forum.xda-developers.com/apps/supersu/suhide-t3450396
3. Why must the binary be called SU? I know it's for the most apps to do their job and somehow Linux standard.
So I just recently came across this watch and have been fiddling with it. I managed to twrp it, unpack the 5.1.1 boot img other day and patch it with magisk and flashed it successfully. There was a little error in magisk manager you could slide by when you first opened it but it showed installed could grant superuser permissions.
The newest updates (6.0.1) and above I guess are using this squashfs scheme for system so it's not mountable. I noticed on the lg watch there was a squashfs doryimg, does anyone have squashfs sprat compatible twrp already anywhere, or can create one quicker than me? Or lead me in the right direction to compile it myself? An update installed on me unrooted me and failed to install, ideas on easiest way to freeze them prefferably adb shell pm uninstall -0 type command? Managed to also magisk patch 6.0.1boot img and flash it successfully get superuser permissions but its not proper doesnt have system permission to change anything much because of squashfs.
Tried DPI Changer is nice. Google Keyboard is good but wish it had an enter button so I can fiully type in jackpal terminal spaces that require an enter key. Will maybe try hackers keyboard(tried swype, gboard, minuum on 5.1.1 no dice). Google Analog draw keyboard zip kind of nice but annoying to type with. Es File Explorer pro size render disallowed looking at others app menu beside users. Es File Explorer worked to uninstall on 6.0.1 but not 5.1.1 had to go to go to data/ app to uninstall on 5.1.1. Could not install apk from device. Have been having to use adb install and push commands to get most files on the watch. Chrome apk latest works. I'd like to stay at 5.1.1 to maintain proper magisk/ twrp solely because of lack of squashfs support. Anyway to update google play service (1.1 to android 1.3 or 1.5) without updating version or install real playstore? Tried remote desktop/ gmail but only thing stopping me was I am unable to login to a google account on device because there is no account section in settings. Tried several app versions, shortcuts, workarounds no luck but lmk if you were able to.
Used rootjunky restore tool v2 to restore stock 4.4 it works well. V3 wouldn't recognize my almost bricked device but V2 would. OTA back from 4.4 is super annoying tho adb doesnt work says unauthorized until 5.1.1 doesnt give key doesnt pop up. Adb sideload is friend. There is not another boot img until 6.0.1 so had to apply patch updates then unpack/ repack. Had issues with backups not restoring root somehow. https://forum.xda-developers.com/wiki/Samsung_Gear_Live couldnt find anything newer besides one reddit post. first 6.0.1 update is twrp flashable.
well thats about all for now when I reupgrade I'll try and upload 5.1.1 magisk root if nothing changes. Thank you kindly Feel free to chime in if you still have this device, what worked for you., any tips, :good:
Still looking??
Sorry, I can't help you....... The gear live support just keeps getting less..... Well, it IS five years old after all...
Anyhow, I still have mine an love it. I read you were able to get TWRP on it successfully.
I can flash TWRP to the Gear Live just fine, but as soon as I reboot normally, the stock software replaces TWRP with the original recovery.
Supposedly, TWRP has a patching feature built in, but I've not been able to make it work.
SO....... Do you have any ideas why mine would not be working??
Thanks
Boowho??
I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.
Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.
UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel:
Hi all!
I might be asking a stupid question, so forgive me if I do.
The situation is the following... I have a TVBOX Q96 HOME 4K (cheap Chinese one based on RK3229) that is pre-rooted. All applications using root work fine. However, there is no "superuser" manager installed on it in order to disallow certain apps to gain root access. In the past I already had a similar situation with some other box and when I installed SuperSU apk the device hasn't boot anymore. I that case I got a stock firmware and could unbrick it, but now I can't find any ROM for this device in order to play with it.
So, the question is... is it possible to install Magisk Manager in order to manage access to the built-in su? Older version I tried correctly identify the device as rooted (with SuperSU 2.76), but do not offer me a Superuser menu where I could manage access to the su of the apps. Neither I get a prompt when an app is requesting access to su.
Any solution to my problem?
No, you will not be able to use the Magisk Manager to manage superuser access for SuperSU.
Any idea what might cause the device to not boot anymore after installing SuperSU.apk?
I compared the installed su binary with the one from chainfire's UPDATE-SuperSU-v2.76-20160630161323.zip (arm7), and they are identical. What does installing an apk alone to the system beside managing the access for the apps?
I have to admit I don't know exactly what happens "behind the scene".
I have absolutely no idea why installing the SuperSU apk would cause your device not to boot... Sorry.
Edit: Wait... You write "installing an apk alone to the system". You're not installing it as a regular app, but to the /system partition? If so, that's what might be causing issues.
Sorry to mislead you... I wrongly expressed myself.
I'm not installing it as a system app - I have installed it (on previous box) as an ordinary user app and as I said the system couldn't boot anymore afterwards (I had to reflash the ROM to unbrick it).
BTW... this is a known issue with these Chinese TVBOXes. There are couple of posts also here in XDA about it and nobody knows AFAIK what is the root cause.