Database Develop

Unable to root Kindle Fire HD

Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie

Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.

soupmagnet said:
Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.
Click to expand...
Click to collapse
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.

noskill123 said:
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.
Click to expand...
Click to collapse
7.20 is on the 32GB that I just received today.

soupmagnet said:
Sounds like you received a defective device. Send it back..
Click to expand...
Click to collapse
yup, it's the right advice. don't try to force any root, send the device back instead and have a new try with the next one.

The root will work for both 7.2.0 and 7.2.1, barring any anomalies with your specific device. I would use the automated root found on this forum when you try rooting next time, since it'll eliminate any possible mistakes (not saying you made any). Either way, everyone else is definitely right in saying you got a defective device. Luckily, Amazon's pretty good about replacements when you're under warranty. My own device's CPU was running so hot, it smelled like things were melting. Got it replaced with no fuss, and no extra charges.

noskill123 said:
Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie
Click to expand...
Click to collapse
That’s exactly what happen to me about 10 days ago my KFHD
Get hot and speed is unbelievable slow down but I do manage to reset to factory setting
http://forum.xda-developers.com/showthread.php?p=32866304#post32866304
But finally I manage to root my KFHD and switch off upgrade option because I don’t want
The same problem occurs to me again.
My mistake at the first time is I mix up the method using manually method by reverendkjr
And on half way using script giving by sparkym3, so on the second attempt I only use
manually method by reverendkjr doing exactly what he is done and I get my KFHD rooted
I hope this will help you
NB
Even I uncheck automatic update they still updated my KFHD now I am with 7.21
and became unroot yes will start allover again.:fingers-crossed:

[Q] Just asking for general advice after rooting

Dear members of XDA Forums:
So, a few days ago I decided to purchase an e-reader, because there are a lot of books in their original language that are almost impossible to get here in Argentina in physical format. I looked in a few stores, and the Kindle Fire HD 7 seemed fine. It had android, wifi, and some cool random stuff. Well, I purchased it, and was really glad after realizing that what I had in my hands could be turned into a fully functional (and pretty powerful) tablet, not just a reader. So I rooted it, installed a custom launcher, that kind of stuff, and everything went well.
I've been trying to investigate even further, but there are a few particular points to which I found no answer on the forums:
- Currently I'm using the latest version of the firmware (I think it was 7.4.1), and it seems pretty obvious after a quick look at the forums that no wallpaper can be set in that version because Amazon disabled them with a switch in the framework or something like that, and it can only be accesed by decompiling or using the custom script created by mr. stunts513; both of which seem too dangerous for me at this moment (I have absolutely no way of getting a factory cable if something goes wrong, and this thing was worth 2/5 of my monthly salary...)
Was there any update regarding this, or it remains in the same situation?
- At some point before rooting, I'm sure I updated my Kindle. But I've only had it for a few days, so a data wipe doesn't scare me yet. What will happen if I do a total factory restore? I mean, without using any app, just hitting the button in the settings menu. I guess it will unroot and all my apps and personal stuff will be erased, but what about the firmware? Will it remain in the latest I had before restoring (7.4.1) or will it go back to the one it had when I took it from the box?
- I've read several ways to block OTA updates, but there seem to be mixed sollutions for the K7 and the K8'9 in the same threads. Regarding my 7, I only changed the name of the .zip file that controls it (can't remember it's name now, it was in system/etc/security, I think). Will that be enough for a 7?
Thanks in advance, and best regards!
P.S.
Mr. stunts513, please do not take my commentary as a way to despise your work; quite the contrary, I'm grateful and would try it without a doubt if I was sure I could unbrick my Kindle if something goes wrong. But there is no way to be 100% sure, so for now I'd rather wait with a black desktop.

Ah No problem I completely understand, if you feel safe trying to install 2nd boot loader and twrp you won't need a fastboot cable if it bricks, but that has some risks of its own. Factory reset I think pretty much just wipes the data folder, maybe some of the system folder, so it doesn't restore the is to a previous version, least as far as I have ever heard. I can't really speak for everyone but I think renaming the ota certs zip file does the trick but I have heard mixed reviews on whether it does as of late or not, I'd wait for someone else to confirm that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

[Help Thread][Kindle Fire HD] 3rd Gen (2013) Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Kindle Fire HD
3rd Gen (2013)
soho/KFSOWI​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@sd_shadow
@DoLooper
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible of posting there, you may post here. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
Fire Index: Which Amazon (Kindle) Fire Do I have? There are several Amazon Fires. Be sure you know which one you have
Not compatible with 7" Kindle Fire HD - 2012 Hacks/Roms
Most supporters are found on the G+ community, along with the up to date Guides.
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
​

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Kindle Fire HD 2013[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: How do I tell if i have a Kindle Fire HD 2013?[/SIZE]Kindle Fire HD 2013 has 7in Screen, Power and volume buttons on the back, No Camera, and No HDMI output?.​
[SIZE=+1]Q2: Can the bootloader be unlocked?[/SIZE]Yes,
[UNLOCK] KFSOWI Bootloader Unlock and TWRP ​[SIZE=+1]Q3: What is a Fastboot Cable and Why Do I need One?[/SIZE]A Fastboot Cable Cable forces the Kindle Fire HD, into Fastboot Mode. See What is a Fastboot Cable? and Setting up Adb/Fastboot Tools​*​Forum Rules | New Users Guide | XDA Tour | Report Posts​A special thanks to everyone who contributed to the production of this FAQ​

Index
Basic Device Information
Codename: soho
Model #:KFSOWI
FAQs for Kindle Fire HD 2013 - Google Doc
USB Drivers
Kindle_Fire_HD_ADB_Drivers.zip
For those with Windows 8.1 or 10
Watch [Video] How to disable driver signature enforcement - Windows 8.1 & 8
or How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
and try
Open the charm bar and go into Settings and at the bottom click on Change PC Settings.
Go to the update and Recovery on left then Recovery
Advanced Startup > restart now
Choose the Troubleshoot option followed by Advanced options.
Choose Startup settings then on next screen click on ‘restart’.
Select option
Disable driver signature enforcement
Windows 8.1 will now reboot and you can go ahead and use the Kindle_Fire_HD_ADB_Drivers.zip
more here https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/all​
Official Stock Firmware
Kindle Fire HD (3rd Generation) Software Updates
Device Tools, Root/Un-root/Un-brick methods
HOW TO ROOT THE LATEST 11.4.5.5 OS USING FIREROOTER
How to Root Your KFSOWI
Unlock Bootloader
[UNLOCK] KFSOWI Bootloader Unlock and TWRP

PM Quote, with permission to share, edited for length.
DoLooper said:
...
The index points 2013 Kindle Fire HD (KFSOWI/soho) owners to the Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2 2012-2014 forums. The guides in those forums are not for the 2013 Kindle Fire HD. Because this was never clear, many people bricked their KFSOWIs. I understand the index is for XDA, but all info for rooting KFSOWI is at KFSOWI modding on G+.
Also, the device specs and descriptions for 3rd gen 2013 KFHD are incorrect. There's no camera on the KFSOWI. Amazon's product page here links to the 2012 model (idiots!), so is also linked in your post.
Amazon's correct product page is here (It's misleading though, including HDX models with camera and other features...)
Click to expand...
Click to collapse

Added @DoLooper to list of Supporters

br0adband said:
Alright, since I got the other issue of not even knowing which device I had (or thinking it was something else, basically) I've not got this Fire HD 7 2013 (no cameras, buttons on the back, etc) ready to go for Firerooter. I've installed all the necessary drivers (verified), I have a home-made fastboot cable (works fine, made it from an Atrix HD car dock that I had no further use for, used this cable with multiple devices and when I plug it into the FHD7 (powered off) it goes right into fastboot mode as expected. Using fastboot -i 0x1949 devices shows me the device number so that's a go.
I grabbed Firerooter (latest version), extracted it, put the FHD7 in fastboot mode from the cable (verified it's listed in Device Manager as Google Nexus ADB Interface), checked Task Manager to make sure no instances of adb were running since I know that can cause problems, then ran Firerooter, chose the install option, chose the 11.4.5.2 option, checked all the boxes, waited for it to download all the necessary components and then it went into what looked like the flashing process.
Firerooter is currently still showing the "We have all the necessary information..." and "Installing FireOS..." (the flashing process with the progress bar had already finished) and the FHD7 itself shows "Booted successfully!" with some info at the bottom.
It's been like this going on 35 minutes now so, I suppose after all this my one question is:
How long is this entire process supposed to take, if anyone has either an exact time or even a guesstimate 'cause it seems like it's taking a long time. I've looked at Task Manager and it shows 3 instances of adb.exe*32, a cmd.exe, a fastboot.exe*32, and a lua5.1.exe*32 - of those the only one showing any kind of activity is the lua5.1.exe*32 task which has its RAM usage jumping all over the place (the other tasks are basically static).
I'm tempted to kill everything and reboot the FHD7 to see what's going on but so far it's just sitting here and I'm still wondering how long this should possibly take overall.
Not a tough question to answer, I hope...
Click to expand...
Click to collapse
I've copied your post to [Help Thread][Kindle Fire HD - 2013] Ask Any Question, Noob Friendly

Well as an addition I waited a solid hour and nothing happened so I scrapped the whole process, deleted all the downloaded files, and shut down my laptop totally. Restarted it, did everything from scratch all over again and the entire process completed in under roughly 9 mins but the subsequent first boot took almost 12. I was tempted to give up and try things yet one more time but it eventually did boot to the setup screen as expected.
We'll see what happens...

br0adband said:
Well as an addition I waited a solid hour and nothing happened so I scrapped the whole process, deleted all the downloaded files, and shut down my laptop totally. Restarted it, did everything from scratch all over again and the entire process completed in under roughly 9 mins but the subsequent first boot took almost 12. I was tempted to give up and try things yet one more time but it eventually did boot to the setup screen as expected.
We'll see what happens...
Click to expand...
Click to collapse
Great, normally if a device doesn't boot in 10 mins, is not going to.

KFSOWI needs OS 4.5.5 for working Play Store
br0adband said:
Well as an addition I waited a solid hour and nothing happened so I scrapped the whole process, deleted all the downloaded files, and shut down my laptop totally. Restarted it, did everything from scratch all over again and the entire process completed in under roughly 9 mins but the subsequent first boot took almost 12. I was tempted to give up and try things yet one more time but it eventually did boot to the setup screen as expected.
Click to expand...
Click to collapse
If you installed OS lower than 4.5.5, Play Store won't work. Follow steps here to install 4.5.5 with Firerooter.

original question posted in another thread
br0adband said:
Ok, so I'm going to be reading quite a bit I know but what the hell, I'm just going to ask this:
I picked up a Kindle Fire HDX 7 earlier from a pawn shop. They had zero success with getting it functional even after trying to charge it for several hours using several different microUSB cables. It had to have been functional when the person that brought it in pawned it, of course, because they wouldn't have loaned any money on a dead device, so I asked them if they'd lower the price. It had been in the "clearance" case for several weeks for $20, and the Manager on duty noted the price sticker had "notes" written on it that it was dead and wouldn't charge so he said "How about $5?" and I said "SOLD!!!"
I've had several Kindles in the past few months that were "dead" but I was able to get something out of them, but when I got this HDX7 home it didn't respond as I'd hoped. I went through a few different microUSB cables till I used one that was really tight on the insertion and voila, the battery/lightning bolt appeared and I had one of those "YES!!!" moments.
Anyway, I let it charge up for a bit, it had the previous owner's PIN in place so once I got to 35% on the battery I did the reset. Right now it's just sitting here charging while I do research on what to do with it at this point. Here are the known facts:
- Device info is a Kindle Fire HDX 7 with 16GB
- Wi-Fi is OFF and will stay off until I decide on how to proceed
- System version shows as 11.3.2.5_user_325001620 Build date Tuesday August 5, 2014
- it's in great condition but it has a lot of cosmetic damage to the rubberized coating on the back and edges, the display glass is crystal clear and without damage of any kind
Ok, so, having said that, here's the magic question:
I'd like to get rid of the stock OS for obvious reasons (it's crap as we all know) and get CM on here but I haven't decided which version as of yet, as I said I'm doing a lot of reading tonight into what I can do with this.
Also, can anyone explain briefly what the version system seems to mean as I see almost nothing related to 11.3.2.5 but I see a ton of info about 13.3.2.5 - what the hell is the difference there 'cause I can't seem to decode the versioning numbers and what they relate to on this device, unfortunately.
If I can unlock the bootloader obviously I'd like to get that done first and foremost because it should allow me to do anything I want but I do know that there's a lot of risk with these devices because of Amazon being you-know-whats, so maybe the bootloader is or will be left alone as long as I'm capable of getting CM on here. I really do like Android 4.4.4 for a variety of reasons so, whichever CM that is - CM11 I believe - may be just what I want but I'm not opposed to checking out CM12 for Lollipop I suppose.
I'll hold off doing anything including turning on Wi-Fi for a while in the hopes that someone can answer and set me on the right course of action so thanks for any responses.
Have fun, always...
Click to expand...
Click to collapse

DoLooper said:
If you installed OS lower than 4.5.5, Play Store won't work. Follow steps here to install 4.5.5 with Firerooter.
Click to expand...
Click to collapse
as originally posted: System version shows as 11.3.2.5_user_325001620 Build date Tuesday August 5, 2014

Right. I was addressing OS Firerooter would have installed. (This post, when he was having problem, says he chose OS 4.5.2. I presume that's what he ended up with.)

Well yes, I ended up using 4.5.2 because that's what Firerooter will download natively, but of course that's not the latest and yes I know about that other link to use the same process (with 4.5.5) and then alter the filename to 11.4.5.2 and Firerooter will go from there. I did notice that on 4.5.2 I was able to sign into my Google account but the Play Market was somewhat half working, reboots didn't change anything, etc. So now I'm aware of the issue with 4.5.2.
The issue now is that when I try to do the whole process again with the actual 4.5.5 bin file renamed to 4.5.2 is that it just kinda gets to a point where it never finishes. This 4th attempt I'm working on now has been going for 25 mins and it's just not happening. If I do the "scrap everything start clean" and download everything a second time including 4.5.5 and rename that to 11.4.5.2.bin and use it as required it still just gets to a point where it hangs.
Not exactly sure what the hell is going on so I'm going to scrap it one last time and give the 4.5.5 install one last attempt, if that fails then I'll just take a break and wait while doing some more research.
Thanks for the responses.
EDIT:
Well I got impatient and did the scrap everything and it still got stuck. So I mentally retraced my steps from when it was successful for the 4.5.2 clean one (meaning Fireroot downloaded that directly and not me using 4.5.5 renamed) and realized that I did a reboot of the laptop beforehand. It figures that since I missed it I'll reboot the laptop and make that final attempt to do the 4.5.5 renamed to 4.5.2 install and sure enough it worked. Not sure what's going on because I did verify nothing was running, not adb, not fastboot, etc, nothing related to the device itself.
I can't say why it worked after I did a laptop reboot but it did so, right now it's up and running, shows 4.5.5 under System Updates, has Xposed active and the modules working, Superuser works fine, and so on and so forth. Odd, but that's how it goes sometimes.

_RumRunner_ said:
Need Help stopping my Kindle Fire SOHO 2013 3rd Gen from constantly downloading the 11.4.5.4 FireOS Update.
If I use 11.3.2.5 FireOS, it will not try to download any updates ... XPosed Modules actually work. However using the 11.4.5.2 FireOS, It still downloads the 11.4.5.4 Update with the XPosed Modules activated that are supposed to block these updates.
I'm curious if there is a way to stop this from downloading this everytime I turn the Kindle on? Thankfully it does not let it Install, however when I'm around poor wifi, the download of this unneeded update really hampers my bandwidth.
Is there any updated XPosed Framework or Modules that will prevent this?
-Or-
Is there any specific file that can be altered or deleted to prevent this?
Thank You!
Click to expand...
Click to collapse
copied from other thread
Sent from my KFFOWI using Tapatalk

_RumRunner_ said:
Is there any updated XPosed Framework or Modules that will prevent this?
-Or-
Is there any specific file that can be altered or deleted to prevent this?
Click to expand...
Click to collapse
Rename extension of /system/priv-app/DeviceSoftwareOTA.apk to .apkoff

DoLooper said:
Rename extension of /system/priv-app/DeviceSoftwareOTA.apk to .apkoff
Click to expand...
Click to collapse
Thank You so much!!!
Dern thing has been driving me nuts for the past 3 weeks LOL.

Since I'm on a roll these days I might as well as the most obvious question 'cause in all the reading I've done so far I still can't seem to get a grip on this one aspect:
Can the Soho make use of custom ROMs? Everything I see with respect to the 2nd bootloader setup is related to the Tate, not the Soho, so before I go any further with this experimentation I need to figure that one out for sure since I'd prefer not to hose this device now that it's working. I can't stand Amazon's OS, that much is obvious so, if it's possible to get CM11 or CM12 on here I would like to know - I'm not asking for a step by step, that much I can figure out for myself as time passes with the info in this forum obviously, I'm just asking IF it's possible to get CM11 or CM12 on it because as I noted all the info seems to be about the Tate variant and I have the Soho (confirmed multiple times so far, and I just backed up all the partitions on the device and the shell prompt shows [email protected] so that's confirmed).
I love XDA, I really do, but sometimes even for a relatively experienced person like myself (been flashing devices for 15+ years now, hundreds of 'em) sometimes the treasure trove of info becomes an "overload" of sorts and makes it difficult to actually find that one little tidbit of info that someone is looking for. I hate asking for help, I really do, I find that I'm usually the one providing it, but in this situation I figured there are people vastly more experienced with these Kindles (which I don't particularly like to be honest, I prefer B&N Nook hardware but they're basically dead nowadays since B&N uses Samsung tablet hardware now) so for once I decided to just ask.
Thanks again for any responses...

br0adband said:
Since I'm on a roll these days I might as well as the most obvious question 'cause in all the reading I've done so far I still can't seem to get a grip on this one aspect:
Can the Soho make use of custom ROMs? Everything I see with respect to the 2nd bootloader setup is related to the Tate, not the Soho, so before I go any further with this experimentation I need to figure that one out for sure since I'd prefer not to hose this device now that it's working. I can't stand Amazon's OS, that much is obvious so, if it's possible to get CM11 or CM12 on here I would like to know - I'm not asking for a step by step, that much I can figure out for myself as time passes with the info in this forum obviously, I'm just asking IF it's possible to get CM11 or CM12 on it because as I noted all the info seems to be about the Tate variant and I have the Soho (confirmed multiple times so far, and I just backed up all the partitions on the device and the shell prompt shows [email protected] so that's confirmed).
I love XDA, I really do, but sometimes even for a relatively experienced person like myself (been flashing devices for 15+ years now, hundreds of 'em) sometimes the treasure trove of info becomes an "overload" of sorts and makes it difficult to actually find that one little tidbit of info that someone is looking for. I hate asking for help, I really do, I find that I'm usually the one providing it, but in this situation I figured there are people vastly more experienced with these Kindles (which I don't particularly like to be honest, I prefer B&N Nook hardware but they're basically dead nowadays since B&N uses Samsung tablet hardware now) so for once I decided to just ask.
Thanks again for any responses...
Click to expand...
Click to collapse
no custom recoveries, no custom roms

see https://docs.google.com/document/d/1flhQjVTm_NBfCuu1xNATpx4eSSwpYMhqETftnMHTlrQ/edit?hl=en&forcehl=1

Ah well, was fun while it lasted. Guess I'll toss it up on craigslist today and see who might bite on it. Considering I paid $5 for it I'm guessing a profit is definitely in sight.
Thanks for your assistance, sd_shadow.

From Nook to Kindle, needing a little help.

Hello all, I appreciate any help you could give me.
I just recently bought a Kindle Fire (2015) with the intention of rooting it out, and throwing CyanogenMod on there, but I'm having trouble finding solid, step-by-step instructions. I'm not entirely unfamiliar with the process in general, I currently own a Nook Color that I did the same thing with. Originally my Nook was running off an SD card that had CM on it as part of a bootable SD card, but after a while I had decided to just skip the extra step, free up a little bit of space on the card, and throw it natively onto the Nook.
However, time has not been kind to my poor Color and with the 5th Gen Kindle being almost comically cheap, (I got it during a recent sale for less than 40 bucks after shipping) and way more powerful than my poor Nook it looked like it was time to retire my beloved tablet.
I've got a passing familiarity with how ADB works, and I've used some of the tools for college work. I've rummaged through CM's wiki on the unofficial release for the system, but honestly the thread on here for the process is not very concise. It gives leaps of steps, rather than an Idiot Proof methodology and I'd really rather not brick out the tablet no matter how cheap it cost.
Alternatively! I really only used my Nook for book reading, I just didn't like the limited functionality that it offered originally, is there any suggestions on other possible ROMs that would offer a bit more functionality without the somewhat unnecessary power that CM offers?
I appreciate, greatly, any guidance that you all could offer me. :highfive:

First step, turn off the wifi, then go into settings, Device Options, System Updates and see what Fire OS it says you are running.
If as I suspect it's 5.1.1 then you can't root or install any roms atm.

Pond-life said:
First step, turn off the wifi, then go into settings, Device Options, System Updates and see what Fire OS it says you are running.
If as I suspect it's 5.1.1 then you can't root or install any roms atm.
Click to expand...
Click to collapse
Most likely it is, but just out of curiosity, I don't currently have anything on it, so if I were to set it back to factory defaults would it still keep the 5.1.1, or since when I got it it updated (Which is why I think it does have the 5.1.1 as you said) would it bounce back to the previous version?
If it does bounce back, any suggestions on where to go to try and proceed with the rooting?

Vez'Roth said:
so if I were to set it back to factory defaults would it still keep the 5.1.1
Click to expand...
Click to collapse
Yep, once the fire updates itself, you're stuck with it. And don't try to manually side load 5.0.1, results in a brick.
No root is available for 5.1.1. No custom ROMs. Only thing you can currently do on 5.1.1 is install google play store.

Vez'Roth said:
Most likely it is, but just out of curiosity, I don't currently have anything on it, so if I were to set it back to factory defaults would it still keep the 5.1.1, or since when I got it it updated (Which is why I think it does have the 5.1.1 as you said) would it bounce back to the previous version?
If it does bounce back, any suggestions on where to go to try and proceed with the rooting?
Click to expand...
Click to collapse
Nope factory defaults doesn't affect the system only personal files, it would be on a clean 5.1.1 which it already is.
And trying to revert from 5.1.1 to the old 5.0.1 bricks the tablet.
So if it is on that, your quest to apply a different rom of any kind is thwarted for now.

Pond-life said:
Nope factory defaults doesn't affect the system only personal files, it would be on a clean 5.1.1 which it already is.
And trying to revert from 5.1.1 to the old 5.0.1 bricks the tablet.
So if it is on that, your quest to apply a different rom of any kind is thwarted for now.
Click to expand...
Click to collapse
Thank you for responding at least. I will remain thwarted, but I am sure that this will not stop you all, or me, for long. It'll be broken open again. I don't know why these companies are so against it.

Vez'Roth said:
Thank you for responding at least. I will remain thwarted, but I am sure that this will not stop you all, or me, for long. It'll be broken open again. I don't know why these companies are so against it.
Click to expand...
Click to collapse
Because they're EVILLLLL!
[emoji49] [emoji35] [emoji48]
[emoji83]
lol

Tab a (2017) force oem unlock

I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build

B1G7r33! said:
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
Click to expand...
Click to collapse
What's the REAL difference between what you did today and what we did days ago.? Is the same thing we came up with 3 days ago.. Just your version of the same thing..

Three days ago?

This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.

B1G7r33! said:
Three days ago?
Click to expand...
Click to collapse
actually starting on 14th November 2018, 07:17 PM and ending about 4 days ago.. with ptballers solution.
post 118 was the beginnings of it on the thread: https://forum.xda-developers.com/ga...10-02-2018-t3747564/post78159074#post78159074
but even THAT came from earlier works that weren't detailed enough and reconstructed.
the builds seem to be way different here in the solution, i had luck with what we came up with but have only done that once so far.
I am using build NMF26X.T380DXU1ARB3 myself, what about you?
we need to figure out what ptballer is using and everyone else too as we confirm stuff so we know what to do with tablets based upon builds.
seems there is no single solution yet, and that's what we really need too keep confusion cut down to a minimum.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Evul1 said:
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
Click to expand...
Click to collapse
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.

Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33

capriorn1971ad said:
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Click to expand...
Click to collapse
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3

Evul1 said:
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Click to expand...
Click to collapse
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.

B1G7r33! said:
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
Click to expand...
Click to collapse
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..

capriorn1971ad said:
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
Click to expand...
Click to collapse
It shouldn't be that much work at all if your method to get OEM Unlock to display actually works, as your bootloader will then be unlocked and you can immediately re-root, re-flash TWRP, and restore a nandroid backup. Rooting this tablet [flashing TWRP and su and/or magisk and/or a nandroid image] is actually quite simple and can be done in 5 minutes once you have OEM Unlock displayed.
You certainly wouldn't need a whole day just to try this. But I understand. Samsung's security nonsense makes the initial root of this tablet rather fragile if you don't know all the potential roadblocks beforehand. And a comprehensive root guide that explains all of this would certainly help people looking to root this tablet, so I don't want to rush you.

capriorn1971ad said:
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
Click to expand...
Click to collapse
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?

B1G7r33! said:
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
Click to expand...
Click to collapse
don't think we can really.
trial and error..
thought i was on the right path earlier, but if it didn't work for you then it isn't the solution, cause the solution will work for everyone.
has to be some small thing were overlooking i would assume.
I worked for Metricom through Verso Technologies back in the late 90's, the first coast to coast wireless provider, had dealings with the big wigs and all, but they always opted for less security and more accessibility in most everything pertaining to networking, always afraid to give up backdoors.
i need to go back to what you said too and see what slight differences there are, did you have any luck this time around? was it repeatable?
sucks to know i am going to have to root to cause a failure to try to bypass and root again only to cause a second failure to verify, and to get it right it is going to take that really, the bypass has to be repeatable, i think setting the date back before the systems restore is key to it, but i could be wrong.
if you would lose root and be able to get it pass the first 7 days OEM unlock then your good, because even if you can't get the second, and something goes wrong to where you need it, your gonna have to wipe anyways, which means you just wipe, set date back and then do the factory reset, not being able to reboot afterwards until the OEM unlock appears and not being able to advance it through the last 7 days means little so long as the root is good and right, funny thing really, took me a while to realize that, there is no real need to rush the second 7 days, only the first 7, but it would be nice to be able to reboot it again afterwards, the same day, and not have to worry about it anymore, but like i said earlier, i got detected somehow and lost root still., wish i knew how.
that's alot of my problem though, i do things and try to document them afterwards rather than as, and i am not 20 years old anymore with a mind like a razor, it's just a serrated steak knife now at almost 50, wish i wasn't like that, because i lose bits and pieces as i go.

so if my tablet auto updates to Oreo 8.1 ... then i'm SOL huh?