yashsingh1/xdaforums huggingface dataset:
[Magisk] ssamurai:
Hello

I have a redmi note 8 when I was on MIUI 12.0.1 magisk was working perfectly with zygisk and all the modules I had.

After updating to MIUI 12.5 I lost it and that update was so laggy and full of issue so I went back to MIUI 12.0.1.

When I flash the magisk 24.3 after changing it to a zip file it flash with TWRP with no issue but when I turn on the phone I find the magisk icon when I clicked on it it asked to download and install magisk but it never does it keep the message downloading even the app had access to the storage, so I cancel that and Install the magisk APK :

which ask that it requires addtional setup and I click OK but it said it fails

then the phone become so laggy when I check the internal storage I find that the phone created a folder named 0 and start copying all file and folder from the internal storage to that folder.

When I try to unistall it from the application it said that it hasn't acess to \data

so I went to TWRP and removed it with a uninstaller zip, if I insall and old version of magisk like 23 I dont get this kind of issue

any help please.
[Magisk] alecxs:
1. you have accidentially duplicated your internal storage /sdcard aka /storage/emulated/0 aka /data/media/0.

connect adb shell in TWRP recovery. I assume you are firm with basic toybox coreutils cp, rm etc. you have to do it manually from command line in TWRP adb shell or terminal because you lost root (requires TWRP, OrangeFox, RedWolf or whatever custom recovery with encryption support or unencrypted device).

- merge /data/media/0/0 into /data/media/0 and

- delete unwanted /data/media/0/0 duplicate directory to free up disk space

Don't make any mistakes, you might lose your pictures, WhatsApp media, etc. from Internal Storage.

2. clean Magisk installation

- delete /data/adb directory and

- wipe /cache partition

- install Magisk again

You will lose all modules and superuser settings.
[Magisk] ssamurai:
Thanks for the answer I tried all the above things except removing /data/adb and wipe cache partition

I installed magisk 23.0 yesterday but didnt accept to do the requires addtional setup.

should I remove magisk then try to install the latest one then do step 2?

another question I must not reboot the phone after clean Magisk installation in step 2 just feolow the other steps directly ?
[Magisk] ssamurai:
I did what you asked and it worked

the only issue I had is I couldn't install the magisk 24.x so I installed the 23.0 and updated and everything is good

thanks
[JASJAR, XDA Exec, MDA Pro ROM Development] ghostikisme:
Hi all i want to buy an universal its not important what firm it is pls me me for prices.
[JASJAR, XDA Exec, MDA Pro ROM Development] orb3000:
Do a SEARCH on the Universal forum

There are like 3 persons selling Uni´s

Good luck and welcome
[JASJAR, XDA Exec, MDA Pro ROM Development] ghostikisme:
srry for repeating but all are sold i think :(
[Galaxy Tab 3 Q&A, Help & Troubleshooting] A-Winters:
I've recently been given a tablet and I'm looking for ways to improve its performance.

It's slow, freezes a lot and it's too outdated for most apps, including Galaxy Store. Google Play even crashes and closes itself regularly when I attempt app installations.

I'm a complete novice.

There are a few files around the forum from some time ago, are there any that are still good? Is there a list of downloads that I need, please?

Really appreciate any advice!

Device details:

SM-T210

Android 4.4.2

Kernel 3.4.5-3952694 dpi@SWDD5922 Last updated: Jan 22 2015

Build number: KOT49H.T210XXBOA3
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] HengYeDev:
This is a community port of Sailfish OS to the Galaxy Tab S6 Lite Wi-Fi.

SailfishOS is a GNU/Linux mobile operating system developed by Jolla. it uses libhybris to run on Android devices.

Disclaimer

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/

Instructions

Make sure to follow all steps carefully. Do NOT omit ANY steps!

Make sure your device model is gta4xlwifi (SM-P610) - exact match is required. LTE version will NOT work.

Install the Stock ROM for Android 10 from the firmware downloader of your choice. It might not boot at this step, don’t worry about it

Install LineageOS Recovery 17.1

Install LineageOS system 17.1

Check that LineageOS boots

Boot into recovery and format userdata

Flash Sailfish ZIP

Status

Working: Boot to GUI, Touchscreen, Wifi, Bluetooth, Camera, S-Pen

Not Working: Built-in audio, Sensors (auto-rotation, etc), Jolla store access

Download

Android base (Lineage 17) recovery and image: https://archive.org/download/lineageos20210217

Sailfish ZIP: https://github.com/sailfish-on-gta4xlwifi/docs/releases

Source code

See https://github.com/sailfish-on-gta4xlwifi for source code including kernel and Sailfish build packages

Kernel: https://github.com/sailfish-on-gta4xlwifi/android_kernel_samsung_gta4xl

View attachment 5566645
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] gimetttt:
Interesting, I wonder if it's able to run Plasma.
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] HengYeDev:
I don't think so, but you I believe can run certain flatpak apps
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] gimetttt:
Isn't this a Linux? (I know Android is also Linux, but only the kernel, a outdated kernel.)

Why can't use Plasma? I love Plasma.
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] HengYeDev:
It's not exactly a standards-conforming linux system - to get Plasma working, need to patch it for libhybris (android drivers, hwcomposer, etc) which has been done on certain devices (see debian on gemini pda for example)
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] gimetttt:
I don't think using a full-scale desktop on a small device like gemini pda (even with a keyboard) is a good idea, neither blowing up a mobile interface like Android on a 10+ inch screen. That's why I'd like to see something real useful like Plasma on such big portable device. Unfortunately I have no idea about what you said "need to patch it for libhybris"😔
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] HengYeDev:
Take a look here: https://github.com/gemian/xf86-video-hwcomposer

similar thing would need to be done to get kde working here
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] gimetttt:
Oh gosh, C with OpenGL? I don't have the intention or skills to understand this. I can only talk.
[Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri] Dexin5080:
i am surprised that this exists lmao

i hope a native Linux desktop distro will be ported into this tablet
[Android Head-Units] vaporhead:
For the life of me I cannot find an option to shut off the beeping sound whenever I touch the screen. I just installed this unit, so I'm not to familiar. Any suggestions?
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Michael Carleone:
I tried the usual key holding combinations but they didn't work. I even tried connecting headphones as suggested on reddit, but that didn't work. I'd like to wipe the cache partition and troubleshoot a font issue.

My S7+ tab is NOT rooted. Thanks
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Village_Idiot:
You need to plug it into a computer via USB for it to work.
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Michael Carleone:
Thank you. Can you confirm what the correct procedure with Android 13 is once plugged in? Thanks
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Village_Idiot:
Android 13? Don't you mean 12?

Samsung hasn't released Android 13 for the Tab S7/S7+ yet.
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Michael Carleone:
My bad. Yes, I mean 12. I noticed the fonts are now small, even after doing a factory install.

For instance, when using Google Sheets app and selecting a file from the device, the name, size, etc. fonts are all tiny now. Has anyone else noticed this?
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Michael Carleone:
BTW, I wasted hours and I lost some data because I couldn't do a clean reset as I wasn't able to get into Recovery Mode with S7 tablet connected to my PC.
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Village_Idiot:
I'm sorry to hear that. Being connected to a computer via USB and holding the power and volume up buttons, then releasing as soon as the Samsung splash screen appears is the only way to get into recovery mode.
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] rijrg4:
Hey, I don't know if you still need to know how to factory reset your tablet from recovery mode, but I had the same problem and I've followed this quick guide and it worked for me :)

1) Press the "Power" and "Volume down" buttons simultaneously until "Switch off" and "Restart" appear on the screen.

2) Press the red "Switch off" symbol on the screen and confirm again. The tablet shuts down.

3) Connect the tablet to a PC with a USB-C cable and wait until the final battery level is displayed in percent (the percentages count up and the circular ring around the battery level becomes brighter and brighter). No "recovery mode" without USB-C cable!

4) With the tablet still switched off and connected to USB-C, press the "Power" and "Volume up" buttons until the tablet has entered "Recovery mode".

5) In "Recovery Mode", the menu items can be selected with the "Volume up" and "Volume down" buttons and confirmed with the "Power" button.

6) Exit the "Recovery Mode":

Remove the USB-C cable.

For some reason it only worked after I installed Smart Switch...
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] diehard2013:
has samsung acknowledged this new procedure?

is it documented by samsung?
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] SSThing:
I spent 45 minutes chatting with Samsung support yesterday and one of the things they asked me to do is clear the cache from the recovery menu. I tried many many times using just the pwr/v^ buttons and they kept repeating the same instructions, then told me that I must have a faulty device. Eventually I quit the chat and came to look here and I can confirm 100% that when connected via USB to my pc the pwr+v^ method works.
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Village_Idiot:
I think the, plugging it in to a PC via USB requirement was implemented when it was updated from Android 10 to 11.
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] Village_Idiot:
I downloaded the latest version of the user manual (Apr 2022) and it was not documented.

I don't remember where I first saw the change. But it has been over a year; I think when Samsung updated it to Android 11.
[Sony Xperia 1 III] Nepturion:
Hi.

Been a while since I where on XDA last, had first Xperia 1, and didnt wanna unlock it to root it because of the drm keys.

I can't find a proper post about this, and want to be sure if it exists.

I have read articles like:

Flashing a Xperia 1 iii without unlocking

[GUIDE][WINDOWS] Bootloader Unlock & Relock, Drivers, Magisk rooting, Firmware and GSI ROM flashing without TWRP

I don't want to unlock the phone...
[Sony Xperia 1 III] rom4ster:
drm key losing is a myth, relocking will just re enable those and bring widevine L1
[Sony Xperia 1 III] ilukin:
@rom4ster

So, there is no reason to backup TA partition and you can unlock and re-lock the bootloader without any special actions?
[Sony Xperia 1 III] UsernameNotRecognized:
You don't have to backup anything.

Absolute worst case you can recover everything with EMMA in bootloader.
[Sony Xperia 1 III] ilukin:
I want to unlock the bootloader and try LineageOS, but i still have two years warranty on my phone. In service center they says that the warranty will void if I will unlock bootloader. So the question is, will i be able to recover everything with EMMA and save the warranty after unlocking bootloader?
[Sony Xperia 1 III] MK73DS:
First, look for your country law. Usually they can't deny your warranty for a software mod, no matter what they do.

If that fails for some reason, yes, you can recover everything and have your phone be indistinguishable as a new phone which has never been unlocked. As far as I know, there isn't any fuse like in some Samsung phones that burns when unlocked. So restoring everything is enough.
[Sony Xperia 1 III] ilukin:
Ok. And i hope my last question is:

In service menu there is no info about my current CDA. So i don't know a region of my current firmware. In service menu i see just "GLOBAL-C2", is this what i need? But in XperiFirm i see only CN, HK, SEA, TW and RU regions. There is no global. Or it doesn't matter and i can try to restore with any firmware?
[Sony Xperia 1 III] Ainz_Ooal_Gown:
yep that's some BS on sammy's part
[G1 Android Development] snoslicer8:
https://android.clients.google.com/updates/signed-kila-ota-114235-prereq.TC4-RC19.zip

Not sure when this is from. I was tooling around trying to find a way to flash myself off of the RC29 test build that I stupidly put on. Stumbled across this. Tried to flash it over my RC29-Test, and it failed with the following error:

E:Failure at line 1:
assert file_contains(SYSTEM:build.prop", "test-keys"0 == "true" || file_contains
("SYSTEM:build.prop", "ro.build.fingerprint=tmobile/kila/dream/trout:1.0/
TC4-RC19/109652:user/ota-rel-keys,release-keys") == "true"
Installation aborted.

My build contains the following line:

ota-rel-keys,for-testing,release-keys

Let me know what y'all think.
[G1 Android Development] Darkrift:
I think its something good to add to my collection :) Thx
[G1 Android Development] snoslicer8:
I think it will be good for doing file diffs when we get to that point.
[G1 Android Development] Yos025:
Thanks, It is good to have this...
[G1 Android Development] neoobs:
Has anyone thought of trying to apply these updates to the RC1 from the emulator?
[G1 Android Development] Darkrift:
yeah, some guy named neoobs thought of it, not sure if he tried it yet though ;)
[G1 Android Development] neoobs:
If I knew how to apply them I would have tried... but how do you hold the home button and the power button on the emulator? LOL
[G1 Android Development] RyeBrye:
can you mis-match specific files?

I wonder if you can mis-match specific files in the updates.

I.e I wonder if you copied an RC19 file and built a custom version - but also copied the signatures into the appropriate files - since the file is still signed and it would still verify, I think it would still work to grab old versions and mix in with new versions.

The usefullness of making a frankenbuild is probably "not much" - but perhaps if there is a vulnerable file in one version it could be injected into a later version.
[G1 Android Development] neoobs:
That won't work because there are 2 files with signatures... one of which is signed in the other. So if you change the signature file it will not validate. Pretty smart if you ask me.
[G1 Android Development] RyeBrye:
I don't see where the one signs the other - the only META-INF file that is signed is the update-script that I can see in either file.

I do see in the code where it EXPLICITLY does NOT verify the .SF files however:

for (i = 0; i < mzZipEntryCount(pArchive); ++i) {
const ZipEntry *entry = mzGetZipEntryAt(pArchive, i);
UnterminatedString fn = mzGetZipEntryFileName(entry);
int len = mzGetZipEntryUncompLen(entry);

// Don't validate: directories, the manifest, *.RSA, and *.SF.

if (entry == mfEntry) {
LOGV("Skipping manifest %.*s\n", fn.len, fn.str);
} else if (fn.len > 0 && fn.str[fn.len-1] == '/' && len == 0) {
LOGV("Skipping directory %.*s\n", fn.len, fn.str);
} else if (!strncasecmp(fn.str, "META-INF/", 9) && (
!strncasecmp(fn.str + fn.len - 4, ".RSA", 4) ||
!strncasecmp(fn.str + fn.len - 3, ".SF", 3))) {
LOGV("Skipping signature %.*s\n", fn.len, fn.str);
} else {
unverified[i] = true;
totalBytes += len;
}
}

So I think it is entirely possible to swap in other files that are signed with the same key from an older version. If they change keys, I don't think it will work.
[G1 Android Development] RyeBrye:
Another thought...

It doesn't make sense to me that the public key would be distributed along with the update - it looks like the phone is using the public key to verify the signed hashes - which is fine - they can see that the hashes were signed by the private-key pair of that RSA file...

But the .RSA is explicitly not verified, and I don't see in the verify.c file where it checks against any kind of keystore on the device...

I wonder if it is just checking that the files are signed, but not necessarily who they are signed by? Meaning - it's making sure the update hasn't been corrupted or tampered with - but not who made the update in the first place?
[G1 Android Development] neoobs:
in one of the SF's (Signature Files HAHA never caught that till now) It has the SHA1-digest of the other. I believe it is Cert.sf, at the top it signs manifest.sf

This is why you can not alter the SF's at all because they both have all the files signed with one of them signing the other. Making it impossible to get around. And with SHA1 it just makes it hard to even think about it. Might as well do as others have said and find exploits.
[G1 Android Development] neoobs:
I like that idea... anyone know how to sign the files with your own rsa?
[G1 Android Development] quedijo:
Aperantly not many people know about private-public key cryptography.

Please, if you have the time, wiki private-public key cryptography or download the podcast from TWiT (This Week in Tech) Security now on that subject (episode ~15 or so, it was early on).

A simple explination:

Two keys are generated at random (or user input through an algorithm). A private key and a public key. The private key is used to encrypt files an ONLY the public key can decrypt it. IT IS NOT REVERSABLE.

The public key can be "publicly known", hence the name. It actually has to either be with the files or on the device that needs to unencrypt said files.

Now here's the awsome part a brute force attack on SHA1 would take millions of years to crack ON ONE KEY. (Much more detail to that)

Another added mesure of security is hash checking. Run a file through an algorythm and you get an unique ID for that file. You change as much as ONE BIT on that file and the output of the algorythm is COMPLETLY different.

Not imposible to crack, imposible to stay alive long enough to see it done.
[G1 Android Development] hetaldp:
Thats the Thing with PKey and Private Key and it Impossible to crack unless the Boot loader is not checking for Signing Authority.

Please Understand Signing a File and Encrypting the File is Different thing we have G1 Update.zip as Normal Zip file but The moment we change any byte in Zip Store the Checking gets failed. if G1 Boot loader is really not checking Singer and only rely on Signed Object whosmever may have signed then we got the Solution but i dont either HTC or Google is that foolish to do that.

We must have to look at G1 Source code for Details.

I think what cmonex and Olipro does is better. Get Source code of Boot loader Recompile it with disabled Signing Funda. Load the Boot Loader into Memory and that Jump to that Location. here Root access to Device is Necesory once we are Succefull to run Patched Bootloader from Memory Flashing Customised Image may not be a Problem
[G1 Android Development] canOpoop:
can anyone post this file somewhere i can get it? it's not there anymore. My PC no longer see's my device, i'm wondering if flashing back to RC19 will work.
[G1 Android Development] quedijo:
First, you can't flash the RC19 if you have RC29.

Second, what do you mean your PC doesn't see your device? If your talking about the SD card through the phone, at the top of your phone when you have connected, you will have a notification at the top of your phone.

Either drag the notification bar or press menu on your home screen and click on Notifications. Select the USB selectionan it will prompt you, select "Mount"
[G1 Android Development] canOpoop:
First: check this out. http://www.blogsdna.com/1256/how-to-quickly-update-t1-mobile-g1-phone-firmware-manually-rc29.htm

i'm thinking if i get the file (RC19) i can flashback.

Second: It had worked before (before the OTA update). I have tried 3 different PC's 2 different USB cables, REFlash of RC29, and a hard reset (to Factory). i do not ever get a notification to mount in Notification bar. Windows throws out the error "One of the USB Devices attached to this computer has malfuctioned, and windows does not recognize it." And yes i have tried different USB ports.

i'm open to any more ideas...
[G1 Android Development] neoobs:
Use anycut and create a shortcut to the activity "SD Card" and see what it says when you open it.
[G1 Android Development] canOpoop:
Tmobile is replacing device. I should get a new on Tuesday the 11th. they are out of stock.:(
[Samsung Galaxy A7 (2018) Questions & Answers] uberpawn1337:
Does any1 have idea why android see just 16 GB of internal memory? I think it's supposed to be 64 GB. After recent soft upgrade my phone worked for some time and one day restart and didn't want to restart, so I erased it, and installed recent XEO soft downloaded from Samsung downloads. Just AP in Odin. Any clues?

Soft info says it's a750fn/ds. It's gold colour. Recovery show its a7y18lte.

View attachment 5566675
[Samsung Galaxy A7 (2018) Questions & Answers] uberpawn1337:
Reinstalled android, from the same file I did before with ODIN and it works fine.
[Realme GT Master Edition] NextB:
https://xdaforums.com/t/guide-back-to-stock-rom-howto-downgrade-howto.4014773/post-81108309

this guys says

I have found out that in fact stock recovery does not exist as a prebuilt file :) It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p

It means in theory you can recreate stock recovery having only Realme ozip file.

EDIT1 The command to do it in Linux shell is

Code:

bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p

Cool! Tested.

EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should.

EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader.

EDIT4 In order to combine everything in one place:

Stock recoveries for RMX1991 (China version): here

Stock recoveries for RMX1992 (India version): here

Stock recoveries for RMX1993 (Euro version): here

EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there.

EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why).

any idea how to explain this in easy understanding word for me to have a stock recovery.img for RMX3363