Related
After flashing the latest global stable miui 10 ROM on mi max 3, I can't flash tarp without bootloop or stuck on mi logo. My device is Chinese version and before installing global stable miui 10, I flashed twrp successfully. Now I can't even flash eu ROM, it just sticks on mi logo. I tried with magisk, but unlucky. Anyone have the same experience? At last my decision is, this version of miui is the culprit, though I m not sure!
Can you give a bit more information?
What steps did you take and in which order?
mierlo420 said:
Can you give a bit more information?
What steps did you take and in which order?
Click to expand...
Click to collapse
Every possible order.
1st, flashed twrp/s
2. Formatted data, because it asked for password to decrypt
3. Mount every possible partition
4. Wipe all without 'system'
5. Flash eu ROM
6. And it stucks on boot.
And only possible sollution after this stuck for me is, to flash again a fastboot ROM. No recovery ROM at this stage gains a successful boot.
Note: I have to flash several times my phone fastboot ROM to recover phone and try again again. No success. Every time I try it starts from decrypt data option and stuck on boot. Even I tried with flashing magisk also, after flashing eu ROM. But no luck.
At a point I found 'reset phone' option and gboard has stopped bug, but whenever I try to reset, it goes to twrp.
Because global stable and TWRP don't work together. Have you seen anyone root global stable? I haven't. This is why global is not as versatile compared to xiaomi.eu roms.
opasha said:
Because global stable and TWRP don't work together. Have you seen anyone root global stable? I haven't. This yes why global is not as versatile compared to xiaomi.eu roms.
Click to expand...
Click to collapse
But, am i now stuck with no option for twrp or even no option to flash any custom rom like eu roms?
silentext said:
But, am i now stuck with no option for twrp or even no option to flash any custom rom like eu roms?
Click to expand...
Click to collapse
Did you try twrp app? Just as a test. Also try magisk app to install magisk to see if it helps. When we were testing Resurrected kernel, magisk was needed to get past boot screen. None if this is proven to work, but just trying to see if it helps.
opasha said:
Did you try twrp app? Just as a test. Also try magisk app to install magisk to see if it helps. When we were testing Resurrected kernel, magisk was needed to get past boot screen. None if this is proven to work, but just trying to see if it helps.
Click to expand...
Click to collapse
Yes, tried official twrp. Even tried official twrp with magisk. In both case it stuck with booting screen/mi logo. No luck.
Edit: my all tries are: twrp+reboot / twrp+eu rom+magisk+reboot / twrp+lagzyflasher+reboot..
All the combinations resulted in a bootloop/ stuck in mi logo. In every time the only work around to past the boot screen is to flash again a fastboot rom. Only that time it successfully boots.
silentext said:
Yes, tried official twrp. Even tried official twrp with magisk. In both case it stuck with booting screen/mi logo. No luck.
Click to expand...
Click to collapse
When you flash TWRP, you can boot to twrp or no? If you can, then it's when you flash an eu rom where you get stuck? Are you factory resetting before flashing eu rom?
opasha said:
When you flash TWRP, you can boot to twrp or no? If you can, then it's when you flash an eu rom where you get stuck? Are you factory resetting before flashing eu rom?
Click to expand...
Click to collapse
Yes, i can boot to twrp. And always reset to factory/wipe everything before and after flashing eu rom. As i edited my comment above, with just twrp+magisk+reset+reboot / twrp+reset+eurom+magisk+reset+boot every times it gets stuck on reboot after flash.
silentext said:
Yes, i can boot to twrp. And always reset to factory/wipe everything before and after flashing eu rom. As i edited my comment above, with just twrp+magisk+reset+reboot / twrp+reset+eurom+magisk+reset+boot every times it gets stuck on reboot after flash.
Click to expand...
Click to collapse
Who told you to reset after flashing? That's why you're having issues. Don't reset after eu or magisk.
Twrp - factory reset - eu rom - reboot. That's it.
opasha said:
Omg - who told you to reset after flashing! That's why you're having issues. Don't reset after eu or magisk.
Click to expand...
Click to collapse
Oh, no. After Flashing just wiped delvic and cache. It was adviced somewhere.
opasha said:
Who told you to reset after flashing? That's why you're having issues. Don't reset after eu or magisk.
Twrp - factory reset - eu rom - reboot. That's it.
Click to expand...
Click to collapse
But, sure, i m trying again with this plain instruction. Thanks a lot. Though i m sure, i did this plain combination before with no luck. Before flashing global stayble i have flashed eu roms and twrp several times with no trouble.
silentext said:
Oh, no. After Flashing just wiped delvic and cache. It was adviced somewhere.
Click to expand...
Click to collapse
Wiping cache and dalvik cache are not the same as reset. They shouldn't cause any problems. Regardless, try without wiping them.
opasha said:
Wiping cache and dalvik cache are not the same as reset. They shouldn't cause any problems. Regardless, try without wiping them.
Click to expand...
Click to collapse
just tried with your plain instruction. it again stuck with mi logo.
edit: i can reboot to recovery easily.
silentext said:
just tried with your plain instruction. it again stuck with mi logo.
edit: i can reboot to recovery easily.
Click to expand...
Click to collapse
Which eu rom are you flashing? Download the latest 8.10.25. Flash that.
opasha said:
Which eu rom are you flashing? Download the latest 8.10.25. Flash that.
Click to expand...
Click to collapse
yes. that one. 8.10.25.
silentext said:
yes. that one. 8.10.25.
Click to expand...
Click to collapse
Maybe try fastboot flash an ARB 8.10.25 china rom first - clean flash only - don't lock (very important setting at BOTTOM of Miflash Tool).
opasha said:
Maybe try fastboot flash an ARB 8.10.25 china rom first - clean flash only - don't lock (very important setting at BOTTOM of Miflash Tool).
Click to expand...
Click to collapse
oh. i tried that with china 8.10.30 version. because that was my first flash from so called fake global rom that shipped with. but that also didnt work.
silentext said:
oh. i tried that with china 8.10.30 version. because that was my first flash from so called fake global rom that shipped with. but that also didnt work.
Click to expand...
Click to collapse
Don't know what to tell you then. Sorry, buddy.
Try this
1- TWRP flashing method:
Boot Twrp or Redwolf using “fastboot boot XYZ.img”
Copy img to device then flash Image file of XYZ.img again from recovery.
Flash Lazyflasher Or Magisk
Or you can just flash any AOSP/LOS based ROM
Click to expand...
Click to collapse
I got this from Redmi Note 5 Anti-rollback thread here https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that
logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.
so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D
cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards
Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/
daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?
NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way
daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers
i’m going to post this here because i just created an account; so, after unlocking the bootloader on my redmi note 5 (whyred), i successfully installed twrp, the latest version. I deleted everything typing “yes”, then reinstalled twrp theni try to flash the pixel experience and it gives me an error 7, that i fixed with a youtube tutorial. the roms installs, then i wipe data/cache and dalvik, but when i try to boot into the rom the phone is stuck on Mi Unlocked screen for an unlimited amount of time. what can i do?
thisaintalex said:
i’m going to post this here because i just created an account; so, after unlocking the bootloader on my redmi note 5 (whyred), i successfully installed twrp, the latest version. I deleted everything typing “yes”, then reinstalled twrp theni try to flash the pixel experience and it gives me an error 7, that i fixed with a youtube tutorial. the roms installs, then i wipe data/cache and dalvik, but when i try to boot into the rom the phone is stuck on Mi Unlocked screen for an unlimited amount of time. what can i do?
Click to expand...
Click to collapse
same issue, my twrp version: 3.3..1-0
ctplate said:
same issue, my twrp version: 3.3..1-0
Click to expand...
Click to collapse
please let me know if you find anything, its my first modding and im pretty upset
Install Xiaomiflash and download the last fastboot rom for redmi note 5 pro of your region and extract it. then connect your device to your computer, launch Xiaomiflash, click on refresh, if your device was detected, click on the explorer of Xiaomiflash and select the extracted rom. Click on "clean all m" and flash the rom, after a few minute you can boot your smartphone
Sorry for my bad english and sorry for not giving a link, I have a new account
moreover I also had exactly the same problem when trying to flash pixel experience
Try flashing another rom
ugomaugo said:
Try flashing another rom
Click to expand...
Click to collapse
It is OK using havoc os 2.5
ctplate said:
It is OK using havoc os 2.5
Click to expand...
Click to collapse
Yes
thisaintalex said:
i’m going to post this here because i just created an account; so, after unlocking the bootloader on my redmi note 5 (whyred), i successfully installed twrp, the latest version. I deleted everything typing “yes”, then reinstalled twrp theni try to flash the pixel experience and it gives me an error 7, that i fixed with a youtube tutorial. the roms installs, then i wipe data/cache and dalvik, but when i try to boot into the rom the phone is stuck on Mi Unlocked screen for an unlimited amount of time. what can i do?
Click to expand...
Click to collapse
Hi,
Did you install the pie firmware recommanded by the dev (9.4.25 or 9.5.23).
After all I read and perhaps "understood" this is due to not having the right firmware. I mean one of the both I wrote.
Hope it helps...
Download and install FW 9.4.25 from Xiaomi Firmware Page
Have you guys solved this problem?
I have exactly the same problem! I can't install PE or LineAge, Havoc OS works fine for some reason :/
I had this issue, but it solved by install twrp 3.3.1.1 and flash pie f.w, then P.E rom
howdy
Because there was no dedicated thread here on XDA for the redmi note 9 pro (international) on how to root phone
I tried it kind of on my own:
I went here first
to try and unlock the bootloader.
(fyi) it told me I had to wait (I think) 176 hrs or about 1 week before it let me do it.
The problem is that when I try fastboot recovery I get the Redmi flash program instead of TWRP
(I also installed the Miflashtool from here
Thinking about it, I should be able to use THAT tool to install
what I believe is a good TWRP image (from here)
Will update as I make progress!!
cheers, and I do like this phone. fast, spiffy, and even larger then the Note 10 I use for work!
ok, tried the redmi flash tool, and tried to see if I could get the image , it will see the phone after I do a refresh, but cannot find a script
So that doesn't work.
Apparently I need to figure out how to uninstall the redmi recovery partition, so I can install the twrp partition.
at least it boots into android and isn't broken. That's a start!
cheers
Look for bprp miatoll, i have and works perfect.
I have this one: TWRP-3.4.1B-joyeuse-fix.img
It runs perfect!
The file "341 Note 9 Pro.rar" doesn´t run on my phone.
Follow this
that worked for me easily.
---------- Post added at 09:53 AM ---------- Previous post was at 09:53 AM ----------
Follow this
that worked for me easily.
H_a_R_e_L said:
Follow this
that worked for me easily.
---------- Post added at 09:53 AM ---------- Previous post was at 09:53 AM ----------
Follow this
that worked for me easily.
Click to expand...
Click to collapse
so far i know for sure that this phone requires vbmeta.img and correct twrp (twrp-3-4-1b-joyeuse-fix-img) to be installed bu before that erase he recovery o be sure that it will not be corupted. \
Next thing is to deal with he encryption. Disable it with the given scripts at any guide you can find, there is plenty of them. Why? It is known that it may trigger the phone to self encrypt without asking you for permission. Yesterday i wiped out and started from scratch 5-6 times becouse of this crap. so thinking to avoid TWRP and make mod of fastboot rom and flash that. Will see how it will go.
Everything you need to know about TWRP for joyeuse is here: https://xiaomi.eu/community/threads...-note-9-pro-joyeuse-2-versions-already.56896/
hello,
on the global or EEA version for redmi note 9 pro, can j install the orangefox twrp, Alpha-curtana?
carabot said:
hello,
on the global or EEA version for redmi note 9 pro, can j install the orangefox twrp, Alpha-curtana?
Click to expand...
Click to collapse
Of course you can.
The name is deceiving but it is a Miatoll build.
Yemble said:
Everything you need to know about TWRP for joyeuse is here: https://xiaomi.eu/community/threads...-note-9-pro-joyeuse-2-versions-already.56896/
Click to expand...
Click to collapse
I followed this guide and flashed twrp, miui 12 and magisk suceessfully. But problem whenever i run any game ,it crashes to homescreen after few seconds.. Plz help
EDIT: (SOLVED)
Magisk Root was the cause , upon unsitalling completely ,problem is no more. Can anyone tell me why was such the case?
Hello my friends, finaly I succeded to unlock bootloader and flash TWRP (mauronofrio), it works fine... but I didn't worked with a RedmiMi phone till now and when I want to take a nandroid backup I'm confused in TWRP... I don't know what to select for backing up... I found two options "super" with the same size... which of them to select? I'm not sure but I think this is the system partition. Am I wrong?
For backing up I'd selected boot, data and one of those two super option. Am I wrong? Or maybe somedy can tell me what is necesary to select for backup...please I need help! Thank you.
Edit
I'm back my friends, excuse me please... but this way to backup is useless! I tried another ROM and I want to return to the old one but without succes... Yes, the restored backup was "succesfully"... and was ended up with a boot loop and no way to regain access to my system. I had to flash everything from scratch... So, please, can anybody tell me which of the TWRP options should be chosen for a successfully usable backup and restore? Thank you.
I flash TWPR from this: https://xiaomi.eu/community/threads...-note-9-pro-joyeuse-2-versions-already.56896/
My joyeuse turn to Curtana and I can't flash this ROM: MIUI Custom-ROM Builder for Xiaomi RedMi Note 9 Pro EU! (mi-globe.com)
Pls help!
dtbinh said:
I flash TWPR from this: https://xiaomi.eu/community/threads...-note-9-pro-joyeuse-2-versions-already.56896/
My joyeuse turn to Curtana and I can't flash this ROM: MIUI Custom-ROM Builder for Xiaomi RedMi Note 9 Pro EU! (mi-globe.com)
Pls help!
Click to expand...
Click to collapse
Try OrangeFox: https://orangefox.download/device/miatoll
Dungphp is releasing twrp 3.5 builds Over here
jwchips said:
Dungphp is releasing twrp 3.5 builds Over here
Click to expand...
Click to collapse
Awesome. 3.4.0 didn't work any more for me after MIUI 12 upgrade, but this one is fine!
Yep. I can confirm that it worked with the TWRP 3.5 build. Just had to flash the recovery again after I installed MIUI 12 stable. Works like a charm.
here the same. Runs perfect with RROS 8.6.4. Good job done!!!
Thank you !
Hello, will dungphp twrp work with redmi note 9s curtana ?
I have the error device is not certified with locked bootloader after reflashing the persist partition when it was corrupted (I took persist.img file from fastboot rom). I think that a dump of persist partition from the other poco f3 may solve this problem. Dump of persist partition can be made with termux using this commands (need root): 1. su 2. dd if=/dev/block/by-name/persist of=/sdcard/persist.img So, can someone do it and send a file?
Pocouser1357 said:
I have the error device is not certified with locked bootloader after reflashing the persist partition when it was corrupted (I took persist.img file from fastboot rom). I think that a dump of persist partition from the other poco f3 may solve this problem. Dump of persist partition can be made with termux using this commands (need root): 1. su 2. dd if=/dev/block/by-name/persist of=/sdcard/persist.img So, can someone do it and send a file?
Click to expand...
Click to collapse
My Poco F3 is currently on Xiaomi.eu MIUI 14 Weekly. I'm about to flash Stock Poco MIUI 13.0.9 EEA but will keep the bootloader unlocked. I can backup the Persist-partition with my OrangeFox Recovery, do you still want it?
BTW, i'm not sure if I myself would get the Persist-error... On Xiaomi.eu right now I did not get this error.
cyanGalaxy said:
I can backup the Persist-partition with my OrangeFox Recovery, do you still want it?
Click to expand...
Click to collapse
Yes, if it is possible, send the backup of persist
cyanGalaxy said:
My Poco F3 is currently on Xiaomi.eu MIUI 14 Weekly. I'm about to flash Stock Poco MIUI 13.0.9 EEA but will keep the bootloader unlocked. I can backup the Persist-partition with my OrangeFox Recovery, do you still want it?
BTW, i'm not sure if I myself would get the Persist-error... On Xiaomi.eu right now I did not get this error.
Click to expand...
Click to collapse
So, could you send your persist backup?
Pocouser1357 said:
I have the error device is not certified with locked bootloader after reflashing the persist partition when it was corrupted (I took persist.img file from fastboot rom). I think that a dump of persist partition from the other poco f3 may solve this problem. Dump of persist partition can be made with termux using this commands (need root): 1. su 2. dd if=/dev/block/by-name/persist of=/sdcard/persist.img So, can someone do it and send a file?
Click to expand...
Click to collapse
1) Clean Flash any A12 AOSP rom
2) Reboot into the rom and use it for 10min
3) Clean Flash Stock Fastboot rom
This procedure worked according to some people with this problem
Hi,
Yep been there, it very easy to get a fresh copy from any MIUI rom, my F3 is the EEA version, i used Alioth_eea_V12.5.6.0.RKHEUXM_07-09-2021,
Pocouser1357 said:
I have the error device is not certified with locked bootloader after reflashing the persist partition when it was corrupted (I took persist.img file from fastboot rom). I think that a dump of persist partition from the other poco f3 may solve this problem. Dump of persist partition can be made with termux using this commands (need root): 1. su 2. dd if=/dev/block/by-name/persist of=/sdcard/persist.img So, can someone do it and send a file?
Click to expand...
Click to collapse
Hi Been there,
but i have a unlocked bootloader, i downloaded the latest MIUI Firmware, only to be faced with the dreaded,
"find device storage corrupted your device is unsafe now"
what was strange is that when i logged into my Miui account the message disappeared as soon as i signed out of my account the message came back,
i tried a Xiaomi.eu rom but i still had the same issue.
I backed up a copy of my Persist.img file "just in case" using TWRP Recovery`s built in terminal: using the command dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img.
I used TWRP Recovery 3.6.2 12 POCOF3 v6.3 A12-alioth-skkk to flash the persist.img from the "Original" https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHEUXM/
rom and that did the trick, no more nag screen.
Please note this Persist.img is for EEA Firmware only,
I hope this helps
johnr64 said:
Hi Been there,
but i have an unlocked bootloader, i downloaded the latest MIUI Firmware, only to be faced with the dreaded "find device storage corrupted your device is unsafe now", what was funny is that when i logged into my Miui account the message disappeared, as soon as i signed out of my account the message came back,
i tried a Xiaomi.eu rom but i still had the same issue.
I backed up a copy of my Persist.img file just in case using the TWRP Recovery built in terminal: using the command dd if=/dev/block/by-name/persist of=/sdcard/persist.img.
I used TWRP to flash the persist.img from the original fastboot rom and that did the trick, no more nag screen.
Please note this for EEA Firmware, https://pixeldrain.com/u/LVDrGrm8
I hope this helps
Click to expand...
Click to collapse
Is you device certified with locked bootloader? I tried this methode, no more error but the device is not certified with locked bootloader
makes me wonder why people ignore the fix because it sounds easy and look for complicated methods that dont fix the issue
3zozHashim said:
1) Clean Flash any A12 AOSP rom
2) Reboot into the rom and use it for 10min
3) Clean Flash Stock Fastboot rom
This procedure worked according to some people with this problem
Click to expand...
Click to collapse
didn't work bro, do you know any other trick for this?
Did you find the img bro
airb05 said:
didn't work bro, do you know any other trick for this?
Click to expand...
Click to collapse
This process works, I have done it last week. I was getting that storage corrupted message, but all sensors were working fine. My issue was due improper downgrade stages from A13 to A11, this should be step by step A13> A12> A11. I have not touched persist partition until used these steps. MIUI 14 A13 EU > PE 12 (Use it for few minutes) > Flash A12 stock using MI flash. Use this safe method, flashing persist is only last resort and useful when sensors are broken. I hope someone pin these steps, coz i was struggling to find such instructions for almost 2 months. Thank you 3zozHashim
ketanmore said:
This process works, I have done it last week. I was getting that storage corrupted message, but all sensors were working fine. My issue was due improper downgrade stages from A13 to A11, this should be step by step A13> A12> A11. I have not touched persist partition until used these steps. MIUI 14 A13 EU > PE 12 (Use it for few minutes) > Flash A12 stock using MI flash. Use this safe method, flashing persist is only last resort and useful when sensors are broken. I hope someone pin these steps, coz i was struggling to find such instructions for almost 2 months. Thank you 3zozHashim
Click to expand...
Click to collapse
Can you please send us dump for persist partition because we flashed the persist and this blown away key attestation generator.
Ineed a backup from a working phone to regenerate the the gey attestation generator
I made it before in one plus and worked perfectly
ketanmore said:
This process works, I have done it last week. I was getting that storage corrupted message, but all sensors were working fine. My issue was due improper downgrade stages from A13 to A11, this should be step by step A13> A12> A11. I have not touched persist partition until used these steps. MIUI 14 A13 EU > PE 12 (Use it for few minutes) > Flash A12 stock using MI flash. Use this safe method, flashing persist is only last resort and useful when sensors are broken. I hope someone pin these steps, coz i was struggling to find such instructions for almost 2 months. Thank you 3zozHashim
Click to expand...
Click to collapse
i already flashed persist.img bro i can't wait so long for someone to reply but thanks for your help
ketanmore said:
My issue was due improper downgrade stages from A13 to A11, this should be step by step A13> A12> A11.
Click to expand...
Click to collapse
Interesting. I think this might be it because if I remember correctly I too tried to go back to A11 from A13 and then the error appeared.
Edit: Tried it and it didn't work for me.
For me i tried to go back to pixel experience A13 from MIUI 14 Eu rom and again to stock MIUI 13. Any Solution?
puskalregmi9 said:
For me i tried to go back to pixel experience A13 from MIUI 14 Eu rom and again to stock MIUI 13. Any Solution?
Click to expand...
Click to collapse
I tried the A13>A12>A11 downgrade recently but unfortunately it didn't work.
I turned on location and logged into my MI account. Rebooted a few times and then flashed persist.img from twrp. After flashing the persist.img the error is gone now.
No clear solution for now. Trial and error.
user0u said:
I tried the A13>A12>A11 downgrade recently but unfortunately it didn't work.
I turned on location and logged into my MI account. Rebooted a few times and then flashed persist.img from twrp. After flashing the persist.img the error is gone now.
No clear solution for now. Trial and error.
Click to expand...
Click to collapse
Which TWRP version did you use? And miui version.
puskalregmi9 said:
Which TWRP version did you use? And miui version.
Click to expand...
Click to collapse
I went from Custom A13 Rom > Official MIUI 13 > Official MIUI 12.
TWRP 3.6.1_11-0 was used while on MIUI 12 to flash persist.
user0u said:
I went from Custom A13 Rom > Official MIUI 13 > Official MIUI 12.
TWRP 3.6.1_11-0 was used while on MIUI 12 to flash persist.
Click to expand...
Click to collapse
Thanks i will try the same. Can you help me flash persist via twrp, i tried via orange fox didnot suceed.