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.
Related
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.
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.
In my 5th gen fire hd7 I tried to root using rootjunky supertool.
I don't know what went wrong during the process but the SuperSU app always says su binary needs to be updated and when I select normal it fails. I'm very much disappointed and annoyed and decided to unroot.I tried the universal unroot app but it fails .nRoot checker says root access is not proper and root explorer can't edit root files.
Is there any way to unroot without updating su binary?
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.
Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).
have you enabled Developer Options?
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".
Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse