Related
OK guys, My solution to the reboot data corruption is to install an ODEX version. I figured out that the DALVIk-CACHE was the main culprit, thus with an odexed version there are less data written to the DALVIK-CACHE.
USE l1q1d's latest 11/29 kernel.
This is my latest build BETA 3 protection. I have made changes on the way partitions are mounted, extra mount options added to /data to decrease writes and more speed. All apps in data are automatically odexed and a few apps in system folder is odexed. Wifi tether, skyfire, estrong file explorer etc were moved to system to provide more space in data partition for odexing apps. Few files in the build are replaced.
BETA3
http://www.4shared.com/file/yDdKUQcL/androidinstall_8.html
HOW TO INSTALL:
1. Clear Dalvik-cache and repair permssions
2. Install androindinstall.tgz
3. Install all your apps, MAKE SURE YOU INSTALL TERMINAL EMULATOR
4. Open Terminal Emulator and type:
su
sh /system/bin/odex.sh (This will odex your apps without rebooting)
Wait till it is finish.
5. Reboot
6. Make sure you press the D-Pad while reboot to enter LAUNCHER
7. Clear-Dalvik cache
THAT"S IT Hope this helps and let me know how it goes.
-------------------------------------------------------------------------------
------------------------------------------------------------------------------
Beta2 (depreciated)
http://www.4shared.com/file/p0BrSQVK/androidinstall_7.html
----------------------------------------------------------------------------------------
Beta1
http://www.4shared.com/file/lvONbK35/androidinstallodex.html
ENG/Spanish Only.
*** DO NOT DO A RESTORE of APPS, INITIAL FRESH INSTALLATION OF APPS IS REQUIRED ***
Rename to androidinstall.tgz and install system/data on NAND
Requirements and tips:
1. LATEST 11-27 kernel by l1q1d 2.6.32
2. Install system and data on NAND only
3. Radio 1.65 - 1.70 (reported issues with 1.71 have been noted but not verified)
4. Overclock and Reboots should be done within reason
5. If you press the power button and it seems like it is not responding, It's on Fake Vsync mode. Open keyboard and press FN+Left Soft button, then FN+ Right Soft button and it should wake it up.
BTW, if you were having any issues with my Final Release, it would be the same issues with this build. This is basically just an ODEX'd Version of my Eng/Spanish ROM
Bring it on !! I spent all of my sunday getting my TyTn2 to work on your builds....lets hope this one will be The One !
Much appreciated !
btw: do I need to make an install-sq with atools? with what settings ????
Goldfingerz said:
Bring it on !! I spent all of my sunday getting my TyTn2 to work on your builds....lets hope this one will be The One !
Much appreciated !
btw: do I need to make an install-sq with atools? with what settings ????
Click to expand...
Click to collapse
Let me know specs for your tilt and I'll upload one after I upload the rom..eg. Keyboard type, Screen type, battery...BTW, are u using 1.70 radio now?
PM me the data and I'll PM you of the link
clemsyn said:
Let me know specs for your tilt and I'll upload one after I upload the rom..eg. Keyboard type, Screen type, battery...BTW, are u using 1.70 radio now?
PM me the data and I'll PM you of the link
Click to expand...
Click to collapse
okay, done !...thanks !
Goldfingerz said:
okay, done !...thanks !
Click to expand...
Click to collapse
Check ur PM, I need more info
currently my kaiser is running your build, but i haven't done a reboot yet.
what could happen if i do it?
vaupunkt said:
currently my kaiser is running your build, but i haven't done a reboot yet.
what could happen if i do it?
Click to expand...
Click to collapse
A chance of data corruption since it is deodexed and would have more data written in dalvik-cache. Simply clearing out the dalvik cache and fixing permissions should help. With an Odexed build, there are less data written in dalvik cache coz the data is with the odex files.
thank you!
is there a way, to install it as an update?
so that it won't delete everything?
just rename it to "androidupdate" instead of "androidinstall"?
vaupunkt said:
thank you!
is there a way, to install it as an update?
so that it won't delete everything?
just rename it to "androidupdate" instead of "androidinstall"?
Click to expand...
Click to collapse
Sorry, I don't think there is a way to make an androidupdate, the whole odex build is different in a way..
Gonna take it for a spin right now
Gonna give it a shot right now, send u my impressions later, thkns in advance
Update
OK, did my igo GPS to go to McDonalds, did some browsing at McDo then went home played some music, pulled out the battery while playing music...STILL NO loop, FC or lost app...so far so good. If this is OK for 24 hrs, I'll take off the beta label.
could you please also update the corresponding one for installation on system/NAND and data/SD?
I tried the version of system/NAND and data/SD with the latest the kernel. it crashed and rebooted many times.
cqf20022002 said:
could you please also update the corresponding one for installation on system/NAND and data/SD?
I tried the version of system/NAND and data/SD with the latest the kernel. it crashed and rebooted many times.
Click to expand...
Click to collapse
I don't think this odex will work with SD coz I haven't tried it. I suggest you try to Final release instead of this odexed beta for NAND installation. The main purpose of this release is to attempt to fix data corruption on NAND installation (which so far this odex version has done for me at the moment).
Update:
Pulled the battery out and reboot was OK. Ate dinner with the family. Went back and was stuck on white screen. Was on massive Fake Vsync so I pulled the battery out and restarted. Looks good except my Launcher had no app (black blank), it might have been loading but I pulled the battery out again....Turned it on and everything is back as it should, no FC no rpc loop, every app back in launcher. Still looks good.
Hey clem I'm testing ur SD build with latest l1qu1d's kernel (11-27) its rock solid but kinda sluggish... how's ur new build in speed? I mean, its odexed.. that's a pro, but I have my doubts bout having cache on the SD (look at my sig, I'm using a class 2 SDHC) could it be compared to a NAND or its more lika a SD installation?
Sent from my Kaiser.
clemsyn said:
Update:
Pulled the battery out and reboot was OK. Ate dinner with the family. Went back and was stuck on white screen. Was on massive Fake Vsync so I pulled the battery out and restarted. Looks good except my Launcher had no app (black blank), it might have been loading but I pulled the battery out again....Turned it on and everything is back as it should, no FC no rpc loop, every app back in launcher. Still looks good.
Click to expand...
Click to collapse
Didn't realized I overclocked at 570...will drop it to 475 but so far no reinstallation required.
albertorodast2007 said:
Hey clem I'm testing ur SD build with latest l1qu1d's kernel (11-27) its rock solid but kinda sluggish... how's ur new build in speed? I mean, its odexed.. that's a pro, but I have my doubts bout having cache on the SD (look at my sig, I'm using a class 2 SDHC) could it be compared to a NAND or its more lika a SD installation?
Sent from my Kaiser.
Click to expand...
Click to collapse
Yeh, class 2 is pretty slow so that is your slow down. I would you ask you try this odexed build for NAND installation on both system and data. So far so good for my testing.
So far, so good
well beem triying this for like 2 hours and got to say its neraly perfect, i´ve rebooted 3 times now and everything is working perfectly
i put on the NBH the following config:
Kaiser, panel type 2, 240X320, froyo, tilt,and overcloked to 470 and is working woderful with wifi, many widgets, and a lot of apps installed about 12, have not triying data and oo i almost forgot, im using latest l1qu1d kernel 27-11
mizad09 said:
well beem triying this for like 2 hours and got to say its neraly perfect, i´ve rebooted 3 times now and everything is working perfectly
i put on the NBH the following config:
Kaiser, panel type 2, 240X320, froyo, tilt,and overcloked to 470 and is working woderful with wifi, many widgets, and a lot of apps installed about 12, have not triying data and oo i almost forgot, im using latest l1qu1d kernel 27-11
Click to expand...
Click to collapse
Thanks for trying it I think we really got it this time. I was driving with Igo Running, asked my wife to pull out the battery while Igo was running (this usually gives me errors and requires reinstallation) and locked on a signal. Then turned it back on...no errors, no loops, all apps still in my Launcher.
I will build an all language after 24 hrs of testing this.
Hey Clemsyn! Thanks for this build, I'm testing right now. So far so good. Turned off, turned on. Pulled battery, Still working.
Now I have a question, Way before, when I used Vanilj Eclair, I never had any problems with data corruption. I used the build for like 3 months before I decided it was time to upgrade to a more Up-to-date Android Build for my Kaiser. My main point is, Why is it just now that there are problems with Data corruption??? Thanks!
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
(irc help would be awesome still since I now have some help with main issue- I enter all the correct info into the app but it shows nothin. I've tried several to no avail. I appreciate the help) second I've ran into more pretentious ppl in these forums for Android then others no offense to the good guys but just my exp. It was brash to say that in this post tho. Thank you guys again for the ones willing.
That's because even the biggest idiot can work an iphone.
Jataadroid said:
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
Click to expand...
Click to collapse
Jataadroid said:
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Click to expand...
Click to collapse
Patience dude. I didn't catch it, but what exact kernel are you using, net has a lot of em, the one in the OP of myn's thread you mean? What recovery(and version of that recovery, some versions of clockwork floating around that have some bugs i think) did you use to flash the rom? what radio version and pri version do you currently have installed? Which ROM were you coming from, and did you do a full wipe(data, cache, davlik cache) before flashing it? I have never experienced anything like you are describing whilst using Myn's, his ROMs have been solid. Give a little more info and surely we can help you get running smoothly again.
thanks for the reply heres the details...myn's rls5, net toast havs more, ra_superson
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Looks like we're running nearly the same setup, minus my ra_supersonic 2.2.1 recovery. I have attempted the stock kernel furnished in the Rom zip but since it didn't offer overclock I switched to net havs more smartass. I do the dalvik and cache wipe each time.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
Not trying to be a smart ass but do you realize that by insulting us will not get you any help? Rhetorical question
From reading what you jus stated the obvious problem is you did not do a FULL WIPE as you should do when flashing between roms.
Also next time please be patient as those like myself who browse through this section to help impatient ppl like your self, do actually have a life outside of xda. Its been a big snow storm in the southeast so most like myself included are outside enjoying the snow!
DO A FULL WIPE THEN REPORT BACK!
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
gotta do a full wipe if you are switching between roms
Sent from my PC36100 using XDA App
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Ok. Well crap.... thanks guys since that is apparently my only option.
OneStepAhead said:
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The kernel was included in the op and I've seen tags with same setup as mine.
Jataadroid said:
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
Click to expand...
Click to collapse
Sorry you feel that way but since i have had the hero, on every thread about a rom says wipe all! This must be a joke for someone as rude as yourself to come on here and disrespect those who are trying to help.
Next time you decide to flash a rom remember to do a full wipe because inside the data partition is files for the particular rom, if you dont wipe, the new files will just over lay but not delete the old one. This will cause conflicting issues within the files as the phone tries to do both at the same time.
Screen tearing and the "jigglies" as I like to call it have always come from kernels - in my experience. And just because someone might have the same set up as you, the way it affects your phone ccan be quite different as you are running different apps, different settings, etc.
First thing I would do if I were you is to freeze any kernel govenor you are using - no setcpu, no secreen off profile, no set on boot, no os monitor govenor, no nothing like that. You don't want want any of that going on when you flash a new rom or kernel.
I know you don't want to do a full data wipe so let's see if we cna get you going without that. I used to HATE doing data wipes, I don't mind so much now because I've learned that trobule shooting can frequently take longer than just doing a data wipe.
I would say #1 make sure you are using AMON RA. Power button-reboot-recovery. Wipe cache at least twice, wipe dalvik at least twice. Now JUST flash the rom (you've already said your radios are updated so you wont have a problem with this). Let the phone boot up and give it time to settle in. You wont have any screan tearing. Now you're running a completely stock Myn's rls5 rom. Check some stuff out, make sure your basic settings are good, make sure your 4g is not scanning, etc.
Make a nandroid of this and keep it.
Now start making changes if you'd like. Flash a different font, flash a different kernel, etc. But leave all the governors OFF until you have a kernel that you KNOW will run ok on your phone. For example - I can run 2 of ziggy's kernels but the others don't work for me. I can run a few of net's kernels, but many don't work for me.
So my basic suggestion is to make sure you get a stable, stock Myn's rls5 on your phone before you mod it. If you can't get that, then yes - you might want to wipe data. Doing a batch backup in Titanium is really easy and it makes restoring very easy as well. It's our own customizing that is time consuming because we are all probably very picky (and proud!) of our beautiful phones.
Thanks for the helpful info from ALL that posted. I understand the risk of the non entire wipe, nandroid is safe of original stock Rom but not of new one. After tinkering with setcpu I've gotten more consistent stability. I know I will reflash with an entire data wipe here soon to see results. Running ra_supersonic 2.2.1 recovery.
I've made list of check point when I test some new Roms and kernels. I have some more question on backing up user info from backed up apps but Im sure ill find it on here.
Now that my system is stable for the time being, some one mind help me setup irc? And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it. Ra_supersonic 2.2.1 recovery i like also.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
You're welcome. I am late at getting back to this post, but yea. Definitely. As everyone else has suggested, you have to do a full wipe when changing ROMS. Only time you could get away with just wiping davlik cache and cache is when upgrading the same rom ( like from rls 3 to rls 4, and rls to rls 5), but even then, it doesn't always work. Full wipe is always recommended. I would also recommend downloading your apps one at a time from the market, and adding your mods one at a time, make sure everything is stable after each flash. Good luck.
QUOTE And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it QUOTE
If your phone is the newer hardware (late 003 or 004), you can only use the stock kernel, or a kernel based off stock for the camera to work. That would be htc #15. I believe Net's 4.3 kernels are based off of that. I am also pretty sure that Net explains that in his kernel thread in the development section.
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
r.storm85 said:
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
Click to expand...
Click to collapse
This isn't true, the problem is ALWAYS the kernel. I'm running myn rls5 and mikfroyo 4.3 with an SBC #15 v7 kernel (i'll edit post and add the link) and I have had zero issues except I can't download MMS messages on 4g on mikfroyo.
Jataadroid said:
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Click to expand...
Click to collapse
Okay, this process will 100% work. It's the one I've been using since my lowly mytouch slide oh so many months ago.
*before you do this, make sure you have backups of your nandroid and your rsa keys. I'll edit post and give you links on how to back up your rsa keys*
RSA Key back-up: http://forum.xda-developers.com/showthread.php?t=887900 ...since you're rooted you can go straight to the part where it says "if you're rooted do this.."
1. First you need to fix the sd card. Create a folder on your computer desktop and call it "my sd card". Plug your phone into the computer and select "disk drive". Next you're going to copy EVERYTHING from the sd card and place it in the folder on the desktop (and dude I mean everything! AS IS, DON'T CHANGE ANY NAMES). Then, you're going to unhook your phone, go to settings>sd and phone storage. Then you're going to format your sd card. Yes, do it, but make sure you have EVERYTHING backed up first. After that's done, plug your phone back in, select disk drive and copy everything from your "my sd card" folder on your computer and put it back onto your sd card.
*phew*
Okay now that the sd problem is fixed, here's how you fix the rest. You see, when you upgrade your PRI to 1.90 and your radio, etc etc you gotta update the kernel to a version that's 1.90 supported. I'll edit post and post a link to where you can find one OR you can just use the kernel that's included with myn's rom because it WILL WORK. *edit* the kernel I'm using has been taken down because of the witch hunt against SBC kernels. So for now, just stick with stock. It works just fine.
Anyway.
Steps to getting myn working perfectly.
*before starting, re-download myn rls5 in case the screen flickering was caused by a corrupted download*
1. Download Titanium Back-up from the market. Back up all the apps you want to keep (basically, anything you downloaded from the market as you'll get facebook, sense widgets, etc back). You can do this while you re-download the rom.
2. Make a nandroid back-up in case something goes seriously wrong. A rom that flickers your screen is better than a brick.
3. Once that back-up is done, reboot into recovery. Once there, you're going to WIPE EVERYTHING. Full data, cache and dalvik wipe. Yes, do it. There is no other option.
3. Flash myn's rom. Let it go all the way through. Do NOT flash a new kernel until you've found one that's 3.70 compatible and works with PRI 1.90. Myn rls5 is designed to work with the newest updates (which means a #15 kernel, like the one that came stock).
4. Reboot. If the screen is still flickering, then at this point it's a hardware problem. Flash back to stock, unroot and go get a new one. If it works fine, re-download titanium back-up from the market and restore all your apps. From there it's just putting your widgets back on your home screen.
From here, you can search the forums for a kernel that works with the newest updates. If you read them, they'll tell you what they're compatible with. Remember do NOT use an AOSP kernel with a SENSE rom, that's just spells IDIOCY. Until you find a kernel that works, stick with the one that came with the rom because everyone knows that one works.
I hope this helps. As for the IRC chat, not all the experts are on all the time. If no one is online that can help when you get one, try getting a few hours earlier or a few hours later.
I loaded the syndacite rom about 2 weeks ago and i love it. Yesterday i started gettign this error. "twlauncher has stopped unexpectedly". I try to force close it over and over again and even a reboot doesn't work. I reboot twice and it appears a few times then i'm able to use my phone again. Anyone know what the problem is? I used the syndacite fully loaded rom.
Clear data for the launcher in Settings > Applications.
k0nane said:
Clear data for the launcher in Settings > Applications.
Click to expand...
Click to collapse
I went there but i don't see a clear data option. Can you explain a little bit further to me? thanks!
howufiga said:
I went there but i don't see a clear data option. Can you explain a little bit further to me? thanks!
Click to expand...
Click to collapse
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data
k0nane said:
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data
Click to expand...
Click to collapse
I can't even get to settings. I can only pull down the the menu with the WIFI and GPS settings. any tips on how to get into settings? I keep on getting twlauncher has stopped over and over again.
If you can't open settings, try going into CWM > Advanced, and fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
Actually, just curious. What happens when you try to go into settings? Does the menu come up to enter settings, does it FC when you open?
i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol
howufiga said:
i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol
Click to expand...
Click to collapse
If this happens in the future, hold down the search key and say something to search for, this should take you to the browser. Search for and download launcherpro, zeam, or another launcher you don't already have. After it installs, hit home and choose the new launcher, then you can clear data for touchwiz. This happened to me when I had one homescreen on touchwiz and it was full, and an app tried to automatically add a shortcut.
Sent from my always stock, EC05 Epic 4G
howufiga said:
i couldn't open applications. Everytime I tried in between hitting force close it would just flash then come back and reload over and over again. I had the bright idea of pulling the battery and then it wouldn't boot at all. Had to reflash the ROM. Now need to reinstall all my apps. lol
Click to expand...
Click to collapse
It sounds like a bad reflash though. I've had that, where it FCs so repeatedly that I can't do anything at all. When you have it all set the way you want, make a CWM Nandroid backup, and then restore that backup to turn journaling back on... then battery pulls won't affect you.
You made my day!
zanderman112 said:
If this happens in the future, hold down the search key and say something to search for, this should take you to the browser. Search for and download launcherpro, zeam, or another launcher you don't already have. After it installs, hit home and choose the new launcher, then you can clear data for touchwiz. This happened to me when I had one homescreen on touchwiz and it was full, and an app tried to automatically add a shortcut.
Click to expand...
Click to collapse
What a simple and elegant solution! This error showed up for me last night, and then completely ruined my morning. After searching countless forums and finding nothing but overly technical instructions containing so much jargon I had to search forums to figure out what the instructions meant....I nearly threw my phone up against the wall. Just before I was about to restore to factory settings, I found this thread and these instructions worked PERFECTLY!!! I am not a gadget guy and had a Sanyo Katana that was held together with tape until a month ago, so this solution was right up my alley! I actually registered on this site simply to say thanks. Hopefully the Thanks button will show up after I make this post so I can hit it until my finger blisters.
Props here as well
k0nane said:
Settings > Applications > Manage Applications > TWLauncher (or TouchWiz Launcher, or com.samsung.twlauncher) > Clear Data
Click to expand...
Click to collapse
Thanks to k0nane as well. Once I got LauncherPro to download with zanderman's intructions this helped me clear and reload touchwiz.
LdoFoSho said:
What a simple and elegant solution! This error showed up for me last night, and then completely ruined my morning. After searching countless forums and finding nothing but overly technical instructions containing so much jargon I had to search forums to figure out what the instructions meant....I nearly threw my phone up against the wall. Just before I was about to restore to factory settings, I found this thread and these instructions worked PERFECTLY!!! I am not a gadget guy and had a Sanyo Katana that was held together with tape until a month ago, so this solution was right up my alley! I actually registered on this site simply to say thanks. Hopefully the Thanks button will show up after I make this post so I can hit it until my finger blisters.
Click to expand...
Click to collapse
No problem! I forgot about this.
Please click both links below and vote: http://picketfenceblogs.com/vote/3616
http://apps.facebook.com/gerberphotosearch/entry/935/amber.aspx
Oh God bless you, zanderman112. I thought I was going to have to reset my mom's new phone after I finally finished setting it up and she just started getting used to it.
Red Jenny said:
Oh God bless you, zanderman112. I thought I was going to have to reset my mom's new phone after I finally finished setting it up and she just started getting used to it.
Click to expand...
Click to collapse
Thank you. Now, you can also try market.android.com to wirelessly install apps.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"
Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.
Epiclectic said:
Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.
Click to expand...
Click to collapse
Gonna try to help.
Both SFR and bonsai are oollldddd roms. SFR froze up because it isn't journaled. I highly recommend using ODIN to get to stock EC05, then update to EL30. Then use qbking77s "How to root Samsung epic 4g gingerbread" video to get CWM and root.
CWM 5 can flash any Rom, but those roms in particular are so old and buggy.
Sent from something with a Ｋモ尺れモㄥ.
Epiclectic said:
Sorry to drag up an old thread, but I can't find any help on this thru searches, so here goes:
Does SynFro 1.1.0 clash with CWM5?
My Epic been on Bonsai 4.0.1 (CWM 3.0.0.6, ext4, golauncherex) for a long time. I used Rom manager to update CWM to 5, and to flash the ROM Syndicate Fro_fully loaded 1.1.0 . Seemed to run fine at 1st (hr or so) then while DL'ing a goLauncherex from market, the system froze. after battery pull and reboot, I had constant FC's. Booting into recovery from Rom manager lead to a generic Android recovery system (instead of CWM).
Powered off, 3 fingered into CWM, which suddenly had reverted to v3.0.0.6 . Tried to restore Bonsai, but only got error msgs ("syste.img not found. skipping restore of /system" same with data, android_secure, cache, sd-ext, etc. )
Had to triple wipe (data,cache, dalvik), reflash my bonsai rom and re-update CWM to 5 to get back to a normal functioning phone.
If the issue here seems to be conflicts between older roms clashing with newer CWM versions, is there a way to check which ROMs require which CWM?
thanks for your time.
Click to expand...
Click to collapse
I've got you man.
What you need to do is direct your attention to this thread right here by DRockstar: RECOVERY] ClockworkMod 5.0.2.7 BML Officially supported by ROM Manager
What you had done wrong was you installed through Rom Manager, which is a temporary flash ontop of CWM 3, it in itsellf is not CWM 5 installed. Within that thread you've a choice of an update zip of CWM 5 or a Odin tar, CWM zip is preferrable. But otherwise you should be fine. The zip from within that thread is more final.
AproSamurai said:
I've got you man.
What you had done wrong was you installed through Rom Manager, which is a temporary flash ontop of CWM 3, it in itsellf is not CWM 5 installed. Within that thread you've a choice of an update zip of CWM 5 or a Odin tar, CWM zip is preferrable. But otherwise you should be fine. The zip from within that thread is more final.
Click to expand...
Click to collapse
Ok, I got the real CWM5 zip, flashed, now all roads lead to CWM5, so that part is fine. And I stopped trying those olds ROMs , tried to flash SynIce.
My Epic runs Bonsai4.0.1, I did the triple wipe and then flashed the rom (from CWM5) but I get the following:
SYN Ice Logo
"Take a shower, pick an outfit, put on some smell good, call my crew.."
then the yellow bar freezes about 15% into its progress. it eventually kicks back out to CWM. no msgs or errors to share. I dont have access to Odin (or a PC) and Heimdall wont recognize my epic....any1 having similar probs? is it my kernel? I see suggestions sometimes to use Odin to switch from "EC05" to "EL30"...i thought flashing the ROMs changed your base ROM (DK28, EL13, etc) to the one it needed....is that not the case?
Epiclectic said:
Ok, I got the real CWM5 zip, flashed, now all roads lead to CWM5, so that part is fine. And I stopped trying those olds ROMs , tried to flash SynIce.
My Epic runs Bonsai4.0.1, I did the triple wipe and then flashed the rom (from CWM5) but I get the following:
SYN Ice Logo
"Take a shower, pick an outfit, put on some smell good, call my crew.."
then the yellow bar freezes about 15% into its progress. it eventually kicks back out to CWM. no msgs or errors to share. I dont have access to Odin (or a PC) and Heimdall wont recognize my epic....any1 having similar probs? is it my kernel? I see suggestions sometimes to use Odin to switch from "EC05" to "EL30"...i thought flashing the ROMs changed your base ROM (DK28, EL13, etc) to the one it needed....is that not the case?
Click to expand...
Click to collapse
Never heard of synice... I would really suggest odining to ec05 just to clean up the phone and then root and flash... just cleaner that way... btw where did you find that rom...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Never heard of synice... I would really suggest odining to ec05 just to clean up the phone and then root and flash... just cleaner that way... btw where did you find that rom...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Dude really SynIce is SRF lol wow how did that not click.
This is a guide I’ve put together from my (in)experience with flashing ACS. It mainly comes from the replies of k0nane and theimpaler747 in the SyndicateROM thread. However, since there’s so many pages that can be tricky to search for idiots like me who just throw up random posts for others to solve their problems, I thought it would be good to summarize it along with anything I happened to notice from flashing a couple of Epics. Consider it the FIBI guide.
Step 1: Read all posts by k0nane on page 1 of the SyndicateROM thread before doing a damn thing! http://forum.xda-developers.com/showthread.php?t=976194
Instructions for CWM are in this thread: http://forum.xda-developers.com/showthread.php?t=897612
Useful hotkeys:
Download mode - Hold down 1 on the keyboard when you power on the phone
Recovery mode - Hold Volume down+camera+power to power on the phone
Reset phone - Hold volume up+camera+power. This generally works when the phone is completely locked up.
Flashing:
When going between versions of ACS, check their notes to see if you need to do anything other than flash. You can go between some versions without wiping or losing anything. You can also flash between standard and fully loaded without wiping or losing anything.
Sdcard doesn’t mount in CWM, but shows up in Android - Format the sdcard in Android.
Boot hangs on the Samsung screen – Redownload, format your SD card and reflash
Boot screen flashed between different things – Wipe cache & data 3x and reflash
Journaling:
Enable journaling – In CWM, go to backup and restore. Backup, then restore using that backup. Journaling enabled!
Make it so you don’t need journaling – Keep a copy of the ROM on your phone at all times. Should you ever have data corruption, jump into CWM and flash the ROM again. It’s quick, no wipes needed.
If you restore a backup made in CWM and want to have non-journaled again – Flash the ROM after restoring.
Other issues:
FC in a specific app – Go into manage applications and clear data for that app
FC in several apps – In CWM > Advanced, try fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
If you have any major issues that seem unresolved, Odin everything back to stock with EB13, format your sdcard in android, re-download everything, re-install CWM, re-read all of k0nane’s posts on page 1 and try again.
If you want ads back – Install adfree from market and hit revert
If your phone is freezing often - Flash either the vision kernel found here: http://forum.xda-developers.com/showthread.php?t=1012136 or the Twilight 1.0.4 kernel found here: http://forum.xda-developers.com/showpost.php?p=12504067&postcount=5904. I haven't had the freezing issues, but I'd recommend trying the vision kernel first as it has some other potential benefits.
Recommended tweaks and add ons:
Fugutweaks – This will smooth out a few random things on the phone. I’ve noticed more responsiveness on the lock screen and icons on my homescreen. Small, but nice. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=981125
Impaled Keyboard – Makes the keyboard less likely to skip keys. Still have some, but they’ve gone down a lot. I use the Speed Demon Edition, still had a fair amount of dropped keys with standard one. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=1025533&page=18
SetCPU – Handles scaling the CPU and overclocking. Use ondemand setting for smooth performance. If you have issues when the phone is idle or it doesn’t wake up properly, set minimum CPU to 200Mhz. Free for XDA members, APK can be found here: http://forum.xda-developers.com/showthread.php?t=505419
Battery Calibration – If you want to calibrate your battery without going into CWM, grab the app from this thread: http://forum.xda-developers.com/showthread.php?t=1024867. It’s now available from the Android Market.
Vision Kernel – Pretty much Twilight + gives you 1.4Ghz and Voodoo colour which improves balance when brightness is at 100%. Flash in CWM, wipe dalvik. Kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1012136
And a final note that I'm now about 10 hours into testing... if you are using fully loaded and want better battery life, really try standard. It very easy to switch, it flashes over fully loaded with no wipes or data loss, the only thing you lose is that it resets your homescreens. But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Great info! I recently installed the newest SyndicateROM 1.1.0 on my Epic and the only trouble I had was with the included Twilight 1.1.0 kernel. My phone kept freezing and I would have to pull the battery to reboot.
This is an issue that has been documented with the ROM and is said to be caused by the kernel and its adjustments to voltage and overclocking, not all phones handle this well.
To fix the issue I flashed the Twilight 1.0.4 kernel, as suggested by k0nane, and I am about a day into testing without any freezing issues. The only problem is that the Twilight 1.0.4 kernel has a known issue with video recording and it does not work.
Let me say that the performance increase from installing SyndicateROM and ext4 are well worth the trouble.
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
is your brightness at 100%??? what was the difference between standard and fully loaded again??
VeNoM vZ said:
is your brightness at 100%??? what was the difference between standard and fully loaded again??
Click to expand...
Click to collapse
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
k0nane said:
SyndicateROM Standard includes LauncherPro. All Samsung and Sprint bloatware are completely gone!
SyndicateROM Fully Loaded - the choice of ACS team lead rjmjr69 - features TouchWiz instead of LauncherPro, and adds in Social Network Sync, Facebook, BuddiesNow, Program Monitor, and the stock live wallpapers. All the rest of the bloat is still gone!
Click to expand...
Click to collapse
Catalyst Shift said:
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
Click to expand...
Click to collapse
The brightness for battery life.
No, brightness is not at 100%. I generally use 0-25%, though I'll kick it to 100% when viewing photos or when I'm outside. Even with the lower brightness setting, I'd always have to recharge in the afternoon. I'm still doing a lot of testing for ways of having the battery last longer, today is longest it's ever gone for. I'll be adding more information when I feel like I've got a solid way of having it all setup.
OP, could you add the freezes and "terrible battery life" solutions? Namely, flash the kernel in the second post or VisionKernel. It's the most annoying one to answer multiple times daily.
Thanks much for this! Hopefully people read it.
I want to get the battery situation on my phone sorted out before adding it to the list. I was having pretty bad battery life, but switching to standard and removing gallery has made my phone last all day for the first time ever. I want to do some experiments between setcpu options, juicedefender and the vision kernel to see what works best. Hopefully by this weekend I'll have a more detailed idea as to how to get better battery life.
But for now, anyone having battery issues my current setup is using ACS standard and replacing gallery with quickpic. This has doubled my battery life.
Hey wassup everyone, first time writer long time viewer, and first let me say thanks to all the great people that have provided us with great roms for the epic and the syndicate team as well, Im currently using a Epic 4G with sindicate rom freeze 1.1.0 and i must say its awesome, aside from my battery dying really quickly when im runing it at 1.3ghz its actually great, usually i end up operatig it at 800mhz to actually save some battery life last me for 3 days at a time, and when i have it pluged in or show off my awesome epic i raise it back upto 1.3ghz, big difference cuz when i raise it up there my battery drains rather quickly like 3 percent a minute or so.....
well anyways now that, thats says, I have CWM 3..0.5 with syndicaterom twilight 1.1.0 and ive been sucessful at loading custom boot animation, but one thing is that im having trouble is loading the animation with sound? any idea onhow i can od that?, what are the steps, cuz so far ive been using root explorer to transfer and change bootanimation to load up on my screen, but i have no idea where to put the sound or how to even get it to load with the bootanimation any one have any ideas? please help, i do all his trought my phone, put the bootanimation on my sd and work from there and trasfer it to the system/media, most bootanimation that do have sound on them say to put it on the system/custimization/resources but i look every where and the syndicate rom doesnt have that archieve just the system/media, how can i load the sound into my boot? and how can i change the power off animation as wll?
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals..
This might.. just maybe (crosses fingers) alleviate the never ending repeating of questions in the main sfr thread
Catalyst Shift said:
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
Click to expand...
Click to collapse
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
The first sign of trouble came when I installed a fresh version of SyndicateROM 1.1.0 and then flashed Vision kernel 1.1. The phone booted-up fine but when I went to shut down it immediately froze and I had to pull the battery.
Im going to stay on Twilight 1.0.4 kernel for a while until I find something else.
I have tested Twilight 1.0.4 kernel for about a day or two and have not had any problems so far. I even overclocked with SetCPU to 1.2GHz without any issues.
tmspyder said:
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals.
Click to expand...
Click to collapse
I would be more than happy to contribute my experiences if this gets up and running. PM me with any updates to the "SyndicateROM [TSG] WiKi"
Please Help a Novice
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen. Have I bricked my phone? How do I recover? Please please please help...Haven't even had my phone for a day...
By the way, the error I'm getting is:
ClockworkMod Recovery v2.5.1.0
E:Can't open /cache/recovery/log
I backed up before I installed this ROM, and Restore brings me back to this same screen / message
mercerma said:
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen.
Click to expand...
Click to collapse
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Hey, great idea for the thread.
Something I learned:
I was having AWFUL freezing problems. Tried all the fixes (vision kernel, old twilight) to no avail. If these don't fix your problems, try Genocide Kernel (on these forums). Solved my problems.
Catalyst Shift said:
But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Click to expand...
Click to collapse
Ok, so im thinking of switching to the standard edition of he rom cuz im currently using the fully loaded added the 1.0 kernel vision on it to get the 1.4ghz, and its pretty smooth its stable at times so im keeping it at 1.3 for now until its set more stable..... however when u said that ure at 10 hours and u still have 62% whats the speed u have ure epic set at and whats the brightness?
Nolyrics2 said:
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
Click to expand...
Click to collapse
Fix permissions in CWM/etc.
Kernels cannot cause that. It's that simple.
Nolyrics2 said:
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Click to expand...
Click to collapse
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
I installed CWM previous to transferring the rom to my sd card
I did not the first time, but per instructions on the page where I downloaded the ROM, I reformatted my sd card, redownloaded the ROM, wiped everything 3x's and tried to reinstall. Same result. I keep getting the error on just about everything I do that states "E:Can't open /cash/recovery/log"
And thank you for your advise, any more would be greatly appriciated. I did search the forum, but there is so much information, hard to find what I really want, especially as a novice. I plan to not be a novice for long thanks to xda!
mercerma said:
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
Click to expand...
Click to collapse
I could probably answer that question, im still a noob, but from what i know u need to install CWM version 3.0.5/6 in order for u to run does roms, thats why ure having trouble flashing it, since Syndicate roms are EXT4 Base Roms anything lower then CWM3 wont support since they are RFS files, go here and follow the steps
http://forum.xda-developers.com/showthread.php?t=976194
download the CWM3 and root it again, u can run the CWM Root over the previous 1 so dont worry, i did it that way and i had no problems what so ever, as to check to see what modem u had, go to settings, about phone, under base band version check to see if the last 4 letters says EB13, or DK28, or if u have the ECO5 which is the newest stock base update that came out.
Also its best to know if ure phone is from stock, or if u updated from any of the first 2 version updates, EB or DK, if u where like me that waited for the update and stayed at Eclair then updated when the ECO5 OTA came out then u should be fine....
Just incase u are from a update of EB or DK here is the link for does 2 versions of CWM3
http://forum.xda-developers.com/showthread.php?t=897612
if im wrong then someone please correct me im still a noob learning.
EDIT: just noticed that u said ure phone is messed at that point, umm u can try to do a factory reset then restart ure phone see if that fixes the problem, then try follow the steps above, if that doesnt work, u will have to download odin, which is also in that link and reflash back to stock, everything is there so if u follow does instrunctions u wont have a problem.....its actually pretty easy.....
I'm not entirely sure where this topic would go, but I have figured out how to get wildchild 2.0 and 3.3 up and running on the VM WFS. It might work for other CDMA Wildfires, but I'm not sure. I figured it out after reading a post by 'threefootsmurf' who said he got it working. I'm just making a tutorial on how to install it and get it running fully without problems, since I had a few problems, and to show that we have a great rom for CDMA phones. Oh and these steps are pretty straightforward, but I left out things like backing up everything since you should be in the habit of it already.
1. Download the wildchild file. Either 3.3 or 2.0, I have found that the odex version for 2.0 and the deodex for 3.3 tend to work better than the other..
2. Download the 'Hensemod' VM patch.
3. Put them on the root of you micro sd.
4. Boot to recovery and factory reset and wipe dalvik
5. Flash the wildchild ROM.
6. Boot the phone and go through everything, you will probably get error messages and the phone may shut off and power back on, but your main goal is to get to the home screen after doing the google setup and everything.
7. Reboot back into recovery and do a factory reset and dalvik wipe again.
8. Flash the hensemod VM Patch. (You may need to reflash the rom again and then the VM patch in one go here, it all depends)
9. Boot the phone and go through the google set up and everything again, and the phone should be in working order.
Those were the exact steps I used. I tested multiple ways to do it, some gave me bootloops, some stayed on the HTC splash screen, and some kept rebooting the phone. I like the wildchild ROM and this tut will open up the wonderful rom for VM and possibly all other CDMA users. I hope this helped you guys.
Wildchild 3.3: http://forum.xda-developers.com/showthread.php?t=1842771
Wildchild 2.0: http://forum.xda-developers.com/showthread.php?t=1652973
Hensmod: http://forum.xda-developers.com/showthread.php?t=1434497
thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid
I advise you to post tutorials like this in the General section
threefootsmurf said:
thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid
Click to expand...
Click to collapse
I know what you mean I'm a pretty big noob at this stuff too, but it's fun thinking I have some kind of involvement in something. I'm using WC 2.0 right now since I can't get 3.3 to load on the odexed version with wifi and data working. I gotta edit my post. I got the deodexed version running, but it's got bugs, like FB wont work, and a few apps wont work right either, and of course no A2SD support... Lame. And I tried flashing all at the same time. But i'd get bootloops with 2.0. So I had to do it the way I described. Not sure if it's my phone my recovery or what. But yeah....
THANKS
This should be stickied for marvelc.
Thank's wc running great on marvelc.
Sent from my HTC_A510c using xda app-developers app
I just flashed WildChild 3.3 to my VMUSA Wildfire S last night. Here is my experience so far:
Definitely install WC and the VM patch right on top of each other in one shot
Skip the keyboard tutorial in the setup
If you get to the wifi setup and yours isn't listed, you need to wipe/reset/clear dalvik and install both files again or you're gonna have a bad time
I've got video playback problems. Videos I record playback with horizontal matrix green crap, and videos in the YouTube app give me audio only
Opinion: There are a few things I don't like about WildChild which are causing me to abandon it after 24 hours. The video issue is unacceptable, and a bunch of strange app choices make this not much better than the crap apps that come with HTC/VM Sense to begin with. Stock browser is absent in favor of Dolphin, no Google Talk app, no default Calendar, required use of Startup Manager (Free) which I feel is pretty useless to me, and a whole list of other apps (like a dozen) I am too lazy to deal with. I realize what I am looking for is a barebones setup, and I'm going to look for it starting now.
Thanks for this post. I've been running Wildchild 2.0 for a few months now. The video issue mentioned above comes & goes with certain app installations - oddly enough a reinstall of the youtube app usually clears it up on my WFS.