Hi!
I have hard bricked Redmi 9 (cattail) device and now I want to unbrick it. According to a video, I need to flash boot.img of stock fastboot rom to get fastboot working and then flashing the stock rom. But, when I try to flash it, I get the following error:
Handshake error, retrying...
It comes about 7 - 8 times and the program exists. What could be the possible reason?
Btw if someone has a link that shows how to brick this device in a detailed way, I would be more than happy
Related
Hello, yesterday I bought used Lenovo k3 note. Man was selling it for insane price and said that it is stuck on logo. I bought it and thought that it would be fixed by simple flash but I was wrong.
The phone can easily be recognized by computer and when powered on is only stuck on logo "Lenovo powered by android" I can also go in stock recovery and factory mode without problem. But when I try to flash something it always results in errors. SP flash tool starts flashing process but at the end( some checksums) says :" BROM ERROR:S_CHKSUM ERROR(1041) "with no further hint, after little research I did a memory test in SP flash tool which showed " ERROR: NAND flash was not detected!" With following message :"BROM ERROR: S_DA_MT_DEDICATED_PATTERN_ERROR(3098)" I tried multiple ROMs and also tried to flash twrp recovery but it ended in the same way. Please help me if you can.
P.S. I tried flashing without DA DL checksum and flashing process succeeds but when powered on there is no change at all, everything is like before flashing. Also I opened device and there are no signs of physical damage.
Please anybody ?
Hello everyone, I wanted to open a topic here because I'm about 6 hours that I'm trying, but without any success ...
practically, after flashing via MiFlash (the latest version available) the update of 8.1.0 with the patches of October, the smartphone has started correctly, and then, suddenly turn off and go into EDL mode.
I tried all the possible combinations with the keys, but the result is that it simply always goes to EDL (the computer, also in Device Manager, detects Qualcomm HS-USB QDLoader 9008) ...
When i try to flash any rom stock, MiFlash detects the smartphone, but by flashing it gives me "hello packet not received" or, after flashing the firehose and abl me files from "You can not authorized to Download !!!" or, start the flash and then disconnect the smartphone by giving "can not read from port COM *number*".
I also tried to replace the files inside "images" by taking the files from Patched Programmer, but the result is always the same.
I really do not know how to continue ...
By chance, does anyone have a solution?
Thanks in advance for any help from you.
oscar-goat said:
Hello everyone, I wanted to open a topic here because I'm about 6 hours that I'm trying, but without any success ...
practically, after flashing via MiFlash (the latest version available) the update of 8.1.0 with the patches of October, the smartphone has started correctly, and then, suddenly turn off and go into EDL mode.
I tried all the possible combinations with the keys, but the result is that it simply always goes to EDL (the computer, also in Device Manager, detects Qualcomm HS-USB QDLoader 9008) ...
When i try to flash any rom stock, MiFlash detects the smartphone, but by flashing it gives me "hello packet not received" or, after flashing the firehose and abl me files from "You can not authorized to Download !!!" or, start the flash and then disconnect the smartphone by giving "can not read from port COM *number*".
I also tried to replace the files inside "images" by taking the files from Patched Programmer, but the result is always the same.
I really do not know how to continue ...
By chance, does anyone have a solution?
Thanks in advance for any help from you.
Click to expand...
Click to collapse
1)your bootloader is unlocked or not when you flash stock rom with MiFlash?(fastboot oem unlock and fastboot flashing unlock critical and this will wipe all your data if you don't already use this command)
2)Hello packet not received is currently with USB 3.0 and USB 3.1 port, try USB 2.0 port and reboot your PC and the phone
3)If this not work try to use your warranty
I tried to root my realme x2 pro using magisk. i patched boot.img and flashed via fastboot ( i was on latest update from realme ui2.0
RMX1931EX _11 _ F.12).
after booting into system all the google service crashed all service stopped and there were no google account on phone play store stopped working.
so i decided to re flash my device from begening and i wiped data from realme stock recovery and boot into fastboot and flashed system,vendor,boot,dtbo,vbmeta images and i reboot my phone.
From that moment my device is looping into bootloader.
I cant boot on any custom recovery, because it loops back into bootloader
If i flash stock recovery and boot into recovery, full white screen appears and my device stuck there.
In bootloader it says device state unlocked and secure boot yes. is this secure boot thing is creating this problem? or the latest patch of my system. I found that i cant flash custom recovery on realme ui 2.0 after bricking my phone.
REALME FLASH TOOL "CANNOT FIND CENTRAL DIRECTORY" ERROR
MSM TOOL, DONT HAVE USERNAME PASSWORD
QFIL TOOL (i used extracted ofp files in qfil tool)
2021-09-08 19:19:27.687 19:19:27: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
2021-09-08 19:19:27.687
2021-09-08 19:19:27.687 19:19:27: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
literally im pissed right now DO SOMETHING ENTHUSIAST
"Please help me to unbrick my phone. THANKYOU."
HELP PLEASE
PETER.PARKER said:
I tried to root my realme x2 pro using magisk. i patched boot.img and flashed via fastboot ( i was on latest update from realme ui2.0
RMX1931EX _11 _ F.12).
after booting into system all the google service crashed all service stopped and there were no google account on phone play store stopped working.
so i decided to re flash my device from begening and i wiped data from realme stock recovery and boot into fastboot and flashed system,vendor,boot,dtbo,vbmeta images and i reboot my phone.
From that moment my device is looping into bootloader.
I cant boot on any custom recovery, because it loops back into bootloader
If i flash stock recovery and boot into recovery, full white screen appears and my device stuck there.
In bootloader it says device state unlocked and secure boot yes. is this secure boot thing is creating this problem? or the latest patch of my system. I found that i cant flash custom recovery on realme ui 2.0 after bricking my phone.
REALME FLASH TOOL "CANNOT FIND CENTRAL DIRECTORY" ERROR
MSM TOOL, DONT HAVE USERNAME PASSWORD
QFIL TOOL (i used extracted ofp files in qfil tool)
2021-09-08 19:19:27.687 19:19:27: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
2021-09-08 19:19:27.687
2021-09-08 19:19:27.687 19:19:27: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
literally im pissed right now DO SOMETHING ENTHUSIAST
"Please help me to unbrick my phone. THANKYOU."
Click to expand...
Click to collapse
bro i have exact same issue with my Realme 3 pro
it was on Realme ui 2.0 and i flashed custom recovery from that stage it is stuck in fastboot/bootloader mode.
i also tried REALME FLASH TOOL but it showed me the same error as you got "CANNOT FIND CENTRAL DIRECTORY" error.
i have tried all the possible ways to unbrick it but it again boots back into bootloader
IT IS STUCK AND REBOOTING AGAIN AND AGAIN INTO BOOTLOADER
PLEASE HELP ME IF YOU GOT A SOLUTION PLEASE CONTACT
THANK YOU
Darshit16 said:
bro i have exact same issue with my Realme 3 pro
it was on Realme ui 2.0 and i flashed custom recovery from that stage it is stuck in fastboot/bootloader mode.
i also tried REALME FLASH TOOL but it showed me the same error as you got "CANNOT FIND CENTRAL DIRECTORY" error.
i have tried all the possible ways to unbrick it but it again boots back into bootloader
IT IS STUCK AND REBOOTING AGAIN AND AGAIN INTO BOOTLOADER
PLEASE HELP ME IF YOU GOT A SOLUTION PLEASE CONTACT
THANK YOU
Click to expand...
Click to collapse
SAME PROBLEM
I Tried Flashing TWRP in my realme 3 pro but it started boot looping.... I tried flashing stock recovery and vbmeta file so now my phone is bricked and it shows (as shown in picture)
Also tried realme flash tool but it shows "CANNOT FIND CENTEAL DIRECTORY"
Darshit16 said:
bro i have exact same issue with my Realme 3 pro
it was on Realme ui 2.0 and i flashed custom recovery from that stage it is stuck in fastboot/bootloader mode.
i also tried REALME FLASH TOOL but it showed me the same error as you got "CANNOT FIND CENTRAL DIRECTORY" error.
i have tried all the possible ways to unbrick it but it again boots back into bootloader
IT IS STUCK AND REBOOTING AGAIN AND AGAIN INTO BOOTLOADER
PLEASE HELP ME IF YOU GOT A SOLUTION PLEASE CONTACT
THANK YOU
Click to expand...
Click to collapse
Is there any solution here, I landed to this problem here
rizwanp880 said:
Is there any solution here, I landed to this problem here
Click to expand...
Click to collapse
Nah bruh still nothing i visited service centre twice and they said it's motherboard issue you need to change the whole motherboard which costs approx 4000 INR.
Who would do that it's just a software problem and also i found out that if device bootloader is locked then there is only 1 tool which can make it work again that is MSM TOOL and for that we need to do that outside in shop or somewhere, you can't flash at home as it needs user id & password and that we don't have, they charge like 800 to 900 INR.
I also tried the crack version of this tool but it doesn't detect the phone and doesn't work.
rizwanp880 said:
Is there any solution here, I landed to this problem here
Click to expand...
Click to collapse
text me on WhatsApp i can help +917889751393
Darshit16 said:
Nah bruh still nothing i visited service centre twice and they said it's motherboard issue you need to change the whole motherboard which costs approx 4000 INR.
Who would do that it's just a software problem and also i found out that if device bootloader is locked then there is only 1 tool which can make it work again that is MSM TOOL and for that we need to do that outside in shop or somewhere, you can't flash at home as it needs user id & password and that we don't have, they charge like 800 to 900 INR.
I also tried the crack version of this tool but it doesn't detect the phone and doesn't work.
Click to expand...
Click to collapse
You can visit Realme Service Centre and ask them to flash the software they'll charge you around 177 to 200 INR and your phone will be flashed.
Ive a problem now with my RN9. I unlocked the bootloader but did not immediately flash a custom rom. I made steps to try install PixelPlus but in the process of trying to install TWRP Ive hit a snag. Im not sure what Ive done wrong but Im in a boot loop. The phone either bootloops or I can get to Fastboot logo.
I tried following this video -
- Unbrick Redmi Note 9 or Redmi 10X 4G (merlin) using SPFlash Tool
When I select the DA, Scatter and Authentication file and go to "firmware upgrade" I get the error - "Partition [recovery ] No image file Exist!
My fear is somehow I've wiped the file from the phone. Im going round in circles trying to find a solution but im stuck.
If anybody has any help, Id greatly appreciate it!
Thanks for reading.
Hello, As You Saw from the title, i need help for the SM-M315F (ZTO), as it was bricked.
How did i get here? Well, i thought of installing evolutionX unofficial custom ROM, alongside TWRP, and while following the tutorial i got from the TWRP, the download failed sucessfully (its funny, but its technically true from my standpoint, as it was marked as a sucess by odin, but it didnt open TWRP on my M31).
And then it got into a bootloop, which i got it resolved by making the tutorial again, and then it asked for vbmeta.
But when i saw that it was a tutorial for android 10 firmware, it was too late. my phone was bricked. Smart switch wouldnt fix it, my device manager would only detect the usb driver for the cable and the USB-C entry on the phone, and if i try to reboot, it would get me back to the download mode screen with a error:
Error verifying vbmeta image: HASH_MISMATCH (3)
you would may say: "oh, well, try at least getting back to original firmware". That maybe would work, but i dont have too much patience and sometimes the odin firmware install would stop randomly...
Any Help would be Grateful.
Cheers,
MGT1.
MGT1 said:
Hello, As You Saw from the title, i need help for the SM-M315F (ZTO), as it was bricked.
How did i get here? Well, i thought of installing evolutionX unofficial custom ROM, alongside TWRP, and while following the tutorial i got from the TWRP, the download failed sucessfully (its funny, but its technically true from my standpoint, as it was marked as a sucess by odin, but it didnt open TWRP on my M31).
And then it got into a bootloop, which i got it resolved by making the tutorial again, and then it asked for vbmeta.
But when i saw that it was a tutorial for android 10 firmware, it was too late. my phone was bricked. Smart switch wouldnt fix it, my device manager would only detect the usb driver for the cable and the USB-C entry on the phone, and if i try to reboot, it would get me back to the download mode screen with a error:
Error verifying vbmeta image: HASH_MISMATCH (3)
you would may say: "oh, well, try at least getting back to original firmware". That maybe would work, but i dont have too much patience and sometimes the odin firmware install would stop randomly...
Any Help would be Grateful.
Cheers,
MGT1.
Click to expand...
Click to collapse
Unless your device is completely dead and unresponsive, it isn't bricked.
I assume you unlocked the bootloader, yes?
What guide did you follow to flash the firmware?
Are you able to boot into recovery?
What happens when you try to put your device in download mode?
Closed at the OP's request.