Related
Hi guys,
I've seen this question asked a few times, but no one ever answers it. I tried looking around on other sites, but can't seem to find an answer.
I just came over from a Galaxy S5, and I don't think we ever used those. Is there anybody who'd be willing to point me in the direction of knowing?
It holds proprietary binaries for the Nexus 5x, 6p and 9, from what I've read.
Hey OP, did you find out what a vendor.img is yet? Have also come to Nexus from Samsung. Flashing my first rom, and don't know what this vendor file is. Or if I even need it. Like you, have found threads where people ask, but no definitive answers...
I've been curious about this, too.
Also wondering how the Vendor partition differs from System. What do the data/functions in the Vendor partition do?
EFS partition seems to be specific to the individual device (unique IMEI). Is Vendor specific to each phone too, or do all Nexus 6Ps have the same thing in the Vendor partition (assuming they're on the same build of Android)?
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Gorgtech said:
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Click to expand...
Click to collapse
OK cool, so the vendor file is Nexus specific. And the OS won't operate properly without it? So I assume it's not possible to bake the vendor file straight into a custom rom? Just flashed pure nexus vendor.img along with the rom. Still not exactly sure what it does, but hey, if I need it, I'll flash it if I change roms.
Gorgtech said:
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Click to expand...
Click to collapse
Supplemental information about Vendor from a former member of the Android team
SlimSnoopOS said:
Supplemental information about Vendor from a former member of the Android team
Click to expand...
Click to collapse
Thanks for the link. So from my understanding, all the proprietary nexus files are stored on it's own 'vendor' partition, separate from the OS. And is updatable with it's own .img. Which is different to touchwiz (for eg.), which merges it's own files with android into the one partition.
Edit: FYI, just found this in PureNexus FAQ's:
Q: What is the vendor.img/vendor.zip? (5X and 6P only)
A: The vendor partition is new to Nexus phones with the 5X and 6P. Previous devices had the vendor files (proprietary binaries and drivers) within the system partition (/system/vendor); on these devices, they now have it in their own partition (/vendor). If this is not up to date, you will get an error message and need to flash the latest one so your phone continues to work properly. Beans has made this a TWRP flashable file available in the OP of the 5X and 6P threads (also linked below) so you do not have to fastboot it.
I'm a bit late on this one, but does anyone know if updating OTA (stock android updater) updates the vendor partition as well or do you specifically have to flash it?
So, with this partition for drivers ROMs can keep the same camera quality as stock?
Llaver said:
I'm a bit late on this one, but does anyone know if updating OTA (stock android updater) updates the vendor partition as well or do you specifically have to flash it?
Click to expand...
Click to collapse
No, the vendor.img does not need to be flashed independently of the OTA update.
I have seen it in many phones other than mentioned in the thread, it is even in infinix phones. what i think is it contains apps from google like maps, drive, gmail, photos, and also some apps from the manufacturer of the phone. why i think this is the case? here is the my guess.
yesterday when i tried to remove google bloatware and manufacturer bloatware with root permissions etc. it didn't work.
i have magisk root, i had set selinux permissive as someone told me it would help BUT i was still unable to remove bloatware. they were removed for now but whenever i rebooted my phone, they were reinstalled and i think this vendor file does that.
as per google's android documents here is the difinitoin.
vendor: The vendor partition contains any binary that is not distributable to the Android open source project.
means, google apps are never distributed with AOSP but manufacturers does that via vendor.img to make it non-removable? i guess.
jameeldroid said:
I have seen it in many phones other than mentioned in the thread, it is even in infinix phones. what i think is it contains apps from google like maps, drive, gmail, photos, and also some apps from the manufacturer of the phone. why i think this is the case? here is the my guess.
yesterday when i tried to remove google bloatware and manufacturer bloatware with root permissions etc. it didn't work.
i have magisk root, i had set selinux permissive as someone told me it would help BUT i was still unable to remove bloatware. they were removed for now but whenever i rebooted my phone, they were reinstalled and i think this vendor file does that.
as per google's android documents here is the difinitoin.
vendor: The vendor partition contains any binary that is not distributable to the Android open source project.
means, google apps are never distributed with AOSP but manufacturers does that via vendor.img to make it non-removable? i guess.
Click to expand...
Click to collapse
????? This is a nexus, it contains no bloat because its a google device, its not a Motorola , lg, samjunk etc. Those devices contain "bloat" there are zero applications installed from the mfg, its stock android.
Not sure why you can't remove system apps, sounds like user error. I have never had an issue removing something with root and titanium backup.
The vendor contains what it says it does the binarys, blobs and other interworking's of the device that are needed for it to operate.
Hello. I'm a new to Android world. I have a Moto G4 (XT1622) and I install AOSiP-8.1-Derp-athene-20180501/Android Open Source Illusion Project ROM (arm64).
I see 'your vendor image does not match the system' message on every boot with a prompt to flash npjs25.93-14-13.
I download latest Nougat ROMs (arm32) (both adb and twrp flashable). Try both methods of flashing with success.
Then I install custom ROM again (with TWRP, clean) and see the same message again.
I search regarding this problem and everything ends with flashing Stock ROM and perform installing custom one again, what I done and mention of vendor.img file.
I try to find such file but no luck, my device has only vendor folder.
So my question is: how to remove this message in the custom ROM?
I post it here because ROM's thread is closed
Thanks.
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning signifies a mismatched vendor and system partition. The vendor partition was integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS base. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone. The phone will fail to boot if you mismatch the vendor.img with a different OS base. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat.
Click to expand...
Click to collapse
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
SlimSnoopOS said:
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
Click to expand...
Click to collapse
Thanks so much for the swift reply! I'll check these links out right away. I'm sure they will fill in the gaps for me.
Best,
KT
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
jhs39 said:
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0..
Click to expand...
Click to collapse
MultiRom support for this device was released when Marshmallow was out. So MR33 is based on the Marshmallow branch and ships with 3.0.2. The developer just isn't ready to release support for Nougat 7.0 and couple that with the issues of TWRP 3.0.2-x. He's actively pushing commits to support Nougat.
Sent from my Nexus 5X using Tapatalk
jhs39 said:
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
Click to expand...
Click to collapse
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
KilgoreTrout71 said:
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
Click to expand...
Click to collapse
It might just take a while for the service to go through. Good luck.
For those that didn't receive the update yet, I've requested the links to the Wileyfox nougat support team, so here you can download the incremental, recovery and fastboot images of the latest upgrade TOS118C.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
INCREMENTAL UPDATE (OFFICIAL) (DRIVE MIRROR LINK by me) (from TOS089A to TOS118C / from decf3a575d to aa4d5d86bc)
In the post below you can have some information on how to grab OTA links from the WileyFox BSP server. Have fun, and don't forget to debloat your system
How to grab the official OTA from BSP's server
In the OP, I left a link to the official incremental update right from the OTA server (which I'll talk about a bit later). If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
... Or you can just wait til someone mirrors it, like I already did
Lastly, as a side note, I'd also like to comment the following, regarding BSP:
Wileyfox's devices software is now in charge of this company, called BSP.ninja and that clearly defines themselves as a company to "launch an Android device without knowing where to start". It's said to be formed by former Cyanogen employees, or, at least Ricardo Cerqueira @aremcee (which btw, is also in charge of the Open Source code available in BitBucket for the Wileyfox devices), since he's the owner of the domain. In any case, what I want to say is that the code is being done quite possibly by the very same people that did the job at the now dead Cyanogen, so it shouldn't be a reason to worry. Also, it'd be awesome if the team released a working device tree so that the community could bring custom ROMs just like you (the team) used to do.
linuxct said:
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
Click to expand...
Click to collapse
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?
boa05 said:
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?
Click to expand...
Click to collapse
Correct. I'm preparing a new version of my debloater tool, and I'll briefly explain in it's thread how to move from TOS089A to TOS118C without losing anything in rooted and/or debloated devices. Stay tuned!
Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.
zerospaced said:
Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.
Click to expand...
Click to collapse
I also skin my phone through substratum (the default orange theme is disgusting), I use magisk and plenty of other tools both systemless or even require modifying the system partition (like Wileyfox debloater), and, using the instructions I wrote in this post here I've found no single problem upgrading my device from a debloated, rooted and themed TOS089A to TOS118C to then debloat, root and theme it again. It's true you will need to install your substratum themes again, but the rest should work perfect.
I've tried the recovery update on my Swift 2X but can't get it to boot. I have TWRP installed (3.1.0-0) and it's rooted via SuperSU. Do I have to unroot first?
Edit for more info: I did the OTA upgrade from the stock CyanogenOS ROM to 7.1.1 TOS089A. Then I installed TWRP and flashed SuperSU. The OTA to TOS118C predictably doesn't work. Flashing the recovery image via TWRP seems to go fine but I'm stuck at the white "Wileyfox powered by Android" screen. Tried wiping Cache/Dalvik but no dice.
Edit 2: flashing Magisk afterwards seems to make it work.
I try to install the ZIP via TWRP and after the process ends the phone reboots but it remains stuck at the "WileyFox" white screen.
EDIT: I tried the fastboot one and it worked. Sometimes is hard to understand our devices
I'm guessing it's some kind of dm-verity issue? Flashing in TWRP worked for me when I flashed Magisk 12.0 afterwards, which seems to take care of dm-verity. Linuxct suggested installing Magisk in his debloat thread and I thought "what's the harm". Now I'm a happy camper.
Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.
Will this Firmware work on my Swift 2 Plus?
Cappucinto said:
Will this Firmware work on my Swift 2 Plus?
Click to expand...
Click to collapse
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.
Afifus said:
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.
Click to expand...
Click to collapse
Thank You so much
Installed it via fastboot and now iam stuck in a bootloop :S
EDIT: Did a factory reset in recovery! Works now.
Swift 2 Plus on 13.1.5 Cyanogen. Which method is best to install Android 7.1.1 TOS118C manually. The phone is stock, not rooted. Thanks
gaborkov9 said:
Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.
Click to expand...
Click to collapse
If you use the
Code:
adb reboot "dm-verity enforcing"
can you remove the dm-verity menu on boot or do you need it left as after bootloader unlocked?
TOS373J?
Anyone have the images for the latest update?
TOS373J OTA
other link
Pooh042 said:
TOS373J OTA
other link
Click to expand...
Click to collapse
doesnt work gives me instal error 7 when i try to instal it
DarthBraindrain said:
doesnt work gives me instal error 7 when i try to instal it
Click to expand...
Click to collapse
what is your current firmware version?
8.1 Final, updated adb/fastboot, & problems and fixes - update 12/17/2017 TWRP fixed
UPDATE 12/17/2017: @phaino00 and other users have reported that TWRP v3.2.1-0.img take care of the internal storage decryption problem.
https://forum.xda-developers.com/showpost.php?p=74868928&postcount=380
Get it at https://twrp.me/. It has been reported that FLASHing the new TWRP.zip (as opposed to just fastboot boot twrp.img) will make the phone only boot back into recovery every time - never back into Android. I haven't not personally confirmed this, however.
UPDATE 12/9/2017: Word is at https://forum.xda-developers.com/showpost.php?p=74782925&postcount=6238 that Magisk v14.2 (not v14.5 build 1456) both works with Android 8.1 AND with FlashFire - which is an alternative to using TWRP. I used FlashFire 100% from Android 8.0 November for installing complete firmware images and flashing ElementalX and SuperSU, so may work just fine with ElementalX v3.00 and Magisk v14.2.
I have not tested this myself.
UPDATE 12/7/2017: If you had a Contacts Sync issue, the fix was shared by @Jank4AU in this post https://forum.xda-developers.com/showpost.php?p=74767941&postcount=45. Make sure and understand it's the "Contacts Storage" app, not merely the "Contacts" app. THEN Storage section, then Wipe App Data. HEADS UP: Call History will be wiped and it may take a minute or two for Contacts settings to re-sync so your Voicemail tab may disappear and reappear, if applicable.
UPDATE 12/6/2017: ElementalX v3.0.0 has been updated by @flar2 for Android 8.1 Final and the December security patches. IF YOU ROOTED, you MUST flash the stock boot.img before flashing any version of ElementalX.
DO NOT USE FlashFire v0.73 under Android 8.1 Final, at least with Magisk v14.5 build 1456. Just seem to get minutes-long black screen. A long black screen can be normal with FlashFire, but I think that was too long.
Heads up, the standalone platform tools (adb, fastboot...) have changed since the day before Android 8.1 Final was released. Moreover, the zip is now 4.30 MB (14.5 MB uncompressed) vs before and a month ago was 9.31 MB (30.7 MB uncompressed), and was 7.16 MB in July.
Get the latest Platform Tools in preparation for flashing 8.1 final: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
NOTICE: This link doesn't change, but the file it links to does every so often.
Edit: Links up: https://dl.google.com/dl/android/aosp/sailfish-opm1.171019.011-factory-56d15350.zip
SHA-256 56d15350a2c54960b149fc8a080547f17e1c4bba4da89bb03f6c634746ca6318
Used FlashFire to flash entire firmware package including enabling to flash all the dangerous/protected partitions, then had FlashFire flash ElementalX 2.03 (seems to be working fine), then SuperSU 2.82 SR5. DO NOT install ElementalX v2.03 AND/OR SuperSU v2.82 SR5! ElementalX v2.03 caused a system error dialog at least on first boot, caused bootloops like crazy when you go to reboot, and SuperSU v2.82 SR5 just doesn't achieve patching selinux, so no root. SuperSU v2.82 SR5 problem confirmed with others. You should be able to FlashFire ElementalX v3.00 and Magisk v14.5 build 1456 works fine IF you do them in the same chain/after having FlashFire flash the full firmware. FlashFire doesn't seem to work once you're booted into Android 8.1.
The SuperSU installation, I noticed had some failure to patch selinux.
The error on every boot after installing Magisk v14.5 build 1456 is:
Code:
[SIZE="4"][B]Android System[/B][/SIZE]
There's an internal problem with your device. Contact your manufacturer for details.
and an OK button.
I don't think the screen will even sleep with this dialog in front. At least not until my preferred 10-minute delay but I'm told it's harmless otherwise.
KNOWN ISSUES
SuperSU v2.82 SR5 problem confirmed with others.
Both fastboot boot TWRP v3.2.0-0 and 3.1.1-1 don't accept my pin. TWRP problem confirmed with others. No solution other than to use USB-OTG or remove your PIN to install the Magisk v14 build 1456 zip. Hint: A USB 3.0 flash drive via USB-OTG in TWRP is FAST! Too bad we can't backup 8.1 data yet since no decryption (unless you remove PIN).
See the update at the top of the post, the latest version of TWRP is reported to take care of the internal storage decryption problem.
A select very few or individual contact(s) are missing from the Contacts/Phone app. Contacts missing problem confirmed with others. Wiping the Contacts app data didn't help. Turning Contacts/People sync on and off didn't help. Rebooting didn't help. Haven't tried wiping Phone app data but I wouldn't think that would be related since Contacts is a separate app. I've confirmed that my missing contact(s) are still listed in Google Contacts through the web UI on a PC. Exporting via csv/vcf and re-importing/duplicating the contact hasn't helped two of us who have tried that.
Fix shared by @Jank4AU in this post https://forum.xda-developers.com/showpost.php?p=74767941&postcount=45. Make sure and understand it's the "Contacts Storage" app, not merely the "Contacts" app. THEN Storage section, then Wipe App Data. HEADS UP: Call History will be wiped and it may take a minute or two for Contacts settings to re-sync so your Voicemail tab may disappear and reappear, if applicable.
sliding_billy said:
I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.
Click to expand...
Click to collapse
There's an error dialog, as noted above, every time you boot into Android after flashing Magisk v14.5 build 1456.
Some users are being offered an OTA from the already flashed Final 8.1 to the DP2 of 8.1. Two users reported. The fix reported by @TonikJDK is to unenroll from the beta program. Thank you!
FlashFire v0.73 doesn't work with Magisk v14.5 build 1456 on Android 8.1. Word is at https://forum.xda-developers.com/showpost.php?p=74782925&postcount=6238 that Magisk v14.2 (not v14.5 build 1456) both works with Android 8.1 AND with FlashFire - which is an alternative to using TWRP. I used FlashFire 100% from Android 8.0 November for installing complete firmware images and flashing ElementalX and SuperSU, so may work just fine with ElementalX v3.00 and Magisk v14.2.
I have not tested this myself.
Let me know if there are any other issues, and links to confirmation posts by others if you have them. I won't post one-off issues here, only those confirmed reported by two or more people. Thanks!
Click to expand...
Click to collapse
Was able to flash-all with -w removed.
Attempted to fastboot boot twrp and adb sideload supersu, but I'm not able to gain root.
Anyone else with any success?
patso23 said:
Was able to flash-all with -w removed.
Attempted to fastboot boot twrp and adb sideload supersu, but I'm not able to gain root.
Anyone else with any success?
Click to expand...
Click to collapse
Fastboot boot TWRP and installed magisk 14.5 via usb-otg and root is successful.
phaino00 said:
Fastboot boot TWRP and installed magisk 14.5 via usb-otg and root is successful.
Click to expand...
Click to collapse
I haven't had any success getting fastboot booted twrp.img to accept my pin. Did you install magisk before setting up Android or after? But I suppose from USB-OTG bypasses that issue, so thanks for reporting.
roirraW "edor" ehT said:
I haven't had any success getting fastboot booted twrp.img to accept my pin. Did you install magisk before setting up Android or after? But I suppose from USB-OTG bypasses that issue, so thanks for reporting.
Click to expand...
Click to collapse
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.
phaino00 said:
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.
Click to expand...
Click to collapse
Thanks again, seems to be working 100% with ElementalX v2.03 and Magisk v14.5 (build 1456).
PSA: I recommend avoiding ElementalX 2.03 on 8.1 Final until it's updated. At first, it seems to be working, but boot loops galore when you reboot. No boot loops without it. Also, just because it's related, SuperSU 2.82 SR5 doesn't work for me (repeated tries on fresh installs) on 8.1 Final. Magisk 14.5 build 1456 seems to, though (thanks @phaino00).
phaino00 said:
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.
Click to expand...
Click to collapse
can you tell me which version of v4a you are working with? I cant seem to find a stand alone version of it but have read several posts whee it's been mentioned. I keep ending back up in the ARISE thread. thanks for the help
Having a major problem with my most important contact not syncing. My wife! I see her in Google in the web ui but she's not on the phone. Tried clearing Contacts app data, turning off sync and back on, rebooting the phone multiple times, I exported her contact info from the web ui and reimported her so there's now two, still no change.
quinejh said:
can you tell me which version of v4a you are working with? I cant seem to find a stand alone version of it but have read several posts whee it's been mentioned. I keep ending back up in the ARISE thread. thanks for the help
Click to expand...
Click to collapse
I have been working with this:
https://forum.xda-developers.com/pixel-2-xl/how-to/viper4android-8-1-0-t3711474/page2
The v4a is 2.5.0.5 app and 2.5.0.4 driver. This seems to be working for some on the pixel 2.
I have not succeeded yet.
---------- Post added at 03:58 AM ---------- Previous post was at 03:32 AM ----------
roirraW "edor" ehT said:
Having a major problem with my most important contact not syncing. My wife! I see her in Google in the web ui but she's not on the phone. Tried clearing Contacts app data, turning off sync and back on, rebooting the phone multiple times, I exported her contact info from the web ui and reimported her so there's now two, still no change.
Click to expand...
Click to collapse
I lost my son and sister....very odd issue
Besides what you did, I exported their contact info as a .vcf and imported to contacts app. Their contact info showed up and within seconds disappeared again.
The latest SuperSU is not working, saying patching sepolicy failed.
A rather strange thing is that the files I have flashed in twrp does not populate after system boots, eg, I placed a file under /system/system/blabla (I have checked mount system read/write in twrp), but after a reboot, I could not find the file under /system
churchmice said:
The latest SuperSU is not working, saying patching sepolicy failed.
A rather strange thing is that the files I have flashed in twrp does not populate after system boots, eg, I placed a file under /system/system/blabla (I have checked mount system read/write in twrp), but after a reboot, I could not find the file under /system
Click to expand...
Click to collapse
I have the same sepolicy crash. Does yours happen on a non-XL Pixel, because that issue only happened to me on the non-XL. My XL rooted fine with the USB install workaround.
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
sliding_billy said:
I have the same sepolicy crash. Does yours happen on a non-XL Pixel, because that issue only happened to me on the non-XL. My XL rooted fine with the USB install workaround.
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
Click to expand...
Click to collapse
Yes, mine is pixel, generation 1.
I tried to install magisk 14.5 and it works flawlessly.
phaino00 said:
I lost my son and sister....very odd issue
Besides what you did, I exported their contact info as a .vcf and imported to contacts app. Their contact info showed up and within seconds disappeared again.
Click to expand...
Click to collapse
Really odd. That is why they should wait longer than a week after a DP to release a Final. [emoji16]
Guess I'll type her in manually for now, at least basic info. I have her exported and since I can see her in the web UI nothing is really lost.
TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?
m0h1t said:
TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?
Click to expand...
Click to collapse
I removed any screen locking, had a pattern before and tried with pin and password. Removing the screen lock solved the problem.
m0h1t said:
TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?
Click to expand...
Click to collapse
You can also use USB-OTG to install things (like Magisk). I'm sure TWRP will have to be updated before it'll work with decrypting the internal storage on 8.1 Final. Keep an eye on the OP - I'll update there when or if it's fixed.
I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.
Has anyone gotten MTP working to access internal storage from a Windows PC from within Android 8.1 Final WITHOUT turning off USB Debugging? Device Manager sees it just fine on Windows 7 but it's not available until I turn off USB Debugging - or is that normal!? Actually, even with it off, Windows Explorer sees the Pixel, but when I enter it, there's no storage listed.
Once again, USB-OTG worked just fine within Android 8.1, at least.
sliding_billy said:
I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.
Click to expand...
Click to collapse
I do use a custom launcher (Nova - can never live without it for long), but thanks for noticing since I wouldn't have. I'll add that as a known issue.
Spent hours trying to fix contacts last night, haha.
I got a few that kept disappearing on sync to sync and stay by erasing the anniversary date listed and then manually readding it on my phone after the sync.
I've put together a guide for building your own LineageOS 17.1 (android 10) using a docker build environment or on your own system. The guide includes environment setup, and installation instructions as well as some troubleshooting and debugging information.
The easy way is as simple as cloning two git repos, getting the docker image, and running build_sargo.sh
The hard way goes into more detail, requires more previous knowledge, and doesn't use the docker but is useful for getting more familiar with the process.
The docker image is one that already existed for building lineageos 16modified to supports lineagsos 17.
It also includes patches that haven't been merged upstream yet that fix bluetooth, a bootloop, and increase battery life.
With some small modifications, this could also be used for the Pixel 3a XL (bonito)
https://github.com/SolidHal/Build-lineageos-sargo
Thanks for this!
Stealth111
SolidHal said:
I've put together a guide for building your own LineageOS 17.1 (android 10) using a docker build environment or on your own system. The guide includes environment setup, and installation instructions as well as some troubleshooting and debugging information.
The easy way is as simple as cloning two git repos, getting the docker image, and running build_sargo.sh
The hard way goes into more detail, requires more previous knowledge, and doesn't use the docker but is useful for getting more familiar with the process.
The docker image is one that already existed for building lineageos 16modified to supports lineagsos 17.
It also includes patches that haven't been merged upstream yet that fix bluetooth, a bootloop, and increase battery life.
With some small modifications, this could also be used for the Pixel 3a XL (bonito)
https://github.com/SolidHal/Build-lineageos-sargo
Click to expand...
Click to collapse
There should be VERY little modification required from sargo to bonito as one is simply a different size than the other. (I'm actually surprised that nobody ever compared the two in terms of hardware (especially since their simultaneous release).
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
anonym12 said:
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
Click to expand...
Click to collapse
If you include gapps in your build, the esim manager should stop crashing. If running gappless, I remove esim and hotword enrollment from the proprietary files.
gee one said:
If you include gapps in your build, the esim manager should stop crashing. If running gappless, I remove esim and hotword enrollment from the proprietary files.
Click to expand...
Click to collapse
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
spinxen said:
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
Click to expand...
Click to collapse
The issue is the new dynamic partition scheme doesn't leave enough room to install any extra system apps. There is a patch on the Lineage Gerrit, but it hasn't been merged (https://review.lineageos.org/c/LineageOS/android_device_google_bonito/+/261941).
fireclaw722 said:
The issue is the new dynamic partition scheme doesn't leave enough room to install any extra system apps. There is a patch on the Lineage Gerrit, but it hasn't been merged (https://review.lineageos.org/c/LineageOS/android_device_google_bonito/+/261941).
Click to expand...
Click to collapse
Thanks for letting me know, so as of now there is no workaround to get GApps work with this branch after it has been installed?
spinxen said:
Thanks for letting me know, so as of now there is no workaround to get GApps work with this branch after it has been installed?
Click to expand...
Click to collapse
Not that I know of. You either have to create space for G-Apps, or bundle G-Apps with the ROM.
spinxen said:
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
Click to expand...
Click to collapse
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
Would you mind to share your zip? Thanks!
spinxen said:
Would you mind to share your zip? Thanks!
Click to expand...
Click to collapse
https://opengapps.org/
anonym12 said:
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
Click to expand...
Click to collapse
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
This is somewhat above my level of knowledge, if you have a complete build zip with Gapps, do u mind sharing this with me?
How to install?
LioneageOS 17.1 for Poxel 3a: Notes from the front
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
Because of the issues, I have stuck with those versions that include GApps (invisiblek's simple LineageOS 17.1 works a treat, and is cloneable for those looking to build their own). Until beta 3 of Android 11 drops, I'm running this. Still no TWRP, or root, or anything else. Other than Pixel Launcher, I'm basically running stock Lineage.
Hi guys,
Just built my own image according to the 'easy' method (using docker). Took about 5 hours, and seemed to have gone well, almost no errors
I started out by flashing the Pixel 3a with the lastest Android 10 Factory Image from Google (QQ2A.200305.002, Mar 2020) to be sure it's as clean as possible. Booted into Android 10 once, enabled Developer Settings et cetera.
Then followed the 'Install' steps from https://github.com/SolidHal/Build-lineageos-sargo:
- boot into bootloader (fastboot mode)
- run 'fastboot flash boot boot.img'
- reboot into recovery -> Apply update -> Apply from ADB -> run 'adb sideload lineage-17.1-20200404-UNOFFICIAL-sargo.zip' (in my case)
When entering recovery mode I noticed an error at the botton of the screen: 'E:[libfs_mgr]Failed to mount /data: Invalid argument'. Despite that I could continue and sideload/install my self built lineageos zip, which finished without error (status 0). After installation the phone went back to into recovery mode (as described on the Github guide). Unfortunately, when I continued and picked 'Reboot System Now' I got thrown into the bootloader with enter reason: 'error boot prepare'. Every time the phone boots I see this error now.
Does anybody have a clue what I could be doing wrong? Any help is appreciated, thanks!
Edit: Okay, seems my problem is solved. When flashing the self-built boot.img, in my case I also had to specify which boot part to flash to: boot_a or boot_b. After having done that, booting now works.
Thanks SolidHal for providing your docker file and making it easy to built your own LineageOS 17.1 image!
Working and Running Smoothly
Thanks for posting this.
I was also able to build and install this successfully using the easy method. Yes, it takes a long time and requires an ample amount of memory and storage.
The battery life is excellent compared to the other roms/kernels I've tested so far. Started with a factory flash of Android 10.0.0 (QQ2A.200305.002, Mar 2020) (https://developers.google.com/android/ota). Then I followed the instructions here.
I also had the E:[libfs_mgr] error but it still installed correctly after the second try. Specifying boot_a or boot_b may have been what got this to work for me. Thanks to P1x3l3d.
Rooted by patching the boot image with Magisk (https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783).
P1x3l3d said:
Hi guys,
Just built my own image according to the 'easy' method (using docker). Took about 5 hours, and seemed to have gone well, almost no errors
I started out by flashing the Pixel 3a with the lastest Android 10 Factory Image from Google (QQ2A.200305.002, Mar 2020) to be sure it's as clean as possible. Booted into Android 10 once, enabled Developer Settings et cetera.
Then followed the 'Install' steps from https://github.com/SolidHal/Build-lineageos-sargo:
- boot into bootloader (fastboot mode)
- run 'fastboot flash boot boot.img'
- reboot into recovery -> Apply update -> Apply from ADB -> run 'adb sideload lineage-17.1-20200404-UNOFFICIAL-sargo.zip' (in my case)
When entering recovery mode I noticed an error at the botton of the screen: 'E:[libfs_mgr]Failed to mount /data: Invalid argument'. Despite that I could continue and sideload/install my self built lineageos zip, which finished without error (status 0). After installation the phone went back to into recovery mode (as described on the Github guide). Unfortunately, when I continued and picked 'Reboot System Now' I got thrown into the bootloader with enter reason: 'error boot prepare'. Every time the phone boots I see this error now.
Does anybody have a clue what I could be doing wrong? Any help is appreciated, thanks!
Edit: Okay, seems my problem is solved. When flashing the self-built boot.img, in my case I also had to specify which boot part to flash to: boot_a or boot_b. After having done that, booting now works.
Thanks SolidHal for providing your docker file and making it easy to built your own LineageOS 17.1 image!
Click to expand...
Click to collapse
Did you build in Linux? If so, which version? (I'm not used to building Docker - and especially in Linux - and I'd rather do it right; therefore WHICH version of Linux has everything to do it right is critical.)
PGHammer, I don't think it's going to matter too much what distro you use because you're going to have to install the latest platform-tools and install docker from a repo anyways. Just use something recent. Ubuntu comes to mind if you're not a huge GNU/Linux guy.
I built using Debian Stretch and had no issues other than my ram got all used up so I had to create more swap and add
vm.swappiness=60 to /etc/sysctl.conf
You need 100+GB HDD, 16GB+ RAM, and a fat swap space (I used a 20GB Swap file)
Also someone (anon12?) already posted a ~700MB zip of their build in this thread and I can confirm it works.
barqs_root said:
Also someone (anon12?) already posted a ~700MB zip of their build in this thread and I can confirm it works.
Click to expand...
Click to collapse
How did you you get this to install, I get signature verification failed, error:21. Then abd aborts the installation. I confirmed the integrity of the images with the provided checksum files. I even downgraded back to February's update because I was on Aprils update and thought that maybe that was the issues.
The steps I did are as follows:
Unlock bootloader
Enable debugging
Booting into the boot loader- run ./fastboot flash boot_a boot.img( ./ before is required due to being stuck on windows while I work from home.) Successfully installs to boot_a in 2.5sec.
Booting to recovery
Wipe/factory reset
Apply update from ADB- ./adb sideload lineage-17.1-20200222-UNOFFICIAL-sargo.zip
This is the following errors
E: failed to verify whole-file signature
Update package verification took 35.0 s (result 1).
E: Signature verification failed
E: error: 21
Install from ADB completed with status 2.
Installation aborted.