Database Info

UK Nougat update just arrived

Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.

m+a+r+k said:
Just checked and my Style is offering me Nougat with August security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
Woohoo! I think I shall downgrade my reteu-flashed Nougat to retgb 6.0 this weekend in preparation for it then.
If you happen to have an unlocked bootloader, do you mind capturing the OTA via TWRP? The way to do it is the following, if you have downloaded the OTA but not yet installed it:
Install ADB drivers (Windows): https://adb.clockworkmod.com/
Get the ADB command line (Windows): https://forum.xda-developers.com/showthread.php?t=2317790
Download the latest twrp .img for clark: https://dl.twrp.me/clark/twrp-3.1.1-0-clark.img.html
Turn on USB debugging on your phone: https://developer.android.com/studio/run/device.html
Disconnect the phone's USB connector (e.g. to a charger) if connected.
Turn off the phone.
Start the phone into the bootloader by holding down Volume Down as you power up the phone, and then releasing it.
Connect it to a PC or Mac via USB. On Windows, wait for it to be recognized.
On the command line, verify that it is available to fastboot by running the command
Code:
fastboot devices
and verifying that it shows up.
From the ADB/Fastboot command line, run
Code:
fastboot boot \path\to\twrp-3.1.1-0-clark.img
.
Wait for TWRP to start.
Once it is started, from the ADB/Fastboot command line, issue the command
Code:
adb shell find / /data /cache -xdev -name 'Blur_Version*' -print
; you should see at least one file with that name appear.
From the ADB/Fastboot command line, issue the command
Code:
adb pull /path/to/Blur_Version_....zip \path\on\pc\Blur_Version_....zip
Issue
Code:
adb reboot recovery
which should reboot the phone into the stock recovery, assuming your ROM is stock 6.0 including the stock recovery.
Once it is started, issue
Code:
adb sideload \path\on\pc\Blur_Version_....zip
. This will attempt to flash the OTA via adb sideload.
Once you have the OTA, you could put it somewhere useful (e.g. find a way to get it to prazaar's site) for the rest of us!

Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.

US needs this terribly.

m+a+r+k said:
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
All good. Update was reasonably quick and no problems at all. No settings or software lost.
Very happy.
Shame it is only 7.0 and not final version 7.1.2.

i could do with the Blue and Red boot logo now

Just got August Security update.
Blimey, what's going on? Nothing for over half a year then Nougat and a security update in 2 days!!!

Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)

obs3rv said:
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
Click to expand...
Click to collapse
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Maybe it has something to do with your experience. Someone else noticed it?

Edvin73 said:
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Someone else noticed it?
Click to expand...
Click to collapse
Yes. In fastboot, the existing Nougat bootloader is able to protect itself so you get the preflash verification failed error. If you continue to flash the MM firmware, it does boot, and does offer OTAs. One of these OTAs (the one that goes from 24.221.4 to 24.221.5) then flashes the aboot partition from within the OTA update.zip in the stock recovery. At that point, the bootloader is inactive so cannot protect itself from being effectively downgraded. This replacement of the aboot/emmc_appboot is what hard bricked my phone. So be careful!
Probably the better thing to do would be for people with retgb or retfr firmware, and an unlocked bootloader, to upgrade to the retgb/retfr Nougat firmware with August 2017 security patch, then boot (but not flash) twrp using
Code:
fastboot boot /local/path/to/twrp-3.1.1-0-clark.img
, and then create a backup of boot and system, then post it somewhere for others of us who are on the reteu firmware to use. This way we do not meddle with the bootloader but can still receive OTAs. (I captured a TWRP backup of the reteu version in this manner before I bricked my phone by attempting to switch to retgb.)
I have also managed to capture the intermediate OTAs between RETEU-UK-FR_6.0_MPH24.49-18 and 24.221.5 by successively downloading OTAs, starting up the bootloader and using TWRP via fastboot boot to copy them out of /cache on the device via adb pull. As far as I can tell, no one's ever made them available via web before. I have these:
24.49-18 to 24.201.3 (named with 24.11.18)
24.201.3 to 24.221.4 (named with 24.201.3)
24.221.4 to 24.221.8 (named with 24.221.4 -- this hard bricked my phone on flashing the bootloader)
But please be extremely careful with these -- don't use them if you've ever had newer stock firmware versions via fastboot or OTAs via stock recovery (of any region).
@Prazaar, @dzidexx -- any interest in putting these in your archives?

Not that I care, but...
smallmj said:
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
Click to expand...
Click to collapse
There's still hope for the peanut gallery. I heard that Verizon's HTC One (M9) just recently got a software update for Android N. That puts Motorola neck-in-neck with HTC and only about six months behind Samsung.

So Moto Alert has gone ? **** sake I actually used that so my girlfriend knew I was on my way back from biking and could stick my tea on.

question about OTA after a custom rom

Hi, i flash the pixel experience rom oreo 8.1 on my moto g 2015 but i dont liked, so i flashed the stock rom 6.0 via adb fastboot and some updates have appeared, i can do?

Twinsen78 said:
Hi, i flash the pixel experience rom oreo 8.1 on my moto g 2015 but i dont liked, so i flashed the stock rom 6.0 via adb fastboot and some updates have appeared, i can do?
Click to expand...
Click to collapse
While I don't know exactly how it is on Moto G3, it seems kind of a game of luck if you get OTA updates back. But necessary steps device independent often are:
- Flash stock ROM with a full wipe
- flash stock recovery
- relock the bootloader
- some devices include a flash counter, for example almost all Samsung devices. This counter has to be reset. Works different for every phone.
- for some devices, for example Sony, specific files MUST be backuped before a flash, otherwise there is no chance of getting OTA back.
But keep in mind that this device doesn't receive updates anymore since about last year. So maybe you just look for the most up to date stock ROM and flash it, which btw on my phone is Android Marshmallow, security patch level April 2017.
I hope this helps a little bit, even though I can't provide very detailed information. Let's hope someone more experienced helps further, or just search around in the web.

BenjyTec said:
While I don't know exactly how it is on Moto G3, it seems kind of a game of luck if you get OTA updates back. But necessary steps device independent often are:
- Flash stock ROM with a full wipe
- flash stock recovery
- relock the bootloader
- some devices include a flash counter, for example almost all Samsung devices. This counter has to be reset. Works different for every phone.
- for some devices, for example Sony, specific files MUST be backuped before a flash, otherwise there is no chance of getting OTA back.
But keep in mind that this device doesn't receive updates anymore since about last year. So maybe you just look for the most up to date stock ROM and flash it, which btw on my phone is Android Marshmallow, security patch level April 2017.
I hope this helps a little bit, even though I can't provide very detailed information. Let's hope someone more experienced helps further, or just search around in the web.
Click to expand...
Click to collapse
are only 3 security patch, i updated and not brick but thanks for the reply.

GUIDE: How to FLASH and RESTORE your STOCK firmware on the TA-1054 (and others)

It seems like there are a few people having trouble going back to stock and getting everything working.
As always, this requires an unlocked bootloader. If you don't have an unlocked bootloader then search google for a $5 service that does. It is what I did.
I flashed Project treble on my TA-1054. It worked great except it kept saying "insert SIM" when there was already a sim card inside, so I could not use it.
I tried to go back to stock but that firmware file on that google drive thread was corrupted, bad upload. Took me a few days to source this original firmware.
There is a tool called OST ( around 115MB), and a patch that comes with it (the smaller file less than 1MB)
The firmware is almost 2 GB
Download everything, including firmware.
1. Install the OST tool.
2. Replace the EXE file in the program files with the patch file you downloaded.
3. Delete the Onlineupdatetoolexe.config file. If you don't do this, the program will not start correctly.
4. Put phone into download mode ( either by powering it off, pluging into USB cable and immediately hold power and volume down. Or if you can boot into android with ADB debugging, just do a adb reboot bootloader.
5. Pick firmware file and click next.
THe first 2 times I tried this, It hanged at the last second. Third time was a charm. Give it time. Use a good USB cable.
I assume that this is the same way to flash other firmware files for other devices.
As soon as i get my hands on a android one firmware, I will flash it.
Or if anyone can guide me on how to extract the firmware on my TA-1045 USA version and flash it to my TA-1054 Chinese , let me know. Cheers.
Google drive folder with all the files I uploaded.
https://drive.google.com/open?id=1NbzO6lfSGacjM2wqrtBg3jMpljsZswne

Thanks bro...I am downloading it.

PL2-2380-0-00WW-B01.NBx.zip is global firmware name. firmware size is 4gb.

thanks! for extract is with nb0 tools FIH Mobile v3.4

https://drive.google.com/open?id=1cSgjrZUxIsN7oLbo7AP-RnILDZdswmB-
its android one firmware. I have no tool for flash...plz try and let me know

Flashing now. Will report back after flashing is done. thanks!!
Edit: Looks like the version I have for OST does not read NBX files. Will try to update that and report back. I have ntool but no working username password

I cannot flash the NBX file. I changed it to nb0 but OST LA says cannot read firmware. Is there any other way to flash?
EDIT: I went ahead and purchased a bunch of credits for NTOOL.
I will flash and see if it works!

It fails with the mdtp.img partition (no such partition) . I would think that it would just skip that partition but it did not. I will later try to extract and flash separately

For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.

stealthj said:
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
Click to expand...
Click to collapse
can u flash my chinese rom which is nbo format via ntool. I have have ntool but i dont have user name,password, i downloaded rom which u provide.my device still cant connect to mobile data.

NBX format only works on Ntool. but Ntool needs working user name and password to works. OST cant read or flash Nbx format.
if u get Ntool with working user id .. then plz flash my device also via remote mode like teamviewer.

Ntool Bricked my device. the only real restore you can do is by using ost with the stock chinese firmware. edit your apn. why is your data not working?

Global rom cant flash via ntool in Ta1054..showed error in partition. if it will be solved then china to global will be easy process..

I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.

Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic

safron35 said:
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
Click to expand...
Click to collapse
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.

stealthj said:
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
Click to expand...
Click to collapse
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.

TheImpulson said:
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
Click to expand...
Click to collapse
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc

stealthj said:
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
Click to expand...
Click to collapse
How to flash it?
Edit: Also OnlineUpdaterTool in your 1st post asks for a password. What's the password?

nooby_pls said:
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Click to expand...
Click to collapse
I put the original chinese firmware on the first post.
There is an option to install google play store, but that would make your rom unable to receive updates.

Motog8 plus root

Does anyone know how to root? Till yet ?
Today IT was my Christmas.present
Thanks
Daniel

No source from motorola, nor updates yet.

Hello you can root your moto with magisk.

Mounib BOULAABI said:
Hello you can root your moto with magisk.
Click to expand...
Click to collapse
If you have a copy of the boot.img
Sent from my mata using XDA Labs

Thanks by the way. I found i way to root my Device.

Please do tell, how?

Danieldergrosse said:
Thanks by the way. I found i way to root my Device.
Click to expand...
Click to collapse
Would you mind sharing your way to root your device? Every piece of knowledge can help other users here on XDA.
Sent from my Moto G5 Plus using XDA Labs

http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method

Danieldergrosse said:
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Click to expand...
Click to collapse
*
your link seems dead or not correct. - edit: link correct, was not working due to my vpn...
I assume he patched a G8+ boot.img with magisk manager.
boot image can be extracted from official Doha firmware found here: https://mirrors.lolinet.com/firmware/moto/doha/official/
manual on how to do this can be found on official magisk manager website.
be aware that when unlocking bootloader your phone will reset to factory settings.

This is what I did. Yes..

Worked great for my G8+. I guess people should just check which stock ROM file they get from lolinet to make sure it's the right one. I say that because, in my case, lolinet list had two files for the Brazilian stock ROM. I went to Settings / About / Version number and downloaded the matching file. Don't know whether the other file would work the same or not. Just didn't want to risk having any issue since G8+ is somewhat new and there's not much info on solving root problems on the Internet.

Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl

carl.13 said:
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
Click to expand...
Click to collapse
Hello, Carl. I guess it's not possible unless there's a flaw in the security. There are some articles on the Internet about that. Google "is-there-a-way-to-root-an-android-phone-without-unlocking-the-bootloader". I can't post URLs yet.
As for Motorola devices, I was able to unlock the bootloader without problems on my G8+, last week. The only caveat, I'm my case, is that I had to wait some days for the unlock bootloader option be available under developer options. It was disabled by default in my G8+. And, yes, they're releasing bootloader unlocking codes.

THANKS!

Have anybody with a rooted device tried to get wide angle camera working in gcam ports?
Thanks.

successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google

esrd43 said:
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
Click to expand...
Click to collapse
magisk module debloater and also sdmaid helped with most of the bloatware, the only thing I could not remove was google files but I just deactivated it.

a really weird thing happened with the April 1st update, basically the update started automatically and it failed at 3/6 so I tought I should restart my phone and test it again, but it got stuck in bootloop and I had to reflash a rom with fastboot cmd.
I think that's because I unlocked the bootloader and rooted my phone, cause u lose the right for updates after you do that, but for some reason lenovo/moto update system goes automatically the next second u connect to the internet and fails halfway thru so u have a higher chance to ruin your phone or something, instead of denying the update from the start
so the solution I found was to try and delete "moto update service" app that I can't force stop or disable but I couldnt find it in system/app or system/priv-app, that's because the app name is "3c_ota", so deleting that with SD Maid app worked and the "update system" option in settings is reverted to a sort of default android one that lets you check manually.

Had a similiar issue. I soft bricked my phone (bootloop) and installed a stock rom from an unofficial source. The funny thing is, this version did make like 3 or 4 system upgrades to PPSI.29.65-51 without any issue. But the 1st April updated failed to install. I then flashed the official 1st april stock image with the moto rescue and smart assistant. After that, the official ROM tells me my phone is not allowed to do updates because the security of this phone is compromised and I should contact lenovo support
Those upates are kinda annoying if they don't work, I guess I'll just completey flash the phone every 6-12 months with the moto assistant.

yeah you should always have a backup rom that you can download with moto assistant or from lolinet g8 roms (https://mirrors.lolinet.com/firmware/moto/doha/official/)
I also got the same message saying that my phone is compromised ( unlocked bootloader + rooted) and it won't receive any further updates, but I just deleted the "3c_ota" app (the moto update service) which is bad cause if forces automatic updates the second u connect to internet.
I'm not going to touch any further updates or security patches until android 10, which I will attempt to flash via moto assistant

Device has failed verification and may not work properly after flash whit lock BL

Hi, yesterday I received the Troika terminal.
I set out to flash to the latest version instead of waiting for all the updates I detected.
Even with the bootloader locked, I installed the latest available via fastboot:
XT2013-2_TROIKA_RETEU_9.0_PSB29.39-49-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but it doesn't start
this is the error ... your device has failed verification and may not work properly
I ALWAYS BELIEVED THAT TO FLASH AN OFFICIAL ROM I DID NOT MISS THE UNLOCK OF THE BOOTLOADER.
AT LEAST ON THE G5 MOTORCYCLE IT WAS THAT
:crying:

Solved
I've flashed again but this time this rom PSBS29.39-49-7-1
*and has no longer given bootloader errors during flashing.
And it is working.
I leave the thread here to serve in the future.

have u tried to install retail android 10?

Furieuxariel said:
have u tried to install retail android 10?
Click to expand...
Click to collapse
Yes after solving it and being able to use the mobile again. (I like danger). xD
And he gave the same error again, getting stuck in the verification and not even going to recovery. I do not recommend updating to the only version currently available in lolinet.

* * * Thread Cleaned * * *
Please keep comments relevant to the topic, and not towards insulting other members.
Thank you.

Could you, please, post a step-by-step of what happened? It might help others.
So, bootloader was locked at all times, right? Then you flashed Android 10 (which exact version? could you post the name or a link)? Then you tried to go back to Android 9, but you selected and older version (I'm guessing probably older than the Android 10 Security Patch), and it wouldn't boot anymore? Is this what happened?
The difference between PSBS29.39-49-7 and PSBS29.39-49-7-1 is (if I'm not mistaken), exactly the Security Patch. The latter should be December, which means the first one is probably November.