My gf has a fascinate, I personally use an X10 so rooting and flashing my phones different. i've only done hers once. the comm romm has been having some fc's for her, and she cant send MMS, it gets stuck in sending, so she wants to try a new rom. I dont read up enough on this forum for her so I would like some common users advice.
First of all whats the advantage of ed01? is it better than ed03?
Is evil as good or better tham comm? she wants a stable rom with all the same features.
Shes on verizon, currently ed03
You might not have to flash another ROM. If you boot into CWM recovery, try wiping data, cache, and Dalvik and rebooting. If that doesn't work, go back to CWM recovery and try fixing permissions (in the advanced menu). Otherwise, you could download Evil Fascination, wipe data, cache, Dalvik and then flash your Evil Fascination download. EF and Comm ROM are both good (not a vast difference between the two), but I'd recommend staying with your ED01 modem for now. I can't speak for everyone, but I've had GPS problems with ED03 and ED04.
Another Fascinating post by my XDA app...
Related
I am preparing to flash this rom.. i am a n00b and cant reply in developmentel forums. I was wondering if someone hasd this rom and could help me.
It says not to wipe with 1.2 treat it as an upgrade. Does this apply to the people who already have this rom just an easrlier version? I am flashing from the stock rom should i wipe..?
Yes, if you are flashing for the first time, wipe data, wipe cache and dalvik cache.
dalivk cache? what is that?
reboot into recovery and there should be an option. I did just have a bad install though of this rom after getting virus working, It couldve been a bad DL or install who knows, but please make sure to make a backup of your system before you wipe. Its just always smart to do so you know you always have something to revert to. I had freeze ups twice but just rebooted into recovery and am restoring now. I only say this so if something does go buggy you dont freak.
you have to flash 1.1 first before 1.2. I do not know if 1.2.1 fixes that but as of a few hours ago that is how it had to be done. I kept getting my TB stuck on the storm and never logged into the phone.
no you dont...i never installed 1.1, just wiped cache and dalvik and flashed right over the old debloat rom..
The whole point is that apparently a lot of people are having issues booting into Das BAMF 1.2 after wiping data. So, basically, you want to NOT wipe (which is the exact opposite of normal ROM flashing behavior).
A "sure fire way" to succeed is to (obviously, backup first) install Das BAMF 1.1, wipe data&cache, boot ... add your gmail accounts and let everything settle, reboot into recovery and install Das BAMF 1.2, and just reboot WITHOUT wiping.
I came from using Das BAMF 1.1 and had no issues, but I didn't wipe. Good luck!
ok, i installed 1.2.. froze my phone.. had to do a recovery.. seems to be fine..
i see theres a 1.2.1.. should i do that with a wipe? or should i do 1.1 with wipe then upgrade?
My experience too.
Zshazz said:
The whole point is that apparently a lot of people are having issues booting into Das BAMF 1.2 after wiping data. So, basically, you want to NOT wipe (which is the exact opposite of normal ROM flashing behavior).
A "sure fire way" to succeed is to (obviously, backup first) install Das BAMF 1.1, wipe data&cache, boot ... add your gmail accounts and let everything settle, reboot into recovery and install Das BAMF 1.2, and just reboot WITHOUT wiping.
I came from using Das BAMF 1.1 and had no issues, but I didn't wipe. Good luck!
Click to expand...
Click to collapse
This is how I got it working. This ROM screams on my phone! Also keep in mind that the boot animation is short and the reboot after install is usually long. I waited at least 10 minutes before doing a battery pull.
Coming from the boLTEd rom I am assuming to wipe everything, flash 1.1, then flash 1.2. Here goes!!
All this talk of not wiping makes me wanna grab some sanitizer. hehehe
dahotz said:
you have to flash 1.1 first before 1.2. I do not know if 1.2.1 fixes that but as of a few hours ago that is how it had to be done. I kept getting my TB stuck on the storm and never logged into the phone.
Click to expand...
Click to collapse
Yeah this is what happened to me. I was going to try doing what you did but it was 2 am my time already and had to be up for work in five hours. I put the virus rom on first to see the look and feel of it, so had to do a data wipe, when I went to do das. Ill try DAS again later tonight, i think i may like the feel of this one more after playing around with virus for a bit. right now Im back to my stock root de bloated with what I did, so if i have problems this afternoon ill post back.
You guys running this... is Tango working for you? I can't get it to activate my camera
the reason i ask is i want to know if anyone has had a problem going from rom to rom with out going back to there back up then flashing the new rom?
must wipe before going to different rom. you may have issues booting up.
affliction said:
the reason i ask is i want to know if anyone has had a problem going from rom to rom with out going back to there back up then flashing the new rom?
Click to expand...
Click to collapse
I've had no problem at all. I always do a full wipe before flashing a new rom though. If you don't want to do a full wipe, and you're only updating the same rom (for instance, from viper 1.1 to viper 1.2 or something), then you could try minimally wiping cache and dalvik cache. I always recommend a full wipe for best results though. I consider a full wipe to be wiping system, boot, data, cache, dalvik cache, and sd-EXT (if you have an EXT partition on your sd card)
I've successfully flashed joelz' ShooTeR ReWInD 3D over stock OTA w/o wipe with no issues and then flashed Evervolv's Absurd over that with no wipe and no issues.
USSENTERNCC1701E said:
I've successfully flashed joelz' ShooTeR ReWInD 3D over stock OTA w/o wipe with no issues and then flashed Evervolv's Absurd over that with no wipe and no issues.
Click to expand...
Click to collapse
That will most likely start giving you problems eventually, if you continue not to wipe. Things from one rom will start showing up in the next rom you flash, and you'll most likely start getting weird little bugs here and there. At least it always did with my Evo 4G. A full wipe is usually recommended, but every flasher has their own techniques.
k2buckley said:
That will most likely start giving you problems eventually, if you continue not to wipe. Things from one rom will start showing up in the next rom you flash, and you'll most likely start getting weird little bugs here and there. At least it always did with my Evo 4G. A full wipe is usually recommended, but every flasher has their own techniques.
Click to expand...
Click to collapse
+ 1 to full wipe, you will get bugs eventually, might battery life or maybe apps won't install or work, right now might be cause all the roms are mostly the same with no heavy customization but when they start messing a lot with roms you migh get screw
If you don't have an Evo3d well you don't have an Evo3d
Both these roms are based on the stock OTA ROM for 3VO. Also "format("ext4","EMMC", "/dev/block/mmcblk0p23")" is written into the updater-script of both ROMS, wiping the /system partition prior to install. Flashover issues usually happen when you start throwing AOSP and ports into the mix. That being said, I'm meticulous about backups and will never blame an issue in a flashover on the ROM without a fresh install or a peek into the zip to ensure the issue exist.
USSENTERNCC1701E said:
Both these roms are based on the stock OTA ROM for 3VO. Also "format("ext4","EMMC", "/dev/block/mmcblk0p23")" is written into the updater-script of both ROMS, wiping the /system partition prior to install. Flashover issues usually happen when you start throwing AOSP and ports into the mix. That being said, I'm meticulous about backups and will never blame an issue in a flashover on the ROM without a fresh install or a peek into the zip to ensure the issue exist.
Click to expand...
Click to collapse
It's still best to do a full wipe if you ask me. I do it even if I'm flashing the exact same ROM with say, one tweak in one of my battery icons or something. I always wipe lol.
yeah i just hate dealing with a full wipe everytime so i figured i would get some opinions on the issue right now im running steel rom and want to flash viper so im not sure what i want to do
So I currently have Das BAMF 3.0 flashed onto my HTC Thunderbolt. It's working perfectly fine; but say I wasnt to flash another ROM, do I have to wipe my data and cache again via clockwork recovery? (yes I backed my phone up and backed up with titanium back up)
Yes or you will run into issues like me
Sent from my ADR6400L using XDA App
When switching between ROMs from different devs one should always wipe data/cache. Different devs sometimes use different packages for some of the base system apps and the data usually won't "mesh". If you don't wipe, you may not notice a problem initially...but a few day's later you'll be asking "Why does XXXX force close on me?"
Only time you shouldn't have to worry about wiping is if you're flashing nightlies or incremental versions of a rom where not much has changed unless the dev states otherwise in the release post.
Hi, everyone. I'm used to rooting/ROMing/etc. on the Samsung Epic, but I'm very new to the Thunderbolt. I rooted my girlfriend's phone and had some problems with the data connection being inactive following a kernel install. I went back to as close to stock as I could in order to get everything working again, but new problems have surfaced:
1. GTalk crashes
2. Camera fails to open
3. Documents fail to open, as in Word
4. Phone fails to update, though it indicates an update is ready
Right now, she's on a pretty much stock Froyo ROM and what I believe is the stock kernel, or something very close.
I've read a bit about the camera and gtalk problems. I saw a link to a CWM flashable zip that apparently fixes the date problem that causes the closes. However, it wasn't clear if that zip was only for GB for if it also works for Froyo. Please advise on that.
I haven't seen any reference to the document opening problem, unfortunately.
As far as the update thing goes, I'd rather keep her on a custom ROM, as I assume the update will kill her root.
Basically, I'm looking for a stable and reliable kernel, ROM (preferably GB), and radio combination that is known to run without issues. Last time I tried to pick a combo myself, it ended up killing the data connectivity, so I'm trying to figure out the "best" combination that is known to work. Also, if there are any Thunderbolt-specific flashing procedures that tend to cut down on force closes and errors following a flash, please let me know.
Thanks a lot,
-Rob
When you say update, you mean OTA? If so, you have to be 100% stock to get an OTA to install. You can't have a custom recovery installed.
Pretty much all the GB ROMs out there are pretty stable. The question is, do you want a Sense ROM, or AOSP?
As far as kernels go, Imoseyon's kernels are top notch. I prefer jdkernel for AOSP ROMs though.
I use the latest OTA radio and have 0 problems, and it works for both froyo and GB ROMs.
...
Thanks a lot for the response. I'd like to keep on the Sense side of things, just to keep the user experience sort of like stock for the girl.
So, to go one step at a time:
First, the radio. Is this the latest OTA radio that you mentioned (MR2?): http://forum.xda-developers.com/showthread.php?t=1154010
Second, the kernel. It looks like nerozehl has a great kernel that's based off of Imoseyon's leankernel. There are so many versions, though. Would the latest Sense kernel 2.3.6 (from http://forum.xda-developers.com/showthread.php?t=1099996) be appropriate, considering the ROM below?
Last, the ROM. It looks like SynergyROM is a good place to start. I believe the latest one is found off the download link near the top of this page: http://infectedrom.com/showthread.p...IGHTLYS-2.3.4-SENSE-3.0-★-☆-★?p=4368#post4368 Any thoughts on SynergyROM?
Does that combination seem like one that should work correctly?
Also, just so I have the steps correct for installation:
1. Flash radio in hboot.
2. Wipe in CWM (cache, dalvik cache, anything else?)
3. Flash kernel in CWM.
4. Flash ROM in CWM.
5. Reboot.
Thanks again for any help. It is definitely much appreciated. Can't go around breaking the girlfriend's phone, after all...it just looks bad!
-Rob
There is an issue with the lib files for the Camera ,which is messing up Gtalk. There is a fix in several threads, something HTC did on the new base.
Here is the fix:
http://themikmik.com/showthread.php?8436-Flashable-G-talk-Camera-Fix
...
Thanks, fillyo! I assume this works for both GB and Froyo ROMs?
-Rob
If you flash the kernel before the ROM whatever kernel comes built in to the ROM will overwrite the kernel you just flashed. I would say ROM, kernel, radio.
Oh and when you wipe I would do:
1. Wipe data/factory reset
2. wipe cache
3. Advanced, wipe dalvik cache
4. Under mounts and storage select format /system
Sent from my HTC Thunderbolt
JBO, thanks for the advice. That makes a lot of sense. Do you have any comments on the radio, rom, kernels I've selected above? Particularly the radio. I was told the latest OTA radio works well, but is that the one also knows as MR2?
Thanks,
-Rob
Sent from my SPH-D700 using XDA App
Yes the MR2 radio will work with that ROM as well as any leaked radio that is newer than the MR2. What radio works best is kinda subjective and seems to vary from person to person. I don't know if the kernel you linked is compatible you would need to ask in the Synergy thread. Honestly as far as the kernel goes I would just use the one built into synergy. I hear its quite good and has a great set of features.
Sent from my HTC Thunderbolt
I've used SynergyROM and it is an awesome ROM. It comes with Ziggy's kernel, which is an awesome kernel. The OTA Radio basebands are 1.39.00.0627r, 0.01.69.0625r
I hope you find a ROM/kernel/radio combo that works for you!
That's exactly the info I needed. I'll just stick with the built-in kernel and the MR2 radio. Thanks for all the help, guys.
-Rob
Sent from my SPH-D700 using XDA App
Hi guys,
with new ICS themes for stock ROM becoming available, one of my needs (aesthetic) to go MIUI went down.
Considering also the issues MIUI has on SGS2 (bad voice calls, not 100% smooth, not great battery life, gps slow and unreliable), I'm going back to stock.
... except I'm not really sure how to do it.
Would you suggest
- install mobile odin (I have no windows pc)
- download and flash KJ3 (ROM kitchen, pre-rooted)
would make it right ?
This way I think I couldn't make any deep clean, I suppose...
or perhaps you could suggest something better ?
Many thanks
Just get the rom you want, go into recovery.
Select wipe data/factory reset
Wipe cache
Advanced, wipe dalvik-cache
Then flash your new rom.
Edit-
Those bugs you have with MIUI, I don't have 'em. If you want ICS, you better wait.
I've jumped from MIUI to stocks with great battery and great kernals to ICS and stuff but I keep going back to MIUI.
I've done this more than 10 times but I'm still going back to MIUI...
(Edit)
If you have MIUI you should have CWM right?
Just flash Simple&Clean or Checkrom (I prefer either these, Simple&Clean prefered for me), then flash the ICS Theme, I prefer Big Bang's for this, I can't get Vertumus's to work...)
Then I'll flash a kernal to save some battery (I use Speedmod's Kernal!)
Then I'll wipe everything in CWM and reboot!