yashsingh1/xdaforums huggingface dataset:
[ASUS ZenFone 8] huangjqiu:
Thanks much.

I softbricked oneplus 8 pro last night after I tried to flash a boot.img patched with Magisk.

I successfully changed the slot to b using

sudo ./fastboot set_active b.

The phone can boot with slot b now but it start from the Hello screen which means I have to set up the phone from scratch. Will it erase everything if I set up the phone again? I am a bit hesitating if I will lose all data.
[ASUS ZenFone 8] bnsmb:
It shouldn't ... but I recommend to power off the phone, boot the phone from a TWRP recovery image, backup your data and then reboot the Android OS again to finish the config

regards

Bernd
[ASUS ZenFone 8] huangjqiu:
Unfortunately, there is no TWRP recovery image for Oneplus 8 Pro on Android 13. It took me hours to set up the phone and customize it. Luckily most data can be recovered from google backup.
[ASUS ZenFone 8] bnsmb:
Is there a recovery from LineageOS for that phone?

There is also adb support in the recovery from the LineageOS (at least for the Asus Zenfone 8) but it must be enabled manually in the booted Recovery

regards

Bernd
[ASUS ZenFone 8] huangjqiu:
I am not familiar with custom ROMs. I have always been using stock ROM with this phone. Thanks for the suggestion! I will keep that in mind next time when updates go wrong.
[ASUS ZenFone 8] abcezx:
Stealing the thread a bit here

I moved from MIUI to LOS20 on my Mi mix 4 which uses A/B, after using it for a while some bugs were found (probably due to dirty flashing 2-3 times across the updates). Is there any way to completely format the system partition (wherever that is) so I can install the latest LOS again cleanly? I noticed that by installing without wiping system (which isn't possible on A/b for what I tried) the install isn't clean. Some apps are logged in right after re-install
[ASUS ZenFone 8] bnsmb:
AFAIK the installation of a new OS image with Android will always overwrite the system partition. The system partition is read-only after the installation so new applications will never be written to the system partition. Instead installed applications are written into directories in the data partition . That's the reason why your application and configuration survives an OS upgrade (the OS upgrade will never touch the files in the data partition)

So to get rid of your applications either deinstall them before installing the new OS or do a factory reset (but be aware that a factory reset will delete ALL applications and user data)

There is an option to do a factory reset in the LineageOS recovery used for the installation of LOS.

IMHO it's recommended to do a factory reset before switching from one OS distribution to another (I assume MIUI is the original Android that is most probably only partially compatible with LOS)

And for the records:

In the latest Android version /system and some other partitions are not physical partitions anymore -- they are now "dynamic" partitions. Dynamic partitions are in the end only logical volumes on one of the physical volumes.

Hope this helps

regards

Bernd
[ASUS ZenFone 8] abcezx:
Bernd, you just enlightened me better than my 3-day-self-digging on the interwebz. Thanks a lot!

I did use LOS's factory reset feature right after this reply and while it seemed to have done it (strangely, by some operations on TWRP), it seems like the old problem still occurs: some apps are logged in right after re-install, the bugs associated with them are there as well (little bugs like videos can't play in apps, Gmail not loading chat properly).

This drove me crazy because even after re-flashing stock ROM in Fastboot, wipe internal multiple times, i believe some partition (likely data?) has never been wiped cleanly, leaving the bugs intact after every re-flash, no matter what ROM I picked.

So my question is, is there anyway to make sure I have a clean Flash? Like REALLY clean.

Again, thank you for your reply, while it didn't immediately solve my problem for now, it helped me a lot with understanding this A/B super device thingy.
[ASUS ZenFone 8] bnsmb:
Hi

If the errors also occurs if the original ROM is installed it might be a general (Hardware?) problem with the phone.

AFAIK a factory reset should delete all apps and user data on all phones. The default partition for all user data and apps is the partition mounted to /data.

To check that the factory reset was done you might boot your phone from the TWRP image connect via adb and check that /data is mounted to the data partition and that there are no files or directories except /data/recovery in /data.

On the other hand nowadays there are a lot of partitions with device specific files on the phones. There should be no user data or apps in these partitions but you newer know.

For the ASUS Zenfone 8 ASUS provides a "raw" image that will overwrite every partition on the phone with the original data but I doubt that this also exists for other phones.

regards

Bernd
[ASUS ZenFone 8] abcezx:
Thanks again Bernd, I think I might have to check if a factory reset was properly done using the command you mentioned, can you show me how to do that?
[ASUS ZenFone 8] bnsmb:
- do a factory reset and boot the phone into the bootloader (NOT into the installed OS)

- when the phone is in the bootloader connect it via USB to a PC and execute on the PC

sudo fastboot boot <twrp_image>

Where twrp_image is the fully qualified name of the TWRP image for your phone, e.g. for the ASUS Zenfone 8 this is <path>/twrp-3.7.0_12-0-I006D.img

When the phone is booted connect via adb (or execute in the shell in TWRP) and do

df -h /

df -h /data

The devices used for / and /data must be different, e.g it should look like this:

1|ASUS_I006D:/ # df -h /
Filesystem Size Used Avail Use% Mounted on
rootfs 3.2G 103M 3.1G 4% /

ASUS_I006D:/ # df -h /data
Filesystem Size Used Avail Use% Mounted on
/dev/block/dm-5 108G 3.3G 104G 4% /sdcard
ASUS_I006D:/ #

If that is not the case execute the command

twrp mount /data

in the adb shell and check again.

If the devices used for / and /data are still equal the TWRP used can not mount /data.

If the device for /data is a separate partition check that there are no files or directories in /data

(except /data/recovery).

In any case you can try to do the factory reset via TWRP GUI:

- select "Wipe"

- then select "Format Data"

- enter "yes"

regards

Bernd
[ASUS ZenFone 8] wasteoinc:
I know it may sound stupid but could I switch from this cursed A/B to A and delete B partitions so I can save some space?

I don't care abou OTA updates I will probably use the same system once I properly install it.

Because the way I get it , if I have stock MiUi and then flash LOS the stock MiUi with all these useless programs stay in B partition, so I don't benefit much from the smaller LOS
[ASUS ZenFone 8] bnsmb:
The A/B scheme is part of the OS . To reuse the disk space occupied by the not active slot you must install an OS that is not using the A/B scheme .

It might (!) be possible to reuse the disk partitions for the other slot using a lot of manual commands but that's neither supported nor useful.

I really do not recommend to try this approach on a productive used phone.

regards

Bernd
[ASUS ZenFone 8] DocMAX:
Device is Jelly Star here. Switching to slot b works. Also current-slot says "b". But it still boots into "a".
[ASUS ZenFone 8] bnsmb:
How did you switch the slot?

Can you try one of the other methods to switch the slot?

And there is a bootable OS in slot b?

regards

Bernd
[ASUS ZenFone 8] DocMAX:
Slot 1: lineage-20.0-20240112-UNOFFICIAL-arm64_bvS.img.xz

Slot 2: lineage-20.0-20240112-UNOFFICIAL-arm64_bvS-vndklite.img.xz

I booted into fastbootd, then:

c:/RSL/platform-tools $ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.011s
c:/RSL/platform-tools $ fastboot set_active b
Setting current slot to 'b' OKAY [ 0.009s]
Finished. Total time: 0.018s
c:/RSL/platform-tools $ fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
c:/RSL/platform-tools $ fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.016s
c:/RSL/platform-tools $ adb shell getprop ro.boot.slot_suffix
_a

So, still _a.

Also tried with Magisk. Will try bootctl
[ASUS ZenFone 8] bnsmb:
LineageOS 20 is a different beast -- I never tested it with that OS.

The maintainer of the LineageOS did "something not usual" in the version 20 -- my ASUS Zenfone 8 can't even boot anymore from the TWRP image if LineageOS 20 is installed (and I don't know why).

But please try Magisk - hopefully that works

regards

Bernd
[ASUS ZenFone 8] the Rodrigues:
Esse e de um outro celular, que não está ligando, não aceita instalação da rom original, e descobri que o Corrent slot não tem A e nem B como resolver isso?
[ASUS ZenFone 8] Feenix0:
Running ADB on Windows 10:

C:\puter>fastboot getvar current-slot
current-slot: a
finished. total time: 0.009s

C:\puter>fastboot set_active b
usage: fastboot [ <option> ] <command>

commands:
.....

Since the OP is using Linux (sudo), I was wondering if the commands are different on Windows. The "set_active" command was not recognized.

I thought I had switched slots in Magisk, but I ended up overwriting my old OS anyway. I'm currently on LOS 21 with Magisk 27. I don't really need this to work for me now, but I'm flashing and rooting my wife's phone (same model) next, and I really need to be able to switch back to her old slot if she doesn't like the new OS.
[ASUS ZenFone 8] bnsmb:
probably an outdated version of fastboot - do

[ OmniRom 14 Dev - xtrnaw7@t15g /data/develop/android/SELinux-Explorer ] $ fastboot --version
fastboot version 34.0.4-android-tools
Installed as /usr/bin/fastboot
[ OmniRom 14 Dev - xtrnaw7@t15g /data/develop/android/SELinux-Explorer ] $
[Upgrading, Modifying and Unlocking] vantrung:
Ve Thiet ke webdite, lap trinh, ke toan, nhac
[OnePlus 10 Pro] ugendersingh:
Hi guys has anyone moved from Oxygen os 13 beta 2 to this stable build? Are all the bugs removed? Also does going from beta 3 to this stable build wipe your data? Thanks
[OnePlus 10 Pro] ugendersingh:
Also when you backup your data using the oneplus clonephone app, the photos and videos are not backed up. Has anyone found a way around it?
[Redmi Note 9 Pro (International Model) General and] carabot:
hello

having on my redmi notes 9 pro rom xiaomi. eu, android 11, wanting to install the new rom xiaomi. eu, android 12, I have to install the new orangefox twrp, but I don't know which version is suitable for the redmi note 9 pro between fbe v1 and fbe v2.
[Redmi Note 9 Pro (International Model) General and] crok.bic:
For Xiaomi.EU ROM you have to use the FBEv1 versoin but I had problems with it, see here and read further - tl;dr if I set pin/pattern then OFox is asking for it but even if I input the correct one it says decryption failed.. but apparently not, if you tap the home or back button you will see your internal storage and /data correctly. This isn't a problem when you aren't using PIN/pattern for lock screen though.

But anyway the joyeuse ROM for Xiaomi.EU is still in fastboot form so for the installation you won't even need the recovery.
[Redmi Note 9 Pro (International Model) General and] carabot:
no, the 13.0.2.0 is in recovery format, is the redmi note 9 pro, with xiaomi. eu corresponds to redmi note 9s
[Redmi Note 9 Pro (International Model) General and] crok.bic:
^---- You said Note 9 Pro, that's joyeuse.

If you say Note 9s (or Note 9 Pro India) then it's a curtana.

But both are using FBEv1 anyway and both are under the umbrella name miatoll anyway, too - so the OrangeFox to be installed is exactly the same, too.
[Redmi Note 9 Pro (International Model) General and] carabot:
only by way of knowledge, how do you see if you need fbev1 or fbe v2
[Redmi Note 9 Pro (International Model) General and] crok.bic:
From the mount options and some props afaik.
[Ubuntu Touch Ports to Android] علاء العمارين:
Please some one help me to port Ubuntu touch for POCO F3 ,☺️
[General Questions and Answers] ATBG:
I'm thinking about buying a Google Pixel 3 XL on Amazon, it's renewed. It is factory unlocked and I was wondering if it means it can be OEM unlocked. Does factory unlocked mean it doesn't come with a carrier?
[General Questions and Answers] xXx yYy:
Factory Unlocked means it's unlocked for all carriers.
[General Questions and Answers] ATBG:
Thank you, so that means no blocking of OEM unlock?
[General Questions and Answers] ATBG:
Because I heard Verizon blocks OEM unlocking.
[General Questions and Answers] xXx yYy:
Factory Unlocked ( read: device without network/SIM lock ) and OEM Unlock ( read: device's bootloader is unlocked ) are completely different things, they don't relate.

Whether the phone in question can get OEM unlocked or not I don't know: I don't own such a device.
[General Questions and Answers] ATBG:
So factory unlocked doesn't have a carrier and can choose any or not have any?
[General Questions and Answers] ATBG:
Google Pixels on Verizon can't be bootloader unlocked, I want to make sure I don't get Verizon. Factory Unlocked mean you don't have any, right?
[General Questions and Answers] Droidriven:
Factory unlocked means it is SIM/Carrier unlocked so that the device can be used on any carrier network. This has nothing to do with OEM unlocking.

OEM unlock only applies to unlocking the bootloader so that the software on the device can be modified or install custom software.

Verizon blocks OEM unlock on all of its devices, you can't unlock the bootloader on Verizon devices, this means you can't use Magisk, TWRP, custom ROMs and you can't modify the software on the device.

Do you understand the difference now? If you want to be able to root a device or install TWRP and custom ROMs, do not buy a Verizon device because you will not be able to do these things on a Verizon device. Don't waste your money on a Verizon device.
[General Questions and Answers] ATBG:
Okay, so factory unlocked means no Verizon?
[General Questions and Answers] ATBG:
I understand.
[General Questions and Answers] Droidriven:
No, Verizon may offer factory unlocked devices, but, that only means the device can be used on non-Verizon networks, it does not mean that it can be rooted, customized, modified or use custom software.

All devices have a bootloader, whether they are factory unlocked or not, the bootloader has nothing to do with "factory unlocked" and whether the bootloader is unlocked or not has nothing to do with "factory unlocked" and has nothing to do with whether or not a device has a bootloader. We are talking about two different kinds of "unlock" and they each have nothing to do with the other, they are each, their own specific purposes. "Factory unlocked" applies to the network(s) a device can be used on, "OEM unlock" applies to what software is allowed to be used on the device itself. You are confusing the two of them and associating them to each other in a way that is not correct, separate the two ideas in your head and understand each of them alone, without the other.

If you want a device that you can root and modify or use TWRP and custom ROMs on it, DO NOT BUY A VERIZON DEVICE. None of these can be done on Verizon devices unless you go all the way back to using devices such as a Verizon Galaxy S3 or S4 or older devices. Everything that Verizon has sold since the Galaxy S5 era has been bootloader locked to prevent root and custom software modifications.
[General Questions and Answers] ATBG:
How do I make sure it's not Verizon?
[General Questions and Answers] Droidriven:
By not buying a device that is branded by Verizon, sold by Verizon or has a Verizon model number. Do a search using the model number, if it is a Verizon model number, your search results will show that it is Verizon. All or most of the US versions of Pixel devices for the different US carriers(i.e. Verizon, AT&T, Sprint, T-Mobile, etc...) are bootloader locked, buy directly from Google or by an international version of pixel with an international model number.
[General Questions and Answers] ATBG:
What about OnePlus devices? I found a OnePlus 7 Pro, I kinda want to use OnePlus instead. Does Verizon lock OnePlus too?
[General Questions and Answers] Droidriven:
What are you trying to do? What kind of "unlocked" are you looking for?

Do you want a device that is SIM/Carrier unlocked (also known as "factory unlocked") so that it can be used on a different network than it was "made" for?

Or do you want a device that has an unlocked bootloader or has a bootloader that can be unlocked by using the "OEM unlock" in order to root the device, install TWRP and custom ROMs or otherwise modify the stock software?

If you want a device that can be used on any network, you're looking for any kind of "factory unlocked" device. Many different carrier branded devices can be factory unlocked but I know that Verizon does not like allowing this on their devices.

If you're looking for something that can be customized and can use custom software, you are locking for a device that has an unlocked bootloader or at least a bootloader that can be unlocked via the "OEM unlock" setting or via fastboot commands, then, you do not want any kind of Verizon device, as in, NONE OF THEM. Stop asking about Verizon devices because I'm sure a Verizon device will not allow whatever it is you're wanting to do. Stop considering Verizon branded devices/model numbers. Stay away from Verizon devices, you'll only be wasting your money on a device that you will not be able to do anything with except use the device on their network using only the software that they install/allow.

Please stop beating your head against the wall, it isn't going to give or miraculously change into the answer that you "want" it to be.
[General Questions and Answers] ATBG:
Okay, I understand now. I choose OnePlus now instead of Google since I want a fully de-Googled experience.
[General Questions and Answers] Droidriven:
As long as it isn't a Verizon model of OnePlus.
[General Questions and Answers] ATBG:
I chose the Google Pixel 3a XL and it said it was international. That's good, right?
[General Questions and Answers] ATBG:
Thank you for helping me, man.
[General Questions and Answers] ATBG:
I found a custom kernel for it.

Does it matter if the custom kernel was made in 2019 or?
[General Questions and Answers] Droidriven:
What matters is that the kernel is made for the specific model number, it can't be a kernel for a different model number and it must be compatible with the android version on the device.
[General Questions and Answers] Droidriven:
Factory unlocked means it is not dedicated to a specific network, even if it is branded by a specific carrier. For example, it could be a Verizon device that is specifically branded/offered/sold/supported by Verizon with Verizon's company logo stamped on the device. It is possible to buy that Verizon device, then SIM/carrier unlock(factory unlock) the device and use it on any network instead of being dedicated to Verizon's network. The same would apply if it were a T-Mobile, Sprint or AT&T device or a device from any other carrier. Factory unlocked has nothing to do with what carrier the device was originally sold by. Factory unlocked only effects which networks it can be activated on.

Again, factory unlocked has nothing to do with OEM unlock or whether it can be OEM unlocked or not. They are two separate things and are not, in any way, associated with each other or have any effect on each other. Stop trying to connect factory unlock with OEM unlock. Will you please, once and for all, understand that.

As I stated, if you want a device that can be OEM unlocked, DO NOT BUY A DEVICE FROM ANY OF THE US CARRIERS(Verizon, AT&T, Sprint, T-Mobile, etc...), they pretty much all have OEM unlocking blocked, make sure the device has an international model number.
[General Questions and Answers] ATBG:
How do I check that?
[General Questions and Answers] Droidriven:
Where you get the kernel from should have information about the specific model number it is built for and should have information about which android version it is for, if not, ask questions in the thread where you get the kernel.
[General Questions and Answers] ATBG:
Okay, thanks. I just got the Google Pixel 3a XL, installed LineageOS, rooted it. Will it work with Lineage?
[General Questions and Answers] ATBG:
I have Pixel 3a XL, running LineageOS 19, looking for custom kernel.
[General Questions and Answers] Oswald Boelcke:
In this case I suggest to check here; looks like a few are available although I don't know if compatible with LOS 19:

https://xdaforums.com/f/google-pixel-3a-xl-roms-kernels-recoveries-ot.8879/
[Samsung Galaxy A50 Questions & Answers] ben.marks:
Hi all,

I've been trying to root my A505FN all day with the help of various guides but everytime Magisk starts up via Recovery method I get a bootloop. It starts up the startup wizard, then 10 seconds later reboots.

I have flashed a stock Android 10 firmware on it with BIT5 - A505FNXXS5BTLA - all working fine.

Took the AP file, and pushed it to the device, and stripped the .md5 off the end.

Installed Magisk.

Patched the AP file using Magisk App, and the log looked ok and said -patched recovery.img

Pulled the magisk_patched.tar file

Put the magisk_patched file into AP slot on ODIN, and added other .tar.md5 files as normal. Unchecked Auto-reboot

Flashed successfully, rebooted myself, and then held the recovery buttons to enter recovery to do factory reset

Rebooted again and held recovery buttons to the OEM unlock splash screen and then let go.

Boots up fine, but then 10 seconds later, reboot, can't even get past Wi-fi setup.

Any ideas? Thanks
[Samsung Galaxy A50 Questions & Answers] ben.marks:
Trying this again and flashing multidisabler, that could be the issue. If that still fails I'll be using OrangeFox and trying that method.
[Samsung Galaxy A50 Questions & Answers] ben.marks:
OrangeFox Recovery method worked with the following

- recovery sequence is Vol Up + Power button

- to get to download, from a powered off state, press Vol Up + Vol Down and plug in cable

- to get back to rooted/Magisk state, I have found the following works better

- power on device, you will see Samsung startup A50 'Secured by Knox screen'

- you then need to press power button to continue booting

- you then see Samsung startup 'secured by knox' screen again.

- once you see JUST the Samsung logo with black screen, now press Vol Up + Power

- seems to boot to rooted state with no issue
[Moto G Play (2021)] decaderider2000:
I got a locked tracfone moto g play from a relatives. I try to flash twrp to use other roms. But when I try to unlock bootloader it said:

(bootloader) usage: fastboot oem unlock < unlock code >

FAILED (remote failure)

finished. total time: 0.080s

Does that mean I have to contact the carrier to unlock my phone so I can unlock booloader? And if it is, are there any ways to install twrp without unlock it? Pls help me?

Thank for reading!
[Moto G Play (2021)] mario0318:
Not the carrier but Motorola is who you have to contact. In fact the only thing you need to do is register your phone with Motorola. Follow the instructions as stated officially by Motorola in order to get your device ID and check if your device qualifies for an unlock code. Keep in mind this is not a network/carrier lock. This is for unlocking the phone's bootloader which is essential for rooting and flashing.

In regards to TWRP it may be a hit or miss with how you follow what you got to do based on the posts spread throughout this forum and whether you'll have a flawless experience with a fully functional TWRP, or you may have one of the phones manufactured with some slightly different hardware which winds up TWRP flashing OK but no touchscreen capabilities. Or you may not even get or need to flash it and get by just sideloading the image.

Honestly, reading thru all relevant threads will be your best interest. Check out the other like-design Moto G 2021 device forums as well for additional insight on how these devices behave, quirks and common issues, etc. Good luck and try to have fun doing this.