Database Develop

[Q] can't get Cyanogenmod working

I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1

adrazar said:
I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1
Click to expand...
Click to collapse
try this:
using a rom that works flash a new recovery image using ROM Manager (find it in the market)
Tell ROM Manager to flash the recovery for ClockworkMod 2.5.0.1
Then Reboot to recovery.
**********NANDROID FIRST!!*********
Starting the flash:
1. Choose the "Wipe data/factory reset" then click "wipe cache partition"
2. Choose "install zip from sdcard" and choose "choose zip from sdcard"
3. Pick the zip file with the CM6 make sure it completes and the installer confirms that it is complete.
4. Reboot phone. This might take more then 5 mins on the initial boot, when it boots up all the way and everything has loaded, do one more reboot to clear out the cache from the initial boot and you are good to go
**If this doesnt work for you, follow step one, select a DIFFERENT ROM, reboot, then reboot into recovery, then wipe again, and flash back CM6.

I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.

adrazar said:
I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.
Click to expand...
Click to collapse
Find a new download of CM6, the one you downloaded was corrupt, try finding the thread, its in Development so find the extreme blue or redglass version.

I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.

Does anyone know what those error messages could be caused by or a way to get around this issue?

adrazar said:
I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.
Click to expand...
Click to collapse
adrazar said:
Does anyone know what those error messages could be caused by or a way to get around this issue?
Click to expand...
Click to collapse
What recovery are you using?

I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid

adrazar said:
I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid
Click to expand...
Click to collapse
That's probably the problem, try the 1.7 Darch RA, much better IMHO

Also ive noticed sometimes when I download a rom onto my computer for some reason it doesnt download the whole file correctly. So just make sure that when you download your rom to your computer the the size of the file is correct.If the rom is 50 mb make sure your download is the same.

I found a post that I believe I got that one from (RA-Darchstar.img) but it is an img file and i am having trouble getting that to install. i found another post elsewhere telling me to use commands from the SDK, it said to use
cd C:\android-sdk-windows\tools
adb devices
adb shell
flash_image recovery /sdcard/RA-Darchstar.img
exit
adb shell reboot recovery
which seems like it should work however when I do the flash_image recovery /sdcard/RA-Darchstar.img it tells me that the flash_image cannot be found. is this the wrong command line? and i do have the file on my phone's SD card in the root directory. or is there another way to get the 1.7 Darch RA?

never mind on my last question I figured it out, I wasn't in the Recovery program I already had when trying to do it. I got the 1.7 Darch RA on and working then tried to flash some of the ROMs again and every one of them failed with the same logcat errors as before.

Try backing up ur SD then taking out ur SD and formatting it on ur CPU then put it back in ur phone and format it threw the recovery I have a 28 MB swap and the rest for the system them go to ext and upgrade/update ur ext from ext2 to ext3 then try and flash CM6.1 hope this helps good luck.
Root-Hack-Mod-Always™

I formatted my card via the computer, formatted everything that RA-Darchstar will let me format, I then set up the partitions and upgraded to ext3, and then copped the CM6.1 to the phone and installed it (also tried EXTBLUE_09NOV). the end result was the same as each other time I have tried to install any of them CM6 ROMs.

Ok I ended up getting it to work by following some of the things I read on
http://forum.cyanogenmod.com/topic/...-cm-build-but-cm-6-nightly-tests/page__st__20
the part where they told this other person to extract the framework.jar to the PC and point adb to it.

[CWM-APP] full_wipe && easy_upgrade_wipe ZIPs [EXT2,3&4], last updated [2014-06-23]

[CWM-APP] full_wipe && easy_upgrade_wipe ZIPs [EXT2,3&4], last updated [2014-06-23]
Hello everybody!
I got inspired by mero01, who made similar tools for my previous mobile phone, the HTC Desire HD.
Imho a new version of an Android ROM should NEVER ever do a full wipe. Personally I prefer to wipe on my own AND to _personally_ have the option which file system is going to be used.
That's why I've created my own zip files, which do either a FULL_wipe or an easy_upgrade_wipe.
These zip files could work on multiple phones, but they are only tested and confirmed to be working on the LG Optimus 2x (P990). Just for the sake I've also implemented a check inside of them if that's the phone, which the wipe(s) are performed on.
**** !NONE WILL FORMAT YOUR SDCARD! ****
I DON'T TAKE ANY RESPONSIBILTY FOR DATA LOSS OR ANY DAMAGE CAUSED TO YOUR DEVICES. USE AT YOUR OWN RISK!!! UNDO IS NOT POSSIBLE!
PREREQUISITES:
* Clockworkmod Recovery (recommended version: v6.0.2.5)
INSTRUCTIONS FOR EVERY FILE:
Code:
1. Download the zip file you want.
2. Place it anywhere in your /sdcard/
3. Reboot into CWM recovery
4. Install zip from sdcard
5. CONFRIM --- CAUTION! THIS IS UNDO-ABLE!!!
6. done :)
7. Don't reboot, flash any rom you want
8. Flash it
9. Reboot and have fun! ;)
FULL_WIPES
This patch comes in two versions (EXT3 and EXT4) and needs to be applied prior to the flash of any ROM. It will WIPE your device and format all partitions either in EXT3 or EXT4.
Wipes performed:
* SYSTEM
* DATA
* CACHE (always EXT3)
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
EASY_UPGRADE_WIPES
These patches also come in the previous two versions (EXT3 and EXT4) and there is an additonal lite variation, which won't wipe your dalvik cache. Use the easy upgrade wipes if you DON'T want to remove your data (especially useful for ROM upgrades)!
Wipes performed:
* SYSTEM
* CACHE (always EXT3)
* non lite versions: Wipes the dalvik cache on DATA
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
NO_JOURNAL
This won't do any wipes, but will remove the JOURNAL(S) on your file systems. If it gets applied to EXT3 partitions it clearly results in EXT2 partitions.
You will get the fastest possible EXT* file systems if it is applied to the EXT4 partitions.
It can also be applied on already existing file systems, although I'd suggest to use a clean file system. Make a backup if you still want to perform it, because it can be dangerous!
Wipes performed:
* NONE
CHANGELOG:
Code:
[U]2014-06-23[/U]
- New LITE easy upgrade wipes available, which won't clean your dalvik cache.
[U]2012-12-10[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.5 (ICS versions only)
- Fixed system partition wipe.
[U]2012-11-27[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.4
- Fixed progress bars.
- Now available in two versions: one for the old (GB), one for the new (ICS) partition layout
- Easy upgrade wipes will now also clean the dalvik cache
- All full and easy wipes re-made from scratch, please use with care and eventually perform a backup before using them.
[U]2011-12-28[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.3
- First public release
************************************************************
[U]2012-12-10[/U]
NO_JOURNAL v0.3 (ICS version only)
- Fixed system partition converting.
[U]2012-11-27[/U]
NO_JOURNAL v0.2
- Fixed progress bars
[U]2011-12-28[/U]
NO_JOURNAL v0.1
- First public release
Have fun!
Greetings,
dr4go

Frequently asked questions (FAQ):
What is the difference between the o and n versions?
The o stands for OLD-, whereas n is an abbreviation for NEW-partitioning layout. Unfortunately LG changed the location of the data partition (from mmcblk0p8 to mmcblk0p9).

so what's the difference between the erase/reset data factory on CWM???

By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.

koboltzz said:
By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.
Click to expand...
Click to collapse
Exactly. Thanks for the answer koboltzz.
For the HTC Desire HD there was also an EXT4 version of CWM available, which changed the default algorithms of the "Wipe data/Factory reset" and the "Format" options to EXT4.
But with the latter possibility you loose the ability to format EXT3 partitions. That's also why I always used mero01's zip files to accomplish wipes.
Imho it's the best option, because if you REMOVE the formatting lines from the ROMs you want to flash it's absolutely no problem to also use an EXT3 designed ROM (like Hypnos2X for example) on EXT4 file systems (that's the operating system I'm currently on).
And I tell you also because I dislike the FULL wipes on nearly every ROM available for the LG Optimus 2X. If you have a problem and just want to reinstall the ROM without loosing any data there is no way to do that.
Yes, an easy wipe should always be done by the standard ROM zip itself - of course... but I've always also removed those lines, because that way you also get the freedom of the file system.
It's up to you...

sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
Using it and after that flashing Fr19 with ext4 Kernel (from modaco) -> no boot at all ->freezing
This will not happen, if you first do a fullwipe by cwm (ext3), then flash Fr19 and after that use the universal converter to ext4 from benee.
But this only changes data and system partition to ext4 by default.
There is definitely something wrong with the script, an other example:
First flashing 0-full_wipe_0.3_ext4.zip
after that Fr19 ROM (up to this point it would have been a bootfreeze, look above)
and after that flashing universal converter to ext4, phone will boot now, but will not be able to install any app 'there is insufficient space' (which is totally not true), most likely because cache partition is fu.cked up by 0-full_wipe_0.3_ext4.zip
Time for version 0.4

koboltzz said:
sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
[...]
Time for version 0.4
Click to expand...
Click to collapse
I will look into it. Thank you for the additional information.

Delete this comment i guess i need to learn how to read im sorry!

dr4go said:
I will look into it. Thank you for the additional information.
Click to expand...
Click to collapse
Anything new to this?

koboltzz said:
Anything new to this?
Click to expand...
Click to collapse
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.

dr4go said:
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.
Click to expand...
Click to collapse
hey dr4go got something weird here...
when i flash your ext3 zip everything is fine atleast the mount command say so
but then when i want to convert them to ext2 something really weirds occur the system partition becomes ext2 but the data and cache partition become ext4 according to the mount command using recovery 5.0.2.7R2

Here is the convert tool made by Topogigi, and slightly modified by me to include /system conversion.
/cache has not the same parameters it seems.

First (and second) post(s) updated.
And I'll promise you also to release something bigger next time. Guesses won't be commented.

ONly comment I can do is: Nice to see you my friend! How are you?

carburano said:
ONly comment I can do is: Nice to see you my friend! How are you?
Click to expand...
Click to collapse
Everything fine here! Nice to see you too. I finally found some free time and also motivation, because of the marvellously working CyanogenMod 10 on our phones. It's unbelievable... I was nearly freaking out when reading the notice.
And you? How are you? Hopefully everything is also great on your side?

Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app

maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea

spica1234 said:
Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Thank you. As you may have realized... a little busy as usual... otherwise totally fine. How is it on your side? Everything ok?

cojo11 said:
maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea
Click to expand...
Click to collapse
What exactly did you do? And which ROM did you try to flash afterwards? Imho the zips should be fixed now - I didn't encounter a single problem since using them.

i try it with ICS 28E and 28G for my Ghostrider Aroma Rom with new Partition Layout,but when i use ext3 or ext4 i got a Bootloop,i put the stuff in the Updater-Script,all runs with Aroma and lokks fine but when i reboot,i got the Bootloop

[MOD] EXT4All Continued + Now with TWRP 2.3 Support

The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.

Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium

I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.

the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351

Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?

funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2

I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium

tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.

Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium

tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...

funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2

hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?

funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?

funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended

Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?

funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.

hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!

Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...

omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.

[ROM][KK][4.4.4][KTU84P] CyanogenMod 11 20140714-UNOFFICIAL

CyanogenMod is a free, community built after-market firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Downloads
Read install directions before downloading or use ^C^V
Latest ROM md5sum: c821ebacaa5c969c55b0a511be8a3933
Current GApps 4.4.4 :: PA
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
For Odin: select the ops file, enable one package in options, then load the md5 file with the One Package button[1]
Installation
Install at your own risk
- First time flashing CM11 to your Galaxy Exhibit (or coming from another ROM)?
Boot into existing recovery and create a Nandroid Backup!
Install at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
Reboot recovery into at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
CWM: WIPE dalvik-cache, format: data, system, and cache. TWRP: WIPE dalvik-cache, data, system, and cache.
** Optionally back-up sdcard0 before install and format it in recovery if experiencing install issues **
Install the ROM (without gapps)
Reboot system
After system boots, boot back into recovery and install KK Google Apps.
Wipe dalvik-cache and cache. Reboot.
- Upgrading from CM11
Boot into existing recovery and create a Nandroid Backup!
CWM: WIPE dalvik-cache and format cache. TWRP: WIPE dalvik-cache and cache.
Install the ROM
Reboot
Known Issues
ART takes ~15 minutes to install and some apps may not be compatible.
Display remains on while device is powered off and charging
Kernel Source
Credits
arco68, jocala, Christopher83,
pawitp, davidteri, mikeNG,
AriesVE DevConnection Team

Changelog
20140714
Sync with CM sources
Add center clock option
Add Xposed fix
Remove KSM
Disable LPA
416 MB userspace memory
md5sum: c821ebacaa5c969c55b0a511be8a3933
20140710
Sync with CM sources
Kernel 3.4.98 compiled with Christopher83's 2014.06 4.9.1 toolchain
406 MB userspace memory
Remove zram
md5sum: 7b0c0d8abf63adfa267b1f8f2c72b269
20140415
Sync with CM sources
Kernel compiled with Christopher83's 2014.04 toolchain
md5sum: bc9b6c5403d94a7e63f69aba7f1ec194
20140414
Sync with CM sources
Kernel v3.4.87
Enable LPA (credit arco)
md5sum: 23b1e4fb4b6f863eae2a5ac447f6dafb
20140402
Sync with CM sources
Kernel v3.4.85 (credit Christopher83)
Use older Adreno blobs
Netflix confirmed working
Add Performance Control (credit h0rn3t)
md5sum: d6dbb5bbeb4758657e9c74ad50c16ac8
20131125
Initial release
md5sum: 4fa0b6dd64730f4139d54375555dd91

Basebands & Misc.
Basebands
Flash in CWM recovery. Wipe cache and Dalvik-cache before installing.
T679UVLG3 2012 July
md5sum 61efc2e31fd0885dc0f948f84f94574f
T679UVLK2 2012 November
md5sum 0c0175d46e3fc4c9f11ee3352af85442
Odin 4.43 and USB driver
Placeholder for Odin 4.43, ancora.ops, and Samsung USB v1.3.2410 driver here in rar format.
Newer drivers will not connect with device in download mode.
Works with XP and will not work with win 8.

nice one didn't realize anyone else was deving for our phones. I'll test it out later after i get initial release up for AOIP CE.

Fantastic! I'll let you know if GPS doesn't work. I use it everyday during my runs.
edit*
GPS does work for me. The ROM does boot and works, but it's somewhat slow at times. The browser crashes. I tried clicking the news tab on the google main page. AND... everything is tiny. I'm not sure if that's how kit kat is suppose to look or not. Wow, they weren't kidding when they said kit kat uses little ram. Bluetooth also works... I paired my phone to my Windows 8.1 laptop successfully. I was able to play music on my phone through my laptop speakers, view files stored on my phone and send and receive files.

Thanks for the hard work and bringing us 4.4. Going to give it a whirl and see what happens!

I have heard of some issues with the stock browser on some other devices, due to webviewapi but everyone says chrome works fine. Don't know if that's helpful or the case here. Downloading now, eager to try some Kit Kat.
Sent from my SGH-T679 using xda app-developers app

I use chrome and it performs well enough that I never tested stock browser. chromewebview takes forever to compile, but I'll look at it later.

TripFX said:
nice one didn't realize anyone else was deving for our phones. I'll test it out later after i get initial release up for AOIP CE.
Click to expand...
Click to collapse
Let us know how camera works with ion, I think that's why arco switched back to pmem, but I'll try helping when you're there.

DPI
I went into the build.prop and changed the DPI to 240, I'm sure most folks know how to do that but thought I'd mention it for those who are wondering so all apps will be compatible & such.
On another note Titanium Backup is not showing all apps in batch restore mode that I have backed up, but when I view the Backup/Restore list they are all there. Might be a 4.4 bug.

Thanks for the effort to bring Kit Kat to our phone, hope you'll feel welcome to our community!

ArtfulDodger said:
I went into the build.prop and changed the DPI to 240, I'm sure most folks know how to do that but thought I'd mention it for those who are wondering so all apps will be compatible & such.
On another note Titanium Backup is not showing all apps in batch restore mode that I have backed up, but when I view the Backup/Restore list they are all there. Might be a 4.4 bug.
Click to expand...
Click to collapse
Might be st with the storage mounting points. I know usbdisk is logging a fit and sdcard1 doesn't seem mounted properly, so sdswap may be a temp issue.

jfbs said:
Might be st with the storage mounting points. I know usbdisk is logging a fit and sdcard1 doesn't seem mounted properly, so sdswap may be a temp issue.
Click to expand...
Click to collapse
Well when I try to restore most of those apps, the restore button is missing? Hmmmm...

ArtfulDodger said:
Well when I try to restore most of those apps, the restore button is missing? Hmmmm...
Click to expand...
Click to collapse
It could be caused by selinux permissions, or within TB itself regarding 4.4's API.

jfbs said:
It could be caused by selinux permissions, or within TB itself regarding 4.4's API.
Click to expand...
Click to collapse
Yeah because any system apps can be restored, and just a handful of user apps. 90% of the apps are being read as data only backups. Not sure what else to do at this point. Going to restore my nandroid, backup again and re-flash the ROM. Oddly enough the Play store didn't give the option of just downloading all of them again like it normally does. At any rate if I can't get my apps restored in bulk I won't be able to do this. Manually it would take forever and a day.
I have to tell you however your ROM is very light and smooth with zero tweaks. I'd really like to get this going if I can!

It could be superuser. Try supersu?

jfbs said:
It could be superuser. Try supersu?
Click to expand...
Click to collapse
I did, no luck. If I can get Play to just re-download the apps, I will do that and then restore data.

jfbs said:
Let us know how camera works with ion, I think that's why arco switched back to pmem, but I'll try helping when you're there.
Click to expand...
Click to collapse
Thanks since you are deving roms I can skip making my own rom then and focus more on ION :highfive:. Ya acro switched back because the cam driver has to be rewritten from scratch to work with it. It's not a biggie for me just mostly time consuming but it will be well worth the effort to keep our phones going longer and break the 3000 mark on quadrant :fingers-crossed: You should check out AOIP CE when it's up if ya like the installer I can mod/make one for you :angel:

some questionable advice
ArtfulDodger said:
Yeah because any system apps can be restored, and just a handful of user apps. 90% of the apps are being read as data only backups. Not sure what else to do at this point. Going to restore my nandroid, backup again and re-flash the ROM. Oddly enough the Play store didn't give the option of just downloading all of them again like it normally does. At any rate if I can't get my apps restored in bulk I won't be able to do this. Manually it would take forever and a day.
I have to tell you however your ROM is very light and smooth with zero tweaks. I'd really like to get this going if I can!
Click to expand...
Click to collapse
Don't tell anyone I suggested this, but as long as you have enough nandroids I suspect it can't hurt to try restoring just data from the backup and seeing if KitKat can cope with updating your JB-based data. Worst case nothing works and you have to go back to this unfortunate plan, but you might get away with it. Despite everyone's advice I haven't started from scratch since CM10 -- when moving to AOIP I just wiped ROM and cache but not data. When I briefly tried AOIP 2.0 I saw a message on the screen about "upgrading contacts database". So the bottom line is that Android knows how to handle version upgrades -- which makes sense, because the manufacturer OTA updates don't usually wipe your data.
With AOIP 1.5 the only trouble I had after my unorthodox migration was a crash in the calculator app and it went away when I performed "clear data" on just that app. So it might be worth a try.
[I didn't try asking Android to downgrade data when I switched back from AOIP 2.0 to 1.5 though... I restored the data from my last 1.5 nandroid at that point.]

aaopt said:
Don't tell anyone I suggested this, but as long as you have enough nandroids I suspect it can't hurt to try restoring just data from the backup and seeing if KitKat can cope with updating your JB-based data. Worst case nothing works and you have to go back to this unfortunate plan, but you might get away with it. Despite everyone's advice I haven't started from scratch since CM10 -- when moving to AOIP I just wiped ROM and cache but not data. When I briefly tried AOIP 2.0 I saw a message on the screen about "upgrading contacts database". So the bottom line is that Android knows how to handle version upgrades -- which makes sense, because the manufacturer OTA updates don't usually wipe your data.
With AOIP 1.5 the only trouble I had after my unorthodox migration was a crash in the calculator app and it went away when I performed "clear data" on just that app. So it might be worth a try.
[I didn't try asking Android to downgrade data when I switched back from AOIP 2.0 to 1.5 though... I restored the data from my last 1.5 nandroid at that point.]
Click to expand...
Click to collapse
I was a little skeptical I might get FCs out the wazoo but this actually works, for the most part. It breaks system settings however (no surprise). Only problem is now RAM Expander can no longer use the swap file, even if recreated. Get the "invalid argument" error after creation, although the file is there.
This was a great tip though as most all apps work just fine with no FCs. If I can get Expander working and Viper all will be well.
Edit: Swap files will not work with this ROM. Probably has something to do with path issues, IDK. Viper does not work either but that is a common issue among 4.3 and 4.4 ROMs. Oh well. Still this is nicely done, very lightweight and functional. 4.4 is going to have issues until app devs can catch up.
Great work and first effort @jfbs. I have a feeling I'll be back to try future updates.

[Q] What's NOT getting wiped when I flash?

I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?

jran0880 said:
I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?
Click to expand...
Click to collapse
Sounds like /data isn't getting wiped or formatted.

jran0880 said:
I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?
Click to expand...
Click to collapse
One other thing... Have you set up Google to track your installed apps/etc? If so, Google will automatically restore them.

Failbringer60 said:
I did a full wipe for the initial install. But for the newest build i wiped system only and flashed on top of the previous build. I can do a full wipe again and reinstall the newest build to see if it corrects my issues. But i can assure you i wiped everything when i installed the previous build.
Click to expand...
Click to collapse
shinobisoft said:
Umm... I'm seen a bunch of references in your posted log that refer to the old sdcard path ( as in stock, /storage/external_SD. New path is : /storage/sdcard1 ). This is telling me that you did NOT format your /system and or /data partition when you installed CM for the first time. Obviously the only way to remedy this is to do a fresh installation following the instructions I posted in the OP.
Click to expand...
Click to collapse
shinobisoft said:
One other thing... Have you set up Google to track your installed apps/etc? If so, Google will automatically restore them.
Click to expand...
Click to collapse
I changed the "auto restore" setting so it won't automatically install my apps and tried another "clean" install with the same results. It's almost like I'm restoring from a previous back up! I made sure to wipe and format everything twice just to be certain. Installed only CM and gapps zips, wiping dalvik and cache before booting system. My result was the same as previous..... Choose language.... WiFi connects, and my settings restore.... I am NEVER asked to login to my Google or Cyanogen account(s)......
I'm about to back up and wipe everything, use fastboot to format the partitions? Ideas? Thoughts? Suggestions?
Perhaps restore my "rooted factory ROM" from TWRP back up and start from there? Or restore from .kdz?

Maybe try a factory reset from Settings after installing? Kind of a long shot but that's what I had to do after flashing back to stock when nothing seemed to have changed ...