Related
Didn't realize how common this was until I had to look around for a fix. Apparently when flashing a new rom (In this case it was Oxygen OS, Bliss, and Lineage I was trying) It's possible to screw up your Persist partition which govern your sensors. As a result me and a few other people when flashing new roms lose auto-rotate. So I was looking on ways to fix it, but the downloads were too old and broken.
So **** it, I decided to try flashing Miui global from the recovery tool.
So my system image, and recovery image are gone. That leaves me with just Fastboot with unlocked bootloader.
I explained my situation, but here's what I'm really asking. #1 I used to have a Xiaomi account that was authorized to unlock my bootloader. It's been over a year, but before the recovery tool bricked my Mi Pad, it said EDL not authorized. So do you lose your permissions over time? Anyway to get it back.
And #2, does anyone have, know, or would like to provide me backups to vendor, firmware, and/or persist so I can try to fix those? I don't have the time tonight, but even though I don't have a system or recovery, I'm assuming with an unlocked bootloader and fastbook, I can still flash twrp, and work my way from there...
Lastly #3, does anyone know how to bypass EDL not authorized in the recovery tool? This is my preferred way of recovery, since it would reflash all the partitions back to stock and I could just re-mod from there...
I have actually recovered from a destroyed system image, destroyed recovery image, with a locked bootloader. But didn't encounter the EDL issue in my memory, it's been so long I forgot how that happened
Just like to add that I discovered that I still have recovery access, so I could just flash a rom to get back into working order, but that still leaves my sensors not working. So if anyone has a link or backup for Persist partition that would be appreciated
Okay, I know no one replied or helped, but I resolved my own issue, and I'll describe how I messed myself up to get myself better.
1. Flashed a rom via TWRP, this somehow led to rotation not working. Learned rotation sensor data is in Persist partition. Assuming this partition overwritten, corrupted, or likely wiped due to negligence.
2. This led to me trying out Xiaomi recovery tool. I would find out that my account isn't authorized anymore. So flashing tool would always stop flashing when it came to flashing the kernel. Then I created this thread for help. Particularly to acquire a backup of someone's Persist. Help did not arrive
3. This led me to download the Chinese rom (flagship zip) of Miui for Xiaomi Mi Pad 4. This was going to overwrite my recovery and vendor partitions, so I was hoping it would flash my Persist partition as well.
4. System would not boot, softbrick/bootloop. Recovery reverted to stock Chinese. Bootloader still unlocked. Booted into Fastboot
5. ADB terminal, typed:
Code:
fastboot devices
Getting device ID, looking good. Then typed
Code:
fastboot flash recovery rec.img
(I renamed TWRP to rec.img for lazy reasons) ADB says writing flashed recovery successful.
I reboot into recovery. Recovery still Chinese stock ?️?️?
Back to Fastboot, repeat #5, same. Then I type
Code:
fastboot erase recovery
ADB confirms erased recovery, I type:
Code:
fastboot boot recovery
ADB does not detect recovery. So I'm thinking my recovery is gone now... Then I try booting into recovery through Vol Up + Power to make sure recovery had been destroyed... Recovery still Chinese stock ?️?️??
So my assumption was correct that I couldn't overwrite my recovery partition, and my fear was that I needed to enable USB debugging even though my system partition is destroyed
6. I boot back into Fastboot and I type
Code:
fastboot boot rec.img
This boots TWRP without flashing it to your recovery partition... Atleast this works.
7. Attempt to wipe System/Data/Cache/Internal, even though only half those weren't necessary. Could not wipe. Mounted, then repeated... Could not wipe. Assuming this was encryption related, I go back to Wipe and just Slide to format to factory conditions. Finally getting somewhere here.
8. Tired of this hole I dug myself into, I plug in my USB flash drive and flashed TWRP Permanently using TWRP, reboot into recovery to confirm -> looking good -> Flash Lineage + Gapps, with the acceptance that because I didn't have an authorized Xiaomi account anymore, and no one would share a Persist backup, that I was just gonna have to deal with no rotation and rely on an app-crutch
9. Boot into System, rotation working. ?️??️
I didn't think flashing the zippable Chinese rom would actually fix Persist. I originally intend to just use the Chinese Miui and setting up my Mi Pad 4 with my Xiaomi account to somehow re-authorize my account to try the flashing tool again. I did not expect the bootloop, and I damn sure didn't expect ADB telling me I successfully flashed recovery or erased it, only to find out stock recovery kept refusing to go away.
And my final question is:
Can anyone tell me how much usable storage the 32GB Mi Pad 4 should freaking have?!
I always used Micro SD flashed as Internal Storage so I'd always see 80GB free. But now on a fresh install on a new rom I see that I only have 22GB usable storage, on a 32GB device, Lineage less than 1GB, and gapps only 200MB. So all together OS should not exceed 2-3GB unpacked...
WHERE THE HELL IS THE REST OF MY STORAGE?!
I SHOULD HAVE 5 MORE GB, I SHOULD HAVE 26~27GB OF USABLE STORAGE BUT MY SYSTEM SAYS ONLY 22Gb
DOES anyone else have 10GB of storage missing?!
How much should I have?!
Thanks this is good read and may help someone in the future.
There is a persist.zip shared in the Miui 12 port thread.
I have the 64gb version but never took notice of how much remaining storage out of the box. Next time I flash a ROM I'll check and let you know.
scloss84 said:
Thanks this is good read and may help someone in the future.
There is a persist.zip shared in the Miui 12 port thread.
I have the 64gb version but never took notice of how much remaining storage out of the box. Next time I flash a ROM I'll check and let you know.
Click to expand...
Click to collapse
Yeah, I found persist zips but the link was broken.
This is actually the 2nd time I bricked my device, but the 1st time I bricked it, I had just got it around the same time I got the Poco F1, so I had a Xiaomi account, with authorization. So I assumed how I un-bricked my device the 1st time, would fix the brick the 2nd time. I never imagined my account would lose authorization. So flashing the Miui using the Xiaomi recovery tool was useless. So I had to learn/relearn other tricks.
I actually enjoy bricking my devices a little bit for the experience to learn new things. Like this time, I didn't know you could run a recovery on the side through fastboot commands without flashing it. I also didn't know that recovery partition would reject flashes because mi stock recovery was encrypted (or maybe it was a USB debugging thing) , I didn't know Mi Flash authorization could be revoked, and I didn't know what the Persist partition did.
My 1st brick happened because of the Mi recovery tool. No one told me that if you buy a Mi Pad 4 with unlocked bootloader from AliExpress, use the Mi recovery tool, the tool actually intentionally bricks your device and locks your bootloader. The fix for that was opening the mi pad up, shorting some contacts, force the pad into EDL mode, and use a patched bat file and run the tool again and pray it takes. Because I wasn't authorized it wouldn't run the tool.
Thank ****ing God my bootloader was still unlocked this time. I don't think I could have came back
Post 225 in the Miui 12 port thread, the persist.zip is still being shared I checked just now. Not that you really need it if flashing the full rom got your rotation back.
There was 1 time my twrp touch screen became unresponsive after flashing and trying different twrps, and then system touch screen also gone dead, so I can't restore persist even if I wanted to.
One question, lots of tutorials talk about extracting the persist.zip from the fastboot ROM, but I can't find it in the fastboot rom... But the MiFlash tool had never failed me so anything goes wrong I'll just MiFlash it.
I was a Mi A2 user for a while, now I'm moving to Note 9 Pro and I feel a bit lost because of lacking of guides and tools.
I encounter some unexpected issues with disabling phone encryption. In short, I followed the steps I used for my Mi A2, but it seemed only working partially, and I encountered boot loop when upgrading ROM afterwards.
The details are as follow:
I have Note 9 Pro global (joyeuse), originally it was on stock ROM V11.0.5.0.QJZMIXM
After unlocking bootloader, I booted to TWRP with TWRP-3.4.1B-joyeuse-fix.img (from https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ ) and flashed Magisk, then Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (from https://zackptg5.com/android.php#disverfe )
Everything was fine, I could debloat and disable Xiaomi services, and Google Pay was working (with Magisk Hide and MagiskHide Props Config).
But when entering TWRP again, TWRP requested passcode to decrypt data, that's when I realized the phone was not decrypted. Booting to normal mode, phone Settings showed "Encrypted". But because TWRP was able to decrypt with passcode and could backup as normal, so I ignored it.
When V11.0.7.0.QJZMIXM was released, I backed up /data using TWRP and flashed the new ROM using fastboot without erasing data. Then the phone was in boot loop (it showed redmi logo then vibrated then rebooted)
I flashed back V11.0.5.0.QJZMIXM without erasing data, but it still entered boot loop.
I decided to wipe data (using TWRP and using Wipe menu in XIaomi recovery mode), but boot loop still occurred.
I flashed V11.0.7.0.QJZMIXM again, but this time without keeping data (flash_all.bat), but boot loop still occurred.
I accidentally selected flash all & lock bootloader (in MiFlashTool), then phone could boot up normally. But I lost root, and bootloader was relocked.
Additional info: In a rage, I turned on Developer mode and tapped to bind mi account, and now I have to wait 168hrs to unlock bootloader again.
Questions:
What have I done wrong that the phone entered boot loop even after wiping data?
What's the proper way of using TWRP so that I can backup data and can update ROM in the future without going through this mess again?
HRSE said:
I was a Mi A2 user for a while, now I'm moving to Note 9 Pro and I feel a bit lost because of lacking of guides and tools.
I encounter some unexpected issues with disabling phone encryption. In short, I followed the steps I used for my Mi A2, but it seemed only working partially, and I encountered boot loop when upgrading ROM afterwards.
The details are as follow:
I have Note 9 Pro global (joyeuse), originally it was on stock ROM V11.0.5.0.QJZMIXM
After unlocking bootloader, I booted to TWRP with TWRP-3.4.1B-joyeuse-fix.img (from https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ ) and flashed Magisk, then Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (from https://zackptg5.com/android.php#disverfe )
Everything was fine, I could debloat and disable Xiaomi services, and Google Pay was working (with Magisk Hide and MagiskHide Props Config).
But when entering TWRP again, TWRP requested passcode to decrypt data, that's when I realized the phone was not decrypted. Booting to normal mode, phone Settings showed "Encrypted". But because TWRP was able to decrypt with passcode and could backup as normal, so I ignored it.
When V11.0.7.0.QJZMIXM was released, I backed up /data using TWRP and flashed the new ROM using fastboot without erasing data. Then the phone was in boot loop (it showed redmi logo then vibrated then rebooted)
I flashed back V11.0.5.0.QJZMIXM without erasing data, but it still entered boot loop.
I decided to wipe data (using TWRP and using Wipe menu in XIaomi recovery mode), but boot loop still occurred.
I flashed V11.0.7.0.QJZMIXM again, but this time without keeping data (flash_all.bat), but boot loop still occurred.
I accidentally selected flash all & lock bootloader (in MiFlashTool), then phone could boot up normally. But I lost root, and bootloader was re-locked.
Additional info: In a rage, I turned on Developer mode and tapped to bind mi account, and now I have to wait 168hrs to unlock bootloader again.
Questions:
What have I done wrong that the phone entered boot loop even after wiping data?
What's the proper way of using TWRP so that I can backup data and can update ROM in the future without going through this mess again?
Click to expand...
Click to collapse
first of all you are not the only one that faces same problems. So chears mate. Next is the TWRP and the lack of stable/working version since i have done quite few phones now i can tell that the TWRP encryption ignore is not persistent and it works while you don't touch the recovery and not booting it up. Upon the boot it triggers the encryption and although he filesystem is not encrypted it still thinks it is.
Solution for now? wait for the fixed version while this is new phone and may take some time to re-code he recovery (find the damn cause of the encryption trigger).
Anyways. I am still thinking to do the fastboot rom mod, root it while it is not flashed and hen flash it while i don't actually need. I just need to remove all the miui/xiaomi stuff, block the damn ADS and root the phone and those things can be done on a pc i am just figuring out the correct way to do i.
The idea about skipping the TWRP came right after i downloaded mi-flash tool and found out that it uses same fastboot mode to flash everything and the file structure of the rom is not packet or something. Img files can be exacted and re-packed again so everything in the image can be modified.
What i really hate is the fact that there is tons of tools for other phones but somehow Xiaomi was skipped in the device selection...
Downloaded unlock tool, nice but limited to only requesting ad unlocking the phones bootloader. Next thing is the flash tool, it is limited to only flashing. There is xiaomi tool v2 that can also install the twrp, and cause the encryption crap or download and install stock or xiaomi.eu...
What i was looking for was the tool that can take the stock, decompress it and allow you to choose the apps you want to be per-installed, add some functions to it, mod bootscreens, pre-root it and eventually pack and flash the damn thing. While you are skipping the recovery procedure you are way safer than with its crap.
Agree with me?
daigtas said:
first of all you are not the only one that faces same problems. So chears mate. Next is the TWRP and the lack of stable/working version since i have done quite few phones now i can tell that the TWRP encryption ignore is not persistent and it works while you don't touch the recovery and not booting it up. Upon the boot it triggers the encryption and although he filesystem is not encrypted it still thinks it is.
Solution for now? wait for the fixed version while this is new phone and may take some time to re-code he recovery (find the damn cause of the encryption trigger).
Anyways. I am still thinking to do the fastboot rom mod, root it while it is not flashed and hen flash it while i don't actually need. I just need to remove all the miui/xiaomi stuff, block the damn ADS and root the phone and those things can be done on a pc i am just figuring out the correct way to do i.
The idea about skipping the TWRP came right after i downloaded mi-flash tool and found out that it uses same fastboot mode to flash everything and the file structure of the rom is not packet or something. Img files can be exacted and re-packed again so everything in the image can be modified.
What i really hate is the fact that there is tons of tools for other phones but somehow Xiaomi was skipped in the device selection...
Downloaded unlock tool, nice but limited to only requesting ad unlocking the phones bootloader. Next thing is the flash tool, it is limited to only flashing. There is xiaomi tool v2 that can also install the twrp, and cause the encryption crap or download and install stock or xiaomi.eu...
What i was looking for was the tool that can take the stock, decompress it and allow you to choose the apps you want to be per-installed, add some functions to it, mod bootscreens, pre-root it and eventually pack and flash the damn thing. While you are skipping the recovery procedure you are way safer than with its crap.
Agree with me?
Click to expand...
Click to collapse
More than one month, 280 view, 1 comment, no solution, no answer. Everyone out there are competing with each other to create their own ROMs/recovery/kernel images with whatever catchy names they can think of. Nice. But what's the point if the basics are not yet nailed down?
BTW, Telegram channel is flooded with non-contributing chit chat.
My casual observation is that lrtwrp seems to be a common theme for those who have had major issues on Joyeuse.
sir_bazz said:
My casual observation is that lrtwrp seems to be a common theme for those who have had major issues on Joyeuse.
Click to expand...
Click to collapse
For what it's worth, TWRP does not currently have any official builds for curtana OR joyeuse as far as I can tell. The flashing of early, unofficial, pre-alpha ports of TWRP directly onto partitions causing bricks is not that surprising. Xiaomi locking down EDL access is a ****ty move, but still.
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?
The device is a Xiaomi Redmi Note 4 (codename: mido)(4/64 GB variant)
So I had this problem yesterday where I was stuck in a bootloop and was unable to get into recovery, so I asked for help in a few subs and XDA, and some good people suggested various suggestions. What worked for me was going back to stock by flashing a stock fastboot ROM via MiFlash Tool.
After getting back to stock, I tried installing TWRP recovery again and everything went smooth, except the fact that it did not get installed at all and I am still on the default Mi-recovery. I have tried numerous versions of the TWRP image, double checked whether USB debugging is switched on or not, but I still can't seem to install TWRP.
Here's a video of the entire process I followed to install TWRP and the issue I am facing:
Apologies for the long video. It is difficult to hold a film with one hand while trying to do stuff on the PC with the other.
Any help is greatly appreciated. Thank you.
laneofmagic said:
The device is a Xiaomi Redmi Note 4 (codename: mido)(4/64 GB variant)
So I had this problem yesterday where I was stuck in a bootloop and was unable to get into recovery, so I asked for help in a few subs and XDA, and some good people suggested various suggestions. What worked for me was going back to stock by flashing a stock fastboot ROM via MiFlash Tool.
After getting back to stock, I tried installing TWRP recovery again and everything went smooth, except the fact that it did not get installed at all and I am still on the default Mi-recovery. I have tried numerous versions of the TWRP image, double checked whether USB debugging is switched on or not, but I still can't seem to install TWRP.
Here's a video of the entire process I followed to install TWRP and the issue I am facing:
Apologies for the long video. It is difficult to hold a film with one hand while trying to do stuff on the PC with the other.
Any help is greatly appreciated. Thank you.
Click to expand...
Click to collapse
First, I noticed that your TWRP version is old. You said you have tried different versions, but are you sure you tried the latest one? You can download it from here: Download TWRP for mido
Alternatively, you can try with OrangeFox recovery, which is well-recognized as well and personally I use this one: Xiaomi Redmi Note 4 (mido) build releases | OrangeFox Recovery Downloads
Anyway, after the command...
fastboot flash recovery recovery.img
...try this one:
fastboot boot recovery.img
If doesn't work try...
fastboot reboot
..and right after you push Enter button, hold Power and Volume+ buttons.
When you enter the TWRP/OrangeFox finally, you should wipe stock system and format data partition, then flash your custom rom.
Lord Sithek said:
First, I noticed that your TWRP version is old. You said you have tried different versions, but are you sure you tried the latest one? You can download it from here: Download TWRP for mido
Alternatively, you can try with OrangeFox recovery, which is well-recognized as well and personally I use this one: Xiaomi Redmi Note 4 (mido) build releases | OrangeFox Recovery Downloads
Anyway, after the command...
fastboot flash recovery recovery.img
...try this one:
fastboot boot recovery.img
If doesn't work try...
fastboot reboot
..and right after you push Enter button, hold Power and Volume+ buttons.
When you enter the TWRP/OrangeFox finally, you should wipe stock system and format data partition, then flash your custom rom.
Click to expand...
Click to collapse
That worked.
I just realized you are the same person who helped me on reddit as well. Thanks mate, you're awesome.
laneofmagic said:
That worked.
I just realized you are the same person who helped me on reddit as well. Thanks mate, you're awesome.
Click to expand...
Click to collapse
You're welcome, I like to help people if I am able to Enjoy!
Hi, I have Redmi Note 5 and I tried to install TWRP recovery(twrp-3.5.2_9-0-vince.img). But every time in the TWRP it is telling that "Internal Memory" is showing as 0 MB and I am unable to change it. It would be pleasure if you know a method to overcome this issue. Thank you.
Baranetharan said:
Hi, I have Redmi Note 5 and I tried to install TWRP recovery(twrp-3.5.2_9-0-vince.img). But every time in the TWRP it is telling that "Internal Memory" is showing as 0 MB and I am unable to change it. It would be pleasure if you know a method to overcome this issue. Thank you.
Click to expand...
Click to collapse
I think you have to format your data partition, but then you will lose all. Backup first all photos and other things. And why not orange fox?
joke19 said:
I think you have to format your data partition, but then you will lose all. Backup first all photos and other things. And why not orange fox?
Click to expand...
Click to collapse
Redmi Note 5 - Whyred or Vince?
Hello, just come over to ask, want to buy my wife and me new phones and found the xiaomi redmi note 5 (global version). Specs are good enought for us, so want to buy it and want (of course) flash lineageOS but now i am confused with...
forum.xda-developers.com
Thank you so much for the help.
joke19 said:
Redmi Note 5 - Whyred or Vince?
Hello, just come over to ask, want to buy my wife and me new phones and found the xiaomi redmi note 5 (global version). Specs are good enought for us, so want to buy it and want (of course) flash lineageOS but now i am confused with...
forum.xda-developers.com
Click to expand...
Click to collapse
OrangeFOx recovery is also asking for a PIN, that why I am thinking.
Ok, I will prepare to format my device the help.
Thank you so much for the help.
Help request.
Situation:
- Redmi 4X (Global, santoni), bootloader unlocked,
- flash recovery TWRP, v. 3.6.0_9-0 performed by ADB and using "Temporary" same
versions of TWRP,
- flash recovery TWRP, v. 3.5.1_9-0 performed by ADB and using "Temporary" same
versions of TWRP,
- Backup partition recovery is used to check if the flash has actually taken place.
Always with a positive result (each version is checked with "sh2")!
- Reboot into recovery or shutdown and put into recovery mode, always with a positive
result - TWRP recovery works!
- Once the OS has been booted at least once, the contents of the partition recovery will
take effect immediately returns to stock recovery - ALWAYS!
- an attempt was made with flash stock recovery - the result was adequate,
- all these experiments took place even after using SW MiFlash20210226 with parameter
Save user data. Results without change - always returned stock recovery.
Thank you for your help (please excuse your English level - thank you)
nemohouci said:
Help request.
Situation:
- Redmi 4X (Global, santoni), bootloader unlocked,
- flash recovery TWRP, v. 3.6.0_9-0 performed by ADB and using "Temporary" same
versions of TWRP,
- flash recovery TWRP, v. 3.5.1_9-0 performed by ADB and using "Temporary" same
versions of TWRP,
- Backup partition recovery is used to check if the flash has actually taken place.
Always with a positive result (each version is checked with "sh2")!
- Reboot into recovery or shutdown and put into recovery mode, always with a positive
result - TWRP recovery works!
- Once the OS has been booted at least once, the contents of the partition recovery will
take effect immediately returns to stock recovery - ALWAYS!
- an attempt was made with flash stock recovery - the result was adequate,
- all these experiments took place even after using SW MiFlash20210226 with parameter
Save user data. Results without change - always returned stock recovery.
Thank you for your help (please excuse your English level - thank you)
Click to expand...
Click to collapse
I recommend this recovery.
Xiaomi Redmi 4X (santoni) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Redmi 4X (santoni)
orangefox.download
You use mi flash tool as last? Then the customer recovery will be replaced. Mi flash tool, development settings, OEM unlock and flash your recovery over fastboot. Here is a good guide, but don't use the recovery from this site.
[All-in-One] Redmi Note 7 (lavender): Unlock Bootloader, Flash TWRP, Root, Flash ROM
Dear Redmi Note 7 user, I'm not responsible if anything happens to your device. If you execute these AiO procedures properly then you shouldn't face any problems. Before you proceed please back up all your important data and make sure that...
forum.xda-developers.com
Begin by point c