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

[zero neck]

wheres the hboot?

Read please

 

[rckstrgil]

thanks guys i appreciate the help. i just remembered i backed up my system before i went on this little ****ed ass of an adventure. im restoring 1.6.3 right now. my fingers are crossed

 

[rckstrgil]

thanks guys i appreciate the help. i just remembered i backed up my system before i went on this little ****ed ass of an adventure. im restoring 1.6.3 right now. my fingers are crossed

 

[Iceycold]

Guys, I don't understand.. This requires a gingerbread radio. Aren't those the ones that are bricking phones?

edit: What I mean, is how the hell are there 346 pages of xda members that haven't gotten hard-bricked with this radio? I was gonna install, till I saw that it was a GB RAdio.

 

[NotJustAPhone]

Guys, I don't understand.. This requires a gingerbread radio. Aren't those the ones that are bricking phones?

That's right and that's why after running das BAMF 2.0 for a week I switched back to a Foyo ROM. I didn't want to run the risk of bricking my phone. Some users for various reasons are willing to take the risk. I'm still following the thread over at xda and based on the discussion there I am not willing to risk bricking.

Sent using Tapatalk

 

[Iceycold]

I knew it Good thing I took some precaution .

 

[NotJustAPhone]

I knew it Good thing I took some precaution .

Over on the xda thread, they're calling it Death ROM. Lol.


Sent using Tapatalk

 

[Boggus]

What's the backup assistant link again so I can load it on my phone again?

 

[dstrass]

What's your opinion of someone who has installed this ROM with no problems? Are the bricks happening during the install of the ROM or are they happening randomly?

Sent from my ADR6400L using Tapatalk

 

[NotJustAPhone]

I ran the Gingerbread edition of das BAMF for a week without any problems (other than some issues with some compatibility problems with a couple of apps). I didn't notice any random reboots and had no problems installing the GB radio and different versions of the ROM.

The reports on the xda thread are that bricking occurs after installation. Further, the bricked phones appeared to be running well and there were no signs of problems before bricking. One of the theories is that the radio code writes excessively to emmc storage causing it to fail. The suddenmess of the bricking is what had me concerned. Since I didn't want to risk bricking, I went back to Froyo.

 

[nate44]

I'm back on this ROM. I understand the risk in doing so, and have come to the conclusion that although there were some reported bricks, it wasn't nearly as many as I first thought. The initial warning that was given was a little strong handed in my opinion, but I understand why it was done in such a way.

Anyways back on GB and loving it for the past few days. I also read that butch is working on an update for this, so that's more of a reassurance that things are not quite that unstable. I don't know if Adrynalyne is doing the same, but I can't imagine why he wouldn't be. I mean how could you resist this little guy?

 

[thehotboy#AC]

I'm back on this ROM. I understand the risk in doing so, and have come to the conclusion that although there were some reported bricks, it wasn't nearly as many as I first thought. The initial warning that was given was a little strong handed in my opinion, but I understand why it was done in such a way.

Anyways back on GB and loving it for the past few days. I also read that butch is working on an update for this, so that's more of a reassurance that things are not quite that unstable. I don't know if Adrynalyne is doing the same, but I can't imagine why he wouldn't be. I mean how could you resist this little guy?

that is exactly what i am saying, so far i don't know of anyone who has had their bolt bricked .. i like too many features of this ROM and have been debating going back to froyo but i simply just can't
so far i've had GingerBamf 2.0 since the 23rd ( so one week ) and i have not bricked my phone. i think i will take the risk :-X

 

[marcusjpitts#AC]

i'm thinking about making the switch back to GB as well. Any word on when the new update is rolling out cus i always seem to flash a new rom a day before an update comes out smh.

 

[NotJustAPhone]

Saw a post from Adrynalyne on xda where he said that the computer he uses for ROM work died. Sounds like until his new computer arrives he won't be able to do much.

 

[mclarryjr]

I haven't changed since this rom came out because I have been away from my computer the last week so. I don't plan on going back to a froyo rom because I'm really enjoying this one and that's why I have insurance.

 

[djinsydius]

that's why I have insurance.

Hypothetically speaking, IF your phone ends up in the endless loop of reboots, what excuse would you give to get a new phone?

 

[normio2]

Hypothetically speaking, IF your phone ends up in the endless loop of reboots, what excuse would you give to get a new phone?

He doesn't have to give an excuse, he can just say he lost it and pay $50 to replace it, or he can say it was after he did the OTA update.

 

[project.in.process]

He doesn't have to give an excuse, he can just say he lost it and pay $50 to replace it, or he can say it was after he did the OTA update.

yup.
if it's through Asurion/Vzw it's $100 b/c it's a smartphone.
still worth it, though.

really want to jump on this ROM for GB but i'll wait til it's more stable. lovin' DB1.7 (1.6.3)

 

[mclarryjr]

Hypothetically speaking, IF your phone ends up in the endless loop of reboots, what excuse would you give to get a new phone?

First I would try getting a free replacement from Verizon I have replaced a few rooted devices and never have had any problems. I know there is no guarantee doing this and could very well be charge full retail price.

 

[mchandl1]

Has anyone had issues with Lotus Notes? Once I upped to 2.5 I haven't been able get Notes Traveler to sync... (yes my company uses ridiculous software)

Sent from my Bolt using Tapatalk.