Related
Now Official CM14.1 is available for our beloved Google Nexus 7 2013 WiFi (flo). The nightlies and changelogs could be find here: https://www.cmxlog.com/14.1/flo/
I updated from CM13 (around Aug 29 nightly): dirty flash Nov 13 nightly + OpenGapps nano package (7.1) Nov 11 ver.
Everything is fine. Updating my apps now.
************************************
Please take note of the following:
1) TWRP recovery should be used to flash CM14.1 nightlies.
2) Recommended Gapps should be Open Gapps (arm, 7.1 pico). Otherwise you may encounter "insufficient space error" as reported. Mine is 32 GB. I installed nano package and I also have about 70 apps installed on my end.
3) The 2 lines of error mentioning "E:command log" (or something similar~), during flashing, is a common thing for Nougat based ROM
4)CM's gerrit: https://review.cyanogenmod.org/#/q/status:open
5)CM's github: https://github.com/CyanogenMod
Update: This a discussion thread and thus users can come together to discuss issues, provide solutions and assist other users that are using CM14.1 Nightlies. (Thanks @Bobbi lim for these suggestions!)
I recommend clean flash if you comes from CM13 or other custom ROMs, and please make nandroid backup using TWRP before installing this.
Please also be noted that I am just a "power user", not a Dev
************************************
I did dirty flash of 20161115 nightly over the initial 20161113 nightly as well. Dirty flash 20161117 nightly as well
************************************
Again I recommend clean flash if you comes from CM13 or other custom ROMs, and please make nandroid backup using TWRP before installing this.
************************************
************************************
Update (Nov 18, 2016) : Official Thread:
http://forum.xda-developers.com/nex...icial-cyanogenmod-14-1-nightlies-flo-t3502494
I'm first booting it right now, I try to installs gapps micro, but it says they were to big, so I had to install the Pico Version
Edit: Sound Recorder, Live Display and Mail is not working yet
---------- Post added at 01:49 AM ---------- Previous post was at 01:33 AM ----------
Also Touch force is not available yet
Anybody else experiencing a long boot screen. Seeing the cm robot logo and os never loads
Works great for me. Went from the unofficial to this and I can't really complain.
Source quality on twitch has issues but thats about it
does anyone have issues with the screen rotation? seems to be fixed at portrait no matter what settings.
^Rotation works fine for me on the first nightly.
Screen search isn't working for me. Some quick googling says it might just be an early 14.1 bug. Can someone confirm? Make sure it's on in the Now settings then longpress the home button, anything pop up?
Otherwise it's working quite well for the first nightly.
Edit: Screen Search has to be enabled in Settings > Buttons. Works now.
No problems so far, except for the odd random "CM bug report has stopped". Using TWRP 3.0.2.0, I wiped all 5 partitions before flashing, then all partitions except "System" after flashing (first boot might have taken a while).
I only flashed Delta Gapps (Base 7.1.1, Pixel Launcher, Search, TTS, and Connectivity Services). OK Google works, orientation works, Home button long-press Search Assistant works... I'm still not too familiar with Nougat, and wasn't aware of the settings to assign functions to the Home button (thank you for the info).
Bugged
when i try to flash it i get an error.
Error: unknown command[log].
dunno what to do, tried redownloading and stuff, gonna try the knew build today.
EstoyMejor said:
when i try to flash it i get an error.
Error: unknown command[log].
dunno what to do, tried redownloading and stuff, gonna try the knew build today.
Click to expand...
Click to collapse
I think all Nougat ROMs show that error twice during flashing, but it doesn't seem to cause any problems, CM still boots and works fine.
i flashed the CM 14.1 nightly on my N7 2013 today.
it works as far as i can see, but i cannot get the gapps to install.
i tried aroma, full, mini, micro, nano and pico. (Platform: ARM, Android 7.1)
they all give me the insufficient space error.
i tried to install from "sdcard"-memory and by sideload.
It is the 16 gb version of the tablet.
How do i get the gapps onto my tablet ?
it is practically useless without it.
SlurmMcKenzie said:
i flashed the CM 14.1 nightly on my N7 2013 today.
it works as far as i can see, but i cannot get the gapps to install.
i tried aroma, full, mini, micro, nano and pico. (Platform: ARM, Android 7.1)
they all give me the insufficient space error.
i tried to install from "sdcard"-memory and by sideload.
It is the 16 gb version of the tablet.
How do i get the gapps onto my tablet ?
it is practically useless without it.
Click to expand...
Click to collapse
WOW even Pico? I just clean flashed the latest build (but this time with Google Now Launcher). I have the 32GB model. I haven't used OpenGapps, I'm only using Delta Gapps, I choose only the apps I want to flash/replace, so I don't have redundant apps. So far no issues with the last 2 builds (still shows the 2 red errors during CM flashing, but that's not really a problem).
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Use Base Gapps 7.1.1 to get tha Play Store/Services only.
---------- Post added at 12:28 PM ---------- Previous post was at 12:07 PM ----------
If you have problems and need to go back to stock, you can get the factory images straight from Google:
ONLY FLASH THE LATEST IMAGE, DO NOT DOWNGRADE!
https://developers.google.com/android/images
"razor" for Nexus 7 [2013] (Wi-Fi)
Extract it and flash it with fastboot in bootloader mode (flash-all.bat).
Could not get it to work. Went back to stock for now.
SlurmMcKenzie said:
Could not get it to work. Went back to stock for now.
Click to expand...
Click to collapse
No clue, but there should be enough space for CM and Gapps. Were you using the latest TWRP 3.0.2-0? Did you wipe all partitions before flashing?
Gus Ghanem said:
No clue, but there should be enough space for CM and Gapps. Were you using the latest TWRP 3.0.2-0? Did you wipe all partitions before flashing?
Click to expand...
Click to collapse
i used the cyanogen recovery that they offer on the download page right next to the image i used.
i also wiped everything, multiple times.
maybe next time i will try the other recovery.
for now i prefer a working tablet. maybe i will also wait for the stable release before i try again.
Dirty flash Nov 15 nightly (using TWRP) and everything is still fine. Mine is 32 GB (mentioning this since some reported insufficient space error).
SlurmMcKenzie said:
i used the cyanogen recovery that they offer
Click to expand...
Click to collapse
I tried with the Cyanogenmod recovery+pico gapps, fails. Without gapps it flashes fine, but cyanogenmod doesn't boot. With TWRP+pico gapps everything works fine.
Installed cm-14.1-20161115-NIGHTLY-flo.zip and open_gapps-arm-7.1-nano-20161111.zip, everything works fine. Only problem, i had to trigger google backup transport from command line to get my wifi passwords back.
@MT2-User can you please edit your first post to actually assist users?
Please take note of the following:
1) Please mention that TWRP recovery should be used to flash CM14.1 nightlies
2) Recommended Gapps should be Open Gapps (arm, 7.1 pico)
3) The 2 lines of error mentioning "E:command log" (or something similar~) is a common thing for Nougat based ROM
4)CM's gerrit: https://review.cyanogenmod.org/#/q/status:open
5)CM's github: https://github.com/CyanogenMod
6) Change the title to a discussion thread and thus users can come together to discuss issues, provide solutions and assist other users that are using CM14.1 Nightlies.
Bobbi lim said:
@MT2-User can you please edit your first post to actually assist users?
Please take note of the following:
1) Please mention that TWRP recovery should be used to flash CM14.1 nightlies
2) Recommended Gapps should be Open Gapps (arm, 7.1 pico)
3) The 2 lines of error mentioning "E:command log" (or something similar~) is a common thing for Nougat based ROM
4)CM's gerrit: https://review.cyanogenmod.org/#/q/status:open
5)CM's github: https://github.com/CyanogenMod
6) Change the title to a discussion thread and thus users can come together to discuss issues, provide solutions and assist other users that are using CM14.1 Nightlies.
Click to expand...
Click to collapse
Thanks! Changes were made upon your request
Dirty flash 20161117.nightly.
Nexus 7 Flo 2013 Wi-Fi
I tried a guide from Windows & another from Ubuntu (rep to low to link.)
But former just shows dead android with exclamation in red triangle sign spewing out. The latter just sits with a Google loader until powered off. I really wanna install Lineage OS for timely security updates (& if successful will convert my Moto G4 Plus!) Not having much good fortune so far though....
EDIT;
TWRP is flashing successfully as long as I do not reboot, I take this is by design & not an error? However flashing Lineage fails ZIP verification, so I must download again maybe?
So now TWRP not flash Lineage OS Flo properly? (Nexus 7 2013 WiFi.)
ZIP signature verification failed apparently.
Now then... Are we sitting comfortably? Then I'll begin...
Flash TWRP then reboot like guide said would wipe tempoary TWRP Flash; Donna reboot but choose recovery with volume rocker, select with power button.
Flash latest Lineage for your specific device, Guide may link similar device.
Wipe everything except local storage before installing Lineage
Uncheck ZIP Verification
Download & flash PICO GApps if not enough room for main event
Watch out! Download may spit out random bin file & not ZIP (if so, rename.)
You have Lineage OS & can now bask in the much acclaimed glory of all history!!!
:good::silly::good:
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.
Let's get this out of the way. I don't have much experience flashing ROMs. I've done it on a few phones, but I can't say I really understood what I was doing. I'm just good at following directions. So, I know about enough to get into trouble.
And ...I've gotten into trouble. My goal is to install LineageOS on my brother's Essential Phone. Based on directions I found here, I determined the active slot was b, so I installed TWRP on slot a. TWRP worked in recovery, but without touch. I then flashed twrp-3.2.3-0-mata.img to the non-active slot. Lastly, I sideloaded twrp-installer-mata-3.2.3-0.zip. I then changed the active slot back to b and rebooted. It now boots only to the bootloader and not to the OS. No matter what option I select--Start, Bootloader, Recovery--it reboots to the bootloader.
Any help to get out of this would be greatly appreciated.
Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps
MuddyDog said:
Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps
Click to expand...
Click to collapse
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.
mcmc08 said:
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.
Click to expand...
Click to collapse
Try:
Fastboot flash:raw boot_slot recovery.img
So, I found a solution. In order to overcome the errors I was getting, I had to use the raw command. So it was fastboot flash:raw boot [image file]. Once Lineage recovery was installed, I could boot to recovery and sideload Lineage.
MuddyDog said:
Try:
Fastboot flash:raw boot_slot recovery.img
Click to expand...
Click to collapse
I guess our replies crossed. At any rate, the raw command did the trick. Thanks for your help.
I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)
Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.
rocketrazr1999 said:
Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.
Click to expand...
Click to collapse
I installed Lineageos directly on the february android stock version. (which is the last one from Essential)
Simply by following the tutorial on the LineageOS website.
Everything worked the first time.
So there is no need to switch back to the January android stock version. The image recovery provided by Lineage works very well.
And for your information LineageOS is updated almost every Monday.
Moreover the developers of the TWRP are not the developers of Essential. Company which closed at the end of February.
---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------
KJannot said:
I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)
Click to expand...
Click to collapse
Which Rom would you like to install instead of Lineage?
groovebox said:
Which Rom would you like to install instead of Lineage?
Click to expand...
Click to collapse
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?
KJannot said:
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?
Click to expand...
Click to collapse
Paranoid Android: What I heard is VoLTE broken, if you enable it, SMS/MMS might not work properly.
Evolution: No update in Android 10 since August, not sure they contine to support Essential phone for Android 11
Pixel Experience: I don't think they Anroid 10 for Essential phone, only official Anroid 9 which is too old
TWRP issue: You need to go back to Jan stock rom before going to any rom if you just flashed LOS
What current stable rom with Nov security update: I'm using crDroid 6.12 (unofficial release but from XDA reliable source)
https://forum.xda-developers.com/essential-phone/development/rom-crdroid-v6-7-t4129739
Hi, I'm a long-time lurker on these forums but recently had some success flashing a GSI and rooting the Lenovo Tab M10 Plus (FHD) (X606F) with TWRP, and wanted to share my exact steps here. This device is awesome for the price point but unfortunately not popular enough to have many guides available. The tablet is Project Treble compatible and uses A/B roms (although it is not an A/B device in terms of OTA updates). You can use the Treble Info app to confirm that the devices uses an ARM64 A/B operating system. This was tested with the CAOS 11 GSI based on Android 11; it may work on other GSIs and other Android versions but I have not tested those (NOTE: user below confirms working on Android 12). I've written this guide at a bird's-eye-view meant for users familiar with flashing.
A couple useful notes before we begin:
- Hardware force off: hold down both volume buttons + power button
- Hardware boot into bootloader: while powered off, hold volume down + power button
- Hardware boot into recovery: hold down both volume buttons + power button
- While in fastboot mode, the command `fastboot reboot recovery` does not work for me on this device. You may have to hardware boot into recovery using the hardware steps above (power off completely then hardware boot). [This command may work for some people. It does not work for my device.]
Obviously, make sure your bootloader is unlocked before starting.
1. I used Ubuntu since Windows was having trouble recognizing the device in fastboot mode; linux drivers seem to be better developed for this particular device. I used `sudo apt install android-sdk` to get the drivers. Much easier than the nonsense that you have to do on Windows to get this device to work. Unfortunately, the Lenovo rescue app is available only for Windows, so you'll need access to Windows to gain access to vbmeta.img for installing TWRP (below).
2. Install TWRP following this guide: https://forum.xda-developers.com/t/...rp-3-5-x-for-lenovo-tab-m10-fhd-plus.4222887/. It is important that you follow all these steps. After flashing the recovery, you must reboot into recovery to ensure that TWRP permanently installs. If the `fastboot reboot recovery` command does not work for you, hold down the power button to power off the device, then hardware boot into TWRP by holding down both volume buttons + power button to boot into TWRP. If you do not perform this step, the device will boot normally and TWRP will be erased. After booting into TWRP, wipe -> format data.
3. In TWRP, flash CAOS 11 GSI: https://forum.xda-developers.com/t/official-aosp-r-mod-caos11.4265059/. You can try with other GSIs - it will probably work - but I've only tested this particular one, and can attest for the stability of CAOS 11 on this device. The image you'll want is named with -arm64-bgZ. If you use another GSI, make sure to use the A/B arm64 image. CAOS 11 has gapps included, so no need to flash here; if you use another GSI that does not have, you'll need to flash the appropriate gapps yourself. You can also opt for the non-gapps download if you don't want Google spying on you.
4. (Optional/No longer necessary) In TWRP, flash to disable dm-versity: https://zackptg5.com/android.php#disverfe.
5. (Optional - many GSIs come with root) In TWRP, flash standard Magisk.zip: https://github.com/topjohnwu/Magisk. I didn't need to use Magisk-Phh.
6. Reboot system.
7. You may or may not get errors from Google Play saying that the device is not certified. Follow these steps:
- Sign into Google account on device via settings
- Download and install the Get ID app: https://f-droid.org/en/packages/makeinfo.com.getid/
- Open the app and Copy Google Service Framework Key
- Go to https://www.google.com/android/uncertified/
- Sign in and paste the copied value to it, register
- Reboot (this actually took me a few tries to get working, I believe the key is to make sure you're signed into your Google account)
- Google Play should be working
Feel free to ask any questions here.
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
dpn982 said:
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
Click to expand...
Click to collapse
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
shnioob said:
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
Click to expand...
Click to collapse
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
dpn982 said:
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
Click to expand...
Click to collapse
I think this tablet has always had an issue with Netflix due to lack of DRM or something of that nature - I wasn't able to get Netflix on the stock version. Disney+ is probably the same issue.
If you have some free time, it would be great if you can outline your steps for getting safetynet to pass. I haven't bothered with it.
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
emilio666 said:
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
Click to expand...
Click to collapse
NEVERMIND, it got solved by just waiting a couple of hours after using the Google website: https://www.google.com/android/uncertified/
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks for the clarifying info, updated the OP a bit. And thanks for providing us with a TWRP to make this possible. Otherwise this awesome tablet would be stuck on Android 10 forever.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Happy to help, glad it worked for you. I tried installing some other GSIs with and without flashing Magisk - LineageOS 12 boots but is very buggy, after reboot I was unable to get past the lockscreen. PixelExperience 11 and 12 cause a bootloop. If anyone has had success with PixelExperience I would love to get your input.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
jebise101 said:
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
Click to expand...
Click to collapse
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
shnioob said:
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
Click to expand...
Click to collapse
How do you go back to stock in case this does not work?
Is there a factory image?
jebise101 said:
How do you go back to stock in case this does not work?
Is there a factory image?
Click to expand...
Click to collapse
you can download the stock ROM from LMSA
I also have Lenovo tab m10 fhd plus but it is tb-x606v. Can I flash x606f rom on this device and flash twrp after.i don't want my device to be bricked.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Hi, I'm trying to follow what you did, but I'm having issues with the Gapps, do you have some pointers to solve it? Thank you in advance
Hello everybody!
I finally installed CAOS 11 and it's working like a charm. Gapps are definitely working as excpected and system seems to be stable as possible.
I have two question to those that installed it to :
Is anyone kow why some widgets on X606F are not clickable, an do not actualize till reboot?
Am I the only one that lost double tap to wake on CAOS?
Thank you all
I tried AOSP V412 12L too, we lost fingerprint sensor and face unlock, widevine DRM. There is some troubles on wifi, beside of this it is pleasant. Of course this not as smooth as android 10. I do not recommend it for daily basis.
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
garconblair said:
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
Click to expand...
Click to collapse
Thanks for the feedback. What about Widevine L1 and SafetyNet test with CAOS11? Are you able to play content at 1080p resolution with the Netflix App?