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
Related
Apologies in advance for being such a n00b.
I'm currently running CM7 RC1.1 with the MR2 radio on my rooted TBolt.
Heard lots of good things about BAMF 3.0 and thought I'd give it a try.
Did a complete wipe. Installed. Immediately after boot, things started going wrong. Lots of crashes even before I could sign into my Google Acct, VZW appeared briefly and went away altogether, and I couldnt connect to any wifi network.
Tried a few reboots. Reflashed the MR2 radio. Did a complete reset. Still no success.
I'm back on CM7 now but very keen on trying BAMF. Any suggestions on what I might be doing wrong?
nulambhbk said:
Apologies in advance for being such a n00b.
I'm currently running CM7 RC1.1 with the MR2 radio on my rooted TBolt.
Heard lots of good things about BAMF 3.0 and thought I'd give it a try.
Did a complete wipe. Installed. Immediately after boot, things started going wrong. Lots of crashes even before I could sign into my Google Acct, VZW appeared briefly and went away altogether, and I couldnt connect to any wifi network.
Tried a few reboots. Reflashed the MR2 radio. Did a complete reset. Still no success.
I'm back on CM7 now but very keen on trying BAMF. Any suggestions on what I might be doing wrong?
Click to expand...
Click to collapse
Did you flash BAMF from ROM Manager or Recovery. Don't flash from ROM Manager. Flash it directly from the recovery. Also try wiping multiple times.
I did flash from recovery. Will try multiple wipes this time. Just to be clear, which selection in recovery is the proper one for a complete wipe?
Thanks for the idea!
nulambhbk said:
I did flash from recovery. Will try multiple wipes this time. Just to be clear, which selection in recovery is the proper one for a complete wipe?
Thanks for the idea!
Click to expand...
Click to collapse
Its Wipe Data/Factory Reset. There's also Wipe Cache Partition. And under advanced there's a Wipe Dalvik Cache. Make sure you Nandroid(Backup)!!!!
Btw if you don't know how to navigate in recovery menu, its volume button to scroll and the power button to select
Up and running. Thanks!
I've tried the Liquid Thunderbred 2.2 and 2.3 and I can't get either if them to work. I get a constant android.phone force close. Using 627r and I do a full wipe procedure. Any ideas? I've heard good things about this rom and would like to try it out.
Did you try format system in recovery. Do after you wipe data and cache.Then load ROM.
Good luck it is nice ROM
Sent from my HTC ThunderBolt using XDA App
i am having this same issue regardless of what rom I use. It fc and then it acts like it has lost the 3g signal. I am going mad here with trying to figure out what is causing it to crash when I try calling. It isnt consistent either as some numbers arent crashing. any ideas?
I had issues with mine until I did a full wipe, loaded the radio first (MR2.5) followed by installing LTBv2.3. Make sure the back is on too. I kept wondering why I only had a x1.5 connection for a couple hours, thought I had screwed up installing the radio. Eventually I popped on the backing and it was fine.
A lot of what your experiencing is either a radio issue or a full wipe issue,,, I wipe data, cache, and dalvick cache at least twice and then load whatever radio that the rom suggests and when the rom loads up give it time to normalize, dont rush it. Be careful reformatting anything in cwm it will erase data on your SD card.
nrbowler said:
I've tried the Liquid Thunderbred 2.2 and 2.3 and I can't get either if them to work. I get a constant android.phone force close. Using 627r and I do a full wipe procedure. Any ideas? I've heard good things about this rom and would like to try it out.
Click to expand...
Click to collapse
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.
Hello everyone,
I have been reading these threads for a while, getting prepared to root my Thunderbolt. I rooted about a week ago with Revolutionary and had no problems whatsoever. A couple days ago I flashed my first ROM (Gingeritis) using the instructions on this forum, and everything worked great, except that I accidentally restored some system data with Titanium Backup, which I read can cause FCs, etc.
Therefore, I restored the stock ROM by booting into recovery and following those steps. Again, everything went well.
This morning, I wanted to try out a different ROM, so I followed the same steps with das BAMF 1.10, and I flashed the ROM successfully with no problems. However, after restoring my contacts (one of the green pieces of system data that I thought were ok to restore) with Titanium Backup, the popup "Sorry!" repeatedly came up saying that the application.com.android was not responding and needed to be force closed. It came up again so fast after clicking "close" that I couldn't even reset. Finally, I pushed the power button at the exact right time to be able to see the menu of options, and I clicked restart (not in recovery).
Now, the phone is running through the das BAMF and HTC startup screens repeatedly. The battery is pretty low. What do I do???
Thank you so much! I really really want to resolve this and avoid bricking my phone like an idiot.
-Matt
Turn it off. Charge to atleast half or so battery. Boot into recovery, wipe cache, data, dalvik cache, and format system. Load up whatever ROM you want and only restore user apps and data.
Sent from my ADR6400L using XDA App
Just what he said but let google restore the contacts, this us unless you never allowed google to let th them sync.