yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] eshroom:
But who exactly is it working for? I've seen one report and screenshot from a Reddit user. Everyone else I've seen test hasn't got it working. Back in October one person reportedly had dual eSim on this forum. So how do we know this isn't just another bug? I'd love it to be released in March feature drop, but I'm not holding my breath, so far I've seen no solid evidence that might indicate this, only hearsay and dubious "proof".
[Google Pixel 7] Lughnasadh:
For what it's worth...

https://twitter.com/i/web/status/1616460377071702022
[Google Pixel 7] eshroom:
Thanks, but what does this mean? Google is slowly filtering out sim manager updates?
[Google Pixel 7] EtherealRemnant:
Seeing how I was the person who had dual eSIM here, it's more frustrating for me than others who didn't have it to begin with.

That said, there has been talk since just before release about Google releasing dual eSIM in the March update (they say Germany here but there's no reason they wouldn't drop it in the US where eSIM is actually useful) so here's hoping.

https://twitter.com/i/web/status/1580249885290663937
[Google Pixel 7] eshroom:
As a European, I can confirm not having dual SIM here is a PIA, I have sims for 3 countries in Europe and when I travel further afield, I get a temporary 4th. At least with a dual SIM tray you have flexibility, but the current pixel 7 is driving me nuts. I bought it knowing dual esim wouldn't drop until March, so the lost convenience of a dual SIM tray was factored in. I just hope it does actually drop.

Do you not still have dual esim then?
[Google Pixel 7] EtherealRemnant:
It's becoming more and more common for people to carry around multiple carriers here in the US too and eSIM is really taking off.

Nope, they took it away some time between October and December. I wasn't using it at that point so I didn't notice it was gone until I wanted to use it when I picked up a second eSIM again in December.
[Google Pixel 7] eshroom:
Anyone tried Beta 3 for dual eSim?
[Google Pixel 7] EtherealRemnant:
Doesn't work.
[Google Pixel 7] Aks:
Here is what Google says.

View attachment 5829427
[Google Pixel 7] eshroom:
Taking with a pinch of salt since feature drop isn't due till march. That said, SIM manager app is not necessarily related to feature drop.

That also said, if this post on Reddit is reliable, SIM manager isn't what controls MEP (as the current SIM manager available for non Beta devices was updated in October and is Version D.2.1.473171966).
[Google Pixel 7] as10158508:
I successfully downloaded 2 esim profiles using Google Fi and Verizon. Works fine. Only flaw is can only have 1 active at a time. Using 1 esim and 1 physical sim, you can use data from one profile and calls and texts from the second profile.
[Google Pixel 7] as10158508:
View attachment 5838641
[Google Pixel 7] eshroom:
Multiple eSim profiles is standard, what is supposedly coming soon is dual active eSims.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Spectato:
Do I have to reinstall the china a11 rom and install the rom again or is this intended?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] gromas:
wym abt it ? just format storage and flash whatever u want (it will erase your data)
[Galaxy S 4 Q&A, Help & Troubleshooting] nononononos22:
So, I wanted to ask If there is unofficial, beta or similar rom on LineageOS 20 (Android 13) for Samsung galaxy s4 i9505? I found some similar rom but then I lost it and now I can't find it.
[Galaxy S 4 Q&A, Help & Troubleshooting] alecxs:
https://xdaforums.com/t/unofficial-lineageos-20-0-android-13.4502947
[Galaxy S 4 Q&A, Help & Troubleshooting] nononononos22:
This one is GT-I9506, I need for GT-I9505. There are some difference between the models too.
[Galaxy S 4 Q&A, Help & Troubleshooting] IGor2Orel:
not yet. there's lineage 19 though, 20 wip
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] tulcoturo1000:
Hello,

I recently tried to flash a custom rom on my poco f3, but I couldn't install twrp, because I didn't have the option to install it when i boot to it.

So I followed some instructions online and formated data partition to ext2, and then back to ext4. Now I can't copy any files to the phone storage and can't do anything else.

I can reboot to fastboot, and I can boot to twrp, but it's pretty much useless because I can't sideload anything, and can't install twrp anyways.

Did I do something wrong? Is it easily fixable?

Thanks in advance.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] alecxs:
f2fs?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] tulcoturo1000:
I don't understand what you mean, sorry. I'm newbie.

Should I format the data partition to f2fs？
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] alecxs:
Idk depends on ROM. MIUI is f2fs
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] tulcoturo1000:
Oh. I tried a different twrp version and could install it on the phone. Now flashed crDroid and it said my system was broke so had to factory reset. It is working now. Thanks.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] tulcoturo1000:
But now I can only access the crDroid recovery, how can I install back twrp? if I try to fastboot boot twrp.img it simply reboots back to system.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] alecxs:
try to boot TWRP from other slot maybe? (don't forget to switch back)

fastboot --set-active=other
fastboot boot twrp.img

if that fails just flash TWRP into vendor_boot partition, and restore vendor_boot.img from crDroid right after
[Galaxy S III General] vintagephoneguy:
So I have a SHV-E210S lying around, and all the roms seem to use TWRP.

Unfortunately there isn't much custom recoveries out there for this phone. So I tried flashing TWRP for the GT-I9300. It works.. but flashing anything throws a signature error. I searched c1skt (device model) and got some interesting results. Cyanogenmod recovery for this specific phone. So I tried it with a different Cyanogenmod ROM. Now it still throws a signature error. It's irritating. Any help?
[Galaxy S III General] ze7zez:
Show exactly what the error message looks like.
[Galaxy S III General] vintagephoneguy:
View attachment 5816541
[Galaxy S III General] vintagephoneguy:
I didn't mention, I flashed CWM on it as well.
[Galaxy S III General] vintagephoneguy:
It also says Untrusted Package. I am questioning the integrity of the file, but opening it in RAR has no problem whatsoever.
[General Questions and Answers] Leonniar:
Hello guys,

I run into a problem recently were my device won't boot. I tried a plethora of different solutions but nothing worked, I will have to factory reset to fix the issue.

My problem right now is that I can't access my files to make a backup. On my computer the device is connected and recognized but I can't access it's files. I also have TWRP and in TWRP Recovery it's unable to mount the Internal Storage and it shows up as 0MB. After a lot of research what seems to be the problem is that my files are encrypted, I don't know why this is (I guess for protection) but I didn't have any problems before. To my understanding if the phone is booted up you can access the files but if it can't boot then they stay encrypted. The encryption key should still be in my phone since I haven't formated it.

So how can I decrypt my data so that I can backup my files ? there must be a way for cases like this when something happens and the device can't boot, since the key is in the device it's self and I have the phone I should be able to, I also have access to every single account (google, xiaomi etc.) that is associated with this smartphone. If for security reasons that is not possible, would an authorized repair center be able to do it with proof of purchase and ownership ?

I am not 100% sure of my os version but it was 12.5.x.x, I have the unofficial twrp 3.5.0_10-beta. USB Debugging is enabled. Any other information you might need I can provide!

Thanks a lot everyone !
[General Questions and Answers] xXx yYy:
Your phone basically uses FBE ( File-Based Encryption ) to encrypt /data partition. When you boot phone into Recovery mode then the recovery.fstab file gets read by system

If you take a look into this file then you can notice that /data partition isn't encrypted ( it's only flagged encryptable and NOT fileencryption ).
[General Questions and Answers] alecxs:
TWRP will ask for lock screen credentials used for decrypting userdata partition. on FBE encryption the partition is mounted and even with no credentials provided one should at least see encrypted files.

In your case it's bit more complicated as that device uses FBE + metadata encryption. while in TWRP provide recovery.log to see what is going on. (share link to pastebin.com with expiration date 1 month)

adb pull /tmp/recovery.log

Note: there exist no relation between (FDE) encryptable= and (FBE) fileencryption= flags, these flags aren't interchangeable.

https://github.com/mhmdeve/twrp_dev...-twrp/recovery/root/system/etc/twrp.fstab#L18
[General Questions and Answers] Leonniar:
Here is the pastebin: Recovery.log

I read somewhere that changing the flags would solve the problem, after looking into it I pretty much found out what you said.

I also have an updated thread, if you can take a look it has some extra information provided !

Updated Thread
[General Questions and Answers] Leonniar:
Hello guys,So my devices is stuck in a bootloop, I want to reflash the ROM but I need a backup first.Things I've tried to fix bootloop that didn't work:

Re-flashed the boot.img

Re-flashed the vbmeta.img

Wiping cache through TWRP Recovery

Things I've tried to back up my data:

Going into TWRP to make a backup it reads: "Internal Storage (0MB)", when I try to mount system or data I get "Unable to mount."

When I use the Mount->Decrypt Data option it asks me for a password, I tried every password I ever had on the phone and any "default" ones I found online and nothing worked.

I tried the adb pull command from my computer I get: "0 files pulled, 0 skipped." and nothing gets copied over.

So I don't know where to go from here, I have some things I have yet to try like:

Re-flashing ROM (dirty flash)

Re-flashing ROM update

Flash TWRP Update (if any)

But I don't know if they're going to to anything or just waste my time. Also I am not sure any of the 3 options will 100% keep my data.I am not too worried about apps and settings but more about Photos, Videos, PDFs, TXTs and Downloads.

Any ideas on what I should do ? Thanks a lot !

My device: Xiaomi Mi 10T Pro
[General Questions and Answers] alecxs:
I:Unable to decrypt metadata encryption
E:Unexpected value for crypto key location
E:Error getting crypt footer and key

I:operation_start: 'Repair Partition'
Repairing Data using fsck.f2fs...
I:Repair command: /system/bin/fsck.f2fs /dev/block/sda34
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 4096
Info: total sectors = 28051451 (109575 MB)
Invalid SB CRC offset: 1205917355
Can't find a valid F2FS superblock at 0x0
Invalid SB CRC offset: 876348585
Can't find a valid F2FS superblock at 0x1
/system/bin/fsck.f2fs /dev/block/sda34 process ended with ERROR: 255
Unable to repair Data.

you have formatted userdata partition. your data is gone now...

I:operation_start: 'Change File System'
Formatting Data using mke2fs...
I:mke2fs command: mke2fs -t ext4 -b 4096 /dev/block/sda34 28051451
mke2fs 1.44.4 (18-Aug-2018)
Discarding device blocks: 4096/28051451 done
Creating filesystem with 28051451 4k blocks and 7020544 inodes
Filesystem UUID: c9db44bf-b076-41c6-b191-1013f3c1184e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: 0/857 done
Writing inode tables: 0/857 done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: 0/857 done

I:mke2fs -t ext4 -b 4096 /dev/block/sda34 28051451 process ended with RC=0
I:Cannot lookup security context for '/data'
Done.

to fix boot-loop, factory reset device and format userdata back to f2fs from fastboot.

fastboot format:f2fs userdata
fastboot format:ext4 metadata
[General Questions and Answers] alecxs:
of course not. stock recovery neither provides adb nor is able to decrypt data.
[General Questions and Answers] Leonniar:
But how ? I never formatted my data ?
[General Questions and Answers] alecxs:
you have formatted -> to ext2 -> to ext4 -> with the 'Change File System' option in TWRP
[General Questions and Answers] Leonniar:
That deletes your data ? I read it on a guide and it was not mentioned. I has 110+ GBs worth of files and the process was done in seconds, are you sure the data is gone ? Or that this was the cause ?
[General Questions and Answers] alecxs:
actually it's you repeating nonsense without reading explanations because usually you already "no longer participate in this thread"

https://xdaforums.com/t/recover-dat...e-is-stuck-on-boot-loop.4536965/post-87941947

btw should I remind you to forum rules ;)

https://xdaforums.com/t/xda-developers-forum-rules.4200559

No, that wasn't the cause of boot-loop. but next time you must not follow random guides without understanding what you're actually doing. yes, formatting userdata partition deletes all data. it's too late now...
[General Questions and Answers] Leonniar:
I was under the impression that changing the system file could be done without deleting the data, that's what the guide said and there was no warning or message regarding loss of data inside TWRP (for example there are a lot of messages in the WIPE section) so I figured it could work... I was out of options... damn...

So I am screwed pretty much ?
[General Questions and Answers] alecxs:
wording matters.

changing the system file could be done without deleting the data.

changing the file system of the partition not. this is common sense, no warning required.

my explanation: you don't know what a file system actually is (but then you're not in the position of dealing with file systems anyway)

https://xdaforums.com/t/question-fa...ed-to-unlock-bootloader.4531349/post-87917999

that said, if it's any consolation to you, encryption of userdata partition was already corrupted beforehand. on (plain) FBE encryption some users could repair ext4 file system with e2fsck. your device is formatted f2fs which isn't as easy to repair as ext4.

'Repair Partition' fsck.f2fs could have worked in case the f2fs file system have had (minor) issues.

But in your case most likely (if I got the recovery.log right) the early metadata encryption was broken (maybe metadata partition faulty) so there were no chance to decrypt block device anyway, which is prerequisite for mounting/decrypting or even just repairing (FBE encrypted) userdata partition.

So the chances to recover any files were very low to zero from the beginning.
[General Questions and Answers] Leonniar:
Yeah I know, for real I don't know why I didn't realize. I've been changing file systems of USB Drives to use for softmoded consoles and I format them every time. Yet I didn't even realize I did the same here...

But yeah, since I didn't have much luck from the beginning I guess it just made it easier for me to delete my files...

Thanks for all the help and the explanations !
[General Questions and Answers] Leonniar:
Hello and sorry for bothering you again.

I am currently trying to fix the bootloop, I formatted userdata back to f2fs but I noticed Cache is also on ext4 format, should I change that as well ?

Also on your original comment on how to fix bootloop you told me

But factory reset fails so I am changing the file system first before trying again.

I will also root my device again as soon as I have it up and running, will a factory reset be sufficient ? NO leftovers or anything ? Or should I go with "Format Data" or just wipe everything ?

And absolute last question, I am trying all this through TWRP Recovery. Will any of the above mentioned options (Factory Reset, Wipe Data, Format Data) delete TWRP as well ? As I said since I will root the phone again I would like to remove TWRP as well and do a clean install.

Thanks again !
[General Questions and Answers] alecxs:
Format Data is what I meant with factory reset. you can do it from TWRP. you haven't changed file system of cache therefore no need to change file system to f2fs.

You won't lose root or TWRP, unless you restore backup of stock boot.img
[General Questions and Answers] Leonniar:
Oh so Formatting Data keeps magisk ?

So there is no need for clean install of TWRP or Root ? I just update anything if needed and I am good to go ?

Edit:

After rebooting the device and trying to re-activate it with my Mi Account I can't connect to the internet. SIM Card is inserted, I was not asked for a pin and it shows no signal (there is definitely signal). Turning on wifi shows 0 available networks even tho there are plenty. Any idea why ?
[General Questions and Answers] alecxs:
you lose Magisk superuser but you won't lose root. just install apk from github again.

the other issue sounds like you lost baseband, probably due booting into wrong slot.
[General Questions and Answers] Leonniar:
Oh ok great, easy to do.

I am not sure why this happened, trying to change slots using cmd and fastboot

"fastboot --set-active=b" or "fastboot --set-active=a"

I get:

"Device does not support slots" So most likely it didn't boot in the wrong slot, any other ideas ? Should I make a separate thread if it's not an easy fix ? I don't want to keep bothering you.

Thanks again !
[General Questions and Answers] alecxs:
Did baseband work last time rooted with Magisk? check the about phone - baseband version
[General Questions and Answers] Leonniar:
Yeah I had no problems, calls sms internet everything worked. About the baseband, I can't go into settings because the device is locked, tried to get it via ADB:

"adb shell getprop gsm.version.baseband" this didn't return anything

"adb shell getprop | grep baseband" with this I got an error "'grep' is not recognized as an internal or external command"
[General Questions and Answers] alecxs:
it seems you forgot to remove mi account after unlocking bootloader, now you're locked in FRP.

download stock ROM according to your current buildno and flash radio/modem from fastboot (or flash all partitions and start from scratch)
[General Questions and Answers] Leonniar:
Am I not supposed to have a mi account with an unlocked bootloader ? No guide mentioned that and I kept it because I use a lot of it's features (cloud, that's were I save contacts etc.)

For the stock ROM I just need to find the latest version right ? I don't need the older version that was preinstalled in the device correct ? Any idea how to find which one I need to use ? The box and manual of the phone provide no information, I've found many websites to download the ROMs but none that help you find the right one with your build number like you mentioned

I also noticed that some ROMs with the same version name have Types that are either fastboot or recovery which one should I download ?
[General Questions and Answers] alecxs:
no need to remove mi account. but keep in mind you have to unlock FRP each time you factory reset device.

check fastboot for hints

fastboot getvar all
[General Questions and Answers] Leonniar:
OK great, that's fine by me

I got nothing usefull, only serialno but tried searching with that already and found nothing, I couldn't find any information using it to guide me to my Stock ROM.

I did notice that baseband and bootloader version came up empty.

I also noticed that some ROMs with the same version name have Types that are either fastboot or recovery which one should I download ?
[General Questions and Answers] alecxs:
download the fastboot variant for global, flash from fastboot with flash_all_except_storage.bat

you can check version in TWRP. mount System and check build.prop for ro.build.fingerprint

adb shell
# mount /system_root
# mount /system
# grep ro.build.fingerprint /system*/system/build.prop
[General Questions and Answers] Leonniar:
OK give me a moment because I am not familiar with how to do this part:

Running the commands, "# mount /system_root" didn't return something

"# mount /system" I got this: mount: '/system' not in fstab

"# grep ro.build.fingerprint /system*/system/build.prop" also returned nothing

Also, I am searching for ROMs at xiaomifirmwareupdater.com and it mentions: "This page shows a single update only." Will that work ?

Edit:

I have ADB and Fastboot installed on my computer but I can't find the "flash_all_except_storage.bat" script. Can I do the same thing using cmd ? Or is it better to just find and download the script ?
[General Questions and Answers] alecxs:
mount System from TWRP menu. use TWRP file explorer to find build.prop
[General Questions and Answers] Leonniar:
found it
[General Questions and Answers] alecxs:
try the grep command or view the whole file with cat
[General Questions and Answers] Leonniar:
Edit:

After a reboot into recovery cat command works

can't find ro.system.build.fingerprint reads:

RKQ1.200826.002/V12.5.4.0.RJDEUXM
[General Questions and Answers] alecxs:
extract the apollo_eea_global_images_V12.5.4.0.RJDEUXM_20210708.0000.00_11.0_eea_6ddfcb37f6.tgz 5.3 GB file (fastboot ROM) with 7-Zip and find the flash_all_except_storage.bat batch file inside.

make sure your platform-tools directory (with fastboot.exe) is in path.

double check fastboot devices and run the batch file. you will lose root and have to patch boot.img again (you can backup magisk patched boot.img from TWRP and copy to PC beforehand)
[General Questions and Answers] Leonniar:
Ok, updating you shortly.

Quick question, RJDEUXM has no MIUI13, would it be possible to update to the global rom later on where MIUI 13 is available ?
[General Questions and Answers] alecxs:
you can of course install recent version, but bear in mind Anti-Rollback Protection will prevent downgrades. I don't like Android 12 but that's up to you.

no need to quote all of my posts btw, just use the reply button ;)
[General Questions and Answers] Leonniar:
Great, I will take a look first thanks. I am using reply but it quotes everything automatically hahaha

Just a bit of clarification, should I put the ROM inside the platform-tools directory or just he .bat file or I don't have to move anything at all. Also I am not sure how to run flash_all_except_storage.bat with cmd.

I have CMD open and cd-ed into the platform-tools dir already

Edit:

Is that correct ?

Path- Environment Variables
[General Questions and Answers] alecxs:
cd into extracted ROM directory where flash_all_except_storage.bat is. just type 'fastboot devices' and 'flash_all_except_storage.bat' if fastboot is in path.

edit: if \ABD 2\ is no typo then yes ;)
[General Questions and Answers] Leonniar:
Yeah ABD is a typo I made when making the folder so yeah PATH is right.

The .bat doesn't seem to work tho:

CMD Output
[General Questions and Answers] alecxs:
no clue what is the problem with that batch file..

either comment out first two lines with notepad (prefix REM) or add these first line maybe?

@echo off
setlocal enabledelayedexpansion
REM fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *apollo" || echo Missmatching image and device
REM fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *apollo" || exit /B 1

btw: you can select terminal output with mouse, copy with Enter key, and paste the text in [CODE]tags[/CODE] here. screenshots are hard to read on mobile.
[General Questions and Answers] Leonniar:
Adding the "REM" gets me this.

Same with the extra lines but without the echos: This is easier to read, but the same error

Thanks for the tip! Here is the error:

"antirollback check pass"
Erasing 'boot' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
"Erase boot error"