DROID BIONIC Jelly Bean Update

[SamuriHL]

It would make me feel better if I was also watching TV, and not sitting in my Finance class...

You keep talking about buying unsubsidized phones. And I'm assuming there is going to be an unlocked xphone. Will having an unlocked xphone on verizon's network fix this problem of crapware and updates?

For me it would. As soon as I got the thing I'd unlock it, throw custom recovery on it, and that'd be the end of OTA updates for me.

 

[zachthebomb13]

For me it would. As soon as I got the thing I'd unlock it, throw custom recovery on it, and that'd be the end of OTA updates for me.

How would you get the newest software on it then? Say for example the Bionic was in that position, how would you get JB to work on it? I guess I don't know much about all this. I just thought the build had to be specific to the phone, and that comes from the manufacturer. I know it's getting late, so you don't have to explain it if it's lengthy. Just curious.

 

[SamuriHL]

How would you get the newest software on it then? Say for example the Bionic was in that position, how would you get JB to work on it? I guess I don't know much about all this. I just thought the build had to be specific to the phone, and that comes from the manufacturer. I know it's getting late, so you don't have to explain it if it's lengthy. Just curious.

The Android source code is published by Google. ROM devs take that and build it for specific phones. With an unlockable phone, you can flash all the partitions including the kernel. When people try JB builds on the bionic, they're hampered by lack of a native kernel with updates for JB. If we could flash a kernel, then JB would work flawlessly like it does on other phones. Kexec muddies the waters a little bit by allowing a native kernel with updates to "second init" and replace the phone's kernel in memory. But it's not the same as FLASHING a kernel. Anyway, with unlockable phones, the ROM community will work on building custom ROMS for it such as CM10.x. And they are VERY fast about it. Consider my Xoom which is still waiting for the 4.1.1 build that was finished by Moto in September and blocked by VZW...I'm running 4.2.2 on it as we speak thanks to Team EOS.

 

[zachthebomb13]

The Android source code is published by Google. ROM devs take that and build it for specific phones. With an unlockable phone, you can flash all the partitions including the kernel. When people try JB builds on the bionic, they're hampered by lack of a native kernel with updates for JB. If we could flash a kernel, then JB would work flawlessly like it does on other phones. Kexec muddies the waters a little bit by allowing a native kernel with updates to "second init" and replace the phone's kernel in memory. But it's not the same as FLASHING a kernel. Anyway, with unlockable phones, the ROM community will work on building custom ROMS for it such as CM10.x. And they are VERY fast about it. Consider my Xoom which is still waiting for the 4.1.1 build that was finished by Moto in September and blocked by VZW...I'm running 4.2.2 on it as we speak thanks to Team EOS.

I see. And it would work just fine on their network?

I'm liking this route more and more. Thanks to people like you and Team EOS, I might just take this route. Is it difficult to do all this that you're talking about?

 

[zachthebomb13]

The Android source code is published by Google. ROM devs take that and build it for specific phones. With an unlockable phone, you can flash all the partitions including the kernel. When people try JB builds on the bionic, they're hampered by lack of a native kernel with updates for JB. If we could flash a kernel, then JB would work flawlessly like it does on other phones. Kexec muddies the waters a little bit by allowing a native kernel with updates to "second init" and replace the phone's kernel in memory. But it's not the same as FLASHING a kernel. Anyway, with unlockable phones, the ROM community will work on building custom ROMS for it such as CM10.x. And they are VERY fast about it. Consider my Xoom which is still waiting for the 4.1.1 build that was finished by Moto in September and blocked by VZW...I'm running 4.2.2 on it as we speak thanks to Team EOS.

Have you decided what your next phone will be yet? Or are you waiting for the S4 unveiling this week?

 

[SamuriHL]

I see. And it would work just fine on their network?

I'm liking this route more and more. Thanks to people like you and Team EOS, I might just take this route. Is it difficult to do all this that you're talking about?

On an unlocked phone, it's not hard at all once the ROM devs get moving. It works like this:

o) Install custom recovery
o) Nandroid your current install (if you don't, I'll beat you myself )
o) Use custom recovery to install your custom rom, following all advice and directions. (Don't skip things...if they tell you to format system, FORMAT SYSTEM. If they tell you to factory reset, DO IT. A little pain up front saves a MASSIVE PAIN IN THE HEAD later)
o) Install GAPPS (Google Apps). NOT OPTIONAL.
o) Reboot, and set up your ROM the way you like
o) NANDROID....AGAIN
o) Install Goo Manager or ROM Manager....have them auto update your ROM from now on.
o) DONE

- - - Updated - - -

Have you decided what your next phone will be yet? Or are you waiting for the S4 unveiling this week?

I have decided NOTHING yet. I need to see the S IV and I need to see what Moto's got cooking. I will compare my options and pick which one makes sense when I'm ready to buy. I recommend everyone do the same.

 

[zachthebomb13]

Easy enough. Does team EOS just do the Bionic, or many other devices? How do I follow you guys in the future, just in case you decide to buy a different phone than I do?

 

[SamuriHL]

Team EOS does not do Bionic. I don't do Bionic roms because it's not an unlocked device and I haven't really felt any rom lives up to what I expect. That is NOT to put down rom devs and the incredibly hard work they put into them. D Hacker and Hashcode are now part of the CM team. Very good news. They're working on Kexec even more. That's very good. If I get a new device, you'll know. I'm not hard to find.

 

[moonlightinwhite]

I've been following this thread for some time - I had a Thunderbolt (in all its unlocked bootloader and ROMs galore goodness!), but then I lost it...and picked up a used Bionic. Overall, I like the Bionic soooooo much better! Except for the bootloader, anyway

So, my question is this: why is an leaked JB build out of the question (assuming VZW screws us all over)? I threw 4ext recovery on my Bolt on day 1, overclocked the (single core) processor to 1.7GHz, and never used an official build (including jumping up to the ICS leak when it came out, because HTC/VZW took forever). When I got my Bionic, I put Eclipse ICS on it on day 1 and haven't looked back because it's been rock solid.

My point is that I'm pretty familiar with ROMs...but I'm not a dev, nor am I especially clear on the role the bootloader plays. If there's a stable, working JB build that is ONLY being held up by the jerkfaces at VZW, why wouldn't a leak to the dev community yield us a JB ROM in short order? Is it because we're changing the base from ICS to JB and that requires a bootloader update?

 

[zachthebomb13]

I'm sure when you decide on your new phone we'll have a discussion on why you decided that way. What does Team EOS work on? I guess I could just google it...

 

[SamuriHL]

I've been following this thread for some time - I had a Thunderbolt (in all its unlocked bootloader and ROMs galore goodness!), but then I lost it...and picked up a used Bionic. Overall, I like the Bionic soooooo much better! Except for the bootloader, anyway

So, my question is this: why is an leaked JB build out of the question (assuming VZW screws us all over)? I threw 4ext recovery on my Bolt on day 1, overclocked the (single core) processor to 1.7GHz, and never used an official build (including jumping up to the ICS leak when it came out, because HTC/VZW took forever). When I got my Bionic, I put Eclipse ICS on it on day 1 and haven't looked back because it's been rock solid.

My point is that I'm pretty familiar with ROMs...but I'm not a dev, nor am I especially clear on the role the bootloader plays. If there's a stable, working JB build that is ONLY being held up by the jerkfaces at VZW, why wouldn't a leak to the dev community yield us a JB ROM in short order? Is it because we're changing the base from ICS to JB and that requires a bootloader update?

I see you truly do not understand the role of the bootloader. When you have a locked bootloader, the *ONLY* thing you can flash to your phone is a *SIGNED* (by SERIOUSLY heavy encryption no less) code. If Moto leaks a signed update, it will likely get sued. You'll notice they killed cheesecake. No leaks of JB. This was not unintentional. So as I said before, the best we can do is let the phone boot up with what's on it, and then run stuff on top of that. Kexec allows a second init of the kernel which means it can be replaced in memory, but, that has limitations vs being able to flash a new kernel. Locked bootloader == no flashed kernel == no JB fixes for things like camera, bluetooth, etc.

- - - Updated - - -

I'm sure when you decide on your new phone we'll have a discussion on why you decided that way. What does Team EOS work on? I guess I could just google it...

I don't know all the devices they do. I use it on my Xoom. I know they have Nexus roms, as well.

 

[zachthebomb13]

Ah, i thought you were part of the Dev team.

Sent from my DROID BIONIC using Tapatalk 2

 

[moonlightinwhite]

I see you truly do not understand the role of the bootloader. When you have a locked bootloader, the *ONLY* thing you can flash to your phone is a *SIGNED* (by SERIOUSLY heavy encryption no less) code. If Moto leaks a signed update, it will likely get sued. You'll notice they killed cheesecake. No leaks of JB. This was not unintentional. So as I said before, the best we can do is let the phone boot up with what's on it, and then run stuff on top of that. Kexec allows a second init of the kernel which means it can be replaced in memory, but, that has limitations vs being able to flash a new kernel. Locked bootloader == no flashed kernel == no JB fixes for things like camera, bluetooth, etc.

Ah, gotcha. I tried to admit my ignorance of the bootloader up front

It really is such a shame. I've hated on VZW for a number of reasons, but this just clinches it for me. I'm out of contract in June and at that point, I'm going to (try to) unlock the Bionic's GSM radio and throw a Straight Talk (AT&T) SIM in there. VZW probably won't mind losing me, as I'm still on an old Alltel plan with unlimited data (which is only $20/month after my discount)...but heck if I'm going to give them anything more past my contract end date.

Thanks for all of your feedback, hints, inside tidbits, etc! If nothing else, I've learned that the locked bootloader is a thing from VZW, not the manufacturer (which I never knew). It's good to know where to place blame.

 

[SamuriHL]

Ah, i thought you were part of the Dev team.

Sent from my DROID BIONIC using Tapatalk 2

Nope. I do the House of Bionic. No dev affiliation.

 

[SamuriHL]

Ah, gotcha. I tried to admit my ignorance of the bootloader up front

It really is such a shame. I've hated on VZW for a number of reasons, but this just clinches it for me. I'm out of contract in June and at that point, I'm going to (try to) unlock the Bionic's GSM radio and throw a Straight Talk (AT&T) SIM in there. VZW probably won't mind losing me, as I'm still on an old Alltel plan with unlimited data (which is only $20/month after my discount)...but heck if I'm going to give them anything more past my contract end date.

Thanks for all of your feedback, hints, inside tidbits, etc! If nothing else, I've learned that the locked bootloader is a thing from VZW, not the manufacturer (which I never knew). It's good to know where to place blame.

I know you did. I'm just giving you a hard time. Technically you aren't allowed to unlock the phone now. It's technically illegal so be aware of that. Just keep an eye on things cause it will change.

 

[moonlightinwhite]

I know you did. I'm just giving you a hard time. Technically you aren't allowed to unlock the phone now. It's technically illegal so be aware of that. Just keep an eye on things cause it will change.

Good point - I had chosen to forget about that little technicality, hah. Although I have little evidence to support my belief, I don't think it will stay illegal in the long run. That's a discussion for another thread, I suppose.

 

[SamuriHL]

Good point - I had chosen to forget about that little technicality, hah. Although I have little evidence to support my belief, I don't think it will stay illegal in the long run. That's a discussion for another thread, I suppose.

Last word on this, but, it won't. Senate and House both have a bill to make it fully legal. Even if you did get sued by VZW (NOT likely) it'd be a 2500 USD fine. Just don't unlock it and sell it. That'd be a big no no.

 

[AllPurposeRadio]

Wife's Razr just got the OTA update for Jelly Bean...installing as we speak.

Sent from my DROID BIONIC using Android Central Forums

 

[gwhizkids]

Wife's Razr just got the OTA update for Jelly Bean...installing as we speak.

Sent from my DROID BIONIC using Android Central Forums

Same for my coworker. Living vicariously...

Sent from my DROID BIONIC using Tapatalk 2

 

[SamuriHL]

Fwiw I believe that we're going to get jb. I can't get into the details but I'm told things have changed. All I'll say is we want build 22. Iow let's hope 21 fails. It may delay it more but the wait will be worth it.

Sent from my Xoom using Tapatalk HD