Hey guys and gals, I'm new to the pixel and new to unlockable phones. I've always used AT&T brand phones with locked bootloaders so that being said I've never used Magisk or TWRP, although i used SafeStrap back on my S5 which is sortof like TWRP. I've rooted every device that I've had and installed SuperSu, roms etc but what I'm wondering is what is the difference in Magisk and SuperSu, which one is better in your opinion. I've read about making sure I'm on the latest image before doing certain things like installing roms and i believe TWRP, when yall say image, is that just saying the latest firmware. Sorry for my ignorance but I've always ran samsung phones. I just ordered my pixel 2 through Google so it's not carrier branded or locked down, it'll be away my house Friday so I'm just trying to do a little homework before it gets here so i can hit the ground running.
Thanks in advance
Magisk vs. SuperSU: Use Magisk as SuperSU was just announced as EOL.
Meaning of "image": In the context of "be on the latest image" it refers to the Factory Images (firmware) available from google. It's seems to be best to always flash the Factory Image (as opposed to an OTA image). If you must retain your data then you can edit the flash-all.bat (or flash-all.sh) file to remove the "-w" flag towards the end to keep the batch file from wiping data.
If you're new to pixel phones then you should beware of A/B partitions and their effect on the order of flashing/booting partitions. Also, know that the recovery is tucked inside of the boot image so flashing new ROMs will wipe out your TWRP installation so you can either reflash TWRP every time or get in the habit of just"fastboot boot"ing TWRP every time you need it. Last, be sure to update your fastboot/adb files regularly as several Pixel OS updates in the last 2 years have required the absolutely newest fastboot. Google now makes them available as a standalone direct download which is far more convenient than installing Android Studio if you only need the fastboot/adb files.
cntryby429 said:
Magisk vs. SuperSU: Use Magisk as SuperSU was just announced as EOL.
Meaning of "image": In the context of "be on the latest image" it refers to the Factory Images (firmware) available from google. It's seems to be best to always flash the Factory Image (as opposed to an OTA image). If you must retain your data then you can edit the flash-all.bat (or flash-all.sh) file to remove the "-w" flag towards the end to keep the batch file from wiping data.
If you're new to pixel phones then you should beware of A/B partitions and their effect on the order of flashing/booting partitions. Also, know that the recovery is tucked inside of the boot image so flashing new ROMs will wipe out your TWRP installation so you can either reflash TWRP every time or get in the habit of just"fastboot boot"ing TWRP every time you need it. Last, be sure to update your fastboot/adb files regularly as several Pixel OS updates in the last 2 years have required the absolutely newest fastboot. Google now makes them available as a standalone direct download which is far more convenient than installing Android Studio if you only need the fastboot/adb files.
Click to expand...
Click to collapse
Thanks for the info. I'll keep reading up on it all. The A/B partitons sounds like two different slots that you can boot from, is that correct. Like having stock backup on partition A and a rom on partition B. It i could be wrong all together. Lol. Anyhow thanks for the info. Can't wait to get it and play with it. It'll be my backup phone since whe I'm working AT&T don't pick up service i bought the pixel so i can put a prepaid sim in it to run on Verizon network.
FilthyFord said:
Thanks for the info. I'll keep reading up on it all. The A/B partitons sounds like two different slots that you can boot from, is that correct. Like having stock backup on partition A and a rom on partition B. It i could be wrong all together. Lol. Anyhow thanks for the info. Can't wait to get it and play with it. It'll be my backup phone since whe I'm working AT&T don't pick up service i bought the pixel so i can put a prepaid sim in it to run on Verizon network.
Click to expand...
Click to collapse
The A/B partition system was designed for seamless OTAs. Your device functions as usual, while the inactive slot updates. Once you reboot after an OTA, the slot changes to the updated slot, whether it be A or B, as if nothing happened. I know that you can switch between the two, but I don't believe that you can choose to occupy either of them with a custom ROM or a backup. Just follow the guide about updating to the latest Google software and you'll be golden.
DuckRuckus said:
The A/B partition system was designed for seamless OTAs. Your device functions as usual, while the inactive slot updates. Once you reboot after an OTA, the slot changes to the updated slot, whether it be A or B, as if nothing happened. I know that you can switch between the two, but I don't believe that you can choose to occupy either of them with a custom ROM or a backup. Just follow the guide about updating to the latest Google software and you'll be golden.
Click to expand...
Click to collapse
Thank you for clearing that up for me.
Sorry for the noob question, but not understanding whether a TWRP backup is attached to a particular device with a particular ID, or if it can be used to restore two identical devices.
So let's say you buy two of the exact same model phones, unlock bootloader and root both the same way.
After setting up phone #1, you do a TWRP backup.
Can that backup be used to set up phone #2?
I've done it many times with the HTC One M8, HTC 10, and Motorola Z2 Force. The first two devices weren't A/B partitioned like the Z2 Force though. Bricked and went through 3 Z2 Force's during the process, but I have restored multiple TWRP backups on different (but same) devices.
I am entirely sure if it works, but I suspect so
TWRP however does not offer to save all partitions for me, you might have to manually flash the stock rom images first to make sure things like bootloader modem etc. match in both slots on both phones
It may only cause problems if the backup you trynna restore is older than the already installed OS on the second device.
Thanks guys.
From what I'm understanding, if the same OS is installed the same way, there's a decent chance of success.
Good to know in case there's a chance to buy the same phone at a giveaway price.
Can please some good developer manage to provide something like that custom twrp with dual boot or any other alternative way?
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Slim K said:
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Click to expand...
Click to collapse
Your device already rooted right? How long u wait to unlock bootloader?
Kuma_Chaser said:
Your device already rooted right? How long u wait to unlock bootloader?
Click to expand...
Click to collapse
You have to wait 604,800 seconds. Same for everyone
A possible solution could be to create a new dynamic partition and flash your custom OS onto it.
people on xda working on that for other fons already here (TWRP), here (TWRP) and here (orangefox). would be great to have that for poco x3 nfc too
Slim K said:
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Click to expand...
Click to collapse
drahtwurst said:
people on xda working on that for other fons already here (TWRP), here (TWRP) and here (orangefox). would be great to have that for poco x3 nfc too
Click to expand...
Click to collapse
Did you check those posts and above comment? They all do use A/B partitions the x3 does not have. And imo a true non buggy/ deep hack multi boot solution without partition support is yet to find.
i was showing links i found for anyone interested and hopefully//partially//capable in developing a solution. it is clear, the poco does not have a/b patition scheme. are you mad i did not provide a solution?
drahtwurst said:
i was showing links i found for anyone interested and hopefully//partially//capable in developing a solution. it is clear, the poco does not have a/b patition scheme. are you mad i did not provide a solution?
Click to expand...
Click to collapse
Why should I be mad? I am not interested in dual boot. I am just telling you, that it wont be of any help as all 3 links point to OnePlus devices (2 also to already linked OP7) where TWRP/OF does make use of A/B partitioning. It doesnt mather how many twrp dual boot links you post if you can clearly see that they use s.t. which the x3 nfc does not have.
To make that more clear here mi a2 A/B do you think it will help? No. Several old methods of dual booting, one thing more buggy than the other https://www.xda-developers.com/dual-boot-on-android-a-power-users-holy-grail/ and lets not forget https://forum.xda-developers.com/t/app-boot-manager-pro-dual-boot-unlimited-roms-wip.1617055/ ... all useless (never stable or for A10+ anyway). There was this rel good working method for Sony Dev. loading up in early in modified kernel but yeah device specific, limited kernel & Co. .... Had no future. Except A/B partitioning there is simply nothing that works (good and/or modern devices).
you have clearly more oversight. i just guessed A/B partitioning can be done somehow. maybe dual boot is not even the best solution for what i am looking for. it used to be for me some years ago.
still searching for best solution to use banking+navigation but avoid gaugle + tracking as much as possible. keeping data with myself using FOSS apps+nextcloud is what i started with recently. OT.
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use this guide to install any GSI as the process should work the same. You can find various projects in Treble-Enabled Device Development.
WARNING: These instructions are intended ONLY for those who are familiar with Android, partitions, Odin, TWRP, ADB tools, etc. If you are a beginner/novice, GO NO FURTHER. I am NOT a developer, and I will NOT provide support. All software linked herein is provided AS IS. If you screw something up with your phone because you're trying to do something you know nothing about, I won't help you fix it.
To check whether you can run a GSI on your device, you can either use Termux or adb shell:
getprop ro.treble.enabled
If this returns TRUE, your device is Treble enabled and can run GSIs.
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
Disconnect USB/power cables and turn your device OFF
Hold both Volume buttons (do not press Power) and plug in the USB cord connected to your PC
The download/unlock screen should come up immediately. Select the option for device unlock mode.
Disable Knox Guard
After unlocking your bootloader, boot your device normally. Skip through setup, but make sure you connect to the Internet.
Enable Developer options again; OEM Unlocking will likely not be visible. To fix this, initiate a check for a firmware update. Do not download the update.
Go back to Developer Options and confirm that OEM Unlocking is visible; it should be grayed out with the message "Bootloader is already unlocked". If you do NOT see OEM Unlocking, do not attempt to flash any custom firmware.
Put your device in Download Mode. Look for a line that says "KG STATUS" - CHECKING or COMPLETE are OK. If this says LOCKED or PRENORMAL, do not attempt to flash custom firmware and go back to step 1 of this section.
Flash TWRP
Download TWRP for your device. You need the file that ends in .tar.
Put your device in download mode and connect to your PC.
Using Odin, flash the TWRP image in the AP slot. Make sure you either uncheck Auto Reboot in the Options tab, or be ready to force recovery mode when the device reboots. If you allow the OEM firmware to boot after flashing TWRP, it will automatically install the OEM recovery.
Install Multidisabler
Download Multidisabler, transfer it to your device, and flash in TWRP. Among other things, this will disable the recovery restoration, although since you won't be using the OEM firmware this doesn't matter.
Format /data.
Install GSI
Download the Android Preview GSI from Google
These builds are similar to what Pixel devices are running, although they lag behind in updates, and the GMS flavor includes Google Apps. If you want the pure AOSP source, check out Android Continuous Integration for the "master" builds.
If you prefer, you can install the vanilla version, and flash the GApps package of your choice. I highly recommend LiteGapps or NikGapps
Extract system.img from the above archive and transfer to your device
Wipe /system in TWRP. Do not wipe /boot as this will erase your kernel!
Install GSI in TWRP: Install > Install Image > Select GSI image > Select /system and flash.
Important: If you need to flash a GApps package, do this immediately after installing the GSI. You may need to resize /system if you get an error.
Root/Pass Play Integrity
If you want root, just flash Magisk in TWRP. No need to rename it to .zip. If you choose not to root, be aware that the device will not pass Play Integrity, so many banking/DRM apps will not work.
If you do want to be able to use banking/DRM apps, root with Magisk and install the Universal SafetyNet Fix Displax mod to pass BASIC_INTEGRITY and DEVICE_INTEGRITY attestation.
Notes:
If your device does not have TWRP available, you can try patching your own recovery to enable fastbootd; this will allow you to flash partitions directly from a fastboot command line.
If you're feeling really brave, you can try running a Generic Kernel Image, which you'd flash to /boot. This may not boot properly.
Thanks for the tutorial
I have a Galaxy Note 9 (snapdragon) and Galaxy Tab S8+, wich doesn't have (almost) any roms.
Do you think Samsung hardware like s pen and camera will work fine on GSI ?
Do KVM is enabled on GSI ?
shim80 said:
Thanks for the tutorial
I have a Galaxy Note 9 (snapdragon) and Galaxy Tab S8+, wich doesn't have (almost) any roms.
Do you think Samsung hardware like s pen and camera will work fine on GSI ?
Click to expand...
Click to collapse
The idea behind GSIs, specifically Project Treble, is that the system image can change, while the hardware drivers and kernels will remain the same. So, in theory, yes - since you'd be using the original kernel, all hardware features should work. YMMV though, and I have no idea how to make them work if they don't. I'm not a developer.
shim80 said:
Do KVM is enabled on GSI ?
Click to expand...
Click to collapse
What is KVM? If it is Samsung specific, then likely not, unless it's built into the kernel.
V0latyle said:
What is KVM? If it is Samsung specific, then likely not, unless it's built into the kernel.
Click to expand...
Click to collapse
KVM (for Kernel-based Virtual Machine) is a feature that allow hardware virtualization on recent ARM chips.
It's enabled by default on Exynos and Tensor (Google), but Qualcomm is using it for protecting the kernel, so it's can't be enabled unless using modified custom kernel...
shim80 said:
KVM (for Kernel-based Virtual Machine) is a feature that allow hardware virtualization on recent ARM chips.
It's enabled by default on Exynos and Tensor (Google), but Qualcomm is using it for protecting the kernel, so it's can't be enabled unless using modified custom kernel...
Click to expand...
Click to collapse
Ah. Well, as I explained above, a Generic System Image is designed to be used with a separate kernel, most often the OEM kernel, so you could potentially flash a custom kernel and use a GSI with it. More to your point though, I have no idea - if KVM is implemented in the kernel, it should work on a GSI, provided you install the necessary framework to use it.
can you send any screenshot??
amirabbas mm said:
can you send any screenshot??
Click to expand...
Click to collapse
It's just AOSP, it's not custom. Looks like the Pixel interface. I don't have any screenshots.
Suggestion, you can add https://github.com/Johx22/Patch-Recovery
for devices without twrp. I and other ppl have already tested on galaxy tab A7 Lite and it works fine
V0latyle said:
The idea behind GSIs, specifically Project Treble, is that the system image can change, while the hardware drivers and kernels will remain the same. So, in theory, yes - since you'd be using the original kernel, all hardware features should work. YMMV though, and I have no idea how to make them work if they don't. I'm not a developer.
What is KVM? If it is Samsung specific, then likely not, unless it's built into the kernel.
Click to expand...
Click to collapse
What’s the catch? In other words, how is this different then the pixel experience rom?
Skorpion96 said:
Suggestion, you can add https://github.com/Johx22/Patch-Recovery
for devices without twrp. I and other ppl have already tested on galaxy tab A7 Lite and it works fine
Click to expand...
Click to collapse
I've never used that, can you describe how it works? I don't really intend this guide for beginners so I won't write detailed instructions but I can cover the basics. It sounds as though this can be used to flash system images via fastboot?
Arealhooman said:
What’s the catch? In other words, how is this different then the pixel experience rom?
Click to expand...
Click to collapse
I'll be honest, I've never used Pixel Experience, but from what I can see, the major difference is that it is based on AOSP and has a lot of Pixel stuff included. You can absolutely use this guide to install any GSI, they should all work the same since they're designed to work with a separate kernel. That being said, it appears that Pixel Experience is provided in a sideloadable ZIP, so you'd simply install the ZIP in TWRP.
What I have linked in this thread is the official Android Developer GSI which is intended to be used as a Compatibility Test Suite platform for Android apps, so it isn't really fine tuned for daily use, but in my experience it's been quite stable and usable. You can also use the master AOSP builds if you want the pure source.
V0latyle said:
I've never used that, can you describe how it works? I don't really intend this guide for beginners so I won't write detailed instructions but I can cover the basics. It sounds as though this can be used to flash system images via fastboot?
I'll be honest, I've never used Pixel Experience, but from what I can see, the major difference is that it is based on AOSP and has a lot of Pixel stuff included. You can absolutely use this guide to install any GSI, they should all work the same since they're designed to work with a separate kernel. That being said, it appears that Pixel Experience is provided in a sideloadable ZIP, so you'd simply install the ZIP in TWRP.
What I have linked in this thread is the official Android Developer GSI which is intended to be used as a Compatibility Test Suite platform for Android apps, so it isn't really fine tuned for daily use, but in my experience it's been quite stable and usable. You can also use the master AOSP builds if you want the pure source.
Click to expand...
Click to collapse
Would this have everything Google pixels have? Is this Google pixel firmware?
Arealhooman said:
Would this have everything Google pixels have? Is this Google pixel firmware?
Click to expand...
Click to collapse
This is just AOSP - plain Jane vanilla Android, optionally with Google apps. As such, it doesn't include any of the device specific customizations that Pixels may have. Pixel firmware is very close to AOSP and I'm not sure what all is different but the Pixels are marketed as Google's "Android Showcase" devices that demonstrate what Android is capable of.
What the Pixel series does is use a generic kernel and system image - meaning that you could, in theory, use the same system image on any GSI capable device - but they also have a product partition that contains the various customizations for that particular device. This is done to make software updates much simpler; on the Pixel series, Google basically uses one system build across all its active devices, meaning they don't have to rebuild for every update, while the product partitions are what hold the device specific software.
Long story short, Pixels are indeed running the AOSP GSI that I've shared here, but the GSI itself does not contain anything specific to the Pixels.
Tysm, and thsi has no chance of a brick if I do it right and am supported by project treble?
Arealhooman said:
Tysm, and thsi has no chance of a brick if I do it right and am supported by project treble?
Click to expand...
Click to collapse
It depends on your definition of "brick". To me, "bricked" means the device is completely unusable and unrecoverable with the software and tools that are available to the average user - for example, if the screen doesn't come on, the bootloader is corrupted, something like that.
Using a GSI won't cause this to happen, if you do everything properly. At the very worst, it may be unstable, and you may have to go back to your last known good configuration to be able to get your device working again, but that's just a matter of either flashing different firmware or going back to OEM firmware.
It's entirely possible that this may not work properly on your device, and since I am not a developer, I am not providing any support whatsoever. Use at your own risk.
V0latyle said:
I've never used that, can you describe how it works? I don't really intend this guide for beginners so I won't write detailed instructions but I can cover the basics. It sounds as though this can be used to flash system images via fastboot?
I'll be honest, I've never used Pixel Experience, but from what I can see, the major difference is that it is based on AOSP and has a lot of Pixel stuff included. You can absolutely use this guide to install any GSI, they should all work the same since they're designed to work with a separate kernel. That being said, it appears that Pixel Experience is provided in a sideloadable ZIP, so you'd simply install the ZIP in TWRP.
What I have linked in this thread is the official Android Developer GSI which is intended to be used as a Compatibility Test Suite platform for Android apps, so it isn't really fine tuned for daily use, but in my experience it's been quite stable and usable. You can also use the master AOSP builds if you want the pure source.
Click to expand...
Click to collapse
It decompile stock recovery, add fastboot and recompile, I'll show you a photo as attachment
Skorpion96 said:
It decompile stock recovery, add fastboot and recompile, I'll show you a photo as attachment
Click to expand...
Click to collapse
Ah ok, so when you're in fastbootd mode, you can just flash the partitions directly?
Skorpion96 said:
It decompile stock recovery, add fastboot and recompile, I'll show you a photo as attachment
Click to expand...
Click to collapse
In this picture, is this how fast boot d look like? Im scared flashing too good to be true stuff on my device, and even more scared that it works, and then when I try to flash soemthign thru it it break connection and gives me a hard brick
Arealhooman said:
In this picture, is this how fast boot d look like? Im scared flashing too good to be true stuff on my device, and even more scared that it works, and then when I try to flash soemthign thru it it break connection and gives me a hard brick
Click to expand...
Click to collapse
It is fastboot on my galaxy tab A7 Lite, you can enter by recovery, it will add the option
V0latyle said:
Ah ok, so when you're in fastbootd mode, you can just flash the partitions directly?
Click to expand...
Click to collapse
Yep
can i install on costume rom??