Related
Hi all,
I'm currently not encrypted and prefer to keep it that way, I don't like entering passwords everytime I go to TWRP and I prefer the old school android system where encryption was a choice, not a mandatory decision made for you.
So when I install a ROM I run a few commands prior to installation to avoid forced encryption, unless it has an option within aroma to disable force encryption which most don't
Thanks to @j to the 4n for help with this, legend
Anyway if you'd like to install a ROM like lineage or aosp or resurrection remix etc and remain not encrypted? Keep reading.
*Note: if you're encrypted prior to doing this then stop, this is for people who've chosen to disable force encryption already but would like to retain it after installing aosp / lineage ROMs.
However if you'd like to remove encryption you'll need to format data via TWRP, not a wipe! Format.
Make sure you back up prior to doing this as it will format data, best to have the ROM on your SD card too so you don't end up with no OS.
If you've done the above or you already have a ROM installed without encryption, then you should be good to go.
------------------------------------------------------------------------------------------------
Just before youre about to install a ROM, let's say resurrection remix ( tested )
Make sure your phone is in TWRP and you're connected to your PC then just before you're about to click install, open up a command prompt on your PC then from ADB shell send the following commands to the device from your PC..
For Magisk:
echo "KEEPFORCEENCRYPT=false" >> /cache/.magisk
If the rom uses SuperSU, send the following commands.
echo "KEEPFORCEENCRYPT=false" >> /data/.supersu
echo "KEEPFORCEENCRYPT=false" >> /cache/.supersu
Then install your rom as normal.
Obviously for ROMs like viper your don't need to do this as there is an option within aroma, but for the likes of RR or lineage this will mean your phone will not encrypt on boot.
Should work for all ROMs but I've not tested this on all of them so if it goes wrong then it's not on me, this worked perfectly for me on RR coming from viper whilst not encrypted.
*Note: if you're not sure what root method your ROM uses then simply send all three commands and you should be good to go.
By using these you're not going to find yourself in TWRP being asked for a password you don't have as your device has been encrypted, I've lost data myself this way and it's extremely annoying.
:good:
If I can ask if anyone tries this and it works, would you mind replying with what it worked on so I can update the OP.
Cheers.
PS: if you're not sure what this is or have any questions, please ask away
Anyway to do this from the device for when your not near a PC?
JohnFawkes said:
Anyway to do this from the device for when your not near a PC?
Click to expand...
Click to collapse
Yes i believe it is, would need to write up a script which is ran prior to installing the rom, i've not got around to doing it yet.
Strictly speaking this should be an option with all roms, it's not exactly a lot of work is it?
Deleted
Works pretty well on Stock ROM.
Just RUU'd, and before rebooting went into download mode, flashed Recovery, flashed SuperSU, used this Command. and boom.
Multirom works.
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
dladz said:
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah it pisses me off. But at least with this handy zip you can flash it anyway and have some mental relief that you stay decrypted.
Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Haldi4803 said:
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Click to expand...
Click to collapse
Sorry I hadn't tested with all ROMs, not even sure Pure Fusion was even available when I had my HTC 10.
Stick to the script, it's quick, easy and works, you can try a zip but unless someone has gone before you you're potentially walking into a bad time.
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Haldi4803 said:
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Click to expand...
Click to collapse
That's absolutely fine. Because this thread isn't about the zip..I have nothing to do with that, so in regards to the zip you flash it at your own risk.
Deleted
Though i do agree with him that having a .zip and not needing a Computer every time would be pretty usefull.
Does anyone know how to create TWRP flashable zips that includes only this 2 commands?
Hello I tied this for RR rom but I got this message in the cmd, am i doing something wrong?
edit i found my fault I had to adb shell
I know it's been about a year, since somebody posted, but: if anbyone else like me stumbles across this thread, have a look at: https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
It gives you even more information how to enable or disable encryption or dm-verity while usinf magisk.
Btw. you can use the terminal in twrp also, see link.
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Subh4sh said:
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Click to expand...
Click to collapse
Ofcourse,cause echo command is available everywhere.just make sure you install the magisk/supersu first before running the command
hi,
If I format /data, then the encryption is gone and LOS can be installed where backup with TWRP work?
I have U11, but i think it is the same...
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
When does the development starts?
I don't know the procedure of ROM development. Are devs waiting for the oreo update from HTC?
Some devs already work on Oreo aosp, but it's not that easy to get it working on the 10 so that everything works. Maybe even stock will be earlier here than custom Roms like aosp and los
Sent from my HTC 10 using XDA Labs
Don't really know about LOS but AOSP based is already here...
https://forum.xda-developers.com/htc-10/development/rom-official-pure-fusion-os-oreo-t3694203/page2
P.S why is there a Dev in the Title?
Is there any news?
kingfared said:
Is there any news?
Click to expand...
Click to collapse
Lineage has a whole site with news and downloads and everything: https://www.lineageos.org/
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
Honestly Annoying said:
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
Click to expand...
Click to collapse
You can't start a "Dev thread" if you aren't a dev on the project; you can only start a "Nag thread".
Sorry for unqualified question. I know the new site but I don't know where to find dev threads. If you can help me I'll be glad.
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Ndaoud360 said:
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Click to expand...
Click to collapse
That device still has an active developer working on it. crpalmer, the user who brought 14.X to HTC 10 seems to have moved on to newer devices.
hope it will have LOS15.1
Even though Raymon left development does this mean there are no los 15 for us?
As already stated by fagyi, once he solves all bugs on aosip 8.1 he will build los.
15.1 Running flawless albeit hot sometimes!
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
heyChristo said:
Ladies and Gentleman,
I have been extremely pissed off lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
If you are so frustrated about stuff you get for free than just stay stock and stop being frustrated.......mwuhahaha funny how the world works these days......oh and by the way, you don't downgrade your kernel, you downgrade your firmware.
Cheers, have an absolutely fabulous Sunday
heyChristo said:
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Musthafa-Noor said:
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Click to expand...
Click to collapse
Nougat.
heyChristo said:
Nougat.
Click to expand...
Click to collapse
Maybe was wrong. Maybe was Oreo firmware. Switched to this and had to go the other one. Sometimes I just go into a flashing rage and can't rememember what happened after.
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Click to expand...
Click to collapse
I'm using that ROM build of 15.1 on my HTC 10 (Android 8.1), and it works pretty good actually. besides a few minor issues.
Unlocked Bootloader from HTCDev, Running latest TWRP Recovery, S-On (for me at least was not needed to turn this off), Latest Magisk (which seems to pass the Safetynet check) / Busybox.
I changed the Kernel afterwards to "kernel_htc_pme_aosp_tabp0le_eas_4.02-O" (from tabp0le) because it has the "performance" cpu governor that i can enable using Kernel Adiutor.
The bugs i encountered so far :
- Camera apps open slowly, except for "Open Camera" , not a big issue.
- HTC Sense Launcher doesn't seem to work, just get the famous (app has stopped) message, but maybe it's a conflict with my GAPPS installation
- Only 1 speaker works, HTC10 has Boomsound with 2 speakers on stock rom, 1 is a treble speaker, the other one is kinda like a small subwoofer for the low frequencies.
Is there any soundmod that would enable both speakers again?
There is not any mod to do that. But the dev of this ROM is working on getting the bottom speaker working.
I just saw that a new build-version is released for HTC10.
lineage-15.1-20180624-UNOFFICIAL-pme.zip
Any help is greatly appreciated, I have no experience with Google phones, I was years into Sony.
I have just bought a Pixel 2 XL from a local shop in Greece, and of course, I want to root it and be able to install custom roms etc.
I have a few questions that I am searching everywhere recently and I would really appreciate if someone can make it clear to me:
1) I have read that you have to buy your phone from Google so you are able to unlock it? Can someone explain this to me? (My phone is not a specific carrier) How do I know if I am able to unlock my bootloader?
2)I have flashed roms and kernels in the past on my Sony phones, however I haven't really messed with the bootloader other than just unlocking it in the beginning. So now on the Pixel 2 XL I am reading so much about the unlock_critical vs the normal unlock, and I can admit I cannot understand the difference. Why does someone want to flash a bootloader? ( I do not understand what does "flash a bootloader" mean)
What I want to be able to do is flash custom roms, flash factory images to revert back to stock whenever I want, flash custom kernel, flash stock kernel, make a nandroid backup with twrp and restore a nandroid backup with twrp. That is all I want to be able to do without facing any errors with the bootloader,so do I need the unlock_critical ? And why?
3)If I unlock the bootloader with any of the two ways, am I able to re-lock it like nothing has happened? For example if the screen has dead pixels for some reason and I want to send it back for warranty but the bootloader is unlocked, can I lock it without it being logged? Or once unlocked, there is no going back to the warranty by re-locking? On many Sony phones we could do that.
4)If I unlock the bootloader and install TWRP I read that I will not be able to receive official updates from settings any more (OTA):
"NOTE #1: If you have mounted /system as rw at any point (like in TWRP), you must upgrade using the factory image method. OTAs will fail because they cannot verify the integrity of the disk since its verity data has been changed."
My question is, if I flash a stock image, does that get fixed? ( so if I flash 8.1.0 stock manually, will I be able to get an official update e.g. 9.0.0 from settings?)
Or if I just grab the stock boot.img of my current version of android and flash it with fastboot, then will I be able to get official updates from settings normally again?
5)Can I do the following on this order? :
Enable USB Debugging and OEM Unlocking
Unlock the bootloader (either critical or normal, whatever works)
Boot into Fastboot
Boot the twrp image from fastboot to the device
Flash the twrp zip to the phone to install TWRP
Flash the magisk zip so I root the device
Reboot and everything works? (Or do I need a custom kernel for TWRP or Magisk to work?)
Is there any issue you see with the above plan of mine?
6) Before I tweak my device in any way, is it okay if I update the device fully? So can I install any update available (OTA) and then unlock the bootloader and root etc? Or do I have to be on a specific version and not on the latest?
7)I have read something about 2 different slots on some flashing forums here, slot a and slot b, but it is not clear to me what that is. Does anyone know what that is? At which point may I face this?
Thank you very much.
A quick and not complete response to get you going
Plan 5 seems solid, unlock the bootloader to allow custom stuff. At boot you will get a warning screen to let you know.
I forgot if I only unlocked the bootloader or also the critical, try it etc.
Personally I never had to tinker with the A/B slots, within TWRP you can choose which to use.
Before Magisk, I used to flash another recovery like cwm or twrp but it is not required. You must however boot to twrp.img to flash the magisk zip.
As far as I know it is indeed the altering of the /system folder that denies future OTA (when using factory image). A manual flash (of future OTA) is easy but may require altering (removing) a switch command in the install.bat file to remove the -w (wipe).
As to the custom kernels, I never noticed the need and am running the latest v10 image with only Magisk flashed to get root.
My main goal is to get rid of ads. I use AdAway.
To get that to work in v10 you need to enable systemless host module im the Magisk manager app (reboot after).
A final feedback; when you get to sideload and need to get to recovery you may get the screen 'no command' or so; press volume-up and click power or power->click volume.
Let us know if you worked it etc!
arismelachrinos said:
Any help is greatly appreciated, I have no experience with Google phones, I was years into Sony.
I have just bought a Pixel 2 XL from a local shop in Greece, and of course, I want to root it and be able to install custom roms etc.
I have a few questions that I am searching everywhere recently and I would really appreciate if someone can make it clear to me:
1) I have read that you have to buy your phone from Google so you are able to unlock it? Can someone explain this to me? (My phone is not a specific carrier) How do I know if I am able to unlock my bootloader?
2)I have flashed roms and kernels in the past on my Sony phones, however I haven't really messed with the bootloader other than just unlocking it in the beginning. So now on the Pixel 2 XL I am reading so much about the unlock_critical vs the normal unlock, and I can admit I cannot understand the difference. Why does someone want to flash a bootloader? ( I do not understand what does "flash a bootloader" mean)
What I want to be able to do is flash custom roms, flash factory images to revert back to stock whenever I want, flash custom kernel, flash stock kernel, make a nandroid backup with twrp and restore a nandroid backup with twrp. That is all I want to be able to do without facing any errors with the bootloader,so do I need the unlock_critical ? And why?
3)If I unlock the bootloader with any of the two ways, am I able to re-lock it like nothing has happened? For example if the screen has dead pixels for some reason and I want to send it back for warranty but the bootloader is unlocked, can I lock it without it being logged? Or once unlocked, there is no going back to the warranty by re-locking? On many Sony phones we could do that.
4)If I unlock the bootloader and install TWRP I read that I will not be able to receive official updates from settings any more (OTA):
"NOTE #1: If you have mounted /system as rw at any point (like in TWRP), you must upgrade using the factory image method. OTAs will fail because they cannot verify the integrity of the disk since its verity data has been changed."
My question is, if I flash a stock image, does that get fixed? ( so if I flash 8.1.0 stock manually, will I be able to get an official update e.g. 9.0.0 from settings?)
Or if I just grab the stock boot.img of my current version of android and flash it with fastboot, then will I be able to get official updates from settings normally again?
5)Can I do the following on this order? :
Enable USB Debugging and OEM Unlocking
Unlock the bootloader (either critical or normal, whatever works)
Boot into Fastboot
Boot the twrp image from fastboot to the device
Flash the twrp zip to the phone to install TWRP
Flash the magisk zip so I root the device
Reboot and everything works? (Or do I need a custom kernel for TWRP or Magisk to work?)
Is there any issue you see with the above plan of mine?
6) Before I tweak my device in any way, is it okay if I update the device fully? So can I install any update available (OTA) and then unlock the bootloader and root etc? Or do I have to be on a specific version and not on the latest?
7)I have read something about 2 different slots on some flashing forums here, slot a and slot b, but it is not clear to me what that is. Does anyone know what that is? At which point may I face this?
Thank you very much.
Click to expand...
Click to collapse
1) The reason for this is Google had an exclusivity contract to sell through the US cellular company, Verizon; much like the original Apple iPhone did (at first) with AT&T. And, for reasons that are most likely stupid, foolish, and unconvincing in its justifications, Verizon locks their device's bootloaders. So, not that it's "locked" or "unlocked" in terms of carriers, but more-so whether a device is "locked bootloader" or unlockable because it was purchased from Google (or elsewhere, but at least originally Google) and not from Verizon. If you're wondering further, getting it from Verizon would allow Verizon subscribers and customers to be able to "lease" and pay the Pixel off in increments with their usual cell phone bill; but it's not all too exclusive because Google offers to lease if you purchase from them also! The only caveat is you have to pass a credit check when leasing from Google; but, then again, you have to pass a credit check when signing up for a Verizon cell plan as well!
2) So, with my limited understanding between the difference between just a regular "unlock" and an "unlock_critical" is that it might be that a regular unlock allows you to get a R/W access (root access) to the various vital partitions (i.e. system, data [not to be confused with userdata], even boot to a degree) while unlock_critical allows you to straight modify and replace partitions (i.e. what would've been the recovery partition [but now there's no such thing and recovery just resides in the boot partition], the whole system & data partition to have/run custom ROMs, bootloading screen, etc.). But it all is rather convoluted that Google probably agreed and, so you can/should be aware, they updated things within the past few months (I'm guessing June or July) where they rid the need to "unlock_critical" and bootloaders that are newer than a certain point/month no longer needs that fastboot command to unlock the bootloader and everything else in order to flash custom anythings...
3) Okay, so here's a very tricky thing to this.... Technically, yes you can relock the bootloader as well as there have been many who have successfully done so; BUT there are so many more that have COMPLETELY and permanently bricked their device attempting to do so and most (if not all) the experts here would advise anyone to just leave well enough alone. But, if it is insisted and must be, the way to do it is to remove all Magisk modules (because, for whatever reason, these modules can survive a complete flashing of a Full Factory stock image), run a Full Factory image where the flash-all command is left intact (meaning “-w” is unedited; I’ll go more into this later), running it through the initial set up process, then (for good measure, this step might not be at all absolutely necessary) switch slots and run the flash-all command on the other slot, running the initial set up process again, then rebooting to Bootloader Mode and running the fastboot locking command, then unticking (if wished and insisted) unticking the OEM unlocking. Again, a word of warning, that so many have relocked the bootloader and unticked the OEM unlocking which allows the unlocking of the bootloader, then find that their device goes into a bootloop; and since they had just locked the bootloader in 2/all different ways, it leaves rescuing the device with all but the fewest options – usually because it’s forgotten in one way or another returning all of the device back to stock.
If anything, what has been said around these forums is that, if returning to Google, there hasn’t been an (proven) instance that Google refused to repair/replace it because it had its bootloader unlocked. But it’s usually for that fear or re-selling the device in which this is usually sought; but in most (if not all) cases (the experts here figure), having the bootloader unlocked would be refused or looked down upon.
4) So, most of what you assumed here is correct; but may be a bit misguided due to not knowing some things – which, of course, can be expected since you had just said you just moved to this device from a totally different manufacturer (Sony). If you are rooted (Magisk), there is absolutely no way you can update via the regular System Update from an OTA from within the Settings in the OS. And even having just an unlocked bootloader will cause OTAs to not work -- but there are conflicting reports stating differently, but I, personally, am under the understanding that even at that point you cannot.
But here’s the key thing; there really isn’t any reason to install updates by download and using OTAs anyways. Most (if not all) the experts here actually forego the OTAs and merely download the Full Factory stock images from Google’s Developers website and flash those. Here’s the reason; in the “olden days”, flashing a stock Full Factory image would erase absolutely everything and return the device to a complete factory state. But Google, in their “infinite wisdom”, allowed it to be possible to flash this but still withhold and save/keep all of one’s apps, settings, and data – essentially leaving both device data and userdata untouched! This is achieved by simply editing a batch file called “flash-all.bat” (or “flash-all.sh” for Linux and MacOS) and removing the 3 characters “-w” (3rd character would be a space “character”) from within its code. In this manner, OTAs can be considered a “dirty flash” because, while a Full Factory will completely overwrite (I could be wrong, but I believe it erases and formats it) the system, radio, bootloader, boot, etc., which would/should take care of any erroneous bugs or glitches, while OTA’s do not necessarily do this and just “modifies” the existing data; and therefore bugs and glitches may still remain being more on the root of things and/or OTAs would just modify “on top” or elsewhere where those glitches may reside.
And in either/both cases, one would still be required to reflash/reinstall everything root.
But, if insisted, there are multiple methods to achieve a state where you can run an OTA; either downloading an OTA image from Google and manually flashing it (“sideloading”), or unrooting temporarily to be able to use & download the regular System Updater (can be found HERE : https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md#ota-installation under the “Devices with A/B Partitions” which is my preferred method if I was to do this sort of thing, but I have never done this so I’m unsure if it even is successful in our device). I even wrote out an in-depth and step-by-step guide, but it is rather convoluted and was written in the beginnings of our taimen and there are most likely more updated methods now; but if you want to check it out, you can HERE.
But, to answer your questions directly; No, flashing the stock image will not allow you to user the stock System Updater; although there are conflicting reports, I am under the impression that anything other than a locked bootloader will allow the stock System Updater to work.
5)More correctly, you boot into “Bootloader Mode” to be able to use the “fastboot” commands. And no, you do not need to permanently flash a custom recovery (TWRP), a custom kernel, or anything else to achieve root – although I do highly recommend it – as you can temporarily boot into TWRP (by downloading the TWRP image file (*.img) and install Magisk in that manner – I do not suggest you root/install Magisk using the app. Other people have had success, but many (most?) have issues that you wouldn’t run into if you installed it via TWRP – but here’s a key thing; no matter what you intend to flash and install, unless you need to have root for it to already be installed, you should always flash Magisk last. Moreso, as the great Az Biker of ‘round thes’ parts greatly suggests, you should even reboot to bootloader after each and every flash separately. Explanation is, for whatever reason and even though many claim to be able to “detect” and modify their flash for an already modified boot and dtbo (where modifications must happen for root access), most don’t play well with Magisk and Magisk must modify the boot and dtbo after all other modifications or else problems can arise (or at least it has for me).
Just keep these things in mind, but, for the most part, your “order” of things will do well enough. Again, just keep in mind that if you are going to install a custom recovery or kernel, try to do that before Magisk as well as if you can avoid it, don’t use the Magisk app to install or manually flash any boot.img if you can help it.
6)No, you don’t have to stick to a specific version; it might even be suggested to update it stock before doing anything. BUT (of course there is a caveat), consider this; many things (especially anything root and specifically TWRP) aren’t really “playing nice” with Android Q/10; so, if you update and go to the most up to date, but don’t wish to run into those glitches/bugs and wish to “hold off” (like I am, actually and for the same reasoning), then of course you should only go up to August (I believe that was the last before the upgrade to Q/10) Full Factory.
7) There are many great resources on the information on having the 2 different slots; I apologize if I can’t recall where I even saw them – other members (maybe an RC or Mod even) input a URL to read and I can’t for the life of me recall where it possibly could be. But, for the most part, you would really only run into identifying and manually changing to a specific one if you were attempting to rescue or deeply modify your device; I can say that me and the great @Az Biker have never felt the necessity to manually change or choose a certain, specific slot. And, my guess, is that, because the coding and flashing output when running the Full Factory states something about “system_other” or a “system_b”, but while the main system can be close to 3GB, the system_other is closer to 300MB, and that boot, dtbo, vendor, and something called lafb has a “_b” partition, I’m thinking it’s something as a safety or backup, maybe something like what used to be in old laptops a sort of RAM to help load things up faster. In any case, it seems that going from one to the other, a to b or vice-versa, doesn’t seem to be too key or much of a hassle, so….take that for what you will.
Alright…hopefully I was able to answer all your inquiries. And, if you have any more, please feel free to ask them…that’s what we’re all about here. And I know I can run on and get wordy, so thank you for bearing with me with all of this.
I mean, it’s really good to have a user/member who really does their research, reading, and due diligence before getting into their new device; there are so many instances here and in my own experience where the “…if I only knew that beforehand…” would be supremely helpful, and supremely easier on everyone else! So that’s to be commended and reinforced…!
Hope this helps and welcome to your Pixel and this taimen forum!
I really cannot thank you enough for your time. I truly appreciate it very much.
1) Very clear.
2) Do you happen to have a link or do you know how to check if my phone supports unlock_critical? How can I check if I have that newer bootloader? Or do you remember where did you learn this?
3) Thank you so much about that. Very clear aand you just saved my phone
4) Very clear.
5) Thank you for the info! Interesting, I was searching on how to root the device running Android 10 (I have fully updated and I really am not going back to Android 9 ), and I saw that you have to patch your boot.img with the Magisk app, and then flash it with fastboot. So first you get the factory image from google and you extract the boot.img and insert it to the phone. Then you load it into Magisk app and patch it. Then moving the patched to the PC, booting to bootloader and flash it on boot partition. This is the way I saw on how to get root working fine with Android 10, not sure if it is the best method or the worst.
6) What do you mean with "go up to August"? Do you mean that the "oldest" image I can flash is "9.0.0 (PQ3A.190801.002, Aug 2019)"? So one cannot go back to 8.0.0 and Google has done something to prevent us from doing that? Also, if I wanted to go back to that August image or any "compatible", the procedure is just to run the flash-all.bat file of that image?
I used to experement a lot with custom roms, custom kernels and mods with my Sony devices, but that was mainly because I wanted stock android and some more features. The thing is that I have almost anything I need with this device, with some minor wishes. So I can leave without flashing custom roms and kernels, but I wanted to just root and at least install Adaway(!!!!!! I cannot leave with those ads!!!!!!), Titanium Backup and some other similar root apps that don't really do any harm. Have you tried rooting Android 10 and it was unusable? Do you suggest that it is not really worth it? The thing is that I love Android 10, the gestures and all the features, and I could not go back to Android 9, even though I only used the phone for a week, I am used to it and really like the way it currently is.
7)Hmm okay so I should not really mess with that. Maybe as I saw online, when flashing stock or unrooting, it is best to flash the same thing to both a and b slots, seems a bit complicated but whatever
Thank you for being so helpful!!
arismelachrinos said:
I really cannot thank you enough for your time. I truly appreciate it very much.
1) Very clear.
2) Do you happen to have a link or do you know how to check if my phone supports unlock_critical? How can I check if I have that newer bootloader? Or do you remember where did you learn this?
3) Thank you so much about that. Very clear aand you just saved my phone
4) Very clear.
5) Thank you for the info! Interesting, I was searching on how to root the device running Android 10 (I have fully updated and I really am not going back to Android 9 ), and I saw that you have to patch your boot.img with the Magisk app, and then flash it with fastboot. So first you get the factory image from google and you extract the boot.img and insert it to the phone. Then you load it into Magisk app and patch it. Then moving the patched to the PC, booting to bootloader and flash it on boot partition. This is the way I saw on how to get root working fine with Android 10, not sure if it is the best method or the worst.
6) What do you mean with "go up to August"? Do you mean that the "oldest" image I can flash is "9.0.0 (PQ3A.190801.002, Aug 2019)"? So one cannot go back to 8.0.0 and Google has done something to prevent us from doing that? Also, if I wanted to go back to that August image or any "compatible", the procedure is just to run the flash-all.bat file of that image?
I used to experement a lot with custom roms, custom kernels and mods with my Sony devices, but that was mainly because I wanted stock android and some more features. The thing is that I have almost anything I need with this device, with some minor wishes. So I can leave without flashing custom roms and kernels, but I wanted to just root and at least install Adaway(!!!!!! I cannot leave with those ads!!!!!!), Titanium Backup and some other similar root apps that don't really do any harm. Have you tried rooting Android 10 and it was unusable? Do you suggest that it is not really worth it? The thing is that I love Android 10, the gestures and all the features, and I could not go back to Android 9, even though I only used the phone for a week, I am used to it and really like the way it currently is.
7)Hmm okay so I should not really mess with that. Maybe as I saw online, when flashing stock or unrooting, it is best to flash the same thing to both a and b slots, seems a bit complicated but whatever
Thank you for being so helpful!!
Click to expand...
Click to collapse
It’s really my pleasure! And I’m just as thankful that you/anyone would even go through the trouble of reading all of that…!
1) Thank you for the compliment
2)Usually, if your bootloader version is within a certain version – which you can find when in bootloader mode – then you either do or do not need unlock_critical. I can’t remember how many months prior to Android 10/Q, it was within 6 I believe, so any bootloader version from 5 or 6 months ago to now, and obviously if you’re on 10/Q, you would not need to run the command unlock_critical. But, if anything, you don’t have to have any fear of it, whether you need to or not, or don’t know your bootloader version, running the “fastboot flashing unlock_critical” when you don’t need to will just amount to a simple error and nothing bad will happen. And if it does end up doing something, well, then that’s a good thing. It almost amounts to unlock_critical-ing twice, the second on will just state that it’s already unlocked and that’s it.
If anything, I believe I found the resource here from the great Az Biker: https://forum.xda-developers.com/showpost.php?p=78908055&postcount=2843
If you are very curious, it should address much of what you’re seeking and/or at least point you to where you might find that information.
3) You’re very welcome. It really is a good thing that saves you in the future, and saves those who try to help some grief as well.
4) Thank you for the compliment.
5) I would say that the process you described is certainly doable, but is far from the best/easiest. From my experience helping many here on this forum, many bugs or things go wrong when loading the stock boot.img to the phone, having Magisk modify it, then getting the modified boot.img and successfully flashing it. More often than not, one ends up having a device turn into a boot loop and are usually forced to flash the stock boot.img and have to give it a number of tries.
The best way (subjectively) is to download the Magisk installation .zip. Then boot into TWRP (which doesn’t mean you have to replace the stock recovery since you can temporarily boot into it), and “Install” it using the .zip. Then everything is automated and done for you, if anything goes wrong you have an output log you can use to troubleshoot, but it seems best to leave it to the experts who created all this than us manually attempting to ourselves.
Oh and AFAIK this method still works on Android 10/Q as it has for Pie and Oreo.
6) I meant that, if you did not wish to update to 10/Q, then you shouldn’t do anything newer than from August’s security update/patch, since all the Full Factory images and updates are of 10/Q. But, if you go to Google’s Developers site, you’ll see that they pretty much list and make available all the Full Factory images ever published; to the point that there are some that go back to Oreo!
And everything you’ve said is understandable. And I kinda feel the same way. For me, in my humble opinion, it is supremely good idea to root and for whatever issues you get doing that, the returns are incalculable. It is most definitely worth it/rooting! The extra options and customizations and modifications all make it worth while and more! And, even if rooting gives the capability of rendering the device rather unusable, take confidence in that Google, in all their “infinite wisdom”, gave us “Bootloader Mode”…and pretty much, as long as you can get into Bootloader Mode and successfully connect to a computer, your phone would never be considered too far lost/gone. I’ve only witnessed that be opposite on less than a handful of cases.
But, most importantly, and if you have been in the rooting and ROMing game, you should well know this, but the most vital part of having root access is the ability to make the best backups! So, as long as you make sure to backup (Nandroid is best) and key times, running into some pitfalls here and there shouldn’t take you all the way out of the game….
7) Yeah…I mean, it is rather fascinating, and when up against an issue and you have an idea that deals with it, that’s when you can read up and learn about it and experiment I imagine. But for me and one of the great ones here in all of XDA, we’ve done all the custom ROM, custom recovery, custom kernel, Full Factory recover, root, Magisk modules, theming, Xposed, and countless other things, and all without the need to ever mess with manually or forcing an assignment between the two.
Again, it’s my pleasure. And if you any further questions or thoughts, bring them on! I’d be happy to address them…
Hope these are helpful….
arismelachrinos said:
I really cannot thank you enough for your time. I truly appreciate it very much.
1) Very clear.
2) Do you happen to have a link or do you know how to check if my phone supports unlock_critical? How can I check if I have that newer bootloader? Or do you remember where did you learn this?
3) Thank you so much about that. Very clear aand you just saved my phone
4) Very clear.
5) Thank you for the info! Interesting, I was searching on how to root the device running Android 10 (I have fully updated and I really am not going back to Android 9 ), and I saw that you have to patch your boot.img with the Magisk app, and then flash it with fastboot. So first you get the factory image from google and you extract the boot.img and insert it to the phone. Then you load it into Magisk app and patch it. Then moving the patched to the PC, booting to bootloader and flash it on boot partition. This is the way I saw on how to get root working fine with Android 10, not sure if it is the best method or the worst.
6) What do you mean with "go up to August"? Do you mean that the "oldest" image I can flash is "9.0.0 (PQ3A.190801.002, Aug 2019)"? So one cannot go back to 8.0.0 and Google has done something to prevent us from doing that? Also, if I wanted to go back to that August image or any "compatible", the procedure is just to run the flash-all.bat file of that image?
I used to experement a lot with custom roms, custom kernels and mods with my Sony devices, but that was mainly because I wanted stock android and some more features. The thing is that I have almost anything I need with this device, with some minor wishes. So I can leave without flashing custom roms and kernels, but I wanted to just root and at least install Adaway(!!!!!! I cannot leave with those ads!!!!!!), Titanium Backup and some other similar root apps that don't really do any harm. Have you tried rooting Android 10 and it was unusable? Do you suggest that it is not really worth it? The thing is that I love Android 10, the gestures and all the features, and I could not go back to Android 9, even though I only used the phone for a week, I am used to it and really like the way it currently is.
7)Hmm okay so I should not really mess with that. Maybe as I saw online, when flashing stock or unrooting, it is best to flash the same thing to both a and b slots, seems a bit complicated but whatever
Thank you for being so helpful!!
Click to expand...
Click to collapse
As @simplepinoi177 said, I'm part of the community that just let's the factory image flash the slot it needs/wants to, and it's never once been an issue.
Look at it like this; some people prefer to simply copy/paste a link or block of text in the PC, some people prefer to CTRL + C then CTRL + V.... BOTH take you to the same end.
Plus, knowing me, the more I manually mess with Slot A vs Slot B, the more chance there is for me to screw something up
Best of luck with your 2 XL, it's a FICKLE device, but it's a really, really great device once you get it as you want it.
Thank you all very much! I am pretty busy these days so once I find some time I will do more research and root it.
@simplepinoi177
I am not sure if your paypal address works, I felt like buying you a coffee earlier, the least I could do with all the time you spent explaining
Oh forgot to ask some minor things,
to make a nandroid backup, I just send twrp.img via fastboot to the phone and boot into it and make it? And if I want to revert back I do the same and restore it?
Also if TWRP asks me the question about if I want to enable modification to the system, what do I answer? Either for the nandroid backup, the restore or for flashing magisk.zip? Do any of those require that enabled?
Lastly, I understood that just unlocking the bootloader alone can result in no OTAs. But, will I keep getting the security updates? I heared something about security updates that are frequently available from the playstore or something like that but I have the phone for less than a week and haven't gotten anything. No OTAs mean no security updates as well? Or they are irrelevant and I will keep getting those security updates once rooted?
arismelachrinos said:
Oh forgot to ask some minor things,
to make a nandroid backup, I just send twrp.img via fastboot to the phone and boot into it and make it? And if I want to revert back I do the same and restore it?
Also if TWRP asks me the question about if I want to enable modification to the system, what do I answer? Either for the nandroid backup, the restore or for flashing magisk.zip? Do any of those require that enabled?
Lastly, I understood that just unlocking the bootloader alone can result in no OTAs. But, will I keep getting the security updates? I heared something about security updates that are frequently available from the playstore or something like that but I have the phone for less than a week and haven't gotten anything. No OTAs mean no security updates as well? Or they are irrelevant and I will keep getting those security updates once rooted?
Click to expand...
Click to collapse
So, about booting TWRP...
You can temporarily boot into TWRP just the one time if you wish. If you are using the newest version of TWRP (for the Pixel 2), they actually give an option to flash and replace the recovery with TWRP from within their recovery environment; I'm guessing they use the temporarily booted twrp.img to install. In any case, you can find the option in the Install section. In any case, it's up to you whether you install it as your custom recovery, but it's easy enough to restore it back to stock recovery either by manually flashing the stock boot.img (and maybe dtbo.img for good measure, as I'm unsure...) and/or if you update your device via a Full Factory (or even a downloaded OTA) image, as that will update and replace the boot partition regardless...
So, about the alert for enabling modification to the system; In the past, I had always enabled it. Of course you would want to have r/w and mounting capabilities towards the device's system and data partitions. But keep this in mind...until the TWRP team updates the latest version, there is no write capabilities/permissions. It will pull up an error that it either can't mount or doesn't write -- For this reason, I'm holding off so I don't have firsthand experience... -- but installing and flashing and backing up from within TWRP does work even if it spits up some errors. What you should be careful about is if/when it asks to install it as a "system service" or something, as general consensus says at no circumstance should you do this as it "forks" up many other things while at it.
But, to answer your question directly, I'm unsure whether you can or cannot install Magisk root or restoring without enabling this "modification" capability, but I say it can't hurt.....
As for your inquiries on OTAs, as I understand it (so anyone please correct me if I'm wrong), but the monthly security updates come with the OTAs (also monthly, so I believe they may be one in the same). I'm unsure about the whole seeing the security updates on the Play Store or something like that, but I highly doubt that is the case. Conventional knowledge says that you can only get these either from the stock System Updater or if you download them yourself and either sideload or "flash-all" it. That's why many (most) experts will download the Full Factory image every month (usually first Monday of the month) and we have this whole step-by-step process in updating platform-tools, unregistering Magisk modules and screenlocks/fingerprints, running the flash-all, temporarily booting TWRP, installing all custom modifications (Magisk last), rebooting after each and every flash/install, then going back into the OS and resetting up the screenlock/fingerprints and Magisk modules. As it would be nice if we could simply and always use the stock System Updater, but in any case, one would need to re-install all the custom modifications anyways. So, it is one of the sacrifices/compromises having a rooted Pixel 2….
But it is peculiar that you haven’t gotten any alert (unless you inadvertently updated to the latest already), for it still should alert you that there is an update available, and usually, if you have unlocked your bootloader, while it’s downloading and attempting to install, it will throw up an error; but everything would look like normal up to that point. But, then again, Google notifying updates on their various devices are intermittent at best. It would be simpler and best if you just keep it in mind that there’s usually the monthly update on/after the first Monday of the month and do what we all do and have to manually install the updates to keep most up to date.
If there’s anything else, you know you can ask…
Good luck and hope this helps…!
I'm on 10 with an unlocked bootloader, 1st gen Pixel. I still get security updates. Twrp doesn't mount /system or /vendor, so I take system/vendor IMAGE backups with no issue. Not sure if I'll get updates still after unrooting. I've always flashed factory after rooting. Theoretically it should return to stock if you flash the Magisk uninstaller. The boot image (boot + recovery + base system) will be restored. You should then be able to get OTA updates. They will be installed to the OTHER slot, so if the phone fails to boot (3 times?) it will switch back to the first slot. If you have issues and want to go back, you can manually switch slots in fastboot or go into twrp, tap reboot, tap the other slot, then reboot system. It will show a message that the slot has changed. You can of course always check the active slot in fastboot to make sure. If you want to roll back an OTA update, reboot to twrp, change the active slot, then reboot system, and it should boot to the older version. Make sure to turn off automatic updates or else it will redownload the same update again. I believe I've lost twrp by installing an OTA update, which installs to the inactive slot, which overwrites recovery, and then boots to that slot. Meaning if you don't have a pc to switch slots in fastboot, you can't go back to the first slot which still has twrp. The command is fastboot set_active, something like that. Quick google search.. No pc means no restore if something goes wrong while you're away from a computer. The only way I know of to change slots at that point is to hard reset 3 times, which will trigger the phone to switch slots. ALWAYS reboot after flashing bootloader/radio. I'm decently sure that the bootloader has to match the system, so if you install lineage Pie, you need to flash the bootloader/radio from Pie or the phone won't boot. Flash bootloader, reboot, flash radio, reboot, flash matching rom. It is technically possible to have dual boot, where one slot is lineage and the other is stock, as long as they're the same Android versions. Lineage Pie/stock Pie for example, because the bootloader won't match if you flash Lineage Oreo/stock Pie. Keep in mind OTAs will overwrite twrp with stock recovery, so if you reboot, you might lose access to twrp, and I don't know of a way to OTA and reboot on the same slot. I don't know if there is an app or command for this, WHICH WOULD BE REALLY FREAKING NICE. Also, when restoring boot from twrp, I always reflash twrp to make sure. It will install to both slots. You can keep a copy of twrp on your data partition. To reflash twrp from within twrp, Install > Select Image > find twrp.img > flash to RAMDISK. If you flash to boot, it will overwrite system, and leave you with only twrp. When installing in older twrp's, I believe it will install to the same slot. With newer twrp's that specifically support Treble, it will flash to the other slot. Don't quote me on that. Due to the single data partition, there's a chance Lineage will have issues with stock data. I've never seen it though. I've dirty flashed a couple times with few issues. I think I've even dirty flashed different OS versions. If you get app crashes, open that app's info, delete its storage/cache, and reopen the app. Most of the app data is the same across versions anyway. The Pixel is a complete pain in the ass when coming from non Treble phones. Sorry if this is repeated info, the posts above are LONG lol. Hope this helps.
Edit- not sure if relevant to you, but I get bootloops when flashing twrp to the ramdisk. There should be an option in twrp to fix it. I always do this after flashing twrp this way.
So I've read enough posts to get this first - GLOBAL ONLY I got my phone on Amazon its a global unlocked NOTE8PRO. Any of you with something else like China or India try this method and brick your phone don't cry to me over it. After trial and error, bricking my device and paying some guy in Spain 30EUR to unbrick it (thanks brother you rock) I thought I'd share my final experience and how you can get your GLOBAL RN8P to a stable place to install the ROMS available at this time. I will include at the end my thoughts on the 2 ROMS I installed and used over the past week. Honestly if you're on a global version I'm not sure it's worth it although as I type this I kinda want to flash Pixel Experience again, I really liked it. But more on that later. I compiled this guide from sources here, if I don't give you credit I apologize in advance please just let me know.
First let's make sure we don't brick this mofo.
Hit the MEGA thread if you haven't read it then you shouldn't be flashing your phone, and do this from a clean install of MIUI-V11.0.6.0PGGMIXM and do yourself a favor and get it from Xiaomi or a reliable source, not everyone on here has good intentions. There are some "official" ROMS out there that have been played with and will break your phone.
1. Do it how you want I did this from fastboot. Dump the official MIUI global ROM in a folder, and (I'm on linux box so adjust yourself if you're sadly using Windows) I executed this command from FASTBOOT in the MIUI ROM folder with ADB and FASTBOOT installed for my system.
./flash_all.sh (I think its flash_all.bat for Windows)
This going to wipe your stuff out, have it backed up. I'm dedicated to Google and GDRIVE I don't care I get everything back when I wipe including sms and phone records etc, but to each his own.
It's going to wipe and restore to factory image on that ROM version and you're going to go throught setup again, tedious (I say that having done it 4 times this week) but none the less it is what it is. After you are up and running on that ROM version keeping in mind if you're going to flash a new ROM like PE then don't set it up all the way because you're going to do it all over again anyways move to the next step.
2. From the MEGA thread flash this and reboot. Read the thread download the files and do what Agent_fabulous (awesome guy btw) says. Reboot. Make sure you can reboot to SYSTEM and all is well, don't worry about recovery or bootloader yet.
Code:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
3. OK kids we're almost there, now you need to install TWRP and there are MANY versions floating around. Honestly the official version sucks IMHO. go to this thread and download TWRP and do exactly what it says in the thread. Assuming you're device is unlocked already and if its not then come back later follow EXACTLY steps 2 and 3. From there you will update MAGISK after the reboot and be fully rooted and pass SaftyNet checks.
You are stable and rooted. All you do next is enjoy your rooted device and or install a custom ROM. If you do install a custom ROM - READ READ READ and FOLLOW directions I hate to add to the confusuion but there are so many threads on this phone (becasue it sucks to MOD it) and it's frustrating because all of it assumes you know everything or they just don't give you all the steps and you end up bricking your phone. I have never by the way rooted or flashed a phone in my life before this one.
At this time all the custom ROMS need to be flashed after flashing the Indian Vendor image, this is in fact the only way I know and it worked for me everytime. So at this point if you're flashing a new ROM first flash the India Vendor image then flash the new from all from TWRP. But in my experience just follow what it says because Agent_fabulous and friends may crack this tomorrow and it won't be the same. What I am giving you is a VERY stable platform to start flashing ROMS from or just to be rooted and happy. As an FYI from this you can install RIRU and EdXposed if you want to do that, I wasn't impressed other than dark mode in GMail on A9 and ad-blocking in YouTube, I get the ads in YouTube but Google no dark mode in GMail on A9? WTF??
Happy rooting and ROMing.
DC.
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
Given how aggressive the battery optimizer is on stock, I doubt you'll get more juice out of it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
It's fine to flash ROMs I felt PE was way faster the audio was better over Bluetooth and it was pretty stable. Battery improvement was negligible.
@dcindallas glad you had such a nice experience. have you tried flashing miui 12 on it? seems there are some beta versions for it. seems to bring a lot of eye candy, privacy and performance fixes. give it a go.
@dcindallas hi, can you please add a portion for updating miui rom through twrp (when new version available) the procedure. thanks.
I've not flashed anything but custom ROMS I had to wipe go back to A9 stock ROM due to Pixel Experience dropping wifi constantly.
Well, I appreciate all the effort going into this thread and this device. Thru all the reading I've done on this simple project with different advice, it almost seems there's too much info on it. Anyway, I'm having a dickens of a time with it, just getting it to load up TWRP! I thought I followed all the directions.. y'know... hold this button, dont hold this one, release this one, then repress that one... but I got a bootloop just from flashing TWRP. I had to re-flash the whole MIUI (an older one even) with Mi Flash, the only one I could find that had a flash-all script in it.
I'm a little gun shy, but I'd sure like to give it a go again.
I flashed twrp-3.3.1-0-begonia.img, then rebooted. Any advice why I bootlooped? Was it the TWRP version or did I mess up the button press?
Cheers
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!
I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.
In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.
For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.
nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.
harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.