[MOD] DarkTremor (DT) a2sd on Synergy and Kingdom ROMs - EVO 4G Themes and Apps

I mucked around with an updater script for Synergy last night to replace the built in CM A2SD with DT A2SD. It works. I've tested this on Nightly 6/15 and Nightly 6/16 and it works flawlessly. This should work with ANY ROM that uses the built-in CM A2SD, but I've only tested on Synergy. Let me know and I'll make changes here and there, but my main goal is having this work on Synergy, so I'm not going to be super supportive of other ROMs at the moment.
First of all:
All credit for DT a2sd goes to TKirton. I did NOT write the DT a2sd script. I just modified it to work with Synergy.
Update:
Tested successfully on Virus' Kingdom Revolution B1.3
Update:
This script will now automatically wipe Cache and Dalvik-Cache
What I did:
I updated (and re-signed) the original DT install script. It now looks for the presence of CM A2SD and removes it before installing DT. This is what was causing bootloops when trying to install it after a Synergy installation: The two A2SD programs were conflicting.
I have tested this on a wiped/fresh install as well as an install where I've completely set up the ROM (restored apps, set them up, etc) to my liking, and I had no issues.
Instructions:
NANDROID NANDROID NANDROID...I can't stress this enough. Just because it worked for me doesn't mean it will work for YOU (I can't see any reason why it wouldn't but better safe than sorry).
I have successfully installed this immediately after flashing both Kingom and Synergy ROMs before the first reboot. Your mileage may vary. Some ROM's need to boot once to set everything up which is why I suggest booting it the first time and THEN flashing the zip, but at least on Synergy and Kingdom it doesn't seem to be necessary.
Fresh install:
1. Flash Synergy
2. Let it boot. Set up your google account (or not if you want to do it later, it doesn't matter.)
3. Reboot into recovery and flash synergy-dtapps2sd-2.7.5.3-beta04-signed.zip
4. Reboot.
5. Your phone may reboot once or twice. You're not boot looping I promise.
6. Once it comes up you can check the installation by going into terminal (or adb shell) and typing 'a2sd check'. If the a2sd check screen comes up you're all set.
Installing after your ROM is set up:
1. Boot to recovery
2. Wipe cache and dalvik-cache (no longer necessary)
3. Flash synergy-dtapps2sd-2.7.5.3-beta04-signed.zip
4. Reboot
5. Your phone might/might not reboot a couple of times.
6. Once it comes up you can check the installation by going into terminal (or adb shell) and typing 'a2sd check' as above.
Usage:
Type a2sd help to get a list of commands. Some useful ones (to me) are:
a2sd cachesd (moves dalvik-cache to SD)
a2sd cachepart (moves dalvik-cache to /cache)
a2sd nocache (moves dalvik-cache to internal storage)
a2sd zipalign (performs a zipalign at boot time)
a2sd heapsizexx (changes the system heapsize. a2sd heapsize32 for example will make your heapsize...you guessed it, 32mb)
Those are the ones I'm mainly using. You can get the full list (including memory killer settings and such) by doing a2sd help from terminal or adb shell.

I found this after I already installed everything and set up my nightly 6/16. I still just nandroid'd and flashed it anyway... hope it works... haha...

Looks like it worked, from what you posted in Myn's thread. And that's the whole idea: You should be able install it whenever you want, in case you decide to tweak things after you have your ROM set up the way you want it. This method means not having to wipe/reinstall, which is a big plus as far as I'm concerned.

Gonna give this a try when once I Nand and switch to Synergy.
p.s. I'm in 19720 everyday. lol

boostedeg said:
Gonna give this a try when once I Nand and switch to Synergy.
p.s. I'm in 19720 everyday. lol
Click to expand...
Click to collapse
Let me know how it goes. I updated it so it wipes cache and dalvik for you.
And I'm in 19701 now...gotta change that info. That's cool though.

Successfully tested on Virus Kingdom B1.3

I'm new at this stuff. Is this better than what is native in the rom? Make it run better? Thanks
Sent from my PC36100 using XDA App

chrisfales said:
I'm new at this stuff. Is this better than what is native in the rom? Make it run better? Thanks
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The rom comes with dalvik-cache set up on the SD card. Flashing this moves it back to internal storage. It's a trade-off really. You'll lose about 130mb on /data, but you'll gain some speed.
Having said that, if your ROM is running quickly enough for you and it's stable...and if you don't feel the need to tinker with memory settings and such...leave it as it is. I never mess with something that's working for me. ("If it ain't broke, don't fix it.")

I've noticed the Synergy updater has a beta 5. What's the difference? Apologize but I didn't get a chance to read through all the posts on the warm 2.2 thread.

gqukyo said:
I've noticed the Synergy updater has a beta 5. What's the difference? Apologize but I didn't get a chance to read through all the posts on the warm 2.2 thread.
Click to expand...
Click to collapse
It's the same thing. I forgot to change the name of it when I uploaded it here.
Edit: Changed it here as well.

I will be running this shortly and will report back.

smw6180 said:
I mucked around with an updater script for Synergy last night to replace the built in CM A2SD with DT A2SD. It works. I've tested this on Nightly 6/15 and Nightly 6/16 and it works flawlessly. This should work with ANY ROM that uses the built-in CM A2SD, but I've only tested on Synergy. Let me know and I'll make changes here and there, but my main goal is having this work on Synergy, so I'm not going to be super supportive of other ROMs at the moment.
First of all:
All credit for DT a2sd goes to TKirton. I did NOT write the DT a2sd script. I just modified it to work with Synergy.
Update:
Tested successfully on Virus' Kingdom Revolution B1.3
Update:
This script will now automatically wipe Cache and Dalvik-Cache
What I did:
I updated (and re-signed) the original DT install script. It now looks for the presence of CM A2SD and removes it before installing DT. This is what was causing bootloops when trying to install it after a Synergy installation: The two A2SD programs were conflicting.
I have tested this on a wiped/fresh install as well as an install where I've completely set up the ROM (restored apps, set them up, etc) to my liking, and I had no issues.
Instructions:
NANDROID NANDROID NANDROID...I can't stress this enough. Just because it worked for me doesn't mean it will work for YOU (I can't see any reason why it wouldn't but better safe than sorry).
I have successfully installed this immediately after flashing both Kingom and Synergy ROMs before the first reboot. Your mileage may vary. Some ROM's need to boot once to set everything up which is why I suggest booting it the first time and THEN flashing the zip, but at least on Synergy and Kingdom it doesn't seem to be necessary.
Fresh install:
1. Flash Synergy
2. Let it boot. Set up your google account (or not if you want to do it later, it doesn't matter.)
3. Reboot into recovery and flash synergy-dtapps2sd-2.7.5.3-beta04-signed.zip
4. Reboot.
5. Your phone may reboot once or twice. You're not boot looping I promise.
6. Once it comes up you can check the installation by going into terminal (or adb shell) and typing 'a2sd check'. If the a2sd check screen comes up you're all set.
Installing after your ROM is set up:
1. Boot to recovery
2. Wipe cache and dalvik-cache (no longer necessary)
3. Flash synergy-dtapps2sd-2.7.5.3-beta04-signed.zip
4. Reboot
5. Your phone might/might not reboot a couple of times.
6. Once it comes up you can check the installation by going into terminal (or adb shell) and typing 'a2sd check' as above.
Usage:
Type a2sd help to get a list of commands. Some useful ones (to me) are:
a2sd cachesd (moves dalvik-cache to SD)
a2sd cachepart (moves dalvik-cache to /cache)
a2sd nocache (moves dalvik-cache to internal storage)
a2sd zipalign (performs a zipalign at boot time)
a2sd heapsizexx (changes the system heapsize. a2sd heapsize32 for example will make your heapsize...you guessed it, 32mb)
Those are the ones I'm mainly using. You can get the full list (including memory killer settings and such) by doing a2sd help from terminal or adb shell.
Click to expand...
Click to collapse
Do you have to have your SD card partioned before you run this?

Adam1422 said:
Do you have to have your SD card partioned before you run this?
Click to expand...
Click to collapse
yes ;0 do it now

Ive used the dt script since I flashed us this thread any different then the cm or did I miss something in the op.
Confirm on b1.3 and works with GUI from market as well
Sent from my PC36100 using XDA Premium App

Used it with kingdom sacs v7 port. Boot loop after wrote a2sd datasd. Wipe dalvik cache and boom.. !! it booted and i got 100mb more free ram. Strange, but have no problem until using it about 20 hours.
Sent from my PC36100 using XDA Premium App

snxxxxx said:
Used it with kingdom sacs v7 port. Boot loop after wrote a2sd datasd. Wipe dalvik cache and boom.. !! it booted and i got 100mb more free ram. Strange, but have no problem until using it about 20 hours.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Do you really have to partition? That may be a problem. I formatted my phone installed synergy restarted, wiped delvick then flashed the zip, and it installed. When the phone booted, I ran titanium to restore apps, and ran out of space. I dont think it worked right.

Successfull test!
Works great on 6/23 aka b1.4 kingdom! Love it! Unfortunately it doesn't work at all on new synergy-kingdom hybrid. That's ok, I like kingdom better anyway! Anyone have wake lock issues in 1.4 using this? Pri is 1.77 but still wakelocked after dalvik move

a2sd cachesd (moves dalvik-cache to SD)
a2sd cachepart (moves dalvik-cache to /cache)
a2sd nocache (moves dalvik-cache to internal storage)
a2sd zipalign (performs a zipalign at boot time)
a2sd heapsizexx (changes the system heapsize. a2sd heapsize32 for example will make your heapsize...you guessed it, 32mb)
What are the advantages of each one of these? Should I move dalvik-cache to sd,cache or internal storage? Is there a place to find out why to do zipalign or to change the system heapsize? I'm running the stock 8gb card that is partitioned. Thanks for any help.

ianelectro said:
Unfortunately it doesn't work at all on new synergy-kingdom hybrid.
Click to expand...
Click to collapse
If you could get this script working on the new Synergy Kingdom, I would be eternally grateful, as I'm having space issues on that ROM currently (and I really shouldn't be).

a2sd
Thanks for the break down. Never fully understood how to use this. Big improvement in performance. Using partition to its proper use. Played with Heap size and got it as low as I could (15) and am very happy with the changes. Any one who has not done this SHOULD.

Related

Build Your Own alt+w Wipe...(edit: if you don't use apps2sd...)

First Note: These apps will become uninstallable! (much like any other stock rom apk) and must be deleted using the console, somehow.. anybody care to shed some light on how?
Hopefully someone can add more to this or use this info to build a much more thorough how-to, but for now here's what I've got...
Instead of building your own update.zip you can modify your alt+w wipe data to reinstall the downloaded/backed-up apks of your choice. This can also be used to install 3rd party apks without having access to any other installer, for instance if you wipe then find yourself without any access to the internet/market or a computer.
To do this you must first have the apps on the sd. I used astro to backup apps which puts the apks in /sdcard/backups/apps
I'm doing this on IonR2, your system apps may be elsewhere, mine are located in /system/app, you'll need to know where they are for this to work.
Power off your phone and do this (enter the bold stuff only, replace my directories with yours):
home+power (enter recovery)
alt+x (to go to console)
hit enter (cause the prompt says so..)
/ # mount sdcard
/ # mount system
/ # cd sdcard/backups/apps (or cd to where ever your backed up apks are)
/sdcard/backups/apps # ls *appname* (this may be useful for finding the exact *.apk name)
/sdcard/backups/apps # install -cp org.appName.com.apk /system/app (remember to capitalize where necessary)
at this point it should hang for a second then return to the "/sdcard/backups/apps #" prompt, if so the apk has successfully been added.
/sdcard/backups/apps # reboot (or install more apks if you like)
home+power then alt+w to test if you so desire. now your backed up apk should reinstall itself if you ever have to do an alt+w wipe again..(weather the apk is on the sd card or not)
I know, not very thorough but wth, I figured someone might find this as useful as I did(or be able to expand on it a bit, data, app settings etc). Also cool if you happen to have no net connection, no pc access and a wiped phone with no real useful/fun apps...
u only have to do this once, and it'll flash the new roms WITH these apps installed? how do we 'clear' these apps if we don't want to have them installed when we wipe?
Is it possible to install all the apps in your backup directory at once, with some sort of batch command?
These apps will become uninstallable! (much like any other stock rom apk) and must be deleted using the console, somehow.. anybody care to shed some light on how?
@ Lieu10ant, yeah, you only have to do once/updated rom, this modifies the base install. the newely added apks will be installed every time you alt+w (wipe). If you apply an update.zip this process will need to be redone(I'm pretty sure, haven't tried).
@ lukekirstein, I'm sure there's a way but I'm not sure how. Really hoping someone more knowledgable jumps in here with a bit more info :/
I've added a file manager(with backed up apps installer) and wifi tether because I always need/use em and never really planned on uninstalling em..
Im pretty sure you would have to use "rm" and individually remove all apps you dont want.
instead of backing up your apps, just run apps to sd and never reinstall any apps again
Breakthecycle2 said:
Im pretty sure you would have to use "rm" and individually remove all apps you dont want.
Click to expand...
Click to collapse
you would mount the system again from the recovery console and 'rm' each app you don't want. You would want to be careful not to batch delete stuff.
sonikamd said:
These apps will become uninstallable! (much like any other stock rom apk) and must be deleted using the console, somehow.. anybody care to shed some light on how?
@ lukekirstein, I'm sure there's a way but I'm not sure how. Really hoping someone more knowledgable jumps in here with a bit more info :/
Click to expand...
Click to collapse
Wouldn't it be a nice thing to make them uninstallable? That would, in theory, make them a lot more stable like the stock apps and can only be updated, not modified. You can probably delete them through console in recovery or even through ADB if you wanted to. It'd definitely be impossible to do it through some basic installer or the package uninstaller while the phone is running normally. The same process as a stock app.
I know you can't do it while the phone is running (bummer :/) but I was hoping it's possible when the phone is off.
@ Breakthecycle2, cool, I figured rm through console after mounting but haven't tried so wasn't 100% on that one.
@ Sirus20x6, I prefer this method to apps2sd, mainly because everything's stored in the phone's internal memory. Although I know most folks now seem to be using an apps2sd of some sort.
@ lukekirstein, yeah. That's why I do it this way, but some may want them uninstallable so I figured I better make a point to inform those folks
Wouldn't this decrease your internal memory since these apps are being saved to the phone so you can later wipe?
jusplainmike, I would assume so. Something to keep in mind.
Would a nand be better?
sonikamd said:
I'm doing this on IonR2, your system apps may be elsewhere, mine are located in /system/app, you'll need to know where they are for this to work.
Click to expand...
Click to collapse
(10c)
perhaps, depends on what you want I suppose. I wipe clean every so often just to get a fresh start, speed things back up etc. Sometimes while installing themes I wipe multiple times and also just want a clean slate.
This is definitely not the way to go for a complete backup-restore. Just seems a good way to reinstall a few missing by stock apps after a wipe.
lol soulife i know, i know
I believe apps2sd is the best bet for keeping apps after a wipe or fresh install.
retort
sonikamd said:
lol soulife i know, i know
Click to expand...
Click to collapse
The only reason is because you push a market app to internal memory it read only. If there's an update you have to open terminal or adb and rm and push the update back. Plus if you flash a new update it will wipe them out. With a2sd however you can update them no hastle, and even if you flash a new build, with a2sd the reinstall themself. Much more convient as long as you smart with your partitioning.
I think you guys may be doing this the hard way. If you are wiping and moving to a compatible ROM, just leave the sd card as it is and the new ROM should be able to find and install the apps as long as it has apps2sd built in.
If you are moving to an incompatible ROM you will have to remove old sd app directory first.
rm -r /system/sd/app
then you should be able to just copy over your entire apk backup directory to your sdcard as follows.
cp- a /sdcard/yourdirectoryname /system/sd/app
and if you are installing a ROM that has app2sd built in, it should find all the apps and install them.
If the ROM you use does not have apps to sd, then you will be able to use Lucid script to move apps from phone to sd card app directory (with already copied apps) and link directory
Tru, I just don't use apps2sd. My sd is constantly getting mangled for one reason or another..
uh, by doing this you're filling up your /system folder which actually needs memory to improve. and you can uninstall them by
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm/system/app/nameof.apk
on another note wouldnt wiping while having info in the system ; wipe?
anyways

[ROM] Zen-RCMix22 Beta

BETA IS CLOSED FOR NOW.
This is a beta. I haven't tested it except for booting and making sure the hardware works.
It is based on the latest RCMix22 from capychimp and robocik.
http://forum.xda-developers.com/showthread.php?t=702398
Wipe everything before flashing.
If you have problems with sleep then install ZenKernel from the link in my signature.
This is a gsm Rom so you can't do prl updates and this doesn't have sprint vvm.
Post what ever thoughts you have.
Woot, can't wait to try this!
Sent from my HERO200 using XDA App
this looks interesting.
if i gather correctly, this is a froyo sense rom?
Im having issues downloading the zip is there a mirror?
Sent from my HERO200 using Tapatalk
11% can't wait. Dl straight to phone.
Edit....54% come on already!
Sent from my HERO200 using XDA App
niiice.thanks for this! downloading now
Downloading. Will do some testing tonight. Thanks Zen.
Wow, nice job zen .... ditched sense for CM 6 but u might have just brought me back
Nice job Zen... Been running this for about 30 mins. now and not having any issues yet. Question though, can we use any of the Extras for RCMix22?
stuck on the android boot screen....i think its looping?
edit: wiped everything again,including ext this time.will report in a few
johndoehizzle said:
stuck on the android boot screen....i think its looping?
Click to expand...
Click to collapse
Ya I got it to boot up but then got FC of something BG, so I rebooted and now boot loop on android screen aswell. Gonne redo everything again.
kingdazy said:
this looks interesting.
if i gather correctly, this is a froyo sense rom?
Click to expand...
Click to collapse
" [ROM][Sense 2.1][18 Sep]RCMix 2.2b"
Nope not Froyo
Testing time
kingdazy said:
this looks interesting.
if i gather correctly, this is a froyo sense rom?
Click to expand...
Click to collapse
I wish !!!!
I have been waiting for this lol didn't want to violate one of his rules though. DL now!
Edit:Taking a while to download
Edit:Got it to download, booted up, everything looks ok right now. What clock speed is this at right now, 691?
kk..so fa so good...just real quick,what r the differences with this rom n others?..compared to ZenRom?
kingdazy said:
this looks interesting.
if i gather correctly, this is a froyo sense rom?
Click to expand...
Click to collapse
No, I don't think it is, just another port of a better 2.1 sense rom.
10 min into install and initial setup...
1) What's TWLauncher? The Homescren Selector is nice, especially since it's functional....will have to install ADW and LPP to see if they show up as selectable. But I hadn't heard of TWLauncher before....so far, seems nice and plays well w/ the ROM.
2) I noticed my Build # shows NFX-Hero2.2.1, which is odd since I just wiped/flashed from CM6, and haven't used NFX since a day before THAT flash. The kernel version seems to have updated though. What's everyone else showing as build number?
pwrmedia said:
10 min into install and initial setup...
1) What's TWLauncher? The Homescren Selector is nice, especially since it's functional....will have to install ADW and LPP to see if they show up as selectable. But I hadn't heard of TWLauncher before....so far, seems nice and plays well w/ the ROM.
2) I noticed my Build # shows NFX-Hero2.2.1, which is odd since I just wiped/flashed from CM6, and haven't used NFX since a day before THAT flash. The kernel version seems to have updated though. What's everyone else showing as build number?
Click to expand...
Click to collapse
It's the same build.prop as nfx. It was the only one I had that was Sprint based.
Twlauncher is the touchwiz launcher.
Sent from my HERO200 using XDA App
Nice and snappy here! One issue found with apps2sd - it appears that it won't allow for the Dalvik Cache to be setup in the cachepart. I get an error on 'a2sd check':
Dalvik Cache - [ ] Regular directory.
[ ] File .dalvikcachepart found.
[X] Dalvik runs from Int. Storage.
Setup Issue. Run a2sd repair to fix.
and then on 'a2sd repair' I get:
Dalvik Cache - [-] Regular directory.
[-] File .dalvikcachepart found.
[X] Dalvik runs from Int. Storage.
rm: cannot remove '/data/dalvik-cache': Device or resource busy
[*] Issue repaired.
But on 'a2sd check' it still shows the same error message, as above, etc.
And no other mods | kernels | OC/UV changes, etc., added at this point. Will flash the latest Darktremor A2SD to see if that helps any ...
Latest Darktremor A2SD (2.7.5 Final) was no help, hangs at 'ANDROID' boot screen.
Wiped everything then flashed ROM and then flashed 2.7.5 Final, then rebooted. System came up with Dalvik Cache set to internal. Set Dalvik Cache to SD cache partition and system auto-rebooted. On startup lots of FC's so I booted into recovery, wiped Dalvik Cache, and rebooted and system came up with lots of FC's again - I suppose the ROM just doesn't want to see the Dalvik Cache in the SD cache partition!
But then, placing the Dalvik Cache on the SD card but not in the cache partition does seem to work fine ...

Valhalla Black Issue Fix

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...

[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.

Categories

Resources