Need help. Phone won't go into recovery - Redmi Note 9 Questions & Answers

so after updating to miui 13 (13.0.2.0 SJOMIXM), first off my google sans magisk module doesn't seem to be working anymore, and I could go into stock xiaomi recovery, but after I flashed SHRP and tried to go into recovery it just went to a black screen and then went back to the Mi splash screen
so this is how it goes: *normal bootup screen* -> *black screen for a sec* -> *normal bootup screen and boots into miui*
idk what to do, and the only rom available for 13.0.2.0 is a recovery rom so it doesn't include the stock recovery.img, so I cant revert to that (unless the 12.5.4.0 recovery is safe to install).

also does anyone know how to bring back the gaussian blur?

SymtaxError said:
also does anyone know how to bring back the gaussian blur?
Click to expand...
Click to collapse
SymtaxError said:
so after updating to miui 13 (13.0.2.0 SJOMIXM), first off my google sans magisk module doesn't seem to be working anymore, and I could go into stock xiaomi recovery, but after I flashed SHRP and tried to go into recovery it just went to a black screen and then went back to the Mi splash screen
so this is how it goes: *normal bootup screen* -> *black screen for a sec* -> *normal bootup screen and boots into miui*
idk what to do, and the only rom available for 13.0.2.0 is a recovery rom so it doesn't include the stock recovery.img, so I cant revert to that (unless the 12.5.4.0 recovery is safe to install).
Click to expand...
Click to collapse
try to flash the boot.img file

casdeltha104 said:
try to flash the boot.img file
Click to expand...
Click to collapse
sorry for being late, wouldn't that remove root?

Yes, but it solves the bootloop

Related

Stuck at boot screen after twrp install MIUI 9

the problem im having is after upgrading to the latest 9.2.3 firmware when i try to install TWRP everything goes fine but the phone refuses to go past boot screen. I i can boot into TWRP with no problem at all but if i try booting the phone it just gets stuck at the boot logo.. So then i reverted back to the 9.1.1 firmware and now the problem has started there as well. anyone have any idea what im doing wrong?
PS: iv used 3.0.3, 3.1.1 and 3.2.1 none work
Hey after flashing TWRP your supposed to flash lazyflasher.zip if your running MIUI or you'll be stuck at the MI logo. This is a completely normal problem, nothing to worry about. Boot into TWRP and flash the lazyfalsher zip and your MIUI will be up and running. You can download it here
Bro after flashing twrp. Go inside twrp, options/settings, advanced, click on fix boot/disable verification something like that. Thats all It will boot.
hey thank man i just followed what you said and its working fine now
hey thanks for the reply i got it working
Glad it worked. Happy flashing!

miui 11 beta TWRP problem /help

hi guys i normal install this beta miui 11 version 9.926 via TWRP .
after that i click on settings on phone and go to recovery but i see that there is miui recovery 3.0 so it delete twrp
then i normal install back TWRP and only click only restart system or i need click or check another settings ??
but after that phone not boot anymore i dont know why
could y help me how install back twrp and use miui11 beta
thx for help
tubabuyukustun said:
hi guys i normal install this beta miui 11 version 9.926 via TWRP .
after that i click on settings on phone and go to recovery but i see that there is miui recovery 3.0 so it delete twrp
then i normal install back TWRP and only click only restart system or i need click or check another settings ??
but after that phone not boot anymore i dont know why
could y help me how install back twrp and use miui11 beta
thx for help
Click to expand...
Click to collapse
Alright so, to properly install twrp I noticed, you have to boot twrp through adb by going to fastboot and typing the command "fastboot boot recovery.img(or however you have named the twrp file you downloaded)" Your phone will boot into twrp. After that,you need through there to flash magisk or generally the root you prefer. Once you've done that boot into your phone,download the twrp app and flash twrp through there. If your phone is not booting for some reason you might have installed an incompatible image or something.If the phone doesn't boot at all and you can't enter twrp, boot twrp using the method I said earlier and restore a backup you have made, then do the process I told you by installing the app and flashing it, and then continue trying to install a ROM. Always be sure that twrp is working perfectly before flashing ROMs.

stuck on "MI"

I'm on twrp and I can't install any aosp rom anymore. format "yes", install fw 0.9.0. start with the flash seems to be all right, reboot system and get stuck on MI and nothing happens, try again with another rom and it is the same. I returned to the initial state with XiaomiFlash, I install twrp, I redo all the procedures and start again as before. any idea about it?
if i install a rom xiaomi.eu with twrp the phone works, if i install a rom always with different twrp inside it does not install anything. It had never happened to me, the problem appeared after I tried xiaomi.eu 12 how do you suggest me to proceed?
baggino said:
I'm on twrp and I can't install any aosp rom anymore.
Click to expand...
Click to collapse
Unfortunately you're not very clear with what you did. So I only can assume that you probably didn't flash vbmeta.
Cheers
Toscha
thanks tosca, I don't know how but I had used the wrong firmware ..., now all solved

Stock boot.img is not booting on boot_b

Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
Code:
fastboot oem unlock
Code:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
Code:
fastboot flash boot_b twrp-3.4.0-0-jasmine_sprout.img
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via
Code:
fastboot flash boot_b jasmine_global_images_V11.0.12.0.QDIMIXM_10.0/images/boot.img
(my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
floydsen said:
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via (my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
Click to expand...
Click to collapse
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
Code:
fastboot boot TWRP-3.4.0-0-jasmine_sprout-for_V11.0.12.0.img
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
floydsen said:
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
Click to expand...
Click to collapse
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
also the name of that looks like one hell of a job ..shorten it to
recovery.img or twrp.img
fastboot boot recovery.img
but first run
fastboot getvar all
& also run fastboot flashing unlock_critical
but most importantly get another recovery
& i don't want to insult your intelligence but after flashing stock did you check to make sure bootloader was still unlocked and that dev settings was activated and that adb was toggled to on and that you authorised adb again
basicall after stock boot device and do the above ..plug in usb ..toggle adb ..authorise ..run adb devices ..if you see your device ..adb reboot bootloader ..fastboot devices ..see your device ..fastboot getvar all ..see bootloader is unlocked ..fastboot flashing unlock_critical if not done yet ...make sure to do ALL the above again after data gets wiped.....put twrp in adb folder ( MUST BE UNOFFICIAL RUSSIAN OR MODUFIED BY NEBRASSY ..rename to revovery.img ...fastboot boot recovery.img .. use file manager to put magisk.zip on internal then flash ..then reboot to rooted phone with stock recovery ...
Sent from my wayne using XDA Labs
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
KevMetal said:
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
floydsen said:
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
Click to expand...
Click to collapse
jajaja well now you know ...be careful ...some "official" roms are also more buggy than unofficial ones for Jasmine/Wayne..
LOS is an example ..so be forewarned .. if you like android 1 i guess stock rooted is a smart option to keep updates and keep device certified for google stuffs . .
alternativeky go FULL custom rom because stock and custom recovery is just a pain and not worth the hassle on an A/B treble device flashable by fastboot ..just boot the recovery when if ever needed
fyi ..you can flash magisk and it will boot ...if you don't try changing the recovery ..so you can have stock rooted with magisk without rcustom recovery...* recommended by me if you only wamt stock with root
Sent from my wayne using XDA Labs
All good now, thanks for your help! I just flashed Magisk (and also TWRP) and everything works nicely! I will need to get some experience, but I'll keep in mind that I maybe want to get rid of the TWRP recovery. Finally security testing is fun again. Thx!

Evolution x problem

So i installed/flashed evolution x rom OSS vendor using orangefox (unchecked the unmount system thingy)without any error
my phone is decrypted so first thing i did is
wipe the cache,data,system,vendor,dalvik/art cache then
Add the evo x rom to queue then next is the DFE.zip then after succesfully flashed i reboot to system it worked and played for hours then I was planning to install magisk and pressed the reboot to recovery then the problem begun always stuck at fastboot wont boot to recovery cant even shutdown the phone always starts at fastboot.
whats the problem? or did I do anything wrong??
right now im using stock rom again but i want to use custom rom.
Mi 9t pro global latest update.
I had the same problem with other ROM. Even after flashing recovery once again my phone couldn't exit fastboot. The cause could be a damaged boot partition, but I'm not 100% certain.
hash8bits said:
So i installed/flashed evolution x rom OSS vendor using orangefox (unchecked the unmount system thingy)without any error
my phone is decrypted so first thing i did is
wipe the cache,data,system,vendor,dalvik/art cache then
Add the evo x rom to queue then next is the DFE.zip then after succesfully flashed i reboot to system it worked and played for hours then I was planning to install magisk and pressed the reboot to recovery then the problem begun always stuck at fastboot wont boot to recovery cant even shutdown the phone always starts at fastboot.
whats the problem? or did I do anything wrong??
right now im using stock rom again but i want to use custom rom.
Mi 9t pro global latest update.
Click to expand...
Click to collapse
Fast Boot Issue solved. Only tested on K20 pro
Run this you will get your twrp back by pressing vol + while booting and Boot into recovery system also working fine
fastboot flash dtbo dtbo.img
dtbo file attached below
I have problem with fingerprint.
When I use in full screen brightness its work perfectly, but when my screen on low brightness fingerprint don't recognise.
Pls help.
K20 pro
Evolution x
hash8bits said:
So i installed/flashed evolution x rom OSS vendor using orangefox (unchecked the unmount system thingy)without any error
my phone is decrypted so first thing i did is
wipe the cache,data,system,vendor,dalvik/art cache then
Add the evo x rom to queue then next is the DFE.zip then after succesfully flashed i reboot to system it worked and played for hours then I was planning to install magisk and pressed the reboot to recovery then the problem begun always stuck at fastboot wont boot to recovery cant even shutdown the phone always starts at fastboot.
whats the problem? or did I do anything wrong??
right now im using stock rom again but i want to use custom rom.
Mi 9t pro global latest update.
Click to expand...
Click to collapse
i have the exact problem, just i used twrp (3.5.2_9-0-raphael-1)
flashing dtbo doesnt do anything :/
how can I get out of bootloop? stuck at fastboot...
thank you so much
oriped said:
i have the exact problem, just i used twrp (3.5.2_9-0-raphael-1)
flashing dtbo doesnt do anything :/
how can I get out of bootloop? stuck at fastboot...
thank you so much
Click to expand...
Click to collapse
flashed the latest fastboot version from https://xiaomifirmwareupdater.com/miui/raphael to bring the phone back to life.
same problem? repeat after me:
choose a fastboot version, click download and then scroll down to the fastboot version (.tgz file type, don't get confused as the first download button is recovery version again...). extract and copy to minimal adb & fastboot. run "flash_all.bat".
phone starts with miui
softbrick, soft brick mi9 t pro, fastboot, flash stock rom, bootloop fastboot, Redmi K20 Pro, Raphael
still wondering what caused that bootloop...

Categories

Resources