I own a Shield TV 2017 (16GB) remote only (P2894, Darcy) which currently has Nvidia 7.1.0 developer OS, unlocked bootloader and the boot.img was patched using Magisk Manager 6.2.1/Magisk 18.0.
It has been noted patching boot.img using Magisk Manager 6.2.1/Magisk 18.0 only performs a partial root and that something else in the "DTB" information needs to be modified in order to allow full root access to read/write.
I'm new to this so please forgive me if I ask something obvious.
I've connected my Shield TV to my PC via ADB and executed
fastboot oem dtbname
...
(bootloader) tegra210-darcy-p2894-0050-a08-00.dtb
OKAY [ -0.000s]
finished. total time: -0.000s
I don't know how to extract the *.dtb information or know what's required to patch it.
The command to flash it is
fastboot flash DTB tegra210-darcy-p2894-0050-a08-00.dtb
Can someone else help provide what's required to extract, modify, etc... in order to flash and gain full root access?
Mogster2K said:
Zulu99 mentioned something similar - that dm-verity was enabled in darcy's DTB file, preventing any custom firmwares from executing. Foster does not seem to have this problem.
He's provided a patched DTB here - use at your own risk: http://bit.ly/2CxB1hS (WARNING! ONLY FOR 2017 DARCY MODEL!)
Original post here.
Click to expand...
Click to collapse
It's my understanding that this is required to allow TWRP 3.2.3.0 foster to work properly. If not can someone please clarify this for us beginner users?
NOTE: The patched DTB file above is not for the same version as the one I have.
nanerasingh said:
As my test on 2017 16gb 7.2.2 official TWRP patched the boot img i got root access but not fully write.
I used the DTB and flashed from fastboot and reboot without any reset -w command.
No issue of unresponsiveness and boots up normal.I tried edit build.prop in system via ES explorer and reboot the see the persistent and rw works.
So system dm-verity patch by DTB works.
Click to expand...
Click to collapse
Noting this too...
Thanks for the confirmation!
The fastboot -w should only be required if the forced cyption was already in use on the device.
But if I am not mistaken than on the developer version only the data prtition is encrypted, which is no issue.
nadia p. said:
It's my understanding that this is required to allow TWRP 3.2.3.0 foster to work properly. If not can someone please clarify this for us beginner users?
NOTE: The patched DTB file above is not for the same version as the one I have.
Click to expand...
Click to collapse
AFAIK the patched DTB is for booting custom ROMs. More work still needs to be done to get TWRP working again.
---------- Post added at 09:45 PM ---------- Previous post was at 09:42 PM ----------
nadia p. said:
I own a Shield TV 2017 (16GB) remote only (P2894, Darcy) which currently has Nvidia 7.1.0 developer OS, unlocked bootloader and the boot.img was patched using Magisk Manager 6.2.1/Magisk 18.0.
It has been noted patching boot.img using Magisk Manager 6.2.1/Magisk 18.0 only performs a partial root and that something else in the "DTB" information needs to be modified in order to allow full root access to read/write.
I'm new to this so please forgive me if I ask something obvious.
I've connected my Shield TV to my PC via ADB and executed
fastboot oem dtbname
...
(bootloader) tegra210-darcy-p2894-0050-a08-00.dtb
OKAY [ -0.000s]
finished. total time: -0.000s
I don't know how to extract the *.dtb information or know what's required to patch it.
The command to flash it is
fastboot flash DTB tegra210-darcy-p2894-0050-a08-00.dtb
Can someone else help provide what's required to extract, modify, etc... in order to flash and gain full root access?
Click to expand...
Click to collapse
Is root not working for you now? If you have never upgraded the stock ROM past 7.1, then it should work without needing a patched DTB.
Mogster2K said:
AFAIK the patched DTB is for booting custom ROMs. More work still needs to be done to get TWRP working again.
---------- Post added at 09:45 PM ---------- Previous post was at 09:42 PM ----------
Is root not working for you now? If you have never upgraded the stock ROM past 7.1, then it should work without needing a patched DTB.
Click to expand...
Click to collapse
I'm quite the beginner at all of this Android stuff, although I have experience with several other software related things. I'm currently stuck trying to install TWRP 3.2.3.0 foster on my Shield TV 2017 (16GB, remote only + usb keyboard + usb mouse). I haven't been able to backup the entire device yet to use that to see if I can restore everything back to that exact state yet. I don't know how to tell how "rooted" I really am yet.
Steel01 says TWRP 3.2.3.0 fosters is working on Darcy. I'm still trying to confirm this. My main reason for TWRP is to complete a full backup which I can later restore back to that exact state if/when something should happen if accidentally updated and it breaks everything again.
nadia p. said:
I'm quite the beginner at all of this Android stuff, although I have experience with several other software related things. I'm currently stuck trying to install TWRP 3.2.3.0 foster on my Shield TV 2017 (16GB, remote only + usb keyboard + usb mouse). I haven't been able to backup the entire device yet to use that to see if I can restore everything back to that exact state yet. I don't know how to tell how "rooted" I really am yet.
Steel01 says TWRP 3.2.3.0 fosters is working on Darcy. I'm still trying to confirm this. My main reason for TWRP is to complete a full backup which I can later restore back to that exact state if/when something should happen if accidentally updated and it breaks everything again.
Click to expand...
Click to collapse
TWRP works for darcy IF AND ONLY IF it has never been upgraded to stock rom 7.2 or higher. 7.2 majorly broke a lot of things, including TWRP, which is why this thread has so much traffic lately and I why asked whether you had upgraded past 7.1. Please confirm whether you have or not.
Mogster2K said:
TWRP works for darcy IF AND ONLY IF it has never been upgraded to stock rom 7.2 or higher. 7.2 majorly broke a lot of things, including TWRP, which is why this thread has so much traffic lately and I why asked whether you had upgraded past 7.1. Please confirm whether you have or not.
Click to expand...
Click to collapse
Hello Mogster2K, Originally without any modifications the factory installed Nvidia software upgraded itself through on-line updates to 7.2.1 which then broke other 3rd party Apps for me. I then attempted to downgrade to 6.3.0 developer OS, however because it was my first time unlocking the bootloader it wiped everything so once it 6.3.0 was successfully flashed, I had to connect to the internet, sign-in again to Google Play and meanwhile it forced itself to update back to 7.2.1 again. Later by following ACiDxCHRiST's guide HERE, I was able to successfully downgrade to 7.1.0 developer by patching the 7.1.0 boot.img then manually flashed each line item in flash-all.bat.
Later I tried to install TWRP 3.2.3.0 so I could backup the device, however I've not been successful with that since I have a Shield TV 2017 (16GB) remote only model so I must use a USB keyboard and USB mouse to do it. I was reading these other posts here about what the issues might be preventing me from installing TWRP and using it to back everything up. Does this help answer your question?
So I'm currently on 7.1.0 developer OS, patched boot.img using Magisk Manager 6.2.1/Magisk 18.0. So far the Apps that were broken by 7.2.0 "factory" are again working fine in 7.1.0. I don't game, I mainly watch movies and tv series with my device so I don't have many requirements other than I'd like to back everything up so in case it accidentally gets updated somehow I can revert back to a working archive and continue from there.
Mogster2K said:
TWRP works for darcy IF AND ONLY IF it has never been upgraded to stock rom 7.2 or higher.
Click to expand...
Click to collapse
I realized I wasn't sure if by upgrading the "stock" rom this included updating the device to 7.2.0 (or later) via on-line updates or just flashing the rom itself to 7.2.0 (or later).
Does anyone know how to test for certain criteria to help determine if:
A) anything needs to be modified in regards to DTB
B) if their device has been updated in such a way that it currently breaks TWRP (or other things) in such a way there is no fix as of today
This should prove quite useful to help us understand if/anything needs to be done or where the device resides at any given moment.
nadia p. said:
I realized I wasn't sure if by upgrading the "stock" rom this included updating the device to 7.2.0 (or later) via on-line updates or just flashing the rom itself to 7.2.0 (or later).
Click to expand...
Click to collapse
Both. Anyway, I did not realize at the time that darcy could be fully downgraded to 7.1, sorry. It doesn't work on my foster, so I can't use TWRP at all. Also, to the best of my knowledge, TWRP requires at least a USB mouse to function regardless of which ShieldTV model you have. And the modified DTB is just for booting modified images on darcy 7.2+. You're fine without it on 7.1.
Stuck... post backup TWRP 3.2.3.0, now corrupt w/black screen
I'm not sure if this had anything to do with it but I'm suck at a black screen after backing up TWRP.
More information can be found at this POST.
Already this 7.2 update is creating topics all over the place
Anyway, let me try to at least some light on things.
My latest findings:
1. The bootloader does not downgrade to 7.1 once you had at least the 7.2.x installed, not sure about 7.2 as it is too late for me to test this.
I did not check with the 6.3 either but maybe someone who did is able to state what bootloader is working then.
2. The DTB is not included in the firmware images at all but it seems it was included in some pre 7.1 to include the "updates" for the Darcy models.
What makes the Zulu one tick is the simple fact that it is patched to disable DM-Verity completely.
Hence the requirement for the fastboot -w or a factory reset.
TWRP and such....
This might get quite long, so anyone without half decent knowledge about rooting, firmwares and recoveries can just skip it
First thing I learned from 7.2 was: Do not mess with your bootloader!!!
Second thing I learned is that Linus was right with his statement about NVidia and their open source suppport.
So what actually changed?
For starters the NVidia statement of the developer firmware being rootable is not true the same way it was before.
Google latest kernel fixes and changes have been implemented - look it up yourself please to spare me thausand of lines of typing!
In short it means that all backdoors or such that Magisk or SU have used are unavailabe now.
Rooting still works but with the limit of write access.
And that is the important factor one for TWRP, the second is "routing".
Let me try to word it as simple as I can...
We can not modify the system to ignore the stock recovery or related security features.
We can not write to required areas of the system required to boot into TWRP through the recovery.
If you somehow manage to get into TWRP, like when I still had a working mod, there again is no write access to system available and the internal memory will be corrupted if you write a backup.
The DTB Zulu provided gives us system wide write rights again by disabling DM-Verity but this only goes for the system!!
The recovery does not use the DTB in this way.
Best thing you end up with is a dark screen where ADB seems to be working.
It actually works with full root access for me in several cases LOL
So if that really is TWRP then why can't we see it?
My TV is great as it allows multi input formats.
So a 1080P signal will be accepted as such.
And every time this screen format changes I see a little pop up with the new resolutions on the screen.
Since 7.2 this popup no longer shows up....
TWRP might actually be there and working but we can not see or use it.
The strange thing however is that at least on the 7.2.2 I had the strange problem that just trying to boot into tWRP through fastboot resulted in a corrupt system.
The bootloader realises the recovery written into the temp area has no NVidia signature or hash code to match.
This means for the bootloader a possible attack on the system happened and it is "secured", resulting in a soft brick.
My plans to fix all this crap for good:
The DTB is a partial solution at best as we
a) don't really know how compatible it is with future updates.
b) we still fail to properly use TWRP again.
All up a total nighmare for any modder or person with a lot of data and apps to backup and restore.
My first attempt was to build the 7.2 from the sources, thinking at least here the NVidia statements are correct that their installer takes care of everything.
Lol! It did take of about 120GB in downloads but did not give me any of require software suites actually required to even load a build tree.
Would need far more time than I have to mae complete and work with registrations, accounts and all this.
So I decided to go back to my roots before Magisk was a thing.
Dissecting the firmware, disabling all new "safety" features and not required encryptions and hash checks.
That bit I think I finnished to my satisfaction.
On the packing to make it work to be installed under 7.2.X I am still working.
Biggest drawback for me is that I lost TWRP and that the TWRP builder does not even let me log in on my Shield.
So even if a more offical way or porting or building could be a way out I can not access it.
Means I can neither try to install my modded firmware nor test it.
So if anyone reading here has a confirmed way to downgrade to something that brings TWRP back to live with working write access and working backup functions:
Don't be shy, we don''t bite (much)!
Share your way, give us the links and if my magic still works a bit this nightmare shall soon be over for good
7.2 sources still have not been released yet, anyway. I found a reference to a new branch "rel-30-r2-partner-o" but that's all.
Downunder35m said:
Already this 7.2 update is creating topics all over the place
Anyway, let me try to at least some light on things.
My latest findings:
1. The bootloader does not downgrade to 7.1 once you had at least the 7.2.x installed, not sure about 7.2 as it is too late for me to test this.
I did not check with the 6.3 either but maybe someone who did is able to state what bootloader is working then.
2. The DTB is not included in the firmware images at all but it seems it was included in some pre 7.1 to include the "updates" for the Darcy models.
What makes the Zulu one tick is the simple fact that it is patched to disable DM-Verity completely.
Hence the requirement for the fastboot -w or a factory reset.
TWRP and such....
This might get quite long, so anyone without half decent knowledge about rooting, firmwares and recoveries can just skip it
First thing I learned from 7.2 was: Do not mess with your bootloader!!!
Second thing I learned is that Linus was right with his statement about NVidia and their open source suppport.
So what actually changed?
For starters the NVidia statement of the developer firmware being rootable is not true the same way it was before.
Google latest kernel fixes and changes have been implemented - look it up yourself please to spare me thausand of lines of typing!
In short it means that all backdoors or such that Magisk or SU have used are unavailabe now.
Rooting still works but with the limit of write access.
And that is the important factor one for TWRP, the second is "routing".
Let me try to word it as simple as I can...
We can not modify the system to ignore the stock recovery or related security features.
We can not write to required areas of the system required to boot into TWRP through the recovery.
If you somehow manage to get into TWRP, like when I still had a working mod, there again is no write access to system available and the internal memory will be corrupted if you write a backup.
The DTB Zulu provided gives us system wide write rights again by disabling DM-Verity but this only goes for the system!!
The recovery does not use the DTB in this way.
Best thing you end up with is a dark screen where ADB seems to be working.
It actually works with full root access for me in several cases LOL
So if that really is TWRP then why can't we see it?
My TV is great as it allows multi input formats.
So a 1080P signal will be accepted as such.
And every time this screen format changes I see a little pop up with the new resolutions on the screen.
Since 7.2 this popup no longer shows up....
TWRP might actually be there and working but we can not see or use it.
The strange thing however is that at least on the 7.2.2 I had the strange problem that just trying to boot into tWRP through fastboot resulted in a corrupt system.
The bootloader realises the recovery written into the temp area has no NVidia signature or hash code to match.
This means for the bootloader a possible attack on the system happened and it is "secured", resulting in a soft brick.
My plans to fix all this crap for good:
The DTB is a partial solution at best as we
a) don't really know how compatible it is with future updates.
b) we still fail to properly use TWRP again.
All up a total nighmare for any modder or person with a lot of data and apps to backup and restore.
My first attempt was to build the 7.2 from the sources, thinking at least here the NVidia statements are correct that their installer takes care of everything.
Lol! It did take of about 120GB in downloads but did not give me any of require software suites actually required to even load a build tree.
Would need far more time than I have to mae complete and work with registrations, accounts and all this.
So I decided to go back to my roots before Magisk was a thing.
Dissecting the firmware, disabling all new "safety" features and not required encryptions and hash checks.
That bit I think I finnished to my satisfaction.
On the packing to make it work to be installed under 7.2.X I am still working.
Biggest drawback for me is that I lost TWRP and that the TWRP builder does not even let me log in on my Shield.
So even if a more offical way or porting or building could be a way out I can not access it.
Means I can neither try to install my modded firmware nor test it.
So if anyone reading here has a confirmed way to downgrade to something that brings TWRP back to live with working write access and working backup functions:
Don't be shy, we don''t bite (much)!
Share your way, give us the links and if my magic still works a bit this nightmare shall soon be over for good
Click to expand...
Click to collapse
First of all thank you so much for putting all this in layman's terms so someone like me can understand it. Total respect!
Since my device is useless if there is some way I can offer you remote access to a PC, the device and anything else I can assist you with please don't hesitate to let me know.
If you need me to send you my device with remote that you can use to complete these things and get everyone unstuck from this dreadful situation I'm all for that too.
I wish there were a means, like with computers, that we can purchase a band new device, fully back it up before even connecting it to the internet and being forced to sign-in to Google Play before we even have access to the device. We'd also need a way to wipe, format and reinstall this backup without any issues. Is this too much to ask for in an Android world?
EDIT: I have time, access to certain hardware PCs, Macs and Linux, and have some basic skills with computers, phones, etc... If I can assist you or anyone with certain time consuming things let me know. The only Android device I currently own now is the Shield TV.
Would it Work to just flash the system/vendor files without updating the Bootloader?
nadia p. said:
Since my device is useless if there is some way I can offer you remote access to a PC, the device and anything else I can assist you with please don't hesitate to let me know.
Click to expand...
Click to collapse
Sorry, I've lost track of your particular situation. Are you unable to reflash Stock 7.2 or 7.2.1? I realize it's hardly ideal, but it would at least make the ShieldTV usable.
From what I understand the dtb file is in the blob file, so simply flashing back a blob file would put back the stock dtb file. The only issue with flashing blob files is if you tried flashing back a Nougat blob file if you were already on a Oreo Firmware, as long as you only try flashing a Oreo Firmware blob file you shouldn't run into any problems, I would have to go back and have a read, but I'm sure I read that you may have done this and if you had tried to flash a Nougat blob file when you were already on an Oreo Firmware, that could be where you first ran into problems. But I'm not too sure if you are asking where to get the modified dtb file or not, I'm not sure if you have already flashed the modified dtb file or you are asking where to get the modified dtb file. I checked the dtb version on my 2017 Darcy Shield and it came up with a different number version than yours, mine came back with: tegra210-darcy-p2894-0050-a04-00.dtb whereas you have posted you have the tegra210-darcy-p2894-0050-a08-00.dtb. I done the check on what version of the dtb I had before and after using the modified dtb and also after when I flashed back a Oreo blob file and back to a Full Stock Oreo firmware and they both came back as the a04 version.
I would try and flash back to the latest Stock 7.2.1 image released on Nvidia's site: https://developer.nvidia.com/gameworksdownload
If successful then I would look at downgrading back to 7.1 Stock Firmware. I'm still a bit confused if this is what you have done or you only have a black screen when trying to boot to system?
The Fifth and Sixth version on the downloads screen are the versions for the 2017 model, one being the Developer version and the one below being the Stock version of 7.2.1. I would try flashing the Stock Version first and see if that gets you back up and running again. If it does, I would again check the dtb version as I am sure the 2017 Darcy model should be showing the a04 version and not a08.
---------- Post added at 01:06 PM ---------- Previous post was at 12:55 PM ----------
I just had a quick read back, you have said you have flashed the Developer image and then also flashed a patched boot.img. I have not done this combo as it is not the way I would do things. I would use just the Stock Firmware and not the Developer image with a patched boot.img. I do not know 100% for sure if the only difference between the Developer version and the stock version is the boot.img but if you are going to use a patched boot.img anyway, this is the reason why I say there is no need to flash the Developer version as you are going to use a Patched boot.img anyway, I would just stick with the Stock version.
Mogster2K said:
Sorry, I've lost track of your particular situation. Are you unable to reflash Stock 7.2 or 7.2.1? I realize it's hardly ideal, but it would at least make the ShieldTV usable.
Click to expand...
Click to collapse
Hello Mogster2K, from the factory install which was updated OTA to 7.2.1 I was able to 1st unlock the bootloader and flash 6.3.0 developer OS to my device successfully, or so I thought so. What I mean by this is based on what Downunder35m said once the device has been updated to 7.2.0 regardless of how when flashing previous versions of OS (developer or recovery) it may not revert the bootloader to 6.3.0. This we still have to see and test to confirm, unfortunately he nor I have any way to test things right now. That being said because I unlocked the bootloader (forced wipe) then flashed 6.3.0 that all went fine accept when booting to the Nvidia home screen it required me to connect to the internet and then sign-in to Google Play. Doing this the OS forces it to update itself again back to 7.2.1 (at that time).
So now that the previous steps were useless I then discovered ACiDxCHRiST's guide HERE and followed that since the bootloader was already unlocked I could modify the boot.img form 7.1.0 then flash that. Well two things happened, it worked perfectly however it's most likely Magisk didn't truly root the device 100%, it only rooted it partially. So now the device worked fine on 7.1.0 and everything was going well UNTIL I decided to install TWRP and backup my device. Doing so totally screwed it, now I have a black screen.... Read THIS.
So one of the reasons I started this thread was to find out more about DTB and how do we start to first test a devices current state, perhaps patch it to what we need to recover from the 7.2.0 changes and restrictions. The benefit of all of this is we should be able, with expertise, be able to climb our way out of this hole and get back to a working device.
whiteak said:
From what I understand the dtb file is in the blob file, so simply flashing back a blob file would put back the stock dtb file. The only issue with flashing blob files is if you tried flashing back a Nougat blob file if you were already on a Oreo Firmware, as long as you only try flashing a Oreo Firmware blob file you shouldn't run into any problems, I would have to go back and have a read, but I'm sure I read that you may have done this and if you had tried to flash a Nougat blob file when you were already on an Oreo Firmware, that could be where you first ran into problems. But I'm not too sure if you are asking where to get the modified dtb file or not, I'm not sure if you have already flashed the modified dtb file or you are asking where to get the modified dtb file. I checked the dtb version on my 2017 Darcy Shield and it came up with a different number version than yours, mine came back with: tegra210-darcy-p2894-0050-a04-00.dtb whereas you have posted you have the tegra210-darcy-p2894-0050-a08-00.dtb. I done the check on what version of the dtb I had before and after using the modified dtb and also after when I flashed back a Oreo blob file and back to a Full Stock Oreo firmware and they both came back as the a04 version.
I would try and flash back to the latest Stock 7.2.1 image released on Nvidia's site: https://developer.nvidia.com/gameworksdownload
If successful then I would look at downgrading back to 7.1 Stock Firmware. I'm still a bit confused if this is what you have done or you only have a black screen when trying to boot to system?
The Fifth and Sixth version on the downloads screen are the versions for the 2017 model, one being the Developer version and the one below being the Stock version of 7.2.1. I would try flashing the Stock Version first and see if that gets you back up and running again. If it does, I would again check the dtb version as I am sure the 2017 Darcy model should be showing the a04 version and not a08.
---------- Post added at 01:06 PM ---------- Previous post was at 12:55 PM ----------
I just had a quick read back, you have said you have flashed the Developer image and then also flashed a patched boot.img. I have not done this combo as it is not the way I would do things. I would use just the Stock Firmware and not the Developer image with a patched boot.img. I do not know 100% for sure if the only difference between the Developer version and the stock version is the boot.img but if you are going to use a patched boot.img anyway, this is the reason why I say there is no need to flash the Developer version as you are going to use a Patched boot.img anyway, I would just stick with the Stock version.
Click to expand...
Click to collapse
In short the 7.2.1 update broke the factory install by affecting other apps I use and that were working perfectly fine in 7.1.0 before the update occurred. This was the sole reason I attempted to revert back to a previous OS.
Just flashing 6.3.0 didn't work as it updated itself back to 7.2.1 forcibly. I then had to work around that issue and the only way I found was to download 7.1.0, patch it's boot.img file, flash 7.1.0 developer to keep the bootloader uplocked so it wouldn't wipe the system whereby deleting the user info, apps, etc..., make sense? The only issue is that Magisk didn't fully root the device properly and with the new OS verification added to 7.2.0 it created all sorts of other protections where we're not able to fully wipe everything and flash back normally. These protections kick in and prevent it. This is why we're trying to see how to undo the protection settings so we can actually do what we need to do. DTB is part of this.
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.
I am grateful and I bought this because next tk Samsung s22 yktra this phone is definitely #2 in my opinion, which is saying a lot.
However the root process is tedious because I am not around a computer I am just lazy to get ito do flashing etc.
My question is, why do. We not have a a real recovery and ability to back up and restore various roms we or flash zips senselessly.
So my question is (since I just bought this) do you guys rhibj we will have to dastboir flash everything or at least much harder then with cwmod or twrp recovery. Is it not possible to have a recovery like those on t his phone?
Is there a better phone in the us that is unlockaable but has the quality like this phone and screen or the Samsung s22 yktra phone?
Thanks
Without a PC you can't run fastboot commands to unlock bootloader and root it. Twrp isn't available for stock a12, let alone the upcoming release of a13
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
I don't think that you will find too many phones from the primary companies (Google, Samsung, etc) nowadays that will have TWRP builds. As time progresses, the technology (and what is available) progresses as well.
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
This is the most recent news about Android 12 compatibility for TWRP:
TWRP 3.6.2 Released
TWRP 3.6.2 is out now for most currently supported devices.
twrp.me
We are continuing work on Android 12. There is no ETA currently. You can follow our status on Zulip
Click to expand...
Click to collapse
Disclaimer: I am not advocating signing up for "Zulip", and I won't be doing so myself. When/if TWRP for Android 12 becomes available, I'll hear about it whether I sign up on there or not. It's also likely Android 13 will be stable by then.
Supposedly, the Official TWRP App (not itself updated since 2020) will notify when there's a new version - but I don't know if that applies to when there's no current version of TWRP Recovery already installed.
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
96carboard said:
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
Click to expand...
Click to collapse
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have
Pixel devices do not have a recovery partition; recovery lives in /boot with the kernel, as well as whatever patches you've applied. Currently, TWRP and Magisk cannot coincide for whatever reason. You can patch a boot image with TWRP, and it'll work AFAIK....but if you try to patch it with Magisk too, you'll get a boot loop.
Because we have full fastboot access, there's not really any need for TWRP. You can dump and backup partition contents using fastboot, but it's tedious.
jgrimberg1979 said:
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have.
Click to expand...
Click to collapse
ADP, Nexus, and Pixel devices have NEVER needed a recovery to function fully. This goes right back to the first Android phone in 2008. So nothing really has changed in this respect. Its mostly the "other" brands that need a recovery to work around various restrictions.
Backups can be taken from within the main OS, and restored similarly, and this is actually much preferred since the backup can be stored to a remote location such as a self-hosted Nextcloud server. You can look into seedvault (integrated solution) and neobackup (root solution).
Since Android 11 you cannot have TWRP and Magisk installed at the same time or it will lead to a bootloop. However, you can fastboot boot TWRP (without installing it) and have Magisk installed without getting into a bootloop. At least this is the way it was on Android 11 with the Pixel 2 XL.
Haven't used TWRP in a long time and don't miss it at all, to be honest.