Database Develop

I'm facing problem when I'm trying to update my K20 Pro Chinese device.

My phone was better before unlocking bootloader. But after unlocking the bootloader I'm facing updating problem. Please see the screenshot below.
{
"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"
}
Please help me to solve this

L1mon said:
My phone was better before unlocking bootloader. But after unlocking the bootloader I'm facing updating problem. Please see the screenshot below.
Please help me to solve this
Click to expand...
Click to collapse
No screenshot is visible. Unlocked Bootloader does not prevent OTA, but if you installed a custom Recovery (e.g., TWRP or OrangeFox) OTA will fail (when phone reboots, it looks for stock Recovery to process OTA package)
And/or, if you installed Magisk (or custom Kernel), you need to force Full OTA package (2,4 GB or so) from System Update, Settings - because default incremental OTA lacks full Boot image and cannot update Boot from your custom Boot (Magisk or custom Kernel affect Boot)
Hence if you want to update by OTA, revert Boot and Recovery to stock before you go

zgfg said:
No screenshot is visible. Unlocked Bootloader does not prevent OTA, but if you installed a custom Recovery (e.g., TWRP or OrangeFox) OTA will fail (when phone reboots, it looks for stock Recovery to process OTA package)
And/or, if you installed Magisk (or custom Kernel), you need to force Full OTA package (2,4 GB or so) from System Update, Settings - because default incremental OTA lacks full Boot image and cannot update Boot from your custom Boot (Magisk or custom Kernel affect Boot)
Hence if you want to update by OTA, revert Boot and Recovery to stock before you go
Click to expand...
Click to collapse
I've installed magisk but i uninstalled that also I flash stock rom from orange fox.
But same thing happening.

L1mon said:
I've installed magisk but i uninstalled that also I flash stock rom from orange fox.
But same thing happening.
Click to expand...
Click to collapse
I answered you in the previous post that for OTA you must not have OrangeFox - you must reflash stock Recovery before you go for OTA

[RECOVERY][UNOFFICIAL] TWRP 3.5.2 for Xperia 1 II

Disclaimer
Builds are provided AS-IS without warranty or repair. I am not responsible if you brick your device.
About
I was using the existing TWRP build that's been floating around and noticed it had a few issues, so I made a device repo and rebuilt an improved version.
Noteworthy features:
English language defaults
Added support for microSD
Added support for USB storage mounts
Added support for userdata encryption
Support for MTP and ADB
Added backup options for DTBO, verity meta, OEM partitions
Screenshots
{
"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"
}
Downloads
Downloads are available at https://github.com/shinyquagsire23/twrp_sony_pdx203/releases/
Flashing
Flashing is only supported on phones which have an unlocked recovery and verified booting disabled!
Code:
#!/bin/bash
# Reboot to fastboot
sudo adb reboot bootloader
# Flash recovery img
sudo fastboot flash recovery recovery.img
# Reboot to recovery
sudo fastboot reboot recovery
Source Code
Source code is uploaded at https://github.com/shinyquagsire23/twrp_sony_pdx203/. I also provided some brief compilation instructions in the README.md for anyone interested.
Special Thanks
Thanks to Sjll for twrp_sony_pdx201, which I based my repository on.

Thank you, I will be testing this weekend.

Very cool, thanks for sharing.

You my friend are a life saver. I installed a magisk module (riru sui) that bootlooped my device. Tried every damn near every option to remove that module...couldn't gain access via ADB as my device was coming up as "unauthorized". I fastboot flashed your twrp successfully....got into file manager and manually removed the module..and my phone booted back up. THANK YOU!

Junior-J said:
You my friend are a life saver. I installed a magisk module (riru sui) that bootlooped my device. Tried every damn near every option to remove that module...couldn't gain access via ADB as my device was coming up as "unauthorized". I fastboot flashed your twrp successfully....got into file manager and manually removed the module..and my phone booted back up. THANK YOU!
Click to expand...
Click to collapse
thats why older Samsung phone running android 7 and lower are considered the safest. they have a inbuilt download mode to recover their software incase of a bootloop. but xperia phones aren't the hardest to root either since they are one of the most used. only problem is that some xperia phones will have their recovery menu and commands etc in chinese/japanese depending where you bought them.

Thanks for sharing，Great Works ~!

Does this not support decryption? I wasn't able to get in with my password using this version of TWRP, but I was with OrangeFox.

Can you give me build.prop from Sony xperia 1 ii Please? give me in my mail or telegram : t.me/Info_Shakib [email protected]

Seems there is a fix for fastbootd @ https://gerrit.twrp.me/c/android_bootable_recovery/+/2910
If I have time next week I'll try patch and make PR shinyquagsire23 unless someone does it first..

Can someone tell me how can to compile twrp recovery for xperia 1(j9110). I need some guidance. Thanks.

TWRP flashed on xq-at51 android 11 without any issue, thank you for the guide

Is it work for experia 1 iii ???

recovery not booting up after flashing stock android 12 january patch, the screen keeps getting splashed with the logo of twrp

Ask, Pixel Experience Plus 12.1 v413 is only img after decompression, can only use TWRP to flash the machine, 1ii 12 has no TWRP available, whether to downgrade 11, use TWRP to flash .img, which partition to flash into TWRP, still trying to learn, Please enlighten me.

Thanks so much. Exceptional.
Works on XQ-AT51 (Europe, dual SIM) . Flashed twice to _a and _b. on Android 11.

I'm having the same problem, whenever i boot into recovery, TWRP logo just keeps flashing, like it's crashing , android 12 btw, any other possibilities to root the 1ii? thanks for the help

marcvie said:
I'm having the same problem, whenever i boot into recovery, TWRP logo just keeps flashing, like it's crashing , android 12 btw, any other possibilities to root the 1ii? thanks for the help
Click to expand...
Click to collapse
To my knowledge, you don't need TWRP to get ROOT. This guide should help: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4119493/

Gunseng said:
To my knowledge, you don't need TWRP to get ROOT. This guide should help: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4119493/
Click to expand...
Click to collapse
Thanks for the reply, that will be handy for flashing, but i eventually got my 1ii rooted using this guide: https://www.getdroidtips.com/unlock-bootloader-root-sony-xperia-1-ii/

If u r on Android 12, just use recovery of this thread:
[ROM][Officiall][pdx203][12.1] LineageOS 19.1
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Not twrp but almost the same (lineage).
Flash recovery, then "fastboot reboot recovery"

And this is really working on a rooted stock rom ?

Question Cant wipe system in TWRP

I have been using crdroid on my redmi note 10 for a couple months, I've just tried to update but I have ended up getting stuck at the crdroid logo on boot every time after trying to reinstall flame gapps. When I go to wipe in TWRP there is no option to wipe the system.. how can I wipe the phone to clean flash crdroid? or is there a way I can uninstall the flamegapps zip in twrp? I used another gapps in the past that allowed to to uninstall by renaming the zip to uninstall, but that doesn't seem to work with flame gapps.

itsfatso said:
I have been using crdroid on my redmi note 10 for a couple months, I've just tried to update but I have ended up getting stuck at the crdroid logo on boot every time after trying to reinstall flame gapps. When I go to wipe in TWRP there is no option to wipe the system.. how can I wipe the phone to clean flash crdroid? or is there a way I can uninstall the flamegapps zip in twrp? I used another gapps in the past that allowed to to uninstall by renaming the zip to uninstall, but that doesn't seem to work with flame gapps.
Click to expand...
Click to collapse
Wipe/format data(yes)/reboot twrp.

NOSS8 said:
Wipe/format data(yes)/reboot twrp.
Click to expand...
Click to collapse
This doesnt help. In the wipe menu there is no option for storage. which is why i'm having problems

itsfatso said:
This doesnt help. In the wipe menu there is no option for storage. which is why i'm having problems
Click to expand...
Click to collapse
isn't there that?
{
"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"
}

yes I can format data but it doesn't change anything.. I have formatted then rebooted countless times but the rom doesn't get cleared from the phone, if I boot into system it goes back to being stuck at the crdroid logo

It's good practice to make a full twrp backup of your device before installing zips like gapps or installing stuff like magisk. Any change to your system or boot partition can result in a bootloop so back these up at least.

itsfatso said:
yes I can format data but it doesn't change anything.. I have formatted then rebooted countless times but the rom doesn't get cleared from the phone, if I boot into system it goes back to being stuck at the crdroid logo
Click to expand...
Click to collapse
Also check that you are using the correct TWRP/O.F.https://androidfilehost.com/?w=files&flid=321666
A12/A11
Start from zero
flash firmware recommended by O.P or complete rom** without re-lock the bootloader(**best solution).
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

Should I update to Magisk 25.2 after flashing 24.3

According to this thread: https://forum.xda-developers.com/t/...1-legendarypixieos-4-1-for-galaxy-m21.4379385
Flashing 25.x with that certain rom bootloops, and I have that version of Magisk flashed and installed to my device, but the app is bothering me to download the latest version of it.
Should I continue? Since this is after the fact?
{
"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"
}

Magisk stopped patching avb and some other stuff since 25.0 so some roms and kernels that need it wont work anymore. But if you already had v24 installed everything should be already patched. I've noticed that if you're only flashing v25*, flashing dmverity disabler along with it fixes bootloops.
So in theory it should be okay if you already have magisk installed. However, dont forget to take a backup of your boot before doing anything.

Alright, I'll update the thread if everything goes well.
Thank you!

Whelp, it is bootlooping with no access to twrp and shutdown.
I'll try to turn it off by removing the battery and reflashing back the working 24.3.
Note to future-self:
You can uninstall the newer magisk version by renaming the APK of the version you updated to by renaming it to `uninstall.zip` and flashing it.
You can also get an infinitely bootlooping device to odin mode by holding the power up and down keys while being connected to a computer when the boot cycle starts.

I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.

newt23 said:
I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.
Click to expand...
Click to collapse
Greetings Friend,
Can you attach the Dmverity Disabler zip?

OldNoobOne said:
Greetings Friend,
Can you attach the Dmverity Disabler zip?
Click to expand...
Click to collapse

Greetings Friend newt23,
Can you also elaborate on the exact steps you did to get the GSI to boot.
I mean steps like which GSI booted? & did you put the GSI in sdcard then use terminal commands like- { mount partition system, cd documents, super flash system.img etc., did you use chodoe flasher, gapps }?
Thanks in advance.
Also, Magisk 26.1 seemed more stable on stock rom without the addon.d script ability on stock but some devs insisting on staying with 24.3 stable even though 26.1 has better SafetyNet but. What would be your advice?

Question Magisk-ing MIUI 14 EEA

Hello again,
So about 2-3 weeks ago, tried to flash Magisk on my Redmi w/ a boot image from the Recovery ROM of 14.0.1 EEA. Put it on my phone, patched, but after flashing the phone would boot to FASTBOOT. Tried patching the vbmeta, just in case, but no luck. OK, tried flashing the stock boot image, but IT STILL wouldn't boot, even if it was from 14's recovery or 13's FASTBOOT. Even went as far as flashing China ROM image. But here's where it gets interesting, but before that...
Last night I saw that now there's a FASTBOOT ROM available for EEA, so before bricking my phone again ( I'll explain), I want to ask if there's also somebody trying to root their phone on MIUI 14, and if they did, was everything alright?
Now the Chinese story! I said that I've flashed a China boot image on EEA, but it didn't boot. BUT I tried using XiaoMiTool to flash the correct firmware, cuz I had access to recovery and FASTBOOT, and it identified as camelliA, not camelliAN. It wasn't doing this before... Said it was bricked and it started flashing China 14.0.2 in FASTBOOT. Ofc it didn't boot. Then I tried w/ access to FASTBOOT to flash the Recovery 14 EEA boot image AND THEN connecting the phone, and THIS TIME, it showed camelliAN, even tho there's China ROM. Then I bricked it and flashed 13, then upgraded, tra-la-la-la, la-la, bulls**t stuff.
My thinking, is that the OSs boot image is somehow the source of identity for the device's specs and codename.
With that in mind, is there a way to successfully flash China MIUI 14 ROM on Global, and if yes, can it be flashed European or any global ROM's boot image on top of the Chinese ROM and identify w/ codename camelliAN instead of camelliA? AND THEN patched Magisk?
Just asking, ya know...

Currently running Magisk on MIUI 14 using a patched boot.img from the MIUI 14 EEA Fastboot ROM. I flashed the stock firmware first to make sure it booted. Then I flashed the patched boot.img. I went from MIUI 13 Global to EEA MIUI 14 however. I'm not sure if it's possible to use the EEA boot.img on a China ROM, this is my first Xiaomi device so someone will know more than myself. Already bricked it once No issues yet with root, even bypassed Play Integrity API for Google Wallet
{
"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"
}