Database Develop

[OOS] 10.0.11.HD01AA [Patched boot.img]

Extracted stock boot.img from latest Global Stable 10.0.11 and patched with latest Magisk Manager 8.0.0
https://www.androidfilehost.com/?w=files&flid=318127

Any chance of one patched in Magisk Manager 8.0.0 and Magisk v21.0?
Edit: If I could get the Stock Boot IMG that would be great too.

digidude512 said:
Any chance of one patched in Magisk Manager 8.0.0 and Magisk v21.0?
Edit: If I could get the Stock Boot IMG that would be great too.
Click to expand...
Click to collapse
Done! Check OP link

Rooted I bootloop but Stock I boot fine.
I hate when this happens.

digidude512 said:
Rooted I bootloop but Stock I boot fine.
I hate when this happens.
Click to expand...
Click to collapse
It's not .img problem, all good here.

FSadino said:
It's not .img problem, all good here.
Click to expand...
Click to collapse
I know, Just venting and hoping someone can tell what I'm doing wrong.

digidude512 said:
I know, Just venting and hoping someone can tell what I'm doing wrong.
Click to expand...
Click to collapse
What were exactly your steps to flash patched.img?

FSadino said:
What were exactly your steps to flash patched.img?
Click to expand...
Click to collapse
I tried both
adb reboot bootloader
fastboot boot 10.0.11.HD01AA_Patched.img
fastboot reboot
and
adb reboot bootloader
adb flash boot 10.0.11.HD01AA_Patched.img
fastboot reboot
But I'm stuck at the spinning OnePlus logo but adb devices shows the phone.

digidude512 said:
I tried both
adb reboot bootloader
fastboot boot 10.0.11.HD01AA_Patched.img
fastboot reboot
and
adb reboot bootloader
adb flash boot 10.0.11.HD01AA_Patched.img
fastboot reboot
But I'm stuck at the spinning OnePlus logo but adb devices shows the phone.
Click to expand...
Click to collapse
I can't help you with booting without flashing because I never did. What i always do and never fails to me is:
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot patched_boot.img
fastboot reboot

FSadino said:
I can't help you with booting without flashing because I never did. What i always do and never fails to me is:
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried that, Also tried removing Magisk Modules via ADB but I'm still on the spinning white dots but ADB shows the device.
So it's a bit weird.
Also when flashing stock I lose Wi-Fi and it force restarts randomly unless I flash the Update ZIP again.

digidude512 said:
Tried that, Also tried removing Magisk Modules via ADB but I'm still on the spinning white dots but ADB shows the device.
So it's a bit weird.
Also when flashing stock I lose Wi-Fi and it force restarts randomly unless I flash the Update ZIP again.
Click to expand...
Click to collapse
My advice is to clean flash OOS and repeat all steps

I'm an idiot...HD01BA not HD01AA....

OOS stable boot image and patched magisk boot image both for 11.1.1.1.

Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.

I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​

235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D

sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot

235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well

sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process

sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)

previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later

abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.

I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!

F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.

I got boot loop after updating to 11.1.2.2
Any new boot img?

izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go

rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.

The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!

rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?

raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes

rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you

Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.​​I uninstalled magisk by mistake and could regain root, quick and painless​

Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?

How To Guide Rooted my Pixel 7

Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, enter bootloader do a "fastboot flash init_boot magskpatchedfile.img.
9, reboot and test,
I have removed the _a in the cmd line as it appears its not needed
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum.
Ok,, this how I flashed ,and will flash, the new updates coming out so as not to lose data ,this will NOT do a wipe plus it's faster ,,,,, I know there are multiple other ways but for now I choose this,, hth
1. Download the correct ota file here
https://developers.google.com/android/ota and copy to adb folder
2. Place phone in factory recovery and toggle to apply update from adb,,
3. Open cmd prompt in adb folder type adb sideload factoryota.zip ,,,takes 5-10 minutes to complete, reboot ,,
if rooted,
1 download correct full image zip here
https://developers.google.com/android/images. That matches ota you just flashed,
2 extract the ini.boot.img , patch with magisk and reflash in adb for root

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
Does the screen come on at all? In your other post you said it was black. If there's nothing at all on the screen, your phone is probably bricked.

JimJamer8 said:
it doesnt turn on at all
Click to expand...
Click to collapse
Have you tried a hard reset - hold the power button down for 10 seconds or so until the phone vibrates?

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You didn't try the steps I listed as I never said to flash a rooted bootloader

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You may need to disable Verity and Verification. I flashed my stock image back to the phone using the tool here: https://flash.android.com/ and checked the boxes to disable verity and verification, then followed the steps above. Important to note that booting to Bootloader tells you which slot is active, and running the command fastboot flash init_boot magisk_patched_25205_GUID.img automatically patches the active boot slot. From there you just need to run the Universal Safety net fix from KDrag0n and the latest MagiskHide and you should be good to go

hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Thank you for the help, turned out the _a was screwing me over, works great now!

mnemonical said:
Thank you for the help, turned out the _a was screwing me over, works great now!
Click to expand...
Click to collapse
I know ,,that was messing me up too, it did not work untill I put that part in,, don't ask me why! Lol

Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.

googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.

atom_jack said:
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
Click to expand...
Click to collapse
I'll give it a try

googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
Use the non replace version of revanced and disable stock YT

Hitman478™ said:
Use the non replace version of revanced and disable stock YT
Click to expand...
Click to collapse
Revanced Manager app is just going to black screen after install

hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?

AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik

googletermsofservice said:
Revanced Manager app is just going to black screen after install
Click to expand...
Click to collapse
I've it installed and it's working without any issue

AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
Use fastboot flash init_boot "image.img" without quotes and without specific the partition, it will goes on the active one, for me it has working at first try

hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
THX, in fact the "fastboot boot" command was used a lot with OnePlus devices because it is safer to boot in the rooted os and when there is an error you can just reboot without the command...and when you install it afterwards with magisk you know it will work

Does Universal Safetynet Fix work?

Just wanted to thank OP. My Pixel 7 arrived about an hour ago, got the bootloader unlocked no problem, then actually I flashed the latest System Image first, then had Magisk patch init_boot.img, flashed that, easy peasy.

hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
It's usually used to temporarily boot a patched boot image and then you can do direct install in magisk manager

Question Mi 11 venus, Xiaomi.eu weekly and TWRP

Hello! On the official TWRP website I downloaded the latest version 3.7.0-11 and it turns out that I can't update the weekly ROM because TWRP doesn't show any file. Reading and asking on the internet they gave me a solution but I do not know how safe and reliable it is, they referred me to this link: https://www.123pan.com/s/qHhDVv-nuQJv where they tell me that I have to do, adb, "fastboot boot TWRP.img" with the version (BOOT) 3.7.0_12_Mi11_v7.0_A13-venus-skkk_64135681 .....the question is. How reliable is that file, considering that on the official TWRP website only supports Android 12 and earlier versions? Does anyone with Mi 11 and android 13 TKQ know how to solve this problem? Using ADB Sideload could it be possible to update without losing any data?
Thank you for all!!!

Gor3zno said:
Hello! On the official TWRP website I downloaded the latest version 3.7.0-11 and it turns out that I can't update the weekly ROM because TWRP doesn't show any file. Reading and asking on the internet they gave me a solution but I do not know how safe and reliable it is, they referred me to this link: https://www.123pan.com/s/qHhDVv-nuQJv where they tell me that I have to do, adb, "fastboot boot TWRP.img" with the version (BOOT) 3.7.0_12_Mi11_v7.0_A13-venus-skkk_64135681 .....the question is. How reliable is that file, considering that on the official TWRP website only supports Android 12 and earlier versions? Does anyone with Mi 11 and android 13 TKQ know how to solve this problem? Using ADB Sideload could it be possible to update without losing any data?
Thank you for all!!!
Click to expand...
Click to collapse
If you are on xiaomi.eu_multi_MI11_V14.0.23.1.3.DEV_v14-13.zip
and want to update on the
xiaomi.eu_multi_MI11_V14.0.23.1.9.DEV_v14-13.zip
Start by removing security on the lock screen and reboot then use OTA to download the update and update the phone reboot and the twrp install the rom.
If you want to install the latest TWRP remove security on the lock screen and reboot then flash the TWRP in fastboot mode, assuming it is a TWRP boot.
Command:
fastboot boot twrp.img
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
If REC version
Install with TWRP or fastboot flash recovery_ab twrp.img
Note that the TWRP A13 is already on the rom that you use if weekly A13.
If your system is in A12 use a TWRP A12 to flash A13.

I have Android 13. When I try to download TWRP A13 from https://sourceforge.net/projects/re...wrp-3.7.0_12-v7.0_A13-venus-skkk.img/download I get: 'Software download may not be possible on this device'
When I flash current TWRP I get two sentences, in red (error) 'Unmont data.../.../.twrp'.
Is this command 'fastboot flash recovery_ab twrp.img' new to me, what is the difference with 'fastboot boot twrp.img'?
I don't know what this REC version means?

Gor3zno said:
I have Android 13. When I try to download TWRP A13 from https://sourceforge.net/projects/re...wrp-3.7.0_12-v7.0_A13-venus-skkk.img/download I get: 'Software download may not be possible on this device'
When I flash current TWRP I get two sentences, in red (error) 'Unmont data.../.../.twrp'.
Is this command 'fastboot flash recovery_ab twrp.img' new to me, what is the difference with 'fastboot boot twrp.img'?
I don't know what this REC version means?
Click to expand...
Click to collapse
What is the current TWRP?
If the fastboot boot twrp.img command worked, it's a boot.twrp.
The REC version installs with the TWRP or fastboot flash recovery_ab twrp.img.
To download on Souceforge with the phone.
In the Android browser, press the Menu button and then Settings.
Touch the Advanced options menu.
Touch the User Agent item.
Select the system you want to pass your browser to.
The change is immediate.
What is the version number of your phone?
Go to /settings/my phone/features/model
Example:M2011K2G, M2011K2C
Did you try?
"If you are on xiaomi.eu_multi_MI11_V14.0.23.1.3.DEV_v14-13.zip
and want to update on the
xiaomi.eu_multi_MI11_V14.0.23.1.9.DEV_v14-13.zip
Start by removing security on the lock screen and reboot then use OTA to download the update and update the phone reboot and the twrp install the rom."

I have M2011K2G, xiaomi.eu 14.0.22.12.16 and TWRP 3.7.0-11, the last in the oficial web. Although, according to my research, it seems that this version is not valid for Android 13.
Yes, I removed the fingerprint and the security pattern before.

Gor3zno said:
I have M2011K2G, xiaomi.eu 14.0.22.12.16 and TWRP 3.7.0-11, the last in the oficial web. Although, according to my research, it seems that this version is not valid for Android 13.
Yes, I removed the fingerprint and the security pattern before.
Click to expand...
Click to collapse
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/
You have a Twrp A12 on an A13 system.
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and rebbot on the TWRP at each attempt.
Then flash this TWRP
twrp-3.7.0_12-v7.0_A13-venus-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
and install the rom.

NOSS8 said:
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.D
Click to expand...
Click to collapse
Sorry, 22.12.26 is the ROM.
'fastboot flash recovery twrp.img' doesn't work for me, only the boot command.
I didn't try 'fastboot flash recovery_ab twrp.img' but the TWRP I have (3.7.0-11) is apparently not compatible with Android 13 and that's why some say it doesn't work, but I don't understand, it's the latest version on the official TWRP website.

Gor3zno said:
Sorry, 22.12.26 is the ROM.
'fastboot flash recovery twrp.img' doesn't work for me, only the boot command.
I didn't try 'fastboot flash recovery_ab twrp.img' but the TWRP I have (3.7.0-11) is apparently not compatible with Android 13 and that's why some say it doesn't work, but I don't understand, it's the latest version on the official TWRP website.
Click to expand...
Click to collapse
We are talking about these roms, right?
because the TWRP is included in the rom.
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/

NOSS8 said:
We are talking about these roms, right?
because the TWRP is included in the rom.
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/
Click to expand...
Click to collapse
That's strange, when I installed that room, it turns out that the 'main menu' was the normal one, the one that comes without many options.

Gor3zno said:
That's strange, when I installed that room, it turns out that the 'main menu' was the normal one, the one that comes without many options.
Click to expand...
Click to collapse
I have the impression that you are talking to me about the Stock EEA rom for Europe and not the Xiaomi Eu rom custom rom.

NOSS8 said:
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/
You have a Twrp A12 on an A13 system.
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and rebbot on the TWRP at each attempt.
Then flash this TWRP
twrp-3.7.0_12-v7.0_A13-venus-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
and install the rom.
Click to expand...
Click to collapse
So I can't try to flash or boot with A13 version without doing the wioe and without losing all the data?

NOSS8 said:
I have the impression that you are talking to me about the Stock EEA rom for Europe and not the Xiaomi Eu rom custom rom.
Click to expand...
Click to collapse

Ok, now it's clear.
22.12.26 was in Fastboot.zip because no functional TWRP at this time.
try again to install the TWRP A13
twrp-3.7.0_12-v7.0_A13-venus-skkk.img**
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
This is the official TWRP developed by SKK and uploader by Camerado84
Command:
fastboot boot twrp.img**
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Try several rebooting each time in Fastboot mode.
If after several attempts 5/6 still the same you will have to:
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and reboot on the TWRP at each attempt.
Then flash this TWRP**
Rename it twrp.img**

NOSS8 said:
Ok, now it's clear.
22.12.26 was in Fastboot.zip because no functional TWRP at this time.
try again to install the TWRP A13
twrp-3.7.0_12-v7.0_A13-venus-skkk.img**
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
This is the official TWRP developed by SKK and uploader by Camerado84
Command:
fastboot boot twrp.img**
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Try several rebooting each time in Fastboot mode.
If after several attempts 5/6 still the same you will have to:
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and reboot on the TWRP at each attempt.
Then flash this TWRP**
Rename it twrp.img**
Click to expand...
Click to collapse
As soon as I have time I'll try it and let you know, thank you

Gor3zno said:
As soon as I have time I'll try it and let you know, thank you
Click to expand...
Click to collapse
To try.
In the Fastboot rom 22.12.26 look in the img folder and replace the recovery.img with the TWRP A13 by renaming it recovery.img.
Important check that the sizes are identical otherwise it will not work.
Then use the Update.bat file.
Then update via OTA.
This will allow you to keep the data.

NOSS8 said:
To try.
In the Fastboot rom 22.12.26 look in the img folder and replace the recovery.img with the TWRP A13 by renaming it recovery.img.
Important check that the sizes are identical otherwise it will not work.
Then use the Update.bat file.
Then update via OTA.
This will allow you to keep the data.
Click to expand...
Click to collapse
There is no recovery.img but the 'boot.img' file happens to weigh exactly the same as the twrpA13skkk file.
Is it possible that boot is the recovery you are referring to?
If so, I should rename the twrpA13skkk.img file to boot.img in this folder.
Although, probably misinformed, I thought that boot is the one in charge of booting the system..... so I'm afraid that changing the file will only boot in TWRP mode without being able to enter system or fastboot.

Gor3zno said:
There is no recovery.img but the 'boot.img' file happens to weigh exactly the same as the twrpA13skkk file.
Is it possible that boot is the recovery you are referring to?
If so, I should rename the twrpA13skkk.img file to boot.img in this folder.
Although, probably misinformed, I thought that boot is the one in charge of booting the system..... so I'm afraid that changing the file will only boot in TWRP mode without being able to enter system or fastboot.
Click to expand...
Click to collapse
Nope, this is a method I used a long time ago and there was a recovery.img.
Stock fastboot rom

NOSS8 said:
Nope, this is a method I used a long time ago and there was a recovery.img.
Click to expand...
Click to collapse
Well, it seems that it is no longer called that.
By installing the twrpA13skkk version you told me, via fastboot, it works perfectly !!!!! I think a lot of people have had the same problem as me because we went to the official TWRP website and the latest version listed there is not compatible with Android 13.
I looked at the cmd command screen and I noticed that after typing 'fastboot boot twr.img' appears writing 'boot.img' so maybe you can change the boot.img file from xiaomi.eu by twrpA13skkk.img (renaming it to boot.img) but as we are not sure we better not move forward on that issue until someone solves that unknown.
If it wasn't for you I wouldn't have found the TWRP version compatible with my device so thank you very much! This is the magic of forums and the internet, now I will be able to help other people thanks to you !!!!!
I have one last doubt, now that I can see the Zip file of the updated Xiaomi eu weekly version, to UPDATE WITHOUT DELETING ANYTHING I simply have to hit 'install' select the ROM and...already?
I ask this because some sites say that you have to do wipe/dalvik and wipe/cache.... in some sites say to do it before installing, in other sites say to do it after installing the ROM, in other sites say to do it before and after and in other sites say that none of this is necessary.

Gor3zno said:
Well, it seems that it is no longer called that.
Click to expand...
Click to collapse
"TWRP website"is obsolete, use my link.
Update via ota then install, the phone reboot on the Twrp and install the rom. No wipe necessary.

Would it be possible to please move this discussion to venus forums? This forum is for alioth, and this discussion could lead to some confusion. Thanks.

Question stuck at bootlogo after installing gsi

Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation

WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.

starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible

kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing

I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?

stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.

lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.

kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.

stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.

stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?

Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.

mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.

No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).

mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully

The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?

mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.