Hi there!
I'm stuck in a bootloop with dm verity error message. Phone turns off and on continiously. I'm not able to get into recovery / fastboot using button combo :\.
How I got into this:
I tried unlocking my merlinx, but ... didn't want to wait 7 days with the official tool. So I used https://github.com/bkerler/mtkclient and did the "unlock bootloader" procedure. Phone booted fine, though there was dm verity error message and I had to press the power button to continue booting.
Then I followed this guide: https://forum.xda-developers.com/t/...roid-for-redmi-note-9-merlin-merlinx.4333179/
Then, I downloaded shrp recovery, crDroid rom, gapps and firmware. Booted in fastboot, did `fastboot flash recovery shrp.img` and booted to recovery. Then I took backup of IMEI, wiped the data and saw an interesting builtin zip for dm verity disabling. Flashed that, then proceeded with custom rom installation. All went smooth.
I booted the rom. There was no dm verity message, nor Redmi logo, but phone booted normally. If I remember correctly, I didn't have to press the power button to continue (there was no message about it.)
Proceeded with phone setup. Camera didn't work ... Tried rebooting, once again no Redmi logo but phone boots fine. "Ok then, I'll try a different ROM and hopefully camera works". I choose "advanced restart -> recovery" and phone turned off. Screen turned on (like you'd expect) but then turned off again. Again, no Redmi logo or dm verity message.
And now the phone does that. Screen turns on and off after ~30 seconds.
My first thought was that bootloader got locked again somehow. Using the mtkclient tool, linked above, I relocked and unlocked the bootloader.
There's still no Redmi logo present, though I can see the dm verity message again.
What have I done wrong? I know it could be the impatience with 7 day waiting, but since phone booted fine 2 times ..? Was it the recovery dm verity zip?
Does anyone know what to do here? I'm able to use mtkclient tool. Button combos for recovery and fastboot seem unresponsive ...
Thank you very much.
Hello.
I did exactly same think with my Redmi Note 9 and I can say you hard bricked your phone. But don't worry there is a way to solve it. You need to follow vagelis199's guide exactly and there should be no worries. It is not so easy but not so hard too.
Sending this from my Redmi Note 9 with android 12 R vendor.
I'm not so knowledgeable about this part of tech but crDroid guide is outdated in my opinion and it should be replaced with new one, that is a big problem and should be considered. I installed Android 12 S vendor, most recent one from my android 11 MIUI and it bootlooped, after installing with Firmware of Global MIUI it was hardbricked. So I am waiting a little and trying to install most resent crDroid with EU MIUI Firmware which very recently was published with MIUI 13 Android 12 EU. I am not sure why it didn't work because EU and Global are very similar.
Thank you, will try that.
Related
SOLUTION: Turns out I was still able to boot into eRecovery. From there I could reboot normally into the system. I then went into fastboot and flashed Blackball's TWRP 3.2.1-0 build for Oreo. Everything boots smoothly now.
Hello,
today I decided to try and flash the ResurrectionRemix-GSI to my Huawei P10 (EMUI 8.0) which was successful at first. I unlocked the bootloader, flashed TWRP via fastboot (First Link to TWRP in this thread). From TWRP I did a complete backup and wipe and installed ResurrectionRemix (ARM64 A-only from this thread). The system booted up just fine and everything seemed to work like a charm. I then went on to boot into recovery again, because I wanted to install the pico package from OpenGApps.
The problem now is that I'm stuck on the splash screen of TWRP. When I try to turn off the phone by holing the power button, it just reboots to recovery, which greets me with the everlasting splash screen. I have also tried rebooting the phone via adb -> same result. And to make it even better: When I try to get into fastboot mode via "adb reboot bootloader", I get thrown back into recovery as well.
My current "strategy" is to just drain the battery and hope for the best (well... I can't even turn the phone off anyway). I've read that other people have waited up to 6 min for TWRP's splash screen to dissapear. I'm waiting for roughly an hour now, so I'm pretty positive, that it's stuck.
Hope someone can help.
UPDATE: The battery has drained now. When I connected the phone to its charger, it went straight into recovery and is stuck again. Fastboot still doesn't work.
Huawei phones do not seem to go along very well with TWRP for installing GSIs. The original recovery is required to do a factory reset, before you can boot into system. Can you reboot in fastboot mode? If yes I would flash the original recovery and system from fastboot. It is clearly explained on the Openkirin.net website. I can also recommend flashing one of their GSIs, since they include the Huawei camera and nano Gapps.
M1chiel said:
Huawei phones do not seem to go along very well with TWRP for installing GSIs. The original recovery is required to do a factory reset, before you can boot into system. Can you reboot in fastboot mode? If yes I would flash the original recovery and system from fastboot. It is clearly explained on the Openkirin.net website. I can also recommend flashing one of their GSIs, since they include the Huawei camera and nano Gapps.
Click to expand...
Click to collapse
No, I can't boot into fastboot mode, at least not via adb (only method I know of). When I run "adb reboot bootloader" it just throws me back into recovery mode with the splash-screen stuck.
I have a redmi 4x and i tried flashing pixel experience rom on it but was not successful in doing that . Also didn't take any backup . And i was struck in the twrp recovery for a couple of days . Then i flashed the miui stble rom through my sd card and didn't get any error . But when i was going to boot it said "No OS installed" . So i thought of having a backup before booting for the first time and as i tried having a backup then phone switched off and showed no signs that it was working . It didnt even boot and was bricked . So i thought it was hard bricked . But after a day and some charging the notifictaion light light started working on charing and also phone vibrated on pressing down the power button . But when i try to boot it the phone shows some backlight but nothing on the screen and it goes off . Is it Hard Bricked or Soft Bricked ?
Bhagyesh2491 said:
I have a redmi 4x and..........
Click to expand...
Click to collapse
I don't have this device but, you may be able to obtain some member guidance within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3800104
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
Showing "No OS installed" it did happened with me when few months back i flashed first Global beta MIUI 10, the installation went perfectly good with message "No OS installed" it was strange when flashing was went right.
after rebooting it to system it was stuck in bootlogo. i do not know why it said "No OS installed" despite installation went perfect.
at first i did checked if system is checked for boot or not in recovery(it was not) so i checked it and rebooted but it still refused to boot and keep getting stuck in bootlogo but after flashing latest Redwolf treble recovery at that time solved issue for me(currently using redwolf recovery) and i was able to boot into system and later other ROMs.
anyways this solution worked for me "No OS installed". (writing this because it might help someone if they have same issue)
what is current state of your device? are you able boot in fastboot or recovery ? if any one of this works i would recommend you to flash if you are able boot into fastboot then flash latest stable Global MIUI ROM via Mi flash tools or flash latest treble supported recovery via fastboot.
if it isn't booting at all or it refused boot into any mode you might have to go for test point method to revive your device as you can see in above mentioned comment by xda recognized contributor's thread you can find test point method is mentioned by OP or here is link for it http://en.miui.com/thread-693884-1-1.html
you can also find video for the same on youtube.
proceed with precaution.
No it isn't booting at all . It is detected by my PC as a Battery but it shows it is android . Also notification light turns on after trying to charge it and it also vibrates . When i hold down the power button its shows some kind of a backlight but it doesnt boot . Is it hard bricked or soft bricked ?
Bhagyesh2491 said:
No it isn't booting at all . It is detected by my PC as a Battery but it shows it is android . Also notification light turns on after trying to charge it and it also vibrates . When i hold down the power button its shows some kind of a backlight but it doesnt boot . Is it hard bricked or soft bricked ?
Click to expand...
Click to collapse
I am not sure if it is hard bricked or soft bricked.
It detects on computer and doesn't shows anything on display.
Try connecting to PC and see if detects on Mi flash tools if it does then flash latest stable ROM through it.
Try using mi flash tool. This happened to me too, tried flashing pixel experience pie on mine and bricked it. Couldn't even access the twrp and my phone was stuck on fastboot screen. Luckily I had mi flashing tool and knew how to flash official MIUI rom through it. I did a clean flash of MIUI rom and it pretty much reverted the phone back to original conditions but few hours later i re installed twrp and went back to pixel exp OREO.
Do we get a ota update from pixel experience oreo to pixel experience pie rom ?
Have you tried to boot into the fastboot mode?
if yes then flash miui stable rom via mi flash tool
Carefully Read instruction bro :----
PC required windows 8 or Up..
1-Firstly installed Adb
2.twrp installer for redmi 4x zip
3-Extract all file in zip
4-Click .bat file and follow instruction of command window
5-twrp successfully installed in your device automatic device boot in recovery mode
6-Sd card inserted do you want flash ROM by TWRP
7- FLASH do you want any thing ..
8- Lazy Flasher is Compulsory flash
9 - enjoyed ROM without Bug
Hello,
I have a bootloop on my mi note pro.
I deleted everything, wiped after that i flashed room 6.1.7 china stable and phone dosent start.
I flashed many other rooms and xiaomi still gets into recovery, its going recovery all the time if i turn on.
I can enter into fastboot there is no problem, i was flashing by oem edl, bootloader is unlocked, my pc dosent recognize device as mass storage so i cannot put any rom to it.
Well after new room flashed the xiaomi stays on logo and after 1h there is nothing more, still logo.
In recovery i can move only down by vol- i cannot move up thats normal or i had broken button?
I was trying to dismount buttons and then start my phone and i get same result... recovery.
I was trying to flash 3 other twrp, same thing.
Maybe i doing something wrong, dont know. Please help me.
So I have a K20 Pro from China that came with bootloader unlocked and a 'global rom'. I installed TWRP 3.3.1-13 and installed Xiaomi.EU and worked fine for some days. Today I rebooted to recovery from the power menu and in TWRP it asked for a password and I entered it then it started decrypting data and I just rebooted system and it's now stuck in a bootloop in Redmi logo and after a while it just reboots back to TWRP and asks for the password. How can I fix this?
Thanks in advance
I tried reinstalling XiaomiEU ROM but now it says there's no OS installed. It gets stuck in the Powered by Android screen and then after a while goes back to TWRP. What should I do?
Isley_ said:
I tried reinstalling XiaomiEU ROM but now it says there's no OS installed. It gets stuck in the Powered by Android screen and then after a while goes back to TWRP. What should I do?
Click to expand...
Click to collapse
Try formatting data (where you type yes)
Hello everyone, my phone (Redmi Note 9 merlin) has started bootlooping. It can boot to fastboot, but is unable to boot to recovery (either through fastboot reboot recovery or Vol + during boot). I have tried using SP Flash Tool using the hard brick tutorial and it still bootloops even though all steps proceed normally. I have tried to flash both old and new versions of MIUI, and all of them stlil do not work.
My bootloader is still locked so I am unable to use fastboot or other tools (like MiFlashBoot) on it.
Trying to unlock it from Mi Unlock gives me an error (1004). It seems to be due to the SIM card not being the same but I have not touched the SIM card since I got the phone.
In the past I have used MiPhoneAssistant to restore it as I could access recovery mode, but now even recovery mode is out of my reach.
What should I do now?
Thanks for your time.
Do you know what could cause the boot looping? The most common one is after installing a new version of MIUI.
I'm not sure how it happened, but if it is caused by a MIUI update, how would I go about fixing it?
If it has a locked bootloader and it's still in a warranty. Visit the store where you bought it from and claim the phone has stopped working and started bootlooping.