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.
I was about to give up and go back to stock but lo and behold I got ahold of a link to a really nice GSI for our Honor 7x devices, and any other device with the Hi6250 chipset. It has worked flawlessly on my BND-L24 and doesn't give me weird uncertified device and internal storage errors like the treble GSI found in the treble ROM forums.
Download link (2nd time just in case) - https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-dotos-8-1-huawei-hi6250-t3793970
Open GApps (I use Pico) - https://opengapps.org
Treble GSIs (Why not) - https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Latest Magisk (Beta for fixed bugs and whatnot) - https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Installation instructions -
crayonicle said:
I assume you have this TWRP installed, if not, install it: TWRP
Alright, let's install.
1. Boot into TWRP
2. Go to wipe - advanced wipe
3. Wipe all but SD card
3. Then go back to wipe.
4. There is an option next to advanced wipe, forgot what it was. (I think it was "Format Data")
5. Tap that option and type "yes"
6. Reboot back into TWRP
7. Flash the ROM and flash Open GApps right after flashing the ROM (I used Pico Open GApps)
8. Do a factory reset, wipe Cache, Dalvik / ART cache, and Data in advanced wipe just to be sure.
9. Reboot
Click to expand...
Click to collapse
EDIT: I'm no longer on this ROM so if there are bugs and you want me to reproduce them, I can not help you. Sorry, I need a more stable ROM for our Honor 7x's than this one. Thanks for understanding.
It's not the best idea to wipe with TWRP. It's better to do it with stock recovery or manually with fastboot.
Hi !
Does it work on BND-L21C432 ? What are the steps to install the rom ? Does it have to be EMUI 8.0 ?
Thank you for your work on this rom!
flashing this i hope the battery sot is good
Thanks for pointing this Rom out crayonicle, just flashed it and it's freaking great!!
jmoss1972 said:
Thanks for pointing this Rom out crayonicle, just flashed it and it's freaking great!!
Click to expand...
Click to collapse
Well until i flashed magisk and now all i get after flashing the rom is stock recovery
imHadees said:
It's not the best idea to wipe with TWRP. It's better to do it with stock recovery or manually with fastboot.
Click to expand...
Click to collapse
Yeah, you're right, I could end up messing up partitions and whatnot...
But I'm known for being careless ¯\_(ツ)_/¯
DaRkLinK_35 said:
Hi !
Does it work on BND-L21C432 ? What are the steps to install the rom ? Does it have to be EMUI 8.0 ?
Thank you for your work on this rom!
Click to expand...
Click to collapse
Yes, this ROM will run on your device!
Well, I didn't make this ROM at all, I'm just here to share it...
I already showed you the steps, read the original post!
You must be on EMUI 8 or you will brick your device!
jmoss1972 said:
Well until i flashed magisk and now all i get after flashing the rom is stock recovery
Click to expand...
Click to collapse
Did you flash the latest Magisk Beta?
Usually that is the one that works, or you can find a treble-compatible version of Magisk to flash.
crayonicle said:
Did you flash the latest Magisk Beta?
Usually that is the one that works, or you can find a treble-compatible version of Magisk to flash.
Click to expand...
Click to collapse
Yes I flashed the 16.4, not sure what happened. I can get into twrp, tried wiping and flashing the DotOs image again but all it does is boot into Huawei recovery. When I get home I will try downloading the stock firmware from the MT website and if I can get it to boot up Ill try flashing DotOs again.
jmoss1972 said:
Yes I flashed the 16.4, not sure what happened. I can get into twrp, tried wiping and flashing the DotOs image again but all it does is boot into Huawei recovery. When I get home I will try downloading the stock firmware from the MT website and if I can get it to boot up Ill try flashing DotOs again.
Click to expand...
Click to collapse
Hmmmm... I flashed Magisk fine here...
Hope you get it working again :good:
crayonicle said:
Hmmmm... I flashed Magisk fine here...
Hope you get it working again :good:
Click to expand...
Click to collapse
How's it compared to lineage 15.1? How's battery life? Post few screenshots and check whether substratum works or not? TIA
Tried flashing gapps linked and get an error about gapps isnt compatible. Tried flashing 8.0, 8.1 and 7.1.2 gapps and none work.
Hell yeah got the phone operational again, time to get back to flashing.
Username.php said:
How's it compared to lineage 15.1? How's battery life? Post few screenshots and check whether substratum works or not? TIA
Click to expand...
Click to collapse
More features than Lineage and the SOT seems to be higher
Substratum only works with Magisk or other root installed
Screenshots: Google Drive link
tlxxxsracer said:
Tried flashing gapps linked and get an error about gapps isnt compatible. Tried flashing 8.0, 8.1 and 7.1.2 gapps and none work.
Click to expand...
Click to collapse
Most likely there is something wrong with what you're using to flash the GApps, like the SD card, USB OTG, etc. Try switching it out.
But before doing all that, first flash the ROM, and then reboot again into TWRP and try flashing it if that makes a difference. Make sure you're flashing the ROM like the original post says.
crayonicle said:
Most likely there is something wrong with what you're using to flash the GApps, like the SD card, USB OTG, etc. Try switching it out.
But before doing all that, first flash the ROM, and then reboot again into TWRP and try flashing it if that makes a difference. Make sure you're flashing the ROM like the original post says.
Click to expand...
Click to collapse
Trust me, I am. ROM boots up fine though.
crayonicle said:
Hmmmm... I flashed Magisk fine here...
Hope you get it working again :good:
Click to expand...
Click to collapse
It was there all along, I'm a moron. It was in the settings menu.
crayonicle said:
I was about to give up and go back to stock but lo and behold I got ahold of a link to a really nice GSI for our Honor 7x devices, and any other device with the Hi6250 chipset. It has worked flawlessly on my BND-L24 and doesn't bootloop like the treble GSI found in the treble ROM forums.
Download link (2nd time just in case) - https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-dotos-8-1-huawei-hi6250-t3793970
Open GApps (I use Pico) - https://opengapps.org
Treble GSIs (Why not) - https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Latest Magisk (Beta for fixed bugs and whatnot) - https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Installation instructions -
Click to expand...
Click to collapse
That's great! Definitely giving this one a try
I recommend it, working great for me as well.
Is it just me or does the inbuilt UI tweaker not work? I can change the accents but not the settings and quicksettings background
** Post updated on 01/10/19 to include AOSiP GSI **
After trying out a lot of Android 10 GSIs, I have managed to get Lineage OS 17 and AOSiP GSI builds by Erfan to run on Mi Max 3. Thanks to the Dev erfanoabdi and his team who have worked on these.
On Mi Max 3 they are very smooth when they are working. However, certain apps can trigger freezing episodes or forced reboots. AOSiP seems smoother and more stable for now. Both are almost stock with no customization. Over all they are still buggy, just usable, and not reliable.
I am not a developer! Try at your own risk!!
** PLEASE NOTE: You would need to be on one of the AOSP- or LOS-based custom Pie Roms with firmware version 9.9.3 (as base) before flashing this rom. Havoc and AEX have been confirmed to work**
Here are the steps
What you would need:
1. GSI Android 10 Rom:
a. Lineage 17 GSI by Erfan: lineage-17.0-Aonly-10-20190909-ErfanGSI.img.7z
b. AOSiP
2. Permissiver_v4.zip
3. FixZygote_v2.zip
4.open_gapps-arm64-10.0-nano-20190920-UNOFFICIAL.zip
5. Magisk 19.4
6. Any file extractor app. I used ZArchiver from Play store.
Installation Steps.:
1. Extract system image from Android 10 GSI zipped file using app of your choice (ZArchiver in my case)
2. Boot into your recovery (I used Nijel's TWRP 3.2.3-3 and 3.2.3-4)
3. Back up your current ROM
4. Wipe data, system, art/davlik and cache
5. Tap install. Then tap ''Image''. Then select the (extracted) Lineage-17 system image, then tap System. Swipe to install.
6. Install Permissiver_v4 zip file.
7. Install FixZygote_V2 zip file
8. Install Magisk 19.4 zip file.
9. Boot into system. Tap ''OK'' on the screen pop up.
10. Reboot into TWRP.
11. Install OpenGaps.
13. Reboot system and set up your phone.
14. Reboot phone and start using.
What works
1. Mobile data, Wifi and bluetooth
2. Phone calls and messaging including dual sim
3. Playstore
4. Rooting with Magisk
5. Finger print reader
6. Gestures are amazing. Dark mode great!
Bugs
1. Stock camera and torch light do not work.
2. Slider does not control brightness
3. Chrome browser freezes. . Firefox and Via browser running smoothly.
4. Camera and video apps force-close or cause random reboots
Where are the links to the packages and why you install two different gapps (Bitgapps&Opengapps)???
L_e_x_t_e_r said:
Where are the links to the packages and why you install two different gapps (Bitgapps&Opengapps)???
Click to expand...
Click to collapse
There are no links to the packages as I wasn't certain of the XDA rules on links to other websites. Just google them and they are easy to find.
I tried just open gapps or just BitGaps and didn't work. Flashing BitGaps first appeared to point the Open Gapps to the right partition, and that worked.
Thanks for posting but very confusing without links. I know what mean about the rules but you can link the page for the GSI not the download etc
shingers5 said:
Thanks for posting but very confusing without links. I know what mean about the rules but you can link the page for the GSI not the download etc
Click to expand...
Click to collapse
I understand.
Thanks to the Nesh Patel at Tweakguy for the links.
My thanks to the devs who have worked on these.
Here are the links:
For Lineage GSI: https://github.com/resk84/releases/...ineage-17.0-Aonly-10-20190909-ErfanGSI.img.7z
For permissive: https://androidfilehost.com/?fid=600693192411788649
For bitzygote:
https://androidfilehost.com/?fid=1395089523397961748
Permissive link not working
shingers5 said:
Permissive link not working
Click to expand...
Click to collapse
Missed one digit at the end.
Permissiver link:
https://androidfilehost.com/?fid=6006931924117886495
This won't boot on global mix max 3 boot loop with both Nigel mod and orangefox recoveries. No work for global 4gb 64gb ROM model
shingers5 said:
This won't boot on global mix max 3 boot loop with both Nigel mod and orangefox recoveries. No work for global 4gb 64gb ROM model
Click to expand...
Click to collapse
I was on the latest Havoc Rom for Mi Max 3. Also my hardware is 6GB 128GB.
I tried a lot of the Android 10 GSIs and this was the only one that booted. The sequence has to be exactly same as in my post to boot.
Also, I don't know if it may have to do with your vendor. I didn't wipe and then flash the device-specific vendor firmware as suggested in some GSI how-to's.
So you were on an android pie ROM and flashed android 10 over it without wipe? I was on miui 11 before flash on global device
shingers5 said:
So you were on an android pie ROM and flashed android 10 over it without wipe? I was on miui 11 before flash on global device
Click to expand...
Click to collapse
Yes Havoc Pie Rom. I wiped davlik/art, system, data and cache only. Then proceeded exactly as outlined in my post. I have just flashed the LOS 17 again with my steps and it boots.
stonesolouk said:
Yes Havoc Pie Rom. I wiped davlik/art, system, data and cache only. Then proceeded exactly as outlined in my post. I have just flashed the LOS 17 again with my steps and it boots.
Click to expand...
Click to collapse
first attempt
i had derpfest AOSIP so i flashed LOS 17 over that with no wipe then the permissive and fix zip and it booted with errors. gestures for home works but edges dont. also kept fail on system etc
2nd attempt
flashed derpfest AOSIP then reboot
back to recovery then wipe as you did flash LOS17 then permissive and fix zips then reboot. boots up but same as before home gesture works and dark mode etc but edges don't. the bitgapps dont flash and open gapps nano causes bootloop on its own
3rd attempt gonna try with firmware 9.9.3 and flash without wipe vendor like the old days to see what happens
Got it good as I can for now
Flashed and booted AEX 6.7
Back to recovery and wiped as you say and not vendor
Flashed LOS 17 image then permissive and fix zips and magisk
Reboot
Didn't need flash 2 gapps just open gapps nano and reboot
Seems good apart from obvious
Brightness doesn't work
Camera
Battery drain very high
shingers5 said:
Got it good as I can for now
Flashed and booted AEX 6.7
Back to recovery and wiped as you say and not vendor
Flashed LOS 17 image then permissive and fix zips and magisk
Reboot
Didn't need flash 2 gapps just open gapps nano and reboot
Seems good apart from obvious
Brightness doesn't work
Camera
Battery drain very high
Click to expand...
Click to collapse
That's great. It settles down after a few more boots. I will update my post with your findings.
Brightness and all edge gestures work for me though.
stonesolouk said:
That's great. It settles down after a few more boots. I will update my post with your findings.
Brightness and all edge gestures work for me though.
OK cool. Hopefully someone can get it working fully or at least stable enough for daily use
Click to expand...
Click to collapse
And what about the AOSIP-Aonly-10-20190924-ErfanGSI.7z? Do I flatten the Lineage-17.0-Aonly-10-20190909-ErfanGSI.img or do I have to decide between one of them?
Does not herfor from the instructions
rudiratlos57 said:
And what about the AOSIP-Aonly-10-20190924-ErfanGSI.7z? Do I flatten the Lineage-17.0-Aonly-10-20190909-ErfanGSI.img or do I have to decide between one of them?
Does not herfor from the instructions
Click to expand...
Click to collapse
Yes it is one or the other.
You could try each one separately, then decide the one you prefer. AOSiP seems more fluid and stable.
Thank you for your prompt reply
What's the report on AOSIP as I haven't tried it yet. Wish someone would take the gsi and get it stable
shingers5 said:
What's the report on AOSIP as I haven't tried it yet. Wish someone would take the gsi and get it stable
Click to expand...
Click to collapse
It is smoother and more stable compared to LOS 17 but brightness slider and camera still don't work.
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?
Nokia x6 ta-1099 CN.
This week any and all versions of LineageOS (official 17-19, incl. microG versions) started to bootloop instantly after the flashing. I.e the rom installs fine, recovery menu works, but when the lineageOS logo comes up, it only lasts for abt. 1 seconds before auto-rebooting the phone.
I used to be able to install and run LineageOS in the past no problem using LineageOS official method (adb sideload) as well as TWRP "wipe->flash" method. Also, non-lineageOS roms work fine (HavocOS, PixelPlusUI, ArrowOS, AOSP).
Any reason why it suddenly bootloops? Is there any rookie mistake I'm making here?
are you doing a Clean Wipe before install?
clean wipe - wipe all partitions excluding vendor.
ai.Sanaul said:
are you doing a Clean Wipe before install?
clean wipe - wipe all partitions excluding vendor.
Click to expand...
Click to collapse
Yes, though I was wiping everything including the vendor.
Totesnochill said:
Yes, though I was wiping everything including the vendor.
Click to expand...
Click to collapse
maybe your phone is not compatible with the version, please check...
Edit: and yes this rom is not compatible with your phone. check some unofficial builds for your phone of Linage OS.
ai.Sanaul said:
maybe your phone is not compatible with the version, please check...
Edit: and yes this rom is not compatible with your phone. check some unofficial builds for your phone of Linage OS.
Click to expand...
Click to collapse
LineageOS for MicroG is officially compatible though, and I clearly remember installing an unofficial build in the past
Totesnochill said:
LineageOS for MicroG is officially compatible though, and I clearly remember installing an unofficial build in the past
Click to expand...
Click to collapse
Linage Os is officially not available for Nokia X6 ta-1099, i checked on offficial site...
Totesnochill said:
Nokia x6 ta-1099 CN.
This week any and all versions of LineageOS (official 17-19, incl. microG versions) started to bootloop instantly after the flashing. I.e the rom installs fine, recovery menu works, but when the lineageOS logo comes up, it only lasts for abt. 1 seconds before auto-rebooting the phone.
I used to be able to install and run LineageOS in the past no problem using LineageOS official method (adb sideload) as well as TWRP "wipe->flash" method. Also, non-lineageOS roms work fine (HavocOS, PixelPlusUI, ArrowOS, AOSP).
Any reason why it suddenly bootloops? Is there any rookie mistake I'm making here?
Click to expand...
Click to collapse
Can you please link me the TWRP latest file ? I haven’t found it yet. And also, were you able to install LineageOS on your phone?