RN9 Anti-Rollback triggered - Redmi Note 9 Questions & Answers

Hello
I Bricked My RN9 by triggering an older Miui Version
I saw on the internet and most people said that I should go to a Mi Service Center
they took it there for almost 3 weeks and then, They told me the phone is out of warranty!!
How should i fix it
Thanks.
Edit: It's actually not a hard brick
The phone bootloops and the pc gets recognized to it but, I can't boot into recovery mode or fastboot mode so I can't flash anything.
Anyone knows the solution ?

Actually , the Official store should be able to fix it.

Enter fastboot and flash
If it's a softbrick, you're seriously lucky
Enter fastboot mode by holding down volume down and power button
In some cases once the phone is bootlooped, you only need to hold volume down
Once entered fastboot, flash miui latest version via Mi Flash tools

Actually all firmwares keep in same rollback version.
So you can have V12.0.6.0 installed and then flash older version, as V11.0.2.0. Or opposed.
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 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/
Only after it, you can use sp flash tool again.
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/

Related

mi5 brick after edl flash. start only fastboot. locked bootloader

hi,
i flashed 6.5.12 by miflash in edl mode.
Flash done in miflash, but on reboot mi5 is bricked. Logo Mi and shut down.
bootloader is locked.
my devices start only fastboot mode. it don't go in edl mode. if i press powe and vol + it's don't start and shut down.
By fastboot it's don't go in edl
help me pleas
If your are logged into your Mi Account on the phone you can do this: apply for the bootloader unlock code with that MI account (use other phone while you fix the xiaomi), wait for the unlock approval sms code, its tooks like 7 to 15 days, then download the software for the unlock bootloader process, loggin with your approved mi account, put your phone in fastboot mode, connect it to the pc press start and thats all (no need to boot in normal mode for unlock), you should have your bootloader unlocked and you will be able to enter in EDL mode and flash again the rom.
P.D. Sorry for my bad english
Ehi, I know how to fix your phone.
I can link you an italian forum's thread, a guy had your same problem. You have to plug your phone to pc and press power button and vol+ button, your pc will recognize it correctly if you had installed drivers, even if your phone shuts down. Now you can enter in edl mode (maybe mi5 is already in it) and flash a rom with miflash.
Sorry for my English.
Have you try to flash using MiFlash?
You can download it from here
My friend also encounter this problem and what he did is:
1. Use a fresh installed notebook with Win 7
2. Use MiFlash to flash the image file.
Image file can be downloaded from here.
It should works with locked bootloader as you are flashing the stock image.
Please give it a try.
littleprince86 said:
By fastboot it's don't go in edl
Click to expand...
Click to collapse
Please try this method.
I had the same issue after I had relocked bootloader using command
fastboot oem lock
Click to expand...
Click to collapse
When I noticed this strange behaviour, I switched to fastboot mode again (VolDown + Power) and unlocked bootloader again using MiUnlock tool for Windows and USB data cable. After that it my phone works again. No data was lost - everything remained as before.

Soft Bricked Redmi 4X Global, Can't find solution, please help me :(

Hello Xda community,
I need help badly , I bricked my phone one week after receiving it !! My goal was to install Clarity kernel for better battery performance.
I try to tell you all the steps and informations you will need to help me :
1 - I unloacked bootloader using Mi unlock.
2 - I installed TWRP 3.1.1-0 and root my device this way : LINK (method 2)
3 - I flash in recovery mode last MIUI rom 9.5.5.0, phone still running well after that
4 - I boot in recovery and flash this firmware in order to flash Clarity Kernel after
5 - After flashing the firmware I reboot and Im stuck at MIUI logo. I can go to fastboot mode though. But unable to reach recovery mode neither switch off the phone.
6 - I install MiFlash and tried to flash different version of rom MIUI santoni from official website (9.5.5.0 / 8.2.10.0) neither work SEE IMAGE I tried with mi flash 2016.08.30 same result
I get different status on mi flash, one is (image not matching device), even though I think I did everything well.
7 - Since last try of flashing my computer does not even recognise my phone in fastboot mode like before :/ and MiFlash doesn't see my phone :/
Please give me some advice/clue to revive my phone :crying:
In advance I thank you so much :good:
I use Windows 10 - 64 bits
try booting recovery from fastboot "fastboot boot *twrp image*.img"
Niaph said:
Hello Xda community,
I need help badly , I bricked my phone one week after receiving it !! My goal was to install..........
In advance I thank you so much :good:
I use Windows 10 - 64 bits
Click to expand...
Click to collapse
Well i am not at all an expert in miui, infact this is my first mi phone. But i think this tool called xiaomi adb/fastboot tool can help u. Google it.... It is available in reddit. One piece of general advice : before any kind of experiment always keep a preparation for the worst case scenario. I think ur phone is stuck at boot. U can try to hold the power button for about 10-15 seconds to turn off. Also just relax and have patience... It will b solved. Let me know how it goes.
Niaph said:
Hello Xda community,
I need help badly , I bricked my phone one week after receiving it !! My goal was to install Clarity kernel for better battery performance.
I try to tell you all the steps and informations you will need to help me :
1 - I unloacked bootloader using Mi unlock.
2 - I installed TWRP 3.1.1-0 and root my device this way : LINK (method 2)
3 - I flash in recovery mode last MIUI rom 9.5.5.0, phone still running well after that
4 - I boot in recovery and flash this firmware in order to flash Clarity Kernel after
5 - After flashing the firmware I reboot and Im stuck at MIUI logo. I can go to fastboot mode though. But unable to reach recovery mode neither switch off the phone.
6 - I install MiFlash and tried to flash different version of rom MIUI santoni from official website (9.5.5.0 / 8.2.10.0) neither work SEE IMAGE I tried with mi flash 2016.08.30 same result
I get different status on mi flash, one is (image not matching device), even though I think I did everything well.
7 - Since last try of flashing my computer does not even recognise my phone in fastboot mode like before :/ and MiFlash doesn't see my phone :/
Please give me some advice/clue to revive my phone :crying:
In advance I thank you so much :good:
I use Windows 10 - 64 bits
Click to expand...
Click to collapse
Nevermind I misread... If you think clarity or the firmware messed up your phone I could give you my kernel and firmware for you to restore it
Though if you're desperate for a solution, I'd transfer a ROM into your phone and start over with it, you can flash MIUI also by flashing https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view after it
Your version of miflash is a little bit outdated! The last One is from may, last year if my memory doesnt fail. Install latest version of miflash and try to flash again stock ROM.
You can try also flashing stock ROM with miflash but in edl mode (emergency download mode) , instead of fastboot mode, but to do that you have to acess stock recovery, and then use this command " adb reboot edl", connect your phone to PC, and then see of detects, then flash then stock ROM. To acess stock recovery, press volume up + Power, if that not works, press volume up + volume down+ Power. Hope i helped
Ok I solved the problem using this method.
So I removed back cover, disconnected battery, connected the 2 points with a twizzer then flashed STOCK rom and it worked!! So relieved!
Thank you for the help anyway.
Speaker87 said:
Your version of miflash is a little bit outdated! The last One is from may, last year if my memory doesnt fail. Install latest version of miflash and try to flash again stock ROM.
You can try also flashing stock ROM with miflash but in edl mode (emergency download mode) , instead of fastboot mode, but to do that you have to acess stock recovery, and then use this command " adb reboot edl", connect your phone to PC, and then see of detects, then flash then stock ROM. To acess stock recovery, press volume up + Power, if that not works, press volume up + volume down+ Power. Hope i helped
Click to expand...
Click to collapse
Dear sir,
flashing redmi4 with miflash tool in edl shows me "object reference is not set to an instance of the object". Any solution please. This was second time i try flashing soft bricked redmi4 , first time few days ago flashed successfully and was using it properly in edl with miflash tool. Then During downloading update shown in setting by ota and rebooting it, and again got stuck on mi logo, means softbricked again.but try edl this time gives an error mentioned.
Speaker87 said:
Your version of miflash is a little bit outdated! The last One is from may, last year if my memory doesnt fail. Install latest version of miflash and try to flash again stock ROM.
You can try also flashing stock ROM with miflash but in edl mode (emergency download mode) , instead of fastboot mode, but to do that you have to acess stock recovery, and then use this command " adb reboot edl", connect your phone to PC, and then see of detects, then flash then stock ROM. To acess stock recovery, press volume up + Power, if that not works, press volume up + volume down+ Power. Hope i helped
Click to expand...
Click to collapse
chandan shah said:
Dear sir,
flashing redmi4 with miflash tool in edl shows me "object reference is not set to an instance of the object". Any solution please. This was second time i try flashing soft bricked redmi4 , first time few days ago flashed successfully and was using it properly in edl with miflash tool. Then During downloading update shown in setting by ota and rebooting it, and again got stuck on mi logo, means softbricked again.but try edl this time gives an error mentioned.
Click to expand...
Click to collapse
Problem solved.
I got revived my redmi 4 again from softbricked locked bootloader,
By trying an older rom
santoni_global_images_V8.2.12.0.MAMMIEA_20170629.0000.00_6.0_global_751410291c.tgz​With miflash-20220218 in edl mode .

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/

Question Hi, just bricked my device

So, I was trying to flash a GSI Custom Rom on my device, I tried fastboot flash super ./system.img, and it didn't work. (fastboot screen)
I couldn't boot into fastbootd, because when I tried fastboot reboot fastboot, twrp appeared, device not recognized by fastboot devices, and touch not working.
So I rebooted into bootloader and tried to flash global rom, so I could get fastbootd but I realized that I could just flash boot.img, so I closed MiFlash before it was flashing super partition (bad idea) and tried to do fastboot flash boot ./boot.img.
It didn't work, so I rebooted it... black screen, stuck in EDL.
Then tried to flash global rom in MiFlash again, saw COM4, but tried to flash anyway. And I got "write time out, maybe device was disconnected."
Tried multiple times, the same message.
Holding Power + Vol Down didn't do anything.
And I need to ask you, is there any way to boot into fastboot and then into twrp or something, without Testpoints, and authorized Xiaomi account?
I don't quite have money, or something to repair.
Thanks.
flash this :https://drive.google.com/file/d/1quyYpwV8IkZxnICZ2PEBXduuarxemlBI/view?usp=sharing, it's an engenering rom which works with edl mode. after the flash let the rom boot and reflash the rom you want.
Got the same error,
it flashed "prog_firehose_ddr.elf"
And then again write time out, maybe device was disconnected.
reversee said:
Got the same error,
it flashed "prog_firehose_ddr.elf"
And then again write time out, maybe device was disconnected.
Click to expand...
Click to collapse
Do you use the usb cable sold with the mi 11 ?
Pikaone41 said:
Do you use the usb cable sold with the mi 11 ?
Click to expand...
Click to collapse
Yes i did
reversee said:
So, I was trying to flash a GSI Custom Rom on my device, I tried fastboot flash super ./system.img, and it didn't work. (fastboot screen)
I couldn't boot into fastbootd, because when I tried fastboot reboot fastboot, twrp appeared, device not recognized by fastboot devices, and touch not working.
So I rebooted into bootloader and tried to flash global rom, so I could get fastbootd but I realized that I could just flash boot.img, so I closed MiFlash before it was flashing super partition (bad idea) and tried to do fastboot flash boot ./boot.img.
It didn't work, so I rebooted it... black screen, stuck in EDL.
Then tried to flash global rom in MiFlash again, saw COM4, but tried to flash anyway. And I got "write time out, maybe device was disconnected."
Tried multiple times, the same message.
Holding Power + Vol Down didn't do anything.
And I need to ask you, is there any way to boot into fastboot and then into twrp or something, without Testpoints, and authorized Xiaomi account?
I don't quite have money, or something to repair.
Thanks.
Click to expand...
Click to collapse
Hi
I had the same problem with k20 pro
The Emmc was distroyed.
So you need to go to a service center.
Hello, press volume + and power key at the same time when the phone turns on immediately press the volume key - but without releasing the volume + or the power key, this will take you directly to recovery twrp or to fastboot, hopefully we will solve it soon
Pikaone41 said:
şunu flashlayın: https://drive.google.com/file/d/1quyYpwV8IkZxnICZ2PEBXduuarxemlBI/view?usp=sharing , bu, edl moduyla çalışan geliştirici bir rom'dur. Flaştan sonra rom'un önyüklemesine izin verin ve istediğiniz rom'u yeniden yükleyin.
Click to expand...
Click to collapse
Dosyayı tekrar paylaşabilir misiniz?
reversee said:
So, I was trying to flash a GSI Custom Rom on my device, I tried fastboot flash super ./system.img, and it didn't work. (fastboot screen)
I couldn't boot into fastbootd, because when I tried fastboot reboot fastboot, twrp appeared, device not recognized by fastboot devices, and touch not working.
So I rebooted into bootloader and tried to flash global rom, so I could get fastbootd but I realized that I could just flash boot.img, so I closed MiFlash before it was flashing super partition (bad idea) and tried to do fastboot flash boot ./boot.img.
It didn't work, so I rebooted it... black screen, stuck in EDL.
Then tried to flash global rom in MiFlash again, saw COM4, but tried to flash anyway. And I got "write time out, maybe device was disconnected."
Tried multiple times, the same message.
Holding Power + Vol Down didn't do anything.
And I need to ask you, is there any way to boot into fastboot and then into twrp or something, without Testpoints, and authorized Xiaomi account?
I don't quite have money, or something to repair.
Thanks.
Click to expand...
Click to collapse
please use testpoint for edl and then flash the engineering rom and flash the global rom
mvikrant97 said:
lütfen edl için testpoint'i kullanın ve ardından mühendislik rom'unu yükleyin ve global rom'u yükleyin.
Click to expand...
Click to collapse
mvikrant97 said:
please use testpoint for edl and then flash the engineering rom and flash the global rom
Click to expand...
Click to collapse
When I plug in the usb cable, it acts as if it's in edl mode. no flash method worked, the only solution is the prog_firehose_ddr.elf file, unfortunately I can't find it for Venus 11

Help redmi4 edl error: "object reference not set as an object"

I had soft bricked redmi 4 mobile with locked boot loader, I could go to mi recovery 3.0 and fastboot etc. I tried to flash santoni 10.3 rom via fastboot mode but couldn't flash it with "critical partition error" due to locked bootloader. Then I entered edl mode by shorting test points, then successfully flashed rom with clean all option via miflash tool 'santoni_10.3 global', mobile started well and i used it 2 days. It shows ota updates available of 11.0.2nammixm in setting's updater. I downloaded it and after rebooting it left me mi recovery 3.0 and then I choosen reboot to system and got suck on mi logo again. It means i softbricked device again with locked bootloader. This time i again tried edl mode with miflash tool but it gives error "object reference not set as an object ". Don't know hot fix it. I tried 2 different miflash tool versions, both the fastboot roms "santoni 10.3 global" and "santoni 11.0.2 global" to flash, but getting that error again and again.
Sorry for my bad english.
Please help me, I can go into fastboot mode and edl with port 'qhsusb 9008 com10'
Crying...
Problem resolved,
I got revived again my redmi 4 mobile.
Solution is to try any older rom and older version of mi flash tool.
Suggestions-
Use santoni_global_images_V8.2.12.0.MAMMIEA_20170629.0000.00_6.0_global_751410291c.tgz
And miflash-20220218 or miflash-20170425
Use Edl mode if you have locked bootloader,
Fastboot mode if having unlocked bootloader.
I will update my successes report if get managed to switch on miui 11 (currently having miui 8).

Categories

Resources