yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
I tried the flash-all from latest factory img and it failed:

[whiskeyjack] [~/pixel/sailfish-nmf26v]: ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloaderb' (32980 KB)...
OKAY [ 1.110s]
writing 'bootloaderb'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.152s]
finished. total time: 5.262s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.200s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radiob' (57192 KB)...
OKAY [ 1.833s]
writing 'radiob'...
OKAY [ 0.562s]
finished. total time: 2.395s
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.292s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FA6930309215
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'bootb' (24821 KB)...
OKAY [ 0.843s]
writing 'bootb'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [bootb] doesn't exist)
finished. total time: 1.295s

---------- Post added at 01:05 AM ---------- Previous post was at 01:05 AM ----------

Where can I get the vendor from?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Pretty sure it has to be extracted from OTA or just wait a little bit and PN will have it posted when ROM is released. I'm not on Jan patch so I don't have it. Your just getting the error when you boot right, if so you can still run the Rom w/o issue for now.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Haven't asked any ROMs yet but follow all of the forums and this is the first time I've seen mention of having to flash vendor separately. Just curious why we would have to do this? (I'm not even sure what it is I just know there's one on each slot :) )
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
Yep the ROM seems to work just fine. Just though I could sort out the vendor issue. If I can't for now (either because of my inexperience or lack of files) that's fine, as the ROM works.

Thanks for the help!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Take a look at DU or non AOSP Weta, flashing Vendor is part of install process. I haven't flashed this yet so I can't speak for this ROM. Vendor changes with every monthly google update/patch.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Personally waiting until there is a stable build up with Gapps and all pixel features functioning with fool proof install instructions.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Pixel and Nexus devices require flashing Vendor separately. Look at DU instructions. You can follow those same instructions for this ROM. They also have the vendor in their download section.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Is this ROM based on Dec or Jan?

---------- Post added at 05:22 PM ---------- Previous post was at 05:16 PM ----------

When you go to settings/about phone what security patch does it show, Dec or Jan?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Thats weird and I think where the confusion comes in in that I have never flashed vendor when installing WETA, DU and never had any problems?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
That's Pixel for you, strangest phone to flash stuff on so far!! I've been flashing Roms since the Thunderbolt and so far anyways the Pixel has been a little weird.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ninjanurse:
This one "nmf26v" if for Europe i think. So why both, maybe thats the problem. IDK
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
Dec. I assume that means I did something wrong?

---------- Post added at 02:33 AM ---------- Previous post was at 02:32 AM ----------

I tried both but neither solved the issue. Just trying to rule out the possibilities.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
If your on dec patch you should this vendor, actually go to G+ and go to Dirty Unicorns. They have the correct Vendor there.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
Tried, but failed. :(

[whiskeyjack] [~/Downloads]: fastboot flash vendor sailfish_nmf26q.img
target reported max download size of 536870912 bytes
sending 'vendora' (235186 KB)...
OKAY [ 7.554s]
writing 'vendora'...
FAILED (remote: partition table doesn't exist)
finished. total time: 7.616s

Oh well, I appreciate the effort!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Here is the problem guys.

When you flash a ROM the slot switches. So if you have correct vendor in one slot does not mean you do in the other.

Flash ROM and reboot to bootloader. Then fastboot vendor image from there.

There is nothing weird going on once you understand it. Only weird part is that the slots switch when flash, I think TWRP does it. Not sure.

Pretty sure this rom was based on nmf26q but if it isn't it's the one before it.

Edit: also make sure you have the latest fastboot. This article has the latest.

https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Does it fail when flashing in TWRP?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Get latest fastboot.

https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
I'm not sure. I keep losing TWRP. I try to use fastboot to boot a TWRP img and when I look at my SDCard it's just a bunch of folders with random/letters and numbers. I assume that's because I didn't reflash TWRP after flashing Carbon. But it seems weird that I basically now have to reflash the factory image, then TWRP, then ROM, then TWRP, all over again. Unless I'm missing something.

---------- Post added at 03:13 AM ---------- Previous post was at 03:11 AM ----------

Still fails with latest platform-tools.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
TWRP cannot decrypt without a password. That's why you see the funny text. After you flash factory image, boot into rom and set a password or pattern and you will be good to go with Twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TheNerdLLC:
Yeah, but you don't get the thrill of being apart of the testing the builds and teaching yourself very useful things along the way. If you have backups, factory image files and such, what matters? Just get tot testing, it's fun.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Completely agree. However I have yet to find a reliable way to restore a backup in TWRP. No one seems 100% sure yet on as what to back up and what not to. Until that's figured out, I'm going to sit back and read read read :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
Is it seriously that simple? Because it's been driving me insane. Historically I've just breezed through the device set up and skipped sign in/pin/etc because I knew I'd be flashing another ROM (I've flashed on Captivate, Galaxy Nexus, Nexus 4/5/5x, Honor 8, etc) and never ran into these weird things.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TheNerdLLC:
You can inbox me if you want. I know it says I am a Junior Member, but I have been on here since the fascinate days, lost access to my old account, so started one with my business name attached. I have flashed DU, Carbon and Weta.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Agreed, everytime I flash something i hold my breath until it boots!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I've been flashing all Roms and using TWRP buckup and restore. All works well. I've made my system crash once with Sabsrtaum theme but that was probably my fault. It's fun lol.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Like you said in an earlier post, this isn't rocket science. Once a user knows what overwrites what when flashing, it becomes very easy to decipher, and very fun to manipulate these slots. Know what all reside in the boot image, know what potentially overwrite it, then you'll know why you boot loop, and how to put things back. Know which slot you're playing in. I spent a full week when the first root came out for this and fastbooted every which way to experiment. And use flash-all as your get-out-of-jail card. Don't just take advices at face value, think them through. Things make sense. I'm having a ball with these Pixels.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
It becomes a little more complicated when you throw in a few different versions (should we be flashing U? V? Q? Does it matter?). For most of us a second slot is confusing, and I haven't seen an explanation as to why there are two, what's contained on either, or what TWRP targets when it's flashing. The posts might exists...I don't know, I'm still fresh with this device.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
The Pixel has 2 slots to facilitate OTA updates. When slot A is in use, it updates slot B. When the device is rebooted, it switches slot. Obviously, this is moot if you root or run a custom ROM since that disables OTA auto updates.

When flash-all is used, system image is flashed to the active slot, othersystem image is flashed into inactive slot. Both slots have their own boot images, system images, and share userdata. TWRP is flashed once but installs one copy in each slot. Kernel, SU, vendor are slot-independent.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
So once you've got a custom ROM installed, you're working on a single slot and don't have to concern yourself with the second slot?

If that's true, can I assume the second slot works reasonably well as a recovery partition?

---------- Post added at 04:34 AM ---------- Previous post was at 04:25 AM ----------

Finally! After re-flashing the OTA, TWRP, and ROM several times (it was my fault, I never set up the stock rom with a PIN), TWRP prompted me with a password, and my PIN let me in and read contents from the SDCard. From there I was able to flash the vendor img and now the error is gone.

Thanks a lot!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jonesin:
Attempted to DL and install this and I keep getting and error before install in TWRP. Have you succesfully installed this zip package before?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
I have not yet. [MENTION=7889765]TheNerdLLC[/MENTION] and a few others have reported successful installs though
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Yes and no, mostly yes, it depends on the ROM. So far, stock ROM (Weta) has flashed to the slot I specifically dictated, while AOSP likely installs to the opposite non-active slot.

In regard to your other question, you can certainly run a different ROM (custom or stock) in one of the slots. You can leave it unrooted as well. Can you use it as a safety net? Sure, as long as you didn't unintentionally affect it by flashing something that touched both slots such as twrp or bootloader or radio.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
You should make a thread in the general forum! While I've been around here forver I've mostly had Samsung devices so I've never needed fastboot. I'm learning a lot every day but I've yet to fully understand these slots and what does what and what needs to be flashed when lol. I've seen you help tons of people out on here so a good thread just explaining how to manipulate the slots would be awesome. I'm sure a lot of us would benefit from it. For example I have no idea when I would ever need to flash boot.img.. yet I've seen so many people throw it around as a step for different reasons. I know we had a lengthy discussion about what's stored in the slots and jcase cleared some things up but it's still very confusing
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jonesin:
Downloaded a second copy and checked MD5 and I am still ending up with the same error.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
This package worked for me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
DU flashes to inactive slot as well. Developers said that's how TWRP flashing works in Pixel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Are you saying it flashes too both slots? Because I'm on DU and it flashed to my active slot, being A.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
You'd "fastboot flash boot boot.img" to recover your original boot image. That sounds logical and over-simplified, right? Because it is. Boot.img contains kernel and information on mount points and basic boot instructions. So, if you flash a custom kernel and overwrite your boot.img, and have a boot loop into TWRP for example, you'd fix it this way. Then have to turn around and reinstall TWRP and SU to get those functions back.

---------- Post added at 11:40 PM ---------- Previous post was at 11:30 PM ----------

Every other Pixel ROM flashes only to the active slot, just not this Carbon. So it's not TWRP. I've had stock + stock, stock + Weta, stock + DU, DU + Weta, but I've never had Carbon + anything else after flashing Carbon. I always ended up having to flash stock back to one slot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
That makes more sense, both DU and Weta flashed to my active slot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
So just trying to understand this.. I haven't installed TWRP or Root yet. I was waiting for a new TWRP hoping some issues were resolved. Let's say I flash carbon as my first ROM. From what your saying it flashes to both slots. How would I then go about flashing completely stock to the other slot and then how would I boot in between them?

So let's say I have that all set up and working and I wanted to go back to 100% stock at some point. Do I just use flashall and that will overwrite both slots back to completely stock?

I'm sure once this clicks in my head it's gonna be a lot more simple but for some reason it hasn't been explained in a way that made sense to me yet so the slots are confusing because I know nothing about boot.imgs and vendor.imgs etc etc etc
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spaceman860:
DU always flashes to the other slot when you flash it and when you reboot it switches to that slot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
So if my active slot is A and I flash DU it flashes too B? If I make a backup and need to restore it do I have to restore from slot B?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spaceman860:
Correct if you're on slot A and flash DU it will flash to slot B. If you restore a backup it will restore to the slot you're on.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Wow, learning something new everyday with this phone!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
I am sure you're correct (you're the dev of DU, right?). However, that's not my experience. I've installed DU 3 times this past weekend from a previously flash-all state. I wanted to test just for the heck of it. I do everything 3 times to establish a repeatable cause and behavior conclusion. Maybe I had too much New Year's celebration, but I am pretty certain I made slot b active, verified it with fastboot reboot bootloader, then installed DU. It booted up in b. You have me curious now. I'll do it again today. I have the feeling you're right, but I know I couldn't have been that drunk. (I'm just kidding, I don't even drink.)

PS: Let's take this discussion elsewhere or off-line. Since this thread is about Carbon, I want to show Myself5 the respect his ROM deserves. I'll attempt to make a video of my DU installation and we'll take a look. I'll DM you.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
That one is similiar to the OpenGApps method I used on my unofficial build.

Looks intresting, will try right away.

Ok, thats messed up. Did you modify the installer scripts on DU then? The default AOSP way is the installation to both the partitions. Actually, would you be up for a quick chat on Hangouts/Telegram/Whatever you want? Would be awesome if you can let me know about your prefered way of communication :P I'm having some questions for the Pixel development that I've not yet been able to answer on my own.

To the others: The current official build as well as my unofficial build is based NMF26Q (As that was build before the January Patset dropped). However, the Weeklys that will be released today are going to be based on NMF26V (We went for that as its the Pixel branch with the newest security patches, no matter if its Europe only or not, there won't be drawbacks).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
[MENTION=4433359]spaceman860[/MENTION] I just reflashed DU to confirm what you said. Yes, you are right. I stand corrected. I had Weta on a, DU on b. After reflashing DU to b as the chosen active slot, my device booted up to a. Now I ended up with DU on both a & b. Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spaceman860:
You can hit me up on telegram [MENTION=4433359]spaceman860[/MENTION] or hangouts doesn't matter.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
So right now our best bet is to have the Playstore and good play services apks on hand until gasps work?

Can I flash the weekly right over top your unofficial?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Nice, will do.

The Gapps link I quoted should work. You should be able to flash that with the weekly that will be released later today.

You can flash over my unofficial just fine, system will be wiped anyways. Be sure to flash GApps afterwards.

GApps survival script is WIP for the AB systems.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Good to hear I will try the weekly and the beans Gapps and report back.

Any chance of a built in updater in the Rom?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
We're working on an updater already ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Would there be a way to flash this ROM onto just my currently inactive slot, and leaving my current active slot exactly how it is? Then being able to switch between the two?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] fix-this!:
I assume theres no new build for the jan update?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
There is a build being released later today that is the Jan update. "V" variant.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Yes but you have to wipe data anyway to go to custom ROM so you didn't really accomplish anything. Data is shared between slots.

Then to go back to stock you would flashall.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Could I back up all data with TWRP now, and restore that data while running carbon?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] computercarl:
Does the variant really matter to us though? I thought the differences on the variants were radio modules. I have a VZW Pixel, which is currently running stock "U" versions, but I can safely flash a "V" can't I?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
I'm wondering the same thing. I'm currently on "U" as well, as I'm in the US.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
A work around would be to create another user which can be accessed by on of the slots.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Doesn't matter to us the flasher, nothing different on our end.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] computercarl:
I'm waiting for that rom link... f5,f5,f5,f5,f5,f5...
[Lenovo Vibe K5 Plus Guides, News, & Discussion] netship:
First of all Happy new year!

Here is orignal thread but since we got our own Forum, I am making a new one.

Update-

Finally i update my phone with latest Stock with Volte(s105) and made a twrp backup but file is too large for uploading(Cellular data),

So If any devs want any specific folders or files I will upload.

BTW i think lenovo s105 update modem partition because on aokp when i dial *#*#4636# i saw VoLTE provision flags but after update even on Aokp now i can see VoLTE and video call provision Flags(See Screenshot)
[Lenovo Vibe K5 Plus Guides, News, & Discussion] dr.bathman:
Uploaded vibe k5 a6020a40 Indian varient with twrp flashable backup of s102 firmware (which enables volte in vibe k5 a6020a40) ..

https://mega.nz/#!qtZFQDLb!udeBTpXCW7XPj-TAczAtRWhtKLf65Ohok8Simubk9Hw
[Lenovo Vibe K5 Plus Guides, News, & Discussion] shomil49:
can anyone cofirm do volte work we flash cm14 after upgrading to official volte update ...
[Lenovo Vibe K5 Plus Guides, News, & Discussion] netship:
Not working but we get another flag(video). I think we only need some little modification of some files.
[Lenovo Vibe K5 Plus Guides, News, & Discussion] Shivender Kumar:
Is it the whole firmware backup. If i restore this will i get volte enabled in my phone
[Lenovo Vibe K5 Plus Guides, News, & Discussion] DragonSpitz:
Just install the latest stock firmware from http://moto.shreps.fr/ and install using qfil

Hello VoLTE :)
[Lenovo Vibe K5 Plus Guides, News, & Discussion] rajuz:
Works on Lenovo K3 Note ?
[Lenovo Vibe K5 Plus Guides, News, & Discussion] k4k:
volte for custom roms?
[Lenovo Vibe K5 Plus Guides, News, & Discussion] firemaker911:
[MENTION=7684607]netship[/MENTION]

No One Answer This, I Want A Answer Too To This Question.....!!!
[Lenovo Vibe K5 Plus Guides, News, & Discussion] riazul.islam20:
Please visit this thread. You may find solution.

Please hit Thanks if it works. :)
[Lenovo Vibe K5 Plus Guides, News, & Discussion] mejarkarak:
Does it support volte video calling facility ??
[Lenovo Vibe K5 Plus Guides, News, & Discussion] riazul.islam20:
No aosp rom supports ViLTE. May be developers can help to enable this feature in future.
[Lenovo Vibe K5 Plus Guides, News, & Discussion] mayukh2000:
Can't use VoLTE in lineage 14.1 on lenovo a6020

Its a super cool os but I'm stuck the VoLTE issue. In India VoLTE is a major feature as we use a Jio sim which uses VoLTE for calling. There is an option to enable VoLTE but it doesn't matter weather it is enabled or not bacause I simply can't make a VoLTE call. It is not a Jio sim issue as in the stock rom after an OTA uodate I used to call from Jio. Any solutions? Otherwise I've to revert back to stock rom:rolleyes:
[Lenovo Vibe K5 Plus Guides, News, & Discussion] riazul.islam20:
Have you enabled Wi-Fi video calling feature? If not, do it and restart your device. That might solve your problem.
[Lenovo Vibe K5 Plus Guides, News, & Discussion] mayukh2000:
Thanks for the response?.

Yeah I tried wifi calling, but that doesn't work.

I found a solution. First you have to flash the stock rom VoLTE functionality. Then you have have to flash the custom rom. (One thing to note here that while installing the custom rom, one should not wipe the system). But still there is a problem, you have to toggle off and on the Enhanced 4G LTE mode(VoLTE) to activate VoLTE functionality. And if you turn on or off mobile data the VoLTE functionality will be gone, then again you have to do the same.