On Google developer sight. MOB30I. Link below.
https://dl.google.com/dl/android/aosp/shamu-mob30i-factory-21357b09.tgz
Edit: MOB30I includes new bootloader.
Edit 2: Two new images posted today. MMB30G also. Not a clue as to why...
Looks like they also posted MMB30G. Any idea in the difference between the two?
Encryptable boot/kernel IMG for MOB30I:
https://www.androidfilehost.com/?fid=24530981327208519
MrBrady said:
Looks like they also posted MMB30G. Any idea in the difference between the two?
Click to expand...
Click to collapse
MOB30G was posted about April 10th. MOB30I was posted today and is newer, includes May security updates and new bootloader.
Edit: MOD30D was posted mid April. Above information is incorrect.
cam30era said:
MOB30G was posted about April 10th. MOB30I was posted today and is newer, includes May security updates and new bootloader.
Click to expand...
Click to collapse
The one posted on mid april was MOB30D. I'm pretty sure two new ones were posted today.
blanco2701 said:
The one posted on mid april was MOB30D. I'm pretty sure two new ones were posted today.
Click to expand...
Click to collapse
You are correct. Two updates posted today. I do not know why. With no info posted by Google, they are confusing us.....
cam30era said:
You are correct. Two updates posted today. I do not know why. With no info posted by Google, they are confusing us.....
Click to expand...
Click to collapse
Same radio of 05.34 as Preview 2 of N.
cam30era said:
You are correct. Two updates posted today. I do not know why. With no info posted by Google, they are confusing us.....
Click to expand...
Click to collapse
Flashed the MOB30I image, hope i made the correct choice
gee2012 said:
Flashed the MOB30I image, hope i made the correct choice
Click to expand...
Click to collapse
I did the same thing. Honestly, I do not understand why Google posts two images, simultaneously, and gives us no information on what's different. At least last year, with all of the confusion on the multiple images, they posted a little bit of direction....
gee2012 said:
Flashed the MOB30I image, hope i made the correct choice
Click to expand...
Click to collapse
Please let us know if there is something new, or just the security update.
gothy.gothy said:
Please let us know if there is something new, or just the security update.
Click to expand...
Click to collapse
Only the security update + new bootloader.
gothy.gothy said:
Please let us know if there is something new, or just the security update.
Click to expand...
Click to collapse
New bootloader , boot.img and radio (same as the 2nd N preview) it seems if i`am correct. From what i read here and there one of the images is supposedly a T-Mobile version.
gee2012 said:
New bootloader , boot.img and radio (same as the 2nd N preview) it seems if i`am correct.
Click to expand...
Click to collapse
The "new" radio was included previously in MOD30D, about April 11th. No need to flash it for anyone running that version.
cam30era said:
The "new" radio was included previously in MOD30D, about April 11th. No need to flash it for anyone running that version.
Click to expand...
Click to collapse
Aah oke, i stand corrected
Yup, It's my understanding that MOB contains a new radio vs MMB. They will be updating MMB until all the carriers get around to approving the new radio. Because I have an at&t sim dropped in my nexus 6, it will most likely OTA to MMB30G(with May security updates). This knowing at&t never gets in a hurry when it comes to approvals.
phoenixms said:
Yup, It's my understanding that MOB contains a new radio vs MMB. They will be updating MMB until all the carriers get around to approving the new radio. Because I have an at&t sim dropped in my nexus 6, it will most likely OTA to MMB30G(with May security updates). This knowing at&t never gets in a hurry when it comes to approvals.
Click to expand...
Click to collapse
Good info. I haven't heard that previously. For the record, I just flashed the MOB30I on my VZW Nexus 6 and it's working fine. Did the whole fastboot flash-all deal.
will wait for the official changelogs.. hopefully
reyscott1968 said:
will wait for the official changelogs.. hopefully
Click to expand...
Click to collapse
There's this: http://source.android.com/security/bulletin/2016-05-01.html
https://source.android.com/source/build-numbers.html
MOB30D android-6.0.1_r30 Marshmallow Nexus 5, Nexus 6, Nexus 7 (flo/deb), Nexus 9 (volantis/volantisg), Nexus Player, and Android One
MMB29X android-6.0.1_r20 Marshmallow Nexus 5, Nexus 6, Nexus 7 (deb), Nexus 9 (volantisg)
its probably the same thing. consolidation.
So MOBxxx is newer than MMBxxx, because of r30 against r20?
But, why there are two updates, and not only MOBxxx?
Regards.
Sent from Nexus 6
Related
Those who are using Indian soak test before and now using official release in India.... Do you notice any changes?
Sent from my XT1068/69 using XDA Premium 4 mobile app
Soak Testers didn't get the final OTA and will not get it. Reason is, the final OTA rolled out today is the same one soak testers got. They just got it a little early. You can see in the screenshots that everything under About Phone is same in soak test version and final version.
So does this in theory then mean that those of us who installed the captured soak test from the other thread will not need to use any other captures in the future and be able to use the ota update just fine without any chances of bricks etc
bla7e said:
So does this in theory then mean that those of us who installed the captured soak test from the other thread will not need to use any other captures in the future and be able to use the ota update just fine without any chances of bricks etc
Click to expand...
Click to collapse
Correct. It is like we got the final OTA a little early.
Sri2702 said:
Correct. It is like we got the final OTA a little early.
Click to expand...
Click to collapse
Cool so we won't have any worries about our phones bricking if we do an ota as is then I guess? Then that puts me at ease of mind.
bla7e said:
Cool so we won't have any worries about our phones bricking if we do an ota as is then I guess? Then that puts me at ease of mind.
Click to expand...
Click to collapse
What do you mean by "we do an ota as is"?
Sri2702 said:
What do you mean by "we do an ota as is"?
Click to expand...
Click to collapse
I mean we'll be able to download ota's without worries of getting our phones bricked because of it being from soak. I remember reading the other day someone was talking about how if we want to be able to use ota we'd have to use a stable capture first in order to be able to use ota. It seems that won't be an issue though since soak and stable are the same with just different release dates so we shouldn't have to worry about that right? Sorry for being silly here. I'm not exactly an ape man when it comes to tech but I'm not feeling the need to fiddle around with roms and bootloaders on this phone when I shouldn't really need to
bla7e said:
I mean we'll be able to download ota's without worries of getting our phones bricked because of it being from soak. I remember reading the other day someone was talking about how if we want to be able to use ota we'd have to use a stable capture first in order to be able to use ota. It seems that won't be an issue though since soak and stable are the same with just different release dates so we shouldn't have to worry about that right? Sorry for being silly here. I'm not exactly an ape man when it comes to tech but I'm not feeling the need to fiddle around with roms and bootloaders on this phone when I shouldn't really need to
Click to expand...
Click to collapse
Well, it was me who said that the other day. That time the official update hadn't rolled out and we thought it would be a newer system version. But, now that it's released; we now know that it is the exact same OTA, so no problems for future updates either. It's like we never installed soak.
Sri2702 said:
Well, it was me who said that the other day. That time the official update hadn't rolled out and we thought it would be a newer system version. But, now that it's released; we now know that it is the exact same OTA, so no problems for future updates either. It's like we never installed soak.
Click to expand...
Click to collapse
Yea i suspected something like that was going on when I saw that new thread about the stable and people were saying everything's exactly the same but just wanted some sort of confirmation. Now the only thing that I don't know if it'll affect anything in the future is that my build number on 4.4.4 was kxb now it's lxb (unless k stands for kitkat and l for lolipop lol. dunno) but i don't think it would be a problem since the system version has only the numbers changed and everything else is as it was on kitkat. Seems like the indian release works on european xt1068's as well contrary to what I read some people were saying but I guess it depends on some things...
bla7e said:
Yea i suspected something like that was going on when I saw that new thread about the stable and people were saying everything's exactly the same but just wanted some sort of confirmation. Now the only thing that I don't know if it'll affect anything in the future is that my build number on 4.4.4 was kxb now it's lxb (unless k stands for kitkat and l for lolipop lol. dunno) but i don't think it would be a problem since the system version has only the numbers changed and everything else is as it was on kitkat. Seems like the indian release works on european xt1068's as well contrary to what I read some people were saying but I guess it depends on some things...
Click to expand...
Click to collapse
Funny, but you're right. The Build number on KitKat was "KXB21.85-23" on mine, but now it's "LXB22.46-28".
Sri2702 said:
Funny, but you're right. The Build number on KitKat was "KXB21.85-23" on mine, but now it's "LXB22.46-28".
Click to expand...
Click to collapse
Well that pretty much solved all questions I had regarding lolipop on my moto g. Now the only mystery that remains is if the indian update works just fine when you install it on a eu moto g (well you need to manually install from recovery doe doesn't detect it in the ota screen) why is the eu xt1068's update nowhere to be talked about. All I've seen is india brazil and so on but eu is so silent that even babies can sleep
bla7e said:
Well that pretty much solved all questions I had regarding lolipop on my moto g. Now the only mystery that remains is if the indian update works just fine when you install it on a eu moto g (well you need to manually install from recovery doe doesn't detect it in the ota screen) why is the eu xt1068's update nowhere to be talked about. All I've seen is india brazil and so on but eu is so silent that even babies can sleep
Click to expand...
Click to collapse
That´s a mystery for sure!
The only difference between the indian and the european XT1068 is the fact, that the indian version has 16 gb of memory,european model has 8gb.
But there must be something more that differs! In europe even a soaktest is rumored,surveys were sent,so everthing looks like we have to wait in europe for a few more days/weeks.
But why? In another thread I considered that Motorola is afraid of being taken to court or something by european users if something doesn´t work right. European laws are tough. Isn´t that a bit far out?
Or are there any technical differences between these models which are barely known?
Wolfcity said:
That´s a mystery for sure!
The only difference between the indian and the european XT1068 is the fact, that the indian version has 16 gb of memory,european model has 8gb.
But there must be something more that differs! In europe even a soaktest is rumored,surveys were sent,so everthing looks like we have to wait in europe for a few more days/weeks.
But why? In another thread I considered that Motorola is afraid of being taken to court or something by european users if something doesn´t work right. European laws are tough. Isn´t that a bit far out?
Or are there any technical differences between these models which are barely known?
Click to expand...
Click to collapse
Aside from the ram I highly doubt there's any real difference since when I got mine in the first few days of fiddling around it had the hindi, korean and pinyin keyboards which i disabled so I don't think that would be the case....I mean why would most eu phones need these inputs from the get go. As far as laws go I can't really see much reasoning there either since it's a 130-50eu phone so they can't really have much to complain and unless it somehow magically bricks the device I doubt there would be many if any at all issues...Dunno doe. I'm not motorola so i have no idea what's going on through their heads but it's just kinda silly to me considering that everything's running fine on mine at least without any factory resets or anything....could be just me doe. On another note I think one of my little gripes about lollipop is that it doesn't hide the signal bar for my secondary sim when it's inactive and just shows it. Is this just for me or does everyone have that cuz I didn't pay attention to that on screenshots the last few days
Did some one backed up latest Indian Lollipop rolled on 23 Jan in TWRP in recovery mode and uploaded somewhere? Please share.
cmahendra said:
Did some one backed up latest Indian Lollipop rolled on 23 Jan in TWRP in recovery mode and uploaded somewhere? Please share.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t3002426
Sri2702 said:
http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t3002426
Click to expand...
Click to collapse
The link is old version uploaded on 14 January. I am asking about 23 January version with new Baseband ver 1032.3105
cmahendra said:
The link is old version uploaded on 14 January. I am asking about 23 January version with new Baseband ver 1032.3105
Click to expand...
Click to collapse
The 14th Jan one does have 1032.3105.
EDIT: Looking at a screenshot in that thread, it doesn't have the above mentioned version.
Weird though, I have installed the same version, but using a .zip captured by one soak tester. How could the version be different, when the update is same?
Sri2702 said:
The 14th Jan one does have 1032.3105.
EDIT: Looking at a screenshot in that thread, it doesn't have the above mentioned version.
Weird though, I have installed the same version, but using a .zip captured by one soak tester. How could the version be different, when the update is same?
Click to expand...
Click to collapse
Yes, weird but there is reason. MD5 of old link and new capture matched perfect. Update in link by you and new both are same. Looks like Motorola fooled everyone and rolled same update again.
Anyways! Can anyone share TWRP backup of this version?
some apps bugs ..
Some apps like fifa 15 ut and some others are not supported for locked device and while installing from play store it showed error 505.
Stop making such threads...use the search option instead.
Hey all, I just used my invite to buy a oneplus 2, has anyone else ordered one? how long does it take to arrive?
also is there an ETA on my shareable invites? I have googled around but I cant find anything as of yet.
cheers
@Jonnyn93 - Congratulations. Once you receive your unit and have updated to the latest version of OxygenOS. Can you please flash TWRP, wipe, then create a backup zip and post a link to it here. Those of us with the Chinese handset flashed with OxygenOS are stuck on the pre-release firmware (OnePlus2Oxygen_14_OTA_002_all_1507251956).
Oneplus have some info on shipping on their website. Not sure if this applies to the Oneplus 2 though.
https://oneplus.net/dk/support/topic/shipping
khr0n0s said:
@Jonnyn93 - Congratulations. Once you receive your unit and have updated to the latest version of OxygenOS. Can you please flash TWRP, wipe, then create a backup zip and post a link to it here. Those of us with the Chinese handset flashed with OxygenOS are stuck on the pre-release firmware (OnePlus2Oxygen_14_OTA_002_all_1507251956).
Oneplus have some info on shipping on their website. Not sure if this applies to the Oneplus 2 though.
https://oneplus.net/dk/support/topic/shipping
Click to expand...
Click to collapse
I'll do my best mate haha. It still says processing, hopefully it will get shipped today!
khr0n0s said:
@Jonnyn93 - Congratulations. Once you receive your unit and have updated to the latest version of OxygenOS. Can you please flash TWRP, wipe, then create a backup zip and post a link to it here. Those of us with the Chinese handset flashed with OxygenOS are stuck on the pre-release firmware (OnePlus2Oxygen_14_OTA_002_all_1507251956).
Oneplus have some info on shipping on their website. Not sure if this applies to the Oneplus 2 though.
https://oneplus.net/dk/support/topic/shipping
Click to expand...
Click to collapse
Huh? isn't that's the only version of OxygenOS anyway iirc
Roxas598 said:
Huh? isn't that's the only version of OxygenOS anyway iirc
Click to expand...
Click to collapse
heh, no. There was a huge OTA update last week which fixed a lot of bugs and improved performance, battery life and the finger print reader. Check out this video for the build no (150807):
Oh **** seriously? And I'm guessing OTA is out of the question? Well **** I didn't know the current t build online was a prebuild
Roxas598 said:
Oh **** seriously? And I'm guessing OTA is out of the question? Well **** I didn't know the current t build online was a prebuild
Click to expand...
Click to collapse
It was online even before the OPT was released in China (4th of August). I have tried the HydrogenOS OTA update. It has quite a few bug fixes and improvements. It's a shame that HydrogenOS is so awful.
khr0n0s said:
It was online even before the OPT was released in China (4th of August). I have tried the HydrogenOS OTA update. It has quite a few bug fixes and improvements. It's a shame that HydrogenOS is so awful.
Click to expand...
Click to collapse
With all the devices out there someone should have uploaded the new one? Actually come to think of it why haven't OP uploaded the factory image yet?
Slightly miffed the pre-release can't be OTA'd
Roxas598 said:
With all the devices out there someone should have uploaded the new one? Actually come to think of it why haven't OP uploaded the factory image yet?
Slightly miffed the pre-release can't be OTA'd
Click to expand...
Click to collapse
I'm not sure. That is a good question. I was just talking with someone who has an international OPT and they have the same build no. So they might not have rolled it out to everyone yet. Which means there is hope. Some of the reviewers definitely got the OTA though as they wrote about it in their reviews. One I read was pissed as they turned down the OTA to download it later, but it never came again and checking for updates manually didn't work.
khr0n0s said:
It was online even before the OPT was released in China (4th of August). I have tried the HydrogenOS OTA update. It has quite a few bug fixes and improvements. It's a shame that HydrogenOS is so awful.
Click to expand...
Click to collapse
khr0n0s said:
I'm not sure. That is a good question. I was just talking with someone who has an international OPT and they have the same build no. So they might not have rolled it out to everyone yet. Which means there is hope. Some of the reviewers definitely got the OTA though as they wrote about it in their reviews. One I read was pissed as they turned down the OTA to download it later, but it never came again and checking for updates manually didn't work.
Click to expand...
Click to collapse
Huh what an absolute mess
I'm on the international variant with 150725 build but software update says up to date. Grrr sound like the update will fix some stupid annoyances.
-- from my OnePlus 2
Looks like there is a new update coming.
https://9to5google.com/2016/12/05/android-7-1-1-update-ota-nexus-pixel-december/
Interesting that it is coming to Verizon pixels but no factory images from Google yet. Curious to see if both models will always have the same updates or if sometimes Verizon models will have specific ones.
This is just the january patch due to be released on the 2nd of Jan
123cyborg said:
This is just the january patch due to be released on the 2nd of Jan
Click to expand...
Click to collapse
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
b00ster23 said:
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
Click to expand...
Click to collapse
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
123cyborg said:
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
Click to expand...
Click to collapse
I'm guessing because of the New Year's Holiday the push was delayed. I would suspected it would have come out today. So if it's not out yet, then I'm maybe next Monday. That's if they stick with their current deployment scheme.
Two versions just posted, NMF26U and NMF26V.
sliding_billy said:
Two versions just posted, NMF26U and NMF26V.
Click to expand...
Click to collapse
Haha that was fast :laugh:
I'm on NMF26O. Nothing shows when I click check for updates on my phone. It's Verizon phone with root running on TMobile. Should I go ahead and sideload NMF26V?
and "NMF26V" is international?
thats the question, how can i identfy which one is my OTA file from Europe, version NMF26O
Not sure which version to use. Google phone on Verizon.
Cares said:
Not sure which version to use. Google phone on Verizon.
Click to expand...
Click to collapse
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
TonikJDK said:
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Click to expand...
Click to collapse
I got the OTA U on a Verizon phone activated on Project Fi. I'm thinking unless specifically you know to use V then the U update is the way to go if you want to sideload.
Google updated the image site, V is for Europe/O2 and U is for everyone else.
mrjiggywiggy said:
Google updated the image site, V is for Europe/O2 and U is for everyone else.
Click to expand...
Click to collapse
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
TonikJDK said:
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
Click to expand...
Click to collapse
Well since you have their ear, perhaps you can tweet them to update the OTA images with descriptions. Only the full images have that. Not that it's hard to deduce but since some people sideload the ota rather than wait it might be nice.
fritzgerald said:
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
Click to expand...
Click to collapse
I used 2.79 SR2 and didn't have any problems.
EE simlocked uk versions got nmf26u, i'd think if you have nmf26o then you have the current version for your carrier, which carrier is 'o'
is there a way right now to get the bootloader unlocked on a verizon pixel xl...... 7.1.1?
Well it's that time again VZW put out a new OTA anyone taken this yet what does it fix and is it worth it and I think all of us will be wondering is will it lock your bootloader Its unlocked
Me too, I got an OTA notification today, update size is 823.5 MB, don't know what build it is.
I have VZ Pixel, unlocked, stock rooted NMF260 with VZ service. Is it safe to install updates ? Please advice.
Thanks in advance.
azn6929 said:
Me too, I got an OTA notification today, update size is 823.5 MB, don't know what build it is.
I have VZ Pixel, unlocked, stock rooted NMF260 with VZ service. Is it safe to install updates ? Please advice.
Thanks in advance.
Click to expand...
Click to collapse
I think your safe I doubt Verizon would lock your bootloader. That would wipe your device again
@Shiftydogit, @azn6929 got hold of a screenshot? If yes, pls share.
As you can see OTA notification
My guess is it's probably another patch or possibly a kernel update who knows or bug fix one of the three
Here it is
azn6929 said:
Here it is
Click to expand...
Click to collapse
Might as well just do it lmao
So one of you said you are on nmf260. That is December. So i doubt this is a "new" update, you are just behind. Google only releases on the first Monday of the month. VZ uses the same exact releases. There is no special VZ version.
Update away.
TonikJDK said:
So one of you said you are on nmf260. That is December. So i doubt this is a "new" update, you are just behind. Google only releases on the first Monday of the month. VZ uses the same exact releases. There is no special VZ version.
Update away.
Click to expand...
Click to collapse
Brand new update came out yesterday last update was December as you can see
Shiftydogit said:
Brand new update came out yesterday last update was December as you can see
Click to expand...
Click to collapse
Holy cow, they are two months behind. I had no idea, that is nuts. It is the exact same as the Google December update, FWIW.
TonikJDK said:
Holy cow, they are two months behind. I had no idea, that is nuts. It is the exact same as the Google December update, FWIW.
Click to expand...
Click to collapse
Leave it to VZW to be behind on updates as they try to patch everything I think it's safe to update I'll probably do it tonight
Shiftydogit said:
Leave it to VZW to be behind on updates as they try to patch everything I think it's safe to update I'll probably do it tonight
Click to expand...
Click to collapse
That's the crazy part. It is the exact same as what Google released in December. The Pixel's are different...they are only using Googles updates. No changes, no bloat, no nothing.
TonikJDK said:
That's the crazy part. It is the exact same as what Google released in December. The Pixel's are different...they are only using Googles updates. No changes, no bloat, no nothing.
Click to expand...
Click to collapse
Then us VZW users may want to start checking Google for updates instead of waiting for VZW OTAs
Shiftydogit said:
Then us VZW users may want to start checking Google for updates instead of waiting for VZW OTAs
Click to expand...
Click to collapse
They are at the link below, posted the first Monday of each month. Dunno how you get them on an unlocked phone, I know it is doable...just dunno how.
https://developers.google.com/android/ota
EDIT: LOL, I'm an idiot. The instructions are right at the top of the page I linked to.
TonikJDK said:
They are at the link below, posted the first Monday of each month. Dunno how you get them on an unlocked phone, I know it is doable...just dunno how.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
You'd just download them then sideload the OTA via recovery or you can flash it via fastboot/ADB but if you have TWRP installed fastboot will replace it with stock recovery
OK so with update my phone lost TWRP and root other than that bootloader is still unlocked and everything seems fine
Also build number changed after update OK then
If you are getting a new Verizon OTA, it is late. My Verizon Pixel updated to NOF26V (Feb security patch), weeks ago. NOF26V is the most current image for Verizon Pixels.
I updated. New build is NOF26V. Everything seems to be fine. But root is gone. lol
Can anyone tell me what the most current build of Android is for the Moto g5 plus ? Currently it's showing build 7.0 January security patch NPN25 137-33
I'm used to just FastBoot and Nexus/Pixle devices so Motorola is a change for me , does Moto have an image site or somewhere I can download factory Images from ?
Sadly no. You have to wait to get the OTA directly, or for someone to capture a compatible one and post it here. I'm retgb and have exactly the same version as you currently with a January security patch.
surrealjam said:
Sadly no. You have to wait to get the OTA directly, or for someone to capture a compatible one and post it here. I'm retgb and have exactly the same version as you currently with a January security patch.
Click to expand...
Click to collapse
Damn , I thought Motorola had a tool like Samsung's ODIN ?
surrealjam said:
Sadly no. You have to wait to get the OTA directly, or for someone to capture a compatible one and post it here. I'm retgb and have exactly the same version as you currently with a January security patch.
Click to expand...
Click to collapse
Im sure you have already seen this but if not https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
I just got the device so I'm going to spend a few more days learning about it till I jump into flashing but it seems pretty straight forward like NEXUS Devices are .
drawde40599 said:
Im sure you have already seen this but if not https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
I just got the device so I'm going to spend a few more days learning about it till I jump into flashing but it seems pretty straight forward like NEXUS Devices are .
Click to expand...
Click to collapse
Yeah sorry I just meant there is no official firmware listing so you're reliant on people posting links here. Also there's a bit of a minefield for us as there isn't one standard device/software channel across the whole world like there is with Nexus devices. I really miss those days, but the Pixel was just too rich for me.
surrealjam said:
Sadly no. You have to wait to get the OTA directly, or for someone to capture a compatible one and post it here. I'm retgb and have exactly the same version as you currently with a January security patch.
Click to expand...
Click to collapse
That has been my big question, I'm on retus and with several different versions being posted, will I ruin my modem or make some parts incompatible if I sideload? I am not rooted yet but I'm frustrated being on the same(??) version you are.