Related
Hi Everyone,
I just installed FireFly's ROM and unlike when I flash Serendipity 5.12 it didn't ask me to apply the LagFix upon reboot. I am believing this was probably because I didn't root my phone before I flashed FireFly? Regardless, I booted into Clockwork Manager Recovery, went into the SpeedMod advanced options, and applied it through there.
I selected the option apply and restore factory data and at that point it did its thing and rebooted successfully. I went back into FireFly's ROM and noticed a lot of the apps were missing (EX: SGS Tools, etc...) but SuperUser was still there. So I went back into Clockwork Manager Recovery and re-installed the FireFly ROM from its .zip file.
When it rebooted successfully I check to make sure all those apps were there, and they were. I rebooted into Clockwork Manager Recovery and check to make sure the LagFix was still applied and it was (i.e. data_fs=ext4). However, I could during all of this never find the VooDoo folder using a file manager. As apparently, if I wanted too, I could disable the VooDoo LagFix by creating a folder in there. My question is:
Does applying the VooDoo LagFix through the SpeedMod advanced options in Clockwork Manager Recovery not create a VooDoo folder on the SDCARD?
NightTickler said:
Hi Everyone,
I just installed FireFly's ROM and unlike when I flash Serendipity 5.12 it didn't ask me to apply the LagFix upon reboot. I am believing this was probably because I didn't root my phone before I flashed FireFly? Regardless, I booted into Clockwork Manager Recovery, went into the SpeedMod advanced options, and applied it through there.
I selected the option apply and restore factory data and at that point it did its thing and rebooted successfully. I went back into FireFly's ROM and noticed a lot of the apps were missing (EX: SGS Tools, etc...) but SuperUser was still there. So I went back into Clockwork Manager Recovery and re-installed the FireFly ROM from its .zip file.
When it rebooted successfully I check to make sure all those apps were there, and they were. I rebooted into Clockwork Manager Recovery and check to make sure the LagFix was still applied and it was (i.e. data_fs=ext4). However, I could during all of this never find the VooDoo folder using a file manager. As apparently, if I wanted too, I could disable the VooDoo LagFix by creating a folder in there. My question is:
Does applying the VooDoo LagFix through the SpeedMod advanced options in Clockwork Manager Recovery not create a VooDoo folder on the SDCARD?
Click to expand...
Click to collapse
It may not create the folder, try getting the voodoo control app fromt he market and checking to see if its showing as applied in there. If it says it is, I wouldnt honestly worry about the voodoo folder ( that is normally empty other than log files to begin with).
People, there are ROM-specific stickies in the Q&A subforum where stuff like this is supposed to go. Please use them.
Speedmod Kernel does NOT use Voodoo for lagfix. So you will never find the Voodoo file.
If clockwork says lagfix is enabled, then it is.
Alright, so without much help, I've gathered a bit of info on my own on how to do stuff with rooting and custom ROMS and Kernels, but I'm still very new to all of this so I'd like to ask a few questions instead of asking one on each individual thread. (Hate cluttering websites with n00b questions and just have people get upset because to them it's common knowledge). Also, I don't mind if you send links to answer my questions, I've searched around and all I found were UPDATES to each thing or How To install, but never explanations.
First some info about my phone:
ROM: Infused 1.5.3
Kernel: Defuse 1.5
1) What exactly does the Voodoo lagfix do? I know it changes the file system to ext4, but does it have any other scripts?
2) Why do you have to disable the Voodoo lagfix (I haven't, yet)? Or do you only have to disable it when installing a ROM? If you don't, does it really mess up ROM installs?
3) What's the difference between CWM Green and Red? My best guess is Green is using it within the OS (the Rom Manager app) and Red is through Recovery.
4) Do you have to keep the update.zip file? After all the installations are said and done, do you NEED it?
5) What files can I delete? For example the ROM downloads on my phone that Rom Manager fetched? What files shouldn't I touch, ever (except for advanced use)?
6) Will all my apps and data delete each time I install an update to the ROM? (Like if Infused updates to 1.6) I really don't like re-doing the entire first-time setup. Even though Titanium Backup backs apps and data up, it doesn't let me back up stuff like that? (Or even simply the dictionary to my SWYPE keyboard)
7) Every time I install a ROM or Kernel, do I have to delete all the Data and Cache and Delvik Cache? Because deleting Data and Cache obviously removes my apps and settings etc.
8) (Combination of 6+7) So if I wanted to update my ROM from 1.5 to 1.6, I'd still have to delete all that data?
Those are all the questions I have for now, thank you. <3
Re: Just to get the n00b questions
Khyrdantai said:
Alright, so without much help, I've gathered a bit of info on my own on how to do stuff with rooting and custom ROMS and Kernels, but I'm still very new to all of this so I'd like to ask a few questions instead of asking one on each individual thread. (Hate cluttering websites with n00b questions and just have people get upset because to them it's common knowledge).
First some info about my phone:
ROM: Infused 1.5.3
Kernel: Defuse 1.5
1) What exactly does the Voodoo lagfix do? I know it changes the file system to ext4, but does it have any other scripts?
2) Why do you have to disable the Voodoo lagfix (I haven't, yet)? Or do you only have to disable it when installing a ROM? If you don't, does it really mess up ROM installs?
3) What's the difference between CWM Green and Red? My best guess is Green is using it within the OS (the Rom Manager app) and Red is through Recovery.
4) Do you have to keep the update.zip file? After all the installations are said and done, do you NEED it?
5) What files can I delete? For example the ROM downloads on my phone that Rom Manager fetched? What files shouldn't I touch, ever (except for advanced use)?
6) Will all my apps and data delete each time I install an update to the ROM? (Like if Infused updates to 1.6) I really don't like re-doing the entire first-time setup. Even though Titanium Backup backs apps and data up, it doesn't let me back up stuff like that? (Or even simply the dictionary to my SWYPE keyboard)
7) Every time I install a ROM or Kernel, do I have to delete all the Data and Cache and Delvik Cache? Because deleting Data and Cache obviously removes my apps and settings etc.
8) (Combination of 6+7) So if I wanted to update my ROM from 1.5 to 1.6, I'd still have to delete all that data?
Those are all the questions I have for now, thank you. <3
Click to expand...
Click to collapse
You are just asking way too many questions, especially for being a n00b
Perhaps you will have better luck by using the "search" feature here in the forums.....
When I was a N00b I was lucky to get even ONE of my questions answered!
I don't know about infused 1.6, was under the impression that it'd be gb, might want to wipe data with that one
no need to clear data if you upgrade to a custom rom from stock atm but maybe in the future it'll be a good idea. upgrading fro different versions of the same rom without wiping data as long as the firmware veraion is the same should be ok. if the firmware is updated it is questionable, Samsung roms change odd things and upgrading can cause force closes if data is not wiped. id imagine Samsung updates have scripts to correct the issues I the old data causes.
switching from one custom rom to another it might be a good idea to clear data.
use titanium backup and backup apps, you can backup app and system data but never restore system data to a new firmware version. app data is usually ok but not recommended. clearing cache is always ok, clearing dalvik cache is always recommended for any flash you do.
voodoo should only be disabled before returning to stock, I used to have to odin flash twice on my captivate sometimes to restore the phone to stock if I switched from a jfs enabled ulf kernel to a voodoo kernel if I forgot to disable lagfix. right now there are only voodoo kernels, there isn't too much reason to confuse the community with different types of lagfixes so don't think too much about disabling lagfix till there are alternatives to voodoo.
voodoo converts the file system to ext4 which is the google standard. Samsung uses a weird spinoff of fat32 that they branded rfs and they use on there tvs and other devices. rfs can slow the device down in theory and it certainly benchmarks lower.
I'm hoping to see a nilfs2 conversion on an aosp cm7 kernel eventually. nilfs2 is designed for flash memory and eliminates a lot of the time used to overwrite and move files. I saw quadrant scores on the nexus s at around 3500 with nilfs2 stagefright settings changed and some overclock.
Khyrdantai said:
Alright, so without much help, I've gathered a bit of info on my own on how to do stuff with rooting and custom ROMS and Kernels, but I'm still very new to all of this so I'd like to ask a few questions instead of asking one on each individual thread. (Hate cluttering websites with n00b questions and just have people get upset because to them it's common knowledge). Also, I don't mind if you send links to answer my questions, I've searched around and all I found were UPDATES to each thing or How To install, but never explanations.
First some info about my phone:
ROM: Infused 1.5.3
Kernel: Defuse 1.5
1) What exactly does the Voodoo lagfix do? I know it changes the file system to ext4, but does it have any other scripts?
2) Why do you have to disable the Voodoo lagfix (I haven't, yet)? Or do you only have to disable it when installing a ROM? If you don't, does it really mess up ROM installs?
3) What's the difference between CWM Green and Red? My best guess is Green is using it within the OS (the Rom Manager app) and Red is through Recovery.
4) Do you have to keep the update.zip file? After all the installations are said and done, do you NEED it?
5) What files can I delete? For example the ROM downloads on my phone that Rom Manager fetched? What files shouldn't I touch, ever (except for advanced use)?
6) Will all my apps and data delete each time I install an update to the ROM? (Like if Infused updates to 1.6) I really don't like re-doing the entire first-time setup. Even though Titanium Backup backs apps and data up, it doesn't let me back up stuff like that? (Or even simply the dictionary to my SWYPE keyboard)
7) Every time I install a ROM or Kernel, do I have to delete all the Data and Cache and Delvik Cache? Because deleting Data and Cache obviously removes my apps and settings etc.
8) (Combination of 6+7) So if I wanted to update my ROM from 1.5 to 1.6, I'd still have to delete all that data?
Those are all the questions I have for now, thank you. <3
Click to expand...
Click to collapse
I think lagfix might do some other filesystem tuning (journaling settings and such) that differ from default, but not sure.
You need to disable Lagfix when moving to any ROM/kernel that does not support ext4, as the kernel won't recognize the filesystem. Right now this means the stock kernel - all alternate kernels out there have ext4 support.
As I understand it, green CWM doesn't understand ext4. Red does. I'm not entirely sure on this one though.
You don't need to keep the update.zip unless you want to re-apply it. I keep a copy of everything I currently have flashed, and a copy of whatever I was last running stable, in case I have a weird problem "on the go"
Apps and data don't automatically delete when installing a ROM, but using CWM's "wipe data" function is always recommended when changing to a new ROM. In general:
1) If changing only a kernel, no need to wipe anything
2) If applying an update to a newer version of a ROM you're already running, usually no need to wipe unless the ROM author says that release needs a wipe. However, you WILL almost surely have to wipe before the next Infused, as the next Infused version will likely be Gingerbread.
3) If changing to a different ROM, you should wipe
Wiping Dalvik cache occasionally is a good idea, and won't cause your apps to lose settings.
Misterjunky said:
You are just asking way too many questions, especially for being a n00b
Perhaps you will have better luck by using the "search" feature here in the forums.....
When I was a N00b I was lucky to get even ONE of my questions answered!
Click to expand...
Click to collapse
That's why I made a thread, because the "search" feature didn't do much help, nobody directly asked these questions that I saw (at least using search and scouting out the comments).
I have faith in people, there's a lot who are willing to help out someone in search of knowledge. ^_^
Dani897 said:
I don't know about infused 1.6, was under the impression that it'd be gb, might want to wipe data with that one
Click to expand...
Click to collapse
Just using 1.6 as an example.
Thanks for some clearing up on information, though!
Entropy512 said:
I think lagfix might do some other filesystem tuning (journaling settings and such) that differ from default, but not sure.
You need to disable Lagfix when moving to any ROM/kernel that does not support ext4, as the kernel won't recognize the filesystem. Right now this means the stock kernel - all alternate kernels out there have ext4 support.
As I understand it, green CWM doesn't understand ext4. Red does. I'm not entirely sure on this one though.
You don't need to keep the update.zip unless you want to re-apply it. I keep a copy of everything I currently have flashed, and a copy of whatever I was last running stable, in case I have a weird problem "on the go"
Apps and data don't automatically delete when installing a ROM, but using CWM's "wipe data" function is always recommended when changing to a new ROM. In general:
1) If changing only a kernel, no need to wipe anything
2) If applying an update to a newer version of a ROM you're already running, usually no need to wipe unless the ROM author says that release needs a wipe. However, you WILL almost surely have to wipe before the next Infused, as the next Infused version will likely be Gingerbread.
3) If changing to a different ROM, you should wipe
Wiping Dalvik cache occasionally is a good idea, and won't cause your apps to lose settings.
Click to expand...
Click to collapse
Very helpful as always.
Great post and thanks, I had some of the same questions.
Sent from my SAMSUNG-SGH-I997 using XDA App
yes voodoo has aditional tweeks to the mount options and I think the cache in non journalling , I don't know specifics. and thank entropy for the better explanation on the wipe/dont wipe situation.
Okay, I'm trying to get to the update. It has downloaded, but I can't apply it because I rooted. Specifically, I've got CWM and a rooted Voodoo Kernel, but everything else is EE4 stock. I think, based on what I've read, that this is the path I should take to get there:
[1] Disable the Voodoo Lagfix (convert back to rfs)
[2] Flash the stock recovery
[3] Re-install stock kernel from zip
[4] Allow the OTA upgrade to proceed
[5] Re-flash CWM variant
[6] Install rooted kernel
[7] (Optionally) Re-enable Voodoo Lagfix
I have a few questions about this:
1) Is this the correct path to getting 2.3.6?
2) Will this allow me to keep from wiping the phone?
3) How can I backup my phone's current state in case it gets screwed up? (Analogous to a disk image for a computer)
Thank you in advance for taking the time to read and answer!
Aurrin said:
Okay, I'm trying to get to the update. It has downloaded, but I can't apply it because I rooted. Specifically, I've got CWM and a rooted Voodoo Kernel, but everything else is EE4 stock. I think, based on what I've read, that this is the path I should take to get there:
[1] Disable the Voodoo Lagfix (convert back to rfs)
[2] Flash the stock recovery
[3] Re-install stock kernel from zip
[4] Allow the OTA upgrade to proceed
[5] Re-flash CWM variant
[6] Install rooted kernel
[7] (Optionally) Re-enable Voodoo Lagfix
I have a few questions about this:
1) Is this the correct path to getting 2.3.6?
2) Will this allow me to keep from wiping the phone?
3) How can I backup my phone's current state in case it gets screwed up? (Analogous to a disk image for a computer)
Thank you in advance for taking the time to read and answer!
Click to expand...
Click to collapse
your phone will need to be wiped in order to get back to stock to receive the OTA, you can back up apps and data with Titanium Backup and export a copy of your phonebook to your SD card or sync with your Google account to restore later (apps can be done this way too but the app data won't save)
other than that you have a few extra steps there but yes that's how you would do it:
-make backups
-flash stock EE4 with pit file in Odin
-boot up and do the setup really quick
-let OTA download/install
-let phone start and do anything else it asks or just look around for a few minutes and enjoy the poop lol
-flash CWM
-flash voodoo kernel in CWM
the kernel will root you and activate ext4/lagfix on boot so you're all set, then use TiBu to restore your stuff and Google sync/import your contacts and you're done... it will be horribly bloated though so you may want to use Root Explorer (or root file explorer of your choice, Super Manager is a nifty free option) and and get rid of the extra crap
sent from my Acer Iconia A500 beast of a tablet via XDA app
Okay, I don't want to sound pushy, so please don't take it the wrong way, but I really don't get why the phone has to be wiped, given that I didn't use a custom ROM, just a kernel and recovery. They can obviously be installed separately, as that's how I got it rooted in the first place, and the OTA is clearly designed to install right over the top of the existing system without a wipe. So, what gives? (I have a very, very slow internet connection, so wiping is not just a minor inconvenience - it's probably a full day to restore.)
How about flashing this > http://forum.xda-developers.com/showthread.php?p=19750449
Just back up your apps in titanium or whatever, and backup CWM and then follow danolo's instructions in that thread? You'll be on the official release without worrying how to get your phone to do it on its own
Sent from my SCH-I510 using xda premium
Okay, quick n00b follow-on question:
How do I wipe data and cache? That package doesn't do it automatically.
Aurrin said:
Okay, quick n00b follow-on question:
How do I wipe data and cache? That package doesn't do it automatically.
Click to expand...
Click to collapse
Boot into cwm. You will see wipe cache right below factory wipe. Then further down you will see advanced. Go into there and you will see dalvik cache. Ofcourse you use the volume buttons to scroll to what you need to select and the power button to follow though.
yes follow that linked thread and it will be stock debloated/rooted/deodexed but you might still need to restore at least *some* data
and to answer your previous question, every official firmware update contains a root checker script that scans your system before installing to make sure its 'stock' and clean... the least it will do is not prompt for update or say download failed but can be as bad as bootlooping or even bricking your phone when installed, which means you need a clean system to accept/install it properly (hence the recommendation to wipe clean or flash back to stock).. you can do this yourself without a wipe if you know where all the superuser file paths are and weed them out I suppose
sent from my Acer Iconia A500 beast of a tablet via XDA app
Hello everyone
This is a modified version of Vahalla Black rc3.3-fix that raver posted up that will (hopefully) get you a working version of it.
It's the beginning of a project I'm going to call the SGS4G CWM Rom Installer so I'm going to need a few testers.
NOTES
* This will wipe your phone clean before installing the rom, so MAKE A BACKUP before you flash this
* Formats /system, /cache and /data as ext4 before your rom installs
* Automatically mounts the partitions so you no longer need to check the mounts manually (this means no more having to use UMMU!)
* This has working progress bars and a verbose install! You will know what's going on during your ROM install!
* This will FINALLY automatically install busybox for you during your ROM install.
INSTRUCTIONS
1) MAKE A BACKUP
2) Did you already make a backup? If not, MAKE A BACKUP RIGHT NOW
3) Enable voodoo lagfix in CWM
4) Flash the zip file through CWM
5) Enjoy the ROM!
I hope you made a backup since I told you to do so 3 times before I told you to flash!
DOWNLOAD LINK
valhalla_black_rc3.3_issue_fix.zip
Please give me feedback as I'm still tweaking the install script. Hopefully all the rom authors will catch on to this procedure as it's the best way to get a stable install without having to revert to Odin/Heimdall.
Downloading now
Download complete
backups in progress
Update: Install went smooth as silk - letting it bake now
Saves a lot of clickies!
Working fine for me, so far. Been up and running for about 45 minutes with no issues.
I tried the one from the main development post and it bricked my phone. Its unbricked now so will this one actually flash correctly?
Did you unbrick using a gingerbread rom? Are you currently ON gingerbread? If so, then this should work fine for you.
FBis251 said:
Did you unbrick using a gingerbread rom? Are you currently ON gingerbread? If so, then this should work fine for you.
Click to expand...
Click to collapse
Yeah i had to odin then i restored my old backup of valhalla black 3.2
This should work fine for you then. Just make sure you don't restore any nandroid data and if you restore a titanium backup that you only restore user apps.
The install went just fine. Listened to Linda & thought I heard "her" say something about not converting. I didn't catch the verbiage, though, so I opened a shell & checked. /cache, /data, and /system are all rfs, not ext4.
stephen_w said:
The install went just fine. Listened to Linda & thought I heard "her" say something about not converting. I didn't catch the verbiage, though, so I opened a shell & checked. /cache, /data, and /system are all rfs, not ext4.
Click to expand...
Click to collapse
Ah, I think you had lagfix disabled in voodoo options.
FBis251 said:
Ah, I think you had lagfix disabled in voodoo options.
Click to expand...
Click to collapse
D'oh. Is there a way for the installer to override those? (I did have it disabled - my bad. I guess I forgot to re-enable it after going back to 2.3.6 with Bryan's one-click).
downloaded, installed and baked. lol so far not noticing any issues. well report back later on with any findings.
sent from within pure darkness
stephen_w said:
D'oh. Is there a way for the installer to override those? (I did have it disabled - my bad. I guess I forgot to re-enable it after going back to 2.3.6 with Bryan's one-click).
Click to expand...
Click to collapse
Funny, until I saw you mention it, I didn't realize I hadn't heard Linda at all... I was working while it was rebooting and it didn't register.
So, booted back to recovery just now, system lagfix is Yes, but voodoo lagfix was disabled...
Set it to enable on next boot.
Booted and nada... no Linda Lovin'
Back to recovery... still says disabled/next boot enable...
Boot again... and same thing...
I'm going to clear and start over.
Other than the above - no problems that I noticed...
FB,
Thank you for making this, I really think this will help out some of the people that don't read and flash away. (I haven't had problems, but that's because I read). I know that when everyone started coming out with the "no wipe" roms it was fun and all, but I believe that it just causes problems in the long run. A clean wipe is the best method. As you stated in the OP, I hope the devs start to use this package that you have cooked up for flashing a rom. It should help keep the "my phone does (insert random problem here) and its not supposed to" posts out of the devs' threads.
Thanks Again
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
Core,
Download voodoo control app and check if it says lagfix is enabled in there. It should say EXT4 on /system /cache/ data. I noticed in CWM it doesn't list it as being enable, even when I have disabled and re-enabled it again, though voodoo control app says it is enabled.
stephen_w said:
D'oh. Is there a way for the installer to override those? (I did have it disabled - my bad. I guess I forgot to re-enable it after going back to 2.3.6 with Bryan's one-click).
Click to expand...
Click to collapse
Core618 said:
So, booted back to recovery just now, system lagfix is Yes, but voodoo lagfix was disabled...
Set it to enable on next boot.
Booted and nada... no Linda Lovin'
Back to recovery... still says disabled/next boot enable...
Boot again... and same thing...
Click to expand...
Click to collapse
I'll have to look through the Voodoo initramfs since I forgot which files it checks for, but it can be added into the files it copies over so that it converts automatically.
The updater-script does the ext4 conversion in order to do the format, but if you have terminal emulator you can run
Code:
mount | grep ext4
If you see any result (you should see 3 lines at least) you're on ext4 already.
FBis251 said:
I'll have to look through the Voodoo initramfs since I forgot which files it checks for, but it can be added into the files it copies over so that it converts automatically.
The updater-script does the ext4 conversion in order to do the format, but if you have terminal emulator you can run
Code:
mount | grep ext4
If you see any result (you should see 3 lines at least) you're on ext4 already.
Click to expand...
Click to collapse
I'll check mounts in a little while
The bit where it keeps telling me "Voodoo lagfix is actually: disabled
next boot: enabled
No matter how many times I reboot is driving me crazy!
Core618 said:
I'll check mounts in a little while
The bit where it keeps telling me "Voodoo lagfix is actually: disabled
next boot: enabled
No matter how many times I reboot is driving me crazy!
Click to expand...
Click to collapse
I checked my mounts and all three (system, cache, and data) are ext4. I can validate what Core's saying as a potential bug because CWM shows:
Voodoo lagfix is actually: disabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
stephen_w said:
I checked my mounts and all three (system, cache, and data) are ext4. I can validate what Core's saying as a potential bug because CWM shows:
Voodoo lagfix is actually: disabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
Click to expand...
Click to collapse
I'll have to look into this later tonight since I'm about to head out.
FBis251 said:
This should work fine for you then. Just make sure you don't restore any nandroid data and if you restore a titanium backup that you only restore user apps.
Click to expand...
Click to collapse
Do you mean we should start completely fresh after this flash? What happens if I do an advance restore of data afterwards?
BTW, awesome work! Things just keep getting better for our 4g's
Sent from my SGH-T959V using XDA App
7TimesCursed said:
Do you mean we should start completely fresh after this flash? What happens if I do an advance restore of data afterwards?
BTW, awesome work! Things just keep getting better for our 4g's
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Since I already had 3.3 fixed onboard, after I tinkered around with things I did go back and restore data from advanced. I haven't had any problems, yet, but I haven't touched everything I have installed so I can't be 100% sure.
If you're coming from anything else, you might want to start from scratch.
Install your apps from the market, and if needed, do data only restores for those apps from TB if you use it...
That'd be the safe bet... just my 2 coppers worth...
Barebone SGS4G KJ6 ROM
Use at your own risk, I take no responsibility for anything that may happen to your phone because of this ROM.
Here is a ROM that I made for myself, but what the heck, let's share. This ROM is very stock-like with just few usability mods.
Features
Will not wipe your programs or data, /data is preserved upon install
Heavily debloated. Most essentials apps are still there (like WiFi Calling)
No extra programs added, you need to add your own
ODEXed to save space in /data
CarrierIQ is completely removed
Extended Power Menu (including Screenshot)
Extended Quick Panel (10 buttons, including Data toggle)
1% battery (horizontal)
CRT-Off
Time zone version 2012b
/etc/hosts to cut ads out of the box (keep up to date with AdAway or similar)
Few conservative presets in build.prop and init.d
Basic with a Twist 1.1.3 kernel included
Notes
* Don't get confused about ODEXing, it's actually better to run and saves quite a bit of space in /data.
* Some Google apps (Maps, Streets, Voice) and Adobe Flash are removed from /system. Install them from market. Benefit - they can be moved to SD card this way.
* Original Swype is removed, is somebody needs it flash this.
* In case you need it, use this thread to add some bloat back.
* Factory Reset is removed from Settings->Privacy, use CWM if you ever need to reset all data.
* KJ6 modem included. Use this thread to flash a different modem if needed.
Install
Flash with CWM. Wait until the system boots up, then wait few more minutes for it to settle.
Download
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.8
Changelog
1.1.3
Removed "Mobile data connection disabled. Connect?" popup on boot
1.1.2
Removed Factory Reset from Settings->Privacy
Updated kernel
1.1.1
Fixed voicemail notifications not working without Visual Voice Mail installed
1.1.0
CIQ is properly removed
Some neutral cosmetics (logo, animations)
Minor update to the kernel
1.0.8
Fixed slow stock browser scrolling
1.0.7
Extended Quick Panel
1.0.6
Added Screenshot to power menu
1.0.5
Removed DriveSmart and Software Update from Settings menu
1.0.4
Put original framework-res.apk certificate back
1.0.3
Added power menu mod
1.0.2
Original public release
does it have a screenshot option from the power menu??
m0bstr said:
does it have a screenshot option from the power menu??
Click to expand...
Click to collapse
Nope, never bothered with power menu. I don't reboot the phone too often and to say the truth don't even remember when last time I needed to take a screenshot. I use ShootMe and QuickBoot when I need to, they both do the job just fine.
Yes, power menu is fully modded now, including Screenshot option.
Thank you for this, Anton! Love your kernel. Is this ROM ok for OC/UVing with you OC/UV kernel? I think this will be the second ROM I have ever installed. Haven't bothered to try anything since first getting Val Final.
Download link is not working
Sent from my SGH-T959V using XDA
Does this come pre-rooted?
Blaggah said:
Does this come pre-rooted?
Click to expand...
Click to collapse
Yeppers it does.
I updated the link. I actually took it down on purpose, wanted to look at something but never had time.
I was troubleshooting an error message during boot time, so I traced it to the CIQ trying to execute some on-boot code, which was removed by Krylon. Strangely the original code itself doesn't do much, it's initilizing a broadcast receiver with an empty onReceive method. Removing this was a moot point, it probably didn't do much. I disabled the BOOT_COMPLETED permission for the service to avoid the error message.
So I looked at the CIQ more closely. What I found is a little peculiar. The main CIQ code is integrated quite deeply into the framework, it cannot be removed easily, there are just too many calls that send various metrics to the CIQ Agent. The main CIQ classes are not in the framework.jar, they are in ext.jar. Probably that's why nobody noticed them and never tried to modify them. What is strange that many calls seem to be not implemented. For example the sumbitMetric is an empty method, shouldSubmitMetric always returns zero, etc.
It's possible that T-Mobile decided not to use CIQ on our phone (at least extensively), but instead of removing it completely just plugged few calls.
I'm removing the "CIQ removed" description because it's actually not removed, although may not be doing much.
I cannot get it to boot. After the "Galaxy S 4G" screen, the screen goes back then nothing ever happens. I rebooted into CWM (which still shows Team Acid's logo) and tried fixing permissions to no avail.
Given that the OP says it won't wipe programs, data, etc, was it possibly a Bad Idea™ to have wiped everything before installing this ROM?
Update:
Indeed, installing from a blank phone (literally, I wiped everything) didn't work for me. I flashed Bryan's one-click with CWM, it booted, rebooted into recovery, flashed this, and it booted. Now for testing. Thanks, Anton!
I had the same issue as well... Thought it was just my phone
Sent from my SGH-T959V using xda premium
Would be interesting to look at the logcat to see where it's stuck.
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
wont flash
I wipe everything, the ROM installs, and then black screen...noting. Let it sit for 20min however this did not resolve issue. I was able to install Valhalla no prob. flashed your rom on top of Valhalla and then my phone boots your rom. Do i need to install on top of another rom? I should just be able to whipe my phone and install your rom correct?
AntonX said:
Would be interesting to look at the logcat to see where it's stuck.
Click to expand...
Click to collapse
I can probably capture that because I can use adb to get into the OS. I ran top to see what, if anything, was hogging CPU but there was nothing obvious & CPU usage was minimal. I have the phone running now but I'm willing to wipe it again and re-flash. Mind you, I did more than factory reset. I was quite literally trying to start from scratch, so here's what I did (if this helps at all):
Backed up /efs to my PC
Backed up the SD card to my PC
Wiped cache
Wiped Davlik cache
Wiped battery stats
Performed a nandroid backup
Copied the backup from /sdcard/clockworkmod/backup to my PC
Formatted /data, /system, & /sdcard
Rebooted back into recovery
Copied the ROM to the SD card
Flashed it
Let it cook for ~20 minutes
So it was quite literally a blank slate.
AntonX said:
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
Click to expand...
Click to collapse
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
stephen_w said:
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
Click to expand...
Click to collapse
Wow, you really wiped everything from your phone
I'd appreciate if you send me the log. All you need to do is to save the file with "adb logcat -d >MyLogFile.log" after couple of minutes of this black screen. On an factory reset phone ODEXed ROM should boot very fast the first time because it doesn't have to build Dalvik.
I just tried downloading from my own link and reinstalling, everything seems OK. I also tried installing after full phone reset yesterday, it went fine too. I don't want to reset and restore everything anymore, too lazy
If it proves to be the certificate in the framework-res.apk, I may need to put the original AndroidManifest.xml back.
Hey Anton,
You can snag the logcat from here. In case anyone wants them & to clarify what I did, here are the steps I followed (similar to above but more detailed):
- Boot into CWM
adb reboot recovery- Disable voodoo lagfix
- voodoo lagfix- disable lagfix- /system lagfix off- Reboot
- Create a backup directory structure on your PC (mine is in C:\Users\username\Downloads\SGS4G)
mkdir backupscd backupsmkdir efs nandroid sdcard- Backup /efs to your PC
cd efsadb pull /efs/- Backup /sdcard to your PC
cd ..\sdcardadb pull /sdcard/- Boot into CWM
adb reboot recovery- Wipe cache
- wipe cache partition- Wipe Dalvik cache
- advanced- Wipe Dalvik Cache- Wipe battery stats
- Wipe Battery Stats- Create a nandroid backup
- +++++Go Back+++++- backup and restore- backup- Copy the backup to your PC
cd ..\nandroidadb pull /sdcard/clockworkmod/backup/- Format /data
- mounts and storage- format /data- Format /sdcard
- format /sdcard- Format /system
- format /system- Reboot into CWM (necessary for CWM to see the sdcard contents)
- +++++Go Back+++++- advanced- Reboot Recovery- Copy the ROM to the sdcard (this is from the directory in which the ROM is located on your PC)
adb push ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip /sdcard/- Flash the ROM
- install zip from sdcard- choose zip from sdcard- ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip- Reboot & let it sit for ~10 minutes
Sorry for the lengthy post, but I wanted to ensure there was transparency in what I did.
stephen_w,
Seems that it's not framework-res.apk issue, it's not complaining about any certificates.
A lot of unknown permissions in the log, but it's OK, we've removed some of the system packages that grant those permissions but they do more harm than good in the end.
The crash has something to do with that: *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService. Hm......
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Weird...it flashed fine for me with no wipe....
I did move on and never gave it a break in....but it did work
Sent from my SGH-T959V using xda premium
AntonX said:
stephen_w,
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Click to expand...
Click to collapse
I usually don't do it that extensively at all. I was writing a process for myself in case I wanted to really clean it out So this gave me a good excuse to test it. I was having some weirdness which prompted me to write the instructions for myself.
I haven't tried shutting it down after the install. I can certainly try that for you, if you like.
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Sent from my SGH-T959V using xda premium
Lawful123 said:
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Click to expand...
Click to collapse
Doubtful. Nothing I can think of, off-hand. I have to wait until later this afternoon/evening to reflash it and try powering off vs. rebooting from recovery. If you have the chance, please feel free and let us know what happens.