Develop Bugs

Defy 2.2 Re-Release Upgrade to CM7 - Multiple Queries - Plz Help

Hi Friends,
Plz bear with by silly questions and help me (by answering the following queries or redirecting to the threads where i can find appropriate answers. I know these have been discussed earlier in many threads but as a newbie to android, i am a bit confused and would like some specific help here)
I just bought a new Defy in India. It has a green lens with SOC module. It is running on 2.2 Re-Release version exactly as mentioned here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to upgrade to CM7 keeping downgrade ability to stock 2.2 in case i need to go to warranty. I tried to grab some info on this from existing posts and understood a bit but still a bit confused. (just that I dont want to get things wrong)
- Which version/build of CM7 is the latest and stable? Plz provide the link.
- What exactly I need to do to be able to downgrade to official 2.2 stock in order to get warranty in future. Plz explain this stepwise.
I went through the Defy Beginner's Guide. It helped but got confused regarding the following points:
- SBFs, Fixed SBFs, NanDroid Backup, CG versions (All related to make sure I can downgrade to stock 2.2 in future for warranty). Which option is suitable for me? Full SBF / Fixed SBF with Nandroid backup. What exactly I need to check/verify regarding CG versions?
Plz help me.

You will be able to go back to your previous firmware as long as you don't flash the full leaked gingerbread sbf. If you follow the CM7 faq/guide you won't have a problem. I am on 2208 nightly and have no issues. You can follow the guide and replace the rc1 by the nightly as it is a "boot" nightly. If you would like to try later nightlys, you have to flash latest boot first and next wipe cache and dalvic cache and then instal the nightly. Along as you don't flash another boot, the boot image stays the same. You only need to flash it ones, not with every nightly.
Sent from my MB525

Defy 2.2 Re-Release Upgrade to CM7
1.Download superoneclick 1.9.5
2.In your mobile. Settings->Applications->Development(check USB debugging on)
3.Connect your phone to PC. Open superoneclick ->Click ROOT. Thats it your phone is rooted.
4.Restart your mobile.
5.Download 2nd init from android market. install the 2nd init recovery. It will ask the superuser permission Accept it.
6.Uncheck the USB debugging from Settings->Applications->Development and restart the phone now.
7.It will go in to bootmenu select normal boot at now.
8.After mobile booted copy the cm7 rc1 or nightly(whatever you downloaded) zip file to root of your SD card.
9.Restart the phone it will go in to boot menu or you can press vol - button when you see the blue led light.
10.Now go to recovery -> Custom recovery -> Wipe data/factory and Wipe cache -> Install zip file from sd card(select the zip file you copied to sd card) thats it. (Some times after install zip file from sd card goback and WIPE cache only to avoid some instability in fresh ROM)
11.After installation completed reboot the phone now it will go to the boot menu or press vol - button when blue led flash at booting. Make 2nd init as a default boot. thats it. You are in 2.3.5 gingerbread. I recommend CM7 nightly boot-179-4. it is more stable and having less bugs. defycm7.tanguy.tk/cm7-110822-1650-BOOT179-4-Jordan.zip[/url]
To downgrade to Stock rom it is very simple.
1.Download RSD lite and Motorola usb drivers to flash SBF file.
2.Download Stock froyo SBF for your region(Search xda forum)
3.Check USB debugging on your phone and connect to the pc and wait until all motorola drivers install.
4.Open RSD lite(right click and open as a administrator). It will show connected. Now select the sbf file you located on the system and click start and wait till it completes 100% process. thats it. it will flash your phone to stock froyo and it will automatically restart and boot.
Note: Some times when rebooting after RSD lite flash your phone stuck in bootloop(M logo or it continously loading in Android menu). It is better to go to stock recovery(Hold the vol - button and then power button and then release it. you will get android logo with exclamatory symbol. Press vol - and vol + button at the same time to get in to stock recovery). Select wipe data/factory and wipe cache.
*But i would recommend this method before you flashing the full stock sbf.

labsin said:
You will be able to go back to your previous firmware as long as you don't flash the full leaked gingerbread sbf. If you follow the CM7 faq/guide you won't have a problem. I am on 2208 nightly and have no issues. You can follow the guide and replace the rc1 by the nightly as it is a "boot" nightly. If you would like to try later nightlys, you have to flash latest boot first and next wipe cache and dalvic cache and then instal the nightly. Along as you don't flash another boot, the boot image stays the same. You only need to flash it ones, not with every nightly.
Sent from my MB525
Click to expand...
Click to collapse
watz the diff b/w boot179 and nightly?
Also,how to install a boot??

The boot also change the boot.img and the modules. Boot contains things like wifi and kernel, these are taken from official sbfs. At first the were working with base roms for CM7 but with RC1 they included these so everyone will have the same experience. Later boot were for testing if some problems were still present. Latest seems to be better on wifi.
Edit: instal them just the same. If its the first time on cm wipe all in custom recovery, this will erase all apps, for update wipe cache/dalvic, and instal.
Sent from my MB525

but what if I directly flash nightly without rc1, then my boot of the current stock won't be replaced with cm7 properly working,huh??
OR
even the nightlies replace my current boot but the diff is just that boot179 is the latest one??

Only nightlys with boot in there name and the rc1 replace them. yes, if you install a normal nightly, your current boot will be kept. If you want to try the latest nightly, it is best to install the boot. If you com from the 17x(or way you just said) you don't have to do this.
Vinodh3 guide is very good. I would also suggest that nightly.
Sent from my MB525

My first and so far only CM7 installation on my defy was 110822 boot179 nightly.
I started off on vodafone uk 2.2.2 (179-4) firmware. I did not flash another sbf.
I rooted using super1click 2.1. This was the most difficult part, getting hold of motorola adb drivers.
Once rooted, I installed sndinitdefy 1.4_2. Copied the cm7 zip and gapps zips to my SD card. Rebooted a couple of times to make sure all was well.
Then in boot loader I wiped data, cache, dalvik cache, etc. Then applied the cm7 zip. Let it finish installation and boot, then once it was up and running in CM7, I rebooted and installed the gapp zip.
All going great here on that basis.

Guys, I read this topic as well as other ones but I remain confused about ROM versions I can install.
The thing is I was running stock 2.2.2 in my Defy and I got a CM7 RC1 on it. And now my system info says I'm running 2.3.4. Am I still able to go back to stock 2.2.2 as I haven't flashed any other SBF than stock one?
The other thing is: if I'd like to get a newer, nightly version of CM7 to get some minor bugs fixed, what version exactly can I get? Can I download the latest nightly build from 29th August, "cm7-110828-1034-NIGHTLY-Jordan.zip"? Will it work? Do I have to do a WIPE or I can install it with my current CM7 "as is"?
The amount of information I've read is so tremendous that I'm lost in everything. Please help

2908 is a bad one. Many bugs. Try 2208 or before 2908. No data wipe is needed. But do wipe cache and dalvic in advanced. Yes you can downgrade with ease. Only thing you should avoid is to flash the full ginger sbf from motorola. They are work around if you did won't to try that. If so, check greenginger(or something)
Sent from my MB525

i need to send my defy for warranty so i needed to downgrade from cm7 to stock froyo!
therefore, i wanna know will flashing full sbf remove everything such as root, 2ndinit etc??
and i just have to disable usb debugging before flashing full sbf or do i have to do something more??do i have to wipe cache nd data in stock recovery before flashing full sbf or later??
plzz tell me all the steps!!

[ROM][CWM][LTE] ICL53F Deodexed Rooted Busyboxed+Softkeys+APM/AB+ChargeFix (1/2/12)

This is just a very basic stock ROM. I deodexed the ICL53F system image from Google (Android 4.0.2) rooted it and installed busybox. I saw that no such stock ROM was available and decided to share mine.
Features
Stock 4.0.2 ICL53F
Deodexed Framework and System Apps
All APKs Zipaligned
Latest Superuser and su
Busybox Installed
Insecure boot.img (adb remount privileges)
Requirements
LTE Galaxy Nexus
Clockwork Recovery
Kernel and baseband in screenshot below (if you don't have them, look in the 2nd post for the fastboot images - flash them in bootloader prior to flashing the ROM)
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions
No need to wipe data coming from stock
Boot into Clockwork, make a backup (highly suggested)
Wipe dalvik and cache
Flash ROM
Reboot
Profit!
Some things to watch out for
The first boot will take a few minutes
Download
toro_signed_ICL53F_rooted_deodexed_bigxie_010212.zip
MD5: c1499d3f76f0b2eeeac8ab7976ffbec7 toro_signed_ICL53F_rooted_deodexed_bigxie_010212.zip
If you enjoy my work, consider buying me a beer
Donations FabDroid

Advanced Power Menu + Autobrightness Tweaks (credit he_stheone64 on XDA for GSM version)
Adds reboot and recovery options to power menu. Raises auto brightness levels slightly.
*flash this in recovery, wipe dalvik and cache
APM_AB_LTE_ICL53F.zip
57d65c60bafc7e14cec29449dfb01097 *APM_AB_LTE_ICL53F.zip
Fastboot images (optional, for those not on the latest kernel/baseband)
toro_radio_kernel_ICL53F.zip
Code:
fastboot flash boot boot.img
fastboot flash radio radio-toro-i515.ek02.img
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
Softkeys Mod (credit to Paul O'Brien, I learned from his SystemUI.apk to make mine ;-)
Must be on a deodexed ROM to install! Install after initial boot!
Search button, hidden menu buttons on both sides (exposed when apps call for them)
softkeys_mod_ICL53F.zip
4d1713cfc93517cb5c6fa5f97d713be1 *softkeys_mod_ICL53F.zip
*flash this, no need to wipe anything

You have a quick way to revert the modded soft keys?
Sent from my Galaxy Nexus using Tapatalk

bangdrum said:
You have a quick way to revert the modded soft keys?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I would just reflash the ROM, that will switch it back to stock.

Will this work on any of the stock zipaligned roms?
Sent from my Galaxy Nexus using Tapatalk

You can also just insert the systemui.apk from the main ROM in the update.zip of the mod (overwrite the systemui in this zip) and flash.

for some odd reason I could not get this to work. Just kept getting stuck at the goggle logo. Yes I downloaded the correct LTE version.

bangdrum said:
Will this work on any of the stock zipaligned roms?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Not quite sure if it will, those are still odexed. For sure you'll want to delete the SystemUI.odex file if you flash this.
ihyln said:
for some odd reason I could not get this to work. Just kept getting stuck at the goggle logo. Yes I downloaded the correct LTE version.
Click to expand...
Click to collapse
A few things, did you already accept the 4.0.2 OTA prior to flashing the ROM (you need to in order to get the new kernel and baseband)? Did you wipe dalvik and cache when you flashed the ROM? Did you check the MD5SUM to make sure the file wasn't corrupted?

Is there any way to make the search key have long press abilities? Sorry for all the questions bro lol
Sent from my Galaxy Nexus using Tapatalk

bigxie said:
Not quite sure if it will, those are still odexed. For sure you'll want to delete the SystemUI.odex file if you flash this.
A few things, did you already accept the 4.0.2 OTA prior to flashing the ROM (you need to in order to get the new kernel and baseband)? Did you wipe dalvik and cache when you flashed the ROM? Did you check the MD5SUM to make sure the file wasn't corrupted?
Click to expand...
Click to collapse
MD5SUM was correct. I did take the 4.0.2 OTA but I wanted to get a deodexed rom so I gave it a try. Also wiped dalvik and cache prior to installing.

I have the kernel but my baseband is ek05/ek02 how would i change the baseband i forgot to make a backup and im not on stock

Tried this an got a bootloop.
Logcat gives me the following:
quote removed because error is gone, i was trying the wrong ROM... i am so stupid -.-
Click to expand...
Click to collapse
Maybe this can help somebody
I was coming from 4.0.1 stock ROM rooted without wipe, only cleared dalvik cache and /cache.
I am happy i did a nandroid backup
EDIT: error is gone, i was trying the wrong ROM... i am so stupid -.-

myxor said:
I was coming from 4.0.1 stock ROM rooted without wipe, only cleared dalvik cache and /cache.
I am happy i did a nandroid backup
Click to expand...
Click to collapse
The issue could be that you came from 4.0.1 instead of 4.0.2 like the OP called for. I would think that the upgrade would have gone smoother than the downgrade (like if you were on 4.0.2 trying to flash a 4.0.1 ROM) but i bet you it would fix your issues just to update first to the current build OTA or you could wipe data/cache.

Hey everyone that is coming from 4.0.1, I uploaded the new kernel and radios into the 2nd post.
You can flash them in bootloader using fastboot, then reboot right into recovery to flash the ROM.

I don't suppose that you can craft a version of the soft-key mod like Paul's that has the menu button always shown? This is the only thing I have issues with in ICS - many apps (like FBReader) don't show the menu button, which makes the app useless...
Paul's patch still causes the top and bottom bar to disappear on the LTE Nexus...

jeffreycentex said:
I don't suppose that you can craft a version of the soft-key mod like Paul's that has the menu button always shown? This is the only thing I have issues with in ICS - many apps (like FBReader) don't show the menu button, which makes the app useless...
Paul's patch still causes the top and bottom bar to disappear on the LTE Nexus...
Click to expand...
Click to collapse
My softkeys are built using the exact same mods he used in his MCR ROM.
Those menu buttons are persistent in both corners, but the three dots only show up when apps call for them.

bigxie said:
Not quite sure if it will, those are still odexed. For sure you'll want to delete the SystemUI.odex file if you flash this.
A few things, did you already accept the 4.0.2 OTA prior to flashing the ROM (you need to in order to get the new kernel and baseband)? Did you wipe dalvik and cache when you flashed the ROM? Did you check the MD5SUM to make sure the file wasn't corrupted?
Click to expand...
Click to collapse
OP i don't know why you don't have more thanks but this thread is absolutely perfect. i was looking for a stock rom that was deodexed so i could load the paul obrien mods as well as the battery display mods, thanks for your hard work.

So I have a stock 4.0.2 how do I go about getting this installed?

ihyln said:
So I have a stock 4.0.2 how do I go about getting this installed?
Click to expand...
Click to collapse
Read the OP.

bigxie said:
Fastboot images (optional, for those not on the latest kernel/baseband)
toro_radio_kernel_ICL53F.zip
Code:
fastboot flash boot boot.img
fastboot flash radio radio-toro-i515.ek02.img
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
Softkeys Mod (credit to Paul O'Brien, I learned from his SystemUI.apk to make mine ;-)
Must be on a deodexed ROM to install! Install after initial boot!
Search button, hidden menu buttons on both sides (exposed when apps call for them)
softkeys_mod_ICL53F.zip
4d1713cfc93517cb5c6fa5f97d713be1 *softkeys_mod_ICL53F.zip
*flash this, no need to wipe anything
Click to expand...
Click to collapse
tried flashing the new baseband/kernel, flashes the first radio perfectly, but when i try and flash the radio-cdma, it sends the file to the phone, but gets stuck when writing it to the phone
*updated* both radios flash perfectly. It just takes a really long time to write the radio-cdma to the phone. thanks for your help!!!

NOOB: Rooting and Kernal for Galaxy Nexus

Anyone willing to give some time to write up on what I should do?
I heard that the best combination is bigxie's rom along with franco's kernel.
How do I go about doing this? Do I need to backup my kernel, firmware etc?
I really appreciate the help and am willing to reward anyone who can take me through this step-by-step.

Read the stickied post in GSM (or) CDMA Development forum that tells you how to get started.
CDMA: Verizon
GSM: Not verizon? SIM card? You have GSM.
Best combination is whatever ROM that is 4.0.3 with the features that YOU want.
AOKP or Bigxie + Franco Kernel

zephiK said:
Read the stickied post in GSM (or) CDMA Development forum that tells you how to get started.
CDMA: Verizon
GSM: Not verizon? SIM card? You have GSM.
Best combination is whatever ROM that is 4.0.3 with the features that YOU want.
AOKP or Bigxie + Franco Kernel
Click to expand...
Click to collapse
I'm GSM.
What would you recommend? AOKP or Bigxie?

BrandonPrice31 said:
I'm GSM.
What would you recommend? AOKP or Bigxie?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1392310
I personally use the old school method with fastboot oem unlock rather than that to root. But I think that one might be easier for you to use.
I personally use AOKP + Franco's Kernel.

zephiK said:
http://forum.xda-developers.com/showthread.php?t=1392310
I personally use the old school method with fastboot oem unlock rather than that to root. But I think that one might be easier for you to use.
I personally use AOKP + Franco's Kernel.
Click to expand...
Click to collapse
Will that tool backup my current state?

BrandonPrice31 said:
Will that tool backup my current state?
Click to expand...
Click to collapse
Backup as in what? Your apps, data? Probably not.
Unlocking the bootloader will do a complete wipe of your phone. So backup whatever you need that is important or you'll lose it.

zephiK said:
Backup as in what? Your apps, data? Probably not.
Unlocking the bootloader will do a complete wipe of your phone. So backup whatever you need that is important or you'll lose it.
Click to expand...
Click to collapse
Precisely, my apps, data.... I presume that's backed up by my Google account and is synced automatically correct?
What is a kernel?

BrandonPrice31 said:
Precisely, my apps, data.... I presume that's backed up by my Google account and is synced automatically correct?
What is a kernel?
Click to expand...
Click to collapse
Your apps, data are not backed up. At most it'll go to the Android Market and redownload all of them. But after you've rooted you can successfully back up all of this stuff using a handy tool named Titanium Backup. I recommend getting the pro version or you can use MyBackUp. Which does the same thing but I've never tried it.
Also, I believe "fastboot oem unlock" (unlocking bootloader) wipes your sdcard as well, so backup any important pictures or whatever you need before doing this.
Kernel: http://en.wikipedia.org/wiki/Android_(operating_system)#Design

zephiK said:
Your apps, data are not backed up. At most it'll go to the Android Market and redownload all of them. But after you've rooted you can successfully back up all of this stuff using a handy tool named Titanium Backup. I recommend getting the pro version or you can use MyBackUp. Which does the same thing but I've never tried it.
Also, I believe "fastboot oem unlock" (unlocking bootloader) wipes your sdcard as well, so backup any important pictures or whatever you need before doing this.
Perfect! In that tool it shows me, theres different options. Should I rename Restore Files and Flash CWM Recovery?
How do I get 4.0.3? I'm on 4.0.1 right now?
Do I download Release 2.1 AOKP GSM B15.zip?
Click to expand...
Click to collapse

BrandonPrice31 said:
Perfect! In that tool it shows me, theres different options. Should I rename Restore Files and Flash CWM Recovery?
How do I get 4.0.3? I'm on 4.0.1 right now?
Do I download Release 2.1 AOKP GSM B15.zip?
Click to expand...
Click to collapse
To get 4.0.3, yeah.. you need to download either:
- AOKP Milestone 2 [Have to get it from Rootzwiki.. as latest on XDA is build 15]
- Bigxie's Build 8
(Select one of them that you'd like to use)
and Franco Kernel.. it'll improve your battery life // performance.
You just need to unlock bootloader, flash clockwork recovery

zephiK said:
To get 4.0.3, yeah.. you need to download either:
- AOKP Milestone 2 [Have to get it from Rootzwiki.. as latest on XDA is build 15]
- Bigxie's Build 8
(Select one of them that you'd like to use)
and Franco Kernel.. it'll improve your battery life // performance.
You just need to unlock bootloader, flash clockwork recovery
Click to expand...
Click to collapse
Can you link me to AOKP?
If I do AOKP means I don't need Bigxies right?

BrandonPrice31 said:
Can you link me to AOKP?
If I do AOKP means I don't need Bigxies right?
Click to expand...
Click to collapse
AOKP: http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-milestone-2/
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=1367341
And yes that is correct.
Basically once you have Clockwork Recovery up and running (black background, tealish colors).. although I don't think the link that I gave you installs Clockwork Recovery Touch Enabled (which is really cool). Basically use the volume buttons and go into:
install zip from sdcard
select
choose AOKP (this will flash it)
select again
choose franco kernel (this will flash it-- you have to do this in order)
wipe: factory, cache, (you can find these on the main menu), go into advanced and wipe dalvik cache too.. then hit go back then reboot system!
congrats you will be on 4.0.3 with a custom kernel.

zephiK said:
AOKP: http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-milestone-2/
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=1367341
And yes that is correct.
Basically once you have Clockwork Recovery up and running (black background, tealish colors).. although I don't think the link that I gave you installs Clockwork Recovery Touch Enabled (which is really cool). Basically use the volume buttons and go into:
install zip from sdcard
select
choose AOKP (this will flash it)
select again
choose franco kernel (this will flash it-- you have to do this in order)
wipe: factory, cache, (you can find these on the main menu), go into advanced and wipe dalvik cache too.. then hit go back then reboot system!
congrats you will be on 4.0.3 with a custom kernel.
Click to expand...
Click to collapse
So to sumarize I'm going to be using AOKP Milestone 2 with Franco's Kernal, correct? Will I be able to do this all with that tool you provided? Are you sure I should not rename the Restore Files nor glash the CWM?

BrandonPrice31 said:
So to sumarize I'm going to be using AOKP Milestone 2 with Franco's Kernal, correct? Will I be able to do this all with that tool you provided? Are you sure I should not rename the Restore Files nor glash the CWM?
Click to expand...
Click to collapse
Yes that is correct. And it is kernel not kernal (doesn't bother me but other people might. I don't know what that tool would be restoring as you don't have any nandroid backups present or any backups at all.
To restore something, something needs to be present to "restore."

zephiK said:
Yes that is correct. And it is kernel not kernal (doesn't bother me but other people might. I don't know what that tool would be restoring as you don't have any nandroid backups present or any backups at all.
To restore something, something needs to be present to "restore."
Click to expand...
Click to collapse
I just installed Titanium backup on my non-rooted phone.. Can't find the application? How do I get to it?

BrandonPrice31 said:
I just installed Titanium backup on my non-rooted phone.. Can't find the application? How do I get to it?
Click to expand...
Click to collapse
App won't work on a non-rooted device. To be rooted, you need to unlock your bootloader. Unlocking your bootloader will fully wipe your phone as I mentioned previously.
1. Backup any important files off your device. You cannot backup apps/data. By this step I mean important files such as pictures, documents, whatever.
2. Unlock bootloader
3. Flash Clockwork Recovery
4. Flash ROM, Kernel [also wipe]
5. Reboot
6. You're on 4.0.3

zephiK said:
App won't work on a non-rooted device. To be rooted, you need to unlock your bootloader. Unlocking your bootloader will fully wipe your phone as I mentioned previously.
Click to expand...
Click to collapse
Oh, I don't care..... My applications are synced with my account anyway.. Don't really lose much haha!
Alright, waiting till' my phone is fully charged then going to give it a go. PM for compensation

zephiK said:
App won't work on a non-rooted device. To be rooted, you need to unlock your bootloader. Unlocking your bootloader will fully wipe your phone as I mentioned previously.
1. Backup any important files off your device. You cannot backup apps/data. By this step I mean important files such as pictures, documents, whatever.
2. Unlock bootloader
3. Flash Clockwork Recovery
4. Flash ROM, Kernel [also wipe]
5. Reboot
6. You're on 4.0.3
Click to expand...
Click to collapse
Just to verify, that application unlocks, and flashes my clockwork recovery for me, correct?

BrandonPrice31 said:
Oh, I don't care..... My applications are synced with my account anyway.. Don't really lose much haha!
Alright, waiting till' my phone is fully charged then going to give it a go. PM for compensation
Click to expand...
Click to collapse
You don't really need to wait for your phone to be charged, it'll charge while your phones plugged in your USB
@Post above: Yes that is correct. You'd want to do numbers: 1 & 4
Then go to 17.... boot into Android, it'll tell you to put your Google information etc etc.. skip all of it, and what you want to do now is get to the homescreens. When you're in the home screen, drag the zip of AOKP and the kernel onto the root of your sdcard (main folder). Then you can use that tool again and go to 16 (or if you manually want to... turn the phone off then hold volume up and down + power [all three] then that'll bring you to fastboot mode, press the volume rocker until you see "Recovery" when it's there.. press on the power button and it'll bring you to a screen looking like this,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically once you have Clockwork Recovery up and running (black background, tealish colors).. although I don't think the link that I gave you installs Clockwork Recovery Touch Enabled (which is really cool). Basically use the volume buttons and go into:
install zip from sdcard
select
choose AOKP (this will flash it)
select again
choose franco kernel (this will flash it-- you have to do this in order)
wipe: factory, cache, (you can find these on the main menu), go into advanced and wipe dalvik cache too.. then hit go back then reboot system!

zephiK said:
You don't really need to wait for your phone to be charged, it'll charge while your phones plugged in your USB
@Post above: Yes that is correct. You'd want to do numbers: 1 & 4
After doing those then go to 16... when in fastboot mode, press the volume rocker until you see "Recovery" when it's there.. press on the power button and it'll bring you to a screen looking like this,
Click to expand...
Click to collapse
Can I root for the sake of rooting? So I can get rooted applications etc?

Reboot cycle

Can someone please help me? I'm worried my phone may be really screwed up.
I recently rooted my phone using the instructions from this forum and everything went great. I had no problems for a couple days.
Then I installed Titanium Backup and backed up all my apps.
Then I deleted some apps, like Allshare, Dropbox and other bloatware. I still had no problems.
Then I saw that an OTA update was available. I read somewhere that the update can cause problems if stock apps are removed, so I went into Titanium Backup to restore the apps I had deleted. This is where things started to go wrong. When I tried to restore apps, Titanium Backup was hanging and I had to restart the phone. After Dropbox wouldn't restore, I restarted the phone and I'm stuck in a reboot cycle. The phone restarts, I see the usual boot up screens, I see my lock screen, there's a circled i with a cross through it in the notification bar and I can't unlock the phone. How can I get access to my phone back? I'm really upset that this has happened. I thought I was being very careful and this is exactly the kind of thing I was trying to prevent from happening.
Please help.

BraveRobot said:
Can someone please help me? I'm worried my phone may be really screwed up.
I recently rooted my phone using the instructions from this forum and everything went great. I had no problems for a couple days.
Then I installed Titanium Backup and backed up all my apps.
Then I deleted some apps, like Allshare, Dropbox and other bloatware. I still had no problems.
Then I saw that an OTA update was available. I read somewhere that the update can cause problems if stock apps are removed, so I went into Titanium Backup to restore the apps I had deleted. This is where things started to go wrong. When I tried to restore apps, Titanium Backup was hanging and I had to restart the phone. After Dropbox wouldn't restore, I restarted the phone and I'm stuck in a reboot cycle. The phone restarts, I see the usual boot up screens, I see my lock screen, there's a circled i with a cross through it in the notification bar and I can't unlock the phone. How can I get access to my phone back? I'm really upset that this has happened. I thought I was being very careful and this is exactly the kind of thing I was trying to prevent from happening.
Please help.
Click to expand...
Click to collapse
Be Brave, little Robot.
From what you've described, you're not out of luck here. I seriously doubt you've hard-bricked your phone. In order for me to help you, I need you to verify the following:
You can get into your Recovery (either CWM or TWRP).
You can get into download mode.
If these two are true, you're in luck. Below, I've copied a post I made yesterday helping someone else through a similar situation. Some things may be a bit different, but for the most part, it'll help you through you stuff.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Ok, now that we've identified what's wrong with your phone, we can now help solve it!
Solution/Fixes
Are you able to get into a custom Recovery? If not, you need to use Odin and follow The Rooting Guide to get back to a custom recovery (I recommend TWRP, but CWM is just as good).
Next, you want to download a Rom and put it on your device. I'd recommend (just for now), to get Freeza's stock TW Rom.
Now, before you try to flash this Rom, you'll have to wipe. In order to get rid of the FCs, you'll have to at least wipe System. I'd recommend a full wipe of your Internal SD Card (after backing up anything you want to save), but it's not technically necessary. Afterwards, you can wipe data and cache/dalvik cache.
Then you can flash your Rom. It seems like you know how to do this, but in case you don't, I have previously posted directions over here.
Hope this helps!
Click to expand...
Click to collapse

Be Brave, little Robot.
Click to expand...
Click to collapse
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?

BraveRobot said:
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
Click to expand...
Click to collapse
I've always given my instructions in TWRP, but the options/settings should be very similar in CWM. In the quoted post below, there are instructions on how to flash a new Rom.
For your situation, I'd recommend wiping system in step 4 below:
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
I'm going home from work for the night. I'll try to keep up with the thread, but if you have any questions, look over at this thread, I think Miguelcoo1 asked just about every question that can be asked, haha (he's a good guy, I'm just giving him a hard time).

In CWM recovery it says wipe data/factory reset. Is that what I want?

BraveRobot said:
In CWM recovery it says wipe data/factory reset. Is that what I want?
Click to expand...
Click to collapse
Is there an advanced option? Factory rest only wipes Data and Cache, if I recall correctly.

Here are my options:
- reboot system now
- install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
In advanced, here are my options:
- reboot recovery
- wipe dalvik cache
- wipe battery stats
- report error
- key test
- show log
- fix permissions
- go back
By the way, I have to wait 5 minutes between posts because my account is new. (How do I get rid of that?)

BraveRobot said:
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
Click to expand...
Click to collapse
Here's the guide for CWM

Ok, it sounds like you're on an old version of cwm. In my Sig, click on flashable and you can flash the newest version of cwm. Then you should have the option to wipe system.
Sent from my SPH-L710 using xda app-developers app

topherk said:
Ok, it sounds like you're on an old version of cwm. In my Sig, click on flashable and you can flash the newest version of cwm. Then you should have the option to wipe system.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Alright. I don't mean to sound ungrateful, but this is all very new to me. How do I flash the new CWM onto my phone?

g_money said:
Here's the guide for CWM
Click to expand...
Click to collapse
Oh! from g_money's guide, under "Mounts and Storage" there should be an option to wipe system. Now be aware, wiping system is wiping your Rom, so you won't be able to boot your phone back up to anything besides recovery and download modes (which is no different than you can do right now anyways).

topherk said:
Oh! from g_money's guide, under "Mounts and Storage" there should be an option to wipe system. Now be aware, wiping system is wiping your Rom, so you won't be able to boot your phone back up to anything besides recovery and download modes (which is no different than you can do right now anyways).
Click to expand...
Click to collapse
I am so freaking lost.
What is the end-game here? Am I trying to wipe system and then reflash a new rom? And if so, where does that rom come from? Am I basically starting over like in the root guide using Odin?

BraveRobot said:
I am so freaking lost.
What is the end-game here? Am I trying to wipe system and then reflash a new rom? And if so, where does that rom come from? Am I basically starting over like in the root guide using Odin?
Click to expand...
Click to collapse
If you go into recovery/backup and restore/restore, do you have any backups listed?

g_money said:
If you go into recovery/backup and restore/restore, do you have any backups listed?
Click to expand...
Click to collapse
It says "No files found."
So I guess I didn't back anything up?

Could someone clue me into what I'm trying to do?
Am I trying to flash a new rom or do I need to do something else?
Sorry for being a noob. I'm trying to learn about this stuff, but it's a little difficult. I really appreciate you guys helping me.

BraveRobot said:
Could someone clue me into what I'm trying to do?
Am I trying to flash a new rom or do I need to do something else?
Sorry for being a noob. I'm trying to learn about this stuff, but it's a little difficult. I really appreciate you guys helping me.
Click to expand...
Click to collapse
Yes the instructions topherk gave you where to wipe and flash freezas stock rom. He gave you the links. Make sure you have the rom on your sd card ready to flash.
Transmitted with a portable device using Xparent Blue Tapatalk 2

Ok, that worked. Thanks guys! Everything seems to be back working again.
Does anyone have any idea went wrong with my Titanium Backup? It's kind of useless if it's going to crash my phone when I use it for the main thing it was designed for.
Edit: Actually, I may try to return my phone to stock. Can anyone recommend a guide to un-doing root access and putting everything back completely stock? I think that's probably better for someone with my level of knowledge.

No I think your ok. At some point you restored one bad data or something. The only thing you should ever restore are apps you downloaded from the play store. Never restore any system apps. And samsung apps (bloat) you don't want to delete you just want to freeze.
Transmitted with a portable device using Xparent Blue Tapatalk 2

BraveRobot said:
Ok, that worked. Thanks guys! Everything seems to be back working again.
Click to expand...
Click to collapse
Good to hear
BraveRobot said:
Does anyone have any idea went wrong with my Titanium Backup? It's kind of useless if it's going to crash my phone when I use it for the main thing it was designed for.
Click to expand...
Click to collapse
Reread topherk's previous posts. It's a great guide for understanding Titanium. And Titanium is an awesome program.
BraveRobot said:
Edit: Actually, I may try to return my phone to stock. Can anyone recommend a guide to un-doing root access and putting everything back completely stock? I think that's probably better for someone with my level of knowledge.
Click to expand...
Click to collapse
LOL. I hear ya. But if your phone's working, it's all good right? QBking77 has a video on unrooting here. After what you've been through, you may want to stick around and learn even more?

g_money said:
Good to hear
Reread topherk's previous posts. It's a great guide for understanding Titanium. And Titanium is an awesome program.
LOL. I hear ya. But if your phone's working, it's all good right? QBking77 has a video on unrooting here. After what you've been through, you may want to stick around and learn even more?
Click to expand...
Click to collapse
Yeah, I guess I'll keep it rooted, but I'm going to give things a few days rest after that scare. I need my phone! Maybe I'll come back and mess with it more later.

CM 11 4.4 kitkat issue

I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?

mr. ya-di-da said:
I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?
Click to expand...
Click to collapse
Flash it from cwm... but after the flash completes, reboot recovery and do you're wipes ( again ) and flash kitkat from it's recovery. Then reboot.
Let it chill for a few minutes, then boot back to recovery and flash you're 4.4 gapps.
This process always worked for me on 4.3 and I'm assuming it will work on 4.4. But I've not flashed 4.4 yet. So proceed with caution.
Good luck...

I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?

mr. ya-di-da said:
I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?
Click to expand...
Click to collapse
I'm not sure about the mobile Odin issue... are you making sure the tar file for the kernel is a good download and that it is compatible with the Android version and rom you're trying to run...?
Try downloading the Directboot EL29 kernel from rwilco12's repo.. ( make sure you get the Directboot EL29 kernel and not the stock el29 kernel )
After you have it and the rom you want on you're sdcard... use mobile Odin to flash the el29 db kernel.. it should boot to recovery on it's own..
Push volume up, volume down, volume up... this enables the power button as the select button...
Do you're wipes... and flash 4.4...reboot recovery... do wipes.. ( data, cache, dalvik, and format system )...flash 4.4 again.. reboot.. settle in for a few minutes and then boot recovery and flash gapps 4.4...reboot.
Let me know how it goes... I'll stick around tonight until we get ya up and running...

It failed.. (status 7)

mr. ya-di-da said:
It failed.. (status 7)
Click to expand...
Click to collapse
Ok... I'll try to get to it tomorrow... but Thursday at the latest.

OK thx. I saw that other people where getting the same fail (status 7) let me know what u find.

Status 7 is a syntax error in the updater script... Probably missing a semicolon or something silly like that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Not related to this issue, unsure if it would be better etiquette to make my own thread for this, but an issue I'm having with dastins CM11 ROM (12-04-13 version) is that I have two "Internal Storages" instead of one (I do not own/use a SD card)
On CM10/10.1/10.2 I had one internal storage, but on CM11 I have a 2GB internal storage and then a second internal storage (that things seem to not be installed to at all) with the remainder of my devices space.
One of the applications I used a lot on stock TouchWiz and earlier versions of CM is larger than two gigs, so on CM11 I can't even install it because it says I have insufficient storage. Is there a way I can combine the two internal storages into one, so it functions like it did on CM10.2 so I can use all of my devices space instead of only 2GB?
---------
Another question, and this one I'm probably just being blind and not seeing it, or maybe this setting is in a different location in KitKat, is my phone is set to USB mass storage instead of MTP. Normally I head over to Settings > Storage > hit the menu key and change USB connection type to MTP, but the menu key doesn't seem to do anything anymore on the Storage page. Where would I change to MTP instead of Mass Storage, or how can I just disable Mass Storage, I honestly don't care about being able to get any files on/off the device, but 90% of the time I'm charging on USB and I just don't want a full screen prompt showing up every time I touch my phone saying "Hey! It's Plugged In! Do you want to turn USB Storage on?"

You need to flash cm11 with the newest cwm... The old regular way of the"safe" recovery doesnt work... The easy way Is to download the blasphemy kernel and install it then boot back into recovery... It will be cwm 6.0.4.5... Flash the rom with this and no status 7...
Hope this helps...
Sent from my SPH-D710 using Tapatalk 2

I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.

kitkat 4.4.1
I rooted my device using rwilcos fl24 method although I was on a fd24 model. After root I flashed a custom recovery using Odin I believe it was agats...I then proceeded to flash a ROM cm10.1 then upgraded to cm 10.2. Now running KitKat 4.4.1 12/7 edition I believe and works like a charm...thought I had a battery problem because it wouldn't charge right it would take forever. I didn't I jus had to stop oc/uv ...BTW using the kernel that came with the rom flashed using cwm recovery from cm10 which was on jb not ICS and works fine little bugs here and there such as attempting to open incognito window fc browser the battery read when phone was off was inconsistent versus when the device is off but other then that KitKat is great if I can help anyone I'll be more then glad to I don't mind helping people that don't know I don't give attitude and noon user friendly,after all I was there once....besides all the guys who really know what thier doing are busy creating Roma and tweakimg programs to keep us happy let's make it a little easier on them like I said I don't know everything but I have some knowledge and if I'm able to point you in the right direction without wasting your time I will

easyrider77 said:
I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.
Click to expand...
Click to collapse
There's a tread that might use your assistance
Sent from my d710 using XDA Premium 4 mobile app

CM 4.4.1 build 2013-12-07
Hey guys...Been rocking this build for a month now with no real problems. Only a couple of things i have noticed and thought I would drop in and mention since I haven't heard about it talked about in the main thread or here yet.
1. Every once in a while I will be showing full 3g bars and wont connect to the internet (says "no connection") I have fixed this with just toggling off and then back on the Sprint Radio Toggle in the drop down window. The phone will then immediately connect after.
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
SPH-D710 EL26.....flashed to Boost Mobile with working Hangouts MMS and SMS from day one (no fix)
Build; 4.4.1 2013/12/07
Everything else is just ROCK SOLID, and love this ROM.

adjday said:
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
Click to expand...
Click to collapse
This Camera Fix worked to get my camcorder working perfectly. Have you tried it? http://forum.xda-developers.com/showthread.php?p=48620791&highlight=3a04f599232ee62c6b63a6e4f1d3f7d3#post48620791

You can uninstall the gallery app (using titanium backup)
Then download and install a different Kit Kat gallery app...(just search google, it's everywhere Lol)