I have a Kindle Fire HD 7 which I am running Amazon OS 7.2.3. I have followed various guides / tools and installed 2nd bootloader and TWRP. I then installed Cyanogenmod 11 nightly for tate. When I reboot after the install I get the Cyanogenmod boot animation and thats it, I have waited for 10 - 15 minutes and nothing happens just see the boot animation. I restore 7.2.3 and that boots fine. What should I look at to figure out what's going on here.
Did you factory reset (in twrp) when coming from Amazon os?
Sent from my LG-P769 using Tapatalk
stunts513 said:
Did you factory reset (in twrp) when coming from Amazon os?
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
That seems to have done the trick, I was wiping data / cache after install but not prior to it. Doing factory reset prior to install was the key.
Related
I recently purchased a kindle fire hd 7 version 7.3.1 which i am looking to install cm10.1 on. i have read through many threads and have download all the needed files to undertake this project. the only problem that i have encountered which proves to be very troublesome is loading my kindle into fastboot mode. can any one help me with this problem? thank you.
Why are u trying to get into fast boot mode? You should only need adb to back it up then use fire flash to put 2nd bootloader and twrp on it, then transfer over the cm 10.1 images for flashing from twrp. That's it in a nutshell. Fast boot it only for if you brick it in the process, which in most cases you will need a factory cable to get it into fast boot mode.
To be more specific about this read seokhuns awesome guide, but follow it to the tee or u may get a red screen on your bootloader to which you will need a factory cable to fix.
http://forum.xda-developers.com/showthread.php?t=2271909
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Why are u trying to get into fast boot mode? You should only need adb to back it up then use fire flash to put 2nd bootloader and twrp on it, then transfer over the cm 10.1 images for flashing from twrp. That's it in a nutshell. Fast boot it only for if you brick it in the process, which in most cases you will need a factory cable to get it into fast boot mode.
To be more specific about this read seokhuns awesome guide, but follow it to the tee or u may get a red screen on your bootloader to which you will need a factory cable to fix.
http://forum.xda-developers.com/showthread.php?t=2271909
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you. i have done some reading and it says that fire flash supports 7.3.0 but i am running 7.3.1 ... will this work properly or will it brick my device?
kodie. said:
thank you. i have done some reading and it says that fire flash supports 7.3.0 but i am running 7.3.1 ... will this work properly or will it brick my device?
Click to expand...
Click to collapse
i did take the risk and try it and it did work twrp in successfully installed now im trying to install cm10.1 after i wipe the system, factory reset cache, Dalvik cache and proceed to installing cm10.1 it says failed.. can you help me? thanks
After u have the zip file on your sdcard I suggest using es file explorer to check the files properties and calculate its md5sum and compare it to the md5sum on the download link. If they match up then it should be working, if not it just didn't probably transfer or DL right.
U will probably need to flash a modded stock image of kindle os if you didn't back up your os first, so your kindle has an os to boot into. By modded stock image I mean that on the kindle android development forums there are a few modded stocks that come rooted without reflashing the stock boot loader and recovery plus have ota disabled. Makes things easier so you don't need to reflash the boot loader and twrp and reroot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
After u have the zip file on your sdcard I suggest using es file explorer to check the files properties and calculate its md5sum and compare it to the md5sum on the download link. If they match up then it should be working, if not it just didn't probably transfer or DL right.
U will probably need to flash a modded stock image of kindle os if you didn't back up your os first, so your kindle has an os to boot into. By modded stock image I mean that on the kindle android development forums there are a few modded stocks that come rooted without reflashing the stock boot loader and recovery plus have ota disabled. Makes things easier so you don't need to reflash the boot loader and twrp and reroot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thanks kindle fire up and running cm10.1 and google appps .. i change my usb cable and re downloaded the files and then it worked
Many work with cm10.1 kfhd7 of Hashcode .
I installed 2nd bootloader on 7.3.1 but I forgot to disable auto-updates and I woke up to 7.4.3 and lost root and 2nd boot. I managed to root It again but i'm kinda scared to install the bootloader. I think I'm gonna wait until someone verifies and it's ok.
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
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.
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!