yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Mine Mi 11 Lite 5G NE:

Xiaomi 11 Lite 5G NE - Full phone specifications

www.gsmarena.com

Not a new mode but still selling. Wasn't top of the line either (was a good value for money), but I'm still satisfied and use it daily (dual SIM, work and private, Magisk, etc). Upgraded to A13, having TWRP (of course not 'official' from TWRP.me since they don't support A13 yet)

Generally, on GSMArena you can read specs, reviews, compare specs (many Xiaomi models have Qualcomm chipsets)

Xiaomi.eu provides custom ROMs (only for Qualcomm models) that can be installed by custom recovery, and one senior member maintains a repo with custom recoveries per models (mostly TWRP but in some cases Orange Fox, doesn't really matter):

Recovery for Xiaomi devices - Browse Files at SourceForge.net

List of relevant recovery in one place

sourceforge.net

Hence, you can find a newer, more powerful model that will fit your wishes, like Qualcomm plus custom recovery

PS: Models on the Repo with recoveries is organized per codenames (eg, mine is Lisa) - to match the model names, check this table (Xiaomi.eu MIUI 14/A13 Stable ROMs, all Qualcomm):

https://xiaomi.eu/community/threads/miui-14-stable-release.67685/
[Magisk] tuxayo:
Indeed, I forgot to say that, if that's only that stuff that breaks, that's not an issue. Unless there is a risk of breaking the bootloader.

So thanks for confirming that it's should only impact the boot image. I don't know what it could do in the background.

Hm maybe that's why the install instruction have this?

(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img (note that it may wipe your data)

Installation

The Magic Mask for Android

topjohnwu.github.io

Good to know, that's terrible! :eek:

Indeed sorry that it didn't mention that reflashing system, boot, vbmeta isn't an issue. It was about if there was anything known to fear about /data or something having the keys to decrypt it.

What do you mean by "recover images"?

That's the issue

I have a fair share of apps that don't have an export function (and thinking of backuping all apps one by one has risks of missing one)

I can't trust adb backup or seedvault

TWRP can't backup /data (doesn't support current encryption method IIUC)

I don't have root to use neobackup

I feel like it's the situation of every phone with a recent Android and encryption (often enabled by default) when someone wants to root if after some time using it.

I should have come here before putting any data on the phone >_<
[Magisk] J.Michael:
If you have so many apps you can't remember them all, maybe you shouldn't worry so much about losing the settings of one of them. If you are actually creating content, pay attention and back up as you go.

I wouldn't count on being able to blindly back up "absolutely everything" and later restore.

I would think you would have the most luck saving to a removeable SD-card. As long as it is not encrypted, you can move the card to a PC and then copy its contents.

If you already have TWRP, can't you use TWRP to copy the boot partition to a file on the external SD-card, or the "download" directory in internal storage? Then at least you would know that you had the right boot image, both to patch with Magisk, and to recover from problems after flashing a patched image. Find some mention of your device to make sure you know which partition needs to be patched -- if you get the wrong one, you should still be able to use whatever you got to recover, but getting the right partition the first time cuts down on the chance of having a problem.
[Magisk] AssoorA:
Yes stock and custom rom
[Magisk] AssoorA:
I see that you have a xiaomi phoneWhile i have a Samsung galaxy Note9 (SM-N960F/DS) running on Noble rom 3.6 Zambrone, One ui 5.1 with july security patch on fake enforcing. May that be the problem, even though stock rom has the same problem?
[Magisk] pndwal:
Nothing should touch bootloader except official updates...

Well not really... that's because some devices may require verified boot disabled (or rather, strip AVB flags) in order to boot, eg some custom kernels... Generally this is no longer needed and Magisk's stance is also to leave AVB intact if at all possible... Nb. Magisk itself stripped those flags for all 2SI devices (launched with A10+) until a recent refactoring of magiskinit injection (which previously required fstab patching)... While this is no longer generally needed for Magisk, the option to disable verity is still available for devices/kernels that rely on it and Magisk instructions were updated to clarify that.

... I'd recommend paying a little extra for Qualcomm devices to any modder... China SOCs are good and work well in the wild, but for us lion tamers it's good to remember that most custom mods/solutions have been principally developed for Qualcomm SOCs.

No real issue unless you rely on custom recoveries... Magisk couldn't afford to rely on TWRP to catch up; John simply got way ahead of Dee's Troy and team in implementing needed changes to accommodate Google's ever changing boot architecture in order to support current devices and ROMs (there have been long periods where TWRP support has not been available for new devices, as is occurring again now) so a means to install Magisk that took 3rd party mods out of the equation was needed and inevitable, not to mention that there were so many TWRP issues being blamed on Magisk, or that some devices (eg many A-only legacy SAR, ie 2018, 2019) simply can't be installed from custom recovery anyway...

Still, BACK UP important data before rooting... Be prepared for the worst!... Don't wait for root to back up... Afraid that's putting the cart before the horse...

My bad... Meant 'restore images', ie unpatched (to unroot/recover bootable system)... Corrected. 👍

Unlocking bootloader wipes data (not rooting) so in "the situation of every phone with a recent Android and encryption, when someone wants to root if after some time using it" they'll generally need to backup their data w/o root in any case. (Unless they used device unlocked but unrooted for 'some time')... 🙃

😆 PW
[Magisk] zgfg:
I would not trust 'fake enforcing'

Never needed/used (I'm always on Enforcing) and IDK does it really hide Permissive mode - and if not, then you have problem (Enforcing is required)
[Magisk] sbanskot:
Hey guys,

I am relatively new to this custom ROM business, so maybe my situation is less complicated than it seems to me, so any advice would be appreciated.

I have a Samsung Galaxy Tab Active3 tablet that I have rooted with Magisk. Therefore, at the vbmeta.img level, dm-verity is surely disabled. I can confirm this because I can pretty much follow this XDA thread on modifying the system.img inside the stock super.img (Android 13) and flashing it back to the device. I do not get stuck in a boot loop or anything like that. I can confirm that I did all of this correctly.

The issue is that none of my changes that I made in the system.img persists once I boot the device. For example, I added a "hello_world.txt" into the root directory of system.img and I also added some comments to the init.environ.rc file. After flashing and booting up, these changes are gone. I am unsure as to why this is. I am using odin 3.14 to flash and I only flash the super.img partition.

Shouldn't magisk modifications to vbmeta.img have allowed me to flash custom ROM. Is my flashing step incorrect? After some research, I have some suspicion that it has to do with fstab and dtb. The fstab file in my device has the following for the system partition:

wait,avb=vbmeta, logical,first_stage_mount, avb_keys=/avb/q-gsi.avbpubkey:/avb/r-gsi.avbpubkey:/avb/s-gsi.avbpubkey

I am not sure where to go from here. This is a non A/B device btw.

Thank you for any help!
[Magisk] zgfg:
Did you ask in the thread you are quoting,. The method was posted there, they should know better...
[Magisk] HippoMan:
Thank you very much for ALL of this! This is all very useful and helpful information!
[Magisk] HippoMan:
PS: One more question ...

Is it likely that "... a newer, more powerful model that will fit your wishes, like Qualcomm plus custom recovery ..." is likely to be just as reliably and easily root-able and TWRP-able (or Orange-Fox-able) as your 11 Lite 5G NE model?

Thank you!
[Magisk] zgfg:
Xiaomi provides official procedure and tools for unlocking BL (IDK how it affects warranty). Of course, unlocking (and relocking) BL triggers Factory Reset.

The inconvenience is that once you request, you have to wait exactly 7 days = 168 hours to be allowed to unlock:

Apply for permissions to unlock Mi devices

en.miui.com

All those models in the Xiaomi.eu table that are supported with Hybrid type of Xiaomi.eu ROM - last column in the table (most, if not all there - btw, all have also Qualcomm chipsets since Xiaomi.eu supports only Qualcomm models) means that Xiaomi.eu can be flashed both from custom recovery and from TWRP.

Therefore, for each of them there exists an appropriate TWRP (or OFox), suitable for MIUI 14/Android 13 (the thread is about Stable MIUI 14 ROMs) and that recovery can be found on the SFN repository, in the folder named after the model's codename (corresponding codenames are listed in the first column, in that same table on the Forum)

Actually you don't need to manually install custom recovery. If you decide to flash Xiaomi.eu ROM (basically, debloated official Xiaomi ROMs, targeting European and Global usage), you can flash it first time from Fastboot (by running the scripts provided for Windows and Linux)

The ROM will automatically install the custom recovery. Then, in the future, you will just obtain a notification that the ROM update is available, you will click to accept, download, reboot, etc (just like for the official OTA), phone will reboot to the installed custom recovery, it will automatically flash the update and will automatically reboot. Seamless like the official OTA

They have to use custom recoveries since their ROMs are not official, hence they cannot be flashed through stock recovery

Btw, we were recently visited on XDA by their PM IngBrzy (transl: Eng Fast) in the USNF thread (Xiaomi.eu ROMs, although custom and running on the unlock BL as required for flashing, provide Basic and Device Integrity out-of-the-box-box, but that can be later affected by Google's moves on the server side)

At the end, an interesting article from 2017 about the history of Xiaomi.eu ROMs and Forum:

About xiaomi.eu work (miuipolska.pl article, English version)

This morning, I've written an article regarding xiaomi.eu history and current work to celebrate the10th birthday of miuipolska.pl site, Polish unofficial MIUI fansite, managed by @Acid. Because, well, Polish website is being visited rather by Polish people, not foreigners, I've decided to write...

xiaomi.eu
[Magisk] HippoMan:
Thank you again -- very much! -- for this additional, equally useful information!
[Magisk] eritik:
Dear guys, I'm new to this forum, I would like to ask advice from people who understand Magic and Android.

The situation is such that I installed Magisk, everything works perfectly, I put safetynet-fix-v2.4.0-MOD_2.0 on top.

Google wallet works perfectly.

But there is a problem, I need to bypass the protection of my bank so that it does not see that my phone is rooted.

When entering the bank, he does not see that the phone is rooted, but if you link a bank card through google wallet and then pass card verification in the bank's application, he sees that my phone is rooted and I have 14 days to reset the phone to factory settings.Otherwise, I won't be able to get into the bank anymore.

Question:Is it possible to get around this?

If you knit a card directly through the bank's applications, then everything is fine.But for my tasks, I need to first enter the card data into google wallet and after that, pass verification at the bank.
[Magisk] DiamondJohn:
I have never and would never use it, but every time I re-initialise a phone after clean flashing a ROM, I am sure it asks if I want Google to back up my apps and their data. ie Doesn't google provide the feature for non-rooted devices?
[Magisk] pndwal:
Starling bank detects Zygisk even with new (WIP) native bridge loaded Zygisk (built in unofficial Magisk) ATM... See workarounds and efforts in this thread:

https://xdaforums.com/t/banking-app-starling-detecting-magisk.4576421/

👀 PW
[Magisk] J.Michael:
Google saves what Google wants to save. People looking for a magic "just backup everything" don't want to be responsible for knowing what data from what apps needs to be saved. ai think they would also be disappointed if they ever restored a backup and suddenly lost everything that was changed since the moment of the backup.

On the other hand, with all the protection of one app from another, the only backing up is by calling a function that asks an app for a blob of data. If the app doesn't provide the function, or doesn't include all of its data in the blob, you (and whatever so-called backup program you are trying to use) are stuck.
[Magisk] zgfg:
With Swift Backup, I coupled of times returned to an older version of certain apps. However, I backed-up both the app and its data (screenshot). And before restoring I uninstalled the app (or at least wiped its data)

But once when I bricked the phone and reinstalled the ROM with Factory reset, Swift Backup did not recognize that it was the same phone and I was unable to restore anything
[Magisk] GrndSers-Rcng:
Hello, hopefully someone can help me with this issue.

I have a Google P7P running latest A14 and using Magisk Canary. When my phone is rooted with Magisk and I'm playing a video, or in the YTM app playing music, or with the camera app open, or Chrome open (this is just a few of the situations my issue happens), and I rotate my phone either portrait to landscape or vice versa, the phone struggles to rotate and for example if I'm in the camera app, the shutter button will gray out, or the YTM app will stop playing and forget what song it was playing, or the video that is playing will stop playing or take forever to play, or chrome will close and then minimize the whole app to PiP mode. Literally apps opened when rotating the screen will act super weird and stop working.

I never had this issue with A13 while rooted and I have tried Magisk Stable also and no modules, factory resetting and rooting right after the reset without any apps installed, etc, but regardless this issue happens in A14 while the phone is rooted with Magisk.

I have searched all over the place to see if this is happening to anyone else, but haven't seen it mentioned anywhere else. Just wondering if it's just me and if there is something I can do to fix it. Any help you guys can provided would be super appreciated.
[Magisk] Nergal di Cuthah:
My biggest fear with using swift maybe i should switch to neo, hmm.
[Magisk] Lord Sithek:
If you have access to your account you can restore apps even from different devices, especially from a cloud
[Magisk] sbanskot:
Quick question about Magisk patch compatibility.

I want to apply Magisk patch to multiple of the same devices (Samsung Galaxy Tab Active3 - SM-T577U). Is there anything wrong with patching the AP on one device, and then flashing that same AP on other SM-T577U devices? From my attempts, it seems like I can. However, just want to make sure I am not creating some issue I am not aware of.
[Magisk] DiamondJohn:
@tuxayo

when restoring an "old" backup, if the app was developed correctly, I would recommend restoring the old app with the old data and then upgrading the app. If the app has been updated properly, it should contain specific code to handle the update/correction of its own old data into a format useable with the new version of the app. But including this code can be very laborious for the devs, so sometimes its not there, especially when upgrading a few versions in a single upgrade.

Just "restoring" may not be enough to keep your old data. Its related to the reason sometimes doing a clean flash is required when doing a minor rom upgrade, and why a clean flash is basically a must when upgrading android versions. The system apps data is no longer compatible with the previous versions, to the point it will crash the system app and hence the OS. And with the complexity & number of system apps, it would be unbelievably onerous and bring dev to a halt, to include data update scripts/methods for every single system app.
[Magisk] zgfg:
Sorry if you didn't understand

My intention was to downgrade to the older version of thode apps and to keep my data (from that time)

Eg, I wanted to downgrade Microsoft Teams and Outlook. Hence I wiped their data, restored the older versions from SwiftBackup together with their data from that time.

When I opened Teams and Outlook, they synced the chats, mail, calendar and contacts but I did not need to configure them gain

And by UpdateLocker I then prevented Google Play to update Teams and Outlook to the newer version I didn't like at that time for certain reasons

Similarly with Android Auto, YouTube (back in tine) and so
[Magisk] pndwal:
This should work fine if OS is the same on each (ie configuration data matches)... Of course, DON'T flash only AP for reasons given in Samsung Installation Instruction section; flash all 4 binaries... 👀 PW
[Magisk] pndwal:
Sounds like it may be the PI deviceIntegrity fix you use rather than Magisk...

Or such things can happen if the boot image (init_boot.img for you) doesn't exactly match current ROM running, eg. you took OTA and afterward flashed back the previous patched image rather than obtaining new image to patch from the full ROM...

If you're sure patched image properly matches, issue may be related to shipping level prop which was set globally to API/SDK level 32 before @Displax's USNF Mod_2.0. However his 2.0 shipping setting no longer works for 33+ devices... He's working on a fix; I suggest you wait as setting 32 in GMS only (not globally) will likely be the best solution... His comment:

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88847911

Bit more:

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88840539

However @chiteroman has released an updated 'play integrity fix' module with the better targeted spoofing:

https://xdaforums.com/t/module-play-integrity-fix.4607985/post-88862059

... Properly targeting the GMS droidguard/attestation service will likely fix you issue if it's related to deviceIntegrity fix... I'm still wondering why @chiteroman chose to spoof old level 25 while Google only uses shipping levels of 33+ to enforce hardware-backed verdicts and 32 therefore works fine, but with targeted spoofing this shouldn't really matter (unless Google starts spotting extreme mismatches); it should work fine and you may want to give that a shot at least until @Displax updates his solution...

Nb. The original @kdrag0n USNF has been more or less broken since 2.4.0 build...

🤠 PW
[Magisk] GrndSers-Rcng:
Thanks for the reply and your help. Actually I have the issue regardless of the safetynet fix. All it takes for the issue to happen is for the phone to be rooted.

I use the OTA to update, but then download the image for the same version as the OTA to patch the init_boot with Magisk.

Now as for the device integrity fix I was using the safetynet fix MOD version 1.2 instead of the latest version until I read your reply and now im trying @chiteroman latest fix module to see if that fixed the issue, but unfortunately I'm still facing the issue of my last post.
[Magisk] pndwal:
Sorry didn't help...

Still a bit suspicious of your OTA method; I'd be tempted to download full OTA ROM and use it both to update and to extract/patch init_boot.img, but I'm really not familiar with Pixel devices...

I'd ask for help here:

https://xdaforums.com/t/august-7-20...r-root-pixel-7-pro-cheetah-safetynet.4502805/

where expert and layman P7P users congregate... 😋 PW
[Magisk] J.Michael:
Just pay attention to what you are doing. It doesn't really matter that you have "multiple of the same devices". What matters is whether they are running the same ROM. You are patching a ROM, if you are sure every device is using the same ROM, then you can get away with patching once and flashing many times.

If you are using Magisk to patch the full AP of the ROM, and when you use Odin you provide the full set of files, and they are really multiple instances of the same device (so the ROM will work on each), you are not creating any issue. Unless one or more devices have been upgraded to the point where they will no longer accept a downgrade, in which case I think you just won't be able to change it.
[Magisk] J.Michael:
If you change the Android setting so the phone does *not* auto-rotate, do you still have this issue?
[Magisk] sbanskot:
Great. Thank you. Today, I tested flashing the same patched AP on different units of the same model from the same ROM starting point and the update worked fine on all units.

While we are at the issue of flashing Magisk patch with ODIN. One thing I am having to do with my device that is not listed on any of the rooting tutorial is reflash the stock BL. After I do the first round of flashing the patched AP with the rest of stock BL, CP, CSC with ODIN (which completes with success) and then reboot the device, it goes to this:

Through trial and error, I found out that you can resolve this issue by reflashing just the stock BL with ODIN. I am wondering why this is so maybe I can make a patch to not make this happen. My suspicion is that BL also seems to contain a vbmeta.img file and maybe the vbmeta.img in AP and BL are conflicting when flashed together? Not sure. Any insight as to why Samsung is doing this?

This shows the log of magisk patching the stock AP:
[Magisk] pndwal:
Only patched AP?!!

Please confirm that you are doing what I said above (ie. DON'T flash only AP):

If you are flashing all 4 binaries (magisk_patched AP, BL, CP, and CSC if initial install needing wipes or HOME_CSC if after an OTA), do you mean you must flash BL binary again? 🤔

If not, be aware that Odin may already have shrunk your /data filesystem size, and that there are several important considerations and warnings for SAR/2SI Samsung device users specifically... Please familiarise yourself with them:

https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root 😬

👀 PW
[Magisk] J.Michael:
Are you saying that after flashing magisk-patched-AP.tar with stock BL,CP,CSP, when you try to reboot you get that error and no further progress? You never boot to Android?

How old is your device? Is Magisk being installed to recovery? Are you going from download screen while using Odin to recovery to do a factory reset before the first attempt to boot Android?

There is no excuse for "wondering" whether BL.tar contains a vbmeta. You were unpacking a super image and reconstructing a filesystem. You can use "tar -tvf" to see what files are in BL.tar.

I am interested in the second vbmeta in AP.tar: "vbmeta_samsung.img.lz4". Do you have any way of telling whether you have a partition named "vbmeta_samsung"? I do not know, but it could be that Odin, or its counterpart on your device, ignores the underscore and everything after it, and that *that* is the second vbmeta being flashed. I do not think it is likely -- the error messages include a complaint that the disable verification bit is set, which doesn't seem likely in a stock ROM.

Try flashing the unpatched, stock, all four tar files. Just to make sure this vbmeta glitch does not occur without Magisk's patches.
[Magisk] dope77:
Is it normal for a patched Samsung AP file to shrink by 1gb after patching?

Original file is 5.41 GB

Patched file is 4.11 GB

Pushed and pulled using adb
[Magisk] GrndSers-Rcng:
Yes, its still happens.