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)
Related
So I got the Red Triangle, and I can choose reboot your kindle (which doesn't solve any problem) and Reset to Factory Defaults. Is there any way I can access my kindle folders from the computer. I have some important documents which I don't want to loose
Nope, but that won't matter, because you probably just need to reflash the system partition to fix whatever you did. What exactly did you do before this happened?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Actually I did nothing. The only thing I noticed is that it was low in space for some while. Out of sudden it froze, I closed the tablet and then that message showed. So what do you recommend? Do you have a link with the recommended step. You say I might be able to save my personal data?
I tried one time to root... half year ago. But I gave up, I had a bad tutorial... I don't think I made changes to the system.
rajavan said:
Actually I did nothing. The only thing I noticed is that it was low in space for some while. Out of sudden it froze, I closed the tablet and then that message showed. So what do you recommend? Do you have a link with the recommended step. You say I might be able to save my personal data?
I tried one time to root... half year ago. But I gave up, I had a bad tutorial... I don't think I made changes to the system.
Click to expand...
Click to collapse
A red triangle is just a soft brick. This should be a simple enough fix in regards to what can happen. A red triangle means that the Kindle is, for one reason or another, not booting into the software.
You will need to make or buy a factory fastboot cable so you can access the bootloader. This is the only thing you can do at this point. When you get that cable follow these instructions/tutorials
First you need to restore using KFHD System.img Restore Tool located http://forum.xda-developers.com/showthread.php?t=1951254 This will have you restored with root access.
That root will break when Amazon does an OTA update unless you use Kindle Fire FirstAid to "remove OTA updates." You can go ahead and use it to install Goggle Apps/ Play Store as well. Find that here http://forum.xda-developers.com/showthread.php?t=2096888
Then you can install a 2nd bootloader and TWRP if you want. http://forum.xda-developers.com/showthread.php?t=2271909 and http://forum.xda-developers.com/showthread.php?t=2128848 are both a way. One flashes and one uses ADB commands to pus/pull.
Then slap a ROM on that bad boy. Most of them are found after one of the tutorials listed. About 2/3rds down through the tutorial. http://forum.xda-developers.com/showthread.php?t=2271909
If you get stuck in TWRP without a ROM or a bootloop then use Stunts fix to get a ROM pushed onto TWRP http://forum.xda-developers.com/showthread.php?t=2459498
Here is a great help thread where the 2nd bootloader and TWRP write ups are simplified a bit. I recommend a read of that too http://forum.xda-developers.com/showthread.php?t=2347170
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Hyperiunn said:
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Click to expand...
Click to collapse
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Fastboot
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Hyperiunn said:
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Click to expand...
Click to collapse
I've been interested. Unfortunately, my mother won't let me touch her new 2013 Fire HD. Still, if you can find someone who's rooted and not bricked, maybe they could backup their boot, system, and recovery .imgs for you and post them for you. And since they're already rooted, you would be too (someone correct me if I'm wrong). If I could get a temporary root or find a way to remove root later I would back them up for you.
The system restore tool for the 2012 Fire HD flashes the boot, recovery, and system partitions. Theoretically, the same tool would work, but only if you replaced the .img files with the ones for the 2013 Fire HD.
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
There is no confirmation that a fastboot cord even works with the 2013 model nor are the stock images available yet. The 2012 KFHD and the 2013 KFHD do not use the same images.
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
Hyperiunn said:
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Click to expand...
Click to collapse
It won't work on the 2013 Kindle fire HD yet though. Since that is the topic here I guess that narrows it down to this tablet not all the others don't it.
Fastboot cable works just fine with the one I have.
Tip: When you receive your Fire 2015 tablet, don't setup WiFi if you want to install custom ROM (skip WiFi setup)
Why: They are still shipping with FireOS 5.0.1 and it will autoupdate to 5.1.1 as soon as it sees Internet connection (it doesn't ask and takes over tablet)
Why is that bad: Because it's easier to install custom ROM with 5.0 and still a pain/riskier if from 5.1.1 (as of December 2015)
Why is this method easier/safer: No need to root first, no messing with original ROM (can backup first), no need to enable Developer mode, no need to grant ADB permissions
Prerequisites:
- This method will not work if tablet has upgraded to FireOS 5.1.1 or higher, only 5.0.x works
- Need fastboot tools installed on a computer (Windows tools/drivers here if needed) or (Linux/Mac)
- Download TWRP Recovery here to same computer
- Download your new ROM/support files of choice to an external SD Card
- If on Windows, to keep things simple you might place fastboot command, Recovery image in same folder/directory
Install: Fastboot TWRP Recovery from computer, Install Custom ROM from SD Card
- When you receive Fire, don't power it on (or if you do, don't setup WiFi as it will autoupdate to 5.1.1)
- Copy your downloaded ROM image and support files to an SD card, then insert SD into tablet
- Boot tablet directly into fastboot (power button and volume up button)
- USB attach tablet to computer that has fastboot tools and TWRP recovery image
- Unlock and Boot directly into TWRP image from computer terminal or command line
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot boot TWRP_Fire_2.8.7.0_adb.img
- Takes seconds to transfer file then recovery should appear
- Optional but recommended: From TWRP, Backup Stock Amazon ROM to external SD card
- Factory Reset from TWRP Recovery
- Install ROM and support files from TWRP via external SD card
- Reboot, profit
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
xenokc said:
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
Click to expand...
Click to collapse
Did you buy it from Amazon? I just ordered mine yesterday.
stef-nix said:
Did you buy it from Amazon? I just ordered mine yesterday.
Click to expand...
Click to collapse
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
xenokc said:
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
Click to expand...
Click to collapse
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
stef-nix said:
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
Click to expand...
Click to collapse
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
xenokc said:
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
Click to expand...
Click to collapse
Gotcha. As soon as I opened it, I blocked OTA updates. Rooted/installed SuperSU, and backed up the stock ROM.
I'm currently running CM12.1 and it's working perfectly.
I did not like how it auto signed into my Amazon account once connecting to WiFi (with OTAs blocked)
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Parhelius said:
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Click to expand...
Click to collapse
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
stef-nix said:
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
Click to expand...
Click to collapse
I connected to wifi and the updates came through automatically. I hadn't read threads like this one beforehand unfortunately, so I didn't realise that would happen.
Sounds like Amazon is still shipping with 5.0.1 so this method can still apply for those who catch this thread before receiving/booting their tablet. What's nice about this method is you can backup original ROM before modding and don't need to root. Sounds like many have thrashed their tablet trying to root.
Just dont connect to wifi and your fine.
Amazon having a $40 sale, if you ordered one might not setup WiFi when first receiving - re-read first post why.
http://www.amazon.com/Fire-Display-Wi-Fi-GB-Includes/dp/B00TSUGXKE
Just ordered 3 today ... Can't wait to tinker with it.
Thanks for the heads up regarding auto-update!
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
percussionking said:
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
Click to expand...
Click to collapse
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
vn33 said:
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
Click to expand...
Click to collapse
My 4th one came from Ft. Worth. I immediately booted into recovery mode but could not boot TWRP. Obviously this turned out to be a 5.1.1 system. If this had been a 5.0.1 system, the first full boot would have been to CM rather than to stock. So if 5.1.1 is installed at the factory you can't get your TWRP on this way.
Just got mine today it had 5.0.1 creating a backup now
Hi,
where can you download twrp from their page?
I see their list of devices but none of them says fire 5th generation.
https://twrp.me/Devices/
THANK YOU!
No you get twrp from here http://forum.xda-developers.com/amazon-fire/development/wip-bootable-recovery-kffowi-ford-t3238683
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Pcprik said:
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Click to expand...
Click to collapse
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Davey126 said:
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Pcprik said:
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Click to expand...
Click to collapse
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
That's what I thought.
Thanks again for your help!
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Pcprik said:
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Click to expand...
Click to collapse
Correct. Summary here; see index for more robust coverage.
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."