Related
I've used Wugfresh utilities to get the latest 7.1.1 on a recently acquired Nexus 9, since I'd used it a couple of years back. However, I'm finding that the noforce_encrypt build of Android 7.1.1 can't be found using those utilities. I found a version of it on androidfilehost.com, but have no idea what to do with it, or if it's the best/easiest option. Is my only option to use adb, fastboot, Java SDK, etc. and figure it out?
Also, there's a TWRP (3.5.?) on it that I don't see on the Nexus 9 I've been using for a couple of years. What suggestions do folks have for me moving forward? I can go ahead and use Android 7.1.1 via Wugfresh, but I wanted to build this without encryption and run it side-by-side with my other one to see if it smooths out some gaming, etc.
Thanks!
First thing, the tablet has reached EOL (where google is concerned), no more updates for it.
To run the tablet un-encrypted all you need to do is format data and flash one of the following (before booting the rom): -
SuperSU, Magisk, Custom Kernel or FED Patcher
Also get the latest TWRP from here.
As mentioned already, no support from google, so consider switching to a Custom Rom (e.g. LineageOS).
Also NRT is out of date and has not been update in a while. Learn how to use fastboot commands instead of relying on toolkits.
Edit: - If you go with a custom rom, remember to reflash your chosen method above, before booting an updated version or the device will encrypt again.
Thanks for the prompt reply - I will be dependent on Google Play Store so I don't think I can use any other OS besides Android, correct?
Kazz5 said:
Thanks for the prompt reply - I will be dependent on Google Play Store so I don't think I can use any other OS besides Android, correct?
Click to expand...
Click to collapse
Custom roms are also based on android, and you can flash GAPPS package and have full access to the play store.
[ROM][OFFICIAL] LineageOS 14.1 for Nexus 9 (flounder)
As my signature, that is the rom i have been using since September.
corkiejp said:
Custom roms are also based on android, and you can flash GAPPS package and have full access to the play store.
[ROM][OFFICIAL] LineageOS 14.1 for Nexus 9 (flounder)
As my signature, that is the rom i have been using since September.
Click to expand...
Click to collapse
I thought GAPPS was just a subset and didn't include a fully functional Google Play Store. Thank you!
Kazz5 said:
I thought GAPPS was just a subset and didn't include a fully functional Google Play Store. Thank you!
Click to expand...
Click to collapse
Most gapps have everything you need to have the stock Google experience. Opengapps, or beans. You get play store, Google play services, sync adapters, everything. And how many Google apps you get depends on the size of gapps you use. E.g. full, mini, micro, nano.
Thank you again! I'll start doing my homework. There are 3 parts, yes? TWRP, bootloader, and the OS?
*EDIT: And GAPPS*
Kazz5 said:
Thank you again! I'll start doing my homework. There are 3 parts, yes? TWRP, bootloader, and the OS?
*EDIT: And GAPPS*
Click to expand...
Click to collapse
Depending on rom, make sure you have proper bootloader, vendor (on arm64 you need proper vendor) then install latest twrp. Then use twrp to install rom and gapps.
https://developers.google.com/android/ota
Ota is live too...
Where I found the changelog?
Thanks
shark147 said:
Where I found the changelog?
Thanks
Click to expand...
Click to collapse
Same place as always: https://source.android.com/security/bulletin/pixel/2019-05-01.html
There doesn't seem to be much though:
This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices.
Click to expand...
Click to collapse
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
CSX321 said:
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
Click to expand...
Click to collapse
1) flash-all (minus -w). Phone reboots to system automatically.
2) shut down and boot to BL
3) fastboot boot twrp-3.3.0-0-blueline.img (be sure to have a copy of the .img file on your phone)
4) install twrp using Advanced > Install Recovery Ramdisk > twrp-3.3.0-0-blueline.img
5) boot to system
6) shut down and boot to BL>recovery (TWRP loads)
7) install Magisk-v19.1 (I did already have 19.1 installed on this phone via Magisk Manager update/Magisk update from before the May image came out in case it matters, so if necessary install 18.1 and then update to 19.1 with Magisk Manager)
8) reboot to system
9) confirm root and install kernel (for me that was ElementalX automated install using EX Kernel Manager app but installing the kernel by going back to TWRP and flashing should do the same)
The two things I might be doing different than others are not using ADB to get back to BL or recovery (I always use the key combo) and booting to system before next step (I don't stack my TWRP/Magisk/kernel installs). Hope this helps.
Whew! Back in business. Thanks!
CSX321 said:
Whew! Back in business. Thanks!
Click to expand...
Click to collapse
That's cool. Which part was the culprit?
sliding_billy said:
That's cool. Which part was the culprit?
Click to expand...
Click to collapse
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
CSX321 said:
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
Click to expand...
Click to collapse
I'd just be spit balling at this point like you are, but at least you are up and running. I do think there is possibly something going on with Magisk going from 18.1 to 19.1 without Manager doing the back end work (even if it happened previously) since Magisk still does retain some data even if root is lost during the upgrade. There are certainly some changes that occured between 18.1 and 19.0 beta since coming from 18.1 you would need to redo your Magisk hide check marks. Either that or using MM to patch boot may have completely changed.
sliding_billy said:
There are certainly some changes that occured between 18.1 and 19.0 beta
Click to expand...
Click to collapse
I probably just had something in some weird state, because I ran 18.1, 19.something beta, 19.something canary, then back to 19.1 stable when it came out. I forgot, I also ran the uninstaller at some point in my previous attempts.
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Same question
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I was coming to ask the same question, only I am in WA and have T-mobile. Stock, not rooted. Not had an issue before.
Same here. New P3 during April, so awaiting first security update for my new device. Carrier is AT&T, but why would that matter, right? Just seems strange having to wait. I got the impression that monthly updates for Pixels would come out the same day they were announced as being available. Live and learn I guess.
Finally popped this evening (5/16/2019). No clue why the delay.
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I have a Pixel 3 on Google Fi and still haven't gotten the update. Contacted support yesterday and they couldn't find anything wrong. They "promised" I'd get it. Always gotten them within a day or two before.
I guess I just never looked into this before since I'm a new Pixel user or I'm just naive but I assumed when I got a Pixel phones updates would not have to be pushed through my carrier anymore? No May update here on my stock Pixel 3 on T-Mobile.
Always get OTA on the day of release, stock phone, T-Mobile, the Netherlands.
(Pixel didn't launch in the Netherlands, I got it from Germany)
Just installed the may update OTA.
Anyone else having issues with apps accessing the gallery. Both WhatsApp and stock messenger now taking ages to display the thumbnails of the images and videos in my gallery when I add them to a message.
ok could I get some hints here on how to update?
I have rooted and I have magisk.
So here is a little pretext.
I have recently installed LineageOS 18.1 from here on my mido. I was previously on LineageOS 16.0 and my device was rooted with magisk.
After leaving MIUI I have never enabled encryption on my device. But this time after installing my current version of ROM I found that my device was encrypted. I could have formatted my device to disable encryption but then I would have to restore my apps+data again which I wanted to avoid. So I didn't format my device.
Recently I got the update for LineageOS 18.1 through the in-built Updater. I have downloaded it but I am hesitating before installing it. I am quite nervous because I am not sure if the process will go smoothly. I could also dirty flash the update. But I am not sure whether there is a difference between dirty flashing this update or installing via using the internal updater.
Can anybody help me with this. I have tried to search on internet but the results are not as relatable to my query. Some old posts on reddit and stackexchange covers dirty flash and/or OTA as different entities and even more posts are so old that according to them the idea of custom ROMs providing OTA updates is impossible.
Will somebody please guide me to some resources..!
Hey, I'm trying to downgrade my phone so I can use Lineage. I only have access to Linux and can't get Virtualbox to work, so I'm pretty sure MSM tool is out of the question. I've updated my phone to Oxygen 12, but Oxygen 11 is still in the other slot. I did try switching slots to get on Android 11, but it wouldn't boot, even after I cleared the userdata partition. Now that I think about it, would I even need to boot the device to install Lineage, or would I just need to have Android 11 installed and be able to use the bootloader with fastboot commands? Or if I would need to boot, how would I get Oxygen 11 fully working?
(Also, it's T-Mobile firmware, so I also can't downgrade with their official app)
You don't have A11 firmware anymore, which I guess is also why you can't boot stock A11 now. Updates can update more than what the A/B slots cover.
AndyYan said:
You don't have A11 firmware anymore, which I guess is also why you can't boot stock A11 now. Updates can update more than what the A/B slots cover.
Click to expand...
Click to collapse
you mean a11 just disappeared from the other slot? i could reflash it but i'm scared, i guess if everything is in separate slots then i can't mess up alot tho
androidloyal said:
you mean a11 just disappeared from the other slot? i could reflash it but i'm scared, i guess if everything is in separate slots then i can't mess up alot tho
Click to expand...
Click to collapse
Only some partitions remain, not enough to cover the "firmware" part. Just find a Windows PC to MSM with.
androidloyal said:
Hey, I'm trying to downgrade my phone so I can use Lineage. I only have access to Linux and can't get Virtualbox to work, so I'm pretty sure MSM tool is out of the question. I've updated my phone to Oxygen 12, but Oxygen 11 is still in the other slot. I did try switching slots to get on Android 11, but it wouldn't boot, even after I cleared the userdata partition. Now that I think about it, would I even need to boot the device to install Lineage, or would I just need to have Android 11 installed and be able to use the bootloader with fastboot commands? Or if I would need to boot, how would I get Oxygen 11 fully working?
(Also, it's T-Mobile firmware, so I also can't downgrade with their official app)
Click to expand...
Click to collapse
you should downgrade with the T-Mobile MSM tools. Note that your data will be wiped, so make sure you have a backup if you want one!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.