I downloaded Super-Sume Pro Version 9.6.0 - it recognized my Fire HD 10 OS 5.1.1.
When I went to run it installed a Super-Sume prep to check my license and it passed
I ran the app - I granted it Super user access - It ran and completed Part 1 but for Part 2 it didn't auto start SuperSu for me
I then saw the SuperSU app and ran it and updated it with Normal and it worked.
I attached a few screenshots.
What generation/ year of HD 10 is this?
Spedkiller said:
What generation/ year of HD 10 is this?
Click to expand...
Click to collapse
It is HD 10 Gen 5 OS 3.1.1
Related
hello all
I have the tablet version of the a8-50 wil roms for the phone work on the tab to?
maby this is a stupid question but i was just wondering
passie1981 said:
hello all
I have the tablet version of the a8-50 wil roms for the phone work on the tab to?
maby this is a stupid question but i was just wondering
Click to expand...
Click to collapse
Hello my dear friend.
You may redirect this Q to Lenovo A5500 as THAT thread is regarding YOUR tablet, not HERE. Full model name of your tablet is probably either A5500-F (wifi only ver with MT8121 chipset) , A5500-H ( wifi+3g but no call functionality) or A5500-HV ( tablet that you can make call with it)
Be precise which type you have.
This was sent from my Lenovo A850 via XDA mobile app.
I used KingRoot (ver 4.8.2) to root my Lenovo Tab2 A8-50F Tablet.
I used KingRoot as part of a SuperTool. The SuperTool, using a batchfile script, also removed KingRoot after the tablet was rooted and then installed SuperSU.
The SuperTool (April 6, 2016 version) was created by xda's RootJunky for the Amazon Fire 7 5th gen tablet, using KingRoot and SuperSU, but it rooted my Lenovo Tab2 A8-50F Tablet, uninstalled KingRoot and installed SuperSU, all with only a couple of mouse clicks.
Even if you are already rooted with KingRoot, you can use this tool to uninstall KingRoot and install SuperSU. (Just run the tool, let it re-install KingRoot, don't run KingRoot but hit Enter on the SuperTool to then uninstall KingRoot and install SuperSU).
Lenovo Tab2 A8-50F Tablet info:
Model Number: Lenovo TAB 2 A8-50F
Android version: 5.1
Kernel version: 3.10.65
Build number: A8-50F_S000037_151023_ROW
Software version: A8-50F_151023
Hardware version; LenovoPad A8-50F
The SuperTool batch file script rooted the tablet with KingRoot and then uninstalled KingRoot and installed SuperSu.
I have since installed ES File Manager, Titanium Backup, Link2sd on the tablet. Root is totally working. Rooted with only a couple of clicks!
Just enable Developer options on Lenovo Tab2 A8-50F (by tapping tablet Build Number 7 to 10 times [Settings, About Tablet, Build Number (tap 7 to 10 times)]), enable USB debugging on Tablet in the Developer options settings.
Connect Tablet to Windows 10 with a USB data cable (I used the USB 2.0 port). When screen message on the Tablet mentions connections, make sure it is in the MTP mode.
Extract RootJunky's SuperTool Zip file to the Windows 10 desktop.
Run RootJunky's SuperTool (Amazon-Fire-5th-gen.bat) You may have to read the instructions on the pages below and install adb drivers. Pick option #6 Root. Choose Option #3: version 5.1.2. This will run a script that installs KingRoot, allows you to run it manually, and then removes KingRoot and installs SuperSU.
Press enter and KingRoot will be installed on the Tablet from the SuperTool. (approve any messages that appear on Tablet screen) Now don't touch the PC SuperTool until the Tablet is rooted.
Open KingRoot on the Tablet and run it. You may have to run KingRoot several times and the Tablet may reboot. Just keep running KingRoot until the Tablet is rooted. After KingRoot reaches 100%, then press ENTER on the PC.
The SuperTool will now uninstall KingRoot and install SuperSU on the Tablet.
Choose NORMAL SuperSU install on the Tablet when prompted. When SuperSU is installed, reboot the Tablet. Disconnect data cable.
After reboot the Lenovo Tab2 A8-50F Tablet is rooted. There will be a request by SuperSU to upgrade. Approve it. You can now install Titanium Backup, Link2sd, ES File Manager, etc. Your Tablet is rooted. As easy as that. THANKS ROOTJUNKY!!!
Info and links to Download RootJunky's SuperTool at these pages:
Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
"AmazonFire5thGenSuperTool.zip" 2016-04-06 version
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool
I ran the autoroot script found here to to root my stock device (with TWRP installed).
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
SuperSu is now installed, and when running TitaniumBackup I get a prompt for root however after granting permissions it complains that it could not acquire root privileges. Did I do something wrong?
EchoVelocity said:
I ran the autoroot script found here to to root my stock device (with TWRP installed).
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
SuperSu is now installed, and when running TitaniumBackup I get a prompt for root however after granting permissions it complains that it could not acquire root privileges. Did I do something wrong?
Click to expand...
Click to collapse
Solved it myself, next time I'll spend 10 more minutes diagnosing before asking. Turns out the version of TitaniumBackup from the Play Store doesn't play nice with Android 5.0, so I'm using the beta they posted to their twitter feed instead.
question
EchoVelocity said:
Solved it myself, next time I'll spend 10 more minutes diagnosing before asking. Turns out the version of TitaniumBackup from the Play Store doesn't play nice with Android 5.0, so I'm using the beta they posted to their twitter feed instead.
Click to expand...
Click to collapse
do you have a link for that twitter feed?? same thing is happening to me right now!!
The current play store version should work correctly now. Just in case it doesn't, have a look here.
https://twitter.com/titaniumbackup
Hi All,
I have a Nexus 7 2013 and I wish to update it. However when the OTA update is run a error message appears. I rooted the tablet several months ago and have since then un-rooted it. When I run a root checker Superuser Binary Files are still installed alongside BusyBox. Could this be the reason as to why the OTA is failing if so, how do I completely remove the files?
Thanks
which SU , manager you used?
maybe you uninstalled the wrong way.
if bussybox is installed, open the remove binary and uninstall.
if not working, install the SU manager you used, go to setting of it and " remove root/binaries"
Hello! I have managed to get Xposed Framework working 100% on my rooted Kindle Fire HD 8 2016. My apologies if I posted in the wrong forum or incorrectly titled this thread as I am new here.
The following method I used is as follows.
1. Downloaded the Xposed Framework installer located at:
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
2. Get some sort of File Explorer app. I personally recommend ES File Explorer.
2. Install APK normally with either browser or file manager app (ex: ES File Explorer)
3. Open app and go to official tab.
4. You should see something that looks like xposed-v87-sdk22-arm, next to it there should be a little downward facing arrow.
Click on it.
5. Select xposed-v87-sdk22-arm64 from the dropdown menu.
6. Click on Install or Install/Update
7. By now you should see a little console window popped up displaying that there was an error finding "app_process64". This is normal.
8. Go to home screen and open your File Explorer app.
9. Navagate to /system/bin/ and delete the file: "app_process64_xposed"
10. Reboot your tablet ("Optimizing System blah blah blah" is normal when booting.)
11. Open the Xposed installer app we downloaded earlier
12. If you see a green box with a checkmark in the middle it worked!
13. Go give coltxL2717 a big ol' thanks over on his post at:
https://forum.xda-developers.com/showpost.php?p=70607706&postcount=4
He's the real MVP!
what kind of xposed tweak would you recommend for this tablet?
What modules are you using?
Sent from my KFGIWI using Tapatalk
vandyman said:
What modules are you using?
Click to expand...
Click to collapse
I am using AdBlocker reborn, Xstana (can only change nav bar), YouTube AdAway and YouTube Background Playback.
Most mods do not work, but I've only tried a very few out of all the options they have.
tkdfriend said:
Hello! I have managed to get Xposed Framework working 100% on my rooted Kindle Fire HD 8 2016.
Click to expand...
Click to collapse
Thank you for this! Rooted. Installed the framework which was needed first and have now installed Xprivacy module. Important to control what applications can and cannot access (location, network, identity, accounts, etc.)
Has anyone tried this on the older model?
What module is working to modify the home button to launch a new launcher app instead of returning to the Fire OS home screen?
@coopmaster Confirmed also working with HD 8 (5th Generation), buy using arm only; not the x64 or x86 and no further deletion is needed.
ttcontributor said:
@coopmaster Confirmed also working with HD 8 (5th Generation), buy using arm only; not the x64 or x86 and no further deletion is needed.
Click to expand...
Click to collapse
so i should be fine if i use just arm ? just making sure before i start this.
coopmaster said:
so i should be fine if i use just arm ? just making sure before i start this.
Click to expand...
Click to collapse
Yes, exactly fine. But make sure not to test every Xposed module cz it might soft brick your Fire !
I recommend 'GravityBox [LP]' as it has pretty extensive features.
ttcontributor said:
Yes, exactly fine. But make sure not to test every Xposed module cz it might soft brick your Fire !
I recommend 'GravityBox [LP]' as it has pretty extensive features.
Click to expand...
Click to collapse
:crying: Already hard bricked my first Fire 6 :crying: Luckily Amazon was a good sport and sent me a new one. Yes! I've learned very quickly to make sure everything is completely stable before attempting anything on these devices as they are VERY touchy! :good:
ttcontributor said:
Yes, exactly fine. But make sure not to test every Xposed module cz it might soft brick your Fire !
I recommend 'GravityBox [LP]' as it has pretty extensive features.
Click to expand...
Click to collapse
GravityBox says it's for vanilla ROMS. Does it work on the Fire?
JAS_21 said:
GravityBox says it's for vanilla ROMS. Does it work on the Fire?
Click to expand...
Click to collapse
Get the [LP] Lollipop version.
I got it working by choosing soft reboot from the xposed installer menu
If someone could help me with a module to change nova launcher prime that'd be great!
"app_process 64 xposed cannot be deleted"
Using ES
Update: Woops, forgot to enable Root Explorer.
Hey, I am stuck at the step where I have to choose the framework. I only have xposed-v89-sdk22-arm64. How do I get v87?
I read that v89 works and used it.
v89 downloads then when the popup to install appears, the app freezes and i'm booted back to the desktop...
i broke it
So, i'm pretty sure i messed up the process, i selected the wrong option from the drop down and it gave me an error. Once i restarted the Fire 10, it's now stuck in bootloop. (fire logo). I tried logging in to the recovery (vol Down+power) but it doesn't let me and restarts.
The tablet was rooted, and had google apps installed.
Any suggestions to get it back?
marksee said:
So, i'm pretty sure i messed up the process, i selected the wrong option from the drop down and it gave me an error. Once i restarted the Fire 10, it's now stuck in bootloop. (fire logo). I tried logging in to the recovery (vol Down+power) but it doesn't let me and restarts.
The tablet was rooted, and had google apps installed.
Any suggestions to get it back?
Click to expand...
Click to collapse
Ugg, same thing happened to me. I followed all the directions after rooting. Stuck at "Fire" logo as well.
Had to boot into recovery and flash stock image (5.6.1.0) to get working again......
UPDATE - 2nd time around all went well. First time I couldn't delete the file using ES, so I just figured I'd reboot first.... Bad idea. Make sure you delete the file first (Enable Root Explorer in ES if it says it can't be deleted)
This is downloading on my device? Is this going to brick it?
No it's fine. Lots of us received that update the days. I don't see anything new but the performance after the update seems very good.
Sent from my iPhone using Tapatalk
Why would you think it would brick your device?
Did any of the previous updates brick it?
I know the number looks strange - it really should be 5.6.... not 5.3, but that's a mistake on Amazon's end as the "Learn more" link to the User Guide has the correct number.
OP had probably downgraded his tablet to a earlier version of FireOS like I did and installed the play store and nova launcher. I havent used it in a few days but when i got it out today, it said it downloaded and installed 5.3.6.4 on 11/11/18 at 1:16am... which is weird because I had previously used this guide to downgrade to 5.4.0.0 ( https://forum.xda-developers.com/amazon-fire/help/fire-7-2017-7th-gen-downgrade-debloat-t3699937 ) and this "update" seems to have downgraded it even further. But nothing has changed except the version number. Lockscreen ads and all the bloat is still gone and nova is still my launcher, so having the update message appear is very head scratching...
BTW, i did the downgrade to 5.4.0.0 MONTHS ago, and have never seen an update message until today. In fact, if I went into the Device Options and selected System Update, it wouldn't allow me into the setting...it would just kick me back to the home screen. Now it DOES allow me into the setting. Very strange.
5.3.6.4 Update remove root?....
After receiving the 5.3.6.4 update on my HD 10 (11/15/18) -
Lock Screen Ads re-appeared on reboot
Titanium Backup - "no longer finds root" (and in turn, no longer works)
SuperSu - No longer works
Nova Launcher remains in-place oddly enough
I have since theoritically (read on) uninstalled all apps mentioned above and re-rooted via kingoroot and can access a root prompt via ADB (id reflects uid=0(root) gid=0(root) context=u:r:init:s0), however I have been unable to update the binaries for SuperSU despite multiple re-installs and reboots (I'm running the previously working v2.79 btw). Additionally, when I now run a fresh install of Titanium BackUp, all I get is an ongoing "Detecting SU & Busybox..." message onscreeen that leads to no where (I just re-installed BusyBox prior) AND when I run Root Checker, it relects no root as well, despite both kingoroot reflecting root within it's app and my ability to run su via an adb shell on my PC., though please also note that I am unable to run su via a shell/terminal emulater installed on the device ("su: not found").
Thoughts?....thanks in advance for the assist.
Peace.