Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.
Would be nice if you posted that guide on this forum too.
Thanks for the guide.
Oooohh pictures
Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.
"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!
Disclaimer: By following this guide, you understand and accepts that I, and any developers mentioned in this guide, will NOT be held responsible in the event that your device stops functioning or dies. While I try my best to make everything as clear and concise as it can be, accidents will happen should you not follow everything like a hawk.
Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial
I'm going to lead you through installing Hashcode's 2nd-Bootloader and TWRP in order to start flashing custom ROMs and make backups. First, let's go over the basics and why I'm doing this in the first place. I wrote this guide to be used on a Windows computer, but as long as you can do the same things on Mac/Linux, the whole guide applies. If there are any issues, please first refer to the troubleshooting portion at the end of the guide. The 8.9 version of the device does not need the factory cable to enter fastboot mode.
+Note: As of Amazon OS update 8.3.1+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 8.3.1 or higher, please proceed with caution. I strongly recommend you make backups in Step 2.
===== 1. Why do we need a 2nd bootloader? =====
The stock Amazon bootloader doesn't play nice with Android even though it has Android at its core. We can still use fastboot commands with it, but other than that, it's quite locked-down. In other words, normal exploits used to unlock the bootloader on other Android devices, for example, like the Nexus series by Google or the handsets by HTC don't apply here. In order to use the same features, like a custom ROM, custom kernel, custom recovery, we must bypass Amazon's software by installing a 2nd bootloader.
===== 2. Why are you posting a tutorial? =====
I'm doing this because the lack of a guide means that people like myself, who are not proficient developers, keep running into issues and some ended up bricking their devices. This means that they end up with a heavy paperweight, with no chance of fixing, other than hoping that they're lucky with a fastboot cable (not the one that came with the device) and find their way back to the beginning. I'm sick of seeing so many questions about the exact same issues so I thought, why not just make a guide everyone can follow and thus make the world a better place.
===== 3. Do I need any special equipment/knowledge? =====
You don't need any special equipment, provided that you follow this guide word-for-word and be careful. I successfully installed the 2nd-Bootloader + TWRP and flashed CM10.1, within minutes. The key is make sure you don't miss anything, and if you're not sure, don't make any random guesses. As far as knowledge, yes, and no. Know what you're dealing with. Anything underneath the ROM has the chance to brick the device, so know what you're getting into.
===== 4. Can't I just use FireFireFire or another automatic tool to install the bootloader + TWRP? =====
Definitely not. This is the exact reason why there are so many threads in the Q&A section about bricked devices in the first place. Never use a tool that wasn't made for the version of your tablet. The Kindle Fire (1st gen), the Kindle Fire 2 (2nd gen), and the Kindle Fire HD 7" & 8.9" (3rd gen) are not the same devices, at all. Due to the way the bootloader behaves, flashing the files that are only compatible for the Kindle Fire 2 on a Kindle Fire HD 7" will definitely brick it. This is because the bootloader is so-named for a program that checks the booting process before the device actually boots, and if there are any bad sectors that don't match, the device won't boot.
How do you avoid this? By following guides like mine, and first knowing exactly what model you have. Yes, the Kindle Fire 2 and the Kindle Fire HD 7" look similar, and Amazon seriously have problems with their naming method, but a bit of research tells you that the Kindle Fire HD actually contains an HD resolution screen, 1280x800 for the 7" and 1920x1200 for the 8.9". Also, ONLY the Kindle Fire HD 7" and 8.9" models have a front-facing camera while the other models don't have one at all. If you want to be sophisticated about it, you can use working fastboot to identify the tablet.
+Note: if you know 100% that you have the right model, skip to Step 1 and begin the guide. This part is only for those with knowledge of fastboot and would like to confirm scientifically that they have the right model. You don't need to know how to use ADB or fastboot in order to successfullly complete the guide and install custom ROMs:
In CMD, type:
Code:
fastboot -i 0x1949 getvar product
Hitting enter will return with <waiting for device>. If you connect your powered-off Kindle Fire HD 7" or 8.9" at this point, it will reboot into fastboot mode, and on CMD, it will return with "tate-xxx-xxx" for the 7" and "jem-xxx-xxx" for the 8.9". I cannot stress this enough, please know your stuff before you end up crying about how you made a simple mistake that cost you $200, or however many in other currencies, but I do know that universally, it's quite a lot of money.
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
===== 6. How do I boot into fastboot mode? =====
This relies on you having a working device (as long as it can boot at all, you're good). If you wish to enter fastboot mode to flash system images like new versions of TWRP or restore Amazon OS 8.1.4 if you've got freezing or bootloops, then you need a regular USB cable that came with the device, or any other mini-USB cable that fits the device and the computer. Again, you need to have Android SDK installed before you can use fastboot. Turn the device off, and leave it unplugged. Go to your computer, open command prompt, and type this:
Code:
fastboot -i 0x1949 getvar product
Hit enter, and it should return with <waiting for device>. If it doesn't, your fastboot drivers aren't working. Install Android SDK and go from there. If it does, connect your turned-off Kindle to the computer. Two things will happen: one, the command prompt will show "jem-xxx-xxx" (something there), and two, your Kindle should reboot into fastboot mode. From here, you can begin using fastboot commands to flash to the device's partitions. To exit fastboot mode, after you finished flashing what you needed, type this:
Code:
fastboot -i 0x1949 reboot
And that's all for the basics! Let's move on to the actual process.
Step 1: Rooting
+Note: Some users reported not being able to root on later software versions, so check for 8.1.4 in your Settings, if it's higher than that, you may have some trouble, which is why I provided 3 methods.
Before you can do anything else, you need to root the device first. Rooting is the process of acquiring superuser (administrator) access on a Linux system, allowing you to modify just about anything with regards to software. It is generally very safe to do, provided you follow the correct guides and you use the correct tools, and if there are no tools, the knowledge to manually root the device. On many other Android devices, rooting also installs a custom recovery, but the Kindle Fire HD 8.9" is different. You must root first before you do any modifications.
Go to this thread: QEMU Root by sparkym3, and download the necessary attachments. Use any decompressing software to unzip the files, and install the Kindle Fire HD 8.9" ADB drivers (this may fail, no need to worry). Then jump to your device, go to Settings and turn on ADB, then plug it into your computer. At this time, your computer should report that the ADB Composite Interface has been installed. What this means is that your ADB drivers work. Go ahead and use that thread's instructions to root the device.
Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry, same idea. Make sure your ADB drivers are working, and that ADB is turned on in Settings. Open the RunMe.bat file, choose option 1. Now it will ask for your Amazon account password to restore, go ahead and type in your password and proceed. After the device reboots, it will be sluggish, now run the first method again, and you'll be back to normal with root.
You can aso try this: Root Kindle Fire HD with Windows
To check if you're rooted, when the device is on, go to the Amazon Appstore, install "ES File Manager" or any other root application, you want to see the window asking for superuser permissions. Once it installs, open it, go to settings, and turn on root browsing. If it asks for superuser permissions, you have root access, and you can move on to the next step. If the root programs say you have root, but you don't see the window asking for the permission, remember to go to the app listing, and tap on superuser to initialize the daemon, then try to check for root again.
Recap:
1. Download the root tools from the threads
2. Proceed to root by using the provided tools
3. Check if you successfully have root access using any root application
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Step 3: Installation
You might have noticed that Hashcode made a pretty extensive thread to help you flash the bootloader, but another coder has since developed an automatic app to do all the work for you: FireFlash. Go ahead and download the .apk file. Move that file to the sdcard, and on the device, install it using "ES File Manager" (tap on that file) or "Easy Installer" (after it finishes scanning, select it and install), both found on the Amazon Appstore. You will then find it in the applications listing, go ahead and open it.
The first thing you notice is that there are spots to plug in files for different partitions. This is where those files from Hashcode come into play. Plug the freedom-boot.img into the boot partition space, plug the TWRP recovery.img into the recovery partition, and make sure to hit "apply stack". If you are NOT on the 8.1.4 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 8.1.4 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on.
Check that "disable recovery auto update" box, leave everything else alone, unplug the cable, and hit flash (the first option). You will see a progress window, and just hit OK. Then, turn off the device. Now, when you turn it on, this is the way to enter recovery every time: the moment you turn it on, you'll see the yellow Kindle title. Immediately hold down the Volume Up button (leftmost from the power button) before it turns blue, and once it does, count to three in your head and let go and you'll see the TWRP splash logo. Once you're in TWRP, you're done. Just hit reboot, and everything's finished. Now you can browse the 8.9" Development forum for custom ROMs.
If you want to save space, you can now go ahead and delete all the files we just used; you no longer have a need for any of them. Keep FireFlash, though, because in the future you might want to update TWRP, then leave everything blank, plug the update image into the recovery partition and hit flash. Only use Hashcode's TWRP builds as of now, because he specifically altered those builds to work on the Kindle Fire HD 7" and 8.9" so the official ones on the TWRP site won't work. If you flash those (especially the "blaze" codename), you will brick the device, so don't do it!
Recap:
1. Download FireFlash and install on device using file manager or installer
2. Plug in the required files in the correct areas, and check the necessary checkboxes
3. Flash, and boot into TWRP to confirm successful installation of both 2nd-Bootloader and TWRP recovery
Step 4: Flashing Custom ROMs
This is what you've been waiting for, the ability to load custom ROMs. You have a few choices at this point in time. This list contains (somewhat, if not) stable releases only:
1. CyanogenMod 11 by Hashcode (AOSP, Android 4.4 KitKat)
2. ParanoidAndroid Port by jb2kred (AOKP, Android 4.2.2 Jelly Bean)
3. PAC-man by goldflame09 (AOKP, hybrid of CM + PA, Android 4.3 Jelly Bean)
4. CM11/SGT7 by twa-priv (CM + Samsung Galaxy Tab 7 mods, Android 4.4 KitKat)
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Now, in case your custom ROM doesn't automatically include GApps, and you would know if you boot up and you don't see Play Store or Google Maps in the app drawer, follow this. Go to this link. You will notice a table, and on the left side, you see the CM version that corresponds to the Android version number. All the custom ROMs should use the row that corresponds to the Android version. For example, CM10.1 runs 4.2.2, CM10.2 runs 4.3, so click on the one that corresponds. If your ROM runs 4.2.2, use the 4.2.2 row, etc. After you finish downloading that .zip file, move it to the sdcard, and boot into TWRP. From there, if you want to be fancy, wipe cache and Dalvik cache before flashing, but you don't have to unless there are problems after you restart. If there are problems, like freezing on boot, or crashing, then boot back into TWRP and wipe the two cache partitions.
Generally, you only need to flash the file and you're done, but you can never be too safe. This also applies to ROMs: if you're moving from ROM to ROM, say Ubuntu Touch to CM10.1, you MUST wipe EVERYTHING except the sdcard itself, and this includes the "Factory Reset" option. However, if you're moving from one update of a ROM to another, say a nightly of CM10.1 to a newer nightly of CM10.1, you can just simply flash the update over the old one, no wiping needed (this is called dirty-flashing). However, again, if you notice problems afterward, simply boot back in TWRP and wipe the two cache partitions. Remember to always make backups before you make changes to an otherwise stable build. If there are issues that you can't seem to resolve, you can always restore back to the previous build.
Recap:
1. Download .zip for ROM + GApps and move to sdcard
2. Boot into TWRP, make backups, and wipe the necessary partitions
3. Flash ROM, and wipe cache + Dalvik cache, then reboot
4. Wait for 5 minutes after successful reboot, then reboot again
5. If there's no GApps for your ROM, use the link to download the proper version.
6. Move the file to sdcard, then boot into TWRP and flash.
7. Reboot, and if there are problems, reboot back into TWRP and wipe cache partitions.
Credits: Hashcode, fattire, and verygreen for the work on the bootloader, stanga72 for the app FireFlash, sparkym3 & prokennexusa & Bin4ry for their rooting methods, and myself for the creation of this guide.
This guide/tutorial was extremely helpful to me as a novice, just starting how to learn to modify my Fire HD 8.9". I'd like to suggest a few changes/enhancements to the guide:
1. In the NOTE paragraph just below the first paragraph you mention issues with 8.4.1. specifically you mention issues with this release but there is no indication if these issues will prohibit successful update if the guide is strictly followed. Also, a cable is mentioned. In other posts I have seen references that indicate that no cable is necessary with the Fire HD 8.9". In fact, one post mentions that using a cable may, in fact, possibly damage the Fire HD 8.9".
2. Because I'm so new at this I'm very paranoid about making a mistake. I've read the horror stories in many of the posts and I'd like to avoid these mistakes. And because I'm so new, my only experience is with the 8.4.1 release and unfortunately it is so new, I suspect, that the developers have not had time to verify that their applications are compatible. I am not complaining since I know that 99.9% of these good people do this out of the goodness of their heart, and not for monetary gain. However, I do wish this issue of software release version could be more fully addressed.
3. Just an example - The heading clearly states that this guide applies to the Fire HD 8.9". Very clear and difficult to misunderstand! In Step 3 Installation, FireFlash is mentioned with no reference to a Fire HD operating system release number. Can I safely assume then that this utility is compatible with 8.4.1? It may be that the answer would be obvious to a more experienced person but to someone like me(and from reading many, many posts there must be a bunch of folks out there just like me), with little experience in flashing, rooting, etc.,I'm at an impasse regarding should I proceed or not proceed Thank you..
There will have to be some changes to the method to install boot and recovery on both 8.4.1 and now people are receiving 8.4.3 all the present methods will break the system, unless you have a Rom waiting on your sdcard to flash afterwards.
rebelduke said:
This guide/tutorial was extremely helpful to me as a novice, just starting how to learn to modify my Fire HD 8.9". I'd like to suggest a few changes/enhancements to the guide:
1. In the NOTE paragraph just below the first paragraph you mention issues with 8.4.1. specifically you mention issues with this release but there is no indication if these issues will prohibit successful update if the guide is strictly followed. Also, a cable is mentioned. In other posts I have seen references that indicate that no cable is necessary with the Fire HD 8.9". In fact, one post mentions that using a cable may, in fact, possibly damage the Fire HD 8.9".
2. Because I'm so new at this I'm very paranoid about making a mistake. I've read the horror stories in many of the posts and I'd like to avoid these mistakes. And because I'm so new, my only experience is with the 8.4.1 release and unfortunately it is so new, I suspect, that the developers have not had time to verify that their applications are compatible. I am not complaining since I know that 99.9% of these good people do this out of the goodness of their heart, and not for monetary gain. However, I do wish this issue of software release version could be more fully addressed.
3. Just an example - The heading clearly states that this guide applies to the Fire HD 8.9". Very clear and difficult to misunderstand! In Step 3 Installation, FireFlash is mentioned with no reference to a Fire HD operating system release number. Can I safely assume then that this utility is compatible with 8.4.1? It may be that the answer would be obvious to a more experienced person but to someone like me(and from reading many, many posts there must be a bunch of folks out there just like me), with little experience in flashing, rooting, etc.,I'm at an impasse regarding should I proceed or not proceed Thank you..
Click to expand...
Click to collapse
Thepooch said:
There will have to be some changes to the method to install boot and recovery on both 8.4.1 and now people are receiving 8.4.3 all the present methods will break the system, unless you have a Rom waiting on your sdcard to flash afterwards.
Click to expand...
Click to collapse
I am aware of the changes, but I have not been caught up with the status of the methods and their effects on the tablets. I have placed warnings at the beginning of the guide.
I have two questions about Step 2 for backing up files.
1. Is boot0block.img ever needed? It looks like it is backed up, but it isn't referred to in the restore step (fastboot commands).
2. The "adb pull" commands don't work for me. For example, this error message displays: "remote object /sdcard/stock-boot.img' does not exist". But the files are definitely there.
Sorry about asking about 2! I was actually putting the brackets around the local folder, but I realize now that you only had them to indicate that parameter was optional. However, the error that was occurring before wasn't about the local file...it was about the .img file which did exist. I'm baffled because now if I put the brackets back, it only fails with an error about that, not about the .img file. I realize I'm not making much sense, but I can't reproduce it so that it says the same error that I first mentioned above in 2.
I'd still like to know about 1 though. Thanks.
EDIT: I did Step 3 - Installation. I booted into TWRP and did a backup. I assumed that I did not have to do any wipes or install of any other rom yet, i.e. I just wanted to boot the existing 8.1.4 rom that was already there. However, when I "reboot system" from TWRP, it goes into TWRP again instead of booting up the rom.
I tried doing a restore of what I just backed up, but the result is the same. So does this mean I was required to do the wipes and install of another rom, rather just booting up my existing one? Or is there some other step I'm missing to make it get out of TWRP?
sga999 said:
I have two questions about Step 2 for backing up files.
1. Is boot0block.img ever needed? It looks like it is backed up, but it isn't referred to in the restore step (fastboot commands).
2. The "adb pull" commands don't work for me. For example, this error message displays: "remote object /sdcard/stock-boot.img' does not exist". But the files are definitely there.
Click to expand...
Click to collapse
Boot0block is backed up in the event something happens to that particular partition somewhere along the way, you will know if it does no wifi ect. Shift plus right click inside the folder that adb is located, select open command window here. Run all your commands from that cmd prompt. It will pull all those files to that folder location. Since you will know what folder it is to be pulled to this portion of the command can be omitted [C:\KFHD8Backup].
Thepooch said:
Boot0block is backed up in the event something happens to that particular partition somewhere along the way, you will know if it does no wifi ect. Shift plus right click inside the folder that adb is located, select open command window here. Run all your commands from that cmd prompt. It will pull all those files to that folder location. Since you will know what folder it is to be pulled to this portion of the command can be omitted [C:\KFHD8Backup].
Click to expand...
Click to collapse
I realized more about the format of the 'adb pull' command and posted late last night. It's in my post above your response. Thank you for answering. Also, it's good to know about what boot0block is in case something fails later.
I also added another question there, wondering about why I can only boot into TWRP, not the stock rom I already had installed. I'm pointing that out again now, just because you(and others?) may not have seen it in my EDIT above.
Do a full wipe and flash a Rom.zip. Now you will need to
Code:
adb push Rom.zip /sdcard/
For obvious reasons just don`t wipe your sdcard .
Thepooch said:
Do a full wipe and flash a Rom.zip. Now you will need to
Code:
adb push Rom.zip /sdcard/
For obvious reasons just don`t wipe your sdcard .
Click to expand...
Click to collapse
I can do that. But I'm curious to know why you're recommending this. Is it because I had problems booting up the old 8.1.4 rom and you just want me to try some other rom? Or is it that you know that what I did will never work, i.e. using FireFlash with the boot and recovery images and two checkmarks will never allow me to boot into the original rom?
Just "for fun", here's what I see when I try to boot. Times are approximate:
orange 2 seconds, blue 8 seconds, orange 30 seconds, totally black screen 2 seconds, orange 1 second (kind of flickers), blue 3 seconds, TWRP comes up.
My reason for wanting to do this is to "prepare" for going to CM10 (or other) "soon" but not quite yet. I'd like to keep the original rom for now and not wipe any data. Maybe this goal is impossible?
Thanks for your help.
sga999 said:
I can do that. But I'm curious to know why you're recommending this. Is it because I had problems booting up the old 8.1.4 rom and you just want me to try some other rom? Or is it that you know that what I did will never work, i.e. using FireFlash with the boot and recovery images and two checkmarks will never allow me to boot into the original rom?
Just "for fun", here's what I see when I try to boot. Times are approximate:
orange 2 seconds, blue 8 seconds, orange 30 seconds, totally black screen 2 seconds, orange 1 second (kind of flickers), blue 3 seconds, TWRP comes up.
My reason for wanting to do this is to "prepare" for going to CM10 (or other) "soon" but not quite yet. I'd like to keep the original rom for now and not wipe any data. Maybe this goal is impossible?
Thanks for your help.
Click to expand...
Click to collapse
Your system is broken for some reason the present method just does that. Flash Hashcode`s 8.4.1 zip. Disable OTA`s with kindlefire FirstAide or Free your kindle http://forum.xda-developers.com/showthread.php?t=2072198 or even Soupkit http://forum.xda-developers.com/showthread.php?t=2162973 . YOU MUST WIPE. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash Rom.zip disable OTA`s before enabling wifi or you will go in circles.
Thepooch said:
Your system is broken for some reason the present method just does that. Flash Hashcode`s 8.4.1 zip. Disable OTA`s with kindlefire FirstAide or Free your kindle http://forum.xda-developers.com/showthread.php?t=2072198 or even Soupkit http://forum.xda-developers.com/showthread.php?t=2162973 . YOU MUST WIPE. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash Rom.zip disable OTA`s before enabling wifi or you will go in circles.
Click to expand...
Click to collapse
Thanks, Thepooch. If I have to wipe anyway, I may as well just go to CM10 now. The main thing I wanted to know was whether I had done something wrong or whether what I tried to do (i.e. not install a new rom and just boot into the original rom) cannot be accomplished by anyone. I think you are saying the latter, right?
I appreciate all the help you've given me!
sga999 said:
Thanks, Thepooch. If I have to wipe anyway, I may as well just go to CM10 now. The main thing I wanted to know was whether I had done something wrong or whether what I tried to do (i.e. not install a new rom and just boot into the original rom) cannot be accomplished by anyone. I think you are saying the latter, right?
I appreciate all the help you've given me!
Click to expand...
Click to collapse
Well you got a free thanks so make sure you hit mine as well. I don`t believe you did anything wrong but I really could not tell you for sure. I have been stuck just where you are a couple times and I know I did everything right. Others I have helped became stuck the same way because Amazon has been diddling around with the boot for the last three updates. I can only assume that some encrypted part of the framework is running a stack check resulting in the system appearing broken. So yes it would be best to have something to flash before starting this process.
Thepooch said:
Well you got a free thanks so make sure you hit mine as well. I don`t believe you did anything wrong but I really could not tell you for sure. I have been stuck just where you are a couple times and I know I did everything right. Others I have helped became stuck the same way because Amazon has been diddling around with the boot for the last three updates. I can only assume that some encrypted part of the framework is running a stack check resulting in the system appearing broken. So yes it would be best to have something to flash before starting this process.
Click to expand...
Click to collapse
Thepooch, it helps to know that you and others ran into this. I did read posts that were similar, but I never was sure if anyone found an answer or knew what went wrong. This is a friend's Kindle that she got in December. I got it rooted for her back then, and I did whatever was necessary to not get OTA's. So it's way back on release 8.1.4. So I don't think Amazon's last 3 updates would have any bearing on this. But who knows! Again, thanks.
sga999 said:
Thepooch, it helps to know that you and others ran into this. I did read posts that were similar, but I never was sure if anyone found an answer or knew what went wrong. This is a friend's Kindle that she got in December. I got it rooted for her back then, and I did whatever was necessary to not get OTA's. So it's way back on release 8.1.4. So I don't think Amazon's last 3 updates would have any bearing on this. But who knows! Again, thanks.
Click to expand...
Click to collapse
You will have issues rolling it back that far, just saying there are changes that likely if not done properly will leave you stuck again. My suggestion is to flash 8.4.1 then create a solid backup when booted normal giving yourself a safety net in the event of a mishap.
Thepooch said:
You will have issues rolling it back that far, just saying there are changes that likely if not done properly will leave you stuck again. My suggestion is to flash 8.4.1 then create a solid backup when booted normal giving yourself a safety net in the event of a mishap.
Click to expand...
Click to collapse
Thepooch, I'm not sure if this is interesting to you at all, but I experimented a little and learned something. As you suggested, I flashed 8.4.1 and decided to try an unusual step.
After I used Fire Flash yesterday and booted into TWRP, I immediately created a backup. But it turned out to be no good in the sense that restoring it did not help me fix the problem of not being able to boot into the 8.1.4 (old) rom (I could only boot into TWRP). But now that I was on 8.4.1, I did a restore of ONLY the data from that old 8.1.4 backup. It seems fine so far, except for Google Play app, which just exits as soon as I execute it.....it's not a big deal to fix that. (There may be other issues, but I haven't hit anything else yet).
So....it seems like something is bad in either the boot or the system portions of the backup. It's probably system since it has framework, which you had mentioned might be causing the problem. Again, this may not be interesting, but I thought I'd let you know.
Makes sense google play rarely works from my restored backups and your system was in good shape if you flashed the 8.4.1 zip prior to restoring data.
Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP with 8.4.3
Has anyone attempted Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP running 8.4.3? If so, were you successful? If you were successful did you follow the procedure defined here or did you have to deviate? If you had to deviate, what were the deviations? Thanks!
How to root kindle fire any version (including 8.4.3) ONE CLICK
Hi I need some help.
KFHD 8.9, non-us user, but bought at amazon, i am unsure of the exact version.
ADB worked ok, device showed there. BUT "fastboot devices" didnt really show anything at all. Still I went ahead with it. Rooted using bin4ry, qemu did not work at all, permission denied error.
I did everything up to the point of flashing the freedom-rom and twrp through fireflash. It did not have 8.1.4 bootloader, so I checked the box, checked the other one and left all else as is. It seemed to flash ok. Then I rebooted,,, and its stuck on orange kindlefire logo, forever. doesn't matter what volumes i hold. tried rebooting and everything.
Now I dont really know what to do... any ideas?
Getting errors trying to install the drivers from the QEMU zip file, so no device ( sdcard ) access from recovery and the Advanced...sideload option is not working either.
I'm on windows 8, when plugging in the KFHD89 to my laptop, I see the kindle show up, but I have the yellow explanation sign. When I try to update driver software, i get error it can't update Windows ADB.
Between windows 8 and ubuntu, I've been able to get fastboot working enough to get all the files loaded...but for the lift of me !!! my copy of CM10.1 and gapps.zip are not seen via recovery...AND...I get stuck at Blue boot logo...so I'm sort stuck in recovery and need to get drivers sorted between windows and/or ubuntu so I can copy the .zip files over.
EDIT: #6 from http://forum.xda-developers.com/showthread.php?t=2277105 helped me out. I was starting ADB Sideload and connecting USB out of sequence. Followed directions and it worked.
I received a Fire 5th gen running stock Fire OS v5.1.3. I have only turned it on so far. I have not connected it to WIFI, I have not installed anything, I have not altered it from the factory default state in any way. I am brand new to customizing Android. I've spent the better part of 3 days digging through threads and watching videos, and as of right now my head is spinning. Information is fragmented and I am not sure how to put it all together.
I would greatly appreciate any help that will set me in the right direction.
Firstly, do I have a KFFOWI | Ford device? I have searched the settings and options and all I can find is "Device Model - Fire (5th Generation)". Based on THIS it would seem that all current Fire 7 models are "KFFOWI", but wanted to ask the experts of XDA before proceeding.
I want to flash the unofficial CM 12.1 ROM. I have heard good things about CM but if another ROM is recommended, please do not hesitate to let me know about it. My goal is to get away from Fire OS, but beyond that I am a simple user who won't do a lot of heavy app toying. After reading about how to Flash CM, I have become rather confused. The instructions say that on Fire OS >= 5.1.1 to use FlashFire 0.5.0. I Googled that and found the FlashFire app in the Playstore. The app says it requires Root access. Am I correct to assume that I can go no further without gaining Root? If that is so then I must downgrade from 5.1.3 to 5.1.2 using THIS information?
If this is correct, after downgrading what is the best way to gain Root (THIS tool?) After gaining Root access, how do I proceed with the CM install? I do apologize, but I find the unofficial CM 12.1 instructions (linked above) are written for someone who has done this before. I have not and am perhaps seeking a simpler guide with basic steps. I just feel overwhelmed and a bit fearful, I want to make sure I do this right and that the process is fun! For example, how do I install FlashFire without having the Playstore installed? I found a video for installing the Playstore (Root Junkies) but it seems to include tools based on Fire OS 5.1.1.
I hope this wasn't too long of a post. To summarize, I am assuming I need to do the following but am unsure exactly how to proceed.
1. Downgrade from 5.1.3 to 5.1.2
2. Gain Root
3. Install the Playstore to install FlashFire, then use FlashFire to flash files from an external mSD to install CM 12.1
What else am I missing? Please help me to connect the dots!
Thank you for reading!
Blastyrant said:
I received a Fire 5th gen running stock Fire OS v5.1.3. I have only turned it on so far. I have not connected it to WIFI, I have not installed anything, I have not altered it from the factory default state in any way. I am brand new to customizing Android. I've spent the better part of 3 days digging through threads and watching videos, and as of right now my head is spinning. Information is fragmented and I am not sure how to put it all together.
I would greatly appreciate any help that will set me in the right direction.
Firstly, do I have a KFFOWI | Ford device? I have searched the settings and options and all I can find is "Device Model - Fire (5th Generation)". Based on THIS it would seem that all current Fire 7 models are "KFFOWI", but wanted to ask the experts of XDA before proceeding.
I want to flash the unofficial CM 12.1 ROM. I have heard good things about CM but if another ROM is recommended, please do not hesitate to let me know about it. My goal is to get away from Fire OS, but beyond that I am a simple user who won't do a lot of heavy app toying. After reading about how to Flash CM, I have become rather confused. The instructions say that on Fire OS >= 5.1.1 to use FlashFire 0.5.0. I Googled that and found the FlashFire app in the Playstore. The app says it requires Root access. Am I correct to assume that I can go no further without gaining Root? If that is so then I must downgrade from 5.1.3 to 5.1.2 using THIS information?
If this is correct, after downgrading what is the best way to gain Root (THIS tool?) After gaining Root access, how do I proceed with the CM install? I do apologize, but I find the unofficial CM 12.1 instructions (linked above) are written for someone who has done this before. I have not and am perhaps seeking a simpler guide with basic steps. I just feel overwhelmed and a bit fearful, I want to make sure I do this right and that the process is fun! For example, how do I install FlashFire without having the Playstore installed? I found a video for installing the Playstore (Root Junkies) but it seems to include tools based on Fire OS 5.1.1.
I hope this wasn't too long of a post. To summarize, I am assuming I need to do the following but am unsure exactly how to proceed.
1. Downgrade from 5.1.3 to 5.1.2
2. Gain Root
3. Install the Playstore to install FlashFire, then use FlashFire to flash files from an external mSD to install CM 12.1
What else am I missing? Please help me to connect the dots!
Thank you for reading!
Click to expand...
Click to collapse
FlashFire can be sideloaded; no need to install the Play Store or any other Google components before/after rooting.
http://www.apkmirror.com/apk/chainfire/flashfire/
I can not get any driver installs to take. I have not been able to start the 5.1.2 downgrade to attempt rooting. This has become rather frustrating.
Installed the Kindle Fire USB Drivers and the device becomes recognized. When I plug it in an "auto run" pop-up appears. But I am unable to connect via ADB to begin to downgrade. I have USB debugging turned on and followed the instructions in the Root Junky video guide. After that I restored my system. I tried to associate the driver via Device Manager but am always unable. My Win7 machine is unable to find them when I search as per the many instructions I've read thus far. From what I've read and seen, I should have an option in the "let me pick from a list of device drivers on my computer" button that says "Android devices" or "mobile" and those (or anything even remotely like them) are never in the list.
I then ran the 15 sec ADB Installer v1.4.3. This copys 0 files, when in THIS video guide it shows it copying 4 files. When asked to "install the USB drivers" the program gives me an error log that says "Invalid command or parameter", which has something to do with DPInst_x64.exe. I do not have the permissions to post in the discussion thread for this tool to ask what I am doing wrong.
After that I tried THIS method. When I browse the extracted folder I get a message that "Windows was unable to install your Fire" and "Windows could not find driver software for your device".
WARNING Do not downgrade below 5.1.2. It has been confirmed to brick the device.
Here is a status update for anyone who is attempting to do the same thing and has been running into obstacles.
I uninstalled all of the drivers. I did this with a system restore. But you could just as easily do this manually. I've also seen some "wipe" tools online that claim to rip out all Android drivers, maybe try one of those if needed? Once they were gone I turned the Fire 7 ADB debug mode on. I then installed the Kindle drivers from Amazon. Then I plugged in the Fire 7 via USB and let it "install drivers". I checked Device manager and this time ADB was showing up. I then shut down the Fire, held volume down+power to boot into Recovery Mode. I had to then manually point the Fire in Device Manager to the correct drivers. Then I sideloaded the 5.1.2 firmware and it has flashed successfully. Next is Root and then CM12.1.
Here is what I did:
To start, it was running 5.1.3 out of the box. I never connected it to WIFI, never altered it, never updated it, etc. It was a stock Fire 7 Gen 5.
1. Delete all previous Amazon driver installations (if required)
2. Install THESE drivers (I'm on Win7)
3. Enable ADB debugging on your Fire tablet (Info can be found here)
4. Download and extract THESE ADB Fast Boot Files from Root Junkys.
5. Download the v5.1.2 OS build from HERE and then verify the SHA1 and MD5 checksums with THIS free online tool.
SHA1: 66B5423725B79CEB0D5866FA32FF414A99A4B50A
MD5: 5B0DCC957DEF3ACCFF58BF33794D6D88
6. Connect your powered-off (turned off, in the off state, etc) Fire 7 5th Gen tablet via USB and then hold volume down+power to boot into Recovery Mode.
7. (perhaps optional) If Fire is not listed as a usable device in Device Manager when in Recovery Mode (or has that warning icon next to it), you'll need to manually point it to the drivers you installed.
.....Select Other Devices > Fire and then Right Click it and choose Update Driver
.....Click the button to let you pick from a list of drivers on your computer. Find the Amazon device (Fire Device) in the list and then choose "from disk".
.....Navigate to the default driver install folder (C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers)
.....Select Android Composite ADB interface (this is for Stock ROM, recovery/adb sideload)
More info for step 7 can be found HERE under "Connecting Your Tablet to Your Computer"
8. Hold Select and Right Click anywhere in the extracted ADB Fast Boot Files folder and choose "Open Command Window Here" from the context menu.
9. In the command window type "adb sideload <path to the v5.1.2 firmware>"
.....IE: C:\Users\MyPC\Desktop\Amazon Fire\ADB FASTBOOT FILES WINDOWS>adb sideload "C:\Users\MYPC\Desktop\Amazon Fire\update-kindle-global-37.5.4.2_user_542168620.bin"
.....You can make this easier on yourself by typing "adb sideload " and then drag-drop the v5.1.2 file into the command widow and the correct path will be automatically populated for you.
.....Click Enter, and allow the process to run its course
You should now be running v5.1.2 stock firmware, which is fully rootable. Next up is rooting and then installing CM 12.1.
I'll start reading up on rooting from THIS thread. I'll make a post with what I did after I have it working.
Rooting...
I watched THIS Root Junkys tutorial video for gaining root access. The Super Tool successfully installed KingRoot, but that application is unable to root this device. So what I did was grab the most recent (as of today: v4.9.5) from THIS thread. I renamed that file to Kingroot.apk and replaced the old version found in the Super Tool "apps" directory. I then went through the normal installation procedure and have gained root. To verify this I blocked OTB updates and disabled lock-screen advertisements.
Next up is installing CM 12.1.
Installing Unofficial Cyanogenmod v12.1 (7/10/2016):
I used Root Junkys Super Tool to install Google Play. The tool does eveything for you so there is no need to type out the steps. You can get that tool HERE
Once Google Play was installed, I linked an account and downloaded/installed the current version of FlashFire.
To install CM 12.1 I followed the instructions in THIS thread.
Next up is tweaking CM to my liking and getting the Play store installed.
I apparently picked the wrong GApps package so it did not install. Now I am trying to sideload the nano or pico package but they fail to verify the file signature. Any suggestions?
Blastyrant said:
I apparently picked the wrong GApps package so it did not install. Now I am trying to sideload the nano or pico package but they fail to verify the file signature. Any suggestions?
Click to expand...
Click to collapse
Likely an incompatible package. Verify ARM/5.1/nano. You can check the file integrity in advance by downloading and opening the MD5 checksum file (available for every package) in a text editor. Then use a third party tool like ES File Explorer to see if the signatures match.
Davey126 said:
Likely an incompatible package. Verify ARM/5.1/nano. You can check the file integrity in advance by downloading and opening the MD5 checksum file (available for every package) in a text editor. Then use a third party tool like ES File Explorer to see if the signatures match.
Click to expand...
Click to collapse
Thank you for the reply. I re-downloaded the file again and made sure I had ARM/5.1/nano. I grabbed the MD5 checksum file and verified that the signatures match. The adb sideload continues to fail at 46% with the error "failed to verify whole-file signature" and "signature verification failed".
I also tried to sideload FlashFire v0.52 and received an error "Footer is wrong" and "Signature verification failed". I also verified the MD5 checksum.
I'm going to dig a bit and hopefully uncover a solution through research. Any additional information or suggestions would be greatly appreciated, as I would rather fix this without reverting to stock o/s and then redoing the entire process.
I gave in and re-did the whole process. I got CM installed and Google Play running w/o issue this time. =)
With CM installed, is there a safe way to get rid of the "Amazon" text that shows on before each boot?
Blastyrant said:
Thank you for the reply. I re-downloaded the file again and made sure I had ARM/5.1/nano. I grabbed the MD5 checksum file and verified that the signatures match. The adb sideload continues to fail at 46% with the error "failed to verify whole-file signature" and "signature verification failed".
I also tried to sideload FlashFire v0.52 and received an error "Footer is wrong" and "Signature verification failed". I also verified the MD5 checksum.
I'm going to dig a bit and hopefully uncover a solution through research. Any additional information or suggestions would be greatly appreciated, as I would rather fix this without reverting to stock o/s and then redoing the entire process.
Click to expand...
Click to collapse
Blastyrant said:
I gave in and re-did the whole process. I got CM installed and Google Play running w/o issue this time. =)
With CM installed, is there a safe way to get rid of the "Amazon" text that shows on before each boot?
Click to expand...
Click to collapse
Wait - you are trying to sideload GAaps (and apparently FlashFire) via the stock recovery menu? Can't do that on this device. GAaps zips and other items targeting the system partition get installed via FlashFire which can be obtained from apkmirror or other trustworthy download site if running on a device that lacks Play store access.
Amazon spash screen originates from locked bootloader and can not be replaced.
I just completed the same process for a 5.1.1 Fire 7 5th Gen. Instead of messing with the 5.1.1 rooting, which was not the exact same process as 5.1.2, I simply upgraded to 5.1.2 (using the same methods I used to downgrade from 5.1.3) and then completed the exact same steps.
CM 12.1 is working great on both devices. =)
Davey126 said:
Wait - you are trying to sideload GAaps (and apparently FlashFire) via the stock recovery menu? Can't do that on this device. GAaps zips and other items targeting the system partition get installed via FlashFire which can be obtained from apkmirror or other trustworthy download site if running on a device that lacks Play store access.
Amazon spash screen originates from locked bootloader and can not be replaced.
Click to expand...
Click to collapse
This is my first time ever trying to hack an Android device. I had chosen the wrong GApps package the 1st time and thought I could sideload the correct one to get it to install. Again, I am very new to this so I do not know what works, what doesn't, or why. As I am faltering I am taking the time to research a bit in an effort to educate myself so that my next Android experiment is that much more fun!
Thank you for the information!
Blastyrant said:
I just completed the same process for a 5.1.1 Fire 7 5th Gen. Instead of messing with the 5.1.1 rooting, which was not the exact same process as 5.1.2, I simply upgraded to 5.1.2 (using the same methods I used to downgrade from 5.1.3) and then completed the exact same steps.
CM 12.1 is working great on both devices. =)
Click to expand...
Click to collapse
Blastyrant said:
This is my first time ever trying to hack an Android device. I had chosen the wrong GApps package the 1st time and thought I could sideload the correct one to get it to install. Again, I am very new to this so I do not know what works, what doesn't, or why. As I am faltering I am taking the time to research a bit in an effort to educate myself so that my next Android experiment is that much more fun!
Thank you for the information!
Click to expand...
Click to collapse
Glad to hear all is well on both devices and that you are taking time to research and understand the 'why' behind the 'what' & 'how'. Makes the experience much more enjoyable IMO. Not to mention less error prone.
BTW - root procedures are identical for 5.1.1/5.1.2 but it's easy to think they are different reading through the hundreds of contributor posts, some with conflicting information.
I want to use Titanium Backup to backup/restore when it comes time to update CM 12.1. I downloaded it but it says "Root access: Failed". I then downloaded and installed Root Checker by Super User and it says I am rooted. It reports SU Found (/system/bin/su/system/xbin/su) and Busy Box is installed (/sbin, vendor/bin, /system/sbin, /system/bin, /system/xbin). I also ticked on Root access for apps in the Developer options of CM 12.1. I am assuming that I need SuperSU to provide root access to applications?
I installed SuperSU and on launch it asks to update the binary. This always fails. The link it provides takes me to http://supersu.com/insteadbinaryfile.html. It is here that I am getting confused.
Method 2: replace system/ Xbin with SU file, Steps : <-- Where to I obtain the SU file?
Step 1: Install Root.Explorer APK. <-- Is this the app by by Speed Software that cost $3.99?
Step 2: Rename Su to .SU
Step 3: Copy .SU to system/xbin
Step 4: Authorize Su (chmod 0777 .su) <-- I am unsure how to do this.
Step 5: delete the other SU files, such as ksu, etc. <-- etc means what exactly? What are the files I would need to delete?
Step 6: Rename.SU to SU
Step 7: Go back to the desktop to delete the other authorization apps <-- Which other authorization apps?
I feel like I am making something easy into something much harder. Any help would be greatly appreciated!
I uninstalled Titanium Backup and SuperSU. I then ticked off root for apps in developer settings, ticked it back on, and rebooted the device. Then I reinstalled SuperSU and this time clicked the "expert" button on first start. It installed and is working. Then I installed Titanium backup and that is also working. So looks like it was just an order of operations needed to solve my problem.
Revisiting this old thread. I am going to upgrade to the Fire Nexus ROM and post my steps.
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714