I'm new to XDA and to ROMs, so let me begin by saying hello and thank you to the regular posters. Many of my initial questions were answered by browsing and searching here.
My Nextbit Robin is still on the factory ROM: 7.1.1, security patch level April 1 2017. That's already too long to go without security updates in my opinion, hence my interest in moving to a maintained ROM that gets regular security fixes. My questions are:
Are there ROMs for Nextbit that are especially good on security updates? Or alternatively ROMs that aren't?
How are security updates usually handled by ROMs? Are they rolled into regular OTA updates? Are they separate and have to be manually applied? Something else?
Those ROMs I've looked most closely at (OmniROM and LineageOS) are at 7.1.2, just one minor release beyond the factory's 7.1.1. Does this imply that OmniROM and LineageOS's security releases haven't proceeded beyond when 7.1.2 was released quite some time ago?
I did search this forum, the sites of OmniROM and LineageOS, and the web, but if the answers are out there I didn't find them. Telling me to RTFM is fine; just point me to the FM.
Although I would not reject other things that ROMs can bring (improved performance vs. factory ROM, non-security bugfixes, new features, etc.), my chief interest is in keeping the phone up to date with all future security fixes via automatic OTA that I don't have to think about. Anything else that comes along with that would be great but would not be part of my decision making.
Feel free to go beyond my questions and point out things that I haven't mentioned but ought to know. I'm don't mind admitting that I'm new at this and there's a lot I don't yet know.
wpost said:
Are there ROMs for Nextbit that are especially good on security updates? Or alternatively ROMs that aren't?
How are security updates usually handled by ROMs? Are they rolled into regular OTA updates? Are they separate and have to be manually applied? Something else?
Those ROMs I've looked most closely at (OmniROM and LineageOS) are at 7.1.2, just one minor release beyond the factory's 7.1.1. Does this imply that OmniROM and LineageOS's security releases haven't proceeded beyond when 7.1.2 was released quite some time ago?
Click to expand...
Click to collapse
1. I recommend LineageOS. It's good on security updates. (Currently on March 5, 2018 security patch level.)
2. Yes, They are rolled into regular OTA. They usually include security updates within one or two weeks after they are released.
3. I may not have understood the third quesion correctly. 7.1.2 is the latest version of Android 7.x.x. After That It's 8.x. I don't think that affects the security updates.
OTA updates are checked automatically and you will be notified once an update available. But they won't be downloaded automatically. You have to press download button and then install it.
If you are planning to use encryption, you should use TWRP from LineageOS. I had problems with decrypting using TWRP from their official site.
And there are Oreo roms for robin. I think they also have latest security patches. I can't tell you much about them because I haven't tried all of them. However I've used AICP 13.1 and unofficial LineageOS 15.1 (OREO) releases (Read the last few pages of this thread and you can download them from here). Both are very usable. AICP is more customizable.
Thank you for the clear and complete answer. This will be my project for next weekend then.
KA5UN said:
1. I recommend LineageOS. It's good on security updates. (Currently on March 5, 2018 security patch level.)
2. Yes, They are rolled into regular OTA. They usually include security updates within one or two weeks after they are released.
3. I may not have understood the third quesion correctly. 7.1.2 is the latest version of Android 7.x.x. After That It's 8.x. I don't think that affects the security updates.
OTA updates are checked automatically and you will be notified once an update available. But they won't be downloaded automatically. You have to press download button and then install it.
If you are planning to use encryption, you should use TWRP from LineageOS. I had problems with decrypting using TWRP from their official site.
And there are Oreo roms for robin. I think they also have latest security patches. I can't tell you much about them because I haven't tried all of them. However I've used AICP 13.1 and unofficial LineageOS 15.1 (OREO) releases (Read the last few pages of this thread and you can download them from here). Both are very usable. AICP is more customizable.
Click to expand...
Click to collapse
Interesting that you brought up TWRP from Lineage OS.
I had used TWRP from TWRP site which I need to Format Data at first use which will decrypt me. So if I want to stay encrypted I should use TWRP from Lineage OS not normal TWRP?
iluvatrix said:
Interesting that you brought up TWRP from Lineage OS.
I had used TWRP from TWRP site which I need to Format Data at first use which will decrypt me. So if I want to stay encrypted I should use TWRP from Lineage OS not normal TWRP?
Click to expand...
Click to collapse
Yeah.
I had the same problem while using official version. I couldn't install OTA updates while using encryption because twrp can't decrypt data partition.
Also I think I read somewhere to remove any screen locks before encrypting (set them after). But I'm not sure if it's necessary.
KA5UN said:
Yeah.
I had the same problem while using official version. I couldn't install OTA updates while using encryption because twrp can't decrypt data partition.
Also I think I read somewhere to remove any screen locks before encrypting (set them after). But I'm not sure if it's necessary.
Click to expand...
Click to collapse
I'm confused now.
I want to be encrypted while on Lineage.
So if I rolled back to last stock ROM which is encrypted I should then flash the Lineage twrp you linked?
Thereafter on Lineage with Lineage twrp remaining encrypted I would be able to receive Lineage ota updates?
iluvatrix said:
I'm confused now.
I want to be encrypted while on Lineage.
So if I rolled back to last stock ROM which is encrypted I should then flash the Lineage twrp you linked?
Thereafter on Lineage with Lineage twrp remaining encrypted I would be able to receive Lineage ota updates?
Click to expand...
Click to collapse
TWRP can't decrypt stock encryption. If you're coming from stock you have to Format Data before installing lineage. After flashing lineage, you can encrypt the phone again. Then twrp (from lineage) can decrypt it.
If you are already on lineage and not encrypted, just flash that TWRP from lineage and encrypt the phone from settings.
If you're on lineage and encrypted, you can try flashing that TWRP. but I don't know if it'll be able to decrypt since I haven't tried to do that.
And yes, you would be able to install OTA updates.
KA5UN said:
TWRP can't decrypt stock encryption. If you're coming from stock you have to Format Data before installing lineage. After flashing lineage, you can encrypt the phone again. Then twrp (from lineage) can decrypt it.
If you are already on lineage and not encrypted, just flash that TWRP from lineage and encrypt the phone from settings.
If you're on lineage and encrypted, you can try flashing that TWRP. but I don't know if it'll be able to decrypt since I haven't tried to do that.
And yes, you would be able to install OTA updates.
Click to expand...
Click to collapse
Thanks for the detailed response. I'm concerned about encrypting under Lineage & getting bricked.
Is there a way to go from Stock encrypted > Lineage encrypted directly?
iluvatrix said:
Thanks for the detailed response. I'm concerned about encrypting under Lineage & getting bricked.
Is there a way to go from Stock encrypted > Lineage encrypted directly?
Click to expand...
Click to collapse
I don't think that's possible
KA5UN said:
I don't think that's possible
Click to expand...
Click to collapse
Yeah no prob
I'll just run unencrypted
Related
So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?
You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.
Twrp is working fine but I have nothing to flash to test...????
networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build
Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk
I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.
If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk
Hi all,
I'm currently on DP2 of 7.1.1 and I'd like to root my phone and install elementalX and possibly custom ROMS.
Once I am in a standard configuration I'm comfortable rooting and such, but I am unsure if I need to get off DP2 before doing so, and if I do need to get off DP2, I am not sure how to. I've seen reports that you cannot update to the release due to the older build date of the release than DP2... Odd but okay.
So my question to you fine folks is:
Do I need to get off DP2 before proceeding, and if so what should I flash to get off DP2?
Thanks!
I unenrolled in the beta program which pushed me back to 7.0, then flashed OTA to 7.1.1, unlocked bootloader, then flashed TWRC, then SuperSu, then kernel manager. Now I am done and happy
boardsportsrule said:
I unenrolled in the beta program which pushed me back to 7.0, then flashed OTA to 7.1.1, unlocked bootloader, then flashed TWRC, then SuperSu, then kernel manager. Now I am done and happy
Click to expand...
Click to collapse
I did the same.
Voluntarily withdrew from the OTA program here.
Flashing is quite simple. Just take it slowly
I have several Moto Z Plays here; two are retus and one is reteu. The reteu one is running 7.1.1 (official version, not a soak test, NPN26.118-22) because I downloaded the official update and sideloaded it yesterday. It has the July security patch. I was never a soak tester, either. The retuses are still on 7.0, May security patch (NPN25.137-24.4).
Here's the issue. When I sideload NPN26.118-22 (7.1.1. official) on a retus, I get an error saying "E3002: Package expects build thumbprint of 7.1.1/NPN26.118-22/21:user/release-keys or 7.0/NPN25.137-24.3/4:user/release-keys; this device has 7.0/NPN25137-24.4/5:user/release-keys," and it fails. (This also happened on reteu, but I happened to have the package it wanted to see, so I installed it first. See below.)
So, my next move is to replicate what worked on reteu, which was to flash the other package I have first, but I get another error saying "E3002: Package expects build thumbprint of 7.0/NPN25.137-24.3/4:user/release-keys or 7.0/NPNS25.137-24-1-9/10:user/release-keys; this device has 7.0/NPN25.137-24.4/5:user/release-keys."
I'm sort of at a loss from here of what to do, since the May security update for retus does seem to prevent compatibility with flashing any new package. The reason this wasn't an issue on the reteu one was, I'm assuming, because it was on the April security update, and I was able to install the second package, and then finally official 7.1.1 to get it current.
Anyone have any ideas? I can't be the only one running this freaking NPN25.137-24.4 (May) update on the retus Z Play that is preventing me from sideloading official 7.1.1. Thanks in advance!
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Zeljko1234 said:
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Click to expand...
Click to collapse
I appreciate your reply, but this isn't really relevant to my question at all. I acknowledge there are risks with flashing, but I did it successfully on one of my devices and it's really not the scariest thing I've ever done on ADB.
If you're content to wait, that's fine; what I want to know is the reason why I can't seem to do it on 2/3 of my devices. I'd appreciate responses that are relevant to my question.
I replied to your post on reddit, but I'll share it here too. Someone may even correct me here on XDA if I've got any info wrong.
The 7.1.1 that was released to most of us (retbr, retca, etc) require the build number NPN25.137-24.3 (May 2017 security patch) to be installed.
The May security patch on retus has the build number of NPN25.137-24.4 (I guess there was a change that warranted the .4 over .3). All retus phones will have this build number if they've installed the May patch.
This is why you were getting errors when trying to sideload 7.1.1 onto the retus phones (trying to install an update not meant for the device). retus will likely get a different install package for Android 7.1.1
How do you sideload using stock recovery? I tried adb devices and my device is not listed. I want to sideload Google stuff to stock ROM, any idea how to do that? Tried to install the APK files manually but I got force closed after that. Thank you.
Hi all,
so my current smartphone died for good and instead of getting a new one, I thought I'd revive my old Sony Xperia Z1 Compact. It's been a while since I switched it on so the battery is dead but I'm planning to buy a new battery and replace it. Then I plan to install LineageOS (which is based on Android 10 I believe?)
However I've never done rooting or anything more than basic end user stuff so I've searched the internet and thought I needed to root my phone and then flash the LineageOS. I've read some beginner guides on this forum and other places. However, I've ran into some conflicting/confusing(?) info and need some clarification before starting out. Hope someone can help with my admittedly-very-noobie questions:
1) Can I install LineageOS WITHOUT rooting my phone?
I believe that the bootloader needs to be unlocked first but is rooting necessary? The reason being is that I just want to get rid of the current stock ROM (I think it was Lollipop - can't know for sure because the new battery hasn't arrived yet) and install LineageOS. I don't want a rooted phone because it might conflict with banking apps and such (I know there are workarounds i.e. masking/reflashing/unrooting but as I am not that familiar with the development systems I will just be exposing myself to unknown vulnerabilities) so is it possible to just have the custom ROM and not completely root the phone?
2) Unlocking the bootloader
So I read I have to do a backup first before unlocking the bootloader. Is an SD card necessary or only for rooting? Since unlocking the bootloader will format the SD card anyway? Where should the backup be stored then?
I'd really appreciate some guidance. Thanks!!
Cheers,
traegr
LineageOS or most other roms aren't rooted by default. You will have to install solutions like magisk.
If you install twrp https://forum.xda-developers.com/sony-xperia-z1-compact/development/recovery-twrp-3-3-1-t3960699 make sure you are on latest stock firmware as you need the latest bootloader which allows booting into recovery. Flash firmware with Xperia Flashtool which has inbuilt firmware downloader. http://www.flashtool.net/index.php
If you can't boot into TWRP, you can try flashing attached file with xperia flashtool.
Instead of unofficial lineage I recommend AICP forum.xda-developers.com/sony-xperia-z1-compact/orig-development/rom-aicp-15-0-q10-0-amami-t4005457 . It's got good battery life and nice inbuilt tweaks and customization options..
Hope this helps
Also you need to flash Gapps if you want to use certain apps. Important point for AICP is that you can use microg instead. https://microg.org/
drater2 said:
LineageOS or most other roms aren't rooted by default. You will have to install solutions like magisk.
If you install twrp https://forum.xda-developers.com/sony-xperia-z1-compact/development/recovery-twrp-3-3-1-t3960699 make sure you are on latest stock firmware as you need the latest bootloader which allows booting into recovery. Flash firmware with Xperia Flashtool which has inbuilt firmware downloader. http://www.flashtool.net/index.php
If you can't boot into TWRP, you can try flashing attached file with xperia flashtool.
Instead of unofficial lineage I recommend AICP forum.xda-developers.com/sony-xperia-z1-compact/orig-development/rom-aicp-15-0-q10-0-amami-t4005457 . It's got good battery life and nice inbuilt tweaks and customization options..
Hope this helps
Click to expand...
Click to collapse
Hi, thanks for replying.
What's the difference between the lineage and AICP?
traegr said:
Hi, thanks for replying.
What's the difference between the lineage and AICP?
Click to expand...
Click to collapse
AICP provides more customizations while lineage is a "cleaner" approach. In the end AICP builds on top of lineage sources and adds several features. It totally depends on your personal taste. I consider it to be a bit overloaded. But that's my opinion. Which may be a bit influenced as I build the lineage version. Hehe
But once you have a recovery set up you can easily flash one, test it, and try the other one afterwards.
Hardware functionality should be same as AICP (SpiritCroc) and lineage (mse and me) share the same device tree sources. If one of us repairs something the other one will also get the fixes.
Both AICP and lineage have OTA update support. If you need microg you can either go with AICP 15 (Android 10) or Lineage 16 (Android 9).
Also you can easily backup your entire system with twrp if something goes wrong when flashing or whatever.
And when "hopping" roms you can make backups with Titatnium (root needed)
Can someone send me.a direct link to all Firmwares for the pixel 6 pro that I can flash stock Firmwares that is. I need the official Firmwares for all countries
Is this what you are looking for
https://developers.google.com/android/ota
Or the full firmwares https://developers.google.com/android/images, and the December ones that they removed from there Alternate links to December full factory images for .017, .016.A1 & A4, and OTAs for .017 & .016.A1 available.
I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?
Vincent_40 said:
I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?
Click to expand...
Click to collapse
You'll be able to use Official Google Android Flash Tool or the full factory image zip which as always would be available at Pixel 6 Pro Factory Images. Either will fully wipe your device. I don't have firsthand experience with Official Google Android Flash Tool so I don't know if it wipes by default but I know it can or has an option to if it's not default. The full factory images at Pixel 6 Pro Factory Images, without modification, always fully wipes the phone. Make sure and update SDK Platform Tools every month (sometimes earlier version Platform Tools doesn't work correctly and update the Google USB Driver if you're using Windows.
Ok thx i'll try to clean flash with next update with flash tool.
Hope Twrp will be released soon.
Vincent_40 said:
Hope Twrp will be released soon.
Click to expand...
Click to collapse
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.
roirraW edor ehT said:
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.
Click to expand...
Click to collapse
Yeah, about a month or two ago bigbiff said he was working on TWRP for Android 12 in general, but it would be a while. Honestly, haven't used it since the Nexus days. Really haven't missed it at all and probably wouldn't use it even when/if it does come out.
I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important
Vincent_40 said:
I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important
Click to expand...
Click to collapse
Yes, you can root with Canary Magisk 23016 without disabling verity & verification.
Ok i'll try
Thx for your reply