Related
Ok, so this device came with 5.1.1 and when I plugged it in to let it charge up (even in airplane mode) it had already gotten a hold of 5.1.2.1. So yeah, it installed 5.1.2.1 and after much aggravation and research, I realized I was able to downgrade to 5.1.2 I used the files from here: http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3 to get the 5.1.2 binary file.
It did downgrade successfully to 5.1.2 because now it's telling me "Your device is running Fire OS 5.1.2, Fire OS 5.1.2 (542169020) is ready to install."
Anyway, I've installed the latest official version of Kingroot (4.92 from June 3rd-2016) and it's a no-go.
It will get to between 16%-18% and then reboot itself. Then it will get to about 19% and then Kingroot will crash.
I've tried all the tricks, unplugged my USB, rebooted a million times, installed Kingroot several times, factory reset/cache clear, tried the PC version of Kingroot, removed Kingroot from "Recents" between reboots/crashes and I end up with the same. ZERO results.
If anyone has any insight into anything I may have missed or any other ideas, I would very much appreciate it.
Thank you
tucstwo said:
Ok, so this device came with 5.1.1 and when I plugged it in to let it charge up (even in airplane mode) it had already gotten a hold of 5.1.2.1. So yeah, it installed 5.1.2.1 and after much aggravation and research, I realized I was able to downgrade to 5.1.2 I used the files from here: http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3 to get the 5.1.2 binary file.
It did downgrade successfully to 5.1.2 because now it's telling me "Your device is running Fire OS 5.1.2, Fire OS 5.1.2 (542169020) is ready to install."
Anyway, I've installed the latest official version of Kingroot (4.92 from June 3rd-2016) and it's a no-go.
It will get to between 16%-18% and then reboot itself. Then it will get to about 19% and then Kingroot will crash.
I've tried all the tricks, unplugged my USB, rebooted a million times, installed Kingroot several times, factory reset/cache clear, tried the PC version of Kingroot, removed Kingroot from "Recents" between reboots/crashes and I end up with the same. ZERO results.
If anyone has any insight into anything I may have missed or any other ideas, I would very much appreciate it.
Thank you
Click to expand...
Click to collapse
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
Ill give this a shot. Thanks!
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
You, my friend... Are. The. Man! Thank you. It did hiccup on the first try but the second one was successful and I was able to switch over to SuperSu and all is well. Thank you!
What a dumb thing to cause such an issue. I would have pulled all my hair out before trying this. Thanks again!
tucstwo said:
You, my friend... Are. The. Man! Thank you. It did hiccup on the first try but the second one was successful and I was able to switch over to SuperSu and all is well. Thank you!
What a dumb thing to cause such an issue. I would have pulled all my hair out before trying this. Thanks again!
Click to expand...
Click to collapse
Glad it worked out! If you intend to flash a custom rom (CM12, Nexus, etc.) be sure to grab the latest version of FlashFire from here (guidance/tips here). Some earlier versions were a bit shaky on this device.
Davey126 said:
Glad it worked out! If you intend to flash a custom rom (CM12, Nexus, etc.) be sure to grab the latest version of FlashFire from here (guidance/tips here). Some earlier versions were a bit shaky on this device.
Click to expand...
Click to collapse
Yeah, I'm aware of all of those things. These were actually 4 separate tablets (3 for my daughters and one for my mother) and I just wanted to remove the lock screen ads and prevent future OTAs (all of which require root) plus plop on the Play Store.
I don't think any of them care about flashing ROMs, but I hate when a system takes control over my device and prevents me doing what I want to do with it.
Again, thanks for that most obscure of solutions (on top of the other obscure prerequisites)!
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
I am having the same issue as OP. I have tried not registering with Amazon and it still isn't working for me. I am definitely on 5.1.2 and not 5.1.2.1. I have 3 of these tablets and this is the only one that I haven't been able to get it to work on. The others only took 1 or 2 tries. Anything else I could try?
Edit: Right after posting this it finally worked. If anyone else finds this thread with the same issue, I would say just keep trying. It took me probably 15-20 attempts but it eventually just worked.
Also I had trouble using the kingroot app on the tablet. If you go to the website and dl it to the pc and use kr it works every time
Sent from my SM-N910T3 using XDA-Developers mobile app
Hi all
I've just bought a Fire Tablet on Amazon day with the intention of rooting it and installing CM, but I am a newbie and there's so much information on here it's kind of overwhelming, and most of it has a lot of "if this, then that, or if you want to use that, do this" type guides, which for someones who doesn't really know what all the different methods and options are is really confusing!
So can someone please tell me the step by step process for doing it?
From what I've read I think I have to downgrade to 5.1.2 of the OS as I can't root on 5.1.4? Is that correct?
So do I have to root before I do that? Or do I downgrade first and then root, and then install the CM?
If someone can list each of the steps I need to take to get it from a fresh new 5th Gen Fire 7 to having all the Amazon rubbish off and having it running CM, then I can look for the guides for each step!
Thanks, I hope that makes sense!
:angel:
PS: I've already bricked one by trying to downgrade to 5.1.1 because that wasn't apparent until it was too late, replacement on its way!
Yeah, I read the same thing and I bought it on Prime day. When's the 5.14 tool going to come out? I know, beggars... I really think it's silly to have to downgrade and risk bricking it when normal root for those OS versions don't have such a concern.
Bob Boblaw said:
Hi all
I've just bought a Fire Tablet on Amazon day with the intention of rooting it and installing CM, but I am a newbie and there's so much information on here it's kind of overwhelming, and most of it has a lot of "if this, then that, or if you want to use that, do this" type guides, which for someones who doesn't really know what all the different methods and options are is really confusing!
So can someone please tell me the step by step process for doing it?
From what I've read I think I have to downgrade to 5.1.2 of the OS as I can't root on 5.1.4? Is that correct?
So do I have to root before I do that? Or do I downgrade first and then root, and then install the CM?
If someone can list each of the steps I need to take to get it from a fresh new 5th Gen Fire 7 to having all the Amazon rubbish off and having it running CM, then I can look for the guides for each step!
Thanks, I hope that makes sense!
:angel:
PS: I've already bricked one by trying to downgrade to 5.1.1 because that wasn't apparent until it was too late, replacement on its way!
Click to expand...
Click to collapse
I did the same thing, bought the tablet on prime day and was successfully able to root it and put the AOSP nexus rom
First things first make sure you have the 7-inch tablet for the following steps because apparently it only works with that specific model. Since this is my first post I can't post any links so sorry about that however, I have added the video title so that you can just google it and find the video.
Anything above fire os 5.1.2 ( that is 5.1.4, 5.1.3, 5.1.2.1) has to be downgraded to 5.1.2.
Also downgrading from 5.1.4 to 5.1.1 is going to give you a hard brick. I don't know how you didn't know that but it was clearly stated in the xda guide I was following
Basically you have to follow rootjunkys video and instead of using the file he uses in the video use the fire OS 5.1.2 file which is also available on his website.
Imortant: Do a factory reset before downgrading. I did not do that and the rooting process did not work.
Video title: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
After you have fire OS 5.1.2 follow the rooting process shown in another rootjunky video
Video title: How to root the Amazon Fire 5th gen 7in on Fire OS 5 1 2 SuperTool Mac linux and Windows
Note: He shows how to do the whole process while using mac but it can be done on windows awell and the windows files are already present. Instead of using the .sh file and opening the terminal double click the .bat file and follow along.
You can use his SuperTool to put the play store app and fire flash app.
Note: For some reason fire flash was not working properly for me by using the SuperTool, so I just installed it from the google play store.
Now you should have rooted fire OS 5.1.2 along with superSU. Now with the fire flash app and you can download any rom that you want to flash. Follow the steps in the video for instructions
Video title: Amazon Fire 5th gen AOSP Nexus rom install with Flash Fire app
Hope this helps.
All credit to rootjunky
erikthebikeman said:
Yeah, I read the same thing and I bought it on Prime day. When's the 5.14 tool going to come out? I know, beggars... I really think it's silly to have to downgrade and risk bricking it when normal root for those OS versions don't have such a concern.
Click to expand...
Click to collapse
It's not a matter of someone getting off their keister and whipping up a "tool" (presumably you are talking about root) that works with FireOS 5.1.4 or whatever the latest version is. Like many manufactures Amazon actively discourages rooting devices and attempt to block known exploits. It's a cat and mouse game. We may see a "tool" soon, much further down the road or never. Be happy you can root the device at all and be thankful for the individuals who unselfishly share their time and talents with the community.
Thanks nefarian.
The problem was that the guide I was referred to for getting CM onto it already assumed it had been rooted, and when I started googling and looking on the different guides on rootjunky there were so many coming from different angles but nothing giving the clear start to end steps for what I wanted to do, for a newbie it was very confusing. Plus in the guide I was following (a rootjunky one) he had an older version of the OS and the toolkit had different files/folders to what are in it now, so I guess at that time there was no mentioned of 5.1.4 and not being able to go back.
After thinking I needed to downgrade the OS I found the one for unbrinking and downgrading and did that fine to 5.1.2, but then when I tried the superkit it still said it was too new, so I tried to downgrade further, which is when I bricked it.
There was no mention of it on the video..... other than a bloody great overlay in the corner, which must have been added later on, and probably because I was tearing my hair out and getting confused I didn't spot it. That's my excuse anyway!
Thanks for your help, I'll have a go with the new one on Monday. So instead of trying to find an all in one guide, I need to find guide for the steps in this order;
1 - do a factory reset on the device (from the device settings, or do I need to do it in the bootloader settings?)
2 -downgrade to 5.1.2 (I should be able to do this now)
3 - root the device (and install supersu?)
4 - install CM
Then it should have full CM and none of the Amazon OS left.
I'm not missing any steps there am I?
Thanks again!
Bob Boblaw said:
Thanks nefarian.
The problem was that the guide I was referred to for getting CM onto it already assumed it had been rooted, and when I started googling and looking on the different guides on rootjunky there were so many coming from different angles but nothing giving the clear start to end steps for what I wanted to do, for a newbie it was very confusing. Plus in the guide I was following (a rootjunky one) he had an older version of the OS and the toolkit had different files/folders to what are in it now, so I guess at that time there was no mentioned of 5.1.4 and not being able to go back.
After thinking I needed to downgrade the OS I found the one for unbrinking and downgrading and did that fine to 5.1.2, but then when I tried the superkit it still said it was too new, so I tried to downgrade further, which is when I bricked it.
There was no mention of it on the video..... other than a bloody great overlay in the corner, which must have been added later on, and probably because I was tearing my hair out and getting confused I didn't spot it. That's my excuse anyway!
Thanks for your help, I'll have a go with the new one on Monday. So instead of trying to find an all in one guide, I need to find guide for the steps in this order;
1 - do a factory reset on the device (from the device settings, or do I need to do it in the bootloader settings?)
2 -downgrade to 5.1.2 (I should be able to do this now)
3 - root the device (and install supersu?)
4 - install CM
Then it should have full CM and none of the Amazon OS left.
I'm not missing any steps there am I?
Thanks again!
Click to expand...
Click to collapse
- no need for a factory reset at any point; offers no benefit for what you are trying to accomplish.
- installation of SuperSU (replacing Kinguser and related Kingroot cruft) after rooting is highly recommended prior to using FlashFire or any other tool that messes with the system partition. The SuperTool can facilitate this otherwise ugly task.
- if you are struggling with RootJunky videos you should give serious consideration to the challenges of installing a custom rom. It doesn't get any easier going forward.
Thanks. I managed to root my Nvidia Shield TV fine so I should be able to do it, I just needed to be clear of the full process from start to finish, and as I wasn't starting from the beginning of the process that made it more confusing. The rootjunky videos are great, but when someone is saying you can use this or that or do this or that it's putting choices and variables in to the mix so it's not a straighforward step by step, and when the kits and the webpages shown on the videos have changed since they were made, for someone trying to piece the info together it takes a bit more time.
Maybe I should point out that I didn't look on here initially when I started trying to do it, I basically saw the fire on offer mentioned on a forum I use and someone said yeah, it's easy to root and get CM on if, just user this video, with the link to a rootjunky YouTube video which didn't mention the prerequisite of already having downgraded the OS (why would it) so in hindsight I didn't start at the right place or have the best information.
After reading through some stuff on here (and that's over whelming for a first timer as there is so much stuff on here for many, many devices and platforms - even just finding the Amazon fire sub forum on an iPad wasn't easy!) I'm getting a better idea for attempt two.
I'll get there, and at least I know how to not brick it now! :good:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Bob Boblaw said:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (
&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Click to expand...
Click to collapse
- Kingroot/Purify, not Kingmaker/Purity
- I can't think of a better suite of guides than the videos produced by RootJunky
- use FlashFire 0.51 to install (flash) the rom of your choice
- OP for Nexus rom has video link and and basic FlashFire guidance
- get over the minor variations in the language/tools used to support this device between the making of videos and the latest release.
Bob Boblaw said:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Click to expand...
Click to collapse
1. Get the CM rom and put it in the tablet from here: http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
2. Install FlashFire 0.51 from play store or use the SuperTool
3. Follow the video instructions and instead of the nexus rom use the CM rom you downloaded:
Thanks guys. All going well. CM12 is now installed using that Nexus guide. However, because he used Nexus the Play store was installed by default, which CM12 doesn't have.
Looking here - https://wiki.cyanogenmod.org/w/Google_Apps#Installation - I need to download Google Apps and install it, but which package for the Fire 7 5th gen? There are a number of variants to choose from. Looks like using twrp it would have been a pico one, but as it's a new OS a different one is needed?
So it's ARM device, Android 5.1 and Nano variant?
That gives me a zip file, but I can't work out how to install it. The videos I've found all have it as being installed as part of the OS installation via twrp. Should I have installed gapps when I installed the CM12.1 OS, or can I still install it later?
When I go into the boot menu the only install option is to apply update from ADB, wipe data/factory reset, wipe cache partition, reboot to bootloader or power down/reboot.
I tried to use apply update from ADB and did "adb sideload gapps-filename.zip" but it failed to complete the install and went back to the boot menu.
What do I need to do to get Play Store on there?
Thanks again
Bob Boblaw said:
Thanks guys. All going well. CM12 is now installed using that Nexus guide. However, because he used Nexus the Play store was installed by default, which CM12 doesn't have.
Looking here - https://wiki.cyanogenmod.org/w/Google_Apps#Installation - I need to download Google Apps and install it, but which package for the Fire 7 5th gen? There are a number of variants to choose from. Looks like using twrp it would have been a pico one, but as it's a new OS a different one is needed?
So it's ARM device, Android 5.1 and Nano variant?
That gives me a zip file, but I can't work out how to install it. The videos I've found all have it as being installed as part of the OS installation via twrp. Should I have installed gapps when I installed the CM12.1 OS, or can I still install it later?
When I go into the boot menu the only install option is to apply update from ADB, wipe data/factory reset, wipe cache partition, reboot to bootloader or power down/reboot.
I tried to use apply update from ADB and did "adb sideload gapps-filename.zip" but it failed to complete the install and went back to the boot menu.
What do I need to do to get Play Store on there?
Thanks again
Click to expand...
Click to collapse
Reinstall FlashFire 0.51 (here) on CM 12.1 then use it to flash the GAapps package. Agree with your selection: ARM/5.1/nano.
Ah, great, thank you, yep, that's got it on there.
Excellent! All modded and running very quickly! Thanks for the help guys, I appreciate the patience.
Not much space on these Fire's is there, it's already telling me it's low on space and I've only installed MediaMonkey!
Two more quick questions and I'll leave you alone....!
Is it possible to have the SD card to be used as combined storage? For example, my Shield TV lets me 'add' the SD card to the main storage so it sees it all as one instead of a second removable device, so can install apps on it, etc. If this possible with Cyanogenmod? (Not sure what you'd call that feature to search for it!) Thankfully the main reason I bought it was to help manage my music with MediaMonkey so I won't be installing lots on it, but if it is possible it would be useful.
Second, with regard to OS updates on CM, are they automated or do they need to be done manually (and, if so, with care?)
Thanks again!
Bob Boblaw said:
Two more quick questions and I'll leave you alone....!
Is it possible to have the SD card to be used as combined storage?
Second, with regard to OS updates on CM, are they automated or do they need to be done manually ...
Click to expand...
Click to collapse
Short answer: 'yes'. There are various approaches to utilizing SD cards for app installation/storage each with pros, cons and compromises. I highly recommend using a tool that leverages 'symbolic links' which is by far the most reliable method. An example is Link2SD which you can find in the Play Store.
All custom roms for this device are updated manually via FlaahFire or TWRP (if available). Instructions can usually be found in the OP.
@Bob Boblaw
did you open up the file manager and install the flashfire.apk? I am on the same problem you had on your post #11, but my problem I ran into now is flash fire says "root access could not be acquired" otherwise this would be a easy to do.
I think I might have to reinstall everything and start over. >_<
Yes, I copied it over via USB and installed it from the file manager. Do you have root enabled in the developer settings, I enabled it for adb and apps.
Bob Boblaw said:
Yes, I copied it over via USB and installed it from the file manager. Do you have root enabled in the developer settings, I enabled it for adb and apps.
Click to expand...
Click to collapse
Yes! Thank you, that is what I had missed plus I didn't reboot my device so took like 15mins trying to figure out why it wasn't still working.
Glad you got it working ! :good:
Great post guys!! I am getting ready to root my fire OS 5.1.4 and this helps me greatly! Been searching for a downgrade guide and this is it! Have one question is Cm only recovery program or is there a TWRP version for this ? I would think that lastest TWRP would work since its all android but have to ask .I like TWRP myself cause i have it on rooted tablets
thunderman98 said:
Great post guys!! I am getting ready to root my fire OS 5.1.4 and this helps me greatly! Been searching for a downgrade guide and this is it! Have one question is Cm only recovery program or is there a TWRP version for this ? I would think that lastest TWRP would work since its all android but have to ask .I like TWRP myself cause i have it on rooted tablets
Click to expand...
Click to collapse
You can not boot/install/use twrp on this device unless running FireOS 5.0.1 or lower. Nor can you rollback to any version below 5.1.2 without bricking the device. FlashFire is the tool of choice for installing roms and performing other maintenance tasks that are typically done in a custom recovery environment.
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)
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
If the OS Version is 5.3.2.1, or 5.3.3.0, then no...not root yet.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
The stock version is 5.3.3.0 so, no root.
DragonFire1024 said:
If the OS Version is 5.3.2.1, or 5.3.3.0, then no...not root yet.
Click to expand...
Click to collapse
Thanks for your reply. I haven't received it yet to check the OS version but I'm hearing it will be OS Version 5.4
nyknight77 said:
Thanks for your reply. I haven't received it yet to check the OS version but I'm hearing it will be OS Version 5.4
Click to expand...
Click to collapse
Mine came with 5.3.3.0.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
In addition to other responses no assessment of custom rom compatibility on 7th gen devices can be conducted without root. IMO it is highly unlikely an exploitable vulnerability will be found in recent builds of FireOS or the device bootloader anytime soon given recent efforts to shore up all Android based ROMs.
I just got 4 Fire 7 gen 7s in the mail today; two with a red case, two with a yellow case.
The odd thing is that the yellow colored ones came with 5.4.0.0, while the red ones came with 5.3.3.0. The red ones must not be as popular and I was sent slightly older stock I assume.
Even worse is that the 5.4.0.0 yellow ones won't even let you bypass/skip the initial wifi setup and amazon account login. You MUST be connected to the internet and login with an Amazon account to setup the tablet.
AlwaysLucky said:
I just got 4 Fire 7 gen 7s in the mail today; two with a red case, two with a yellow case.
The odd thing is that the yellow colored ones came with 5.4.0.0, while the red ones came with 5.3.3.0. The red ones must not be as popular and I was sent slightly older stock I assume.
Even worse is that the 5.4.0.0 yellow ones won't even let you bypass/skip the initial wifi setup and amazon account login. You MUST be connected to the internet and login with an Amazon account to setup the tablet.
Click to expand...
Click to collapse
I would highly advise you not allow those to update, flash 5.3.2.1 (the oldest version you can safely revert to if you haven't yet hit 5.4.0.1), and then use the tool linked below to remove all of the Amazon bloatware and install the launcher of your choice. This will get you as close as possible to a stock Android experience.
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
Technocian said:
This will get you as close as possible to a stock Android experience.
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
Click to expand...
Click to collapse
I appreciate the link to the updated tool. The added features are nice indeed and I will try it out.
Technocian said:
I would highly advise you not allow those to update, flash 5.3.2.1 (the oldest version you can safely revert to if you haven't yet hit 5.4.0.1), and then use the tool linked below to remove all of the Amazon bloatware and install the launcher of your choice.
Click to expand...
Click to collapse
Unfortunately, these are the 7th generation Fire 7 tablets (not 5th gen 'ford'). AFAIK, the earliest initial firmware shipped with these gen 7s is the 5.3.3.0. Even worse, is that I've tried to adb sideload every firmware version since 5.3.2.1 (even tried 5.3.3.0), but I got the same error every time at 47% progress:
"whole-file signature verification failed"
"aborted"
On that note, do you or anyone know if there is a way to adb sideload older firmware versions to a gen7? I was using the Windows 10 built-in USB drivers and that seems to be working but I have read elsewhere that the newer Fire generations require the Amazon USB ADB drivers to communicate properly with the computer. So my next step is to try using the Amazon USB driver and try again.
AlwaysLucky said:
On that note, do you or anyone know if there is a way to adb sideload older firmware versions to a gen7? I was using the Windows 10 built-in USB drivers and that seems to be working but I have read elsewhere that the newer Fire generations require the Amazon USB ADB drivers to communicate properly with the computer. So my next step is to try using the Amazon USB driver and try again.
Click to expand...
Click to collapse
Bootloader is locked and anti rollback measures are in place. If you are on 5.4.0.0, the lowest you can downgrade to currently is 5.3.2.1. Trying to go lower will result in a hard bricked tablet. Look at it this way...if you want to experiment, knock yourself out. If you do brick it beyond repair, you have 30 days from date of purchase (or delivery? Not sure how that works) to return it for another. Just get a color you haven't gotten and who knows what those are on, if the event you described regarding colors is true.
EDIT: I am in no way encouraging you to brick your device or do any harm to it.
DragonFire1024 said:
Bootloader is locked and anti rollback measures are in place. If you are on 5.4.0.0, the lowest you can downgrade to currently is 5.3.2.1. Trying to go lower will result in a hard bricked tablet. Look at it this way...if you want to experiment, knock yourself out. If you do brick it beyond repair, you have 30 days from date of purchase (or delivery? Not sure how that works) to return it for another. Just get a color you haven't gotten and who knows what those are on, if the event you described regarding colors is true.
EDIT: I am in no way encouraging you to brick your device or do any harm to it.
Click to expand...
Click to collapse
haha, nice edit.
Well I read your previous post stating that downgrading to 5.3.2.1 was possible, but I get the same above error trying to sideload any version firmware file to it. I am assuming this is because I am on the gen 7 (aka austin), not the gen 5 (aka ford). I have done some extensive searching on xda but it seems not many people actually have a gen 7, so I think I'm pioneering this a little bit.
With that, I can say that the Amazon USB driver for ADB made no change. Any ideas?
AlwaysLucky said:
haha, nice edit.
Well I read your previous post stating that downgrading to 5.3.2.1 was possible, but I get the same above error trying to sideload any version firmware file to it. I am assuming this is because I am on the gen 7 (aka austin), not the gen 5 (aka ford). I have done some extensive searching on xda but it seems not many people actually have a gen 7, so I think I'm pioneering this a little bit.
With that, I can say that the Amazon USB driver for ADB made no change. Any ideas?
Click to expand...
Click to collapse
Debugging mode is on I presume (ADB Enabled)? Have you installed any Google Services (Play Store etc)? Go here and please and follow the installation steps for Total Commander and tell me the info for the 1st and 2nd lines on your device.
DragonFire1024 said:
Debugging mode is on I presume (ADB Enabled)?
Click to expand...
Click to collapse
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"installation aborted."
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
AlwaysLucky said:
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"Whole-file verification failed"
"Aborting installation"
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
Click to expand...
Click to collapse
I have no idea. Regardless, you CANNOT downgrade to anything lower than FireOS 5.3.2.1 (which cannot be rooted). If your tablets are on 5.3.3.0 or 5.4.0.0, the lowest you can go is 5.3.2.1. If you are having ADB trouble, I would download Android Studio full version and make sure the SDK is up to date and start a new ADB folder from there. If your Kernel is of a later date than June 2017, you might not be able to rollback at all.
AlwaysLucky said:
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"Whole-file verification failed"
"Aborting installation"
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
Click to expand...
Click to collapse
Have seen this before (crap out at 47%). Usually pops up when attempting to sideload an inappropriate '.bin' file. Likely the 5.3.1 build you are using is for 5th gen devices. Different mainboard/SOC than 7th gen. Be happy Amazon's firmware detects this and doesn't allow the device to brick.
DragonFire1024 said:
Regardless, you CANNOT downgrade to anything lower than FireOS 5.3.2.1 (which cannot be rooted).
Click to expand...
Click to collapse
Ohhh I understand, so even if downgrading to 5.3.2.1 actually worked, I can't even root on that firmware anyways. Ugh, well I will be patient. Thanks for the info and your time.
If your goal is to have these all ultimately rooted, I would return them and get your money back (if you still can). It's not likely a root method will be found.
This isn't a hot new device like the Pixel 2 where hoards of talent will be flocking to try and make it more usable. I got mine second hand for 25 bucks, this device from a monetary standpoint just isn't worth anyone's time.
The only realistic way I see root happening is if they release firmware based on a new version of Android or Kingroot find an Android exploit that would be compatible with our device.
AlwaysLucky said:
Ohhh I understand, so even if downgrading to 5.3.2.1 actually worked, I can't even root on that firmware anyways. Ugh, well I will be patient. Thanks for the info and your time.
Click to expand...
Click to collapse
Correct...but keep in mind, so far it seems anyone on 5.4.0.1 won't be be able to debloat anymore. So downgrading to 5.3.2.1 is a better option than being so close to the latest version.
I'm not looking to root (i am, but i understand its not possible right now)... So is there any possibility to install apps other than the amazon app store?
thygreyt said:
I'm not looking to root (i am, but i understand its not possible right now)... So is there any possibility to install apps other than the amazon app store?
Click to expand...
Click to collapse
Please see this thread.
hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
havikx said:
hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
Click to expand...
Click to collapse
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Davey126 said:
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Click to expand...
Click to collapse
now that you mention, thats probably exactly what i forgot to do. Also, i'm on 5.1.1. My bad. As far as i know, 5.1.1 system still has that locked bootloader preventing android upgrades. Though I havent kept up with development too much. Ill get started on returning to stock and rerooting. Hope this little tablet get a breakthru in the near future!
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
havikx said:
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
Click to expand...
Click to collapse
Agreed. The technique you used doesn't work for everyone; hence my generic 'return-to-stock and redo everything' guidance. Glad you are back in business with minimum fuss.