I installed KingRoot through the Supertool, after downgrading from 5.3.2 . I've tried rooting maybe a dozen times, it reboots at 16% and then says root failed, no strategy now at 30%. Any Suggestions? Thanks!
FireandIce13 said:
I installed KingRoot through the Supertool, after downgrading from 5.3.2 . I've tried rooting maybe a dozen times, it reboots at 16% and then says root failed, no strategy now at 30%. Any Suggestions? Thanks!
Click to expand...
Click to collapse
- make sure WiFi is enabled during root attempts
- deregister device from Amazon, reboot, try again
- if no lucky try a different version of KingRoot. Success has been reported with 4.85, 4.92 and 4.96
- avoid 5.x series as uninstalling (required for custom rom) is problematic
http://www.apkmirror.com/apk/kingroot-studio/kingroot/
Hey guys,
Also having the same issue and have followed all of Davey's steps already. I'm generally pretty savvy (have rooted multiple other devices and done other similar processes without issues), but I've tried over and over again without fail. Definitely on 5.3.1, at my wit's end. Thanks!
EDIT: Retried over and over again with 4.96 after posting, and after 4 hours of retries, it finally worked. So I guess I still don't know why it took so long, but keep trying if you have the same issue!
nakatayuji said:
EDIT: Retried over and over again with 4.96 after posting, and after 4 hours of retries, it finally worked. So I guess I still don't know why it took so long, but keep trying if you have the same issue!
Click to expand...
Click to collapse
Thoughts:
http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70077755
desktop kingroot 3.2.0 is what works for me and you might have windows rot as that is what gave me nightmares when following these xda tutorials. with desktop you dont have to turn tablet online and risk nasty O.T.A.
if its not windows rot (no specific order but this is what got mine re-rooted ehen had trouble)
delete and reinstall king root 3.2.0 desktop (use IOBIT uninstaller since kingroot seems to stop working after re-rooting or lots failed attempts)
recovery and reflash stock rom
recovery and wipe data
recovery and wipe cache
Related
Hi Everyone:
I am attempting to root and install cm11 on my son's KFHD. I am a bit of a noob, but I have successfully rooted my nook color in the past and read MANY threads on how to root, but I'm kind of at a loss.
The problem is that I followed the thread on how to root and I had a bunch of trouble. I finally was able to get through the steps, but the command box closed before the KFHD rebooted successfully. In an attempt to "fix" it, I restored the device to factory settings. It seems to be working just fine with stock os, but there is a superuser app which has requested access to apps.
I downloaded an app from Mobile1 to check that there is root access and the app indicates that I do indeed have root access. Should I go ahead and try to install a rom?
I would like to root it because my son is using it for school and is having a hard time adjusting to the stock os. (Which I hate, too).
Thank you so much!!!!
-NDH
1. Super User is the app that lets apps have access to root. (easy way of understanding it)
2. You need to Install Twrp and 2nd bootlander before installing the rom.
go to this video and follow the directions carefully. http://www.youtube.com/watch?v=a1bLCuQN0-U
3.Go to this video to install cm 11 rom for 2012 version. http://www.youtube.com/watch?v=0ODVX_EYaVY
4. once intalled new rom go to settings-about tablet-cyanogenmod updates and then update to latest version. IMPORTANT
thank you
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
ndharvey said:
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
Click to expand...
Click to collapse
Did you flash anything before this happened?
nope
SafinWasi said:
Did you flash anything before this happened?
Click to expand...
Click to collapse
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
ndharvey said:
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
Click to expand...
Click to collapse
I would recommend you to install a custom ROM like CyanogenMod. Trust me,you'll love it. AOSP is much better than Amazon OS.
Ok, so this device came with 5.1.1 and when I plugged it in to let it charge up (even in airplane mode) it had already gotten a hold of 5.1.2.1. So yeah, it installed 5.1.2.1 and after much aggravation and research, I realized I was able to downgrade to 5.1.2 I used the files from here: http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3 to get the 5.1.2 binary file.
It did downgrade successfully to 5.1.2 because now it's telling me "Your device is running Fire OS 5.1.2, Fire OS 5.1.2 (542169020) is ready to install."
Anyway, I've installed the latest official version of Kingroot (4.92 from June 3rd-2016) and it's a no-go.
It will get to between 16%-18% and then reboot itself. Then it will get to about 19% and then Kingroot will crash.
I've tried all the tricks, unplugged my USB, rebooted a million times, installed Kingroot several times, factory reset/cache clear, tried the PC version of Kingroot, removed Kingroot from "Recents" between reboots/crashes and I end up with the same. ZERO results.
If anyone has any insight into anything I may have missed or any other ideas, I would very much appreciate it.
Thank you
tucstwo said:
Ok, so this device came with 5.1.1 and when I plugged it in to let it charge up (even in airplane mode) it had already gotten a hold of 5.1.2.1. So yeah, it installed 5.1.2.1 and after much aggravation and research, I realized I was able to downgrade to 5.1.2 I used the files from here: http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3 to get the 5.1.2 binary file.
It did downgrade successfully to 5.1.2 because now it's telling me "Your device is running Fire OS 5.1.2, Fire OS 5.1.2 (542169020) is ready to install."
Anyway, I've installed the latest official version of Kingroot (4.92 from June 3rd-2016) and it's a no-go.
It will get to between 16%-18% and then reboot itself. Then it will get to about 19% and then Kingroot will crash.
I've tried all the tricks, unplugged my USB, rebooted a million times, installed Kingroot several times, factory reset/cache clear, tried the PC version of Kingroot, removed Kingroot from "Recents" between reboots/crashes and I end up with the same. ZERO results.
If anyone has any insight into anything I may have missed or any other ideas, I would very much appreciate it.
Thank you
Click to expand...
Click to collapse
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
Ill give this a shot. Thanks!
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
You, my friend... Are. The. Man! Thank you. It did hiccup on the first try but the second one was successful and I was able to switch over to SuperSu and all is well. Thank you!
What a dumb thing to cause such an issue. I would have pulled all my hair out before trying this. Thanks again!
tucstwo said:
You, my friend... Are. The. Man! Thank you. It did hiccup on the first try but the second one was successful and I was able to switch over to SuperSu and all is well. Thank you!
What a dumb thing to cause such an issue. I would have pulled all my hair out before trying this. Thanks again!
Click to expand...
Click to collapse
Glad it worked out! If you intend to flash a custom rom (CM12, Nexus, etc.) be sure to grab the latest version of FlashFire from here (guidance/tips here). Some earlier versions were a bit shaky on this device.
Davey126 said:
Glad it worked out! If you intend to flash a custom rom (CM12, Nexus, etc.) be sure to grab the latest version of FlashFire from here (guidance/tips here). Some earlier versions were a bit shaky on this device.
Click to expand...
Click to collapse
Yeah, I'm aware of all of those things. These were actually 4 separate tablets (3 for my daughters and one for my mother) and I just wanted to remove the lock screen ads and prevent future OTAs (all of which require root) plus plop on the Play Store.
I don't think any of them care about flashing ROMs, but I hate when a system takes control over my device and prevents me doing what I want to do with it.
Again, thanks for that most obscure of solutions (on top of the other obscure prerequisites)!
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
I am having the same issue as OP. I have tried not registering with Amazon and it still isn't working for me. I am definitely on 5.1.2 and not 5.1.2.1. I have 3 of these tablets and this is the only one that I haven't been able to get it to work on. The others only took 1 or 2 tries. Anything else I could try?
Edit: Right after posting this it finally worked. If anyone else finds this thread with the same issue, I would say just keep trying. It took me probably 15-20 attempts but it eventually just worked.
Also I had trouble using the kingroot app on the tablet. If you go to the website and dl it to the pc and use kr it works every time
Sent from my SM-N910T3 using XDA-Developers mobile app
I have a Fire 7" that is mysteriously failing when trying to flash with FlashFire. My process is:
- Downgrade FireOS
- Root using KingRoot
- Install SuperSU
- Install FlashFire
I've been restoring a backup of a Fire tablet that is set up how I need to. This process has worked on several other Fire 7 tablets recently, and in general I've been able to do this on about 50 tablets. On this particular tablet, I tried flashing the restore image twice with FlashFire 0.50, once with 0.51, and then the last time I decided to directly flash the CM 12.1 and GApps instead of restoring.
Every time, FlashFire appears to quite somewhere in the middle of flashing and I get stuck in a boot loop. I can sideload the downgraded FireOS to get it running again.
So, I was curious if anyone had any ideas as to how to approach this? Hopefully this is the last of these damn things I need to do this with.
Radixdiaboli said:
I have a Fire 7" that is mysteriously failing when trying to flash with FlashFire. My process is:
- Downgrade FireOS
- Root using KingRoot
- Install SuperSU
- Install FlashFire
I've been restoring a backup of a Fire tablet that is set up how I need to. This process has worked on several other Fire 7 tablets recently, and in general I've been able to do this on about 50 tablets. On this particular tablet, I tried flashing the restore image twice with FlashFire 0.50, once with 0.51, and then the last time I decided to directly flash the CM 12.1 and GApps instead of restoring.
Every time, FlashFire appears to quite somewhere in the middle of flashing and I get stuck in a boot loop. I can sideload the downgraded FireOS to get it running again.
So, I was curious if anyone had any ideas as to how to approach this? Hopefully this is the last of these damn things I need to do this with.
Click to expand...
Click to collapse
In your shoes (and given your experience) I might try a stand alone, full-on wipe with FlashFire which, with any luck, will yield an 'empty', unbootable device. You can then reload FireOS via recovery menu and do the prep-for-custom-rom dance again. If FlashFire behaves the same way you might want to cut your losses and request an exchange from Amazon.
Davey126 said:
In your shoes (and given your experience) I might try a stand alone, full-on wipe with FlashFire which, with any luck, will yield an 'empty', unbootable device. You can then reload FireOS via recovery menu and do the prep-for-custom-rom dance again. If FlashFire behaves the same way you might want to cut your losses and request an exchange from Amazon.
Click to expand...
Click to collapse
Word, I'll give that a shot. This one is already an exchange (last batch had a lot of stuck pixels), not sure I have the mettle to go through all that again.
Davey126 said:
In your shoes (and given your experience) I might try a stand alone, full-on wipe with FlashFire which, with any luck, will yield an 'empty', unbootable device. You can then reload FireOS via recovery menu and do the prep-for-custom-rom dance again. If FlashFire behaves the same way you might want to cut your losses and request an exchange from Amazon.
Click to expand...
Click to collapse
Curious; doing a wipe (all boxes checked) with FlashFire 0.51 seems to just result in a factory reset. Blah.
Radixdiaboli said:
Curious; doing a wipe (all boxes checked) with FlashFire 0.51 seems to just result in a factory reset. Blah.
Click to expand...
Click to collapse
Suggests the system partition is not writable in the manner FlashFire uses which points to a larger issue such as an underlying permission issue. Not sure how to further diagnose/remediate.
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
you can downgrade and then you can root
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os. Is it required to side load?
Ubuntu_noobi said:
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os.
Click to expand...
Click to collapse
Wrong procedure. See forum index for details, in particular the first two posts in this thread.
Ubuntu_noobi said:
Is it required to side load?
Click to expand...
Click to collapse
Yes.
So glad I found this post. Researching the same thing. Trying it out now
Sent from my iPhone using Tapatalk
yungskeeme01 said:
So glad I found this post. Researching the same thing. Trying it out now
Click to expand...
Click to collapse
Any new info to share? I still haven't been able to figure it out
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
What exactly are you trying to "figure out"? Responded a few days ago with downgrade/rollback links which includes a step-by-step video.
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
I downgraded to 5.3.1. Rooted the fire and am now running CM 12.1. Very smooth!. Took me a awhile to get since I have a Mac but got it working. Used Rootjunky's YouTube video on how to restore. That's how I downgraded. Then used his Supertool for Mac and rooted. I then installed Flashfire and put CM12 on the tablet.
Sent from my iPhone using Tapatalk
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
Davey126 already answered it here.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
amerkiller1995 said:
I used KingRoot directly and decided not to replace it with SuperSu.
Click to expand...
Click to collapse
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
amerkiller1995 said:
Davey126 already answered it here.
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
Click to expand...
Click to collapse
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Davey126 said:
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
Click to expand...
Click to collapse
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
yungskeeme01 said:
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
amerkiller1995 said:
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
Click to expand...
Click to collapse
Sorry if I misread it. I used the version included and KingRoot so I replaced it in Supertool and re-rooted using SuperTool and it removed it no issues. Whatever though, it got rooted one way or another!
Sent from my iPhone using Tapatalk
Awesome I will try again tonight
Solved!!! Finally!!!
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
TL;DR: THERE IS NO "One click" OPTION THAT WORKS. I DOWNLOADED ALL OF THEM. IVE TRIED EVERY DAMN ONE OF THEM. STOP SEARCHING. You MUST side load the system with the code necessary to make it capable to root. Downgrading to 5.3.1 was the secret, instead of trying to root on 5.3.2. I made a glossary of the confusing terminology, made a step by step walk through for noobs
SO, having felt encouraged by the response by people on this forum, last night I decided it was worth another try.
I finally figured out what I was missing. IF YOU CURRENTLY HAVE FIREOS VERSION 5.3.1, YOU MUST ROLL IT BACK THRU SIDE LOADING see here: SIDELOAD TUTORIAL
I tried to load straight onto the system disk and caused all kinds of problems. Once I followed that step by step, which TBH, was a lot of pausing and rewinding. I am not familiar with many terms so I made this...
Android Common Terms:
Boot: A sequence of commands written into the underlying software that tells the device what order to operate in
Bootloader: See Previous (this is the sequence I referenced previously)
Locked Bootloader: Think of trying to edit a PDF you did not create... Exactly.
ADB Fastboot: THIS IS A PROGRAM... NOT A FUNCTION. I still get this confused, thinking that it is a quicker version of the boot sequence... IT IS NOT. ADB Fastboot is a program that gives access to the base software code making it reachable to use certain sections of to "edit the PDF".
Custom Recovery: It is the new version of Windows 10 you were updating to when your crappy laptop you JUST bought came with Windows 8.1. Essentially.
Root: Remember the PDF? Well, if you work somewhere that has Adobe Reader, and you see the window on the right pop up with the ability to login to Adobe Online or whatever? Well, rooting is having login credentials to ACTUALLY edit that damn PDF.
Flash: Download from the internet, and install on your hard drive, or SD Card. It actually means you erase whatever is there completely first, then install. It's two steps, which is why they don't just call it installing... I think.
Partition: Have you ever worked in an office with cubicles? Exactly. A partition is a wall that you put up to segregate files, or programs, or whatever.
SuperTool: Based in your computer. RootJunky Went through and basically made one tool that has everything you need for rooting. PROBLEM IS THAT HE TELLS YOU TO DOWNLOAD ADB FASTBOOT AND DRIVERS AND A BUNCH OF STUFF, then says, or you can just download the SuperTool, which means, I now HAVE TWO OF ALL OF IT, and then I spend the next three hours trying to figure out if its the "custom rom that I sideload into the TWRP, or if the Flashed version of the bootloader gets added to the recovery image, but not before the drivers are flashed into the fastboot."
While this doesn't cover a lot, I hope that people in this community understand what it is like for someone unversed in the lingo to grasp exactly what is going on. I don't think we should speak like idiots and elementary students, but I also think we lose a ton of people that may have something to offer one day because they got frustrated with the terminology and gave up. Luckily, I stuck it out and gave it one last chance and I got it.
So, once I downgraded from 5.3.2 to 5.3.1, I went about trying to root the device, which was also a little confusing.
Step 1: Downgrade if you have 5.3.2 to 5.3.1
Step 2: Enable ADB and Debug in the Settings
Step 3: Hold down the Power and Volume Down button, release the power button once the device starts to reboot and a menu will popup
Step 4: Use the volume keys to access the first selection. This is how you access the "sideloading".
Step 5: Open the SuperTool, click on the batch file which should say Auto... because calling it SuperTool would be confusing
Step 6: follow the super easy instructions. Honestly.
It will walk you through the process and get you to the part about Kingroot and FlashFire and eventually root the device.
I honestly hope this helps someone. God knows it would have saved me from spending approximately 30 hours trying to figure this out.
I am coming with hat in hand fully expecting to find out that there is no solution and I am out the $$$ it will cost me to replace. After having this device for close to 2 years, I decided I would root it. I have 5 other devices currently that are rooted and numerous others that I have rooted over the years (including Samsung). Admittedly, I dislike Odin and a lot of other things about rooting Samsung devices. That is part of the reason this was the only device that I ever kept unrooted for more than a month or two. I installed twrp_3.1.0-1_sm-t713_14417n with Odin with no issues. I had SuperSU 2.82 in internal. When I got into TWRP to install it, I saw nothing but directories in internal and it became clear to me that it was encrypted. Attempts to mount, wipe and even reset data all ended up with me booting back to TWRP. I'm sure frustration set in the more things I tried, but now I can't even shut the device down from TWRP or by long pressing power and volume down. Even that just goes back to TWRP. Obviously, I can't get into download mode or system. I just get the recovery booting set warranty bit: recovery message when it starts back up to TWRP. Can't say I have ever seen a device that can't even be forced to shut down, LOL. Thanks in advance if anyone can help.
*I've made some progress. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power down and volume and spam the home button until I got to the download screen. I was able to get back into Odin, but the full firmware file I tried to install errored out at the end with a rev check fail. Hopefully, it was because it thought it was downgrading, so I am downloading the newest file now. The samsung-firware.org D/L is brutally slow. Has a few more hours to go, and I am not positive if it will work yet. Cross your fingers, and throw out any ideas if you have them.
Well, it's alive. Everything is back to normal (except needing to reinstall). Time to root now, LOL!
OK, tried again and ended up restoring the full image again (minus D/L time at least). I am ready to scrap root on this device. I have tried to do everything in the [TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17 thread. https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 I would have tried installing no verify, but no matter what I do not see the SU and no verify files on the tablet either after format data without reboot or after rebooting into TWRP. After the format, it shows that data is mounted. Looking at the pictures in the thread, I think maybe it needs the work done on the external SD but the instructions say nothing about that. Time to sleep on it, and maybe someone smarter than me can think of what I might be missing and maybe better step by step instructions are available. At least it is up and running, KNOX trips be damned. I'll post to the TWRP/ROOT thread. BTW, the OS version I am running is XAR-T713XXU2BRB2_T713XAR2BRB2-20180206.
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
sliding_billy said:
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
Click to expand...
Click to collapse
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
rholm said:
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The instructions in the TWRP thread are OK, but they could be a little clearer in some places. Take a look at the interaction between ashyx and I towards the end of the TWRP thread.
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627