Hello Everyone
I have a redmi note 11 Spes, I had TWRP installed and working and the phone was rooted.
Until the last system update 13.0.5.0.SGCINXM that removed the custom recovery and root.
I had to flash it back but the phone didn't boot and keep going back to recovery, I had the pull the boot.img from the latest stock rom and flash it with adb so the phone can boot.
but after trying all the TWRP I found on the internet for redmi note 11 Spes I also tried orange fox too and SHRP no1 worked either it stucks on MI logo or boot directly to recovery or bootloader.
When I try to flash an old stock Rom with miFlash and choose clean all or save user data it always ends with this error "error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done" ,the rom is flashed and work but still can't install a custom recovery the same problem stuck in MI logo or boot to recovery or bootloader.
But when I choose clean all and lock the operation ends with no error I just need to unlock the bootloader again after that still cant make any custom recovery works.
when I try to flash a stock rom, same error when I choose clean all or save user data .
Testing any of those custom recovery with a custom ROM they work with no issue.
Anyone has an Idea what can be the issue.
Regard
ssamurai said:
Hello Everyone
I have a redmi note 11 Spes, I had TWRP installed and working and the phone was rooted.
Until the last system update 13.0.5.0.SGCINXM that removed the custom recovery and root.
I had to flash it back but the phone didn't boot and keep going back to recovery, I had the pull the boot.img from the latest stock rom and flash it with adb so the phone can boot.
but after trying all the TWRP I found on the internet for redmi note 11 Spes I also tried orange fox too and SHRP no1 worked either it stucks on MI logo or boot directly to recovery or bootloader.
When I try to flash an old stock Rom with miFlash and choose clean all or save user data it always ends with this error "error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done" ,the rom is flashed and work but still can't install a custom recovery the same problem stuck in MI logo or boot to recovery or bootloader.
But when I choose clean all and lock the operation ends with no error I just need to unlock the bootloader again after that still cant make any custom recovery works.
when I try to flash a stock rom, same error when I choose clean all or save user data .
Testing any of those custom recovery with a custom ROM they work with no issue.
Anyone has an Idea what can be the issue.
Regard
Click to expand...
Click to collapse
I'm not very familiar wtih Redmi devices, but I think they are pretty close to Pixels in the partition layout, meaning they don't have a separate recovery partition. Since the recovery kernel lives in the boot image, flashing a custom recovery image to /boot overwrites the existing kernel and ramdisk. Your device is doing what it's supposed to - loading what's in /boot, which happens to only be the custom recovery.
There does not seem to be a way to permanently install a custom recovery on these devices, because the recovery kernel is compressed, and most custom recoveries do not support the compression needed. Instead, you'd want to "live boot" your recovery image - fastboot boot twrp.img - which sends the image to your phone to temporarily load WITHOUT writing it to the partition.
V0latyle said:
I'm not very familiar wtih Redmi devices, but I think they are pretty close to Pixels in the partition layout, meaning they don't have a separate recovery partition. Since the recovery kernel lives in the boot image, flashing a custom recovery image to /boot overwrites the existing kernel and ramdisk. Your device is doing what it's supposed to - loading what's in /boot, which happens to only be the custom recovery.
There does not seem to be a way to permanently install a custom recovery on these devices, because the recovery kernel is compressed, and most custom recoveries do not support the compression needed. Instead, you'd want to "live boot" your recovery image - fastboot boot twrp.img - which sends the image to your phone to temporarily load WITHOUT writing it to the partition.
Click to expand...
Click to collapse
Interesting perspective. I've seen this behavior beyond just the lack of a recovery partition, all the way to finding no way to permanently install a custom recovery on this device via ramdisk within TWRP, etc. Some instructions exist on how to install it permanently to ramdisk from within the custom recovery, but none of those attempts worked, at least not on crDroid 9.3 for me. I posted a question about trying a method of flashing a custom recovery to ramdisk directly from fastboot to this forum and the ROM developer, but neither produced any responses. This suggests that it would not be recommended or even possible (I am loath to risking potential data loss), since apparently it has not worked for anyone yet. All my attempts to permanently install a custom recovery on this recovery partition-free phone from recovery send me back to fastboot only.
The installed recovery with crDroid 9.3 is basic and I really want to replace it.
EDIT: I was successful in replacing the stock with TWRP 3.7.0_12-0.img to "ramdisk." Before, it was repeatedly dumping me back to fastboot regardless of choosing system or recovery target. Yay!
thank you for our replies
It's fixed i
the rick was in miflash tool atfer doing many research in the internet, the rick was to check verbose and erase all in miflash tool config also removing what's in checkpoint
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in the config file inside the rom folder I edited flash_all.bat file and removed all the lines that have Antirollback, flashing an old rom worked and the phone booted after flashing TWRP and root
i am using the same device as you (spes) and i flashed twrp using android platform tools
and i used the following command to boot into twrp then install it from the twrp advanced menu
fastboot boot (twrp.img)
i am using a custom rom and i installed magisk root and i dont have any issues/bootlooping hope this helps
barantas0147 said:
i am using the same device as you (spes) and i flashed twrp using android platform tools
and i used the following command to boot into twrp then install it from the twrp advanced menu
fastboot boot (twrp.img)
i am using a custom rom and i installed magisk root and i dont have any issues/bootlooping hope this helps
Click to expand...
Click to collapse
Please identify which Android version and custom ROM name and version you are using, the step you used to "install it from the twrp advanced menu", and what version of TWRP you are using. Also, please describe what you ultimately see when you choose "recovery" as your reboot target from TWRP, and again with choosing "system."
Sheist! said:
Please identify which Android version and custom ROM name and version you are using, the step you used to "install it from the twrp advanced menu", and what version of TWRP you are using. Also, please describe what you ultimately see when you choose "recovery" as your reboot target from TWRP, and again with choosing "system."
Click to expand...
Click to collapse
1.) i use crDroid 9.3 (Android 13)
2.)after booting into twrp (using the "fastboot boot twrp.img" command) in the advanced menu there is an option called "flash current twrp" which makes the twrp recovery permanent
3.) i use twrp 3.6.1 (unofficial)
i didnt understand the following:
" Also, please describe what you ultimately see when you choose "recovery" as your reboot target from TWRP, and again with choosing "system." "
but this link could help you out:
forum.xda-developers.com/t/shared-unofficial-a12-a13-twrp-3-7-0-for-redmi-note-11-spes-spesn.4507819/
barantas0147 said:
1.) i use crDroid 9.3 (Android 13)
2.)after booting into twrp (using the "fastboot boot twrp.img" command) in the advanced menu there is an option called "flash current twrp" which makes the twrp recovery permanent
3.) i use twrp 3.6.1 (unofficial)
i didnt understand the following:
" Also, please describe what you ultimately see when you choose "recovery" as your reboot target from TWRP, and again with choosing "system." "
but this link could help you out:
forum.xda-developers.com/t/shared-unofficial-a12-a13-twrp-3-7-0-for-redmi-note-11-spes-spesn.4507819/
Click to expand...
Click to collapse
What is the source for the TWRP 3.6.1? What name is it? i.e. Nebrassy, Jabiyeff, kewl, etc
Please provide your source link. (important)
To clarify my last question for you, reboot/recovery and then reboot/system within TWRP, did it reboot to recovery/system, or did you get sent to fastboot?
barantas0147 said:
but this link could help you out:
forum.xda-developers.com/t/shared-unofficial-a12-a13-twrp-3-7-0-for-redmi-note-11-spes-spesn.4507819/
Click to expand...
Click to collapse
That post/link only provides 3.7.0, not 3.6.1. The 3.7.x install attempts were all fails for me before and I really do not want to return to that horrorland again.
What link did you use to get your 3.6.1?
barantas0147 said:
1.) i use crDroid 9.3 (Android 13)
2.)after booting into twrp (using the "fastboot boot twrp.img" command) in the advanced menu there is an option called "flash current twrp" which makes the twrp recovery permanent
3.) i use twrp 3.6.1 (unofficial)
i didnt understand the following:
" Also, please describe what you ultimately see when you choose "recovery" as your reboot target from TWRP, and again with choosing "system." "
but this link could help you out:
forum.xda-developers.com/t/shared-unofficial-a12-a13-twrp-3-7-0-for-redmi-note-11-spes-spesn.4507819/
Click to expand...
Click to collapse
Is this your link for the 3.6.1 TWRP?: https://forum.xda-developers.com/t/recovery-twrp-3-6-1-spes-android-11-only-stable-shared.4557149/ (this one looks like the dblenk9 TWRP 3.6.1)
That states this: "Decrypted (Does not support encryption,so format data is necessary to use recovery for A12)" - (which means if you install your ROM encrypted, this recovery will NOT work for you! I am decrypted already, since the always-format step is necessary most of the time anyway with ROM installs, but not everyone may be aware of this.)
Also notice it explicitly says "Android 11 only" at the top (I am on A13), and the following at the end:
"Do not replace the recovery or try to update recovery that comes with roms. This can cause problems such as reboots, apps crashing,etc as recovery is integrated into boot partition in which kernel is also integrated."
crDroid DOES provide its own recovery! It is not nearly as powerful as TWRP or Orangefox, which is why I want to move off it.
You can use the "Install Recovery Ramdisk" option in the custom recovery of your choice, after booting it with "fastboot boot <recovery.img>" ( no quotation marks )
EDIT: The one I use: https://forum.xda-developers.com/t/...p-3-7-0-for-redmi-note-11-spes-spesn.4507819/
Vagelis1608 said:
You can use the "Install Recovery Ramdisk" option in the custom recovery of your choice, after booting it with "fastboot boot <recovery.img>" ( no quotation marks )
EDIT: The one I use: https://forum.xda-developers.com/t/...p-3-7-0-for-redmi-note-11-spes-spesn.4507819/
Click to expand...
Click to collapse
This finally worked for me to "ramdisk!" Woo hoo.
barantas0147 said:
1.) i use crDroid 9.3 (Android 13)
2.)after booting into twrp (using the "fastboot boot twrp.img" command) in the advanced menu there is an option called "flash current twrp" which makes the twrp recovery permanent
3.) i use twrp 3.6.1 (unofficial)
i didnt understand the following:
" Also, please describe what you ultimately see when you choose "recovery" as your reboot target from TWRP, and again with choosing "system." "
but this link could help you out:
forum.xda-developers.com/t/shared-unofficial-a12-a13-twrp-3-7-0-for-redmi-note-11-spes-spesn.4507819/
Click to expand...
Click to collapse
This finally worked for me to "ramdisk." I used the 3.7.0_12-0.img.
Related
Hi, I've just got my MI 5 and it is very, very nice. But I am now starting to look further into it and I am confused by all the different ROMs....
The one I have came with MIUI Global 7.3 | Stable MI7.3.3.0.0(MAACNDD). First confusion is that I can't find any references to a ROM by that number anywhere - it has double 0 at the end MI7.3.3.0.0. Is it a real ROM?
More generally I can't work out which ROM would be best for a user in the UK? Without rooting that is so CM is out for the moment.
Can anyone point me in the right direction, thanks.
It may be fake rom. If you want to use MIUI better flash xiaomi.eu ROM: https://xiaomi.eu/community/threads/6-6-23.32335/ but it will need unlocked bootloader.
Without unlocking bootloader you can flash official global using MiFlash: http://en.miui.com/download-299.html
Thanks! I have applied to unlock the bootloader and will flash the unofficial ROM ASAP. Well, I will do some more reading to see which is most appropriate to me.
palexr said:
Thanks! I have applied to unlock the bootloader and will flash the unofficial ROM ASAP. Well, I will do some more reading to see which is most appropriate to me.
Click to expand...
Click to collapse
Hey how did you get on with this ? did you get the unlock code ?
Im in a similar situation to you
Ry2mkk said:
Hey how did you get on with this ? did you get the unlock code ?
Im in a similar situation to you
Click to expand...
Click to collapse
Not done it yet.
I need to flash the China Dev ROM first apparently. I think I will use this method to flash to a "recovery" (?) ROM from which I can then flash the China Dev ROM and then subsequently flash one of the unofficial eu miui ROMs.
I'll update when I have found the time to do all these things.
Hey, I can tell that you'll have an easier time if you do what I did:
Apply for bootloader unlock. Do the unlock (follow the guide here to be sure) It should work on any ROM, mine was China 7.3.2.0.
Back up any images, videos etc. to your PC.
Download a ROM zip of your choice (xiaomi eu in your case but any compatible ROM on this forum or on miui forum will do)
Get the Xiaomi eu TWRP zip from their page. Extract the recovery img file, and the boot img file.
You could also get SuperSU zip from their page if you want root.
Do you have adb and fastboot? If not, just get "minimal adb and fastboot" from the forum here for Windows, or if you're on Linux your package manager probably has them both listed.
Put your phone into fastboot. (Switch off, press volume down and power button until it boots to a screen saying fastboot.) Then connect to your PC.
Open your command prompt from the "run" dialogue: cmd
Use this command: (double check this by googling)
fastboot flash recovery (path to recovery img)
Since you plan to flash xiaomi eu ( you don't need this for a CM based ROM):
fastboot flash boot (path to boot img)
Now to go into the recovery:
fastboot boot recovery (path to recovery img)
There is probably an easier way to do this but I'm not sure of it yet.
Your phone will boot into TWRP. You might face the unresponsive touchscreen bug (I did) but it goes away after some time (or you could plug unplug it from the PC multiple times, seemed to work for someone else on the forums).
If it asks you for the encryption password (it asked me, and I was on a Chinese ROM so it might ask you) then you'll have to wipe the data partition under the wipe menu (it's named as internal storage). This is why the backup was needed.
Under the wipe menu, you'll need to do a factory reset, but I wiped everything just to be safe. Now, just after wiping when I tried to access the internal storage from twrp (Under advanced > file manager) it didn't show me anything (probably because I wiped the internal storage). So just reboot into twrp (reboot > recovery) and it should show the internal storage now.
Open the internal storage on your PC (still connected, right?) and put the xiaomi eu ROM in the internal storage. Then go to install menu in TWRP and select the ROM and flash it. After it's done, it'll offer to wipe cache and dalvik cache. Do it to be safe.
Flash the SuperSU zip if you want it.
Reboot to system.
Profit.
Disclaimer: I haven't flashed xiaomi eu ROM so I cannot guarantee that the steps are perfect. Normally, I would just point you to xiaomi eu's website, but the reason I wrote in such detail is because they say "Install TWRP zip via updater app or fastboot", which is stupid, because not even OFFICIAL xiaomi ROMs work with the updater app (I tried to install global stable and it said couldn't verify package what even), and fastboot mode doesn't allow flashing zips... so. Also, I've read that xiaomi eu comes with Google apps preinstalled, so that's good. Otherwise you need to download even that zip and flash just after flashing the ROM.
andy356 said:
Hey, I can tell that you'll have an easier time if you do what I did:
Apply for bootloader unlock. Do the unlock (follow the guide here to be sure) It should work on any ROM, mine was China 7.3.2.0.
Back up any images, videos etc. to your PC.
Download a ROM zip of your choice (xiaomi eu in your case but any compatible ROM on this forum or on miui forum will do)
Get the Xiaomi eu TWRP zip from their page. Extract the recovery img file, and the boot img file.
You could also get SuperSU zip from their page if you want root.
Do you have adb and fastboot? If not, just get "minimal adb and fastboot" from the forum here for Windows, or if you're on Linux your package manager probably has them both listed.
Put your phone into fastboot. (Switch off, press volume down and power button until it boots to a screen saying fastboot.) Then connect to your PC.
Open your command prompt from the "run" dialogue: cmd
Use this command: (double check this by googling)
fastboot flash recovery (path to recovery img)
Since you plan to flash xiaomi eu ( you don't need this for a CM based ROM):
fastboot flash boot (path to boot img)
Now to go into the recovery:
fastboot boot recovery (path to recovery img)
There is probably an easier way to do this but I'm not sure of it yet.
Your phone will boot into TWRP. You might face the unresponsive touchscreen bug (I did) but it goes away after some time (or you could plug unplug it from the PC multiple times, seemed to work for someone else on the forums).
If it asks you for the encryption password (it asked me, and I was on a Chinese ROM so it might ask you) then you'll have to wipe the data partition under the wipe menu (it's named as internal storage). This is why the backup was needed.
Under the wipe menu, you'll need to do a factory reset, but I wiped everything just to be safe. Now, just after wiping when I tried to access the internal storage from twrp (Under advanced > file manager) it didn't show me anything (probably because I wiped the internal storage). So just reboot into twrp (reboot > recovery) and it should show the internal storage now.
Open the internal storage on your PC (still connected, right?) and put the xiaomi eu ROM in the internal storage. Then go to install menu in TWRP and select the ROM and flash it. After it's done, it'll offer to wipe cache and dalvik cache. Do it to be safe.
Flash the SuperSU zip if you want it.
Reboot to system.
Profit.
Disclaimer: I haven't flashed xiaomi eu ROM so I cannot guarantee that the steps are perfect. Normally, I would just point you to xiaomi eu's website, but the reason I wrote in such detail is because they say "Install TWRP zip via updater app or fastboot", which is stupid, because not even OFFICIAL xiaomi ROMs work with the updater app (I tried to install global stable and it said couldn't verify package what even), and fastboot mode doesn't allow flashing zips... so. Also, I've read that xiaomi eu comes with Google apps preinstalled, so that's good. Otherwise you need to download even that zip and flash just after flashing the ROM.
Click to expand...
Click to collapse
Thanks Andy, that is a really useful reply and I will definitely use to flash my next ROM.
In the meantime I managed to update to the latest official global ROM using the updater! I tried initially to Chinese Dev one put I got the same "can't verify package" error message. I had downloaded it on my PC and transferred it manually to the phone. I then downloaded the global version directly to the phone and that worked.
So now I need to figure out if i need to be on the Chinese dev rom to unlock or if the official global rom will do?
Unlocking can be done on any ROM. I unlocked on Chinese stable. It's good that you could flash the global ROM, at least the sense of urgency to get Google play services is gone now.
I have tried a number of times to install TWRP (unrooted) on my Nexus 6. I am following the instructions from here
https://twrp.me/devices/motorolanexus6.html
I am noting the warnings here
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Once I issue the fastboot reboot command before the Nexus 6 shows anything on the display I press power and vol down and get into TWRP. It seems to what it's supposed to do (presumably patch the stock ROM) and then I reboot to Android.
But the next time I boot to recovery I end up with stock recovery again. I have tried this a number of times and while I can get TWRP installed it always reverts to stock recovery after the next restart.
Is there something else I have missed here in the instructions? They seem fairly clear.
Not that I think it matters but I am running 7.1.1 (flashed with the OTA image since I was not getting OTA updates)
Thanks
Instead of using the fastboot command to reboot to recovery after you have flashed TWRP do it manually. Been a while but I believe that should work.
Dont use the fastboot reboot command, use the volume keys to enter twrp recovery after flashing twrp in fastboot mode
Once you are in twrp swipe to allow changes and if needed change twrp settings, after that reboot into rom.
TMG1961 said:
Dont use the fastboot reboot command, use the volume keys to enter twrp recovery after flashing twrp in fastboot mode
Once you are in twrp swipe to allow changes and if needed change twrp settings, after that reboot into rom.
Click to expand...
Click to collapse
I have done that several times. This is the screen I see when TWRP is loading for the first time.
Not sure if those red messages are fatal or not
When I am in TWRP I can reboot to recovery and it gets back to TWRP but if I reboot to system and then try to enter TWRP on a reboot (holding power and volume up/down it boots into the Fastboot and when I choose Recovery mode I send up with stock recovery again.
Am running 7.1.1 myself and flashed the latest TWRP 3.1.1-0
Were did you download the twrp img from? I download mine from https://dl.twrp.me/shamu/ Once i downloaaded it i rename it to recovery.img
I use cmd on laptop andhook up the phone, then run adb reboot bootloader followed by fastboot flash recovery recovery.img, then i use the volume keys to get into twrp, swipe to allow changes and make changes to settings. Then reboot into rom.
TMG1961 said:
Am running 7.1.1 myself and flashed the latest TWRP 3.1.1-0
Were did you download the twrp img from? I download mine from https://dl.twrp.me/shamu/ Once i downloaaded it i rename it to recovery.img
I use cmd on laptop andhook up the phone, then run adb reboot bootloader followed by fastboot flash recovery recovery.img, then i use the volume keys to get into twrp, swipe to allow changes and make changes to settings. Then reboot into rom.
Click to expand...
Click to collapse
That is pretty much what I have been doing. The only difference is, the first time I did this (before I realised it wasn't working), I rebooted from adb and I did see the swipe to allow changes. But since then if I boot from abd or boot from the bootloader, I don't see the TWRP option to swipe to allow changes anymore.
I wonder if it's because the data is encrypted (standard on a N6?)
I checked the box to not show the swipe to allow modification. I have never decrypted my phone and twrp sticks. So not sure why yours isnt sticking.
TMG1961 said:
I checked the box to not show the swipe to allow modification. I have never decrypted my phone and twrp sticks. So not sure why yours isnt sticking.
Click to expand...
Click to collapse
Well the first time I did it I saw that message about allow modification and I agreed. Never seen it again.
The point of installing TWRP was to install a custom ROM. I wonder if I load the ROM image into the phone first, install TWRP and get into the first time, which I can, then install the ROM would that work?
lchiu7 said:
Well the first time I did it I saw that message about allow modification and I agreed. Never seen it again.
The point of installing TWRP was to install a custom ROM. I wonder if I load the ROM image into the phone first, install TWRP and get into the first time, which I can, then install the ROM would that work?
Click to expand...
Click to collapse
After using fastboot to flash TWRP, use the volume and power buttons to boot into TWRP, and allow modifications, then make a backup and reboot system. Go back to recovery and if all is well, then flash your ROM. Make sure you've got your TWRP issue fixed first though.
The same thing keeps happening to me. I can't seem to make twrp stick. I'd really appreciate some help.
Depending on what your doing, typically you have to manually boot into recovery after flashing twrp (from fastboot), don't use fastboot reboot xxxx. Use the power/volume key combo to reboot. Then accept either system modification or flash a systemless root solution. This will enable custom recovery to "stick". Otherwise, stock android will overwrite recovery on boot.
The TWRP thread has discussions about this. Starting at post 1044 should help.
mrcreativity said:
The same thing keeps happening to me. I can't seem to make twrp stick. I'd really appreciate some help.
Click to expand...
Click to collapse
Is your device encrypted before you flash TWRP?
Yes it is encrypted.
Anyway, I tried all the various methods and combinations but ended up going back to stock recovery. What worked was flashing SU after TWRP.
I'm running pure nexus now and enjoying it.
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
IronJacob said:
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
Click to expand...
Click to collapse
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
lolo9393 said:
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
Click to expand...
Click to collapse
No i did know. Just tried but both twrp don't work.
Btw i'll try to write in that thread too.
Thank you
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Stoffl_ said:
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Click to expand...
Click to collapse
As written on eu forum, the only recovery working is the 3.2.2.
Every other recovery, 1208 too give me:
Mi logo (unlocked) - black screen - Mi logo (unlocked) - system. But no recovery.
Tried to flash a custom rom different to xiaomi.eu but got bootloop, same with kernel flashable zips on xda. Only bootlooo...
I really don't know what to do anymore...
Yeah weird, I've literally guided a friend through the process just yesterday with that method.
Zero issues
My phone keeps getting stuck on fastboot mode.
I'll flash the standard MIUI ROM using the MiFlash Tool, then I flash a custom recovery and a custom ROM(EvolutionX in this case), everything works and I can set up my phone, but as soon as I reboot I can no longer boot into android or recovery. i've tried flashing multiple recoveries using fastboot and straight up booting a recovery using "fastboot boot recovery.img" but it still always go to fastboot. The only solution is to start the process all over again, and obviously that's just not an option since I can never turn my phone off after that.
Any tips?
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Out of all that, the one instruction that solves it is the format data step. This is the magic step required. You always need to do this when flashing over MIUI.
Flashing vendor was totally irrelevant.
This will tell you what you need to do.
Simple Guide to flashing successfully
Here's a quick guide to some of the basics. Which recovery. ---------------------------- Use the latest from here. https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363/post79823568 Do not use Orange...
forum.xda-developers.com
Thanks a lot man! I'm having this issue and it is beyond annoying. I've lost so much time with this BS.
Edit: Does not help actually
I just had the same problem with my Lamentablet.
I was trying stuff up and restarted it in fastboot mode and got stuck there.
So, ways to deal with it:
adb reboot recovery
rebooted the tablet in recovery mode. All I had then was to press the power button to activate Reboot. Solved! From now on it boots normally.
Meanwhile I had discovered that by typing
fasboot continue
the tablet would resume, but at the next reboot cycle, power down + up cycle or reboot after a crash, the tablet would reboot into fastboot mode...
And I found this out when it crashed (it's not called a Lamentablet for nothing!).
Luckily I had a PC with Linux around. It didn't have the software installed but drivers were already in the Kernel and installing adb and fastboot was a matter of mere seconds. If I didn't have an easily ready PC at hand, this tablet would have become a brick until plugged in and rebooted...
OMG Thanks dude.... I'm literally working to installing custom rom on redmi 7a from stock rom but I don't know what reason that make my phone always stuck on fastboot when format data, before this was fine.
Osga21 said:
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Click to expand...
Click to collapse
thanks bro. flashing vendor after a format from twrp did the good
I'm on a POCO M4 Pro 5G eea global V13.0.1.0.SGBEUXM, and my fastboot doesn't accept the "fastboot reboot recovery" command.
Every time I install the recovery.img, then I can't go to the installed custom recovery, I tried every solution I could find:
fastboot flash recovery recovery.img
fastboot reboot bootloader
and then select Recovery using Vol-Up/Down buttons + Power button to start the recovery ROM
Click to expand...
Click to collapse
1.fastboot set_active b
2.fastboot flash boot_b New_fox.img
3.fastboot reboot recovery
4.Select "Flash current OrangeFOX" in menu (automatically flashe to both slot ab )
5.Select "reboot" in menu
6.Select "Slot A is active"
7. reboot
Click to expand...
Click to collapse
fastboot flash recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
fastboot boot twrp.img
Click to expand...
Click to collapse
None of these methods allowed me to initialize the installed custom recovery.
Any suggestion?
Thank you so much in advance
escalhavardo said:
I'm on a POCO M4 Pro 5G eea global V13.0.1.0.SGBEUXM, and my fastboot doesn't accept the "fastboot reboot recovery" command.
Every time I install the recovery.img, then I can't go to the installed custom recovery, I tried every solution I could find:
None of these methods allowed me to initialize the installed custom recovery.
Any suggestion?
Thank you so much in advance
Click to expand...
Click to collapse
hi
I think the arraki's TWRP on xda cannot be started.
Better to use orangeFox.
There is no Recovery partition on this phone, so we use "fastboot flash boot recovery.img".
I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Edited: I managed to restore boot.img (thank God) :
Fastboot flash boot_a boot.img (Original firmware)
Fastboot flash boot_b boot.img (Original firmware)
fastboot reboot
escalhavardo said:
I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Click to expand...
Click to collapse
Use Xiaomi Flash Tool.
If you can get into fastboot mode, you can restore.
Then do the following. or give up.
1.fastboot set_active b
2.fastboot flash boot_b New_fox.img
3.fastboot reboot recovery
4.Select "Flash current OrangeFOX" in menu (automatically flashe to both slot ab )
5.Select "reboot" in menu
6.Select "Slot A is active"
7. reboot
escalhavardo said:
I think I just bricked my phone. I got it to enter in orangefox, then I selected restart system, and then is just looping into poco logo.
I can enter in fastboot, but even when i restore the original boot.img, it keeps looping in poco logo.
Can someone give me a help? I don´t have a clue how to boot a firmware trough fastboot
Very thankfully in advance
Edited: I managed to restore boot.img (thank God) :
Fastboot flash boot_a boot.img (Original firmware)
Fastboot flash boot_b boot.img (Original firmware)
fastboot reboot
Click to expand...
Click to collapse
I forgot to say
Be careful not to lock bootloader with Xiaomi Flash Tool. It's a very confusing setting.
kousuke5555 said:
6.Select "Slot A is active"
Click to expand...
Click to collapse
Where is "Slot A is active" ? i don´t see it
Did you mean "Switch to slot A" ?
Thank you so much, you're a lifesaver.
escalhavardo said:
Where is "Slot A is active" ? i don´t see it
Did you mean "Switch to slot A" ?
thank you so much, your a life saver.
Click to expand...
Click to collapse
Go back to fastboot
"fastboot set_active a"
1.fastboot getvar current-slot
2.if the result is slot a.(slot a in which the system boots)
3.fastboot set_active b
4.fastboot flash boot_b New_fox.img
5.fastboot reboot recovery
6.Select "Flash current OrangeFOX" in menu (automatically flash to both slot a/b )
7.Select "back"
8.Select "reboot" in menu
9.Select "Slot A is active"
10.reboot
You solved my problem. Thank you so much for all your help. You're a life saver.
kousuke5555 said:
I forgot to say
Be careful not to lock bootloader with Xiaomi Flash Tool. It's a very confusing setting.
Click to expand...
Click to collapse
Can you send me unlocked bootloader backup of poco m4 pro 5g i just locked it and i can't unlock it now because my phone is bricked and it's showing nv data is corrupted if you have solution on this plz share it.
delete
kousuke5555 said:
hi
We can't solve boot loops with the bootloader locked.
Please go to the service center.
Had you backed up seccfg.img, you could have unlocked it again.
However, it is specific to each device.
I can't send.
Click to expand...
Click to collapse
Do you have any other solution to this error "nv data is corrupted"
delete
It's important to note that many devices do not have a recovery partition. A/B slot devices are an example of this. The recovery kernel, as well as the system kernel and ramdisk, is in /boot. If you flash a recovery image to /boot, this overwrites anything that was already in there, meaning that you just deleted your system kernel.
To work around this, do not FLASH custom recoveries, but instead LIVE BOOT them:
fastboot boot twrp.img
This tells your device to load the image you're sending, without flashing it to the boot partition.
From here, once TWRP is running, you should be able to install TWRP which replaces the recovery kernel in /boot with TWRP, while preserving your system kernel.
However, in many cases, installing TWRP shouldn't be necessary at all if you can flash partitions directly from fastboot.
If you made this mistake and your device is only booting to TWRP, simply reflash the factory boot image.
V0latyle said:
It's important to note that many devices do not have a recovery partition. A/B slot devices are an example of this. The recovery kernel, as well as the system kernel and ramdisk, is in /boot. If you flash a recovery image to /boot, this overwrites anything that was already in there, meaning that you just deleted your system kernel.
To work around this, do not FLASH custom recoveries, but instead LIVE BOOT them:
fastboot boot twrp.img
This tells your device to load the image you're sending, without flashing it to the boot partition.
From here, once TWRP is running, you should be able to install TWRP which replaces the recovery kernel in /boot with TWRP, while preserving your system kernel.
However, in many cases, installing TWRP shouldn't be necessary at all if you can flash partitions directly from fastboot.
If you made this mistake and your device is only booting to TWRP, simply reflash the factory boot image.
Click to expand...
Click to collapse
hi
Unfortunately, some models of xiaomi cannot use the fastboot "boot" command.
The method mentioned in the thread here is a last resort.
I've talked to some developers but they don't accept this method.
sad.
However, there is no thread in xda, but the developer made twrp, so I think we should use it.
shanawgray said:
Do you have any other solution to this error "nv data is corrupted"
Click to expand...
Click to collapse
hi
I'm sorry. I was wrong.
I thought I needed an official unlock.
but maybe it seems that SP Flash Tool can also be used for locked.
How-to-fix-system-destroyed-on-locked-MTK-bootloader
ttps://telegra.ph/How-to-fix-system-destroyed-on-locked-MTK-bootloader-07-10
"nv data is corrupted" may be another issue.
Perhaps putting in the "correct" stock ROM might fix it.
However, it may be impossible if nvram is completely erased.
There are smart people who made the guide link above in the telegram group, so I think you should talk to them.
kousuke5555 said:
hi
I'm sorry. I was wrong.
I thought I needed an official unlock.
but maybe it seems that SP Flash Tool can also be used for locked.
How-to-fix-system-destroyed-on-locked-MTK-bootloader
ttps://telegra.ph/How-to-fix-system-destroyed-on-locked-MTK-bootloader-07-10
"nv data is corrupted" may be another issue.
Perhaps putting in the "correct" stock ROM might fix it.
However, it may be impossible if nvram is completely erased.
There are smart people who made the guide link above in the telegram group, so I think you should talk to them.
Click to expand...
Click to collapse
Hi
I was trying to flash gsi on my poco m4 pro 5g and that didn't work and my phone got bricked after that i flash stock rom with sp flash tool but the download only option was not working then i try to flash with format all + download and it did worked and the error started showing up. can i bypass that error "nv data is corrupted" and boot into system?
shanawgray said:
Hi
I was trying to flash gsi on my poco m4 pro 5g and that didn't work and my phone got bricked after that i flash stock rom with sp flash tool but the download only option was not working then i try to flash with format all + download and it did worked and the error started showing up. can i bypass that error "nv data is corrupted" and boot into system?
Click to expand...
Click to collapse
If you flash the wrong stock ROM (for example, evergreen rom → evergo rom) with SP TOOL and get "nv data is corrupted", it is highly likely that you can fix it by flashing the original ROM.
However, your case is different.
format all + download is a taboo setting.
I think the unique IMEI information was also erased.
Since it is a new problem apart from the bootloader lock problem, recovery is very difficult.
This is a problem beyond my knowledge
I'm sorry.
kousuke5555 said:
If you flash the wrong stock ROM (for example, evergreen rom → evergo rom) with SP TOOL and get "nv data is corrupted", it is highly likely that you can fix it by flashing the original ROM.
However, your case is different.
format all + download is a taboo setting.
I think the unique IMEI information was also erased.
Since it is a new problem apart from the bootloader lock problem, recovery is very difficult.
This is a problem beyond my knowledge
I'm sorry.
Click to expand...
Click to collapse
thanks.....!
but I think I got the solution
For those looking at this thread.
Just in case, I'll mention it below.
This article is about "arraki's" TWRP and orangefox.
Information is old.
there's a new TWRP, so any troubles or questions should be resolved in that TWRP thread.
Thank you