yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] foosion:
I had thought the idea of Treble was to present a standard interface between hardware and the OS, to separate the device-specific, lower-level software written in large part by the silicon manufacturers from the OS.

"Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work." https://www.xda-developers.com/project-treble-custom-rom-development/

Doesn't that mean someone can just compile the latest AOSP build and it will run on a Treble Pixel 1? Don't the current Nexus and Pixel phones essentially run AOSP, but have to be modified to work with the specific hardware, modifications that won't be necessary with Treble?

Or is this the issue: "You won’t be able to boot up flawlessly-working generic Android 9.0 builds on your Treble device just yet, though – device trees and kernels will still require being worked on."
[Google Pixel Questions & Answers] GuestK0037:
that's the general idea, but afaict, it's not there yet and not for the pixel 1

I didn't read your link, but I did watch the linaro talk from a week or two ago about... The vendor test suite (VTS), is to be used to have aosp be bootable on XYZ SOC, as the idea is to keep all of the vendor blobs outside of aosp / the core of android.... in practice though, even with the pixel, it still isn't 100% like that. ROMs like LOS are still pulling vendor blobs and baking them into their build system....

who knows about android 9.0, but it doesn't work for Oreo and the pixel 1... Nexus and Pixel run aosp with a bunch of Google's tweaks from their own internal android tree + all of the google services and apps... I'm sure there is a reasonably sized set of patches / Delta between aosp and Google's own builds.... but obviously, google provides a very 'vanilla' version of android.
[Google Pixel Questions & Answers] jss2:
Independent of the discussion here regarding Treble, the original Pixel is getting updates for the same duration (from release) as the Pixel 2.

Both devices will get 2 years of Android version updates, and another year of security updates.

https://support.google.com/pixelphone/answer/4457705

The original Pixel will get android version updates through October 2018, and security updates through October 2019. The Pixel 2 will get updates for one year longer simply because it was released one year later, but no additional promises have been made for the Pixel 2.
[Google Pixel Questions & Answers] surrealjam:
Fairly sure Pixel 2 is getting 3 years of OS updates which is probably a result of Treble. Google want to show off how easy updates are now so it wouldn't be good if they drop support after 2 years still.

As for the first gen Pixel, I don't believe our devices support Treble.

Edit: sorry, looks like first gen Pixel does support Treble. My bad.
[Google Pixel Questions & Answers] jss2:
I'd love it if Google extended the support period for their devices. And I could be wrong, but I'm basing stuff from this page:

https://store.google.com/us/product/pixel_2_specs

Under the "Safe and Secure" section, they state "Security updates for up to 3 years".

Farther down on the page, in the tech specs section, they say:

"Minimum 3 years of OS and security updates" and "Pixel’s software and security updates for three years. See website for details." And the website reference is the FAQ page that I linked to above. That page states:

"Pixel phones get Android version updates for at least 2 years from when the device first became available on the Google Store. After 2 years, we can't guarantee more updates." and "Pixel phones get security updates for at least 3 years from when the device first became available on the Google Store, or at least 18 months from when the Google Store last sold the device, whichever is longer. After that, we can't guarantee more updates."

Again, it'd be great to see these phones official support period be extended. But from what I can tell, Google is sticking to 2 years of OS updates + another 1 year of security updates. Even with Treble support.
[Google Pixel Questions & Answers] surrealjam:
I take your point. I was hoping they just hadn't updated the support page as it doesn't list the Pixel 2 yet. But you may be right.... the tech specs section is badly worded and may be misleading.
[Moto Z Questions & Answers] shiffty_dnb:
Hi, it's there any chance to re-lock bootloader on Moto Z with 7.1.1 and last security patch?
[Moto Z Questions & Answers] x-geo:
yes, there is a change.... only if you have a full image from 7.1.1 last security patch.... what patch do you have?
[Moto Z Questions & Answers] apocalypse_bg:
NPLS26.118-20-1 (August 2017) XT1650-03 reteu with unlocked second SIM
[Moto Z Questions & Answers] shiffty_dnb:
NPLS26.118-20-5 (1. september security patch)

Do you mean full image via TWRP recovery?I bought it already unlocked - I need re-lock bootloader due to use Android Pay (and warranty ofc) in my country.
[Moto Z Questions & Answers] x-geo:
with this firmware, you can relock bootloader

https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

with this commands via fastboot or mfastboot (reeplace fastboot with mfastboot)

fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot flash system system.img_sparsechunk.12
mfastboot flash system system.img_sparsechunk.13
mfastboot flash system system.img_sparsechunk.14
mfastboot flash system system.img_sparsechunk.15
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot

No, only via fastboot, this procedure remove twrp and leave the phone totally stock with lock bootloader
[Moto Z Questions & Answers] shiffty_dnb:
Ok, it's same codes as for apocalypse_bg right? When i extract XT1650-03_GRIFFIN_RETUS_7.0_NPLS25.86-30-12_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml they are in the folder only system.img 1-12, so that will not be a problem?
[Moto Z Questions & Answers] x-geo:
no, only depends of the ammount of system.img_sparsechunk in the file
[Moto Z Questions & Answers] apocalypse_bg:
Thank you for the info! Any mirror on the image, I'm getting an access denied :mad:
[Moto Z Questions & Answers] Dëmön_1:
For me its still not possible to lock the bootloader.

While flashing it this message appears while flashing: "Image signed with key bad key".

On boot the message of the open bootloader appears but as key there is only "n/a" shown, can this be the problem?
[Moto Z Questions & Answers] x-geo:
yes,

https://androidfilehost.com/?fid=745425885120763874

hello.... what security patch do you have?
[Moto Z Questions & Answers] Dëmön_1:
Its 1st september.
[Moto Z Questions & Answers] x-geo:
that's the problem...... we have to wait to the september full image to be available...
[Moto Z Questions & Answers] Dëmön_1:
After I have answered I tried something out and I think I had August yesterday.

Because the error with the bad key doesnt appear anymore while flashing - now it says its security downgrade.

Im not sure if I had the newest update installed.
[Moto Z Questions & Answers] x-geo:
can you post a "about phone" screenshot?
[Moto Z Questions & Answers] Dëmön_1:
Sure.

Now I have the newest update installed, thats for sure.

I beginning to think that I maybe did something wrong long time ago that I have now this problems.

The good thing is it is my 2nd phone and I am using it only at the moment to test things out.
[Moto Z Questions & Answers] x-geo:
don't worry, when the update comes out, i'll post it here... in the morning mine get the update... only have to wait the full image
[Moto Z Questions & Answers] x-geo:
ok mate, here is the update... go on and lock that bootloader... jejejeje... and post the result

https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
[Moto Z Questions & Answers] Dëmön_1:
Thanks but the link isnt working for me.
[Moto Z Questions & Answers] x-geo:
try again... doesnt work yesterday, but today it was
[Moto Z Questions & Answers] nouriassafi:
Managed to relock bootloader. Thank you so much for sharing.
[Moto Z Questions & Answers] Benoe:
Here you can find several full ROMs, there is even a 7.1.1 one (GRIFFIN_NPL26.118-20) as well:

https://androidfilehost.com/?w=files&flid=72584

Not sure which channel though.
[Moto Z Questions & Answers] Benoe:
Now I see that you linked the most current version (NPL26.118-20-5) with september patch.

Do you think I can safely flash this to my locked unrooted reteu XT1650-03?
[Moto Z Questions & Answers] nouriassafi:
Yes you can. I managed to relock the bootloader.
[Moto Z Questions & Answers] Dëmön_1:
Wich boot.img are you trying?

Is it possible to send it to me?

I downloaded the rom from another side because from official motorola it is saying I need to be logged it.

While flashing it is saying that it is a security downgrade and boot cant be verified.
[Moto Z Questions & Answers] nouriassafi:
I tried this image:

GRIFFIN_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (September 2017)

and I managed to lock the bootloader.
[Moto Z Questions & Answers] Dëmön_1:
I have done it.

The bootloader is locked and phone working.

I needed to do some steps.

The first time the bootloader was locked but the phone was only starting to fastboot, no normal boot was possible.

I unlocked the bootloader again and flashed the NPL26.118-20-5 rom again but this time without locking.

Let the phone boot complete until I could use it.

Now again into fastboot mode and flashed only boot.img, oem.img and all systemchunks, without erasing anything.

Locked the bootloader with "fastboot oem lock" and it worked.

Bootloader is closed.

EDIT:

I forgot to say something.

The rom I used was this: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Today I could not only start the download it was completly downloaded.

fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot flash system system.img_sparsechunk.12
mfastboot flash system system.img_sparsechunk.13
mfastboot flash system system.img_sparsechunk.14
mfastboot flash system system.img_sparsechunk.15
mfastboot flash system system.img_sparsechunk.16
mfastboot flash system system.img_sparsechunk.17
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
[Moto Z Questions & Answers] forexamplejohn:
Any chance you could be so kind as to rehost the zip somewhere like androidfilehost? I have to return my Z tomorrow (bluetooth is and was always totally broken) and I'd like to return it stock/locked if possible to avoid getting charged unfairly. Appreciate all the work you've done

*** edit - nevermind - if you google the zip name, there are some google plus pages that have links to the same moto URL - but they work, presumably the referrer links are whitelisted somehow. Will be giving this a try in a min!
[Moto Z Questions & Answers] Benoe:
Please let us know that after this reflash your battery consumption/SoT got any better than before.

Thanks.

---------- Post added at 04:28 AM ---------- Previous post was at 04:08 AM ----------

Please also let us know if your bt problem has solved by the reflash.

BTW what model/region do you have?
[Moto Z Questions & Answers] forexamplejohn:
Sure - the first attempt just now failed. I skipped the initial instructions, in that I omitted the 'fastboot oem lock' steps, and went right to your second step from post #26. Let it boot to setup, then exited back to fastboot, and did boot.img/oem.img/chunks/oem lock. Still got the 'untrusted' loading screen.

I have xt1650-03 united states GSM unlocked. Nothing has fixed bluetooth - it's screwed. Had the issue I found in several searches - the bluetooth settings page never finds any devices, and no devices can find the moto. The "scanning" wheel never turns. Disabling location scanning didn't help, nor did safe mode. Cache clearing via settings->apps, or TWRP didn't work. Flashing roms didn't work. I even got some 7.12 Bluetooth Sharing/BluetoothMidi apks and painstakingly set those up as system apps. No dice. Hardware problem, clearly, and I wasn't willing to go without bluetooth.

I'm trying the process again, this time going through the full flash instructions, then the flash without locking, then the step from #26 where you flashed some images and locked. Will see if that helps.

One other note - clogo has failed to flash each time I've tried to do it:

erasing 'clogo'...

(bootloader) Permission denied

FAILED (remote failure)
[Moto Z Questions & Answers] forexamplejohn:
no luck with the second go round either. could it be because I have bootloader version 91.07?
[Moto Z Questions & Answers] Dëmön_1:
Was is possible for you to lock the bootloader at all?

I could lock it at first try already but then the phone didnt want to boot at all - only to fastboot with the error "couldnt verify and use the software repair program on computer to fix it".

The bootloader was for sure locked but the phone not working.

I made some tests while I was at it.

I tried directly fastboot oem lock but of course the error was "still need signed boot".

flashed boot - now with fastboot oem lock I got "still need oem and/or system - key bad key"

At this point I did it like I have written in #26.

I could see that flashing boot seems to work.

I tried the other day with a zip downloaded from other place.

With the other rom it didnt work at all and trying flashing boot the error was "security downgrade". It should have been 20-5 but I think it wasnt.

Since bootloader lock the phone passes safetynet directly.
[Moto Z Questions & Answers] Benoe:
Do you have any improvement in battery consumption since the reflash, or is it the same as before?
[Moto Z Questions & Answers] kyndofux:
access denied

hey dude, can you reupload that .zip please. thanks in advance
[Moto Z Questions & Answers] Finsther:
Link Is dead man [emoji24][emoji24]

Enviado desde mi XT1650 mediante Tapatalk
[Moto Z Questions & Answers] sno1c:
Hi guys,

I want to return to stock and the relock the boot loader on my Moto z.

Actually i am using the resurrection remix custom rom.

Which steps do i have to follow to return to stock and relock?

I downloaded the firmware "GRIFFIN_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".

Do i just have to flash this rom with fast boot and everything is fine, or do i have to follow other steps?

Thanks in advance for your reply.
[Moto Z Questions & Answers] Benoe:
Flash should be enough, check Demon's post.

Tapatalkkal küldve az én XT1650 eszközömről
[Moto Z Questions & Answers] sno1c:
Thanks.

I just read his post and downloaded the firmware version from there.

So I will try his steps and see if it is working.
[Moto Z Questions & Answers] sno1c:
Just a short report of my progress:

Got my bootloader relocked. Followed post #26 and this did the trick:

Full flash of the stock rom.

Boot up the stock rom and do the inital android setup.

Reboot to bootloader.

Run "fastboot oem lock" it tells you to run and the command a second time so

Run "fastboot oem lock" again

Flash boot.img

Flash oem.img

Flash all sparsechunks

Run "fastboot oem lock"

Then the phone rebooted with a relocked bootloader into the android system.

Thanks a lot for this tutorial :)
[Moto Z Questions & Answers] matonka007:
Did the same as in #26 post and everything working now! This is only one working solution. Tried many other guides and nothing helps. Great. Now I have locked BL again and everything working :)
[Moto Z Questions & Answers] Dëmön_1:
Glad to hear that it worked for you guys too ;)
[Moto Z Questions & Answers] bionemesis:
Just wanted to make a complete post of how I just did this, as it combines information from 3 different posts.

Step 1: Download the latest factory image and extract the ZIP file to a folder of your choice.

Step 2: Boot the phone into fastboot mode and run the following against the files extracted from the ZIP file:

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash system system.img_sparsechunk.17
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot

Please note that the second last one (fastboot erase clogo) will likely fail.

Step 3: Boot into your phone and walk through the wizard just enough to get to the home screen. Don't bother signing in with your account, just skip everything.

Step 4: Boot your phone into fastboot mode again.

Step 5: Run the following:

fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash system system.img_sparsechunk.17
fastboot oem lock

And that's it! Your phone will automatically reboot after the last command a re-locked bootloader awaits.
[Moto Z Questions & Answers] Stuttgarter1234:
it works for me too. oem locked, but software status modified?
[Moto Z Questions & Answers] Shaggart:
link is briken, can someone restore it pls
[Moto Z Questions & Answers] Spaniard89:
In the step 5, following has to be executed first:

fastboot oem lock begin
fastboot oem lock begin
[Moto Z Questions & Answers] jmc86:
just tried this and was stuck with "still require signed boot.img" until after step 3 I turned on developer options and usb debugging on. I was then able to lock bootloader.
[Moto Z Questions & Answers] TobiPeter:
worked for me!

Thanks!
[Moto Z Questions & Answers] mwillian:
Works on XT1650-03 retbr?

The unlocked bootloader message go away?
[Moto Z Questions & Answers] Marke2566:
Hello, I need the link for download the GRIFFIN_NPLS26.118-20-5-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from android host.

thanks :o
[Moto Z Questions & Answers] Marke2566:
worked for me!

I also add this code:

fastboot oem fb_mode_clear

for return to normal boot.
[Moto Z Questions & Answers] edzilla:
I agree with the other posters here.

I had to:

at the end of step 3:

go to developers options and turn on USB debugging.

Before step 5:

fastboot oem lock begin
fastboot oem lock begin

After that phone is back to locked
[Moto Z Questions & Answers] knjigo:
I get error at the first line (flashing gpt.bin)

"Preflash validation failed"

"Security downgrade"

I get this with the latest firmware that I found.

Should I just ignore this message and keep going?
[Moto Z Questions & Answers] Loader009:
Always skip gpt and bootloader flashing. It won't work.
[Moto Z Questions & Answers] knjigo:
Yes i skipped these.

Tried to flash this one XT1650-03_GRIFFIN_RETEU-EMEA_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA.xml

i get error at boot.img also (not signed or corrupt)

As result, i have bootloop.

It stuck at warning about unlocked bootloader, and thats all. It started again.

---------- Post added at 04:21 PM ---------- Previous post was at 03:55 PM ----------

I flashed retbr image with no problem.

Started the phone. Worked everything fine.

then i started the last step with

fastboot oem lock begin (twice)

after that i get error on everything i tried to flash

like this:

(bootloader) Security version downgrade

(bootloader) Image boot failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)
[Moto Z Questions & Answers] Loader009:
If you had once stock Nougat on the Moto Z, you can't flash Marshmallow. (MPL indicates a Marshmallow ROM)

Look for a Nougat ROM, you can also flash RETBR on RETEU devices (did this already).

edit: Dunno on your current problem, never relocked the bootloader.
[Moto Z Questions & Answers] m0ritz:
Okay since my build number is: NPLS26.118-20-5-3 I downloaded "XT1650-03_GRIFFIN_RETAIL_7.1.1_NPLS26.118-20-5-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" ... I followed the flash instructions on here but

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

will not work I always get an error message:

and nothing works ... The phone will normaly start - bootloader still unlocked.

And since that does not work, anything after

fastboot oem lock begin

fastboot oem lock begin

does not work either.
[Moto Z Questions & Answers] knjigo:
I have the same problem. I think I'm never gonna be able to return to stock.
[Moto Z Questions & Answers] RedLink1155:
You could try turning oem unlocking off in developer options, I'm not sure if it will re lock your bootloader but it's worth a shot.