Related
Hello everyone. So I'm brand new to not only xda but rooting and the likes all together. Yesterday I rooted my nexus 6p without issue and I will now list what I used. Twrp 3.0.0 -1-angler, BETA-SuperSU-v2.67-20160121175247. My phone build was MMB29P. then I flashed on pure_nexus_angler-6.0.1-20160315-CMTE and PureNexus_Dynamic_GApps_6.x.x_3-15-16.zip. Now my phone is saying its build MHC19J. I don't know if that is normal, but now I'm confused. When I boot up I get an Android System message saying " It appears your vendor image may be out of date. Please flash the latest vendor image for your device. " So followed the link to the vendor images and I see the list of vendor images however I don't see my build MHC19J.. or am I to get MMB29P? also once I do get it downloaded and load up twrp I see the option to click image and there's several boxes there to check/uncheck.. Do i just check vendor? So put as short as possible I need to know which vendor image i should get and how to flash it from twrp. Thanks for reading and your help will be greatly appreciated.
Also I almost forgot.. Will i need to flash a raido file or anything like that??
Read this first: http://forum.xda-developers.com/showpost.php?p=64399854
Then read this: http://forum.xda-developers.com/showpost.php?p=65102741&postcount=7741
The answers to your question are both in those links, which you should ALWAYS read. You'll thank me later for making you read those.
Danzilla79 said:
Hello everyone. So I'm brand new to not only xda but rooting and the likes all together. Yesterday I rooted my nexus 6p without issue and I will now list what I used. Twrp 3.0.0 -1-angler, BETA-SuperSU-v2.67-20160121175247. My phone build was MMB29P. then I flashed on pure_nexus_angler-6.0.1-20160315-CMTE and PureNexus_Dynamic_GApps_6.x.x_3-15-16.zip. Now my phone is saying its build MHC19J. I don't know if that is normal, but now I'm confused. When I boot up I get an Android System message saying " It appears your vendor image may be out of date. Please flash the latest vendor image for your device. " So followed the link to the vendor images and I see the list of vendor images however I don't see my build MHC19J.. or am I to get MMB29P? also once I do get it downloaded and load up twrp I see the option to click image and there's several boxes there to check/uncheck.. Do i just check vendor? So put as short as possible I need to know which vendor image i should get and how to flash it from twrp. Thanks for reading and your help will be greatly appreciated.
Also I almost forgot.. Will i need to flash a raido file or anything like that??
Click to expand...
Click to collapse
The vendor version you need is MHC19I which you can download following the link on the first post on the pure nexus ROM. Flash it via TWRP by hitting the flash img button and then selecting the vendor partition (duh). It's also good to make sure you are running the latest bootloader and radio (the bootloader should be on version 3.51 and the radio on 3.61).
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.
TL;DR - Apparently Google did something in their most recent updates that ignored all modifications made to /vendor...
So recently Google gave us the 7.1.2 and February patch updates. They decided not to mention much on behalf of the 7.1.2 and let us figure it all out. "Yay", they've given us fingerprint perfect - or is it. Seems they decided to do something quite sneaky. They've made sure /vendor cannot be edited or modified, but it's used by many mods and even Substratum Legacy.
HERE Per Lykce noticed this with and gave a fix with the February patches.
Let's get this fixed up cleanly!
Per Lycke said:
The common fix is to re-flash the vendor partition in fastboot. Don't forget to pick a slot for the partition if you're using the Pixel.
Click to expand...
Click to collapse
In other words:
Enter fastboot mode (with OEM Unlocked, obviously).
Download and extract one of the device images below (relevant to your version).
Copy the vendor.img file to the folder containing fastboot.exe and it's necessities.
Open command prompt (or your OS's terminal application) in the folder with the vendor.img and fastboot (previously platform-tools) files.
Type
Code:
fastboot.exe flash vendor vendor.img
Go to TWRP and reflash all your mods that use the /vendor partition and or retheme your device using Substratum.
Reboot and done, your mods have finally applied !
EDIT: Apparently, the 7.1.2 allows /vendor modification from within the ROM but not TWRP, I'm not sure whether you can flash mods in TWRP on a February patch but you can't modify from within the ROM!
7.1.1 (N4F26O, Feb 2017)
7.1.2 PixelROM (NPG05D, Jan 2017)
This goes beyond the 5X; my Nexus 6P fails to apply overlays on the Feb. 2017 patch. I can only assume anyone who has the patch or 7.1.2 won't be getting Substratum up and running that easily.
Xenotrumpet said:
This goes beyond the 5X; my Nexus 6P fails to apply overlays on the Feb. 2017 patch. I can only assume anyone who has the patch or 7.1.2 won't be getting Substratum up and running that easily.
Click to expand...
Click to collapse
I've explained how to fix it. Just "CLICK TO SHOW CONTENT" !
Xenotrumpet said:
This goes beyond the 5X; my Nexus 6P fails to apply overlays on the Feb. 2017 patch. I can only assume anyone who has the patch or 7.1.2 won't be getting Substratum up and running that easily.
Click to expand...
Click to collapse
Well anyone who is using Substratum is already going to be rooted and thus have an unlocked bootloader, so they will easily be able to follow the instructions given for the fix.
It doesn't work.
78jimm said:
It doesn't work.
Click to expand...
Click to collapse
Try following the instructions after a dirty ROM flash. Also, try booting up your device a few times before actually flashing the vendor image. This allows the system to "set-up" the vendor mounts and everything, and flashing after that won't be affected. Sometimes it just doesn't work, so just keep trying it and it should eventually :good:.
Also, it would be great if you could tell me what you are trying to do. Substratum Legacy? Newer security updaters prevent many previous mods from working (eg. PIE-only) and that may be your case instead.
I must be missing something here. If the problem is that the vendor partition can't be modified anymore, why does downgrading to a previous version of substratum magically fix it? For the record, reflashing the vendor image did nothing for me either.
Does anybody else has this bug with WiFi Settings on 7.1.2 ?
When you try to enter in to the WiFi Settings (the gear icon) the Settings crash! "Settings has stopped"
Haik0 said:
Does anybody else has this bug with WiFi Settings on 7.1.2 ?
When you try to enter in to the WiFi Settings (the gear icon) the Settings crash! "Settings has stopped"
Click to expand...
Click to collapse
That's not relevant to this thread. However, yes that is a bug in 7.1.2 developer preview 1.
matslarson said:
I must be missing something here. If the problem is that the vendor partition can't be modified anymore, why does downgrading to a previous version of substratum magically fix it? For the record, reflashing the vendor image did nothing for me either.
Click to expand...
Click to collapse
Like I said. Some people have it, some don't. Substratum had it's own previous issue too, but that's what you experienced.
Up till what ik, This issue occurs in custom ROMs with the stock vendor partition (AKA PixelROM).
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.
I have Moto G7 (River, XT1962-4) with the bootloader unlocked by fastboot ("fastboot oem unlock <unlock code>"). I am ready to install LineageOS, and I haven't yet installed a recovery package.
However, it appears that the A/B slots (partitions?) are still causing a lot of ROM install difficulty. especially with the moto g7. So, it's a bit concerning.
The problem seems to stem from the fact that, when slot A is active and one flash esLineage OS using TWRP (or Lineage recovery), the image is written to slot B and and the phone switches to booting from slot B. Then, rebooting fails because there is no bootloader in slot B. Is my understanding correct?
It seems that most favor TWRP over the LineageOS recovery package. So, I would like to install TWRP.
The LineageOS instructions for temporarily booting and installing TWRP differ from the install instructions given on the TWRP Moto G7 page.
The Lineage page directs the user to employ fast boot ("fastboot flash boot <twrp_filename>.img") with "a boot__a" or "boot__b" flag, to install TWRP to the desired slot. Unfortunately, these instructions don't tell how/where to use that flag in the fastboot command syntax.
On the other hand, the TWRP page instructs users to install TWRP via their installer. That TWRP installer puts TWRP in both the A and B slots.
It seems that the TWRP procedure is more foolproof, but does that method bork the later steps given in the LineageOS instructions?
The next step is given in the "Pre-install instructions" on the LineageOS page. It says to sideload the copy-partitions.zip package with TWRP booted (and already installed).
The copy-partitions.zip package copies slot A to slot B (or vice versa), so that it exists in whichever slot the phone chooses. This process is explained in the LineageOS install page for the Moto G7. This process seems easy, but, again, will it be borked by the previous TWRP installer that addressed both slots?
The rest of the procedure seems fairly straightforward, but will my phone be rooted automatically? If not, how does one root the phone (what app/package should I use)?
Also, in most ROM install tutorials on the Interwebs, there usually comes a point in which certain things are "wiped," such as "Dalvic/ART cache," "cache" and "data." I see that there is a "Wipe" step and a "Format" step in the "Installing LineageOS from recovery" section of the Lineage instructions, but neither step specifies "Dalvic/ART cache," "cache" nor "data." Are those the things that are being wiped?
Thanks very much!
go on telegram and get instructions there as XDA is outdated
HueyT said:
go on telegram and get instructions there as XDA is outdated
Click to expand...
Click to collapse
Thank you for the reply!
I am not familiar with Telegram. Does one have to give their phone number and other sensitive information to sign up there?
What do you mean by "XDA is outdated?" I see lots of recent posts on this forum, with one or two that specifically pertain to the problems regarding attempting a LineageOS install on a Moto G7.
Hopefully, somebody here has experience dealing with A/B partitions and can give me a quick answer as to whether or not using the TWRP installer will bork things, when I later try to copy the bootloader to the inactive slot by sideloading "copy-partition.zip."
Thanks!
tuppb said:
Thank you for the reply!
I am not familiar with Telegram. Does one have to give their phone number and other sensitive information to sign up there?
What do you mean by "XDA is outdated?" I see lots of recent posts on this forum, with one or two that specifically pertain to the problems regarding attempting a LineageOS install on a Moto G7.
Hopefully, somebody here has experience dealing with A/B partitions and can give me a quick answer as to whether or not using the TWRP installer will bork things, when I later try to copy the bootloader to the inactive slot by sideloading "copy-partition.zip."
Thanks!
Click to expand...
Click to collapse
Installation instructions on LOS page are not good. If you go to the AEX rom here on XDA, those instructions are better. The thing is XDA is not really used by the devs too much. Its better to go to the telegram group. The only info telegram uses is your phone number to sync up.
http://t.me/motog7river
Also, telegram group has many more roms, and if you have problems its much easier to get help there.
JAS_21 said:
Installation instructions on LOS page are not good. If you go to the AEX rom here on XDA, those instructions are better. The thing is XDA is not really used by the devs too much. Its better to go to the telegram group. The only info telegram uses is your phone number to sync up.
Also, telegram group has many more roms, and if you have problems its much easier to get help there.
Click to expand...
Click to collapse
Thank you!
I searched for a specific AEX (aosp extended) rom section on this forum, and I couldn't find one. I did find a few threads regarding releases, but no official install instructions. Couldn't find anything on the AEX site, too. Do you have a link to those instructions?
I am unable to get on Telegram -- can't give out my phone number and online SMS sites seem to be useless.
It's a shame that folks don't use open forums such as this one.
Thanks!
UPDATE: I am happy to report that _Clon_'s guide to installing Lineage 17.1 worked on my Moto G7!
If you get an error message when using fastboot to set the active slot to "_a" in step 1.4, move on, because setting the active slot to "_a" can wait until step 1.6 whne it is set with TWRP.
By the way, when I ran the "fastboot getvar all" (in step 1.3), it showed that my current slot was "_b" and that slot "_a" was not bootable. Slot "_a" became bootable when I ran the TWRP installer (in step 4.1). My LineageOS 17.1 install runs from slot "_a".
In addition, it seems that Lineage Recovery has some advantages over TWRP. I have seen posts in other forums suggesting that LOS OTA updates will install Lineage Recovery over the installed TWRP (which is what I want).
Thanks, _Clon_!