Database Info

Hard bricked my OnePlus One by just rebooting it, help! [5$ REWARD]

I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.

Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.

First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English

sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)

Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.

sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers

MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.

I have same thing did it work
I am just wondering if u managed to fix it.

I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/

Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.

install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers

My phone is not being recognized, bricked phone.

Hi! Today I was trying to update my 1+6 to Android 10. I always make a wipe in my phone and later I flash the zip of the OTA. Well, in this case, my phone doenst want to turn up on recovery mode and I can't make anything. I can enter to fastboot mode (to use msmdownloadtool) and my phone there is in cmd fastboot devices, but not in msmdownloadtool. I have installed all the drivers,I have used ALL IN ONE TOOL, I have changed the usb ports but my phone is not in device manager on windows. It is frustating and it never happened to me.
Sorry for my bad english, and thank you for reading!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Use msndownloadtool, but you're doing it wrong, you need to get in download mode in order for msn to work, to do that you need to unplug any cable from your phone and shut down your phone, connect a cable to your pc, hold vol up in your phone, plug in cable from PC, nothing is going to pop up in your phone but you can hear a sound in your pc, now you can use msn tool to reinstall oos, let me know if i helped you out

Use this method??
Hi if you are able to go to fastboot then just download fastboot Rom for Android 10 and flash it through fastboot.
If you get problem in flashall.bat then just edit that in notepad and delete -w and save that file then try flashing again. Once done it will boot into stock recovery, erase all data and then reboot. everything will work fine

J0nhy said:
Use msndownloadtool, but you're doing it wrong, you need to get in download mode in order for msn to work, to do that you need to unplug any cable from your phone and shut down your phone, connect a cable to your pc, hold vol up in your phone, plug in cable from PC, nothing is going to pop up in your phone but you can hear a sound in your pc, now you can use msn tool to reinstall oos, let me know if i helped you out
Click to expand...
Click to collapse
No.. I hear the sound and my phone is in download mode, but doesn't appear on devices manager of windows. I don't know what happened. The msmdownload is on blank, no devices are listed in

rahulbhola123 said:
Hi if you are able to go to fastboot then just download fastboot Rom for Android 10 and flash it through fastboot.
If you get problem in flashall.bat then just edit that in notepad and delete -w and save that file then try flashing again. Once done it will boot into stock recovery, erase all data and then reboot. everything will work fine
Click to expand...
Click to collapse
Hi! I get problem with flashall.bat, but when I opene it on Notepad and deleted the "-w" It says me "cannot load logo.img" or something like that jajajaj.

Marcos2310 said:
Hi! I get problem with flashall.bat, but when I opene it on Notepad and deleted the "-w" It says me "cannot load logo.img" or something like that jajajaj.
Click to expand...
Click to collapse
You're not using msn you're using the fastboot one
Try this one instead this is the msntool, it will restore your device to life
https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109

J0nhy said:
You're not using msn you're using the fastboot one
Try this one instead this is the msntool, it will restore your device to life
https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Click to expand...
Click to collapse
Nop, the problem is that my phone is not being recognized anymore by the tool..

Marcos2310 said:
Hi! I get problem with flashall.bat, but when I opene it on Notepad and deleted the "-w" It says me "cannot load logo.img" or something like that jajajaj.
Click to expand...
Click to collapse
Did you tried without deleting the -w

Marcos2310 said:
Hi! Today I was trying to update my 1+6 to Android 10. I always make a wipe in my phone and later I flash the zip of the OTA. Well, in this case, my phone doenst want to turn up on recovery mode and I can't make anything. I can enter to fastboot mode (to use msmdownloadtool) and my phone there is in cmd fastboot devices, but not in msmdownloadtool. I have installed all the drivers,I have used ALL IN ONE TOOL, I have changed the usb ports but my phone is not in device manager on windows. It is frustating and it never happened to me.
Sorry for my bad english, and thank you for reading!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

Marcos2310 said:
Nop, the problem is that my phone is not being recognized anymore by the tool..
Click to expand...
Click to collapse
Try with different cables, your cable might be the problem

Any update?

help me！

When I tried to install Android 12 beta2 for my 4a, I accidentally deleted the boot file, which caused my phone to go black. There was no response when I pressed the power button, and the bootloader was not displayed. I connected my 4a to the computer via usb, and the device manager showed QUSB_BULK_CID:xxxx_SN:xxxxxxxx. How can I repair my phone.

accidentally deleted???????
i mean how did you just wiped boot partition or flashed wrong boot image
please explain so that i can help you.

[email protected] said:
accidentally deleted???????
i mean how did you just wiped boot partition or flashed wrong boot image
please explain so that i can help you.
Click to expand...
Click to collapse
My English is very poor, use google translation, please forgive me. I’m not sure if I deleted something. I unzipped the image package to platform-tools and ran flash-all.bat. I still have an error. I didn’t put the phone in the boot loader state but the system state. . When I ran flash-all.bat, the phone went black for an instant, and then there was the situation I said, I couldn't boot up, the screen was completely black, and I couldn't enter the boot loader.

speak in native language i will use google translate.
first thing try to connect your phone to pc {windows} and go to devices and printer in control panel. and see if some thing shows up like unknown device in it.

[email protected] said:
speak in native language i will use google translate.
first thing try to connect your phone to pc {windows} and go to devices and printer in control panel. and see if some thing shows up like unknown device in it.
Click to expand...
Click to collapse
I connect the phone to the pc, the device manager shows this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

so, good news your phone is alive.

[email protected] said:
so, good news your phone is alive.
Click to expand...
Click to collapse
Really？, what should i do

now try to get into bootloader mode and flash boot image of 12beta2 using fastboot flash boot.img

[email protected] said:
now try to get into bootloader mode and flash boot image of 12beta2 using fastboot flash boot.img
Click to expand...
Click to collapse
I can't enter the bootloader, this is a problem

[email protected] said:
now try to get into bootloader mode and flash boot image of 12beta2 using fastboot flash boot.img
Click to expand...
Click to collapse
When I press the power button, the phone screen is completely black and nothing happens

wait brother i have to look up. may be you have hard bricked it. but worry not i am working to find solution just be online for a while.

[email protected] said:
wait brother i have to look up. may be you have hard bricked it. but worry not i am working to find solution just be online for a while.
Click to expand...
Click to collapse
OK i am online

can you send me link of 12beta2 file you flashed and you device full name.
is it pixel 4a 4G or pixel 4a 5G.

is pixel 4a.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
[email protected] said:
can you send me link of 12beta2 file you flashed and you device full name.
is it pixel 4a 4G or pixel 4a 5G.
Click to expand...
Click to collapse

which one you flashed 4G or 5G and which method you used

my phone is pixel 4a 4g and flashed 4g

I think my situation is the same as his situation

ok, bro just listen :- your phone is hard bricked.
next:- to recover your phone just use qualcomm edl tool.
here is the video to help you with.
press like if i helped thanks this works 100%

[email protected] said:
ok, bro just listen :- your phone is hard bricked.
next:- to recover your phone just use qualcomm edl tool.
here is the video to help you with.
press like if i helped thanks this works 100%
Click to expand...
Click to collapse
OK I am watching

[email protected] said:
ok, bro just listen :- your phone is hard bricked.
next:- to recover your phone just use qualcomm edl tool.
here is the video to help you with.
press like if i helped thanks this works 100%
Click to expand...
Click to collapse
I can't find pixel 4a firehose

Nokia 1.4 TA-1322 Help

Hello everyone, I need some help.
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time (Source: https://www.nokia.com/phones/en_int...-reboot-my-smartphone-when-its-not-responding ).
When my phone turned on again I was happy till the next restarting of my phone. My nokia get Stucked in a Reboot Loop.
Screen lights and when Android GO Logo appears it turns off again and again.
I tried to flash my phone using QFIL Tool but there was unsolved issue of Android ADB Interface driver. The QFIL Tool couldn't detected my device. Mybe it needed different keys combination when connectiong it to PC to boot.
QFIL Tool source: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Than I unlocked bootloader using this command:
Code:
fastboot oem unlock-go
I thought it was boot or recovery fail and by the reason I downloaded the firmware from alien9firmware
Source: https://alien9firmware.com/index.php?a=downloads&b=file&id=1325
Because QFIL Tool did not work I flashed boot and recovery via ADB. I moved these two .img files to disk C and ran the following commands
Code:
fastboot devices
fastboot reboot bootloader
fastboot flash recovery c:\recovery.img
fastboot flash boot c:\boot.img
fastboot reboot bootloader
fastboot erase cache
fastboot reboot
Disconnect device
You guess what do you think guys happen
My nokia was still stucked in reboot Loop.
Than I googled smartphones with same Core Qualcome QM 215 and downloaded Nokia 8 and Nokia 6.2 TWRPs from twrp official website.
Source: https://twrp.me/Devices/Nokia/
ADB thrown me an error when I tried to flash Nokia 8 TWRP. "The file is too large and blablabla..."
Then I tried to flashed twrp-3.6.0_9-0-SLD_sprout(nokia6.2) with no errors.
I have never seen anything like that. When I press to "Power button + Volume down" buttons my phone shows the stock recovery again which has no matter.
Then I gooled so many times I and I made a decision that every smartphone with Qualcomm QM215 core has absolutely same bugs.
There are smartphones with this terrible Processor:
Smartphones with Qualcomm Snapdragon 215 processor
List of smartphones that works with Qualcomm Snapdragon 215 processor inside.
www.kimovil.com
Than I found this video. In this video he used dryer and it worked. Unfortunately I have not dryer and... It may works on our devices too, Who knows...
Than someone told me to use MiFlash tool to boot my device. I faced another problem the firmware backup was missing the boot_lock.bat file. I had to download Xiaomi Kenzo global firmware to copy and modify the .bat files to my firmware backup. That trying became my night mare. I accidently erased Bootloader.
Today I was searching how connect How to a connect phone with erased bootloader to pc and I found this:
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Than I connected my phone to pc via usb and opened Device manager. There appeared QHSUSB_BULK device missing driver.
Then I found the driver here: https://fixfirmware.com/qhsusb-bulk-driver/
At least I managed to connect my device to pc again. And now QFIL Tool detects my phone.
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?

Oleg69 said:
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Click to expand...
Click to collapse
Try it

optimusodd said:
Try it
Click to expand...
Click to collapse
I have downloaded the firmware but there is not prog_emmc_firehose.mbn in the archive
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Oleg69 said:
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time
Click to expand...
Click to collapse
When it's still under warranty ,why didn't you claim it ?

optimusodd said:
When it's still under warranty ,why didn't you claim it ?
Click to expand...
Click to collapse
It was gifted to me from abroad. You know...

S
Oleg69 said:
It was gifted to me from abroad. You know...O
Click to expand...
Click to collapse
So what was your end result because I'm currently in bootloop with an unlocked bootloader as well but not having much luck with many of the same avenues you spoke of.. anyone?

Absolutely no luck, you gotta take your phone to the service center or buy a new one as I did (another brand)

Absolutely not.. I refuse. If it's an android, there's a way. Thank God this is simply one of 8 phones I've currently got

Does unlocking the bootloader of this device put the device in boot loop. I want to unlock the bootloader coz I want to install custom ROM. Anyone tell me how to unlock the bootloader of this device without putting the device in boot loop.

Question Need some help unbricking (solved)

I bricked my OP9 doing some stuff today. It will not turn on, access bootloader, or anything.
When I plug it into my computer, it makes a connecting sound, waits 10 seconds, then disconnect sound, then repeats the process.
I tried using MSM Tool with the tmobile one I found online (this is a tmo device), and when it makes the connect sound it does show up in MSM, but when I hit start it says downloading firehouse binary or something, then this happens... Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Maybe phone is not fully off? I usually fix the error in the first post by holding the power, volume up and down (keep holding sometimes upto 40 secs) until it reboots in bootloader then power off and try fashing again while holdin volume up and down only

If your device is a T-Mobile, did you use this MSM package?
LINK
Maybe check the instructions here ...

t-ryder said:
If your device is a T-Mobile, did you use this MSM package?
LINK
Maybe check the instructions here ...
Click to expand...
Click to collapse
Yes I have done all of that, same issues.

orangekid said:
Yes I have done all of that, same issues.
Click to expand...
Click to collapse
Did you use the original data cable or a good quality data cable (no eBay crap)? Did you try all USB ports on your PC? Cable and port is the same as you usually use for flashing devices or this device?

t-ryder said:
Did you use the original data cable or a good quality data cable (no eBay crap)? Did you try all USB ports on your PC? Cable and port is the same as you usually use for flashing devices or this device?
Click to expand...
Click to collapse
Yes I have literally done all of that. I think I may have figured out a solution using the indian OP9 Pro MSM and modifying the XML for settings.
This appears to be a known issue with very little recourse, hopeuflly this works.

ya the Indian OP9 Pro MSM worked, now just getting back to original firmware.

orangekid said:
ya the Indian OP9 Pro MSM worked, now just getting back to original firmware.
Click to expand...
Click to collapse
Hey! I have a similar problem "Sahara communication failed". At 18 seconds I have the same error. I see that MSM OP9PRO helped you, but I have the same problem with it. Please explain in as much detail as youcan

Use this guy's MSM Tool. Deselect sha256 and select Use Light Firehose. Make sure you have India selected.
It should get you back to stock Global OP9 ROM.
Restore your Global OnePlus 9 LE2115 via MSM
For those with model LE2115 having trouble restoring their device, follow these steps: https://easyupload.io/xgw3x5 NOTE: Link expires April 26, 2022 M1-1) Download the above file in this post and extract it to the same directory as your MSM...
forum.xda-developers.com

I will try it.

Param preload failed...

Pink Knight said:
Param preload failed...
Click to expand...
Click to collapse
Can you give a screenshot?

Urgent! Help with the MSM tool (stuck in Param preload)
Hi Please help! I have downloaded everything in this link: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 It contains "guacamole_21_O.07_190512_repack" and "L2 drivers" I have followed the mega unbrick guide...
forum.xda-developers.com
IT'S WORKED! JUST INSTALL THE LATEST QUALCOMM DRIVERS. I LOVE YOU GUYS!!!

Pink Knight said:
Urgent! Help with the MSM tool (stuck in Param preload)
Hi Please help! I have downloaded everything in this link: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 It contains "guacamole_21_O.07_190512_repack" and "L2 drivers" I have followed the mega unbrick guide...
forum.xda-developers.com
IT'S WORKED! JUST INSTALL THE LATEST QUALCOMM DRIVERS. I LOVE YOU GUYS!!!
Click to expand...
Click to collapse
Funny that is what I was about to recommend, qualcomm drivers and USB port. Awesome man so glad it worked for you.