Related
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
moyabrit said:
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
Click to expand...
Click to collapse
use adb and flash androkernel to fix the incorrect kernel that you installed. you can do that by renaming it boot.img and sending the command fastboot flash boot boot.img
i haven't messed with androplus in a while but if you were on marshmallow i believe v34 will work and if you were on the absolute newest marshmallow i think its v35 off the top of my head.
fyi you dont need usb debugging on to use flashtool, you can get into fastboot mode with no rom at all installed.
Hi all,
tl;dr: Tried to hard unbrick my Oneplus X, which was partly succesful (no OS is installed in the process, while there should be). I am now stuck with no OS and only the Oneplus recovery. I want to install an OS, but it says my bootloader is locked. To unlock it, I need an OS ==> vicious circle.
Full story below:
Recently I've decided to reinstall LineageOS on my Oneplus X because I had quite some problems with it (battery drain, apps crashing, wifi slow to connect, ...). I've done it like 5 times before on this device for various reasons, so I didn't expect any problems. I had LineageOS 14.1 and TWRP 3.0.3 installed. When I wiped everything, I wanted to flash the ROM I had ready using TWRP. However, gave an error number 7, saying that the ROM is not compatible for the device, which I am sure was. Remembering I had a similar issue a while back, I installed flashed an updated version of TWRP (3.2.2) using TWRP itself. That was successfull, but here's where the trouble began.
I noticed that TWRP didn't recognise any storage (Internal storage, SD card and USB-OTG all showed up as 0 MB) any longer. Neither could I mount any of the storages. I've tried a lot of things to solve this. After a while, I decided that the only hope left was the 'mega unbrick guide' (https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/) which claims to be able to recover any device, unless it has a hardware problem. I got good hope as I got near the end of the guide. The last step says 'Disconnect phone from PC and boot into system', but here I got stuck on the Oneplus boot logo, making me think that there is no OS installed on the device.
I can still access the recovery using power button and volume down, but the recovery that the mega unbrick guide installs, is the limited Oneplus recovery. It allows to install a ROM from the local storage, or from USB using adb sideload. When I try option 1, nothing happens, no new screen opens or anything. When I try option 2, I enter the adb sideload mode which would normally allow me to sideload a ROM using my pc. My pc confirms I'm in adb sideload mode, and I try to sideload a ROM. It starts fine, but after a few seconds, it says 'Installation failed'. I've tried stock OOS, latest OOS as well as LineageOS 14.1 that was installed before.
Another thing that I can do in the Oneplus recovery is rebooting into fastboot mode, where I should be able to flash the recovery of my choice. Again, my phone confirms I'm in fastboot mode and I try to flash or boot TWRP recovery, but I get the message: 'FAILED (remote: Device not unlocked cannot flash or erase)'. Okay, seems like the bootloader is still locked, so I should just go and unlock it using 'fastboot oem unlock'. This gives the message: 'FAILED (remote: oem unlock is disabled)'. I've been searching around a lot on the internet, and it seems like the only way to enable oem unlock, is in the OS itself in the developer settings. But the problem is, I have no OS and cannot install one because the bootloader is not unlocked... So I'm stuck in this vicious circle.
I've been searching on the internet for hours and starting to lose hope. At this point, I would be happy if I can just have any OS (OxygenOS or LineageOS or something else) running. If I have that, I should be able to take it from there.
Any help is much appreciated. Thank you very much.
Kind regards,
Jeroen
Bump
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Japeroen said:
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Click to expand...
Click to collapse
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
gabytzu338 said:
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
Click to expand...
Click to collapse
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Japeroen said:
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Click to expand...
Click to collapse
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from MSM v2.0 and v3.0 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
gabytzu338 said:
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from 2.0 and 3.1 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
Click to expand...
Click to collapse
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Japeroen said:
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Click to expand...
Click to collapse
It was a typo, I meant v2.0 and v3.0(for oneplus 3). The op3 unbrick guide suggested that the v3.0 might work for oneplus x as well, so I tried that out too.
Anyway, I've done the process a couple more times and the phone booted untill you set the device up, when you are finished it just reboots. I can see the lock screen, I can't bring down the upper bar or enter the settings, if unlocked it prompts me to the first time set up and upon it's completion the phone reboots. I wiped cache,data did a factory reset. Now it's back with the recovery menu artifacts and not booting anymore either. I will use that tool a couple more times then I am done until further suggestions from this forum. After all, my life does not depends on reviving it, I was gonna give it to my brother, who shattered his phones' touchscreen, until he repairs his. Thank you again for replying, no need to reply to this, unless it can help my case.
Hello, I have bought and sold a few phones and flashed custom roms, run adb and fastboot etc. So although I class myself as a noob I do have some experience.
Well I recently bought a Huawei Enjoy 5 that will not boot into Android thinking it would be a nice little project, the seller said he tried to flash ios onto it and in the process deleted the system files.
It will boot into the bootloader and stock recovery and I can use adb and fastboot. If I just press the power switch it will boot to a splash screen and stop.
The bootloader is unlocked.
The model is Huawei TIT-TL00
The Build Number is TIT-TL00C01B133
I can't find a vendor country but assume it to be UK or EU.
There is not an awful lot of info for these phones but I did read they are similar to other models, Honor 5X Play, Holly 2 Plus and Y6 Pro but I don't want to flash the wrong rom.
I have managed to download a few stock roms but not C01B133. I have B122, B132 and B202h which are all for that model. But I read downgrading can hard brick them.
I also read that to flash the rom you have to extract the zip and then look in the extracted folder for the UPDATE.APP file. I can't find that file so think I am doing something wrong but I'm not sure what.
Any help would be great. If I can just get the UPDATE.APP file I would try to flash the rom but I don't know where to look.
Many thanks
Amazingly I managed to flash a Rom on this tonight. B203 official Rom. Extracted all the files and although they looked nothing like the files everyone describes I installed the dload folder onto the sd card and gave it a go. It flashed a Chinese Rom with all sorts of bloatware but no Google so I assume it is for the Chinese market. And the time on the screen was Chinese time. Luckily there was an English option to select so I spent some time setting it up. However it won't recognize any SIM and I'm not sure why, but at least it's running Android now.
Unfortunately I couldn't get any further with this because when I installed the rom it relocked the bootloader. So unless someone has any success getting them unlocked then I'm stuffed.?
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
CrustyBurger33 said:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
Click to expand...
Click to collapse
If your bootloader was relocked, encryption and partition checking were enabled again.
TWRP would only cause your phone to register as modified and lock itself...and due to streamlining of a lot of functions, you can't even use the dialer to enter the menu needed.
Best you can do is totally wipe everything on your phone and generate a new android ID. (You have to do this from the actual OS instead of recovery though. Recovery format uses predetermined instructions. The format option from the android settings panel has a different set of instructions and one of them is to generate a new android ID, which includes IMEI)
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
CrustyBurger33 said:
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
Click to expand...
Click to collapse
Android ID is what determines your phone is the phone it claims to be when pinging google services.
Move any files you want to keep to somewhere safe. Format your phone, android will push you a new id number. It won't fix your IMEI, but it'll keep your phone from being absolutely useless in the process.
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
ninjasinabag said:
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
Click to expand...
Click to collapse
I tried everything you said, reset everything, still no IMEI, and even if the Android ID is different it hasn't really changed anything. Just to be clear, when I flashed the stock ROM earlier, everything worked as intended apart from the SIM card (which doesnt work at all) and the WiFi (which keeps dropping after 5 seconds of connection). Those problems persist even now.
Guess I'll be messing around with the SMT mode in MSMDownloadTool since I've already lost my IMEI, see what I can do from that. If there's anything I do actually end up finding out, I'll post it on xda.
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
CrustyBurger33 said:
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
Click to expand...
Click to collapse
Nice! If everything is working properly besides the IMEI at this point, there's a couple of PC applications you can use.
I'd recommend write dual imei, not gonna post a link since IMEI fudging is against the rules (even if you're just trying to repair your IMEI)
Use the IMEI that's on your device sticker or on your phone packaging specifically.
Either way, hoping you get your phone back up to 100%.
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Honestly, check with OnePlus if you're under the 1 year warranty window. This sounds like an issue that can really only be fixed with a replacement device.
CrustyBurger33 said:
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Click to expand...
Click to collapse
Hi I have a similar problem.. My phone oneplus 8t is stuck in 'SMT Download failed error' mode. I was tryimg out custom roms which has caused this. My phone says can only be fixed via SMT Download mode. Can you help me out using the SMT download mode? I have tried MSM Tool normally to unbrick my phone but it doesn't work.
hello @nightfury04
If you have a Oneplus 8T you have to download the appropriate MSMDownloadTool (specifically for it) and make sure the version is correct too. Is your phone global/ locked to a carrier?