DROID BIONIC Jelly Bean Update

Are you set up for automatic restore? SETTINGS>BACKUP & RESET>check BACK UP MY DATA and AUTOMATIC RESTORE.
It really works very well.

Pretty sure that is under Settings --> Privacy.

I also did the full factory reset, reapplied the FXZ to get webtop working. Rooted, Voodoo, upgraded, re-rooted. All worked like a charm thanks to House of Bionic (Cheers Samuri!)

Now re-setting up my apps and configurations. I could have use titanium, but It feels "freesher" with a new install.. Probably just my old bad habits. I had planned on going to the S4 near the release date, but this JB build with Root and Unlimited data...no reason to upgrade. I'm really happy with it. This is the way the phone should have been 18 months ago. My only remaining gripe is the crappy camera which I was never able to get to take decent pictures...but I can haul a nikkon around on vacations just as well.
 
I got my update and since then I have a black pop up screen with GUI EXCEPTION on some WIFI login screen. I have no clue how to correct this!
 
Just a quick noob uncertainty question. Im going to do an FDR then make a rom slot and try the CM10.1. The FDR wont mess with root correct? please keep the flames to a minimum...lol
 
An FDR fixed that issue for me.

Had the same problem, FDR did not fix mine. I did a force stop and then disable on both the backup assistant and backup assistant plus contacts. Haven't had the Gui popup since.


Sent from my GT-N8013 using Tapatalk HD
 
Kids these days. :D LMAO.

o) Install Voodoo OTA Rootkeeper from the play store (not the HoB version as it's fubar)
o) Protect root
o) Install Koush's Superuser
o) Run Koush's Superuser...it will ask for SU permissions. Grant it.
o) It will prompt about updating the su binary. Allow it to do so
o) Uninstall ChainDD Superuser
o) Verify root is working
o) Delete protected su backup in Voodoo
o) Create new protect su backup in Voodoo

I have successfully switched to Koush's SuperUser following these instructions. Now Voodoo OTA status for Superuser app installed has a button for Google Play to download the ChainsDD version. The other 4 boxes are checked. Rootchecker says I have root. I can temp unroot and reroot, both verified with root checker. I can also delete su backup then protect root again. Is this going to cause any problems if I try to do the OTA update or the HOB method?

I was one of like two people who had trouble with HOB when upgrading to ICS. I don't remember the exact problem but the final boot kept crashing, if I recall correctly. I'm a little nervous about trying again since I've never used Linux or Ubuntu and don't have a root exploit if I lose root. Have you heard of anyone using keeping the old security and successfully downgrading back to ics? I'm thinking that may not be a bad option for me. Thanks for all your help and hard work.
 
I have successfully switched to Koush's SuperUser following these instructions. Now Voodoo OTA status for Superuser app installed has a button for Google Play to download the ChainsDD version. The other 4 boxes are checked. Rootchecker says I have root. I can temp unroot and reroot, both verified with root checker. I can also delete su backup then protect root again. Is this going to cause any problems if I try to do the OTA update or the HOB method?

I was one of like two people who had trouble with HOB when upgrading to ICS. I don't remember the exact problem but the final boot kept crashing, if I recall correctly. I'm a little nervous about trying again since I've never used Linux or Ubuntu and don't have a root exploit if I lose root. Have you heard of anyone using keeping the old security and successfully downgrading back to ics? I'm thinking that may not be a bad option for me. Thanks for all your help and hard work.

You're good to go. Install the OTA and have Voodoo to restore root.

There is a method for getting to JB while allowing for downgrade, but, you'd need to use the Linux root method as it involves flashing the system img. It's also a pain.
 
After fiddlin' with various ways to complete the 'ensure you're connected via wifi' issue with the Linux-based root method for JB on Bionic, I accidentally stumbled upon something that worked in that respect. I had both the Linux box and the un-rooted Bionic connected via wifi to another family Bionic's WiFi Hotspot and then by magic the whole share thingy worked. I had prior devised an old router to the point where I could ping in both directions from Bionic to and from Linux box to no avail. Go figure?

So here's another thing to try regarding the WiFi connection portion of the Linux/Samba root method.

On the topic for another thread, somewhere, not sure where yet to start it, the whole one Bionic conx to the internet via another Bionic's WiFi Hotspot problem is still there. I've spent many hours troubleshooting that. That being that if you try to run the internet from one Bionic connected to another Bionic's WiFi Hotspot, it's gawd-awful spotty, to the point of not really being usable. Suggestions as to the best place to start that discussion is welcome, encouraged. I made the reeeeealy dumb mistake of trying to start that discussion on the 'official' moto bionic website, but even after being recognized for the thorough (sp?) documentation of the steps I'd taken to try to resolve the issue and the moderators admission that I'd tried all the fix methods he/she knew of, was summarily dismissed when it was discovered that one of the bionics was rooted, even after I explained that all this was documented b4 rooting. Lesson learned from the 'try safe mode' site . . .
 
What I really want is Android 4.2.2 on my Bionic without having to do it with a 'multi-boot' ala SafeStrap.

There just isn't enough space, after three apps I need with large (~640 Mb) database storage needs, to mount a 1 GB, yet alone a 2 GB partition to do a dual-boot partition thingy for 'stock' 4.1.2 and some other ROM at 4.2.2, as much as I want 4.2.2.

Even with the great K'exec' explanation from our favorite Dr.HoB, and prior noob explainations regarding the bootloader ***** of moto et. al., I'm gonna risk yet another 'Sheesh, Kidz' post response from our resident Herr Doktor about why I cannot find some ROM in 4.2.2 that's a DD, mount it as home without the whole SafeStrap dual/multi boot kludge (sorry SS, I really do appreciate the alternative path you provide!) and be on Android 4.2.2 at boot without all the other jazz.

Hey, y'all, don't leave me alone in the center of the target, please. I know from years of experience that I cannot be the only one who wants to 'go there'

puleeeze???
 
Last edited:
What I really want is Android 4.2.2 on my Bionic without having to do it with a 'multi-boot' ala SafeStrap.

There just isn't enough space, after three apps I need with large (~640 Mb) database storage needs, to mount a 1 GB, yet alone a 2 GB partition to do a dual-boot partition thingy for 'stock' 4.1.2 and some other ROM at 4.2.2, as much as I want 4.2.2.

Even with the great K'exec' explanation from our favorite Dr.HoB, and prior noob explainations regarding the bootloader ***** of moto et. al., I'm gonna risk yet another 'Sheesh, Kidz' post response from our resident Herr Doktor about why I cannot find some ROM in 4.2.2 that's a DD, mount it as home without the whole SafeStrap dual/multi boot kludge (sorry SS, I really do appreciate the alternative path you provide!) and be on Android 4.2.2 at boot without all the other jazz.

Hey, y'all, don't leave me alone in the center of the target, please. I know from years of experience that I cannot be the only one who wants to 'go there'

puleeeze???
Why aren't your databases being stored on your SD card instead of internal memory?

Have you tried SS? I don't find it to be "kludgey" at all...quite the opposite, in fact. It's pretty slick. I am a self-professed ROM addict - you'll never convince me that stock is better than what the devs can and do give us. Moving from the Thunderbolt (with an unlocked bootloader) to the Bionic required a bit of learning (as evidenced by my noobish questions posed to Sam in this thread), but I find that I actually really like SS. I'd make nandroid backups of stock and each ROM, in case I messed something up, but with SS, it's not such a big deal (especially if you want to go back to stock).

You really should give it a shot before deciding you don't like it (and move your DBs to the SD card, if possible!). I've got Avatar's MIUI-ish and LiquidSmooth's 4.2.2 ROMs (both CM10.1-based) installed...they're both very snappy and I like them a lot (though I'd say LiquidSmooth's is probably better for me since I like a more AOSP look and it seems more customizable). I posted about an audio bug that appears in both, but it's easily worked around and should be fixed with the next CM10.1 release (or so I've read).
 
Besides you're never going to get 4.2.2 to work without kexec. The answer as to why should be obvious. A locked bootloader means you can't overwrite the kernel. No kernel, no kernel fixes for things like camera and blue tooth. IOW you're back to the same old routine we always go through with devs trying to hack around the problems of an incompatible kernel. SS solves the problem completely by allowing them to bypass the limitation of a locked bootloader. You get a custom kernel and a working 4.2.2 instance. Try it....

Sent from my Xoom using Tapatalk HD
 
I wanted to ask a question? How long it took for you guys to update to jelly bean once it said it available over the air?

Sent from my XT897 using Android Central Forums
 
I wanted to ask a question? How long it took for you guys to update to jelly bean once it said it available over the air?
I requested the OTA from my Bionic, and got it; the other Bionic in the household has not been prompted to install it, so I'd say that there's no particular rush on the part of the carrier to get it out there.
 
Well th reason why im asking is i have a photon q from sprint.its on the internet that the jb update for the phont q is now available ota as of last Thursday april 25,2013.. and i checked numerous of times and nothing..

Sent from my XT897 using Android Central Forums
 
So far the only drawback I hear about the S4 is that its Super AMOLED+ screen still has viewing difficulty in direct sunlight. Wonder why Samsung hasn't corrected this?
 
There's another drawback. Bootloader locked on AT&T. You know it will be on VZW, as well, but, this is really disappointing. I always thought AT&T would be my escape plan where I could run to if unlockable phones disappeared on VZW's network altogether. Sadly, that may not be the case.
 
Does anyone know if John G, or anyone else for that matter, have come up with a simplified way to root the Bionic JB? I could probably do the original method as outlined by Dan (@djrbliss), but if there is something more simplified that would be great. Apparently someone on DroidForums claims to have one, but I would rather check with this forum as it seems they've been more "in the trenches" with this whole issue and have done a pretty good job of it (thanks Samurihl, Dan and others!!! :) ).

BTW, what are the top two best roms for the Bionic running JB 4.1.2, especially ones where everything is working on them. I'm playing with the thought of trying SafeStrap out but want to know if there is a rom worth using first.

Thank you!! :)
 
Last edited:
Look at the op of the exploit thread and read it.

Sent from my Xoom using Tapatalk HD
 
BTW, what are the top two best roms for the Bionic running JB 4.1.2, especially ones where everything is working on them. I'm playing with the thought of trying SafeStrap out but want to know if there is a rom worth using first.

Thank you!! :)

I put CM10.1 (4/30 nightly build) on mine and I really like it. I always liked the stock Android and this shows you what Moto SHOULD be giving us. Everything seems to be working and working smoothly. I know it won't happen, but an update to 4.2.2 from moto with all of the junk removed would be a nice going away present :)

A lot of people complain about battery life after ROM changes. One of the first things I do is run BatteryCalibration after a switch. It deletes the battery stats and seems to help stabilize the system more quickly.