Mi3 flash problem. - Mi 3 Q&A, Help & Troubleshooting

Hi, I am trying to flash my MI3 using the flash tool. The flashing process is stuck and not going ahead from $fastboot -s 13a2d60 erase DDR. I have the screen shot for the same. Please some one post some help....need it very urgently. I donno how to post the screen shot.
Regards
Hari Kumar Iyer

Take a screenshot using windows key + print screen button. I'll try ....

My phone doesn't stays in fastboot mode for even 20 sec
It was not like this before unable to install any recovery or rom

Related

Unbrick BIOS-Softbrick on X98 Air m5c5 withouth EEPROM Flasher - courtesy of ionioni

Good evening gents,
Since I broke my BIOS on my m5c5 by flashing the wrong one with Tecknights Tutorial, I was desperately trying to get back to the working BIOS.
Thanks to ionioni we have a way to unbrick our devices (as long as they still boot into dnx).
I accidentally flashed the wrong BIOS on to my X98 Air iii (m5c5) and thought i bricked it beyond repair (except opening it up and flashing it with EEPROM Clip).
Now we have a solution to flash the DUAL BOOT - BIOS to the m5c5 through dnx mode:
WARNING: EVERYTHING YOU DO, YOU DO AT YOUR OWN RISK! Only tested on m5c5! Using it on other devices can HARDBRICK!!!
IMPORTANT: DO NOT CUT THE USB OR POWER AND WATCH OUT THAT THERE IS ENOUGH POWER IN THE ACCU.
1. Copy the following files into your fastboot directory on your pc:
https://anonfiles.com/file/28e5e4990eee25d74ff4d6cc99fdb548
2. Boot the device into dnx/fastboot (pressing power and Vol+/Vol- at the same time)
3. Plug the device in via usb, open up a command prompt in your fastboot directory and type the following:
fastboot devices #Check if device is recognized
fastboot flash osloader efilinux.efi #Push Efiloader onto device
fastboot boot bios_restore_m5c5.img #restores the dual boot bios
4. Wait for reboot. There is now a 100 second timer in case of second guesses and afterwards update notifications during the flash. It takes between 3-5 Minutes. DO NOT FORCE REBOOT it WILL HARDBRICK
Be happy to have unbricked your BIOS. And thank ionioni !! PM him if you have any questions!
Fastboot boot --> that instruction not flashing anyting only booting partition to ram .
What is doing that img ? I'm curious .
mirek190 said:
Fastboot boot --> that instruction not flashing anyting only booting partition to ram .
What is doing that img ? I'm curious .
Click to expand...
Click to collapse
it flashes the bios @mirco446 gave me (also asked him and sent me the droidboot.img from the stock)
i used the droidboot.img sent as a base and modified it (included in it the bios sent together with the intel FPT binary for writing a bios file) and it just boots and runs when boot is completed the binary to flash the bios file (this is why one should NOT reset or power off the device after it enters the fastboot boot command as this could result in a partially written bios and this translates to HARD-BRICK). at the end it reboots to load the new bios
normally should also output some messages but for some reason it doesnt capture the framebuffer device and since i don't own the device i cannot 'debug' to check on why... but this is only a minor issue (not having status messages), so one just needs to wait a few minutes until the device reboots confirming that the bios was wrote.
nothing fancy
Interesting ... thanks for explanation .
And he did it for C5J8 too, mine is alive too.
hello i have the same problem with my m5c5 but it don't work for me.
i have this message:
entering dnx mode.
waiting for fastboot command.... efilinux [ 0.000449] ERROR[get_parth:334] couldn't find boot device handle.
Good drivers?
i use driver from TecKnight's Teclast Tutorials series.
i try under linux and same problem.
[email protected] ~/Téléchargements $ sudo fastboot devices
Baytrail02D31E57 fastboot
[email protected] ~/Téléchargements $ sudo fastboot flash osloader efilinux.efi
sending 'osloader' (2463 KB)...
OKAY [ 0.109s]
writing 'osloader'...
OKAY [ 0.008s]
finished. total time: 0.117s
[email protected] ~/Téléchargements $ sudo fastboot boot restore_bios_m5c5.img
downloading 'boot.img'...
OKAY [ 0.791s]
booting...
OKAY [ 0.003s]
finished. total time: 0.794s
tablet wait ~30s and restart on red logo and bootloop.
i upload my original bios but not dual boot:
https://drive.google.com/open?id=0B_A8FEPnUL61WHQ4RzAxOXpzZGM
edit: problem solved for me thank you ionioni!!!!!
bosondehiggs said:
i upload my original bios but not dual boot:
https://drive.google.com/open?id=0B_A8FEPnUL61WHQ4RzAxOXpzZGM
Click to expand...
Click to collapse
i won't invest anymore time in this. already tried this below stuff... not working
seems that it doesn't boot the image at all, this could be due to an existing IA32 bios (post a link to the bios you flashed so i can check)
until then...
you can try again and skip the first 'fastboot flash osloader efilinux.efi' if it still doesn't work replace the efilinux.efi file with one from a x86 older rom
no matter what wait until the tab reboots by itself after you enter the 'fastboot boot' command(~30-40 seconds if it cannot boot, at most 5 minutes if it does, in this case it will also flash your bios)
ionioni said:
i cannot access the share you posted (make it public)
seems that it doesn't boot the image at all, this could be due to an existing IA32 bios (post a link to the bios you flashed so i can check)
until then...
you can try again and skip the first 'fastboot flash osloader efilinux.efi' if it still doesn't work replace the efilinux.efi file with one from a x86 older rom
no matter what wait until the tab reboots by itself after you enter the 'fastboot boot' command(~30-40 seconds if it cannot boot, at most 5 minutes if it does, in this case it will also flash your bios)
Click to expand...
Click to collapse
Hi, can you make one for c6j7?
Hi,
I have exact same problem as bosondehiggs. "couldn't find boot device handle." when I try to flash the restore bios.img. I used the file with the link at top of thread.
Any idea?
Thanks for your help
Hi,
the same problem to me on my Teclast Air III !!
I hope anyone who solved the problem can help us ...
Thx a lot
Alex
Try my idea, maybe help you: http://forum.xda-developers.com/showpost.php?p=64725703&postcount=26
Hi,
thank you Blackbile. Now its working... :good:
Alex
those who cannot restore, see here http://forum.xda-developers.com/showpost.php?p=64736792&postcount=36
acnic said:
Hi,
thank you Blackbile. Now its working... :good:
Alex
Click to expand...
Click to collapse
But what was the solution?????
I booted into BIOS and did what you have written and press restore defaults. Then i flashed again the efilinux and the restore bios. I had the same error and no reboot from the tablet! After waiting 10 minutes i decided to press the Power Button and bling there it is...
Now i have dual boot, but only Mireks Rom installed.
The next days i will try to install Windows, too.
I hope there are no problems again.
Thx for your help...
Alex
I flashed my M5C6 softbricked with the BIOS for C5J8 (2.05c) from the other post and it works now my tablet. The only problem I had me too is that the system doesn't reboot automatically after flashing process like @acnic so after 7 minutes I rebooted manually (with all my fingers crossed), finally the tablet has started like usual (I did the restore default settings into BIOS).
Now the only "problem" I had is that when I shutdown the system from Android or W10, I can't restart with power button so I need to press 10s before to can start the system again, Someone have an idea of this behaviour?
Many thanks again for your incredible work and support!!
Santi
Enviado desde mi SM-G900FD
Gitantos: http://forum.xda-developers.com/x98-air/help/x98-air-3g-doest-power-t3287417
*****************
How did you bricked?
While the restoring happened, did you see messages on the screen as I posted in my thread?
blackbile said:
Gitantos: http://forum.xda-developers.com/x98-air/help/x98-air-3g-doest-power-t3287417
*****************
How did you bricked?
While the restoring happened, did you see messages on the screen as I posted in my thread?
Click to expand...
Click to collapse
Hello blackbile, I bricked using the flashing method from Techknight's. I have unbricked with your guide (BIOS from C5J8)
Enviado desde mi SM-G900FD

Extreme situation with my Honor 4X

Hi guys,
I have Honor 4x Ch1-CL20, i did few thinks like unlocking bootloader, was flashing custom recovery, but than on stock software I wanted do upgrade to 6.0 Official and actually it got bricked..
Now It's just Honor logo, I can't get to Fastboot, recovery, or force update..
Afeter honor logo is flashing screen and actually pc find the device in ADB mode but it's offline and I can't do anything.
i used the honor toolkit which is not for 4x but it gave me option to reboot but anyway it didn't boot to recovery.
Please help me guys as now I don't know what i can do..
szymok said:
Hi guys,
I have Honor 4x Ch1-CL20, i did few thinks like unlocking bootloader, was flashing custom recovery, but than on stock software I wanted do upgrade to 6.0 Official and actually it got bricked..
Now It's just Honor logo, I can't get to Fastboot, recovery, or force update..
Afeter honor logo is flashing screen and actually pc find the device in ADB mode but it's offline and I can't do anything.
i used the honor toolkit which is not for 4x but it gave me option to reboot but anyway it didn't boot to recovery.
Please help me guys as now I don't know what i can do..
Click to expand...
Click to collapse
at first, you post it in wrong place, it should be at q&a thread
what you mean by adb find device but its offline, you cant execute any command?
when you try to boot to force update does it vibrate? if not give it a minute (mine boot into force update after 5 minutes with vibration after 1 minute of honor logo when it was bricked like that)
if you press vol- and connect the usb on the pc, you can enter to fastboot? and vol - vol + and power, it enters to recovery? and after the normal boot, it goes into bootloop or it says an error?
MarcoPLs said:
at first, you post it in wrong place, it should be at q&a thread
what you mean by adb find device but its offline, you cant execute any command?
when you try to boot to force update does it vibrate? if not give it a minute (mine boot into force update after 5 minutes with vibration after 1 minute of honor logo when it was bricked like that)
Click to expand...
Click to collapse
He probably means no connection
PalakMi said:
He probably means no connection
Click to expand...
Click to collapse
You cannot execute adb commands at initial pre-boot stage. It's because it's disabled by default. See the boot image. Extract it and the ramdisk and you'll find a file 'default.prop'. The two flags at the top ro.adb.secure=1 and ro.debuggable=1 (also sometimes ro.secure=1) are responsible for disabling adb at initial boot stage.
---------- Post added at 07:23 PM ---------- Previous post was at 07:19 PM ----------
szymok said:
Hi guys,
I have Honor 4x Ch1-CL20, i did few thinks like unlocking bootloader, was flashing custom recovery, but than on stock software I wanted do upgrade to 6.0 Official and actually it got bricked..
Now It's just Honor logo, I can't get to Fastboot, recovery, or force update..
Afeter honor logo is flashing screen and actually pc find the device in ADB mode but it's offline and I can't do anything.
i used the honor toolkit which is not for 4x but it gave me option to reboot but anyway it didn't boot to recovery.
Please help me guys as now I don't know what i can do..
Click to expand...
Click to collapse
I know it's a bit hard to go to Fastboot mode when the device gets stuck at the Honor logo since there is no way to power it off because we have no removable battery (or you could let the phone battery drain). Still there is a chance to get it to Fastboot mode. When you're stuck at the Honor logo, hold the power button to initiate a forced reboot. Now as soon as device screen goes black immediately hold the volume down button and connect your device to computer via a USB cable. You have 1-3 seconds to do it so it will take several attempts to get success. As soon as your device reaches fast boot, flash a custom recovery and reboot to recovery.
If you're successful report back. We'll see what to do next after it
you cannot do oTA upgrade with twrp installed

Xiaomi Mi 5x Bricked, Need help.

Hello, today I tried to install a custom rom on my xiaomi mi5x, so I unloocked the bootloader and installed twrp, than I installed the android one rom .The problem was that I had to verify my gmail because it got locked, so I looked up a way to bypass that lock. I followed a youtube video on how to bypass that lock on android one, and now my phone has the following issue:
After booting I only see the MI logo for about a second, than it goes into black screen, same thing happens when I try to boot to recovery.
The only thing that works is fastboot.
Please help me!
Go into fastboot and write following command:
fastboot boot twrp.img
Click to expand...
Click to collapse
You will enter a recovery mode. There you could try a factory reset or flash a new ROM.\
If this wont` help, you could flash a new ROM via fastboot also.
SoNhater said:
Go into fastboot and write following command:
You will enter a recovery mode. There you could try a factory reset or flash a new ROM.\
If this wont` help, you could flash a new ROM via fastboot also.
Click to expand...
Click to collapse
hi sir, i am facing also the same problem. and in my case every time i tried that code here is the output
FAILED (remote: unlock device to use this command)
i know that i already unlocked this before.
I would recommend that you flash the official firmware (fastboot version). Please follow the instructions here http://en.miui.com/a-234.html.
I need "emmc_appsboot.mbn" file from a working MD E2 devices.
Any body can help me pls. My mi5x device is now on black secreen. Not openning..
it became after load orijinal rom onto oxygen boot.
Any body can help me pls
I need "emmc_appsboot.mbn" file from a working MD E2 devices.
eman78 said:
I need "emmc_appsboot.mbn" file from a working MD E2 devices.
Any body can help me pls. My mi5x device is now on black secreen. Not openning..
it became after load orijinal rom onto oxygen boot.
Any body can help me pls
I need "emmc_appsboot.mbn" file from a working MD E2 devices.
Click to expand...
Click to collapse
Have you find a solution sir ?
I already have tried to flash in EDL mode but when the flashing is done the phone did not reboot, plugged in the charger, and connected to the computer only received
qualcomm Hs-usb Diagnostics 900e​

Mi A2 Can't enter fastboot mode (Black screen instead of MI bunny logo)

hello guys..
iam getting Black screen instead of fastboot mode !!!!
after rolling back from Wayne to jasmine (mi 6x to mi A2)
if i try to get into fastboot mode (vol down + power btn).. its not even working..
please help... Bootloader is already unlocked. and currently iam using android one. (rolled back from mi 6x)
current Rom is working fine but i want to install miui 10 pie..
plss tell me how to fix fastboot mode...
Reflash stock splash.img
Aerobatic said:
Reflash stock splash.img
Click to expand...
Click to collapse
How to reflash bro... fastboot mode is not working. Is there any other way to install rom without fastboot
hackerh2 said:
How to reflash bro... fastboot mode is not working. Is there any other way to install rom without fastboot
Click to expand...
Click to collapse
You'r fastboot is working, you just lost the image for bunny in proces of reverting
mariosenta said:
You'r fastboot is working, you just lost the image for bunny in proces of reverting
Click to expand...
Click to collapse
i am facing the same problem. pls help... how to recover lost image
Open your phone, flash in EDL mode... it is simple... Find in youtube edl guide for mi a2
Sorry my bad english
I had this problem too. I was trying to flash stock jasmine rom from my amd ryzen pc and this happened. It was the first time I was using ryzen pc for flashing. In a reddit post, I saw this: "fastboot is broken on ryzen pcs". Then I tried to flash from my intel laptop and problem solved.

Redmi Note 9 merlin 4/128 NFC - Hard Brick

A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Already tried power and minus option.when you connect to a desktop what does it say ?
Dokrak99 said:
Already tried power and minus option.when you connect to a desktop what does it say ?
Click to expand...
Click to collapse
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
That's bad.
Hold the power +/- longer then 15 seconds try both.
Second
Charge for about 10 minutes and try the same again.
Last drain it when down keep pushing the power button to flat it.hook it up on desktop and install miflashtools.or try power +/- again
Dokrak99 said:
Hold the power +/- longer then 15 seconds try both.
Click to expand...
Click to collapse
Same as:
LordRedstone05 said:
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
Click to expand...
Click to collapse
Dokrak99 said:
Charge for about 10 minutes and try the same again.
Click to expand...
Click to collapse
When I try to charge it it goes in the bootloop again until I disconnect it and the battery runs out.
Dokrak99 said:
Last drain it when down keep pushing the power button to flat it.
Click to expand...
Click to collapse
It goes on, shows this battery icon, that it's empty and goes off. This repeats until I release the button.
Dokrak99 said:
hook it up on desktop and install miflashtools.or try power +/- again
Click to expand...
Click to collapse
The miflashtool does nothing when I click on Flash with the images and scripts loaded. Power +/- does the same as before.
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Dokrak99 said:
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Click to expand...
Click to collapse
Thanks in advance
What should I do in this tool? The tool doesn't recognize my phone. It brings nothing since I cannot access Fastboot.
Well basically there is only one real option left . contact mi service center because mi don't support or they closed there download,edl support on there phones to prevent rom swapping .there is a edl cable with mtk support around but that's a long shot.because I never had a messed up phone like this.at least not one with mtk.without recognise you're desktop I don't see a fix in this to get in fastboot or flash it.
Download platform tools drop it on c:/ so c:/platform tools .install abd drivers package if you didn't have it.go in platform tools the top line and tick Cmd hit enter.try command : fastboot devices .try a few times if a number pops up you can try .fastboot reboot fastboot
LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
TWRP bricked my redmi Note 9 too, but i had ADB Connection in the black Screen so i rebooted to Fastboot over ADB and reflashed the Stock rom
LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
Did you find solution on this? Please answer bro i need your help
Jayson Galang said:
Did you find solution on this? Please answer bro i need your help
Click to expand...
Click to collapse
Unfortunately i haven't found a solution. I had to send it to a service center 2 Days ago. Sorry, that i couldn't help.
the right driver is mtk this is not adb nothing happens the this you could fixs is
go to the nearest techniciann beacause they need special tools to fix properly
Is your phone still bricked, If yes, I can provide link for the factory firmware recently released for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Communos said:
Is your phone still bricked, If yes, I can provide link for the factory firmware recently leaked for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
Click to expand...
Click to collapse
yow is that legit? Had my redmi note 9 bricked for a week now.
CruisaderX said:
yow is that legit? Had my redmi note 9 bricked for a week now.
Click to expand...
Click to collapse
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If it keeps restarting, you've made any wrong modification. You need to follow your steps back and try to unmake your modification.
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
If you are using V12.0.5.0 or higher, TWRP will not work.
If you want to use sp flash tool, you need to flash the stock rom preloader using V12.0.4.0 (or lower). (It will works perfectly with lower preloader binary version).
With an older preloader version, your phone will can receive DA files and accept flashing with NO auth.
Everything you need to do is plug your phone in usb (without press any key, if you press any key it will enter in EDL mode and requests authenticaion).
Here, are PRELOADER binaries for flashing: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221081/
Here, are DA files for flashing using flash tool: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209767/
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
[/QUOTE
Click to expand...
Click to collapse
I tried actually before after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting), I will call this state 1 brick. In state 1 brick you can still access fastboot mode normally. Then i tried to flash twrp hoping to just flash a rom to fix it leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot bootloader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi devices. Now I am stucked with a hard bricked note 9 with no way of fixing.
CruisaderX said:
i tried before actually after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting, I will call this state 1 brick. In state 1 brick you can still access fastboot mode. Then i tried to flash twrp hoping to just flash a rom leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot boot loader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi device. Now I am stucked with a hard bricked note 9 with no way of fixing.
Click to expand...
Click to collapse
You need to read every line and every word careful and follow only specific guide for your specific problem.
If you try to do anything you see, obviously you will cause more damages to your device.
Please, read my post again: https://forum.xda-developers.com/t/redmi-note-9-merlin-4-128-nfc-hard-brick.4201717/post-84379823
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

Categories

Resources