Ok I have packaged up the 6.2.1 update with only the files changed or modified from 6.2
Included in this is:
unsecure boot image
busybox
su binary
and su apk
This is for anyone with root and TWRP already installed and still on 6.2
this will not format system it will just update the need files.
So all added apps will remain and all data will be intact.
Install and wipe dalvik and cache, then reboot
Download
This had already been done in both secure an unsecure boot images. Wait, sorry, didn't see the modded from 6.2 part...
this is only to update 6.2 to 6.2.1 without wiping the system partition. There was no need to flash the entire update as large portion of the package was the same when compared.
This is also to save the hassel of having to reinstall / reconfig everthing.
Yeah, I figured that out after I posted. My appologies. This should make it a little easier.
Won't get to it for a week because of the holiday but this sounds great. But just to be sure. I'm on 6.2 only right now. I download and install this and I magically get 6.2.1 without being too worry over losing root or changes I made to the /system partition, correct? Does this also mean I don't have to worry about the OTA update coming along and messing things up?
Sent from my HTC Flyer P512 using Xparent Purple Tapatalk
yes you dont have to worry about anything that was added to or modiied on your 6.2 it will remain, as for the OTA update, I cant verify that it wont end up trying to install, but if it actually verifies the system first then you should be good to go.
I did my wifes kindle yesterday and it hasnt tried to update at this point.
Ok, this POS just bricked my Kindle Fire.
Do NOT INSTALL!!!!!
Installed via TWRP.
Rebooted.
Got stuck at the "Kindle Fire" boot logo.
Check the bootmode via the Kindle Fire Utility and tried to change it.
Now all I get is the FireFirefire logo and NOTHING ELSE!!!
No ADB and NO fastboot.
Edit: was able to get ADB and fastbook working thanks to this post (http://forum.xda-developers.com/showthread.php?p=20631342#post20631342), though something in this update destroyed my ability to get into TWRP. Still: Do NOT flash.
andTab said:
Ok, this POS just bricked my Kindle Fire.
Do NOT INSTALL!!!!!
Installed via TWRP.
Rebooted.
Got stuck at the "Kindle Fire" boot logo.
Check the bootmode via the Kindle Fire Utility and tried to change it.
Now all I get is the FireFirefire logo and NOTHING ELSE!!!
No ADB and NO fastboot.
Edit: was able to get ADB and fastbook working thanks to this post (http://forum.xda-developers.com/showthread.php?p=20631342#post20631342), though something in this update destroyed my ability to get into TWRP. Still: Do NOT flash.
Click to expand...
Click to collapse
Wow really this is only the software update has nothing to do with the bootmode. This will take a while to boot as the dalvik needs rebuilt but should boot within 5 minutes.
I tested this several (at least 20) times after restoring my system to the 6.2 backup everytime and never had an issue.
nfinitefx45 said:
Wow really this is only the software update has nothing to do with the bootmode. This will take a while to boot as the dalvik needs rebuilt but should boot within 5 minutes.
I tested this several (at least 20) times after restoring my system to the 6.2 backup everytime and never had an issue.
Click to expand...
Click to collapse
Sorry if I was a little harsh, but I was - hopefully understandably - quite upset.
This update did not work for me and bricked my fire installation.
I left it on for at least 20-30 minutes to give it a chance to boot. No dice.
Maybe you included something specific to your KF?
andTab said:
Sorry if I was a little harsh, but I was - hopefully understandably - quite upset.
This update did not work for me and bricked my fire installation.
I left it on for at least 20-30 minutes to give it a chance to boot. No dice.
Maybe you included something specific to your KF?
Click to expand...
Click to collapse
no nothing other then the updated files, busybox, SU, where added.
You did follow my instructions and ONLY wiped dalvic/cache correct?
this is not a full install it is only for updating/upgrading your current version.
By the way I am not new to android so I do know what I am doing and have run this now on 4 more devices for friends without issue.
I am sorry for your problems but I can not replicate this issue that you have seen.
THANKS!
I chanced it, installed per instructions, and it worked fine. I'd been holding off on 6.2.1 cause I didn't want to re-do all the work I'd done setting up my Fire with the Google services. This is exactly what I wanted -- a way to go to 6.2.1 without wiping. The only oddity is a few apps have lost their icons (like XDA Premium, PocketCloud, and one more). They now have a no-name icon with just little black squares. Easily remedied with a reinstall of the apps I'm sure.
jb0ne said:
I chanced it, installed per instructions, and it worked fine. I'd been holding off on 6.2.1 cause I didn't want to re-do all the work I'd done setting up my Fire with the Google services. This is exactly what I wanted -- a way to go to 6.2.1 without wiping. The only oddity is a few apps have lost their icons (like XDA Premium, PocketCloud, and one more). They now have a no-name icon with just little black squares. Easily remedied with a reinstall of the apps I'm sure.
Click to expand...
Click to collapse
Glad to hear it worked for you, and yes a reinstall or update install should correct the issue.
Sure did! Thanks a lot for putting this together for us. 6.2.1 is much snappier but I really didn't want to jockey this thing anymore, I wanted to use it. This took less than 10 minutes.
Sent from my Kindle Fire using xda premium
Would like you to know that my Kindle Fire installed the update and is now back to a stock state (need to re-root, and install firefirefire and TWRP).
pyrostic said:
Would like you to know that my Kindle Fire installed the update and is now back to a stock state (need to re-root, and install firefirefire and TWRP).
Click to expand...
Click to collapse
Sorry to hear that it got pushed onto you, still working fine on my wifes, hasnt updated since I installed this update, but you can never tell untill we get a way to bypass the FOTA updates
could you do the same for 6.2.2 please ?
6.2.2 update amazon:
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.2.2_D01E_3205220.bin
that would be greatly appreciated by so many users !!!
thank you very much !
Update for 6.2.2 released
nfinitefx45 said:
Update for 6.2.2 released
Click to expand...
Click to collapse
you'r incredible !!!
thank you !
So I put Jelly Bean on the Fire works great... Never had any problems... Flashed this thing tons of times. All kinds of roms. So when I went to go back to stock to read some books I had purchased on Amazon, the Fire would not reboot in to recovery. I was like Hmm ok.... So I booted up Kindle Fire Utility. And it sees it. It goes to write the files to reinstall TWRP. And then all of a sudden it says error. can't write file. Permission denied? I have no clue how to get around this. Anyone know what to do? I can get to the Jelly Bean rom everytime, and do whatever... The device has Super User. It is not in a constant reboot. It is fine, even with KFU, the device reboots when it is told to, but it will not write anything to it? Is there anything I can do? Is this a situation where I need a factory cable? I have been installing crap and working on this thing all day.
Biasmania said:
So I put Jelly Bean on the Fire works great... Never had any problems... Flashed this thing tons of times. All kinds of roms. So when I went to go back to stock to read some books I had purchased on Amazon, the Fire would not reboot in to recovery. I was like Hmm ok.... So I booted up Kindle Fire Utility. And it sees it. It goes to write the files to reinstall TWRP. And then all of a sudden it says error. can't write file. Permission denied? I have no clue how to get around this. Anyone know what to do? I can get to the Jelly Bean rom everytime, and do whatever... The device has Super User. It is not in a constant reboot. It is fine, even with KFU, the device reboots when it is told to, but it will not write anything to it? Is there anything I can do? Is this a situation where I need a factory cable? I have been installing crap and working on this thing all day.
Click to expand...
Click to collapse
Make sure under your kindle setting under device you have allow installation from unknown sources then try again and uhh are you sure your still rooted cause flashing stock wipes out fff twrp and root permissions??
My roommate gave me his Kindle 8.9 to play with and root if possible. I had been successful at rooting, flashing TWRP, but couldn't get a custom ROM to flash. Being stupid, I didn't do a test flash first, so I ended up wiping the system and storage, so I couldn't boot into anything aside from TWRP and ADB was unresponsive. It also caused a power error, causing the device to turn back on immediately when powered down.
I acquired two of these tablets from eBay, for $35.00 a Piece, in like-new condition. I replaced the one I broke and bought one for myself. The problem I had was, there is no single guide which 1) lists the current root method for this tablet 2) The files needed to flash a custom recovery once root is gained 3) the most up to date TWRP recovery available. I read a lot of stuff on XDA. I read a lot of stuff elsewhere. The root methods listed in most every thread, no longer root. It was very hard to find an updated TWRP recovery, but thanks to @ong14, who pointed me to a single post, that was possible. So, I created this guide as a single go to for the current methods to root, TWRP and install a custom ROM.
***THIS GUIDE WILL ROOT YOUR DEVICE AND INSTALL A CUSTOM RECOVERY FOR THE AMAZON HD 8.9 JEM TABLET ONLY***
This method is used with ADB which requires Windows. Please make sure the proper drivers are installed before performing these steps. Required files for rooting and custom recovery installation are available at the bottom of this post. Please see respective links for custom ROMs. I did not create any of this software or the files. I'm not responsible if your device is damaged or bricked.
1. Enable the installation of files from unknown sources in Settings > security.
2. Enable ADB debugging from Settings > device.
3. Using the Silk Browser, go to Kingroot.net and download, install and run the APK. Also from Silk, download and install Total Commander File manager and grant it root access. Once you do that, download FireFlash11.apk at the bottom of this post. Open Total Commander and navigate to /sdcard > Downloads. Install FireFlash, open it and grant it root access to use later. (You can locate FireFlash from Home > Apps.)
5. Download the rest of the files at the bottom of this post and place into a folder of your choice on your desktop. Then go here and download this file and this file and place them in that same folder. Then move the following files to your Kindle: freedom-boot-8.4.6, u-boot-prod-8.1.4, stack and kfhd8-twrp-3.0.2-2-recovery.img.
5. Please follow the steps below from @MeowDude which will tell you how to flash a custom recovery to your Kindle.
now if you moved the files straight to your kindle, then they should be on the sd card, if you downloaded these through silk, they'll be in the downloads folder in your sd card. Now open FlashFire11, and give it root access (if you haven't yet). You should be greeted with a somewhat complicated looking wall of text and checkboxes.
!IMPORTANT!
| | |
\/ \/ \/
1. So, let me now guide you through this app, first of all, there should be red print informing you that you're not on the 8.1.4 bootloader or something like that, so click on the checkbox (at the upper right. The one that says "install kfhd8uboot-prod-8.1.4.img or something like that)
2. Now go down, and you'll see some text that says "Boot Partition Image (boot.img) and a box under it that says "NOT FLASHED" tap it. it should bring up a file manager-like list. scroll down until you see your already downloaded "kfhd8freedom-boot-8.4.6.img" , and tap/select it. (I know it says 8.4.6, IT WORKS ON 8.5.1!).
now go slightly under it and check "apply stack override".
*Next, Go under that to find a line that says "Recover Partition Image (Recovery.img), and slightly under it a box that says "NOT FLASHED" tap that, and again, you'll be greeted with a list-like file manager. scroll down until you see "kfhd8-twrp-3.0.2-2-recovery.img" and tap/select it. last part! go slightly under that and tap the check box next to "disable auto recovery update".
*Now that you have all you options in order, verify that you have them in order, and correctly selected (refer back if needed) and scroll down until you see at the bottom, a box that will install/flash all these things, it will say something like "Execute Flash Script" tap it, and your all set. if you want to boot into recovery (immediately after flashing), go right under that box to find another box that says "reboot into recovery" click it, and wait a sec, your screen will black out, and you will first see the normal kindle fire logo, then a blue one, then some glitchy looking stuff, then it should show a TeamWin logo, and go into recovery.
NOTE: If you don't flash your device with android, the stock Amazon os will erase the recovery, so NEVER REBOOT INTO RECOVERY USING FIREFLASH! Only right after you install/re-install recovery.
Click to expand...
Click to collapse
You should boot back to recovery at this point and do a factory reset. Here is how to do that below:
1. Power off your Kindle.
2. Once off, press first and hold the volume down button, then the power button. Hold them both down until the device boots to the BLUE Kindle logo. Then release the power button then the volume down button.
3. You should see the "Team Win" logo come across the screen. Tap on wipe, advanced, and choose dalvik, data and cache. Ten swipe the wipe button. DO NOT SELECT THE SYSTEM OR INTERNAL STORAGE OPTION. This will do a clean install of FireOS 8.5.1 and get rid of Kingroot.
Installing a custom ROM
You can now use FireOS as you were able to before, but I was unable to get the necessary Gapps to work with each other properly. You can try, but I recommend installing a custom ROM. I've tried two so far and can confirm they both work. I will list the links below where you can get the ROMs and installation instructions.
1. The Candy Rom, based off of Lollipop 5.1.1, works on this tablet. Root is built in so you don't need to install or flash SuperSU, but the post does say you can flash it. I've had a lot of trouble with custom 5.1.1 ROMs when it comes to launchers. Be warned it doesn't play nice with Nova and will cause the SystemUI to crash and restart over and over.
2. Unofficial CyanogenMod (CM 13). I currently use this ROM. Root is also built in. I have had trouble getting used to the permissions for apps. I have to go in and set them myself. If you can't get the Google app to sign you in, go to settings > apps > Google App > permissions > grant all permissions. I cannot get Hangouts to work, but the dialer works perfect. I'm not sure if either of those issues are a fault of mine or just a fluke.
I own 3 Amazon tablets: Amazon Fire 7, rooted with a custom ROM. Amazon Fire HD 8, but unfortunately there's no root for it yet. Amazon Kindle Fire HD 8.9, rooted, custom recovery and ROM. I have had great fun 'hacking' these things. I hate FireOS, but I will give Amazon credit for making some really bad ass tablets.
I didn't really feel too happy with the CM 13 ROM. It was pretty sluggish. Just overall performance was less than it should've been. So I decided to try another CM13 (Marshmallow 6.0.1) build by Temasek . This is by far the best ROM I've ever worked with on Kindle (Sorry Fire Nexus). Performance is off the chart. There's little to no lag. You HAVE to flash SuperSu, but it works really well. You don't see the App icon, just tap settings and SuperSU is listed. You also don't need to flash Viper4Android, already comes installed. Just select it in settings, grant it root access and select yes to download the driver. It will take a minute or two for it to update, but reboot when done and configure your Viper. Just make sure you have BusyBox installed and updated. You can get it from the play store. There are more settings and customization options I can list. Truly an awesome, well built ROM.
First off, I'd like to thank you for taking the time to post your very good guide for us new guys. Another superb tutorial can be found here...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
Your and comwiz's guides that summarize MeowDude's excellent work are two of the best ones I've seen to date and they help us novices a lot.
I want to set my elderly father up with Google's new YouTube TV streaming service when I visit him after the holidays and they currently require an Android L device or better to activate the service and control their interface. All he had was a Kindle Fire HD 8.9 a relative gave him that he never uses, so he sent it to me a few days ago so I could modify it. I've read a few of your posts on this and other threads and you seem very impressed with Temasek's CM13 custom ROM, so that's good enough for me and the one I wanna try first. But I'm a little confused by your followup post when you say "you HAVE to flash SuperSu". Does this mean that one should root with that app instead of Kingroot as was described in your original guide? I'm also not totally clear on exactly where in the procedure BusyBox needs to be installed. Here's what I have done so far to date...
*performed factory reset on Kindle Fire HD 8.9 just to clean it up and get it back to stock
*installed ADB on PC and verified it communicates with the Fire HD (detects device and returns serial number)
*downloaded and installed Total Commander (nice looking file explorer at first glance, BTW)
*sideloaded Root Check and verified device is not rooted
*downloaded the following files to PC but have not yet transferred them to the Fire:
---NewKingrootV5.1.0_C176_B415_en_release_2017_05_11_20170511212237_105203.apk
---fireflash11.apk
---kfhd8-u-boot-prod-8.1.4.bin.img
---kfhd8-freedom-boot-8.4.6.img
---kfhd8-twrp-3.0.2-2-recovery.img
---stack
---SR5-SuperSU-v2.82-SR5-20171001224502.zip
---stericson.busybox.apk
---cm-13.0-20160827-V11-temasek-jem.zip
I think this is everything I need but I'm not yet comfortable enough with my current knowledge level to try rooting and flashing a custom ROM. If you or anybody else could tell me what I should do next or at least point me in the right direction that would be much appreciated. I figure it's better to ask some dumb noob questions now before I attempt anything rather than have to come back later and ask how to unbrick my tablet.
CornellEngineer said:
First off, I'd like to thank you for taking the time to post your very good guide for us new guys. Another superb tutorial can be found here...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
Your and comwiz's guides that summarize MeowDude's excellent work are two of the best ones I've seen to date and they help us novices a lot.
I want to set my elderly father up with Google's new YouTube TV streaming service when I visit him after the holidays and they currently require an Android L device or better to activate the service and control their interface. All he had was a Kindle Fire HD 8.9 a relative gave him that he never uses, so he sent it to me a few days ago so I could modify it. I've read a few of your posts on this and other threads and you seem very impressed with Temasek's CM13 custom ROM, so that's good enough for me and the one I wanna try first. But I'm a little confused by your followup post when you say "you HAVE to flash SuperSu". Does this mean that one should root with that app instead of Kingroot as was described in your original guide? I'm also not totally clear on exactly where in the procedure BusyBox needs to be installed. Here's what I have done so far to date...
*performed factory reset on Kindle Fire HD 8.9 just to clean it up and get it back to stock
*installed ADB on PC and verified it communicates with the Fire HD (detects device and returns serial number)
*downloaded and installed Total Commander (nice looking file explorer at first glance, BTW)
*sideloaded Root Check and verified device is not rooted
*downloaded the following files to PC but have not yet transferred them to the Fire:
---NewKingrootV5.1.0_C176_B415_en_release_2017_05_11_20170511212237_105203.apk
---fireflash11.apk
---kfhd8-u-boot-prod-8.1.4.bin.img
---kfhd8-freedom-boot-8.4.6.img
---kfhd8-twrp-3.0.2-2-recovery.img
---stack
---SR5-SuperSU-v2.82-SR5-20171001224502.zip
---stericson.busybox.apk
---cm-13.0-20160827-V11-temasek-jem.zip
I think this is everything I need but I'm not yet comfortable enough with my current knowledge level to try rooting and flashing a custom ROM. If you or anybody else could tell me what I should do next or at least point me in the right direction that would be much appreciated. I figure it's better to ask some dumb noob questions now before I attempt anything rather than have to come back later and ask how to unbrick my tablet.
Click to expand...
Click to collapse
"Root" is built into the ROM. But, it's not full root. So the ROM maker tells you to Flash SuperSU once the ROM is installed and functioning. You have to do that because you wipe the system (pretty much all of it) before you flash the ROM. That wipes Kingroot, root etc. until you flash the new ROM. You're on the right track exactly. Just make sure your files are placed properly and use FireFlash to install TWRP. Just follow all the steps exactly and it should be successful. The good thing about this method, it doesn't wipe your data to install the recovery.
Okay, DF...thanks. When researching Kingroot & SuperSU I came across a ton of external links about how to get rid of the former if it was used to originally root a device and replace it with the latter. I even found another XDA thread last night where you posted that you yourself spent many hours reading about how to do just that. It seemed like a lot of hoops to jump through so I thought maybe it was better just to use SuperSU to root in the first place and be done with it. But this was all probably before you tried the new ROM you're now using and are apparently liking a lot. It sounds like Temasek's ROM version automatically takes care of most/all of the Kingroot exorcism that gave you such a headache. Apparently on many devices you can install TWRP first and THEN root with SuperSU afterward but I gather the Kindle Fire's funky bootloader unfortunately doesn't permit this.
I'll just keep reading threads over and over again as well as outside reference articles on other sites like I have been so far. Some of it must be finally sinking in because some posts are actually finally starting to make a little sense and in some cases I now understand what a few folks did wrong to cause them problems. When the vast majority of the posts and articles I read make sense and not just some of them then I'll give it a shot. Appreciate the guidance.
Okie dokie, DF...just a quick status report on how we're doing following your new guide. So far, so good...used Kingroot to root the device no problem, verified it was rooted with Root Check, gave Total Commander (which I had installed a few days ago) root access, and downloaded and installed FireFlash. But when I opened the app and clicked on "allow" to have root privilege there was a minor glitch...although I could see the FireFlash menu in the background there was an error message saying it did not have root access and that it was going to close, even though Kingroot verified it as an app that had permission. Tried uninstalling and reinstalling a few times but kept getting the same error message. Finally I simply rebooted the device and it worked fine after that...so if there are any fellow noobs out there who are one step behind me (and heaven help you if you are) you might wanna try a simple reboot during this step if you experience a similar problem to see if that solves it.
Before I do anything else I'm gonna use ADB to create some images of several of the now-rooted stock partitions and save them to my PC just in case I eff something up later on. You did not mention this in your guide but this was summarized nicely by comwiz in his very similar tutorial...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
He also included many screenshots that one will see while following your guides...I found these visual aids to be very helpful in terms of what one could expect to see as you march through all the steps that you guys so graciously spent the time laying out for us newbies. I'm probably gonna hold off on installing TWRP and Temasek's custom ROM for a few days...I wanna read up more about TWRP and fastboot before I take the next baby steps. BTW, like you I just bought another used KFHD 8.9 in almost new condition on eBay today for about the same price that you paid...how's THAT for the ultimate "backup"???
Man, thank God for this XDA forum...no way I try this on my own without all the info and tools and help that experienced folks have taken the time to post here.
CornellEngineer said:
EDITED BY ME, "compjan"
Before I do anything else I'm gonna use ADB to create some images of several of the now-rooted stock partitions and save them to my PC just in case I eff something up later on.
Click to expand...
Click to collapse
PLEASE upload those images !!! if you are running 8.5.1 on a 32 gig model I NEED THEM !
compjan said:
PLEASE upload those images !!! if you are running 8.5.1 on a 32 gig model I NEED THEM !
Click to expand...
Click to collapse
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286
MeowDude said:
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286
Click to expand...
Click to collapse
iRoot doesn't work anymore. At least not when I tried. Regardless of the method used to root, the quicker to get rid of them, the better it makes me feel.
MeowDude said:
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286
Click to expand...
Click to collapse
um, i do not have a working 8.9 tablet. i screwed it up and had a red screen of death for a couple years now. i have been off work due to knee surgery and decided to see if there was a working fix. member sd_shadow has me OFF red screen, now i need to get back to stock BEFORE i start playing with it. that way i can fix it right then if i mess it up again.
SO, i need a copy of the 3 partitions to get back to stock.
UNLESS. . . . i can get the partitions out of the 8.5.1 BIN i grabbed from amazon. that is how sd_shadow ( THANK YOU SIR ! ) got me back to a NOT booting but hung at the fire logo. i flashed the bin to SYSTEM and now i need the other 2 partitions.
UPDATE: GOT IT UP AND RUNNING AS 8.1.4 ! ! !
wife wanted it stock, so i loaded the 8.5.1 update from amazon in the root directory of INTERNAL STORAGE. not i a folder. re-booted and it installed the 8.5.1 update. worked fine . . . EXCEPT . . . .
the built-in amazon app store was buggy as hell. so was the silk browser. gapps worked fine until a re-boot. then crashed as soon as i launched play store.
SO. . . . i'm backing up the 3 partitions and going to load a ROM on this puppy.
EDIT: there is a NEWER 8.5.1 "update" at amazon, it will NOT auto install via the "check for updates" button (afaik. and i tried it on 2 different 8.9's) . download it, copy it to the ROOT of the 8.9, not in a folder. reboot. it will install all by it's self. fixed all my stock problems!! END EDIT
I got CM13 installed on my 8.9 but then having issue.
a. Can't boot into custom recovery. With volume down hold + power button -> Kindle Fire orange -> Kindle Fire blue -> then it either boots back into CM13 or getting "Fast boot".
b. In CM13, i don't have root access. How so? Weird. I am always under the impression that every custom image will come with root access. I maybe wrong though.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
Well, my bad was I downloaded the wrong gapps, picked 7.1 instead of 6.0, so I wanted to boot back in recovery to install the correct gapps.
votinh said:
I got CM13 installed on my 8.9 but then having issue.
a. Can't boot into custom recovery. With volume down hold + power button -> Kindle Fire orange -> Kindle Fire blue -> then it either boots back into CM13 or getting "Fast boot".
b. In CM13, i don't have root access. How so? Weird. I am always under the impression that every custom image will come with root access. I maybe wrong though.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
Well, my bad was I downloaded the wrong gapps, picked 7.1 instead of 6.0, so I wanted to boot back in recovery to install the correct gapps.
Click to expand...
Click to collapse
If using temasek ROM, you'll have to flash SU. Use 2.7X. then update from play store. Root for regular CM is found in developer options. Settings > about device > tap build number 7 times and go back to Maine settings menu, scroll to bottom. For developer options. Enable root in that menu. Select both apps and ADB.
I am using the CM13 ROM by alexander_32, I guess the same one you're using.
Personally, it isn't as snappy as I wish but I'll give it some more time.
Also, the option to boot into recovery on the menu is so much better than using keys combination. Thumb up for that!
what is the optimal gapps to get from open gapps? there are so many options im not sure which works best on jem.
green_reaper said:
what is the optimal gapps to get from open gapps? there are so many options im not sure which works best on jem.
Click to expand...
Click to collapse
I almost always use pico gapps.
DragonFire1024 said:
I almost always use pico gapps.
Click to expand...
Click to collapse
so basically for jem im using CM13 (Marshmallow 6.0.1) build by Temasek . and for gapps should I use (platform = ARM , Android 7.0 and pico) ? or is there a better gapps build selection?
green_reaper said:
so basically for jem im using CM13 (Marshmallow 6.0.1) build by Temasek . and for gapps should I use (platform = ARM , Android 7.0 and pico) ? or is there a better gapps build selection?
Click to expand...
Click to collapse
Go to opengapps website. Always download the gapps for the corresponding Android version. Always choose ARM.