Database Info

[Q] Recovery Boot Loop Problem

Had a problem. Hope someone with experience can give me a few answers.
Nave new t-mobile Note 3, SM-N900T. Stock 4.4.2 KitKat Touchwiz rooted.
Rooted to enable SDFix to use SD card as I want to use it.
Everything great! No problems.
Thought it would be wise to have a Nanoid backup.
Opened Rom Manager and made One change in prefrences. I set it for external SD card storage. (mistake?)
Went to 'Backup current Rom' in Rom manager, started it and it started to reboot. Shut down and restarted in a 'Recovery' boot loop??
No matter what I did, Tried holding power, up volume and home button, nothing. Boot loop continued. Removed battery, waited, as soon as I re-installed battery it instantly went back into recovery boot loop.
I don't know what I did, I kept removing battery and trying again and again and all of a sudden, it booted up back to KitKat and now everything is working great again. No problem on any standard reboot.
What happened? I have used this same set up on my S3 and never had a problem.
I would like to backup the current setup for any future problems. But now, I'm afraid to even try.
I removed Rom Manager and re-installed. Made sure that the storage location was reset to internal and it should be OK??
What did I do when I got out of the Recovery boot loop??
So, afraid to try again. Don't want the boot loop again.

rspilot1 said:
Had a problem. Hope someone with experience can give me a few answers.
Nave new t-mobile Note 3, SM-N900T. Stock 4.4.2 KitKat Touchwiz rooted.
Rooted to enable SDFix to use SD card as I want to use it.
Everything great! No problems.
Thought it would be wise to have a Nanoid backup.
Opened Rom Manager and made One change in prefrences. I set it for external SD card storage. (mistake?)
Went to 'Backup current Rom' in Rom manager, started it and it started to reboot. Shut down and restarted in a 'Recovery' boot loop??
No matter what I did, Tried holding power, up volume and home button, nothing. Boot loop continued. Removed battery, waited, as soon as I re-installed battery it instantly went back into recovery boot loop.
I don't know what I did, I kept removing battery and trying again and again and all of a sudden, it booted up back to KitKat and now everything is working great again. No problem on any standard reboot.
What happened? I have used this same set up on my S3 and never had a problem.
I would like to backup the current setup for any future problems. But now, I'm afraid to even try.
I removed Rom Manager and re-installed. Made sure that the storage location was reset to internal and it should be OK??
What did I do when I got out of the Recovery boot loop??
So, afraid to try again. Don't want the boot loop again.
Click to expand...
Click to collapse
Hi. What recovery are you using?
If you haven't installed a custom recovery, then that explains your issue. Basically, the app scheduled a custom recovery script which kept failing in the stock recovery. You should normally be able to reboot into the system holding the power button, thus skipping going to recovery. This also resets the recovery script so everything is back to normal.
Nandroid is normally only possible using a custom recovery like TWRP or CWM.
I saw that you might be able to perform a Nandroid without restarting the phone (so without a custom recovery) using this app: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en
I have never tried it. Looks promising though.
But please note that you won't be able to restore the backup without a custom recovery.
EDIT: If you do have a custom recovery, why not boot in recovery mode and make the backup from there?
Cheers

Recovery Boot Loop Problem
I have CWM installed. Setup thru Rom Manager as I have done before on other phones.
Tried it again, same thing. Over and over. Constant reboot. Dosen't matter if I hold the power button or try different ways, same thing.
It says: Recovery booting
Recovery is not seandroid enforcing
Set warranty bit:recovery
If I remove battery and wait a couple of minutes, I can install battery and it dosen't start till I hold power button.
So I held volume down, home button and power button and booted into download mode. From there I cancelled and it rebooted normally.
Everything I've read on boot loops always say 'boot into recovery'. I only wish I could. That's the bootloop.
Any idea on what's wrong?
Thank you for your time and trouble.

rspilot1 said:
I have CWM installed. Setup thru Rom Manager as I have done before on other phones.
Tried it again, same thing. Over and over. Constant reboot. Dosen't matter if I hold the power button or try different ways, same thing.
It says: Recovery booting
Recovery is not seandroid enforcing
Set warranty bit:recovery
If I remove battery and wait a couple of minutes, I can install battery and it dosen't start till I hold power button.
So I held volume down, home button and power button and booted into download mode. From there I cancelled and it rebooted normally.
Everything I've read on boot loops always say 'boot into recovery'. I only wish I could. That's the bootloop.
Any idea on what's wrong?
Thank you for your time and trouble.
Click to expand...
Click to collapse
Have you tried booting directly into recovery?
So just shut off your phone and then open it by holding volume up + home + power. It should boot into recovery. If it doesn't, I recommend installing cwm or TWRP using Odin instead of Rom manager.
Might be a problem with your current recovery.
Sent from my GT-I9505

Recovery Boot Loop Problem
andreiav said:
Have you tried booting directly into recovery?
So just shut off your phone and then open it by holding volume up + home + power. It should boot into recovery. If it doesn't, I recommend installing cwm or TWRP using Odin instead of Rom manager.
Might be a problem with your current recovery.
Sent from my GT-I9505
Click to expand...
Click to collapse
Yes, I tried. Does the same thing.
I've never used Odin. All the info I've read mentioned downloading USB drivers and using different .tar files. Checking this and that.
Nothing I've ever done.
No experience with it.
Never had a reason before to use it.
Every instruction website I've read all seem to be different.
I'm gonna have to find out, huh? lol
I've got Odin on my computer, and have the CWM 6 zipped file.
Will do some research.
Thanks

rspilot1 said:
Yes, I tried. Does the same thing.
I've never used Odin. All the info I've read mentioned downloading USB drivers and using different .tar files. Checking this and that.
Nothing I've ever done.
No experience with it.
Never had a reason before to use it.
Every instruction website I've read all seem to be different.
I'm gonna have to find out, huh? lol
I've got Odin on my computer, and have the CWM 6 zipped file.
Will do some research.
Thanks
Click to expand...
Click to collapse
No problem.
A few tips with odin:
-If you have Kies installed, you don't need to install other drivers.
-The file you flash with Odin should have tar or tar.md5 extension
-you have to activate USB debugging from developer options.
-boot your phone into download mode
-run Odin as administrator
-connect your phone. you should see the text Added in Odin. If don't see it, you need drivers.
-you should make sure only auto reboot and f. Reset time are checked
-you should put the file in Pda or Ap(if using latest version)
Click start and wait until it finishes. It will restart itself if you checked auto reboot.
That's about it. It's very safe and easy to use.
Watch some videos on YouTube. You will definitely find some.
Cheers
Sent from my GT-I9505

Recovery Boot Loop Problem
andreiav said:
No problem.
A few tips with odin:
-If you have Kies installed, you don't need to install other drivers.
-The file you flash with Odin should have tar or tar.md5 extension
-you have to activate USB debugging from developer options.
-boot your phone into download mode
-run Odin as administrator
-connect your phone. you should see the text Added in Odin. If don't see it, you need drivers.
-you should make sure only auto reboot and f. Reset time are checked
-you should put the file in Pda or Ap(if using latest version)
Click start and wait until it finishes. It will restart itself if you checked auto reboot.
That's about it. It's very safe and easy to use.
Watch some videos on YouTube. You will definitely find some.
Cheers
Sent from my GT-I9505
Click to expand...
Click to collapse
Thank you, that answered some questions.
you've been a great help.

Recovery Boot Loop Problem
rspilot1 said:
Thank you, that answered some questions.
you've been a great help.
Click to expand...
Click to collapse
Update: The install of CWM with Odin seemed to be successful. Still have same problem.
I believe the problem must be somewhere else.
Something is stopping the recovery boot. More research ahead.
When I find out more, will post here and give update.

rspilot1 said:
Update: The install of CWM with Odin seemed to be successful. Still have same problem.
I believe the problem must be somewhere else.
Something is stopping the recovery boot. More research ahead.
When I find out more, will post here and give update.
Click to expand...
Click to collapse
Strange. You could try TWRP instead of CWM. I use TWRP and really like it:
Here is the download link for your device: http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
This is the Odin flashable recovery.
Here is TWRP page: http://teamw.in/project/twrp2/
EDIT: One more thing. Are these the exact steps you are following when booting into recovery?
"To access recovery mode on your Note 3, turn off the device and press Volume Up+Home+Power buttons at the same time for about 4-6 seconds. When the screen lights up and you see the Samsung logo, release the Power button but keep Volume Up+Home keys pressed until you see the recovery menu screen"
Cheers

Recovery Boot Loop Problem
andreiav said:
Strange. You could try TWRP instead of CWM. I use TWRP and really like it:
Here is the download link for your device: http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
This is the Odin flashable recovery.
Here is TWRP page: http://teamw.in/project/twrp2/
EDIT: One more thing. Are these the exact steps you are following when booting into recovery?
"To access recovery mode on your Note 3, turn off the device and press Volume Up+Home+Power buttons at the same time for about 4-6 seconds. When the screen lights up and you see the Samsung logo, release the Power button but keep Volume Up+Home keys pressed until you see the recovery menu screen"
Cheers
Click to expand...
Click to collapse
Yes, if I use the buttons, the download mode comes up saying 'Boot failed'. That's holding the vol. button 'up'. If I hold vol. down, it loads download mode correctly.
If I try to enter recovery thru Rom Manager, Recovery tries to start and the boot loop starts. ??
I may try TWRP. I've heard a lot about it.
Thanks for the links.

Recovery Boot Loop Problem
rspilot1 said:
Yes, if I use the buttons, the download mode comes up saying 'Boot failed'. That's holding the vol. button 'up'. If I hold vol. down, it loads download mode correctly.
If I try to enter recovery thru Rom Manager, Recovery tries to start and the boot loop starts. ??
I may try TWRP. I've heard a lot about it.
Thanks for the links.
Click to expand...
Click to collapse
Is changing over to TWRP as simple as installing CWM on Odin??
Just install and try?

rspilot1 said:
Is changing over to TWRP as simple as installing CWM on Odin??
Just install and try?
Click to expand...
Click to collapse
Yep. 5 minutes process at most
Sent from my GT-I9505

Recovery Boot Loop Problem
andreiav said:
Yep. 5 minutes process at most
Sent from my GT-I9505
Click to expand...
Click to collapse
Success!! TWRP works!!
Installed with Odin and it started up fine. Backed up system on my Ext. SD card and rebooted back to OS.
Perfect!
Don't know what happened to CWM but problem is solved thanks to your help.
If your ever in Winter Haven, Fl area, I'll buy you a steak dinner.
Thank you.

rspilot1 said:
Success!! TWRP works!!
Installed with Odin and it started up fine. Backed up system on my Ext. SD card and rebooted back to OS.
Perfect!
Don't know what happened to CWM but problem is solved thanks to your help.
If your ever in Winter Haven, Fl area, I'll buy you a steak dinner.
Thank you.
Click to expand...
Click to collapse
Awesome! Really glad it worked.
Cheers!
Sent from my GT-I9505

[Q] Can't get to recovery after (successful) upgrade to KK.

Hi,
just got time to update my 2nd XT925 to KK (RSD'd back from CM11 JBBL to stock SFR rom, let the phone find its update and apply it, everything went fine).
But whatever KK recovery I try to flash, it gives me an exclamation mark and nothing else (I'm unlocked, yes).
Don't know what's happening here. Can someone helps please ?

Poursinet said:
Hi,
just got time to update my 2nd XT925 to KK (RSD'd back from CM11 JBBL to stock SFR rom, let the phone find its update and apply it, everything went fine).
But whatever KK recovery I try to flash, it gives me an exclamation mark and nothing else (I'm unlocked, yes).
Don't know what's happening here. Can someone helps please ?
Click to expand...
Click to collapse
Are you saying you are trying to flash a recovery or are you trying to GET to the stock recovery? If you are trying to get to the stock recovery, the key presses to get to it have changed.
Your best bet is to power off your phone. Then, press and hold power+vol up for a few seconds until you see the menu come up. Then, press vol down to highlight Recovery and then press the vol up button.
Eventually, you'll see the "Dead Andy". From there, press and hold vol down+vol up+power. You might have to do it a couple of times. Eventually, you'll be in the recovery but for the XT926, it's kind of hard to read because for some reason, they decided to make it dim.

No (but thanks anyway). What I tried to was only to install a KK recovery for CM11.
I successed but I had 2 problems mixed: the 1st one was that the Linux version of fastboot (or mfastboot) did'nt work with the new bootloader. Both were complaining about "(bootloader) Variable not supported! ". Had to find some old laptop with Windows installed to use it to flash the recovery without error.
But even then if I just let the phone reboot, I would'nt get the new recovery (just the stock one after the keypress you speak about). I had to go straight from bootloader screen to the recovery (by manually rebooting) to get it work. Looks like the standard boot just restored the stock recovery each time I tried.
Thanks anyway, it's working now.

Poursinet said:
No (but thanks anyway). What I tried to was only to install a KK recovery for CM11.
I successed but I had 2 problems mixed: the 1st one was that the Linux version of fastboot (or mfastboot) did'nt work with the new bootloader. Both were complaining about "(bootloader) Variable not supported! ". Had to find some old laptop with Windows installed to use it to flash the recovery without error.
But even then if I just let the phone reboot, I would'nt get the new recovery (just the stock one after the keypress you speak about). I had to go straight from bootloader screen to the recovery (by manually rebooting) to get it work. Looks like the standard boot just restored the stock recovery each time I tried.
Thanks anyway, it's working now.
Click to expand...
Click to collapse
Variable not supported comes up under some Windows, but it usually still works.
You never go straight to the bootloader when you reboot. You have to reboot the phone (or turn it off first) and then press and hold vol up+power. Then, from there, you use vol down to select recovery and then press vol up.
It never boots directly into the recovery unless you tell it to via an ADB command or from within a custom ROM that allows it.

Keep in mind, the stock recovery will override the custom recovery if you don't immediately boot back into recovery. Flash recovery, when that's done, press power to shutdown, and use the method Bolski described to boot into recovery.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
Keep in mind, the stock recovery will override the custom recovery if you don't immediately boot back into recovery. Flash recovery, when that's done, press power to shutdown, and use the method Bolski described to boot into recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Let me see if i undestood.
You say that if you don't boot right into recovery, the stock one will overwrite CWM/TWRP. So i understand that, after very reboot you must reflash recovery if you want to use it again.
Or am I missing something?

Caliburno said:
Let me see if i undestood.
You say that if you don't boot right into recovery, the stock one will overwrite CWM/TWRP. So i understand that, after very reboot you must reflash recovery if you want to use it again.
Or am I missing something?
Click to expand...
Click to collapse
It won't reflash every time. You only need to boot straight into recovery the first time, so that the update binary completes. After the first time, you'll be good.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
It won't reflash every time. You only need to boot straight into recovery the first time, so that the update binary completes. After the first time, you'll be good.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I think this may be the problem I am having. I cant get my 926 to boot to recovery from fastboot after I load CWM recovery. Is there some trick?

[SOLVED] Unable to root - Recovery is NOT SEANDROID ENFORCING

Phone: Samsung Sprint S5 GM-900P
System: Windows 7
Build: KTU84P.G900PVPU1ANK4 (4.4.4)
Recovery Screen shows:
Android system recovery <3e>
KTU84P.G900PVPU1ANK4
Additional files available/used:
Odin v3.07
CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
philz_touch_6.57.8-klte.tar
ERROR shown after reboot into recovery:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
I tried following the directions from this thread:
ODIN Installation (detailed)
http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Everything worked as I thought it should, but the phone hangs at the recovery screen with above error.
I flash phil's recovery, and the phone will then boot up as normal, but SuperSU reports unable to inject SU binary
I dont care about tripping knox, just looking for a stock build with root (recovery and system) added.
I have rooted my Epic, S2, S3 & S4 with no issues, and as far as I can tell, everything runs as it should, the phone just hangs after the reboot at the recovery screen and never starts the rooting process in the recovery.
I figure I am either missing something simple, or got an update that root wont take with.
Anyone have any tips as to what I am missing and/or doing wrong?

Did you try flashing them from a powered off state, ie battery pull or power off then booting to download mode? That's an essential step in each odin flash
Sent from my SM-G900P using Tapatalk

Yes I did, but I guess I can always try again to be 100%, thanks. :good:
I actually have been flashing for years, that is why I am so puzzled, as everything went how it is supposed to, it is just the rooting process does not start once the phone reboots into recovery.
I watched the vid to see if I just dropped a step, it all matched, but where the phone boots into recovery and asks to root, just never seems to kick off.

You can also try download supersu zip 2.36 then odin custom recovery and flash supersu then boot up. That's what I did on nk4
Sent from my SM-G900P using Tapatalk

banccalif said:
Did you try flashing them from a powered off state
Click to expand...
Click to collapse
This helped... I got it fixed!!
The version of ODIN I had, had auto-reboot checked, and grayed out so you could not uncheck.
I ODIN'ed philz_touch_6.57.8-klte.tarphilz
when ODIN showed the block with finished, and before the phone restarted, I pulled the battery (had back open) & the cable and didnt let boot
I ODIN'ed CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
Pulled battery/cable (no booting!!), then booted directly into Recovery
Waited, it came up into custom recovery, I selected reroot, and BAM!!

Glad to have helped!
Sent from my SM-G900P using Tapatalk

DCRocks said:
This helped... I got it fixed!!
The version of ODIN I had, had auto-reboot checked, and grayed out so you could not uncheck.
I ODIN'ed philz_touch_6.57.8-klte.tarphilz
when ODIN showed the block with finished, and before the phone restarted, I pulled the battery (had back open) & the cable and didnt let boot
I ODIN'ed CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
Pulled battery/cable (no booting!!), then booted directly into Recovery
Waited, it came up into custom recovery, I selected reroot, and BAM!!
Click to expand...
Click to collapse
^This did it for me, holy crap!
I followed the root procedure to a 'T' like you and it would get stuck exactly where yours got stuck.
Seems to me that the stock recovery after rooting is what may be the culprit if this happens???
Either way now I can get everything going hopefully and remove the bloat, some of the nag notifications, etc.
Thanks

I tried these exact steps and I am still getting errors.

y0c0nsci3nc3 said:
I tried these exact steps and I am still getting errors.
Click to expand...
Click to collapse
If autoroot doesn't work for you go and download supersu 2.37 zip (Google it) Odin custom recovery pull battery, boot to recovery and flash supersu them you should be good to go.

banccalif said:
If autoroot doesn't work for you go and download supersu 2.37 zip (Google it) Odin custom recovery pull battery, boot to recovery and flash supersu them you should be good to go.
Click to expand...
Click to collapse
I ended up flashing the NK5 4.4.2 ROM in ODIN then used towelroot.

So I followed the same steps and nothing happened it just froze at the screen on boot.
I was using 4.4.4 stock rom. I fixed mine by installing philz or some other recovery software.
I went into the setting under advance in philz recovery and ran reroot.
It rebooted and I installed supersu and it worked perfect after that.
Hope someone else can get theres to work but I think the problem is with 4.4.4 that people and me didnt read that it doesnt work properly and you have to take extra steps.
DCRocks said:
Phone: Samsung Sprint S5 GM-900P
System: Windows 7
Build: KTU84P.G900PVPU1ANK4 (4.4.4)
Recovery Screen shows:
Android system recovery <3e>
KTU84P.G900PVPU1ANK4
Additional files available/used:
Odin v3.07
CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
philz_touch_6.57.8-klte.tar
ERROR shown after reboot into recovery:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
I tried following the directions from this thread:
ODIN Installation (detailed)
http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Everything worked as I thought it should, but the phone hangs at the recovery screen with above error.
I flash phil's recovery, and the phone will then boot up as normal, but SuperSU reports unable to inject SU binary
I dont care about tripping knox, just looking for a stock build with root (recovery and system) added.
I have rooted my Epic, S2, S3 & S4 with no issues, and as far as I can tell, everything runs as it should, the phone just hangs after the reboot at the recovery screen and never starts the rooting process in the recovery.
I figure I am either missing something simple, or got an update that root wont take with.
Anyone have any tips as to what I am missing and/or doing wrong?
Click to expand...
Click to collapse

installed 10.4, can't install twrp

anyone managed this? 10.4 flashes ok, and i can install twrp recovery but can't get it to start into twrp. using 'fastboot boot twrp.img' while holding up restarts but screen eventually shows kinda corrupted colours then restarts. recovery remains as standard miui.

apesgrapes said:
anyone managed this? 10.4 flashes ok, and i can install twrp recovery but can't get it to start into twrp. using 'fastboot boot twrp.img' while holding up restarts but screen eventually shows kinda corrupted colours then restarts. recovery remains as standard miui.
Click to expand...
Click to collapse
What version MIUI version exactly? And what TWRP did you use?
You must install 3.3.1 or Orange Fox otherwise you will brick.
https://forum.xda-developers.com/redmi-6/how-to/clearing-twrp-ambiguity-versions-t3981875

Che0063 said:
What version MIUI version exactly? And what TWRP did you use?
You must install 3.3.1 or Orange Fox otherwise you will brick.
https://forum.xda-developers.com/redmi-6/how-to/clearing-twrp-ambiguity-versions-t3981875
Click to expand...
Click to collapse
cereus_global_images_V10.4.4.0.PCGMIXM_20190927.0000.00_9.0_global_d8716e22a3.tgz
twrp-3.3.1-0-cereus.img
tried orangefox but same symptoms.
before trying with 3.3.1 i had tried with 3.3.0, same symptoms but escaped by reflashing V10.3.6 and it was all fine.

apesgrapes said:
cereus_global_images_V10.4.4.0.PCGMIXM_20190927.0000.00_9.0_global_d8716e22a3.tgz
twrp-3.3.1-0-cereus.img
tried orangefox but same symptoms.
before trying with 3.3.1 i had tried with 3.3.0, same symptoms but escaped by reflashing V10.3.6 and it was all fine.
Click to expand...
Click to collapse
I'm on 10.4.4 too but I used https://mifirm.net/downloadtwrp/62 3.3.1 by LR team.

Che0063 said:
I'm on 10.4.4 too but I used https://mifirm.net/downloadtwrp/62 3.3.1 by LR team.
Click to expand...
Click to collapse
cheers, will give that a try.

Che0063 said:
I'm on 10.4.4 too but I used https://mifirm.net/downloadtwrp/62 3.3.1 by LR team.
Click to expand...
Click to collapse
managed to flash that but can't boot into recovery, holding up doesn't give the corrupted colours, but it eventually vibrates then just boots into system again.

apesgrapes said:
managed to flash that but can't boot into recovery, holding up doesn't give the corrupted colours, but it eventually vibrates then just boots into system again.
Click to expand...
Click to collapse
Do you see the TWRP screen at all? I'm on 10.4.4 Global ROM on 4/64GB China Redmi 6 (unlocked bootloader of course)
1. Flash the recovery as normal
2. enter 'fastboot reboot recovery'. Hold down Vol + when you press Enter on your computer
3. Keep holding down the volume up
4. After a while the TWRP logo will show up. Do not let go of Vol +
5. Within another 5-10 seconds the phone will reboot. Do not let go of Vol +
6. The phone should then boot into TWRP again. On the second reboot into TWRP, you can let go of Vol +

After installing I'm not able to flash magisk successfully
theirs no install error adhere then system encription BS ..
zip gets flashed successfully but no magisk manager installed , after manually installing magisk manager akp, theirs no magisk system component installed
any ideas ?

Glitches instead of TWRP Rec Mode
Hey guys, I have got the same problem.
I had problems rooting the phone with twrp problems, such as: "couldn't mount" and "data encrypted" while doing the wipe format data. And Once I fixed these problems the phone got stuck at boot (not boot loop, it just was in boot for 20+ minutes).
So I flashed the last firmware with miflash. Installed it. The phone worked and I could go in fast boot mode.
But when I installed the twrp, in recovery mode, it just showed glitches with green, red, blue colours. I tried different versions of twrp and also tried to wait 20+ minutes and flash it in the terminal.
Nothing.
The phone is unlocked and I have usb debugging etc... in developers options.
Now I flashed the firmware again but still the same problem. I think that 10.4 may be the problem.
I would love to know if someone has the solution... I'll still try to use older versions of stuff.
that's exactly what I have installed - just to point out:
global image tested: cereus_global_images_V10.4.4.0.PCGMIXM_20190927.0000.00_9.0_global_d8716e22a3
twrp used:
twrp-3.3.1-0-cereus.img 16.6M 2019-05-19 03:42:44 EDT
twrp-3.2.3-2-cereus.img 16.6M 2018-12-26 19:51:21 EST
twrp-3.2.3-0-cereus.img 15.7M 2018-11-13 18:42:11 EST
I am a beginner in the android world so If I say something off, that's the reason why

rooting problems part 2
Guys, I would really appreciate if someone could read this message and tell me what to do, I would be glad to spam him thanks meter.
So I fixed the glitchy things in twrp flashing this: cereus_global_images_V10.3.3.0.OCGMIXM_20190610.0000.00_8.1_global_66306fcb5b
then I had the twrp recovery asking for ? a password?
(not the type "yes" and no the phone password either...).
I tried different twrp and this one didn't ask it: twrp 3.2.3.1cereus
as always I had the problem "couldn't mount data" that I fixed by --- advanced wipe --- data --fat/exfat... But then it gave me the same problem again.... "unable to wipe data" "unable to format or remove encription" and I forgot to write down how I fixed it...
Finally, after all of these problems, I did a format data properly and it worked. I turned off the phone and moved magisk.zip in the "android" folder in the sd card.
I installed it in the twrp and it worked. I rebooted the phone clicking "reboot phone" at the end. It asked for a password (whatever I typed was correct) and it said to me that the data was corrupted and that I had to reset the phone... I clicked reset and now is stuck in the twrp every time I turnoff.
I can access the fastboot mode but this is a loop (I should try another global image and see if it works but the problem is after the twrp process...). I would really appreciate if someone could help me solve this. I'm not pretending, I'm just asking. I respect your time and I hope someone could help. Thanks for reading.

Orange fox e TWR não funcionou na versão 10.4.4
consegui quando fiz um downgrade para 10.3

Same Problem here.
MRedmi 6 cereus
MIUI11
used latest TWRP twrp-3.3.1-0-cereus
I can flash it by using fastboot flash recovery recovery.img
but
'fastboot reboot recovery' doesnt boot the phone into twrp recover. It boots into system
Any solution or this?

Can't Boot Into Revcovery/Download mode

Recently I flashed Los 20.0 Alpha build on my j7elte. Its alpha build so I guessed Ive to face some problems. Suddenly I discover I can't boot into recovery mode using standard advanced reboot option or magisk or terminal emulator even hardware combination. I attempted to flash stock ROM so I tried to boot into download mode but Alas! I can't even boot into download mode also . Please help me

Cyanoge1 said:
Recently I flashed Los 20.0 Alpha build on my j7elte. Its alpha build so I guessed Ive to face some problems. Suddenly I discover I can't boot into recovery mode using standard advanced reboot option or magisk or terminal emulator even hardware combination. I attempted to flash stock ROM so I tried to boot into download mode but Alas! I can't even boot into download mode also . Please help me
Click to expand...
Click to collapse
Are you suggesting that ROM/magisk installation interferes with the bootloader? In my opinion, this is impossible. Just press Power for a long time to make sure you've turned off the power, and run the standard bootloader entry procedure.

ze7zez said:
Are you suggesting that ROM/magisk installation interferes with the bootloader? In my opinion, this is impossible. Just press Power for a long time to make sure you've turned off the power, and run the standard bootloader entry procedure.
Click to expand...
Click to collapse
Its not working .. When I flash this ROM first time everything was working fine I remember I can boot into recovery mode .. This ROM some times crashes and reboots .. It was automatically rebooted into recovery (I saw recovery is not seandroid enforcing in the left top corner of Samsung boot logo) then it reboot back into system without showing up twrp splash screen ..
Is there anything wrong with twrp bcz I flashed latest twrp before flashing the ROM..
I tried several times to boot into download /recovery mode using hardware button but it still reboot back into system

Cyanoge1 said:
Its not working .. When I flash this ROM first time everything was working fine I remember I can boot into recovery mode .. This ROM some times crashes and reboots .. It was automatically rebooted into recovery (I saw recovery is not seandroid enforcing in the left top corner of Samsung boot logo) then it reboot back into system without showing up twrp splash screen ..
Is there anything wrong with twrp bcz I flashed latest twrp before flashing the ROM..
I tried several times to boot into download /recovery mode using hardware button but it still reboot back into system
Click to expand...
Click to collapse
If you can boot the system, then try adb reboot bootloader, and if that doesn't work, then on the system uninstall magisk by restoring the original kernel and then try adb reboot bootloader.

ze7zez said:
If you can boot the system, then try adb reboot bootloader, and if that doesn't work, then on the system uninstall magisk by restoring the original kernel and then try adb reboot bootloader.
Click to expand...
Click to collapse
I've uninstalled magisk

Cyanoge1 said:
I've uninstalled magisk
Click to expand...
Click to collapse
Now I'm pretty scared bcz still I can't reboot into custom recovery or download mode... Using advanced reboot option..