My One Plus 6t was facing minor errors in the new update. I tried to roll back anf it ended up getting hw and sw error. I read on many forums and got a way to install a custom ROM by using MSM Tool. I mistakenly installed One Plus 6 ROM. Now the device boots up with no response to the screen. The MSM tool is not working. It says "Image Error". The phone is also not recognized by My PC as the usb debugging is off. The device status is displaying "Locked". I have ran out of options and cannot take it to any professional due to Corona Lockdown.
Thanks for your Time.
Related
Reposting it here, since this is the Lenovo sub-forums. Probably may find more help here.
I was using the Allegro ROM for the A1000G and it was running fine and dandy without any problems. Last night I tried installing a game and after I restarted it, it didn't turn on. I thought that maybe the device had low battery or something. So I plugged it in and let it charge for an hour and it still didn't turn on. Than I let it charge overnight and in the morning, it still doesn't turn on. So I tried to flash the Stock ROM for Lenovo a1000g and I got an error saying the storage was different or something - Error 3182 Message: BROM ERROR: S_STORAGE_NOT_MATCH (3182) [Edit - Tried to find the error, this is the one]
It was probably because the Allegro ROM was installed before it stopped working. So after that failed attempt at Flashing the Stock ROM - I don't get the battery indicator anymore and no matter what I try inside SP Flash Tool, it doesn't detect the device and the flashing process doesn't work. I tried installing and uninstalling all the MTK and Mediatek drivers but still not working. It shows up as MediaTek DA USB VCOM (Android) but it doesn't disappear, unless I remove the usb cable.
Before when I flashed the Allegro ROM and as seen across other youtube tutorials and guide, the device would show up for 2-4 seconds before disappearing and the SP Flash Tool would start working. Now it is just blank and the MediaTek DA USB VCOM (Android) doesn't go, no matter what.
Please, I would appreciate help. Since I don't have much knowledge regarding this. What must I do? I am depending on you guys.
~Aaron.
Bump. Please someone help.
FIXED* 6T A6013 bricked "build version and HW version is not match!" + MSMtool Error
[/STRIKE]My OnePlus 6T is currently displaying the message "build version and HW version is not match!" when I try to power it on.
It will turn off shortly after and I am not able to enter fastboot or recovery mode by holding volume up or down while booting.
I can boot into the mode for MSM tool by holding volume up and down while plugging in a USB cable.
But when I run MSM tool I get the error "Device not match image" or "Images do not match with the phone!"
I tried the MSM tools from here https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
10.3.0 and 9.04
I have a complete nandroid backup that I made of the phone, but because I am not able to boot into twrp or use fastboot I am not sure of a way that I can repair this device
I have looked at several different threads and have tried everything I could find, is there any possible way I could still use fastboot or use MSM tool?
I am pretty sure this phone is not a verizon model but an international one. Any help would be appreciated.
Edit:
Okay I downloaded the verizon MSM tool version instead just to see if that would work
And that has successfully started flashing the phone, so it looks like the place I bought it was selling verizon phones they had unlocked to look like international ones even though they are supposed to be a trusted seller and it wasn't an ebay purchase, it was supposed to be brand new
Edit2:
It appears to be working fine now, I have gone through the steps and unlocked my phone again, now running a custom rom and I hope everything will work fine.
AndroidMasterRace12 said:
[/STRIKE]My OnePlus 6T is currently displaying the message "build version and HW version is not match!" when I try to power it on.
It will turn off shortly after and I am not able to enter fastboot or recovery mode by holding volume up or down while booting.
I can boot into the mode for MSM tool by holding volume up and down while plugging in a USB cable.
But when I run MSM tool I get the error "Device not match image" or "Images do not match with the phone!"
I tried the MSM tools from here https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
10.3.0 and 9.04
I have a complete nandroid backup that I made of the phone, but because I am not able to boot into twrp or use fastboot I am not sure of a way that I can repair this device
I have looked at several different threads and have tried everything I could find, is there any possible way I could still use fastboot or use MSM tool?
I am pretty sure this phone is not a verizon model but an international one. Any help would be appreciated.
Edit:
Okay I downloaded the verizon MSM tool version instead just to see if that would work
And that has successfully started flashing the phone, so it looks like the place I bought it was selling verizon phones they had unlocked to look like international ones even though they are supposed to be a trusted seller and it wasn't an ebay purchase, it was supposed to be brand new
Edit2:
It appears to be working fine now, I have gone through the steps and unlocked my phone again, now running a custom rom and I hope everything will work fine.
Click to expand...
Click to collapse
hi bro where did you find verizon MsmDownloadTool
edit: problem solved bro. i used t-mobile msm tool.
Hi guys, I've been following the forum trying to solve my problem but nothing worked. I was trying to rollback from android and oxygen 10 to android pie 9, I did it sometimes (trying to fix the cts fail, another story, I gave up and I was happy to return for the last time to Pie) and everything went ok, but the last time I did it, installed the rollback, rebooted and the yellow message appears. I don't really know what to do, I can't get access to fastboot, cache, hard factory reset, anything. I tried the msm methods, always getting "images do not match the phone" (and I tried different versions for different OSs, also for Tmobile, not the case tho).
Do you have any last options for me or I have to ask for technical support and send it to OP? the phone is brand new (bought it 2 weeks ago), never rooted or anything like this.
Thank you very much.
Power off the phone hold the vol up and down button at the same time while holding then plug in your cord msm should recognize your phone
@matZOOOOO
Check youtube for some videos on how to use msm tool. I have seen a few videos there for 6t restore to stock, unbrick... The XDA thread here for msm tool is extremely detailed.
Any time I've ever delt with windows os it's always always always a driver issue. I hadn't even seen windows in like seven years until I had to install it dual boot on my laptop to use msm tool. But I had similar experience as you are. What worked for me was uninstalling the qualcomm usb drivers and reinstalling them, then of course reboot and after that the tool ran all the way through and I had my phone again.
Hello everyone !
I'm new on this forum but I really need your help. I tried to fix my mistake all day long yesterday (9am to 2am non stop).
So, basically, I have a OnePlus 8 Pro, Model IN2023.
I had OOS 11 updated. I tried to install OOS 12 Bêta and I did but I had a indian version so a lot of bugs.
I wanted to go back to OOS 11 but it was impossible because I was now in an indian version.
I tried with MyApplication2 to local upgrade and downgrade as recommand in Internet.
I tried to unlock bootloader and the following steps but here my problem:
I unlocked my bootloader then I misclick and I locked again my bootloader.
Then my phone just crashed and put this message:
"The current image (boot/recovery) have been destroyed and can not boot."
So, I forced to turn off the phone and try to go in EDL mode but:
1. ADB doesn't work anymore
2. Fastboot work fine
3. EDL mode is impossible
So, my bootloader is unlocked again. My phone is stuck on Fastboot mode:
Fastboot mode
Product_name - kona
Variant - SM8 UFS
Bootloader version -
Baseband version -
Serial number - eed52b71
Secure boot - yes
Device state - unlocked
I used the official firmware on OnePlus website, I used Python and Payload_dumper.py to have the .img from the .bin of the official firmware.
I tried to flash all the images, I tried to install TWRP, I tried almost everything I found but still stuck in Fastboot. Recovery mode doesn't work.
I tried to boot, to flash, to do everything I could.
I also tried MSM Download Tool but nothing appears inside.
Now, when I connect my phone, it's with a cable in USB-C but 3.0, not 2.0. Maybe that's the problem ?
When I plug my phone, in Device Manager, I have a "!" but the phone is recognized under
"Qualcomm HS-USB QDLoader 9008 (COM6). When I click on it, it says (sorry, I'm about to translate from french):
"Windows can not verify the numeric signature for the drives required for this peripheric. It is possible that a material ou software modification has been installed a corrupted file or with an incorrect signature, or it is a malware from an unknown source (Code 52)"
Please help me, contact me on Whatsapp, or here. Let's do this in direct.
Btw, I have a Macbook Pro to do all this. I used also Windows with Bootcamp.
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
andshura said:
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
Click to expand...
Click to collapse
Im happy you fixed your phone.
Read this before you even think to go to A12 again on this device.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Hi guys. As the title says I have a T-mobile Oneplus 6T running Android 11 and I think it is bricked. It is SIM unlocked and bootloader-unlocked as well. The problem started when I tried to flash TWRP and the phone continuously went to a Qualcomm CrashingDump state. Now I've tried several tutorials online but all of them point to the 10.3.8 instead of the 11 that the phone has and using the MSM Tool comes back as The image does not match the device. To make things worst following one of the videos I updated the Qualcomm drivers via WIndows Update and now my PC will not recognize the phone (USB not recognized by Windows error). Please I need the community's help on this one. Thank you soo much in advance.