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.
Related
Hi Everyone,
Sorry for this long-winded post. I've spent hours reading posts here, AndroidCentral and AndroidTablets.net forums, but have not found answers that work for me.
I hope someone can sort out the mess I've created on my rooted 1.1 Nook. Everything worked for 4-5 weeks after I rooted with Decad3nce method until...
A few days ago I decided to try 1.1G kernel. Read many threads about issues with Root Manager/ CWM; 3.0.0.5/3.0.0.6/SD CWM/EMMC CWM/Nook/Nook (old). When I booted into CWM, the version was 3.0.0.5. If I tried flashing CWM through Rom Manager, it said it 'flashed' 3.0.0.6 (tried both "Nook" and "Nook(old)"), but it never changed version of CWM I booted into. I also tried nemiths' "[RECOVERY] Official CWM 3.0.0.6 Update [BROKEN] (new fix soon!)" method to flash 3.0.0.6, but "adb shell busybox" always gave a 'can't get root' type error, so I gave up on that. I ended up using my current CWM to flash 1.1G kernel, and it worked very well. So I ignored the the CWM issues.
Then, I decided to try rookie1's dual-boot method so I could try out Honeycomb. I could never get 'prep_dualboot' zip to flash. It always gave an 'error in zip (status 0)'. His thread showed a few others getting same error, but none of the fixes given worked for me. I re-flashed that zip and ran the 'un-dualboot' zip many times with same result. I then found a "EMMC_CWM_3.0.0.6" zip and flashed that with my CWM. That actually gave me 3.0.0.6 CWM, but flashing dualboot still didn't work. I also again un-dualbooted, wipe cache partition, wipe dalvik cache, fix permissions with same result. So I gave up on that for now.
Then this morning, I found Market updates and downloads don't work anymore. It says 'about to download', then shows the arrows in status bar and nothing else happens. Saw threads regarding this issue and tried clearing Market cache and wiping whatever I could in CWM. Nothing I've found has helped so far.
As a side note in Rom Manager, "Recovery" section now shows 3.0.0.5 (before it wanted to flash 3.0.0.6). Tried flashing 3.0.0.5 there, but it doesn't seem to do anything (same as when it tried to flash 3.0.0.6). I can't understand the logic in Rom Manager. I also have Fascinate phone and RM has issues on that phone also.
I do have CWM backups and Titanium backups of all my stuff, so at worst I can do those. Looking for possibly easier way to get back to 'normal' so Market works and I can download the 'dual boot' zip and be happy again.
Some additional questions I have:
1) I saw in Decad3nce post that he left out 'root' for busybox in an early release, so that may be why mine won't work. I know I had used busybox before, but that may have been on earlier rooted 1.0.1. Is there a way to fix my current busybox without re-rooting?
2) What is the correct CWM I should use for 1.1 and will let me flash dual-boot zip? Also, where can I download it from and how can I replace the one I have?
3) I have saved my SD card to my computer many times and then re-formated it on the Nook. Is there some partition on it that format isn't cleaning that may contain some CWM image(s) causing at least some of my headaches?
Thanks in advance to anyone that can help with these issues. I may have tried a few other 'fixes' that I've since forgotten in the 5 hours last night trying to setup dual boot and quick hour this morning before work trying to sort out Market. Sorry (in advance) if you suggest something and I then say I tried it already. Possibly, just doing all the fixes I've tried previously in the correct sequence is what I need.
I seem to back to where I was before 'bad' versions of CWM skewered Market on me.
1) busybox: found that I just had to 'chmod 755' on my /system/xbin/busybox.
2) Saw that nemith posted a 3.0.0.9 version of CWM. Flashed that using his manual method. Didn't flash his kernel. Rebooted.
3) Tried clearing Market cache and didn't help. Wiped partition cache in CWM (or possibly Dalvik cache, not sure now...was going to do both but rebooted by mistake). After reboot, Market is working again.
Not sure if any of these affected Market, but I also unchecked/checked "Allow Non-Market Apps" and Unchecked/Checked "USB Debugging" and Unchecked "Auto Mount" in Settings.
Can't post in Dev area, so hope some there having same issue as me Market see this.
Now, gonna try the dual-boot again.
Alas, still getting (status 0) error flashing dual boot prep zip. Project for another night.
Sent from my LogicPD Zoom2 using XDA App
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
jhoward88 said:
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
Click to expand...
Click to collapse
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
vinal said:
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
Click to expand...
Click to collapse
No luck getting this to work
vinal said:
No luck getting this to work
Click to expand...
Click to collapse
Got a suggestion from Rookie1 to reformat my media partition. Prep now succeeded!
newfs_msdos -F 32 -L media /dev/block/mmcblk0p8
Hi all,
I've recently rooted my nook color. I installed CM7 through rom manager and it installed, etc and then when it boots up it stays stuck on the android screen with the android logo and rays.
Sorry, but I'm new to nook color and modding. Can anyone help?
Thanks,
Brett
bdws1975 said:
Hi all,
I've recently rooted my nook color. I installed CM7 through rom manager and it installed, etc and then when it boots up it stays stuck on the android screen with the android logo and rays.
Sorry, but I'm new to nook color and modding. Can anyone help?
Thanks,
Brett
Click to expand...
Click to collapse
Which version of CM7 did you install? Sounds to me like you installed a corrupt copy. Make sure the download is correct. If you can open the .zip file, then the file is OK.
Also, did you wipe cache partition before installing CM7? Then wipe Dalvik cache?
CM7 boot gets stuck
I had the same problem when i first installed cm7 on my nook, but for some miraculous and unknown (at least to me) reason, after i plugged it into my computer (while the boot screen was stuck) it booted up no problem. idk what causes it to happen, but plugging it into my computer made it get past the stalled boot.
Fwiw the android screen suggests the kernel has loaded. Are you able to capture a log w adb logcat?
Sent from my HTC Vision using XDA App
Did you wipe data/clear cache?
the android and rays sound like you rooted the stock right(autonooter)?
I had the same issue, i used the 8 fails boots to get to the CWR then wipe data and clear cache and tada boots up to CM7 correctly.
Hi all
I ended up tajing it back to stock, rerooting and flashing cm7 again. All is well now.
I believe i wiped the boot accidentally and thats what started it all.
Thanks for your help.
Brett
Sent from my HTC Desire HD using XDA Premium App
I updated my NC to run the latest CM7 release on the SD card. When I tried to add the latest Dalingrin OC kernel it appears to boot but doesn't get to the CM animation screen. Do I need to clear the cache before updating the kernel? Is this the correct way to do it? "rm -rf /data/dalvik-cache/*"? Will I loose any data or apps?
jmak10 said:
I updated my NC to run the latest CM7 release on the SD card. When I tried to add the latest Dalingrin OC kernel it appears to boot but doesn't get to the CM animation screen. Do I need to clear the cache before updating the kernel? Is this the correct way to do it? "rm -rf /data/dalvik-cache/*"? Will I loose any data or apps?
Click to expand...
Click to collapse
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well
Is factory reset recommended before flashing cm7?
sent from PinoyNook
wrdoss said:
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well
Click to expand...
Click to collapse
Thanks for the reply. I double checked it and I did download the latest SD version (SD-041811c) but it didn't work. I then tried the SD-040411 version and it worked fine. Note that I didn't clear the cache either time.
wrdoss said:
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well
Click to expand...
Click to collapse
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?
robot8 said:
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?
Click to expand...
Click to collapse
This is the exact same setup and problem that I experienced.
robot8 said:
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?
Click to expand...
Click to collapse
Have you tried posting this issue in the development forum?
Yes I did, and it seems there's no easy way. Need to install the SDK and then adb push system from the extracted zip file then swap uImage.
edit: not that it's all that difficult but compared to just swapping uImage previously, well I'll probably wait a bit for the final update. Seems to be some issues with wi-fi.
edit:
Well I couldn't wait so I went ahead and popped 4/18C in. No issues so far.
robot8 said:
Yes I did, and it seems there's no easy way. Need to install the SDK and then adb push system from the extracted zip file then swap uImage.
Click to expand...
Click to collapse
Well that is unfortunate because you have to reinstall the OC kernal every time you install a new CM7 version.
I think I am going to stay with the latest CM7 nightly build and the SD-040411 OC kernel. I ran it some last night and it appeared stable and I didn't experience any of the video issues that people were reporting.
jmak10 said:
Well that is unfortunate because you have to reinstall the OC kernal every time you install a new CM7 release.
Click to expand...
Click to collapse
All this while when you update CM7 you'd need to reinstall the OC kernel, but it was way easy as you just needed to swap uImage. But not with the new test kernels.
Correct me if I'm wrong but I suppose once it's finalized I suppose the system stuff will be merged with main CM7 and we'd be able to swap OC kernels just like before.
robot8 said:
All this while when you update CM7 you'd need to reinstall the OC kernel, but it was way easy as you just needed to swap uImage. But not with the new test kernels.
Correct me if I'm wrong but I suppose once it's finalized I suppose the system stuff will be merged with main CM7 and we'd be able to swap OC kernels just like before.
Click to expand...
Click to collapse
I don't have any idea what is being planned but I hope the developers make this as easy as it was before.
I'm in the same boat. I know wiping the cache will fix it but I'm just stuck again if I reboot.
I'm running CM7, I wiped system, data, cach, dalvik, and did a factory reset before flashing.
Right now I'm just making sure my batter never runs out because reboot = wipe cache and then waste my time restoring apps and settings
I posted a while back about the different recovery images here and have since been using Darch_RA-1.7 for everything (Firerat, GB ROMS, etc.).
When I change my custom partitions, there are two times when I need to ADB (one is arguable). I have to reboot into recovery during one point of modifying mtd partitions with Firerat Recovery, which can be accomplished by pulling the battery and just booting with HOME+POWER keys. It would be super handy though if there was a reboot into recovery command in my recovery image. I know this is in CW 3.x.
Secondly, and more important, is that to limit hickups in google restoring my settings when I load a new ROM, I need to apply s0be's fix before my first boot, which essentially is just making a dir /cache/download and then fixing the permissions for it.
I would love it if these commands could be apart of Darch's 1.7 recovery so that I could re-flash on the go without a computer for ADB shell. I am not completely sure how to do this (modifying the recovery binary), and moreover if I need to find the original source or just unpack and use the binaries. This little conversation was somewhat helpful.
Thoughts? Help?
Replying to my own post, but I had an idea that to address s0be's fix, I could possibly make it into a signed zip, of course assuming that would work (permissions?). Just a thought.
If your using Ra1.7 you don't have to pull the battery when using fr. Just choose the power off option and reboot with home+power. I know its off your op topic but I'd figure I'd post incase you were still using fr.
#Root/Hack-Mod_Always*
And as for the s0be market fix, it is no longer necessary if you use firerat v1.5.8 and set your cache partition to 18
Sent from my HERO200 using XDA Premium App
So that's why people have an 18mb cache.
The Fer-Shiz-Nizzle said:
And as for the s0be market fix, it is no longer necessary if you use firerat v1.5.8 and set your cache partition to 18
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Well that explains why I see a bunch of folks using 18 as the cache size, but didn't see that in the thread. My most recent repart with with 128 and 18, which although is a bit excessive for the cache (only using 4 of 18), will eliminate the need for s0be's fix.
For the record, I went ahead and did it anyways. Also, you can definitely just use the power off function (or battery pull) in Darch's 1.7 to get reboot to recovery.
Bottomline: I would say this is solved for my specific issues with Firerat MTD. Also, Darch's 1.7 is perfectly capable of installing GB ROMs.
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, version compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the LG Optimus 2X. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for most of the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-p990.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-p990.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
Now that Koush added backup support for internal/external sdcard I'll only build onw version (exernal sdcard in file lists) If you really want one build for internal sdcard, let me know and I'll do it.)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
As of this version, I'll only be providing one img file. It seems 5.0 has native support for internal/external SD card. Need confirmation of this, as I don't have this phone myself.
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Reverted back to ext3 for the meantime, since I didn't get ext4 working. Any suggestions are welcome!
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Two versions. One for internal storage and one for external microSD card (same zip file)
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
This recovery bricked my phone
Hell_97 said:
This recovery bricked my phone
Click to expand...
Click to collapse
Anybody with same problem?
Hell_97 said:
This recovery bricked my phone
Click to expand...
Click to collapse
How did you install it? Can you still boot into whatever ROM you were running before? What happens when you start to phone now? Exactly what did you do? Please be a bit more specific so we might have a chance of helping you fix the problem.
Sent from my Nexus S using Tapatalk
Updated recovery.fstab to allow ext4. Might work better. Try at your own risk.
zyonee said:
How did you install it? Can you still boot into whatever ROM you were running before? What happens when you start to phone now? Exactly what did you do? Please be a bit more specific so we might have a chance of helping you fix the problem.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I tried to change kernel and the device is locked on the LG screen, I solved with smartflash.
that's not even related to this recovery mod.... I had the same problem with "original" 4.0.0.5 and after flashing vorkernel had the same problem.... I solved it with restoring nandroid backup. The kernel does not work for me with CM latest nightlies.
So can someone please test the newest recovery version? I'd like to know if ext4 works as it should.
Sent from my Nexus S using Tapatalk
klubipiff said:
that's not even related to this recovery mod.... I had the same problem with "original" 4.0.0.5 and after flashing vorkernel had the same problem.... I solved it with restoring nandroid backup. The kernel does not work for me with CM latest nightlies.
Click to expand...
Click to collapse
I installed vork kernel with "original" 4.0.0.5 on CM53 without problem.
To have ext4 you also need a kernel with ext4 support (correct me if im wrong) So which kernel has the ext4 support?
Sent from my Optimus 2X using XDA App
peewster said:
To have ext4 you also need a kernel with ext4 support (correct me if im wrong) So which kernel has the ext4 support?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Please stay on topic. This thread is about the modified ClockworkMod recovery and possibly its ability to work with ext4, not about custom ROMs or kernels...
Sent from my Nexus S using Tapatalk
If you've changed recovery.fstab, then it should be OK with EXT4, that's all I had to do with my releases to get it working.
zyonee said:
Please stay on topic. This thread is about the modified ClockworkMod recovery and possibly its ability to work with ext4, not about custom ROMs or kernels...
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Just asking because it looks nice but then i need to know wich kernels i can use?
Sent from my Optimus 2X using XDA App
Just flashed the recovery, all ok. The confirmation menu is much better now with just 1: no line
Sent from my Optimus 2X using XDA App
peewster said:
Just flashed the recovery, all ok. The confirmation menu is much better now with just 1: no line
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Very glad to hear it. Wipe, nandroid backup/restore and ext4, did you test all these?
Sent from my Nexus S using Tapatalk
peewster said:
Just asking because it looks nice but then i need to know wich kernels i can use?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Well, see, the problem isn't really which zips you can or cannot flash. It's more about whether you can flash at all or if ext4 works properly. If nandroid backup and restore works or not. I'm fairly certain that all kernels can be flashed, but how well they work is something that I don't see would be affected by this recovery.
Sent from my Nexus S using Tapatalk
Hmm doesnt seem to wipe correctly...after doing a clean install of CM7 I still have all my old apps and settings. That said I did install it in an odd way (replaced Paul's recovery with it and ran his .bat script). What is the easiest method to flash recovery?
That is the easiest way.
xAdaM-- said:
Hmm doesnt seem to wipe correctly...after doing a clean install of CM7 I still have all my old apps and settings. That said I did install it in an odd way (replaced Paul's recovery with it and ran his .bat script). What is the easiest method to flash recovery?
Click to expand...
Click to collapse
Exactly how did you wipe? Did you use the "format" commands in "mounts and storage" or did you use "clear data/factory reset"? I'm starting to think that the format command is not working.
zyonee said:
Exactly how did you wipe? Did you use the "format" commands in "mounts and storage" or did you use "clear data/factory reset"? I'm starting to think that the format command is not working.
Click to expand...
Click to collapse
Didn't go near the format command in mount and storage. In the specific "Wipe" menu --> tried factory reset etc/cache partition...all seemed to work way to quickly to actually be doing anything. Like I'd select wipe data/factory reset, hit yes and it would say completed after like 1 second (usually takes more than 5 with regular recovery). And then of course when I rebooted my device my data was still there, nothing wiped (except perhaps dalvik, but who knows).
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.