Twrp black screen - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

I have a Xiaomi mi9t pro and my problem is that every time I try to enter inside the recovery mode the phone stays on a black screen (I can restart the phone pressing power button and all works well).
The installed phone rom is MIUI 10.5 by xiaomi.eu 9.8.29 Beta (with 9.0 roms was occurs the same)
The main problem with this issue is that if I want to install any other rom or update the xiaomi.eu I have to reset the factory phone, unlock the bootloader again, do it root, install the recovery (it only works the first time)... bla bla
I have tried several recovery images and with everyone I have the same problem, has the same thing happened to someone? Have you any solution occurs?
thanks in advance!

Try orangefox 10.05

I have the same issues. Only latest mauron twrp working on my Mi 9T Pro. On every other twrp i get a black screen whene change the rom.

aforocars said:
I have a Xiaomi mi9t pro and my problem is that every time I try to enter inside the recovery mode the phone stays on a black screen (I can restart the phone pressing power button and all works well).
The installed phone rom is MIUI 10.5 by xiaomi.eu 9.8.29 Beta (with 9.0 roms was occurs the same)
The main problem with this issue is that if I want to install any other rom or update the xiaomi.eu I have to reset the factory phone, unlock the bootloader again, do it root, install the recovery (it only works the first time)... bla bla
I have tried several recovery images and with everyone I have the same problem, has the same thing happened to someone? Have you any solution occurs?
thanks in advance!
Click to expand...
Click to collapse
It happens if you have had your screen/display folder changed. I have two screens of mi k20 davinci. One screen with ips LCD goes successfully into TWRP and shows it when boot into TWRP but if I connect one other screen which is OLED with fingerprint option {hole (you'll understand if you have hardware knowledge)} then it goes black when boot into TWRP. If you just power on the phone then both screens work normal as it should.

Related

Mi5 in mysterious bootloop (unlocked)

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

Need Some Help . Redmi 4x Bricked !

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

mi note pro bootloop

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.

Question Black screen after boot

Hi everybody!
I recently purchased mi 11, after owning mi 10.
Since recently, a strange thing happens after some time. After using phone for a while, the sound does not work. After restart, the phone goes through boot proces, miui logo shows up, and after that only the black screen appears.
I then would go to the recovery mode, select safe mode or repair mode, and after couple of tries the phone boots normally. Everything else works, it is on global miui, bootloader is not unlocked.
Anybody has any idea why is this happening and is there a solution?
Thanks!

Not able to boot in recovery nor fastboot

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.

Categories

Resources