My realme x2 device wifi, fingerprint, and sensors are not working. I want persist partition backup from anyone's realme x2
Same here
can anyone share how to fix fingerprint and face unlock. im getting failed to mount persist in twrp
btw here is the persist file
Same here, i'm on 1993EX F26
Here is the file,now please someone tell me how to do it
Related
Good evening people.
I'm facing issues with the proximity sensor, i've recalibrated it and this persists, anybody know how to flash this partition? (persist.img), i used fastboot and no luck, it can't flash control partitions, my phone has the bootloader unlocked.
This problem appeared after i upgraded to miui 9.5.17.0 from an ota package and i know that i can fix this flashing the mentioned partition, i've done this on an old redmi note 3 and worked like a charm, EDL mode fails with mi flash.
Thanks for your time.
avercros said:
Good evening people.
I'm facing issues with the proximity sensor, i've recalibrated it and this persists, anybody know how to flash this partition? (persist.img), i used fastboot and no luck, it can't flash control partitions, my phone has the bootloader unlocked.
This problem appeared after i upgraded to miui 9.5.17.0 from an ota package and i know that i can fix this flashing the mentioned partition, i've done this on an old redmi note 3 and worked like a charm, EDL mode fails with mi flash.
Thanks for your time.
Click to expand...
Click to collapse
What error do you have on miflash?
Have you tried thru twrp's terminal?
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p53
Persist problem
devcon69 said:
What error do you have on miflash?
Have you tried thru twrp's terminal?
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p53
Click to expand...
Click to collapse
Hi, Im having the same issue with my whyred.
I tried this, but now my phone wont boot. If i flash any miui version it returns back to recovery (even after using the miflash tool by fastboot). After flashing any other rom, the phone is stuck in the boot animation itself. I tried havoc 2.2 and waited for the boot animation to complete for an hour. Please help.
I found out my error.
Please execute these commands in order.
-> simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
-> dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
dont try to directly copy the persist.img file
@fawazahmed0 I need your help to decrypt this A.14 ozip file here is the link Realme 3 A.14 ozip ill just to upgrade from A.13 to A.14 thanks
if decyrpted is it possible to update realme 3 with spflashtool ? or how do you upgrade? thx
Ill get system, vendor and boot.img and ill create flashable via TWRP
Hello, I'm looking for persist.img of redmi note 8 because my phone sensor isn't working by persist partition corruption. Kindly help me with persist.img file.
Thank you in advance.
hjh6743 said:
Hello, I'm looking for persist.img of redmi note 8 because my phone sensor isn't working by persist partition corruption. Kindly help me with persist.img file.
Thank you in advance.
Click to expand...
Click to collapse
download fastboot rom for your device from here http://c.mi.com/oc/miuidownload/detail?guide=2
extract it twice and inside the images folder you can find persist.img
the_weird_aquarian said:
download fastboot rom for your device from here http://c.mi.com/oc/miuidownload/detail?guide=2
extract it twice and inside the images folder you can find persist.img
Click to expand...
Click to collapse
Its showing 404 forbidden
I wiped my persist partition and don't know what to do plz anyone can help me with this
Tried persist replair tool for redmi note 8 but all are showing corrupt
Plz tell what to do
hjh6743 said:
I'm looking for persist.img of redmi note 8
Click to expand...
Click to collapse
AsH9914 said:
I wiped my persist partition and don't know what to do plz anyone can help me with this
Click to expand...
Click to collapse
if you restore persist that way you will lose Widevine l1 (this is spesefic to every device)
it's better to restore your persistbak rename it to persist.img and flash it and hope it's not gone (Widevine)
here is the guide
i have downloaded fastboot rom but persist img is not showing here !
jashan456 said:
i have downloaded fastboot rom but persist img is not showing here !
Click to expand...
Click to collapse
restore your persistbak rename it to persist.img and flash it
loopypalm said:
restore your persistbak rename it to persist.img and flash it
Click to expand...
Click to collapse
but persistbak img is not also showing
jashan456 said:
but persistbak img is not also showing
Click to expand...
Click to collapse
Follow the guide ffs !
loopypalm said:
Follow the guide ffs !
Click to expand...
Click to collapse
plese write all steps it will very helpful for me.
I have been using this Mi 11x (Indian variant of Poco F3/ Redmi K40). It has TWRP by Nebrassy as latest version of Magisk (v23) installed and working. Magisk is working in systemless mode. System structure shows partitions Slot A and Slot B in TWRP. Whenever I attempt to delete any system file using root privileged file manager it return 'failed to delete : error code 1'.
I did try deleting these files using TWRP file manager. There also it says 'failed, Code 1'.
What am I doing wrong. And how to correct it? Please help...
Running Os: Xiaomi.eu with version 12.5.4.0 with MIUI 12.5
Device : Mi 11x (Aliothin)
System files cannot be deleted after android 10
Thread '[SCRIPT][Android 10+] Universal Mount System read write R/W' https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Here I just got the solution... I just installed the flashable.zip file through TWRP in my poco f3 with xiaomi.eu and it was full success in first attempt.
Suryashis said:
Thread '[SCRIPT][Android 10+] Universal Mount System read write R/W' https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Here I just got the solution... I just installed the flashable.zip file through TWRP in my poco f3 with xiaomi.eu and it was full success in first attempt.
Click to expand...
Click to collapse
seems very hard for me... can explain better how ? thanks
Angyone1 said:
seems very hard for me... can explain better how ? thanks
Click to expand...
Click to collapse
I worked on my mi 11x with unlocked, magisk rooted Xiaomi.eu 12.5.4.0 rom (android 11). I just downloaded the flashable zip file from the site attached) and installed it in TWRP recovery. Pretty straight forward... But u need to have atleast 20gb internal memory free, where a backup of your super.img will be stored (u can delete this later). My advice is to go through the thread once since I have read certain feedbacks where the device went into bootloop.
Suryashis said:
I worked on my mi 11x with unlocked, magisk rooted Xiaomi.eu 12.5.4.0 rom (android 11). I just downloaded the flashable zip file from the site attached) and installed it in TWRP recovery. Pretty straight forward... But u need to have atleast 20gb internal memory free, where a backup of your super.img will be stored (u can delete this later). My advice is to go through the thread once since I have read certain feedbacks where the device went into bootloop.
Click to expand...
Click to collapse
Be sure to mount System, Vendor, Product atleast before starting the installation process in TWRP
Hello all,
I've been having the hardest week, all my personal business at the halt (cant use bank apps, email etc.). One morning my phone suddenly entered a bootloop, then since then I was in a bit of hurry, I tried a stock rom recovery update from twrp, that made the phone enter a hardbrick status.
Then since we don't have a firehose for the 'lisa' I had to pay a guy to take it out. That solved the hardbrick but the softbrick remained. Since I am not an android expert just have mediocre knowledge I asked a kind persons help. They've been trying to help me for days but we still couldn't solve the issue and I thought other opinions would be nothing but helpful.
The details you should know:
1. Only hardware operation made on the device is changing a resistor. (Can explain it better, if requested). But the phone was working just fine after it for months.
2. We have identified the partitions are all messed up and and flashing stock rom doesn't solve it, tried Eu, global and Chinese roms.
3. The system was missing on the twrp advance wipe and there were:
dalvik
metadata
data
ınt storage
sdcard1
usb otg
4. I didn't understand all the things he/she tried but tried to fix the partitions mainly using these sources ( it could give you a better idea ):
How to create System partition in Android? Which is accidentally deleted when tried to increase size.
Tools needed can be downloaded from forum.xda-developers Section 3. parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip - [Click for QR Code] ...
illitrateman.blogspot.com
How to fix "Partition does not start on physical sector boundary" warning?
I have one HDD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap). fdisk is giving me the following warning: Partition 1 does not start on physical sector boundary
askubuntu.com
5. We tried 3 different custom roms but no avail.
6. At the moment the phone can enter in fastboot but giving trouble flashing twrp or orangefox.
I'm confident my expert angel has a solution for that but I think in general any thoughts, ideas, suggestions would be highly appreciated.
Thank you in advance...
Try to use Miflash with the oldest Fastboot rom.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
NOSS8 said:
Try to use Miflash with the oldest Fastboot rom.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your input, yes we have thought of that and downloaded the oldest global rom but haven't tried to flash it yet because of another hardbrick possibility. We are trying to fix it with terminal within twrp (we can flash twrp now) attempting to fix the partitions.
Any other ideas?
stercorarius said:
Thank you for your input, yes we have thought of that and downloaded the oldest global rom but haven't tried to flash it yet because of another hardbrick possibility. We are trying to fix it with terminal within twrp (we can flash twrp now) attempting to fix the partitions.
Any other ideas?
Click to expand...
Click to collapse
Not sure that the Twrp for this device is 100% functional, especially since this device has A/B partitions and A13 has write restrictions.
You can try a Xiaomi Eu rom and flash the rom in fastboot mode with the first install.bat script included in the extracted folder.(xiaomi.eu_multi_MI11LE_XM11Lite5GNE_V14.0.6.0.TKOCNXM_v14-1)
Xiaomi.eu Multilang MIUI ROMs - Browse /xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv14 at SourceForge.net
OFFICIAL mirror of MIUI Multilang ROM by https://xiaomi.eu/
sourceforge.net
Format data, erase your data and create a new partition if necessary (Twrp format data type yes, Miflash and Xiaomi Eu rom do it too).
The recovery roms do not contain all the system imgs unlike the Fastboot rom and Xiaomi Eu rom.
Could also be a HW problem.
stercorarius said:
Hello all,
I've been having the hardest week, all my personal business at the halt (cant use bank apps, email etc.). One morning my phone suddenly entered a bootloop, then since then I was in a bit of hurry, I tried a stock rom recovery update from twrp, that made the phone enter a hardbrick status.
Then since we don't have a firehose for the 'lisa' I had to pay a guy to take it out. That solved the hardbrick but the softbrick remained. Since I am not an android expert just have mediocre knowledge I asked a kind persons help. They've been trying to help me for days but we still couldn't solve the issue and I thought other opinions would be nothing but helpful.
The details you should know:
1. Only hardware operation made on the device is changing a resistor. (Can explain it better, if requested). But the phone was working just fine after it for months.
2. We have identified the partitions are all messed up and and flashing stock rom doesn't solve it, tried Eu, global and Chinese roms.
3. The system was missing on the twrp advance wipe and there were:
dalvik
metadata
data
ınt storage
sdcard1
usb otg
4. I didn't understand all the things he/she tried but tried to fix the partitions mainly using these sources ( it could give you a better idea ):
How to create System partition in Android? Which is accidentally deleted when tried to increase size.
Tools needed can be downloaded from forum.xda-developers Section 3. parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip - [Click for QR Code] ...
illitrateman.blogspot.com
How to fix "Partition does not start on physical sector boundary" warning?
I have one HDD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap). fdisk is giving me the following warning: Partition 1 does not start on physical sector boundary
askubuntu.com
5. We tried 3 different custom roms but no avail.
6. At the moment the phone can enter in fastboot but giving trouble flashing twrp or orangefox.
I'm confident my expert angel has a solution for that but I think in general any thoughts, ideas, suggestions would be highly appreciated.
Thank you in advance...
Click to expand...
Click to collapse
Which twrp version were you using and which version of MIUI did you try to flash when you hard bricked?
There's no system partition nowadays, it is now included in the "super" partition (system, system_ext, product and vendor) and developer removed the option to wipe it because you are not intended to wipe it.
My recomendation is to flash any fastboot rom, I've flashed 7 roms with fastboot and it always worked flawlessly.
Hi, I'm the person that has been helping.
Of course we flashed miui (in fastboot). Global and chinese. We haven't tried eu yet.
I think I've found the source of the problem, but I'm not sure if solving it will fix the bootloop. A partition that's called switch is corruped. It reports as 16EiB (yes that is correct, 16 exabytes, 18446744073709551607 sectors, reported by gptfdisk, full report). It could just be a program issue. The switch partition in located in /dev/block/sda1 and /dev/block/dm-5. I also found that a dummy.img file is being flashed to that partition.
I also got this error from trying to open the switch partition from a newer version of gptfdisk.
I'm not sure if that's the reason for the bootloop, but I think it can be.
These reports have been from /dev/block/sda1. From /dev/block/dm-5 it's like this.
If someone wants to look at the tools I found, they're here.
If someone has any suggestions or possible answers for us, please reply.
What is the error generated by Mi Flash?
Miflash log folder
NOSS8 said:
What is the error generated by Mi Flash?
Miflash log folder
Click to expand...
Click to collapse
Hi, there was is no error in miflash.
You can take a look here if you want to.
Indeed, no error.
Could be a boot sector problem but with dynamic+A/B partitions+A13 , it gets tricky.
NOSS8 said:
Indeed, no error.
Could be a boot sector problem but with dynamic+A/B partitions+A13 , it gets tricky.
Click to expand...
Click to collapse
Can we somehow repair the sector?
Sucharek 233 said:
Can we somehow repair the sector?
Click to expand...
Click to collapse
I saw that you changed a transistor, maybe there is a problem elsewhere that is causing this to happen.
Changing the motherboard with the flex cable might be preferable.
I doubt that what you are trying to do is possible due to the complexity of the current system and especially for boot sectors which are not likely to be accessible with current tools.
Especially since the problem has not been identified with precision.
A little update:
We tried flashing EU rom and the oldest rom, but still no luck. Phone is still bootlooping and switch partition is still broken.