FORUMS
Remove All Ads from XDA

[TUT] ROOT HD 10 (7th Gen 2017) - EASY SuperSu (read this before 1st power on!)

972 posts
Thanks Meter: 677
 
By bibikalka, Senior Member on 28th December 2017, 07:46 AM
Post Reply Email Thread

Update v0.8, 01/26/18 - as first reported by @najoor in this post, FireOS 5.6.0.1 is rootable! Today I verified this myself after a somewhat unsuccessful FlashFire update.
Update v0.7, 01/14/18 - @freaky2xd made a video with these rooting instructions, please follow it if you prefer a visual guide (here or here)
Update v0.6, 01/09/18 - there were reports that dr.fone app seems to be able to root the device as well. I took dr.fone for a spin, and based on its bloatedness and a few other annoying features, my personal recommendation is that you stick with the devil we know - Kingoroot (link)
Update v0.5, 01/04/18 - add a DOS bat file to remove any possible updates to Amazon packages
Update v0.4, 01/02/18 - title update
Update v0.3, 12/31/17 - light clean up; I got into a bootloop, and had to sideload a stock ROM & re-root - a.k.a. "eat my own dogfood" - Everything works fine.
Update v0.2, 12/30/17 - some redundant commands are removed.
Update v0.1, 12/30/17 - the rooting procedure is essentially taken from @retyre (here and here). Except, the instructions below include a lot of details, and handle mostly everything from the PC/ADB side. Try, and report back. GOOD LUCK!





Here is the guide to the painless root (while out of the box FireOS allows it; right now all FireOS versions up to and including 5.6.0.1 - the current OTA - are rootable). The key enabler is the original post by @ztrund (link), great work blazing the trail (and motivating me to get another Fire tablet ASAP, LOL).

Given that the devices will be shipping with the (older) rootable FireOS for the next few months (but beware of the upcoming updates - see below !!!), there is a good window of opportunity to acquire a rootable Fire HD 10, and root it. As of Dec 27th 2017, there are no reports yet of non-rootable OTAs, but those OTAs will be coming soon, count on it!

The utmost goal here is to preserve the earliest FireOS version that you get, and not let it get updated by Amazon on a whim.
I am starting with a recently bought Fire HD 10 2017 (light refurb from eBay, missed the Black Friday mega sale ). I have FireOS 5.5.0.0 (earlier than 5.6.0.0!), version name 5.3.5.1 (591450020)





Part I (avoiding Amazon updating procedure upon the initial Fire setup) - this can (almost safely) be skipped today (end of Dec, 2017), since there are no reports of unrootable OTAs yet

Low tech way (thanks to @Blaiser47 and @retyre for suggestions!):
  1. Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
  2. Choose any option on that WiFi screen, press cancel, and then skip
  3. Once Alexa shows up, swipe down from the top, turn on Airplane mode just to be sure

High tech way:
  1. Set up a dedicated slow router, limit upload/download speed to ~25 kbps (this is the trickiest part, I have a dedicated Tomato router which I use to control traffic)
  2. Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
  3. Connect Fire to your slow router
  4. Once Fire finds Internet, it'll immediately have "Checking for updates" on the screen, this is where the slow router should kick in, and do the trick of forcing the update to give up
  5. Wait a bit for updates, hopefully, it won't find them, if found something, do factory reset, and repeat (on my 1st try it did find the update, although, could not download it quickly enough, I did a factory reset via Pwr&Vol+ recovery mode, and tried again - the 2nd time it skipped the update due to the slowness of the connection)
  6. Sign in to Amazon account when prompted
  7. Once Alexa shows up, swipe down from the top, turn on Airplane mode - no more risk of updates!!!





Part II (rooting via Kingoroot, disabling OTA, and getting SuperSu replacement, as per @retyre recommendations)
  1. Take your Fire HD as is, do not do anything dramatic such as "factory reset", Amazon ROM sideloading, etc
  2. Swipe down from the top, turn on Airplane mode - to ensure that there are no OTA updates during the procedure
  3. In "Settings/Device Options", tap "Serial Number" 7 times, a menu "Developer Options" will appear
  4. In "Settings/Device Options/Developer Options", turn ADB debugging to ON (under "Debugging")
  5. In "Settings/Security", turn "Apps from Unknown Sources" to ON
  6. Download ADB to your PC (link)
  7. Setup ADB drivers on your PC, connect Fire to your PC, make sure "adb devices" command shows your Fire device, authorize ADB connection on Fire
  8. Download SuperSu 2.79 (this exact version!!!) to your PC from this link, place it into your ADB PC folder. The filename of this apk will be assumed to be SuperSU-v2.79-20161205182033.apk below
  9. Download the attached su64.zip to your PC (see the attachment below), unzip to your ADB PC folder
  10. Open a CMD window in ADB PC folder (this will be called ADB_cmd window in the following steps), type
    Code:
    adb devices
    adb uninstall eu.chainfire.supersu
    This is a clean up of possible old SuperSu (just in case), ignore any errors you may get (if SuperSu is absent ...)
  11. Download Kingoroot to your PC (link), install, let it update
  12. Connect Fire to your PC; launch Kingoroot on PC; before pushing the big "ROOT" button in Kingoroot, uncheck a small box in the lower left corner for "Install recommended app" ; push "ROOT" button; wait for Kingoroot to root
  13. Once Kingoroot succeeds, open a 2nd CMD window in ADB PC folder to your Fire (this will be called ADB_root window in the following steps), get a root shell, and disable OTA updates
    Code:
    adb shell
    su
    mount -w -o remount /system
    mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_
    ls -l /system/priv-app/DeviceSoftwareOTA/
    ignore any errors you may get while doing this; after 'su', you should see root (#) prompt here
  14. Switch to the first ADB_cmd window, type
    Code:
    adb uninstall com.lionmobi.powerclean
    adb uninstall com.kingoapp.link
    adb uninstall kingoroot.supersu
    adb install SuperSU-v2.79-20161205182033.apk
    adb shell "am start -n eu.chainfire.supersu/eu.chainfire.supersu.MainActivity"
  15. Skip this step - it is not needed
    Switch to the second ADB_root window (with # prompt), type
    Code:
    cd /data/local/tmp
    mount -w -o remount /system
    cp ./su64 /system/xbin/daemonsu
    chmod 0755 /system/xbin/daemonsu
    daemonsu -d &
    cp ./su64 /system/xbin/su
    chmod 0755 /system/xbin/su
    am start -n eu.chainfire.supersu/eu.chainfire.supersu.MainActivity
  16. On your Fire, SuperSu should pop up. Update SuperSu binary as "Normal", it should report "Installation failed." Proceed to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
  17. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
  18. Uninstall all the junk from Kingoroot on your Fire, thanks to @fstanis for detailed instructions (copied here, executed from PC):
    Code:
    adb uninstall com.nemo.vidmate
    adb shell rm -rf /sdcard/VidMate
    adb shell rm -rf /sdcard/.a
    adb shell rm -rf /sdcard/.DataStorage
    adb shell rm -rf /sdcard/.UTSystemConfig

Some troubleshooting options:
  • If you believe you have the correct FireOS, but Kingoroot (or SuperSu) still fail, download the attached no_amzn_updates.zip to your PC, unzip to your ADB PC folder, open a CMD window in ADB PC folder, and type
    Code:
    .\no_amzn_updates.bat
    The script will attempt to uninstall any apk updates to the official Amazon packages. Then repeat the rooting procedure from Step 1 skipping as necessary. See this post for more additional info on what the script does.
  • If you mess up your /system too much and get into a bootloop with "Fire" logo - use this post for links to the official Amazon ROM files; these bin's can be sideloaded via "adb sideload" in recovery
Want to say thanks by clicking the "Thanks" button ?
Attached Files
File Type: zip su.zip - [Click for QR Code] (34.7 KB, 1008 views)
File Type: zip su64.zip - [Click for QR Code] (41.2 KB, 2736 views)
File Type: zip no_amzn_updates.zip - [Click for QR Code] (1.6 KB, 1200 views)
The Following 36 Users Say Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
 
 
28th December 2017, 07:46 AM |#2  
OP Senior Member
Thanks Meter: 677
 
More
Fire HD 10 ROM links & misc :
Fire HD 10 (7th Gen 2017) ROM links from Amazon (use for sideloading your preferred version in case you mess up). If possible, turn off WiFi before sideloading a bin file - you don't want to catch an OTA while it's loading!

FireOS 5.6.0.1
update-kindle-40.5.9.5_user_595550320.bin
System image (restore via FlashFire v0.24) - link. Unzip files to /sdcard/FlashFire/Backups/5.6.0.1. The system image includes SuperSu, Xposed, Busybox; OTA apk is renamed.


FireOS 5.6.0.0
update-kindle-40.5.9.5_user_595457320.bin

FireOS 5.5.0.0
update-kindle-40.5.9.1_user_591450020.bin



In addition, please find attach a SuperSu zip that works with Flash Fire v0.24 (tested with FireOS 5.5.0.0 & 5.6.0.0).

The file was created by taking SuperSu v2.82 zip from this link (file name - SuperSU-v2.82-201705271822.zip).

Then in META-INF\com\google\android\update-binary I replaced one line forcing SuperSu to install armv7 binaries instead of arm64:
Code:
    if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=arm64; SYSTEMLIB=/system/lib64; APPPROCESS64=true; fi;
with this one:
Code:
    if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=armv7; fi;
Everything else is identical to the official version.
Using the official SuperSu zip will cause a bootloop - it looks like Fire HD 10 is not quite arm64 yet, and needs armv7 version of su binaries to work.
The Following 6 Users Say Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
28th December 2017, 07:47 AM |#3  
OP Senior Member
Thanks Meter: 677
 
More
Partition trivia:
Partition info (gdisk binary) :
Code:
root@suez:/ # df
df
Filesystem               Size     Used     Free   Blksize
/dev                   907.7M    80.0K   907.6M   4096
/dev/logd              512.0K    96.0K   416.0K   4096
/sys/fs/cgroup         907.7M    12.0K   907.7M   4096
/mnt/asec              907.7M     0.0K   907.7M   4096
/mnt/obb               907.7M     0.0K   907.7M   4096
/system                  1.5G     1.2G   317.9M   4096
/data                   26.5G     1.1G    25.4G   4096
/data/metrics            5.8M   232.0K     5.6M   4096
/cache                 410.7M    14.9M   395.8M   4096
/mnt/sqfs               79.8M    79.8M     0.0K   32768
/mnt/cd-rom              1.2M     1.2M     0.0K   2048
/mnt/shell/emulated     26.5G     1.1G    25.4G   4096
/storage/emulated      907.7M     0.0K   907.7M   4096
/storage/emulated/0     26.5G     1.1G    25.4G   4096
/storage/emulated/0/Android/obb    26.5G     1.1G    25.4G   4096
/storage/emulated/legacy    26.5G     1.1G    25.4G   4096
/storage/emulated/legacy/Android/obb    26.5G     1.1G    25.4G   4096

root@suez:/data/local/tmp # ./gdisk -l /dev/block/mmcblk0
./gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): B1541C10-343E-474B-B5B2-05796C64E992
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071326
Partitions will be aligned on 1024-sector boundaries
Total free space is 990 sectors (495.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            1024            7167   3.0 MiB     8300  proinfo
   2            7168           16383   4.5 MiB     8300  PMT
   3           16384           18431   1024.0 KiB  8300  kb
   4           18432           20479   1024.0 KiB  8300  dkb
   5           20480           22527   1024.0 KiB  8300  lk
   6           22528           32767   5.0 MiB     8300  tee1
   7           32768           43007   5.0 MiB     8300  tee2
   8           43008          123903   39.5 MiB    8300  metadata
   9          123904          124927   512.0 KiB   8300  MISC
  10          124928          141311   8.0 MiB     8300  reserved
  11          141312          174079   16.0 MiB    8300  boot
  12          174080          208895   17.0 MiB    8300  recovery
  13          208896         3515391   1.6 GiB     8300  system
  14         3515392         4383743   424.0 MiB   8300  cache
  15         4383744        61071326   27.0 GiB    8300  userdata

root@suez:/ # cat /proc/partitions
cat /proc/partitions
major minor  #blocks  name

   7        0      81664 loop0
   7        1       1254 loop1
   7        2      10240 loop2
 179        0   30535680 mmcblk0
 179        1       3072 mmcblk0p1
 179        2       4608 mmcblk0p2
 179        3       1024 mmcblk0p3
 179        4       1024 mmcblk0p4
 179        5       1024 mmcblk0p5
 179        6       5120 mmcblk0p6
 179        7       5120 mmcblk0p7
 179        8      40448 mmcblk0p8
 179        9        512 mmcblk0p9
 179       10       8192 mmcblk0p10
 179       11      16384 mmcblk0p11
 179       12      17408 mmcblk0p12
 179       13    1653248 mmcblk0p13
 179       14     434176 mmcblk0p14
 179       15   28343791 mmcblk0p15
 179       96       4096 mmcblk0rpmb
 179       64       4096 mmcblk0boot1
 179       32       1024 mmcblk0boot0
 179       33          2 mmcblk0boot0p1
 179       34          2 mmcblk0boot0p2
 179       35        256 mmcblk0boot0p3
 179       36        747 mmcblk0boot0p4

 
 root@suez:/ # ls -l /dev/block
ls -l /dev/block
brw------- root     root       7,   0 2017-12-28 11:05 loop0
brw------- root     root       7,   1 2017-12-28 11:05 loop1
brw------- root     root       7,   2 2017-12-28 11:05 loop2
brw------- root     root       7,   3 2017-12-28 11:05 loop3
brw------- root     root       7,   4 2017-12-28 11:05 loop4
brw------- root     root       7,   5 2017-12-28 11:05 loop5
brw------- root     root       7,   6 2017-12-28 11:05 loop6
brw------- root     root       7,   7 2017-12-28 11:05 loop7
brw-rw---- root     system   179,   0 2017-12-28 11:05 mmcblk0
brw-rw---- root     system   179,  32 2017-12-28 11:05 mmcblk0boot0
brw------- root     root     179,  33 2017-12-28 11:05 mmcblk0boot0p1
brw------- root     root     179,  34 2017-12-28 11:05 mmcblk0boot0p2
brw------- root     root     179,  35 2017-12-28 11:05 mmcblk0boot0p3
brw------- root     root     179,  36 2017-12-28 11:05 mmcblk0boot0p4
brw-rw---- root     system   179,  64 2017-12-28 11:05 mmcblk0boot1
brw------- root     root     179,   1 2017-12-28 11:05 mmcblk0p1
brw------- root     root     179,  10 2017-12-28 11:05 mmcblk0p10
brw------- root     root     179,  11 2017-12-28 11:05 mmcblk0p11
brw------- root     root     179,  12 2017-12-28 11:05 mmcblk0p12
brw------- root     root     179,  13 2017-12-28 11:05 mmcblk0p13
brw------- root     root     179,  14 2017-12-28 11:05 mmcblk0p14
brw------- root     root     179,  15 2017-12-28 11:05 mmcblk0p15
brw------- root     root     179,   2 2017-12-28 11:05 mmcblk0p2
brw------- root     root     179,   3 2017-12-28 11:05 mmcblk0p3
brw------- root     root     179,   4 2017-12-28 11:05 mmcblk0p4
brw------- root     root     179,   5 2017-12-28 11:05 mmcblk0p5
brw------- root     root     179,   6 2017-12-28 11:05 mmcblk0p6
brw------- root     root     179,   7 2017-12-28 11:05 mmcblk0p7
brw------- root     root     179,   8 2017-12-28 11:05 mmcblk0p8
brw------- root     root     179,   9 2017-12-28 11:05 mmcblk0p9
brw-rw---- root     system   179,  96 2017-12-28 11:05 mmcblk0rpmb
drwxr-xr-x root     root              2017-12-28 11:05 platform
drwx------ root     root              2017-12-28 11:05 vold
brw------- root     root     254,   0 2017-12-28 11:05 zram0


root@suez:/ # ls -l /dev/block/platform/mtk-msdc.0/by-name/
ls -l /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root     root              2017-12-28 11:05 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2017-12-28 11:05 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2017-12-28 11:05 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2017-12-28 11:05 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root     root              2017-12-28 11:05 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root     root              2017-12-28 11:05 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root     root              2017-12-28 11:05 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root     root              2017-12-28 11:05 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2017-12-28 11:05 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2017-12-28 11:05 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2017-12-28 11:05 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2017-12-28 11:05 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2017-12-28 11:05 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2017-12-28 11:05 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2017-12-28 11:05 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2017-12-28 11:05 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2017-12-28 11:05 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2017-12-28 11:05 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2017-12-28 11:05 userdata -> /dev/block/mmcblk0p15

root@suez:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0

The number of cylinders for this disk is set to 3786.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p
p
Disk /dev/block/mmcblk0: 29 GB, 31268536320 bytes, 61071360 sectors
3786 cylinders, 256 heads, 63 sectors/track
Units: cylinders of 16128 * 512 = 8257536 bytes

Device             Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors
  Size Id Type
/dev/block/mmcblk0p1    0,0,2       1023,255,63          1 4294967295 4294967295 2047G ee EFI GPT
The Following User Says Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
28th December 2017, 02:49 PM |#4  
Senior Member
Flag Washington, DC
Thanks Meter: 126
 
More
Quote:
Originally Posted by bibikalka

Here is the guide to the painless root (while out of the box FireOS allows it - right now all versions up to FireOS 5.6.0.0 are rootable). The key enabler is the original post by @ztrund (link), great work blazing the trail (and motivating me to get another Fire tablet ASAP, LOL).

Given that the devices will be shipping with the (older) rootable FireOS for the next few months (but beware of the upcoming updates - see below !!!), there is a good window of opportunity to acquire a rootable Fire HD 10, and root it. As of Dec 27th 2017, there are no reports yet of non-rootable OTAs, but those OTAs will be coming soon, count on it!

The utmost goal here is to preserve the earliest FireOS version that you get, and not let it get updated by Amazon on a whim.
I am starting with a recently bought Fire HD 10 2017 (light refurb from eBay, missed the Black Friday mega sale ). I have FireOS 5.5.0.0 (earlier than 5.6.0.0!), version name 5.3.5.1 (591450020)


Part I (avoiding Amazon updating procedure upon the initial Fire setup) - this can (almost safely) be skipped today (end of Dec, 2017), since there are no reports of unrootable OTAs yet

Set up a dedicated slow router, limit upload/download speed to ~25 kbps (this is the trickiest part, I have a dedicated Tomato router which I use to control traffic)
Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
Connect Fire to your slow router
Once Fire finds Internet, it'll immediately have "Checking for updates" on the screen, this is where the slow router should kick in, and do the trick of forcing the update to give up
Wait a bit for updates, hopefully, it won't find them, if found something, do factory reset, and repeat (on my 1st try it did find the update, although, could not download it quickly enough, I did a factory reset via Pwr&Vol+ recovery mode, and tried again - the 2nd time it skipped the update due to the slowness of the connection)
Sign in to Amazon account when prompted
Once Alexa shows up, swipe down from the top, turn on Airplane mode - no more risk of updates!!!
Done

Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.
The Following User Says Thank You to Blaiser47 For This Useful Post: [ View ] Gift Blaiser47 Ad-Free
28th December 2017, 03:13 PM |#5  
Senior Member
Flag Central FL
Thanks Meter: 97
 
More
Quote:
Originally Posted by Blaiser47

Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.

Even simpler: Choose any option on that WiFi screen, press cancel, and then skip.

No offense to the OP, but given the kind of questions that get asked on these root threads, s/he probably lost half the visitors at "dedicated slow router."
The Following 2 Users Say Thank You to retyre For This Useful Post: [ View ] Gift retyre Ad-Free
28th December 2017, 05:31 PM |#6  
OP Senior Member
Thanks Meter: 677
 
More
Quote:
Originally Posted by Blaiser47

Why not just try to connect to a wifi with the wrong password, let it try, then hit back, then hit skip. Then you can get through without connecting to internet at all.

Quote:
Originally Posted by retyre

Even simpler: Choose any option on that WiFi screen, press cancel, and then skip.

No offense to the OP, but given the kind of questions that get asked on these root threads, s/he probably lost half the visitors at "dedicated slow router."

Great! Awesome tip!!! Even better than messing with the router - I've updated the post! XDA is no strangers to people with routers, especially if it involves blocking Amazon updates.
28th December 2017, 10:03 PM |#7  
Member
Thanks Meter: 4
 
More
Curious does this work for the Fire 8? If not why?
28th December 2017, 10:29 PM |#8  
OP Senior Member
Thanks Meter: 677
 
More
Quote:
Originally Posted by ginfest

Curious does this work for the Fire 8? If not why?

The key difference is that the 2017 Fire HD 10 has an 'arm64-v8a' compiled system (with 64 bits), while all the older Fires are running 'armeabi-v7a' (with 32 bits). So a 64 bit bug must have slipped in. But let's be clear, if history is any guide, an Amazon update plugging this rootable bug is imminent at this point in time. That is why I urge everybody with root to disable OTA for good by renaming /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk to *apk_

Unfortunately, all the other Fires seem to be on lock down, for now I have disabled updates on all of mine (including Fire TV 2 sticks) in case an exploit becomes available in the future.
The Following User Says Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
28th December 2017, 10:32 PM |#9  
Junior Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by bibikalka

Great! Awesome tip!!! Even better than messing with the router - I've updated the post! XDA is no strangers to people with routers, especially if it involves blocking Amazon updates.

Thanks very much for your simple approach to rooting the hd 10, starting from unboxing it, and giving step by step guide.

What apps/tweaks/settings did you do after you rooted your HD 10 that you recommend we do, you seem to have a way of writing that is concise and to the point, very much appreciated. Any other suggestions for protecting the HD 10 from Amazon OTA updates or other hazards?

Thanks again.
The Following User Says Thank You to davidinfoman For This Useful Post: [ View ] Gift davidinfoman Ad-Free
28th December 2017, 10:37 PM |#10  
encephalon9986's Avatar
Senior Member
Thanks Meter: 25
 
More
Are you saying at the beginning that 5.6.0.0 is or is not rootable?
The Following User Says Thank You to encephalon9986 For This Useful Post: [ View ] Gift encephalon9986 Ad-Free
28th December 2017, 10:42 PM |#11  
OP Senior Member
Thanks Meter: 677
 
More
Quote:
Originally Posted by encephalon9986

Are you saying at the beginning that 5.6.0.0 is or is not rootable?

It is rootable, I clarified, thanks!
The Following User Says Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes