Related
I am thinking of rooting my daughter's fire. Before I do I would like to backup all of her app data. Is there a way to do this so I can restore all her saved games once I am finished rooting it?
Truthfully rooting is obsolete you can send twrp and fff to the kindle. Access recovery, create a backup,flash modaco straight over the stock image without wiping and its rooted with Google play and all her data still intact... Exactly what I did with my daughters..
Thepooch said:
Truthfully rooting is obsolete you can send twrp and fff to the kindle. Access recovery, create a backup,flash modaco straight over the stock image without wiping and its rooted with Google play and all her data still intact... Exactly what I did with my daughters..
Click to expand...
Click to collapse
Can I get twrp and fff from the Amazon App store?
No, but there's a small tool for installing it, check out this thread for installation guides, it's pretty simple: http://forum.xda-developers.com/showthread.php?t=1399889
After I use the tool will I be able to install custom ROMs? I would like to install either ICS or JB on her Fire.
Indirectly yes. You can use that tool to install TWRP. You can then use TWRP to backup your current system and install custom roms.
Before you get in over your head...
You seem like a pretty resonable person, so don't be naive to the complications that normally arise with those that attempt to "root/modify" their devices with the above mentioned utility. You are much better off doing a little research and trying to educate yourself in how this whole process works.
Find out what FFF is, what it does and how to use it. Find out what TWRP is, how it works and how to use it. Most of this stuff is easy to do and understand, but not if you don't know anything about it. Take a look around the forums and you'll see the large number of people who used the Kindle Fire Utility and ran into trouble with no idea of why or how to fix it. It would be beneficial and a lot less stressful for you if you had an idea of exactly what you were getting into.
At the top of this page is a sticky, titled "Before asking for troubleshooting help...". There are links in that thread, to many useful guides with a wealth of information to give you a great head start to keeping everything running smoothly. And don't be afraid to ask questions if you don't understand, just don't be ridiculous about it, because in the end, there is still no better education than experience.
I did find this thread. Is the tool basically an automated version of this?
http://forum.xda-developers.com/showthread.php?t=1638452
I am a little informed on the rooting process as I have rooted my HTC Thunderbolt. I will do a little more research before I do anything to the fire. I don't want to mess up my daughters device and have her upset with me. Are there any good JB ROMs out there for daily driver use or are the only stables one out ICS?
mlott132 said:
I did find this thread. Is the tool basically an automated version of this?
http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
Pretty much, yes.
I am a little informed on the rooting process as I have rooted my HTC Thunderbolt. I will do a little more research before I do anything to the fire. I don't want to mess up my daughters device and have her upset with me. Are there any good JB ROMs out there for daily driver use or are the only stables one out ICS?
Click to expand...
Click to collapse
The Kindle Fire is very solid so it's extremely unlikely you will do anything to permanently "brick" it. Just be sure you are extremely careful installing a custom bootloader. The latest one can be flashed in recovery very safely, so I would skip that option if you decide to use the KFU. All it would take is a slight power surge, blue screen of death or accidentally pulling the USB cable out at the wrong time, and you'll be doing THIS to fix it. Believe me, it's not fun the first time around.
As for a good daily driver...most JB and ICS ROMs are rather stable, with minor quirks here and there, but they are still better than the stock OS any day IMO.
Will I lose all the saved app data during the initial rooting process? If so, is there a way to backup this information so that I will not lose her saved games?
you dont have to root you didn``t read my post very well you only need fff and twrp if you flash modaco you will be rooted and all your daughters data will be intact but this is only the case with modaco. most people who use kfu and select install permanent root with kfu have some type of failure as of recent. failing to push su binaries, failing to push superuser apk failing drivers that cant handle the quick change of fastboot, getting stuck in fastboot and the list goes on and on...
mlott132 said:
Will I lose all the saved app data during the initial rooting process?
Click to expand...
Click to collapse
No. "Rooting" really only consists of adding two files. One that gives you actual root access (ownership) and one that keeps track of App permissions set by you.
The tricky thing is that you need temporary root access to get those files in place. This is where custom recovery comes in. Custom recoveries, like TWRP, come standard with root access, which will allow you to install and configure those two files. Custom recoveries go on their own partitions to replace their current, less effective stock counterparts, so no data capacity is lost in the process. With only those pieces of software in place, you would need to use the command line any time you want to access recovery, this is where a custom bootloader comes in. A custom bootloader will allow you to hold the power button at startup to access recovery on the fly.
The actual rooting process is unnecessary, especially if you intend to flash a custom ROM, because all custom ROMs these days are already pre-rooted. So, all you really have to do to get where you want, is get access to fastboot mode to flash a custom recovery (TWRP), push the desired ROM to your sdcard, wipe System & Factory Reset, install and reboot. The hardest part is getting the adb to work.
mlott132 said:
is there a way to backup this information so that I will not lose her saved games?
Click to expand...
Click to collapse
You can make backups of everything in recovery and transfer it all to your computer.
Thepooch said:
you dont have to root you didn``t read my post very well you only need fff and twrp if you flash modaco you will be rooted and all your daughters data will be intact but this is only the case with modaco. most people who use kfu and select install permanent root with kfu have some type of failure as of recent. failing to push su binaries, failing to push superuser apk failing drivers that cant handle the quick change of fastboot, getting stuck in fastboot and the list goes on and on...
Click to expand...
Click to collapse
Do I just sideload fff and twrp or when I flash modaco will it install these?
mlott132 said:
Do I just sideload fff and twrp or when I flash modaco will it install these?
Click to expand...
Click to collapse
Neither.
http://forum.xda-developers.com/showthread.php?p=25730650
Read through it to get a good understanding before attempting anything.
the actual act of putting twrp and fff is actually fairly straight forward the difficult thing is getting your drivers installed correctly. Rather than going first shot trying to either fastboot flash twrp and fff via command line or via kfu it is best to test your drivers to get a good idea of how they will act and if they will perform correctly. Instead of leaving your computer unable to detect the kindle in an undesirable state...
The kindle needs to enter fastboot to get at least part of the job and unfortunately with windows this sudden driver change tends to confuse it...
Side note: you go outside of modaco which you dont have to wipe when flashing to ICS or JB there will be data loss because a full wipe of everything but your sdcard contents will have to be wiped..
Well I finally pulled the trigger last night and unlocked my daughters fire. I ended up using kfu to install fff and twrp. Then flashed monaco ROM and all is well. Thanks everyone for their help in getting this done.:good:
Congrats! The modified fire is so much better than the stock.
Sent from my Amazon Kindle Fire using Tapatalk 2
Q&A for FireTV Boot Menu 1.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for FireTV Boot Menu 1.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Missed a step...
Well, as careful as I was trying to be, I managed to screw up the steps!
1) I have no way to block OTA updates via the router (I don't have access), but when I booted up the first time I was able to go into system settings and cancel the update it was downloading. Phew. Still on 51.1.0.1_user_510055620.
2) Sideload towelroot and SuperSU. Success.
4) Root and install BusyBox. Done.
3) Block OTA updates. Now I'm safe!
4) Unlock the bootloader and install CWM 6.0.5.1.4a. Version check. Verified.
5) Install 51.1.4.0_514006420 updated via CWM. Now we're making progress!
6) Install BusyBox again. I guess it wasn't included in "51.1.4.0_514006420 updated."
7) I see to update further, I need to install RBox Boot Menu, so I press forward. I was being SO careful. I verified md5sums, read back through the instructions, and tried to follow line-by-line. I finish installing RBox and reboot.
Success, I think, as RBox loads!! I watch the countdown go from 5 to 0, and then... well, nothing. It just sits there. I read back through the instructions and realize I missed one very crucial step. Yup, I missed copying the original boot.img to /system/boot/. So of course now, it just boots to RBox, but doesn't know where to go from there. And I can't do anything else about it tonight because I don't have a USB keyboard -- I did all the stuff above using ADB and recovery-input.
Sooo, I think all I have to do is hook up a USB keyboard, go into recovery (which I can't do right now with no way to select recovery in RBox), reflash "51.1.4.0_514006420 updated," and start over with the RBox install process -- this time making sure I don't miss any steps. Tomorrow I'll bring home a USB keyboard from work and hopefully have better success!
adgriffi said:
Well, as careful as I was trying to be, I managed to screw up the steps!
1) I have no way to block OTA updates via the router (I don't have access), but when I booted up the first time I was able to go into system settings and cancel the update it was downloading. Phew. Still on 51.1.0.1_user_510055620.
2) Sideload towelroot and SuperSU. Success.
4) Root and install BusyBox. Done.
3) Block OTA updates. Now I'm safe!
4) Unlock the bootloader and install CWM 6.0.5.1.4a. Version check. Verified.
5) Install 51.1.4.0_514006420 updated via CWM. Now we're making progress!
6) Install BusyBox again. I guess it wasn't included in "51.1.4.0_514006420 updated."
7) I see to update further, I need to install RBox Boot Menu, so I press forward. I was being SO careful. I verified md5sums, read back through the instructions, and tried to follow line-by-line. I finish installing RBox and reboot.
Success, I think, as RBox loads!! I watch the countdown go from 5 to 0, and then... well, nothing. It just sits there. I read back through the instructions and realize I missed one very crucial step. Yup, I missed copying the original boot.img to /system/boot/. So of course now, it just boots to RBox, but doesn't know where to go from there. And I can't do anything else about it tonight because I don't have a USB keyboard -- I did all the stuff above using ADB and recovery-input.
Sooo, I think all I have to do is hook up a USB keyboard, go into recovery (which I can't do right now with no way to select recovery in RBox), reflash "51.1.4.0_514006420 updated," and start over with the RBox install process -- this time making sure I don't miss any steps. Tomorrow I'll bring home a USB keyboard from work and hopefully have better success!
Click to expand...
Click to collapse
As long as bootmenu and recovery is working, you can just flash to 51.1.4.1 and it'll be fine.
rbox said:
As long as bootmenu and recovery is working, you can just flash to 51.1.4.1 and it'll be fine.
Click to expand...
Click to collapse
Success! Thanks for the advice about not having to start over with RBox. Hooked up the keyboard (which worked flawlessly), installed the latest pre-rooted image and I'm back up and running!
few questions
hello,
Just so I will learn few things
When I power up the machine it start by loading from /boot partition, Then it decide whether to go to /recovery or /system ?
I saw somewhere that the /boot include the kernel and that the /system the OS ?
I saw from the guide that bootmenu is copied into the /boot
and that the original /boot to /system/boot.
Why do need to save the original /boot ?
I guess that the bootmenu does not include the kernel ?
If so - the pre-rooted roms include this /system/boot ?
also - installing a stock rom will fail because it doesn't built this way or will it also overwrite the /boot ?
Sorry for asking a lot - Interested in וnderstanding.
Thank you
Fire TV Menu 1.0 Question
I have the same issue this person this person has, would appreciate any thoughts or ideas, thanks:
After installing bootmenu I get stuck at the boot screen where the count runs to 0 and am unable to choose launch recovery.
The device does boot into the kernel automatically with no issues.
For some reason my keyboard doesn’t allow me to change it to recovery and I have tried several keyboards. However, if I do ctrl-alt-del the unit reboots so it seems the keyboard commands are working. Any way to recover from this?" Have tested with both pre-rooted 51.1.40 and 51.1.41
Today I installed the app following the instructions but after a reboot it won't go past the Amazon Logo. Does anyone have any tips on how to fix it?
I don't have ADB access to the device via the network have not tried via USB
Problem downloading firetv-bootmenu-1.0.img
No matter what i do this file wont' downlaod from mediafire. Can somene PLEASE upload it to another location. It should have a mirror anyways right? I've been attempting to download it for hours.
Thanks guys
FTV now goes to Wired network on reboot
I've got 2 FTVs that I've updated to the latest CWM, Boot Menu, and pre-rooted firmware. Everything works great except on reboot, sometimes instead of joining the wireless network, the units report that they can't find the network and show that they are wired, which they are not. Forgetting the wired network solves the problem only until the next reboot. Is it possible that the latest custom rom has wired as the default instead of wireless?
Thanks for all your great work.
So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
http://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
From the OP rbox:
"Starting with 51.1.4.1, these require FireTV Boot Menu. For the time being, you must update to 51.1.4.0 before updating to 51.1.4.1. Also, if you flashed 51.1.4.0, you must flash bootmenu afterwards. If you are already on 51.1.4.0, then you just need to flash bootmenu."
stutunaru said:
So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
Click to expand...
Click to collapse
You kinda lost me there...but here's what I know
I'm almost certain its not possible for you to have boot menu and cwm without fully functional root privs
[email protected] is what it should say (does it go straight to that after inputting shell? Do you get the # sign?) That means bootloader is fully unlocked.
Supersu on aftv doesn't open and allow you to configure but it works. Not sure why but that's the way its been for a long time.
I think you're all set but sort of skimmed your post. Maybe someone else has insights.
stutunaru said:
So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
Click to expand...
Click to collapse
Sounds like you installed 51.1.4.0 AFTER installing the bootmenu. You're supposed to install 51.1.4.0 first, then the boot menu, then the latest ROM. It's a simple enough fix. Just follow the "Resetting with Recovery Mode" portion of my guide here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
AFTVnews.com said:
Sounds like you installed 51.1.4.0 AFTER installing the bootmenu. You're supposed to install 51.1.4.0 first, then the boot menu, then the latest ROM. It's a simple enough fix. Just follow the "Resetting with Recovery Mode" portion of my guide here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Click to expand...
Click to collapse
@AFTVnews.com here are two separate issues im trying to find explanation:
1. why after installing rooted 51.1.5.0 i got brisked even i was following the same guide as for 51.1.4.0. i think i haven’t missed anything in there.
2. during the recovery the only missed step was nr.2 (missed to wipe cash partition). the question is why as a result of flashing the rooted 51.1.4.0 i got the stock one? (51.1.4.0_user_514006420)?
and the bootmenu i have installed only after applied 51.1.4.0->BusyBox->bootloader.
all works as should except the towelroot and partially supersu. why partially supersu because it still does what should, grants permissions to application but i cant open it, cant remove it, cant update it.
should i go ahead and apply the last rooted release (51.1.5.0_515030720)?
KLit75 said:
You kinda lost me there...but here's what I know
I'm almost certain its not possible for you to have boot menu and cwm without fully functional root privs
[email protected] is what it should say (does it go straight to that after inputting shell? Do you get the # sign?) That means bootloader is fully unlocked.
Supersu on aftv doesn't open and allow you to configure but it works. Not sure why but that's the way its been for a long time.
I think you're all set but sort of skimmed your post. Maybe someone else has insights.
Click to expand...
Click to collapse
according to AFTVnews.com the verification of unlocked bootloader was the adb shell. right after it i get [email protected]:/ #
http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked/
cd2022 said:
http://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
From the OP rbox:
"Starting with 51.1.4.1, these require FireTV Boot Menu. For the time being, you must update to 51.1.4.0 before updating to 51.1.4.1. Also, if you flashed 51.1.4.0, you must flash bootmenu afterwards. If you are already on 51.1.4.0, then you just need to flash bootmenu."
Click to expand...
Click to collapse
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
stutunaru said:
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
Click to expand...
Click to collapse
The rbox ROMs and the stock ROMs are named identically, as far as I know. As far as I know
Towel root probably sees the preroot fw as unsupported because the same version of stock is most definetly unsupported. I never tried because I am rooted so there was never a need.
You are rooted
You have unlocked the bootloader
Supersu is working
You have cwm
When I said you lost me there...I meant from reading your op I can't see anything that indicates you screwed up. In fact, I accidentally tried to flash a stock ROM when I was going through that long process but it won't flash. Rbox designed it to fail so we won't brick. So as far as I know there is no way to be running stock with a custom recovery and to have custom recovery you must be rooted. I could be missing something but I don't see what?
Have you tried flashing a more recent update?
***but don't just try it without ensuring prerequisites are met. Like many others I do things like root and unlocknjust once. There's a definite order to this that can't be overlooked.
Just grab the seeder.apk and try to enable it.
If it enables successfully,then you have root access.
stutunaru said:
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
Click to expand...
Click to collapse
The pre-rooted ROM and the stock software update report the exact same software version number when you look in the Fire TV's about section. Saying "i got 51.1.4.0_user_514006420 which is stock ROM" is silly since the pre-rooted ROM will also say 51.1.4.0_user_514006420. Also, SuperUser not launching is a known issue. It is that way for everyone using the SuperUser app that is included in the pre-rooted ROMs.
You bricked because you either did not install the boot menu or you messed up the boot menu installation. Simple as that.
If you're running 51.1.4.0 right now, then:
Install BusyBox
CAREFULLY install the boot menu
Test that the boot menu is working by restarting your Fire TV and using the boot menu to enter recovery
Then finally, install the latest pre-rooted ROM
AFTVnews.com said:
The pre-rooted ROM and the stock software update report the exact same software version number when you look in the Fire TV's about section. Saying "i got 51.1.4.0_user_514006420 which is stock ROM" is silly since the pre-rooted ROM will also say 51.1.4.0_user_514006420. Also, SuperUser not launching is a known issue. It is that way for everyone using the SuperUser app that is included in the pre-rooted ROMs.
You bricked because you either did not install the boot menu or you messed up the boot menu installation. Simple as that.
If you're running 51.1.4.0 right now, then:
Install BusyBox
CAREFULLY install the boot menu
Test that the boot menu is working by restarting your Fire TV and using the boot menu to enter recovery
Then finally, install the latest pre-rooted ROM
Click to expand...
Click to collapse
Might be. i might've overlooked something during the process.
last night have applied the latest pre-rooted ROM and so far so good.
appreciate all your help folks.
:good::good::good:
I have not been able to update my shield tv 2015 16gb device to 5.2.
The device is rooted with latest 3.1.1 TWRP recovery. Each time I select upgrade with the stock settings it will reboot into recovery and won't update.
Does anyone have a link to the latest ROM or know where Nvidia stores the OTA file? I would rather flash the image my self if I can find get the ROM.
I'm sure this we'll help a few other people I can't be the only one with this issue. Need the 5.2 image not the 5.0.2 which is the previous version of Shield experience update.
you should not flash TWRP to your device reflash original recovery and remove su then try update again
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
.)
Click to expand...
Click to collapse
i didnt know that :good:
but if he has TWRP installed couldnt he format data pation from TWRP thus saving hours of thumb twiddling
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Click to expand...
Click to collapse
Obviously thats a much longer and worse route.
afgok said:
you should not flash TWRP to your device reflash original recovery and remove su then try update again
Click to expand...
Click to collapse
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
On another thread looks like others are having this same issue with only this version 5.2.. ill just wait for the Dev Images to show up hopefully soon.
I unrooted but still got the same issue, it wont install. But I also have another issue, i can't restore my 2015 shield 16gb by using official recovery rom and official tutorials. It consistently fails to flash system.img and vendor.img by saying that the data is too large. The only way I got my system back was by flashing this file https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062 through twrp
Diehardshorty said:
Obviously thats a much longer and worse route.
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Ichijoe said:
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Click to expand...
Click to collapse
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
If you're rooted, the right answer is to wait for Nvidia to release the 5.2 image.
If you absolutely need 5.2 right now for some reason, several people said that doing a factory restore worked. Just unrooting and restoring stock recovery won't do it, you need to do a full restore.
Diehardshorty said:
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
Click to expand...
Click to collapse
The Dev images are quite a bit different, and are also on an entirely different timeline to either the Preview, (Which I'm on), or the most current version.
But, yeah I could see how those would work. Alas mores the pitty that the rooted asspects of those Dev Images, only go as far as ADB, and not say a full /system wide root. Than again... It's probably for the best that way.
But, that doesn't really change the answer if you want / need to update (From root), than you are going to have to bite the big One, and run a Factory Reset. Which again, on the Pro, means a 2h+ reformating (zeroing out), of the /data Partition.
16gb version doesn't take as long to format but I've always remember flashing SuperSU.zip after ROM just incase. Short response for now at work.
Diehardshorty said:
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Use to be here:
/data/data/com.nvidia.ota/app_download
You obviously need root to reach that folder...
If i have time i will upload later this small OTA update to MEGA.
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
sammarbella said:
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
Click to expand...
Click to collapse
Sweet thanks I'll give that a try from the sounds of it it might not work but I'll give a shot after work. Thanks
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Diehardshorty said:
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Cameron581 said:
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Click to expand...
Click to collapse
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Diehardshorty said:
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Click to expand...
Click to collapse
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Cameron581 said:
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Click to expand...
Click to collapse
Ahhhhh that missing point for "error 7".
So the new app bypass that problem!
Thanks for posting it. :good:
My roommate gave me his Kindle 8.9 to play with and root if possible. I had been successful at rooting, flashing TWRP, but couldn't get a custom ROM to flash. Being stupid, I didn't do a test flash first, so I ended up wiping the system and storage, so I couldn't boot into anything aside from TWRP and ADB was unresponsive. It also caused a power error, causing the device to turn back on immediately when powered down.
I acquired two of these tablets from eBay, for $35.00 a Piece, in like-new condition. I replaced the one I broke and bought one for myself. The problem I had was, there is no single guide which 1) lists the current root method for this tablet 2) The files needed to flash a custom recovery once root is gained 3) the most up to date TWRP recovery available. I read a lot of stuff on XDA. I read a lot of stuff elsewhere. The root methods listed in most every thread, no longer root. It was very hard to find an updated TWRP recovery, but thanks to @ong14, who pointed me to a single post, that was possible. So, I created this guide as a single go to for the current methods to root, TWRP and install a custom ROM.
***THIS GUIDE WILL ROOT YOUR DEVICE AND INSTALL A CUSTOM RECOVERY FOR THE AMAZON HD 8.9 JEM TABLET ONLY***
This method is used with ADB which requires Windows. Please make sure the proper drivers are installed before performing these steps. Required files for rooting and custom recovery installation are available at the bottom of this post. Please see respective links for custom ROMs. I did not create any of this software or the files. I'm not responsible if your device is damaged or bricked.
1. Enable the installation of files from unknown sources in Settings > security.
2. Enable ADB debugging from Settings > device.
3. Using the Silk Browser, go to Kingroot.net and download, install and run the APK. Also from Silk, download and install Total Commander File manager and grant it root access. Once you do that, download FireFlash11.apk at the bottom of this post. Open Total Commander and navigate to /sdcard > Downloads. Install FireFlash, open it and grant it root access to use later. (You can locate FireFlash from Home > Apps.)
5. Download the rest of the files at the bottom of this post and place into a folder of your choice on your desktop. Then go here and download this file and this file and place them in that same folder. Then move the following files to your Kindle: freedom-boot-8.4.6, u-boot-prod-8.1.4, stack and kfhd8-twrp-3.0.2-2-recovery.img.
5. Please follow the steps below from @MeowDude which will tell you how to flash a custom recovery to your Kindle.
now if you moved the files straight to your kindle, then they should be on the sd card, if you downloaded these through silk, they'll be in the downloads folder in your sd card. Now open FlashFire11, and give it root access (if you haven't yet). You should be greeted with a somewhat complicated looking wall of text and checkboxes.
!IMPORTANT!
| | |
\/ \/ \/
1. So, let me now guide you through this app, first of all, there should be red print informing you that you're not on the 8.1.4 bootloader or something like that, so click on the checkbox (at the upper right. The one that says "install kfhd8uboot-prod-8.1.4.img or something like that)
2. Now go down, and you'll see some text that says "Boot Partition Image (boot.img) and a box under it that says "NOT FLASHED" tap it. it should bring up a file manager-like list. scroll down until you see your already downloaded "kfhd8freedom-boot-8.4.6.img" , and tap/select it. (I know it says 8.4.6, IT WORKS ON 8.5.1!).
now go slightly under it and check "apply stack override".
*Next, Go under that to find a line that says "Recover Partition Image (Recovery.img), and slightly under it a box that says "NOT FLASHED" tap that, and again, you'll be greeted with a list-like file manager. scroll down until you see "kfhd8-twrp-3.0.2-2-recovery.img" and tap/select it. last part! go slightly under that and tap the check box next to "disable auto recovery update".
*Now that you have all you options in order, verify that you have them in order, and correctly selected (refer back if needed) and scroll down until you see at the bottom, a box that will install/flash all these things, it will say something like "Execute Flash Script" tap it, and your all set. if you want to boot into recovery (immediately after flashing), go right under that box to find another box that says "reboot into recovery" click it, and wait a sec, your screen will black out, and you will first see the normal kindle fire logo, then a blue one, then some glitchy looking stuff, then it should show a TeamWin logo, and go into recovery.
NOTE: If you don't flash your device with android, the stock Amazon os will erase the recovery, so NEVER REBOOT INTO RECOVERY USING FIREFLASH! Only right after you install/re-install recovery.
Click to expand...
Click to collapse
You should boot back to recovery at this point and do a factory reset. Here is how to do that below:
1. Power off your Kindle.
2. Once off, press first and hold the volume down button, then the power button. Hold them both down until the device boots to the BLUE Kindle logo. Then release the power button then the volume down button.
3. You should see the "Team Win" logo come across the screen. Tap on wipe, advanced, and choose dalvik, data and cache. Ten swipe the wipe button. DO NOT SELECT THE SYSTEM OR INTERNAL STORAGE OPTION. This will do a clean install of FireOS 8.5.1 and get rid of Kingroot.
Installing a custom ROM
You can now use FireOS as you were able to before, but I was unable to get the necessary Gapps to work with each other properly. You can try, but I recommend installing a custom ROM. I've tried two so far and can confirm they both work. I will list the links below where you can get the ROMs and installation instructions.
1. The Candy Rom, based off of Lollipop 5.1.1, works on this tablet. Root is built in so you don't need to install or flash SuperSU, but the post does say you can flash it. I've had a lot of trouble with custom 5.1.1 ROMs when it comes to launchers. Be warned it doesn't play nice with Nova and will cause the SystemUI to crash and restart over and over.
2. Unofficial CyanogenMod (CM 13). I currently use this ROM. Root is also built in. I have had trouble getting used to the permissions for apps. I have to go in and set them myself. If you can't get the Google app to sign you in, go to settings > apps > Google App > permissions > grant all permissions. I cannot get Hangouts to work, but the dialer works perfect. I'm not sure if either of those issues are a fault of mine or just a fluke.
I own 3 Amazon tablets: Amazon Fire 7, rooted with a custom ROM. Amazon Fire HD 8, but unfortunately there's no root for it yet. Amazon Kindle Fire HD 8.9, rooted, custom recovery and ROM. I have had great fun 'hacking' these things. I hate FireOS, but I will give Amazon credit for making some really bad ass tablets.
I didn't really feel too happy with the CM 13 ROM. It was pretty sluggish. Just overall performance was less than it should've been. So I decided to try another CM13 (Marshmallow 6.0.1) build by Temasek . This is by far the best ROM I've ever worked with on Kindle (Sorry Fire Nexus). Performance is off the chart. There's little to no lag. You HAVE to flash SuperSu, but it works really well. You don't see the App icon, just tap settings and SuperSU is listed. You also don't need to flash Viper4Android, already comes installed. Just select it in settings, grant it root access and select yes to download the driver. It will take a minute or two for it to update, but reboot when done and configure your Viper. Just make sure you have BusyBox installed and updated. You can get it from the play store. There are more settings and customization options I can list. Truly an awesome, well built ROM.
First off, I'd like to thank you for taking the time to post your very good guide for us new guys. Another superb tutorial can be found here...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
Your and comwiz's guides that summarize MeowDude's excellent work are two of the best ones I've seen to date and they help us novices a lot.
I want to set my elderly father up with Google's new YouTube TV streaming service when I visit him after the holidays and they currently require an Android L device or better to activate the service and control their interface. All he had was a Kindle Fire HD 8.9 a relative gave him that he never uses, so he sent it to me a few days ago so I could modify it. I've read a few of your posts on this and other threads and you seem very impressed with Temasek's CM13 custom ROM, so that's good enough for me and the one I wanna try first. But I'm a little confused by your followup post when you say "you HAVE to flash SuperSu". Does this mean that one should root with that app instead of Kingroot as was described in your original guide? I'm also not totally clear on exactly where in the procedure BusyBox needs to be installed. Here's what I have done so far to date...
*performed factory reset on Kindle Fire HD 8.9 just to clean it up and get it back to stock
*installed ADB on PC and verified it communicates with the Fire HD (detects device and returns serial number)
*downloaded and installed Total Commander (nice looking file explorer at first glance, BTW)
*sideloaded Root Check and verified device is not rooted
*downloaded the following files to PC but have not yet transferred them to the Fire:
---NewKingrootV5.1.0_C176_B415_en_release_2017_05_11_20170511212237_105203.apk
---fireflash11.apk
---kfhd8-u-boot-prod-8.1.4.bin.img
---kfhd8-freedom-boot-8.4.6.img
---kfhd8-twrp-3.0.2-2-recovery.img
---stack
---SR5-SuperSU-v2.82-SR5-20171001224502.zip
---stericson.busybox.apk
---cm-13.0-20160827-V11-temasek-jem.zip
I think this is everything I need but I'm not yet comfortable enough with my current knowledge level to try rooting and flashing a custom ROM. If you or anybody else could tell me what I should do next or at least point me in the right direction that would be much appreciated. I figure it's better to ask some dumb noob questions now before I attempt anything rather than have to come back later and ask how to unbrick my tablet.
CornellEngineer said:
First off, I'd like to thank you for taking the time to post your very good guide for us new guys. Another superb tutorial can be found here...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
Your and comwiz's guides that summarize MeowDude's excellent work are two of the best ones I've seen to date and they help us novices a lot.
I want to set my elderly father up with Google's new YouTube TV streaming service when I visit him after the holidays and they currently require an Android L device or better to activate the service and control their interface. All he had was a Kindle Fire HD 8.9 a relative gave him that he never uses, so he sent it to me a few days ago so I could modify it. I've read a few of your posts on this and other threads and you seem very impressed with Temasek's CM13 custom ROM, so that's good enough for me and the one I wanna try first. But I'm a little confused by your followup post when you say "you HAVE to flash SuperSu". Does this mean that one should root with that app instead of Kingroot as was described in your original guide? I'm also not totally clear on exactly where in the procedure BusyBox needs to be installed. Here's what I have done so far to date...
*performed factory reset on Kindle Fire HD 8.9 just to clean it up and get it back to stock
*installed ADB on PC and verified it communicates with the Fire HD (detects device and returns serial number)
*downloaded and installed Total Commander (nice looking file explorer at first glance, BTW)
*sideloaded Root Check and verified device is not rooted
*downloaded the following files to PC but have not yet transferred them to the Fire:
---NewKingrootV5.1.0_C176_B415_en_release_2017_05_11_20170511212237_105203.apk
---fireflash11.apk
---kfhd8-u-boot-prod-8.1.4.bin.img
---kfhd8-freedom-boot-8.4.6.img
---kfhd8-twrp-3.0.2-2-recovery.img
---stack
---SR5-SuperSU-v2.82-SR5-20171001224502.zip
---stericson.busybox.apk
---cm-13.0-20160827-V11-temasek-jem.zip
I think this is everything I need but I'm not yet comfortable enough with my current knowledge level to try rooting and flashing a custom ROM. If you or anybody else could tell me what I should do next or at least point me in the right direction that would be much appreciated. I figure it's better to ask some dumb noob questions now before I attempt anything rather than have to come back later and ask how to unbrick my tablet.
Click to expand...
Click to collapse
"Root" is built into the ROM. But, it's not full root. So the ROM maker tells you to Flash SuperSU once the ROM is installed and functioning. You have to do that because you wipe the system (pretty much all of it) before you flash the ROM. That wipes Kingroot, root etc. until you flash the new ROM. You're on the right track exactly. Just make sure your files are placed properly and use FireFlash to install TWRP. Just follow all the steps exactly and it should be successful. The good thing about this method, it doesn't wipe your data to install the recovery.
Okay, DF...thanks. When researching Kingroot & SuperSU I came across a ton of external links about how to get rid of the former if it was used to originally root a device and replace it with the latter. I even found another XDA thread last night where you posted that you yourself spent many hours reading about how to do just that. It seemed like a lot of hoops to jump through so I thought maybe it was better just to use SuperSU to root in the first place and be done with it. But this was all probably before you tried the new ROM you're now using and are apparently liking a lot. It sounds like Temasek's ROM version automatically takes care of most/all of the Kingroot exorcism that gave you such a headache. Apparently on many devices you can install TWRP first and THEN root with SuperSU afterward but I gather the Kindle Fire's funky bootloader unfortunately doesn't permit this.
I'll just keep reading threads over and over again as well as outside reference articles on other sites like I have been so far. Some of it must be finally sinking in because some posts are actually finally starting to make a little sense and in some cases I now understand what a few folks did wrong to cause them problems. When the vast majority of the posts and articles I read make sense and not just some of them then I'll give it a shot. Appreciate the guidance.
Okie dokie, DF...just a quick status report on how we're doing following your new guide. So far, so good...used Kingroot to root the device no problem, verified it was rooted with Root Check, gave Total Commander (which I had installed a few days ago) root access, and downloaded and installed FireFlash. But when I opened the app and clicked on "allow" to have root privilege there was a minor glitch...although I could see the FireFlash menu in the background there was an error message saying it did not have root access and that it was going to close, even though Kingroot verified it as an app that had permission. Tried uninstalling and reinstalling a few times but kept getting the same error message. Finally I simply rebooted the device and it worked fine after that...so if there are any fellow noobs out there who are one step behind me (and heaven help you if you are) you might wanna try a simple reboot during this step if you experience a similar problem to see if that solves it.
Before I do anything else I'm gonna use ADB to create some images of several of the now-rooted stock partitions and save them to my PC just in case I eff something up later on. You did not mention this in your guide but this was summarized nicely by comwiz in his very similar tutorial...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
He also included many screenshots that one will see while following your guides...I found these visual aids to be very helpful in terms of what one could expect to see as you march through all the steps that you guys so graciously spent the time laying out for us newbies. I'm probably gonna hold off on installing TWRP and Temasek's custom ROM for a few days...I wanna read up more about TWRP and fastboot before I take the next baby steps. BTW, like you I just bought another used KFHD 8.9 in almost new condition on eBay today for about the same price that you paid...how's THAT for the ultimate "backup"???
Man, thank God for this XDA forum...no way I try this on my own without all the info and tools and help that experienced folks have taken the time to post here.
CornellEngineer said:
EDITED BY ME, "compjan"
Before I do anything else I'm gonna use ADB to create some images of several of the now-rooted stock partitions and save them to my PC just in case I eff something up later on.
Click to expand...
Click to collapse
PLEASE upload those images !!! if you are running 8.5.1 on a 32 gig model I NEED THEM !
compjan said:
PLEASE upload those images !!! if you are running 8.5.1 on a 32 gig model I NEED THEM !
Click to expand...
Click to collapse
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286
MeowDude said:
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286
Click to expand...
Click to collapse
iRoot doesn't work anymore. At least not when I tried. Regardless of the method used to root, the quicker to get rid of them, the better it makes me feel.
MeowDude said:
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286
Click to expand...
Click to collapse
um, i do not have a working 8.9 tablet. i screwed it up and had a red screen of death for a couple years now. i have been off work due to knee surgery and decided to see if there was a working fix. member sd_shadow has me OFF red screen, now i need to get back to stock BEFORE i start playing with it. that way i can fix it right then if i mess it up again.
SO, i need a copy of the 3 partitions to get back to stock.
UNLESS. . . . i can get the partitions out of the 8.5.1 BIN i grabbed from amazon. that is how sd_shadow ( THANK YOU SIR ! ) got me back to a NOT booting but hung at the fire logo. i flashed the bin to SYSTEM and now i need the other 2 partitions.
UPDATE: GOT IT UP AND RUNNING AS 8.1.4 ! ! !
wife wanted it stock, so i loaded the 8.5.1 update from amazon in the root directory of INTERNAL STORAGE. not i a folder. re-booted and it installed the 8.5.1 update. worked fine . . . EXCEPT . . . .
the built-in amazon app store was buggy as hell. so was the silk browser. gapps worked fine until a re-boot. then crashed as soon as i launched play store.
SO. . . . i'm backing up the 3 partitions and going to load a ROM on this puppy.
EDIT: there is a NEWER 8.5.1 "update" at amazon, it will NOT auto install via the "check for updates" button (afaik. and i tried it on 2 different 8.9's) . download it, copy it to the ROOT of the 8.9, not in a folder. reboot. it will install all by it's self. fixed all my stock problems!! END EDIT
I got CM13 installed on my 8.9 but then having issue.
a. Can't boot into custom recovery. With volume down hold + power button -> Kindle Fire orange -> Kindle Fire blue -> then it either boots back into CM13 or getting "Fast boot".
b. In CM13, i don't have root access. How so? Weird. I am always under the impression that every custom image will come with root access. I maybe wrong though.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
Well, my bad was I downloaded the wrong gapps, picked 7.1 instead of 6.0, so I wanted to boot back in recovery to install the correct gapps.
votinh said:
I got CM13 installed on my 8.9 but then having issue.
a. Can't boot into custom recovery. With volume down hold + power button -> Kindle Fire orange -> Kindle Fire blue -> then it either boots back into CM13 or getting "Fast boot".
b. In CM13, i don't have root access. How so? Weird. I am always under the impression that every custom image will come with root access. I maybe wrong though.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
Well, my bad was I downloaded the wrong gapps, picked 7.1 instead of 6.0, so I wanted to boot back in recovery to install the correct gapps.
Click to expand...
Click to collapse
If using temasek ROM, you'll have to flash SU. Use 2.7X. then update from play store. Root for regular CM is found in developer options. Settings > about device > tap build number 7 times and go back to Maine settings menu, scroll to bottom. For developer options. Enable root in that menu. Select both apps and ADB.
I am using the CM13 ROM by alexander_32, I guess the same one you're using.
Personally, it isn't as snappy as I wish but I'll give it some more time.
Also, the option to boot into recovery on the menu is so much better than using keys combination. Thumb up for that!
what is the optimal gapps to get from open gapps? there are so many options im not sure which works best on jem.
green_reaper said:
what is the optimal gapps to get from open gapps? there are so many options im not sure which works best on jem.
Click to expand...
Click to collapse
I almost always use pico gapps.
DragonFire1024 said:
I almost always use pico gapps.
Click to expand...
Click to collapse
so basically for jem im using CM13 (Marshmallow 6.0.1) build by Temasek . and for gapps should I use (platform = ARM , Android 7.0 and pico) ? or is there a better gapps build selection?
green_reaper said:
so basically for jem im using CM13 (Marshmallow 6.0.1) build by Temasek . and for gapps should I use (platform = ARM , Android 7.0 and pico) ? or is there a better gapps build selection?
Click to expand...
Click to collapse
Go to opengapps website. Always download the gapps for the corresponding Android version. Always choose ARM.