Rooted my kindle and flashed a custom ROM. Let a friend borrow it and when I got it back i through it in a closet. Recently moved and found my kindle, charged it, and nothing. I can boot into TWRP but that's about it. I've tried to flash new ROM and get an error message saying "error installing from zip". I've downloaded multiple ROMS multiple times and still no go. Is the kindle done for or am I doing something wrong?
Well your version of twrp is kinda outdated(at least according to the thread title, latest is 2.7), I would first try flashing the latest twrp update hashcode just posted, just download the zip, push it to the device with adb, and flash it and reboot into recovery again. Then try a cm 11 flash. What is did it have on it before all this happened?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Well your version of twrp is kinda outdated(at least according to the thread title, latest is 2.7), I would first try flashing the latest twrp update hashcode just posted, just download the zip, push it to the device with adb, and flash it and reboot into recovery again. Then try a cm 11 flash. What is did it have on it before all this happened?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Not exactly sure. It has been about a year.
MaelstromMonkey said:
Not exactly sure. It has been about a year.
Click to expand...
Click to collapse
Ok, basing it off that it was either amazon os or a cm 10.1 based os. Only reason i ask is because if you tried to install cm 11, and maybe cm 10.2 onto the device at this point it would probably fail with that version of twrp because of lack of selinux support, so i would say go grab latest twrp zip(2.7) for your device, and flash it in recovery, reboot into recovery again, and flash cm 11. Probably should do a factory reset while your at it. I don't think internal storage will need wiping as i doubt it has any selinux xattrib's on it since its more than likely pre-cm10.2ish.
Related
I'm on version 7.4.6 and I flashed the 7.2.3 bootloader, followed by the Freedom Boot 7.4.3 and TWRP 2.6.0.0 - Followed instructions to the T in HashCode's how-to thread. I ended up in a constant reboot to TWRP. I restored back to the images I made in fastboot without a hitch, and now I'm left wondering what could have happened. Any ideas? I did apply the override stack and all of those other things mentioned beforehand.
Well I think I read something about the latest os detecting twrp and not wanting to let you boot I to it but I am not positive if that's what happened.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
For some reason, it appears that the device disagrees to boot onto the stock ROM after you flash a custom recovery (As you said above). My solution was simply to flash a ROM
I'm left feeling kind of dumb for posting this thread haha
I'm starting to wonder if they are must wanting us to brick our kindles at this point, I mean having twrp doesn't mean that we are definitely going to flash a custom ROM, it could mean we want to have insurance against a brick by making a backup, don't know why they see the need to not boot up if we have twrp.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Well I think I read something about the latest os detecting twrp and not wanting to let you boot I to it but I am not positive if that's what happened.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I believe the existence of Kinology should pretty much disprove this theory.
Hey everyone, first time caller, long time listener here. Apologies for the long post but I figured I'd rather provide all the details upfront.
I've had a KFHD 7" for about a year now and have been lurking around the KFHD dev forums ever since, anxiously awaiting ROM's made available for the 7. Finally in July I took the plunge, and using KFFA, downgraded to stock Kindle OS 7.2.3 and followed opensystem's thread here (http://forum.xda-developers.com/showthread.php?t=2347170) on using FireFlash to install kfhd7-Freedom-boot-7.3.0.img as the bootloader and kfhd7-twrp 2.4.4.0-recovery.img as the recovery. Success and all was beautiful!
Since then I've:
* Updated TWRP to version 2.5.0 via Hashcode's ZIP within TWRP
* Updated CM to version 10.2 (8/12/2013 build)
* Reverted CM to version 10.1 (had stability problems)
* Updated TWRP to version 2.6.3.0 via Hashcode's ZIP within TWRP
* Updated CM to version 10.2 (11/15/2013 build)
* Updated TWRP to version 2.6.3.1 via Hashcode's ZIP within TWRP
All this succeeded, and was stable until Thanksgiving Day (go figure). With my tablet acting somewhat laggy, I rebooted it as I have many times before. This time, when the "Kindle" logo went from Orange & White to Blue & White, it froze. I waited 5, 10, 20 minutes and longer, nothing. Wiped Cache, Dalvik, etc via TWRP and tried again... nothing. Reflashed TWRP 2.6.3.0 and CM 10.1 from zips, still freezes. And then it gets really weird when I factory reset it. Here's the sequence of events:
* Restored Kindle OS 7.2.3 via KFFA and fastboot, turned of Amazon updating
* Used FireFlash to install kfhd7-Freedom-boot-7.3.0.img and kfhd7-twrp 2.4.4.0-recovery.img
* Rebooted to TWRP 2.4.4.0 and installed TWRP 2.6.3.1 via Hash's ZIP
* Rebooted to TWRP 2.6.3.1 and installed CM 11.0 (11/25/2013 build)
* Reinstalled applications, etc.
Beautiful again! Worked for several hours with it yesterday, then decided to reboot again and... BAM! Back to the frozen "Kindle" blue & white logo again. Has anyone ever seen this before? Is there some way I can pull up a display of what the bootloader is doing behind the splash screen to see where it is falling over? (BTW, fastboot works, I can still boot into TWRP, and I have a factory cable)
Thanks in advance to all!
Netjerk said:
Hey everyone, first time caller, long time listener here. Apologies for the long post but I figured I'd rather provide all the details upfront.
Thanks in advance to all!
Click to expand...
Click to collapse
Using Freedom Boot with FireFlash does nothing. FireFlash is for images and freedom boot is not an image. You can push it manually no problem. That's why you have to downgrade your firmware to match the Amazon ROM you are about to flash. You may be having a software issue that can't be fixed. Verify your TWRP first. I would do a fresh install of the ROM you choose. Make sure to "swipe" first. Also, how full is your memory? Do you use the Greenify app to keep cpu usage down? Let me know..
LinearEquation said:
Using Freedom Boot with FireFlash does nothing. FireFlash is for images and freedom boot is not an image. You can push it manually no problem.
Click to expand...
Click to collapse
Hey, thanks for the reply. I'm even more confused now than before based on the statement above. Both the seokhun (http://forum.xda-developers.com/showthread.php?t=2271909) and Opensystem (http://forum.xda-developers.com/showthread.php?t=2347170) posts reference using FireFlash to install the kfhd7-Freedom-boot.img. Are you saying I shouldn't install it that way and should instead install via fastboot?
To further clarify, I am doing a full restore of 7.2.3 via Kindle Fire First Aide prior to beginning the procedure. KFFA "pre-roots" the 7.2.3 install and installs the SU app. From there, I'm disabling Amazon OTA updates and then installing ES File Explorer via the Amazon store. ES File Explorer is then used to install the freedom-boot.img as the boot and twrp as the recovery, using the stack override for boot and disabling updates on the recovery. A full reset is done afterwards and before installing CM (cache/dalvik/system wipe). Memory usage should be a non-issue as I haven't yet installed any other applications.
Any thoughts are greatly appreciated!
Opps, wow, I meant you can't flash the bootloader so that's why you downgrade firmware.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------
Netjerk said:
Hey, thanks for the reply. I'm even more confused now than before based on the statement above. Both the seokhun (http://forum.xda-developers.com/showthread.php?t=2271909) and Opensystem (http://forum.xda-developers.com/showthread.php?t=2347170) posts reference using FireFlash to install the kfhd7-Freedom-boot.img. Are you saying I shouldn't install it that way and should instead install via fastboot?
To further clarify, I am doing a full restore of 7.2.3 via Kindle Fire First Aide prior to beginning the procedure. KFFA "pre-roots" the 7.2.3 install and installs the SU app. From there, I'm disabling Amazon OTA updates and then installing ES File Explorer via the Amazon store. ES File Explorer is then used to install the freedom-boot.img as the boot and twrp as the recovery, using the stack override for boot and disabling updates on the recovery. A full reset is done afterwards and before installing CM (cache/dalvik/system wipe). Memory usage should be a non-issue as I haven't yet installed any other applications.
Any thoughts are greatly appreciated!
Click to expand...
Click to collapse
See post above.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
I have a Kindle Fire HD 7 (7.4.6) rooted and I want to know if there's a way that I can install the TWRP Recovery without flashing any rom at the moment and most important without bricking it. I want to have it installed in case that in a future I want to flash a rom. I think it's a must have tool on this device but I'm not quite sure if it's possible and I don't want to try how-to's that I've read in these forums because it's not what I'm looking for and I don't want to mess up the KF . Any help or advice on this will be very appreciated. :angel:
There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the response, I'm trying that... but before I do this... I want to make sure I'm on the right track. I copied three files on the main kindle directory (fireflash11.apk, kfhd7-freedom-boot-7.4.6.img and kfhd7-twrp-2.6.3.1-recovery.img). I've installed the Fire Flash and now... I'm seeing the interface to flash the boot partition and recovery partition, and the bootloader says the warning thing that the bootloader is not kfhd7-u-boot-prod-7.2.3.bin. That last part is where I'm stuck in... I don't know if checking the box will mess up my kindle... so far, I know that I had to check the "apply stack override", "disable recovery auto update", then unplug cable and hit flash. I'm not sure if I'm still needing the kinology rom since I've downloaded the freedom boot from hashcode.
stunts513 said:
There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?
x10knight said:
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?
Click to expand...
Click to collapse
Because they were running 7.4.6 so the 7.4.6 bootloader is a match. The problem is that the exploit was patched at 7.3.0 so one really should downgrade to 7.2.3 first because sometimes clicking flash 7.2.3 bootloader while using FireFlash app does not work and you get a bootloop anyway. It's best to drag and drop a ROM onto the internal sd card before flashing. If you do bootloop, just go into TWRP and flash the ROM.
x10knight said:
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?
Click to expand...
Click to collapse
I'm new and a complete noob to this, I'm running 7.4.6, can someone please explain freedom boot and if it would be possible for me to get a custom Rom loaded on my tablet without downgrading to 7.2.3?
Sent from my KFTT using xda premium
Freedom boot if I understand correctly is a patch to the kernel used for second bootloader, I believe it also has version data stored in it that the kindle is checks on boot, if the kernel doesn't match the kindle os version it boot loops into recovery. So yes you can do all without downgrading the os, its just suggested you do because amazon patched the boot loader a while back and downgrading ensures you don't boot loop in case you have an older freedom boot image or you are on 7.4.7. Its probably also flashes the old boot loader too which helps. Never used kffa so not positive about that though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
So how do you suggest I go about flashing my custom Rom, I don't want to downgrade and I want to use fireflash preferable?
Sent from my KFTT using xda premium
I prefer the fire flash method but if you or the program mess up and don't flash the boot loader with the older version first, you will need a fastboot cable to fix it. I haven't ever had a problem with fire flash myself, as long as you check the first box with a bunch of red warning text under it you should be OK.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I prefer the fire flash method but if you or the program mess up and don't flash the boot loader with the older version first, you will need a fastboot cable to fix it. I haven't ever had a problem with fire flash myself, as long as you check the first box with a bunch of red warning text under it you should be OK.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks figured it out on my own before your post but it's the thought that counts lol your post will help others tho, I was a complete noob it was actually easier than what I thought, I'm running CM11 right now
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
So... what I should do... run the fire flash app checking that box about the warning of boot loader... and put the files in place and check the "apply stack override" and that's it? I'm getting confused because the post went out of topic...
gracielatf said:
So... what I should do... run the fire flash app checking that box about the warning of boot loader... and put the files in place and check the "apply stack override" and that's it? I'm getting confused because the post went out of topic...
Click to expand...
Click to collapse
First, drag and drop what ever ROM you are going to use onto the root of the internal SD card (CM, Paranoid Android, which ever one). This is important. If you do loop, access TWRP and flash the ROM.
Make sure to put the images in the right place, tick "apply stack override" and also tick "disable recovery auto update" and also chaeck "7.2.3 bootloader."
Here is the original tutorial as well for your reference. http://forum.xda-developers.com/showthread.php?t=2271909
Edit: when you do go to flash the ROM from TWRP you first "swipe" then flash the ROM and then wipe only Dalvic and CACHE.
LinearEquation said:
First, drag and drop what ever ROM you are going to use onto the root of the internal SD card (CM, Paranoid Android, which ever one). This is important. If you do loop, access TWRP and flash the ROM.
Make sure to put the images in the right place, tick "apply stack override" and also tick "disable recovery auto update" and also chaeck "7.2.3 bootloader."
Here is the original tutorial as well for your reference. http://forum.xda-developers.com/showthread.php?t=2271909
Edit: when you do go to flash the ROM from TWRP you first "swipe" then flash the ROM and then wipe only Dalvic and CACHE.
Click to expand...
Click to collapse
Got it, wish me luck! :cyclops:
gracielatf said:
Got it, wish me luck! :cyclops:
Click to expand...
Click to collapse
Good luck!
Well... that was fast. I didn't need the Kinology ROM, but I downloaded and dragged it to the Kindle, just in case it boot loop and so have the rom as backup. Just needed the three fiiles. I'll place the instructions clearly just in case anyone wants to do this and worked perfectly for me.
Download:
fireflash11.apk,
kfhd7-freedom-boot-7.4.6.img and
kfhd7-twrp-2.6.3.1-recovery.img.
Copy or Drag & Drop the three files to Kindle Fire HD 7". Make sure to have ON the "allow installations of applications" options found in drop down window (More+ -> Device). Then install the fireflash11.apk, after installation, open the app, if you got the warning message, check the box on the right, then place the kfhd7-freedom-boot-7.4.6.img in the "boot partition" section and tick "apply stack override", then the kfhd7-twrp-2.6.3.1-recovery.img in the "recovery partition" section and tick "disable recovery auto update". Unplug your KFHD7 from the USB, then hit Flash, and that's it! :victory:
No ROM needed, but in case you want like to go in "safe mode" like I did, download the Kinology ROM found here.
Firstly, thanks to SafinWasi and Red_81 who both helped me on other threads, this question follows on from those threads.
I'm trying to downgrade from 7.4.9 user 4952320. Eventually, I will probably install CM11 (I tried once and bricked my device), but for now I just want to downgrade the OS and be able to change the wallpaper, I'm sick of the black paper. (I've tried Stunts wallpaper fix and it didn't work)
When the device upgraded to 7.4.9 I made backups of the whole 12 img files (inc boot0block).
I've read that you need a 7.2.3 boot image to be able to install TWRP as part of the CM11. I obtained a rooted 7.2.3 boot image from Red_81s google drive. I then flashed that boot image and tried rebooting the device. No joy. I got the red triangle. I flashed my 7.4.9 boot image and rebooted. The device rebooted and worked as normal.
I then flashed the 7.2.3 rooted system image and rebooted. Again I got the red triangle. I then flashed the 7.2.3 boot image, (so the device had 7.2.3 system and boot images) but again I got the red triangle.
So, how do you downgrade? Should I have flashed all 3 of the 7.2.3 images? (I don't have the checksums of the images so I recognise if one of the images was corrupted the exercise was doomed to failure.)
By flashing my 7.4.9 system and boot images, my device was restored to functionality, and I learned a bit, but not enough to achieve the goal. I'm hoping someone can show me how to downgrade.
Thought I'd add that I did try Kindle Fire First Aide but got lots of errors about dropbox not being available.
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
cecr said:
.
Click to expand...
Click to collapse
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Red_81 said:
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't flash recovery, at my first attempt, just boot, then I tried boot & system. Both tries gave the red triangle.
I've tried again, with all 3 rooted images from your gdrive - recovery, boot & system, and again got the red triangle. I tried again with the 3 images from another source (my own unrooted 7.2.3 backup when I first got the HD7) and again, got the red triangle.
I haven't wiped the data because I would prefer to keep it so I can use the device (and think it should be possible to downgrade without wiping). I haven't been able to find a command to wipe just the cache...
So I'm more than a bit puzzled. The fastboot commands (eg fastboot -i 0x1949 flash boot boot.img) all return with "sending" then "OKAY", then "writing", then "OKAY" so I don't think there's any problem there.
I must be doing something wrong or missing something.
LinearEquation said:
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your response, but at this stage I don't want to flash a new custom ROM, that may (probably will) come later, but at this stage I want to just downgrade. I've been warned that installing TWRP etc may leave the stock system in a bootloop, so a working stock backup won't be possible.
As I have to downgrade the stock boot image anyway in order to install a custom ROM, I thought I'd downgrade the whole OS in order to have a functioning stock system, then I can make a backup of it in TWRP, then install a custom ROM.
If I'm having problems with a simple downgrade, I might have more severe problems flashing a new ROM and be left with a dead device like I was previously, hence my caution and not wanting to move on until I know I can recover to the previous step if things go wrong.
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Red_81 said:
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Click to expand...
Click to collapse
Yes, I did. Tried them twice, in a different order (didn't think it would make a difference but you never know....). Anyway, tried again, this time, wiped data and cache (took 45 mins) and it worked! I now have 7.2.3 and access to Gplay (was already there).
I haven't registered it to my Amazon account yet, so email and contacts don't work, and am wondering if I should go straight to installing a custom ROM. I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
It's been a bit of a task getting this far, but at least I'm more confident about getting into ADB and Fastboot!
cecr said:
I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
Click to expand...
Click to collapse
well, I know the answer, yes, even though it hasn't logged into an Amazon account (I realise they pre-register them to your account before dispatch), it updated back to 7.4.9 just as I finished the above post and whilst I was thinking I should disable OTA updates using KFFA!
flip. This is turning into hard work. lol, still I know how to do it now.
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
greg2074 said:
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
Click to expand...
Click to collapse
Nice to know. Think I'll be doing something very similar, now I've made backups of 7.4.9 "just in case". Just have to go through all the above again!
All:
I know Kindle Fires can be very finicky and unforgiving, so before I brick my tablet I wanted to get some advice.
Back in 2016 I successfully rooted my Kindle Fire 7 5th gen and installed SlimLP 5.1.1. It's starting to run sluggish, so I'd like to wipe it and do a clean install. Is that as simple as flashing the latest CM or Slim ROM using the stock recovery software, or would you recommend another method?
HuskyCPA said:
All:
I know Kindle Fires can be very finicky and unforgiving, so before I brick my tablet I wanted to get some advice.
Back in 2016 I successfully rooted my Kindle Fire 7 5th gen and installed SlimLP 5.1.1. It's starting to run sluggish, so I'd like to wipe it and do a clean install. Is that as simple as flashing the latest CM or Slim ROM using the stock recovery software, or would you recommend another method?
Click to expand...
Click to collapse
You can not flash a custom ROM using stock recovery. However, if your device is an early 5th gen you can boot TWRP which dramatically simplifies the tasks required to install/refresh a custom ROM. If you do not recall using TWRP then I would not attempt to replace Slim as the tool needed to accomplish this task has become unreliable.
Davey126 said:
You can not flash a custom ROM using stock recovery. However, if your device is an early 5th gen you can boot TWRP which dramatically simplifies the tasks required to install/refresh a custom ROM. If you do not recall using TWRP then I would not attempt to replace Slim as the tool needed to accomplish this task has become unreliable.
Click to expand...
Click to collapse
ADB & fastboot seem to work fine, but when I try and boot to TWRP I get an error message. I also tried using Root Junk's super tool, but after it runds "ADB devices" and displays my device ID, it craps out. Is that the tool that has since become unreliable?
HuskyCPA said:
ADB & fastboot seem to work fine, but when I try and boot to TWRP I get an error message. I also tried using Root Junk's super tool, but after it runds "ADB devices" and displays my device ID, it craps out. Is that the tool that has since become unreliable?
Click to expand...
Click to collapse
FlashFire.
Davey126 said:
FlashFire.
Click to expand...
Click to collapse
Thanks for clarifying.
Any other threads out resources you'd recommend for troubleshooting my issues booting to TWRP?
HuskyCPA said:
Thanks for clarifying.
Any other threads out resources you'd recommend for troubleshooting my issues booting to TWRP?
Click to expand...
Click to collapse
Boot into TWRP will either work or not based on bootloader version (must be 5.00 or 5.01); Amazon addressed the vulnerability in FireOS 5.10 and above. There are no rollback options for this scenario; attempting to do so will brick the device with no possibility for recovery.
Purchasing Flashfire Pro (or ODIN) on another device is your best option. But realistically this device is getting long in the tooth with sluggish performance even with a custom ROM. Plus Flashfire challenges with every ROM update. You'd be better off debloating and call it a day.
HuskyCPA said:
ADB & fastboot seem to work fine, but when I try and boot to TWRP I get an error message. I also tried using Root Junk's super tool, but after it runds "ADB devices" and displays my device ID, it craps out. Is that the tool that has since become unreliable?
Click to expand...
Click to collapse
I've had this issue when using a less reliable USB cable. Once I tried a known good data cable, it eliminated that issue.:good: