Develop Bugs

[Q] Cm 10 to Cm11?

Me and my son rooted our S3's a while ago. We have Cm 10 nightly "Oct 28/12" and want to update to Cm 11 nightly but I think we have to do something different as to a normal rom update? I think I read we have to update the kernal or something first but didn't understand it. We have the newest Clockworkmod 6.0.4.3. If someone could point us in the right direction it would be greatly appreciated. Thanks

Frostman5555 said:
Me and my son rooted our S3's a while ago. We have Cm 10 nightly "Oct 28/12" and want to update to Cm 11 nightly but I think we have to do something different as to a normal rom update? I think I read we have to update the kernal or something first but didn't understand it. We have the newest Clockworkmod 6.0.4.3. If someone could point us in the right direction it would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Alright first of all, which was the last official AT&T software update you did? If your at least updated to 4.1.2, you'll be good. As for the update, since it is a different update, a clean flash is necessary. First, you have two options, can get the latest CM 11 nightlife from
http://download.cyanogenmod.org/?device=d2att
OR, there's an excellent ROM by a developer named PwnCakes193, called Quantum which is based on CM 11, but based on community feedback and comparing it to the official CM 11 bug thread, Quantum is a lot more stable. It doesn't get updated daily but at least every 2-4 days (no promises). If you decide to check it out, make sure to read the thread twice and read a few of the latest comments here:
http://forum.xda-developers.com/showthread.php?t=2390147
For both these, you'll need the latest GApps. I recommend Paranoid Android GApps from here:
http://forum.xda-developers.com/showthread.php?t=2397942
Don't let the name trick you, you can use these GApps for any 4.4.x ROM (I recommend the Modular package).
Once you have a ROM and GApps downloaded and on your phone, the flashing process will be like this for CWM:
Wipe data/factory reset>wipe cache
>format /system>format /cache> wipe dalvik cache. Flash ROM, flash GApps, wipe cache, wipe dalvik cache. After this, you should be good as gold, so just setup and download your apps and that's it!
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Thanks a lot for your help. I have 4.1.2 on my phone .Do I not have to update the kernel ? As I think awhile ago I tried updating to 4.2 and it wouldn't go and someone said I needed to update the kernel,,but that was awhile ago maybe things have changed.I 'll try your method and let you know how it goes. thanks

ok I wiped everything they said to then tried to install Quantum 4.3 and says installation aborted "status 7" I remember this from last time and I never went any further because someone said I had to update the kernel?

its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm

Frostman5555 said:
its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm
I have I747MVLLH1,,its not in the list on the rom,,I remember this from last time and i stopped,,More reading
Click to expand...
Click to collapse

Frostman5555 said:
its not the Kernel, I guess my bootloader isn't in the assert command of the roms approved bootloaders, so it won't load it. so I guess I have to update my bootloader,,,hmmm
Click to expand...
Click to collapse
Are you trying to install 4.3 or Quantum v3?, Because Quantum v3 is 4.4.2 KitKat. Do you have a Canadian Galaxy S3? There might be something related to this in the ROM thread. Double check to make sure your recovery is the latest. If I had to guess, its probably be the boot loader, just be careful and read twice before you do anything.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

It was the bootloader. Updated it with Clockworkmod to the newest Canadian one"DLK4" then the Quantum v3 went on smooth . thanks for the help

Frostman5555 said:
It was the bootloader. Updated it with Clockworkmod to the newest Canadian one"DLK4" then the Quantum v3 went on smooth . thanks for the help
Click to expand...
Click to collapse
Sure thing, glad I could help. If you feel brave, PwnCakes just posted v3.15 about 5 minutes ago, which is the latest 4.4.2. If you decide to, you'll need a clean flash and latest GApps.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Drx,does the 3.12 have the google now working?I can't seem to get it to work.Also what would be the procedure to put 3.15 on now that I have 3.12 on,,thanks

Frostman5555 said:
Drx,does the 3.12 have the google now working?I can't seem to get it to work.Also what would be the procedure to put 3.15 on now that I have 3.12 on,,thanks
Click to expand...
Click to collapse
Yup, all versions have Google Now working. Have you made sure that there's no updates pending for it in the Play Store? Make sure that after every update, even a dirty flash, that you install GApps. If you forget to, the search bar will bring up a Gingerbread looking search app, and a lot of the Google apps and services will not work. For a "dirty" flash (no apps or data is lost), my process goes like this: wipe cache>wipe dalvik cache> format /system (no data will be lost)> Install ROM> Install GApps> wipe cache and dalvik. You should only use this if you are on the ROM already, not if it is a completly new ROM. Hope this helps!

SOLVED: [Q] Help...Gapps won't install properly

Hey guys, I just went from 4.3 JDX to XenonHD (4.4.2) and everything's great with the exception of Gapps. I tried both the PA stock and the modular full images and both behave the same.
After wiping system/data/cache, I Installed Xenon in TWRP (newest) followed by the PA Gapps image. It went through just fine, no errors, congrats yadda yadda. After boot I notice quite a few Gapps missing, Hangouts and G+ being the ones that caught my attention. Trying to install from Play Store results in error "Insufficient storage available", and I have about 5GB left. I'm not sure how relevant the following check was, but I tried restoring a backup from Titanium...any Gapp I try to restore just hangs there at the restore screen with no progress or error. I was guessing that had something to do with the switch between 4.3 and 4.4.
Any ideas about how to get this worked out? Thanks.

kornesque said:
Hey guys, I just went from 4.3 JDX to XenonHD (4.4.2) and everything's great with the exception of Gapps. I tried both the PA stock and the modular full images and both behave the same.
After wiping system/data/cache, I Installed Xenon in TWRP (newest) followed by the PA Gapps image. It went through just fine, no errors, congrats yadda yadda. After boot I notice quite a few Gapps missing, Hangouts and G+ being the ones that caught my attention. Trying to install from Play Store results in error "Insufficient storage available", and I have about 5GB left. I'm not sure how relevant the following check was, but I tried restoring a backup from Titanium...any Gapp I try to restore just hangs there at the restore screen with no progress or error. I was guessing that had something to do with the switch between 4.3 and 4.4.
Any ideas about how to get this worked out? Thanks.
Click to expand...
Click to collapse
Had a similar problem with installing CM 11.1 and PA GApps 4.4.2 - don't know if it's the same for you, but I found out the problem was the /system partition is too small - as CM and GApps have gotten bigger and bigger the partition is now too small to handle them. I had to move over to AOKP and a different 4.4.2 GApps package. Might be time to upgrade to a Nexus 5....

crfrank said:
Had a similar problem with installing CM 11.1 and PA GApps 4.4.2 - don't know if it's the same for you, but I found out the problem was the /system partition is too small - as CM and GApps have gotten bigger and bigger the partition is now too small to handle them. I had to move over to AOKP and a different 4.4.2 GApps package. Might be time to upgrade to a Nexus 5....
Click to expand...
Click to collapse
Well I'll be...i figured with the unified SD card that would be a thing of the past, but it does make sense. I'll give it a whirl. Thanks man.

SOLVED
crfrank said:
Had a similar problem with installing CM 11.1 and PA GApps 4.4.2 - don't know if it's the same for you, but I found out the problem was the /system partition is too small - as CM and GApps have gotten bigger and bigger the partition is now too small to handle them. I had to move over to AOKP and a different 4.4.2 GApps package. Might be time to upgrade to a Nexus 5....
Click to expand...
Click to collapse
That was it. Titanium reported about 20MB system space left so I snagged the micro Gapps and that worked great. Thanks for the idea!

kornesque said:
That was it. Titanium reported about 20MB system space left so I snagged the micro Gapps and that worked great. Thanks for the idea!
Click to expand...
Click to collapse
You're welcome, glad I could help

[Q&A] [ROM] [4.4.2] [TW] Pimpdroid 3.0 beta 20140930 {WiFi, 3G, and LTE!}

Q&A for [ROM] [4.4.2] [TW] Pimpdroid 3.0 beta 20140930 {WiFi, 3G, and LTE!}
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Works perfectly!!
This is my first post since i registered here, and im very happy for the one who created pimpdroid 3.0!!
but i have a little question, how can i delete apps like google maps, music app and other "integrated" apps?
Somebody who knows?

Titanium backup is your friend.
Sent from my SM-T210 using XDA Free mobile app

2.5 version fine, new beta error
Thanks for this guy, got 2.5 working, but the 3.0.3 beta fails and says,
"set_metadata_recursive some changes failed"
error to it.
Using TWRP 2.6 from:
http://forum.xda-developers.com/showthread.php?t=2531784

Lord Sif said:
Thanks for this guy, got 2.5 working, but the 3.0.3 beta fails and says,
"set_metadata_recursive some changes failed"
error to it.
Using TWRP 2.6 from:
http://forum.xda-developers.com/showthread.php?t=2531784
Click to expand...
Click to collapse
Use one of @moonbutt74 's recoveries, as specified in OP.

Bootloop
Hello,
I have downloaded the Jellybean version of Pimpdroid for my Tab 3 10.1 and placed it in my SD card. However, when I flashed it through Philz recovery (I cleared the data, system, cache and Dalvik cache) I get stuck in a bootloop so I simply restore it from my backup. I then try again. Bootloop. I would like to know how to rectify this as I love the work done to this ROM.

Tonio2000 said:
Hello,
I have downloaded the Jellybean version of Pimpdroid for my Tab 3 10.1 and placed it in my SD card. However, when I flashed it through Philz recovery (I cleared the data, system, cache and Dalvik cache) I get stuck in a bootloop so I simply restore it from my backup. I then try again. Bootloop. I would like to know how to rectify this as I love the work done to this ROM.
Click to expand...
Click to collapse
Hey , try flashing the jellybean builds from angel666's TWRP

Aeyan Ashraf said:
Hey , try flashing the jellybean builds from angel666's TWRP
Click to expand...
Click to collapse
I tried doing that with a clean flash but now after i flashed it, my tab reboots and then reboots into recovery.
UPDATE: I managed to flash the rom by flashing the first build which worked and then dirty flashing the latest build over it.

I'm having problems with X multi-window. It's asking me whether I want to put the application on the left or right but only folks the entire screen. It never splits.
Any ideas?

dshulman said:
I'm having problems with X multi-window. It's asking me whether I want to put the application on the left or right but only folks the entire screen. It never splits.
Any ideas?
Click to expand...
Click to collapse
I'm having the same issue with beta3
---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------
Also, I have another question, how can I change the sound that run when I touch the screen, actually it plays the camera sound but it's sooo anoying, how to redtore the stock sound?

igos2 said:
I'm having the same issue with beta3
---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------
Also, I have another question, how can I change the sound that run when I touch the screen, actually it plays the camera sound but it's sooo anoying, how to redtore the stock sound?
Click to expand...
Click to collapse
Go into Settings... Sound and you'll see the setting to turn off Touch Sounds. I hate that as well.

Il turned it off 5 minutes after I installed this rom, but I want it to be on with a less annoying sound.

igos2 said:
Il turned it off 5 minutes after I installed this rom, but I want it to be on with a less annoying sound.
Click to expand...
Click to collapse
So go into sound and go to volume set system volume to a bit low .....................

I want to change the sound, stop saying OOT things

igos2 said:
I want to change the sound, stop saying OOT things
Click to expand...
Click to collapse
I can tell u the method but I think you'll find it very difficult to do it.....
If u want that method write it up here.....

Sur, I think it must be a .wav file somewhere, I can copy the stock sound it place of that .wav, just need to know the path of each of this files.

Helo,
i have bevor Pimpdroid installed have the Bindroid. After installing Pimpdroid i have 2x Bootloop and than going into Recovery.
I have do all right.
But the problem is, i cant install Stock or another ROM after the experience with Pimpdroid. I can do what i want, i get ever 2x Bootloop an the P5210 (wifi) going into Recoverymode.
I tryed another Recovery, have now TRWT installed, but its no better... ok this recovery is 1000x better than CWM, but not for my problem.
So i have try all and now i search the way to install the "stock recovery" or another way the rom install with odin, how i make from zip an tar.md5 file? I see by another user the have the stock rom in tar.md5 and i found only stockrom in zip format?
PS: I havent installed the Beta4, because the developer writed that is not work, i have installed beta3 and after that not worket i have try beta 2,1 and the old 2.5 an than every stock rom than i got.

igos2 said:
Sur, I think it must be a .wav file somewhere, I can copy the stock sound it place of that .wav, just need to know the path of each of this files.
Click to expand...
Click to collapse
Hello brother ,
The file is in system/media/'here' and and it is in .ogg format ......the name of the file I forgot .... I will tell u in some time
Sent from my GT-I9082 using XDA Free mobile app

I have found it on system/media/ui, the file is TW_Touch.ogg.

Status 7
I've done some Google-fu and I still can't figure this one out.
I've done everything I can tell correctly, cleared everything, rooted, put the ROM on my root. I boot into Philz, go into install zip, start the installation and it goes through "installing update". After a short while a message pops up saying "set_metadata_recursive: some changes failed" and it then says that there's a Status 7 error.
After looking up Status 7 it says that it's usually a check that catches if you're not using the same model number that the ROM is for, but I clearly am as it's for the p5210 and I have the p5210. What am I doing wrong? Any help is much appreciated!

[Q&A] [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-

[Q&A] [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-
Q&A for [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

negamann303 said:
You need to be on nk1 firmware and use Cwm recovery
Click to expand...
Click to collapse
My tab was completely stock till today, all i did was root it and flash this

(No longer relevant)

TWRP question?
Hi all, Just wanted to give a big thanks for the work being done on this. I thought it was going to be washed up but it has been
revived ! Thanks again
Now here is what I'm wondering.
After taking the NK1 firmware, I rebooted and Odin the recovery from #2 TWRP
- Noticed in the new recovery it has a message that says "E:unable to mount / firmware" and "E: error sending message to add(or remove) storage 65537" . Is there something else I should be clicking on more?
I basically flashed the ROM as I normally would when I was running the older version of TWRP for a clean install.
I was wondering if all this is normal or did something fail to install when I did my Odin?
thanks again and like I said so far its been running great !!
Z.

Hey guys I cant get my wifi to turn on after clean install

kashis32 said:
Hey guys I cant get my wifi to turn on after clean install
Click to expand...
Click to collapse
Did you double check ur firmware? I upgraded 2 NK1 @ first but only 2 of the 4 (pda csc) updated and the baseband and bootloader didn't @ first. Had to Odin back over again now all r NK1. I use the Samsung phone info app to double check. Try that and make sure u do a full clean install. Well that's what worked 4 me.
Z.

Any update on broken wifi? i am on nk1 so idk why it doesn't work.

zsibisi said:
- Noticed in the new recovery it has a message that says "E:unable to mount / firmware" and "E: error sending message to add(or remove) storage 65537".
Click to expand...
Click to collapse
I have the same errors... So far it doesn't seem like it has affected anything though. The only issue I have is the battery seems to drain a lot faster than on stock nk1.
This is actually my first time flashing a rom so idk if maybe it was one of the options I checked in the beginning or not. I chose the unsecured adb kernel so maybe I'll try the stock kernel and see if the errors or battery thing change because I don't really know what the difference between them is.
---------- Post added at 05:17 PM ---------- Previous post was at 05:09 PM ----------
Tijaun said:
Any update on broken wifi? i am on nk1 so idk why it doesn't work.
Click to expand...
Click to collapse
Hey like I said in my other post this is the first time I've flashed a rom so I don't know much. But when I started this I had to flash stock nk1 and apparently I flashed the wrong version because my wifi wouldn't work even in stock so I then flashed a different stock nk1 and everything worked and continued to work when I flashed this rom.
So what I'm trying to say is maybe you need to flash a different stock nk1 again and see if that works?

Any thoughts on improving battery life? Seems stock had better performance than this ROM. Other than that i love this ROM and will keep it as my daily driver. Buttery smooth and no force closes.
late,
Coz

cozboogie said:
Any thoughts on improving battery life? Seems stock had better performance than this ROM. Other than that i love this ROM and will keep it as my daily driver. Buttery smooth and no force closes.
late,
Coz
Click to expand...
Click to collapse
Try deleting /etc/init.qcom.post_boot and restarting. That's where most of my performance tweaks are. If it saves battery, let me know.
As for recovery. The /firmware mount error doesn't matter. TWRP is the only recovery that doesn't recognize it. I'll just comment it out for next release (already using TWRP 2.8.4.0 on my tablet [emoji14])
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so

negamann303 said:
Try deleting /etc/init.qcom.post_boot and restarting. That's where most of my performance tweaks are. If it saves battery, let me know.
As for recovery. The /firmware mount error doesn't matter. TWRP is the only recovery that doesn't recognize it. I'll just comment it out for next release (already using TWRP 2.8.4.0 on my tablet [emoji14])
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so
Click to expand...
Click to collapse
Deleted suggested file....device "feels" snappier....I'll keep an eye on battery life.
late,
Coz

negamann303 said:
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so
Click to expand...
Click to collapse
When I flashed the rom it gave two options for the kernel one said something like "nega unsecured adb" the other said "completely stock". I figured the one that said nega was you're kernel and the other was the tablets stock? Am I wrong on that and what is the difference between them?

Level47 said:
When I flashed the rom it gave two options for the kernel one said something like "nega unsecured adb" the other said "completely stock". I figured the one that said nega was you're kernel and the other was the tablets stock? Am I wrong on that and what is the difference between them?
Click to expand...
Click to collapse
The version in the Rom just has an edited ramdisk for unsecured adb is all

@negamann303: Thank you for a fantastic rom. It's great to see some renewed interest in the T217S. I discovered it last night, read through both threads, updated firmware first and then flashed your TWRP, rom and themes. Everything is running smoothly. Looking forward to your TWRP update just to hide those firmware error messages.

I had this problem after flashing the recovery zip. Tried both TWRP and Philz with both reporting thd same.
Next question, how do change air gesture options. I made some changes when I turn the option on. Now I can not find Motion or any option in settings to edit or change. What am I missing? ???????

So I just flashed the new recovery and the firmware error is gone but when I flashed timberwolf's theme (atleast I think it was after the theme but I definitely got the error) I still got the "E:error sending message to remove storage 65537" error. But after a quick Google it turns out you have to turn off mtp in the recovery to fix this issue.
The twrp thread here on xda explains it and also tells you how to disable mtp in twrp.
http://forum.xda-developers.com/showpost.php?p=58224851&postcount=102
wingman358 said:
When you first enter recovery, go to the "Mount" menu then on the lower right side it should say "Disable MTP". Click it to disable and you shouldn't get the error if you go and wipe after doing that.
It's not persistent so you'll have to do it each time you restart the recovery and want to do a storage wipe.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse

Okay, so I guess I haven't been following this thread as closely as I thought. I didn't realize we were at v2. Downloading now. Can I dirty flash? Any plans to use SVN? If I need to do a clean flash, I will then have to re flash the kernel and theme, right? I remember SVN was a life saver before because Nega is like a mad scientist....always tinkering. Also, I have never learned how to back everything up for clean flashes. Do I go they the whole setup every time like a pilgrim. Titanium bckup is mystifying to me.

GAPO said:
Okay, so I guess I haven't been following this thread as closely as I thought. I didn't realize we were at v2. Downloading now. Can I dirty flash? Any plans to use SVN? If I need to do a clean flash, I will then have to re flash the kernel and theme, right? I remember SVN was a life saver before because Nega is like a mad scientist....always tinkering. Also, I have never learned how to back everything up for clean flashes. Do I go they the whole setup every time like a pilgrim. Titanium bckup is mystifying to me.
Click to expand...
Click to collapse
If you are using Titanium Backup Pro, I created a screencast video for my phone that shows the right way to create an update.zip file that you can flash from recovery immediately after doing a clean install. I also tried it on my Tab 3 with no problems.

Ramer said:
If you are using Titanium Backup Pro, I created a screencast video for my phone that shows the right way to create an update.zip file that you can flash from recovery immediately after doing a clean install. I also tried it on my Tab 3 with no problems.
Click to expand...
Click to collapse
Thanks! A couple of questions...when I apply the update.zip, will it have trouble re installing apps that I got from sources other than Google Play store? I mean, is it storing the apps to re install from the zip, or re-downloading them from the play store? Because I got some of mine from other sources.

GAPO said:
Thanks! A couple of questions...when I apply the update.zip, will it have trouble re installing apps that I got from sources other than Google Play store? I mean, is it storing the apps to re install from the zip, or re-downloading them from the play store? Because I got some of mine from other sources.
Click to expand...
Click to collapse
No trouble at all. It's creating the update.zip from the apps that you chose to backup, their coming from your phone tablet, not the Playstore.

[Q&A] [ROM] Candy5 Unofficial | 5.1.1 | 4.30.15

Q&A for [ROM] Candy5 Unofficial | 5.1.1 | 4.30.15
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Candy5 Unofficial | 5.1.1 | 4.30.15. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Awesome port
Brilliant job, man!! The ROM seems stable enough for a daily driver, even from a dirty flash from Hashcode's CM12 port. Just a few bugs:
1) When choosing to show the seconds for the time, the seconds show up after the PM/AM text. The attached screenshot demonstrates this (I used the CandyROM sweeteners for the Adventure Time themed navbar).
2) When I paired my Bluetooth keyboard, I was able to type the pairing code as prompted, but even though Android recognizes it as an input device, I'm not able to type with the keyboard. This issue didn't occur in CM11, but it was prominent in Hash's CM12 ports. Maybe it's a lollipop issue in general?
3) the navigation ring targets look awfully large (also shown in the screenshot). This issue appeared before (and after, as well) I customised the navigation ring targets, and it did not do this in Hashcode's port.
Otherwise, this ROM is excellent for a first port!
EDIT: Adding screenshot link: http://imgur.com/dubEMEH

Some games crash and can't be started. There is no not responding or force closed messages., they just crash and returns to home screen. Is it a rom problem or am I doing something wrong?

Does it work on the LTE version. Does the LTE work on it ? Thanks!

[ROM] Candy5 Unofficial | 5.1.1 | 4.30.15 checking connection has gone on for 3 hours
well like the title says i have just flashed this rom on my kindle and the i started it up and connected to wi-fi and it says checking connection for 3 hours now and i tried reboot several times now but nothing seems to get me past this screen???

Lynn472 said:
well like the title says i have just flashed this rom on my kindle and the i started it up and connected to wi-fi and it says checking connection for 3 hours now and i tried reboot several times now but nothing seems to get me past this screen???
Click to expand...
Click to collapse
Did you do a dirty flash from Hashcode's CM12 builds or CM11 nightlies? Try clearing dalvik and cache in TWRP and then reboot. If that fails, I would suggest doing an advanced wipe in TWRP (check all boxes, including system), rebooting into recovery again, and then re-flashing the ROM.

monster1612 said:
Did you do a dirty flash from Hashcode's CM12 builds or CM11 nightlies? Try clearing dalvik and cache in TWRP and then reboot. If that fails, I would suggest doing an advanced wipe in TWRP (check all boxes, including system), rebooting into recovery again, and then re-flashing the ROM.
Click to expand...
Click to collapse
umm no i just got a custom recovery installed but i dident wipe data or anything so ill go try that and re do it

Lynn472 said:
umm no i just got a custom recovery installed but i dident wipe data or anything so ill go try that and re do it
Click to expand...
Click to collapse
With that in mind, you must have come from stock - did you make backups in case you wanted to revert back to stock firmware? Generally speaking, if switching from Amazon's stock firmware to CM or CM to AOKP (differing ROM bases), you should make backups and then wipe system, data, and both caches (Dalvik and regular). Doing so ensures that no conflicts arise when using the new ROMs. If you do encounter problems, the backups ensure you have software to fall back on. If you're flashing an update to an existing ROM (like you're flashing a newer CM ROM on top of an older CM build), then it's OK to dirty flash (just flash the new ROM zip without clearing data or system. Also, make sure you have the latest TWRP release (you can flash that update just like any regular ROM zip, download here: http://forum.xda-developers.com/showthread.php?t=2218802). The reason why you would need Hashcode's port of TWRP 2.8.3.0 for the HD 8.9 is because 2.8.3.0 has support for Lollipop builds, and if you try to flash a TWRP build from TeamWin's website, you'll end up with a brick.

monster1612 said:
With that in mind, you must have come from stock - did you make backups in case you wanted to revert back to stock firmware? Generally speaking, if switching from Amazon's stock firmware to CM or CM to AOKP (differing ROM bases), you should make backups and then wipe system, data, and both caches (Dalvik and regular). Doing so ensures that no conflicts arise when using the new ROMs. If you do encounter problems, the backups ensure you have software to fall back on. If you're flashing an update to an existing ROM (like you're flashing a newer CM ROM on top of an older CM build), then it's OK to dirty flash (just flash the new ROM zip without clearing data or system. Also, make sure you have the latest TWRP release (you can flash that update just like any regular ROM zip, download here: http://forum.xda-developers.com/showthread.php?t=2218802). The reason why you would need Hashcode's port of TWRP 2.8.3.0 for the HD 8.9 is because 2.8.3.0 has support for Lollipop builds, and if you try to flash a TWRP build from TeamWin's website, you'll end up with a brick.
Click to expand...
Click to collapse
ive got this revovery not twrp
http://forum.xda-developers.com/showthread.php?t=2721761

Lynn472 said:
ive got this revovery not twrp
http://forum.xda-developers.com/showthread.php?t=2721761
Click to expand...
Click to collapse
OK, try clearing data, system, and both caches and then flashing the ROM from PhilZ Touch. If you get the same issue again, I would boot into fastboot mode on the Kindle and then flash the TWRP 2.8.3.0 recovery img file (https://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.8.3.0-recovery.img) from there. Best of luck!

Is there a TV Out problem/lack of support?
Everything went perfectly until I tried to send kodi to TV, the app would stall/crash to home and at one point looked just like a broken TV with an interference pattern, requiring a hard shutdown.

Does the sweetener pack work on JEM? Does the pack get flashed or unzipped? What's in it?
Sent from my Amazon Jem using XDA Free mobile app

BobJayJr said:
Does the sweetener pack work on JEM? Does the pack get flashed or unzipped? What's in it?
Sent from my Amazon Jem using XDA Free mobile app
Click to expand...
Click to collapse
It worked for me. I changed the navigation bar icons with no problem. But with aroma on twrp it gets a little complicated.. It works though. See in the main rom thread. I tried to explain there.

Having the same problem with getting stuck on the "Checking connection..." screen. Coming from CM12, but I did a full wipe in TWRP 2.8.3.0 (checked all the boxes, rebooted back into recovery) then installed the ROM and the GAPPS from the link provided in the post.

Bluetooth got problem
Hi everybody,
I flashed the ROM candy5-release.v2.1.1-20150429-OFFICIAL-jem.zip on Kindle Fire HD 8.9 LTE version and got this error message:
Unfortunately, bluetooth share has stopped
Click to expand...
Click to collapse
Temporarily, I must move the folder Bluetooth in /system/app/ to another place and reboot the OS to disable Bluetooth.
Are there any Lollipop version for KFHD8.9 LTE?
Does anyone got this problem? Any idea?
Thanks.

Can't install "Google Play Games". Error on installation: -505

What's new in this one?

Anyone else having an issue with settings? Initially I dirty flashed Candy5 v2.8 over v2.5. I activated developer options but encountered a "settings stopped" error while trying to access developer options. The "Settings Stopped" issue continued after a clean install. I can't access root. Any suggestions/workaround?
Sent from my Amazon Jem using XDA Free mobile app

BobJayJr said:
Anyone else having an issue with settings? Initially I dirty flashed Candy5 v2.8 over v2.5. I activated developer options but encountered a "settings stopped" error while trying to access developer options. The "Settings Stopped" issue continued after a clean install. I can't access root. Any suggestions/workaround?
Sent from my Amazon Jem using XDA Free mobile app
Click to expand...
Click to collapse
Same problem - "settings stopped" on v.2.8. I went back to version v.2.5, it is more stable.

I'm also returning to 2.1. 2.8, though initially appearing stable, became increasing unstable. Messages like "Unfortunately settings has stopped", "Unfortunately Amazon has stopped", "Unfortunately Android has stopped" became more frequent even after reflashing (clean reflash) the system. Chrome browser also seemed to become more erratic - especially if there are multiple frames per page.
Sent from my KFAPWI using XDA Free mobile app