I re-unlocked my device a few days ago after a long time of using MIUI. Unfortunately, I am now facing a peculiar problem I had not faced the previous time I unlocked my device.
I cannot seem to replace MIUI stock recovery with official TWRP.
If I use fastboot flash recovery xxx.img, the terminal does confirm that the action was successful. Yet, when I reboot into recovery, I am greeted by Mi-Recovery 3.0 instead of TWRP.
My initial thought was that maybe there was some restriction in MIUI that prevented the stock recovery from being replaced, so I flashed RR 5.8.5-FINAL. I still cannot flash TWRP.
Some other info:
The MIUI build I was on: MIUI 9 7.9.21 Global Beta
My phone: RN3 SD 2GB/16GB variant, Fpc fingerprint sensor
The temporary workaround I used to flash RR was directly booting into TWRP using fastbooot boot xxx.img
NOTE: I did a standard wipe (factory reset, followed by wiping System, Data and Cache) when I flashed RR.
As you might imagine, using fastboot to boot into TWRP every time I want to flash something is quite tiring and so if anyone can help me to permanently flash TWRP, I'd be really grateful. Thanks in advance.
PS: If this question has already been answered, then please guide me to the relevant thread and I will take down this one.
This problem also happened to my friend's Redmi Note 3 MTK. I don't know if it's going to work on KENZO or not.
The solution is to flash the TWRP recovery image through fastboot ==> Turn off the device by holding down the power button (DISCONNECT PHONE FROM PC) ==> Boot the recovery using button combinations
This should let you boot into TWRP and stays permanent after the first session
Flashing Through Fastboot/EDL Mode
Flashing Twrp through Fastboot is the permanent way of flashing the recovery...The method is very simple and can be done even on locked bootloader but the thing in locked bootloader is that once you have flashed the TWRP the internal storage is inaccessible because the data is encrypted so you need to wipe->format data ...then press "yes" ..by typing yes the internal storage will be formatted completely so make sure you have a backup ...and do copy the ROM file in SD card for flashing ...after wiping process press install then select SD card and flash the ROM and gapps and enjoy the TWRP...
Refer this link for flashing process youtu.be/rCONN1_IPuU(please add https:// before the link)
Hope this solves your problem...
same problem !! did you find any solution !!!
Related
I was running the 8/3 update of Cyanogenmod 13 just fine on my L24. I downloaded the 8/13 nightly from the CM website and tried to flash it, but for some reason it returned error 7, which shouldn't happen because I already updated to EMUI4/MM firmware two weeks ago (as evidenced by me running the 8/3 version with no problems). However, when I then tried to boot back into system, the phone instead booted back into TWRP. Trying to boot into system in any way (from TWRP menu, through bootloader --> fastboot reboot, et cetera) just reboots the phone right into TWRP again. -_-
Now, I can access only TWRP and bootloader, but whenever I try to flash a .zip in TWRP it immediately reboots back into TWRP. I've tried reflashing TWRP (newest version and older versions), flashing the Cyanogenmod recovery for kiwi, factory resetting, and even reflashing the stock recovery and trying to return to stock EMUI. None of these have worked. (And yes, of course I've tried clearing cache/dalvik.)
At this point I'm just looking to actually boot into system...If anyone has any idea how I might be able to fix this, it would be great.
EDIT: to clarify, when I try to flash the ROM in TWRP, I get the following:
updating partition details
full selinux support is present
MTP enabled
and then an immediate reboot. This is very fast - I had to take a video of it and then freeze the frame to see what the message was.
Boot in fastboot and install your crap? Turn phone off connect to your PC hold Power and volume down until it boots.
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
radiobacter said:
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
clsA said:
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
Click to expand...
Click to collapse
Again, the issue is that I can't install any ROM through TWRP, because trying to instantly reboots the phone and brings me back into TWRP. I've tried reflashing TWRP, but it doesn't do anything.
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
radiobacter said:
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
Click to expand...
Click to collapse
The phone is known to be finicky about sd cards. Try formatting it with TWRP
Sent from my SM-N920T using Tapatalk
Hello guys,
There's a problem associated with encryption of my RN 3 Snapdragon edition. Some time ago, I've officially unlocked my bootloader, to flash any custom roms I want, whenever I want (before I was using the way around it, where unlocked bootloader wasn't necessary).
OK. Back to my point, when i unlocked my bootloader, I installed Resurrection Remix rom and it was android 7.x.x I think. Somehow I was offered to encrypt my data, to have better security of my phone, etc. So I encypted it. Then everytime I turn on or reboot the phone, I was asked for a PIN code during the rom start up screen or when entering TWRP recovery. I forgot that my phone was encrypted, and I formated/deleted all possible data on my phone (internal storage, cache, etc) using TWRP and installed a fresh Lineage 8.0. Then it asked for a password on first boot, if i want to use my old data, the old password was not correct and i just chose the option to forget about old data and use it as a new phone. The phone didn't boot at all. It booted only after installing stock MIUI rom via FASTBOOT with miflash tool, and then installing the Android 8.0. But until now it shows, that my phone is encrypted in the settings menu and when i enter TWRP, it tells me the phone is encrypted and I can't see my files on internal memory and it's hard to flash the phone, as I have to use adb sideload or some other ways, but I cannot use the TWRP in normal way.
BTW, I tried factory reseting, wiping everything I can, installing official MIUI roms several times and so on, nothing helped.
If you have any thoughts please write them below, any info is important,
Thanks in advance
Then everytime I turn on or reboot the phone, I was asked for a PIN code during the rom start up screen or when entering TWRP recovery.
Click to expand...
Click to collapse
You obliviously choosed to "Require Pin/Password/Pattern on boot up" when setting up your pin code.
To decrypted the device, you will need to Format Data (Not wipe or Factory Reset), and flash any of following before booting the device:
SuperSU, Magisk, Custom Kernel or FED Patcher.
Thanks alot, it worked.
I've formated data, flashed fresh rom, gapps and custom kernel before first boot up from TWRP.
Reminder!
If you update your rom,
make sure also to reflash the custom kernel before booting the device.
Otherwise your device will encrypt on boot.
Hi. I just received Mi 10 and tried to flash it with xiaomi.eu rom (native one - Global which doesn't support 2 SIM). It was pretty hard as it often declined to boot to the system. Finally I able to flash it successfully and ROM detects both SIM cards. But another problem appears: randomly after reboot phone lose `system` and `data` partitions and stops booting while nothing was touched.
In TWRP (using Chinese TWRP 3.4.1b-0313 by wzsx150) it shows that `data` partition is empty (what cannot be as it contains a lot of apps data) and unable to mount `system_root`. When I ask to reboot to system is says "No OS installed! Are you sure you wish to reboot" that is also strange - OS definitely as installed. One more time - no operations on system partitions were done before device bricked, it just randomly stops booting. While after last installation I rebooted it about 10 times to ensure it works. And after night - it goes to fastboot screen again. While without reboot it works for a long time (before boot uptime was about 6 days).
Device were unlocked after 7-days timeout successfully.
Actions I am doing to flash device (using Linux):
`fastboot flash recovery recovery-TWRP-3.4.1B-0313-XIAOMI10-CN-wzsx150.img` - TWRP flashed ok (I also tried other version include one specified in this thread: Ultimate guide to install stable or Dev rom from Xiaomi.eu)
Boot to TWRP
Format (not wipe) data: re-create FS (i.e. create ext4 FS) and format.
Copy `xiaomi.eu_multi_MI10_20.6.18_v12-10.zip` to device (or use external OTG storage)
Flash it successfully
Copy Magisk 20.4 to device
Reboot to TWRP and flash Magisk
Wipe cache
Reboot to OS
Pass first-time setup, install apps
Reboot couple of time to ensure everything works
Any idea what happens? I ab actually ran out of idea - it is not first phone I am reflashing and not the first Xiaomi device (before used Mi 6 reflashed with LineageOS for about 3 years) and it is first time I see device has probably corrupted data/system partition.
One note: after booting to flashed device I setup fingerprint and pattern for unlock. After reboot when phone cannot boot into OS TWRP doesn't ask for pattern (while in normal situation is should, latest TWRP how to unlock with pattern). It makes me think that at the boot moment partitions already corruppted.
Do that for clean installation:
flash fastboot rom (https://mirom.ezbox.idv.tw/en/phone/umi/) China Stable
when phone is open, shutdown. open fastboot and flash this recovery (https://androidfilehost.com/?fid=8889791610682877442)
in advance wipe section select dalvik, data and internal strorage then wipe
reboot to recovery again, in wipe section do Format Data, then reboot to recovery again
connect pc, put latest eu rom zip to phone then flash
restart and do the first setup
reboot to recovery again and flash Magisk
my redmi note 4 mido is bricked and i don't know how, i left my phone for a month because i travelled away and when i came back the phone was stuck on mi logo i tried to fix it by this methods but nothing worked:
-i tried to flash stock firmware via mi flash tool and it failed so many times (i used an old version which stated that the installation succeed but the phone was still stuck in bootloop)
- i tried edl version and it didn't work
- i tried to install via adb and it didn't work also
- i tried to open recovery (volume + and power) it got me to twrp 3.2.3.0 but it's alway stuck on twrp logo and nothing happens
it only happened 2 times when twrp worked and asked me for decryption password, i wrote my phone pin but said wrong password (tried also password and default_password) then i bypassed the password section and got into twrp but i couldn't mount or format storage (it appears that internal storage and sd card is 0 gb) i tried to format it fails,
tried also to change storage to ext2 it got stuck and i couldn't open the twrp again.
any stock firmware flashed on my mido doesn't work and it still stuck on mi logo ( no android loading logo), and it still has twrp
(i tried to flash another twrp or orangefox it just doesn't flash even if it's successful flash on adb)
i tried also to boot the recovery image it also get stuck on the logo and doesn't open the recovery
please help me to know what the hell is wrong with this phone and how i can fix it
help pleassseeeeeeee
Install magisk if you are stuck in boot loop it fixes the problem otherwise download a recovery rom and change your twrp version to 3.1.0.0 because the decryption password in the new versions of twrp doesn't seem to work on rn4. Now wipe system,vendor,data. import recovery rom from your computer and install it. It will install the rom then flash Magisk otherwise your phone will be stuck in bootloop. Wait for a while and bam your system is back!
i can't install anything or even boot into twrp 3.1.0.0 even if i tried
Can you boot into fastboot atleast? If yes then type fastboot reboot recovery and as you said you have twrp installed then it surely means that your bootloader is unlocked. Do you know the name of your custom rom or are you using stock rom? If yes whichever rom you are using just download the recovery rom of that and extract the boot.img in your adb and fastboot folder and flash it via fastboot by typing fastboot flash boot boot.img . And also when booting in twrp which buttons are you using? This happened to me when I myself bricked my device. I thought I can't boot in twrp but the point was I was using volume up+ power but the actual key to boot to twrp is volume up+volume down+power key
You can flash your Xiaomi Redmi Note 4 [MIDO] using Mi Flash. I have an article that discusses how to flash Xiaomi Redmi Note 4 [MIDO / Snapdragon] that might help you: How to Flash Redmi Note 4 / 4x Snapdragon [Mido] with MiFlash
NOTE: Few problematic tool links in this article. Please search on Google | This website was translated using Google Translate [Indonesian -> English]
pandmc said:
You can flash your Xiaomi Redmi Note 4 [MIDO] using Mi Flash. I have an article that discusses how to flash Xiaomi Redmi Note 4 [MIDO / Snapdragon] that might help you: How to Flash Redmi Note 4 / 4x Snapdragon [Mido] with MiFlash
NOTE: Few problematic tool links in this article. Please search on Google | This website was translated using Google Translate [Indonesian -> English]
Click to expand...
Click to collapse
I think flashing the stock rom should be the last step before which everything possible should be tried
JustExperimentingRedmi said:
I think flashing the stock rom should be the last step before which everything possible should be tried
Click to expand...
Click to collapse
Yes, Flashing Stock ROM should be the last step before he tries to fix. But mostly if the smartphone is bootlooped or bricked there is no other step besides Erase All Data / Format Data or Flashing Stock ROM.
pandmc said:
Yes, Flashing Stock ROM should be the last step before he tries to fix. But mostly if the smartphone is bootlooped or bricked there is no other step besides Erase All Data / Format Data or Flashing Stock ROM.
Click to expand...
Click to collapse
You can flash orignal boot.img which most times fixes the problem and if it didnt work flash system.img it almost always works and the last option is flashing magisk. Then only i will recommend to flash stock rom.
JustExperimentingRedmi said:
Can you boot into fastboot atleast? If yes then type fastboot reboot recovery and as you said you have twrp installed then it surely means that your bootloader is unlocked. Do you know the name of your custom rom or are you using stock rom? If yes whichever rom you are using just download the recovery rom of that and extract the boot.img in your adb and fastboot folder and flash it via fastboot by typing fastboot flash boot boot.img . And also when booting in twrp which buttons are you using? This happened to me when I myself bricked my device. I thought I can't boot in twrp but the point was I was using volume up+ power but the actual key to boot to twrp is volume up+volume down+power key
Click to expand...
Click to collapse
the rom i was using before the phone got bricked is crdroid 10, i downloaded it again as you said and tried to flash boot img then i rebooted into recovery but i got stuck at twrp logo as usual and even if twrp worked it will as for a password i tried all pins i have used on my phone and tried default_password didn't work either, i can't even mount data or storage or anything and it shows everything with 0mb storage (external or internal storage).
i can't even format data to remove encryption it just freezes whenever i do that
pandmc said:
You can flash your Xiaomi Redmi Note 4 [MIDO] using Mi Flash. I have an article that discusses how to flash Xiaomi Redmi Note 4 [MIDO / Snapdragon] that might help you: How to Flash Redmi Note 4 / 4x Snapdragon [Mido] with MiFlash
NOTE: Few problematic tool links in this article. Please search on Google | This website was translated using Google Translate [Indonesian -> English]
Click to expand...
Click to collapse
i tried that before it's always shows me ( mi flash tool could not find a part of the path) error, there's a one time i tried an older version of mi flash tool and the flash succeeded but when phone rebooted it stayed at the bootloop
i checked the recovery and sadly it was still the same twrp recovery
i don't really know if my phone can be fixed or this an emmc problem
So it means you have your stock rom right? Extract boot.img and flash it with
fastboot flash boot boot.img
make sure to put it in adb folder
You can find boot.img in images folder
If it does not work get the system.img and flash it with
fastboot flash system system.img
i flash the whole stock rom via fastboot (adb) and it also didn't work.
sorry if this seems disappointing
Try orangefox recovery then, not sure why is this happening to you
If still not working type
fastboot oem edl
Then flash via mi flash it should work as far as I know. If not then go to mi service centre it's the last thing you can do
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img