Database Info

Oneplus One unbrick issue?

Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help

Tiic said:
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Click to expand...
Click to collapse
How your device got bricked?
Which recovery tool you tried?

Mr.Ak said:
How your device got bricked?
Which recovery tool you tried?
Click to expand...
Click to collapse
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool

Tiic said:
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Click to expand...
Click to collapse
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps

Mr.Ak said:
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Click to expand...
Click to collapse
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM

Flashing 8974_msimage.mbn nin a loop.... you're not the only one with this problem. I couldn't find a solution to this problem so far. Have tried fresh installs of Windows XP and Windows 7 and drivers installed in Test Mode without success. Please report back once you could figure out what's wrong.

Tiic said:
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Click to expand...
Click to collapse
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.

Mr.Ak said:
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Click to expand...
Click to collapse
Just redownloaded the tools and tried again.
Still the same issue, i also tried the color os toolkit like you suggested.

I have the same issue too, keep installing 8974_msimage.mbn again and again.

I'm still open for sugestions since the issue is still there

Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.

kthejoker20 said:
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
Click to expand...
Click to collapse
Although it is correct that you must run it as admin, this isn't the issue at all. There are phones that appear to be broken beyond the point where you can fix it with software.

MrBrainstorm said:
Although it is correct that you must run it as admin, this isn't the issue at all..
Click to expand...
Click to collapse
Yep, i always run tools like this as admin, the issue is something else in this case, but i wouldn't know what exactly

I may have found a solution/work-around to the problem described (in case anyone's still trying to unbrick a OPO after all this time). I must warn, however, that I really have no idea what I'm doing as I'm new to all of this, and have blundered through with no real understanding of what's going on, so pay heed at your own risk. It uses Qualcomm's QFIL program and Zyxxeil's OPO unbricking tool. I want give detail in describing the steps involved, so this will be fairly long.
***background***
My 64GB OPO has for the past couple of months almost always failed to get past the first 6-7 seconds of booting, and powered off before reaching the Cyanogen animation. It did the same when booting into fastboot and recovery, and at some point it stopped being able to access recovery at all. Very rarely it would boot, but pressing the power button while it was on would cause it to crash a few seconds later. I discovered that it would consistently boot properly if volume up were tapped while holding down the power button before it vibrates and the OnePlus logo appears, but this fix simply stopped working recently, and so it became impossible to turn the OPO on. Before giving up on it, I decided it would be worth trying the hard unbricking tool based on the ColorOS installer by Zyxxeil. However, I had the problem where the tool continually repeats the step of flashing 8974_msimage.mbn without progressing any further, to which nobody ever seemed to find a solution. I may have found a way to get around the problem, however.
Even though the procedure seems to have worked, the phone still shuts down after a few seconds as it did before (so I suspect my device has a hardware problem, possibly with the power button, and there's nothing that can be done for it). This means that I can't confirm that the fix actually works, but only that it appears to have worked. What it did was:
1) unbricked the phone - it probably wasn't even bricked before, but it definitely was after the installer hung on 8974_msimage.mbn ; it wouldn't respond to the power button at all afterwards. Applying the workaround allowed it to show signs of life again.
2) installed the COS11 fastboot. I'm not sure and can't tell whether the rest of the OS is there or intact, but the fastboot logo has changed from the newer small one to the bigger one from older versions.
***the problem***
The standard method for dealing with a hard-bricked OPO is to use the ColorOS tool as described in the "[GUIDE] [UNBRICK] Unbrick Oneplus One" thread and then flash Cyanogen, or to use Zyxxeil's tool which goes straight there. A common issue in both is that after pressing start, the tools repeat the step of flashing 8974_msimage.mbn , seemingly disconnecting the phone each time, and never progressing beyond that. This happened to me as well. This will happen if the tool is not run as an administrator, but for some people the same problem is seen even if it's run as an administrator. To the best of my knowledge, nobody has posted a solution to this problem, but some have suggested using alternative methods such as using QFIL (which I have gotten to work) or MiFlash.
***potential solution***
From what I understand, QFIL does the same thing as the unbricking tool, only not automatically. I directed it to use the files provided by Zyxxeil's tool, and it was then able to do something that unbricked the device as described above. This is what I did: (all on Windows 10, *not* using the original cable)
Required files:
1) Obtain the Qualcomm QDLoader driver. I used the the Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64 driver from Zyxxeil's tool's thread (page 5, #48).
2) Download Zyxxeil's tool. I used the 64GB version. Extract DRIVER.iso and run setup.exe as described. I'm not sure whether this actually did anything and presume manually installing the driver in 1) overrides this, but I'm including this for completeness.
3) Download QFIL version 1.0.0.2 . I originally used 2.0.0.5 , but this did not work (it produced the error "unable to read packet header. only read 0 bytes", to which the recommended solution was to use an older version). This can be run from the extracted folder. Open it once, and then close it again - it seems not to behave properly the first time it is run.
Preparation:
4) Create a new folder, for instance on the desktop, and give it a short name. Copy and paste (or just move) the contents of the "OnePlusRestoreTool" folder from Zyxxeil's tool into here. This step is because QFIL supposedly doesn't like long folder names or locations (I'm not sure whether this is true or not but there's no harm in making sure).
5) Install the QDloader driver: (the PC may need to be disconnected from the internet for this stage, I think Windows may try to automatically download and install incorrect drivers)
>Open device manager, then plug the OPO into the computer. It should come up after a few seconds under "Ports (COM & LPT)" as something like QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Mine originally showed up as "Quectel QDLoader 9008". If it comes up as a malfunctioned device ("Unknown USB Device") under "Universal Serial Bus controllers", try holding the power button on the OPO down for a few seconds, or holding it down for a few seconds at the same time as volume up. If it's still not recognised, try rebooting the PC and repeating this step.
>Right click on the device as it appears in device manager, select "Uninstall device", tick the box saying "Delete the driver software for this device", and click on "Uninstall".
>The OPO will disappear from device manager. Unplug and then replug it into the PC, and after a few seconds it should be recognised again, perhaps as "Unknown USB Device" again, requiring the same procedure as above. It should now show up as QHSUSB_BULK under "Ports (COM & LPT)"
>Right click on the device and select "Update driver", then "Browse my computer for driver software". Paste in the file path for the folder containing the driver as downloaded above, which will be called "20561190_ed08f7139a2028da454a6668162f44ac311facc0" if using the driver specified above. Ensure "Include subfolders" is ticked, and click on Next. This should install the driver, and because it's signed, it shouldn't present problems often encountered in this stage. Your device should now be called "Qualcomm HS-USB QDLoader 9008", with (COM#) after it.
Fix:
6) Restart the PC, leaving the phone plugged in. Open device manager again. At this point, if it is detected as a malfunctioned "Unknown USB Device", do not try to remedy it as described above - leave it as it is. This is exactly what happened in my case.
7) Run QFIL.exe as an administrator. I don't know whether this is actually necessary to run as an administrator, but seeing as problems arise in the normal methods from not doing so, it seems sensible. If the device is listed as "Unknown USB Device", then QFIL should say "No Port Available".
8) In QFIL, click on "Browse" in the "select programmer" section. Navigate to the folder where the contents of Zyxxeil's tool were copied/moved to, and open "prog_emmc_firehose_8979.mbn". Lower down, click on "Load XML", which should give you three files to choose from. As I couldn't fully boot my OPO afterwards I don't know which one is most appropriate, but I have tried the procedure with each and it worked for all of them. Perhaps start with rawprogram_unsparse.xml and if that doesn't work try the other two. Click Open, then select patch0.xml , then click Open again.
9) Paying attention to the QFIL window, hold down power+volume up until the text changes from "No Port Available" to "Qualcomm HS-USB QDLoader 9008 (COM#). Incidentally, this will also cause the device to change from "Unrecognised USB Device" to "Qualcomm HS-USB QDLoader 9008 (COM#)" in device manager. I believe that this step starts "Qualcomm's debugging mode" as explained in Zyxxeil's thread, and this is necessary for the process to work.
10) Click on "Download" (below "Load XML"). QFIL should do its thing, and if nothing has gone wrong the phone might be unbricked at the end of the process. Disconnect from the PC and see if it works.
In my experience, where this step did not work it gave one of two errors:
"unable to read packet header. only read 0 bytes" - this happens on the newer version of QFIL, which is why I used the older one.
"unable to download flash programmer using sahara protocol" - this was the troublesome one. I believe it means that the phone is not in Qualcomm's debugging mode. This would probably be the case if, for whatever reason, the PC recognised the phone immediately as Qualcomm HS-USB QDLoader 9008, and so it wasn't necessary to hold power+volume up for the PC to recognise it properly. In my case the program ran properly the first time but was interrupted because I hadn't transferred all of the right files to the target folder. After I had done this and tried again, it gave this error. I fixed this by holding down power+volume up, while the device was recognised, until the PC made a sound indicating something had been plugged in. The next attempt to download was successful.
If the procedure doesn't work properly, it might also be worth using one of the other two XML files mentioned in step 9.
*** ***
Anyway, after hours of searching and trial and error, this unbricked the phone, with it becoming responsive once more to button presses, despite still having the original problem of powering down during boot. It seems to have the CM11 fastboot as expected, and I was able to have my PC recognise it in the short time it stays on using fastboot devices. Other than that, I'm afraid I don't know how successful this was, or how successful it would be for other people. I hope this is useful nonetheless!

hi follow this guide https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

T-Mobile OnePlus -- Hard (HARD) Brick

Sorry for lack of details, but I'm not sure it will help anyway. Feeling pretty bad right now.
T-Mobile Oneplus 7 Pro. 256GB version.
I wanted to go to stock OxygenOS after buying the branded version two weeks ago.
I successfully got T-Mobile to unlock my SIM, and got OnePlus to send me unlock code for my bootloader after a week.
Successfully unlocked via fastboot. Tried several times to flash TWRP and no success using fastboot.
Tried MSM-Downloader from guacamole_21_O.07_190512_repack and successfully held volume both buttons to connect to the PC. MSM-Downloader said it was successfully connected.
I cannot find the exact error message I got from MSM-Downloader, but it said it didn't match plus another error message. At that point, my heart sank.
USB Device Not Recognized keeps popping up on windows again and again, while the connect sound plays. Doesn't matter if I hold down the volume buttons or not.
Can't get into qualcomm EDL mode. My guess is I hosed my boot and now it restarts endlessly when connected to anything at all.
Is this the end of my journey? I did tons of research on the best phone and the best deals available to save money, but looks like I played myself here with lack of caution.

I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.

bmg1001 said:
I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.
Click to expand...
Click to collapse
I cannot get into EDL. Regardless of what buttons I press (I am holding both volume buttons down in excess of 5 seconds) when connecting USB to the phone, Windows makes the "connect" sound endlessly and the driver isn't recognized.
If I can get into EDL, I will definitely try the above.

Do you have the proper drivers installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.

bmg1001 said:
Do you have the proper URL installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.
Click to expand...
Click to collapse
Ok. I may be making progress thanks to your help but do have some hurdles I can see.
I do see the device when I hook it up to another computer. It shows up as Unknown USB Device (Device Descriptor Request Failed).
When I go to device manager to manually update the driver, and browse to the location I extracted the CAB file into, I see lots of devices to choose from, but the Qualcomm driver cab file list does not show "Qualcomm HS-USB QDLoader 9008" as an option. I see many Qualcomm USB Composite Devices in the list but none I have chosen seem to work (install fails).

Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?

bmg1001 said:
Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?
Click to expand...
Click to collapse
Yes, that is correct. Same cable i used to get into fastboot, etc... The original PC I caused the problems with recognized the device differently (showed up as a Qualcomm device) when I got into EDL with it before.
Edit: First event when plugging it into this second PC under device properties:
Device USB\VID_0000&PID_0002\5&3c8d678&0&2 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_0000&PID_0000\5&1AE39384&0&2
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0xF000FFFFFFFFF000
Present: false
Status: 0xC0000719

I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.

bmg1001 said:
I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.
Click to expand...
Click to collapse
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?

unluckyoneplus7pro said:
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?
Click to expand...
Click to collapse
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
I'll try there next. Can't seem to get any of my windows machines to recognize the thing.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.

unluckyoneplus7pro said:
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.
Click to expand...
Click to collapse
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.

razorshiv said:
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.
Click to expand...
Click to collapse
That's pretty cool. Makes the whole process much less stressful.
Got it up and running with international version. Now to see if I can get LOS installed. My sincere thanks to all and apologies for crapping up the board with my panic. I thought I had really screwed up, but it appears it was just stuck in EDL mode and needed a hard (HARD) reset.

Hey man, thanks for the donation. Glad you were able to get your phone up and running!

Holy Sh*t man. I know 5 bucks ain't much but I wanted to thank you so much. I thought I was fukd

Redmi note 6 pro self-bricked overnight - EDL flashing fails

Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
It doesn't turn on, can't be hard-reset, can't go to recovery/fastboot, only EDL mode via test points. Last time (April 2019) it also happened overnight, but I was able to restore it to proper function by EDL flashing it using QFIL and a modified programmer (prog_emmc_firehose_Sdm660_ddr.mbn). The rom I flashed back then was the most recent at the time, Redmi Note 6 Pro Global V10.3.2.0.
This time was a bit different in that I was actually able to hard-reset it at first (it vibrated and seemed to boot), but it then got stuck on the mi-logo during startup. I wasn't able to get it into recovery, but the fastboot screen came on ok. However, the phone didn't register on the pc and I wasn't able to actually send any fastboot commands to the phone, nor flash roms. I don't think fastboot was actually working which might be pointing to chip issues... Unfortunately...
After a few attempts at hard-resetting and failing recovery, I think the battery actually ran flat. Now it is dead-dead. Doesn't react at all, doesn't do anything, just like back in April last year. When I plug it in to my pc it delays for about 10 seconds and then shows up as if it's in EDL mode (Qualcomm HS-USB QDLoader 9008) but it's not really flashable - it doesn't react to QFIL correctly.
I then pulled the phone apart, shorted the EDL points and got it into 9008 mode immediately after plugging in the usb cable, no 10 sec delay doing it this way. However, when trying to flash the phone now it fails and reports a generic 'Firehose FHLoader error'... Please see log attached in this google drive link: drive.google[dot]com/file/d/1nj_0f95qLnLHqIgTEODmilY9ObmAkowz/view
Apologies for the link - I don't have 10 posts yet...
The most recent miui rom for the phone now is "tulip_global_images_V11.0.4.0.PEKMIXM_20200514.0000.00_9.0_global" and that's the one I primarily tried flashing. I also tried the one I had success with last year (fearing though it might re-brick due to the roll-back protection) but that didn't work either, same error. I also tried flashing using different USB cables, all high quality, but the error remains. I also tried it using a laptop, just to rule out windows issues. I've also tried the tips for resolving QFIL errors mentioned on the hovatek forum: forum.hovatek[dot]com/thread-30141.html but with no luck there either.
Have you guys got any ideas how I might proceed? Any tips I could try?
I am kind of resigned to this perhaps being a hardware issue, perhaps this particular chip has failed and that is why not even EDL mode is working properly. But I just wanted to ask the community if you had any ideas. If not, then it's not an expensive phone. However, I would love fixing it if I could, my wife loves it...

I suggest to first short the pins then open the flash tool and try to flash the factory rom. The programmer file will be inside the extracted rom directory, select that and proceed. If it does not work try installing Qualcomm driver and retry .

Talix said:
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
Click to expand...
Click to collapse
I'm sorry for re-opening an old thread, but I'm in a really similar situation.
My Redmi self-bricked, and I don't have any ideas since I have already tried a flash in ELD mode but the Flash Tool says that it's not able to receive the hello packet from the phone.
Have you been able to solve the issue in some ways?
Ps. Here's my post, in case you need further informations

2.0.4DJB TCL 10 Pro Firmware Update

This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch

KaptinBoxxi said:
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
Click to expand...
Click to collapse
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.

JayTM said:
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
Click to expand...
Click to collapse
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.

KaptinBoxxi said:
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
Click to expand...
Click to collapse
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.

JayTM said:
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
Click to expand...
Click to collapse
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to

KaptinBoxxi said:
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
Click to expand...
Click to collapse
Good luck to you.
I contacted TCL support myself with no luck. They immediately put my case in pending close status.

Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.

JayTM said:
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
Click to expand...
Click to collapse
I'll check it out. If its possible to view the code in a tool like dnSpy or extract files from the exe with 7zip, its possible to use with our device, i'm sure as long as the commands are similar

Well you're in luck as it is just a .bat file program simple notepad++ will do.

I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.

Tech101yt said:
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Click to expand...
Click to collapse
Have had the phone for less than 6 months and I'm already having LCD issues. When the display is off, just sitting on a table or something, it'll flash white randomly like its getting an electric signal at random. Its nothing I did. I've never hard dropped the thing. Everywhere I go pretty much is carpeted except work. If manufacturer warranty doesn't cover me, I'll stop recommending the phone to people
I actually switched to an Essential Phone recently. Way better experience, way cheaper too. I have around a dozen of them anyway and have been selling em on swappa (dunno if I'm allowed to say that here, but oh well) lol

@KaptinBoxxi Sounds like you have Ambient Display on for notifications.

mschoolbus said:
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
Click to expand...
Click to collapse
Nah its turned off. It flashes like a broken LCD would look. All snowy and stuff like an old TV. Its not notifications, just a bad LCD

that sucks... could try reseating the screen's ribbon cable :-/

can anybody share the full update rom about android 11?

top170 said:
can anybody share the full update rom about android 11?
Click to expand...
Click to collapse
I don't believe anyone has Logcatted the update process yet to get the firmware, but on the subject of this post, I do have some updates
I was digging through my Logcat from january and realized I missed something massive. I have yet to figure out the URL structure, but I have all the info for it.
So when you go to the following link, it gives a bunch of errors of missing info
https://g2master-sa-east.tclclouds.com/notify_new.php
For the firmware here on this post at least, each value from my device is
Code:
id = 0156260
curef = T799B-2ALCUS11
vk = 741ace917e3527af81412ca93b0fcce2de04a264
salt = 1611977254070885419
fv = 4DJ1LM10
tv = 4DJBLMB0
op = 1000
status = 999
mode = 2
cltp = 10
type = firmware
formatted from logcat
reportContent= {"id":"0156260","salt":"1611977254070885419","curef":"T799B-2ALCUS11","fv":"4DJ1LM10","tv":"4DJBLMB0","mode":"2","cltp":"10","type":"Firmware","op":"1000","status":"999","vk":"741ace917e3527af81412ca93b0fcce2de04a264"}
no matter what, I get the errors on the web page

Question SOLVED EDL Breakdown Loop Help Request

Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?

Raccroc said:
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Click to expand...
Click to collapse
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.

mattie_49 said:
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
Click to expand...
Click to collapse
So, that actually stablized the driver connection; however, it also brought be right back to Sahara Communication Failed.
Progress (I hope)!

Thread '[Solved!] MSM Download Tool Issues - Sahara Communication failed, phone exits EDL' https://forum.xda-developers.com/t/...communication-failed-phone-exits-edl.4245913/

Thanks for the info and links. I am on Windows 11, which seems to be an issue for some. I will see about trying it on my wife's v10 laptop tonight and see if that changes anything.

Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.

Raccroc said:
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Click to expand...
Click to collapse
There is a global msm with target id india

[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com

rizzmughal said:
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...

Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
I know thats when ur phone was hard bricked now this one will work for u to get back to global 2115

Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
These are def not viruses and windows has warned me of these as well on Win 11. Just accept and install. These are legit af

Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/

Raccroc said:
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Click to expand...
Click to collapse
Good deal. That's all we here for neway is to help one another.