Recently bricked my OP6T (T-Mobile Version) attempting to flash the International version using the MSM download tool and I am unable to fix my phone using the stock MSM tool. Any help would be greatly appreciated!
Edit: I fixed this issue by persisting with the MSM tool and after three failed attempts my fourth worked without a hitch and the phone is no longer bricked
Related
Greetings,
My Puerto Rico (Claro) D801 (which is actually a D803) is softbricked after successful rooting but failed KitKat firmware update. I'm used to rooting phones, but the G2 seems to have a few particularly broken elements. I essentially bricked my G2 because it identifies as D801 in software/hardware, but isn't actually compatible with D801 firmware. Major issue, which apparently loads of other people on XDA are having.
Summary:
Can't restore firmware from the phone (stuck in fastboot)
Can't restore from LGMobile Update application (Windows sees the phone on USB but application doesn't)
Can't flash either D801 or D803 TOT using LGFlashTool because of the identification issue.
I can get into Download mode.
I'm desperately looking for help in fixing this. Can supply more info on what I've already tried.
If you're having similar issues, I'm @michellzappa on Twitter. I just sent a public reply to @lguSAMobile containing a Google Documents link where I outline all the issues I'm having.
Thanks.
Not sure what I'm doing wrong (or if it's just my PC) with trying to convert my T-Mobile 6T to the international version.
Device gets detected in the MSM Tool but becomes stuck in the 'Parm Preprocessing' status (when starting the 'upgrade'). Been struggle with trying to resolve this for the passed couple of days. Not able to find much info on it.
[Edit]
Looks like the issue was related to my drivers. grabbed the drivers from here.
Hello, as you all can see I have the T-Mobile version of this phone. I have tried everything and I cant get the device rooted. I bought this phone unlocked from Amazon and I use it on Mint Mobile. I have no idea how or even if it effects the rooting process but, I cant think of any reason why none of the methods I've used dont work. I have tried using the "All In One Tool" and the same thing happens with that tool, that happens with every method I've tried; I can use a cmd window to boot into fastboot but, once I am there none of the commands I enter seem to have any effect. I can explain more but, has anyone experienced this or knows what the problem is?
All the info you need is right here:
[GUIDE] ROOT OnePlus 7T Pro McLaren 5G (T-Mobile version HD1925)
Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I...
forum.xda-developers.com
Assuming your phone has been SIM/carrier unlocked by T-Mobile, you then need to request an unlock token from OnePlus. All info in above thread
But I highly highly highly recommend making a backup of your persist partition using the MSM tool before even unlocking the bootloader
Hello everyone. it's been a week that I work on this problem but I can't solve it myself despite having made numerous attempts. the situation is this: installing lineage os when the system restarted the 6t got stuck in the bootlader. I installed qualcom drivers from here
https://androidfilehost.com/?fid=11410963190603879743
and downloaded msm https://androidfilehost.com/?fid=17248734326145733776
I disabled windows secure boot and installed optional qualcomm drivers on windows... the 6t is correctly recognized as Qualcomm 9008 in the device manager in port 9 but I also tried in the 7 and it is always correct.
I tried other divers (after removing the previous ones) and other versions of msm but I always give the same error : param preload... device not match images.
I have read many discussions and tried many things but I can not solve. someone is willing to help me. Thanks guys.
I also tried uninstalling the drivers and reinstalling these:
QUD.WIN.1.1 Installer-10037.3 Setup.zip | by Dark Nightmare for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
using this version of msm:
6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12.rar | Tool by iaTa for OnePlus 6T
[TOOL] 6T MsmDownloadTool v4.0.58 (OOS v9.0.12) https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
androidfilehost.com
the problem is not solved but changed to: (recording dawnload time in red) images do no match with teh phone!
i can't figure out if it's a msm or driver version problem or maybe something else ...
I don't know what the exact problem. If you have installed magisk or modify something to your phone, sometime msm will fail to recognized or flash..
rom
But if your phone can boot into fastboot mode, try to flash fastboot ROM it might help
Fastboot rom.
[ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if...
forum.xda-developers.com
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
sun-k said:
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
Click to expand...
Click to collapse
if you get a warning in MSM tool: 'images do not match the phone', you are flashing the wrong image. That could happen to a branded phone. So, if you have a T-Mobile branded phone, either convert it to Global first (that tool has 'device check' disabled), or use T-Mobile MSM tool.
Your other option is to contact OnePlus support and they can help you remotely. I got into a similar bind with my 6t a year and ½ ago and nothing I was attempting worked. It was very frustrating. Ultimately I contacted OnePlus and they got me back up and running in no time. I was a little upset that I had to resort to relying on the manufacturer but also relieved to have a working device again and also thankful that it was an option, even if I would've preferred to have fixed it myself. Good luck.
PS - something to be aware of, I'm not 100% sure that it was a result of OnePlus' involvement/remotely flashing the device but somehow I ended up with a new/different IMEI. This created a world of difficulty with my cellular carrier (VZW) - I had finagled a OnePlus 8 out of them by citing manufacturers defect (I had coverage through VZW despite purchasing the phone directly from OnePlus) but they said the OnePlus 6t they received had a different IMEI than what they expected to receive, which makes absolutely no sense and this is the only possible explanation I could come up with. It ultimately saved me from having to pay for retail for the OnePlus 8 but not without a lot of headaches in between. Oh and lemme just say that having a VZW OnePlus with a locker bootloader sucks, I can't wait to get away from this thing and back to something I can root (I only pulled this maneuver in order to buy myself some time as I wasn't thrilled with the 1+9)
I have an H872 on Havoc 4.4. I have upgraded to a Pixel and will be giving the H872 to my father-in-law. He will only be using it for phone calls - very unlikely he will text, and definitely won't use data. It will also be his first smart phone. Since the H872 is rooted, when it boots up it gives the warning display that the phone may be "Corrupted". I don't want to have to explain all that "root" stuff to him, etc... I want the phone as basic and simple as can be, hence , I want to reflash the stock firmware.
I am having troubles though. Booting the phone into download mode and starting LGUP fails to recognize the phone. I've tried with Uppercut as well and it says I'm missing a file in Apps/Roaming, etc...
Not sure the problem because I have reflashed stock many times with LGUP. Could it be that Havoc has changed the "identity" of the phone, or that it's on Android 11?
Any help to get this back to stock is much appreciated!
Got it figured out. Flashed back to an older TWRP (was on Orange Fox), flashed an old stock Oreo ROM, and then was able to flash kdz with LGUP.