Related
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Hi..
I don't know exactly what's wrong with your mi5..coz you're already told that you almost tried everything..but as long the problems just softbrick i think there's nothing wrong to try this way that might be you don't try it before..
What twrp version you're using it currently..?, is it official or zcx twrp..?, if official..just try switch to zcx version first..you can find and download it from here.
After that with zcx twrp tried check and see that your partition system, data and cache are still as Ext4 file system not F2fs or you can try formatting the data partition (caution!!..this will deleting all your internal storage) to make sure everything is clear, then put it again the rom.zip then flash it again the rom but this time just try it using xiaomi.eu rom, you can try this rom
And anyway..what version XiaomiFlash tool you're using it while flashing official fastboot rom..?
Xiaomi eu dont support f2fs,i have tried it myself,the last thing to do if you already haven't do in is to flash the firmware in edl mode(i prefer to try Chinese devolep first),i think that way the phone is fully wiped and than flashed just like it came out of factory,other than good luck
wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Hey guys, I will try your suggestions. In the meantime, I attached the dmesg log - it shows the kernel booting. Maybe you see something. It would be cool, if you can upload a dmesg log as well so I can compare or check if you can see anything.
Further information:
- I am using MiFlash 2016.08.30.0
- Tried it with the alternative ZCX version AND the xiaomi.eu ROM
- Formatted the data partition as well (I could create a backup of it with TWRP)
- still same situation...
- Is there a way to reset partitions or kind of "deep flash" the device?
wolkenjaeger said:
Further information:
- I am using MiFlash 2016.08.30.0
- Tried it with the alternative ZCX version AND the xiaomi.eu ROM
- Formatted the data partition as well (I could create a backup of it with TWRP)
- still same situation...
- Is there a way to reset partitions or kind of "deep flash" the device?
Click to expand...
Click to collapse
Did you try to flash in EDL mode ?
vlatko98 said:
Did you try to flash in EDL mode ?
Click to expand...
Click to collapse
Yes. No luck either. Then I tried to flash (via normal fastboot mode) an old STABLE China MIUI ROM: miui_MI5_V7.3.2.0.MAACNDD_905c2c8100_6.0.zip -> resulted in boot -> black screen. Now I can go into either fastboot nor recovery
wolkenjaeger said:
Yes. No luck either. Then I tried to flash (via normal fastboot mode) an old STABLE China MIUI ROM: miui_MI5_V7.3.2.0.MAACNDD_905c2c8100_6.0.zip -> resulted in boot -> black screen. Now I can go into either fastboot nor recovery
Click to expand...
Click to collapse
Idk what to tell you else than to search miui forum and hope for the best
wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Have you got it fix yet ?
Nope. Next step is to try EDL again.
Gesendet von meinem MI 5s mit Tapatalk
wolkenjaeger said:
Nope. Next step is to try EDL again.
Gesendet von meinem MI 5s mit Tapatalk
Click to expand...
Click to collapse
Hav you got it fixed ??? Even i am facing the same issue.
please do let us know if you have fixed it.
Im using mi5 64gb
Exactly the same problem: " (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...)"
But this has happened after serious damage (car rolled over the phone) and I replaced the screen with new one. So I guess some hardware might be damaged. Flashing ROM's didn't help.
I couldn't find any solution so far
After screen replace , you got it working ?
I can't get into recovery also.
I tried many twrp versions , i can see the twrp screen but then it get stuck and phone restarts to go back to that mi logo bootloop.
I did flashed many Chinese and global ROMs via flashboot and miflash tool but all the same.
I'm so doomed...
My phone has no history of any fall or anything ..
I wonder what happened all of a sudden.
Thanks for the reply
wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Okay, have you tried Mi Flash with deep flash cable ? Flash it again with deep flash cable or go to any reseller shop. They have deep flash cable. Ask them to flash it again. It'd cost you upto $10.
I retried yesterday - no success.
I flashed both stable versions: Global and Chinese, but after flashing, I again had the same problem: bootloop. I stop wasting time, until someone knows the problem. I personally think it's a problem with the hardware, as when you see the log, which I posted above (kernel log of TWRP), there are quite a lot of "errors" in it.
Any other idea?
I asked an android expert who worked in mi about it ...
He was almost sure that either battery or the motherboard is faulty.
He thinks the motherboard is of more chance for the issue.
Bummer..... then I have to wait until I get back to Hong Kong to repair (bought it there). Thanks for the update @bilalsmu.
wolkenjaeger said:
Bummer..... then I have to wait until I get back to Hong Kong to repair (bought it there). Thanks for the update @bilalsmu.
Click to expand...
Click to collapse
Your welcome...
Can you just try flashing with mi flash tool with the option 'clean all and lock'
I just tried mine, and now android is loading *fingers crossed*
Will update if it did complete..
Okay, can you tell me which MiFlash version you have been using (and which ROM?)
I am sorry brother.
Android booted up,I could log into my accounts and I left the phone for charge while it was syncing the accounts ..
When I am back after half an hour , bootloop had already started
I used miflashtool 2016 and miui 8.2.1 official global rom
Hello!
I have a Xiaomi Mi 5 Pro running Global 7.2.8.0.0 Stable. I wanted to unlock my bootloader to install a custom rom.
The sms with unlock permission pin from xiaomi support was already on my device.
My actual rom had no oppurtunity to link the phone with my xiaomi account. So i tried to do a system-update.
That's when i noticed that my phone seems to be on a shop-rom and that i need a deep flash cable to get rid of it.
Because my phone felt a little laggy to me, i decited to do a factory reset. And then the bad supprise happened.
It hangs in a bootloop, showing the recovery image (white phone with cable on black ground).
When i hold volume down, i'm still able to boot into fastboot.
I've ordered a deep flash cable, but it can take 30 days to arrive.
Can somebody help me out? I'm grateful for any hint or help!
best regards
If u are able to boot in to fastboot is it miflash working
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
If you dont want to see all my story, go down 2 see the base of my problem and second question.
Hello, i recently bought this phone in last week, used, for fifty euros and it had 32.3.A.2.33 firmware, and please remember WHITE boot screen.
It havent bootloader unlocked.
For some hours of using, it runs fine, except display, seems to be changed by amateur person, sometimes bad touch sensitivity, but i turned on glove mode and no problem. No lags, camera working, every thing - no problem so far.
And then problem began - after restart for sim change, phone boot animation was very slow, and some display flickering. When it booted, system was very slow, display had very slow reactions, i thinked it was GPU or software problem. After some minutes it itself rebooted, 2 red blinks and then booted very fast.
I tried some restarts, 2 of 5 was this problem.
I tried unlock bootloader, and install TWRP, because i think this isnt GPU problem, if 3 times booted and works flawlessly for HOURS !
Okay, bootloader unlocked, twrp installed, i searching for some roms, but phone have very bad community on XDA, i downloaded 3 roms:
AOSCP 3.5.1 - works flawlessly, no display flickering or something, some bugs like camera with bad quality photos, but after restarts, no display flickering or lag and this is important. But no boot screen (pure black boot screen)
Ressurection Remix 5.8.5 - Android 7.1 - after restart it HAD flickering and lag, something similar like first stock rom, 2 of 5 boots... Not very bad but yes. Very good rom.
LineageOS 14.1 - EVERY BOOT HAD THIS PROBLEM. LAGS, DISPLAY FLICKERING, RESTART AND 2 RED BLINKS.
So i installed again AOSCP 3.5.1 and no problem, only camera.
My not intelligent head was a plan - i prove a downgrade. To 28.0.A.4.8 - stock android 5.0.2. Phone gets black boot screen, and EVERY boot had this problem. Lags, scuttering, flickering... But it booted. I try restart, but no difference. 5 of 5 boots had this problem.
I have installed again nougat rom but not like first, but 32.4.A.1.54. After start flashing with flashtool - report an error with boot_delivery.xml - so i checked exclude bootbundle - no problem with flash. Restarted.
Phone had a BLACK BOOT SCREEN - i looking, because nougat sony roms has a white boot screen.
First boot without Sim card - no lags anytime. It has restarted itself, because i wanted to add sim card.
After reboot, every reboot had this problem.
I tried flash with fastboot twrp like first - https://forum.xda-developers.com/xperia-z4/development/twrp-twrp-3-1-1-z3-z4-t3862684
After fastboot reboot - phone has 2 red blinks and not turning on. I put cable out and i trying to turn on it, but it only vibrates 3 times and nothing. Boot or something, i thinked it is dead, but FOR TODAY im able to get into flash mode and bootloader.
I skip some 5 days with trying with flashtool LP, MM and NOUGAT roms, FLASHING TWRP, Sony companion is unusable, because i unlocked bootloader... My phone (or fifty euros) is in holy phucking s+++ in 2 days of using.
Okay, only twrp what i can boot normally is 2.8.7.0 recovery by old 5.0.2 android Z-ROM https://forum.xda-developers.com/xperia-z4/development/zrom-custom-rom-z3-e6553-28-0-8-251-t3206005
For questions, i tried both this stock firmware and custom rom, rare thing is boot normally, but after restart, no difference.
I tried flash again first stock rom 32.3.A.2.33, no difference, but BLACK BOOT SCREEN aside of white.
One but only one different 3.0.0.0 twrp what im able to flash, only into FOTAKernel or RECOVERY not boot partition, because RED blinks and nothing, but this twrp is from sumire (z5):
https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050.
I founded this argument by flashing and aoscp rom and error: This is for (ivy), your device is sumire.
I think i can change update_script - there i changed every ivy to sumire.
Installed with this twrp flawlessly, flashed magisk, reboot.
Again Red blinks...
Now what im able FUNCTIONAL only - flash 2.8.7.0 (too with display flickering and , but this twrp is ONLY for install Z-ROM, other roms like aoscp and RR i cant install because error E1004: cannot install system boot image.
And other twrps i can flash only to boot (kernel) partition, but red blinks or boot again into this 2.8.7.0 recovery.
I am making with Sony, and i had in the hands SO MANY phones , so many from them for repair, from different brands for 7 years, no problem with flashing so far (i thinked i am unstoppable :victory: ), and this is my 2nd phuckedup phone for whole 7 years (first was LG G6) and i wanna help, because i have working flash and bootloader, but i havent an idea what next, because some (80 percent) threads havent functional download links for NO SUPPORT or something, but this is absurd. Like my issue, but this is real. For example: i have Xperia SP for 6 years, with stable recently updated (30.9) LOS 15.1 and Xperia S (recent nAOSP 8.1) for 7 years, flashed anything, anything, anything... Downgraded, upgraded... And no problem for today. Reliable phones as... SP is my primary phone (for 6 years) and S for testing. I wanted something from sony but more performance - functional for 2 days. And karma is here - in xda.
Recently i put it into wall charger, it booted into that 2.8.7.0 recovery and it had 94° and it still breaths ! And really it was very hot ! Normally it had less than 60°.
If i flash through fastboot mentioned newer twrp 3.1.1, 3.0.2, 3.2.3 or other mentioned, what non-functioning there, after that red led blinks, it will go to (green) flash mode.
The main problem is: I am able to go into flashmode and fastboot, i can boot system, but (now) i am able to flash only one old recovery, where i CANT install and boot for example aoscp rom or other rom without problems (black screen, then red blinks, then green flash mode). Original software - lags, display scuttering, graphic artifacts but rare thing is going flawlessly, so i think isnt gpu problem. I need real help. I need this phone and i think it can be recovered. I can send anything from this phone (logs or videos), what would be helpful.
After factory reset + system format, in that old recovery, i have in internal storage (sdcard) folder with name 0. Everything cleaned, but this folder remains.
So there is second question, someone experienced with this issue ?
Problem with aoscp fixed. Very luckely, but no problem now !
I had an version of flashtool, 0.9.18.6, maybe i havent problems, because i had older phones from sony (my fault) and newer versions i have experience, cant found .ftf with older firmware.
An error, what i had in older flashtool when i trying to flash both nougat and marshmallow roms - entry (0000084F)parsing error boot_delivery, which means an program for boot.
I doing an very bad thing - check exclude bootbundle and flash was without errors, but this is reason, why i havent an white screen in nougat and marshmallow and amount of recoveries i cant flash so i cant flash an rom.
What i do is install an 0.9.23.1 version of flashtool (because i have an x86 notebook and today versions dont support x86, only x64)
Downloaded orange PL 32.2.a.5.11 (marshmallow official stock rom) from XperiFirm and it flashed bootbundle without problems !
I restarted it - WHITE BOOT SCREEN and HOORAY ! But lags, display scuttering and things, what i writed here, was here, also after itself restart - 3 red blinks. So after 3rd reboot i take cable, plugged in with volume +, fastboot flash boot 3.1.1.0 recovery and it worked.
Flashed AOSCP, magisk and booted without problems, no lags, no display scuttering and etc.
I am very glad i fix my problem, but an question still, why in official firmware or some custom roms (except AOSCP) i had this problems with lags, graphic artifacts, scuttering and reboot in random time with 3 red blinks ? On EVERY official firmware
Hint for you
If you have problem like me, every custom rom making problems, use boot image from aoscp https://androidfilehost.com/?w=files&flid=143620
I am not maintainer of this rom, i want only help others, if your device lags or graphic issues.
Maybe you get bootloop, but with this boot image i havent experienced after every reboot any problem with mentioned lags or again flashing twrp.
Still question for E6553
I tried almost all roms for this device and every other roms have problem with mentioned.
After flash and restart, every boot have problem with display flickering, lags and very, very slow reactions.
Even with every official firmware.
AOSCP is ONLY FUNCTIONAL SYSTEM FOR MY DEVICE ! But it have some bugs, like automatic brightness, bluetooth turning off, nfc not working, accelerometer or little bit heat and idle battery drain (it is fixed by GlassCanon LXT magisk mod) or screen does not turn off when i call, but never this boot problem.
One thing what i see, aoscp havent boot logo from sony and when i get out boot.img from this rom and put it into other custom roms (like LineageOS 14.1, crDroid or RR) and reboot it, no lags, no display flickering, pretty fast boot animation, but bootloop, so this boot.img is proprietary.
I tried from androidfilehost download aosp ota, but error 7 in twrp and when i change this in updater-script, then error 6.
Next what i tried from aosp - fastboot flash system.img - and i cant install it, because this file is big - around 1.2gb.
I am in corner with this phone and i wanna help, what more i should do for stable system or fix bugs in this rom.
Thanks
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.