Database Develop

[Bootloader Tool] MotoFlasher

MotoFlasher Bootloader Tool!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why use MotoFlasher?
When Motorola Make the firsts android phones, RDSLite flash all the stuff that make your phone work but now, RDSLite only works like fastboot or directly dont work on some devices.
So, if you want to flash your bootloader, you can use MotoFlasher, that simplifies the process.
Disclaimer
Bootloader Flashing is ONLY for phones that don't boot or don't pass the fastboot, don't use if your phone works.
Features
Easy Flashing With binary files included that simplifies the process.
Support Multiples Devices.
Automatic Process, With Minimal User Interaction.
Over 1K of LineCodes that protect your phone from malfunction/ bad use of qboot/qflash tool.
You Will Find Update Info, New Things and Download on my website
MotoFlasher Website
Issue Tracker (Support)

HOW TO/ FAQ/ Request
How To: Repairing a Moto Bootloader
First, Install the Special Driver (See Below).
Check your phone (on Device Manager), it shows like "Qualcomm HS-USB QDloader 9***".
Open MotoFlasher, select your device and your last android version, detect and Flash...
You Will see the fastboot screen on your device (if everything works great).
Flash the Partition Table, and Full Bootloader Again (See Below).
How to: See if I can use MotoFlasher for repair my phone:
If your device don't turn on, follow this steps:
Plug in your device and check Device Manager:
If the driver isn't installed, the device show like "qusb_bulk" or any that start like "qusb_...."
If the driver is installed, the device show like "Qualcomm HS-USB QDloader 9***".
Install the Driver
Now from 1.7.1.1 the driver is installed automatically, and you can manage on "Driver Installer" app. You didn't need to override signing anymore
TroubleShooting:
a. It hangs on:
Code:
greeting device for command mode
or
Code:
opening device: \\.\COM**
Just mantain power button until the program start working...
b. Error:
Code:
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
or:
Code:
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
your MBM-CI dont match with your bootloader version, use another MBM-CI version.
c. Cant flash GPT / Motoboot:
Use another firmware, try for another android versions.
d. Fastboot Error:
Code:
preflash validation failed
Try your original (or last flashed) firmware.
Requests:
Moto G 4.4.3 Firmware with './MBM-CI' Folder
Moto G 5.0 Firmware with './MBM-CI' Folder
Stop ASKING ABOUT A FIRMWARE, I didn't make the files, i didn't make the MBM-CI, i ONLY make them work on MotoFlasher.
We can't recreate MBM-CI files (programmer and singleimages) they are signature protected, and the phone wouldn't flash it if it modified (or created).
Publish a Request / Complete a Request.
You found a 4.4.3 /5.0 firmware? Click the above link and fill with that:
>Title: 4.4.3 MBM-CI Firmware
>Description: Link to the firmware and your xda user for credits.
>Kind: Task.
>Priority: Mayor.
>Component: Firmware Requests.
>Version: 1.6.1.1
Click to expand...
Click to collapse

Wish there was a Linux port.
The idea is great and the ui looks promising. haven't used but downloaded, incase if i ever need it. thank you.

Dear boss442, thanks for this awesome tool: i receive the message "FAILED (blank-flash:validate-rdl:could not open file)"
What's the problem? It's time to go to Motorola Assistance?

capitanbiglio said:
Dear boss442, thanks for this awesome tool: i receive the message "FAILED (blank-flash:validate-rdl:could not open file)"
What's the problem? It's time to go to Motorola Assistance?
Click to expand...
Click to collapse
Maybe i forgot something, tomorrow i will test
could not open file is because i didn't initialized working directory (facepalm)
EDIT: 1.6.1.1 Is Uploading to the server, when the updates come, tell me if you still receive this error
Ekril said:
The idea is great and the ui looks promising. haven't used but downloaded, incase if i ever need it. thank you.
Click to expand...
Click to collapse
Edit: Sorry but is useless to make on Linux, because there arent Drivers that handle the Qualcomm Bootloader, if you find one, tell me and i will por the app

Can i flash 4.3 firmware If now i have 4.4.4 ? i want 4.3
4.3! not 4.4.3!
thank you

Hey Boss442, nothing to do at all... do you have the last advice?

MadL1fe said:
Can i flash 4.3 firmware If now i have 4.4.4 ? i want 4.3
4.3! not 4.4.3!
thank you
Click to expand...
Click to collapse
Yes but not with this tool, just on fastboot flash system and boot.
capitanbiglio said:
Hey Boss442, nothing to do at all... do you have the last advice?
Click to expand...
Click to collapse
Yes, sorry I was working these days and i was offline

how would i go about using this on a moto razr hd maxx xt926 what files would i need my razr got screwed up trying to restore when plugged in to wall ac power all it does is blink the green led briefly over and over then goes solid for about 10 secs then off for about 30 secs then flashing again does not really respond to the vol or power buttons . When plugged into my pc the green led comes on solid for a moment then goes to flashing a little slower. screen does not come on what so ever. i was on 4.1.2 stock not rooted had flashed twrp to it but then used the razr utility to flash stock recovery so i could take the ota. i then took ota, it rebooted to stock recovery and it loaded about 60 percent then went off . would not power on at all. i plugged into a wall ac power cord and left alone. seems as if it charged. now im at the point discribed in the begining of my reply. any help would be great thanks

mattwheat said:
how would i go about using this on a moto razr hd maxx xt926 what files would i need my razr got screwed up trying to restore when plugged in to wall ac power all it does is blink the green led briefly over and over then goes solid for about 10 secs then off for about 30 secs then flashing again does not really respond to the vol or power buttons . When plugged into my pc the green led comes on solid for a moment then goes to flashing a little slower. screen does not come on what so ever. i was on 4.1.2 stock not rooted had flashed twrp to it but then used the razr utility to flash stock recovery so i could take the ota. i then took ota, it rebooted to stock recovery and it loaded about 60 percent then went off . would not power on at all. i plugged into a wall ac power cord and left alone. seems as if it charged. now im at the point discribed in the begining of my reply. any help would be great thanks
Click to expand...
Click to collapse
This don't work at the moment, and i dont have this device to find a way to repair it, but i will see if i can do something, talk me on PM
ps: send me the codename of your phone

Work downgrade to jb bootloader?

core720 said:
Work downgrade to jb bootloader?
Click to expand...
Click to collapse
It isn't intended for downgrade, and i don't think so, you will get failed if you try to flash the bootloader

@Boss442
can you make it for Android Lollipop? because i need this tool. my phone is dead please....

Boss442 said:
This don't work at the moment, and i dont have this device to find a way to repair it, but i will see if i can do something, talk me on PM
ps: send me the codename of your phone
Click to expand...
Click to collapse
i got this error and my phone doesnt open. what can i do
motoflasher program gives this error:
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: FAILED (blank-flash:device-open:serial-open:could not open device)
OUTPUT*:
OUTPUT:

ralp88 said:
i got this error and my phone doesnt open. what can i do
motoflasher program gives this error:
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: opening device: \\.\COM5
OUTPUT*: FAILED (blank-flash:device-open:serial-open:could not open device)
OUTPUT*:
OUTPUT:
Click to expand...
Click to collapse
you need file MBM-CI android 5,
i hope @Boss442 will create file MBM-CI for bootloader firmware 5.0 faster

Requests:
Moto G 5.0 Firmware with './MBM-CI' Folder

Boss442 said:
This don't work at the moment, and i dont have this device to find a way to repair it, but i will see if i can do something, talk me on PM
ps: send me the codename of your phone
Click to expand...
Click to collapse
Sandivisi said:
Requests:
Moto G 5.0 Firmware with './MBM-CI' Folder
Click to expand...
Click to collapse
our problem is with mbm cı 5.0 ? maybe removing battery will solve the problem ? ?

ralp88 said:
our problem is with mbm cı 5.0 ? maybe removing battery will solve the problem ? ?
Click to expand...
Click to collapse
you can try with removing battery, and if work i will removing battery also

@Sandivisi @ralp88
Have the solution here. Download this firmware: http://sbfdownload.droid-developers...1_1_release-keys-cid12-AmericaMovil_CO.tar.gz
Then flash via fastboot. Skip fastboot gpt and motologo.
Replace this "fastboot flash system systemsparsechunk00,01,02.img"
for this "fastboot flash system system.img"
The other commands are the same. We have to wait for an official firmware if we want to flash to 5.0
Enjoy. Hit thanks if that worked D:

aybarchu said:
@Sandivisi @ralp88
Have the solution here. Download this firmware: http://sbfdownload.droid-developers...1_1_release-keys-cid12-AmericaMovil_CO.tar.gz
Then flash via fastboot. Skip fastboot gpt and motologo.
Replace this "fastboot flash system systemsparsechunk00,01,02.img"
for this "fastboot flash system system.img"
The other commands are the same. We have to wait for an official firmware if we want to flash to 5.0
Enjoy. Hit thanks if that worked D:
Click to expand...
Click to collapse
we cant enter fastboot. phone screen is completly black.

Qhsusb_bulk/Qualcomm HS-USB QDLOADER 9008?

I will be explaining eeverything that happened. If you don't want to read it and just skip to the information about my phone, then please do so.
Ok, so to start with, I first bricked my phone by trying to unlock my bootloader and flashing TWRP recovery. Luckily I backed up my recovery and kernel images using Flashify, before my first brick. I then followed this to unbrick it http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9. After, I was able to unlock the bootloader and flash TWRP recvoery, following http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690. I used the D405n v20a version of the aboot.bin file and TWRP_2 (I forgot which version). I was trying to unlock the PIE security, because when I used qpyplus 2.7 (python) and typed "python", I got an error. This is my thread http://forum.xda-developers.com/subscription.php?do=viewsubscription&folderid=all. I tried a few times to follow multiple tutorials, which each time, I had to reflash the stock ROM after bricking it, and following the first tutorial I linked to unbrick my phone. I would get an error, saying the version is wrong, or something like that, every time I rebooted my phone. I rooted my phone again, then tried to follow the unlock bootloader and flash TWRP, following this tutorial http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690. Using the same aboot.bin and TWRP.img I used before. It was no longer working. When I went from the very start refollowing this http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9, stupidly I tried reflashing the recovery.img instead of the loader.img. Now, my phone never acts like it did when I was bricking it before. It never shows up in My Computer, doesn't show up in drive manager, showing no partitions, when I go to device manager, under "Other devices", my phone is "QHSUSB_BULK" http://i.imgur.com/QP4fRVp.png. In properties, this is under "general" http://i.imgur.com/CVgbAFR.png. "driver" http://i.imgur.com/38HRDib.png. "details" http://i.imgur.com/ejch5sW.png. "events" http://i.imgur.com/XP3Y3TP.png. I've plugged it into different ports, I commonly have it in COM-3. Upon looking around for "bricked phone QHSUSB_BULK", I found this forum http://androidforums.com/threads/hard-brick-lg-g2-qhsusb_bulk-but-no-partitions-detected.934856/. I scrolled down and saw to install some drivers, so I intsalled them. The phone then came under "Ports (COM & LPT)" as "Qualcomm HS-USB QDLoader 9008 (COM3)".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
So that is what happened, here is the information on my phone:
LG D405n L90
Android 5.0.2 (Lollipop)
Kernel 3.4.0+
v20a
Stock recovery
Root
Stock Recovery
*I assume most stuff above is reset or different since it's bricked*
Images:
http://i.imgur.com/zTRWMU6.png
http://i.imgur.com/QP4fRVp.png
http://i.imgur.com/CVgbAFR.png
http://i.imgur.com/38HRDib.png
http://i.imgur.com/ejch5sW.png
http://i.imgur.com/XP3Y3TP.png
Attachments:
http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
http://forum.xda-developers.com/subscription.php?do=viewsubscription&folderid=all
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9
http://androidforums.com/threads/hard-brick-lg-g2-qhsusb_bulk-but-no-partitions-detected.934856/
If anybody could help with this, I would be very greatful. Thank you.
If anyone has the same problem above, please follow this tutorial: http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429 It fixed it for me.

I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.

Maze Alpha hardbricked?

Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?

C0dR said:
Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?
Click to expand...
Click to collapse
would you please add some details, as to what steps you had to take to recover.
you know the only way this "developer" community works is if the people here using it share their knowledge. And you learned something in this experience that could very well help someone down the road.

C0dR said:
Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?
Click to expand...
Click to collapse
Where have you found the correct preloader for Maze Alpha X ? Thanks, CVLo

Have you tried this?
https://forum.xda-developers.com/maze-alpha/development/unbrick-maze-alpha-x-6-64gb-t3817716

Maze Alpha 4GB. Not booting. Black screen after rooting.
Hello everyone,
I have done the same thing as the first post, and my phone is at the black screen, not booting. My Maze is the 4GB version, not the 6GB. Can someone help me unbrick it?
When I put it into usb, I got two usb devices cycling:
Bus 002 Device 047: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
Click to expand...
Click to collapse
and
Bus 002 Device 048: ID 0e8d:0003 MediaTek Inc. MT6227 phone
Click to expand...
Click to collapse
When I try to Format the device, i got:
BROM Exception! ( ERROR : STATUS_SEC_WRITE_DATA_NOT_ALLOWED (-1073610740) , MSP ERROE CODE : 0x00.
[HINT]:
)((exec,../../../flashtool/Cmd/FormatCommand.cpp,78))
Click to expand...
Click to collapse
When I try to download a partition, for example preloader, I got:
executing DADownloadAll...
Stage:
[0] WRITE TO PARTITION [ preloader ]
Download failed.
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_DL_FORBIDDEN (-1073610748) , MSP ERROE CODE : 0x00.
Click to expand...
Click to collapse
or for recovery:
executing DADownloadAll...
Stage:
[3] WRITE TO PARTITION [ recovery ]
Download failed.
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_DL_FORBIDDEN (-1073610748) , MSP ERROE CODE : 0x00.
Click to expand...
Click to collapse
This goes for any partitions the other partitions as well.
I have tried these ROMs:
MAZE_Alpha_4G_V09_SPFT
MAZE_Alpha_V03_20170808
MAZE_Alpha_V04_B_20171018
MAZE_Alpha_V05_20170816
Click to expand...
Click to collapse
The Smart Phone Flash Tool is showing my Chip Info correctly. Maybe i am missing something. A permission maybe? Or the correct ROM. I have no backup too. I didn`t think that the situation will get so ugly.
Any help will be much appreciated.
Thank you in advance.

Bricked! Help me please.

Hello everyone
My brother's Mi A2 is bricked for no reason. I tried to solve this problem and searched a lot but didn't manage to solve it. I hope you can help.
* before telling my story here is some stuff to know:
- The phone was running official firmware and bootloader is locked, I've never played with it's software before.
- Oem unlocking option isn't turned on.
- The phone doesn't go to recovery mode, only fastboot or regular boot.
- I used EDL mode in every flashing attempt.
- I don't remember that there is a mi account assigned to the device.
* Here is what happened:
- The phone suddenly shut down during a call and never passed the AndroidOne logo after that.
- Tried EDL mode and miflash to flash the latest firmware. Flashing completed successfully but the phone still stuck on the androidone logo.
- Did it again and again but the result was constant.
- Tried flashing older firmware "Oreo 8.1" but during flashing system.img the process stopped with an error. (I don't remeber what the error was).
- I tried to turn on the phone but after showing AndroidOne logo This message appeared:
"Your device is corrupt. It can't be trusted and will not boot.
Visit this link on another device: g.co/ABH"
and the device shuts down in a minute.
Hint: Sometimes when I try to turn one the phone the above message appears after androidone logo and sometimes the device just keep showing the logo.
- Trying to flash any firmware version by using Miflash Beta gives an error message "Can not found programmer file" immediately. when I try again it gives: "can't read from port COM4", Changing the port gives the same error with different port number.
-When I use any other version of "Portable miflash", The flashing process starts normally but fails when trying to flash "dsp.img", giving an error of "writing time out".
- I tried reinstalling all drivers needed with no change at all.
I hope that you guys can help me solving this problem.
Thank you so much!

Try EDL mode opening your phone...

Badotti said:
Try EDL mode opening your phone...
Click to expand...
Click to collapse
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.

Ahmed A. Mohsen said:
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...

Badotti said:
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Click to expand...
Click to collapse
I opened the phone and used edl mode already but the problem is still present.

up

Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x

HTCDevil said:
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
Click to expand...
Click to collapse
This needs bootloader to be unlocked and my device's bootloader is locked.
Any solutions?

Go to service center this is last option you save RIP mi a2 ?

As I can see from picture you have posted, your bootloader is unlocked.

SkullSatan88 said:
Go to service center this is last option you save RIP mi a2
Click to expand...
Click to collapse
They refused to receive my device because I bought it from another country.

bomil said:
As I can see from picture you have posted, your bootloader is unlocked.
Click to expand...
Click to collapse
when I checked bootloader status in the beginning it was locked.
Are you sure that it's now unlocked?

Text me on telegram. @dejavutr

[CLOSED] Bricked [Error verifying vbmeta image: HASH_MISMATCH] (Brick between Soft and Hard)

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.