Im trying to root my kindle fire hd (version 7.4.8)
Every time i use Kindle Fire First Aide on the command prompt it says that i have a system path not specified error.
My laptop operating system is windows 8 ( I have not upgraded yet to latest version so I don't know if that's the problem)
Any Help would be appreciated
Steps I Used
1. Download KFFA
2. Opened KFFA using cmd
3. Used option 21 : Alternative root: newer devices
4. Says system path is not specified
5. It starts a daemon but thats all it does
P.S Im not sure but it also looks like i have a adb problem
I turned on the ADB with usb and used the adb drivers in KFFA but it never works
I'm having a similar problem.
I've had my kindle rooted for several months now, and I'm sure that I had turned auto updating off...however, this update (7.4.8) was forced on me a couple of weeks ago, and now I've lost the ability to usefully run Google Play (it keeps giving me a 'no connection' error). I also cannot update any programs that were obtained through google play.
A few things that I have noticed:
BusyBox Installer says that my Kindle is rooted, but cannot install BusyBox, or run any of the scripts.
KFFA cannot access my Kindle. I have tried several proceedures on the forums to rectify this problem, to no avail. I have tried with several cables including the original, and the cable that I previously successfully rooted my kindle with.
My kindle has started showing ads on the lock screen at times, which was something I disabled with KFFA when I first rooted my kindle.
I do have momentary adb access while booting, but it gets disconnected as soon as the lock screen appears and I cannot reconnect
same problem here, can't manage to root kindle with 7.4.8
RE:
Well then i guess it will only work if you brick your kindle to reboot over and over then root and use kffa to root it then unbrick it using it and i think it will work let me try
Successfully rooted Kindle Fire HD 7.4.8
Hi,
So this morning I reset to factory my KFHD 7.4.8. Clean start...
1/ install KFFirstAid from geekappz.blogspot.com/2013/02/root-kindle-fire-hd-and-2-with-windows.html
I did install the 64bit version on my windows 7.
2/ execute all installation steps of KFFA as explained in the link above until reaching C-1 root step 10 (do that step 10).
3/ connect your kindle to your computer via USB
4/ the runme.bat in KFFA depends on another system package called busybox. Great package but... you cannot install from amazon store on a fresh kindle, and the installation via the runme.bat does not work. I decided to do without busybox... So replace the original runme.bat in C:/KFFirstAid by the one attached. I edited the sections 18 and 21 (i "rem"ed some lines, and put the corrected code just below). I edited only these two options. (means do not ask about the others...)
(site did not upload the file, so here is a link to it... drive.google.com/file/d/0ByEA1ADGX9vNS2RKUEdKYnN6Uk0/edit?usp=sharing)
5/ launch "my" runme.bat.
6/ select option 21. This will root the kindle. Follow the instructions (including the full restore at the beginning). It will reboot quite a few times, just be patient... (very). Your kindle may seem up and running, but the adb communication may take a few more minutes to go through...
At the end, superuser.apk is installed, look for it in the command window log. When done, on your kindle, start supersu and let it update itself. Verify root access with root check basic.
7/ return to the main menu of runme.bat,
8/ select option 18. This will install google play. Follow the instructions, including the registration to google on the kindle, in the middle of the installation. During this registration i experienced a few "application stopped working", but it went through anyway... so do not panic...
Again, a lot of reboots...
That's all folks... (takes about two hours...)
Successfully Rooted KFHD 7.4.9
Still works for KFHD 7.4.9
Replaced some "mv" commands by "dd" commands to workaround a cross device link error, in the runme.bat file.
fabienwahl said:
Hi,
So this morning I reset to factory my KFHD 7.4.8. Clean start...
1/ install KFFirstAid from geekappz.blogspot.com/2013/02/root-kindle-fire-hd-and-2-with-windows.html
I did install the 64bit version on my windows 7.
2/ execute all installation steps of KFFA as explained in the link above until reaching C-1 root step 10 (do that step 10).
3/ connect your kindle to your computer via USB
4/ the runme.bat in KFFA depends on another system package called busybox. Great package but... you cannot install from amazon store on a fresh kindle, and the installation via the runme.bat does not work. I decided to do without busybox... So replace the original runme.bat in C:/KFFirstAid by the one attached. I edited the sections 18 and 21 (i "rem"ed some lines, and put the corrected code just below). I edited only these two options. (means do not ask about the others...)
(site did not upload the file, so here is a link to it... drive.google.com/file/d/0ByEA1ADGX9vNS2RKUEdKYnN6Uk0/edit?usp=sharing)
5/ launch "my" runme.bat.
6/ select option 21. This will root the kindle. Follow the instructions (including the full restore at the beginning). It will reboot quite a few times, just be patient... (very). Your kindle may seem up and running, but the adb communication may take a few more minutes to go through...
At the end, superuser.apk is installed, look for it in the command window log. When done, on your kindle, start supersu and let it update itself. Verify root access with root check basic.
7/ return to the main menu of runme.bat,
8/ select option 18. This will install google play. Follow the instructions, including the registration to google on the kindle, in the middle of the installation. During this registration i experienced a few "application stopped working", but it went through anyway... so do not panic...
Again, a lot of reboots...
That's all folks... (takes about two hours...)
Click to expand...
Click to collapse
Root Kindle Fire HD 7.5.1
Still works for KFHD 7.5.1
Option 18, to remove Amazon adds has been recoded in "my" runme.bat
Use also post below to remove an additional file (the kso file is now removed by the option 18 above)
http://forum.xda-developers.com/showpost.php?p=52046640&postcount=73
fabienwahl said:
Still works for KFHD 7.4.9
Replaced some "mv" commands by "dd" commands to workaround a cross device link error, in the runme.bat file.
Click to expand...
Click to collapse
Related
My Nook Tablet just updated to the dreaded 1.4.1 version which makes sideloading pretty difficult.
I was reading this article which has steps to sideload apps onto the 1.4.1 NT without rooting it, and pointed to downloading this script on the XDA forums which will push the apk onto the plugged in tablet, as long as the apk is in the same folder as the Sideload script files.
So, steps 1 to 5 weren't a real problem but its Step 6 that I'm stuck on.
There is a Sideload BAT script which seemed to run (its disclaimer is that it will only run if it finds an Android device -- which is a clear indication that it could find and recognize that my Nook Tablet is plugged in). It even says C:\Sideload>adb wait-for-device. However, when I try to tell it to install the apk via Command Prompt (I type in: adb install Amazon_Appstore-release.apk ), it returns "error: device not found" .
Just for good measure, I also type in C:\Sideload\adb devices and it returns: List of devices attached .
I'd greatly appreciate if somebody could help me with this--I really have it up a wall and would just like to put this problem to bed. Thanks!
i'm having the same exact problems here! are there any specific drivers to install?
Yep, I was still fairly a noob at this when I first posted but have learned a lot ever since. Here's what you want to do:
(btw, I factory resetted to 1.4.0--you may need to as well):
When it says "no device found", it's corresponding to this command line : adb install whatevernameofapp.apk . I interpreted "no device found" to mean that it does not know what "adb" means in the command.
For it to recognize all "adb" related commands, you have to have the USB drivers installed. Look for tgps_launcher.apk on this link: http://forum.xda-developers.com/showthread.php?t=1354487. That will set you up with having you Nook to accept third party applications + having it on UBS debug mode.
Then, install the drivers (I saw this YouTube walkthrough because it is NOT intuitive and you want to be sure you're doing it right , it's not the way you would traditionally update drivers for a mouse or keyboard; here: http://www.youtube.com/watch?v=ZtGveN7jbzs )
After that, I followed the instructions on this article, made a folder in C:, called it sideload, and also pasted an .apk. Now, when I do the Commant Prompt, it says this: http://img23.imageshack.us/img23/2914/cmdnookadb.jpg . While, the transfer was successful, I haven't been able to see the app on my tablet. Does anyone know where I can find this (data/local wasn't found when I connected the tablet to my PC either, and it wasn't on my SD or so). Is it because I'm still on 1.4.0?
Let me know if you get it working all the way!
I followed all those directions exactly. I had received the No Device Found error. I followed the Youtube directions to add drivers and it seems like I did it correctly. I am seeing the android device on the device manager.
I tried running the script again and got the same error! I'm now stuck!
I had the amazon marketplace already installed and was using it successfully until my nook updated to 1.4.2. I thought I had ES File Explorer downloaded but for some reason I can't find it! So I now I am trying to sideload ES File Explorer this way but it wont work!
0x2080
^ put that in %userprofile%\.android\adb_usb.ini
Can you give me more specific instructions on how to do that?
FYI - I have ver 1.4.2 and I am NOT rooted. I have already enabled unknown sources and downloaded the amazon market. I was installing 3rd party apps fine before the update.
[HOW-TO] Use ADB tool | Android Debug Bridge
You need to revert to stock 1.4.0, there are easier and faster ways to do that now > check development section. Basically you need to have CWM booting from sdcard then flash stock ROMS posted >> Albert and I have posted 1.4.0 stock ROMs.
~ Veronica
Moved To Q&A
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment Rockusb.rar
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
Thanks for the info. Will be giving it a go later today
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
when in doubt go back to the forums. I can not get the inf in the rockusb to install. "Installation for this file type not permited" . So I'm stuck, the program will not complete. I'm on windows 7 so maybe the driver is for another system. If you can provide futher help, Thanks in advance.
New approach
Ok I cannot get the drivers to install on my computer. Window 7 seems to default to its own driver and will not let me install the rockusb drivers.
With that said, I have the system Update.img and was wandering if the img itself can be rooted and then updated to the tablet. If this is possible and anyone with the knowledge is willing I will upload it. Or if someone is really patient and would like to walk me through the process and I will attempt to do this myself
No Help
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
Can't tell your level of PC knowledge so if you already know this don't get offended. The .inf is editable and there are areas in there that allow manufacturers to prevent installation on some OS's to prevent conflicts. Make a system restore point or better yet a backup and then post the contents of the INF somewhere and point the folks here to it and they may be able to help you edit it to install. Regardless, you'll have to use the "have disk" option instead of letting windows search for a driver even if you get the edits right. And the usual disclaimers about me not being responsible for any issues with your equipment as a result of this are in effect.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
I was able to root using the instructions above although i don't think you need the rockusb drivers. You just need the usb drivers that come with the android sdk. I am on Win 7. Thanks for the above info for rooting.
I was able to install ROM manager and now proceeding to backup ROM and upgrade using this guide: cant post link as forum is preventing, but search for rom flash guide on androidpolice com.
Hope this helps.
Big thanks to this thread to get me going...!!!
?
could someone please, Barney style, Explain how I am supposed to select the android_winusb.inf because my steps are as follows. Right click on device p771a in device manager, browse my computer, let me pick from a list of device drivers, have disk, point to the google usb driver (C:/Android/android-sdk/extras/google/usb_driver) select the android_winusb.inf open. Hit ok, (The folder you specified doesn't contain a compatible software driver for you device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems). Hope this helps explain my troubles. Glad that my thread is helping others to root this device but it does not work for me.
Could it really be that simple?
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
tannerjames said:
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
Click to expand...
Click to collapse
Glad you could figure it out...
I was not able to use the ROM Manager to backup the ROM since the device is not supported on this tool, but see below for how you can obtain the stock image.
I've tried to flash multiple different ROMs using RKAndroid to the tablet, spending days on this, with no success. The tool itself works great and I am able to flash the ROMs since it supports the RK29 chipset which I believe this tablet has. The stock ROM for this device is available from the manufacturers web site (the link is available when you go to Settings => About Device => System Update, hkcdigital dot com slash update slash update.img), if anyone would like to take the stock rom and upgrade it to Android 4.2/JB.
I was able to unpack/repack the stock image using the wendal image tools and modify / cook the ROM using Android kitchen method described elsewhere in this forum. Rockchip Batch Tool is another great utility to flash custom ROMs to this device. Also, If you put the ROM as update.zip or update.img file on the microSD card, the tablet will take it and flash the image as long as it is in the right format. Ofcourse you can put the tablet into recovery and restore from there as well. I've found that the stock image (update.img) has the following file/folder format when unpacked: /RK29xxLoader(L)_V2.27.bin, /package-file, /parameter, /recover-script, /update-script, /Image/boot.img, /Image/system.img, /Image/recovery.img and /Image/misc.img.
Is it possible to upgrade this tablet to Android 4.2 or atleast Jelly Bean? Would be very helpful if someone is able to do this. The most success I've had so far is with the custom ROM Oma_Odys_Loox_JB_4.1.1_v1.2.2a flashed using RKAndroid. It flashed the tablet fine, updated the boot etc. On tablet boot I am able to see the new logo, but then the it doesn't go anywhere from there. I think customizing this ROM or the stock ROM we should be able to get the new OS on to the HKC tablet. I've given up for now since I don't have the time to spend on this anymore. If someone is able to do this, please post the instructions or upload the custom ROM, as I am sure it will benefit a lot of people and will be much appreciated. Happy cooking!
Thanks!
jawadshaik- rom manager
If you have successfully flashed rom manager on this device could you post the steps you took to do so. What version? Manual flash? The program itself says there is no recovery for this device.
Sorry jumped the gun on that last post. Thanks for the info
What's the secret to keeping the battery from draining so quickly while it's idle? I just got this and see it drained about 40% in about 2 hours I think and I wasn't using it.
tannerjames said:
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
Click to expand...
Click to collapse
@jawadshaik
Just out of curiosity, when you were flashing that Rom that brought up the boot screen, did you do a wipe/factory reset from recovery mode before flashing? I have no idea if that would help or not, but most if not all roms require a data wipe before flashing... Just curious if you had tried this as I have heard of this happening on other devices because a data wipe wasn't done first. Might be worth a shot if you haven't tried it already, just a thought
Sent from my Huawei u8651s using xda app-developers app
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
So after doing working on this a while, I've finally figured it out. Here are some caveats:
1. You can't do this on a Mac or Linux box. Don't ask me why, you just cant.
2. You have to turn on USB debugging, change the Security to allow Unknown sources and MOST IMPORTANT: when you plug it in, you have to change it to "Connected as a Camera". Putting it in storage mode doesn't work!
HOW TO INSTALL THE PROPER DRIVER & ROOT THE DEVICE:
1. Follow the steps quoted above and download the Google Android SDK, and the Java JDK (from oracle.com/java).
2. When you first plug it in (use the USB plug labeled USB not the HOST one), it complains and will discover a P771A device. When it does, right click on your computer, choose Manage my computer, go to the device manager and then right click on the P771A device. Click "Update Device Driver". Choose "Browse my computer for Driver software". Then choose, "Let me pick from a list of drivers on my computer". Browse to the \adt-bundle-windows-x86_64\sdk\extras\google\usb_driver folder which you would have if you had downloaded and installed the Google Android SDK. A list of 3 drivers will appear when you click OK. CHOOSE THE "ANDROID BOOTLOADER INTERFACE" as the driver. None of the others work.
3. Run the root script batch file mentioned above which can be found here at: sourceforge.net/projects/androidroot
4. The root script isn't really great at explaining so I'll try. When you first run it, make sure your device is unlocked and on the home screen.
5. The first thing it will do is reboot your machine. Don't press enter until your machine comes back up.
6. After your machine boots unlock it and then press Enter again. Your machine will reboot. This time it won't seem to come up but the backlight will remain on.
7. Wait about 30-45 seconds then press enter again. You should get: uid=0(root) gid=0(root) in the command prompt window.
8. Press Enter. You should get:
remount succeeded
727 KB/s (22364 bytes in 0.030s)
Removing changes except ROOT...
Installing superuser...
2288 KB/s (843503 bytes in 0.360s)
9. After about 30-60 seconds, your device should reboot. You'll see a box briefly saying "Android is Upgrading" and you'll arrive at the lock screen. Press Enter to exit the command prompt.
Your device is now rooted and you should see "SuperUser" installed. I promptly installed "root uninstaller" to get rid of Facebook, Skype, and Youtube which my little kids don't need access to. This device doesn't have a bootloader or recovery mode so rooting it doesn't get you much besides the ability to uninstall the system software. Have fun.
This may help someone but on step 2 of the guide on the second page, after you right click your device and go to "Let me pick from a list of drivers on my computer". You then click "Show All Devices" then "Have Disk..." Direct it to the root of the adt-bundle folder you downloaded then you can select from the three drivers. I'm on windows 7 32bit and the drivers didn't show up for me like how it was suppose to..
I also could NOT get any of the drivers in the "manufacturer USB" packet to install... I WAS able to install the google drivers, but that also would not allow ADB to see the device... So still stuck with everyone else...
P771A possible problem
I'm having a similar problem where the USB driver downloaded through Android SDK's -> Extras -> Google USB Driver, tells me that the file contains no information about my device. I noticed in the Sources of SDK, there wasn't an API for 4.0.4, only 4.0.3 then 4.1, so i downloaded 4.0.3 repo.
============================================
my devices is on 4.0.4, and my Kernal is as follows:
3.0.8+
[email protected] #8
Wed Aug 29 09:59:19 PDT 2012
Build Number:
P771A-user 4.0.4 IMM76D user.v402.007 release-keys
============================================
I've also made sure weather Unknown Sources is on, as well as USB debugging.
Might the Kernal be the problem? Also, does it matter weather its MTP or CTP?
Now HKC is telling me that they don't support the ability to jail break their devices
Sent from my P771A using xda app-developers app
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Added English version manual on Lenovo-Forums.ru
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
Do this root apply to the s8-50F ?
EDIT: This method indeed does work on the S8-50F variant. Was having problems with device staying in adb while running program, but a reboot of pc fixed that and gained root effortlessly. THanks!
Glad It Helped !!!
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
The download isn't working for me. It's not downloading as a zip? Any suggestions?
If youre using windows, download a program called 7-zip and downoad the file. right click the root software and click extract here. or open with 7-zip. You could also use winrar. The format of the file is in .7z right ? that means search up http://www.7-zip.org/
Any idea how to unroot?
Not sure. Have you tried the full unroot method in the su app?
__McB__ said:
Any idea how to unroot?
Click to expand...
Click to collapse
SuperSU.apk.....in the setting, unroot, cleanup...
icanttinkofaname said:
Not sure. Have you tried the full unroot method in the su app?
Click to expand...
Click to collapse
jazzespresso said:
SuperSU.apk.....in the setting, unroot, cleanup...
Click to expand...
Click to collapse
Thanks both of you. I ended up returning it, root and all, but I'm sure your suggestion would have worked.
After rooting, has there been anything anybody's been able to do about battery life? I don't imagine there's been any Roms built for this device yet, but didn't know if maybe someone's figured out something that's helped extend their battery life, because when playing certain games like clash of clans for instance, I'm lucky to get an hour and a half of game play, and that's with my brightness turned all the way down. Any suggestions would be greatly appreciated. Thanks
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
This root guide works on s8-50f! thanks Xakep
This is a very easy and usefull root instruction, i rooted my tab s8-50f with no problems.
I followed the steps described and got instant root without any issues.
My machin is windows pc with windows 8.1 pro 32bit. Plug your tab and windows recognized the drivers just make sure your device mngr shows lenovo s850 and you are all set. Then just run the flash tool and it will run in less than a minute your tablet will reboot and your tab will be rooted.
Yes this is probably the easiest I've ever rooted any device in the past. If at first it doesn't take, don't worry it will. Just repeat the process till it does. Thanks Hash.h for putting up this thread and passing along the info
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
Where can I download the ADB drivers for S8-50 from?
I think drivers come with tablet. Try to connect the tablet and it will show CD drive on which is the driver.
error: device offline?
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Worked great. Thank you.
Awesome little tablet.
Jirbo said:
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Tried on another computer and succeeded.
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
moogthedog said:
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
Click to expand...
Click to collapse
Same problem here. Lost root after the last update and now I can't get either root method to work.
I installed ADB and fastboot from http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 and Bloater from http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294.
I have one KFHD6 that got the OTA 4.5.4 update prior to anything else. This one connects to my PC just fine and ADB works. It's the device I used to install PDANet, which helped me get the computer to recognize the Kindle in ADB.
I took another KFHD6 out of the box today (on 4.5.3), ADB was enabled by default, I did not setup Wi-Fi so I could keep 4.5.3. When I connect it to my PC, I get the Autoplay popup on my computer, but ADB does not connect. There's no prompt to trust the computer. I've tried the same cable. I've tried turning ADB off and back on. I've rebooted my devices.
I did notice that the Autoplay icon is different for the two Kindles. The 4.5.4 looks like a phone ( http://www.groovypost.com/wp-content/uploads/2012/09/Open-Device-to-View-Files-AutoPlay.png ). The 4.5.3 looks like a tablet like the icon here ( http://cnet1.cbsistatic.com/hub/i/r.../066e9701a8d91559092f149bd6b32516/drivers.jpg )
Does anyone have any suggestions? Thanks!
I figured it out. I don't have PDANet installed on the 2nd Kindle. Can someone tell me the path in the Silk Browser to execute the apk? For example,
file:///Download/PdaNet.apk
But that's not it. I don't have Internet on the Kindle yet, because I don't want OTA updates, so I can't install ES Explorer from the Store. I just need to be able to execute the APK file that I transferred to the Kindle via the USB cable. Thanks!
I figured THAT out. But Silk is not executing the file. It states that it has to download it and that it can be found in Downloads, but then the screen goes black and nothing happens. I hit home to get out of Silk, go back in and it's still black. If I reboot, and then open Silk, it asks if I want to restore my tabs. Yes, gives a black screen. No puts me back at the Silk browser again. The file doesn't show up in the Downloads section of Silk, so I'm unable to execute it. Surely there's a way to install APK files without ES Explorer (I'd actually like to install ES Explorer, but without Internet access).
Which came first--the chicken or the egg? Please help. Thanks!
I have yet to figure this out. I have several KFHD6's. The first one was a breeze to get ADB working. The second one had trouble, but it finally started working when I uninstalled the driver from the Device Manager and the ADB Driver installed. I have 3 more new Kindles which don't want to get on the ADB bus. Does anyone have any suggestions? Here's what I've done:
Installed Minimal ADB and Fastboot (http://forum.xda-developers.com/showthread.php?t=2317790)
Installed PdaNet (http://pdanet.co/)
Installed Android SDK (http://dl.google.com/android/installer_r24.3.3-windows.exe)
Updated an inf file and tried to update the driver (http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/)
The first worked after the first 2 bullets. The second worked after the first 3 bullets and then uninstalling the driver in the Device Manager. Any input would be greatly appreciated.
Here's the solution if anyone has this problem:
Plug in the new device. Let it install the driver in Device Manager. Right-click --> Properties on it. Uninstall device and unplug it. Reboot your PC and you Kindle. Plug your Kindle back in.
It was that easy for me--on 2 new devices. The 3rd was literally plug-and-play. Very weird.
I have a rooted kindle and the past few days my Wi-Fi isn't working right. Some days it will switch right on and connect other says you switch it on and it does nothing and acts as if the wifi is still turned off. Please help. I did factory reset and it didn't help. I can post a video to YouTube to show you if you need.
Heatherb90 said:
I have a rooted kindle and the past few days my Wi-Fi isn't working right. Some days it will switch right on and connect other says you switch it on and it does nothing and acts as if the wifi is still turned off. Please help. I did factory reset and it didn't help. I can post a video to YouTube to show you if you need.
Click to expand...
Click to collapse
- known side effect of KingRoot
- toggling Airplane/Flight mode should work; give it a few seconds to connect
- consider a custom ROM if further relief is needed; Fire Nexus (KitKat based) works best if WiFi reliability/stability is a priority
worse issues lol
I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated.
heather90 said:
I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated.
Click to expand...
Click to collapse
I will respond to this in the next 24 hours - hang tight.
Thank you
I will keep checking for your response. I really appreciate your help.
heather90 said:
I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated.
Click to expand...
Click to collapse
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
LINK?
When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
Heatherb90 said:
When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks.
Click to expand...
Click to collapse
Yes - Motorola drivers have proven to be highly compatible with HDX devices. The link will install some other stuff that is not needed but is otherwise benign (does not run in background, etc).
My other Kindle Tethers fine
I am not sure if this makes any difference but my other Kindle which is exactly the same except unrooted tethers just fine to my laptop. It immediately shows up in file manager as Fire when I plug in the cord.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
waiting
I am installing that motorola driver now. Seems it may take quite a while to install.
It didn't change anything. It still shows in device manager as Andriod Phone > Google Nexus ABD Interface and the only thing it does when I right click is open properties and in properties it has General, Drivers, Details, Events and under drivers my only option is Driver details and it also says Driver Provider: Clockwork Mod.
Heatherb90 said:
When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks.
Click to expand...
Click to collapse
It didn't change anything when I got the motorola drivers. Still shows up in device manager are android phone and no options to uninstall anything.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
I got it to tether sucessfully. Now to try the next steps in recovering my kindle. Thanks so so so so much for your help. I had to go into TWRP menu and select mount usb storage.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
Got the computer to recognize my device but now I can't flash the kindle software. I tried just drag and dropping it into kindle and couldnt find it via twrp install so i found a thread about using adb commands and i get the issue that my device is unauthorized when i type ADB devices.
Davey126 said:
Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands.
Suggested path:
- on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices
- untether device
- open Windows device manager
- boot HDX into recovery (TWRP)
- tether device; take note of what entry(s) appear in device manager
- right click those entries and click 'uninstall'
- untether HDX, wait a few seconds then retether
- when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface"
- open File Explorer in Windows ... does device now appear?
There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
Click to expand...
Click to collapse
Heatherb90 said:
Got the computer to recognize my device but now I can't flash the kindle software. I tried just drag and dropping it into kindle and couldnt find it via twrp install so i found a thread about using adb commands and i get the issue that my device is unauthorized when i type ADB devices.
Click to expand...
Click to collapse
Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there.
On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download".
Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats.
If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
When opening the kindle with file explorer I see internal devices then twrp and in that folder is a single file called twrp. I
I am going to try just dropping it in the twrp folder since that is the only folder I have and if that does not work I am not sure what to do. Could I possible create the Download folder within the internal storage folder?
Davey126 said:
Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there.
On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download".
Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats.
If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
Click to expand...
Click to collapse
OK so I got the file onto the kindle and when i try to flash the rom I get the error E: Error execturing updater binary in zip '/sdcard/downloads/kk-fire-nexus-rom-apollo-20161017.zip'
Davey126 said:
Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there.
On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download".
Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats.
If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
Click to expand...
Click to collapse
Finally got it thank god. The only rom that would work was Thor. The Apollo one would not work and kicked out that error but first try Thor went right on. Thank you so much for all your help and listening to my annoying posts lol.
Davey126 said:
Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there.
On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download".
Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats.
If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
Click to expand...
Click to collapse
Heatherb90 said:
Finally got it thank god. The only rom that would work was Thor. The Apollo one would not work and kicked out that error but first try Thor went right on. Thank you so much for all your help and listening to my annoying posts lol.
Click to expand...
Click to collapse
Glad you got it sorted. FWIW:
- Thor = 7" 3rd gen HDX (your device)
- Apollo = 8.9” 3rd gen HDX