641 replies to this topic

[magicmaster141]

Nice comment in the 11th hour Magicmaster :-)

Thank you, I know how frustrating it can be worrying that you bricked your own phone. Depending how bad you messed it up it can feel like getting a new phone when you finally figure it out. Least for me~

BTW I've installed SS over custom ROMs plenty of times back in the GB days. I've also done it a couple times on the leaks. Right now I am running rag3 v3 or Chronic 1.5 (whatever its ____ing name is) on my unsafe side.

Same here I think im running redhead on unsafe right now. But as I said in my first post I have had to apply the 232 update on top of 905 fxz to get it to boot the *last TWO* times... Havent gave it much thought till now but Im wondering if I can get back to .905 or if I'm stuck on ICS (FXZ'ing + update). Havent ran into any trouble caused by it and I have no desire to go back to GB anyway but I am curious now. Will most likely give it a try tommorow or the next day and let you guys know how it went.

[SamuriHL]

I'm going clarify on what eye_dea was alluding to. There have only been 2 bionics that I couldn't recover and they both involved safestrap. If you reinstall safestrap on the safeside and install recovery again through the app, there is no way to toggle back to the unsafe side and if you fxz, the images with flash per-se but when you reboot you will still be on the rom you where on before flashing.

How in the name of all that's holy is that possible? An FXZ should wipe out all parts that we can flash. There should be no possible way for any safestrap crap to be left after that. This is very scary.

[timmy10shoes]

You tell me man. I'm not about to figure out why. But I can positively tell you it does not work. We fastbooted, moto-fastbooted, used rsd lite. All of which were successful except it always booted back to the same rom.

[SamuriHL]

That's crazy. Like wicked insane. Do these phones still exist?

[timmy10shoes]

It jacks the emmc when you do that. Both bionics couldn't save anything on their anymore. If you added anything to the emmc, it would stay until reboot and then be gone. If you erased anything, it would be back after reboot.

[timmy10shoes]

Both are long gone.

[timmy10shoes]

Test it out on your phone

[SamuriHL]

I'm good thanks. Wow that's pretty nasty. Let's hope no one else ends up like that. Yikes.

[timmy10shoes]

I tried to get their phones but they actually wanted sell them to me for like $150. They were both crazy I guess. It was hard for me not to test it but I thought better of it.

[SamuriHL]

Yea I need my phone working especially now that I'm writing a Linux/mac version of the HoB.

[timmy10shoes]

It was frustrating as hell not being able to help. I hope someone does it again and comes to you and tarnishes your unbricking streak. :-P

[SamuriHL]

Wow you're not nice! Lmao!

[freddy0872]

Hey guys! I wanted to thank you all for your support and prayers during the last few weeks! And thank u for the few who generously donated some funds to help move us along! Thank you all! I can't express my gratitude enough!

But as some of u may of heard we've been home now just over a week. My fiances progress is getting better as time goes on. :-)
But its still going to be a long hard road for the both of us.

I'm going to keep this short so its not off topic. But I wanted to thank you all and say HI! :-)

Sent from my Nexus 7 using Tapatalk 2

[correarc1]

Lastly, the ROMs themselves are divided into 2 main groups. Those that are based on the stock also known as a blur based ROMs. These ROMs have much less tweaks to them however they are fully functional and have few to no problems. The other group are either cyanogen or AOKP roms. These are roms developed by a group of developers and based on Android's original source (AOSP). These are what many ROMs use as their base. They are great because they are tweaked like crazy for battery life, options, etc. They are problematic for the bionic because the hardware doesn't always work right (bluetooth, camera, etc). So, the choice of ROM is dependent on what you are willing to sacrifice. CM9 is cyanogen 9 based on ICS, CM10 is cyanogen10 based on JB.

So, I tried Hash's CM10, and I'm having a little bit of trouble with the camera. Did it work ok for you?

PS: still pumped to have my phone back.

[SamuriHL]

Camera is a known problem in all the cm10 builds.

Sent from my Xoom using Tapatalk 2

[mrredpants]

Use camera 360 from market
Bluetooth doesn't work right

Sent from my DROID BIONIC using Tapatalk 2

[correarc1]

Hey Obsidian,

I just thought I would give you a heads up on this - Hash has changed where he is posting his Roms to rombot. (

Please Login or Register to see this Hidden Content

) for CM10.

[correarc1]

New question (sorry, you have gotten me curious now MrRedPants):

What's the main difference between AOKP and CM? also, in hash's download location he has it divided between the CM10, CM9, AOKP and AOSP. but I thought that AOSP was what Cyanogen and AOKP were based on, so I don't understand how you can have an AOSP rom.

This is really just for instruction's sake, since when I went to download this new rom which I'm trying out, I saw these designations and was mildly confused.

Thanks for everything.

[johnlgalt]

CM is AOSP with a lot of source modifications built in before compiling to make a final ROM.

I misread the previous post, hence this, while true, really does not answer that question.

See Pooka's post

Please Login or Register to see this Hidden Content

for the true meaning.

[correarc1]

I get it. thanks.