Related
Has anyone else noticed leftover apps or info from your previous ROM that should not be in your current ROM? I am noticing this after the GB leak and the GB leaked based ROMs.
This is my process whenever I flash a ROM.
Boot into hboot and flash radio if neccessary.
Boot existing ROM and remove radio file from root of SD card.
Boot into recovery and clear data/factory reset. Wipe cache. Wipe Dalvik. Wipe battery stats. Fix permissions.
Flash ROM in recovery.
Flash kernel in recovery if neccessary.
(I don't use any type of app backup like Titanium or something like that. I just don't mind putting my apps back on because I don't have much to begin with.)
Now some examples, I flashed Teslacoil which I was running for about a week. It has a file manger app that I did not download. Then I flashed dhemke17's plain debloated GB ROM. The File Manager app remained in there which I thought was a little weird because he didn't say he was going to include it but I didn't pay much attention to it.
Then I flashed jcases GB ROM and played with it a little and noticed I couldn't lock GPS for the weather clock. Flashed back to dhemke's ROM and couldn't get a lock with the clock either but the first time it locked fine.
It seems like to me when flashing between other chef's roms it may be carrying over apps and/or info. This might be why we have been seeing extremes from both sides of some have been having great experiences and others it doesn't work for them at all.
Maybe flashing back to stock first before flashing to a new rom may he in order, I know we had to do that with some of the old skool winmo phones (remember those days?).
Anyhow, has anyone noticed these types of instances. Those of you who may be flashing to another's rom try to take notice and see if anything carries over.
Thanks gang!
And just to be sure, I do a wipe everytime I flash someone else's ROM.
Sent from my ADR6400L using Tapatalk
This also might be why some devs have been seeing their work in others Roms without being given credit.
Just guessing on this one.
Sent from my DROID PRO using Tapatalk
I also noticed, I don't like Sense so I normally change some of files to get a Sense-reduced experience from the GB Roms since we don't have a Senseless GB rom yet. I use Root Explorer to change the extension to .bak, when flashing the rom and doing this process for the new rom it would have the new file and still have the .bak file. So it would have like a Rosie.APK file and a Rosie.APK.bak file.
Sent from my DROID PRO using Tapatalk
I've also noticed something similar.. I also wipe on every install even updates to the rom i'm currently running. What I noticed is that after about five to ten minutes the wallpaper will change back to a custom one that I have saved on my sd card. Also when I turn on wifi it still remembers my password and connects to my network. to me if it isn't wiping these things it may not be wiping things that will conflict with any changes to my rom.
Now what I do is wipe data factory reset 3x, wipe cache, wipe davlick 2x, wipe battery stats ..thats clears out the issue I explained above.
To my knowledge that is just the built in restore Froyo has. You probably click to allow Google to store/backup your apps on setup, right?
Built in restore or you are not wiping.
Devs are seeing their work elsewhere because "devs" are asses.
Sent from my LG Revolution
jcase said:
Built in restore or you are not wiping.
Devs are seeing their work elsewhere because "devs" are asses.
Sent from my LG Revolution
Click to expand...
Click to collapse
OK so why am I seeing the .bak files when I change roms? It only does it from the rom right before it. Like I said I flashed from Tesla to dhemke and it had the file manager app. Then I flashed to your rom this was your first GB leak. It did not have the file manager but the weatherclock was not finding my current location. I flashed back to dhemke and this time there was no file manager app and weatherclock would not find current location. Flashed back to Tesla then back again to your rom jcase because you updated yours and file manager was there and weatherclock locked.
If the devs are being asses that's fine I was just throwing that out there, but I am sure our phones are not complete wiping when going from gb rom to gb rom. Like I said I wipe everything everytime because I don't have much crap to begin with and I am used to reinstalling my crap from the winmo days.
Try to flash and see if anything carries over.
And the wallpaper and wifi settings like others suggested is from your g account.
Sent from my ADR6400L using Tapatalk
This happens when you don't wipe and clear cache
Sent from my ADR6400L using XDA Premium App
Well I do wipe everything before each install via recovery. Read the first post for exact steps I take when flashing. When it boots it seems fresh, I have to resync my gmail account, download and install market apps, reinstall my apps that I sideload via sd card, etc. Just the apps that are in the core rom like in the system/apps folder are still there. I was just on chingys gingeritis version IV then flashed and wiped to version VI. On version IV I changed a few files to add .bak extension to get a senseless version like the Rosie.apk. After I flashed to version VI I went into system/apps and the .bak files were still there.
Again to my knowledge this is only happening with GB based roms. If I am wiping the wrong way please let me know that is why I posted my steps in the first post but that is how I wiped and flashed this whole time. The only thing I can think of is wiping, flash the rom, then wipe again. Or wipe via the settings menus.
Before someone flashes, could they try editing a core app in the system/apps folder with a .bak extension. Then wipe and install your ROM, and see if that .bak file is still there? Thank you.
Sent from my ADR6400L using Tapatalk
From looking at the updater-script file of the rom I flashed (1.13.605.7 Debloat/Deodex), it does a rm -rf /system
If your rom's updater-script file does not do that, then you should contact the head dev and ask them to add it in.
If it does have that, then there is definitely something going wrong to cause files to be left behind since that command is literally, "force recursive remove /system"
JM2c
P.S. BTW, wiping does not erase anything in /system. A rom that includes a file manager will have it in /system.
So the rom you flashed after the one with the file manager didn't erase /system before flashing its changes..
So I've read on different ways to boot into CWM then flash to the Krylon fix, but the way I (have) to do it is completely different; First, hit ROM manager then boot into recovery. From there, I cannot click the update from zip option - I get an error and it fails - instead, I go to mounts and storage. Instead of the regular options, my only option is Mount USB Storage. I click that and after some script that I never read, my phone freezes. After the holding the power button to restart, it boots me into the CWM fix that I need to be in in order to flash my ROMs. - Why does it do this?
Also, every time I flash a different ROM, I use a nandroid backup. Recently I almost restored data on an old backup I had from a month ago. How do I delete the old backups that I don't need?
Jabrutal said:
So I've read on different ways to boot into CWM then flash to the Krylon fix, but the way I (have) to do it is completely different; First, hit ROM manager then boot into recovery. From there, I cannot click the update from zip option - I get an error and it fails - instead, I go to mounts and storage. Instead of the regular options, my only option is Mount USB Storage. I click that and after some script that I never read, my phone freezes. After the holding the power button to restart, it boots me into the CWM fix that I need to be in in order to flash my ROMs. - Why does it do this?
Also, every time I flash a different ROM, I use a nandroid backup. Recently I almost restored data on an old backup I had from a month ago. How do I delete the old backups that I don't need?
Click to expand...
Click to collapse
to delete old backup you need to do it manually from the computer when your phone is mounted its in the folder clockworkmod/backups. or delete it from a file manager while on your phone. and what krylon fix are you trying to flash ? are you on stock ?
its the CWM3XX.zip file that I need to get to before flashing ROMs. I can get to it fine, its just that I use a different method of getting there than instructed in the dev threads. I'm running your gingerclone rom. and thanks for the backup advice.
Sent from my SGH-T839 using XDA App
Jabrutal said:
its the CWM3XX.zip file that I need to get to before flashing ROMs. I can get to it fine, its just that I use a different method of getting there than instructed in the dev threads. I'm running your gingerclone rom. and thanks for the backup advice.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
what is the Method your using ?
said method above - flash to cwm, go to mounts ->mount USB (this is my only option) -> frozen screen -> restart ->and when i restart it boots to the krylon fix
That CWMxxx.zip should be update.zip, just checking to make sure you did that. try my updater script, http://forum.xda-developers.com/showpost.php?p=15831175&postcount=124
it will add the modded recovery binary and push krylon's good update.zip, and reboot you into recovery.
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...
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
Barebone SGS4G KJ6 ROM
Use at your own risk, I take no responsibility for anything that may happen to your phone because of this ROM.
Here is a ROM that I made for myself, but what the heck, let's share. This ROM is very stock-like with just few usability mods.
Features
Will not wipe your programs or data, /data is preserved upon install
Heavily debloated. Most essentials apps are still there (like WiFi Calling)
No extra programs added, you need to add your own
ODEXed to save space in /data
CarrierIQ is completely removed
Extended Power Menu (including Screenshot)
Extended Quick Panel (10 buttons, including Data toggle)
1% battery (horizontal)
CRT-Off
Time zone version 2012b
/etc/hosts to cut ads out of the box (keep up to date with AdAway or similar)
Few conservative presets in build.prop and init.d
Basic with a Twist 1.1.3 kernel included
Notes
* Don't get confused about ODEXing, it's actually better to run and saves quite a bit of space in /data.
* Some Google apps (Maps, Streets, Voice) and Adobe Flash are removed from /system. Install them from market. Benefit - they can be moved to SD card this way.
* Original Swype is removed, is somebody needs it flash this.
* In case you need it, use this thread to add some bloat back.
* Factory Reset is removed from Settings->Privacy, use CWM if you ever need to reset all data.
* KJ6 modem included. Use this thread to flash a different modem if needed.
Install
Flash with CWM. Wait until the system boots up, then wait few more minutes for it to settle.
Download
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.8
Changelog
1.1.3
Removed "Mobile data connection disabled. Connect?" popup on boot
1.1.2
Removed Factory Reset from Settings->Privacy
Updated kernel
1.1.1
Fixed voicemail notifications not working without Visual Voice Mail installed
1.1.0
CIQ is properly removed
Some neutral cosmetics (logo, animations)
Minor update to the kernel
1.0.8
Fixed slow stock browser scrolling
1.0.7
Extended Quick Panel
1.0.6
Added Screenshot to power menu
1.0.5
Removed DriveSmart and Software Update from Settings menu
1.0.4
Put original framework-res.apk certificate back
1.0.3
Added power menu mod
1.0.2
Original public release
does it have a screenshot option from the power menu??
m0bstr said:
does it have a screenshot option from the power menu??
Click to expand...
Click to collapse
Nope, never bothered with power menu. I don't reboot the phone too often and to say the truth don't even remember when last time I needed to take a screenshot. I use ShootMe and QuickBoot when I need to, they both do the job just fine.
Yes, power menu is fully modded now, including Screenshot option.
Thank you for this, Anton! Love your kernel. Is this ROM ok for OC/UVing with you OC/UV kernel? I think this will be the second ROM I have ever installed. Haven't bothered to try anything since first getting Val Final.
Download link is not working
Sent from my SGH-T959V using XDA
Does this come pre-rooted?
Blaggah said:
Does this come pre-rooted?
Click to expand...
Click to collapse
Yeppers it does.
I updated the link. I actually took it down on purpose, wanted to look at something but never had time.
I was troubleshooting an error message during boot time, so I traced it to the CIQ trying to execute some on-boot code, which was removed by Krylon. Strangely the original code itself doesn't do much, it's initilizing a broadcast receiver with an empty onReceive method. Removing this was a moot point, it probably didn't do much. I disabled the BOOT_COMPLETED permission for the service to avoid the error message.
So I looked at the CIQ more closely. What I found is a little peculiar. The main CIQ code is integrated quite deeply into the framework, it cannot be removed easily, there are just too many calls that send various metrics to the CIQ Agent. The main CIQ classes are not in the framework.jar, they are in ext.jar. Probably that's why nobody noticed them and never tried to modify them. What is strange that many calls seem to be not implemented. For example the sumbitMetric is an empty method, shouldSubmitMetric always returns zero, etc.
It's possible that T-Mobile decided not to use CIQ on our phone (at least extensively), but instead of removing it completely just plugged few calls.
I'm removing the "CIQ removed" description because it's actually not removed, although may not be doing much.
I cannot get it to boot. After the "Galaxy S 4G" screen, the screen goes back then nothing ever happens. I rebooted into CWM (which still shows Team Acid's logo) and tried fixing permissions to no avail.
Given that the OP says it won't wipe programs, data, etc, was it possibly a Bad Idea™ to have wiped everything before installing this ROM?
Update:
Indeed, installing from a blank phone (literally, I wiped everything) didn't work for me. I flashed Bryan's one-click with CWM, it booted, rebooted into recovery, flashed this, and it booted. Now for testing. Thanks, Anton!
I had the same issue as well... Thought it was just my phone
Sent from my SGH-T959V using xda premium
Would be interesting to look at the logcat to see where it's stuck.
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
wont flash
I wipe everything, the ROM installs, and then black screen...noting. Let it sit for 20min however this did not resolve issue. I was able to install Valhalla no prob. flashed your rom on top of Valhalla and then my phone boots your rom. Do i need to install on top of another rom? I should just be able to whipe my phone and install your rom correct?
AntonX said:
Would be interesting to look at the logcat to see where it's stuck.
Click to expand...
Click to collapse
I can probably capture that because I can use adb to get into the OS. I ran top to see what, if anything, was hogging CPU but there was nothing obvious & CPU usage was minimal. I have the phone running now but I'm willing to wipe it again and re-flash. Mind you, I did more than factory reset. I was quite literally trying to start from scratch, so here's what I did (if this helps at all):
Backed up /efs to my PC
Backed up the SD card to my PC
Wiped cache
Wiped Davlik cache
Wiped battery stats
Performed a nandroid backup
Copied the backup from /sdcard/clockworkmod/backup to my PC
Formatted /data, /system, & /sdcard
Rebooted back into recovery
Copied the ROM to the SD card
Flashed it
Let it cook for ~20 minutes
So it was quite literally a blank slate.
AntonX said:
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
Click to expand...
Click to collapse
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
stephen_w said:
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
Click to expand...
Click to collapse
Wow, you really wiped everything from your phone
I'd appreciate if you send me the log. All you need to do is to save the file with "adb logcat -d >MyLogFile.log" after couple of minutes of this black screen. On an factory reset phone ODEXed ROM should boot very fast the first time because it doesn't have to build Dalvik.
I just tried downloading from my own link and reinstalling, everything seems OK. I also tried installing after full phone reset yesterday, it went fine too. I don't want to reset and restore everything anymore, too lazy
If it proves to be the certificate in the framework-res.apk, I may need to put the original AndroidManifest.xml back.
Hey Anton,
You can snag the logcat from here. In case anyone wants them & to clarify what I did, here are the steps I followed (similar to above but more detailed):
- Boot into CWM
adb reboot recovery- Disable voodoo lagfix
- voodoo lagfix- disable lagfix- /system lagfix off- Reboot
- Create a backup directory structure on your PC (mine is in C:\Users\username\Downloads\SGS4G)
mkdir backupscd backupsmkdir efs nandroid sdcard- Backup /efs to your PC
cd efsadb pull /efs/- Backup /sdcard to your PC
cd ..\sdcardadb pull /sdcard/- Boot into CWM
adb reboot recovery- Wipe cache
- wipe cache partition- Wipe Dalvik cache
- advanced- Wipe Dalvik Cache- Wipe battery stats
- Wipe Battery Stats- Create a nandroid backup
- +++++Go Back+++++- backup and restore- backup- Copy the backup to your PC
cd ..\nandroidadb pull /sdcard/clockworkmod/backup/- Format /data
- mounts and storage- format /data- Format /sdcard
- format /sdcard- Format /system
- format /system- Reboot into CWM (necessary for CWM to see the sdcard contents)
- +++++Go Back+++++- advanced- Reboot Recovery- Copy the ROM to the sdcard (this is from the directory in which the ROM is located on your PC)
adb push ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip /sdcard/- Flash the ROM
- install zip from sdcard- choose zip from sdcard- ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip- Reboot & let it sit for ~10 minutes
Sorry for the lengthy post, but I wanted to ensure there was transparency in what I did.
stephen_w,
Seems that it's not framework-res.apk issue, it's not complaining about any certificates.
A lot of unknown permissions in the log, but it's OK, we've removed some of the system packages that grant those permissions but they do more harm than good in the end.
The crash has something to do with that: *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService. Hm......
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Weird...it flashed fine for me with no wipe....
I did move on and never gave it a break in....but it did work
Sent from my SGH-T959V using xda premium
AntonX said:
stephen_w,
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Click to expand...
Click to collapse
I usually don't do it that extensively at all. I was writing a process for myself in case I wanted to really clean it out So this gave me a good excuse to test it. I was having some weirdness which prompted me to write the instructions for myself.
I haven't tried shutting it down after the install. I can certainly try that for you, if you like.
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Sent from my SGH-T959V using xda premium
Lawful123 said:
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Click to expand...
Click to collapse
Doubtful. Nothing I can think of, off-hand. I have to wait until later this afternoon/evening to reflash it and try powering off vs. rebooting from recovery. If you have the chance, please feel free and let us know what happens.