yashsingh1/xdaforums huggingface dataset:
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Shahaf:
Hello,

I tried to root my 9T(model M2010JI9SG) following this guide:

I used twrp from this link:

Xiaomi Mi 9T / Redmi K20

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me

version 3.5.2_9-0

after I flashed twrp, I got into fastboot mode, which I can't leave.

I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,

I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.

Please help me fix that,

Thanks!!!
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
OMG

You should first of all know your phone model

"Redmi 9T" reads as different name than "Mi 9T", isn't it?

Hence you MUST NEVER flash TWRP for Redmi K20/Mi 9T (guide clearly says it is for that phone, check the big picture in your post) to your Redmi 9T
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Shahaf:
oh damn, I can fix that somehow?
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
Check on twrp.me is there TWRP for your Redmi 9T

Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP

For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Shahaf:
Thank you, I will check with them!
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
Here you can find firmwares for lime:

Xiaomi Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com

You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)

You could also use MiFlash tool to flash the whole firmware, but it must be not needed
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Shahaf:
It worked!!! now my device is working, now in order to root, which twrp should I use?
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)

Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition

If anything goes wrong, flash back the stock boot img

Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?

Generally, use Magisk Stable v23 from TJW:

Magisk/README.MD at master · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Shahaf:
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img

it did ok on sending, but then failed on booting(unknown command), any fix for that?
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Andrologic:
Flash (not boot) a healthy un-patched stock "boot.img" that is signed with your ROM version to the device and see if that works.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
fastboot boot xxx.img boots one time to the xxx.img

For flashing (permanently) to boot you need to use:

fastboot flash boot xxx.img

Before flashing the 'stock' or patched boot img, pls double check: compare your firmware name in Settings / My device against the fastbboot/tgz package you downloaded and extracted the boot.img from

Recovery images might be the same for several firmwares, but boot.img is more critical. If extracted from the wrong firmware, it will not be your real stock boot.img and will not boot

You can use this app (now when your phone boots) to download and look for the proper firmware:

MIUI Downloader - Apps on Google Play

MIUI upgrade app for Mi users.

play.google.com
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.

Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):

[TWRP][OFRP][PBRP] List of relevant recovery in one place

https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I compiled this list because i think it will be useful. Updates are monitored each day. Welcome, friends! https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/

xiaomi.eu

Based on experience with my 9T I would pick

twrp-3.5.2_10-3-lime-brigudav.img

I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)

The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash

That means if people recommend the TWRP as there, it nust be the right one

Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img

You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Shahaf:
it worked! thank you
[Samsung Galaxy J6 Questions & Answers] Makumba666:
Hi all,

First of all I KNOW how to use google and I checked different messages about spots on android phones. My case is different: I see not some abstract spot on phone display, but light sky blue circle and inside it 60. The whole thing is barely visible. At fist I even thought it could be some information displayed by some app, or some bug caused by me (I am game developer), but after factory reset damn thing is still there. Any advice?
[General Questions and Answers] waletogo:
Please sir how to fix fatal : not a git repository ( or any of the parent directories) : .git

Thanks you sir
[Samsung Galaxy S21 Questions] stebrick:
I'm just wondering how secure Samsung's Secure Folder is if I use it as a Sandbox for those high-risk or untrustworthy app (like some from China).

I was told it's supposed to be a sandbox for it doesn't allow any access to the data outside the Secure Folder, but I'm not sure how permissions works in it (like access to GPS/ Phone Call or other hardware). I suppose they couldn't have any access to my phone call or GPS location if I'm not inside the Secure Folder (how about if it's in background)? But on the other hand, access to bluetooth or camera are inevitable when some apps might need it.

If those apps within secure folder can have access to my phone call then I would be much worried about those high-risk app monitoring phone conversation.

I might be wrong. Any insight or elaboration would be great :)
[Samsung Galaxy S21 Questions] monsiu:
last i checked secure folder is where you can store notes....images....and apps(i guess)

you store them and only you have access to them through pin.

its not a sandbox bro....its just a secure folder :)
[Touch Diamond, MDA Compact IV Themes and Apps] jman069:
Has anyone been able to use this app? After registering it sends an sms to your phone and after clicking on the included link it says my device is not yet supported however they said the diamond was supported over a month ago:confused:

http://www.qik.com/

it's a live streaming web video that uses your phones camera and is completely free.

I'm about to try LiveCast to see how that works as well.

Thanks

EDIT: LiveCast doesn't seem to work well with the diamond.

Also when trying to log in at www.qik.com/ on my diamond I receive this message:

Unrecognized user Agent for wap_client_instructions "Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile7.11) Sprint MP6950SP"
[Touch Diamond, MDA Compact IV Themes and Apps] grandinferno:
Hmmmm... weird. Works fine on my Touch Pro. Might have something to do with...

1. I'm using the Australian Three ROM.

2. I'm using Opera as my browser.

3. I'm using a Touch Pro.

*shrugs
[Touch Diamond, MDA Compact IV Themes and Apps] WvanWaas:
Qik is installed here but it will not start up. Just the windows mobile wait cursor and then nothing... Someone????
[Touch Diamond, MDA Compact IV Themes and Apps] AndyLuft:
i tried

no problems here...

download, install, program launch and streaming works like a charm
[Touch Diamond, MDA Compact IV Themes and Apps] WvanWaas:
hm strange maybe i need to try another ROM
[General Questions and Answers] Shivam@07:
ROM
[General Questions and Answers] Deleted member 1890170:
Ask Xiaomi this question. :)
[Samsung Galaxy S21 Ultra] VoidedKN0X:
I just rpoted my 5 month old S21 Ultra and i've noticed since then my sim card suddenly drops out (on firmware not litterally) and 3 seconds later it reconnects... Anyone has that problem or do i need to install or modify something?
[Samsung Galaxy S21 Ultra] blackknightavalon:
I was looking everywhere for this exact problem. I'm having a similar problem but only when my SIM card is in an Android device, not an iPhone. I currently have it in a rooted phone and I'm running a logcat to see if I can find the cause (good thing I have two numbers).
[Redmi 9 Power / 9T] Shahaf:
Hello,

I am big fool and by mistake I flashed mi 9t version instead of redmi 9t,

my redmi 9T( ofmodel M2010JI9SG) was flashed using this guide(for mi 9t):

I used twrp from this link:

Xiaomi Mi 9T / Redmi K20

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me

version 3.5.2_9-0

after I flashed twrp, I got into fastboot mode, which I can't leave.

I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,

I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.

I assume I need ro flash another version,

please help me,

thanks!
[Redmi 9 Power / 9T] Lime user:
Use miflash tool
[Redmi 9 Power / 9T] Lime user:
Use mi flash tool and u will also need correct firmware for ur phone
[Upgrading, Modifying and Unlocking] ossy81:
Hi,

is is possible to disable vibrate when i receive a sms when i'm on the phone. It's very anoying when the phone vibrates when i speaking someone. It would be great if i didn't get anything (no sound, no vibration) when i'm calling.

But i want the phone vibrate when i receive a sms and not calling.

Osman
[Samsung Galaxy A12] edward0181:
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS

Install instructions:

1. Download an arbitrary SM-A127F firmware zip package on SamMobile.com, whose Android version is 11

2. Flash by Heimdall by PIT partitions or by Odin by BL, AP, CP, and CSC tar packages

3. Back to the stock ROM > go to Developments settings > allow OEM unlocking (Developments settings could be enabled by tapping 7~10 times somewhere in About Device)

4. If OEM unlocking is unseen to you, take software updates first

5. Also inside Developments settings, enable USB debugging

6. Download the TWRP image, and unzip.

7. Hold <VolUp>+<VolDn> with device tethered to USB-C with your PC

8. Hold <VolUp> to unlock OEM

9. Hold <VolUp>+<VolDn> again with device not disconnected of USB-C

10. Press <VolUp> without holding to enter Download mode

11. Open ODIN to flash the downloaded TWRP in AP slot with my TWRP image.

12. Hold <VolDn> + <Power> to shut down, then Hold <VolUp> + <Power> to reboot to TWRP

Important: device must boot directly to recovery or stock recovery will be restored if you boot direct to OS.

13. Enjoy!

What is working:

Mounting, flashing

What is not working:

Please do let me know.

Device tree: Links removed and thread locked. @edward0181 Check PM.

CHANGELOG:

25-10-2021:

Changed FSTAB issues, Sideload/MTP and ADB issues.

Reserved free space on dynamic partitions to flash GAPPS if needed.

21-10-2021:

Initial post, issues to be expected.
[Samsung Galaxy A12] LAST_krypton:
Nice work.
[Samsung Galaxy A12] uluruman:
edward0181, thank you for making all this possible! I have a problem though: I want to install LineageOS, I have successfully got TWRP running after repackaging your .img into .tar and flashing it with Odin but I cannot go any further: the SD card contents cannot be read from TWRP and ADB sideloading does not work as well, because the USB device is not detected by the PC when TWRP is working. There is no way to upload any image. Also wiping does not work with lots of "failed to mount" and "block device required" messages. I tried OTG also and it does not work as well. No way to flash the OS.
[Samsung Galaxy A12] uluruman:
You have to repackage it into .tar archive.
[Samsung Galaxy A12] uluruman:
No further help needed, my phone is bricked. I tried to follow the instructions on how to root it, presuming that was needed to move on in my intention to install Lineage OS. I think now it's completely hopeless: it's stuck on the welcome screen (the one with the warning sign) and not detected as a USB device at all at any stage. It just reboots after several minutes, and that's all. All I can do is force to reboot it by pressing power+vol down. No other key combinations work. So bad I can't get into the download mode without USB connection. Or can I?

OK. I have managed to unbrick it by prying the case open, unscrewing some screws inside to reveal the battery connector and disconnecting the battery. Then I have reconnected it, partially closed the case to make the buttons available, pushed vol up+vol down and connected the USB. Voila: it was in the download mode. I have reset the bootloader and reuploaded the stock OS. Fine, now back to the LineageOS problem.

Question: Is it possible to upload the LineageOS image with Odin so that it will be availabe for flashing with TWRP (USERDATA partition may be)? Or may be it's possible to flash LineageOS directly with Odin, like the stock image?
[Samsung Galaxy A12] LAST_krypton:
@uluruman ​

You are not the only one who has ADB sideload issues, DEVI will fix them soon enough... One dude reported his phone wasn't getting detected in SIDELOAD mode but in normal RECOVERY mode was. You probably have same issues, you can try pusshing LinageOs.img file to ROOT directory which isn't encrypted and can safely install Linage then.

Push the file by ADB PUSH

adb push LinageOs.img /root/

After pushing LinageOs Image file you can follow my guide for installing it normaly...

https://xdaforums.com/t/installing-twrp-and-linageos.4334465/

https://xdaforums.com/t/covering-some-misleading-theories-and-issues-with-our-a12.4336999/
[Samsung Galaxy A12] LAST_krypton:
deleted
[Samsung Galaxy A12] uluruman:
Thanks LAST_krypton! Unfortunately the push method does not work for me either, the filesystem is read-only. I guess the phone must be rooted but this is not possible: the magisk-patched file causes the infinite reboot cycle. I tried it again, in case I did something wrong. I also tried some other methods (sideloading via the fastboot, repackaging the stock firmware) but none of them work for one reason or another. Actually just getting rid of the forcefully installed Russian software (which is included in the prism.img) would be enough for me, but I could not accomplish it either.

As of the LineageOS: may be there is some other dir is available both via adb and TWRP, which does not require rooting?
[Samsung Galaxy A12] LAST_krypton:
Disable READ_ONLY restrictions either by TWRP or ADB. You can follow my guide for rooting, it is for the whole enviorment and you have the patched VBMETA with BOOT image.

https://xdaforums.com/t/unlocking-the-bootloader-and-rooting.4331859/
[Samsung Galaxy A12] uluruman:
Thanks, I'll try it!
[Samsung Galaxy A12] edward0181:
CHANGELOG:

25-10-2021:

Changed FSTAB issues, Sideload/MTP and ADB issues.

Reserved free space on dynamic partitions to flash GAPPS if needed.
[Samsung Galaxy A12] uluruman:
Guys, is there another way to reboot into recovery after flashing? I just can't catch the moment when I should press power+vol up, it seems just impossible, it always gets into the red text warning screen, hangs for a while then vibrates and goes on into Android. Strangely enough, I could boot into TWRP with the first release, and can't with this second one. It wasn't easy with the first one but I could do it two or three times. Now I can't do it at all. Strange. Anyway, I'll keep on trying before making conclusions.
[Samsung Galaxy A12] LAST_krypton:
Just when you see the warning screen stop pressing vol + and then after goes from warning PBL unlock screen to LOGO hold vol + again. You can try "adb reboot recovery" from download but dout that will work.
[Samsung Galaxy A12] LAST_krypton:
Once you get good like me, you can reboot and with your fingers still enter download mode or recovery mode in 5s:p
[Samsung Galaxy A12] uluruman:
OK, I'm trying it this way:

1. Flash TWRP then power off manually (auto reboot is turned off in Odin)

2. Push Vol+, then Power and hold them

3. The first logo screen appears

4. The warning screen appears and immediately disappears because I'm still holding the Power button (no time to release the vol+ button here)

5. The second logo screen with the red text and the yellow warning sign appears

6. It vibrates and the Android boots up (just the single Samsung logo on the screen)

At which stage I should release the Vol+ button? May be I should release the Power button at some point?

P.S.: adb does not work in the Download mode, of course. I tried.
[Samsung Galaxy A12] uluruman:
I already know the trick to get into the Download mode with fingers at any point ;) But still no recovery mode.
[Samsung Galaxy A12] uluruman:
Well, sorta... I've found a reliable way to get at least into the stock recovery mode:

1. Connect the phone to PC

2. Turn it off

3. The charging screen appears, with the bolt sign

4. Once the bolt sign changes to the percent counting, press and hold Power + Vol up

5. Hold the buttons until it gets into the recovery mode

Works all the time for me. This method does not work after flashing TWRP though, it just hangs on the second logo screen. I suspect it actually tries to run TWRP at this point but can't, and it's the software problem, because once I allow it to go through and restore the original Recovery program, it boots into Recovery just fine following these steps. But never gets to TWRP.

Quite often after that TWRP loading attempt the phone becomes always hanging at this second logo screen on every boot, without holding any buttons, so I have to reflash the AP partition completely to restore it (reflashing recovery.tar.md5 does not help). I don't know what's wrong here.

My phone is SM-A127F with the SER (Russian) v3 firmware.
[Samsung Galaxy A12] LAST_krypton:
Are you sure you are flashing the correct TWRP.tar.md5 file, if you are on android10 that could be the reason why, try on latest android 11.
[Samsung Galaxy A12] uluruman:
No it's Android 11, and the file I downloaded is the latest from this thread, it's recovery.tar.zip (inside of which is recovery.tar.7z, inside of which is recovery.tar.md5). It all seems correct. Anyway I'll leave the attempts for now, because more v3 firmwares have been published today on samfw.com. I have installed the non-Russian one which is pretty clean of suspicious government-pushed apps, it'll do for now. At least for now.
[Samsung Galaxy A12] IchZerowan:
Great thanks to edward0181 for the job!

I am trying to get TWRP on my SM-A127F TWRP SEK, but I am facing some errors:

1. I have successfully unlocked OEM, and am able to enter the download mode

2. I am successfully flashing the provided .tar.md5 archive into AP with Odin 3.14.4 with auto reboot turned off. After getting the success in Odin, I turn the device off by pressing <VolDn> + <Power>, then try to boot into TWRP but stuck on the welcome screen just like uluruman mentioned

3. First, I disconnected and reconnected the battery and was able to get into Download mode once again, but then found a better way: press <VolDn> + <Power> to restart. When the screen gets black I quickly press <VolUp> + <VolDn> and insert the USB before I can see the intro logo to get directly into Download mode (might be helpful for someone).

4. After several attempts I am still not able to boot into TWRP, getting either stuck on the welcome screen or somehow booting into the stock OS.

5. I then tried to root the device (chances are, TWRP might work on a rooted device) following this guide:

https://xdaforums.com/t/unlocking-the-bootloader-and-rooting.4331859/

6. After successfully flashing the magisk patched and turning the phone off I can see only the charging screen (the first one, without numbers) and it doesn't get any further before force reboot (<VolDn> + <Power>).

7. Following the same logic as with step 3, I tried to press <VolUp> + <Power> during the reload when the screen is black and it worked, I managed to load the bootloader. However, after the factory data reset and whipping cache partition I get stuck on the welcome screen, as with step 2.

8. Flashing the original firmware works well.

Any ideas of what else should I try to finally install TWRP? The primary goal is to install LineageOS or AOSP.
[Samsung Galaxy A12] LAST_krypton:
DM-VERIFY must be disabled or only root user will be able to get in to TWRP. You must first follow the rooting guide and then flash TWRP.

https://xdaforums.com/t/unlocking-the-bootloader-and-rooting.4331859/

https://xdaforums.com/t/installing-twrp-and-linageos.4334465/

Very simple, but if you get problems with beeing stuck on MICS partition (or which ever partition is charging screen stored, maybe LOGO) you just have to force turn of the phone and boot in to DOWNLOAD before triggering partition as said above.
[Samsung Galaxy A12] IchZerowan:
I tried rooting it once again, but I cannot boot after flashing (step 13 of the guide), it's stuck once again on the welcome screen. I can enter the download screen, but flashing it once again doesn't change a thing.

When I flash the magisk patched tar and try to get into recovery with <VolUp> + <Power>, I first get the Android logo with the "Erasing" phrase, and only then I am able to get into recovery with the same keys. Is this OK?
[Samsung Galaxy A12] LAST_krypton:
You are supose to do a wipe data and earse cache.
[Samsung Galaxy A12] IchZerowan:
Sure, that's what I did during all three (now four already) attempts.
[Samsung Galaxy A12] uluruman:
Yes, all the same with my phone. My suggestion is that is has something to do with the fact that the stock firmware is rev. 3 (and it's not downgradable). Because I had had successfully installed TWRP earlier on, when the firmware was the one from the factory, which I guess was rev. 1 or 2. Then I followed one of the instructions and carelessly reflashed it to the latest rev. 3 and never had any success since then, neither with TWRP or the Magisk-patched files. Can anyone confirm successful installation over any rev. 3 firmware?
[Samsung Galaxy A12] LAST_krypton:
Could be a fimware bug, so try other. And do you get in a bootloop or it just gets stuck on warning screen? Maybe wait for a litle until it boots to system, it can take some longer time.
[Samsung Galaxy A12] IchZerowan:
In my case it just reboots after a while.
[Samsung Galaxy A12] physwizz:
I have installed lineages and pixel experience

Exynos 850 Resources

Installing a GSI for Exynos 850 Note: Don't upgrade your system to Android 13 if you want to use sim card with GSIs WARNING: INSTALLING A GSI MAY OCCASIONALLY RESULT IN THE LOSS OF IMEI Reinstall stock firmware to restore it. Download Android 11 GSI (arm64 ab) with GApps 1. Unzip img file...

t.me
[Samsung Galaxy A12] physwizz:
Try this

https://xdaforums.com/t/physwizz-a12s-kernel-twrp.4352297/#post-85879491