yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] heartbreakkid58:
Hi @AnotherM1m, I was checking the sensors in CIT/Engineering Mode, and got this error in Sensor test. Please have a look at the screenshot, maybe from this we can figure out the issue.
[Nothing Phone 1] AnotherM1m:
Are you able to dump/copy your persist partition into a file persist.img and send it to me via DM?
[Nothing Phone 1] ayed78:
it not related...before using on first edl tool no issue,no fingerprint issue no imei issue after use couple time,it starting happen
[Nothing Phone 1] AnotherM1m:
Have you noticed if you had critical partitions unlocked when that was happening?
[Nothing Phone 1] heartbreakkid58:
Just to bring it in your knowledge, I'm using somebody's else persist.img , as I lost the serial number too.. If my dump partition persist still helps, then I will share the file. Thank you.
[Nothing Phone 1] heartbreakkid58:
Hi @AnotherM1m , a gentle reminder for the fingerprint fix, if you have anything to share, please :)
[Nothing Phone 1] AnotherM1m:
unfortunately still nothing... i was thinking about created 102 qfil roms since that fw helped automatically restoring the lost serial number of a user maybe it also works for fingerprint

but before making that qfil rom i would need either a tester or a program that im developing to be finished
[Nothing Phone 1] heartbreakkid58:
@AnotherM1m thank you, I appreciate your help. If you need anything to test, please let me know. I'm not using my phone, it's been in the drawer for the last few months.
[Nothing Phone 1] AnotherM1m:
Anyone with latest nos (255) wants to try with:

Open the dialer and input *#*#9#*#*

Select after sale calibration test, fingerprint calibration

Try calibrating with this method. Try also disabling performance from the fp calibration screen.

Let me know!
[Nothing Phone 1] tekmor:
Thank you AnotherM1m for trying to find a solution.

I just tried and unfortunately it still doesn't work.

Here is the test context:

- NOS stock 2.5.5 (Build number: Spacewar-U2.5-240419-1617-EEA)

- Serial number restored via persist.img file (thanks to you, AnotherM1m)

- Calibration with RELIFE RL-071B (Optical Fingerprint Calibrator)

- Tested in a dark room

And here's the result (common to all attempts, performance enabled or not):

View attachment 6099643

(I've roughly cropped the image so that the post isn't too long. The original image is available as an attachment.)

It seems to me that an error message is displayed before the unknown error, but I'm not sure. I'd have to check by filming the phone screen.
[Nothing Phone 1] AnotherM1m:
dang it.

if you find anything let us know! do you have by any chance a backup of modemst1/modemst2 partitions? were your imei's good after the brick? i searched for this inside our conversation but couldnt find anything.
[Nothing Phone 1] tekmor:
I no longer have a backup and I'm not sure if I had a backup of the modemst1/modemst2 partitions.

No problems with my imei. I don't think they were affected by the brick in my case.

I have two active SIM cards and both are working fine.
[Nothing Phone 1] AnotherM1m:
Thank you, i'll report back if i find anything
[Nothing Phone 1] pyry666:
I learned this hard way back in op8p. Always back up persist and imei. Wont take long. And as np1 is from oneplusses dev. Changing even screeen causes this issue. Just my two cents
[Nothing Phone 1] AnotherM1m:
Yes, users need to backup their persist, modemst1, modemst2, fsc, fsg partitions.

The first contains serial number, fingerprint infos, color.

The latter ones infos about imeis and possibly certificates (still testing)
[Nothing Phone 1] pyry666:
If screen is replaced that dont work. Like other persons persis.img. kind of over kill imo but still. Maybe thief breaks your screen and cuts finger off just to be sure. Sorry for my dark humor
[Nothing Phone 1] AnotherM1m:
Hello, people with issues with their fingerprint, please write a private message to me! i have something to test
[Nothing Phone 1] ayed78:
you found solution?
[Nothing Phone 1] AnotherM1m:
After a test was done unfortunately the fingerprint sensor was still not working.

Back to the start...
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] pleban23:
Hello Guys,

I upgraded my rooted SM-G988B to Android 13, but unfortunatelly I lost my data and e-sim configuration.

Before upgrade I made a full TWRP backup.

View attachment 5771119

How I can restore my TWRP full backup, when my bootloader version also has been upgraded to the highest version ? Any ideas ?

I upgraded Adroid from G988BXXSEFVE6_G988BXXSEFVE6_MQB52013822 (12) to G988BXXSFGVK1_G988BXXSFGVK1_MQB58698382 (13).

Best Regards,

pleban23
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] pleban23:
After restoring "DATA" i have a bootloop and 3 Red Lines in TWRP about wiping device to factory settings.
[OnePlus Nord Questions & Answers] SiiPArch:
Hi!

I'm using a custom rom (Cherish OS) and it's working pretty fine.

However, i want to turn back to the stock Oxygen OS, so I've tried to use the MSM Tool, but i have a problem.

Whenever i do "adb reboot edl", the phone actually boots in EDL, my PC in device Manager recognize the port (I've also installed the Driver), but when i press "Enum" nothing happen, the EDL MODE is not recognized only by the software. (No Device ID, and N/A on connection)

I've tried so many times but nothing seems to change, does anyone know how I should proceed?
[OnePlus Nord Questions & Answers] gorro8:
try to reinstall the correct driver for the firmware from the thread Unbrick tool for Nord
[Redmi Note 10S] Mactha88:
This device have a custom kernel?

if have a custom kernel , is anyone send file?
[Redmi Note 10S] tutibreaker:
read the threads before make a useless post like this
[Redmi Note 10S] Mactha88:
I find only genom kernel.

I don't find any kernel.
[Redmi Note 10S] tutibreaker:
cuz there is no more kernels
[Xiaomi Mi 11 Ultra] jstoner:
My phone has arrived and in few days, I ll attempt to switch to the EU ROM

(I ve bought a CN unit, which arrived nice and sealed in its box)

So, I ll attempt to follow this guide to the letter: https://xiaomi.eu/community/threads/howto-install-fastboot-image.64508/

Heading over to sourceforge, I can see that the latest stable releases for my phone are one from AUG and one from MAY i.e.

xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip

2022-08-05

xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot.zip

2022-05-13

But according to that guide, it says "download latest fastboot" image. And thats the older one released in MAY (V13.0.12.0...)

So I presume I cannot use the latest V13.0.13.0 (released in AUG) for this method!?

Is there a fastboot (V13.0.13.0) in the making, so perhaps I could wait a little longer for that?

Or do I just use the one released 6 months ago?
[Xiaomi Mi 11 Ultra] NOSS8:
Without functional TWRP in A12, Xiaomi Eu rom provided roms in Fastboot .zip.

Now that there is a TWRP, the roms are in Zip.

Either you use a Fastboot .zip and update via Ota or you install the Twrp and flash the rom.

For updates you must go through the Ota and not flash directly with the TWRP.
[Xiaomi Mi 11 Ultra] jstoner:
Regarding TWRP, do I get the latest version (skkk) or the one from TeamWin? (because both are intended for 11 Ultra I think - codenamed "star")

My guess is skkk, which also says "A12"

Then I can use "xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip", which seems to be latest

I plan to use this guide - I hope it is accurate (it says "unofficial"!)
[Xiaomi Mi 11 Ultra] NOSS8:
Official here:

https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/
[Xiaomi Mi 11 Ultra] mclephane:
Just done the same thing yesterday. Use 3.70_12-v6.5_A12-star-skk.img. I had problems with fastboot V13.0.12.0.SKACNXM_v13-12-fastboot had failed status read failed (too many links) errors. But think that's just my adb setup in Windows 11. So just used fastboot to boot twrp. Then in twrp flashed twrp to ramdisk reboot to recovery and flashed xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip formatted data reboot to systsem. Working V13.0.13.0. I ended up just copying V13.0.13.0.zip and twrp to a flash drive mounted OTG in twrp and installed. Only because of issues with laptop.
[Xiaomi Mi 11 Ultra] jstoner:
no, by "unofficial" I meant the Guide ;-)

(if it would work if I followed that guide to the letter - as I m not too tech savvyy)
[Xiaomi Mi 11 Ultra] NOSS8:
The installation remains the same

https://xdaforums.com/t/twrp-mi-11-pro-ultra-mars-star.4280313/

If you install a xiaomi Eu rom (twrp included) check the version of Twrp and update it if necessary.
[Xiaomi Mi 11 Ultra] jstoner:
Now, I ve backed up everything and was about to flash the phone to latest stable MIUI

But just realised v14 was released in the meantime, in December

But for the 11 Ultra, there is only weekly ROM available (no stable)

Looks like I ll have to extend my wait

As for v13, I can still see that the latest is xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12.zip

I wonder - will there be another v13 release for this phone?

Should I go with this latest v13 or wait for the first stable v14 (star) release?

Sometimes, having been presented with choices, makes it so hard to decide! But for sure, I need a stable build for this phone..
[Xiaomi Mi 11 Ultra] NOSS8:
Whether Weekly or stable, both are based on the Chinese rom.

For the stable you will have to wait while Xiaomi releases the rom.

I use the Weekly when available and they are really "stable".

Note that if you install a Weekly and move to the stable you will have to format the data.

Also going from A12 to A13, formatting the data is not mandatory but I recommend it.
[Xiaomi Mi 11 Ultra] jstoner:
Ah, OK - so there's no 'stable' MIUI v14 for the 11 Ultra yet? I get it..

As for the format consideration, I m a huge fan of clean installs too. I guess I ll go with v13 for the time being, as I don't have much of a time luxury to wait for the official stable v14..
[Xiaomi Mi 11 Ultra] jstoner:
Seems like it v14 (stable) has just been released for the 11 Ultra!

xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip

But is this ROM meant to be installed via fastboot or twrp?

In my mind, it is still not clear what the difference is between fastboot and twrp

I can only presume that twrp is essentially a GUI (vs just typing commands in fastboot!?) But I m not really sure anymore

I ve been an Galaxy S series user over the last years. Back then, I used to flash a new ROM via "Odin". Was that using the twrp method or fastboot? I m sorry, but I m totally confused now

Since twrp is an extra software that needs to be installed on the phone - isn't that come with any drawbacks? What is the more 'clean' approach to installing an MIUI on the 11 Ultra?
[Xiaomi Mi 11 Ultra] NOSS8:
Yep, TWRP avoids typing command lines.https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/star/

Two version of roms:

Rom.Fastboot.zip to install with a pc with the Bat file included in the rom folder.

Provided this way if no working TWRP.

Rom.Zip to install via OTA.

If this is a first installation you will have to install the TWRP first then TWRP / wipe format data type Yes (this will erase all your data) and reboot to the TWRp and flash the rom, then the updates will be done via OTA/TWRP.
[Xiaomi Mi 11 Ultra] jstoner:
So basically you imply that recovery (TWRP) is the preferred path

If I understood correctly, the biggest (?) advantage of chosing a recovery ROM (instead of a fastboot one) is the benefit of having OTA afterwards, right? (and maybe simplicity of having the GUI - that is TWRP)

Now, to put this the other way - what's the disadvantage of chosing the recovery ROM over a fastboot one? Is there any? (other than the need to have to install an 'extra layer' - that is TWRP)

So that ROM that was just released (xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip) is a recovery ROM. right? If so, the latest twrp (v3.7.0 from https://eu.dl.twrp.me/star/) will work for this brand new MIUI 14?
[Xiaomi Mi 11 Ultra] NOSS8:
For Xiaomi EU roms regardless of whether they are in ZIP or Fastboot.zip only the way of installing them is different.

For Stock roms, those in Recovery are used for updating or troubleshooting, they only contain the essentials, unlike those in Fastboot containing all the Imgs of the phone.

For the TWRP, you must take into account the version of Android A12 or A13, not Miui13 or 14.

The link https://eu.dl.twrp.me/star/ is obsolete, the one I posted is the official one developed by SKKK.

xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13.zip

use

twrp-3.7.0_12-v6.9_A13-star-skkk.img

The first boot of the rom takes 5/8 minutes.
[Xiaomi Mi 11 Ultra] jstoner:
I ll prob do it in the weekend

From what I read, I also have to unlock the bootloader and from a security PoV, I m not really happy about that, but no way around it. Just can't live with the stock CN ROM

Not sure if unlocking the bootloader takes time or if it is instateneous (via the MI website)

As for my concerns over the method (twrp vs fastboot), it would seem that the fastboot is probably more 'clean'

No disrespect towards the developers who made the twrp possible - thus making it so much easier for people to fiddle with ROMS on their mobile and at no cost, but regardless of that, it is still an extra piece of software that resides on the phone. Just the way I understand it. Again, not looking down at twrp

What do you mean by "fastboot containing all the imgs..."?

Isn't it one single image per phone model?

Or did you mean to say 'features' or 'apps'?

Personally, I d be more interested in less/apps/fancy features (except for security of course)
[Xiaomi Mi 11 Ultra] NOSS8:
As said above, this only concerns stock roms(recovery/fastboot), not xiaomi Eu roms, whether in Zip or Fastboot, it's the same, only the installation method differs.

Unlocking the bootloader takes at least 168 hours before finalization (time to study a bit);).

The latest Stable or Weekly versions are in Zip, so with TWRP.

Unlock

https://new.c.mi.com/global/post/101245

https://en.miui.com/unlock/index.html
[Xiaomi Mi 11 Ultra] jstoner:
Unfortunately, the more I read, the more I m getting kind of disappointed with things 'Xiaomi'

In order to get the unlock process started (1 week..really??), I need to download the MI drivers. OK

So I m trying to search "official" MI drivers and they are nowhere to be found!

All I get is this https://xiaomidriver.com/ which claims to host the official drivers (!)

How can this be for the image of a reputable brand?

How can Xiaomi not hosting themselves all these useful tools like all other major vendors do (in their own domain!)?

How me, as an end user, is supposed to verify authenticity of a driver found on a xyz domain claiming to be the official one?

What's more, at the bottom of this page it says "xiaomidriver.com is not endorsed or affiliated to Xiaomi..."

I mean seriously???

I purchased this phone for its hardware capabilities but is there nothing more than that?

I mean, I get Xiaomi not wanting to encourage people mess with the ROMS. After all, some will end up bricking their phone and then they ll chase up Xiaomi for this

But Xiaomi not hosting something as so very basic as a USB driver??? This can't be right

Even that official page kindly provided by NOSS8 earlier, states "ensure your PC has necessary Mi USB drivers and platform tools" Well...where am I supposed to get these from? The first random site I google up?

........

After bashing my head around this, I eventually found an official link (from miui.com), for obtaining the flash tool from which I can do a workaround to extract the drivers....c'mon!!
[Xiaomi Mi 11 Ultra] NOSS8:
It is very simple.

The installation of the drivers is done with Mi Unlock (gear at the top right) then check:

View attachment 5812945

Also download platform tools which would be useful for installing TWRP or performing certain Fastboot operations.
[Xiaomi Mi 11 Ultra] Reezwan:
@NOSS8 I tried installing xiaomi.eu Rom MIUI14 on the Mi 11 pro. It booted and everything but whatsapp and camera was not working. Whatsapp not syncing, camera asks for SD card?

So I decided to downgrade to MIUI 13 from Aug 2022 the version in this post above. This is what I did:

1. Fastboot TWRP latest skkk for A12.

2. Flash from TWRP last stable MIUI 13 Rom

3. Phone restarts fine but goes in to loop after connecting to wifi. Please note I have done format data before and after flash

4. I rebooted the ROM to recovery it asks for pin, then says wrong password, failed mount.

Please advise. What should I do? I am happy to toll back to MIUI13 as I am not sure what is going on with MIUI 14. How do solve this problem? Many thanks
[Xiaomi Mi 11 Ultra] Bobfish:
It's better to use fastboot when doing downgrade/rollback android or Miui version .
[Xiaomi Mi 11 Ultra] NOSS8:
Miflash

https://xdaforums.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
[Xiaomi Mi 11 Ultra] NOSS8:
The bootloader is already unlocked?
[Xiaomi Mi 11 Ultra] Reezwan:
Thanks!
[Xiaomi Mi 11 Ultra] NOSS8:
You tell me thank you but why I have not yet answered your problem.

If I ask you this question, it's because on Tuesday at 11:30 PM you try to unlock it.

Obviously what you have done requires that the bootloader be unlocked but I would have liked a confirmation to be able to tell you the solutions.

And one of the mistakes made, you were on a system in A13 and you flashed a TWRP A12.
[Xiaomi Mi 11 Ultra] Reezwan:
@NOSS8 yes sorry I didn't see this message. Boot loader is unlocked. But getting this error in TWRP
[Xiaomi Mi 11 Ultra] NOSS8:
Cancel/then wipe format data type yes reboot TWRP

If errors reds lines do it again always rebooting on the twrp at each try.

And if the system is A13 use the TWRP a13 to flash an A12 and vice versa.

I hope you have kept the roms because currently the sourceforge servers are having problems.
[Xiaomi Mi 11 Ultra] jstoner:
Just an update - I have installed MIUI EU v14 on the phone

But I made a mistake initially with TWRP

On my first attempt, I (incorrectly) used "fastboot flash recovery twrp.img" - instead of just "fastboot boot twrp.img"

The flash (as expected) failed and when I subsequently run the 2nd command, it rebooted and then went blank (no TWRP startup). At first, I was worried that I bricked the phone

Then, pressed the buttons again and luckily it started up (went into fastboot mode again)

And that 2nd time, I used "fastboot boot", as I should have from the begining and the TWRP started up automatically

I used latest version (v7.0) of TWRP which has just been released

In TWRP, I changed language to English and then installed the stable recovery ROM MIUI14

After that, I chose 'Format Data'

No other options were ticked - everything else left to default

I didn't even check the option to flash TWRP on the phone, as I didn't want to have it permanently installed

After installation was complete, I got the following warnings/infos:

Although when the phone restarted and booted into the newly installed OS, everything looked OK - should I worry about any of the above warning I got right after installation? From this output, can you tell it was installed properly?

The only thing I cannot figure out is why the File Manager shows up no files (even though I enabled 'Show Hidden/system files..)
[Xiaomi Mi 11 Ultra] NOSS8:
It seems to me that before installing the V14 A13 rom the system was in A12 and you installed the TWRP A13.

Try deleting app data and checking permissions and/or wipe the dalvik cache.
[Xiaomi Mi 11 Ultra] jstoner:
Yes, it was on whatever previous version of Android that came originally with the CN phone

I though this was the right combo, as you suggested previously:

twrp-3.7.0_12-v7.0_A13-star-skkk + xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13

Was I supposed to use the A12 version of TWRP instead?

I remember this 'dalvik cache' option, right after ROM installation

But no clue what app data you mean or how to check permissions..

Something didn't go well, did it?
[Xiaomi Mi 11 Ultra] NOSS8:
If your system is A12 you must use a TWRP A12 to install an A13 rom then install the Twrp A13 for the following updates.

Are you talking about the file explorer application or with the TWRP?

BTW:Could you edit the title of your thread and add "Xiaomi EU rom" thank you.
[Xiaomi Mi 11 Ultra] jstoner:
The 'dalvik cache' option is probably only within TWRP, as for the 'app data' and 'permissions' you are probably referring to within the OS?

Sure!

But I don't really like to have this insecurity (even if the OS seems to be working)

So I d rather do it, fresh, from scratch

Fact is I ve used TWRP for A13, whilst the phone was on A12

As I mentioned, I also opted not to flash the TWRP on the phone (at least that was a good thing, right?)

So now, the only thing that should reside on my phone is that potentially problematic MIUI v14

So how do I go from here, in order to have a fresh start?

Do I fastboot TWRP for A12 or A13 this time (and install the ROM again)?
[Xiaomi Mi 11 Ultra] NOSS8:
Long press the file explorer icon, information and look at permissions and bottom right erase data/erased all data.

Twrp/wipe/select dalvik,art cache.

If the rom works why reinstall it?
[Xiaomi Mi 11 Ultra] jstoner:
Permissions:

access files and docs

access photos and videos

access audio files

All 3 have a green cheeckmark

As for the 2nd part, I can only find a 'Storage' option, at the top of the File Explorer options

That has a 'Clear' (Data/Cache) << that the one you mean? should I clear both?

Because I cannot tell at this point what else might have been affected by me using the incorrect TWRP

I am constantly reading stuff from people complaining about not being able to use a particular app/feature after the flash

I got these post-install warnings (my previous screenshot)

Wouldn't it be better to invest 10 more minutes now, while the phone is totally empty, rather than some problem occuring at a later stage, when I ll have installed apps, have photos and need to backup and start again..? Those "failed to mount.." errors that I got, don't look innocent to me..

So given the current circumstances, which TWRP I should be booting from in order to perform a fresh install?

(my guess would be twrp-3.7.0_12-v7.0_A13-star-skkk)
[Xiaomi Mi 11 Ultra] NOSS8:
Erase all data.

A13 means Android 13, A12 means Android 12.

These errors have no impact on the operation of the rom and are due to the TWRP cache after your errors at the start.

If you had an OTG key, it will be easier to perform a clean flash.
[Xiaomi Mi 11 Ultra] Arcide:
No this is not an issues, devs said these errors are "normal"
[Xiaomi Mi 11 Ultra] jstoner:
OK

So I ve just did a fastboot TWRP

Then, I went to WIPE >> ADVANCED WIPE

And now I get the following options:

Dalvik / ART cache

Metadata

Data

Internal Storage

Cache

USB-OTG

Which of those I need to check/enable to be wiped?
[Xiaomi Mi 11 Ultra] NOSS8:
As written above, just

Dalvik / ART cache
[Xiaomi Mi 11 Ultra] jstoner:
So far, the OS performs as expected, with no issues that I can tell

But for my future reference i.e. when a new EU stable ROM is released, should I be using fastboot TWRP for A13 this time, correct?

Also, if a new fastboot ROM is released, can I just fresh-install it over my existing recovery ROM? Will it clear everything or do I still need TWRP to wipe something first? (I am not saying to use TWRP to install a fastboot ROM! just to remove if anything needs removing from my existing installation..)
[Xiaomi Mi 11 Ultra] NOSS8:
Now that the Twrp is installed, depending on the format of the update, you will use Ota then the Twrp or the pc for a fastboot.

It will just be an update, no need to wipe or anything.

If the next roms are hybrids, you can use the method that suits you.

https://xiaomi.eu/community/threads/hybrid-roms-the-end-of-recovery-fastboot-roms.67987/#post-683193
[Xiaomi Mi 11 Ultra] jstoner:
But I don't think it is installed. Or at least, it shouldn't be

I only fastbooted TWRP - didn't check any option to 'inject' it or flash it to the device

How can I check if it is installed? Is it Vol UP+pwr? (because nothing happens when I try that)