Database Users

[Q] - Help with seemingly perma-bricked LG G2 (VS980)

Hi all -
Thanks for checking in on my tale of woe. The summary is that I have seemingly nuked my partitions on my LG G2 (Verizon Edition VS980) so that nothing happens when I try to power the device on (literally nothing, no logo, no screen backlight turning on, etc.). In Windows, with some coaxing, the device will appear as a QHSUSB_BULK device (with a yellow exclamation point in Device Manager, and even when I boot into Linux to look at the partitions, they aren't visible.
How I got here:
I was happily running XDABBEB VS980 2.3.0 from http://forum.xda-developers.com/showthread.php?t=2715408 with a few Xposed framework tweaks. Great ROM.
I dirty-flashed XDABBEB's VS982.5 v1.0.0 from http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551 to have a look at the G3 interface. I did a Nandroid backup first, like any good crack flasher
I neglected to read the step in the VS982.5 thread about the fact that this ROM was bumped. I still am not sure what that means.
I played with VS982.5 for a bit, and it didn't really seem like I'd want to use it long term. Also, some of the LG apps didn't seem to work on first try, not sure if that was an additional flash required. (QRemote was what I ran into). Anyway, I thought I'd go back to VS980 2.3.0 for then by just restoring my Nandroid.
Booted into TWRP to restore the Nandroid. It did it's thing.
Upon reboot, the device showed the LG Logo and showed a Security Error in the upper left-hand corner, and sat there briefly, then shut off the screen. (Sorry, I don't remember the precise text, it was in small white letters, several lines' worth of text).
I tried rebooting a couple of different ways, and eventually gave up and followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142
From a Linux Live CD (Specifically an old Hiren's 15.2), I thought I'd followed the instructions correctly. The partitions did show up correctly under /dev/sdk1.../dev/sdk36 or whatever. I did the dd as prescribed with the files.
Then I tried to reboot, and here we are. Apparent hard-brick.
What I've tried since the Linux fiasco.
Rebooting many different ways. (Recovery mode, etc.)
Going back to stock with kdz and tot methods, following this: http://forum.xda-developers.com/showthread.php?t=2432476 . The device is not recognized, probably because the normal USB driver won't load.
Checking to see if it'd show up in adb and fastboot commandline interfaces. No, of course.
Booting back into Linux to try the dd again. No luck. The 30+ partitions don't show up under /dev
Letting it charge, thinking the battery may have died. It has been plugged in long enough that it should be 100%. (I can't tell when the device is on or off any more, because there are literally no indications.). This doesn't seem to have made any difference
Holding the Down button and plugging in the USB port gives the QHSUSB_BULK (Code 28) error in Windows, so at least it's doing something... but not much.
Ideally, of course, I'd like to restore the partitions, get my nandroid written back to the device, and carry on with life. Failing that, I'd like to get the nandroid off so I don't have to spend hours setting up another G2. My mistake for keeping the nandroid on the device - I've never bricked a device this badly, and it's always been recoverable with some googling!
Help!

Mark-7 said:
Hi all -
Thanks for checking in on my tale of woe. The summary is that I have seemingly nuked my partitions on my LG G2 (Verizon Edition VS980) so that nothing happens when I try to power the device on (literally nothing, no logo, no screen backlight turning on, etc.). In Windows, with some coaxing, the device will appear as a QHSUSB_BULK device (with a yellow exclamation point in Device Manager, and even when I boot into Linux to look at the partitions, they aren't visible.
How I got here:
I was happily running XDABBEB VS980 2.3.0 from http://forum.xda-developers.com/showthread.php?t=2715408 with a few Xposed framework tweaks. Great ROM.
I dirty-flashed XDABBEB's VS982.5 v1.0.0 from http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551 to have a look at the G3 interface. I did a Nandroid backup first, like any good crack flasher
I neglected to read the bottom of the VS982.5 thread about the fact that this ROM was bumped. I still am not sure what that means.
I played with VS982.5 for a bit, and it didn't really seem like I'd want to use it long term. Also, some of the LG apps didn't seem to work on first try, not sure if that was an additional flash required. (QRemote was what I ran into). Anyway, I thought I'd go back to VS980 2.3.0 for then by just restoring my Nandroid.
Booted into TWRP to restore the Nandroid. It did it's thing.
Upon reboot, the device showed the LG Logo and showed a Security Error in the upper left-hand corner, and sat there briefly, then shut off the screen. (Sorry, I don't remember the precise text, it was in small white letters, several lines' worth of text).
I tried rebooting a couple of different ways, and eventually gave up and followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142
From a Linux Live CD (Specifically an old Hiren's 15.2), I thought I'd followed the instructions correctly. The partitions did show up correctly under /dev/sdk1.../dev/sdk36 or whatever. I did the dd as prescribed with the files.
Then I tried to reboot, and here we are. Apparent hard-brick.
What I've tried since the Linux fiasco.
Rebooting many different ways. (Recovery mode, etc.)
Going back to stock with kdz and tot methods, following this: http://forum.xda-developers.com/showthread.php?t=2432476 . The device is not recognized, probably because the normal USB driver won't load.
Checking to see if it'd show up in adb and fastboot commandline interfaces. No, of course.
Booting back into Linux to try the dd again. No luck. The 30+ partitions don't show up under /dev
Letting it charge, thinking the battery may have died. It has been plugged in long enough that it should be 100%. (I can't tell when the device is on or off any more, because there are literally no indications.). This doesn't seem to have made any difference
Holding the Down button and plugging in the USB port gives the QHSUSB_BULK (Code 28) error in Windows, so at least it's doing something... but not much.
Ideally, of course, I'd like to restore the partitions, get my nandroid written back to the device, and carry on with life. Failing that, I'd like to get the nandroid off so I don't have to spend hours setting up another G2. My mistake for keeping the nandroid on the device - I've never bricked a device this badly, and it's always been recoverable with some googling!
Help!
Click to expand...
Click to collapse
sorry have you fixed your phone yet?? if not install vmware and slax. using this linux environment helped me. then you can follow the instructions on
http://forum.xda-developers.com/showthread.php?t=2582142

v.konvict said:
sorry have you fixed your phone yet?? if not install vmware and slax. using this linux environment helped me. then you can follow the instructions on
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Thanks for your note - I tried that in step 7 above. (VMware + Ubuntu).

Mark-7 said:
Thanks for your note - I tried that in step 7 above. (VMware + Ubuntu).
Click to expand...
Click to collapse
so you tried with slax?? not ubuntu??

v.konvict said:
sorry have you fixed your phone yet?? if not install vmware and slax. using this linux environment helped me. then you can follow the instructions on
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
v.konvict said:
so you tried with slax?? not ubuntu??
Click to expand...
Click to collapse
Hmm, no, I didn't. I'll try with Slax. It didn't occur to me that the linux distro would make a difference.

Mark-7 said:
Hmm, no, I didn't. I'll try with Slax. It didn't occur to me that the linux distro would make a difference.
Click to expand...
Click to collapse
okay give it a try and tell me how it goes

Okay, I did that (this is a really cool distro, I didn't know about it).
But, sadly, still no partitions showing up.
{
"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"
}

Mark-7 said:
Okay, I did that (this is a really cool distro, I didn't know about it).
But, sadly, still no partitions showing up.
Click to expand...
Click to collapse
on your bottom right look for qhulb usb device and connect it to slax. am sure you can see many partitions on your windows. if you connect it to slax they will disappear from windows and then you continuw with ls /dev/sd*

Yes, I did that (that's what I was trying to show with the little thing down in the lower right - the QHUSB_BULK thing is actually showing up as a USB device rather than flash storage).
I had the SDK1-36 partitions showing up in Linux before - and then I must've done something wrong in the thread that we refer to up above...I did all the DD steps and I think I wiped all the partitions somehow, as even though the QHUSB_BULK device is connect to the VM, it's not giving me the partitions (or asking me about all the auto-mount failures).

Mark-7 said:
Yes, I did that (that's what I was trying to show with the little thing down in the lower right - the QHUSB_BULK thing is actually showing up as a USB device rather than flash storage).
I had the SDK1-36 partitions showing up in Linux before - and then I must've done something wrong in the thread that we refer to up above...I did all the DD steps and I think I wiped all the partitions somehow, as even though the QHUSB_BULK device is connect to the VM, it's not giving me the partitions (or asking me about all the auto-mount failures).
Click to expand...
Click to collapse
in slax it doesnt give the automount failures. okay can you tell me what was happen when you connect your phone to windows no the vmware. if it shows many partitions in windows then you are still okay

Nope, the partitions do not show up in Windows any more either.
(I know what it looked like when it did. Now, it is not recognized as a disk device at all).

Mark-7 said:
Nope, the partitions do not show up in Windows any more either.
(I know what it looked like when it did. Now, it is not recognized as a disk device at all).
Click to expand...
Click to collapse
okay have you tried the tot method. i know your phone isnt showing anything but its worth a try i guess.

v.konvict said:
okay have you tried the tot method. i know your phone isnt showing anything but its worth a try i guess.
Click to expand...
Click to collapse
Thanks so much for trying. Yes, I've tried recovering with both the KDZ and TOT attempts.
TOT method appears to fire up correctly (after the megalock weirdness), but because the device won't mount or load drivers, nothing happens after I hit Normal Flash.

Mark-7 said:
Thanks so much for trying. Yes, I've tried recovering with both the KDZ and TOT attempts.
TOT method appears to fire up correctly (after the megalock weirdness), but because the device won't mount or load drivers, nothing happens after I hit Normal Flash.
Click to expand...
Click to collapse
Sorry bro am out of ideas

I thought I'd update this story to let people know how it ended.
I ended up ordering another LG G2, but saw this thread late one night:
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
I had to make a Windows XP VM to get it running with the HS-USB 9008 mode, but after I did that, I kept getting the "device was not found in dload trying flash programmer" error.
I ended up contacting one of the guys in that thread who did a teamviewer session with some custom build of the b2b support tool, and he was able to unbrick it. He does charge for the service though.
It wiped the phone, but it is back in service now under XDABBEB's 2.3.0.
So now I have a spare LG G2 on its way.
Thanks, v.konvict for all the ideas.

another brick in the wall...
Mark-7 said:
Nope, the partitions do not show up in Windows any more either.
(I know what it looked like when it did. Now, it is not recognized as a disk device at all).
Click to expand...
Click to collapse
I dont think you nuked your partitions in Linux.
I HAVE THE EXACT SAME SCENARIO. Going from xdabbebs vs985 ROM back to the vs980 2.3.0 ROM, clean fash, except I didn't Nandroid it I simply flashed the rom back in under TWRP .
The security error thing came up RIGHT AFTER THAT. And I couldn't get it gone. And finally ended up same as you, computer could see the phone but no partifions. I think that just happen because the battery was dying. You just got yours to what's his name before the battery totally failed :victory:
There something in the hardware didn't like it when we reverted to the former ROM.

I don't think it was a hardware issue - my guess is that it had something to do with the fact that the G3 ROM is a bumped ROM, and I didn't know the difference.
Perhaps if I'd reverted back to 24a bootstack before flashing, all would be good.
But I don't know, and am a bit gunshy to play more.

Mark-7 said:
But I don't know, and am a bit gunshy to play more.
Click to expand...
Click to collapse
I can totally relate. I'm thinking I'll have to replace either the main board or the battery on this unit.

I think mine recharged OK, even in the mostly-bricked state. When plugged into the USB port, something seemed to still be happening (recognized as a driverless USB device)

LG G2 Bricked. Fix it and I'll pay you.

Hi,
I initially soft bricked my LG G2 D801 by clearing everything in TWRP. Tried to fix it, went through a bunch of threads and tried different tools but ended up just screwing it up more, now a hard brick. Currently will not go into download mode or TWRP. In device manager it is listed as "LG Android USB Device". Also will continuously restart unless I go into "recovery mode" where it will go into Demigod crash. I basically give up because I dont know what I'm doing.
My proposal:
I will ship you the phone, you fix it and ship it back to me
I will pay you $50 for your trouble via paypal or check
Any other information you need from me to see if it is unbrickable?

Unbricked my g2 two days ago
Hey pal! I hardbricked my lg g2 d802 two days ago. The screen was dim and dark; I was already thinking about buying a new phone. Now im replying with it lol.
I went basically nuts because i couldnt enter into download or recovery mode
I thought everything was lost but through a tool called "srk tool" I was able to force download mode on the phone. (You have to toggle "nuke download mode")
Furthermore, if you happen to plug the G2 to the PC and come across the phone being recognized as 13 drives, srk tool has an option to unbrick the phone.
It would be great if you unbricked the phone. If you can only enter download mode, flash a stock rom. Ill leave you with the two threads which have guided me:
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 (SRK TOOL thread, download latest version 2.1 and proceed according to your situation)
http://forum.xda-developers.com/showthread.php?t=2797190 (lg flash tool. Download your preferred rom or carrier stock, and flash the kdz freshly)
This is what has worked for me. Good luck

Hey!
Just wondering if you got it fixed. If not let me know. I know how crappy it is just let me know which carrier you have and message me if you want me to try n repair it. I screwed mine up badly after trying to get cyanogenmod to work too once. All I would get is an lg symbol then some texts. But I fixed mine.

cuenta_clon1234 said:
Hey pal! I hardbricked my lg g2 d802 two days ago. The screen was dim and dark; I was already thinking about buying a new phone. Now im replying with it lol.
I went basically nuts because i couldnt enter into download or recovery mode
I thought everything was lost but through a tool called "srk tool" I was able to force download mode on the phone. (You have to toggle "nuke download mode")
Furthermore, if you happen to plug the G2 to the PC and come across the phone being recognized as 13 drives, srk tool has an option to unbrick the phone.
It would be great if you unbricked the phone. If you can only enter download mode, flash a stock rom. Ill leave you with the two threads which have guided me:
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 (SRK TOOL thread, download latest version 2.1 and proceed according to your situation)
http://forum.xda-developers.com/showthread.php?t=2797190 (lg flash tool. Download your preferred rom or carrier stock, and flash the kdz freshly)
This is what has worked for me. Good luck
Click to expand...
Click to collapse
thanks cuenta, i've tried those before and the computer doesnt read the phone so i cant use SRK tools (as far as i can tell anyways), also can't flash because cant find phone. basically ive come up with "im not smart enough to fix this myself" haha. ty for the help anyways.

Fix for everything happen to the os http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Please donate to developer george7565 who find that way to unbrick

amin44 said:
Fix for everything happen to the os http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Please donate to developer george7565 who find that way to unbrick
Click to expand...
Click to collapse
thanks admin44, i'm def not smart enough for this. would rather pay someone $50 to fix it than have a disassembled phone that I cant put back together. =)

It is so easy just need some time and good eyes see some video on yotube how to open it .i do that before 2 month and i think i will need to do it again in futur becuase i love play on this phone i will search for some video that can help you

Can you take a shot of the demigod crash screen?
It's still a soft brick, hard brick is when the phone boots but the screen is black (panel gives light no image)
Can you double check in Device manager does it say something like Qhsusb_bulk?

@dudeimstoked , I've successfully unbricked the deepest of bricks on my G2 (demigod CH). I can help you. Sending you a PM.

Hey, as far as the it recognizing it as something else in download mode or whatever. Right click "this pc" on your file explorer and hit manage, it'll pop up a window and hit device manager then locate the phone and right click it and hit update driver software and hit select from currently installed drivers (could be worded different, doing this off head) and on the left it'll give you some manufacturers/corporations, select google and select on the right the one that has fastboot on it. Now if you don't see google in that list on left, that means you need to download and install the google usb drivers. This will help the computer recognize that it's in fastboot/download mode ready to get files flashed to it with the several programs listed above. I've had this issue before. Let me know if this worked!

My lg was not properly detected
My lg was not properly detected by windows 7 (plugged it in and nothing happened) and i was still able to use the srk tool. If you have qhusb... detected as the g2 you can unbrick. If it is not detected at all I would still try nuked download mode.
Good luck!! :good:

I really appreciate the tips here guys. I used to have the Qhusb_bulk or whatever reading in device manager, but in my trying to fix that I screwed it up more I think. Now I currently have what is shown in the images below. I've had a few offers to have this fixed for me, so I'll basically go in the order I received the PMs/posts. I'll do my best to provide everyone with enough info to make sure he/she can fix it without too much trouble.
Device manager (after choosing dload mode in Demigod)
{
"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"
}
Demigod crash (after trying to enter recovery)

The only way your gonna fix it is to use above mention link done it many time g2 is unbrickable with said link i crossed roms models radios everything on mine takes like 10 or 15 minnacter youve done it a few times fairly easy even for people thats not technicly in inclined

dudeimstoked said:
Hi,
I initially soft bricked my LG G2 D801 by clearing everything in TWRP. Tried to fix it, went through a bunch of threads and tried different tools but ended up just screwing it up more, now a hard brick. Currently will not go into download mode or TWRP. In device manager it is listed as "LG Android USB Device". Also will continuously restart unless I go into "recovery mode" where it will go into Demigod crash. I basically give up because I dont know what I'm doing.
My proposal:
I will ship you the phone, you fix it and ship it back to me
I will pay you $50 for your trouble via paypal or check
Any other information you need from me to see if it is unbrickable?
Click to expand...
Click to collapse
Man I know how you feel, it sucks having a bricked phone. Anyways, I totally can relate to your situation. I had a hard bricked (Verizon G2), which I did repair on my own. At first I did spend hours on end going through forum after forum, method after method. All of them stumped me. Well after all the forums, I pretty much sat there on my own and tried to figure out the pieces. I knew that when we flash something to our phone, it has to flash to the motherboard. So a bad flash (hard bricked phone) means oh no the motherboard is dead since the phone is totally unresponsive. I ended up doing a motherboard replacement (yes I did take the phone apart myself and it was my first time), and success! The phone was revived. The process is definitely possible, but again it might not be the right solution for everyone. Just wanted to share my thoughts regarding this issue!
Side note: If you want to go this route I will need to order a motherboard for your model. Depending on how long it could take to arrive, it might be awhile before you get it back repaired. I will have to use the money to purchase the board.

all fixed. thanks to xmayhemreturnsx for the good work.

Please try enter to download mode and flas to stock kdz or enter to twrp and plug your pc if your computer seem the phone same mtp device copy a cyanegonmod rom and install

Lg g3 auto-rec "hard brick" fix

Hello everyone, first let me give major props to my man @bender_007 for creating the amazing LG G Series Autorec Apps which make installing TWRP on LG G Devices a simple process and for also helping me and others who ignorantly misused his app, thanks B!
Anyway recently I bought a LG G3 on Verizon that was on 35b 5.1.1 Lollipop and I rooted. Boy was I eager to get some TWRP poppin on this beast, however flashing TWRP thru Flashify and TWRP Manager left me unsuccessful giving me Secure Booting Error. So desperate I seen Autorec on the Play Store, installed immediately. From there I went through the app's proccesses and from there attempted to boot into recovery hoping for some success.... I did not realize this was went for 24b 5.0.1 until it was late, I mean hey he says it in the description. The phone was dead it wouldn't show anything on the display when I held the power button and it only vibrated, I was f***ed.... At least that is what I thought. I used the method below that me and @bender_007 were collaborating upon as he tried to help me. So please give him credit. I cannot guarantee this will work for you but it worked for me and you don't have to worry about opening up your phone and shorting pins, that nonsense if this works for you.
MATERIALS
A FUNCTIONAL COMPUTER (PREFERABLY WINDOWS, I USED WINDOWS 7)
LG FLASH TOOL 2014: http://www.mediafire.com/?fwrcd3pdj0svjtb
LG DRIVERS-
UNIVERSAL: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
VERIZON:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
THE LATEST KDZ FOR YOUR PHONE MODEL (GOOGLE IT)
Your Dead but Still Amazing LG G3 and a USB Cable
Note: IF DONE PROPERLY YOU WILL STILL HAVE ALL YOUR EXSISTING DATA PRE-BRICK
PROCEDURE
1. Gather all materials, and know the locations of all your downloaded files.
2. Install the drivers for your phone.
3. Unzip LGFlashTool_2014.zip
4. Move the .KDZ you should've downloaded to the LGFLASHTOOL_2014 folder.
5. Open Device Manager (press start, type in Device Manager into search bar, hit enter)
6. Click View, "Show Hidden Devices"
7. PLUG in USB CABLE TO COMPUTER ONLY!
8. THIS STEP IS VERY VERY VERY IMPORTANT! TAKE THE BATTERY OUT OF YOUR LG G3. PUT IT BACK IN. CLOSE THE BACK. HOLD VOLUME UP ONLY, WHILE HOLDING POWER UP DO NOT LET GO PLUG IN OTHER HALF OF USB CABLE INTO PHONE. KEEP HOLDING VOLUME UP FOR 20 SECONDS. YOURE PHONES SCREEN WILL STILL BE BLACK AND IT SHOULDVE VIBRATED ABOUT 2 SECONDS AFTER YOU PLUGGED IN WIRE (You'll know when you do it right when COMPUTER says installing drivers in bottom right corner.)
9. In Device Manager under Modems there should be something like LGandroidNET I DONT REMEMBER EXACTLY THIS IS ALL OFF THE TOP OF MY HEAD. Anyway, if it says that then you are good, believe it or not your in download mode. (IF YOU DO NOT SEE THIS REPEAT STEP 8)
10. Go to LGFlashTool_2014 folder and run the LGFlashTool2014.exe application.
11. Change PhoneMode to Emergency
12. For "SELECT KDZ FILE" open the folder of the the FlashTool, it should be on it by default and pick the KDZ file.
13. Click "Normal Flash"
14. On the next SCREEN click "START" at the bottom
15. Now there should be a pop-up that says "Select Country & Language" Do not mess with this, just click "OK"
16. There should be a SCREEN now that has a % or whatever... From HERE TO THE END OF IT DO NOT UNPLUG YOUR PHONE!!!
17. When you hit like 85% your phone will boot up do not UNPLUG still and once it hits 100% your done! Safe to UNPLUG and YOU FIXED YOUR PHONE!!!!!!
If you have any questions please ask I have pure empathy for anyone who goes through this hell.

The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?

wombatthing said:
The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?
Click to expand...
Click to collapse
Okay I'm here to provide my best assistance and for that you'll have to answer a few questions?
1. What is your device model? ex. VS985 Verizon
2. What KDZ did you attempt to flash? ex. VS98547a_01.kdz
Looking forward to your reply.
Sent from my VS985 4G using Tapatalk

@wombatthing I would go to device manager go to view "Show Hidden devices" then disconnect your phone take out battery put it back in close back then hold volume up for 20 SECONDS while doing that connect to computer. It probably won't say installing drivers because you said it worked the First time, from there see if it's under Modems. Good luck my friend in here for any questions
Sent from my VS985 4G using Tapatalk

Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks

Ray1000 said:
Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks
Click to expand...
Click to collapse
My friend all is good. First of all as long as it says LGandroidnet you are good you should be in download mode, in lg flash took for mode click emergency and not diag then click normal flash THIS WILL KEEP YOURE DATA IF YOU SEE CRS FLASH OR SOMETHING LIKE THAT THEN ITLL RESET YOURE PHONE just do Emergency and Normal Flash and it should work. Hope I help if you have questions please ask.

@Ray1000 "Emergency" Mode is just Download Mode flashing. Diag is not that's why you were unsuccessful.

Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00

For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64

mackleroar said:
Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00
Click to expand...
Click to collapse
Sorry for the late response. First of all you are welcome. I don't know if you fixed the problem yet but I'll help anyway. First remove youre battery for at least 10 seconds then put battery in, hold up and connect charger for 20 seconds. Of you are unsuccessful try reinstalling drivers. Best of luck my friend.
Sent from my VS985 4G using Tapatalk

Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!

Perezvon said:
Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Im having the same problem!!!!!! I've tried everything. I will let you know if I fix it and please let me know if you get your's running?

Does anyone know if this method will work for the Sprint LS990 variant? I too had my phone broke by autorec and I lost download bit have access to TWRP and can flash roms but can't do a factory reset with the LG Flash Tool.
Sent from my LG-ls990 using Tapatalk

Failed to flash
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
{
"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"
}
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!

i also cannot find the Qualcomm's driver on windows 10 & phone looses communication with flash tool..

vajee555 said:
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!
Click to expand...
Click to collapse
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me

ayarihime said:
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me
Click to expand...
Click to collapse
Hello. I managed to get my device to work. Flashed a stock MM rom and now stucked with damn Mcfee kill switch. Can not go to download mode either . Any idea how to fix this? Thanks!

Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC

mjmaxint said:
Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC
Click to expand...
Click to collapse
Hello, I had to short some other two pins to get it identified by my PC. The pins mentioned it this post did not work for me. Follow the link given below and it will work for you. Thank me later.
http://forum.gsmhosting.com/vbb/f494/how-hard-unbricked-lg-g3-all-variants-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/

He guys thank you very much. My LG3 was already down for months after many failed attempts and I was about to bin it. Decided to give it one last try, found your instructions and it works, I now have Marshmallow!! (However I downloaded the KDZ file from "downloadmirror.de" and I am not sure if that was a good idea.

Help with invalid IMEI fater rebooting phone?

Hey guys, I'm trying to fix an lg spirit (h440n)
The phone ran out of battery, and later when I charged it and rebooted, I couldn't get any service, and later realized that the IMEI is now invalid and is listen as "unknown" (as well as a couple of other things). Also, for whatever reason the phone takes a much longer time to boot up.
I'd really appreciate if anyone could assist me with restoring the IMEI.
So far I tried doing a factory reset, which didn't help at all (and now for whatever reason the youtube app appears as a generic android icon with the name com.google.android.youtube...etc.)
I do still have the original IMEI cause i saved the box from the phone.
By the way, I'm on android 6.0

kiraqu33n said:
Hey guys, I'm trying to fix an lg spirit (h440n)
The phone ran out of battery, and later when I charged it and rebooted, I couldn't get any service, and later realized that the IMEI is now invalid and is listen as "unknown" (as well as a couple of other things). Also, for whatever reason the phone takes a much longer time to boot up.
I'd really appreciate if anyone could assist me with restoring the IMEI.
So far I tried doing a factory reset, which didn't help at all (and now for whatever reason the youtube app appears as a generic android icon with the name com.google.android.youtube...etc.)
I do still have the original IMEI cause i saved the box from the phone.
By the way, I'm on android 6.0
Click to expand...
Click to collapse
Try to reflash your stock rom with lg flash tool.

mayankjet said:
Try to reflash your stock rom with lg flash tool.
Click to expand...
Click to collapse
Hi,
so I tried doing that, but I keep running into several errors:
1) If I try doing a normal flash using a stock v20b ROM (android 6.0), the flashing software gives me an error saying "Problem with communication between cell phone and PC". It has some instructions on what to do to restart the flashing process, but it still doesn't work for me even if I do them
2) Flashing the v20b ROM with with the CSE flash method, I get an error on the program saying "Required info cannot be found. Contact the system administrator.."
3) Flashing a 10i ROM (android 5) with the CSE method, the flashing process goes to about 9% on the PC, then my phone reboots and for a split second displays an error with all red letters saying "Boot verification Fail!! cause : DIFFERENT_HASH", and after that the phone reboots as normal and the flashing process is once again failed.
I honestly don't understand where the problem is... I hope it's still possible to solve

kiraqu33n said:
Hi,
so I tried doing that, but I keep running into several errors:
1) If I try doing a normal flash using a stock v20b ROM (android 6.0), the flashing software gives me an error saying "Problem with communication between cell phone and PC". It has some instructions on what to do to restart the flashing process, but it still doesn't work for me even if I do them
2) Flashing the v20b ROM with with the CSE flash method, I get an error on the program saying "Required info cannot be found. Contact the system administrator.."
3) Flashing a 10i ROM (android 5) with the CSE method, the flashing process goes to about 9% on the PC, then my phone reboots and for a split second displays an error with all red letters saying "Boot verification Fail!! cause : DIFFERENT_HASH", and after that the phone reboots as normal and the flashing process is once again failed.
I honestly don't understand where the problem is... I hope it's still possible to solve
Click to expand...
Click to collapse
Go to this link
http://techtrickszone.com/2017/12/06/invalid-imei-number-after-flashing-android-phone/
If the above method doesn't work then try to flash lollipop rom with LG UP software as it is possible that the lg support tool could be having trouble flashing the rom.
Also please post a screenshot of the issue.

mayankjet said:
Go to this link
If the above method doesn't work then try to flash lollipop rom with LG UP software as it is possible that the lg support tool could be having trouble flashing the rom.
Also please post a screenshot of the issue.
Click to expand...
Click to collapse
Seems like the method you sent me in the link requires for my LG to be rooted, which I don't think I'll be able to do - none of the one click root methods worked cause android 6.0 seems to have fixed the exploit those programs use, and doing it manually might also be troublesome cause I can't get the download mode to work with the phone.(Like I mentioned, the error "Boot verification Fail!! cause : DIFFERENT_HASH"). Sorry, I'm not able to post an image of the error cause I'm still a new user on the forums...
So I think LGUP might be my only hope at this point, but I can't get it to recognize my phone. It just shows up as an unknown device and I can't proceed with the flashing process

kiraqu33n said:
Hey guys, I'm trying to fix an lg spirit (h440n)
The phone ran out of battery, and later when I charged it and rebooted, I couldn't get any service, and later realized that the IMEI is now invalid and is listen as "unknown" (as well as a couple of other things). Also, for whatever reason the phone takes a much longer time to boot up.
I'd really appreciate if anyone could assist me with restoring the IMEI.
So far I tried doing a factory reset, which didn't help at all (and now for whatever reason the youtube app appears as a generic android icon with the name com.google.android.youtube...etc.)
I do still have the original IMEI cause i saved the box from the phone.
By the way, I'm on android 6.0
Click to expand...
Click to collapse
Go to this link:
https://lg-kdz-firmware.com/check-your-firmware.html
Open your phone from the back and remove the battery, then you will find the IMEI, write it on that site that i put a link to and you can find the right firmware for your phone, download it, download lg drivers (search on google for them) and install them, then try flashing with LG Flash Tool 2014, and make settings to be like this:
Select Type: CDMA,
PhoneMode: CS_EMERGENCY
and flash with CSE Flash.
To go in download mode turn off your phone and hold the volume down button while holding enter the usb cable in to the phone but it should previously be connected to the pc, hold volume down button until you sea a screen that shows you that you are in download mode than start the tool from your pc and flash the firmware.
Hope this helps.

Tin40 said:
Go to this link:
https://lg-kdz-firmware.com/check-your-firmware.html
Open your phone from the back and remove the battery, then you will find the IMEI, write it on that site that i put a link to and you can find the right firmware for your phone, download it, download lg drivers (search on google for them) and install them, then try flashing with LG Flash Tool 2014, and make settings to be like this:
Select Type: CDMA,
PhoneMode: CS_EMERGENCY
and flash with CSE Flash.
To go in download mode turn off your phone and hold the volume down button while holding enter the usb cable in to the phone but it should previously be connected to the pc, hold volume down button until you sea a screen that shows you that you are in download mode than start the tool from your pc and flash the firmware.
Hope this helps.
Click to expand...
Click to collapse
Hi, I can't get my phone into download mode, the phone displays an error: "Boot verification Fail!! cause : DIFFERENT_HASH", and just reboots like normal and the flashing process ends up failing... I guess the download mode on my phone is somehow broken, though I can't find any way to fix it

kiraqu33n said:
Hi, I can't get my phone into download mode, the phone displays an error: "Boot verification Fail!! cause : DIFFERENT_HASH", and just reboots like normal and the flashing process ends up failing... I guess the download mode on my phone is somehow broken, though I can't find any way to fix it
Click to expand...
Click to collapse
To enter download mode phone must be turned off then press and hold vol. Up button then plug in the usb cable. It is not the volume down button.
If Lg Up recognizes your phone as unknown device that's normal as it has happened to me as well. See if you can enter in download mode with keys, if you can't, just keep your phone booted into rom then start flashing lollipop kdz and your phone should automatically boot into download mode.

On my LG Spirit 4G LTE h440n is the volume down button. The volume up is to go into the bootloader.

mayankjet said:
To enter download mode phone must be turned off then press and hold vol. Up button then plug in the usb cable. It is not the volume down button.
If Lg Up recognizes your phone as unknown device that's normal as it has happened to me as well. See if you can enter in download mode with keys, if you can't, just keep your phone booted into rom then start flashing lollipop kdz and your phone should automatically boot into download mode.
Click to expand...
Click to collapse
In LGUP when my phone shows up as "unknown", I can't do the flashing process cause the program just says "You have to select a known model, please."
Edit: here is a screenshot
{
"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"
}
And about download mode, I know how to get into it, and it is indeed volume up+usb, but like I said, when I enter download mode it just displays that error message about boot verification failed, and the phone just reboots as normal. I thought maybe I'm not explaining it well enough so instead I filmed a video: https://www.youtube.com/watch?v=APlsn5gVvzw&feature=youtu.be

kiraqu33n said:
In LGUP when my phone shows up as "unknown", I can't do the flashing process cause the program just says "You have to select a known model, please."
Edit: here is a screenshot
And about download mode, I know how to get into it, and it is indeed volume up+usb, but like I said, when I enter download mode it just displays that error message about boot verification failed, and the phone just reboots as normal. I thought maybe I'm not explaining it well enough so instead I filmed a video:
&feature=youtu.be
Click to expand...
Click to collapse
Take a look at this thread.
https://forum.xda-developers.com/g-flex2/help/lgup-unknown-device-t3403402

mayankjet said:
Take a look at this thread.
https://forum.xda-developers.com/g-flex2/help/lgup-unknown-device-t3403402
Click to expand...
Click to collapse
Tried everything in that thread, but sadly the result is still the same. I also followed a tutorial in this thread https://forum.xda-developers.com/lg-spirit/how-to/how-to-install-marshmallow-lg-spirit-t3490045 but my phone is still not recognized by LGUP. I'm certain I followed the instructions correctly

kiraqu33n said:
Tried everything in that thread, but sadly the result is still the same. I also followed a tutorial in this thread https://forum.xda-developers.com/lg-spirit/how-to/how-to-install-marshmallow-lg-spirit-t3490045 but my phone is still not recognized by LGUP. I'm certain I followed the instructions correctly
Click to expand...
Click to collapse
Sorry then as i can't think of anything else. If your phone is still under warranty period you can always send it to service center.

mayankjet said:
Sorry then as i can't think of anything else. If your phone is still under warranty period you can always send it to service center.
Click to expand...
Click to collapse
Ahh that's too bad. Well, thank you for your help either way! Sadly, the phone isn't covered by warranty anymore..
I think my best bet is to make the download mode work correctly. I guess I will have to keep searching

I have an LG Spirit 4G (H440n) that lost its IMEI a month ago after shutting down because of a drained battery. After turning it on, the SIM card never got read and the IMEI was unknown. Following a lot of hurdles to reflash a .kdz from download mode I managed to flash a MM firmware and the phone rebooted with its IMEI intact. Then, after a while the phone shut down with a drained battery and the same thing happened. I reflashed and fixed it.
After that... Yeah, the phone shut down after a battery drain and now it doesn't have its IMEI again. Is there any way to restore it and keep there for good without reflashing the whole device from download mode? What could be causing? Should I watch out for the battery forever now?

hitmancho said:
I have an LG Spirit 4G (H440n) that lost its IMEI a month ago after shutting down because of a drained battery. After turning it on, the SIM card never got read and the IMEI was unknown. Following a lot of hurdles to reflash a .kdz from download mode I managed to flash a MM firmware and the phone rebooted with its IMEI intact. Then, after a while the phone shut down with a drained battery and the same thing happened. I reflashed and fixed it.
After that... Yeah, the phone shut down after a battery drain and now it doesn't have its IMEI again. Is there any way to restore it and keep there for good without reflashing the whole device from download mode? What could be causing? Should I watch out for the battery forever now?
Click to expand...
Click to collapse
Wow this really is strange. Just to be clear, this phone I was trying to fix was being used by my dad, not me, and he also said the problems started happening after his battery got drained. Unlike you, however, I never managed to even flash a stock ROM to the phone, cause for me the download mode still doesn't work.
Any LG gurus out there know what's going on with these phones?

I can't post links on threads but i found a video, not sure if it helps or if it works but you got nothing to lose, PM me and i'll send you the link.

Bricked OnePlus 6T, messed up big time! Possible long thread ahead.

Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Oh, now I kind of forgot to edit this - My phone is back working again after RMA.

no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.

shawek said:
no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.
Click to expand...
Click to collapse
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.

xnutzii said:
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.
Click to expand...
Click to collapse
Can you sideload the OOS zip via stock recovery?

MarcoLK said:
Can you sideload the OOS zip via stock recovery?
Click to expand...
Click to collapse
Let me see, what's the cmd command for doing so?

xnutzii said:
Let me see, what's the cmd command for doing so?
Click to expand...
Click to collapse
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery

MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
Click to expand...
Click to collapse
Oh, alright, thanks. I'l try

xnutzii said:
Oh, alright, thanks. I'l try
Click to expand...
Click to collapse
Did not work. It says ''cannot read (name).zip''
MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery
Click to expand...
Click to collapse
Also, there is no sideload on the 6T's stock recovery.

xnutzii said:
Did not work. It says ''cannot read (name).zip''
Click to expand...
Click to collapse
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Edit:
There should be an option.
It should look like 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"
}

MarcoLK said:
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Click to expand...
Click to collapse
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again

xnutzii said:
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again
Click to expand...
Click to collapse
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.

MarcoLK said:
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.
Click to expand...
Click to collapse
No problem, thanks for your support.
That was my last option, if nothing helped.
Also, I just saw your edit, there is no option like this, there are ''wipe data and cache'', '' Advanced'' ''Exit''

You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..

Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it

xnutzii said:
Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Click to expand...
Click to collapse
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.

hagar006 said:
You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..
Click to expand...
Click to collapse
I never said it doesn't recognize my phone though. I know how the phone gets recognized by msmdownloadtool, thanks for your input though.

MRobbo80 said:
Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it
Click to expand...
Click to collapse
I have flashed the sh*t outta my phone already, it doesn't work out sadly enough. I have tried everything besides this ↓
twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
This seems very unlikely, but I thank you for your input, let's see if this actually works for me. Hope I get the timing right.

twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/

xnutzii said:
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/
Click to expand...
Click to collapse
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.

twinnfamous said:
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.
Click to expand...
Click to collapse
The problem is not that the phone doesn't connect, it connects right away without any issues with the volume buttons clicked together, the msmtool runs through too! But the phone does NOT boot up after all of this is finished. It goes straight to Qualcomm crashdump mode.