I recently flashed the Das BAMF 2.1 ROM. I also flashed the MR2.5 radio. Everything loaded up perfect and was running great until I went into the toolkit and tried to change the font. When the phone tried to reboot it went to the white "HTC" screen and that was it. Wouldn't go any further. I was able to pull the battery and boot into recovery. My questions are:
1. Is this a bug with the ROM or is it related to all the buzz about ROMs based on the leaked GB RUU causing bricks? Mine was obviously not a brick.
2. Should I risk flashing it again or would I be safer just sticking to the Froyo based ROMs for now?
By the way I did a complete wipe of data/cache including dalvik before flashing ROM.
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
ever since I've gone from the original GB leak to Froyo and now back to the MR2 leak and GB I've been having issues with ROM's.
it first started when I went back to froyo, after a few days of being on das bamf 1.7, my phone would go on an endless bootloop and I couldn't get back into it. so I tried reflashing the radio, the rom, fixing permissions, but nothing would help. I wasn't OC'd or anything with das bamf. so I wiped the data and flashed the rom again and I was back up and running on das bamf. About 5 days later, the same thing happened, endless bootloop and I couldn't get back into my phone. Luckily the MR2 leak came out and so I flashed to that along with gingeritis test IX. everything worked well, then I flashed to gingeritis 1.0 when it first came out on Monday.
Today, as I was on the phone with someone, my phone suddenly rebooted and got stuck in an endless bootloop. I cleared cache and did a fix permissions and luckily I was able to boot back up. That is, until I called VZW to report that 4G is out in my area (it wasn't my phone since I had 4G at the office 10 mi away, but not at home and I know of a few other people in my area that didn't have 4g either). I rebooted and now I'm stuck in a bootloop, but this time clearing the cache and fixing permissions didn't work.
I ended up having to re-flash the ROM to get back up and running... I guess my question is, am I doing something wrong, or is something wrong with the phone? I hadn't had any reboot issues at all until I switched back from the leaked GB radio and rom.
This happened to me in froyo when I came back from GB. What I did was flash the second radio on this thread and the problem went away. If you want to stay with bamf remix 1.7.
I hope this helps.
It's a leaked alpha version of a test rom basically, there are going to be bugs.
I've read a bunch of forms and I still don't know what is exactly wrong. I believe I did everything right by doing a complete wipe and dalvik; all of that. I then attempted to flash the Das Bamf 2.0.5 file and everything went smooth, then I did adb to get into the hboot and I flashed the new radio for the BAMF file which also looked fine when complete. Once I booted my phone the thunderbolt symbol came up and the BAMF title came up at the bottom then booted into the phone but this is where there's a problem. The HTC background stock skin appears and the notification bar (time, service bars) and that's it! I re-flashed several times but still the same result. Does anyone know why this is happening?
And why is it so important to delete the PG05IMG.zip file after you flash? I've read that people sometimes have to do it but I never have, could that be the problem?
You delete the radio file so if you have to boot into recovery they hboot it doesn't try to update the radio each time, as far a it not working, you flash the room they recovery, not room manager or hboot.
sent from my motorola V60 runnin' bamf gb sense 3 pr 4 for the TB
Your radio file might be bad, try downloading it again.
sent from my motorola V60 runnin' bamf gb sense 3 pr 4 for the TB
Check MD5sums. Reflash in recovery. No wipe.
^_^_^
I redownloaded the radio a few times and I went to youtube and got links from different videos which all pointed me to the same xda form that I found in the beginning.
how do I check the MD5sums?
I read a lot of threads and they say to always do a wipe when flashing the GB roms...
Hello All,
I'm not to this forum. I'm having a very strange issue. I had unlocked and flashed a scotts clean rom to my phone. This rom worked fine. It was the cleanrom standard 4.4. Everything worked fine, but I wanted to try something without sense. So I followed the instructions and ran scott's wipe program that wipes 5 times over. Then I did a wipe on the device. From there it got stuck in a loop where I would boot it into the hboot and it would try to load that weird PH89IMG file and then reboot and do the same thing.
Believe it or not I resolved this by removing the SD card then booting to recovery then slightly lifting the battery and inserting the sd card in and mounting so that I could load another rom after mounting it. Just to be safe I did perform one more wipe. I loaded the CLEANrom tapped edition. It installed and booted up just fine, only one problem. I cannot turn the wifi on.
So I cleared the cache and Dalvik cache, rebooted. still no wifi. It sits on turning on. The wifi mac address is obviously unavailable. It went to an error evetnaully, but there was no detail in it other than the word ERROR. I tried reloading the ICS kernel as well, still nothing. I didn't see anything in the forum on this issue, so I am not sure why it's isolated to my device. can you help me?
Thanks.
I know your tired of wiping and flashing but this has happened to me before on a previous Clean Rom version. Wipe then reinstall ROM. **Caution** Before you boot to Rom, boot to recovery and flash the kernel that came with the Rom. That cleared up my broken wifi. Also beware that if the Clean Rom tapped edition uses a different base ie. 3.14.605.05 or 3.14.605.10. then you have to flash the Stock Rooted RUU of 3.14.605.05 or 3.14.605.10 and then wipe and install ROM. link to stock RUU:
http://forum.xda-developers.com/showthread.php?t=1642217
I have had this issue with a couple newer ICS ROMS I have tried and it all seems to come down to reflashing the Kernel. Even after updating Nils' Roms to newer versions my rezound would load up fine and everything worked except wifi. If I went back into recovery and reflash the kernel wifi would be back to normal again. Make sure you have the correct kernel designated for that ROM as I have noticed some Kernels need to be redownloaded and reinstalled seperately. Good Luck
Hello,
I am having the same problem and I am on Rezound Pure GSM sense 3.6 rom.....I am confused whether to flash the wifi modules for the new kernel from the above link....I don't wanna take any risks as I finally got my GSM working on atnt.
Thanks!!
Hi. i own an HTC EVO V 4G (Virgin Mobile). i used the Search function but sadly didnt found exactly what i needed.
a month or so after activating the phone, i decided to Root, S-off, Flash Recovery, bootloader and a custom Rom. However, its been a while now, that when i do a fresh install i get some inconsistency problems. for example, my first Rom was Harmonia, but later on i switched to MidnightRom. there the problems started to show up. the Sense version was working fine, but then i wanted to try out the Jellybean version. and when i did (after wiping everything, of course) some apps were not working. PlayStore wouldnt let me download anything, Tethering was not working, when using "reboot" the phone would get in a bootloop, which would only go away by removing the battery. and 3D games (Shadowgun, Temple Run, etc.) were graphically laggy. more like, unplayable. the image was distorted to the point it was impossible to see what was going on. messed around with fixing permissions, deleting Cache and Dalvik, re-flashing, and the problem was still there. i tried with other Jellybean Roms (both 4.1 and 4.2) and noticed that the problems were still there. anyways, after deciding to live with the problems (running Wild For the Night). months later i decide to flash MidnightRom again and i see that all the problems are magically gone. to this day ive been running only 4.1+ Roms and i dont have many issues whatsoever. BUT. i tried a Senseless Stock-based Rom the other day (started to miss 3D camera) and it ran well, but the overall behavior of the phone was laggy. it would take longer than usual to do anything. took me about 5 re-flashes to get rid of all the problems. then just yesterday i tried a few other Roms. some worked, though DU was really laggy, and the icons would switch places by themselves at times. as i saw the problem was not going away with re-flashing, fixing permissions and whatnot, i decide to restore to my most stable Flashed Rom.
just to clarify, here is what i do every time im about to flash a new ROM:
Wipe everything except SD card
Wipe Cache and Dalvik
Flash.
Reboot
after i flashed, if something went wrong, or if im flashing something ontop:
Wipe Cache and Dalvik
Fix permissions
Reboot
so question is, is this normal? does this has to do with the phone switching from ICS to JB? or am i doing something wrong?
also, just curious... is there a way one could, say, by some weird reason be "half S-off"? because although my bootloader says S-Off, and i have been able to flash many things, i remember that when doing the Wire thing i experienced many errors, and the thing said it was successful by itself a few seconds later while i wasnt doing anything.
and also, which is the best and most stable Hboot version i could use?
My HBoot version is 1.04.2000 (PG8610000)
Radio is 1.09.00.0706
My Recovery is 4EXT latest version
Thanks in advance