Got a third Kindle from Amazon (warranty replacement), and, surprise, it's running 11.3.0. Have tried using Bin4ry's tool (v17 and the latest, I believe it's v33), along with various Qemu versions, cannot get root. Keeping getting errors on local.prop (in Qemu) and 'permission denied' errors with Bin4ry. Any suggestions? I've got wifi off so it doesn't auto update, but I have ES file explorer and I manually install Root check and superuser, none of these apps will allow me root access, so despite many people saying 'ignore the errors', I'm still stuck.
Tried on a Windows 7 and a Windows 8 system, same results on both.
Related
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)
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.
I would appreciate if anyone could provide me a way to install CyangenMod on my Amazon Fire 5th generation 7†tablet running the Fire OS 5.3.1.0. I have attempted to do so using SuperTool but have been unsuccessful. Currently, my tablet still works using Fire 5.3.1.0, and has not updated to 5.3.2. I have examined the various posts to the forum but have not seen anything that addresses my situation.
Here is what I have done so far. First, I was able to gain access to the tablet using the SuperTool and installed SuperTool’s Kingroot. After repeated attempts at rooting and rebooting, my tablet quit booting. Though the tablet would not boot, the tablet would enter into Fastboot mode and recovery mode. In recovery mode I was able to reinstall Fire OS 5.3.1.0. After recovery Kingroot was still installed but would not work to root the tablet. I installed a newer version of Kingroot, but now Kingroot does not even start. Tapping on the Kingroot icon initially appears to do something, but the screen then returns and Kingroot is not running. Kingroot cannot be uninstalled through application manager as all the buttons are greyed out.
If a similar post exists, I am sorry the duplication. Any assistance would be appreciated.
I also have an Amazon Fire phone and successfully changed the phone to the CyangenMod OS. I find the phone much more usable than with the Fire OS. Now, I want to change my tablet to the CyangenMod OS.
Daddio1949 said:
I would appreciate if anyone could provide me a way to install CyangenMod on my Amazon Fire 5th generation 7” tablet running the Fire OS 5.3.1.0. I have attempted to do so using SuperTool but have been unsuccessful. Currently, my tablet still works using Fire 5.3.1.0, and has not updated to 5.3.2. I have examined the various posts to the forum but have not seen anything that addresses my situation.
Here is what I have done so far. First, I was able to gain access to the tablet using the SuperTool and installed SuperTool’s Kingroot. After repeated attempts at rooting and rebooting, my tablet quit booting. Though the tablet would not boot, the tablet would enter into Fastboot mode and recovery mode. In recovery mode I was able to reinstall Fire OS 5.3.1.0. After recovery Kingroot was still installed but would not work to root the tablet. I installed a newer version of Kingroot, but now Kingroot does not even start. Tapping on the Kingroot icon initially appears to do something, but the screen then returns and Kingroot is not running. Kingroot cannot be uninstalled through application manager as all the buttons are greyed out.
If a similar post exists, I am sorry the duplication. Any assistance would be appreciated.
I also have an Amazon Fire phone and successfully changed the phone to the CyangenMod OS. I find the phone much more usable than with the Fire OS. Now, I want to change my tablet to the CyangenMod OS.
Click to expand...
Click to collapse
- reload/sideload FireOS 5.3.1 as you did previously (details)
- during initialization do not register device with Amazon when prompted
- snag KingRoot v4.8.5 from here (older version) and attempt to root
- if successful use the 'root' option SuperTool to replace KingUser with SuperSU (simply skip root step)
Davey126 said:
- reload/sideload FireOS 5.3.1 as you did previously (details)
- during initialization do not register device with Amazon when prompted
- snag KingRoot v4.8.5 from here (older version) and attempt to root
- if successful use the 'root' option SuperTool to replace KingUser with SuperSU (simply skip root step)
Click to expand...
Click to collapse
- I re-sideload FireOS 5.3.1, but when I rebooted, it did not request that my device be registered.
- Next, KingRoot v4.8.5 failed to install with this result:
adb.exe install - com.kingroot.kinguser_4.8.5-139_minAPI9(nodpi).apk
4171 KB/s (5885104 bytes in 1.377s)
pkg: /data/local/tmp/com.kingroot.kinguser_4.8.5-139_minAPI9(nodpi).apk
Failure [INSTALL_FAILED_VERSION_DOWNGRADE]
It appears that Kingroot does not allow installing an earlier version.
Daddio1949 said:
- I re-sideload FireOS 5.3.1, but when I rebooted, it did not request that my device be registered.
- Next, KingRoot v4.8.5 failed to install with this result:
adb.exe install - com.kingroot.kinguser_4.8.5-139_minAPI9(nodpi).apk
4171 KB/s (5885104 bytes in 1.377s)
pkg: /data/local/tmp/com.kingroot.kinguser_4.8.5-139_minAPI9(nodpi).apk
Failure [INSTALL_FAILED_VERSION_DOWNGRADE]
It appears that Kingroot does not allow installing an earlier version.
Click to expand...
Click to collapse
Yep - that's a problem with Amazon's sideload. It does not wipe the system partition prior to rewriting FireOS. Kingroot leaves crap everywhere; apparently a remnant is getting in the way. May be in the system partition or in user/data storage.
At present there is no mechanism for wiping system unless the device is rooted and using a tool like FlashFire (or bootable TWRP for early production devices).
Return to the stock recovery menu and try the following:
- wipe data/factory reset
- wipe cache partition
- reload FireOS
Then reboot and attempt to download/install KingRoot 4.8.5 again. If still no joy you may need to way a few days while the SuperTool is updated to accommodate KingRoot 5.x (specifically the ability to remove it which should apply to all prior versions).
Davey126 said:
Yep - that's a problem with Amazon's sideload. It does not wipe the system partition prior to rewriting FireOS. Kingroot leaves crap everywhere; apparently a remnant is getting in the way. May be in the system partition or in user/data storage.
At present there is no mechanism for wiping system unless the device is rooted and using a tool like FlashFire (or bootable TWRP for early production devices).
Return to the stock recovery menu and try the following:
- wipe data/factory reset
- wipe cache partition
- reload FireOS
Then reboot and attempt to download/install KingRoot 4.8.5 again. If still no joy you may need to way a few days while the SuperTool is updated to accommodate KingRoot 5.x (specifically the ability to remove it which should apply to all prior versions).
Click to expand...
Click to collapse
Thank you for your assistance. Unfortunately, I have not progressed to the installation of cyanmodgen.
Here is my status. I have completed steps 1, 2, and 3 successfully and installed kingroot 4,8.5 and supersu using the SuperTool. To install kingroot, I renamed ver 4.8.5 to Kingroot.apk for SuperTool to use. Supersu is installed and Kingroot was removed. The tablet is now rooted.
However, when I attempted to install FlashFire-v0.53 by SuperTool, I received this message ‘Invalid APK file: apps\FlashFire-v0.53.apk’ from SuperTool, but a second message from SuperTool claims that Flashfire is installed from a DOS echo statement. Flashfire does not show on the tablet. I have not changed the flashfire program and am confused by the message.
Is there a better version of Flashfire to use?
Thank you for your assistance. Unfortunately, I have not progressed to the installation of cyanmodgen. I'm sorry for the double posting.
Here is my status. I have completed steps 1, 2, and 3 successfully and installed kingroot 4,8.5 and supersu using the SuperTool. To install kingroot, I renamed ver 4.8.5 to Kingroot.apk for SuperTool to use. Supersu is installed and Kingroot was removed. The tablet is now rooted.
However, when I attempted to install FlashFire-v0.53 by SuperTool, I received this message ‘Invalid APK file: apps\FlashFire-v0.53.apk’ from SuperTool, but a second message from SuperTool claims that Flashfire is installed from a DOS echo statement. Flashfire does not show on the tablet. I have not changed the flashfire program and am confused by the message.
Is there a better version of Flashfire to use?
Daddio1949 said:
Thank you for your assistance. Unfortunately, I have not progressed to the installation of cyanmodgen. I'm sorry for the double posting.
Here is my status. I have completed steps 1, 2, and 3 successfully and installed kingroot 4,8.5 and supersu using the SuperTool. To install kingroot, I renamed ver 4.8.5 to Kingroot.apk for SuperTool to use. Supersu is installed and Kingroot was removed. The tablet is now rooted.
However, when I attempted to install FlashFire-v0.53 by SuperTool, I received this message �Invalid APK file: apps\FlashFire-v0.53.apk� from SuperTool, but a second message from SuperTool claims that Flashfire is installed from a DOS echo statement. Flashfire does not show on the tablet. I have not changed the flashfire program and am confused by the message.
Is there a better version of Flashfire to use?
Click to expand...
Click to collapse
There is an coding error in the SuperTool that erroneously looks for FlashFire-v0.53.apk (note the extraneous 'v') instead of FlashFire-0.53.apk which is now the file is actually named. You can either: 1) rename the file on the host machine (PC); 2) manually copy it to your tablet and execute as-is; or 3) download a fresh copy from here.
Davey126,
Many thanks for your assistance. My Amazon Fire appears to be a working Cyanogenmod 12.1; Cyanogenmod is completing setup.
To convert my Amazon Fire 5th gen tablet to Cyanogenmod, I basically followed Rootjunky instructions in his SuperTool with a few exceptions pointed out by Davey126.
- Using the tablet's recovery mode, it was wiped ( data/factory reset and cache partition) and Fire 5.3.1 was re-installed
- To root the tablet I used Kingroot, but I used com.kingroot.kinguser_4.8.5-139_minAPI9(nodpi).apk instead of the kingroot.apk provided in SuperTool. To do that I renamed the Kingroot file. Rooting occurred very quickly using this version.
- To install FlashFire, I renamed FlashFire from flashfire-0.53.apk to flashfire-v0.53.apk, which is referenced in the SuperTool's bat file.
- Used FlashFire to install Cyanogenmod and GAPPS.
Just got a Fire 7" 2015 with 5.1.3 on it. Most of the guides say to downgrade to 5.1.2, but it looks like 5.3.1 is also rootable (it came out after the 5.1.3 guides were written, so I presume that's why they all say 5.1.2). In my non-informed mind, it seems like it would be better to upgrade my tablet to 5.3.1 (sideloading I presume? still getting a grasp on how all this works), and have a later version of firmware with its improvements, rather than using the much older 5.1.2.
Am I correct in this reasoning? Is there any compelling reason to select one firmware over the other? Before installing 5.3.1 I want to make sure I'm not making an irreversible mistake. Thanks!
EDIT TO ADD: Question resolved, I updated to 5.3.1 and successfully rooted. Details of my experience in a below comment.
bump!
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
also got 5.1.3 best way to proceed rom and root please anyone thank you !
Update on successful 5.3.1 upgrade
rob.e.rein said:
also got 5.1.3 best way to proceed rom and root please anyone thank you !
Click to expand...
Click to collapse
Rob, since I never got a response I decided to live dangerously, went ahead and did the upgrade to 5.3.1. It worked great after some fiddling. A summary of my experience in case it helps you or others...apologies that I can't post external links since this is a new account, apparently the forum won't let me do that until I make 10 posts.
First, I installed 5.3.1 using my PC:
* Power on Kindle, do NOT enable wifi or it'll do autoupdate. Exit out of setup.
* Downloaded 5.3.1 update (*.bin filetype) to computer.
* Followed Amazon instructions for manual software updates (google for "Download and Install Fire Tablet Software Updates Manually"). (short summary: Plugged Kindle into PC (Windows 7), which mounted like a flashdrive. Dragged & dropped the update BIN file to Internal Storage folder. Initiated update from Fire -> Settings -> Device -> System Updates.)
After 5.3.1 was installed, I rooted it using the Fire 5th gen RootJunky SuperTool. Had a few quirks with this, don't know if it was because of Fire OS version, my PC OS, or just wonkiness. SuperTool officially supports 5.3.1 but who knows. Notes on my workarounds:
* Installing ADB drivers didn't work through SuperTool, so I downloaded and installed them directly from Amazon (google for "Connecting Your Fire Tablet for Testing". You don't need a special hacked version, ADB just lets your computer communicate with Kindle as if you were a developer.
* You will need to enable wifi for KingRoot to work (it connects to internet to download latest information on how to root). However, the version of KingRoot that SuperTool installed didn't work even after running 6+ times. I used Silk browser to go directly to KingRoot site and downloaded newer version (had to enable Fire allowing 3rd party apps to install). After this I still had to rerun 3-4 times but it eventually worked.
* When SuperTool attempts to replace KingRoot with SuperSU, it had some trouble removing KingRoot. Don't worry about that, SuperSU will prompt to remove remaining pieces of KingRoot when you open it, AND you can also just go to home screen, click & hold on KingRoot, and uninstall it yourself.
Once everything was rooted & Nova Launcher was installed, I had a few issues with Nova Launcher not working 100%, e.g. when I tried to install a widget it would pop open the Fire settings screen & not install. I was able to fix this by moving the launcher APK (the app package) from /data/app to /system/priv-app. DISCLAIMER: DOING THIS OR ANYTHING ELSE WITH ROOT ACCESS CAN BREAK YOUR FIRE! To do this, you'll need to install a file browser, I used FX browser plus the root addon (which you will need to muck with system folder). Using root access, go to /data/app and find the APK with "tesla" in the name, the icon should match the Nova Launcher. Cut & paste it in /system/priv-app. Reboot Fire and you're good to go.
That's all I can think of that I had problems with, many of which I expect weren't related at all to using 5.3.1, but thought I'd share anyways.
I just installed magisk succesfully(?) on my xperia 5 ii following this guide:
https://forum.xda-developers.com/sony-xperia-5-ii/how-to/guide-magisk-twrp-recovery-t4177209/page7
Using the beta channel (stable simply doesn't even boot), magisk manager shows v21 installed. However none of the root apps I tried so far (busybox, adaway, system app remover) works. All of them give some kind of error. The root privileges are being granted (I get the promt to grant/deny and the popup that root was granted). This is very weird and the first time it happens to me on any device. The root browser file managers shows the "root directory" with 0 free space incorrectly (1.6GB used - 1.72 total) I tried copying a file inside the /system directory and it just didn't do anything. I tried reinstalling magisk from the manager, but its still the same. Any help will be appreciated, I really have no idea what to try at this point.
Hard to say... What's "some kind of error"? Maybe the Magisk logs show something (although you'd likely have to switch to the Canary channel to get any useful logs).
I think it's best to wait for a reply to your query in the thread you linked. That's likely to be the best place to get help, since that's where you find other users of the same device...