Develop Bugs

TWRP and FFF Installed; Cannot Boot Fully

Thanks in advance for the help. Like many others I have searched for something similar to what I am experiencing but have not had luck finding it. So here goes my "special" situation:
Background:
-I use a PC with Windows 7 installed
-I downloaded KFU (v. 0.9.6) and ran install_drivers
-Connected KF and ran "run"
-Selected Option 2 for a Permanent Root with Superuser
-I am not sure if this step fully worked because during the root it seemed like my PC and KF disconnected from each other and my PC flashed a message about "smartphone no attached" that I didn't catch the exact verbiage of
-I restarted my KF and found myself in the TWRP (v. 2.2.0) interface
-Followed directions from another post and selected "reboot" and then "system"
-This worked and it loaded the familiar KF home screen
-From here I again ran the "run" file from KFU
-This time I selected Option 6 for extras, then Option 1 for Google Apps / Go Launcher Ex
-The ADB Status was Online and away the install went
-Here I am not totally sure what happened, but I believe a similar problem happened as before with m PC and KF losing connection during install
-Either way, I landed on the KF boot screen (blue Fire, which implies I have FFF installed v. 1.4);
-It was stuck here so I tried the Unbrick Utility and several other suggestions from posts and was once again able to get back to the TWRP interface
-Here, I thought I had everything figured out and again navigated to "reboot" and then "system"
-This time however, I did not go back to the KF home screen and instead got right back to the TWRP interface
-It almost seemed like it tried to load the home screen (yellow word "fire"); but quickly restarted again and went back to the blue fire and then the TWRP interface
-From here, I have tried several different approached to no avail, but here is the state I am in to the best of my knowledge:
1. It appears I have FFF and TWRP installed
2. I may or may not have the Google Aps installed
3. My drivers are all still installed, but the only time my computer recognizes it is the split second when the yellow word "fire" comes up on a system reboot.
I think I am close, but maybe not. Any help is greatly appreciated and let me know if I need to provide more information. Tried to be thorough but this is my first crack at this.

hold the power button down for 20 seconds then power on when you see the white kindle blue fire press your power button to get boot menu
then select recovery from the boot menu with the power button
Download this rom http://forum.xda-developers.com/showthread.php?t=1439916
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
then hit the home button select wipe
wipe factory reset
wipe cache
wipe dalvik
wipe system
then go home again
select install again tap on rom zip flash it let it finish
then select reboot
enjoy your lovely rooted kindle fire
this is just rooted stock with playstore if you wish to try other roms use the same method with the exception of making a backup first

Thepooch said:
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
Click to expand...
Click to collapse
Thanks for the help! I have the ROM downloaded but am still cannot get my KF to be recognized on my PC to transfer files. Any suggestions on how to get the two to communicate?

Linux LiveUSB plus this:
http://forum.xda-developers.com/showpost.php?p=30629067
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
...or you could just pay attention to the directions Thepooch gave you. Just a thought.

soupmagnet said:
Linux LiveUSB plus this:
http://forum.xda-developers.com/showpost.php?p=30629067
...or you could just pay attention to the directions Thepooch gave you. Just a thought.
Click to expand...
Click to collapse
Thanks for getting back to me once more. I did try the directions Thepooch gave me exactly and no connection. Mounting did not allow my KF to connect. I also went into Linux and tried your code to get my KF to connect to my PC. I am no pro, but it seemed your first script just displayed a string and was rather frustrating. Inside one of the folders appeared to be a more complete script (with options 1 and 2) that your "READ ME" instructions hinted at (install_it file). I must be missing something. Would you be willing to provide more guidance on the Linux connection?
I appreciate all the help.

Yeah double click on runit then run in terminal.... Hit selection number 1 hit enter when it prompts for password... let it finish. ...Then hit selection number 2.... Then enter a y hit enter it will reboot.. Then try adb devices in a terminal..

SOLVED!
Thepooch said:
Yeah double click on runit then run in terminal.... Hit selection number 1 hit enter when it prompts for password... let it finish. ...Then hit selection number 2.... Then enter a y hit enter it will reboot.. Then try adb devices in a terminal..
Click to expand...
Click to collapse
Thanks to both of you for all the help! These little added details helped me through the home stretch. I still did not use the ""run_it.sh" script in terminal. I went straight to the "install_it.sh" file. I then followed your directions and had no troubles. The only change I had to do was manually toggle by booting selection after it kept rebooting to TWRP.

noobathon said:
Thanks to both of you for all the help! These little added details helped me through the home stretch. I still did not use the ""run_it.sh" script in terminal. I went straight to the "install_it.sh" file. I then followed your directions and had no troubles. The only change I had to do was manually toggle by booting selection after it kept rebooting to TWRP.
Click to expand...
Click to collapse
I think I'm going to have to change the title of that thread. I really did have faith in people.
There are instructions in that thread and in the README, and nowhere does it say to run any script other than "run_it.sh". There are separate sets of scripts for good reason.
If you had paid attention to the OP, you would have found what to do in your particular situation.

[Q] Unable to view internal storage

After deciding to put my Kindle Fire HD to use as something other than a .cbr reader I rooted my Kindle and tried to flash it. (sorry if I'm using the wrong terms I'm a noob) I was able to root it. After following the guide I was using further and enter a bunch of stuff into the command prompt and having to reboot again I got stuck on the KindleFire start up screen with a blue "Fire". I can access the TWRP menu by holding the Vol. Up button but my Kindle isn't appearing on my computer so I can't copy the CM10.1 custom ROM to install it.
I believe that all I need to do is somehow copy the CM10.1 custom ROM file to my Kindle but I can't figure out a way to do it. I'm running Win 7 on one machine and Vista on another and the drivers successfully installed on both so I'm not sure what the problem is. Any help is appreciated.

melloncollie said:
After deciding to put my Kindle Fire HD to use as something other than a .cbr reader I rooted my Kindle and tried to flash it. (sorry if I'm using the wrong terms I'm a noob) I was able to root it. After following the guide I was using further and enter a bunch of stuff into the command prompt and having to reboot again I got stuck on the KindleFire start up screen with a blue "Fire". I can access the TWRP menu by holding the Vol. Up button but my Kindle isn't appearing on my computer so I can't copy the CM10.1 custom ROM to install it.
I believe that all I need to do is somehow copy the CM10.1 custom ROM file to my Kindle but I can't figure out a way to do it. I'm running Win 7 on one machine and Vista on another and the drivers successfully installed on both so I'm not sure what the problem is. Any help is appreciated.
Click to expand...
Click to collapse
At the main screen of TWRP, tap Mounts, next, make sure there is ONLY an X next to sdcard. Tap Mount. Your kindle will now appear as visible on your computer. Transfer the ROM and the correct version of gapps to the root of your internal storage. Once it is done transferring, unmount sdcard. Go back to the main screen of TWRP. Tap wipe. Do a factory reset (wipe data) and wipe dalvik cache and cache. Back at the main screen tap install, find the ROM and select it. Wait while it flashes the ROM then go back into install and flash gapps.
Wipe dalvik again and then reboot. You should be all set with a nice working kindle
Sent from my Kindle Fire with Tapatalk 2

[Q] COT only or stuck at Kindle Fire logos- No TWRP, ROM

Hi,
I previously rooted my Kindle and things were just peachy until I tried to wipe it to give to my husband. I must have gotten the happy fingers because I deleted everything. After about 6 days of reading through the various threads and trying different things, it will only boot to the Kindle Fire logo screen and it will go from blue and white to the orange one, but it hangs there. The alternate boot option or reset boot mode does not have any other outcome. If I change it to "recovery mode" it will only open into the Cannibal Open Touch v2.1 Meanwhile, back on the computer the Device Manager seems to recognize the Kindle and the adb driver, but the system does not respond when I try to run any of the utilities that I've used; nor does the system respond to any of my commands I attempt. With the KFU it will reboot the Kindle to the logo and then hang at "waiting for device" or boot me back up to the COT Recovery.
I think I have tried every sequence or option with COT but I'm not real sure what the options are supposed to be doing and in what sequence. Below is an image of what I am now able to get on Recovery boot to COT. Can someone help? Is it too late? is it permanently bricked?
Thanks!!!

cpeaches said:
Hi,
I previously rooted my Kindle and things were just peachy until I tried to wipe it to give to my husband. I must have gotten the happy fingers because I deleted everything. After about 6 days of reading through the various threads and trying different things, it will only boot to the Kindle Fire logo screen and it will go from blue and white to the orange one, but it hangs there. The alternate boot option or reset boot mode does not have any other outcome. If I change it to "recovery mode" it will only open into the Cannibal Open Touch v2.1 Meanwhile, back on the computer the Device Manager seems to recognize the Kindle and the adb driver, but the system does not respond when I try to run any of the utilities that I've used; nor does the system respond to any of my commands I attempt. With the KFU it will reboot the Kindle to the logo and then hang at "waiting for device" or boot me back up to the COT Recovery.
I think I have tried every sequence or option with COT but I'm not real sure what the options are supposed to be doing and in what sequence. Below is an image of what I am now able to get on Recovery boot to COT. Can someone help? Is it too late? is it permanently bricked?
Thanks!!!
Click to expand...
Click to collapse
COTR is the best recovery out there, and as long as you even have the worst recovery that functions, your device is certainly not bricked.
It would be better if you put your enthusiasm to have the KFU fix your kindle aside.
Step 1) Download MoDaCo Rom/Any other ROM BUT NOT ANY KITKAT ROM(COTR can NOT flash KitKat)
Step 2) Transfer your ROM while in recovery
Step 3) Do a preflash wipe
Step 4) Do a factory reset
Step 5) Go to 'Install -> Install from SD Card -> Folder where you put your ROM
Step 6) Click Install without Backup
Step 7) Boot Android

LIFE and SANITY Saver!!!
Thank you sooooooo MUCH!!!!
You made me proud of myself...
Everything worked like a charm with my Samsung S4 USB chord.
For the Install step I had to use the "Zip installation" option to see the file MoDaCo file I copied over. Once I did the fat lady was tuning up and in about 5 minutes she was delivering the most beautiful solo I had heard in quite sometime!!!!
MUCH APPRECIATED!!! :good::good::good:

cpeaches said:
Thank you sooooooo MUCH!!!!
You made me proud of myself...
Everything worked like a charm with my Samsung S4 USB chord.
For the Install step I had to use the "Zip installation" option to see the file MoDaCo file I copied over. Once I did the fat lady was tuning up and in about 5 minutes she was delivering the most beautiful solo I had heard in quite sometime!!!!
MUCH APPRECIATED!!! :good::good::good:
Click to expand...
Click to collapse
Yes, by install I meant 'Zip Flashing'
I forgot the functions and didn't see the pic, its been about a month I used COT as to flash KitKat I had to switch to TWRP 2.6.3.1
Nice to see you got it working!

[Q] KF issues and what I have tried so far...

Hello.
I have a KF 1st generation. I had rooted it some time back and then un-rooted it (thought I did?) and haven't had an issue. This week it started loading up and freezing on the Kindle Fire orange and white logo. I am able to boot it to Recovery which gives me Cannibal Open Touch screen and options. I did try a few of the options but still the same end result. After coming here and reading around I found a thread and I followed the directions since the original poster and I seemed to have the same issue. There are the steps I followed:
Step 1) Download MoDaCo Rom/Any other ROM BUT NOT ANY KITKAT ROM(COTR can NOT flash KitKat)
Step 2) Transfer your ROM while in recovery
Step 3) Do a preflash wipe
Step 4) Do a factory reset
Step 5) Go to 'Install -> Install from SD Card -> Folder where you put your ROM
Step 6) Click Install without Backup
Step 7) Boot Android
I downloaded [ROM] 14 Jun Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire and made it to Step 5 using the 'Zip Flashing' option but I can't seem to flash or sideload or any of those options. While the Kindle is plugged into the computer I hear the noise and when I find my Kindle it has a Yellow Triangle with a !. I looked at the Kindle and it tells me I have no drivers and I am not able to drag and drop any files. Also, not sure if it matters but I am no longer using the computer used to root the Kindle.

the rebooting is the new 6.3.3 update trying to install, but because you have custom bootloader/recovery install fails.
may need to install twrp recovery. but my prerooted 6.3.3 zip sbould install fine.
Sent from my DROIDX using Tapatalk

sd_shadow said:
the rebooting is the new 6.3.3 update trying to install, but because you have custom bootloader/recovery install fails.
may need to install twrp recovery. but my prerooted 6.3.3 zip sbould install fine.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
@sd_shadow I appreciate the reply and the twrp file but can you lead me to the direction to getting them to the KF? I can plug the KF into the computer and it no longer gives me the triangle ! sign. I am unsure of the next step and don't wanna mess anything up with unnecessary stuff. Thank You again :good:

Sunnywonder said:
@sd_shadow I appreciate the reply and the twrp file but can you lead me to the direction to getting them to the KF? I can plug the KF into the computer and it no longer gives me the triangle ! sign. I am unsure of the next step and don't wanna mess anything up with unnecessary stuff. Thank You again :good:
Click to expand...
Click to collapse
select mount option in twrp, then just copy to sdcard folder on pc

sd_shadow said:
select mount option in twrp, then just copy to sdcard folder on pc
Click to expand...
Click to collapse
I have been trying to figure this out and searching but I can't seem to figure this out. I am uploading the screen I have on my KF and I don't know how to mount the file. I can't find a thread that will kind of walk me though it so if you know where I should go that would be great. I am uselessly pretty good with figuring things out so maybe I'm making this harder than it looks?

Sunnywonder said:
I have been trying to figure this out and searching but I can't seem to figure this out. I am uploading the screen I have on my KF and I don't know how to mount the file. I can't find a thread that will kind of walk me though it so if you know where I should go that would be great. I am uselessly pretty good with figuring things out so maybe I'm making this harder than it looks?
Click to expand...
Click to collapse
Can't remember if Cannibal Open Touch has mount options
may need to
Download a twrp.img from http://techerrata.com/browse/twrp2/blaze,
latest (24 June 2014) is openrecovery-twrp-2.7.1.0-otter.img
verify md5 check sum
Download ADB/Fastboot.exe Files from adb-fastboot.zip
Unzip adb-fastboot.zip
Copy adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe), and twrp.img
to same folder like c:adb
reboot Kindle to Bootloader
Open command prompt (Start menu>all programs>Accessories>Command Prompt
Enter Commands
Code:
cd\adb
fastboot reboot-bootloader
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot reboot
kindle will reboot
When you see Press Power for Boot Options select recovery
In TWRP (Team Win Recovery Project) select Mount check sd card and tap mount USB Storage
On Pc open sd card folder and copy update-kindle-prerooted.6.3.3.v1.zip downloaded from post 1
once copy is complete, close folder, unmount sd card
in TWRP select Install select update-kindle-prerooted.6.3.3.v1.zip
Swipe to Confirm Flash
after flash is complete, wipe cache, select Back, select Reboot
May take a few minutes to boot first time

Victory!
First off TY for the time you took to get me to the finish line. :victory:
I will admit trying to mount was a nightmare. I couldn't figure out how to do it so after hours of playing around and trying to find anything to try I finally succeed by installing the Kindle Fire Unbrick Utility (again) and running KindleUnbrick.bat file and installing the TWRP that way. Once that worked (and believe me I didn't think it would work since I tried this a few times) and I yelled WOOT, I followed the rest of your directions from "In TWRP (Team Win Recovery Project) select Mount check sd card and tap mount USB Storage" and installed your prerooted 6.3.3 zip and finished off your directions and have myself my dear reading buddy back. I APPRECIATE deeply the time you took to get me back. :highfive:
I want to add for anyone who is looking though threads looking for help with the same issue. If you are trying to get the TWRP file on your Kindle download the Kindle Fire Unbrick Utility and then running the RUN file and follow the directions.

great, Glad I could help.
I have tried to use the Kindle Fire Unbrick Utility a few times, with little success.
I would only suggest it, if nothing else is working, but does work in some situations.

[Q] Non-stock ROM to Hashcode's LP 5.1.x KFHD 8.9"

Hashcode said:
OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 8.9"
Click to expand...
Click to collapse
I want to upgrade my Kindle Fire HD 8.9" with Hashcode's latest marvel. I'm currently running LiquidSmooth, and I'm a bit confused (make that very confused) about the steps I need to take to install it.
Can anyone who has flashed from a similar state give some instructions?

Does the lack of replies mean nobody else has done something similar?

nigelmercier said:
Does the lack of replies mean nobody else has done something similar?
Click to expand...
Click to collapse
I did this a while back. As I recall the install is simply a clean install (i.e.; backup everything; wipe both caches, data and system; flash ROM and GApps; wipe Dalvik cache; reboot system). I think you will find references to this process throughout the original thread. Make sure you have the most recent version of TWRP.
Sent from my Amazon Jem using XDA Free mobile app

BobJayJr said:
.... As I recall the install is simply a clean install (i.e.; backup everything; wipe both caches, data and system; flash ROM and GApps; wipe Dalvik cache; reboot system)...
Click to expand...
Click to collapse
Thanks for the reply, but I have no idea what most of that means. Instructions for the proceedures seem fragmented throughout the forum.

nigelmercier said:
Thanks for the reply, but I have no idea what most of that means. Instructions for the proceedures seem fragmented throughout the forum.
Click to expand...
Click to collapse
I've flashed ROMS on my kindle a zillion times, so I think I can give you the CliffsNotes version.
1) Download the latest CM12.1 build from the website.
2) Also download the TWRP 2.8.7.0 .zip for jem from Hashcode's thread, as he recommends using this version for flashing CM12.1.
3) Optional (but recommended for the best experience): download the latest gapps package from the link in Hashcode's other thread concerning CM12.1.
4) Reboot into TWRP if you haven't done so already. (You can do this by pressing the power button when the kindle is turned off, then immediately pressing and holding volume up, which is the button on the volume rocker that is farthest away from the power button. Keep holding it until about 2-3 seconds after you see the blue Kindle logo.)
5) Connect the kindle to your computer and copy the TWRP update zip from your computer to the kindle.
6) Flash the TWRP update zip from within your current TWRP version. When done, reboot into recovery again. This time, when you see the TWRP version, it should read 2.8.7.0 instead of what it read earlier.
7) Optional but recommended: Hook up the kindle to the computer again and copy all files from the kindle to the PC. When done, delete the original files in "/sdcard" on the kindle and then (from the TWRP main menu) select "Backup", and choose to backup at least "Data". You could also select "system" as well, but I think this would be redundant (you could always flash the base ROM and gapps and then restore your backup). When done (it might take half an hour or more, depending on how much data has accumulated), you should copy the files in /sdcard/TWRP/ to your computer.
8) [Only do if switching between ROMs, like from Candy5 to CM): When done, select "Wipe" from the main menu, choose "Advanced wipe", and select "Cache", "Dalvik cache", "Internal storage", "Data", and "System". Swipe to wipe, wait for the wiping to complete. Go to the main menu. Immediately select Reboot -> Recovery, and ignore the warnings about TWRP detecting no installed or rooted ROM. When back in recovery again, hook the kindle back up to the PC and copy the CM12.1 (and gapps, if you downloaded it) .zip(s) to the kindle. Then go ahead and flash them from TWRP (if you choose to install the gapps, remember to flash CM first and then the gapps). If you didn't flash the gapps (which automatically clear out both caches during flashing), make sure to wipe both caches when done flashing CM. Reboot into system, and be patient.
9) If dirty flashing (for example, if flashing a CM12.1 8/19/2015 build over a 8/17/2015 build), all you need to do is just go to the main menu in TWRP, choose "Install", and then browse to the ROM zip. Flash it (you don't need to worry about wiping caches unless you run into issues), and then reboot into system.
Hope this helped!

That helped hugely, many thanks.
However:
2) Also download the TWRP 2.8.7.0 .zip for jem from Hashcode's thread
I thought this would be simple, but that thread first goes off to another thread talking about things like Android SDK, Stack, Freedom, and FastBoot. WTF?
[Later] I decided to ignore all this and go ahead with your excellent instructions. Most were straightforward, although I did have to delve a little to find what I wanted. For example:
[4] Reboot into TWRP if you haven't done so already. While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button) [From HashCode's thread]
8) When done, select "Wipe" from the main menu, then Advanced Wipe
Flashed CM, then GApps, rebooting...
[Later still]
Got a little pulsing cyan android face in the middle of the screen for a couple of minutes. He zoomed off, now got Android is starting ... Optimizing app XX of 87
After last app updated, 30 second delay.
Screen dimmed, but can see Starting apps
After about 10 minutes I get a message Unfortunately Bluetooth Share has stopped
Screen eventually came back to higher brightness. I think it is working.
WOOT!
Note, the message Unfortunately Bluetooth Share has stopped comes up from time to time, although BT is turned off.

nigelmercier said:
That helped hugely, many thanks.
However:
2) Also download the TWRP 2.8.7.0 .zip for jem from Hashcode's thread
I thought this would be simple, but that thread first goes off to another thread talking about things like Android SDK, Stack, Freedom, and FastBoot. WTF?
[Later] I decided to ignore all this and go ahead with your excellent instructions. Most were straightforward, although I did have to delve a little to find what I wanted. For example:
[4] Reboot into TWRP if you haven't done so already. While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button) [From HashCode's thread]
8) When done, select "Wipe" from the main menu, then Advanced Wipe
Flashed CM, then GApps, rebooting...
[Later still]
Got a little pulsing magenta android face in the middle of the screen for a couple of minutes. He zoomed off, now got Android is starting ... Optimizing app XX of 87
Screen dimmed, but can see Starting apps
After about 10 minutes I get a message Unfortunately Bluetooth Share has stopped
Screen eventually came back to higher brightness. I think it is working.
WOOT!
Note, the message Unfortunately Bluetooth Share has stopped comes up from time to time, although BT is turned off.
Click to expand...
Click to collapse
The Android SDK (which at the bare minimum would include fastboot and ADB) would only be needed when rooting and backing up the stock software and flashing the custom boot, bootloader and recovery files. Even then, you'd most likely only need it for rooting (and backup of stock firmware), as the FireFlash app (for stock Amazon OS only?) would flash the files for you (once you plug them into the app, anyway).
The stack file (for the HD 8.9's stock firmware) is meant to block OTAs for Amazon's software. You wouldn't need to worry about it once you install a custom ROM. Similar story for the freedom-boot img - it's only needed for Amazon's stock software, as it is one of the "keys" that enables custom ROM access on the Kindle.
As for TWRP:
1) Seeing as though you flashed LiquidSmooth, I was thinking that you had known how to get into TWRP. For future reference, you do have to press and hold the volume up key (near the headphone port, or farthest away from the power button) before the yellow Kindle logo turns blue to boot into TWRP.
2) My mistake - you do need to select "Wipe" from the main menu, and then "Advanced wipe" from there to choose which partitions to wipe. (I've been flashing ROMs for so long that I forgot to mention that!)
The pulsing android logo you got after rebooting from TWRP into system was the CM12.1 boot animation featuring the CM mascot, Cid. I'm assuming it worked if you managed to get that far.
Finally, I'm thinking that the BT share crashes might be a momentary issue - I would wait until the next nightly and see what happens. Glad I could help you out!

Thanks for the extra information.
Please note that I meant to be in no way critical of your excellent instructions, I was just laying down a timeline as I did the upgrade in case it was helpful to others.

monster1612 said:
... Finally, I'm thinking that the BT share crashes might be a momentary issue - I would wait until the next nightly and see what happens...
Click to expand...
Click to collapse
Just installed cm-12.1-20150820-NIGHTLY-jem.zip but the "Unfortunately Bluetooth Share has stopped" problem persists. I'll try again in a few days. I don't seem to have a working Disable button for Bluetooth Share.
Some other related issues:
[1] When I first did the update I was asked if I wanted to root the device, I said no. I just updated again (without GApps this time, wiped both caches) but didn't get this option. Would rooting help with the Disable button?
[2] I flashed without GApps as I really don't need any of the stock apps, except Google Play so I can download a few selected apps. However, without GApps, there is no Play! Is there a way to install just this?

nigelmercier said:
Just installed cm-12.1-20150820-NIGHTLY-jem.zip but the "Unfortunately Bluetooth Share has stopped" problem persists. I'll try again in a few days. I don't seem to have a working Disable button for Bluetooth Share.
Some other related issues:
[1] When I first did the update I was asked if I wanted to root the device, I said no. I just updated again (without GApps this time, wiped both caches) but didn't get this option. Would rooting help with the Disable button?
[2] I flashed without GApps as I really don't need any of the stock apps, except Google Play so I can download a few selected apps. However, without GApps, there is no Play! Is there a way to install just this?
Click to expand...
Click to collapse
To answer your questions:
1) You wouldn't need to root, as CM already ships with root pre-installed (it's just hidden and disabled by default). To enable it, all you'd need to do is:
Open the settings app, then tap "About Device".
Tap on the build number 7 times. You'll know you're doing it right when you see a toast notification at the bottom of the screen saying "You are now x steps from being a developer."
When you see a toast that says "You are now a developer!", go back to the main settings screen and choose the newly enabled Developer options.
In this screen, look for the "Root access" setting. Tap on it, then select "Disabled". Tap on it again, and this time select "Apps" or "Apps + ADB". Agree to the warning about the dangers of root.
You should be able to grant and deny root access to apps now.
2) I would look for a minimal/micro gapps package for lollipop (5.1 compatible if possible). While I don't think it would be completely devoid of anything that isn't the Play Store or its dependencies, I think that this is the closest you can get to it. I'll try to look for another solution and update the post as needed.

Thanks again for your reply. Don't go out of your way looking for a minimal GApps package, I can just use the standard one instead. I was just trying to be clever, and failing
My main concern is the "Unfortunately Bluetooth Share has stopped" problem. I honestly don't care if it has stopped working, I just don't want to be told anymore!