Related
To Start off... This is for windows and Linux! I had a lot of trouble at first trying to root. But as soon as i stumbled upon this 1 click root and the correct adb drivers i rooted fast and easy. My kindle was running 8.4.3 for this. But several people have came to me saying it works with 8.4.6 os. So what u want is the normal usb cable and windows/linux. And download the two files at the bottom.
Before you begin, if you have Windows Vista or Windows 7 or 8, open a Command Prompt & type ‘ping 4.2.2.2‘ then press enter. If you get replies, carry on with the rest of the guide. If not, you’ll have to carry out this small fix first! Skip to the bottom where it says "Still not work? Then move onto the "How to?..."
How to?...
1. ENABLE ADB IN SETTINGS UNDER SECURITY
Step 1. Download all files provided in the post and keep kindle unplugged at all times
Step 2. To be safe uninstall any other drivers for the kindle installed on the operating system (Win.) And Reboot.
Step 3. Install the adb drivers provided in the .zip
Step 4. Unzip the bin4ry tool on ur desktop and run the .bat file for windows as admin/.sh for Linux.
Step 5. Keep kindle unplugged still... The menu u will be promoted with will ask you what is ur device type. Select normal.
Step 6. Once you selected normal and the command prompt will say plug in your device. Do it.
Step 7. It will say a bunch of stuff, once it stops spitting out lines, if your kindle isnt already. Unlock it.
Step 8. Hopefully u get a window on ur kindle asking to restore and enter ur credentials. JUST PRESS RESTORE AT THE BOTTOM.
Click to expand...
Click to collapse
IF U GET LOST... ON THE CMD JUST FOLLOW THE DIRECTIONS ON THE COMPUTER. If I helped press the like button:good:
Still not work?
Right click on My Computer/Computer (whichever you have) and choose Properties.
Go into System and this will open System properties. Once here, select ‘Advanced System Settings’.
Next choose ‘Environment Variables’ and under the ‘System Variables’ find ‘Path’.
Select ‘Path’ with your mouse and choose ‘edit’.
Scroll to the very end of the list in here. It’ll have various paths for different things, all separated by a semi-colon like this ‘;‘. Be careful not to change anything else here, simply paste in ‘;C:\Windows\System32‘. Note that there’s no space between ; and the C:\Windows\System32 and this statement isn’t case sensitive, it can be both upper and lowercase or a mix.
Click OK & repeat until you’ve closed System Properties.
Test by opening Command Prompt (Start > Run > cmd OK, Win-key + R > cmd OK, or however you prefer to get there) & ping 4.2.2.2 again. If you see replies, congratz, you’re all set!
Click to expand...
Click to collapse
Kindle Fire HD 8.9 ADB drivers.zip
Bin4ry Root v30
Reserved :highfive:
2nd bootloader and TWRP for 8.4.3
Brandonrz said:
To Start off... This is for windows and Linux! I had a lot of trouble at first trying to root. But as soon as i stumbled upon this 1 click root and the correct adb drivers i rooted fast and easy. My kindle was running 8.4.3 for this. So what u want is the normal usb cable and windows/linux. And download the two files at the bottom.
Before you begin, if you have Windows Vista or Windows 7, open a Command Prompt & type ‘ping 4.2.2.2‘ then press enter. If you get replies, carry on with the rest of the guide. If not, you’ll have to carry out this small fix first! Skip to the bottom where it says "Still not work? Then move onto the "How to?..."
How to?...
IF U GET LOST... ON THE CMD JUST FOLLOW THE DIRECTIONS ON THE COMPUTER. If I helped press the like button:good:
Still not work?
Kindle Fire HD 8.9 ADB drivers.zip
Bin4ry Root v30
Click to expand...
Click to collapse
Now that I'm rooted could you do a tutorial on how to add a 2nd bootloader plus TWRP using 8.4.3? It would be greatly appreciated by many of us beginners!
rebelduke said:
Now that I'm rooted could you do a tutorial on how to add a 2nd bootloader plus TWRP using 8.4.3? It would be greatly appreciated by many of us beginners!
Click to expand...
Click to collapse
I'll get on it asap, but remember that I'm playing it by ear since I just got my kindle about a week ago. Right now I'm creating a tut on how to install the play store.
Sent from my Kindle Fire 8.9 HD via T-T Hd
Unfortunately it's not working for me. My Kindle is on 8.4.3 and has ADB enabled.I've installed the ADB drivers and rebooted my Windows 7 64-bit PC. I've pinged the tablet and get a response. I run the batch file as admin and press (1). I get some messages including "connect your device". A demon gets succesfully started at 5037. But after that I see nothing... My kindle's screen is unlocked, btw.
Any ideas?
pattiman said:
Unfortunately it's not working for me. My Kindle is on 8.4.3 and has ADB enabled.I've installed the ADB drivers and rebooted my Windows 7 64-bit PC. I've pinged the tablet and get a response. I run the batch file as admin and press (1). I get some messages including "connect your device". A demon gets succesfully started at 5037. But after that I see nothing... My kindle's screen is unlocked, btw.
Any ideas?
Click to expand...
Click to collapse
Delete the bin4ry folder. And unzip it again, run option 1 while unplugged. Then plug in your kindle.
Sent from my Kindle Fire 8.9 HD via T-T Hd
I tried the older root option and that worked fine. Thanks for your effort!
pattiman said:
I tried the older root option and that worked fine. Thanks for your effort!
Click to expand...
Click to collapse
Np. Glad I could help.
Sent from my Kindle Fire 8.9 HD via T-T Hd
pattiman said:
I tried the older root option and that worked fine. Thanks for your effort!
Click to expand...
Click to collapse
What does this mean? The older root option?
I am in the exact same boat. I can ping the device, but when running runme.bat it just sticks at waiting for device.
I deleted and re-extracted the zip file. That did not help. I am going to go try other root options to see if I can figure out which one you did that worked.
spearoid said:
What does this mean? The older root option?
I am in the exact same boat. I can ping the device, but when running runme.bat it just sticks at waiting for device.
I deleted and re-extracted the zip file. That did not help. I am going to go try other root options to see if I can figure out which one you did that worked.
Click to expand...
Click to collapse
I was able to use the instructions in the OP to root my KFHD 8.9 on 8.4.3. The adb drivers linked to in the OP were the problem for me. I had previously installed drivers that were a different size exe (9.183 MB) that I reverted to that allowed me to connect to the Fire through adb and run the tool from the OP to root.
spearoid said:
What does this mean? The older root option?
Click to expand...
Click to collapse
I used the method from this thread: http://forum.xda-developers.com/showthread.php?t=2069117
spearoid said:
I was able to use the instructions in the OP to root my KFHD 8.9 on 8.4.3. The adb drivers linked to in the OP were the problem for me. I had previously installed drivers that were a different size exe (9.183 MB) that I reverted to that allowed me to connect to the Fire through adb and run the tool from the OP to root.
Click to expand...
Click to collapse
I'm glad I could help another root
Sent from my Kindle Fire 8.9 HD via T-T Hd
1 downgrade, 2 failed attempts, one brick and a redscreen later... I installed 2nd boot loader + twrp + cm10.1 All starting from 8.4.3 ganna post a tut soon for you guys.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Edit: Delete post, mod please.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
so i did everything step by step ,
it appeared to communicate fine and said done, however my device remains unrooted - no super user function
any ideas?
///
Update - manually installed super user app and prompt app, got it working!!
wnyzfinest said:
so i did everything step by step ,
it appeared to communicate fine and said done, however my device remains unrooted - no super user function
any ideas?
///
Update - manually installed super user app and prompt app, got it working!!
Click to expand...
Click to collapse
Glad you got it
Sent from my Amazon Kindle Fire HD using Tapatalk HD
8.4.6 Update..
Does anyone know if this root method will work for the 8.4.6 update that my Kindle just automatically upgraded to? I had it rooted before on 8.4.3 using this method.
Trying to decide if I risk it or wait till someone with a factory cable tests it first. Please let me know if it works successfully for you and I will update with my results if I get brave and try it myself...
Board373 said:
Does anyone know if this root method will work for the 8.4.6 update that my Kindle just automatically upgraded to? I had it rooted before on 8.4.3 using this method.
Trying to decide if I risk it or wait till someone with a factory cable tests it first. Please let me know if it works successfully for you and I will update with my results if I get brave and try it myself...
Click to expand...
Click to collapse
Did you have OTA updates blocked on 8.4.3? If so, by what method? I'm just asking because I'm still nervous about leaving my wifi on after rooting 8.4.3 and using the method of OTA blocking which renames the otacerts file.
sonicanomaly said:
Did you have OTA updates blocked on 8.4.3? If so, by what method? I'm just asking because I'm still nervous about leaving my wifi on after rooting 8.4.3 and using the method of OTA blocking which renames the otacerts file.
Click to expand...
Click to collapse
No I did not have OTA updates blocked and I always leave WiFi on, otherwise its a paperweight in my opinion. I hope this method will work for root with 8.4.6 but I think I will wait for someone with a factory cable to attempt first.
Board373 said:
No I did not have OTA updates blocked and I always leave WiFi on, otherwise its a paperweight in my opinion. I hope this method will work for root with 8.4.6 but I think I will wait for someone with a factory cable to attempt first.
Click to expand...
Click to collapse
Ah, I agree about that and it's why I hate being uncertain if my OTA blocking works because I'd hate to be stuck with an update that finally breaks the rooting exploit or something of that sort. That said, however, from what I've read the 8.9" Fire HD doesn't need a factory cable to enter fastboot. No confirmation on my end of that, as I've yet to need to use fastboot and thus haven't tried it.
I do know, however, that KFFirstAide's method of rooting with the latest version of the software (downloaded from here: http://forum.xda-developers.com/showthread.php?t=2096888 ) worked flawlessly on 8.4.3 for me. And those who tried the older version on 8.4.3 didn't report any bricking or anything of that sort, simply that the process completed but did not successfully root. I would assume, but certainly not guarantee or suggest to know with any certainty, that it puts the risk of bricking in the event it can't root the firmware version down to a low percentage. It may be worth attempting. But I definitely see why you're worried about it; I'd be hesitant, as well.
Good luck, and I hope someone who's had experience with 8.4.6 can come along and offer you some solid answers. I'd definitely suggest blocking OTA updates when you regain root, though. With OTA blocked, you can still manually download any updates you want (preferably after seeing whether it's capable of being re-rooted) and install them via usb, whenever you wish.
I've tried kffa and the newest binary and neither of them worked, they didn't even recognize my device was plugged in.
Thanks for helping! (That's if I get helped)
That means your drivers aren't installed or you didn't enable USB debugging... Check your kindles security settings and see if USB debugging is on, if not turn it on. Then check your device manager for a device with a yellow triangle next to it, once you see it download my drivers from my signature and extract them somewhere, right click the device with a triangle, hit update drivers then point it to where you extracted mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
I'll try your driver.
Forgot to mention, if you are on windows 8 you will have to disable driver signature enforcement first. If this applies to you then look it up on Google, I Don,t know the exact process offhand, just the gist of it.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Forgot to mention, if you are on windows 8 you will have to disable driver signature enforcement first. If this applies to you then look it up on Google, I Don,t know the exact process offhand, just the gist of it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It says that the best driver for it has already been installed and I tried uninstalling it and everything, but it doesn't seem to want to install.
stunts513 said:
Forgot to mention, if you are on windows 8 you will have to disable driver signature enforcement first. If this applies to you then look it up on Google, I Don,t know the exact process offhand, just the gist of it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok, I got it to install but they still don't reconize my device.
So now there's a android adb connection in the device manager right? I forget the exact name as I use Linux and don't have to worry about driver issues. Try this, find the folder in binaries foot where adb is, right click that folder while holding shift and hit "open new command promoted here", once that is up, type "adb devices" and see if it lists a device, its usually reports back what I think is your serial number then says device. Tell me if it says that or if there's nothing listed.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
So now there's a android adb connection in the device manager right? I forget the exact name as I use Linux and don't have to worry about driver issues. Try this, find the folder in binaries foot where adb is, right click that folder while holding shift and hit "open new command promoted here", once that is up, type "adb devices" and see if it lists a device, its usually reports back what I think is your serial number then says device. Tell me if it says that or if there's nothing listed.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
*In a shameful voice* I forgot to unzip the binary file, my file manager would run RunMe.bat without having to unzip it.
Questionar said:
I've tried kffa and the newest binary and neither of them worked, they didn't even recognize my device was plugged in.
Thanks for helping! (That's if I get helped)
Click to expand...
Click to collapse
Can I ask you something?, how you are rooting your device? You are downgrading the firmware through the KFFA? and then applying the root patch?
Sorry if this a stupid question, I'm new at this and I have lots of questions
Thanks in advance
RockD said:
Can I ask you something?, how you are rooting your device? You are downgrading the firmware through the KFFA? and then applying the root patch?
Sorry if this a stupid question, I'm new at this and I have lots of questions
Thanks in advance
Click to expand...
Click to collapse
You can root it the same way you usally do. You don't have to downgrade anything.
I'm rooting several Kindle Fire's and I've bricked 3 (of 18) and I just noticed on the last one where the commonality lies.... I used a a Downgrade Supertool and if when I ran that it got stuck in "FastBoot" and then I manually went into ADB Sideload mode and pushed the files using the SuperTool it bricked the device. But, when I connect it I can hear the chirp that it connects, but nothing shows up and it won't turn on.
They are the newest Kindle Fire 7" tablets (the ones that are in different colors). Please help! These are for a first grade classroom and I don't know how to fix them!
Danielle926 said:
I'm rooting several Kindle Fire's and I've bricked 3 (of 18) and I just noticed on the last one where the commonality lies.... I used a a Downgrade Supertool and if when I ran that it got stuck in "FastBoot" and then I manually went into ADB Sideload mode and pushed the files using the SuperTool it bricked the device. But, when I connect it I can hear the chirp that it connects, but nothing shows up and it won't turn on.
They are the newest Kindle Fire 7" tablets (the ones that are in different colors). Please help! These are for a first grade classroom and I don't know how to fix them!
Click to expand...
Click to collapse
Sounds like the wrong image may have been pushed. Recheck file identifiers and md5 checksum. Regardless, if you can't access stock recovery little can be done to revive bricked devices at present. Consider an exchange with Amazon given most/all should still be within warranty.
It was the same image I used with all the others... I just had to get to the ADB Sideload menu manually... I'm not sure what the actual difference was. I'm worried if I return three they'll be suspicious. Plus, I don't have access to the account in which they were ordered.
Danielle926 said:
It was the same image I used with all the others... I just had to get to the ADB Sideload menu manually... I'm not sure what the actual difference was. I'm worried if I return three they'll be suspicious. Plus, I don't have access to the account in which they were ordered.
Click to expand...
Click to collapse
Doesn't change the fact recovery is not possible at present. Not certain what happened; I never use automated tools for sensitive operations.
If unable to return best shelve them and hope a generic recovery method becomes available downstream.
Davey126 said:
Doesn't change the fact recovery is not possible at present. Not certain what happened; I never use automated tools for sensitive operations.
If unable to return best shelve them and hope a generic recovery method becomes available downstream.
Click to expand...
Click to collapse
Hope it's ok to piggyback on this question, since you mentioned recovery is not possible ... to be clear, I went the 5.1.4 -> 5.1.2 -> CM12.1 route, does this mean that this device can't even do the temporary TWRP boot using fastboot? (I tried and got the "unknown command" error).
If that is the case, what is the recommended way to do a full backup? I want to mess with build.prop and would like to back it up first.
blowbigchunks said:
Hope it's ok to piggyback on this question, since you mentioned recovery is not possible ... to be clear, I went the 5.1.4 -> 5.1.2 -> CM12.1 route, does this mean that this device can't even do the temporary TWRP boot using fastboot? (I tried and got the "unknown command" error).
If that is the case, what is the recommended way to do a full backup? I want to mess with build.prop and would like to back it up first.
Click to expand...
Click to collapse
Question doesn't belong in this thread but will offer a quick response; follow-ups should be posted in the Q&A section.
- you can not boot/install/use twrp or any other custom recovery
- if you can still boot CM use a well regarded backup app like Titanium
- FlashFire offers a more comprehensive backup but is unproven
- adb backup is another comprehensive solution but requires a tether
- build.prop tweaks to emulate another device are generally ineffective
- if you still want to tinker use a proper editor such as the one integrated into Kernel Adiutor (spelled correctly)
Spent past 3 hours looking at tutorials following all sorts of different guides, but I am no smarter than before. I tried the adb method, but even after finding the matching adb version adb does not list the device, neither does the phone display the popup to auth the debug. I enabled developer options and allowed usb debug already. I now have the phone in recovery, fastboot has found it, but I don't know what to do next. I simply wish to root the phone as it is now, not install a custom rom or reset it killing all files and settings, just root it as is so I can make use of some apps requiring root or adb(as during screen off something keeps killing the battery and I don't know which app it is, also want to remove some bloatware). Where do I go from here?
TampaPowers said:
Spent past 3 hours looking at tutorials following all sorts of different guides, but I am no smarter than before. I tried the adb method, but even after finding the matching adb version adb does not list the device, neither does the phone display the popup to auth the debug. I enabled developer options and allowed usb debug already. I now have the phone in recovery, fastboot has found it, but I don't know what to do next. I simply wish to root the phone as it is now, not install a custom rom or reset it killing all files and settings, just root it as is so I can make use of some apps requiring root or adb(as during screen off something keeps killing the battery and I don't know which app it is, also want to remove some bloatware). Where do I go from here?
Click to expand...
Click to collapse
Which recovery you have? TWRP?
I have not run any rom or different bootloader, because I do not want to lose all data and settings. I tried saving those using the sync manager, failed, tried using Helium, would not connect.
TampaPowers said:
I have not run any rom or different bootloader, because I do not want to lose all data and settings. I tried saving those using the sync manager, failed, tried using Helium, would not connect.
Click to expand...
Click to collapse
Without root you will have trouble with backup. You can only use google backup in settings.
So my only option would be to try my best at making backups and then... well what then, I looked at a lot of tutorials, but none of them seemed to actually be current or the links and things were broken. It's pretty frustrating from an end-user perspective to get root when all the stuff from the search engines linking to here have their links removed or information outdated.
TampaPowers said:
So my only option would be to try my best at making backups and then... well what then, I looked at a lot of tutorials, but none of them seemed to actually be current or the links and things were broken. It's pretty frustrating from an end-user perspective to get root when all the stuff from the search engines linking to here have their links removed or information outdated.
Click to expand...
Click to collapse
If you want to root your phone you'll need to unlock the bootloader (if not already done) and this will wipe your phone, there is no way around this (unless it's S-OFF)
www.htcdev.com/bootloader
Second step is to flash a custom recovery, TWRP is the preferred one
https://dl.twrp.me/m7/
Last step is to flash Supersu.zip or Magisk.zip
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
http://www.supersu.com/download
Adb and fastboot drivers: https://htcusbdriver.com/download/htc-usb-driver-v4-17-0-001
fastboot and adb: https://forum.xda-developers.com/showthread.php?t=2317790 or complete sdk tools here: https://developer.android.com/studio/#downloads
Hello,
I recently purchased a Fire 7 tablet and have a question about rooting it. Currently my tablet has the following out of the box:
- Fire 7 (9th generation)
- Build number = 0002517050244
- Fire OS = 6.3.1.2
After reading many of the posts on XDA, I am confused how to do root. Here are the following posts that talk about root for the Fire 7:
- https://forum.xda-developers.com/amazon-fire/general/fireos-6-3-1-0-amazon-fire-7-2019-t3937209
- https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
- https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
- https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
Which is the best recommended method to root? I don't think I need to install a custom ROM, unless it turns out I need to install a de-bloated stock version.
Thanks in advance!
Software method here (good up to 6.3.1.2) and most recent.
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Michajin said:
Software method here (good up to 6.3.1.2) and most recent.
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Click to expand...
Click to collapse
Thank you... that's what I figured. I'll let everyone know my results.
After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?
gil_happy said:
After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?
Click to expand...
Click to collapse
Hi, any comments on this? Since my Wifi has been disabled the entire time, I don't want to enable it until I know whether I need to disable updates. I don't know if the Fire 7 will automatically try to do an update and break root, etc. Secondly, how do I tell if I have root (keeping in mind that Wifi is still disabled)?
Thanks!
gil_happy said:
Hi, any comments on this? Since my Wifi has been disabled the entire time, I don't want to enable it until I know whether I need to disable updates. I don't know if the Fire 7 will automatically try to do an update and break root, etc. Secondly, how do I tell if I have root (keeping in mind that Wifi is still disabled)?
Thanks!
Click to expand...
Click to collapse
Did you make it through both the bootrom-step and the fastboot-step? Can you boot into TWRP? I would recommend changing to lineage if android is your flavor. You can install a root checker, but if you followed the steps, you should have magisk installed (magisk is a root manager). What exactly are you looking to do with the tablet?
gil_happy said:
After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?
Click to expand...
Click to collapse
Michajin said:
Did you make it through both the bootrom-step and the fastboot-step? Can you boot into TWRP? I would recommend changing to lineage if android is your flavor. You can install a root checker, but if you followed the steps, you should have magisk installed (magisk is a root manager). What exactly are you looking to do with the tablet?
Click to expand...
Click to collapse
Thanks so much for getting back to me. As far as making it through the bootrom-step and the fastboot-step, I think I successfully completed both steps as I can boot into TWRP (I assume booting in TWRP means successfully completing both steps?). A couple of things:
- As mentioned, I can boot into TWRP no problem. I can also see that Magisk is also installed (when I click on Magisk, it looks like it is attempting to access the Internet for updates).
- My Fire 7 currently has Fire OS = 6.3.1.2, but after what I think is the completed install, I still have not turned on the Wifi as I'm worried that something (including the OS) might auto-update and break something, e.g. root. That is why I was asking if OTA needs to be disabled?
- As far as my plans for my tablet, here is my original post (https://forum.xda-developers.com/amazon-fire/help/customize-fire-7-tablet-t4112223), but essentially we would like to use these for promotional purposes. To explain, I want to sent out a tablet to a potential client via mail, and when they power up the tablet, our logo will replace the Amazon / Fire logo (root is needed for that), then after it boots up, it boots right to a screen where there is a some type of product messaging (maybe with a graphic), and then a button that basically says 'press here to watch our video'. It really doesn't even need access to the internet.
Hopefully all of this makes sense?
gil_happy said:
Thanks so much for getting back to me. As far as making it through the bootrom-step and the fastboot-step, I think I successfully completed both steps as I can boot into TWRP (I assume booting in TWRP means successfully completing both steps?). A couple of things:
- As mentioned, I can boot into TWRP no problem. I can also see that Magisk is also installed (when I click on Magisk, it looks like it is attempting to access the Internet for updates).
- My Fire 7 currently has Fire OS = 6.3.1.2, but after what I think is the completed install, I still have not turned on the Wifi as I'm worried that something (including the OS) might auto-update and break something, e.g. root. That is why I was asking if OTA needs to be disabled?
- As far as my plans for my tablet, here is my original post (https://forum.xda-developers.com/amazon-fire/help/customize-fire-7-tablet-t4112223), but essentially we would like to use these for promotional purposes. To explain, I want to sent out a tablet to a potential client via mail, and when they power up the tablet, our logo will replace the Amazon / Fire logo (root is needed for that), then after it boots up, it boots right to a screen where there is a some type of product messaging (maybe with a graphic), and then a button that basically says 'press here to watch our video'. It really doesn't even need access to the internet.
Hopefully all of this makes sense?
Click to expand...
Click to collapse
You should be able to disable OTA with renaming this app,
/system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk
Also a package disabler will work.
I have had sucess with
adb shell
$ su
# pm disable com.amazon.device.software.ota
Or
#pm uninstall com.amazon.device.software.ota
There are a few ways...
Easy to check, do one of these OTA disables connect wifi, check for updates. If you see it downloading, turn wifi back off. If it just closes, or says error, then OTA's are disabled. You might lose root, if you take an udpate, but TWRP should be safe. Make a backup in twrp to go back to what you have now.
Michajin said:
You should be able to disable OTA with renaming this app,
/system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk
Also a package disabler will work.
I have had sucess with
adb shell
$ su
# pm disable com.amazon.device.software.ota
Or
#pm uninstall com.amazon.device.software.ota
There are a few ways...
Easy to check, do one of these OTA disables connect wifi, check for updates. If you see it downloading, turn wifi back off. If it just closes, or says error, then OTA's are disabled. You might lose root, if you take an udpate, but TWRP should be safe. Make a backup in twrp to go back to what you have now.
Click to expand...
Click to collapse
Thanks so much for this! I didn't see anything with the name *.software.ota in that directory. The closest thing I saw was com.amazon.device.sync and sync.sdk.internal. Of course now when I try to boot up my Fire after attempting to reboot it using the touch screen, now my tablet doesn't power up :-/ I was doing so many things trying to get into the shell, I don't fully know what I'm doing. However, when this happened last time, I need to open the tablet, disconnect the battery, and then do some of the shell commands.
gil_happy said:
Thanks so much for this! I didn't see anything with the name *.software.ota in that directory. The closest thing I saw was com.amazon.device.sync and sync.sdk.internal. Of course now when I try to boot up my Fire after attempting to reboot it using the touch screen, now my tablet doesn't power up :-/ I was doing so many things trying to get into the shell, I don't fully know what I'm doing. However, when this happened last time, I need to open the tablet, disconnect the battery, and then do some of the shell commands.
Click to expand...
Click to collapse
Well if you cant find the ota the re-rename method, dont rename the other ones. I have always used disable
adb pm disable com.amazon.device.software.ota
Did you make a back up prior to doing anything as i suggested? What kind of things were you doing to try to get in a shell?
"Make a backup in twrp to go back to what you have now."