DROID BIONIC Jelly Bean Update

[tribblon]

Definitely sounds like FDR time, man. Bummer but at least you'll have a fully functional phone again, and JB is way worth the trouble imo (i ended up having to do FDR myself so i could have root on JB after stupidly accepting the OTA update on rooted ICS without voodoo or anything)

good luck!

Yeah, I just wasn't thinking on that note about reverting.

Yes, I have tried it in another device. It reads fine in my old droid x, and my laptop. I even tried to see if I could redo the update in recovery, but it only shows ".." when you go to select the update.

Note that it isn't just the SD Card, I can't see the device memory either. When I go to Storage in the settings, it force closes with the unfortunately, settings has stopped crap.

So guys any ideas here, do you think that Motorola would support this issues, I guess it wouldn't hurt to try right?

Sent from my DROID BIONIC using Tapatalk 2

 

[804hokie]

Rumor (and I stress this is a rumor) is that Google isn't pleased with the latest prototype of the X Phone, and has sent it back to Moto. Regardless, most are now saying chances are very slim that we'll see any major announcements from Moogle at I/O.

Also, for anyone that's looking for a great background app manager, checkout Greenify (requires root). https://forums.androidcentral.com/e...ails?id=com.oasisfeng.greenify&token=8WYvXny1 After JB got settled in, my battery drained somewhat faster than ICS, but with Greenify needless apps can be hibernated to save data and battery life. It makes a huge difference, without killing or disabling the app process. My battery life is easily improved 50+-percent without running Juice Defender Pro (which does the job, but goes overboard).

 

[Ry]

I apologize for double posting. First time on this forum. I noticed my original message was for a different phone model.

My problem is this, when I leave internet explorer then tabs I had open and websites I visited are no longe there. Whenever I go back into Internet explorer only a single tab is there and its goes to my homepage. I liked it before when I would open internet explorer and my last visited webpage was open.
I checked settings in all that I could think of without any luck.
Any ideas?

Also I had a post it app that now has COMPLETELY disappeared. I had notes on my 'wallpaper' that are gone. This saddens me

The sticky notes apps is gone forever. Support pages said to back export any important info out of it before updating but Motorola should have done a better job getting the word out there.

 

[studcookie]

Failed upgrade, lost 4G

I'm trying to upgrade my wife's rooted 246 ICS Bionic to Jelly Bean, but haven't yet been successful.

I thought I returned it to stock (restored stock recovery, unfroze all apps, reverted a certain change to the settings db). I used Voodoo OTA Rootkkeper. But it failed the checks. So I used House of Bionic to FXZ 246, keeping data. Same result.

Only now I've discovered that I've lost 4G somewhere in the process. Even though my GS3 gets a solid 4G signal, the Bionic reports 3G only.

What's my next move? Do a full FXZ to 246 and lose data? Just go ahead and FXZ straight to JB (losing data) and root it from there? Will I get 4G back flashing the radio with one of these?

 

[SamuriHL]

Re: Failed upgrade, lost 4G

I'm trying to upgrade my wife's rooted 246 ICS Bionic to Jelly Bean, but haven't yet been successful.

I thought I returned it to stock (restored stock recovery, unfroze all apps, reverted a certain change to the settings db). I used Voodoo OTA Rootkkeper. But it failed the checks. So I used House of Bionic to FXZ 246, keeping data. Same result.

Only now I've discovered that I've lost 4G somewhere in the process. Even though my GS3 gets a solid 4G signal, the Bionic reports 3G only.

What's my next move? Do a full FXZ to 246 and lose data? Just go ahead and FXZ straight to JB (losing data) and root it from there? Will I get 4G back flashing the radio with one of these?

Um no. Just no. I get really irritated with comments like "failed the checks" as it's complete meaningless nonsense. How is someone supposed to help you without the actual error message you're receiving? It wastes your time and the people who want to help you's time. Given that I've been at the support game for a very long time I have a few guesses as to what might be wrong, but who can say for sure with no information other than "tried it didn't work"? If the HoB keep data flash was actually successful, then there is no way the jb update still fails with an error 7 assertion failure unless you disabled webtop flashing and the assertion failure is on the webtop partition. But since I don't have the error message or know for sure that the keep data option actually flashed properly, I have no idea what might be wrong. If you want someone to help fix it, they need actual details more than you've given.

Sent from my Xoom using Tapatalk HD

 

[studcookie]

Re: Failed upgrade, lost 4G

Um no. Just no. I get really irritated with comments like "failed the checks" as it's complete meaningless nonsense. How is someone supposed to help you without the actual error message you're receiving? It wastes your time and the people who want to help you's time. Given that I've been at the support game for a very long time I have a few guesses as to what might be wrong, but who can say for sure with no information other than "tried it didn't work"? If the HoB keep data flash was actually successful, then there is no way the jb update still fails with an error 7 assertion failure unless you disabled webtop flashing and the assertion failure is on the webtop partition. But since I don't have the error message or know for sure that the keep data option actually flashed properly, I have no idea what might be wrong. If you want someone to help fix it, they need actual details more than you've given.

My apologies, you've done amazing work for the Bionic community and the last thing I want to do is antagonize you, SamuriHL.

I didn't share the error because it looked so generic that I didn't think it offered any hints. It was an assert failed: apply_patch_check [hex numbers I should have written down] then something about sideload package.zip. I'll repeat the process and get the exact error if it helps, when I next get my hands on my wife's phone. And if the upgrade leaves logs somewhere I'm happy to go digging for them.

At any rate, it sounds like you're convinced that the HoB FXZ should have done the trick. Here are the steps I took there trying to follow the HoB install instructions: Remove su backup, uninstall OTA Rootkeeper app, restore stock recovery with SS (left SS app installed), install latest moto usb drivers, install HoB onto PC, create 246_FXZ directory and copy in .xml.zip file, run HoB, install RSD, run HoB again, phone booted into Fastboot but HoB quit with an error saying something like it couldn't connect to the phone in Fastboot and to try again. Leaving the phone in Fastboot ran HoB FXZ install again and install seemed to succeed (it took a while and RSD opened several times), phone eventually booted back into Android, but without 4G.

There must be a user error in there somewhere.

 

[SamuriHL]

Re: Failed upgrade, lost 4G

That sounds very much like a corrupt update zip. Is this something you downloaded manually and are trying to install from the sdcard? If so, redownload it and try again.

 

[SamuriHL]

Re: Failed upgrade, lost 4G

Also, give me the swdl.txt file in the HoB\rsd directory. Sounds like the radio may not have flash properly so we may have to fix that.

 

[studcookie]

Re: Failed upgrade, lost 4G

Also, give me the swdl.txt file in the HoB\rsd directory. Sounds like the radio may not have flash properly so we may have to fix that.

I will re-download the update, but it does pass an md5sum check- "5c0dbb6adaa5bacd662f3e8879b3795e" which I've run in adb shell on /mnt/sdcard-ext. It was a manual download. Does the filename matter? It's possible I pasted it wrong when I put it on the sdcard.

Here's my swdl.txt file:

05/13/13 23:32:30  --------------------------------------------------------------------------------
05/13/13 23:32:30  New Log Started For Software Download.
05/13/13 23:32:30  The FlashLog key is turned off.
05/13/13 23:32:33  0000125c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:33  0000125c	Phone.cpp	1754	0	ERROR	GetTechnology failed: ERROR.
05/13/13 23:32:33  0000125c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:33  0000125c	Phone.cpp	1754	0	ERROR	GetTechnology failed: ERROR.
05/13/13 23:32:33  0000125c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:33  0000125c	Phone.cpp	1754	0	ERROR	GetTechnology failed: ERROR.
05/13/13 23:32:33  0000125c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:33  0000125c	Phone.cpp	1823	0	ERROR	GetSoftwareVersion failed: SendTC failed: ERROR.
05/13/13 23:32:33  0000125c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:33  0000125c	Phone.cpp	1981	0	ERROR	GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/13/13 23:32:33  0000125c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:33  0000125c	Phone.cpp	1951	0	ERROR	GetBootVerFlashMode failed: SendTC failed: ERROR.
05/13/13 23:32:33  0000125c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:33  0000125c	Phone.cpp	1870	0	ERROR	GetDRMVersion failed: SendTC failed: ERROR.
05/13/13 23:32:33  Multi upgrade started for 1 phones
05/13/13 23:32:33  [Device ID: 0] 1/17 flash mbm "allow-mbmloader-flashing-mbm.bin"
05/13/13 23:32:34  [Device ID: 0] 2/17 reboot-bootloader
05/13/13 23:32:38  [Device ID: 0] 3/17 flash mbmloader "mbmloader.bin"
05/13/13 23:32:38  [Device ID: 0] 4/17 flash mbm "mbm.bin"
05/13/13 23:32:39  [Device ID: 0] 5/17 reboot-bootloader
05/13/13 23:32:43  [Device ID: 0] 6/17 flash cdt.bin "cdt.bin"
05/13/13 23:32:43  ERROR: 6/17 flash cdt.bin "cdt.bin" -> Phone returned FAIL. - on device ID 0.
05/13/13 23:32:43  [Device ID: 0] 6/17 flash cdt.bin "cdt.bin" -> Phone returned FAIL.
05/13/13 23:32:43  ERROR: Failed flashing process. - on device ID 0.
05/13/13 23:32:43  Multi upgrade finished.
05/13/13 23:32:44  --------------------------------------------------------------------------------
05/13/13 23:32:44  New Log Started For Software Download.
05/13/13 23:32:44  The FlashLog key is turned off.
05/13/13 23:32:47  0000134c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:47  0000134c	Phone.cpp	1754	0	ERROR	GetTechnology failed: ERROR.
05/13/13 23:32:47  0000134c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:47  0000134c	Phone.cpp	1754	0	ERROR	GetTechnology failed: ERROR.
05/13/13 23:32:47  0000134c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:47  0000134c	Phone.cpp	1754	0	ERROR	GetTechnology failed: ERROR.
05/13/13 23:32:47  0000134c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:47  0000134c	Phone.cpp	1823	0	ERROR	GetSoftwareVersion failed: SendTC failed: ERROR.
05/13/13 23:32:47  0000134c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:47  0000134c	Phone.cpp	1981	0	ERROR	GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/13/13 23:32:47  0000134c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:47  0000134c	Phone.cpp	1951	0	ERROR	GetBootVerFlashMode failed: SendTC failed: ERROR.
05/13/13 23:32:47  0000134c	Phone.cpp	518	0	ERROR	Generic failure when sending command.
05/13/13 23:32:47  0000134c	Phone.cpp	1870	0	ERROR	GetDRMVersion failed: SendTC failed: ERROR.
05/13/13 23:32:47  Multi upgrade started for 1 phones
05/13/13 23:32:47  [Device ID: 0] 1/1 flash radio "radio.img"
05/13/13 23:32:52  [Device ID: 0] reboot
05/13/13 23:37:29  [Device ID: 0] Waiting for others to finish current operation.
05/13/13 23:37:30  The FlashLog key is turned off.
05/13/13 23:37:30  FlashLog file is turned off.
05/13/13 23:37:30  Multi upgrade finished.

 

[SamuriHL]

I see a very big problem. Cdt failed. What, exactly, has been done to this phone? Cdt will only fail if someone does something moronic like try to fxz to ics from jb. The fact that it's failing to flash Cdt tells me we don't have the whole story on what been tried on that phone.

Sent from my Xoom using Tapatalk HD

 

[studcookie]

I see a very big problem. Cdt failed. What, exactly, has been done to this phone? Cdt will only fail if someone does something moronic like try to fxz to ics from jb. The fact that it's failing to flash Cdt tells me we don't have the whole story on what been tried on that phone.

I'm sure lots of moronic things have been done on this phone, but that wasn't one of them. It's never been on JB and I realize that I can't go back because of the whole security level thing. At any rate, I got the 246 FXZ and JB upgrades to work tonight, and for anyone interested here's how:

Based on SamuriHL's insistence earlier that an FXZ to 246 should have done the trick I decided to try again and watch it like a hawk, tailing the swdl.txt log. I blew away the 246_FXZ directory, created a new 246_FXZ directory, and copied the FXZ .xml.zip file into it. This time I connected the phone over USB before running HoB the first time. When it prompted to boot into Fastboot I manually brought the phone into Fastboot instead of allowing the script to do it. This time the log showed it got past step 6/17, where it had choked before. Once the install was complete I ran the "Preserve Root" option from the Utilities menu in HoB. This installed Voodoo OTA and using it I saw su backups in both the we-need-root and hob-needs-root directories.

Rather than install the JB upgrade manually from recovery I let it take the OTA. This time it worked! Only wrinkle- Voodoo OTA Rootkeeper could see the su-backup, but refused to restore root for me. I was able to do it manually from adb shell, however. For the sake of anyone Googling this, run "/system/usr/we-need-root/su-backup" instead of "su". Then you need to make the system partition writable: "mount -o remount,rw /system" Then "cp /system/usr/we-need-root/su-backup /system/xbin/su" to restore root. cp preserved the setuid/setgid bits, so I didn't need to run chmod. Finally make the system read-only again: "mount -o remount,ro /system"

Anyway, big thanks to SamuriHL for all his work on House of Bionic and being so accessible in the forums. He's being really generous with his time and expertise and it's very much appreciated.

 

[SamuriHL]

So it is likely the fxz was corrupt the first time. Yikes. I'm glad you stuck with it and worked through the issue. Kudos. However, you made one error. I wrote a restore root function in the HoB to automate what you did to fix root. Would have taken about 30 seconds. Lmao. Well done on working through it though.

Sent from my Xoom using Tapatalk HD

 

[studcookie]

So it is likely the fxz was corrupt the first time. Yikes. I'm glad you stuck with it and worked through the issue. Kudos. However, you made one error. I wrote a restore root function in the HoB to automate what you did to fix root. Would have taken about 30 seconds. Lmao. Well done on working through it though.

Ah yes, right next to the Preserve Root item I used. Oops.

 

[SamuriHL]

Ah yes, right next to the Preserve Root item I used. Oops.

Lmao

Sent from my Xoom using Tapatalk HD

 

[450donn]

followed your instructions but every time i start the process it goes to the starting daemon and locks at that point. Nothing happens. So I assume Im doing something wrong, but cant figure out what?

 

[SamuriHL]

That means adb isn't detecting your phone. There's a while bunch of reasons that can happen. I put them in the house of bionic faq under "why doesn't adb like my phone".

Sent from my Xoom using Tapatalk HD

 

[Nec3f]

So, I was following this thread for months before ICS came out. I've had my Bionic since the day it was released and couldn't wait for the new OS. I've had it on my Nexus for a while and was excited to see how it would work on the phone and I was hoping it would take care of a few bugs.

Is anyone else having problems?
My Swype no longer works as well as it used to it auto-corrects so poorly now that I just use it as a normal keyboard. In fact, I beta tested Swype and I just put my email in to beta test a new keyboard (Minuum).

The native browser doesn't work very well. If I use the search/magnifying glass at the bottom, type in a word and tell it to search, the browser will pop up, but then it freezes for about 30 seconds before anything happens. Subsequent searches are fine, but if I go back a few minutes later, it happens again. I also have issues scrolling through Google Images.

Using the dial pad while on speakerphone gives me some sort of double sounds. That is, if I press "5", instead of hearing "beep" I'll hear "beepbeep". If I have to navigate a phone tree on my cell phone I usually just put it on speakerphone so I can leave the dial pad up. I can't do that anymore because it sends all the button presses through twice. Furthermore, I think it may also do it with speakerphone turned off, it's just that I'm hearing it with speakerphone turned on. I've read one other account of that happening (here maybe) and the fix was to turn off dial pad sounds. I haven't tried that yet. Oddly, I also get the double sounds/echo with other applications. I, honestly, haven't tested it a whole lot. I know my podcasts are fine, but if I play Simpsons Tapped Out, all the voices have echos.

I was really hoping they would clean up the whole phonebook system. It's clumsy and hard to navigate. At the very least, there should be a way to take out facebook contacts that don't have phone numbers. If I'm scrolling through my phonebook, trying to find a number, Daniel Tosh shouldn't come up just because I follow him on Facebook. But that seems more related to the phone then anything else. The Motorola Android had that option. Am I missing it? Is there just a better phone contact management app?

I know there's a handful of other things, but that's what I'm thinking of right now. I was really planning on having this be one of the first phones that I kept for 3 or 4 years instead of running out and buying a new one the day my contract was up, but it's up and it's time to start looking. Although I think I'm going to wait for the next wave of Androids to come out.

 

[Boogan1]

I am having problems very similar to the ones you describe. Also battery life really sucks, I am thinking I am going to root and see if that help, it did when this phone had gingerbread. I didn't root on ICS because everything worked great, I like you was expecting great things with JB but it seems like I am always freezing up, restarting, I use swiftkey and it autocorrects a bunch of crap not even remotely like what I was texting, all the time have to correct. If rooting doesn't help, I am shopping for a new phone.

 

[SamuriHL]

Those symptoms usually require an fdr to fix.

Sent from my Xoom using Tapatalk HD

 

[Boogan1]

Thanks Sam! I will give that a try!