Database Develop

Problem when up ROM CHT9110

When I upgrade rom of CHT9110 by P3600i ROM. I got an error Invalid Vendor ID. And screen now is USB Bootloader. How I can restore to the original rom or is there any rom can upgrade for CHT9110 to support English language

up top......................

up up
up up ...............

I confronted same situation as you before. When i tried to flash my 3600i(HK traditional Chinese version) using "RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship.exe" found in forum, my 3600i finished with same error as yours "Invalid Vendor ID" and stayed on 3-color bootloader screen after rebooting. however, It restored to the original rom after I tried to flash my 3600i with upgrading software "D810_GPS_HK_TradChinese.exe" which got from download link appeared on software update in my Htc e-club. flashing "D810_GPS_HK_TradChinese.exe" failed with something like "wrong model" then my 3600i rebooted automatically and restored to the orginal state. I hope my case could do a little help to you.
also found the following from readme.doc in "RUU_Trinity_DOPODASIA_WWE_3.00.707.17_6275_1.46.00.11_108_Ship"
8. Q: I use RUU to update and failed, and my device always boots in three-color mode and cannot enter CE OS anymore, what should I do now?
A: If the update process has failed, you will see that your device will always boot in three-color mode. It’s normal and can be recovered. Please follow the instructions below to reset your device and to establish a connection with the computer.
1. Disconnect your Mobile Device from the USB cradle/cable.
2. Reset your Mobile Device.
3. Reconnect your Mobile Device to the USB cradle/cable.
4. Check that the communication cradle/cable is connected properly.
5. Return to the ROM Update Utility.
Note: You should ignore the ActiveSync connection.

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

Stuck on Bootloader. (device state=unlocked, secure boot=yes)

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.

Huawei P10 VTR-L09 bricked?

Hey everyone,
after spending about 5 hours trying everything I could think of and what I found in all kinds of forums, I'll try here before the phone is gonna be burried.
Got a "dead" P10 from a friend - booted straight to an error page with the headline "Your device has failed verification and may not work properly." My guess is that it was supposed to be updated, didn't have enough memory and then crashed.
Here's what I tried:
Factory reset - aborts at about 25%.
Download of a new firmware version via WLAN - aborts
Upload via SD-Card (dload) - firmware update failed
The phone is not recognized on the PC - so wouldn't know how to flash it from there.
I can still access it via fastboot, but I actually don't now how that could help me
Can anyone think of anything else that could be done?
LG
Maxi

Somebody got any idea?

[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.