Need Help with Z3 Compact - Xperia Z3 Compact Q&A, Help & Troubleshooting

***UPDATE***
I removed Kingroot through their app and unrooted my phone. I tried another one click root, Kingoroot (I know, quite similar names.) The SU which this one installs, isn't restricting me and I successfully set read/write to /system.
I still would prefer to be using superSU but I get a binary occupied message, and the kingouser app doesn't have an option to switch SU app.
For anyone else struggling with kingroot not letting apps work properly, try kingo, who knows.
-----------------------------------------------------------------------------
I have the Z3 Compact, and I HAVE NO ACCESS to a PC, and thus have rooted my phone with King root (which was a terrible idea but any root is better than no root)
I have this issue, where King root in some way shape or form is not allowing anything that requires write permission to /storage access to it.
This is not allowing me to install/use things like busybox, lucky patcher, freedom, and is also, stopping me from using terminal emulator to do things such as mount -o rw,remount,/system or anything else. I tried to use a system I found on XDA to replace Kingroots superuser to SuperSU to get around this, however, the replace_kinguser method, fails with no write permission, and also, fails to remove kinguser from /system/apps/kinguser because that doesn't exist as a directory and I think Kingroot may have made changes to their superuser handler.
I really, really need help getting Kingroot out, and superSU in. Without the use of a PC. Considering I do, have root, there must be something I can do.
I also can't set system to write with ES file explorer or pretty much any other method on the first ten pages of Google.
Any time I try to set /system to r/w I get permission denied.
I'm running, android 5.0.2
Also, BOOTLOADER UNLOCK ALLOWED? NO
So I don't think I can flash a custom recovery of any kind.

Related

Chainfire's Superuser app error on rooted phone

this is my problem. i have a rooted phone and i get this error
https://bu.mp/tEb2VB
thats supersu, what method did you used for rooting? don't you have installed and earlier superuser app? have you installed busybox?
jpsb said:
thats supersu, what method did you used for rooting? don't you have installed and earlier superuser app? have you installed busybox?
Click to expand...
Click to collapse
i used cmw method. i think it was a busybox installer for root
Binary updater fails to update binary – This usually happens because for Superuser can’t write to the system partition where the binary is installed. This can happen for a couple reasons. First, and most common, is that your device has S-ON which prevents the system partition from being written to at runtime. Even if a remount succeeds, and the system thinks that the partition is mounted as rw, you can’t write to it. There are different solutions for different devices, but the easiest usually involves simply updating Superuser through ROM Manager.The app consists of two parts, Superuser.apk and the su binary.The su binary is what other apps call when they need superuser rights. The binary checks the database maintained by Superuser.apk to determine if you have already granted rights to the requesting app.Superuser comes pre-installed on any rooted ROM. In fact, without it, you don’t have a rooted device at all. You cannot uninstall it, it lives on the system partition with other apps that came pre-installed on your device!http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Sounds like I have the same issue, here's my post on chainfires kernel thread:
http://forum.xda-developers.com/showthread.php?t=1331784&page=186
I don't like using CWM out of fear of the brick bug which probably only happens when wipe is used but have stayed away from the first few warnings we had.

Issues installing BusyBox

Hey guys, so I'm trying to install BusyBox on my new Nexus 6 running stock 6.0, rooted. When I try to install via Stericson's installer I got from the Play store, I get:
"We could not verify the integrity of the binary selected..." flashes for a moment, then:
"BusyBox installer was not allowed root access. This may be an issue with Superuser, open Superuser and make sure that you are allowing root access. This application will not work without root access."
I've made sure that the app is allowed root access, and have also tried deleting it from SuperSu so it would prompt me and I could grant it access again, but still the same issue. I'm not sure what the deal is, it seems like I could be having root issues? I appear to have root since I am able to use TiBu, but something seems funky. For example usually when I open FKUpdater it says "FKUpdater has been granted super user access..." and then "Unable to acquire ROOT access." Other times it only says "Unable to acquire ROOT access." I haven't tried flashing a kernel with it because I don't want to at the moment while I figure this other issue out, so I'm not sure if it's falsely reporting the root error.
So, I looked into things further and it seems like I may have some sort of permissions issue. I tried using JRummy's BusyBox installer, but that fails also and just tells me to try installing a different version of BusyBox. It also includes a script for fixing permissions, and when I run it I get "error: only position independent executables (PIE) are supported" and "/data/user/0/com.crummy.busybox.installer/files/temp.sh[118]: sync: can't be executed: permission denied."
Permissions for /data/user/0/com.crummy.busybox.installer are set to drwxr-x--x, as is /system. Also /system is only showing 58 MB free but I don't think that's a problem...
Any ideas? I'm totally stumped...
set your SElinux to be permissive(via app or terminal command)

Uninstall system app

Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Click to expand...
Click to collapse
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
optimumpro said:
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
Click to expand...
Click to collapse
I am using Kingo SuperUser to grant the apps root permission. Had some trouble replacing Kingo SuperUser with Chainfire SuperUser but I figured Kingo should've done the trick as well. When I mount Kingo did prompt me for permission and I allowed it, somehow I think the root is incomplete ?
Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc.
...
...
somehow I think the root is incomplete ?
Click to expand...
Click to collapse
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
kentexcitebot said:
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
Click to expand...
Click to collapse
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Steven90 said:
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Click to expand...
Click to collapse
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
optimumpro said:
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
Click to expand...
Click to collapse
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Steven90 said:
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
Click to expand...
Click to collapse
Ulvgrim said:
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Click to expand...
Click to collapse
Try this, it's almost a one-click tool
http://forum.xda-developers.com/showthread.php?t=2784900
Exploit maybe works with 5.1.1, but if not, downgrade your firmware to 5.0.2, use Easyroot to exploit, then upgrade back.
The "classic" root I was referring to requires downgrading from Sony's Lollipop/Kitkat FW to Jellybean due to Sony patching the exploits in the newer FW used for rooting. The steps are outdated now and is replaced by Easyroot. http://forum.xda-developers.com/showthread.php?t=2688933

kingroot to supersu switching problem

So recently i rooted my Xperia z1 using kingroot and it went smoothly i got root access,then i tried to switch it to supersu and it didnt work,i have used terminal emulator to run the shell file,the method in which you place mrw folder in phone memory,but it just uninstalls the kingroot and installs the supersu,it didnt upate the root app,so supersu doesn't update its binary,i have tried multiple times and i cant do it manually because i camt mount /system to r/w what can i do? Any help please i am so frustrated with this kingroot app.
Hamzashujah said:
So recently i rooted my Xperia z1 using kingroot and it went smoothly i got root access,then i tried to switch it to supersu and it didnt work,i have used terminal emulator to run the shell file,the method in which you place mrw folder in phone memory,but it just uninstalls the kingroot and installs the supersu,it didnt upate the root app,so supersu doesn't update its binary,i have tried multiple times and i cant do it manually because i camt mount /system to r/w what can i do? Any help please i am so frustrated with this kingroot app.
Click to expand...
Click to collapse
First and foremost: Do NOT use Kingroot. There are many threads that explain why Kingroot is shady:
http://androidforums.com/threads/kingroot-safe-to-use.923983/
https://www.reddit.com/r/Android/comments/3vmspw/thoughts_regarding_kingroot/
http://forum.xda-developers.com/showthread.php?t=2604749
Yes, I know there's guides that recommends users to use KingRoot. But unless you want to send private IMEI to China or leak information to the world, just don't use it.
Second, use THIS guide to obtain root.
Alternatively, you can go to the custom ROM route: this will save you a lot of time and headache. Jaguar ROM if you want some AOSP flavor, or DStrikerz if you like Sony's UI. Both includes root, but DStrikerz will allow flashing with locked bootloader. Read THIS for custom recovery.

The second Wind (Parallel SU)

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.

Categories

Resources