Database Info

[Q] Just to get the n00b questions out of the way.

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.

G-Talk

Does anyone know if we can flash the hacked G-Talk app for video and voice chat on Gummy?
Sent from my SCH-I510 using xda premium

I heard it works, but I have no use for it. Make sure you uninstall/freeze the stock gtalk first.
Sent from my Droid Charge running GummyCharged 2.0

kvswim said:
I heard it works, but I have no use for it. Make sure you uninstall/freeze the stock gtalk first.
Sent from my Droid Charge running GummyCharged 2.0
Click to expand...
Click to collapse
So I would just go into Root Explorer and do an uninstall in system/apps?
Sent from my GummyCharged GBE SCH-I510

So I don't know if it's the Hacked G-Talk app that I'm flashing through CWR or if it's the process of Holding power button and choosing recovery. But when I boot back up from recovery I it's like the phone has factory data reset as far as the whole setup of the phone has reset but my apps that I installed are all there. When I go into terminal and mount the filesystem, System and Data are EXT4 but Dbdata and Cache have reverted to RFS. the G-Talk app I'm trying to flash is by XsMagical. Like I said I don't know if it's the flashing of the .zip or Booting into recovery through the Recovery option in the power menu. I'm reflashing GC 1.9 right now.

WilliamKingX17 said:
So I don't know if it's the Hacked G-Talk app that I'm flashing through CWR or if it's the process of Holding power button and choosing recovery. But when I boot back up from recovery I it's like the phone has factory data reset as far as the whole setup of the phone has reset but my apps that I installed are all there. When I go into terminal and mount the filesystem, System and Data are EXT4 but Dbdata and Cache have reverted to RFS. the G-Talk app I'm trying to flash is by XsMagical. Like I said I don't know if it's the flashing of the .zip or Booting into recovery through the Recovery option in the power menu. I'm reflashing GC 1.9 right now.
Click to expand...
Click to collapse
If you're running GC GBE 1.9 (either RC1 or RC2.3), then there is a known issue with CWR and that setup. If you have your partitions converted to EXT4, then going into CWR will reformat them (I guess just some of them) to RFS and wipe your data.
From what I have read and experienced, if you want to have GC GBE and full EXT4, then you can't use CWR. Also, if you want the ability to use CWR, then you can't fully be on EXT4.
I flashed a CWR package right after installing RC2.3, so I didn't notice a reset, but my filesystem is just like yours - part RFS and part EXT4. After reading that using CWR could wipe the phone, I have refrained from flashing anything else. From your information, it looks like the "damage" to my phone is done, and I should be okay to flash anything else through CWR now.
I'm very interested to hear if the hacked GTalk app worked for you by itself, or if you needed something else to make it work. One thread I was looking at included some additional framework pieces, in case they were needed. I'm just curious if that's needed for our phones.

The video works but the audio does not. There's apparently a fix for it but the fixed version only allows video over a wifi connection. For me that's no problem and I've been trying to hunt down that APK but so far I've had no luck.

[REQUEST] Platypus Egg Kernel flashable

I posted this in the general section, but no one has answered it. Please release the platypus egg kernel as a .zip file or post a link to where I can download the kg2 odin file so that I can flash the bali port. I want voodoo and refuse to flash an entire rom just to get voodoo.

check the heimdall thread i have it posted there last 2 pages

heimdall isnt working on my computer unless you posted an odin file in that thread its not going to help me.

Unless you are in love with the Samsung launcher vs. GOv2's Launcher Pro (or my preferance: download ADW.Launcher), there is no reason not to upgrade to GOv2 and get all the other tweaks in addition to the Kernal.
I know you say you've had trouble in the past, but just try it like this:
1) Boot in to CWM with the GOv2 zip on the sdcard.
2) Check your mounts
3) Run a backup
4) Check your mounts
5) Wipe data, wipe cash, wipe dalvik-cache
6) Check your mounts
7) Flash GOv2
8) Check your mounts
9) Advanced-Restore data partition only
10) Check your mounts
11) Reboot
Best case, everything works great and you just upgraded the Kernal as well as many other good things / tweaks, while still keeping all your apps and all your config.
Worst case, just boot in to CWM and restore what you currently have. You only waste about 15min of your life in trying, and I don't see how GOv2 could have any drawbacks over stock+bali (other then the alternate Launcher and themed icons/widgets - I installed AWD, unthemed all my icons, and I love the transparent-black widgets).
You should NEVER need to Odin unless you can't get in to CWM (which should never happen).
NOTE: When I say check your mounts, each partition on that CWM page should read "unmount" (meaning they are currently mounted). Check your mounts before/after each step, including before the final reboot.

I know how to check mounts. I want to keep touchwiz because of the themes. I really like the stock themes, and none of the launchers from the market have the option to view the app drawer as a list. if they did, i would consider using one of them. the stock themes are not really what is important. viewing the app drawer as a list is. my process thus far has been as follows: odin to kd1, kies to kj2, root, backup, flash rom, then restore system only from the backup. it hasnt been stable enough so far, but right now i am considering trying it a little different. i am going to get back to stock kj2, then delete all bloatware and all google apps from the system, then backup, then flash, then restore system from the backup, then reinstall any apps i want from the market. I also have the .apk file for play store, so i am also going to delete market and market updater before backing up. then after restoring system, i am just going to install google play store from my sd card. if anyone has any thoughts, please respond soon. i already odined back to kd1, getting ready to do kies to kj2. that takes a few minutes as i have to unplug the phone from the pc and reinstall the drivers through kies.

But I would prefer to just flash the kernel. I dont see any reason why they wouldnt release it.

well, after a very lengthy and complicated process, i finally have the platypus kernel on kj2. here is what i did. i started kies mini but didnt plug my phone in yet. i just went to menu and install driver. then i odined. after reboot, unplug the phone, back to kies, install drivers again. plug phone in and update firmware through kies. after reboot, unplug and install driver again. turn on usb debugging and root through super one click. reboot. install drivers again. then go through the system and delete all google and tmobile apps. get cwm running and take a backup. connect mass storage and copy b2tb to sd card. flash according to instructions. reboot. let the phone sit while i walk my dog. come back, boot into recovery, select advanced restore, system only. fix permissions, wipe dalvik, reboot. reinstall desired apps through market website. that was all last night. today i supercharged. so far so good.

well, its been almost 24 hours since i finished everything up. stable so far. no random reboots, no force closes, no screen lag or freeze, no crashes. i kept my backup from before the flash, just in case. gonna give it another day or two to make sure everything really is stable, then take a backup of the current setup. once i do that, im leaving this phone the hell alone lol.

To clear the record, I never had trouble flashing roms except for once and it was because i flashed cwm through rom manager before i knew not to do that. my most recent trouble started when i attempted to move dalvik to my ext2 partition. something went wrong when i attempted to move dalvik, and it got deleted. i had a backup and tried to restore, but got an md5sum mismatch. i did a factory reset through voodoo and it screwed up my apn settings. i restored default settings, but it didnt work. so basically after much trial and error, i have a stable advice again.

Do you still want this as a flashable zip???
Sent from my SPH-D710 using xda premium

ReActiveDisorder said:
Do you still want this as a flashable zip???
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I would like this as a flashable .zip, cant find it anywhere.

so if i flash GoV2 , ill get kj2 and all the other goodies? cause i am having a hard time finding stuff on here. and honestly once i get gov2 on my soon to be sidekick. thats all im doing to it since its dead here. i hear its the best

I'm on Generic Ginger 3.8 with the platypus egg V1 kernel, blaze 4g radio. Kicks ass! Battery life is amazing... I just wanted to flash the kernel on some other roms..
Sent from my SGH-T839 using xda premium

HateMeILoveIt said:
I'm on Generic Ginger 3.8 with the platypus egg V1 kernel, blaze 4g radio. Kicks ass! Battery life is amazing... I just wanted to flash the kernel on some other roms..
Sent from my SGH-T839 using xda premium
Click to expand...
Click to collapse
i don't have a flashable zip unfortunately, but what i've been doing is flashing the zimage thru Odin. if that helps you at all, if you're comfortable with Odin, i've been meaning to upload the tar file for the kernel that i made to this thread:
http://forum.xda-developers.com/showthread.php?t=1538576
WolfV2 said he would add it to the OP once i uploaded it. other than that, ReActiveDisorder had made a flashable zip, but i see that all his links have been removed.
edit: there's also nxd's tutorial on flashing a kernel with Hemidall here:
http://forum.xda-developers.com/showthread.php?t=1665150

yogi2010 said:
i don't have a flashable zip unfortunately, but what i've been doing is flashing the zimage thru Odin. if that helps you at all, if you're comfortable with Odin, i've been meaning to upload the tar file for the kernel that i made to this thread:
http://forum.xda-developers.com/showthread.php?t=1538576
WolfV2 said he would add it to the OP once i uploaded it. other than that, ReActiveDisorder had made a flashable zip, but i see that all his links have been removed.
edit: there's also nxd's tutorial on flashing a kernel with Hemidall here:
http://forum.xda-developers.com/showthread.php?t=1665150
Click to expand...
Click to collapse
Thanks a alot, man. Appreciate it.
Sent from my SGH-T839 using xda premium

HateMeILoveIt said:
Thanks a alot, man. Appreciate it.
Sent from my SGH-T839 using xda premium
Click to expand...
Click to collapse
Wait hold up, what am I thinking... had a little brain freeze there!. You could just use nxd's build of the Bali Kernel for KJ2:
http://forum.xda-developers.com/showthread.php?t=1663622
That also has the keystroke logger removed, AND a patch to improve keyboard responsiveness and efficiency!

yogi2010 said:
Wait hold up, what am I thinking... had a little brain freeze there!. You could just use nxd's build of the Bali Kernel for KJ2:
http://forum.xda-developers.com/showthread.php?t=1663622
That also has the keystroke logger removed, AND a patch to improve keyboard responsiveness and efficiency!
Click to expand...
Click to collapse
Sweetness! Thanks again.
Sent from my SGH-T839 using xda premium

HateMeILoveIt said:
Sweetness! Thanks again.
Sent from my SGH-T839 using xda premium
Click to expand...
Click to collapse
no problem, enjoy. if you haven't already, read the thread to see how to play with the timer and column delay settings for the keyboard!

Moved thread to general where it should be

[Q] Using ROM: "JVU[2.3.6] SAUROM", but Apps go away after Reboot

Hi All,
I seriously read all 17 pages of SAUROM's Dev page and only found 1 other use having this issue but post has no response:
http://forum.xda-developers.com/showpost.php?p=20344195&postcount=31
I also searched and most people have somewhat similar issues but not like mine where it works first time fine then upon reboot Apps disappear.
I've rooted my Infuse a long time ago and have been ROM'ing it for several months now. I've changed several ROMs and some have lots of pieces I love but has issues with something I really need (like bluetooth).
So I gave SAUROM 'One rom to rule em all' a shot. I actually really am impressed upon initial Flash. I made lots of changes, and then lost root/SU, then found SU-fix and applied. It worked for about one day then when I reboot my Apps (including Market) were dimmed-out. So I tried to search but no decent threads.
I thought perhaps another Flash of the ROM would fix, but same issue, then thought perhaps a kernel change so I did that too.
But I just did it again and during first boot everything looks good, I make changes add my gmail acct, use some Apps (actually last time I used Supercharger and installed busybox) but even prior to this it was doing the same thing. Then thinking perhaps it might have fixed it, rebooted and still same thing.
Is there any *.zip or setting that perhaps I can check to fix this? Some script that may help to check where this issue lies? How about fstab file that I can check and edit to fix this??
This happens every time I reboot! I installed apps last night and actually held off posting this, then this morning I rebooted and Apps disappear again (even Play Store).

Furosh said:
Hi All,
I seriously read all 17 pages of SAUROM's Dev page and only found 1 other use having this issue but post has no response:
http://forum.xda-developers.com/showpost.php?p=20344195&postcount=31
I also searched and most people have somewhat similar issues but not like mine where it works first time fine then upon reboot Apps disappear.
I've rooted my Infuse a long time ago and have been ROM'ing it for several months now. I've changed several ROMs and some have lots of pieces I love but has issues with something I really need (like bluetooth).
So I gave SAUROM 'One rom to rule em all' a shot. I actually really am impressed upon initial Flash. I made lots of changes, and then lost root/SU, then found SU-fix and applied. It worked for about one day then when I reboot my Apps (including Market) were dimmed-out. So I tried to search but no decent threads.
I thought perhaps another Flash of the ROM would fix, but same issue, then thought perhaps a kernel change so I did that too.
But I just did it again and during first boot everything looks good, I make changes add my gmail acct, use some Apps (actually last time I used Supercharger and installed busybox) but even prior to this it was doing the same thing. Then thinking perhaps it might have fixed it, rebooted and still same thing.
Is there any *.zip or setting that perhaps I can check to fix this? Some script that may help to check where this issue lies? How about fstab file that I can check and edit to fix this??
This happens every time I reboot! I installed apps last night and actually held off posting this, then this morning I rebooted and Apps disappear again (even Play Store).
Click to expand...
Click to collapse
Move your apps to phone.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2 Beta-5

bigfau said:
Move your apps to phone.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
First thanks for the response bigfau!
I have checked this to see if this option would be a good way to resolve my issue but weird thing is that these dimmed-out apps that appear to be on my sdcard actually go away. If they were truly installed on sdcard like SS above says, then I should be able to:
Go to Settings > Applications > Manage applications > On SD Card >
Select App > "Move to phone" but they're not there, only XDA Premium . (attached SS)
After a reboot, I have to go to My Files, App_Manager > App_Backup > user_apps > Re-install My Apps again. But any reboot puts me back at square one.

1. Uninstall and install your launcher app (don't restore)
2. Wipe your dalvik cache (if rooted)
Try this and let me know if that helps.

diablo009 said:
1. Uninstall and install your launcher app (don't restore)
2. Wipe your dalvik cache (if rooted)
Try this and let me know if that helps.
Click to expand...
Click to collapse
*Thanks, your response makes sense as I remember TWLauncher errors with this ROM and think yes my Launcher is the culprit.
Ive been trying to Uninstall and install a launcher (which I thought would be relatively simple).
1. I downloaded/installed 2 different Launchers (Launcher Pro & Go Launcher Ex) from Play Store.
2. Downloaded TW4Manager.apk, tw4key.zip, and ShareApp.apk (for TWLauncer 4.5).
3. Moved TouchWiz30Launcher.apk out of system/apps/ and backed up *just in case*, then rebooted into Recovery and Wiped Dalvik Cache.
When it was booting, it stayed on the Galaxy S boot animation screen for the longest and never booted.
I decided to attempt to Flash Saurom again, (wipe user data, which cache, wipe Dalvik Cache, install ROM zip) and I'm trying again.
But seems like I got some weird chicken/egg thing going on. I can only install apps while booted or phone is on.
Did i do something incorrect?

Furosh said:
I can only install apps while booted or phone is on.
Click to expand...
Click to collapse
Isn't this how it works? I am not sure how you would install apps when the phone is turned off? Or do you mean screen on?

diablo009 said:
Isn't this how it works? I am not sure how you would install apps when the phone is turned off? Or do you mean screen on?
Click to expand...
Click to collapse
Hi diablo009,
Sorry what I was referring to was that it seems yes I can install Apps while phone is on, but they're only available during that time (after installed). Its like they are in RAM and lose them if I shutdown or reboot.
I'm sure it's not the ROM I used as stated in the Title because I've recently done lots of testing on my phone. I again Re-flashed the ROM again doing:
1. Wipe user data/wipe cache/wipe dalvik cache, install ROM .zip.
2. Run Su-fix su-3.0.5-efgh-signed.zip
*Ive tried this with and without reboot in between 1 & 2.
Still same symptoms, loads first time fine. Runs setup, is rooted, can install Apps, then upon reboot they're gone.
So I said okay let's test out another ROM to see if same results, and so yesterday I changed to GamerzRom v8.1, then upped to 9.0 and same results with Apps.
I've used different kernel's (DD_03042012.zip & kernel-2011-11-27.12-40.zip), used diff ROMs, and have also attempted to get back to Stock either by using:
-SGH-I997_UCLB3_INFUSE.zip (I guess this is Stock with Root & couple more things)
-Get back to Stock ROM by using Download-Mode and SGH-i997-UCKJ4-One-Click.jar
After either of these, attempt to re-flash and see if problems go away but they haven't.
Weird thing is sometimes I lose SU/Root sometimes I don't. I'm sure it's something I've done to my phone or the filesystem which is why I'd like to be able to check it out, like fstab, mtab (if there's one), permissions or something else but I'm not sure what to look for =/
Thoughts or other areas I can check?
A checklist would be awesome right now if I could find one....

Backup the data you have on your internal/external SD cards, and format them please. And try to install an app, reboot, and let me know if the issue is still present.

SD
I had the same issue. I blamed it on a bad SD card. I removed the SD card all together and never had the problem since. I only had the stock 2gb card in there so it was not worth the hassle.

icecreamwhat said:
I had the same issue. I blamed it on a bad SD card. I removed the SD card all together and never had the problem since. I only had the stock 2gb card in there so it was not worth the hassle.
Click to expand...
Click to collapse
This is what even I am suspecting now. So only wanted him to format both internal and external. And this one reason I recommend no less than class 6 cards for phones, preferably class 10.
---------- Post added at 04:44 PM ---------- Previous post was at 04:39 PM ----------
1. Clean wipe and ROM install
2. Clean wipe with a different ROM
3. Clear dalvik cache and cache
4. Wipe data for launcher
5. Fresh install of launcher
6. Fresh install of apps and no restoring with TiBu
7. Formatting internal and external memory
8. Take out external memory
9. Change external SD card
There's your checklist, as far as I can think of. And I have marked in green the options you said you have tried.

Hi, you just have to replace the file vold. Fstab and place it on /system /etc
Pm with your mail and I will send to you b/c I have it with me but don't know how to upload here
The file is suppose to say that the apps must stay on the sdcard..
Qkster explain that to me very well, if I were you, I look in his roms thread..
Let me see
Sent from my SAMSUNG-SGH-I997 using XDA

http://forum.xda-developers.com/showthread.php?p=22723345
Sent from my SAMSUNG-SGH-I997 using XDA

diablo009 said:
Backup the data you have on your internal/external SD cards, and format them please. And try to install an app, reboot, and let me know if the issue is still present.
Click to expand...
Click to collapse
Okay glad to report this has helped me! Not sure if the scard (internal/external) was bad or getting full or what but here's what I did:
1. Copied all my data (sdcard [int/ext]) to PC.
2. Format scard: Settings > SD Card/Storage > Unmount SD Card > Format
*Did this for both SDCard & USB Storage
Result in "Lady voice on partioning boot mesg, (basically inoperable phone).
*My fault because I didn't need to do USB storage? Should I have done both SDCard & USB Storage? Either way I think i wanted to restart from scratch with factory type reset/stock ROM.
3. Boot Download-Mode and ROM using: SGH-i997-UCKJ4-One-Click.jar
4. Root phone and tried to Re-flash with custom ROM (Saurom) but need CWM recovery. CWM was in blue-mode, needed Green or Red to flash ROM.
5. Downloading SGS Kernel flasher and flashing it with Entropy's DD
For this I used: DD_03042012.zip, but for me I noticed Market and Maps were "dimmed" out and thought I'm back to square one!
Dunno if this was coincidence or something I did to cause this or what but I think it's important to note because issue seemed to reappear.
I changed the kernel to: kernel-2011-11-27.12-40.zip and dimmed Market/Maps went away.
6. Booted in Recovery, wipe user data/wipe cache/ wipe Dalvik cache, Flash ROM: JVU[2.3.6] SAUROM
7. Booted up, went through SetupWizard, then realized lost Root.
8. Run Su-fix su-3.0.5-efgh-signed.zip
9. Boot phone, verified Root, installed some Apps, and rebooted & Power-Off over 10 times.
All looks good now!
So far its looking like my issue went away!

@OP: This happens many times when the android data files on the external SD get corrupted. And happy to know your issue is resolved

[ROM] Barebone SGS4G KJ6 1.1.3

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 backups​cd backups​mkdir efs nandroid sdcard​- Backup /efs to your PC
cd efs​adb pull /efs/​- Backup /sdcard to your PC
cd ..\sdcard​adb 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 ..\nandroid​adb 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.