Database Users

64gb SanDisk card not functioning

On Ani2 rooted. 64gb card not mounting. Card mounts and reads fine in note3, gs3 and computer. Tried formatting ntsc,Exfat,fat32. 4 and 8 gig cards mount fine in gs5. Hit mount says card is blank or has unsupported file sys. Card is three weeks old. What gives?

jasonbtx said:
On Ani2 rooted. 64gb card not mounting. Card mounts and reads fine in note3, gs3 and computer. Tried formatting ntsc,Exfat,fat32. 4 and 8 gig cards mount fine in gs5. Hit mount says card is blank or has unsupported file sys. Card is three weeks old. What gives?
Click to expand...
Click to collapse
I had similar problems see this link http://forum.xda-developers.com/verizon-galaxy-s5/help/4-4-4-ni2-update-sd-card-blank-t2885047
Only fix I found was to rollback to NE9

Roger

That did the job. Shame ya gotta roll back to fix it.

Agreed.

jasonbtx said:
That did the job. Shame ya gotta roll back to fix it.
Click to expand...
Click to collapse
I had this problem also a month ago or so. Rolled back to fix the issue. Later found out that it was the phone hardware. Had VZW replace it, all is working well now.

Running NI2 and not a problem with a new 64g

128 GB ftw #flashingromsforlife

This is a common problem with the NI2 OTA update. You can use Odin to flash the NI2 Full Stock Tar and it should fix the issue. Here it is if you'd be interested in doing it.
https://www.androidfilehost.com/?fid=23622183712474060

Also encountering this problem. I backed out to NCG and all my SD cards started working, Installed one of the NI2 Roms from Andoid Dev and it stopped working again.
I'll try the full stock one next to see what happens and update the thread accordingly.
---------- Post added at 06:31 AM ---------- Previous post was at 05:38 AM ----------
Made no difference even using the full official rom.

lordcalin said:
Also encountering this problem. I backed out to NCG and all my SD cards started working, Installed one of the NI2 Roms from Andoid Dev and it stopped working again.
I'll try the full stock one next to see what happens and update the thread accordingly.
---------- Post added at 06:31 AM ---------- Previous post was at 05:38 AM ----------
Made no difference even using the full official rom.
Click to expand...
Click to collapse
Wow that's crazy! Samsung really needs to get their crap together and fully test everything before they release updates. It's still very odd how it works on some phones with NI2 firmware, but it doesn't work on others. There was a similar problem with the original Motorola OG Droid. I can't recall the exact issue it's been so long, but some would have the issue and others wouldn't. It turns out that some had a slightly different chipset, even though they were the same exact model phone. I wonder if Samsung has cut some corners on some of the devices and it's a similar situation.

So I was nagging verizon over twitter about this...
"Thanks for clarifying! I apologize for the inconvenience. An update for the issue we be addressed w/ the next software update"
Lets see if it really is fixed with the next update, or if they were just trying to get rid of me.

lordcalin said:
So I was nagging verizon over twitter about this...
"Thanks for clarifying! I apologize for the inconvenience. An update for the issue we be addressed w/ the next software update"
Lets see if it really is fixed with the next update, or if they were just trying to get rid of me.
Click to expand...
Click to collapse
Lol... I think they just wanted to get rid of you JK. I'm not really sure if the hardware differences are present in any of the Samsung phones, but theoretically it's a possibility, because I've personally witnessed it on other devices before. It's weird though because mine was able to read a 128GB card while I was on NI2 firmware. I'm sure it's just a little kink that will be worked out in an update though.
P.S. You never have to apologize for asking questions or think you're being inconvenient. You can never learn if you don't make an effort to, and asking questions is just part of that.

A very short batch hardware difference is the only thing I could think of as-well. It otherwise makes no sense that for the vast majority of people there was no problems, but a select few (at least who posted about it) can be found if you dig deep enough. In all cases so far that I've read about they took the phone to Verizon and it was replaced with one that works. Unfortunately since i'm not in the U.S I don't have that option so I'm praying on it will get fixed.

November security update is up

OTA's and factory images have been posted for November security updare.
https://developers.google.com/android/ota
Three versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon

With the BIG warning on the page about be sure to backup all your Photos and Personal data before applying the Update, does this means that it will delete all your data for just applying an OTA update? I understand that for applying the Full Factory images but does it really wipes the data applying just the OTA updates?
Sorry, but this being my first Nexus/Google phone what I know for OTA updates was just a simple process that doesn't delete anything on the phone, and I just want to be sure how it is here before I proceed, thanks in advance.

erasat said:
With the BIG warning on the page about be sure to backup all your Photos and Personal data before applying the Update, does this means that it will delete all your data for just applying an OTA update? I understand that for applying the Full Factory images but does it really wipes the data applying just the OTA updates?
Sorry, but this being my first Nexus/Google phone what I know for OTA updates was just a simple process that doesn't delete anything on the phone, and I just want to be sure how it is here before I proceed, thanks in advance.
Click to expand...
Click to collapse
Best to back up your data, just to be safe. But I personally sideloaded "U" without any issue. Nothing lost.

cam30era said:
Best to back up your data, just to be safe. But I personally sideloaded "U" without any issue. Nothing lost.
Click to expand...
Click to collapse
Yeah, I understand the risks when updating anything so I always do a backup of the most important stuff just in case, but as you know it's not the same to have to do a Full backup/restore. I needed to be sure but if you did it and you are fine then with what I already have backed up I should be fine too, thanks.

I just restored to stock my L and then checked for updates before rooting.
It said I'm already up to date.
I'll try again in a little while before rooting.
But simply being "unlocked" might be what is preventing me from grabbing an update. Not sure.

CZ Eddie said:
I just restored to stock my L and then checked for updates before rooting.
It said I'm already up to date.
I'll try again in a little while before rooting.
But simply being "unlocked" might be what is preventing me from grabbing an update. Not sure.
Click to expand...
Click to collapse
You can download the update(s) from the Google dev site and adb sideload of fastboot flash the factory image (if your bootloader is unlocked). No need to wait for the OTA, if you don't want to...

Whats the difference between builds NDE63U, NDE63V and NDE63X?

Got a vzw pixel that BL unlocked. Safe to flash the 63X? I saw @jcase said vzw would not do an OTA that relocked your BL. Just wondering if anyone else flashed the 63X build.

armandocorti said:
Whats the difference between builds NDE63U, NDE63V and NDE63X?
Click to expand...
Click to collapse
U-> 11/1 sec patch
V-> 11/5 sec patch
X-> 11/6 sec patch

cam30era said:
U-> 11/1 sec patch
V-> 11/5 sec patch
X-> 11/6 sec patch
Click to expand...
Click to collapse
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.

CZ Eddie said:
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
Click to expand...
Click to collapse
http://source.android.com/security/bulletin/2016-11-01.html

Was going to flash the factory image system but it looks like the process has changed.... More files and slot a and b.
Anyone know the proper way to manually flash the system.img?

cam30era said:
You can download the update(s) from the Google dev site and adb sideload of fastboot flash the factory image (if your bootloader is unlocked). No need to wait for the OTA, if you don't want to...
Click to expand...
Click to collapse
Yes, I realize I can typically install my own updates.
But as of right now, nobody truthfully knows which phone should have which build. P is so far looking Verizon Only.
Nobody I know of on Verizon has the H or L images.
So I'd rather be safe than sorry and let my phone CHOOSE it's update, and it did not so I mentioned that here to prevent others from restoring to stock and trying for an OTA
Anyways, it's just a payload.bin file. Not the same android image as the older files. I'm actually not sure how to install a payload.bin.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
cam30era said:
http://source.android.com/security/bulletin/2016-11-01.html
Click to expand...
Click to collapse
Yeah, I get that there are security patches.
But what I'm asking you is to tell us how you know those security patches correspond with the different builds.
I skimmed the page but didn't notice anything saying one way or the other.

CZ Eddie said:
Yes, I realize I can typically install my own updates.
But as of right now, nobody truthfully knows which phone should have which build. P is so far looking Verizon Only.
Nobody I know of on Verizon has the H or L images.
So I'd rather be safe than sorry and let my phone CHOOSE it's update, and it did not so I mentioned that here to prevent others from restoring to stock and trying for an OTA
Anyways, it's just a payload.bin file. Not the same android image as the older files. I'm actually not sure how to install a payload.bin.
Click to expand...
Click to collapse
My vzw pixel shipped with 63H.

jaxenroth said:
My vzw pixel shipped with 63H.
Click to expand...
Click to collapse
Then you're the only person on the board so far who has an H build on Verizon:
http://forum.xda-developers.com/pixel-xl/help/build-pixel-t3489990/page2
Could you please post in that thread to let others know?
I wonder if you got a non-Verizon phone.

CZ Eddie said:
[/COLOR]
Yeah, I get that there are security patches.
But what I'm asking you is to tell us how you know those security patches correspond with the different builds.
I skimmed the page but didn't notice anything saying one way or the other.
Click to expand...
Click to collapse
Valid question. @jcase has clearly stated that "X" would prevent VZW bootloader unlock. Regarding U and V, and which is 11/1 and which is 11/5, I don't know for sure. But it's clear from the Google dev link that each of the 3 builds include an incremental increase in patches.

"clearly stated that "X" would prevent VZW bootloader unlock."
Those durty basturds.
And that's why I didn't get a VZW phone.
<<----- VZW hater gets to hate on VZW yet again. :laugh:

JustusIV said:
Was going to flash the factory image system but it looks like the process has changed.... More files and slot a and b.
Anyone know the proper way to manually flash the system.img?
Click to expand...
Click to collapse
I guess i will do an adb sideload of the OTA.
I have never done it this way, but it looks like others have done this, and the boot-to-root still works.

with the newest radio being in the v .. i would speculate that its u world v north america and x verizon
corrected radio
Sent from my marlin using XDA Labs

CZ Eddie said:
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
Click to expand...
Click to collapse
"The previous U and V versions were a few days older and are simply there for legacy reasons."
Source > http://www.androidcentral.com/google-posts-latest-pixel-images-november-security-patch

January 2, 2017 Software Update

This morning, my Note received a rather large software update that installed without many problems. Most likely certain security updates, but I was surprised to receive it as we are not really "accustomed" to any attention from Samsung for this tablet. Any further comments from anybody else?

I got the same.
Sent from my HTC 10 using XDA-Developers Legacy app

many problems? like what i have it to and i hate updating. anything broke? IR blaster still work? Please and thanks.

Mispelling
nanofoxx said:
many problems? like what i have it to and i hate updating. anything broke? IR blaster still work? Please and thanks.
Click to expand...
Click to collapse
Sorry for the misspelling. I meant to say "without any problems" not "without many problems". In fact, the whole update process was smooth and fast. Everything works fine. I understand, however, that everyone's setup is different and my experience should not be the absolute rule.

Nothing here on my device. Although it might be because I'm in Sweden.

Did anyone see any changes? I dont see/feel anything other than the version number change even the security patch level date remained the same. Is there a changelog somewhere

dingnecros said:
Did anyone see any changes? I dont see/feel anything other than the version number change even the security patch level date remained the same. Is there a changelog somewhere
Click to expand...
Click to collapse
I don't see any difference after the update, either. I wonder what it was supposed to have updated?

Maris_ said:
I don't see any difference after the update, either. I wonder what it was supposed to have updated?
Click to expand...
Click to collapse
There's a whole new Lollipop firmware on the San mobile firmware site.

Yes...problems
My tablet updated and now the OS boots super slow and then does a soft shutdown and reboots a second time. It takes more than 60 secs to get to the home screen. Anyone know how to uninstall this update?

ADRz said:
This morning, my Note received a rather large software update that installed without many problems. Most likely certain security updates, but I was surprised to receive it as we are not really "accustomed" to any attention from Samsung for this tablet. Any further comments from anybody else?
Click to expand...
Click to collapse
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.

Kingsman1 said:
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Click to expand...
Click to collapse
I also have a SM-P605V but have Verizon as my carrier. I got the notification to update today. I don't see anything on VZW site about it nor under the specific SKU on SamMobile (still has 10/15/15 as the last official update). When looking at the SM-P605 model, there are some in the list (even today's date), though they are for non-USA countries.
Even so, it looks like they are still all Android 5.1.1, so it's likely just some minor tweaks. To my understanding, you would need to pop in an activated Verizon SIM to get the update for your specific tablet, as Verizon is the one that issues it. You can also wait until it's posted on SamMobile and manually do it. https://www.sammobile.com/firmwares/database/SM-P605V/
---------- Post added at 12:02 PM ---------- Previous post was at 11:33 AM ----------
I think I found the official from Verizon: https://www.verizonwireless.com/support/samsung-galaxy-note-10-2014-update/
Software Version: LMY47X.P605VVRSDPL1
The current software update gives you the most up to date Android™ security patch on your device.
Click to expand...
Click to collapse
(I called VZW and she confirmed that it was an Android Security patch, no MM, darnit!)

Kingsman1 said:
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Click to expand...
Click to collapse
You should be able to flash this now that Sammobile posted it... https://www.sammobile.com/firmwares/database/SM-P605V/

I got this a couple of days ago - managed to odin flash after I put the wrong file and got the boot loader triangle a day before.
Its extremely stable and the tablets working like a dream - the only issue is no root.
Edit: I noticed a great improvement in battery management and it will charge to 100% from 30% in 4 hours before I flashed the 5.1.1 rom it took nearly 8 hours with a new(second hand) USB Flex connector and nearly 20 hours with the old usb flex connector to go from 30% to 100%.
I really like this tablet - it reminds me so much of my SM-N910F note 4.

You can root the latest firmware and also install twrp. I have a 600.

louvass said:
You can root the latest firmware and also install twrp. I have a 600.
Click to expand...
Click to collapse
did it actually do anything? or is it not worth it

graffix31 said:
did it actually do anything? or is it not worth it
Click to expand...
Click to collapse
Probably just a security update

Please excuse my silly question but I have P600 with 5.1.1 and never rooted. Do I need to install twrp before I update or it doesn't matter? Updates always make me uneasy with locking bootloader or needing new root methods.

If you just want to update then flash with Odin and the appropriate file. Try looking at sammobile.com for the appropriate rom file.
If you want root then you will need to install a custom recovery using CF auto or Twerp - the latter will NOT work on the SM-605v version as the bootloader is locked and will result in the yellow triangle and stating that the tablet has a strange recovery and that you should see a verizon technician. By installing the recovery you can then update the system or even try out new roms created by the people of this wonderful community.
Rooting will potentially stop business application with built in security from working - i.e. HSBC application, Virgin Media app and Sky Movies apps will not work on rooted phones to name a few.

I updated and rooted and everything is working ok. I had trouble with 64gb Sandisk microsd with "sd card unexpectedly removed" error. Then it mount itself back. Sometime it shows empty and asks to format and sometime it works. Also the lockscreen flicker and that usually when the card error happened. I suspect they are related and it happens only when waking up the device. The card works fine with all my other devices including my note 4 on stock 5.1.1. I'm not sure what caused it because I just used this sd card with the note 10.1 and then updated and rooted all in the same day.
Anyway, I removed the Sandisk and now I'm using 32gb Samsung and it only happened once for maybe 12 hours (could have been 100 times with Sandisk). Also, I don't notice the lockscreen flickering anymore. I will see if this problem comes back or it just that Sandisk doesn't play well my note. I have seen many people here reported similar problem with other Samsung devices for too many reasons. I don't believe file format is the issue but I'm using exFAT.

RETUS Nougat OTA (discussion, root, setups, etc.)

Hey guys,
Not much of a poster but it seems the retus guys are left out in discussions involving flashing our firmware...
I present the official nougat OTA I received for RETUS only. This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
For those sideloading this and are still on MM, you'll just need to adb sideload the file. Keep in mind that I received my OTA update on a November security patch, so it may not mater at all which patch you have.
RETUS NOUGAT OTA (Mega link)​
Preparation:
For those who rooted and caused a bunch of hell on your system partition, you can grab some stock unsigned firmware here and revert what you did. Fastboot flash the boot, sparsechunks (in order), recovery, and oem images (then reboot back to bootloader to choose recovery mode). You can now finally sideload it flawlessly without losing any data. If you need more information you can check out one the revert to stock firmware guides, I'm not going to post something repetitive.
Root options:
You want root? You have two options...first you obviously need TWRP.
flash a custom ROM
flash this gentleman's (tomparr) custom kernel over on his thread and then flash superSU or Magisk. You can flash both SuperSU and Magisk but you could also just flash Magisk which comes with it's own systemless root.
Revert?
You can reflash MM images but I suggest using something more autonomous like this flashing tool by core720 since there's a lot more commands involved to officially downgrade. There's also an edit of the downgrade bat script in the comments of the thread which I suggest to use instead.
Viper4Android!? Atmos!?
There are currently magisk modules that work (both arise and independent ones).

I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.

I am on July security patch and just got the prompt so don't think patch level matters

xantanion said:
I am on July security patch and just got the prompt so don't think patch level matters
Click to expand...
Click to collapse
Please let me know if yours updates, mine has failed four times today already.

Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
Mine went flawlessly

Jimi Mack said:
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
Click to expand...
Click to collapse
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.

DroneDoom said:
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
Click to expand...
Click to collapse
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
xantanion said:
Mine went flawlessly
Click to expand...
Click to collapse
You installed this downloaded OTA or did you get yours OTA? Thanks.

Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
Got my OTA today and had no issues. Just got the phone brand new yesterday as well

Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.

DroneDoom said:
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
Click to expand...
Click to collapse
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "

Jimi Mack said:
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Click to expand...
Click to collapse
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.

DroneDoom said:
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
Click to expand...
Click to collapse
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?

Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.

Jimi Mack said:
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Click to expand...
Click to collapse
I think there may be a difference in security patches but they have the same build number so I'm not too sure.
holabola said:
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Click to expand...
Click to collapse
Yeah it is, it reminds me of the days when I had a Motorola razr lol.

For anyone that was wondering, the display size scaling works PERFECTLY.
I originally changed the DPI to make everything smaller, but it led to a lot of random issues with other apps (mainly involving the camera). The display size scaling mimics the effects of a DPI change right out of the box without all the issues and need for a computer (I wasn't rooted so)
Also, when I got the update, I was on the December 1st security patch.

DroneDoom said:
This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
Click to expand...
Click to collapse
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
DroneDoom said:
Magisk
Click to expand...
Click to collapse
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.

xxBrun0xx said:
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
Click to expand...
Click to collapse
Thanks for the feedback (fixed op), I noticed v11 doesn't patch the kernel correctly and the ROM tries to boot without it. I thought it was just me since I was playing around trying to change my cache partition to f2fs but I guess the kernel doesn't support that filesystem for cache (ROM boots but doesn't initialize).
S3v3n's ROM is based on firmware stock right? I tried magisk with V4A module but it doesn't work and Atmos somehow bricks stock but it doesn't brick on a ROM built from different source (works on xperience). I noticed today that the ARISE project has a magisk module for it's latest project so maybe there's a possibility for stock to have systemless V4A.

Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?

Jimi Mack said:
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Click to expand...
Click to collapse
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.

DroneDoom said:
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
Click to expand...
Click to collapse
I thank you. I got the update to begin to load, it fails and aborts at 45% . It states something about content, lists my build number and give a code 755. I can not find out anything about this one either. I guess something is screwy with what is installed on my phone and what should be...

Android 10 factory images is live

Enjoy!
Currently two builds: QP1A.190711.019 and QP1A.190711.020
Factory Image: https://developers.google.com/android/images#sargo
OTA Image: https://developers.google.com/android/ota#sargo

No OTA here in Germany so far

Anyone know the difference between the two builds?
Sent from my Pixel 3a using Tapatalk

Neither in France

jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
They have diferent checksums

jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
"Within the .19 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565300664 which equates to 08/08/2019 @ 9:44pm (UTC).
Within the .20 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565743352 which equates to 08/14/2019 @ 12:42am (UTC).
Based on one of Google's release tool's code, this value seems to be utilized to determine whether it should perform an incremental or full OTA.
If I'm understanding their upgrade process correctly, the .19 image does not contain the September security patch. The .20 appears to be the full stable release with the September security patch.
It would appear .19 should support an incremental upgrade from the latest Android Pie (9) version, PQ3B.190801.002 but not bring you to the latest September security patch.
This leads me to believe that the .20 image is suitable for almost all OTAs. There may be carrier specific cases that one or the other should be utilized but nothing stands out too clearly within any of the immediately available metadata files."
- https://www.reddit.com/r/Android/comments/cz7lb1/android_10_images_are_live/eywlgww/

Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?

I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Sent from my Pixel 3a using Tapatalk

Atiqx said:
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
Click to expand...
Click to collapse
No, just uninstall magisk or flash stock boot.img. once that is done, you should OTA just fine.

upinsmoke7610 said:
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Click to expand...
Click to collapse
On reddit they say that coming from beta the update file is only this small.

yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
Well I knew banking apps would not work on the beta but now I'm on the stable release and my banking app still will not even open, but of a nightmare really as I rely on it.
Sent from my Pixel 3a using Tapatalk

Got the OTA from pie right now 1188.8mb

I've just received the OTA notification here in Spain
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
anyone knows if is there any difference, or added feature compared to the last beta version?

yabadabadooo said:
They have diferent checksums
Click to expand...
Click to collapse
A factory image is a full replacement - and is meant to replace everything (you'll lose all your data and else that isn't backed up). An OTA is an update - you lose nothing. If you're coming from a STOCK factory image (either a beta of 10 OR 9) and your phone is fine, you want the OTA; otherwise (including AOSP), you want the full factory image.

germany here, installing the update now, takes quite some time for being only 41mb, hope it works

I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.

Got it 30 mins ago from stock rom over ota (1.1GB) in France.
Install was smooth and fast.
So far so good!
Enjoying the dark mode
#Edit: weather widget shows temperature in °F instead of °C while everything is setup right. Strange ^^

sic0048 said:
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Click to expand...
Click to collapse
Thank you sic0048! I followed your guide when my Pixel 3a was on 9 and it was smooth. The best instructions I have found and even bookmarked it.
I do have one quick question. I followed your instructions about updating the phone and keeping root, but I lost root after reboot. I probably did something wrong. :silly:
In your instructions under the "Custom Recovery Installation method" you state that TWRP doesn't support Android 10. So how do I root my phone again? Is it safe to use this method or should I use another one of your methods in this tutorial?

After update to 10, I was able to see "Enable DDS" toggle in phone information shortcut.
Now the toggle is gone.
Anyone else has this issue?

yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
I came from RC2 - the update is indeed that little.
However, you will have to wait for a 10-ready build of TWRP; the current TWRP is not ready (of course).