yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] hansdg1:
i take it that no one has been thinking about this in a long time. i still think this would be a really cool idea!
[Windows Mobile Development and Hacking General] :
How about a way to map a ftp server?
[Windows Mobile Development and Hacking General] cliffordconradsumner:
Just thought I'd bump this because it is such a fantastic idea.
[Windows Mobile Development and Hacking General] codybear:
I thought about this a LOOOOOOOONG time ago.

But never tried to do anything with it.

Maybe someday in the near future I'll mess with it.

But it won't be for a while since I'm working on starting a business.

(check my faq link in signature, last post for a better timetable of my schedule).
[Samsung Galaxy M31 Questions & Answers] abhishekgupta92:
Hello everyone,

I am looking for TWRP recovery image for Samsung M31s. Everywhere I seem to only find either M30s or M31. Kindly help. Unable to root the device so far. Thanks.
[Samsung Galaxy M31 Questions & Answers] pipkakill:
ROOT without TWRP

1. Download the latest firmware to your phone.

2. copy boot.img from the downloaded firmware to the phone:

2.1 On a PC, go to the folder with your unpacked firmware and find the AP file.

2.2 Open it with the 7-Zip archiver (download 7-Zip from here - https://github.com/mcmilk/7-Zip-zstd/releases/tag/19.00-v1.4.5-R3)

2.3 Inside there will be a file boot.img.lz4 - open it.

2.4 It contains only 1 boot.img file - unpack it and copy it to your phone.

3. Patch the file with magisk

3.1 Install Magisk Manager on the phone. (https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk)

3.2 Open Magisk and click INSTALL. Patch boot image. Select our boot.img file. Install.

3.3 When finished, the magisk_patched.img file will appear in the Download folder

3.4 Copy it to a PC, rename it to boot.img and archive it to TAR via 7-zip.

3.5 There should be a boot.tar file inside which the boot.img file

4. Stitching.

4.1 Turn off the phone. We transfer to Download mode (hold down 2 volume buttons and connect with a cable to the PC).

4.2 Open Odin.

4.3 Select only the AP field in which we specify the boot.tar file. Do not touch the rest of the fields (leave them empty).

4.4 Press start.

4.5 The phone must flash and turn on with root.
[Samsung Galaxy M31 Questions & Answers] abhishekgupta92:
After all these steps, i had to open Magisk again and it updated itself, and now the phone is rooted. Thanks everyone.
[Samsung Galaxy M31 Questions & Answers] sammiev:
As a summary, after installing Magisk in recovery (starting from power off):

(Power up normally) → (System with NO Magisk)

(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)

(Recovery Key Combo) → (Splash screen) → (Long press volume up) → (Recovery Mode)
[Samsung Galaxy M31 Questions & Answers] abhishekgupta92:
@sammiev - I didn't understand. This is summary of?

Once the boot.tar file is stiched using Odin, a normal reboot would launch the rooted OS, right?
[Samsung Galaxy M31 Questions & Answers] pipkakill:
does everything work well?
[Samsung Galaxy M31 Questions & Answers] sammiev:
This is for root without TWRP

The second choice would boot you in root mode after doing what @pipkakill posted.

(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
[Samsung Galaxy M31 Questions & Answers] Wynfirdolf:
would this allow me to install custom roms?
[Samsung Galaxy M31 Questions & Answers] Jayanthan:
my Samsung M31s keeps calling emergency services 112 more than 30 times a day. how to disable triple press power button panic mode option. I have changed the settings ,I have uninstalled all the packages with com.sec.android.emergency using adb ,still there is no use. kindly suggest me a solution to stop this .my phone is running on android 11 and I am using Indian SIM .thank you
[Samsung Galaxy A10 Questions & Answers] mauuh:
Hi, I'm from Brazil and would like some help. i have a samsung A10 and i was updating magisk and i don't know what my android is blocked on the download screen. I've tried everything and nothing. I need a lot of help.View attachment 5323797View attachment 5323799View attachment 5323801
[Samsung Galaxy A10 Questions & Answers] BrotherBoard:
maybe magisk you installed is not complatable Bro you have to flash twrp recovery again. If didn't worked flash stock ROM again.

Is the bootloader unlocked?

If it Is unlocked here is some useful steps.

First get Odin latest version.

Flash latest twrp Version

CHECK if the boot loader is unlocked.

Also google it lol

If didn't worked you have to flash stock ROM again.
[Xiaomi Redmi Note 7 Questions & Answers] leprince2007:
Hello everybody,

I bought redmi note 7 from 6 months ago.But my battery lasts only for 6-7 hours sot.

I use the old rom miui pro 9.4.11(extreme debloated)+Sys config patcher+lkt.

I want to know the best rom in battery for redmi note 7.

My usage is social media apps and calls only and performance is not important.

Please help me
[Xiaomi Redmi Note 7 Questions & Answers] matthias1976:
When deepsleep work correct there are no significant changes between roms.

It all depends on screen brightness.

Its big difference if u watch YouTube on wlan in dark room cost ca. 8%/h akku or using gps navigation on lte in the sun cost up to 15%/h
[Xiaomi Redmi Note 7 Questions & Answers] insomniacno1:
Mine last a lotnlonger than that, I have about 6 hours gaming + some web browsing and other stuff = 9hours. If normaluse and maybe 2 hours gaming the battery last about 1.5 day - my phone is about 2.5 years old now, but I just got. new original battery.. I suggest you take it back to the dealer or go to authourized MI service center and get the battery checked, if faulty theb they can change it on the spot. NOT MI shop, they don't do service. Do NOT buy battery online(they are ALL fake), Xiaomi don't sell batteries online, it can ONLY be purchased in their service centers + fee for replacement (if not in warranty).
[TouchPad Development] AHChan:
I have done the install as directed. My Touchpad boots to Evervolv with a clock on an otherwise blank screen. When I swipe up I get 11 resident apps. How do I access and download additional apps like Kindle Reader or SimplyE for library books? And, I am unable to add my Gmail account via the settings app on the app page. The browser works, as does the calculator, calendar, gallery, and even the camera (upside down). Any guidance would be welcome. Thanks, Alan ahc.1440@gmail.com
[TouchPad Development] HP_TOUCHPAD:
To add apps using the google store the Open Gapps must be flash in TWRP:

Select Arm platform and the version of android:

https://opengapps.org/

There are other ways to install apps:

using the aurora app store, doe snot need google services:

https://xdaforums.com/t/app-4-4-aurora-store-open-source-play-store-client-april-8-2021.3739733/

Or directly from a web browser, apps could be downloaded to PC then copy to Tablet and install.

https://m.apkpure.com/

https://androidapksfree.com/
[TouchPad Development] AHChan:
Much appreciate the response and guidance. I made it work! Thank you!!
[Google Pixel 3a XL Questions & Answers] brezzz:
Hi

Just got 3a XL today and unlocked bootloader. I understand that twrp doesn't work above android 9, but how can i root android 11? can the stock boot image be patched with magisk, or does it need to be a customer kernel and if so which ones work?

Many Thanks
[Google Pixel 3a XL Questions & Answers] Tulsadiver:
You should be able to just patch the stock boot img.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
EDIT: i'm really not sure about the correctness of this now. I'll leave the thread up as a sort of guide, but you'll need to do your own checks on ARB. Sorry, i read a couple of threads and thought i had it clear, but now i am not so sure...!

[Alioth, my device: Poco F3] Just writing this in case anyone else faces issues with ARB (anti rollback) while using MiFlash...

I was using a xiaomiEU rom later than the stock backup rom i downloaded which threw an ARB error in MiFlash Tool.

So i checked the ARB status using fastboot cmd 'fastboot getvar anti' which results with 'anti: 1'.

As far as i have found: anti:1,2 or 3 means that anti roll back is not active, it's safe to roll back. 4,5 and ARB is activated (if 4 or 5 are/become active from flashing roms since the time of this post, DO NOT FLASH downgrade rom).

Contained within the extracted rom folder are .bat files that correspond to each action you select in MiFlash (clean all etc in bottom right corner). Simply rename the associated bat file to the action you want to .txt at the end, instead of .bat ie flash_all.bat becomes flash_all.txt and open with notepad

Then delete all text at or near the top with reference to ARB/Anti etc. DO NOT DELETE any fastboot lines. Save and exit.

Rename the file back to .bat

Run MiFlash now without error. BUT, i MUST reiterate. CHECK YOUR ARB status BEFORE, as per opening of this post. If it's 4 or 5 DO NOT ATTEMPT TO ROLL BACK versions.

Many thanks to @pl1992aw for the additional info... taken from post below, i stand corrected;

It doesn't mean "anti:1,2 or 3 means that anti roll back is not active"

If your current Rom is anti 2,

1) you can flash Rom with anti: 3, 4, 5, 6... etc. and the anti will become 3, 4, 5, 6... etc.

2) you can flash Rom with anti: 2, and the anti will remain anti 2.

3) you CANNOT flash Rom with anti 1.

Source:

https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/

and also;

If anti roll back index is 0, that means no anti roll back at all of that Rom, it will not check or change your device ARB index.

Make sure you look at the index correctly. I don't own poco F3 or Mi11x or redmi K40. You have to double check it yourself. You are the one decide to flash.

I would like to also add: those lines in the .bat file are there for a reason, they should prevent bricked devices by preventing wrong flashing. Edit at your own risk!!

View attachment 5323869
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TheBatsEar:
I had to find out all that the hard way, sadly.

Couldn't install Pixel Experience Rom over 12.0.5, learnt i must downgrade to 12.0.3 to try again first. Had that Antirollback feature error, looked into the .bat file and just removed it all. I was then able to downgrade and install the Pixel Experience rom.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] sheikh55:
What if ARB gets activated ?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TheBatsEar:
The script stops and the fastboot commands in it don't get executed and you start scratching your head why that is.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
It doesn't mean "anti:1,2 or 3 means that anti roll back is not active"

If your current Rom is anti 2,

1) you can flash Rom with anti: 3, 4, 5, 6... etc. and the anti will become 3, 4, 5, 6... etc.

2) you can flash Rom with anti: 2, and the anti will remain anti 2.

3) you CANNOT flash Rom with anti 1.

Source:

https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Alin45:
As @pl1992aw said, anything than 0 in anti: x means ARB is active, so u can flash the same/greater ARB than u already have. I said that because many ppl on here said that if ARB is 4 only means the ARB is active.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] sheikh55:
Thank you everyone for putting pieces of knowledge regarding anti rollback.i think people who frequently flash roms should have all understanding about their devices and in this case this one is must because many people have bricked their phones lately and somebody should make a thread with proper guide about how to downgrade or recover from bricked by using mi flash tool.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
Downgrade with unlock bootloader should be possible.

You have to remove anti roll back from the official Rom, creating a modified rom, then you should be able to downgrade. (MIUI by Xiaomi.eu might have their ARB removed, so you can ask them how to remove it.) Of course this will need to be flashed with custom recovery like TWRP. The official Mi-flash might not pass if you modified the rom since it will become a custom Rom, even if most part is the same as official, the hash check or some checks won't match.

Locked bootloader is a different story. The proper way is limited, mostly to find either Xiaomi official repair service, or find EDL account and pay for it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Suhaas:
thanx a lot for the info bro. its very useful.

i just checked the anti rollback of my devices. its 1.

i had MIUI 12.5.1.0 in my phone. Then i unlocked my bootloader then flashed custom ROM Arrow OS. its working fine so far. and i have downloaded fastboot ROM MIUI 12.5.1.0 and checked for its anti rollback index. its 0. if i want to go back to stock ROM means what shall i do? shall i just edit off the anti rollback lines and delete them then will i be able to install the ROM?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
If anti roll back index is 0, that means no anti roll back at all of that Rom, it will not check or change your device ARB index.

Make sure you look at the index correctly. I don't own poco F3 or Mi11x or redmi K40. You have to double check it yourself. You are the one decide to flash.

If you are very sure you had MIUI 12.5.1.0 before ArrowOS, and you want to return MIUI 12.5.1.0, flashing the same version MIUI should be possible. ArrowOS should have no ARB index change.

Return to stock latest stable version is generally not needed to edit the ARB index.

I don't guarantee anything if you brick it. You can either ask someone else to verify, or try and error.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Suhaas:
thanx for the info.. Since i am not sure and ur not sure either i am thinking to remove those lines altogether. will there be any problem if i flash the ROM without those lines?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
You have to ask @reg66 because he is the one said to remove those lines, I don't know.

In my opinion, since the newest version for your device now is 12.5.1.0, you don't need to remove those line. Make sure you use the Rom of your region/country, if not, make sure you don't lock your bootloader.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Suhaas:
@reg66 pls give me ur opinion. thank you
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
@pl1992aw thanks for all the very helpful extra info regarding all this. @Suhaas, tbh I'm not too in the know about xiaomi devices and arb. I just wrote the guide /info from a bit of research. But, if you check one of the recent 'Oh no - another bricked devices' thread a user with arb:1 on device flashed his original arb:0 rom successfully (12.0.3). I appreciate yours is a later version but in principle it all seems fine.

I wouldn't like to say for sure either way tho, just to cover my ass

God luck
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
See this thread too https://xdaforums.com/t/oh-no-another-poco-f3-brick-thread-d.4286291//unread
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
Two Anti version is safe from ARB according to rule:

Anti 0 and 1.

0 is obvious non-active ARB

1 is because there's no positive natural number smaller than 1, unless Xiaomi implement ARB with decimal digits.

So the case that success with Anti 1 is because it can flash to any Anti version. (And unlocked bootloader)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] GabiML:
In my case current rom has arb 1 and stock has 0. It is fine to flash via mi flash?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
Yes, i did the same thing earlier... went from 12.5.1 stable (base build, arrowOS flashed over that - but custom OS's don't affect arb, i believe), device showed arb:1 and flashed back to 12.0.3.0 stable with anti:0 (as a base for re-install/clean flash of latest arrow)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
Fine if the bootloader is still unlocked after flashing.

Many people brick their device because they did not read the correct tutorial and locked their device with different region Roms.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] aravreddy2231:
I was on 12.0.3 and I flashed crDroid 5/9 and it worked but when I tried to update to crDroid 5/26 build from Recovery ->adb install my device bricked (EDL MODE). What could be the reason for it ?

I bought the phone from Amazon Spain , would it be a global or EEA region ?

Thanks in advance.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
You better ask at the custom Rom thread or at the TWRP thread or open a new thread. ARB only involve MIUI. Your first question is irrelevant to this thread.

As for the region, you can check with the MIUI thread:

https://xdaforums.com/t/miui-updates-tracker-poco-f3-mi-11x-redmi-k40-alioth.4263137/

Having MIUI on 12.0.3 is only India, Global, Indonesia and Russia.

Maybe Global, but I don't know.

Since unlocked bootloader, phones can flash different region Roms, so don't know what it is to be on 12.0.3.0.

Some hints may be on the box that came with it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] GabiML:
My phone cannot pass super img, what to do?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] hexisg:
Super.img takes some time to flash.Have you managed to flash it?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Alin45:
Just wait till flash is done (it last over 650 sec).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] GabiML:
True, i was used to MI 9T which takes 400seconds, sorry guys, my fault, phone is working very well, now i know how to flash everything in it:)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Suhaas:
i got this error while flashing stock rom MIUI 12.5.1. after that the device rebooted and entered setup. everything seems. i am worried some part might have been missed. can you help @reg66 ? pls
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] reg66:
that error is normal, it's just saying 'flash and lock' has not been executed, so flags up an error.

the flash went fine though.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Suhaas:
thanx man for such a quick reply.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Alin45:
That is not a ARB error, so kinda wrong thread. Glad u got the info u wanted thought :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mahfujarr:
in my case arb was 1 and my device wont flash but when i placed both the stock rom file and mi flash tool in the same path which is "C://" Mi flash tool flashed my device back to 12.0.5 from 12.5.1 and ARB is still 1 :/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CrushedMango:
So if I have global ROM 12.5.0, can I flash arrow os with no arb issues?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
Only when you want to flash official MIUI, you have to consider ARB issue.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
Hello to all!👉😎🤟

First of all, sorry for my English😞

I want to reflect with you @reg66 @pl1992aw on this problem.

I saw that the arb verification code, present in the "flash_all.bat" file of some ROMs, (this one)👇

it is different from the code present in the file "flash_all.bat" of the European roms miui 12.0.x, 12.5.x of the poco F3, (this one)👇

::check anti_version
if exist %~dp0images\anti_version.txt (for /f "delims==" %%a in (%~dp0images\anti_version.txt) do (set CURRENT_ANTI_VER=%%a))
if [%CURRENT_ANTI_VER%] EQU [] set CURRENT_ANTI_VER=0
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
set anticheck="antirollback check pass"
if %version% GTR %CURRENT_ANTI_VER% set anticheck="Current device antirollback version is greater than this pakcage"
echo %anticheck% | findstr /r /c:"pass" || @echo "Antirollback check error" && exit /B 1

where the "anti_version.txt" file is called.

This file is contained in the "images" folder inside the rom package. (attachment)👇

This is just my guess!

I think the real "current_anti_ver" of the rom is written inside this file, in fact the only thing written inside this file is number 1.

I know we sail into uncharted territory, so I'm not sure if that's the case, I could be wrong ...

Of one thing I'm sure, after checking "anti" in my F3, it is "anti=1" and after downloading and unzipping the "flash_all.bat" and "anti_version.txt" files of all 12.0.x and 12.5.x miui roms EEA for a poco F3, I saw that the code contained in the .bat files and the number in the .txt files does not change.

Perhaps it is for this reason that some have managed to downgrade.

What do you think?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] opg2000:
....same to me. With my Redmi Note 10 pro I have ARB = 3. The "anti_version.txt" from the downloaded correspondending ROM-Image shows also "3". Now I think I can flash this Rom-Image without bricking my device.?!?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
I suggest you still use miflash to flash because it still checks and blocks the installation if the arb of the rom is less than that contained in the phone. However, in principle, if the arb of the rom is equal to or greater than that contained in the phone, the flash is successful.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] opg2000:
...I'll try it so and will report here if it works...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
Before any of this... Make sure that the path towards the folder containing firmware has no spacing at all.

For example , if one of the folders in the path is named Mi flash firmware , or such rename it to Mi_flash_firmwarr or whatever , just make sure to remove the spacing....

ARB check will fail if there's spacing , which leads me to believe that even if you remove ARB check the rest of the flashing process might fail for the same exact reason that ARB failed...

First make sure remove this as a variable , if ARB check still fails only then start thinking about possibly removing the check.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] rafly1952:
My POCO F3 has index 1 and my downloaded ROM is index 0, but when I press the flash button I still get an Anti Rollback error notification, can anyone provide a solution?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] zsolt64555:
maybe you have A12 rom, or still has A12 recovery image on phone.

put the root directory on C: drive to the Miflash and the stock firmware together, run miflash with administrator, set firmware from c: drive, and flash :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Asgharjoon:
I still get the ABR error though I have removed the lines for checking the ABR from flash_all.Bat but MI Flash still gives the ABR error. What am I doing wrong? :(

I have successfully flashed below on a soft/brick Redmi Note 10 Pro(global) but it resulted on "NV data is corrupted" showing on MUI recovery menu so now I tried to flash a newer version (bot rolling back) but it gives me the Antirollback check error.

Currently on: Xiaomi Redmi note 10 pro Europe (EEA) latest Fastboot ROM MIUI V12.5.6.0.RKFEUXM, Stable android 11.0 firmware of sweet.

Trying to flash: Xiaomi Redmi note 10 pro Global latest Fastboot ROM MIUI V12.5.9.0.RKFMIXM, Stable android 11.0 firmware of sweet.

Appreciate any hints. Thanks
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] BoBoGrEy:
Hi guys,

I have xiaomi.eu 13.0.3.0 installed (Android 12).

I wanted to flash 12.5.6 Official Global through fastboot, but I'm getting ARB error.

Is this normal?

How can I revert back to stock global?

Thanks in advance.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] :
Use this tutorial with mi tools
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] roshansai:
well, try to look you don't have space on your folder while flashing with mi flash & if you are still getting issue with mi flash. you can try out xiaomiprotool which is for professional & you can try out using fastboot flash where you can downgrade upgrade any kind of firmware. also you can brick & black out your device by flashing wrong firmware.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] SubV:
Hello everyone. Both my current ROM and the ROM I want to flash are anti 1.

Is it safe to flash the device via MiFlash in fastboot mode?

Thank you in advance.