Develop Bugs

[Q] CM10 Stable - Completely Unstable and Broken

Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.

Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip

Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium

Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.

dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?

Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.

You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.

i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset

If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...

goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.

BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.

Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).

goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.

Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works

wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.

Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end

wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?

Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.

[Q] Any JB 4.3 (or other JB) roms with working ringtone?

Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!

brettbee said:
Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!
Click to expand...
Click to collapse
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.

try beanstalk 1.300
brettbee said:
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.
Click to expand...
Click to collapse
I have been using beanstalk 1.300 with the b-team CM kernel.it has 4.2.2 and everything works! its fast and smooth with great battery life the 4.3 roms have some issues so I am gonna stick with this one

AFAIK everything in the newest Evervolv works.

phillibl said:
AFAIK everything in the newest Evervolv works.
Click to expand...
Click to collapse
Are you using a nightly? Which one?
Does 3G come back after WiFi is turned on?

Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.

kahlil88 said:
Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.
Click to expand...
Click to collapse
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Thanks!

brettbee said:
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Click to expand...
Click to collapse
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.

kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....

kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
brettbee said:
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....
Click to expand...
Click to collapse
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?

brettbee said:
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?
Click to expand...
Click to collapse
What version of gapps are you installing? Try flashing the ROM without installing gapps and see if it will boot, then if you're successful go back into recovery mode and flash gapps-jb-20130813-signed.zip from here.

funny question, does docking mode work with these roms?

Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app

flinzak said:
Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks - found it and downloaded it! I'll give it a try when I can have my phone out of service.....

I flashed Evervolv 10/30 nightly yesterday and it looks like they have the 3G/WiFi toggle issue resolved. The quick settings were missing but, I'm guessing that'll be corrected in the next build. Also, flashed B-Team Kernel. 4.3-s2w version resulted in bootloops but, the 4.3-v2 version worked just fine. No sound issues as far as I can tell.

Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks

jonatcer said:
Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6

ArslanQureshi said:
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6
Click to expand...
Click to collapse
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.

jonatcer said:
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.
Click to expand...
Click to collapse
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean

ArslanQureshi said:
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean
Click to expand...
Click to collapse
Alright thanks a bunch.
Would you, or anyone else still reading this thread, care to weight in on whether Evervolv or CB's rom (Which? Beanstalk?) is more stable?

Problem loading G2 V3 Rom with E980

I have downloaded the G2 V3 update.zip to my phone and have tried installing the zip via CWM. I followed instructions stating factory default first, then flash the update.zip, install the SU add-on 1, then factory default. When I reboot my phone I get the LG boot screen, afterwards my indicator lights both flash on, my phone vibrates and the backlight stays on but I get a blank screen. I left it like this for 20 minutes but it never continues. I have tried rebooting but it does the same thing. I have loaded my previous CM 10.2 Rom since. Tried repeating this process, get same results. Adding to this, when I load the add-on it does say there was a problem with Loki at the end.
Please help.

Are you coming from stock or were you on CM?
I always return to stock before changing roms,, I've heard of people having trouble going from CM to V3....
_________________
Beavers & Ducks!

Always wipe system, cache and dalvik-cache before flashing. I'd also suggest wiping the internal sd card as well. Always gives me the best results. I've jumped from ROM to ROM this way with no problems. :3
Sent from my LG-E988 using XDA Premium 4 mobile app

That has to be what it is, I am going from CM10.2 to this mod. I am going to try to go to stock and then message again my results. Thank you for replying to my message.

tobias87 said:
That has to be what it is, I am going from CM10.2 to this mod. I am going to try to go to stock and then message again my results. Thank you for replying to my message.
Click to expand...
Click to collapse
Yup, that is the issue. Those ROMs do not have stock kernel bundled and hence they do not boot when you come from CM or Carbon or Vanir to V3.
You have to go back to stock and then flash that.
Or there might be another way which might work and will spare you hassles of going back to stock and rerooting. Give it a go.
1. Download this kernel : http://forum.xda-developers.com/showthread.php?t=2363330
This kernel is for stock based ROMs.
2. Install V3 by following the procedure. After second factory reset, before rebooting, flash this kernel. And then reboot.
See if that is successful. It should be. (it will still take 4-5 minutes for first boot )
If not , you can always go back to CM and then go through whole going back to stock thing.

Got The thing to work by flashing the CWM recovery files in three parts. Then updated to V4 and SU. The only thing I can't seem to get working is the wireless reefer devices can connect but the receive no data.
Funkym0nkey said:
Yup, that is the issue. Those ROMs do not have stock kernel bundled and hence they do not boot when you come from CM or Carbon or Vanir to V3.
You have to go back to stock and then flash that.
Or there might be another way which might work and will spare you hassles of going back to stock and rerooting. Give it a go.
1. Download this kernel : http://forum.xda-developers.com/showthread.php?t=2363330
This kernel is for stock based ROMs.
2. Install V3 by following the procedure. After second factory reset, before rebooting, flash this kernel. And then reboot.
See if that is successful. It should be. (it will still take 4-5 minutes for first boot )
If not , you can always go back to CM and then go through whole going back to stock thing.
Click to expand...
Click to collapse

Swype decided to fill in an odd word for what I meant sorry. I meant wireless tether.
tobias87 said:
Got The thing to work by flashing the CWM recovery files in three parts. Then updated to V4 and SU. The only thing I can't seem to get working is the wireless reefer devices can connect but the receive no data.
Click to expand...
Click to collapse

[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