[ROM][GB][5.23.11]Das BAMF 2.0-5

[NotJustAPhone]

I restored back to 163 because of the brickings again. I will wait a few days, see how much i hear about more occurrences, and decide whether to go back. I just cant reallly afford to insurance claim for a replacement.

Anyway, i can practice patience for 3 days i guess.

I really like the look of bamf 2. I even set it up with sense after i set it up for adwx, and i usually Hate using sense. Pretty cool stuff. Is there a way to alter the Sense lockscreen, btw? I looked around but didnt see anything. I'd like to be able to change those widgets.

Only real problem i had with it was the slow charge. Flashed Imoseyon's lean 3.0.1 test1 and it was still unbelievably slow.

I haven't decided whether to switch back to DB 1.7, but am considering making the change to see how the latest bricking situation develops.

You can change the lockscreen icons on the das BAMF 2.0 in Settings (or hit the Personalize button). There are also options to change the lockscreen wallpaper, as well as display weather, stockprices, and photos. The Sense 3.0 elements they included are definitely nice.

 

[zero neck]

You can change the lockscreen icons on the das BAMF 2.0 in Settings (or hit the Personalize button). There are also options to change the lockscreen wallpaper, as well as display weather, stockprices, and photos. The Sense 3.0 elements they included are definitely nice.

that sounds awesome. i backed bamf 2 up, and i was about to flash pre4 to see what its like, when i saw your post abt the brick, so i just went back to froyo.

definitely looking forward to having gb back on this thing tho. hope these radio issues get sorted out.

of course i dont look the one place where those settings obviously would be - personalize.

 

[thehotboy#AC]

that sounds awesome. i backed bamf 2 up, and i was about to flash pre4 to see what its like, when i saw your post abt the brick, so i just went back to froyo.

definitely looking forward to having gb back on this thing tho. hope these radio issues get sorted out.

word around is that the issue isn't with the MR2 on Gingerbread, its with the MR2 on froyo .. i can't see myself reverting back to froyo .. DB 2.0 just keeps getting better and better with every preview .. i can't wait for the new release ( which probably won't be for a week or so but still )

and i just read on XDA that they are going to be working with a new sense 3.0 build .. #niceeeee

 

[zero neck]

word around is that the issue isn't with the MR2 on Gingerbread, its with the MR2 on froyo .. i can't see myself reverting back to froyo .. DB 2.0 just keeps getting better and better with every preview .. i can't wait for the new release ( which probably won't be for a week or so but still )

and i just read on XDA that they are going to be working with a new sense 3.0 build .. #niceeeee

yeah i read it was mr2 froyo, and he had flashed a kernel and rebooted it once or twice before it bricked. but i dont know if a rom, froyo or gb, could cause the brick. i guess it could but thats not usually how it happens (aside from soft bricks). i think the general consensus is that it's hardware related, and that some thunderbolt devices may have a fatal flaw somewhere that causes hardware failure.

I dont really know much about it, though. I just know i dont want to brick and pay for it if since i'm aware of the risk. so i figure i'll wait it out a bit.

edit - also dont know what kernel it was, or the settings he was using, i guess that could play a part in it.

 

[DanSan]

One thing I noticed about DB 2.0 is that you actually have to manually choose to save any new phone number to google. When you enter a number you hit the 'contact type' drop down box and select google... its a pain and took me a couple of ROM changes to realize what was going on. here is a SS of what I mean good luck

if u go into people and go to view and only check Google... when u add a new contact from then on out it will always default to making them as a Google contact.

 

[Harkes2k]

I'm still stuck with the same issue.. the Rom will boot until what should be the homescreen comes up and then it freezes and nothing works. All that is on the screen is the wallpaper and notification bar nothing else. No lockscreen no icons no nothing.. the only button that works is the power button to turn the screen off it will not turn the phone off. No volume buttons or feedback from any buttons.. md5 checks out fine. Any ideas?

 

[bigdonpaul]

I'm still stuck with the same issue.. the Rom will boot until what should be the homescreen comes up and then it freezes and nothing works. All that is on the screen is the wallpaper and notification bar nothing else. No lockscreen no icons no nothing.. the only button that works is the power button to turn the screen off it will not turn the phone off. No volume buttons or feedback from any buttons.. md5 checks out fine. Any ideas?

Clear the dalvik cache and regular cache as well as data wipe 3-4 times in Clockwork Mod Recovery. Works fine after doing that.

 

[Harkes2k]

Iv tried wiping all them multiple times once... no luck still...

 

[thehotboy#AC]

i had that same issue, it was a bad ROM download .. go ahead n flash to a backup, re download the file, clear everything n flash again . It should work

sent from my DB 2.0 THUNDERBOLT !!

 

[ssethv]

Iv tried wiping all them multiple times once... no luck still...

I was going to say the exact same thing as thehotboy, a bad download is def possible, it happened to me when i owned my incredible. like he said, redownload the ROM, and you know the rest... keep us posted.

also, im sure you already know this, but only use CWM and not ROMmanager app

 

[Cyber Warrior]

I'm still stuck with the same issue.. the Rom will boot until what should be the homescreen comes up and then it freezes and nothing works. All that is on the screen is the wallpaper and notification bar nothing else. No lockscreen no icons no nothing.. the only button that works is the power button to turn the screen off it will not turn the phone off. No volume buttons or feedback from any buttons.. md5 checks out fine. Any ideas?

Had the same exact problem. Pull out the battery to shut down the phone. Power back on into bootloader (hold volume down & the power button at the same time until the phone starts up) and go to recovery. Wipe data & caches and flash the rom again. I used the same downloaded zip of the rom. Not sure what went wrong but I had the same problem you had. Screen was unresponsive and all I could see was the wallpaper and notification bar... launcher was gone and I could only use the power button to turn the screen on and off.. it would not power down the phone.

 

[germ447]

standalone gps services popup

is there anyway to disable the popup that comes up every time you enable the gps?

 

[zero neck]

is there anyway to disable the popup that comes up every time you enable the gps?

Isnt there a button that says 'don't warn me again'?

 

[zero neck]

yeah i read it was mr2 froyo, and he had flashed a kernel and rebooted it once or twice before it bricked. but i dont know if a rom, froyo or gb, could cause the brick. i guess it could but thats not usually how it happens (aside from soft bricks). i think the general consensus is that it's hardware related, and that some thunderbolt devices may have a fatal flaw somewhere that causes hardware failure.

I dont really know much about it, though. I just know i dont want to brick and pay for it if since i'm aware of the risk. so i figure i'll wait it out a bit.

edit - also dont know what kernel it was, or the settings he was using, i guess that could play a part in it.

Was reading around at xda and this member KDKobes has these posts about what he thinks is causing the bricks - i'll summarize really quick bc they are long, i think basically what he's saying is a combination of gingerbread's memory issues, overclocking, and incomplete rom/kernel flashing (like not wiping boot and sys, or something, which i've never done actually but may look into now) could be causing hardware failure - something to do with processes not being killed, and memory leaks, and what happens to devices when you OC.

thought it was interesting, and if you believe what he says, this would mean i guess that the radio is not the culprit.

anyway, i dont know what exactly to make of all this, just thought it was interesting to read. if you hit the link and want to read more he has a whole series of links in his sig about this bricking theory.
xda-developers - View Single Post - [NOTICE] Gingerbread Related Bricking - May 27th 2011 update

 

[RockyCJC]

FYI - I set PIN security on my lock screen. When it comes up it displays a message at the time indicating "You have incorrectly drawn your unlock patter %d times. Please try again in %d seconds."

I am successfully able to unlock my phone using my PIN. There doesn't appear to be any problem with functionality, but figure this is another thing to add to the list to fix. Low priority bug.

 

[RockyCJC]

Hey - more critical issue - music apps are force closing on 2.0-5. Take a look at this thread: http://forum.androidcentral.com/thunderbolt-rooting-roms-hacks/92603-music-3-01-crashing-bamf-2-0-5-a.html

Can we get a fix for this one or an alternative app that will work?

Thanks!!!

 

[ssethv]

Weird. I have had no problems with my music

Sent from my ADR6400L using Tapatalk

 

[normio2]

Weird. I have had no problems with my music

Sent from my ADR6400L using Tapatalk

same here

 

[ssethv]

Isnt there a button that says 'don't warn me again'?

when I enable GPS, i do it through the drop down notifications bar and under quick setting and check GPS. then when I open navigation the only pop up I get is about keeping my eyes on the road, which gives me the option to never show again... hope this helps..

 

[ssethv]

Was reading around at xda and this member KDKobes has these posts about what he thinks is causing the bricks - i'll summarize really quick bc they are long, i think basically what he's saying is a combination of gingerbread's memory issues, overclocking, and incomplete rom/kernel flashing (like not wiping boot and sys, or something, which i've never done actually but may look into now) could be causing hardware failure - something to do with processes not being killed, and memory leaks, and what happens to devices when you OC.

thought it was interesting, and if you believe what he says, this would mean i guess that the radio is not the culprit.

anyway, i dont know what exactly to make of all this, just thought it was interesting to read. if you hit the link and want to read more he has a whole series of links in his sig about this bricking theory.
xda-developers - View Single Post - [NOTICE] Gingerbread Related Bricking - May 27th 2011 update

I wonder if the kernel type that a person is using has anything to do with it?