Develop Bugs

[Q] flo 5.0.1 cwm/twrp flashable zip

I have a stock, rooted nexus 7 Flo on 5.0. I would like to move to 5.0.1 but I cannot because the update cannot install through Android because of CWM and there doesn't appear to be a flashable zip to use!

Download the system image then:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Then flash the root zip through twrp. Done.

Or you could flash the stock recovery, flash the OTA, then reflash CWM.

yosmokinman said:
Download the system image then:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Then flash the root zip through twrp. Done.
Click to expand...
Click to collapse
nhizzat said:
Or you could flash the stock recovery, flash the OTA, then reflash CWM.
Click to expand...
Click to collapse
Won't this wipe all my data? I don't want to redo my device.

No it won't wipe data. Data will only be wiped if you use the flash-all file without removing the -w or fastboot flash userdata.

That was useful!

How to update to latest OTA firmware (MRA58V) when rooted?

SO, i'm trying to ADB sideload the latest firmware (MRA58V), but when I go to the google developers website, it downloads in a .TGZ file.
https://developers.google.com/android/nexus/images
I've tried changing it to .ZIP, then flashing, but it fails invalid signature.
What am I doing wrong?
Thanks,

Thread moved to proper forum

Simply flash the .img files inside the zip with fastboot. Takes 2-3 minutes.
Since only boot and system changed that's all you need to flash.
The commands I used today for 6.0.1:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format cache
fastboot reboot
That's it, doesn't wipe anything.

yosmokinman said:
Simply flash the .img files inside the zip with fastboot. Takes 2-3 minutes.
Since only boot and system changed that's all you need to flash.
The commands I used today for 6.0.1:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format cache
fastboot reboot
That's it, doesn't wipe anything.
Click to expand...
Click to collapse
Thanks worked perfect.
Sent from my SM-G920T using XDA Free mobile app

Unable to boot into ROM after flashing

Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?

MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Flash stock
finish setup
before doing anything else

MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.

parakleet said:
Flash stock
finish setup
before doing anything else
Click to expand...
Click to collapse
Yup I did. I just didn't sign in my account or do the security pin/pixel imprint. I skipped everything untill I was at the home/launcher.

Az Biker said:
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.
Click to expand...
Click to collapse
Nothing to special from the norm. I didn't everything the forums told me to do.
Okay definitely, I'll check that out and try those steps.
Also do you think I have a phone that twrp can't decrypt? I remember a while back doing one of the twrp updates that some phones won't decrypt because it used the older encryption method or something like that and TWRP was only able to decrypt then phones using the new method or something like that.

Oh and another question, do you guys think I should root the stock image with magisk then boot into twrp using fastboot and install the room then the twrp.zip?

My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.

amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
Now that's all the steps j took to flash the roms.
I do not install twrp app I skip that.
My first methond to flash stock on both slots is set slot to a then flash stock using the flash all bat file in from the stock images (google directions to flashing images)
Then it would reboot. Then I would set to slot b and flash the stock images the same way using the bat file.
Then I found out that wasn't really the best way to do it so I used deuces (I believe that was the users name) bat file to flash the stock images on both slots the correct way and that's what I've been doing since.
But your steps have a different step then what I do. It seems it does the same as deuces bat file however once it's done I just boot straight into stock rom. I dont boot into stock recovery and factory wipe. But I will definitely try that as well.

Finally fixed it!
I flash both slots and followed everyone's directions.
The problem was I wasn't wiping all the things I needed too.
I read in another roms steps to not only do the factory reset thin in TWRP, but to also manually wipe system, data, dalvik/art cache. Then flashed the room and TWRP.zip.
I did this and BOOM, I booted up into the room! Thanks again for everyone's help!

amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
I stumbled across this post after having several issues trying to get my Pixel 2 XL flashed with a custom ROM (constantly resulting in boot-loops), and the steps worked perfectly.
I've ended up running these steps several times today, but I like keeping all of my stock images in sub-folders by release date. I'm not the greatest Powershell guru, but I've written a script that will search sub-directories in a folder for dates, and select the latest date and automatically flash the radio, bootloader, and image from that directory using your steps.
Code:
clear;
# Execution Policy must be adjusted in order to obtain the current executing directory of the script. This is a one-time command that must be run separately.
# Set-ExecutionPolicy RemoteSigned
# To reverse the command set the execution policy to restricted:
# Set-ExecutionPolicy Restricted
# The root directory which contains date sub-folders in the format yyyy-MM-dd representing an extracted OTA zip.
$startingDirectory = split-path -parent $MyInvocation.MyCommand.Definition;
# Alternatively, hard code a starting directory.
# [System.String]$startingDirectory = 'D:\Flashing\Roms\Taimen\Stock\';
[System.String]$targetFolder = (Get-ChildItem $startingDirectory | Select-Object -Property @{Name='Date';Expression = { Get-Date $_.Name -Format 'yyyy-MM-dd' }}, @{Name='FullName';Expression= {$_.FullName}} | Sort Date -Descending | Select -First 1).FullName;
if (-not $targetFolder) {
throw 'No folders are located in directory ''' + $startingDirectory + ''' with the date format yyyy-MM-dd.';
}
[System.String]$bootloader = Get-ChildItem $targetFolder -Name 'bootloader-*.img';
[System.String]$radio = Get-ChildItem $targetFolder -Name 'radio-*.img';
[System.String]$image = Get-ChildItem $targetFolder -Name 'image-*.zip';
# Validate all files have been successfully located.
[System.Collections.Generic.List[System.String]]$messages = [System.Collections.Generic.List[System.String]]::new();
if (-not $bootloader) {
$messages.Add('The bootloader file was not located.');
}
if (-not $radio) {
$messages.Add('The radio file was not located.');
}
if (-not $image) {
$messages.Add('The image file was not located.');
}
if ($messages.Length -gt 0) {
throw 'Unable to locate files in path ''' + $targetFolder + ''':' + [Environment]::NewLine + [System.String]::Join([Environment]::NewLine, $messages);
}
$bootloader = [System.IO.Path]::Combine($targetFolder, $bootloader);
$bootloader;
$radio = [System.IO.Path]::Combine($targetFolder, $radio);
$radio;
$image = [System.IO.Path]::Combine($targetFolder, $image);
$image;
#adb reboot bootloader;
function Reboot-Bootloader {
fastboot reboot-bootloader;
sleep 5;
}
#flashing bootloader to slot A and slot B
'Flashing bootloader to slot A.'
Reboot-Bootloader;
fastboot flash bootloader_a $bootloader;
'Flashing bootloader to slot B.'
Reboot-Bootloader;
fastboot flash bootloader_b $bootloader;
#flashing radio to slot A and slot B
'Flashing radio to slot A.'
Reboot-Bootloader;
fastboot flash radio_a $radio;
'Flashing radio to slot B.'
Reboot-Bootloader;
fastboot flash radio_b $radio;
#set active slot to B, flash system image
'Flashing system image to slot B.'
fastboot --set-active=b;
Reboot-Bootloader;
fastboot --skip-reboot --skip-secondary update $image;
#set active slot to A, flash system image [different command!!!]
'Flashing system image to slot A.'
fastboot --set-active=a;
Reboot-Bootloader;
fastboot --skip-reboot update $image;

Twrp 3.3.1-0 & root [updated] kane/troika

Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!​
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.

Great guide @tys0n and thank you to @Stricted and @deadman96385 for his work !

tys0n said:
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Click to expand...
Click to collapse
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.

daekdroom said:
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
Click to expand...
Click to collapse
You're right. You can't switch between encrypted / non encrypted without a reset.
This update method have been working for me with the old twrp as well, but this new build is much better and more stable that I see no reason not to switch to the new one.
Actually, I think it may be better to first fastboot flash the new firmware (except vbmeta) so that you have a "clean" boot.img to start with if you're planning to use the install recovery ramdisk. At least if you have the old one installed already.
That's how I switched and I've had no problems.

Worked to my, Thnx

Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards

gonzo1963 said:
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
Click to expand...
Click to collapse
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.

tys0n said:
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
Click to expand...
Click to collapse
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good afternoon,
Any answer?
Regards
Enviado desde mi unknown mediante Tapatalk

Bootloop
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?

"Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop."
Agter this restart the phone in recovery mode and then continue as explained.
Sorry in bad english

First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update

Preceptor said:
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
Click to expand...
Click to collapse
same here !

sennator said:
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Click to expand...
Click to collapse
Hi. Yes, you're right. After flashing the patched vbmeta we need to format data. I've made it more clear in OP now.
Thanks for pointing it out.
kArLiN_dRaKE_MX said:
same here !
Click to expand...
Click to collapse
Format data in twrp

It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.

It worked.
I performed the process again.
and everything went well.
Thanks to everyone involved. :good:
gambiarraweb1 said:
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
Click to expand...
Click to collapse

Just a quick question, when I have TWRP and root I can't pass the SafetyNet check, right?

Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?

simije97 said:
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
Click to expand...
Click to collapse
You probably have Data encrypted. You need to execute Format Data in TWRP.

Has anyone used the official TWRP version? I've been thinking of transitioning from the older, unofficial, TWRP to that, but I haven't found any comment about it at all.

Android 11 OB 2 Magsik patched boot.img

Does anyone have or know of a way to root Android 11 OB 2 for the international OP7t?

Get OTG USB-C flash drive. Put MagiskCanary.zip (download from Magisk github, renamed apk to zip extension) on flash drive (as internal sd is encrypted and not accessible via TWRP). Flash (using fastboot flash recovery_a twrp.img and fastboot flash recovery_b twrp.img commands) TWRP. Boot into recovery (using fastboot reboot recovery command). Install magiskcanary.zip then reboot to system and then renam magiskcanaryl.zip back to apk and install this app as it doubles as magiskmanager app, and you're now rooted.

Here is my magisked boot.img