5.7.893 radio/kernel

Discussion in 'Droid Bionic Hacks' started by dags5000, Nov 25, 2011.

  1. welsalex

    welsalex Member

    Joined:
    Oct 20, 2011
    Messages:
    559
    Likes Received:
    11
    Trophy Points:
    18
    Location:
    Austin, TX
    Ratings:
    +11
    Oh please share all your findings!!

    Sent from my DROID BIONIC using DroidForums
     
  2. Psychlone

    Psychlone Member

    Joined:
    Dec 8, 2009
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    I don't have anything of importance to add to this thread aside from setting something straight:

    First, I need to say that this isn't my first rodeo. I was there on opening day for the original Droid and several others as well, and I've been doing non-official updates for years now.

    I don't understand why everyone is all up in arms about these updates. Why must you worry about rolling back to stock to get the latest OTA update? If that's the general consensus here, then you guys haven't been doing this for long...because you're missing a crucial point.

    EVERYONE that applied an update that wasn't official OTA should have already understood the consequences and understood that they were literally signing away their warranty and rights for an OTA patch. Nowhere, in any update did it mention that you would be able to still be on the official update path - it's never worked like that in the past, and it's not going to change anytime soon.
    There were a few people a few pages back that had mentioned "what a PR fail" it would be to find all these people that updated their phones all of a sudden have no update path... Well, it's not Motorola's fault - it's not Verizon's fault, and it's not the update leaker's fault either. No one is going to suffer from bad PR from a bunch of people that jumped the gun and installed a leaked update that wasn't in the official update channel. It's YOUR fault, and you should have understood the consequences before flashing. There's no way to hold anyone else accountable.

    That being said, the reason we all update our phones is because we want the best, fastest phone possible where everything works as intended (or better!). We have taken OURSELVES out of the official upgrade path - to have that new, shiny ROM before everyone else gets it.
    That also means that our devs will continue to be on top of it as new updates and information leaks. FWIW, even though everyone in this thread may be out of the official update path, you've got to know that SOMEONE is going to leak updates every time they're made available from now until years after the phone has served it's purpose.

    If you look back at the original Droid, it wasn't long before non-official updates started coming out with new kernels and radios already baked into custom ROMs. Once you flashed one of those, there was never a need to go back to stock - because there was ALWAYS something newer and faster that was getting ready to come out the next week, and if you look in the original Droid forum subsection, you'll see that this is STILL the case, even though the hardware has long since been surpassed by the abilities of the software they're putting on it.


    All in all, everyone should just hang tight. There's no need to get our panties all up in a bunch over an update - because it's not going to matter if you get it from OTA or from one of our devs... you're still going to get it.
    It's looking like there's a possibility that those that didn't jump the gun and flash a non-official update might get the update before the rest do, but that's yet to be seen, and even IF that's the case, I don't give it a full 24 hours before one of our devs figures out a way to push it to everyone else. Look at how long it took to root our brand new phone... DAY 0.

    Give it a rest guys. Unless you really, really, really want to be stock, there's no need to go backwards.



    Psychlone
     
  3. mlapaglia

    mlapaglia Member

    Joined:
    Nov 24, 2011
    Messages:
    46
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    Sorry, my phone is utterly useless right now with data drops and BSODs. The 894 update has been up for a few days now, and I need a phone that works.
     
  4. dstreng

    dstreng Member

    Joined:
    Sep 22, 2010
    Messages:
    174
    Likes Received:
    1
    Trophy Points:
    18
    Ratings:
    +1
    if anyone can find the .999 file please send it my way. im still on 5.5.893 so i wanna try out this method.
     
  5. MonkeyTime

    MonkeyTime Member

    Joined:
    Nov 21, 2009
    Messages:
    239
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    East Troy, WI
    Ratings:
    +0
    If they could post a link, that would be great I'm interested too.....
     
  6. thejacked1

    thejacked1 Member

    Joined:
    Sep 26, 2011
    Messages:
    81
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    So maybe I got this wrong then?? I was under the impression that a kernel, or radio, could NOT be baked into any ROM as long as the bootloader is locked?? Because of this, devs CAN include new software (to support the radio/kernel update) in any newer ROM...but not the actual kernel. Soooo a user WOULD have to revert back to stock, to receive the update, to get that kernel or radio. I could be wrong though, I was once before.

    Sent from my DROID BIONIC using DroidForums
     
  7. thejacked1

    thejacked1 Member

    Joined:
    Sep 26, 2011
    Messages:
    81
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    And.....the way I see it, I owe vzw d!kc. I feel NO remorse in saying I'm only a cpo away from any update....regardless of what I'm running right now ;-)

    Sent from my DROID BIONIC using DroidForums
     
  8. Psychlone

    Psychlone Member

    Joined:
    Dec 8, 2009
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    No, you've got it right - as long as the bootloader is locked down - AND our devs haven't figured out a workaround/bypass, then we're stuck with whatever kernels and radios are available.
    But, on the old D1, it didn't take too long for it all to be bypassed and for the devs to follow, baking-in their own kernels in their custom ROMs.

    Granted, the Bionic has been out for a bit now, but it's still WAAAAY to early to be complaining about a lack of updates... the D1 didn't get them for several months after it's release, and this isn't going to be different just because it *was* their new flagship.


    I probably should say that I'm personally in no rush because I'm one of the "lucky ones" that doesn't have any issues - from stock up then back to stock, I've not experienced anything that most of you have complained about with the exception of the speaker jack noise. I updated to ReBlurred until 2.0 came out and then stopped because I had inside info that the new OTA was going to be coming out for a soak test soon, so with a complete revert back to bloated/stock, I'm in line for the update via soak (which I signed up for).

    But all things being equal, it doesn't really matter - either way, we're ALL going to be getting the update. I know for certain that at least one dev will conquer whatever obstacles the new OTA brings and will release it to the modding masses.


    For those that are upset about their device not working properly, I feel for you - I really do, but you also need to know that you're not complaining in the right places. Moto has their own channels that need to be polled for them to even be aware of problems. Not saying that you shouldn't post up your problems and potential fixes, but to go over and over like some of the threads in this forum have is really putting a damper on the real advice in areas that CAN be fixed. Motorola doesn't visit third-party forums, they have their own channels for that.

    Anyone that's really upset about their circumstances - I suggest jumping ship and finding something else that works for you. But pay attention to what you're jumping ship to - the Razr isn't without it's problems, and neither is the S2.


    Good luck guys!
    Psychlone
     
  9. dags5000

    dags5000 Member

    Joined:
    Sep 28, 2011
    Messages:
    202
    Likes Received:
    5
    Trophy Points:
    18
    Ratings:
    +5
    Yes.we know what we did and are responsible for it. The diff here from the OG which I had of course is the locked bootloader. Not being able to update the kernel say if ICS officially comes to the bionic would be disappointing. That is all. I have every intention of using custom roms. For ICS there are changes to the kernel that we would greatly benefit from to get the full on experience. That is why I am searching for a way back and is the only reason. Being doubtful the bootloader will ever be unlocked outside of some other leak there is only so much one can do with custom roms.

    Anyways this thread is different from the usual "get.me back to stock" fears because of the crappy bootloader situation. I know devs will have roms with all the latest software updates. I myself knew of this but wasnt thinking when I applied the leaked update and foolishly thought it was the final official one. There are.many that are looking for a solution for this so I dint see this as a wasted thread.

    Sent from my DROID BIONIC using DroidForums
     
  10. 318Droid

    318Droid Member

    Joined:
    Aug 10, 2011
    Messages:
    120
    Likes Received:
    5
    Trophy Points:
    18
    Location:
    Louisiana
    Ratings:
    +5
    Well wish me luck hopefully I can get the file from these guys at Verizon. On my way there now

    Sent from my DROID BIONIC using DroidForums
     
  11. dags5000

    dags5000 Member

    Joined:
    Sep 28, 2011
    Messages:
    202
    Likes Received:
    5
    Trophy Points:
    18
    Ratings:
    +5
    good luck. let us know what happens!
     
  12. 318Droid

    318Droid Member

    Joined:
    Aug 10, 2011
    Messages:
    120
    Likes Received:
    5
    Trophy Points:
    18
    Location:
    Louisiana
    Ratings:
    +5
    Ok i went in and talked to my buddy Jon...He said that they have this flashing computer in the back and that it does more to the phone than what a factory reset would do...BUT, he couldnt guarantee that the radio/kernal would be changed since he never actually paid attention to the radio/kernal before or after that process. This was my lunch break and I didnt have much time so I didnt get it did since he said it would take virtually 20 mins or so to do the process. He would have to put the phone to it boot img or something (recovery basically) for the process to work....I told him i didnt have that kind of time because of my lunch so I told him that i would be back later...But while i was in there i took a pic of a store bionic "about phone" page and this is what i get below. Will post picture on my next 15 min break here around 2.

    System Version:
    5.9.991.XT875.Verizon.en.US

    Model number
    Droid Bionic

    Android version
    2.3.4

    Baseband version
    CDMA_N_03.1C.50R ltedc_u_05.15.00

    Webtop version
    WT-1.3.0-105_DBN-1

    Kernal Version
    2.6.35.7-g790a33c
    hpn683@il93lnxdroid29 #1

    Build Number
    5.5.1_84_DBN-91-LaunchKit

    ERI version
    5

    PRL version
    15075
     
Search tags for this page

droid bionic radio.zip

,
eri version not available
,
gingerbread baseband.zip
,
how to flash a droid bionic radio
,
how to get rid of the launchkit build number on droid bionic