Separate names with a comma.
Discussion in 'Motorola Droid Bionic' started by sargentmajord, Jul 6, 2012.
Also I am sorry but I couldn't save the update I let it sit to long an it installed :-(
Now FXZ back to .902.
oops, nevermind, missed the part about the baseball game. Put the darn phone down and get back to real life
Can't leaving for a baseball game but 1.2 ghz bump confirmed on the A3 chipset so the bump will go to both chipsets I'll get a pic up
I am currently running it now. Its working amazingly well. I have a lapdock and it is working very smooth and fast. I Have uploaded the file and you can find the file at Bionic 5.9.232 New Leak 7/6/2012 - Android Forums
View attachment 52422
good stuff SM. i'm still happy on what ever leak build i'm on so iwont be movin. but nice find.
as for who ever said this is getting ridiculous heck no! the more the better. USE us as your guinea pigs moto!!!
New radio an kernel we will see how well they perform after battery is full charged an I got to 4G fringe muaahhahaha I am going to put u through hell ICS flavored bionic xD pic of system below
View attachment 52423
Bad pic this is a better one
View attachment 52424
Ok. So I am relatively new to flashing roms. When I installed 2233, I did not use Titanium Backup correctly and lost everything. I am interested in trying 232 but do not want to start all over again. I have two questions (be kind if they are stupid).
One: I read where you cannot use safestrap if GB on one side and ICS is on the other side. Can I use safestrap to flash 232 on the safe side if 2233 is on the unsafe side?
Two: How close do I get to a full restore with TIBU?
The speed bump has absolutely nada to do with chipset revision, this was proven via an informal discussion over at the Droidhive shoutbox. What seems to be happening is simple, a stability test is run on the phone prior to going to the home screen after first boot. The phone either passes or fails at 1.2GHz, and is clocked accordingly.
This is NOT a new kernel, it is the exact same 3.0.8 kernel as before, with a different build signature. This happens EVERYTIME they recompile the OS.