Related
{
"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"
}
THIS WILL NOT WORK ON AMAZFIT PACE, STRATOS OR STRATOS3
THIS WILL NOT WORK ON AMAZFIT PACE, STRATOS OR STRATOS3
THIS WILL NOT WORK ON AMAZFIT PACE, STRATOS OR STRATOS3
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
The unlock system doesn't allow WOS (Watch Operating System) 3.0 ROM versions yet, so you need to use any other valid WOS 2.0 ROM version like 2.6.4.1 or 2.0.43.1.Supported devices: A1801 (Chinese) and A1811 (English)
Properly installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original English Firmware with OTA updates.
Click to expand...
Click to collapse
[MENTION]Neur_User[/MENTION] for PACEfied, STRATOSfied projects and other stuff
[MENTION]Cracklydisc[/MENTION] for AmazIT, StratOS projects and other stuff
Capara [MENTION]1mmortal[/MENTION] for his great support and collaboration
@Nacken and @To+ for collaborating
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues)
4. Wait to the end of the process and don't touch anything
Alternative firmware and OTA installers since v3.2.6.0. Check for More info link of Downloads section.
********************************************************
US Verge 3.2.2.0 Stock Firmware Installer by Saratoga
********************************************************
0. Rebooting adb server
*************************
*****************************
1. Connect the watch to PC
*****************************
*******************************
2. Rebooting to Fastboot mode
*******************************
****************************
3. Checking the connection
****************************
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.463s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.562s
***********************************
5. Waiting connection in Recovery
***********************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.267s)
system.img.gz: 1 file pushed. 4.9 MB/s (332793308 bytes in 65.424s)
md5s.txt: 1 file pushed. 0.1 MB/s (91 bytes in 0.001s)
flash_rom.sh: 1 file pushed. 0.4 MB/s (458 bytes in 0.001s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.651994 seconds, 5.4MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 101.353872 seconds, 8.1MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
***********************************
10. Changing language to English
***********************************
List of devices attached
d41e250a device
***************************************************
Stock Recovery and Bootloader installation process
***************************************************
********************************
11. Rebooting to Fastboot mode
********************************
***************************
12. Booting temporal root
***************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.373s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.426s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.005s)
recovery.img: 1 file pushed. 2.0 MB/s (16777216 bytes in 8.153s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.9 MB/s (964968 bytes in 0.312s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Done. OTA updates should now work.
*************************
15. Flashing Bootloader
*************************
1884+1 records in
1884+1 records out
964968 bytes (942.4KB) copied, 0.131429 seconds, 7.0MB/s
********************
16. Removing files
********************
***************
17. Rebooting
***************
************
18. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Latest version
Stock US/Global/International Firmware Installer 3.2.7.5 with OTA updates | More Info
Previous versions
Stock US/Global/International Firmware Installer 3.2.7.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.6.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.5.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.4.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.3.0 with OTA updates | More Info
Stock US/Global/International Firmware Installer 3.2.2.0 with OTA updates | Mirror | More Info
Stock US/Global/International Firmware Installer 3.2.1.0 with OTA updates | Mirror
Stock US/Global/International Firmware Installer 3.2.0.13 with OTA updates | Mirror
Stock US/Global/International Firmware Installer 3.2.0.7 with OTA updates | Mirror
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual Installation Method
Manual Installation Method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in Post #1.
Unbrick
If your watch is stuck on Amazfit A logo and it doesn't boot, you will need to boot into fastboot manually using the button trick based on this thread:
Watch always connected into PC
Start with same steps of pushing-releasing the button as the video guide
But, when screen goes off, count until "6 mississippis" while screen is off and then release the button, it should be done before Amazfit logo shows
Push the button again to enter fastboot mode
Check fastboot connection as stated on Step #3
5.1 If fastboot devices command doesn't work and you get waiting for device string, that happened to me, disconnect the watch and reconnect to PC again
Now, download and unzip this UNBRICK file, and run UNBRICK_US.bat if you are on Windows PC, or just starting on Step #3 of the manual commands.
Manual commands
On your terminal, go to the path where all the files were unzipped and you are good to go.
Manual command installation
You can copy and paste all needed commands.
Firmware installation
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery-mod.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.426s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.303s
5. Wait until you get a triangle with an exclamation mark (!) in your watch
6. Copy the files to the watch (it may take upto a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
adb push boot.img /data/media/0/
7546 KB/s (9437184 bytes in 1.221s)
adb push system.img.gz /data/media/0/
7194 KB/s (228153632 bytes in 30.969s)
adb push md5s.txt /data/media/0/
88 KB/s (91 bytes in 0.001s)
adb push flash_rom.sh /data/media/0/
297 KB/s (458 bytes in 0.001s)
7. Start Firmware installation (it may take up to 2 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.953804 seconds, 9.4MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 89.945101 seconds, 9.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to English language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US[/COLOR]
Stock recovery installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-US-adb-root.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.349s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.206s
13. Copy stock recovery files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/[/COLOR]
Output (or similar)
Code:
[100%] /data/media/0/install_recovery.sh
[100%] /data/media/0/recovery.img
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Or if above command doesn't work, do it in 2 commands
Code:
[COLOR="blue"]adb shell cd /data/media/0/
adb shell sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 2.461221 seconds, 6.5MB/s
Done. OTA updates should now work.
15 . Delete stock recovery installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img [/COLOR]
16. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
17. Finish.
Go to Amazfit app and update to latest version.
Some extra useful commands
Wipe dalvik/cache
Code:
[COLOR="blue"]adb shell reboot bootloader
fastboot erase cache
fastboot reboot[/COLOR]
Do a Factory Reset (You will lose all the data in your watch. Unpair the watch from Amazfit app while doing this?
Code:
[COLOR="Blue"]adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot reboot[/COLOR]
Reserved 1
Reserved 1
Thanks for the nice work. Has anyone tried it yet? I want to buy chinese version, so i want to know if this will work?
anaragayevafr said:
Thanks for the nice work. Has anyone tried it yet? I want to buy chinese version, so i want to know if this will work?
Click to expand...
Click to collapse
All excellent! Many users with 4PDA sewed from 1801 to 1811. But not yet updated on OTA to 3.2.0.6
Is it the same method on YouTube which converts 70-80% or this is new?
anaragayevafr said:
Is it the same method on YouTube which converts 70-80% or this is new?
Click to expand...
Click to collapse
This is full official firmware.
Saratoga79 said:
This is full official firmware.
Click to expand...
Click to collapse
I've tried but ... I must have the bootloader blocked because I get this message in step # 4:
********************************************************
US Verge 3.2.0.5 Stock Firmware Installer by Saratoga
********************************************************
1. Connect the watch to the PC
********************************
* daemon not running; starting now at tcp:5037
* daemon started successfully
*******************************
2. Rebooting to Fastboot mode
*******************************
****************************
3. Checking the connection
****************************
****************************
4. Booting modded recovery
****************************
< waiting for device >
downloading 'boot.img'...
FAILED (remote: ED: The command is not allowed.)
finished. total time: 0.023s
***********************************
5. Waiting connection in Recovery
***********************************
Click to expand...
Click to collapse
My Amazfit Verge is A1801 fw. 3.0.13.0
Very thanks
luacu said:
I've tried but ... I must have the bootloader blocked because I get this message in step # 4:
My Amazfit Verge is A1801 fw. 3.0.13.0
Very thanks
Click to expand...
Click to collapse
Yes, unlock the bootloader first.
Saratoga79 said:
Yes, unlock the bootloader first.
Click to expand...
Click to collapse
Ok, unlocked and all OK. Thank you very much for everything.
Te debo una
I just tried to go through the unlock procedure via the website. However it doesn't accept the OS version I point to. What am I missing?
All good
tried and everything is fine , thanks a lot
---------- Post added at 02:49 AM ---------- Previous post was at 02:44 AM ----------
Sash! said:
I just tried to go through the unlock procedure via the website. However it doesn't accept the OS version I point to. What am I missing?
Click to expand...
Click to collapse
you need to use the amazfit pace or stratos watch os version like this 2.6.4.1
Yes, the unlock system doesn't allow WOS (Watch Operating System) 3.0 ROM versions, so you need to use any other valid WOS 2.0 ROM version like 2.6.4.1 or 2.0.43.1.
Hi guys,and after this method of rebranding someone flew update OTA? I have information from the resource 4PDA that update 3.2.0.6 arrives for the owners of the global version, but the OTA I have not yet arrived after the rebranding. The question to the topic starter, at the end of the rebranding procedure, do you need to block the bootloader, as in smartphones?
lanch84 said:
Hi guys,and after this method of rebranding someone flew update OTA? I have information from the resource 4PDA that update 3.2.0.6 arrives for the owners of the global version, but the OTA I have not yet arrived after the rebranding. The question to the topic starter, at the end of the rebranding procedure, do you need to block the bootloader, as in smartphones?
Click to expand...
Click to collapse
I have a global version of the Verge and didn't receive the 3.2.0.6 update yet, so maybe just wait a little more.
Aximal said:
you need to use the amazfit pace or stratos watch os version like this 2.6.4.1
Click to expand...
Click to collapse
Thank you so much!
The unlock code arrived instantly and the flash procedure worked like charm.
Interestingly, the Settings menu title is still in Chinese.
Also, Mi Home, the Maps app and the vo8ce assistant are not there.
Also - quite a pity it is not NFC enabled as advertised back in september.
Going fine until step
echo ***************************
echo 12. Booting temporal root
echo ***************************
fastboot.exe boot boot-US-adb-root.img
Then fastboot refused to make the phone reboot. Have to reboot the phone and manual execute the rest of the commands.
Ota update to 3.2.0.7 install errer
lanch84 said:
Hi guys,and after this method of rebranding someone flew update OTA? I have information from the resource 4PDA that update 3.2.0.6 arrives for the owners of the global version, but the OTA I have not yet arrived after the rebranding. The question to the topic starter, at the end of the rebranding procedure, do you need to block the bootloader, as in smartphones?
Click to expand...
Click to collapse
Update to 3.2.0.6 was a Dev/Beta versión so only few people received the OTA. But it's tested that OTA update from 3.2.0.5 -> 3.2.0.6 worked fine.
apollow2007 said:
Going fine until step
echo ***************************
echo 12. Booting temporal root
echo ***************************
fastboot.exe boot boot-US-adb-root.img
Then fastboot refused to make the phone reboot. Have to reboot the phone and manual execute the rest of the commands.
Click to expand...
Click to collapse
And what was the output of the installer on that step? Well, If at least you managed to install the stock recovery manually you are good to go.
tinn44 said:
Ota update to 3.2.0.7 install errer
Click to expand...
Click to collapse
Do you have the update.zip OTA file on your phone's internal memory or on your watch? Seems to be a around 200MB update.
Btw, did you get any issue when installing stock recovery? OTA update from 3.2.0.5 -> 3.2.0.6 worked fine.
Still no OTA update here.
Saratoga79 said:
And what was the output of the installer on that step? Well, If at least you managed to install the stock recovery manually you are good to go.
Click to expand...
Click to collapse
The output of boot recovery is
downloading 'boot.img'...
OKAY [ 0.349s] FAILED (status read failed (Too many links))
No "booting" message. So I have to manually reboot the watch and re-issue the command again.
May be my laptop environment issue. But I managed to follow up with all the commands manually and finished the flash. The English ROM is much more zippy than the CN rom without the Xiaomi Voice Assistance hogging the CPU. No NFC, Mi Home and map functionality. Not surprise though as those are limited to China market.
{
"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"
}
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
Supported devices: A1928 (Chinese) and A1929 (English)
Property installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original English Firmware
Click to expand...
Click to collapse
Multi lingual support
OTA updates
Click to expand...
Click to collapse
@Neur_User for STRATOSfied Rom and other stuff
@Cracklydisc for original script and other stuff
@1immortal for his support
@Jaz, contributors and collaborators in Telegram group.
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues).
4. Wait to the end of the process and don't touch anything.
Installation output
*************************************************************
Stratos 3 US 4.2.3.0 Stock Firmware Installer by Saratoga
*************************************************************
0. Restarting adb server
***************************
**********************************
1. Connect the watch to the PC
**********************************
**********************************
2. Rebooting to Fastboot mode
**********************************
******************************
3. Checking the connection
******************************
*******************************
4. Booting modded recovery
*******************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.450s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.678s
***************************************
5. Waiting for connection in Recovery
***************************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.264s)
system.img.gz: 1 file pushed. 5.0 MB/s (438606404 bytes in 84.087s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.003s)
flash_rom.sh: 1 file pushed. 0.1 MB/s (458 bytes in 0.006s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.836843 seconds, 4.9MB/s
Flashing system.img
287744+0 records in
287744+0 records out
1178599424 bytes (1.1GB) copied, 156.970842 seconds, 7.2MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
**********************************
10. Changing language to English
**********************************
****************************************************
Stock Recovery and Bootloader installation process
****************************************************
********************************
11. Rebooting to Fastboot mode
********************************
****************************
12. Booting temporal root
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.368s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.572s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.009s)
recovery.img: 1 file pushed. 1.6 MB/s (16777216 bytes in 10.082s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.2 MB/s (894764 bytes in 0.387s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.908566 seconds, 8.4MB/s
Done. OTA updates should now work.
*************************
15. Flashing Bootloader
*************************
1747+1 records in
1747+1 records out
894764 bytes (873.8KB) copied, 0.695597 seconds, 1.2MB/s
*******************
16. Removing files
*******************
***************
17. Rebooting
***************
************
18. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
VERY IMPORTANT:
Don't do a factory reset in fastboot or you will brick the watch. Just run FCT_RST_STOCK.bat or use these commands instead.
Method 1:
Code:
adb reboot wipe
Method 2 (Only if watch is fully booted and you are rooted):
Code:
adb shell am broadcast -a android.intent.action.MASTER_CLEAR
Click to expand...
Click to collapse
Latest Version
Stock US/International/Global 4.2.8.0 Firmware Installer with OTA updates | OTA 4.2.7.0 -> 4.2.8.0 Installer | More info
Previous Versions
Stock US/International/Global 4.2.7.0 Firmware Installer with OTA updates | OTA 4.2.6.0 -> 4.2.7.0 Installer | More info
Stock US/International/Global 4.2.6.0 Firmware Installer with OTA updates | OTA 4.2.5.0 -> 4.2.6.0 Installer | More info
Stock US/International/Global 4.2.5.0 Firmware Installer with OTA updates | OTA 4.2.4.0-> 4.2.5.0 Installer | More info
Stock US/International/Global 4.2.4.0 Firmware Installer with OTA updates | OTA 4.2.3.0-> 4.2.4.0 Installer | More info
Stock US/International/Global 4.2.3.0 Firmware Installer with OTA updates | OTA 4.2.2.1 -> 4.2.3.0 Installer | More info
Stock US/International/Global 4.2.2.1 Firmware Installer with OTA updates
OTA 4.2.0.1 -> 4.2.6.0 Installer | More info
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual installation method
Manual installation method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in first post.
On your terminal, go to the path where all the files were unzipped, or if you are running a Windows OS, just run terminal_cmd.bat and you are good to go.
OTA Installation
Download OTA installer from Post #1 and if you are running a Windows PC, run terminal_cmd.bat, or any other command/terminal window on your PC in the root of the unzipped folder.
Copy the update to the watch
Code:
[COLOR="Blue"]adb push update.zip /sdcard
[/COLOR]
And launch the update
Code:
[COLOR="blue"]adb reboot update[/COLOR]
Wait to the end of the update, and when the watch reboots delete the update file
Code:
[COLOR="blue"]adb shell rm /sdcard/update.zip[/COLOR]
Firmware installation
On your terminal, go to the path where all the Firmware files were unzipped.
You can copy and paste all needed commands.
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery_mod.img[/COLOR]
Output (or similar)
Code:
Downloading 'boot.img' OKAY [ 0.450s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.678s
5. Wait until you get a triangle with an exclamation mark in your watch
6. Copy the files to the watch (it may take up to a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.264s)
system.img.gz: 1 file pushed. 5.0 MB/s (438606404 bytes in 84.087s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.003s)
flash_rom.sh: 1 file pushed. 0.1 MB/s (458 bytes in 0.006s)
7. Start Firmware installation (it may take up to 4 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.836843 seconds, 4.9MB/s
Flashing system.img
287744+0 records in
287744+0 records out
1178599424 bytes (1.1GB) copied, 156.970842 seconds, 7.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to English language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US[/COLOR]
Stock Recovery and Bootloader installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-US-adb-root.img[/COLOR]
Output (or similar)
Code:
Downloading 'boot.img' OKAY [ 0.368s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.572s
13. Copy stock Recovery and Bootloader files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/
adb push u-boot-with-spl-mbr-gpt.bin /data/media/0/[/COLOR]
Output (or similar)
Code:
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.009s)
recovery.img: 1 file pushed. 1.6 MB/s (16777216 bytes in 10.082s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.2 MB/s (894764 bytes in 0.387s)
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.908566 seconds, 8.4MB/s
Done. OTA updates should now work.
15. Flash Bootloader
Code:
[COLOR="blue"]adb shell busybox dd if=/data/media/0/u-boot-with-spl-mbr-gpt.bin of=/dev/block/mmcblk0[/COLOR]
Output (or similar)
Code:
1747+1 records in
1747+1 records out
894764 bytes (873.8KB) copied, 0.695597 seconds, 1.2MB/s
16 . Delete stock recovery and Bootloader installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img
adb shell rm /data/media/0/u-boot-with-spl-mbr-gpt.bin
[/COLOR]
17. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
18. Finish.
Go to Amazfit app and update to latest version.
Ultra Mode Resources
Since this firmware installer, I'm adding a new script to manage Ultra Mode resources.
If rebooting into Ultra mode doesn't work or you just get a black screen, run mcu_US.bat when you are in Smart Mode to fix it. This will update all needed files relating to Ultra Mode.
Manual commands
Open a command terminal window in the root of the installer folder and use:
Code:
[COLOR="Blue"]adb push mcu\. /sdcard/firmware
adb shell mcu_res_upgrade -r /sdcard/firmware -z /sdcard/firmware
adb shell check_mcu_res_upgrade.sh
adb shell rm -r /sdcard/firmware
adb reboot[/COLOR]
Some extra useful commands
Factory Reset
VERY IMPORTANT:
Don't do a factory reset in fastboot or you will brick the watch
You can factory reset your watch by:
Code:
[COLOR="Blue"]adb reboot wipe[/COLOR]
When it's done, the watch will turn off.
Launch pairing QR code
You can use:
Code:
[COLOR="Blue"]adb shell am start -n com.huami.watch.setupwizard/.InitPairQRActivity[/COLOR]
Reboot into Ultra mode
You can reboot into Ultra mode by:
Code:
[COLOR="blue"]adb reboot mcu[/COLOR]
Mio1
Mio1
Thank YOu! YOu are Amazfit lord and our savior
Can YOu make firmware with system zip?
arnisv said:
Can YOu make firmware with system zip?
Click to expand...
Click to collapse
What do you exactly mean?
Stock US/Global/International 4.2.3.0 Firmware Installer with OTA updates
Stock US/Global/International 4.2.3.0 Firmware Installer with OTA updates
Firmware Downloads
Stock US/Global/International 4.2.3.0 Firmware Installer with OTA updates
OTA 4.2.2.1 -> 4.2.3.0 Installer
This installer is for those who are on 4.2.2.1 and didn't get 4.2.3.0 OTA and want to update. Only adb/fastboot drivers are needed, unlocked bootloader is not needed as this is an official update.
Unzip the .zip file and run INSTALL_OTA_US.bat.
OTA Downloads
OTA 4.2.2.1 -> 4.2.3.0 Installer
Changelog
Check attachment.
Hi
Thanks Saratoga I updated 4.2.3.0 only OTA unfortunately wifi in watch still not working :crying:, do you know reason what could be wrong?
Stock US/Global/International 4.2.4.0 Firmware Installer with OTA updates
Stock US/Global/International 4.2.4.0 Firmware Installer with OTA updates
Firmware Downloads
Stock US/Global/International 4.2.4.0 Firmware Installer with OTA updates
OTA 4.2.3.0 -> 4.2.4.0 Installer
This installer is for those who are on 4.2.3.0 and didn't get 4.2.4.0 OTA and want to update. Only adb/fastboot drivers are needed, unlocked bootloader is not needed as this is an official update.
Unzip the .zip file and run INSTALL_OTA_US.bat.
OTA Downloads
OTA 4.2.3.0 -> 4.2.4.0 Installer
Ultra Mode Resources
Since this firmware installer, I'm adding a new script to manage Ultra Mode resources.
If rebooting into Ultra mode doesn't work or you just get a black screen, run mcu_US.bat when you are in Smart Mode to fix it. This will update all needed files relating to Ultra Mode.
Manual commands
Open a command terminal window in the root of the installer folder and use:
Code:
[COLOR="Blue"]adb push mcu\. /sdcard/firmware
adb shell mcu_res_upgrade -r /sdcard/firmware -z /sdcard/firmware
adb shell check_mcu_res_upgrade.sh
adb shell rm -r /sdcard/firmware
adb reboot[/COLOR]
Changelog
Check attachment.
Great post,
Question for Ultra mode. Can i fix ultra mode if i don't have unlocked bootloader? I gor update on regular way, but ultra mode is not working.
maksic.jovan said:
Great post,
Question for Ultra mode. Can i fix ultra mode if i don't have unlocked bootloader? I got update on regular way, but ultra mode is not working.
Click to expand...
Click to collapse
Yes, you can. Just use the commands from the post above or the .bat installer for Ultra Mode resources, and see if that helps.
Sorry Saratoga, I'm lost. Which firmware is newer?
CN 4.0.4.15 or US 4.2.4.0?
Because by the number I think it must be the US, but it's strange that a Chinese product has US firmware newer than the CN one's ?
Mormy said:
Sorry Saratoga, I'm lost. Which firmware is newer?
CN 4.0.4.15 or US 4.2.4.0?
Because by the number I think it must be the US, but it's strange that a Chinese product has US firmware newer than the CN one's
Click to expand...
Click to collapse
CN 4.0.14.5 is from January 17th, US 4.2.4.0 is older.
Hello, I bought in China a stratos 3 and was surprised to find that, unlike what i saw on official webbsites, only chinese language was available. I am then looking for a way to install the international version. It seems this thread can allow me to do it.
I have a question however, what is an unlocked bootloader ?
Thanks in advance.
Thanks
hi
i have problem with ultra mode. I run script but still nothing i got output:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
mcu\.\: 3 files pushed. 3.3 MB/s (5697818 bytes in 1.633s)
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=127,oldZikuVer=17
try to upgrade res
...
...
what i am doing wrong? :/
maksic.jovan said:
hi
i have problem with ultra mode. I run script but still nothing i got output:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
mcu\.\: 3 files pushed. 3.3 MB/s (5697818 bytes in 1.633s)
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=127,oldZikuVer=17
try to upgrade res
...
...
what i am doing wrong? :/
Click to expand...
Click to collapse
And what else after "try to upgrade res"?
That output is normal, don't worry about those fails messages.
If you still have issues, try using another stock watchface in Smart mode and before you reboot into Ultra mode, ensure watch and Amazfit app are correctly connected because I've faced strange Ultra mode behaviour if watch was not connected to the app. Also disable all widgets in Amazfit app before rebooting into Ultra.
My output when installing Ultra mode resources in my CN ROM:
Code:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
mcu\.\: 3 files pushed. 2.5 MB/s (5697818 bytes in 2.195s)
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=129,oldZikuVer=17
try to upgrade res
upgrade res successfully
try to upgrade ziku
upgrade ziku successfully
*********************************
4. Checking Ultra Mode resources
*********************************
/etc/firmware/ui_res.bin /etc/firmware/ziku_res.bin /etc/firmware/mcu_res.desc
verify upgrade file successful
res_path=/etc/firmware/ui_res.bin,ziku_path=/etc/firmware/ziku_res.bin
newResVer=129,newZikuVer=17,oldResVer=127,oldZikuVer=17
try to upgrade res
upgrade res successfully
********************
5. Removing files
********************
***************
6. Rebooting
***************
************
7. Finish
************
Presione una tecla para continuar . . .
Saratoga79 said:
And what else after "try to upgrade res"?
That output is normal, don't worry about those fails messages.
If you still have issues, try using another stock watchface in Smart mode and before you reboot into Ultra mode, ensure watch and Amazfit app are correctly connected because I've faced strange Ultra mode behaviour if watch was not connected to the app. Also disable all widgets in Amazfit app before rebooting into Ultra.
Click to expand...
Click to collapse
complete output:
Code:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
cannot stat 'mcu\.': No such file or directory
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=127,oldZikuVer=17
try to upgrade res
upgrade res successfully
try to upgrade ziku
upgrade ziku successfully
*********************************
4. Checking Ultra Mode resources
*********************************
/etc/firmware/ui_res.bin /etc/firmware/ziku_res.bin /etc/firmware/mcu_res.desc
verify upgrade file successful
res_path=/etc/firmware/ui_res.bin,ziku_path=/etc/firmware/ziku_res.bin
newResVer=127,newZikuVer=17,oldResVer=127,oldZikuVer=17
********************
5. Removing files
********************
***************
6. Rebooting
***************
************
7. Finish
************
Press any key to continue . . .
watch restart and nothing happens. I use default watch face, and it's connected to amazfit app. also i try to reinstall ROM (from option in watch itself). Nothing helps...
Also i get firmware update via Amazfit app, so absolutely everything is original and stock.
maksic.jovan said:
complete output:
Code:
******************************************************************
Stratos 3 US 4.2.4.0 Ultra Mode Resources Installer by Saratoga
******************************************************************
0. Restarting adb server
**************************
********************************
1. Connect the watch to the PC
********************************
******************
2. Copying files
******************
cannot stat 'mcu\.': No such file or directory
**********************************
3. Updating Ultra Mode resources
**********************************
res_path=/sdcard/firmware,ziku_path=/sdcard/firmware
res:read byte from file fail,only -1 length
ziku:read byte from file fail,only -1 length
newResVer=0,newZikuVer=0,oldResVer=127,oldZikuVer=17
try to upgrade res
upgrade res successfully
try to upgrade ziku
upgrade ziku successfully
*********************************
4. Checking Ultra Mode resources
*********************************
/etc/firmware/ui_res.bin /etc/firmware/ziku_res.bin /etc/firmware/mcu_res.desc
verify upgrade file successful
res_path=/etc/firmware/ui_res.bin,ziku_path=/etc/firmware/ziku_res.bin
newResVer=127,newZikuVer=17,oldResVer=127,oldZikuVer=17
********************
5. Removing files
********************
***************
6. Rebooting
***************
************
7. Finish
************
Press any key to continue . . .
watch restart and nothing happens. I use default watch face, and it's connected to amazfit app. also i try to reinstall ROM (from option in watch itself). Nothing helps...
Also i get firmware update via Amazfit app, so absolutely everything is original and stock.
Click to expand...
Click to collapse
What does it happen to you exactly? Blank screen in Ultra? Or what?
1. I would wait for a next OTA update as it will install/update Ultra resources during firmware update.
2. You could unlock the bootloader, warranty will be void, and install an older firmware version and check if after updating to latest version everything works fine.
3. Claim for warranty.
Saratoga79 said:
What does it happen to you exactly? Blank screen in Ultra? Or what?
1. I would wait for a next OTA update as it will install/update Ultra resources during firmware update.
2. You could unlock the bootloader, warranty will be void, and install an older firmware version and check if after updating to latest version everything works fine.
3. Claim for warranty.
Click to expand...
Click to collapse
Watch goes to Ultra mode, but screen does not turn on. I just notice that battery level is different in normal and ultra mode.
That is exactly what i plan to do. wait for update, and it that doesn't help - claim warranty.
Thanks For help.
Hello, when flash a stock rom the booloader is locked like factory watch?
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."
[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
First of all make sure your bootloader is unlocked.
1. Install the latest version of MAGISK (version 24.1) on your POCO X3 GT
2. Download the xiaomiADBFastbootTool. (you must have the drivers installed)
3. Download the boot.img (attached in this post)
4. Open Xiaomi adb fastboot tool goto | Device > Reboot to > Fastboot | NOTE : Don't forget to enable USB debugging
5. While your device is on fastboot. Go to | fastboot tab > select image > [select the boot.img] > boot > flash image
6. goto | Device > Reboot to > system
~~~~~~~~For Safetynet fix~~~~~~~~
1. Go to your magisk settings and enable zygisk.
2. Download the Universal Safetynet fix module (https://github.com/kdrag0n/safetynet-fix/releases) | NOTE : DOWNLOAD THE ZYGISK VERSION
3. Install the module in MAGISK APP
4. Restart your device
masteralfred32 said:
First of all make sure your bootloader is unlocked.
1. Install the latest version of MAGISK (version 24.1) on your POCO X3 GT
2. Download the xiaomiADBFastbootTool. (you must have the drivers installed)
3. Download the boot.img (attached in this post)
4. Open Xiaomi adb fastboot tool goto | Device > Reboot to > Fastboot | NOTE : Don't forget to enable USB debugging
5. While your device is on fastboot. Go to | fastboot tab > select image > [select the boot.img] > boot > flash image
6. goto | Device > Reboot to > system
~~~~~~~~For Safetynet fix~~~~~~~~
1. Go to your magisk settings and enable zygisk.
2. Download the Universal Safetynet fix module (https://github.com/kdrag0n/safetynet-fix/releases) | NOTE : DOWNLOAD THE ZYGISK VERSION
3. Install the module in MAGISK APP
4. Restart your device
Click to expand...
Click to collapse
Nice
masteralfred32 said:
First of all make sure your bootloader is unlocked.
1. Install the latest version of MAGISK (version 24.1) on your POCO X3 GT
2. Download the xiaomiADBFastbootTool. (you must have the drivers installed)
3. Download the boot.img (attached in this post)
4. Open Xiaomi adb fastboot tool goto | Device > Reboot to > Fastboot | NOTE : Don't forget to enable USB debugging
5. While your device is on fastboot. Go to | fastboot tab > select image > [select the boot.img] > boot > flash image
6. goto | Device > Reboot to > system
~~~~~~~~For Safetynet fix~~~~~~~~
1. Go to your magisk settings and enable zygisk.
2. Download the Universal Safetynet fix module (https://github.com/kdrag0n/safetynet-fix/releases) | NOTE : DOWNLOAD THE ZYGISK VERSION
3. Install the module in MAGISK APP
4. Restart your device
Click to expand...
Click to collapse
Are u have madule for x3 gt?
masteralfred32 said:
First of all make sure your bootloader is unlocked.
1. Install the latest version of MAGISK (version 24.1) on your POCO X3 GT
2. Download the xiaomiADBFastbootTool. (you must have the drivers installed)
3. Download the boot.img (attached in this post)
4. Open Xiaomi adb fastboot tool goto | Device > Reboot to > Fastboot | NOTE : Don't forget to enable USB debugging
5. While your device is on fastboot. Go to | fastboot tab > select image > [select the boot.img] > boot > flash image
6. goto | Device > Reboot to > system
~~~~~~~~For Safetynet fix~~~~~~~~
1. Go to your magisk settings and enable zygisk.
2. Download the Universal Safetynet fix module (https://github.com/kdrag0n/safetynet-fix/releases) | NOTE : DOWNLOAD THE ZYGISK VERSION
3. Install the module in MAGISK APP
4. Restart your device
Click to expand...
Click to collapse
Global Region? Indonesia ?
Hi, what are the software version compatibility for this root process? Is software version 12.5.7 is included?
Well done my friend
do you have a video?
masteralfred32 said:
First of all make sure your bootloader is unlocked.
1. Install the latest version of MAGISK (version 24.1) on your POCO X3 GT
2. Download the xiaomiADBFastbootTool. (you must have the drivers installed)
3. Download the boot.img (attached in this post)
4. Open Xiaomi adb fastboot tool goto | Device > Reboot to > Fastboot | NOTE : Don't forget to enable USB debugging
5. While your device is on fastboot. Go to | fastboot tab > select image > [select the boot.img] > boot > flash image
6. goto | Device > Reboot to > system
~~~~~~~~For Safetynet fix~~~~~~~~
1. Go to your magisk settings and enable zygisk.
2. Download the Universal Safetynet fix module (https://github.com/kdrag0n/safetynet-fix/releases) | NOTE : DOWNLOAD THE ZYGISK VERSION
3. Install the module in MAGISK APP
4. Restart your device
Click to expand...
Click to collapse
What software version are you using?
Its for 12.5.7 global boot image
masteralfred32 said:
Its for 12.5.7 global boot image
Click to expand...
Click to collapse
Yep