DROID BIONIC Jelly Bean Update

Well, it took 3 attempts to root the wifes phone. Here's a oddity, the only difference between hers and mine, I had Superuser app still installed when I was rooting. She didn't. After I installed the superuser.apk on her phone and then ran the exploit again, she successfully rooted. Interesting indeed.

this one: Superuser (by ChainsDD)
 
Thanks Sam, will try as soon as I get home and let you know what happens.

Well crap... even with the latest moto drivers installed, when i run the fastboot flash system system.img it just sits at "waiting for device"

sigh....

And yes, phone is booted into fastboot mode and connected to the computater
 
Last edited:
Glad we're getting JB. I'm still waiting on ICS
17.jpg
18.jpg
19.jpg
20.jpg
 
According to OTA Rootkeeper I am not rooted at the moment. I should receive the Jelly Bean OTA sometime in the near future right?
 
Yes, see what Mike is talking about. BUT, please flash the system.img from 98.72.22 FXZ BEFORE you try it to clean up any root remnants. That goes for anyone with "leftover root crap" in system.

Boot to AP Fastboot (Power off, hold volume down and press volume), connect to USB, then:

fastboot flash system system.img

Make sure it's the right system.img. fastboot is in the HoB utils dir if you need it.

Alternatively you can use the HoB 10.1 with the 98.72.22 FXZ and do a FXZ Keep Data (DO NOT try to root from the HoB if you're on JB)

Then use the Linux based exploit.

So, I finally gave up using fastboot from windows (it would not see my device for some reason, even after reboots and such). Ran fastboot from the latest android sdk in linux and flashed the system.img from "cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip". Then rebooted into fastboot and tried the linux root exploit... the script ran without any errors, but still don't have root after reboot...

Guess I'll try the HoB FXZ thing now...
 
Well crap... even with the latest moto drivers installed, when i run the fastboot flash system system.img it just sits at "waiting for device"

sigh....

And yes, phone is booted into fastboot mode and connected to the computater

Don't know then. Make sure it's not a USB 3 port.
 
So, I finally gave up using fastboot from windows (it would not see my device for some reason, even after reboots and such). Ran fastboot from the latest android sdk in linux and flashed the system.img from "cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip". Then rebooted into fastboot and tried the linux root exploit... the script ran without any errors, but still don't have root after reboot...

Guess I'll try the HoB FXZ thing now...

Good times. And you followed the instructions to hit a key when it vibrated?
 
Good times. And you followed the instructions to hit a key when it vibrated?
Funny thing about that "vibrate" .. it wasn't just one vibrate.. it was like an earthquake going off on the phone.. like 10 of them in succession. Kinda freaked me out. Again, the difference between the wifes phone and mine, I had a single short vibrate, while hers was the apocalypse happening.
 
Yea some other people had that happen. I rooted pre instructions lol. So I didn't get any of that going on.

Sent from my Xoom using Tapatalk HD
 
Funny thing about that "vibrate" .. it wasn't just one vibrate.. it was like an earthquake going off on the phone.. like 10 of them in succession. Kinda freaked me out. Again, the difference between the wifes phone and mine, I had a single short vibrate, while hers was the apocalypse happening.

First time I tried, after it started vibrating I pushed enter and I discovered that it had fully unrooted (removed Superuser.apk and su). I then tried it again. This time, I let the vibrate thing vibrate for a good whole minute. Then, I cancelled the run.sh (all it does at that point is delete the temp files and then asks adb to reboot). I verified that the Koush Superuser was properly installed, /system/xbin/su was actually present and had the proper permissions, and that su actually worked (it did). THEN I let it reboot.

I manually backed up su as well verifying that the uid and gid were both root and the permissions were still there -- "just in case".
 
Well crap... even with the latest moto drivers installed, when i run the fastboot flash system system.img it just sits at "waiting for device"

sigh....

And yes, phone is booted into fastboot mode and connected to the computater

Same thing happened to me when I was trying to FXZ last week. My computer recognizes and opens files to my bionic with all 3 of my usb ports. However RSD would only recognize my device in one of them. Try the other ports this may be your problem also could be your cable is it oem or after market.
 
I can't use Oracle VM VirtualBox. I've tried for several hours and I keep getting a "system is running on low graphics" error, and I can't log onto Ubuntu. Any other ideas, I would really like to root this phone but I'm having a terrible time. I could try a live cd next I guess, will have to go buy some. My PC is brand new, got it a few weeks ago so I don't know what the problem is, just not working. I tried a USB flash drive and my pc wouldn't boot from it so I need some serious help.
.
 
Has anyone tried vmware's free player? To my knowledge you can create a vm with it now. I used ws 9 to do it on mine. Might be worth a shot for those having problems.

Sent from my Xoom using Tapatalk HD
 
OTA from ICS to JB went smoothly on my rooted Bionic. Took just under half an hour from "Install now" to back up and running. Extract from my notes:

Start Voodoo to restore root. "Device rooted" and "Root permissions granted" were not checked. After restoring root, "Root permissions granted" was still unchecked. Hmmm ...

Over to SuperSU, which wants to update the binary, again, even though it was updated just a couple of days ago. Cancel for now ... nope, that exits the program. All right, let's try again and click Continue ... failed. Try again: this time it succeeds.

Rechecking Voodoo: now all the boxes are checked.
Checking Titanium Backup: superuser granted correctly, shows root access.

Looks like Voodoo succeeded in keeping root!

I did run into an issue with LBE Privacy Guard: granting it superuser to enable the service put me into a boot loop. I had to bring the phone up in Safe Mode to get it to stay up long enough to deal with the issue. After confirming that others had experienced the same issue under JB, I uninstalled it, which is a shame: I liked being able to selectively dial back the permissions on some apps, and I don't see anything else in the Play Store that would be a drop-in substitute in that role.

Tasker was also unable to turn GPS on for apps that required it. I had to check the box to enable Google apps to track my location, after which it now works normally (GPS is mostly off, unless a particular app is running).

After rebooting, the Play Store wanted to update a bunch of apps that I don't use, so it was time to start disabling things. Using JB's native capabilities I was able to disable all of the following:

Backup+ Media
Browser
Chrome
City ID
Facebook
Gmail
Google Calendar Sync
Google Contacts Sync
Google Play Magazines
Google Play Movies & TV
Google+
Movie Studio
NFL Mobile
Picasa Uploader
Slacker Radio
Smart Actions
Talk
Verizon Tones
Video Calling
VZ Navigator
ZumoCast​

I had to use Titanium Backup to freeze the rest:

AcousticWarning
Backup Assistant Plus
Backup Assistant+ Contacts Client
Emergency Alerts
Smart Actions Android Framework
Smart Actions Proprietary Framework​

I moved the old ICS-era Titanium Backup directory out from under my Dropbox directory to force a new backup last night. TB is now uploading a gigabyte or so to Dropbox, so I won't be able to get a very accurate read on battery life today.

All in all, a fairly smooth transition. The phone that needed help from HoB to get to ICS hasn't yet asked to update to JB; we'll see whether it's able to take the OTA this time or whether I have to intervene manually as I did before.
 
All the reviews and articles I've seen about the Galaxy S4 will make it real hard to wait for the next Moto Flagship phone. My upgrade is May 15th. Decisions, decisions...
 
I have stayed unrooted (glad for the exploit for the future however). JB seems to have settled in and the early high battery drain has gone away and battery usage seems normal. How's the new phone Sam?
 
I can't use Oracle VM VirtualBox. I've tried for several hours and I keep getting a "system is running on low graphics" error, and I can't log onto Ubuntu. Any other ideas, I would really like to root this phone but I'm having a terrible time. I could try a live cd next I guess, will have to go buy some. My PC is brand new, got it a few weeks ago so I don't know what the problem is, just not working. I tried a USB flash drive and my pc wouldn't boot from it so I need some serious help.
.

When the message that "your system is running in low-graphics mode" appears press Ctrl+Alt+F1 to enter the terminal. Then login with your credentials, and then run the following commands:
Code:
sudo apt-get install fglrx    
sudo reboot

Your base install should have the settings of the first image, 2d, 3d acceleration on, 128mb memory (max). The network should be a bridged adapter so that it reads directly from the NIC installed. I would also suggest that the base memory of the system be at minimum 2gb (if you have more than 4gb of ram). If you're sitting on 4gb of ram only, then I would only use 1024mb of memory. Hard drive should be a dynamic set, so it can grow in size as needed by the OS. The type of image is not important.

Should look like these:
 
Last edited: