Related
Is anyone successful in loading modded system.img to a system-as-root device like Pixel 2+? With the nexus 5x I use to make some changed to the build.prop and init.rc to get adb on boot/OOBE but due to the new system-on-root with the Pixel devices, I need to modify the system image. I bought the paid version of Kitchen to do just that, and I can build an image (signed and non-signed... not sure the difference, so I've tested both). Below are the steps I've used but the device always fails to load after.
boot-slot: a
Console: DISABLED
Secure Boot: yes (Production)
Device state: unlocked
"ERROR: LoadImageAndAuth Failed: Load Error"
Code:
1. Download Pixel2 8.1.0 firmware from google
2. Pull the system.img
3. Run Kitchen tool and create a new project
4. add the system.img to the project folder
5. Extract the system image (#4 Extract for new rom)
6. Give it a name: TEST
7. Which perm type would you like to use?: #4 raw_img
8. Don't make any changes yet.... testing to see if it can load
9. Go to #8, -> #7 Build Menu -> #2 build ext4 img -> #1 system -> #2 sparse -> #4 system.img
Code:
fastboot flash system_a C:\Users\username\Desktop\Pixel2_Images\system_new.img
fastboot flash system_b C:\Users\username\Desktop\Pixel2_Images\system_new.img
and/or
Code:
fastboot flash system C:\Users\username\Desktop\Pixel2_Images\system_new.img
and/or
Code:
1. rename system_new.img to system.img
2. Repack the system.img in the Pixel Firmware zip
3. Run flash-all.bat
Update 1:
I have also tried the following.
Code:
1. Boot Pixel 2 Image from firmware site
2. Reboot device into recovery mode
2. Wait till you see a Android icon with !
3. Hold Power and hit up arrow
4. Select Wipe data/factory reset
5. When it boots to OOBE, reboot to bootloader
# load the latest TWRP.img
6. fastboot boot C:\Users\username\Downloads\twrp-3.3.0-0-walleye.img
# Device will boot once to TWRP
# Select Wipe -> swipe for factory reset
7. adb push <The image i created using Kitchen> /sdcard/Download
8. select Install and select the Image
Device Boots with error "Can't load Android system. Your data may be corrupt."
prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
I think it's better to provide your questions in Redmi note 9 fourms in Xda.
Check it :https://forum.xda-developers.com/redmi-note-9
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
Redmi note 9 supporting dynamic storage if it come with android 10 out of box..if you hava fastboot rom then go to image folder on it and find super.img.
If super.img found that's mean your are good to go...
Or if you find system.img and vendor.img then sorry
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Mantipallykrishna said:
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Click to expand...
Click to collapse
If you use two GSI. That's mean you install a a dynamic GSI over a GSI then the problem will happen. Because all GSI can not capable with it. If you flash dynamic GSI over MIui Rom then the problem not happened.when you in MIui then restart to go dynamic GSI.when you are in dynamic GSI then do not reboot your device just power off and then power on your device to go MIui.then you find the dynamic GSI restart option again.even if you can not find the notification then go to your device recovery option and reboot device from recovery mood.
Even if your problem not solve then you can activate GSI from adb cmd
adb shell gsi_tool enable
Then you can go GSI and when you reboot you can not go back MIui but it is good option to use GSI without data loss.to deactivate just run this adb cmd
adb shell gsi_tool disable
Now reboot and then you can back MIui again..
But remember to check if your dynamic GSI can connect you PC via adb.
This method work for me.I also face the same problem like you.hope you can solve your problem.and remember one thing that if you use magisk patched boot.img then you can not boot your dynamic GSI.I think it is a bug hopefully it will solve soon
the first time worked fine, then i tried the command: adb shell gsi_tool enable, for some reason i wasn't able to connect to gsi with adb to turn it off: adb shell gsi_tool disable
i flashed miui with miflash, but now the installation won't start again
just found out that when a micro sd card ist in the phone, for some reason dsu won't show up, i removed the micro sd card, restarted the phone, and now dsu shows in the notification bar
Shas45558 said:
prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&source=web&rct=j&url=https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list&ved=2ahUKEwj04pKZwfnrAhVLfXAKHV8FAFcQFjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Click to expand...
Click to collapse
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
fire7ly said:
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
Click to expand...
Click to collapse
Use dsu..it is easy method
Shas45558 said:
Use dsu..it is easy method
Click to expand...
Click to collapse
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
fire7ly said:
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
Click to expand...
Click to collapse
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Shas45558 said:
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Click to expand...
Click to collapse
you mean same directory where gsi present.
fire7ly said:
you mean same directory where gsi present.
Click to expand...
Click to collapse
Yes..
work in poco m3?
how about redmi note 9 pro sir? can you give me a link for the tut?
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Dear Wer99,
I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],
I'm Wondering How Could I Add SuperSU & Root Permission In It
GSI : [CherishOS, AOSP10, AOSP11]
Wer99 said:
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Click to expand...
Click to collapse
I tried all of this and I even went as far as trying to literally change the filesystem UUID and the filesystem of system.img as well, I detected some issues when booting a GSI and it's that the filesystem and the filesystem UUID's had to match (filesystem had to be EXT2 for some reason), and after I did all of that, I flashed the super.img to my phone but after a few seconds of it trying to boot (10 seconds after it's past the unlocked bootloader screen) it just reboots and kicks me to fastboot mode, a friend of mine told me that if it booted to fastboot it meant that the bootloader was able to pass instructions to the OS but failed, hence why it kicked me to fastboot, and after that I tried with different GSIs and neither of them worked sadly.
Also in the attributes I'd recommend changing "readonly" to "none" so that the partitions are Read/Write from super.img, after flashing super.img, just edit the fstab file (located in "/etc/fstab" for recovery) and replace "ro" in the mount points with "rw" so that you can read and write data to them, the point of this is to make the partitions read and write so that you can edit them and install anything you'd like, and that's exactly the reason I did it.
After some time we got a modded magisk apk that does work and doesn't have the legacy device detection issue that it had before, due to the phone using dynamic partitions and using a ramdisk, Magisk would detect the device as legacy and it would use "SAR_init", something that the device doesn't needs and because the boot process fails, it reboots.
Also, before I realized that you could make the partitions inside super.img read/write, I would usually use readonly and it wouldn't work either, I'd appreciate if you could help me with this.
Wer99 said:
Easy to way to install a GSI on your Samsung A21s without installing a Virtual Linux.
NFC, Screen Cast, and USB MTP unfortunately is not working with AOSP 10 and 11. Backup all your data.
If don't want to make one, download my Pre-Rooted GSIs below and flash.
*Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Android 10 -> Download (MediaFire)Android 11 -> Download (MediaFire)Android 11 - AOSP 11.0 v306 -> Download (MEGA) - NEWAndroid 10 Screenshots
1. Requirements:
1. Unlock your Bootloader2. Download and Install a Linux Subsystem -> Ubuntu Subsystem -> "Tutorial How to install Linux Subsystem on Windows 10 | or search how to"3. GSI Android 10 A/B Gapps -> Download only the "arm64, A/B". I recommend releases from Treble Experimentations AOSP like "system-roar-arm64-ab-gapps.img.xz". 4. Samsung.zip -> There's all needed tools and files - Odin, 7-Zip ZS etc...
- Download Samsung.zip and extract the folder "Samsung" to your desktop, and extract your chosen GSI using to this folder.
- Download your stock firmware and extract the super.img.lz4 file from AP_A217XXXXXXXXXX_XXX_XXXX_REV00_XXX.tar.md5 with 7-Zip ZS.
- Now extract super.img.lz4 using 7-Zip ZS (don't use 7-zip) to Samsung folder. Rename super.img to stock_super.img.
2. Convert stock_super.img to raw_super.img:Open CMD ad use this codes:
cd C:\Users\%USERNAME%\Desktop\Samsungsimg2img.exe stock_super.img raw_super.img
Wait...
3. Extract raw_super.img:On your Samsung folder, use SHIFT key of your keyboard + right click and click at "Open Linux Shell Here", wait a little, and use this code and wait the extraction:
./lpunpack --slot=0 raw_super.img
*If the extraction is completed, verify if there's this files odm.img, system.img, vendor.img and product.img. Delete or rename system.img and product.img, then extract your GSI to Samsung folder and rename the xxx.img file to system.img.
4. Pack all the files and Flash:No math here! Just use this code on Terminal and wait (Ignore errors like "Partition system, vendor, odm will resize..." or "Invalid sparce file format at header magic...")
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5557452800 --group main:3819597824 --partition system:readonly:3340271616:main --image system=./system.img --partition vendor:readonly:474976256:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Wait....
Use 7-Zip to archive the super.img to .tar (super.tar) and flash it on Odin (AP) and wait the phone to boot.
Unlock your Bootloader and wipe your data using your stock recovery and quickly boot to Download Mode and flash the super.tar on Odin (AP):
Notes:I not responsible for any damage on your phone. If anything occurs, just flash your stock regional firmware through Odin.
If this tutorial did not work, you did something wrong or your phone is not supported. Don't forget to wipe your data through Recovery, it's very important.
If you want Magisk working on your A21s I recommend you to report to an issue Topjohnwu at Github.
Click to expand...
Click to collapse
Also, Just so you know, the recovery that we have is OrangeFox R11 which is currently an alpha build, thanks to magisk I was able to use the tool "dd" in termux to flash the recovery.img to /dev/block/by-name/recovery (aka the recovery partition) and this helped me bypass DL mode which is even worse now that I upgraded to U5 (I regret it and I tried downgrading from recovery instead of DL mode but the linux kernel itself protects the mmcblk0boot0 partition which is supposed to be the partition where the "BL" is located, and I tried flashing the sboot.bin file to that partition and it didn't work due to it being protected
Anyways back to the original topic, I don't know how but after flashing OrangeFox R11 with dd in android (I used su with magisk of course because), OrangeFox managed to boot with stock vbmeta and this build was supposedly built with A10's firmware in mind, not A11's firmware, so I have some hopes that flashing super.img from recovery might work if given the right vendor and firmware, I even flashed a vbmeta that was made for U3 from OrangeFox and it booted without any issues, oddly enough OneUI booted with that U3 vbmeta.img
LonelyCracker said:
Dear Wer99,
I Successfully Made A Non-Rooted GSI By Following Your [Tutorial / Guide],
I'm Wondering How Could I Add SuperSU & Root Permission In It
GSI : [CherishOS, AOSP10, AOSP11]
Click to expand...
Click to collapse
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
David112+ said:
You don't need SuperSU anymore, There's already a fixed magisk for it, Here's the links:
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
LonelyCracker said:
Yeah I Know But I'm Just Interested In Making A Prerooted GSI
Click to expand...
Click to collapse
What's the point of making a prerooted GSI with an outdated root method?
You can't even install modules with SuperSU
To David112+ :
In My Opinion, Prerooted GSI Is Way Better.
You Could See The Comparison I Made Here.
Also Making One GSI Could Gain Me Lots Of Experience.
So I Couldn't Think Of The Reason Why Not
Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,
Which You Could Find Here.
LonelyCracker said:
To David112+ :
In My Opinion, Prerooted GSI Is Way Better.
You Could See The Comparison I Made Here.
Also Making One GSI Could Gain Me Lots Of Experience.
So I Couldn't Think Of The Reason Why Not
Magisk Patched Stock [Firmware / ROM] Also Have It Own Problem,
Which You Could Find Here.
Click to expand...
Click to collapse
I don't think you've realized or checked the group of the phone but a load of people have already rooted their ROMs with Magisk and so far they have no problems, and still, everyone agrees that installing modules somewhere from the internet is the responsibility of the end user.
And I'm pretty sure that everyone agrees that magisk is the best root method, and even if you wipe data, you can just reinstall the Magisk apk to get the root prompt and finish setting it up, or better yet. use the systemizer module to systemize the magisk apk so that it's installed in system instead of data.
Making a prerooted GSI is just a waste of time, I'd rather just make normal GSI that's flashable on the phone and just install Magisk or systemize the Magisk APK.
I do agree that making a GSI flashable for the phone makes you gain a lot of experience but you're wasting your time into something that barely anyone is going to use, due to the fact that it has SuperSU which is old and outdated and most people prefer Magisk anyways because it's updated and not only that but you can pretty much install anything you'd like with the modules.
To David112+ :
Sorry To Disagree With You, I Was Trying To Acheive A Goal There .
My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).
Hopefully I Could Get Help Somewhere.
But Fun Fact Is...
I Water-Damaged My Phone
Question :
1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
LonelyCracker said:
To David112+ :
Sorry To Disagree With You, I Was Trying To Acheive A Goal There .
My Goal Was To Get ADB (Android Debug Bridge) With "adb root" Working On Magisk Patched Stock [Firmware / ROM]. After Many Research & Attempt To Acheive That, I Gave Up... I Gained Some Knowledge There Too. I Know That Stock Rom Are For Production Purpose & I Can't Gain Root Access Using ADB (Android Debug Bridge).
Hopefully I Could Get Help Somewhere.
But Fun Fact Is...
I Water-Damaged My Phone
Question :
1.) Is It Possible To Make A Non Rooted GSI & Patch It With Magisk ? How ?
Click to expand...
Click to collapse
Custom ROMs should work with ADB root normally
2. To install Magisk just use the links that I shared in this post (https://forum.xda-developers.com/t/...d-gsis-for-samsung-a21s.4269227/post-84975373)
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
To David112+ :
But Is Not Possible To Use ADB (Android Debug Bridge) On Magisk Patched Stock [Firmware / ROM]. What I Was Saying Is To Use "adb root" On Magisk Patched Stock [Firmware / ROM]
I'm Only Able To Use The Command "adb root" In Custom GSI Built By Wer99.
Not Every Custom Build GSI Are Prerooted.
Maybe You're Right Magisk Is Better Than Old Little SuperSU. But I Need "adb root" To Work With It
thatha said:
After upgrading to U5, I can't install these GSIs anymore. It bootloop all the times
Click to expand...
Click to collapse
If you have magisk with stock ROM, good news for you, I'll be working a guide in how to get a GSI installed as a magisk module, I tested this with ShapeShiftOS and I got as far as the boot animation of ShapeShiftOS, Once I was booted I checked ADB and sdcard was encrpyted and that's why it wasn't able to start correctly, it was just stuck in the google logo with a loading bar, I'm gonna try decrypting data, formatting and then installing the module
If this does work then I'll be releasing a guide in how to get a GSI of your preference working as a magisk module
Explanation: Thanks to Magisk's Magic Mount feature, I'm able to systemlessly swap the assets of OneUI with a Custom ROM's of my choosing, such as ShapeShiftOS
Edit: This idea is discarded, Because of the userdata partition being encrypted I can't use ShapeShiftOS, and even after decrypting I can't use it because OneUI gets stuck in "Starting android" when using the boot image with patched fstab and magisk
And if I download gsi android 11 through mediafire, will I have to do all this procedure? or just flash on odin? A21S ANDROID 11.
To Oroki:
These GSI Is Ready To Be Flashed.
LonelyCracker said:
To Oroki:
These GSI Is Ready To Be Flashed.
Click to expand...
Click to collapse
but will i have to do topic 2 and 3?
To Oroki :
Please Explain What Do You Mean By Topic 2 & 3
LonelyCracker said:
To Oroki :
Please Explain What Do You Mean By Topic 2 & 3
Click to expand...
Click to collapse
2. Converta stock_super.img em raw_super.img: e3. Extrato raw_super.img:
To Oroki :
Those Step You Provide Aren't Necessary Anymore
It's Patched Which Mean You Don't Have To Do Anything To It
Sorry For Late Reply
[Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More
Android Security Bulletin—June 2023
Pixel Update Bulletin—June 2023
Introduction
This Guide is for Pixel 6 owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
If you choose to use a Custom Kernels, Custom ROM, etc. You should read the Installation Instructions in their thread before using this guide or attempting to install them. Additionally, the order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting them
.
Prerequisites
A Pixel 6 phone with an unlocked bootloader.
The latest Android 13 Factory or OTA Image: "oriole" for Pixel 6
Factory Image
a. 13.0.0 (TQ3A.230605.010, Jun 2023)b. 13.0.0 (TQ3A.230605.010.A1, Jun 2023, T-Mobile, T-Mobile MVNOs)c. Which one should I use?
OTA Image
a. 13.0.0 (TQ3A.230605.010, Jun 2023)b. 13.0.0 (TQ3A.230605.010.A1, Jun 2023, T-Mobile, T-Mobile MVNOs)c. Which one should I use?
A Computer with the latest working SDK Platform-tools 33.0.3 installed.
Important Notes:
a. Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
b. Update Platform Tools, regularly, for optimal performance.
c. Need Google's USB Drivers for your Pixel Phone?
NEW
Both Slots Bootable
@badabing2003 has found a way to Have both slots bootable.
He has automated the procedure and added it to PixelFlasher.
@Lughnasadh tested the Both Slots Bootable procedure on his Google Pixel 7 Pro and Google Pixel 6 Pro phones: It works!
Android 14 Beta are up.
Builds are only available for the following Pixel devices:
Google Pixel 4a5(G)
Google Pixel 5 and 5a
Google Pixel 6 and 6 Pro
Google Pixel 6a
Google Pixel 7 and 7 Pro
* * * 64-bit-only system images * * *
Google Pixel 4a (5G)
Google Pixel 5
Google Pixel 6
Google Pixel 6 Pro
Android 14 GSI binaries and release
Pixel 4a5(G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a Pro
Pixel 7 and 7 Pro
Update(s)
Factory/OTA Images - 13 June
Android 14 DP
Factory images and OTA images
Android 14 GSI binaries and release
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta -
app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.3 17Jun
SDK Platform-tools 33.0.3 Aug 2022
Custom Kernels
a. Google Pixel 6 Pro ROMs, Kernels, Recoveries, & Otherb. ElementalX Kernel Manager
My Other Guides
Pixel 7 Pro
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
@topjohnwu - Magisk.
vvb2060 - Magisk alpha.
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Use the Android flash tool:
select Wipe => Force Flash Partitions => Lock Bootloader.
Lock Bootloader
If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may brick your phone.
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Manually Install/Update Factory Image keep data or wipe data.
Important Note(s):
If you haven't updated your phones Factory image in awhile. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
"Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time
Warning: The Android 13 update for Pixel 6, Pixel 6 Pro, and the Pixel 6a contains a bootloader update that increments the anti-roll back version for the bootloader. This prevents the device from rolling back to previous vulnerable versions of the bootloader. After flashing an Android 13 build on these devices you will not be able to flash and boot older Android 12 builds. For developers who need to develop and test against an Android 12 environment, a special Developer Support Build that contains the bootloader update should be used.
After taking an Android 13 update and successfully booting the device post update, an Android 12 build resides in the inactive slot (seamless updates for more information on slots) of the device. The inactive slot contains an older bootloader whose anti-rollback version has not been incremented. If the active slot is then flashed with a build that fails to boot, the fallback mechanism of seamless updates kicks in and the device tries to boot from the inactive slot. Since the inactive slot contains the older bootloader, the device enters an unbootable state.
To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot"...
If you want to update to the Android 13 Factory image without wiping your phone: Do Flash Factory Image Keep Data (below).
Always verify you have the latest working version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
If you get an error while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
If you phone bootloops
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
then type
fastboot Reboot
Backup your data
Download the latest Factory Image: Pixel 6 - oriole to your Computer.
Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
Flash Factory Image Keep Data
Upgrading to Android 13
* E D I T - flash-all.bat file *
Flash to current/Active Slot.
@Echo off
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-oriole-slider-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-oriole-a9999a-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot [update image-oriole-aa9a.999999.999.zip
Note:The -w is removed to Keep Data.
echo Press any key to exit...
pause >nul
exit
Note: It is a good idea to flash the Google factory image to both slots (A & B) when Upgrading to new Android Version.
See Flash Other Slot bat file... below, to flash to the other/inactive slot.
* * * * E N D - Edit * * * *
Updating Android 13
Flash to Other/Inactive Slot.
Note: See Flash Other Slot bat file... below.
* * * * Create - Flash Other Slot bat file * * * *
Save Flash Other Slot bat file - as flash-other.bat
Note: To run this file type flash-other at the Command Prompt.
ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
echo This is the slot you are currently on.
fastboot getvar current-slot
echo Press any key to continue...
pause >nul
fastboot --set-active=other
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
echo This is the slot you switched to.
fastboot getvar current-slot
echo Press any key to continue...
pause >nul
flash-all
exit
* * E N D - Creating File * *
After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is completed.
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Data/Internal Storage.
Do not edit the flash-all.bat file.
If you need to disable Verity and Verification: See Disabling Verity and Verification below.
Disabling Verity and Verification
* E D I T - flash-all.bat file *
@Echo off
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot --set-active=other
fastboot reboot-bootloader
fastboot flash bootloader bootloader-oriole-slider-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-oriole-a9999a-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot - w update --disable-verity --disable-verification image-oriole-aa9a.999999.999.zip
echo Press any key to exit...
pause >nul
exit
Notes:
The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
When doing Subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
Once you start Disabling Verity and Verification you should continue doing it. If you skip disabling one time. The next time you Disable Verity and Verification it will wipe your phone.
Some kernels require Disabling verity and verification
To flash both slots (A & B partitions) see Flash Other Slot bat file... above.
* * * * E N D - Edit * * * *
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
android-info.txt
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
On your phone: Boot the bootloader (fastboot mode) (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
(NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
Before you start
Backup your data
Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
Download the latest Factory and OTA image for your device.
Verify the checksum of the Factory and OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
Extract the boot.image from the Factory image:
Extract the Factory Image file that you downloaded (oriole-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-oriole-aa9a.999999.999.zip) into a folder. The stock boot.img file should be in this folder.
Patch the boot.img:
Open the Magisk (Alpha/Beta/Canary/Delta/Stable) App
The Update Channel should be set to Alpha/Beta/Canary/Delta/Stable, depending on the version you installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
Reboot
Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Sideload the OTA zip file
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume up button up once. The recovery text menu will appear.
Connect the phone to the PC via USB cable
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
(Optional) Verify Computer sees your device:
Type: adb devices and press return.
Your device number should shows up with "sideload" next to it.
Sideload the OTA zip file
Select the Apply update from ADB option from the recovery text menu
Type:
adb sideload oriole-ota-aa9a.999999.999-a99999aa.zip and press enter.
Once sideloading finishes, reboot the phone by choosing Reboot system now option on the The recovery text menu.
Note: This slot is bootable and NOT ROOTED
Sideload the OTA zip file to the other slot and Root it.
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume up button up once. The recovery text menu will appear.
Connect the phone to the PC via USB cable
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
Sideload the OTA zip file
Type: adb sideload oriole-ota-aa9a.999999.999-a99999aa.zip at the prompt and press enter.
Once sideloading finishes, choose Reboot system now option on the The recovery text menu.
Flash Magisk_patched....img to root
On the phone: Boot bootloader/fastboot mode
On the PC:
Open a Command Prompt in the SDK Platform-tools folder.
Type: fastboot flash boot magic_patched....img at the Prompt and press enter.
Type: fastboot reboot at the Prompt and press enter.
Disconnect the phone from the PC.
Note: This slot is bootable and ROOTED.
Done!
Extract Files from Factory Image: flash-all.bat boot/init_boot.img Flash boot/init_boot.img
Extract Files from Factory Image
Extract flash-all.bat and boot.img file
Download the latest Factory image to your phone.
Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
Open the folder you extracted the Factory image to and, extract the Image file (image-oriole-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this folder.
Flash boot/init_boot.img
Flashing the boot/init_boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Root/Reroot with Magisk and Pass SafetyNet.
Android 13
Upgrade to Android 13: OP, Part II - INSTRUCTIONS, 2. Install/Update Factory Image keep data or wipe data, Keep data
Patching the boot.img - to root/reroot.
If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app. Do this before you patch the boot/init_boot image:
Open the Magisk Manager app and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager. You can also use TB Checker to check if you have more than one Magisk Manager app installed.
Extract the boot/init_boot.img file from the Factory Image.
Download the latest Factory image to your phone.
Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-oriole-aa9a.999999.999.zip) into the folder. The, stock, boot/init_boot.img file should be in this folder.
Install Magisk Canary - Download app-release.apk
or
Magisk Beta/Stable App
Open Magisk Beta/Canary/Stable App
The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Copy/Move the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Copy it to a USB drive and transfer it to your computer.
Move it to your computer using adb push
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important, if your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Remove Modules
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
fastboot Reboot.
Important, if the Magisk Manager app has the Superuser and Module buttons greyed out:
Read @badabing2003 post
Pass Safety Net with SafetyNet Fix
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
Install Displax's safetyNet Fix
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the Displax's SafetyNet Fix file you downloaded.
Tap the Displax's SafetyNet Fix file.
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk.
Enable Denylist
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
(Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification
It may take 24 hours for Device Certification to be updated.
Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Install/Update Magisk Modules
Download Modules
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Androidacy Module Manager
Open Androidacy Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Androidacy Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 12 (R) T.W.R.P
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Google Pixel 6 ROMs, Kernels, Recoveries, & Other
Other Custom Rom
[ROM][13][raven][oriole] riceDroid 8.0[AOSP][PIXEL]
Themes, Apps, and Mods
Google Pixel 6 Themes, Apps, and Mods
T.W.R.P. Backup/Restore
Waiting for Android 13 T.W.R.P.
huzzah!
Homeboy76 said:
[Guide] Root Pixel 6 Android 12 with Magisk + Unlock/Lock Bootloader + More
Android Security Bulletin—January 2022
Pixel Update Bulletin—January 2022
Introduction
This Guide is for Pixel 6 owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 5'.
NEW
Understand 5G network...
With the Magisk Canary update to 23016, there is no longer a need to wipe or --disable verity -- disable verification
Magisk Alpha (vvb2060)
Download Link.
The differences between the different variants of Magisk
Magisk Modules for Magisk Alpha/Canary
a. GitHub - Fox2Code/FoxMagiskModuleManager: A new module manager for Magisk when the official app drop support for it
b. Fox Magisk Module Manager Releases
Update(s)
Factory/OTA Images - Jan
Magisk Canary - Magisk-23016 15Dec
TWRP - Waiting for T.R.W.P. for Android 12
SafetyNet - SafetyNetFix v2.2.1 (Zygisk) 22Dec
SDK Platform-tools - r31.0.3 18Aug
Custom ROMs[/INDENT]
[ROM][SNOWCONE][oriole][12] StatiXOS v5.0
Custom Kernels[/INDENT]
a. ElementalX - Check ElementalX Kernel Manager
b. [KERNEL] CleanSlate P6 - S1.2.0 |S2S|AdBlock|VIB|BatterySvr [Nov 22] by tbalden
c. [KERNEL] [blu_spark r45] [A12]
Custom ROMs
a. ProtonAOSP[12] 01Nov
b. lineage v18-1 redfin[12] Nightly
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 6 phone with an unlocked bootloader.
The latest Android 12 Factory or OTA Image: "oriole" for Pixel 6
Factory Image
a. 12.0.0 (SQ1D.220105.007, Jan 2022)
b. Which one should I use?
OTA Image
a. 12.0.0 (SQ1D.220105.007, Jan 2022)
b. Which one should I use?
A Computer with the latest SDK Platform-Tools: r31.0.3 installed.
Important Notes:
a. Update Platform Tools, regularly, for optimal performance.
b. Need Google's USB Drivers for your Pixel Phone?
My Other Guides
My other guides:
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
Google - Android 12 factory/OTA images.
@topjohnwu - Magisk.
vb2060 - Magisk alpha.
Those I may have, inadvertently, forgotten.
~ ~ ~ INSTRUCTIONS ~ ~ ~
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep data or wipe data
Important Note(s):
Install Magisk Canary 23016
Note: Tap 3 dot menu across from canary => Download, app-debug.apk
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
If you get an error:while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
Backup your data
Download the latest Factory Image: Pixel 6 - oriole to your Computer.
Extract the factory Image to a folder.
Flash Factory Image Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., DroidEdit app.
Change this line: fastboot -w update image-oriole-sq9d.999999.999.zip
to this: fastboot update image-oriole-sq1d.999999.999.zip
Note: If you do not remove the -w your internal storage will be wiped.
After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is completed.
Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Internal Storage.
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Root/Reroot with Magisk and Pass SafetyNet.
Android 12
Upgrade to Android 12: OP, INSTRUCTIONS, Install/Update Factory Image keep data or wipe data, Keep data
Patching the boot.img - to root/reroot.
Do #6 - Extract boot.img
Install Magisk Canary
Note: Tap 3 dot menu across from canary => Tap Go to file => Download, app-debug.apk
Open Magisk Canary App
Set the Update Channel Canary.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important Notes:If your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
Pass Safety Net with SafetyNet Fix 2.2.1
Download File(s)
Universal SafetyNet Fix · v2.2.1 (Zygisk)
Why Zygisk?
Install SafetyNet Fix 2.2.1
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the SafetyNetFix file you downloaded
Tap the SafetyNetFix file
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk and Enforce DenyList.
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
Optional Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll down to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification.
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 12 (R) T.W.R.P
Extract/Flash boot.img
Extract boot.img
Download the latest Factory image to your phone.
Extract the Factory Image file (oriole-sp1d.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder and, extract the Image file (image-oriole-sp1d.999999.999.zip) into the folder.
Copy the boot.img file to the computer's Platform-tools folder.
Flash boot.img
Flashing the boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Custom ROMs
Need help with a Custom ROM?
First, read and follow the Installation Instructions. The installation instructions are in the OP.
Second, if you have a problem Installing it, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
ROMs
Alpha/Beta
None
Official
None
Unofficial
[ROM][SNOWCONE][oriole][12] StatiXOS v5.0
Apps/Mods/Scripts/Tethering/Themes
Tulsadiver's Mods
Stand alone Clock, Navbargone, etc. Mods
Quick Pull down Tile-Accent Colors
ADB Font Installer including the lockscreen clock
ADB Magisk Module Mod Maker
Other Mods
[MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Thread
aodNotify - Notification Light / LED for Pixel 6!
How-To Enable Two-Button Navigation on Android 12 (Root Required)!
Audio switcher
T.W.R.P. Backup/Restore
Waiting for Android 12 T.W.R.P.
Click to expand...
Click to collapse
Great resource, thanks. Think you can put it in the How To Guide so it's easy to find?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
bobby janow said:
Great resource, thanks. Think you can put it in the How To Guide so it's easy to find?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Click to expand...
Click to collapse
XDA Staff moved it. Are you suggesting I should make a Guide for the Pixel 6 Pro?
Thank you @Homeboy76 as always your guides are excellent.
Nice.!
I put this thread on the watch list incase I have a brain fart. And need to find a good reference for what I am working on at that moment.
Homeboy76 said:
XDA Staff moved it. Are you suggesting I should make a Guide for the Pixel 6 Pro?
Click to expand...
Click to collapse
For sure! Depending on your time committments that would be great.
When I go to patch the boot.img I get an error in Magisk
Code:
- Device platform: arm64-v8a
- Installing 92546e8a (23016)
! Process error
! Installation failed
In the logs, I see the following error in the stack trace
Code:
java.io.FileNotFoundException: /storage/emulated/0/boot.img: open failed: EACCES (Permission denied)
It seems like Magisk doesn't have permission to access the boot image?
EDIT:
Nevermind, it was caused by the app I was using to select the file. I used Google's default Files app and that fixed it
As always, great work! Boomarked in case i have a brain fart
Homeboy76 said:
[Guide] Root Pixel 6 Android 12 with Magisk + Unlock/Lock Bootloader + More
Android Security Bulletin—January 2022
Pixel Update Bulletin—January 2022
Introduction
This Guide is for Pixel 6 owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 6'.
NEW
Understand 5G network...
With the Magisk Canary update to 23016, there is no longer a need to wipe or --disable verity -- disable verification
Magisk Alpha (vvb2060)
Download Link.
The differences between the different variants of Magisk
Magisk Modules for Magisk Alpha/Canary
a. GitHub - Fox2Code/FoxMagiskModuleManager: A new module manager for Magisk when the official app drop support for it
b. Fox Magisk Module Manager Releases
Update(s)
Factory/OTA Images - Jan
Magisk Canary - Magisk-23016 15Dec
TWRP - Waiting for T.R.W.P. for Android 12
SafetyNet - SafetyNetFix v2.2.1 (Zygisk) 22Dec
SDK Platform-tools - r31.0.3 18Aug
Custom ROMs[/INDENT]
[ROM][SNOWCONE][oriole][12] StatiXOS v5.0
Custom Kernels[/INDENT]
a. ElementalX - Check ElementalX Kernel Manager
b. [KERNEL] CleanSlate P6 - S1.3.1 |S2S|AdBlock|VIB|BatterySvr [Jan 15] tbalden
c. [KERNEL] [blu_spark r45] [A12]
Custom ROMs
a. ProtonAOSP[12] 01Nov
b. lineage v18-1 redfin[12] Nightly
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 6 phone with an unlocked bootloader.
The latest Android 12 Factory or OTA Image: "oriole" for Pixel 6
Factory Image
a. 12.0.0 (SQ1D.220105.007, Jan 2022)
b. Which one should I use?
OTA Image
a. 12.0.0 (SQ1D.220105.007, Jan 2022)
b. Which one should I use?
A Computer with the latest SDK Platform-Tools: r31.0.3 installed.
Important Notes:
a. Update Platform Tools, regularly, for optimal performance.
b. Need Google's USB Drivers for your Pixel Phone?
My Other Guides
My other guides:
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
Google - Android 12 factory/OTA images.
@topjohnwu - Magisk.
vvb2060 - Magisk alpha.
Those I may have, inadvertently, forgotten.
~ ~ ~ INSTRUCTIONS ~ ~ ~
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep data or wipe data
Important Note(s):
Install Magisk Canary 23016
Note: Tap 3 dot menu across from canary => Download, app-debug.apk
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
If you get an error:while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
Backup your data
Download the latest Factory Image: Pixel 6 - oriole to your Computer.
Extract the factory Image to a folder.
Flash Factory Image Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., DroidEdit app.
Change this line: fastboot -w update image-oriole-sq9d.999999.999.zip
to this: fastboot update image-oriole-sq1d.999999.999.zip
Note: If you do not remove the -w your internal storage will be wiped.
After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is completed.
Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Internal Storage.
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Root/Reroot with Magisk and Pass SafetyNet.
Android 12
Upgrade to Android 12: OP, INSTRUCTIONS, Install/Update Factory Image keep data or wipe data, Keep data
Patching the boot.img - to root/reroot.
Do #6 - Extract boot.img
Install Magisk Canary
Note: Tap 3 dot menu across from canary => Tap Go to file => Download, app-debug.apk
Open Magisk Canary App
Set the Update Channel Canary.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important Notes:If your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
Pass Safety Net with SafetyNet Fix 2.2.1
Download File(s)
Universal SafetyNet Fix · v2.2.1 (Zygisk)
Why Zygisk?
Install SafetyNet Fix 2.2.1
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the SafetyNetFix file you downloaded
Tap the SafetyNetFix file
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk and Enforce DenyList.
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
Optional Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll down to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification.
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 12 (R) T.W.R.P
Extract/Flash boot.img
Extract boot.img
Download the latest Factory image to your phone.
Extract the Factory Image file (oriole-sp1d.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder and, extract the Image file (image-oriole-sp1d.999999.999.zip) into the folder.
Copy the boot.img file to the computer's Platform-tools folder.
Flash boot.img
Flashing the boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Custom ROMs
Need help with a Custom ROM?
First, read and follow the Installation Instructions. The installation instructions are in the OP.
Second, if you have a problem Installing it, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
ROMs
Alpha/Beta
None
Official
None
Unofficial
[ROM][SNOWCONE][oriole][12] StatiXOS v5.0
Apps/Mods/Scripts/Tethering/Themes
Tulsadiver's Mods
Stand alone Clock, Navbargone, etc. Mods
Quick Pull down Tile-Accent Colors
ADB Font Installer including the lockscreen clock
ADB Magisk Module Mod Maker
Other Mods
[MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Thread
aodNotify - Notification Light / LED for Pixel 6!
How-To Enable Two-Button Navigation on Android 12 (Root Required)!
Audio switcher
T.W.R.P. Backup/Restore
Waiting for Android 12 T.W.R.P.
Click to expand...
Click to collapse
C:\Users\Derek>fastboot flash boot C:\Users\Derek\Desktop\magisk_patched-23016_zt99Y.img
target reported max download size of 261095424 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.853s]
writing 'boot'...
FAILED (remote: partition (boot) not found)
finished. total time: 1.869s
This is the error i get. Even when trying the stock boot.img
What can i do to fix this?
deadliving said:
C:\Users\Derek>fastboot flash boot C:\Users\Derek\Desktop\magisk_patched-23016_zt99Y.img
target reported max download size of 261095424 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.853s]
writing 'boot'...
FAILED (remote: partition (boot) not found)
finished. total time: 1.869s
This is the error i get. Even when trying the stock boot.img
What can i do to fix this?
Click to expand...
Click to collapse
I'm assuming you have the latest version of SDK Platform-tools r. 31.0.3 installed on your computer, there are no typing errors on the command fastboot..., USB debugging is enabled, and fastboot.exe is in this folder:
C:\Users\Derek\Desktop
Try opening Command Prompt in this folder:
C:\Users\Derek\Desktop
Then type:
fastboot flash boot magisk_patched-23016_zt99Y.img to flash it.
After jan. Update my device when rebooting shows ypur device is corrupted before the unlocked bootloader screen warning is this normal? Wasnt there in dec. Update
Nightf0x_007 said:
After jan. Update my device when rebooting shows ypur device is corrupted before the unlocked bootloader screen warning is this normal? Wasnt there in dec. Update
Click to expand...
Click to collapse
No!
Curious, how did you update your phone?
Homeboy76 said:
No!
Curious, how did you update your phone?
Click to expand...
Click to collapse
This is how i updated to dec.
-Executed flash-all flashed bootloader & radio but didnt want to update the device
- fastboot update the image
- fastboot boot magisk patched image
- opened magisk and directly installed magisk
Nightf0x_007 said:
This is how i updated to dec.
-Executed flash-all flashed bootloader & radio but didnt want to update the device
- fastboot update the image
- fastboot boot magisk patched image
- opened magisk and directly installed magisk
Click to expand...
Click to collapse
"Executed flash-all flashed bootloader & radio but didnt want to update the device"
What?
Homeboy76 said:
"Executed flash-all flashed bootloader & radio but didnt want to update the device"
What?
Click to expand...
Click to collapse
Flash-all without -w
Nightf0x_007 said:
Flash-all without -w
Click to expand...
Click to collapse
Did you patch the boot.img with magisk-canary_23016?
Homeboy76 said:
Did you patch the boot.img with magisk-canary_23016?
Click to expand...
Click to collapse
Yes ofcourse, i might end up backing up my data and resetting and flash protonaosp
Update!
Magisk Canary 23017
@Homeboy76
Is this link correct?
Google Pixel 5 - LineageOS 18.1
LineageOS 18.1 Changelog for Google Pixel 5 (redfin). This page is listing the official LineageOS 18.1 (Android 11 11.0) changes and downloads for Google Pixel 5 (redfin).
www.lineageoslog.com
It points to Pixel 5
This step by step tutorial is all about
☆☆☆ FastbootD video tutorial : https://m.youtube.com/playlist?list=PLvggR4skCxYzhB3SXxpSx4LvRzGwx9k45Full round-trip of "GSIs flashing process".
Step to install Stock ROM with Fastboot ability.(need 3in1.tar)
Step to flash GSI on top of Stock ROM.
get rid of SU.which came with "bvS" or "bgS" Variant.(option if you want Magisk)
Step to update GSI without lost your data include magisk.
Step to Recovery back to the First Boot with Magisk (hidden).
<<Additional for PHH AOSP>>
Add Adaptive Auto-brightness for T225 (magisk module) here
Add Face Unlock. here
<< Additional for Stock SAM A13 based>>
Add Restore Samsung Knox features.(had lost from unlocked and root)
Add Advanced Setup New LeOS
ADD DUAL BOOT WITH Vega Bobo DSU Sideloader. (SAM Stock A13 Base) Example here:
**FastbootD Help.
fastboot commands
fastboot commands. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
--info--
Sam did not provided " fastboot mode" for all devices. only "Odin flashing tool".
What is the FasdtbootD?
What is FastbootD? How to Boot to FastbootD Mode
In this tutorial, we will explain you what is FastbootD Mode in Android, how to boot to FastbootD Mode and how to exit this mode.
www.droidwin.com
*Limitation of FastbootD
FastbootD not the same as regular "fastboot", impossible to use fastbootd without " Dynamic partition. etc., dynamic partitions are automatically created, resized, or deleted as needed.
*FastbootD has access in logical partition like Super Partition.
( have odm +product+vendor+system partition inside) , Because dynamic partitions are implemented in userspace, partitions needed by the bootloader can't be made dynamic. For example, boot, dtbo, and vbmeta are read by the bootloader, and so must remain as physical partitions.
then
You can't uses by fastbootD performed
Code:
fastboot --disable-verity flash vbmata vbmeta.img
✓ Not enough space to resize partition solution
Solution:
Removing stock system_ext and/or product from fastbootd is enough, like so:
***Don't uses this command
"fastboot delete-logical-partition product"
why ?
the product partition, with around 1.3GB in size isn’t even required by the GSIs.
then you can delete data on product partition.
*(Didn't delete product partition itself but deletes only data inside this partition , then android will auto-resize product'spartition.)
Do this.
Code:
adb reboot fastboot
Code:
fastboot erase product
set the size of the product partition to 0
Code:
fastboot resize-logical-partition product 0x0
To verify if the partition size has become 0.
Code:
fastboot getvar all
If one of the lines shows the below code, then the process is a success.
Code:
(bootloader) partition-size:product:0x0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or
>fastboot erase system_ext
>fastboot resize-logical-partition system_ext 0x0
---End Info--
Resource:
Basic knownledge.
my customAP tutorial.
** When using FastbootD you should knows
Set of fastbootd command.
-content-
Flashing Any GSIsUsing Fastboot without CustomAP 》Save your time.Example_use AOSP A13 from phhusson TrebleDroid GSI.
Complete Cycle From Fastboot Flashing >>>ROOT (Magisk,SU)>>Customized UI >>Update without Lost Data and Magisk.Requirement:
-Unlocked BootLoader
-(Recommend) Stock Firmware Update to A13 such as
"SM-T225XXU1CWA2" etc.,
Why? Used Android 13 GSIs.
1. MTP works
2. Offline Charging works
3. Google Assistant can call for you. (Ok Google call xxx) Stock A13 didn't do it.
etc.,
>Step to install Stock ROM together with Fastboot ability at the same time.
(clean install with stock firmware)
Extract AP Framework File for "recovery.img.lz4" and patch to add FastbootD ability. [ Download Attach file ] or patch by yourself here https://github.com/Johx22/Patch-Recovery.
Flash Stock Framework File with odin. (AP , BL, CP, CSC_not_home) + Magisk patch-boot & vbmeta & patch-recovery at (USERDATA Slot) ( include 3 patch-files to one tar file) [ Download Attach file ] -After reboot must connects internet and set "Developer options = enable OEM unlocking + USB debugging"
(Computer) Download and extract Platform tools to C:\ https://developer.android.com/studio/releases/platform-tools.
(Computer) Download and install Fastboot interface Driver. https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
Note:
1.you can dirty flash patched fastbootD-recovery at AP slot. When you had any firmware or gsi installed.
2.Howto magisk-patch (boot.img.lz4 + vbmeta.img.lz4). in General Section.
>Step to flash GSI on top of Stock ROM
Set of Command to install GSIs on top of Stock Firmware.
-Connect device with USB cable to Computer.
-Download your GSIs.
-Extract "GSI.img file into platform tools directory.
-open CMD inside the platform-tools folder and then type in the below command
** Check device was already connected with computer.
*** Check bootloader version (patched) is the same as your device's firmware.
0.
Code:
adb devices
1.
Code:
adb reboot fastboot
-Device will turn display into FastbootD mode
2.
Code:
fastboot erase system
option: if you founded ‘Not enough space to resize partition’) error.
Code:
fastboot delete-logical-partition product
3.
Code:
fastboot flash system gsi-filename.img
4. FastootD (pic below)Select "Enter recovery menu"
5.Recovery (pic below)
Select "wipe data/factory reset" menu
6. Recovery (pic above)
Select "reboot system now" menu
>>Finished " Flashing with FastbootD"<<
After installation.
- This variant was included with " PHH-SU".
>Step get rid of SU.(option if you want Magisk) (bvS or bgS variant)
adb shell Enter
su Enter
chmod +x /system/bin/phh-securize.sh Enter
/system/bin/phh-securize.sh Enter
* Device will auto reboot.
After this Magisk icon will show up.
Click Magisk icon to continue setup additional files and reboot.
-----------------------------------------------------------------
*Step to update GSI without lost your data include magisk.
*** (Recommended: use Magisk-Gapps, if you don't want to re-process install gapps again.)
Disable all magisk modules. (if you used another Launcher or Port it from another GSI , pleases uninstall it first.)
Flash New-Update-GSI with FastbootD
Code:
fastboot flash system new-gsi.IMG
then REBOOT System (No factory reset or wipe data)
Code:
fastboot reboot
After get rid of SU , magisk will show up.
get rid of SU
Code:
adb shell
Code:
su
Code:
chmod +x /system/bin/phh-securize.sh
Code:
/system/bin/phh-securize.sh
Note: After this magisk will works again. (with all modules you had installed .)
===End of Update Version info===
Scripts by phhusson to automatically build/CI/Release TrebleDroid GSI
more than 2 times per month
Then I write this easy additional way to update without lost your data..
>Step to Recovery back toThe First Boot with Magisk (hidden installed).
1.Run Factory Reset From Recovery by press and hold (Power+ Vol down)
2. Connect internet and enable Developer options.
3. Enable OEM unlocking & USB debugging.
4. Reboot after that Magisk setting icon will show up again.
--End update--
Happy Chinese New Year!General Section
** Compared 2 projects
** Restore Samsung Knox features.
✓ How to create Magisk patch for boot.img + vbmeta.img
extract (vbmeta.img.lz4 + boot.img.lz4) from your AP Stock
create compress one file xxx .tar with 7zip
move (vbmeta.img.lz4 + boot.img.lz4).tar (xxx.tar) to tab a7 lite
install magisk.apk on you tab a7 lite
patch the tar file. (with magisk manager)
result magisk-patch file at Tab a7 :-Download folder.
✓ Howto install fastboot driver.
How to Install Fastboot Drivers in Windows 11
In this comprehensive tutorial, we will show you the detailed steps to install the Fastboot Drivers onto your Windows 11 PC
www.droidwin.com
✓ [Add pre-patch-recovery-FastbootD]
*** S2 = can't downgrade (Android version) even firmware version.
SM-T220 A13SM-T225 A13SM-T 227U A13SM-T 225N A13T220XXS2CWA7T225XXS2CWA8T227UVLU3CVLAT225NKOU1CWA3T220XXU1CWA2T225XXS2CWA6T220XXU1CWA1T225XXU1CWA2T220XXU1CVL7T225XXU1CVL6T220XXU1CVL5T225XXU1CVL5T220XXS2CWA8T225XXU2CWB3
✓ Howto install "adb &fastboot" on PC
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
You should also replace your adb with the latest binaries by Google.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the platform tools for windows zip file. Find out where your current adb.exe file is located. Extract the zip into that location, overwrite the old file(s).
Note: Don't delete any files from platform-tools
>>>>>>>>>>>>>>
√ Download:
Where are New AOSP A13 official?
Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations
github.com
Note: (Read/Write System should uses variant "vndklite".)
✓Changes PHH-SU to Magisk.
- Connect device with your computer. run below command.
Code:
adb shell Enter
su Enter
chmod +x /system/bin/phh-securize.sh Enter
/system/bin/phh-securize.sh Enter
May be didn't found phh-securize.sh only uses root file manager deleted "/system/xbin/su"
√ You can install "GAPPS" by adb shell or by Magisk-Gapps module.
(Cause we didn't have TWRP, but don't worry about TWRP.)
*install Bromite Systemwebview
*Vega Bobo DSU Sideloader (Root mode with magisk)
*this firmware can't downgrade.**S2**T225XXS2CWA6 , it will no longer be possible to roll back even to the previous firmware .
( A13"SM-T225XXU1CWA2)
* Add some T220 FastbootD -Recovery-patch
Reserved:
Option tools for customize your AOSP GSI.
Install Gapps modules with Magisk. ( For Android 13)DOWNLOAD: https://litegapps.site/index.html
CLICK NAME FOR DOWNLOAD
1. [MAGISK]LiteGapps_Nano_arm64_13.0_v2.8_official.zip (Base)
2. GoogleSearch_LiteGapps_Addon_arm64_13.0.zip. (add-on)
3. GoogleAssistant_LiteGapps_Addon_arm64_13.0.zip. (add-on)
Note: you can add add-on mod from here.
STEP. ( with magisk manager )
Flash 1 and Reboot
Flash 2 and Reboot
Flash 3 and Reboot
How to configure Google Assistant . ( For make a call )
-Set Default Digital Assistant.
Open Setting and Search with keyword " digital assistant or assistant"
-Configure OK Google.
Open Setting 》Google 》Setting for Google apps 》Search Assistant & Voice 》 Google Assistant 》Hey Google & Voice match
ENABLE Hey Google.
tom.android said:
You can install "GAPPS" by adb shell .
Click to expand...
Click to collapse
Where can I download a compatible package and what command besides adb shell do I have to run in order to install?
nirogu325 said:
Where can I download a compatible package and what command besides adb shell do I have to run in order to install?
Click to expand...
Click to collapse
readme inside archrive.
tom.android said:
readme inside archrive.
Click to expand...
Click to collapse
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
1. install root explorer app. (such as Mixplorer)
2. create directory "gapps" or anyname at /data
such as /data/gapps
3. extract archrive " TitaTheGapps.zip" to dir from 2
4. open terminal adb shell ----then su then
cd /data/gapps/tita
chmod +x ./installer.sh
5. add more space for new gapps by delete some unuseful from "/system/system_ext/apex"
Del "android.vndk.v.28,29,30,32 keep only v31
6. run script---> sh ./installer.sh
note you can use command "mount -o rw,remount /system" or used root explorer do it. (changes RO to RW) before mod system.
nirogu325 said:
The readme only leads me to the package's website which does not tell me which specific command I have to run after adb shell. I then went to the Telegram group which basically tells me this: "adb root then adb shell or adb shell then su" and then "just run the script" Uh-huh. How do I run the script? "running it".
Click to expand...
Click to collapse
Here is what I did to install GApps on AOSP A13:
Get TheGappsInstaller-Tita archive here: https://github.com/ChonDoit/TheGappsInstaller/releases/tag/Tita (specifically: TitaTheGapps_Terminal_20221225.tar.xz)
Extract the tar archive from the tar.xz file
Follow instructions below (credits: ozmage)
adb push TitaTheGapps_Terminal_20221225.tar /sdcard/Download
adb root
adb shell
cd /data
mkdir GAPPS
mv /sdcard/Download/TitaTheGapps_Terminal_20221225.tar GAPPS
cd GAPPS
tar xvpf TitaTheGapps_Terminal_20221225.tar
cd TitaTheGapps_Terminal_20221225
chmod a+x ./installer.sh
sh ./installer.sh
tom.android said:
1. install root explorer app. (such as Mixplorer)
2. create directory "gapps" or anyname at /data
such as /data/gapps
3. extract archrive " TitaTheGapps.zip" to dir from 2
Click to expand...
Click to collapse
dapr0b said:
Here is what I did to install GApps on AOSP A13:
Get TheGappsInstaller-Tita archive here: https://github.com/ChonDoit/TheGappsInstaller/releases/tag/Tita (specifically: TitaTheGapps_Terminal_20221225.tar.xz)
*instructions*
Click to expand...
Click to collapse
Thank you both, THAT is real support.
Update: Howto update GSI without lost your data.
Update.
Flashing Any GSIsUsing Fastboot without CustomAP any longer.
tom.android said:
Update.Flashing Any GSIsUsing Fastboot without CustomAP any longer.
Click to expand...
Click to collapse
Thank you.
I have one question though.
My tab is already updated to SM-T225XXU1CWA2. In the firs step, can I just simply flash with ODIN your attached fastbootd-recovery.tar in AP slot and the 3-in-1.tar in USERDATA slot without including the stock framework file (AP, BL, CP, CSC)?
jtrakx said:
Thank you.
I have one question though.
My tab is already updated to SM-T225XXU1CWA2. In the firs step, can I just simply flash with ODIN your attached fastbootd-recovery.tar in AP slot and the 3-in-1.tar in USERDATA slot without including the stock framework file (AP, BL, CP, CSC)?
Click to expand...
Click to collapse
1. flash only 3in1.tar at AP slot. (magisk 25.2 + vbmeta + recovery-patch)
-install gsi
2. remove SU by
adb shell Enter
su Enter
bra bra bra
look at my tutorial
tom.android said:
1. flash only 3in1.tar at AP slot. (magisk 25.2 + vbmeta + recovery-patch)
2. remove SU by
adb shell Enter
su Enter
bra bra bra
look at my tutorial
Click to expand...
Click to collapse
Thank you. That's a big help.
update iconify v6.0 (extract zip file run iconify.apk ) or update from app.
Iconify • Customize Boring Android UI
Updated to v6.0.0
What's new?
• Custom battery color
• Semi Transparent Brightness bar style
• Semi Transparent QS tile style
• Semi Transparent Notification style
• 5 styles of volume panel
• Improved UI roundness
XPosed Menu: (LSPosed recommended)
• Transparent Qs Panel (Supports more rom)
• Window Level Blur and Force blur enabler for unsupported ROMs
• Vertical QS tiles
• Custom header image (GIF supported)
• Custom header clocks
• Custom lockscreen clocks (custom font supported)
• Clock and status icons background chip
Full Changelog: Click Here
Teamfly Launcher (Didn't test)
TeamFiles Launcher
A launcher which aims to provide stability, speed & customizationMore info at github.com/TeamFiles/TeamFiles-LauncherJoin t.me/loopprojects to get more updates!
store.kde.org
May be compatible with quick switch of OneUI 5.
I also have a question, is this only for SM-T225XXU1CWA2 only ? or T220 can do this too . I have T220 XAR us version android 13 gsi pixel Experience plus with magisk. I want to install fastbootD and install gsi without custom AP.. do I use this guide?
abc1054 said:
I also have a question, is this only for SM-T225XXU1CWA2 only ? or T220 can do this too . I have T220 XAR us version android 13 gsi pixel Experience plus with magisk. I want to install fastbootD and install gsi without custom AP.. do I use this guide?
Click to expand...
Click to collapse
yes u can , extract AP file>>recovery.img.lz4. boot.img.lz4. vbmeta.img.lz4. upload here if you can't patch.
Can you explain how to patch it. Thanks
abc1054 said:
Can you explain how to patch it. Thanks
Click to expand...
Click to collapse
1.boot.IMG.lz4. 2. vbmeta.IMG.lz4. patch with magisk
2.recovery.IMG.lz4. patch follow with https://github.com/Johx22/Patch-Recovery
tom.android said:
yes u can , extract AP file>>recovery.img.lz4. boot.img.lz4. vbmeta.img.lz4. upload here if you can't patch.
Click to expand...
Click to collapse
Here is my files