has tmobile pushed a OTA for 6.0 yet and if so did it include a new radio? the radio that came with 6.0 on googles website was really bad for me and dropped a lot of calls so i had to stick with the 5.1.1 radio.
icebear8 said:
has tmobile pushed a OTA for 6.0 yet and if so did it include a new radio? the radio that came with 6.0 on googles website was really bad for me and dropped a lot of calls so i had to stick with the 5.1.1 radio.
Click to expand...
Click to collapse
the ota comes from google. but tmobile does have to aprove it. or you can manually flash the facyory image, since its the same thing this time around. has it been pushed? no idea, since im always flaahing custom builds and not stock.
http://www.tmonews.com/2015/11/t-mo...ate-approved-expected-to-start-arriving-soon/
Sent from my Nexus 6 using Tapatalk
simms22 said:
the ota comes from google. but tmobile does have to aprove it. or you can manually flash the facyory image, since its the same thing this time around. has it been pushed? no idea, since im always flaahing custom builds and not stock.
Click to expand...
Click to collapse
According to Des, the build IS different. The initial build from Google may have been unified, as you have continuously argued, but this doesn't seem the case now. That initial build was NOT unified, insofar as it hadn't been approved by all carriers collectively. I won't be one bit surprised if multiple builds happens again.
This of course, remains true, unless the 58X build Des mentioned is Google's new unified build. Or is a security update build. In which your argument would hold true.
I'll stand corrected if I'm wrong
Sent from my Nexus 6 using Tapatalk
Related
In order for me to go back, I'll have to sbf to 2.1u1 and lose many hours spent customizing my phone the way I want. I want it to be worth it, not just as a way to hide the fact that I voided the warranty.
Can someone list here an impromptu changelog of the diffs between 2.3.15 to 2.2 OTA? Thx.
Sent from my DROIDX using XDA App
A new possibly stronger locked bootloader is enough of a change for me not to update
Sent from my DROIDX using XDA App
gunkle said:
A new possibly stronger locked bootloader is enough of a change for me not to update
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
They just changed keys from the previous bootloader, not made it stronger from what I understand. It'll be a moot point once someone gets a 2.2 sbf. Still, I want to know what benefits, if any, there are between 2.3.15 (or just 2.2 leak) and the 2.2 OTA.
SirBrass said:
They just changed keys from the previous bootloader, not made it stronger from what I understand. It'll be a moot point once someone gets a 2.2 sbf. Still, I want to know what benefits, if any, there are between 2.3.15 (or just 2.2 leak) and the 2.2 OTA.
Click to expand...
Click to collapse
One benefit is to the OTA is the updated Kernal. As of now, we are still on the kernal from the first 2.2 leak.
What benefits does that bring?
EDIT: Tweet from the ever-astute P3Droid:
If you don't need the newest radio .07 or the newest kernel then I would not take the OTA, I refused it on my phone.
Click to expand...
Click to collapse
He lives in the same area (same county, same metro area) that I do, so if he doesn't need the newest radio then neither do I (unless the newest radio... and by that I assume he means the CDMA and phone radio(s), not the FM radio app, has better low-signal strength receive abilities). I'll hold off till birdman gives us that rooted OTA (and hopefully deodexed as well).
TBH also has promised something VERY nice on Friday (assuming this OTA hasn't knocked that something down into 2nd place priority for them).
A friend of mine who did the OTA said his kernel was still at 2.6.32.9 . the characters following that (which I think is just a build time stamp?) is different.
So I question whether its really a newer kernel, or just a newer compile/build of the same source?
Yeah I'm staying on 2.3.15 leak until at least we get 2.2 sbf. I don't really see a point of upgrading right now and putting myself at risk of having the phone bricked, since 2.1 sbf will be useless.
meshdub said:
Yeah I'm staying on 2.3.15 leak until at least we get 2.2 sbf. I don't really see a point of upgrading right now and putting myself at risk of having the phone bricked, since 2.1 sbf will be useless.
Click to expand...
Click to collapse
+1 main reason not to use the OTA
meshdub said:
Yeah I'm staying on 2.3.15 leak until at least we get 2.2 sbf. I don't really see a point of upgrading right now and putting myself at risk of having the phone bricked, since 2.1 sbf will be useless.
Click to expand...
Click to collapse
Overview video of the ota by droidlife revealed the android ver. to be 2.3.15. That is the official OTA. another reason to stay with leaked 2.3.15
Sent from my DROIDX using XDA App
I am running 5.8.894 and .. as far as I can tell, I am the only one. I have seen 5.7.894, and 7.893 .. but I am 5.8.894.
I have two questions.
1) What is the .8? Is it kernel?
2) Am I one of the first, or are my searching skills just way off.
A couple observations as well. I did a full stock restore, applied the 4EVER Root, did a cheesecake to the staging servers of the big M, applied it and I still have root.
Camera is WAAAAAYYYYY Faster too. Hopefully it fixes the radios issues as well and the application vanishing.
So you went out and grabbed this OTA version?
Sounds like it might be the "official" Moto soak test OTA. That is allegedly (It IS Moto after all) about to or already circulating to testers.
How is it running? Impact on battery usage?
Thanks,
RMD
I just installed so I don't really have anything to say about it yet.
So you're saying this is the "official" OTA that I picked up?
I'm guessing that it MAY BE THE OFFICIAL OTA. No way of knowing for certain yet.
Since you grabbed it off an "M" server, that would be my guess.
I haven't yet seen any reports of folks involved in the soak test reporting what version the OTA results in on their handsets.
Keep us posted.
Thanks,
RMD
blocatan said:
I am running 5.8.894 and .. as far as I can tell, I am the only one. I have seen 5.7.894, and 7.893 .. but I am 5.8.894.
I have two questions.
1) What is the .8? Is it kernel?
2) Am I one of the first, or are my searching skills just way off.
A couple observations as well. I did a full stock restore, applied the 4EVER Root, did a cheesecake to the staging servers of the big M, applied it and I still have root.
Camera is WAAAAAYYYYY Faster too. Hopefully it fixes the radios issues as well and the application vanishing.
Click to expand...
Click to collapse
was this update pushed to your phone or did you manually download it from somewhere and install it yourself?
I think he snagged it using cheesecake off a server at Moto.
RMD
rduckwor said:
I think he snagged it using cheesecake off a server at Moto.
RMD
Click to expand...
Click to collapse
Thats a big 10-FOR
yeah my bad, sorry for not reading your original post more carefully
I think it's interesting that this update doesn't block perma root when the first .894 update did. Does this mean Motorola is taking steps in the right direction or is it something as simple as they forgot to put it in this version? Who knows, I'm hoping it's the former though.
I was thinking the very same thing? Moto grows a heart? Or maybe a brain?
RMD
which server from cheesecake?
im going crazy trying to look for it :/
qubanaso said:
which server from cheesecake?
im going crazy trying to look for it :/
Click to expand...
Click to collapse
master-sdc100.blurdev.com under Staging is where I picked it up.
Did you update from stock or from 5.7.893? I'm checking the servers via cheesecake and I cant seem to find it (im on 5.7.893).
P3 has tweeted not to take it that it patches root.
Keep us posted if u have data issues!
Sent from my DROID BIONIC using Tapatalk
were u using wifi or on data?
Sent from my DROID BIONIC using xda premium
So i got tired of waiting for a response so I decided to follow the OPs instructions....I wiped my system back to 886, rooted/forever rooted and launched cheesecake. I saw 5.8.894 on master-sdc100.blurdev.com and attempted to apply the update.
I got an error that the update failed to go through.
yea i had the same problem trying to update with the forever root im currently running 5.5.893
Sent from my DROID BIONIC using xda premium
Haven't seen the update in cheesecake app. Would like to know if anything is different
Sent from my DROID BIONIC using Tapatalk
So i tried to go back to stock without root and apply the update and it still fails on the validation. I guess this means we are off the upgrade path till a leaked fxz appears.
edit: to find the update you need to have a stock system image, for it to install it looks like you need to be 100% stock (bootloader/kernel/radios as well as system).
I just bought my N6 yesterday from Verizon and I spent some time last night reading up on things but I would like some further confirmation from some experienced users. So I've read a few posts where some have bricked their devices by flashing cm12 while on 5.1. The Verizon N6 came with 5.1 already so is it advisable to not flash cm12? And while we're on that topic, is there anything else you should not do while on 5.1? I was looking through all the roms/kernels and some are not updated yet. So if I'm on 5.1, is it ok to flash a rom/kernel that is not 5.1? And the encryption stuff is confusing as well. I'm sure the device will be a little faster with encryption disabled but is it really that big of a difference? I apologize for being a total noob when it comes to Nexus devices. I've never owned one, I've always had HTC or Samsung. I haven't ran cm since I had my HTC Rezound lol so I'm anxious to run it again. So if someone could please tell me what roms I can and cannot flash and just give me some general advice about this phone I would greatly appreciate it.
highdro said:
I just bought my N6 yesterday from Verizon and I spent some time last night reading up on things but I would like some further confirmation from some experienced users. So I've read a few posts where some have bricked their devices by flashing cm12 while on 5.1. The Verizon N6 came with 5.1 already so is it advisable to not flash cm12? And while we're on that topic, is there anything else you should not do while on 5.1? I was looking through all the roms/kernels and some are not updated yet. So if I'm on 5.1, is it ok to flash a rom/kernel that is not 5.1? And the encryption stuff is confusing as well. I'm sure the device will be a little faster with encryption disabled but is it really that big of a difference? I apologize for being a total noob when it comes to Nexus devices. I've never owned one, I've always had HTC or Samsung. I haven't ran cm since I had my HTC Rezound lol so I'm anxious to run it again. So if someone could please tell me what roms I can and cannot flash and just give me some general advice about this phone I would greatly appreciate it.
Click to expand...
Click to collapse
it is NOT ok to flash a rom for any other version than what youre on. so dont flash any 5.0.2 roms or kernels if youre on 5.1. (exception being the radio. i believe that can be swapped without incident, but youll have to do some extensive reading in the General and Development sections)
personally im on 5.0.2 for now until chroma gets realllll shiny and polished
i havent been encrypted since my first bootup, but my understanding any lag associated with that has basically been resolved
shelooga said:
it is NOT ok to flash a rom for any other version than what youre on. so dont flash any 5.0.2 roms or kernels if youre on 5.1. (exception being the radio. i believe that can be swapped without incident, but youll have to do some extensive reading in the General and Development sections)
personally im on 5.0.2 for now until chroma gets realllll shiny and polished
i havent been encrypted since my first bootup, but my understanding any lag associated with that has basically been resolved
Click to expand...
Click to collapse
So that could be why people are messing their phones up? By flashing cm12 while on 5.1? I thought I read somewhere that cm hasn't updated to 5.1 yet. Thanks for the info. I didn't think I could flash anything other than 5.1 but this is not a familiar device to me so it could've been different.
shelooga said:
it is NOT ok to flash a rom for any other version than what youre on. so dont flash any 5.0.2 roms or kernels if youre on 5.1. (exception being the radio. i believe that can be swapped without incident, but youll have to do some extensive reading in the General and Development sections)
personally im on 5.0.2 for now until chroma gets realllll shiny and polished
i havent been encrypted since my first bootup, but my understanding any lag associated with that has basically been resolved
Click to expand...
Click to collapse
Simply inaccurate. You can run 5.0.2 roms after updating to 5.1 without issue. Just don't touch the bootloader. You cannot downgrade the bootloader from 5.1.
highdro said:
So that could be why people are messing their phones up? By flashing cm12 while on 5.1? I thought I read somewhere that cm hasn't updated to 5.1 yet. Thanks for the info. I didn't think I could flash anything other than 5.1 but this is not a familiar device to me so it could've been different.
Click to expand...
Click to collapse
The issue with CM was that they had a brute force bootloader flashing script built in. This has been removed.
akellar said:
Simply inaccurate. You can run 5.0.2 roms after updating to 5.1 without issue. Just don't touch the bootloader. You cannot downgrade the bootloader from 5.1.
The issue with CM was that they had a brute force bootloader flashing script built in. This has been removed.
Click to expand...
Click to collapse
So the only ROM that had the bootloader included was cm? So I can flash anything I want now? Thanks for clearing things up man.
highdro said:
So the only ROM that had the bootloader included was cm? So I can flash anything I want now? Thanks for clearing things up man.
Click to expand...
Click to collapse
That I'm aware of, yes
Sent from my Nexus 6 using XDA Free mobile app
highdro said:
So the only ROM that had the bootloader included was cm? So I can flash anything I want now? Thanks for clearing things up man.
Click to expand...
Click to collapse
Anything that is 5.1 yes, I would stick to ROMs based on the "E" build of 5.1, since that's what you're phone came on. Most ROMs are in process of updating to E.
akellar said:
Simply inaccurate. You can run 5.0.2 roms after updating to 5.1 without issue. Just don't touch the bootloader. You cannot downgrade the bootloader from 5.1.
The issue with CM was that they had a brute force bootloader flashing script built in. This has been removed.
Click to expand...
Click to collapse
my bad
I'm currently on Krypton 1.4 (Kitkat 4.4.4) and this is pretty much stock 4.4.4 with the carrier bloat removed and some additional tweaks. I have not seen 5.1.1 ROM in a similar fashion, am I overlooking something in the development section or since 5.1.1 was recently OTA I need to exercise more patience? Thank you!
There is no VZW 5.x OTA, so that's probably why you've not seen anything. Maybe wait until there is an actual update before asking again?
Sent from my Nexus 6
meber said:
I'm currently on Krypton 1.4 (Kitkat 4.4.4) and this is pretty much stock 4.4.4 with the carrier bloat removed and some additional tweaks. I have not seen 5.1.1 ROM in a similar fashion, am I overlooking something in the development section or since 5.1.1 was recently OTA I need to exercise more patience? Thank you!
Click to expand...
Click to collapse
Exercise more patience.
5.1 is still going through Test Drive and Soak tests, it hasn't been finally pushed yet to anyone... The full push MIGHT happen next week -> https://plus.google.com/+DavidSchuster/posts/ci1UAEv2oYB
I'm not sure how long it will then take to make a custom rom built on 5.1 after it hits our phones. If they'll need to wait for the SBF files, or what...
And since you have a Non-Dev Verizon device, you might want to see -> http://forum.xda-developers.com/moto-x/general/lollipop-warning-unlocked-via-sunshine-t3114428 But if you're not planning on taking an OTA, then you should be relatively ok.
Hi all I have been searching on the newest firmware for the note 4 was going to install but I get mixed info one which is the newest to install I have baseband ANK4 cannot that be updated to COG2 or DOFC which is the newest? Thank you searched for answer but get mixed info
Cog2 and cod6 are both 5.0.1 firmware. One of these is, cant remember which, has the stagefright patch.
Dog1 is 5.1.1
ctrlaltdeln said:
Cog2 and cod6 are both 5.0.1 firmware. One of these is, cant remember which, has the stagefright patch.
Dog1 is 5.1.1
Click to expand...
Click to collapse
Ctrlaltdeln is correct.
Expanding upon his response.
These are for NON T3
U2DOK2 bumps 5.0.1 to 5.1.1
COG2 has stagefright running 5.0.1
COD6 is first Lollipop rollout with 5.0.1
These are for T3
U1DOK2 is 5.1.1
DOG1 is 5.1.1
5.1.1 has been released for NON T3 version on 11/30/15
Andel7539 said:
Ctrlaltdeln is correct.
Expanding upon his response.
These are for NON T3
COG2 has stagefright running 5.0.1
COD6 is first Lollipop rollout with 5.0.1
These are for T3
DOG1 is 5.1.1
5.1.1 has not been released for NON T3 version.
Click to expand...
Click to collapse
Might want to amend that. DOK2 is the first 5.1.1 build for the 910T and it came out last night / this morning.
Sent from my SM-N910T using Tapatalk
vprasad1 said:
Might want to amend that. DOK2 is the first 5.1.1 build for the 910T and it came out last night / this morning.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Amended.
Andel7539 said:
Amended.
Click to expand...
Click to collapse
Reading through the DOK2 thread, it's also available for the T3.
Sent from my SM-N910T using Tapatalk
DOK2 is the newest firwame, you can download it and update over Odin
Is no one concerned that once you flash DOK2 that you can't currently go back to any previous version? What happens if you decide you don't like any of the roms with DOK2 and want to go back, to Firekat for example?
phoneturf said:
Is no one concerned that once you flash DOK2 that you can't currently go back to any previous version? What happens if you decide you don't like any of the roms with DOK2 and want to go back, to Firekat for example?
Click to expand...
Click to collapse
No.
1. N910T3 users never had that option to try Firekat
2. N910T users have had a few months of 5.1.1 ROM ports from Sprint 5.1.1, and some are still available to determine whether they're willing to make the permanent leap.
Sent from my SM-N910T using Tapatalk
phoneturf said:
Is no one concerned that once you flash DOK2 that you can't currently go back to any previous version? What happens if you decide you don't like any of the roms with DOK2 and want to go back, to Firekat for example?
Click to expand...
Click to collapse
I installed the modem and baseband, doesn't matter about 'going back' cause I use an awesome AOSP ROM.
The real question is if you're happy with the ROM you are on, why switch?
Sent from my SM-N910T using Tapatalk
phoneturf said:
Is no one concerned that once you flash DOK2 that you can't currently go back to any previous version? What happens if you decide you don't like any of the roms with DOK2 and want to go back, to Firekat for example?
Click to expand...
Click to collapse
I'm... potentially concerned. DOK2 seems fine and all, but apparently going forward there will be "no ability to downgrade due to updated security policies". OK, makes some sense, and the Note 4 receives updates so infrequently it's (sort of) less of an issue than with other devices, but what is this "security policy" accomplishing beyond removing user choice/control? Not every firmware version is flawless... for example, let's say DOK...6 reduces SOT by 2 hrs and drops WIFI connections every hour? Whatever, DOK2 just happens to be a much better user experience... too bad, enjoy your bugged firmware until the next update (that is, potentially several months or maybe even never).
Further, I really don't think "regular users" downgrading their firmware to their detriment is a problem... or something that even happens. This policy is really only something that is likely to affect "power users" detrimentally. I mean, I'm all for device security and everything, but it really seems (to me) that anyone who would potentially be considering downgrading their firmware would be quite capable or weighing the pros and cons of doing so.
So there's my essay on the topic.... to summarize, not a negative issue now, but potentially something that could become one, for no discernible reason, in the future.